Data Formats Reference Manual

PSS®E 36.1.0
June 2024
Copyright © 1997 - 2024 Siemens Industry, Inc., Siemens Power Technologies International
Information in this manual and any software described herein is confidential and subject to change without notice and does not repre-
sent a commitment on the part of Siemens Industry, Inc., Siemens Power Technologies International. 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 purchaser's personal use, without the express written permission of Siemens
Industry, Inc., Siemens Power Technologies International.
®
PSS E high-performance transmission planning software is a registered trademark of Siemens Industry, Inc., Siemens Power Technolo-
gies International in the United States and other countries.
® ® ®
The Windows 10 and Windows Server 2016 and later operating systems, the Visual C++ development system, Microsoft Office Excel
®
and Microsoft Visual Studio are registered trademarks of Microsoft Corporation in the United States and other countries.
® ®
The Intel Visual Fortran Compiler and Intel oneAPI Toolkit for Windows is a trademark of Intel Corporation in the United States and
other countries.
TM
The Python programming language is a trademark of the Python Software Foundation.

Other names may be trademarks of their respective owners.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
ii
Table of Contents
Power Flow Data File (RAW) .............................................................................................................. 1
Overview ................................................................................................................................. 1
Extended Bus Names ................................................................................................................ 1
Default Values .......................................................................................................................... 2
Q Record .................................................................................................................................. 2
Case Identification Data ............................................................................................................ 4
System-Wide Data .................................................................................................................... 5
GENERAL Record ............................................................................................................... 6
GAUSS Record .................................................................................................................. 6
NEWTON Record ............................................................................................................... 7
ADJUST Record ................................................................................................................. 8
TYSL Record ..................................................................................................................... 8
SOLVER Record ................................................................................................................. 9
BRANCH RATING NAME Record ........................................................................................ 10
SWITCHING DEVICE RATING NAME Record ......................................................................... 10
Bus Data ................................................................................................................................ 11
Bus Data Notes ............................................................................................................... 13
Load Data .............................................................................................................................. 13
Load Data Notes ............................................................................................................. 15
Constant Power Load Characteristic ................................................................................. 15
Constant Current Load Characteristic ............................................................................... 16
Fixed Bus Shunt Data .............................................................................................................. 17
Fixed Shunt Data Notes ................................................................................................... 19
Voltage Droop Control Data ..................................................................................................... 19
Voltage Droop Control Data Notes ................................................................................... 21
Generator Data ....................................................................................................................... 21
Reactive Power Limits ..................................................................................................... 25
Modeling of Generator Step-Up Transformers (GSU) .......................................................... 25
Multiple Machine Plants .................................................................................................. 26
Switching Device Rating Table Data ......................................................................................... 27
Non-Transformer Branch Data .................................................................................................. 29
Zero Impedance Lines ..................................................................................................... 32
System Switching Device Data ................................................................................................. 33
Transformer Data .................................................................................................................... 34
Three-Winding Transformer Notes .................................................................................... 50
Example Two-Winding Transformer Data Records ............................................................. 50
Example Three-Winding Transformer Data Records .......................................................... 51
Transformer Vector Group Clock Position and Phase Angle ................................................. 52
Two Winding Transformer Vector Groups .......................................................................... 54
Three Winding Transformer Vector Groups ........................................................................ 55
Areas, Zones and Owners ....................................................................................................... 57
Area Interchange Data ............................................................................................................ 59
Area Interchange Data Notes ........................................................................................... 60
Two-Terminal DC Transmission Line Data .................................................................................. 61
Two-Terminal DC Line Data Notes .................................................................................... 65
Voltage Source Converter (VSC) DC Transmission Line Data ........................................................ 65
VSC DC Line Data Notes .................................................................................................. 68
Transformer Impedance Correction Tables ................................................................................ 69

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
iii
Data Formats Reference Manual

Impedance Correction Table Notes ................................................................................... 70

Multi-Terminal DC Transmission Line Data ................................................................................ 72
Multi-Terminal DC Line Notes .......................................................................................... 78
Multi-Section Line Grouping Data ............................................................................................ 79
Multi-Section Line Example ............................................................................................. 80
Multi-Section Line Notes ................................................................................................. 81
Zone Data .............................................................................................................................. 81
Zone Data Notes ............................................................................................................. 82
Interarea Transfer Data ............................................................................................................ 82
Interarea Transfer Data Notes .......................................................................................... 83
Owner Data ........................................................................................................................... 83
FACTS Device Data .................................................................................................................. 84
FACTS Device Notes ........................................................................................................ 88
Switched Shunt Data .............................................................................................................. 89
Switched Shunt Notes ..................................................................................................... 93
Switched Shunt Example ............................................................................................... 94
GNE Device Data .................................................................................................................... 95
Induction Machine Data .......................................................................................................... 97
Machine Electrical Data ................................................................................................. 101
Load Mechanical Data ................................................................................................... 102
Load Type Data ..................................................................................................................... 102
Load Type Data Notes ................................................................................................... 103
Interface Data ...................................................................................................................... 103
Interface Element Data ......................................................................................................... 104
Substation Data Group .......................................................................................................... 107
Substation Data ............................................................................................................ 108
Node Data .................................................................................................................... 108
Node Data Notes .................................................................................................. 109
Station Switching Device Data ....................................................................................... 110
Equipment Terminal Data .............................................................................................. 111
RAWX Data Table Format for Equipment Terminal Data ............................................ 111
Load Terminal Data ............................................................................................... 112
Fixed Shunt Terminal Data .................................................................................... 113
Machine Terminal Data ......................................................................................... 113
Branch and two winding Transformer Terminal Data ................................................ 113
Three winding Transformer Terminal Data .............................................................. 114
Switched Shunt Terminal Data ............................................................................... 114
Induction Machine Terminal Data ........................................................................... 115
Two-terminal DC Line Terminal Data ....................................................................... 115
Voltage Source Converter (VSC) DC Line Terminal Data ............................................ 116
Multi-terminal DC Line Terminal Data ..................................................................... 116
FACTS Device Terminal Data .................................................................................. 117
End of Data Indicator ............................................................................................................ 117
Power Flow RAW Format Change Summary .................................................................................... 118
Extensible Power Flow Data File (RAWX) ........................................................................................ 127
Overview .............................................................................................................................. 127
Additional RAWX Documentation ................................................................................... 127
Introduction to JSON ............................................................................................................. 128
JSON Data Types ........................................................................................................... 128
RAWX Format Specification ................................................................................................... 129
RAWX File Structure ...................................................................................................... 129

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
iv
Data Formats Reference Manual

Parameter Sets ............................................................................................................. 131

Data Tables .................................................................................................................. 132
Field List Customization ................................................................................................ 133
Custom Field Definitions ............................................................................................... 134
Partial Datasets (Read and Change) ............................................................................... 135
Custom Table Definitions ............................................................................................... 137
Importing/Exporting from CSV files ........................................................................................ 138
Importing RAWX tables from CSV ................................................................................... 138
Exporting RAWX tables to CSV ....................................................................................... 139
Sequence Data File ....................................................................................................................... 141
Overview .............................................................................................................................. 141
Change Code ........................................................................................................................ 142
System Wide Data ................................................................................................................. 142
Generator Sequence Data ...................................................................................................... 143
Load Sequence Data ............................................................................................................. 146
Zero Sequence Non-Transformer Branch Data ......................................................................... 147
Zero Sequence Mutual Impedance Data ................................................................................. 148
Zero Sequence Transformer Data ........................................................................................... 150
Zero Sequence Switched Shunt Data ...................................................................................... 158
Zero Sequence Fixed Shunt Data ........................................................................................... 159
Induction Machine Sequence Data ......................................................................................... 160
Non-Conventional Source - Fault Contribution Characteristics Data ........................................... 162
Non-Conventional Source - Generator Data ............................................................................. 165
Application Notes - Transformers in the Zero Sequence ........................................................... 168
Auto Transformer Equivalent Circuit ............................................................................... 169
Two Winding Transformer Zero Sequence Networks ........................................................ 170
CC=1 and CC=11 .................................................................................................. 170
CC=2 and CC=12 .................................................................................................. 171
CC=3 and CC=13 .................................................................................................. 173
CC=4 and CC=14 ................................................................................................. 175
CC=5 and CC=15 .................................................................................................. 176
CC=6 and CC=16 .................................................................................................. 177
CC=7 and CC=17 .................................................................................................. 179
CC=8 and CC=18 .................................................................................................. 180
CC=9 and CC=19 .................................................................................................. 182
CC=20 ................................................................................................................. 184
CC=21 .................................................................................................................. 186
CC=22 .................................................................................................................. 187
Three Winding Transformer Zero Sequence Network ........................................................ 188
CC=1 and CC=11 (511) ......................................................................................... 189
CC=2 and CC=12 (113) ......................................................................................... 190
CC=3 and CC=13 (313) ......................................................................................... 191
CC=4 and CC=14 (333) ......................................................................................... 192
CC=5 and CC=15 (121) ......................................................................................... 193
CC=6 and CC=16 (111) ......................................................................................... 194
CC=17 .................................................................................................................. 195
CC=18 .................................................................................................................. 197
Optimal Power Flow Data File ........................................................................................................ 198
Overview .............................................................................................................................. 198
Change Code ........................................................................................................................ 199
Bus Voltage Constraint Data .................................................................................................. 199

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
v
Data Formats Reference Manual

Bus Voltage Attribute Record ......................................................................................... 200

Adjustable Bus Shunt Data .................................................................................................... 201
Bus Load Data ...................................................................................................................... 202
Bus Load Record .......................................................................................................... 202
Adjustable Bus Load Table Data ............................................................................................. 203
Adjustable Bus Load Table Record ................................................................................. 203
Generator Dispatch Data ....................................................................................................... 204
Generator Dispatch Data Record ................................................................................... 204
Active Power Dispatch Data ................................................................................................... 205
Active Power Dispatch Record ........................................................................................ 205
Generation Reserve Data ....................................................................................................... 206
Generation Reserve Record ........................................................................................... 206
Generation Reactive Capability Data ....................................................................................... 207
Generation Reactive Capability Record ........................................................................... 207
Adjustable Branch Reactance Data ......................................................................................... 208
Adjustable Branch Reactance Record ............................................................................. 208
Piece-wise Linear Cost Data ................................................................................................... 209
Piece-wise Linear Cost Record ....................................................................................... 210
Piece-wise Quadratic Cost Data .............................................................................................. 210
Piece-wise Quadratic Cost Record ................................................................................. 211
Polynomial and Exponential Cost Table .................................................................................. 212
Polynomial and Exponential Record .............................................................................. 212
Period Reserve Constraint Data .............................................................................................. 213
Period Reserve Constraint Record .................................................................................. 214
Branch Flow Constraint Data ................................................................................................. 215
Branch Flow Constraint Record ..................................................................................... 215
Interface Flow Constraint Data .............................................................................................. 217
Linear Constraint Dependency Data ....................................................................................... 219
Linear Constraint Dependency Record ........................................................................... 219
GIC Data File ................................................................................................................................ 223
Overview .............................................................................................................................. 223
File Identification Data .......................................................................................................... 224
Substation Data .................................................................................................................... 224
Bus Substation Data .............................................................................................................. 226
Transformer Data .................................................................................................................. 226
Fixed Bus Shunt Data ............................................................................................................ 230
Branch Data ......................................................................................................................... 230
User Earth Model Data .......................................................................................................... 231
Switched Shunt Data ............................................................................................................ 232
Two-Terminal DC Data ........................................................................................................... 233
VSC DC Data ........................................................................................................................ 234
Multi-Terminal DC Data ......................................................................................................... 235
FACTS Device Data ................................................................................................................ 235
Load Data ............................................................................................................................ 236
Harmonics Data File (RAWX) .......................................................................................................... 238
Overview .............................................................................................................................. 238
Impedance Characteristics Data ............................................................................................. 239
Voltage Sources Data ............................................................................................................ 240
Current Sources Data ............................................................................................................ 241
Load Data ............................................................................................................................ 243
Generator Data ..................................................................................................................... 245

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
vi
Data Formats Reference Manual

Non-Transformer Branch Data ................................................................................................ 247

Transformer Data .................................................................................................................. 248
Two-Terminal DC Data ........................................................................................................... 250
VSC DC Data ........................................................................................................................ 251
FACTS Device Data ................................................................................................................ 252
Induction (asynchronous) Machine Data ................................................................................. 254
Multi-Terminal DC Data ......................................................................................................... 255
Passive Filter Data ................................................................................................................. 256
Machine Capability Curve Data File ................................................................................................ 259
Overview .............................................................................................................................. 259
Change Code Data ................................................................................................................ 259
Capability Curve Data ............................................................................................................ 259
IEC Data File ................................................................................................................................. 261
Overview .............................................................................................................................. 261
File Identification Data .......................................................................................................... 261
GSU, Equivalent Generator and Motor Data ............................................................................ 262
Transformer Nameplate Winding MVA Data ............................................................................ 263
Induction Machine Data ........................................................................................................ 263
Wind Power Station Asynchronous Generator Data .................................................................. 264
Wind Power Station Doubly Fed Asynchronous Generator Data ................................................. 264
Wind and Photovoltaic Power Station Generator with Full Size Converter Data ........................... 265
SUB/MON/CON File Descriptions ..................................................................................................... 267
Overview .............................................................................................................................. 267
File Notational Conventions ........................................................................................... 267
Bus Input/Output Using Bus Numbers and Names ........................................................... 268
Special Data Records ..................................................................................................... 269
Subsystem Definition Data File .............................................................................................. 269
Monitored Element Data File ................................................................................................. 273
Individual Flow Monitoring Records ............................................................................... 273
Group Flow Monitoring Records ..................................................................................... 274
Subsystem Tie Monitoring Records ................................................................................. 276
Subsystem Switching Device Monitoring Records ............................................................ 280
Voltage Monitoring Records ........................................................................................... 280
Contingency Definition Data File ............................................................................................ 283
Contingency Case Block Structure .................................................................................. 283
Automatic Contingency Specification ............................................................................. 292
Node-Breaker Contingency Specification ......................................................................... 295
Automatic Contingency Specification ..................................................................... 297
Advanced Linear Analysis/MUST SUB/MON/CON File Extensions and Options ...................................... 300
Description of Input Data ...................................................................................................... 300
Input Data Types ........................................................................................................... 300
Conventions and Special Data Records ........................................................................... 300
INCLUDE Record ............................................................................................................ 301
Subsystem Definition Data File .............................................................................................. 302
General Description and Advanced Linear Analysis/MUST Subsystem Extensions ................. 302
Defining Buses within a Subsystem ................................................................................ 303
Subsystem Adjustments Methods ................................................................................... 306
Automatic Specifications Using the ADD Command ......................................................... 307
Defining Buses Using the PARTICIPATE Command ............................................................ 310
Automatic Participation Factors Definition within the SUBSYSTEM Group ........................... 311
Defining New Subsystems Based on Already Defined Subsystems ..................................... 313

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
vii
Data Formats Reference Manual

Adding Subsystems by Bus or Generator ......................................................................... 314

Reporting Available Subsystems ..................................................................................... 315
Subsystem Detailed Report ............................................................................................ 315
Saving Subsystem Adjustments in a Load Flow Case ........................................................ 315
Monitored Element Data File ................................................................................................. 316
General Description and Advanced Linear Analysis/MUST Extensions ................................. 316
Monitored Branches Specifications ................................................................................. 316
DC and Linear Analysis - Branch Limit Checking ...................................................... 316
Non-Linear AC Models - Branch Limit Checking ....................................................... 317
Interface Specifications ................................................................................................. 317
Flowgates Formats ........................................................................................................ 319
Defining Rating Multiplier by Areas or Zones .................................................................. 320
Defining Distribution Factors Cutoff by Control Areas and Zones ....................................... 321
Contingency Definition Data File ............................................................................................ 322
Individual Contingency Specifications ............................................................................. 322
Automatic Contingency Specifications ............................................................................ 323
Single Automatic Contingency Labels – Single Branch ............................................. 323
Single Automatic Contingency Labels – Three-Winding Transformer .......................... 324
Automatic IN Contingencies .................................................................................. 324
Automatic TIE Contingencies ................................................................................. 326
Automatic Generator and Bus Contingencies .......................................................... 326
DISPATCH Record Format ............................................................................................... 327
DISPATCH Record .................................................................................................. 327
Default Dispatch ................................................................................................... 328
Multi-Section Line Outages ............................................................................................ 329
Load Throwover ............................................................................................................ 329
Three-Winding Transformer Contingency ........................................................................ 330
EXCLUDE Data File ................................................................................................................ 331
Why Use an Exclude Data File? ...................................................................................... 331
Exclude Input Data Formats ........................................................................................... 331
Exclude File .................................................................................................................. 332
Summary of Advanced Linear Analysis/MUST File Extensions Not Available in PSS®E ................... 333
General Input Files Extensions ....................................................................................... 333
Subsystems Definition Extension .................................................................................... 334
Monitored Elements Files Extensions .............................................................................. 334
Contingency Data File Extensions .................................................................................. 334
Simulation Run Assembler PSAS User’s Ready Reference .................................................................. 336
NOTES: ............................................................................................................................... 340
PSAS Command Help ............................................................................................................ 341
®
User-Entered PSS E Commands .............................................................................................. 341
PSAS Input Files .................................................................................................................... 341
To Execute PSAS From PSSDS4 ............................................................................................... 341
Sample PSAS Command File .................................................................................................. 341
NOTES: ................................................................................................................................. 342
Engineering Basic PSEB User’s Ready Reference ............................................................................... 343
NOTES: ............................................................................................................................... 345
PSEB Command Help ............................................................................................................ 346
®
User-Entered PSS E Commands .............................................................................................. 346
PSEB Input Files .................................................................................................................... 346
To Execute PSEB From PSSLF4 ................................................................................................ 346
Sample PSEB Command File .................................................................................................. 346

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
viii
Data Formats Reference Manual

NOTES: ................................................................................................................................. 347

Graphic Report Generator GRPG User’s Ready Reference .................................................................. 348
NOTES: ............................................................................................................................... 352
GRPG Command Help ........................................................................................................... 353
GRPG Input Files ................................................................................................................... 353
To Execute GRPG From PSSLF4 ............................................................................................... 353
Sample GRPG Command File ................................................................................................. 353
Locations Data File ....................................................................................................................... 355
Overview .............................................................................................................................. 355
Record Block Format ............................................................................................................. 355
Block Identifier ..................................................................................................................... 355
Block Locations Data Format ................................................................................................. 355
Locations Data - BUSES ......................................................................................................... 356
Locations Data - BRANCHES ................................................................................................... 357
Locations Data - NODES ........................................................................................................ 358
Location Data File - Example ................................................................................................. 358

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
ix
List of Figures
Load Representation on Bus ............................................................................................................ 13
Constant Power Load Characteristics ................................................................................................ 16
Constant Current Load Characteristics .............................................................................................. 17
Fixed Shunt Representation on Bus .................................................................................................. 17
Generator QV characteristic ............................................................................................................. 19
Generator Representation on Bus .................................................................................................... 21
Implicit GSU Configuration – Specified as Part of the Generator ........................................................ 26
Explicit GSU Configuration– Specified Separately from the Generator ................................................. 26
Multiple Generators at a Single Plant ............................................................................................... 27
Data Set for the Multiple Generators in Figure 1.9 ............................................................................ 27
Equivalent PI model of a Long Transmission Line .............................................................................. 29
Two and Three-winding Transformer Configurations Related to Data Records ....................................... 35
Sample Data for Two-Winding Transformer ....................................................................................... 51
Sample Data for Three-Winding Transformer ..................................................................................... 52
Two Winding Transformer Vector Group Clock Position and Phase Angle ............................................. 52
Three Winding Transformer Vector Group Clock Position and Phase Angle ........................................... 53
Overlapping Areas and Zones .......................................................................................................... 58
Two Terminal DC Configuration ....................................................................................................... 61
VSC DC Configuration ..................................................................................................................... 65
Typical Impedance Correction Factor Curve ....................................................................................... 72
Multi-Terminal DC Configuration ...................................................................................................... 72
Multi-Terminal DC Network .............................................................................................................. 79
Multi-Section Line Grouping ............................................................................................................ 79
Multi-Section Line Example ............................................................................................................. 80
Interarea Transfer ........................................................................................................................... 82
Owner Data ................................................................................................................................... 83
FACTS Device Configuration ............................................................................................................ 84
FACTS Control Device Setpoints and Limits ....................................................................................... 89
Switched Shunt Configuration ......................................................................................................... 89
Example Data Record for Combination of Switched Shunts ................................................................ 95
Induction Machine Equivalent Circuit ............................................................................................. 101
Generator Sequence Networks ....................................................................................................... 146
Mutual Coupline - Example 1 ........................................................................................................ 150
Mutual Coupline - Example 2 ........................................................................................................ 150
Two-Winding Transformer Positive Sequence Connections ............................................................... 157
Three-Winding Transformer Positive Sequence Connections ............................................................. 158
Induction Machine Sequence Network ........................................................................................... 161
Non-conventional Source Fault Contribution Characteristics ............................................................. 164
Non-conventional Source Sequence Network .................................................................................. 165
Auto-transformer Equivalent Circuit ............................................................................................... 169
YNyn transformer zero sequence network ...................................................................................... 170
YNyn with neutral impedance transformer zero sequence network ................................................... 170
YNd transformer zero sequence network ........................................................................................ 171
Znyn, Zny, or ZNd transformer zero sequence network .................................................................... 171
YNy core type transformer zero sequence network .......................................................................... 172
Dyn transformer zero sequence network ........................................................................................ 173
YNzn, Yzn or Dzn transformer zero sequence network ..................................................................... 173
Yyn core type transformer zero sequence network .......................................................................... 174

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
x
Data Formats Reference Manual

Yy, Yd, Dy, Dd, Yyn or YNy transformer zero sequence network ........................................................ 175
Ya ungrounded auto transformer zero sequence network ................................................................ 175
CC=5 or CC=15 zero sequence network .......................................................................................... 176
YNd transformer with Zigzag or YNd earthing transformer on winding 2 side zero sequence network ... 177
YNzn or Dzn core type transformer zero sequence network ............................................................. 178
Dyn transformer with Zigzag or YNd earthing transformer on winding 1 side zero sequence network ... 179
ZNyn or ZNd core type transformer zero sequence network ............................................................. 179
YNa core type auto transformer zero sequence network .................................................................. 180
YNa core type auto transformer zero sequence network .................................................................. 182
YNyn with or without neutral impedance core type transformer zero sequence network ..................... 184
YNa auto transformer zero sequence network ................................................................................. 186
Ya ungrounded core type auto transformer zero sequence network .................................................. 187
YNynyn with magnetising impedance modelled transformer zero sequence network .......................... 189
YNynd transformer zero sequence network .................................................................................... 190
Dynd transformer zero sequence network ...................................................................................... 191
Ddd, Ddy, Dyd, Dyy, Ydd, Ydy, Yyd or Yyy transformer zero sequence network ................................... 192
Dynd auto transformer zero sequence network ............................................................................... 193
YNynyn transformer zero sequence network ................................................................................... 194
Ynad (grounded) auto transformer zero sequence network .............................................................. 195
o
Equivalent zero sequnce network for a transformer with two externally available neutrals and 0 phase shift
between windings 1 and 2 ............................................................................................................ 195
Yad (ungrounded) auto transformer zero sequence network ............................................................ 197
Capability Curve Example file savnw.gcp for savnw.sav Case ............................................................ 260

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
xi
List of Tables
Power Flow Raw Data Input Structure ................................................................................................ 2
Examples of Two Winding Transformer Vector Groups ....................................................................... 54
Clock Positions and Phase Angles specified in Transformer Power Flow Data ........................................ 55
Three Winding CC=11 ..................................................................................................................... 56
Three Winding CC=12 ..................................................................................................................... 56
Three Winding CC=13 ..................................................................................................................... 56
Three Winding CC=14 ..................................................................................................................... 56
Three Winding CC=15 ..................................................................................................................... 56
Three Winding CC=16 ..................................................................................................................... 57
Three Winding CC=17 ..................................................................................................................... 57
Three Winding CC=18 ..................................................................................................................... 57
Sequence Data Input Structure ...................................................................................................... 141

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
xii
 Chapter 1
Power Flow Data File (RAW)

1.1. Overview
The input stream to activity READ consists of 28 groups of records, with each group containing a particular
type of data required in power flow work (refer to Table 1.1). The end of each category of data, except the
Case Identification Data, is indicated by a record specifying a value of zero; the end of the system-wide, FACTS
device, DC line, and GNE device data categories may alternatively be indicated with a record specifying a
NAME value with blanks.

1.1. Extensible Power Flow Data File (RAWX) Documentation

Documentation for the Extensible Power Flow Data File (RAWX) is located in two places. This chapter contains
consolidated syntax and data field documentation for both RAW and RAWX. The sections describing case
identification, system-wide data, and all network element records include the record formats and data item
descriptions for the RAW file records as well as the RAWX parameter sets and data tables. For the complete
documentation for the RAWX format, see the Extensible Power Flow Data File (RAWX) chapter.

1.2. Extended Bus Names

On its Bus Data record, each bus is assigned a bus number and a 12 character alphanumeric name. When
the bus names input option of activity READ is enabled, data fields designating buses on load, fixed shunt,
generator, non-transformer branch, transformer, area, two-terminal dc line, VSC dc line, multi-terminal dc
line, multi-section line, FACTS device, switched shunt, GNE device, and induction machine, data records may
be specified as either extended bus names enclosed in single quotes or as bus numbers.

The requirements for specifying an extended bus name are:

• The extended name of a bus is a concatenation of its 12 character alphanumeric name and its base voltage.

• It must be enclosed in single quotes.

• The 12 character bus name, including any trailing blanks, must be the first 12 characters of the extended
bus name.

• The bus base voltage in kV follows the 12 character bus name. Up to 6 characters may be used.

• For those data fields for which a sign is used to indicate a modeling attribute, a minus sign may be specified
between the leading single quote and the first character of the 12 character bus name.

Thus, valid forms of an extended bus name include 'aaaaaaaaaaaavvvvvv' and 'aaaaaaaaaaaavvv'. For
those data fields cited in (4) above, '-aaaaaaaaaaaavvvvvv' and '- aaaaaaaaaaaavvv' are also valid forms
of extended bus names.

As an example, consider a 345 kV bus with the name ERIE BLVD. The following are all valid forms of its
extended bus name:

'ERIE BLVD 345.0'

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
1
Power Flow Data File (RAW) Default Values

'ERIE BLVD 345'

'ERIE BLVD 345'

The following is not a valid form of its extended bus name because the bus name, including trailing blanks,
are not all included before the start of the base voltage:
'ERIE BLVD345'

1.3. Default Values

All data is read in free format with data items separated by a comma or one or more blanks; [Tab] delimited
data items are not recommended.

Because there are default values for many of the data items specified in the Power Flow Raw Data File, you
can include only the specific information you need. For example, if bus 99 is a 345 kV Type 1 bus assigned
to zone 3, the Bus Data record in the file could be:

99,,345,,,3

This is equivalent to specifying the data record:

99,' ',345.0,1,1,3,1,1.0,0.0

If, in addition, you name the bus 'ERIE BLVD', the minimum data line would be:

99,'ERIE BLVD',345,,,3

1.4. 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 transmission 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

• the second or subsequent records of the series of data records defining a GNE device

Table 1.1. Power Flow Raw Data Input Structure

Case Identification Data

System-Wide Data

Bus Data

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
2
Power Flow Data File (RAW) Q Record

Load Data

Fixed Bus Shunt Data

Voltage Droop Control Data

Generator Data

Switching Device Rating Tables

Non-Transformer Branch Data

System Switching Device Data

Transformer Data

Area Interchange Data

Two-Terminal DC Transmission Line Data

Voltage Source Converter (VSC) DC Transmission Line Data

Transformer Impedance Correction Tables

Multi-Terminal DC Transmission Line Data

Multi-Section Line Grouping Data

Zone Data

Interarea Transfer Data

Owner Data

FACTS Device Data

Switched Shunt Data

GNE Device Data

Induction Machine Data

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
3
Power Flow Data File (RAW) Case Identification Data

Load Type Data

Interface Data

Interface element Data

Substation Data

Q Record

Each substation block data consists of following records.

Substation Data Record

Node Data

Station Switching Device Data

Equipment Terminal Data

1.5. Case Identification Data

Case identification data consists of 8 data items on 3 lines for case-wide parameters and case identification.

RAW Record Format

IC, SBASE, REV, XFRRAT, NXFRAT, BASFRQ

TITLE1

TITLE2

RAWx Record Format

"caseid":{
"fields":["ic", "sbase", "rev", "xfrrat", "nxfrat", "basfrq", "title1",
"title2"],
"data":[0, 100.00, 35, 0, 1, 60.00, "", ""]
}

Field RAWX Key Description

IC ic New case flag:

0 for base case input (i.e., clear the working case before adding data to it)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
4
Power Flow Data File (RAW) System-Wide Data

Field RAWX Key Description

1 to add data to the working case

IC = 0 by default
SBASE sbase System MVA base

SBASE = 100.0 by default

REV rev PSSE revision number

REV = current revision by default

XFRRAT xfrrat Units of transformer ratings (refer to Transformer Data). The transformer percent
loading units program option setting (refer to Saved Case Specific Option Set-
tings) is set according to this data value.

XFRRAT <= 0 for MVA

XFRRAT > 0 for current expressed as MVA

XFRRAT = present transformer percent loading program option setting by default

(refer to activity OPTN).
NXFRAT nxfrat Units of ratings of non-transformer branches (refer to Non-Transformer Branch
Data). The non-transformer branch percent loading units program option setting
(refer to Saved Case Specific Option Settings) is set according to this data value

NXFRAT <= 0 for MVA

NXFRAT > 0 for current expressed as MVA

NXFRAT = present non-transformer branch percent loading program option set-

ting by default (refer to activity OPTN).
BASFRQ basfrq System base frequency in Hertz. The base frequency program option setting (refer
to Saved Case Specific Option Settings) is set to this data value. BASFRQ = present
base frequency program option setting value by default (refer to activity OPTN).
TITLE1 title1 First line of the case title. May contain up to 60 characters.
TITLE2 title2 Second line of the case title. May contain up to 60 characters.

When current ratings are being specified, ratings are entered as:
-6
MVArated = √ 3 x Ebase x Irated x 10

where:

Ebase Is the branch or transformer winding voltage base in volts.

Irated Is the rated phase current in amps

1.6. System-Wide Data

Through the system-wide data category, data that pertains to the case as a whole (rather than to individual
equipment items) may be included in the Power Flow Raw Data File to allow convenient transfer of it with
the case. Records may be included that define:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
5
Power Flow Data File (RAW) GENERAL Record

• power flow solution parameters

• descriptions of rating sets

• information on the most recent power flow solution attempt

Generally, each record specified in the System-Wide Data category begins with a NAME that defines the type
of data specified on the record. The formats of the various records are described in the following paragraphs.

1.6.1. GENERAL Record

The GENRAL record contains solution parameters used by all of the power flow solution methods. These
solution parameters that are specified may be entered in any order.

RAW Record Format

GENERAL, THRSHZ=0.0001, PQBRAK=0.7, BLOWUP=5.0, MAXISOLLVLS=4, CAMAXREPTSLN=20,

CHKDUPCNTLBL=0

RAWx Record Format

"general":{
"fields":["thrshz", "pqbrak", "blowup", "maxisollvls", "camaxreptsln",
"chkdupcntlbl"],
"data":[0.0001, 0.7, 5.0, 4, 20, 0]
}

Using keyword input, any or all of the following solution parameters may be specified:

• THRSHZ (the zero impedance line threshold tolerance)

• PQBRAK (the constant power load characteristic voltage breakpoint)

• BLOWUP (the largest voltage change threshold)

• MAXISOLLVLS (the maximum levels to move outward from a element when attempting to isolate it by
breaker/switch actions)

• CAMAXREPTSLN (the maximum number of times to try and solve a contingency/remedial action)

• CHKDUPCNTLBL (check for duplicate contingency labels when create DFAX file and running contingency
analysis)

1.6.2. GAUSS Record

The GAUSS record contains solution parameters used by the Gauss-Seidel power flow solution methods (SOLV
and MSLV).

RAW Record Format

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
6
Power Flow Data File (RAW) NEWTON Record

GAUSS, ITMX=100, ACCP=1.6, ACCQ=1.6, ACCM=1.0, TOL=0.0001

RAWx Record Format

"gauss":{
"fields":["itmx", "accp", "accq", "accm", "tol"],
"data":[100, 1.6, 1.6, 1.0, 0.0001]
}

Using keyword input, any or all of the following solution parameters may be specified:

• ITMX (the maximum number of iterations)

• ACCP (real component voltage change acceleration factor)

• ACCQ (imaginary component voltage change acceleration factor)

• ACCM (type 1 bus complex voltage change acceleration factor in MSLV)

• TOL (voltage magnitude change convergence tolerance)

1.6.3. NEWTON Record

The NEWTON record contains solution parameters used by the Newton-Raphson power flow solution meth-
ods (FDNS, FNSL and NSOL).

RAW Record Format

NEWTON, ITMXN=20, ACCN=1.0, TOLN=0.1, VCTOLQ=0.1, VCTOLV=0.00001, DVLIM=0.99,

NDVFCT=0.99

RAWx Record Format

"newton":{
"fields":["itmxn", "accn", "toln", "vctolq", "vctolv", "dvlim", "ndvfct"],
"data":[20, 1.0, 0.1, 0.1, 0.00001, 0.99, 0.99]
}

The NEWTON record contains solution parameters used by the Newton-Raphson power flow solution meth-
ods (FDNS, FNSL and NSOL). Using keyword input, any or all of the following solution parameters may be
specified:

• ITMXN (the maximum number of iterations)

• ACCN (voltage magnitude setpoint change acceleration factor at voltage controlled buses)

• TOLN (mismatch convergence tolerance)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
7
Power Flow Data File (RAW) ADJUST Record

• VCTOLQ (controlled bus reactive power mismatch convergence tolerance)

• VCTOLV (controlled bus voltage error convergence tolerance)

• DVLIM (maximum voltage magnitude change that may be applied on any iteration)

• NDVFCT (non-divergent solution improvement factor)

1.6.4. ADJUST Record

The ADJUST record contains solution parameters used by the automatic adjustment functions of the Gauss-
Seidel and Newton-Raphson power flow solution methods.

RAW Record Format

ADJUST, ADJTHR=0.005, ACCTAP=1.0, TAPLIM=0.05, SWVBND=100.0, MXTPSS=99,

MXSWIM=10

RAWx Record Format

"adjust":{
"fields":["adjthr", "acctap", "taplim", "swvbnd", "mxtpss", "mxswim"],
"data":[0.005, 1.0, 0.05, 100.0, 99, 10]
}

Using keyword input, any or all of the following solution parameters may be specified:

• ADJTHR (automatic adjustment threshold tolerance)

• ACCTAP (tap movement deceleration factor)

• TAPLIM (maximum tap ratio change on any iteration)

• SWVBND (percent of voltage band switched shunts with voltage violations that are adjusted on any iter-
ation)

• MXTPSS (maximum number of tap and/or switched shunt adjustment cycles)

• MXSWIM (maximum number of induction machine state switchings)

1.6.5. TYSL Record

The TYSL record contains solution parameters used by the balanced switching network solution (TYSL)

RAW Record Format

TYSL, ITMXTY=20, ACCTY=1.0, TOLTY=0.00001

RAWx Record Format

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
8
Power Flow Data File (RAW) SOLVER Record

"tysl":{
"fields":["itmxty", "accty", "tolty"],
"data":[20, 1.0, 0.00001]
}

Using keyword input, any or all of the following solution parameters may be specified:

• ITMXTY (the maximum number of iterations)

• ACCTY (voltage change acceleration factor)

• TOLTY (voltage magnitude change convergence tolerance)

1.6.6. SOLVER Record

The SOLVER record identifies the power flow solution method and solution options used in the last power
flow solution attempt.

RAW Record Format

SOLVER, FNSL, ACTAPS=1, AREAIN=0, PHSHFT=0, DCTAPS=1, SWSHNT=1, FLATST=0, VAR-

LIM=0, NONDIV=0

RAWx Record Format

"solver":{
"fields":["method", "actaps", "areain", "phshft", "dctaps", "swshnt",
"flatst", "varlim", "nondiv"],
"data":["FNSL", 1, 0, 0, 1, 1, 0, 0, 0]
}

Following the name SOLVER is the name of the solution method (either FDNS, FNSL, NSOL, SOLV or MSLV).
Then, using keyword input, any or all of the following solution option selections may be specified:

• ACTAPS (the ac tap adjustment code)

• AREAIN (the area interchange adjustment code)

• PHSHFT (the phase shift adjustment code)

• DCTAPS (the dc tap adjustment code)

• SWSHNT (the switched shunt adjustment code)

• FLATST (the flat start code)

• VARLIM (the reactive power limit application code)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
9
Power Flow Data File (RAW) BRANCH RATING NAME Record

• NONDIV (the non-divergent solution code)

1.6.7. BRANCH RATING NAME Record

The RATING specifies a six-character name and a 32-character description associated with a specified non-
transformer and transformer branch rating set.

RAW Record Format

RATING, 1, "STEMER", "Short term summer emergency"

RAWx Record Format

"rating":{
"fields":["irate", "name", "desc"],
"data":[
[1, "STEMER", "Short term summer emergency"],
...
[12, "WINCON", "Winter continuous"]
]
}

Following the name RATING are the following data items:

• the number of the rating set (1 through 12),

• a quoted string that contains the rating's name (this is used as a column heading in several reports), and

• a quoted string that contains the rating's description.

If no RATING record is specified for rating set "n", its name is set to "RATEn" and its description is set to "RATING
SET n".

1.6.8. SWITCHING DEVICE RATING NAME Record

The SWITCHING DEVICE RATING NAME record specifies the options used by the 12 ratings of Switching Device
Rating Table record. These rating names are applicable to the System Switching Devices and Station Switching
Devices.

RAW Record Format

SWDRATNAM, RN, RNAM, RTYP, UNIT, DESC

RAW Example

SWDRATNAM, 1, "THERM1", 0, "MVA", "Thermal continuous limit 1"

...
SWDRATNAM, 12, "INTRP4", 1, "AMP", "Fault interruption limit 4"

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
10
Power Flow Data File (RAW) Bus Data

RAWx Record Format

"swdratnam":{
"fields":["irate", "rnam", "rtyp", "unit", "desc"],
"data":[
[ 1, "THERM1", 0, "MVA", "Thermal limit 1"],
...
[12, "INTRP4", 1, "AMP", "Fault interrupting limit 4"]
]
}

The name SWDRATNAM is followed by these data items:

• RN -- the number of the rating set (1 through 12),

• RNAM -- 6-character name, a quoted string that contains the rating's name. This is used as a column head-
ing in several reports. If no NAME is specified for rating "n", its name is set to "RATEn".

• RTYP -- type of rating RN. TYPE=0 for Thermal rating and TYPE=1 for interrupting rating. TYPE=0 by default.

• UNIT -- unit of rating RN. UNIT="MVA" or "AMP". UNIT="MVA" by default.

• DESC -- 32-character description, a quoted string that contains the rating's description that can be used to
further identify the rating. It is used for information only. By default it is set as "SWD RATING SET n".

Note that RTYP and UNIT of rating set N are not allowed to change if that rating set has non zero rating values.

System wide data input is terminated with a record specifying a value of zero.

1.7. Bus Data

Each network bus to be represented in PSSE is introduced by reading a bus data record.

RAW Record Format

I, NAME, BASKV, IDE, AREA, ZONE, OWNER, VM, VA, NVHI, NVLO, EVHI, EVLO

RAWx Record Format

"bus":{
"fields":["ibus", "name", "baskv", "ide", "area", "zone", "owner", "vm",
"va", "nvhi", "nvlo", "evhi", "evlo"],
"data":[
[101, "NUC-A", 21.6, 2, 1, 1, 1, 1.01, -19.0, 1.1, 0.9, 1.1, 0.9],
...

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
11
Power Flow Data File (RAW) Bus Data

[93002, "INDGEN2", 0.69, 1, 5, 6, 5, 0.94, -4.3, 1.1, 0.9, 1.1, 0.9]

]
}

Field RAWX Key Description

I ibus Bus number (1 through 999997). No default allowed.
NAME name Alphanumeric identifier assigned to bus I. NAME may be up to twelve characters
and may contain any combination of blanks, uppercase letters, numbers and spe-
cial characters, but the first character must not be a minus sign. NAME must be
enclosed in single or double quotes if it contains any blanks or special characters.

NAME = twelve blanks by default

BASKV baskv Bus base voltage; entered in kV

BASKV = 0.0 by default

IDE ide Bus type code:

• 1 - for a load bus or passive node (no generator boundary condition)

• 2 - for a generator or plant bus (either voltage regulating or fixed Mvar)

• 3 - for a swing bus

• 4 - for a disconnected (isolated) bus

IDE = 1 by default
AREA area Area number (1 through 9999).

AREA = 1 by default
ZONE zone Zone number (1 through 9999).

ZONE = 1 by default
OWNER owner Owner number (1 through 9999).

OWNER = 1 by default
VM vm Bus voltage magnitude; entered in pu.

VM = 1.0 by default
VA va Bus voltage phase angle; entered in degrees.

VA = 0.0 by default
NVHI nvhi Normal voltage magnitude high limit; entered in pu.

NVHI = 1.1 by default

NVLO nvlo Normal voltage magnitude low limit, entered in pu.

NVLO = 0.9 by default

EVHI evhi Emergency voltage magnitude high limit; entered in pu.

EVHI = 1.1 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
12
Power Flow Data File (RAW) Bus Data Notes

Field RAWX Key Description

EVLO evlo Emergency voltage magnitude low limit; entered in pu.

EVLO = 0.9 by default

Bus data input in the RAW file is terminated with a record specifying a bus number of zero.

1.7.1. Bus Data Notes

VM and VA need to be set to their actual solved case values only when the network, as entered into the
working case via activity READ, is to be considered solved as read in. Otherwise, unless some better estimate
of the solved voltage and/or phase angle is available, VM and VA may be omitted (and therefore set to their
default values; see Default Values).

1.8. Load Data

Each network bus at which load is to be represented must be specified in at least one load data record.
Multiple loads may be represented at a bus by specifying more than one load data record for the bus, each
with a different load identifier.

Figure 1.1. Load Representation on Bus

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 Load, activities CONL and RCNL, Modeling
Load Characteristics and Basic Load Characteristics.

RAW Record Format (on single line)

I, ID, STATUS, AREA, ZONE, PL, QL, IP, IQ, YP, YQ, OWNER, SCALE, INTRPT, DGENP,
DGENQ, DGENM, LOADTYPE, NAME

RAWx Record Format

"load":{
"fields":["ibus", "loadid", "stat", "area", "zone", "pl", "ql",
"ip", "iq", "yp", "yq", "owner", "scale", "intrpt",
"dgenp", "dgenq", "dgenm", "loadtype", "name"],
"data":[
[152, "1", 1, 1, 1, 1200.0, 360.0, 868.3, 360.5, 837.8, -351.3,
1, 1, 0, 0.0, 0.0, 0, "", ""],
...

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
13
Power Flow Data File (RAW) Load Data

[3010, "1", 1, 5, 4, 12.0, 5.0, 0.0, 0.0, 0.0, 0.0, 5,

1, 0, 0.0, 0.0, 0, "", ""]
]
}

Field RAWX Key Description

I ibus Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names).

No default allowed.
ID loadid 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 stat Load status of one for in-service and zero for out-of-service.

STATUS = 1 by default
AREA 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 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 pl Active power component of constant MVA load; entered in MW.

PL = 0.0 by default
QL ql Reactive power component of constant MVA load; entered in Mvar.

QL = 0.0 by default
IP ip Active power component of constant current load; entered in MW at one per unit
voltage.

IP = 0.0 by default
IQ iq Reactive power component of constant current load; entered in Mvar at one per
unit voltage.

IQ = 0.0 by default
YP yp Active power component of constant admittance load; entered in MW at one per
unit voltage.

YP = 0.0 by default
YQ 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 capacitive load.

YQ = 0.0 by default
OWNER 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 scale Load scaling flag of one for a scalable load and zero for a fixed load (refer to SCAL).

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
14
Power Flow Data File (RAW) Load Data Notes

Field RAWX Key Description

SCALE = 1 by default
INTRPT intrpt Interruptible load flag of one for an interruptible load for zero for a non interrupt-
ible load.

INTRPT = 0 by default
DGENP dgenp Distributed Generation active power component; entered in units of MW.

DGENP = 0.0 by default

DGENQ dgenq Distributed Generation reactive power component; entered in units of MVAR.

DGENQ = 0.0 by default

DGENM dgenm Distributed Generation operation mode; 0 = distributed generation on feeder is
OFF, 1 = distributed generation on feeder is ON.

DGENM = 0 by default
LOADTYPE loadtype Alphanumeric load type descriptor of up to twelve characters used to distinguish
among different types of load.

LOADTYPE is blanks by default

NAME name Alphanumeric identifier assigned to the load. NAME may be up to forty characters
and may contain any combination of blanks, uppercase letters, numbers and spe-
cial characters. NAME must be enclosed in single or double quotes if it contains
any blanks or special characters.

NAME must be unique within all loads.

NAME is blank by default

Load data input is terminated with a record specifying a bus number of zero.

1.8.1. Load Data Notes

The area, zone, and owner assignments of loads are used for area, zone, and owner totaling purposes (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 Interchange Control and activities AREA,
ZONE, TIES, TIEZ, INTA, and INTZ).

1.8.2. Constant Power Load Characteristic

The constant power characteristic holds the load power values, and also, the distributed generation power
values, constant as long as the bus voltage exceeds a value specified by the solution parameter PQBRAK. The
constant power characteristic assumes an elliptical current-voltage characteristic of the corresponding load
current for voltages below this threshold. Figure 1.2 depicts this characteristic for PQBRAK values of 0.6, 0.7,
and 0.8 pu. The user may modify the value of PQBRAK using the [Solution Parameters] GUI (refer to PSSE
GUI Users Guide, Section 11.1.1, Boundary Conditions).

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
15
Power Flow Data File (RAW) Constant Current Load Characteristic

Figure 1.2. Constant Power Load Characteristics

1.8.3. 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 1.3 for voltages below 0.5 pu.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
16
Power Flow Data File (RAW) Fixed Bus Shunt Data

Figure 1.3. Constant Current Load Characteristics

1.9. 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.

Figure 1.4. Fixed Shunt Representation on Bus

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
17
Power Flow Data File (RAW) Fixed Bus Shunt Data

RAW Record Format

I, ID, STATUS, GL, BL, NAME

RAWx Record Format

"fixshunt":{
"fields":["ibus", "shntid", "stat", "gl", "bl", "name"],
"data":[
[151, "F1", 1, 5.0, -400.0, ""],
...
[3022, "1 ", 1, 0.0, 1080.0, ""]
]
}

Field RAWX Key Description

I ibus Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names).

No default allowed
ID shntid One- or two-character uppercase non-blank alphanumeric fixed shunt identifier
used to distinguish among multiple fixed shunts at bus I. It is recommended that,
at buses for which a single fixed shunt is present, the fixed shunt be designated
as having the fixed shunt identifier '1'.

ID = '1' by default
STATUS stat Shunt status of one for in-service and zero for out-of-service.

STATUS = 1 by default
GL 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 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 en-
tered as part of load data; line charging and line connected shunts, which are
entered as part of non-transformer branch data; transformer magnetizing admit-
tance, 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
NAME name Alphanumeric identifier assigned to the fixed bus shunt. NAME may be up to forty
characters and may contain any combination of blanks, uppercase letters, num-
bers and special characters. NAME must be enclosed in single or double quotes if
it contains any blanks or special characters.

NAME must be unique within all fixed bus shunts.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
18
Power Flow Data File (RAW) Fixed Shunt Data Notes

Field RAWX Key Description

NAME is blank by default

Fixed bus shunt data input is terminated with a record specifying a bus number of zero.

1.9.1. Fixed Shunt Data Notes

The area, zone, and owner assignments of the bus to which the shunt is connected are used for area, zone,
and owner totaling purposes (e.g., in activities AREA, OWNR, and ZONE); refer to Section 14.7, “Summarizing
Area Totals” through Section 14.12, “Summarizing Zone-to-Zone Interchange”) and for shunt scaling purpos-
es (refer to SCAL).

The admittance specified in the data record can represent a shunt capacitor or a shunt reactor (both with
or without a real component) or a shunt resistor. It must not represent line connected admittance, switched
shunts, loads, line charging or transformer magnetizing impedance, all of which are entered in other data
categories.

1.10. Voltage Droop Control Data

The voltage droop control data defines QV characteristic curve and controlled bus.

Figure 1.5. Generator QV characteristic

RAW Record Format

NAME, STATUS, REGBUS, QDB, QMIN, QMAX, VDBLOW, VDBHIGH, VLOW, VHIGH

RAWx Record Format

"voltagedroop":{
"fields":["name", "status", "regbus", "qdb", "qmin", "qmax", "vdblow",

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
19
Power Flow Data File (RAW) Voltage Droop Control Data

"vdbhigh", "vlow", "vhigh"],

"data":[
["VLTDRP_A", 1, 0, 10, -50.0, 100.0, 0.97, 1.03, 0.95, 1.05],
["VLTDRP_B", 1, 101, 15, -70.0, 155.0, 0.98, 1.02, 0.96, 1.04],
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to this voltage droop controller.
Each voltage droop control must have a unique NAME of up to 40 characters.

No default allowed.
STATUS status Status of voltage droop control, one for in-service and zero for out-of-service. If
it is set to one, then the power flow solution will attempt to solve to meet the QV
characteristic. If set to 0, then the devices that are assigned to this PPC will default
back to their original behavior of controlling a regulated bus to a voltage setpoint.

STATUS=1 by default
REGBUS regbus Bus number, or extended bus name enclosed in single quotes of the controlled
bus(refer to Extended Bus Names ).

REGBUS=0 by default
QDB qdb The reactive power in Mvar at Regbus when voltage is within VDBLOW and VDB-
HIGH.

QDB = 0.0 by default

QMIN qmin Minimum reactive power in Mvar at the Regulated Bus being contributed by the
devices in the Power Plant Controller.

QMIN = -100.0 by default

QMAX qmax Maximum reactive power in Mvar at the Regulated Bus being contributed by the
devices in the Power Plant Controller.

QMAX = 100.0 by default

VDBLOW vdblow Lower end of the per unit voltage range at the Regulated Bus when the reactive
power injection remains at QDB.

VDBLOW = 0.98 by default

VDBHIGH vdbhigh Upper end of the per unit voltage range at the Regulated Bus when the reactive
power injection remains at QDB.

VDBLOW = 1.02 by default

VLOW vlow Per unit voltage at the Regulated Bus at QMAX

VLOW = 0.90 by default

VHIGH vhigh Per unit voltage at the Regulated Bus at QMIN.

VDBLOW = 1.1 by default

Voltage droop control data input is terminated with a record specifying a bus number of zero.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
20
Power Flow Data File (RAW) Voltage Droop Control Data Notes

1.10.1. Voltage Droop Control Data Notes

The Q inputs of voltage droop QV characteristic curve must be monotonically decreasing (QMAX>QD-
B>QMIN), and the V inputs of the curve must be monotonically increasing (VHIGH>VDBHIGH>VD-
BLOW>VLOW).

It is suggested to set the voltage range of each segment in the VQ characteristic curve to greater than 0.02
to prevent a numerical issue due to a narrow band.

1.11. Generator Data

Each network bus to be represented as a generator or plant bus in PSSE 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.

Figure 1.6. Generator Representation on Bus

RAW Record Format (on single line)

I, ID, PG, QG, QT, QB, VS, IREG, NREG, MBASE, ZR, ZX, RT, XT, GTAP, STAT, RMPCT,
PT, PB, BASLOD, O1, F1, ..., O4, F4, WMOD, WPF, DROOPNAME, NAME

RAWx Record Format

"generator":{
"fields":["ibus", "machid", "pg", "qg", "qt", "qb", "vs", "ireg", "nreg",
"mbase", "zr", "zx", "rt", "xt", "gtap", "stat", "rmpct",
"pt", "pb", "baslod", "o1", "f1", "o2", "f2", "o3", "f3", "o4",
"f4", "wmod", "wpf","droopname","name"],
"data":[
[101, "1", 750.0, 165.2, 400.0, -100.0 1.01, 101, 0, 900.0, 0.01,
0.3, 0.0, 0.0, 1.0, 1, 100.0, 800.0, 50.0, 0, 1, 0.1289, 2, 0.2524,
3, 0.1031, 4, 0.5156, 0, 1.0,"VLTDRP_A","GEN_A"],
...

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
21
Power Flow Data File (RAW) Generator Data

[3018, "2", 100.0, -0.157, 75.0, -75.0, 0.99, 3018, 0, 120.0, 0.024,
0.36, 0.0, 0.0, 1.0, 1, 92.5, 110.0, 20.0, 0, 1, 0.3003, 2, 0.1358,
3, 0.2857, 4, 0.2782, 0, 1.0,"VLTDRP_B","GEN_B"]
]
}

Field RAWX Key Description

I ibus Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names).

No default allowed
ID machid 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 pg Generator active power output; entered in MW.

PG = 0.0 by default
QG 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 qt Maximum generator reactive power output; entered in Mvar. For fixed output
generators (i.e., nonregulating), QT must be equal to the fixed Mvar output. For
infeed machines (WMOD=4), QT is not used in powerflow calculations. The reac-
tive power output of infeed machines is held constant at QG.

QT = 9999.0 by default
QB qb Minimum generator reactive power output; entered in Mvar. For fixed output
generators, QB must be equal to the fixed Mvar output. For infeed machines
(WMOD=4), QB is not used in powerflow calculations. The reactive power output
infeed machines is held constant at QB = -9999.0 by default.
VS vs Regulated voltage setpoint; entered in pu.

VS = 1.0 by default
IREG ireg Bus number, or extended bus name enclosed in single quotes, of the bus for which
voltage is to be regulated by this plant to the value specified by VS. If IREG specifies
a remote bus (i.e., a bus other than bus I), bus IREG must be a Type 1 or 2 bus
(if it is other than a Type 1 or 2 bus, bus I regulates its own voltage to the value
specified by VS). IREG may be entered as zero if the plant is to regulate its own
voltage. If bus I is a Type 3 (swing) bus, IREG must not specify a remote bus.

When the generator is under voltage droop control as specified by DROOPNAME,

IREG is replaced by REGBUS of DROOPNAME record if the REGBUS is non-zero.

IREG = 0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
22
Power Flow Data File (RAW) Generator Data

Field RAWX Key Description

NREG nreg A node number of bus IREG. The bus section of bus IREG to which node NREG
is connected is the bus section for which voltage is to be regulated by this plant
to the value specified by VS. If bus IREG is not in a substation, NREG must be
specified as 0.

NREG = 0 by default
MBASE 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

ZR,ZX zr,zx Complex machine impedance, ZSORCE; entered in pu on MBASE base. This data
is not needed in normal power flow and equivalent construction work, but is re-
quired for switching studies, fault analysis, and dynamic simulation. For dynamic
simulation, this impedance must be set equal to the unsaturated subtransient im-
pedance for those generators to be modeled by subtransient level machine mod-
els, and to unsaturated transient impedance for those to be modeled by classical
or transient level models. For short-circuit studies, the saturated subtransient or
transient impedance should be used.

ZR = 0.0 and ZX = 1.0 by default

RT,XT rt,xt Step-up transformer impedance, XTRAN; entered in pu on MBASE base. XTRAN
should be entered as zero if the step-up transformer is explicitly modeled as a
network branch and bus I is the terminal bus.

RT + jXT = 0.0 by default

GTAP gtap Step-up transformer off-nominal turns ratio; entered in pu on a system base. GTAP
is used only if XTRAN is non-zero.

GTAP = 1.0 by default

STAT stat Machine status of one for in-service and zero for out-of-service;

STAT = 1 by default
RMPCT rmpct Percent of the total Mvar required to hold the voltage at the bus controlled by bus
I that are to be contributed by the generation at bus I; RMPCT must be positive.
RMPCT is needed only if there is more than one local or remote setpoint mode
voltage controlling device (plant, switched shunt, FACTS device shunt element,
or VSC dc line converter) controlling the voltage at bus IREG.

RMPCT = 100.0 by default

PT pt Maximum generator active power output; entered in MW.

PT = 9999.0 by default
PB pb Minimum generator active power output; entered in MW.

PB = -9999.0 by default
BASLOD baslod Base loaded flag;

• = 0 Normal, the machine is not base loaded

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
23
Power Flow Data File (RAW) Generator Data

Field RAWX Key Description

• = 1 Down only; the machine can be scaled down but will not be scaled for any
increase in generation

• = 2 Neither up nor down; the machine can be scaled neither up nor down

• = 3 Up only; the machine can be scaled up but will not be scaled for any de-
crease in generation

BASLOD = 0 by default
Oi o1, o2, o3, Owner number (1 through 9999). Each machine may have up to four owners. By
o4 default, O1 is the owner to which bus I is assigned (refer to Bus Data) and O2,
O3, and O4 are zero.
Fi f1, f2, f3, f4 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.
WMOD wmod Machine control mode; WMOD is used to indicate whether a machine is a conven-
tional or a non-conventional machine (e.g. renewables, infeed) machine, and, if
it is, the type of reactive power limits to be imposed. Non-conventional machines
are renewables (e.g., wind, PV etc.) and infeed machines (for definition of infeed
machines, see description below of WNMOD=4)

0 - a conventional machine (e.g. synchronous machines).

1 - renewable type machine for which reactive power limits are specified by QT
and QB.

2 - renewable type machine for which reactive power limits are determined from
the machine's active power output and WPF; limits are of equal magnitude and
opposite sign

3 - renewable type machine with a fixed reactive power setting determined from
the machine's active power output and WPF; when WPF is positive, the machine's
reactive power has the same sign as its active power; when WPF is negative, the
machine's reactive power has the opposite sign of its active power.

4 - infeed type machine. An infeed type machine is one for which the machine
reactive power (QG) is held constant. The QT and QB limits values are not used
and are for information only. QG value has to be between QT and QB.

WMOD = 0 by default
WPF wpf Power factor used in calculating reactive power limits or output when WMOD is
2 or 3

WPF = 1.0 by default

DROOP- droopname The alphanumeric name of voltage droop controller.
NAME
DROOPNAME must be defined in voltage droop control table.

Droopname is blank by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
24
Power Flow Data File (RAW) Reactive Power Limits

Field RAWX Key Description

NAME name Alphanumeric identifier assigned to the machine. NAME may be up to forty char-
acters and may contain any combination of blanks, uppercase letters, numbers
and special characters. NAME must be enclosed in single or double quotes if it
contains any blanks or special characters.

NAME must be unique within all machines.

NAME is blank by default

Generator data input in the RAW file is terminated with a record specifying a bus number of zero.

1.11.1. 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 solu-
tions 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 sys-
tem 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 refer to Section 6.3.12,
“Generation” and Section 6.3.18, “AC Voltage Control”.

1.11.2. 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 1.7 shows that bus K is the Type 2 bus. This is the bus at which the generator will regulate/control
voltage unless the user specifies a remote bus.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
25
Power Flow Data File (RAW) Multiple Machine Plants

Figure 1.7. 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 1.8, 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.

Figure 1.8. Explicit GSU Configuration– Specified Separately from the Generator

1.11.3. Multiple Machine Plants

If a generating plant has several units, they can be represented separately even if they are connected to the
same Type 2 bus. When two or more machines are to be separately modeled at a plant, their data may be
introduced into the working case using one of two approaches.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
26
Power Flow Data File (RAW) Switching Device Rating Table Data

A generator data record may be entered in activities READ, TRSQ, or RDCH for each of the machines to be
represented, with machine powers, power limits, impedance data, and step-up transformer data for each
machine specified on separate generator data records. The plant power output and power limits are taken
as the sum of the corresponding quantities of the in-service machines at the plant. The values specified for
VS, IREG, and RMPCT, which are treated as plant quantities rather than individual machine quantities, must
be identical on each of these generator data records.

Alternatively, a single generator record may be specified in activities READ, TREA, or RDCH with the plant
total power output, power limits, voltage setpoint, remotely regulated bus, and percent of contributed Mvar
entered. Impedance and step-up transformer data may be omitted. The PSSE power flow activities may be
used and then, any time prior to beginning switching study, fault analysis, 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 1.9 shows three Type 2 buses, each having two connected units. For generators 1
through 4, the GSU is explicitly represented while for generators 5 and 6 the GSU is implicitly represented.
Figure 1.10 shows the generator data records corresponding to Figure 1.9.

The separate transformer data records for the explicitly represented transformers from buses 1238 and 1239
to bus 1237 are not included in Figure 1.10.

Figure 1.9. Multiple Generators at a Single Plant

I,'ID', PG,QG, QT, QB, VS,IREG,NREG, MBASE, ZR, ZX, T, XT, GTAP,STAT, RMPCT, ...
1238,'1 ', 200., , 120., 0.0, 1.03, 0, 0, 200.0, 0.0, .26, 0., 0.0, 1.00, 1, 50.0, ...
1238,'2 ', 250., , 150., 0.0, 1.03, 0, 0, 250.0, 0.0, .22, 0., 0.0, 1.00, 1, 50.0, ...
1239,'3 ', 200., , 120., 0.0, 1.03, 0, 0, 200.0, 0.0, .26, 0., 0.0, 1.00, 1, 50.0, ...
1239,'4 ', 250., , 150., 0.0, 1.03, 0, 0, 250.0, 0.0, .22, 0., 0.0, 1.00, 1, 50.0, ...
1237,'5 ', 750., , 500., 0.0, 1.06, 0, 0, 800.0, 0.0, .25, 0., 0.18, 1.05, 1, 50.0, ...
1237,'6 ', 750., , 500., 0.0, 1.06, 0, 0, 800.0, 0.0, .25, 0., 0.18, 1.05, 1, 50.0, ...

Figure 1.10. Data Set for the Multiple Generators in Figure 1.9

1.12. Switching Device Rating Table Data

The Switching Device (SWD) Rating Tables are used to define rating sets for System Switching Devices or
Station Switching Devices. These rating sets could contain continuous ratings [thermal] and fault interruption
ratings [short circuit withstand current]. Multiple switching devices can refer to the same rating set.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
27
Power Flow Data File (RAW) Switching Device Rating Table Data

RSETNAM, DESC, RATE1, ..., RATE12

RAWx Record Format

"swdratset":{
"fields":["rsetnam", "desc",
"rate1", "rate2", "rate3", "rate4", "rate5", "rate6",
"rate7", "rate8", "rate9", "rate10", "rate11", "rate12"],
"data":[
["BRK-MDL-123", "BREAKER MODEL 123, MFG ABC, INSTALL JULY 2022, TEST ANSI",
100.98, 101.87, 102.76, 103.65, 200.98, 201.87,
202.76, 203.65, 300.98, 301.87, 302.76, 303.65],
...
["DSW-MDL-456",
"Disconnect Switch MODEL 456, MFG XYZ, INSTALL JULY 2023, TEST IEC60909",
100.98, 101.87, 102.76, 103.65, 200.98, 201.87,
202.76, 203.65, 300.98, 301.87, 302.76, 303.65]
]
}

Field RAWX Key Description

RSETNAM rsetnam Alphanumeric identifier assigned to the rating set. RSETNAM may be up to 40
characters and may contain any combination of blanks, uppercase letters, num-
bers and special characters. RSETNAM must be enclosed in single or double quotes
if it contains any blanks or special characters.

RSETNAMmust be unique within all SWD rating tables.

No default allowed.
DESC desc Alphanumeric description about switching device. DESC may contain any combi-
nation of blanks, uppercase letters, numbers and special characters.

DESC could be used specify switching device type, model, manufacturer, testing
standard, installation date etc.

DESC is used for information only.

DESC is blank by default.

RATEn rate1, rate2, nth rating; entered in the unit specified for that nth SWDRATNAM specified on the
rate3, rate4, SWITCHING DEVICE RATING NAME Record.
rate5, rate6,
rate7, rate8, Each RATEn = 0.0 by default. When RATEn = 0.0, rating check for this switching
rate9, device is not done in any rating examination. Refer to activity RATE.
rate10,
rate11,
rate12

Switching Device Rating Tables input is terminated with a record specifying a blank rating table name or a
rating table name of ’0’.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
28
Power Flow Data File (RAW) Non-Transformer Branch Data

1.13. Non-Transformer Branch Data

Each ac network branch to be represented in PSSE as a non-transformer branch is introduced by reading a
non-transformer branch data record.

Branches to be modeled as transformers are not specified in this data category; rather, they are specified
in Transformer Data.

When specifying a non-transformer branch between buses I and J with circuit identifier CKT, if a two-winding
transformer between buses I and J with a circuit identifier of CKT is already present in the working case, it
is replaced (i.e., the transformer is deleted from the working case and the newly specified branch is then
added to the working case).

In PSSE, the basic transmission line model is an Equivalent Pi connected between network buses. Figure 1.11
shows the required parameter data where the equivalent Pi is comprised of:

• A series impedance (R + jX).

• Two admittance branches (jB/2) representing the line's total capacitive admittance (line charging).

• Two admittance branches (GI+jBI and GJ+jBJ) for shunt equipment units (e.g., reactors) that are connected
to and switched with the line.

To represent shunts connected to buses, that shunt data should be entered in fixed shunt and/or switched
shunt data records.

Figure 1.11. Equivalent PI model of a Long Transmission Line

I, J, CKT, R, X, B, NAME, RATE1, ..., RATE12, GI, BI, GJ, BJ, ST, BP, MET, LEN, O1, F1, ..., O4, F4

RAWx Record Format

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
29
Power Flow Data File (RAW) Non-Transformer Branch Data

"acline":{
"fields":["ibus", "jbus", "ckt", "rpu", "xpu", "bpu", "name",
"rate1", "rate2", "rate3", "rate4", "rate5", "rate6",
"rate7", "rate8", "rate9", "rate10", "rate11", "rate12",
"gi", "bi", "gj", "bj", "stat", "bypass", "met", "len",
"o1", "f1", "o2", "f2", "o3", "f3", "o4", "f4"],
"data":[
[151, 152, "1", 0.0026, 0.046, 3.5, "", 1200.0, 1100.0, 1000.0,
1200.4, 1100.5, 1000.6, 1200.70, 1100.80, 1000.90, 1200.10,
1100.11, 1000.12, 0.01, -0.25, 0.011, -0.15, 1, 0, 2, 150.0, 1,
0.2, 2, 0.3, 3, 0.4, 4, 0.1],
...

[3008, 3009, "1", 0.003, 0.025, 0.06, "", 25.0, 22.0, 18.0, 0.0,
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 1, 0,
2, 60.00, 1, 0.1797, 2, 0.2695, 3, 0.3594, 4, 0.1914]
]
}

Field RAWX Key Description

I ibus Branch from bus number, or extended bus name enclosed in single quotes (refer
to Extended Bus Names).

No default allowed
J jbus Branch to bus number, or extended bus name enclosed in single quotes.
CKT ckt One- or two-character uppercase non-blank alphanumeric branch circuit identifi-
er; the first character of CKT must not be an ampersand ( ); refer to Multi-Section
Line Grouping Data.

CKT = '1' by default

R rpu Branch resistance; entered in pu. A value of R must be entered for each branch.
X xpu Branch reactance; entered in pu. A non-zero value of X must be entered for each
branch. Refer to Zero Impedance Lines for details on the treatment of branches
as zero impedance lines.
B bpu Total branch charging susceptance; entered in pu.

B = 0.0 by default
NAME name Alphanumeric identifier assigned to the branch. NAME may be up to forty char-
acters and may contain any combination of blanks, uppercase letters, numbers
and special characters. NAME must be enclosed in single or double quotes if it
contains any blanks or special characters.

NAME must be unique within all non-transformer and transformer branches.

NAME is blank by default

RATEn rate1, rate2, nth rating; entered in either MVA or current expressed as MVA, according to the
rate3, rate4, value specified for NXFRAT specified on the first data record (refer to Case Iden-
rate5, rate6, tification).
rate7, rate8,

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
30
Power Flow Data File (RAW) Non-Transformer Branch Data

Field RAWX Key Description

rate9, Each RATEn = 0.0 (bypass check for this branch; this branch will not be included
rate10, in any examination of circuit loading) by default. Refer to activity RATE.
rate11,
rate12 When specified in units of current expressed as MVA, ratings are entered as:
-6
MVArated = √ 3 x Ebase x Irated x 10

where:

Ebase is the base line-to-line voltage in volts of the buses to which the terminal of
the branch is connected

Irated is the branch rated phase current in amperes.

GI, BI 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 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 stat Branch status of one for in-service and zero for out-of-service;

ST = 1 by default
BP bypass bypass flag; one is to bypass the branch and treat it as a zero impedance line (refer
to Zero Impedance Lines), and zero is to disable bypass;

BP = 0 by default
MET 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

PSSE assigns losses to non-metered end of the branch.

LEN len Line length; entered in user-selected units.

LEN = 0.0 by default

Oi o1, o2, o3, Owner number (1 through 9999). Each branch may have up to four owners. By
o4 default, O1 is the owner to which bus I is assigned (refer to Bus Data) and O2,
O3, and O4 are zero.
Fi f1, f2, f3, f4 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.

Each Fi is 1.0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
31
Power Flow Data File (RAW) Zero Impedance Lines

Non-transformer branch data input is terminated with a record specifying a from bus number of zero.

The branch is treated as series compensated line when its R=0 and X is < 0.

1.13.1. Zero Impedance Lines

PSSE provides for the treatment of bus ties, jumpers, breakers, switches, and other low impedance 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.

A non-transformer branch is treated as zero impedance line if its bypass flag is enabled regardless of its
impedance values.

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.

When obtaining power flow solutions, zero impedance line flows, as calculated at the end of the solution, are
preserved with the working case and are available to the power flow solution reporting activities. Similarly,
in activity SCMU, the positive, negative, and zero sequence branch currents on zero impedance lines are
determined and preserved, and are subsequently available to activity SCOP. In the ACCC, as well as activity
ASCC and in the linearized network analysis activities, zero impedance line results are calculated and reported
as needed.

The remainder of this section contains points to be noted, and restrictions to be observed, in using zero
impedance lines.

Branch impedances may not be specified as identically zero; a non-zero reactance must be specified for all
branches, and those meeting the criteria above are treated as zero impedance lines.

The zero impedance line threshold tolerance, THRSHZ, may be changed using the category of solution pa-
rameter data via activity CHNG or the [Solution Parameters] dialog. Setting THRSHZ to zero disables zero
impedance line modeling, and all branches are represented with their specified impedances.

A zero impedance line may not have a transformer in parallel with it. Although not required, it is recommend-
ed that no other in-service lines exist in parallel with a zero impedance line.

A zero impedance line may have non-zero values of line charging and/or line connected shunts. This allows,
for example, a low impedance cable to be modeled as a zero impedance line.

When more than two buses are connected together by zero impedance lines in a loop arrangement, there is
no unique solution to the flows on the individual zero impedance lines that form the loop. In this case, the
reactances specified for these branches is used in determining the zero impedance line flows.

It is important to note that buses connected together by zero impedance lines are treated as a single bus by
the power flow solution activities. Hence, equipment controlling the voltages of multiple buses in a zero im-
pedance connected group of buses must have coordinated voltage schedules (i.e., the same voltage setpoint
should be specified for each of the voltage controlling devices). Activity CNTB recognizes this condition in
scanning for conflicting voltage objectives, and activity REGB may be used to generate a regulated bus report.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
32
Power Flow Data File (RAW) System Switching Device Data

Similarly, if multiple voltage controlling devices are present in a group of buses connected together by zero
impedance lines, the power flow solution activities handle the boundary condition as if they are all connected
to the same bus (refer to Setpoint Voltage Control).

In fault analysis activities, 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 zero sequence branch impedance. Zero sequence
mutual couplings involving a zero impedance line are ignored in the fault analysis solution activities.

1.14. System Switching Device Data

Breakers and switches can be represented by system switching devices in PSSE. System switching devices are
set to represent breakers or switches by setting the STYPE data element described below.

Most activities do not honor the system switching devices. System switching devices are treated as zero
impedance lines if they have characteristics of zero impedance lines; otherwise, they are treated as regular
non-transformer branches.

System switching devices are recognized in Substation Reliability Assessment (refer to Section 6.16, Calcu-
lating Substation Reliability) and activity DFAX. Substation Reliability Assessment simulates operations of
breakers to isolate faults in a substation and manual switching to restore the service to supply loads. Dis-
tribution 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, PSSE is able to handle a loop arrangement consisting of
zero impedance lines so that users can build a fully detailed bus/breaker model for any bus configuration,
such as a ring bus configuration. When adding a system switching device into a network model, connectivity
nodes where the terminals of a transmission line connect to the terminals of the system switching device
must be added as well. This will change a bus branch configuration which is widely used in planning studies
to a detailed bus breaker configuration and lead to a tremendous increase in number of buses. In such cases
as this, the use of the the use of the extensive substation modeling capabilities introduced in PSSE 34 is
recommended.

I, J, CKT, X, RSETNAM, STATUS, NSTATUS, METERED, STYPE, NAME

RAWx Record Format

"sysswd":{
"fields":["ibus", "jbus", "ckt", "xpu",
"rsetnam", "stat", "nstat", "met", "stype", "name"],
"data":[
[151, 201, "*1", 1.0E-4, "BREAKER_0103", 1, 1, 2, 3, ""],
...

[153, 3006, "@1", 1.0E-4, "DISCONNECT_0102", 1, 1, 2, 2, ""]

]
}

Field RAWX Key Description

I ibus From bus number.

No default allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
33
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

J jbus To bus number.

No default allowed
CKT ckt Two-character uppercase non-blank alphanumeric switching device identifier.

CKT = '1' by default

X xpu Branch reactance; entered in pu, must be less than or equal to THRSHZ (zero im-
pedance line threshold tolerance)

X = THRSHZ by default.
RSETNAM rsetnam Previously defined rating set Switching Device Rating Table name.

RSETNAM is blank by default.

STATUS stat Switching device status

0 - Open

1 - Closed

2 - Stuck closed

STATUS = 1 by default
NSTAT nstat Switching device normal status

0 - Open

1 - Closed

2 - Stuck closed

NSTAT = 1 by default
METERD met Metered end
STYPE stype Switching device type

1 - Generic connector

2 - Circuit breaker

3 - Disconnect switch
NAME name System switching device name

System Switching Device data input is terminated with a record specifying a from bus number of zero.

1.15. Transformer Data

Each ac transformer to be represented in PSSE is introduced through transformer data record blocks that
specify all the data required to model transformers in power flow calculations, with one exception. That
exception is an optional set of ancillary data, transformer impedance correction tables, which define the
manner in which transformer impedance changes as off-nominal turns ratio or phase shift angle is adjusted.
Those data records are described in Transformer Impedance Cor.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
34
Power Flow Data File (RAW) Transformer Data

Both two-winding and three-winding transformers are specified in transformer data record blocks. Two-wind-
ing transformers require a block of four data records. Three-winding transformers require five data records.

t = t1 / t2; transformer turns ratio

t1:
winding 1 turns ratio in kV or pu on
t2: bus voltage base or winding volt-
age base

winding 2 turns ratio in kV or pu on

bus voltage base or winding volt-
age base

Figure 1.12 shows the transformer winding configurations.

Figure 1.12. Two and Three-winding Transformer Configurations Related to Data

Records
RAW Format

The five record transformer data block for three-winding transformers has the following format:

I, J, K, CKT, CW, CZ, CM, MAG1, MAG2, NMETR, NAME, STAT, O1, F1, ..., O4, F4, VECGRP, ZCOD

R1-2, X1-2, SBASE1-2, R2-3, X2-3, SBASE2-3, R3-1, X3-1, SBASE3-1, VMSTAR, ANSTAR

WINDV1, NOMV1, ANG1, RATE11, ..., RATE121, COD1, CONT1, NODE1, RMA1, RMI1, VMA1, VMI1, NTP1,
TAB1, CR1, CX1, CNXA1

WINDV2, NOMV2, ANG2, RATE12, ..., RATE122, COD2, CONT2, NODE2, RMA2, RMI2, VMA2, VMI2, NTP2,
TAB2, CR2, CX2, CNXA2

WINDV3, NOMV3, ANG3, RATE13, ..., RATE123, COD3, CONT3, NODE3, RMA3, RMI3, VMA3, VMI3, NTP3,
TAB3, CR3, CX3, CNXA3

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
35
Power Flow Data File (RAW) Transformer Data

The four-record transformer data block for two-winding transformers is a subset of the data required for
three-winding transformers and has the following format:

I, J, K, CKT, CW, CZ, CM, MAG1, MAG2, NMETR, NAME, STAT, O1, F1, ..., O4, F4, VECGRP

R1-2, X1-2, SBASE1-2

WINDV1, NOMV1, ANG1, RATE11, ..., RATE121, COD1, CONT1, NODE1, RMA1, RMI1, VMA1, VMI1, NTP1,
TAB1, CR1, CX1, CNXA1

WINDV2, NOMV2

RAWx Record Format

"transformer":{
"fields":["ibus", "jbus", "kbus", "ckt", "cw", "cz", "cm",
"mag1", "mag2", "nmet", "name", "stat",
"o1", "f1", "o2", "f2", "o3", "f3", "o4", "f4",
"vecgrp", "zcod", "r1_2", "x1_2", "sbase1_2",
"r2_3", "x2_3", "sbase2_3", "r3_1", "x3_1",
"sbase3_1", "vmstar", "anstar",
"windv1", "nomv1", "ang1",
"wdg1rate1", "wdg1rate2", "wdg1rate3", "wdg1rate4",
"wdg1rate5", "wdg1rate6", "wdg1rate7", "wdg1rate8",
"wdg1rate9", "wdg1rate10", "wdg1rate11", "wdg1rate12",
"cod1", "cont1", "node1", "rma1", "rmi1", "vma1", "vmi1",
"ntp1", "tab1", "cr1", "cx1", "cnxa1",
"windv2", "nomv2", "ang2",
"wdg2rate1", "wdg2rate2", "wdg2rate3", "wdg2rate4",
"wdg2rate5", "wdg2rate6", "wdg2rate7", "wdg2rate8",
"wdg2rate9", "wdg2rate10", "wdg2rate11", "wdg2rate12",
"cod2", "cont2", "node2", "rma2", "rmi2", "vma2", "vmi2",
"ntp2", "tab2", "cr2", "cx2", "cnxa2",
"windv3", "nomv3", "ang3",
"wdg3rate1", "wdg3rate2", "wdg3rate3", "wdg3rate4",
"wdg3rate5", "wdg3rate6", "wdg3rate7", "wdg3rate8",
"wdg3rate9", "wdg3rate10", "wdg3rate11", "wdg3rate12",
"cod3", "cont3", "node3", "rma3", "rmi3", "vma3", "vmi3",
"ntp3", "tab3", "cr3", "cx3", "cnxa3"],
"data":[
[101, 151, 0, "T1", 2, 2, 1,
0.171, -0.102, 2, "", 1,
1, 0.32, 2, 0.39, 3, 0.14, 4, 0.15,
"Dyn1", null, 0.001, 0.0091, 1200.0,
null, null, null, null, null,
null, null, null,
21.6, 21.6, 0.0,
1200.0, 1100.0, 1000.0, 0.0,
0.0, 0.0, 0.0, 0.0,
0.0, 0.0, 0.0, 0.0,
1, 101, 0, 22.68, 20.52, 1.05, 0.95,

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
36
Power Flow Data File (RAW) Transformer Data

25, 0, 0.00021, 0.00051, 0.0,

500.0],

...

[3008, 3012, 3010, "2", 2, 1, 1,

2.1E-04, -1.2E-04, 1, "", 2,
5, 0.8, 3, 0.05, 2, 0.1, 1, 0.05,
"D1y0y0", 0, 5.15E-3, 0.5, 20.0,
9.2E-3, 0.8, 15.0, 3.75E-3, 0.41667,
25.0, 0.98625, -30.5021,
230.0, 230.0, 0.0,
20.0, 18.0, 14.0, 0.0,
0.0, 0.0, 0.0, 0.0,
0.0, 0.0, 0.0, 0.0,
0, 0, 0, 1.1, 0.9, 1.1, 0.9,
33, 0, 0.0, 0.0, 0.0,
230.0, 230.0, 0.0,
15.0, 13.0, 9.0, 0.0,
0.0, 0.0, 0.0, 0.0,
0.0, 0.0, 0.0, 0.0,
0, 0, 0, 1.1, 0.9, 1.1, 0.9,
33, 0, 0.0, 0.0, 0.0,
21.6, 21.6, 30.0,
25.0, 19.0, 16.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0,
0, 0, 0, 1.1, 0.9, 1.1, 0.9,
33, 0, 0.0, 0.0, 0.0]
]
}

Note: The above RAWX example includes both a 2-winding and a 3-winding data row example. The 2-winding
example skips several trailing fields at the end of the record.

Control parameters for the automatic adjustment of transformers and phase shifters are specified on the
third record of the two-winding transformer data block, and on the third through fifth records of the three-
winding transformer data block. All transformers are adjustable and the control parameters may be specified
either at the time of raw data input or subsequently via activity CHNG or the transformer [Spreadsheets]. Any
two-winding transformer and any three-winding transformer winding for which no control data is provided
has default data assigned to it; the default data is such that the two-winding transformer or three-winding
transformer winding is treated as locked.

Refer to Transformer Sequence Numbers and Three-Winding Transformer Notes for additional details on the
three-winding transformer model used in PSSE.

When specifying a two-winding transformer between buses I and J with circuit identifier CKT, if a nontrans-
former 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).

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
37
Power Flow Data File (RAW) Transformer Data

All data items on the first record are specified for both two- and three-winding transformers except for ZCOD,
which is specified only for three-winding transformers.

Field RAWX Key Description

I ibus The bus number, or extended bus name enclosed in single quotes (refer to Extend-
ed Bus Names), of the bus to which Winding 1 is connected. The transformer's
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 ad-
justed by the power flow solution activities; any winding(s) of a three-winding
transformer may be adjusted.

No default is allowed
J jbus 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 kbus 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 ckt One- or two-character uppercase non-blank alphanumeric transformer circuit
identifier; the first character of CKT must not be an ampersand ( ), at sign ( @ ),
or asterisk ( * ); refer to Multi-Section Line Grouping Data and Section 6.15.2,
Outage Statistics Data File Contents.

CKT = '1' by default.

CW cw The winding data I/O code 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 cz The impedance data I/O code defines the units in which the winding impedances
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 volt-
age base

• 3 for transformer load loss in watts and impedance magnitude in pu on a spec-

ified MVA base and winding voltage base

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
38
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

In specifying transformer leakage impedances, the base voltage values are al-
ways 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 not specified, it is assumed to be identical to the winding n bus
base voltage.

CZ = 1 by default.
CM cm The magnetizing admittance I/O code defines the units in which MAG1 and MAG2
are specified:

• 1 for complex admittance in pu on system MVA base and Winding 1 bus voltage
base

• 2 for no load loss in watts and exciting current in pu on Winding 1 to two MVA
base (SBASE1-2) and nominal Winding 1 voltage, NOMV1.

CM = 1 by default.
MAG1, mag1, mag2 The transformer magnetizing admittance connected to ground at bus I.
MAG2
When CM is 1, MAG1 and MAG2 are the magnetizing conductance and suscep-
tance, respectively, in pu on system MVA base and Winding 1 bus voltage base.
When a non-zero MAG2 is specified, it should be entered as a negative quantity.

When CM is 2, MAG1 is the no load loss in watts and MAG2 is the exciting cur-
rent in pu on Winding 1 to two MVA base (SBASE1-2) and nominal Winding 1
voltage (NOMV1). For three-phase transformers or three-phase banks of single
phase transformers, MAG1 should specify the three-phase no-load loss. When a
non-zero MAG2 is specified, it should be entered as a positive quantity.

MAG1 = 0.0 and MAG2 = 0.0 by default.

NMETR nmet The nonmetered end code of either 1 (for the Winding 1 bus) or 2 (for the Winding
2 bus). In addition, for a three-winding transformer, 3 (for the Winding 3 bus) is
a valid specification of NMETR.

NMETR = 2 by default
NAME name Alphanumeric identifier assigned to the transformer. NAME may be up to forty
characters and may contain any combination of blanks, uppercase letters, num-
bers and special characters. NAME must be enclosed in single or double quotes if
it contains any blanks or special characters.

NAME must be unique within all non-transformer and transformer branches.

NAME is blank by default

STAT stat Transformer status of one for in-service and zero for out-of-service.

In addition, for a three-winding transformer, the following values of STAT provide

for one winding out-of-service with the remaining windings in-service:

• 2 for only Winding 2 out-of-service

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
39
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

• 3 for only Winding 3 out-of-service

• 4 for only Winding 1 out-of-service

STAT = 1 by default
Oi o1, o2, o3, An owner number (1 through 9999). Each transformer may have up to four own-
o4 ers. By default, O1 is the owner to which bus I is assigned and O2, O3, and O4
are zero.
Fi f1, f2, f3, f4 The 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.

Each Fi is 1.0 by default

VECGRP vecgrp Alphanumeric identifier specifying vector group based on transformer winding
connections and phase angles. VECGRP value is used for information purpose on-
ly.

VECGRP is 12 blanks by default

ZCOD zcod Method to be used in deriving actual transformer impedances in applying trans-
former impedance adjustment tables:

• 0 apply impedance adjustment factors to winding impedances

• 1 apply impedance adjustment factors to bus-to-bus impedances

ZCOD = 0 by default

ZCOD value is used only for three winding transformers. It is not used for two
winding transformers.

For three winding transformers, winding impedances are the equivalent T-model
impedances Z1, Z2 and Z3; and the bus-to-bus impedances are impedances Z12,
Z23 and Z31.

For three winding transformers and bus-to-bus impedance correction factors, on-
ly one of the three windings must be adjustable (only one of COD1, COD2 and
COD3 can be non-zero).

The first three data items on the second record are read for both two- and three-winding transformers; the
remaining data items are used only for three-winding transformers:

Field RAWX Key Description

R1-2, X1-2 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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
40
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

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 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 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 sbase2_3 The Winding 2 to 3 three-phase base MVA of a three-winding transformer; ig-
nored for a two-winding transformer. SBASE2-3 = SBASE (the system base MVA)
by default.
R3-1, X3-1 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 trans-
former.

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 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.

VMSTAR vmstar The voltage magnitude at the hidden star point bus; entered in pu.

VMSTAR = 1.0 by default.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
41
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

ANSTAR anstar The bus voltage phase angle at the hidden star point bus; entered in degrees.

ANSTAR = 0.0 by default

All data items on the third record are read for both two- and three-winding transformers:

Field RAWX Key Description

WINDV1 windv1 When CW is 1, WINDV1 is the Winding 1 off-nominal turns ratio in pu of Winding
1 bus base voltage; WINDV1 = 1.0 by default.

When CW is 2, WINDV1 is the actual Winding 1 voltage in kV; WINDV1 is equal to

the base voltage of bus I by default.

When CW is 3, WINDV1 is the Winding 1 off-nominal turns ratio in pu of nominal

Winding 1 voltage, NOMV1; WINDV1 = 1.0 by default.
NOMV1 nomv1 The nominal (rated) Winding 1 voltage base in kV, or zero to indicate that nom-
inal Winding 1 voltage is assumed to be identical to the base voltage of bus I.
NOMV1 is used in converting magnetizing data between physical units and per
unit admittance values when CM is 2. NOMV1 is used in converting tap ratio data
between values in per unit of nominal Winding 1 voltage and values in per unit
of Winding 1 bus base voltage when CW is 3.

NOMV1 = 0.0 by default

ANG1 ang1 The winding one phase shift angle in degrees. For a two-winding transformer,
ANG1 is positive when the winding one bus voltage leads the winding two bus
voltage; for a three-winding transformer, ANG1 is positive when the winding one
bus voltage leads the T (or star) point bus voltage. ANG1 must be greater than
-180.0º and less than or equal to +180.0º. ANG1 = 0.0 by default.
RATE1n wdg1rate1,
wdg1rate2,
wdg1rate3,
wdg1rate4,
wdg1rate5,
wdg1rate6,
wdg1rate7,
wdg1rate8,
wdg1rate9,
wdg1rate10,
wdg1rate11,
wdg1rate12
COD1 cod1 The transformer control mode for automatic adjustments of the Winding 1 tap or
phase shift angle during power flow solutions:

• 0 - for fixed tap and fixed phase shift

• ±1 - for voltage control

• ±2 - for reactive power flow control

• ±3 - for active power flow control

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
42
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

• ±4 - for control of a dc line quantity (valid only for two-winding transformers)

• ±5 - for asymmetric active power flow control

If the control mode is entered as a positive number, automatic adjustment of this

transformer winding is enabled when the corresponding adjustment is activated
during power flow solutions; a negative control mode suppresses the automatic
adjustment of this transformer winding.

COD1 = 0 by default.
CONT1 cont1 The bus number, or extended bus name enclosed in single quotes (refer to Ex-
tended 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
transformer; 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.
NODE1 node1 A node number of bus CONT1. The bus section of bus CONT1 to which node
NODE1 is connected is the bus section for which voltage is to be controlled by the
transformer turns ratio adjustment option of the power flow solution activities
when COD1 is 1. NODE1 should be non-zero only for voltage controlling trans-
former windings. If bus CONT1 is not in a substation, NODE1 must be specified
as 0.

NODE1 = 0 by default.
RMA1, RMI1 rma1, rmi1 When |COD1| is 1, 2, 3, or 5, 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 or 5. No default is allowed.

Not used when |COD1| is 0 or 4; RMA1 = 1.1 and RMI1 = 0.9 by default.
VMA1, VMI1 vma1, vmi1 When |COD1| is 1, 2, 3, or 5, the upper and lower limits, respectively, of one of
the following:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
43
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

• 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 or 5. No default is allowed.

Not used when |COD1| is 0 or 4.

VMA1 = 1.1 and VMI1 = 0.9 by default.

NTP1 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 tab1 The number of a transformer impedance correction table if this transformer wind-
ing's 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 transformer
impedance correction is to be applied to this transformer winding. TAB1 = 0 by
default.

For three winding transformers, these impedance correction factors are applied
to the equivalent T-model impedance Z1 when ZCOD=0 and to the bus-to-bus
impedance Z12 when ZCOD=1.
CR1, CX1 cr1, cx1 The load drop compensation impedance for voltage controlling transformers en-
tered in pu on system base quantities; used when COD1 is 1.

CR1 + j CX1 = 0.0 by default

CNXA1 cnxa1 Winding connection angle in degrees; used when COD1 is 5. There are no restric-
tions on the value specified for CNXA1; if it is outside of the range from -90.0 to
+90.0, CNXA1 is normalized to within this range.

CNXA1 = 0.0 by default.

The first two data items on the fourth record are read for both two- and three-winding transformers; the
remaining data items are used only for three-winding transformers:

Field RAWX Key Description

WINDV2 windv2 When CW is 1, WINDV2 is the Winding 2 off-nominal turns ratio in pu of Winding
2 bus base voltage; WINDV2 = 1.0 by default.

When CW is 2, WINDV2 is the actual Winding 2 voltage in kV; WINDV2 is equal to

the base voltage of bus J by default.

When CW is 3, WINDV2 is the Winding 2 off-nominal turns ratio in pu of nominal

Winding 2 voltage, NOMV2; WINDV2 = 1.0 by default.
NOMV2 nomv2 The nominal (rated) Winding 2 voltage base in kV, or zero to indicate that nominal
Winding 2 voltage is assumed to be identical to the base voltage of bus J. NOMV2

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
44
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

is used in converting tap ratio data between values in per unit of nominal Winding
2 voltage and values in per unit of Winding 2 bus base voltage when CW is 3.

NOMV2 = 0.0 by default.

ANG2 ang2 The winding two phase shift angle in degrees. ANG2 is ignored for a two-winding
transformer. For a three-winding transformer, ANG2 is positive when the winding
two bus voltage leads the T (or star) point bus voltage. ANG2 must be greater
than -180.0º and less than or equal to +180.0º.

ANG2 = 0.0 by default.

RATE2n wdg2rate1, Winding 2's twelve three-phase ratings, entered in either MVA or current ex-
wdg2rate2, pressed as MVA, according to the value specified for XFRRAT specified on the first
wdg2rate3, data record (refer to Case Identification Data). Each RATEn2 = 0.0 (bypass loading
wdg2rate4, limit check for this transformer winding) by default.
wdg2rate5,
wdg2rate6,
wdg2rate7,
wdg2rate8,
wdg2rate9,
wdg2rate10,
wdg2rate11,
wdg2rate12
COD2 cod2 The transformer control mode for automatic adjustments of the Winding 2 tap or
phase shift angle during power flow solutions:

• 0 - for fixed tap and fixed phase shift

• ±1 - for voltage control

• ±2 - for reactive power flow control

• ±3 - for active power flow control

• ±5 - for asymmetric active power flow control

If the control mode is entered as a positive number, automatic adjustment of this

transformer winding is enabled when the corresponding adjustment is activated
during power flow solutions; a negative control mode suppresses the automatic
adjustment of this transformer winding.

COD2 = 0 by default.
CONT2 cont2 The bus number, or extended bus name enclosed in single quotes (refer to Ex-
tended 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
COD2 is 1. CONT2 should be non-zero only for voltage controlling transformer
windings.

CONT2 may specify a bus other than I, J, or K; in this case, the sign of CONT2
defines the location of the controlled bus relative to the transformer winding.
If CONT2 is entered as a positive number, or a quoted extended bus name, the

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
45
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

ratio is adjusted as if bus CONT2 is on the Winding 1 or Winding 3 side of the
transformer; if CONT2 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 |CONT2| is on the Winding 2 side of the transformer.

CONT2 = 0 by default.
NODE2 node2 A node number of bus CONT2. The bus section of bus CONT2 to which node
NODE2 is connected is the bus section for which voltage is to be controlled by the
transformer turns ratio adjustment option of the power flow solution activities
when COD2 is 1. NODE2 should be non-zero only for voltage controlling trans-
former windings. If bus CONT2 is not in a substation, NODE2 must be specified
as 0.

NODE2 = 0 by default.
RMA2, RMI2 rma2, rmi2 When |COD2| is 1, 2, 3, or 5, 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 or 5. No default is allowed.

Not used when |COD2| is 0.

RMA2 = 1.1 and RMI2 = 0.9 by default.

VMA2, VMI2 vma2, vmi2 When |COD2| is 1, 2, 3, or 5, 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 or 5. No default is allowed.

Not used when |COD2| is 0.

VMA2 = 1.1 and VMI2 = 0.9 by default

NTP2 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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
46
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

TAB2 tab2 The number of a transformer impedance correction table if this transformer wind-
ing's 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 transformer
impedance correction is to be applied to this transformer winding.

TAB2 = 0 by default.

For three winding transformers, these impedance correction factors are applied
to the equivalent T-model impedance Z2 when ZCOD=0 and to the bus-to-bus
impedance Z23 when ZCOD=1.
CR2, CX2 cr2, cx2 The load drop compensation impedance for voltage controlling transformers en-
tered in pu on system base quantities; used when COD2 is 1.

CR2 + j CX2 = 0.0 by default.

CNXA2 cnxa2 Winding connection angle in degrees; used when COD2 is 5. There are no restric-
tions on the value specified for CNXA2; if it is outside of the range from -90.0 to
+90.0, CNXA2 is normalized to within this range.

CNXA2 = 0.0 by default.

The fifth data record is specified only for three-winding transformers:

Field RAWX Key Description

WINDV3 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 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

ANG3 ang3 The winding three phase shift angle in degrees. ANG3 is positive when the wind-
ing three bus voltage leads the T (or star) point bus voltage. ANG3 must be greater
than -180.0º and less than or equal to +180.0º.

ANG3 = 0.0 by default

RATE3n wdg3rate3, Winding 3's twelve three-phase ratings, entered in either MVA or current ex-
wdg3rate2, pressed as MVA, according to the value specified for XFRRAT specified on the first
wdg3rate3, data record (refer to Case Identification Data).
wdg3rate4,
wdg3rate5, Each RATEn3 = 0.0 (bypass loading limit check for this transformer winding) by
wdg3rate6, default.
wdg3rate7,
wdg3rate8,

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
47
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

wdg3rate9,
wdg3rate10,
wdg3rate11,
wdg3rate12
COD3 cod3 The transformer control mode for automatic adjustments of the Winding 3 tap or
phase shift angle during power flow solutions:

• 0 - for fixed tap and fixed phase shift

• ±1 - for voltage control

• ±2 - for reactive power flow control

• ±3 - for active power flow control

• ±5 - for asymmetric active power flow control

If the control mode is entered as a positive number, automatic adjustment of this

transformer winding is enabled when the corresponding adjustment is activated
during power flow solutions; a negative control mode suppresses the automatic
adjustment of this transformer winding.

COD3 = 0 by default
CONT3 cont3 The bus number, or extended bus name enclosed in single quotes (refer to Ex-
tended 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
COD3 is 1. CONT3 should be non-zero only for voltage controlling transformer
windings.

CONT3 may specify a bus other than I, J, or K; in this case, the sign of CONT3
defines the location of the controlled bus relative to the transformer winding.
If CONT3 is entered as a positive number, or a quoted extended bus name, the
ratio is adjusted as if bus CONT3 is on the Winding 1 or Winding 2 side of the
transformer; if CONT3 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 |CONT3| is on the Winding 3 side of the transformer.

CONT3 = 0 by default
NODE3 node3 A node number of bus CONT3. The bus section of bus CONT3 to which node
NODE3 is connected is the bus section for which voltage is to be controlled by the
transformer turns ratio adjustment option of the power flow solution activities
when COD3 is 1. NODE3 should be non-zero only for voltage controlling trans-
former windings. If bus CONT3 is not in a substation, NODE3 must be specified
as 0.

NODE3 = 0 by default.
RMA3, RMI3 rma3, rmi3 When |COD3| is 1, 2, 3, or 5, the upper and lower limits, respectively, of one of
the following:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
48
Power Flow Data File (RAW) Transformer Data

Field RAWX Key Description

• Off-nominal turns ratio in pu of Winding 3 bus base voltage when |COD3| is 1
or 2 and CW is 1; RMA3 = 1.1 and RMI3 = 0.9 by default.

• Actual Winding 3 voltage in kV when |COD3| is 1 or 2 and CW is 2. No default

is allowed.

• Off-nominal turns ratio in pu of nominal Winding 3 voltage (NOMV3) when |

COD3| is 1 or 2 and CW is 3; RMA3 = 1.1 and RMI3 = 0.9 by default.

• Phase shift angle in degrees when |COD3| is 3 or 5. No default is allowed.

Not used when |COD3| is 0.

RMA3 = 1.1 and RMI3 = 0.9 by default

VMA3, VMI3 vma3, vmi3 When |COD3| is 1, 2, 3, or 5, 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 or 5. No default is allowed.

Not used when |COD3| is 0.

VMA3 = 1.1 and VMI3 = 0.9 by default

NTP3 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 tab3 The number of a transformer impedance correction table if this transformer wind-
ing's 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 transformer
impedance correction is to be applied to this transformer winding.

TAB3 = 0 by default

For three winding transformers, these impedance correction factors are applied
to the equivalent T-model impedance Z3 when ZCOD=0 and to the bus-to-bus
impedance Z31 when ZCOD=1.
CR3, CX3 cr3, cx3 The load drop compensation impedance for voltage controlling transformers en-
tered in pu on system base quantities; used when COD3 is 1.

CR3 + j CX3 = 0.0 by default

CNXA3 cnxa3 Winding connection angle in degrees; used when COD3 is 5. There are no restric-
tions on the value specified for CNXA3; if it is outside of the range from -90.0 to
+90.0, CNXA3 is normalized to within this range.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
49
Power Flow Data File (RAW) Three-Winding Transformer Notes

Field RAWX Key Description

CNXA3 = 0.0 by default

Transformer data input is terminated with a record specifying a Winding 1 bus number of zero.

1.15.1. 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 PSSE as
a grouping of three two-winding transformers, where each of these two-winding transformers models one
of the windings. While most of the three-winding transformer data is stored in the two-winding transformer
data arrays, it is accessible for reporting and modification only as three-winding transformer data.

In deriving winding impedances from the measured impedance data input values, one winding with a small
impedance, in many cases negative, often results. In the extreme case, it is possible to specify a set of mea-
sured impedances that themselves do not individually appear to challenge the precision limits of typical
power system calculations, but which result in one winding impedance of nearly (or identically) 0.0. Such
data could result in precision difficulties, and hence inaccurate results, when processing the system matrices
in power flow and short circuit calculations.

Whenever a set of measured impedance results in a winding reactance that is identically 0.0, a warning
message is printed by the three-winding transformer data input or data changing function, and the winding's
reactance is set to the zero impedance line threshold tolerance (or to 0.0001 if the zero impedance line
threshold tolerance itself is 0.0). Whenever a set of measured impedances results in a winding impedance for
which magnitude is less than 0.00001, a warning message is printed. As with all warning and error messages
produced during data input and data modification phases of PSSE, 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?).

Activity BRCH may be used to detect the presence of branch reactance magnitudes less than a user-specified
threshold tolerance; its use is always recommended whenever the user begins power system analysis work
using a new or modified system model.

1.15.2. Example Two-Winding Transformer Data Records

Figure 1.13 shows the data records for a 50 MVA, 138/34.5 kV two-winding transformer connected to system
buses with nominal voltages of 134 kV and 34.5 kV, and sample data on 100 MVA system base and winding
voltage bases of 134 kV and 34.5 kV.

Example of 2-Winding Transformer:

Data Formats

I,J,K,CKT,CW,CZ,CM,MAG1,MAG2,NMETR,NAME;,STAT,O1,F1,...,O4,F4,VECGRP

R1-2,X1-2,SBASE1-2

WINDV1,NOMV1,ANG1,RATE11...RATE121,COD1,CONT1,NODE1,RMA1,RMI1,

WINDV2,NOMV2

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
50
Power Flow Data File (RAW) Example Three-Winding Transformer
Data Records

Data

6150, 6151, 0, '1', 1, 1, 1, 0.0, 0.0, 2, 'TWO-WINDINGS', 1, 5, 1.0

0.0, 0.30, 100.0

1.0299, 0.0, 0.0, 50.0, 60.0, 75.0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 6151, 0, 1.1, 0.9, 1.025, 1.0, 33, 0, 0.0, 0.0

1.0, 0.0

Figure 1.13. Sample Data for Two-Winding Transformer

1.15.3. Example Three-Winding Transformer Data Records

Figure 1.14 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.

Example of 3-Winding Transformer:

Data Formats

I,J,K,CKT,CW,CZ,CM,MAG1,MAG2,NMETR,NAME;,STAT,O1,F1,...,O4,F4,VECGRP,ZCOD

R1-2,X1-2,SBASE1-2,R2-3,X2-3,SBASE2-3,R3-1,X3-1,SBASE3-1,VMSTAR,ANSTAR

WINDV1,NOMV1,ANG1,RATE11...RATE121,COD1,CONT1,NODE1,RMA1,RMI1,

WINDV2,NOMV2,ANG2,RATE12...RATE122,COD2,CONT2,NODE2,RMA2,RMI2,

WINDV3,NOMV3,ANG3,RATE13...RATE123,COD3,CONT3,NODE3,RMA3,RMI3,

Data

3001, 3002, 3000, '1', 1, 1, 1, 0.0, 0.0, 2, 'THREEWINDING', 1, 5, 1.0

0.003, 0.03, 100.0, 0.001, 0.03, 100.0, 0.001, 0.035, 100.0, 1.025, 0.0

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
51
Power Flow Data File (RAW) Transformer Vector Group Clock Posi-
tion and Phase Angle

1.00, 0.0, 0.0, 300, 400, 600, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3001, 0, 1.1, 0.9, 1.04, 1.0, 33, 0, 0.0, 0.0, 0.0

1.02, 0.0, 0.0, 300, 400, 600

1.00, 0.0, 0.0, 50, 60, 75

Figure 1.14. Sample Data for Three-Winding Transformer

1.15.4. Transformer Vector Group Clock Position and Phase Angle

Following examples provide how vector group clock position and power flow data winding phase angle are
defined.

1. Two winding delta-wye transformer

Figure 1.15. Two Winding Transformer Vector Group Clock Position and Phase
Angle
For delta-wye transformer with winding connections as shown in Figure 1.15(a), there is 30 degrees
phase shift between phase-to-neutral and phase-to-phase voltages. The delta winding bus voltages
[VABC] lag the wye winding bus voltages [Vabc] by 30 degrees. Therefore, using the PSSE power flow

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
52
Power Flow Data File (RAW) Transformer Vector Group Clock Posi-
tion and Phase Angle

winding phase shift angle convention (ANG1 is the winding 1 bus voltage by which leads winding 2 bus
voltage), the PSSE power flow data input is entered as:

• Vector group = Dyn11 [delta clock position is 12 and wye clock position is 11.]

• ANG1 = -30 degrees [that is winding 1 bus voltage lags winding 2 bus voltage by 30 degrees.]

2. Three winding wye-delta-delta transformer

Figure 1.16. Three Winding Transformer Vector Group Clock Position and Phase
Angle
Figure 1.16(a) shows three winding wye-delta-delta transformer winding connections. Figure 1.16(b)
shows its T-model representation in analysis. It is three two winding transformers, with star-point trans-
formers modeled as wye-grounded for flow continuity between windings.

• Winding 1 - Figure 1.16(c) shows phasor diagram of winding 1 and star-point. It is a wye-wye trans-
former.

• Vector group = YNyn0 [wye clock position is 12 and star-point wye clock position is 12.]

• ANG1 = 0 degress [that is winding 1 bus voltage is in phase with VSTAR bus voltage.]

• Windings 2 and 3 - Figure 1.16(d) shows phasor diagram of winding 2 - star-point and winding 3
– star-point. They are delta-wye transformers. Using the ANSI/IEEE standard for transformers stating
that the HV winding bus voltages phase angle should lead the LV winding bus voltages, the delta
winding bus voltage [VABC] leads the star-point wye winding bus voltage [Vabc] by 30 degrees.

• Vector group = D11yn0 [delta clock position is 11 and star-point wye clock position is 12.]

• ANG1 = +30 degrees [that is delta winding bus voltage leads the star-point VSTAR bus voltage by
30 degrees.]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
53
Power Flow Data File (RAW) Two Winding Transformer Vector
Groups

• Therefore, for this wye-delta-delta transformer, power flow data is provided as below:

• Vector group = YN0d11d11

• ANG1 = 0, ANG2 = +30, ANG3 = +30 degrees

1.15.5. Two Winding Transformer Vector Groups

Table 1.2 shows examples of two winding transformer vector groups, corresponding phase angles and con-
nection codes. A different winding clock position can be used by appropriately specifying the phase angle
ANG1.

Table 1.2. Examples of Two Winding Transformer Vector Groups

Vector Group PSSE Phase Transformer Connection Transformer Connection

Angle (ANG1) Type Code (CC) Type Code (CC)

YNyn0 0 shell 11 core 20

YNyn6 180 shell 11 core 20
YNd1 30 shell 12
YNd11 -30 shell 12
YNd5 150 shell 12
YNd7 -150 shell 12
ZNd0 0 shell 12 core 17
ZNd1 30 shell 12 core 17
ZNd6 180 shell 12 core 17
ZNd7 -150 shell 12 core 17
ZNyn1 30 shell 12 core 17
ZNyn11 -30 shell 12 core 17
ZNyn5 150 shell 12 core 17
ZNyn7 -150 shell 12 core 17
ZNy1 30 shell 12 core 17
ZNy11 -30 shell 12 core 17
ZNy5 150 shell 12 core 17
ZNy7 -150 shell 12 core 17
Dyn1 30 shell 13
Dyn11 -30 shell 13
Dyn5 150 shell 13
Dyn7 -150 shell 13
Dzn0 0 shell 13 core 16
Dzn1 30 shell 13 core 16
Dzn6 180 shell 13 core 16
Dzn7 -150 shell 13 core 16
YNzn1 30 shell 13 core 16

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
54
Power Flow Data File (RAW) Three Winding Transformer Vector
Groups

YNzn11 -30 shell 13 core 16

YNzn5 150 shell 13 core 16
YNzn7 -150 shell 13 core 16
Yzn1 30 shell 13 core 16
Yzn11 -30 shell 13 core 16
Yzn5 150 shell 13 core 16
Yzn7 -150 shell 13 core 16
Dd0 0 shell 14
Dd6 180 shell 14
Dy1 30 shell 14
Dy11 -30 shell 14
Dy5 150 shell 14
Dy7 -150 shell 14
Yd1 30 shell 14
Yd11 -30 shell 14
Yd5 150 shell 14
Yd7 -150 shell 14
YNy0 0 shell 14 core 12
YNy6 180 shell 14 core 12
Yyn0 0 shell 14 core 13
Yyn6 180 shell 14 core 13
Yy0 0 shell 14
Yy6 180 shell 14
YNa0 0 core 18 or 19 shell 21
Ya0 0 core 22 shell 14

1.15.6. Three Winding Transformer Vector Groups

Table 1.3 through Table 1.11 show examples of three winding transformer vector groups, corresponding
phase angles and connection codes. A different winding clock position can be used by appropriately speci-
fying the phase angles ANG1, ANG2 and ANG3.

Vector groups are specified forming combinations of allowed winding connections and clock positions for
various transformer connection codes.

Table 1.3. Clock Positions and Phase Angles specified in Transformer Power Flow Data
Clock Position Phase Angles (ANG1/ANG2/ANG3)
0 0
6 180
1 -30
5 -150
7 150
11 30

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
55
Power Flow Data File (RAW) Three Winding Transformer Vector
Groups

Table 1.4. Three Winding CC=11

Allowed Winding Configurations Allowed Clock Positions
Winding 1 YN 0, 6
Winding 2 yn 0, 6
Winding 3 yn 0, 6
Examples YN0yn6yn0, ANG1=0, ANG2=180, ANG3=0

YN0yn0yn0, ANG1=0, ANG2=0, ANG3=0

Table 1.5. Three Winding CC=12

Allowed Winding Configurations Allowed Clock Positions
Winding 1 YN 0, 6
Winding 2 yn 0, 6
Winding 3 y 0, 6
d 1, 5, 7, 11
Examples YN0yn6d5, ANG1=0, ANG2=180, ANG3=-150

YN6yn0y0 ANG1=180, ANG2=0, ANG3=0

Table 1.6. Three Winding CC=13

Allowed Winding Configurations Allowed Clock Positions
Winding 1 D 1, 5, 7, 11
Winding 2 yn 0, 6
Winding 3 d 1, 5, 7, 11
Examples D1YN0d1, ANG1=-30, ANG2=0, ANG3=0

D5YN0d5, ANG1=-150, ANG2=0, ANG3=-150

Table 1.7. Three Winding CC=14

Allowed Winding Configurations Allowed Clock Positions
Winding 1 Y 0, 6
D 1, 5, 7, 11
Winding 2 y 0, 6
d 1, 5, 7, 11
Winding 3 y 0, 6
d 1, 5, 7, 11
Examples Y6d11d7, ANG1=180, ANG2=30, ANG3=150

D1d1y6, ANG1=-30, ANG2=-30, ANG3=180

Table 1.8. Three Winding CC=15

Allowed Winding Configurations Allowed Clock Positions
Winding 1* D 1, 5, 7, 11

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
56
Power Flow Data File (RAW) Areas, Zones and Owners

Allowed Winding Configurations Allowed Clock Positions

Winding 2 yn 0, 6
Winding 3* d 1, 5, 7, 11
Examples D1yn0d1, ANG1=-30, ANG2=0, ANG3=-30

D1yn6d11, ANG1= -30, ANG2=180, ANG3=30

* Note: Windings 1 and 3 form auto-transformer. So their clock positions are always identical.

Table 1.9. Three Winding CC=16

Allowed Winding Configurations Allowed Clock Positions
Winding 1 YN 0, 6
Winding 2 yn 0, 6
Winding 3 yn 0, 6
Examples YN0yn0yn0, ANG1=0, ANG2=0, ANG3=0

YN6yn0yn6, ANG1=180, ANG2=0, ANG3=180

Table 1.10. Three Winding CC=17

Allowed Winding Configurations Allowed Clock Positions
Winding 1 YNa 0
Winding 2
Winding 3 d 1, 5, 7, 11
Examples YNa0d1, ANG1=0, ANG2=0, ANG3=-30

YNa0d7, ANG1=0, ANG2=0, ANG3=150

Table 1.11. Three Winding CC=18

Allowed Winding Configurations Allowed Clock Positions
Winding 1 Ya 0
Winding 2
Winding 3 d 1, 5, 7, 11
Examples Ya0d5, ANG1=0, ANG2=0, ANG3=-150

Ya0d11, ANG1=0, ANG2=0, ANG3=30

1.16. Areas, Zones and Owners

In the analysis of large scale power systems for both planning and operations purposes, it is often convenient
to be able to restrict the processing or reporting of PSSE functions to one or more subsets of the complete
power system model. PSSE provides three groupings of network elements which may be used for these
purposes: areas, zones, and owners.

Areas are commonly used to designate sections of the network that represent control areas between which
there are scheduled flows. PSSE provides for the identification of areas and their schedules. Alternatively, the
network can be subdivided between utility companies or any other subdivisions useful for specific analyses.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
57
Power Flow Data File (RAW) Areas, Zones and Owners

Each ac bus, load, and induction machine, as well as each dc bus of each multi-terminal dc line, is assigned
to an area.

Assigning buses to specific zones allows an additional subdivision of the network to facilitate analyses and
documentation. While PSSE provides documentation of zone interchange, it provides no analytical facility to
schedule interchange between zones. Each ac bus, load, and induction machine as well as each dc bus of
each multi-terminal dc line, is assigned to a zone.

Although areas cannot overlap other areas and zones cannot overlap other zones, areas and zones can over-
lap each other.

Figure 1.17 shows a system subdivided into three areas and three zones, each with a unique name. Notice
the following:

• An area does not have to be contiguous. Area #1 covers two separate parts of the network.

• Zone #1 lies entirely in Area #1.

• Zone #2 lies partly in Area #1 and partly in Area #4.

• Zone #3 lies partly in Area 4 and Area 2.

Figure 1.17. Overlapping Areas and Zones

Assigning ownership attributes to buses and other equipment allows an additional subdivision of the network
for analysis and documentation purposes. PSSE provides neither analytical facility to schedule interchange

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
58
Power Flow Data File (RAW) Area Interchange Data

between owners, nor documentation of owner interchange. Each of the following power system elements
is assigned to a single owner:

• ac bus

• load

• induction machine

• dc bus of a multi-terminal dc line

• FACTS device

• GNE device

Each of the following elements may have up to four owners:

• synchronous machine

• non-transformer branch

• two-winding and three-winding transformer

• VSC dc line

Area, zone and owner assignments are established at the time the network element is introduced into the
working case, either as specified by the user or to a documented default value. Assignments may be modified
either through the standard power flow data modification functions (refer to Section 5.9, Changing Service
Status and Power Flow Parametric Data) or via activities ARNM, OWNM and ZONM.
Additional Information
See also: Section 4.8, Subsystem Selection Section 4.9, Subsystem Reporting Adjusting Net Inter-
change Area Interchange Control Area Interchange Data Interarea Transfer Data Owner Data Zone
Data Bus Data Load Data Generator Data Non-Transformer Branch Data Transformer Data Volt-
age Source Converter (VSC) DC Transmission Line Data Multi-Terminal DC Transmission Line Data

Induction Machine Data FACTS Device Data

1.17. Area Interchange Data

Area identifiers and interchange control parameters are specified in area interchange data records. Data for
each interchange area may be specified either at the time of raw/rawx data input or subsequently via activity
CHNG or the area [Spreadsheet]. Each area interchange data record has the following format:

RAW Record Format

I, ISW, PDES, PTOL, ARNAME

RAWx Record Format

"area":{
"fields":["iarea", "isw", "pdes", "ptol", "arname"],
"data":[
[1, 101, -2800.0, 10.0, "CENTRAL"],

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
59
Power Flow Data File (RAW) Area Interchange Data Notes

...

[6, 402, 300.0, 20.0, "EAST_COGEN2"]

]
}

Field RAWX Key Description

I iarea Area number (1 through 9999).

No default allowed.
ISW isw Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of the area slack bus for area interchange control. The bus must be a
generator (Type 2) bus in the specified area. Any area containing a system swing
bus (Type 3) must have either that swing bus or a bus number of zero specified
for its area slack bus number. Any area with an area slack bus number of zero is
considered a floating area by the area interchange control option of the power
flow solution activities.

ISW = 0 by default.
PDES pdes Desired net interchange leaving the area (export); entered in MW. PDES must be
specified such that is consistent with the area interchange definition implied by
the area interchange control code (tie lines only, or tie lines and loads) to be spec-
ified during power flow solutions (refer to Section 6.3.20, Automatic Adjustments
and Area Interchange Control).

PDES = 0.0 by default.

PTOL ptol Interchange tolerance bandwidth; entered in MW.

PTOL = 10.0 by default

ARNAME arname Alphanumeric identifier assigned to area I. ARNAME may be up to twelve char-
acters and may contain any combination of blanks, uppercase letters, numbers
and special characters. ARNAME must be enclosed in single or double quotes if it
contains any blanks or special characters.

ARNAME is twelve blanks by default

Area interchange data input is terminated with a record specifying an area number of zero.

1.17.1. Area Interchange Data Notes

All buses (ac and dc), loads and induction machines can be assigned to an area. The area number is entered
as part of the data records for the buses, loads, and induction machines (see Areas, Zones and Owners, Bus
Data, Load Data and Multi-Terminal DC Transmission Line Data).

Area interchange is a required net export of power from, or net import of power to, a specific area. This does
not imply that the power is destined to be transferred to or from any other specific area. To specify transfers
between specific pairs of areas, see Interarea Transfer Data.

Each bus in the PSSE working case may be designated as residing in an interchange area, for purposes of
both interchange control and selective output and other processing. When the interchange control option

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
60
Power Flow Data File (RAW) Two-Terminal DC Transmission Line Da-
ta

is enabled during a power flow solution, each interchange area for which an area slack bus is specified has
the active power output of its area slack bus modified such that the desired net interchange for the area falls
within a desired band. Refer to Area Interchange Control for further discussion on this option of the power
flow solution activities.

1.18. Two-Terminal DC Transmission Line Data

The two-terminal dc transmission line model is used to simulate either a point-to-point system with rectifier
and inverter separated by a bipolar or mono-polar transmission system or a back-to-back system where the
rectifier and inverter are physically located at the same site and separated only by a short bus-bar.

Figure 1.18. Two Terminal DC Configuration

The data requirements fall into three groups:

• Control parameters and set-points

• Converter transformers

• The dc line characteristics

RAW Record Format (3 lines)

NAME, MDC, RDC, SETVL, VSCHD, VCMOD, RCOMP, DELTI, METER, DCVMIN, CCCITMX, CCCACC

IPR, NBR, ANMXR, ANMNR, RCR, XCR, EBASR, TRR, TAPR, TMXR, TMNR, STPR, ICR, NDR,
IFR, ITR, IDR, XCAPR

IPI, NBI, ANMXI, ANMNI, RCI, XCI, EBASI, TRI, TAPI, TMXI, TMNI, STPI, ICI, NDI,
IFI, ITI, IDI, XCAPI

RAWx Record Format

"twotermdc":{
"fields":["name", "mdc", "rdc", "setvl", "vschd", "vcmod", "rcomp",
"delti", "met", "dcvmin", "cccitmx", "cccacc", "ipr", "nbr",
"anmxr", "anmnr", "rcr", "xcr", "ebasr", "trr", "tapr",
"tmxr","tmnr", "stpr", "icr", "ndr", "ifr", "itr", "idr",
"xcapr", "ipi", "nbi", "anmxi", "anmni", "rci", "xci", "ebasi",
"tri", "tapi", "tmxi", "tmni", "stpi", "ici", "ndi", "ifi",
"iti", "idi", "xcapi"],
"data":[
["TWO_TERM_DC1", 1, 7.8543, 1490.65, 525.0, 400.0, 3.942, 0.1556,
"I", 0.00, 20, 1.0, 301, 2, 13.00, 7.50, 0.0111, 3.88, 500.0, 0.44,
1.06275, 1.1, 0.9, 0.00525, 0, 0, 0, 0, "1 ", 2.0034, 3021, 2, 21.00,
18.5, 0.0, 3.047, 230.0, 0.95652, 1.075, 1.1, 0.8, 0.00625, 0, 0,
152, 3021, "T4", 2.0],

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
61
Power Flow Data File (RAW) Two-Terminal DC Transmission Line Da-
ta

...

["TWO_TERM_DC2", 1, 8.2, 1500.0, 525.0, 400.0, 4.1, 0.15, "I", 0.00,

20, 1.0, 301, 2, 12.0, 8.0, 0.011, 3.88, 500.0, 0.44, 1.0545, 1.112,
0.9, 0.00515, 0, 0, 0, 0, "1 ", 0.0098, 3022, 2, 20.0, 18.0, 0.012,
3.047, 230.0, 0.95652, 1.06250, 1.1, 0.8, 0.00625, 0, 0, 152, 3022,
"T5", 0.0074]
]
}

The first of the three dc line data records defines the following line quantities and control parameters:

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to this dc line. Each two-terminal
dc line must have a unique NAME. NAME may be up to twelve characters and
may contain any combination of blanks, uppercase letters, numbers and special
characters. NAME must be enclosed in single or double quotes if it contains any
blanks or special characters.

No default allowed
MDC mdc Control mode: 0 for blocked, 1 for power, 2 for current.

MDC = 0 by default
RDC rdc The dc line resistance; entered in ohms.

No default allowed
SETVL setvl Current (amps) or power (MW) demand. When MDC is one, a positive value of
SETVL specifies desired power at the rectifier and a negative value specifies de-
sired inverter power.

No default allowed
VSCHD vschd Scheduled compounded dc voltage; entered in kV.

No default allowed
VCMOD vcmod Mode switch dc voltage; entered in kV. When the inverter dc voltage falls below
this value and the line is in power control mode (i.e., MDC = 1), the line switches to
current control mode with a desired current corresponding to the desired power
at scheduled dc voltage.

VCMOD = 0.0 by default

RCOMP rcomp Compounding resistance; entered in ohms. Gamma and/or TAPI is used to attempt
to hold the compounded voltage (VDCI + DCCUR*RCOMP) at VSCHD. To control
the inverter end dc voltage VDCI, set RCOMP to zero; to control the rectifier end
dc voltage VDCR, set RCOMP to the dc line resistance, RDC; otherwise, set RCOMP
to the appropriate fraction of RDC.

RCOMP = 0.0 by default

DELTI delti Margin entered in per unit of desired dc power or current. This is the fraction
by which the order is reduced when ALPHA is at its minimum and the inverter is
controlling the line current.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
62
Power Flow Data File (RAW) Two-Terminal DC Transmission Line Da-
ta

Field RAWX Key Description

DELTI = 0.0 by default
METER met Metered end code of either R (for rectifier) or I (for inverter).

METER = I by default
DCVMIN dcvmin Minimum compounded dc voltage; entered in kV. Only used in constant gamma
operation (i.e., when ANMXI = ANMNI) when TAPI is held constant and an ac
transformer tap is adjusted to control dc voltage (i.e., when IFI, ITI, and IDI specify
a two-winding transformer).

DCVMIN = 0.0 by default

CCCITMX cccitmx Iteration limit for capacitor commutated two-terminal dc line Newton solution
procedure.

CCCITMX = 20 by default
CCCACC cccacc Acceleration factor for capacitor commutated two-terminal dc line Newton solu-
tion procedure.

CCCACC = 1.0 by default

The second of the three dc line data records defines rectifier end data quantities and control parameters:

Field RAWX Key Description

IPR ipr, ipi Rectifier converter bus number, or extended bus name enclosed in single quotes
(refer to Extended Bus Names).

No default allowed
NBR nbr, nbi Number of bridges in series (rectifier).

No default allowed
ANMXR anmxr, an- Nominal maximum rectifier firing angle; entered in degrees.
mxi
No default allowed
ANMNR anmnr, an- Minimum steady-state rectifier firing angle; entered in degrees.
mni
No default allowed
RCR rcr, rci Rectifier commutating transformer resistance per bridge; entered in ohms.

No default allowed
XCR xcr, xci Rectifier commutating transformer reactance per bridge; entered in ohms.

No default allowed
EBASR ebasr, ebasi Rectifier primary base ac voltage; entered in kV.

No default allowed
TRR trr, tri Rectifier transformer ratio.

TRR = 1.0 by default

TAPR tapr, tapi Rectifier tap setting. TAPR = 1.0 by default.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
63
Power Flow Data File (RAW) Two-Terminal DC Transmission Line Da-
ta

Field RAWX Key Description

If no two-winding transformer is specified by IFR, ITR, and IDR, TAPR is adjusted to
keep alpha within limits; otherwise, TAPR is held fixed and this transformer's tap
ratio is adjusted. The adjustment logic assumes that the rectifier converter bus is
on the Winding 2 side of the transformer. The limits TMXR and TMNR specified
here are used; except for the transformer control mode flag (COD1 of Transformer
Data), the ac tap adjustment data is ignored.
TMXR tmxr, tmxi Maximum rectifier tap setting.

TMXR = 1.5 by default

TMNR tmnr, tmni Minimum rectifier tap setting.

TMNR = 0.51 by default

STPR stpr, stpi Rectifier tap step; must be positive.

STPR = 0.00625 by default

ICR icr, ici Bus number of the rectifier commutating bus (rectifier firing angle measuring
bus), or extended bus name enclosed in single quotes (refer to Extended Bus
Names). The firing angle and angle limits used inside the dc model are adjusted
by the difference between the phase angles at this bus and the ac/dc interface
(i.e., the converter bus, IPR).

ICR = 0 by default
NDR ndr, ndi A node number of bus ICR. The bus section of bus ICR to which node NDR is con-
nected is the bus section used as the rectifier commutating bus. If bus ICR is not
in a substation, NDR must be specified as 0.

NDR = 0 by default
IFR ifr, ifi Winding 1 side from bus number, or extended bus name enclosed in single
quotes, of a two-winding transformer.

IFR = 0 by default
ITR itr, iti Winding 2 side to bus number, or extended bus name enclosed in single quotes,
of a two-winding transformer.

ITR = 0 by default
IDR idr, idi Circuit identifier; the branch described by IFR, ITR, and IDR must have been en-
tered as a two-winding transformer; an ac transformer may control at most only
one dc converter.

IDR = '1' by default

XCAPR xcapr, xcapi Commutating capacitor reactance magnitude per bridge; entered in ohms.

XCAPR = 0.0 by default

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, ANMXI, ANMNI, RCI, XCI, EBASI, TRI, TAPI, TMXI, TMNI, STPI, ICI, NDI, IFI, ITI, IDI, XCAPI

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
64
Power Flow Data File (RAW) Two-Terminal DC Line Data Notes

DC line data input is terminated with a record specifying a blank dc line name or a dc line name of '0'.

1.18.1. 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, induction machines other dc line converters, FACTS device sending ends, and GNE devices
are permitted at converter buses.

When either XCAPR > 0.0 or XCAPI > 0.0, the two-terminal dc line is treated as capacitor commutated. Capac-
itor commutated two-terminal dc lines preclude the use of a remote ac transformer as commutation trans-
former 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.17, DC Lines.

1.19. 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.

Figure 1.19. VSC DC Configuration

RAW Record Format (three lines)

NAME, MDC, RDC, O1, F1, ... O4, F4

IBUS, TYPE, MODE, DCSET, ACSET, ALOSS, BLOSS, MINLOSS, SMAX, IMAX, PWF, MAXQ,
MINQ, VSREG, NREG, RMPCT

IBUS, TYPE, MODE, DCSET, ACSET, ALOSS, BLOSS, MINLOSS, SMAX, IMAX, PWF, MAXQ,
MINQ, VSREG, NREG, RMPCT

RAWx Record Format

"vscdc":{
"fields":["name", "mdc", "rdc", "o1", "f1", "o2", "f2", "o3", "f3", "o4",
"f4", "ibus1", "type1", "mode1", "dcset1", "acset1", "aloss1",
"bloss1","minloss1", "smax1", "imax1", "pwf1", "maxq1", "minq1",
"vsreg1", "nreg1", "rmpct1", "ibus2", "type2", "mode2", "dcset2",
"acset2", "aloss2", "bloss2", "minloss2", "smax2", "imax2", "pwf2",
"maxq2", "minq2", "vsreg2", "nreg2", "rmpct2"],

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
65
Power Flow Data File (RAW) Voltage Source Converter (VSC) DC
Transmission Line Data

"data":[
["VDCLINE1", 1, 0.710, 1, 0.3204, 2, 0.3883, 3, 0.1942, 4, 0.0971,
3005, 2, 2, -209.0, 0.950, 100.0, 0.1, 50.0, 400.0, 1200.0, 0.1,
100.00, -110.00, 3005, 0, 100.0, 3008, 1, 1, 100.0, 0.99, 90.0,
0.150, 40.0, 350.0, 1200.0, 0.15, 150.0, -140.0, 3008, 0, 100.0],
...
["VDCLINE2", 1, 0.35, 1, 0.3705, 2, 0.3597, 3, 0.1799, 4, 0.0899,
203, 2, 1, -100.0, 1.0, 100.0, 0.15, 123.0, 200.0, 1200.0, 1.0,
200.0, -150.0, 203, 0, 100.0, 205, 1, 1, 100.0, 1.0, 93.0, 0.12,
98.0, 250.0, 1250.0, 1.0, 225.0, -250.0, 205, 0, 99.0]
]
}

The first of the three VSC dc line data records defines the following line quantities and control parameters:
Field RAWX Key Description
NAME name The non-blank alphanumeric identifier assigned to this dc line. Each VSC dc line
must have a unique NAME. NAME may be up to twelve characters and may contain
any combination of blanks, uppercase letters, numbers and special characters.
NAME must be enclosed in single or double quotes if it contains any blanks or
special characters.

No default allowed.
MDC mdc Control mode:

• 0 - for out-of-service

• 1 - for in-service

MDC = 1 by default.
RDC rdc The dc line resistance; entered in ohms. RDC must be positive.

No default allowed
Oi o1, o2, o3, An owner number (1 through 9999). Each VSC dc line may have up to four own-
o4 ers. By default, O1 is 1, and O2, O3 and O4 are zero.
Fi f1, f2, f3, f4 The 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.

Each Fi is 1.0 by default

The remaining two data records define the converter buses (converter 1 and converter 2), along with their
data quantities and control parameters:
Field RAWX Key Description
IBUS ibus Converter bus number, or extended bus name enclosed in single quotes (refer to
Extended Bus Names).

No default allowed
TYPE type Code for the type of converter dc control:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
66
Power Flow Data File (RAW) Voltage Source Converter (VSC) DC
Transmission Line Data

Field RAWX Key Description

• 0 - for converter out-of-service

• 1 - for dc voltage control

• 2 -for MW control

When both converters are in-service, exactly one converter of each VSC dc line
must be TYPE 1.

No default allowed
MODE mode Converter ac control mode:

• 1 - for ac voltage control

• 2 - for fixed ac power factor

MODE = 1 by default
DCSET dcset Converter dc setpoint. For TYPE = 1, DCSET is the scheduled dc voltage on the dc
side of the converter bus; entered in kV. For TYPE = 2, DCSET is the power demand,
where a positive value specifies that the converter is feeding active power into
the ac network at bus IBUS, and a negative value specifies that the converter is
withdrawing active power from the ac network at bus IBUS; entered in MW.

No default allowed
ACSET acset Converter ac setpoint. For MODE = 1, ACSET is the regulated ac voltage setpoint;
entered in pu. For MODE = 2, ACSET is the power factor setpoint.

ACSET = 1.0 by default

ALOSS, aloss, bloss Coefficients of the linear equation used to calculate converter losses:
BLOSS
KWconv loss = ALOSS + (Idc * BLOSS)

ALOSS is entered in kW. BLOSS is entered in kW/amp.

ALOSS = BLOSS = 0.0 by default

MINLOSS minloss Minimum converter losses; entered in kW.

MINLOSS = 0.0 by default

SMAX smax Converter MVA rating; entered in MVA. SMAX = 0.0 to allow unlimited converter
MVA loading.

SMAX = 0.0 by default

IMAX imax Converter ac current rating; entered in amps. IMAX = 0.0 to allow unlimited con-
verter current loading. If a positive IMAX is specified, the base voltage assigned
to bus IBUS must be positive.

IMAX = 0.0 by default

PWF 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 vio-

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
67
Power Flow Data File (RAW) VSC DC Line Data Notes

Field RAWX Key Description

lated. 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 maxq Reactive power upper limit; entered in Mvar. A positive value of reactive power
indicates reactive power flowing into the ac network from the converter; a nega-
tive value of reactive power indicates reactive power withdrawn from the ac net-
work. Not used if MODE = 2.

MAXQ = 9999.0 by default

MINQ minq Reactive power lower limit; entered in Mvar. A positive value of reactive power
indicates reactive power flowing into the ac network from the converter; a nega-
tive value of reactive power indicates reactive power withdrawn from the ac net-
work. Not used if MODE = 2.

MINQ = -9999.0 by default

VSREG vsreq Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of the bus for which voltage is to be regulated by this converter to
the value specified by ACSET. If VSREG specifies a remote bus (i.e., a bus other
than bus IBUS), bus VSREG must be a Type 1 or 2 bus (if it is other than a Type
1 or 2 bus, bus IBUS regulates its own voltage to the value specified by ACSET).
VSREG may be entered as zero if the converter is to regulate its own voltage. Not
used if MODE = 2.

VSREG = 0 by default
NREG nreg A node number of bus VSREG. The bus section of bus VSREG to which node NREG
is connected is the bus section for which voltage is to be regulated by this con-
verter to the value specified by ACSET. If bus VSREG is not in a substation, NREG
must be specified as 0.

NREG = 0 by default
RMPCT rmpct Percent of the total Mvar required to hold the voltage at the bus controlled by bus
IBUS that are to be contributed by this VSC converter; RMPCT must be positive.
RMPCT is needed only if there is more than one local or remote setpoint mode
voltage controlling device (plant, switched shunt, FACTS device shunt element,
or VSC dc line converter) controlling the voltage at bus VSREG.

RMPCT = 100.0 by default

VSC dc line data input is terminated with a record specifying a blank dc line name or a dc line name of '0'.

1.19.1. 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, induction machines,
other dc line converters, FACTS device sending ends, and GNE devices are permitted at converter buses.

• It must not have the terminal end of a FACTS device connected to the same bus.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
68
Power Flow Data File (RAW) Transformer Impedance Correction Ta-
bles

• It must not be connected by a zero impedance line to another bus that violates any of the above restrictions.

In specifying reactive power limits for converters that control ac voltage (i.e., those with unequal reactive
power limits where the MODE is 1), the use of very narrow var limit bands is discouraged. The Newton-Raph-
son 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 VSC converters have Mvar
ranges substantially wider than this minimum permissible range.

For interchange and loss assignment purposes, the dc voltage controlling converter is assumed to be the
non-metered end of each VSC dc line. As with other network branches, losses are assigned to the subsystem
of the non-metered end, and flows at the metered ends are used in interchange calculations.

For additional information on dc line modeling in power flow solutions, refer to Section 6.3.17 DC Lines.

1.20. Transformer Impedance Correction Tables

Transformer impedance correction tables are used to model a change of transformer impedance as off-nom-
inal turns ratio or phase shift angle is adjusted. Data for each table may be specified either at the time of raw
data input, or subsequently via activity CHNG or the impedance table [Spreadsheet].

Each impedance correction table may have up to 99 points. The scaling factors are complex numbers; the
imaginary components of these factors may be specified as 0.0. Points are specified six per line in the im-
pedance correction table data block. As many records as are needed (with six points per record) are entered.
End of data for a table is specified by specifying an additional point with the three values defining the point
all specified as 0.0.

RAW Record Format

I, T1, Re(F1), Im(F1), T2, Re(F2), Im(F2), ..., T6, Re(F6), Im(F6)

T7, Re(F7), Im(F7), T8, Re(F8), Im(F8), ..., T12, Re(F12), Im(F12)

...

...

Tn, Re(Fn), Im(Fn), 0.0, 0.0, 0.0

RAWX Parameter Set Format (one data row for each point)

"impcor":{
"fields":["itable", "tap", "refact", "imfact"]
"data":[
[1, -30.0, 1.100, 0.000],
[1, -24.0, 1.091, 0.000],
...
[1, 30.0, 1.110, 0.000],
[2, 0.6, 1.060, 0.000],
...
[2, 1.4, 0.950, 0.000]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
69
Power Flow Data File (RAW) Impedance Correction Table Notes

]
}

Field RAWX Key Description

I itable Impedance correction table number (1 through the maximum number of imped-
ance correction tables at the current size level; refer to Table 3-1, Standard Max-
imum PSS®E Program Capacities).

No default allowed
Ti tap Either off-nominal turns ratio in pu of the controlling windings bus voltage base
or phase shift angle in degrees.

Ti = 0.0 by default
Fi refact, im- Complex scaling factor by which transformer nominal impedance is to be mul-
fact tiplied to obtain the actual transformer impedance for the corresponding Ti. Fi
= (0.0+j0.0) by default. The impedances used in calculation of Fi should be ex-
pressed in percent or pu on winding voltage base at specified tap position Ti and
MVA base used in power flow data. This is the same base as per CZ of power flow
data but winding voltage at tap Ti.

Transformer impedance correction data input is terminated with a record specifying a table number of zero.

Example: Transformer Test Data, MVA=50, Nominal Tap position=10, winding voltage=132 kV,
Impedance=123.1118 ohms/phase

Tap Position Winding kV Z12 Data Base Z (ohms) PU Z

(ohms/phase)
1 112.20 81.7016 251.7768 0.3245
10 132.0 123.1118 346.48 0.3532
19 151.8 178.8155 460.8648 0.3880

Corresponding Impedance Correction Table data would be as below (CZ=2).

Ti Fi
0.85=112.2/132.0 0.9187=0.3245/0.3532
1.0=132.0/132.0 1.0=0.3532/0.3532
1.15=151.8/132.0 1.098277=0.3880/0.3532

1.20.1. Impedance Correction Table Notes

The Ti values on a transformer impedance correction table record block must all be either tap ratios or phase
shift angles. They must be entered in strictly ascending order; i.e., for each i, Ti+1>Ti. Each Fi entered must be
non-zero. For each table, at least 2 sets of values must be specified (plus the additional end-of-table point
of zeros), and up to 99 may be entered. For a graphical view of a correction table for which the imaginary
component of each scaling factor is 0.0, see Figure 1.20 .

The Ti values for tables that are a function of tap ratio (rather than phase shift angle) in pu of the controlling
winding bus voltage base.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
70
Power Flow Data File (RAW) Impedance Correction Table Notes

A transformer impedance is assigned to an impedance correction table either on the third, fourth or fifth
record of the transformer data record block of activities READ, TREA, RDCH (refer to Trans), or via activity
CHNG or the two-winding and three-winding transformer [Spreadsheets]. Each table may be shared among
many transformer impedances. If the first T in a table is less than 0.5 or the last T entered is greater than
1.5, T is assumed to be the phase shift angle and each transformer impedance dependent on the table is
treated as a function of phase shift angle. Otherwise, the transformer impedances dependent on the table
are made sensitive to off-nominal turns ratio.

For three-winding transformers, a data item associated with the transformer (ZCOD) indicates whether im-
pedance adjustment is to be applied to winding impedances or to the bus-to-bus impedances. If applied to
winding impedances, the input to the table look-up is the winding tap ratio or phase shift angle, as appro-
priate, and the scaling factor is applied to the winding's nominal impedance.

When impedance adjustment is applied to the bus-to-bus impedances of a three-winding transformer, the
following requirements must be met:

• exactly one winding of the transformer must be automatically adjustable.

• at least one winding must have an impedance correction table assigned to it.

• the impedance correction table(s) must be sensitive to the quantity that is automatically adjustable (tap
ratio or phase shift angle, as appropriate).

In this case, the input to each of the tables is the appropriate quantity (tap ratio or phase shift angle) of the
adjustable winding. If an impedance correction table is specified for winding 1, impedance adjustment is
applied to Z1-2; if an impedance correction table is specified for winding 2, impedance adjustment is applied
to Z2-3; and if an impedance correction table is specified for winding 3, impedance adjustment is applied
to Z3-1.

The power flow case stores both a nominal and actual impedance for each transformer winding imped-
ance. The value of transformer impedance entered in activities READ, TREA, RDCH, CHNG, or the transformer
[Spreadsheets] is taken as the nominal value of impedance. Each time the complex tap setting of a trans-
former is changed, either automatically by the power flow solution activities or manually by the user, and
the modified quantity is an input to the table look-up function of any impedance correction table associated
with the transformer, actual transformer impedances are redetermined if appropriate. First, the scaling fac-
tor 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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
71
Power Flow Data File (RAW) Multi-Terminal DC Transmission Line
Data

Figure 1.20. Typical Impedance Correction Factor Curve

1.21. Multi-Terminal DC Transmission Line Data

PSSE allows the representation of up to 12 converter stations on one multi-terminal dc line. The dc network of
each multi-terminal dc line may consist of up to 20 dc network buses connected together by up to 20 dc links.

Figure 1.21. Multi-Terminal DC Configuration

Each multi-terminal dc transmission line to be represented in PSSE 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 bus numbers and the control mode. Following
this first record there are subsequent records for each converter, each dc bus, and each dc link.

Each set of multi-terminal dc line data records begins with a record of system definition data in the following
format:

RAW Format

NAME, NCONV, NDCBS, NDCLN, MDC, VCONV, VCMOD, VCONVN

RAWx Record Format

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
72
Power Flow Data File (RAW) Multi-Terminal DC Transmission Line
Data

"ntermdc":{
"fields":["name","nconv","ndcbs","ndcln","mdc","vconv","vcmod","vconvn"],
"data":[
["MULTERM_DC_1", 4, 5, 4, 1, 212, 400.0, 0]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to this dc line. Each multi-termi-
nal dc line must have a unique NAME. NAME may be up to twelve characters and
may contain any combination of blanks, uppercase letters, numbers and special
characters. NAME must be enclosed in single or double quotes if it contains any
blanks or special characters.

No default allowed
NCONV nconv Number of ac converter station buses in multi-terminal dc line I.

No default allowed
NDCBS ndcbs Number of dc buses in multi-terminal dc line I (NCONV NDCBS).

No default allowed
NDCLN ndcln Number of dc links in multi-terminal dc line I.

No default allowed
MDC mdc Control mode:

• 0 - for blocked

• 1 - for power control

• 2 - for current control

MDC = 0 by default
VCONV vconv Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of the ac converter station bus that controls dc voltage on the posi-
tive pole of multi-terminal dc line I. Bus VCONV must be a positive pole inverter.

No default allowed
VCMOD vcmod Mode switch dc voltage; entered in kV. When any inverter dc voltage magnitude
falls below this value and the line is in power control mode (i.e., MDC = 1), the line
switches to current control mode with converter current setpoints corresponding
to their desired powers at scheduled dc voltage.

VCMOD = 0.0 by default

VCONVN vconvn Bus number, or extended bus name enclosed in single quotes, of the ac converter
station bus that controls dc voltage on the negative pole of multi-terminal dc line
I. If any negative pole converters are specified (see below), bus VCONVN must be
a negative pole inverter. If the negative pole is not being modeled, VCONVN must
be specified as zero.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
73
Power Flow Data File (RAW) Multi-Terminal DC Transmission Line
Data

Field RAWX Key Description

VCONVN = 0 by default

This data record is followed by NCONV converter records.

RAW Record Format

IB, N, ANGMX, ANGMN, RC, XC, EBAS, TR, TAP, TPMX, TPMN, TSTP, SETVL, DCPF,
MARG, CNVCOD

RAWx Record Format

"ntermdcconv":{
"fields":["name", "ib", "n", "angmx", "angmn", "rc", "xc", "ebas", "tr",
"tap", "tpmx", "tpmn", "tstp", "setvl", "dcpf", "marg", "cnvcod"],
"data":[
["MULTERM_DC_1", 402, 4, 10.0, 8.0, 0.0, 19.0, 500.0, 0.22, 1.01,
1.1, 0.97, 0.01, 321.0, 1.0, 0.15, 3],
...

["MULTERM_DC_1", 213, 4, 20.0, 18.0, 0.0, 10.0, 230.0, 0.452, 1.1,

1.1, 0.9, 0.01, -303.8, 1.0, 0.0, 4]
]
}

Field RAWX Key Description

IB ib ac converter bus number, or extended bus name enclosed in single quotes (refer
to Extended Bus Names).

No default allowed
N n Number of bridges in series.

No default allowed.
ANGMX angmx Nominal maximum ALPHA or GAMMA angle; entered in degrees.

No default allowed
ANGMN angmn Minimum steady-state ALPHA or GAMMA angle; entered in degrees.

No default allowed
RC rc Commutating resistance per bridge; entered in ohms.

No default allowed
XC xc Commutating reactance per bridge; entered in ohms.

No default allowed
EBAS ebs Primary base ac voltage; entered in kV.

No default allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
74
Power Flow Data File (RAW) Multi-Terminal DC Transmission Line
Data

Field RAWX Key Description

TR tr Actual transformer ratio.

TR = 1.0 by default
TAP tap Tap setting.

TAP = 1.0 by default

TPMX tpmx Maximum tap setting.

TPMX = 1.5 by default

TPMN tpmn Minimum tap setting.

TPMN = 0.51 by default

TSTP tstp Tap step; must be a positive number.

TSTP = 0.00625 by default

SETVL setvl Converter setpoint. When IB is equal to VCONV or VCONVN, SETVL specifies the
scheduled dc voltage magnitude, entered in kV, across the converter. SETVL is
positive for positive pole inverter and negative for negative pole inverter. 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 negative
value indicates an inverter.

No default allowed
DCPF dcpf Converter participation factor. When the order at any rectifier in the multi-termi-
nal 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 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 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
negative pole converters.

CNVCOD = 1 by default

RAW Record Format

These data records are followed by NDCBS dc bus records of the following format:

IDC, IB, AREA, ZONE, DCNAME, IDC2, RGRND, OWNER

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
75
Power Flow Data File (RAW) Multi-Terminal DC Transmission Line
Data

RAWx Record Format

"ntermdcbus":{
"fields":["name","idc","ib","area","zone","dcname","idc2","rgrnd","owner"],
"data":[
["MULTERM_DC_1", 1, 401, 4, 4, "DC1", 0, 0.0, 4],
...

["MULTERM_DC_1", 5, 0, 4, 4, "DC5", 0, 0.0, 4]

]
}

Field RAWX Key Description

IDC idc dc bus number (1 to NDCBS). The dc buses are used internally within each mul-
ti-terminal dc line and must be numbered 1 through NDCBS.

No default allowed
IB ib ac converter bus number, or extended bus name enclosed in single quotes (refer
to Extended Bus Names), or zero. Each converter station bus specified in a con-
verter record must be specified as IB in exactly one dc bus record. DC buses that
are connected only to other dc buses by dc links and not to any ac converter buses
must have a zero specified for IB. A dc bus specified as IDC2 on one or more other
dc bus records must have a zero specified for IB on its own dc bus record.

IB = 0 by default
AREA area Area number (1 through 9999).

AREA = 1 by default
ZONE zone Zone number (1 through 9999).

ZONE = 1 by default
DCNAME dcname Alphanumeric identifier assigned to dc bus IDC. DCNAME may be up to twelve
characters and may contain any combination of blanks, uppercase letters, num-
bers and special characters. DCNAME must be enclosed in single or double quotes
if it contains any blanks or special characters.

DCNAME is twelve blanks by default

IDC2 idc2 Second dc bus to which converter IB is connected, or zero if the converter is con-
nected directly to ground. For voltage controlling converters, this is the dc bus
with the lower dc voltage magnitude and SETVL specifies the voltage difference
between buses IDC and IDC2. For rectifiers, dc buses should be specified such that
power flows from bus IDC2 to bus IDC. For inverters, dc buses should be specified
such that power flows from bus IDC to bus IDC2. IDC2 is ignored on those dc bus
records that have IB specified as zero.

IDC2 = 0 by default
RGRND rgrnd Resistance to ground at dc bus IDC; entered in ohms. During solutions RGRND is
used only for those dc buses specified as IDC2 on other dc bus records.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
76
Power Flow Data File (RAW) Multi-Terminal DC Transmission Line
Data

Field RAWX Key Description

RGRND = 0.0 by default
OWNER owner Owner number (1 through 9999).

OWNER = 1 by default

RAW Record Format

These data records are followed by NDCLN dc link records of the following format:

IDC, JDC, CKT, MET, RDC, LDC

RAWx Record Format

"ntermdclink":{
"fields":["name", "idc", "jdc", "dcckt", "met", "rdc", "ldc"],
"data":[
["MULTERM_DC_1", 1, 5, "1", 1, 29.0000, 0.00],
...

["MULTERM_DC_1", 4, 5, "1", 1, 29.0000, 0.00]

]
}

Field RAWX Key Description

IDC idc Branch from bus dc bus number.

No default allowed
JDC jdc Branch to bus dc bus number.

No default allowed
CKT ckt One-character uppercase alphanumeric branch circuit identifier. It is recommend-
ed that single circuit branches be designated as having the circuit identifier '1'.

CKT = '1' by default

MET met Metered end flag:

• <= 1 - to designate bus IDC as the metered end

• >= 2 - to designate bus JDC as the metered end

MET = 1 by default
RDC rdc dc link resistance, entered in ohms.

No default allowed
LDC ldc dc link inductance, entered in mH. LDC is not used by the power flow solution
activities but is available to multi-terminal dc line dynamics models.

LDC = 0.0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
77
Power Flow Data File (RAW) Multi-Terminal DC Line Notes

Multi-terminal dc line data input is terminated with a record specifying a dc line number of zero.

1.21.1. 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 PSSE working memory. Therefore, there may simultaneously exist, for example, a
two-terminal dc line identified as dc line ABC along with a multi-terminal line for which the name is ABC.

• Multi-terminal lines should have at least three converter terminals; conventional dc lines consisting of two
terminals should be modeled as two-terminal lines (refer to Two-Terminal DC Transmission Line Data).

• AC converter buses may be Type 1, 2, or 3 buses. Generators, loads, fixed and switched shunt elements,
induction machines, other dc line converters, FACTS device sending ends, and GNE devices are permitted
at converter buses.

• Each multi-terminal dc line is treated as a subnetwork of dc buses and dc links connecting its ac converter
buses. For each multi-terminal dc line, the dc buses must be numbered 1 through NDCBS.

• Each ac converter bus must be specified as IB on exactly one dc bus record; there may be dc buses con-
nected only to other dc buses by dc links but not to any ac converter bus.

• AC converter bus IB may be connected to a dc bus IDC, which is connected directly to ground. IB is specified
on the dc bus record for dc bus IDC; the IDC2 field is specified as zero.

• Alternatively, ac converter bus IB may be connected to two dc buses IDC and IDC2, the second of which
is connected to ground through a specified resistance. IB and IDC2 are specified on the dc bus record for
dc bus IDC; on the dc bus record for bus IDC2, the ac converter bus and second dc bus fields (IB and IDC2,
respectively) must be specified as zero and the grounding resistance is specified as RGRND.

• The same dc bus may be specified as the second dc bus for more than one ac converter bus.

• All dc buses within a multi-terminal dc line must be reachable from any other point within the dc subnet-
work.

• The area numbers assigned to dc buses and the metered end designations of dc links are used in calculating
area interchange and assigning losses in activities AREA, INTA, TIES, and SUBS as well as in the interchange
control option of the power flow solution activities. Similarly, the zone assignments and metered end
specifications are used in activities ZONE, INTZ, TIEZ, and SUBS.

• Section 5.7.2 Reading RDCH Data Files Created by Previous Releases of PSS®E describes the specification of
NCONV, NDCBS and NDCLN when specifying changes to an existing multi-terminal dc line in activity RDCH.

For additional information on dc line modeling in power flow solutions, refer to Section 6.3.17, DC Lines.

A multi-terminal layout is shown in Figure 1.22. There are 4 convertors, 5 dc buses and 4 dc links.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
78
Power Flow Data File (RAW) Multi-Section Line Grouping Data

Figure 1.22. Multi-Terminal DC Network

1.22. Multi-Section Line Grouping Data

Transmission lines commonly have a series of sections with varying physical structures. The section might
have different tower configurations, conductor types and bundles, or various combinations of these. The
physical differences can result in the sections having different resistance, reactance and charging.

Figure 1.23. Multi-Section Line Grouping

A transmission line with several distinct sections can be represented as one multisection line group.

RAW Record Format

I, J, ID, MET, DUM1, DUM2, ..., DUM9

RAWx Record Format

"msline":{
"fields":["ibus", "jbus", "mslid", "met", "dum1", "dum2", "dum3", "dum4",
"dum5", "dum6", "dum7", "dum8", "dum9"],
"data":[
[101, 201, "&1", 2, 102, 103, 104, null, null, null, null, null, null]
...

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
79
Power Flow Data File (RAW) Multi-Section Line Example

]
}

Field RAWX Key Description

I ibus From bus number, or extended bus name enclosed in single quotes (refer to Ex-
tended Bus Names).

No default allowed
J jbus To bus number, or extended bus name enclosed in single quotes.

No default allowed
ID mslid Two-character upper case alphanumeric multi-section line grouping identifier.
The first character must be an ampersand (' ').

ID = '1' by default
MET 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
DUMi dum1, Bus numbers, or extended bus names enclosed in single quotes (refer to Extended
dum2, Bus Names), of the dummy buses connected by the branches that comprise this
dum3, multi-section line grouping.
dum4,
dum5, No defaults allowed
dum6,
dum7,
dum8,
dum9

Multi-section line grouping data input is terminated with a record specifying a from bus number of zero.

1.22.1. Multi-Section Line Example

The DUMi 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):

Figure 1.24. Multi-Section Line Example

The path from I to J is defined by the following branches:
I D1 C1

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
80
Power Flow Data File (RAW) Multi-Section Line Notes

D1 D2 C2
D2 J C3

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

1.22.2. 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 trans-
mission 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, Program Run-Time Option
Settings and activity OPTN), several power flow reporting activities such as POUT and LOUT do not tabulate
conditions at multi-section line dummy buses. Accordingly, care must be taken in interpreting power flow
output reports when dummy buses are other than passive nodes (e.g., if load or generation is present at a
dummy bus).

1.23. Zone Data

Zone identifiers are specified in zone data records. Zone names may be specified either at the time of raw/
rawx data input or subsequently via activity CHNG or the zone [Spreadsheet].

RAW Record Format

I, ZONAME

RAWx Record Format

"zone":{
"fields":["izone", "zoname"],
"data":[
[1, "NORTH_A1"],
...

[9, "ALL_A4_A6"]
]
}

Field RAWX Key Description

I izone Zone number (1 through 9999).

No default allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
81
Power Flow Data File (RAW) Zone Data Notes

Field RAWX Key Description

ZONAME zoname Alphanumeric identifier assigned to zone I. ZONAME may be up to twelve char-
acters 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

Zone data input is terminated with a record specifying a zone number of zero.

1.23.1. Zone Data Notes

All buses (ac and dc), loads, and induction machines can be assigned to a zone. The zone number is entered
as part of the data records for the buses, loads, and induction machines (see Areas, Zones and Owners, Bus
Data, Load Data and Multi-Terminal DC Transmission Line Data).

The use of zones enables the user to develop reports and to check results on the basis of zones and, conse-
quently, be highly specific when reporting and interpreting analytical results.

1.24. Interarea Transfer Data

The PSSE user has the ability to assign each bus, load, and induction machine 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.

Figure 1.25. Interarea Transfer

These active power transfers are specified in interarea transfer data records.

RAW Record Format

ARFROM, ARTO, TRID, PTRAN

RAWx Record Format

"iatrans":{
"fields":["arfrom", "arto", "trid", "ptran"],
"data":[
[1, 2, "A", 1000.0],
...

[3, 5, "D", 2900.0]

]
}

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
82
Power Flow Data File (RAW) Interarea Transfer Data Notes

Field RAWX Key Description

ARFROM arfrom From area number (1 through 9999).

No default allowed
ARTO arto To area number (1 through 9999).

No default allowed
TRID trid Single-character (0 through 9 or A through Z) upper case interarea transfer iden-
tifier used to distinguish among multiple transfers between areas ARFROM and
ARTO.

TRID = '1' by default

PTRAN ptran MW comprising this transfer. A positive PTRAN indicates that area ARFROM is sell-
ing to area ARTO.

PTRAN = 0.0 by default

Interarea transfer data input is terminated with a record specifying a from area number of zero.

1.24.1. 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).

1.25. Owner Data

PSSE 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, induction machines, FACTS devices, and GNE 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, Multi-Ter, and GNE Device 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.

Figure 1.26. Owner Data

Owner identifiers are specified in owner data records. Owner names may be specified either at the time of
raw/rawx data input or subsequently via activity CHNG or the owner [Spreadsheet].

RAW Record Format

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
83
Power Flow Data File (RAW) FACTS Device Data

I, OWNAME

RAWx Record Format

"owner":{
"fields":["iowner", "owname"],
"data":[
[1, "OWNER 1"],
...

[5, "OWNER 5"]

]
}

Field RAWX Key Description

I iowner Owner number (1 through 9999).

No default allowed
OWNAME owner Alphanumeric identifier assigned to owner I. OWNAME may be up to twelve char-
acters 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

Owner data input is terminated with a record specifying an owner number of zero.

1.26. FACTS Device Data

There are a variety of Flexible AC Transmission System (FACTS) devices currently available. These include
shunt devices, such as the Static Compensator (STATCOM), series devices such as the Static Synchronous
Series Compensator (SSSC), combined devices such as the Unified Power Flow Controller (UPFC), and parallel
series devices such as the Interline Power Flow Controller (IPFC).

Figure 1.27. FACTS Device Configuration

PSSE accepts data for all of these devices through one generic set of data records. Each FACTS device to be
represented in PSSE is specified in FACTS device data records.

RAW Record Format (on a single line)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
84
Power Flow Data File (RAW) FACTS Device Data

NAME, I, J, MODE, PDES, QDES, VSET, SHMX, TRMX, VTMN, VTMX, VSMX, IMX, LINX,
RMPCT, OWNER, SET1, SET2, VSREF, FCREG, NREG, MNAME

RAWx Record Format

"facts":{
"fields":["name", "ibus", "jbus", "mode", "pdes", "qdes", "vset", "shmx",
"trmx", "vtmn", "vtmx", "vsmx", "imx", "linx", "rmpct", "owner",
"set1", "set2", "vsref", "fcreg", "nreg", "mname"],
"data":[
["FACTS_DVCE_1", 153, 0, 1, 0.0, 0.0, 1.015, 50.0,100.0, 0.9263, 1.134,
1.0, 0.0, 0.05652, 100.0, 1, 0.0, 0.0, 0, 153, 0, ""],
...

["FACTS_DVCE_2", 153, 155, 1, 350.0, 40.0, 1.015, 25.0, 9999.0, 0.9,

1.1, 1.0, 0.0, 0.05, 100.0, 1, 0.0, 0.0, 0, 153, 0, ""]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to this FACTS device. Each FACTS
device must have a unique NAME. NAME may be up to twelve characters and
may contain any combination of blanks, uppercase letters, numbers and special
characters. NAME must be enclosed in single or double quotes if it contains any
blanks or special characters.

No default allowed
I ibus Sending end bus number, or extended bus name enclosed in single quotes (refer
to Extended Bus Names).

No default allowed
J jbus Terminal end bus number, or extended bus name enclosed in single quotes; 0 for
a STATCON.

J = 0 by default
MODE mode Controlmode:

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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
85
Power Flow Data File (RAW) FACTS Device Data

Field RAWX Key Description

• 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 Vd + jVq setpoint is modified during power flow
solutions to reflect the active power exchange determined by the master device

MODE = 1 by default
PDES pdes Desired active power flow arriving at the terminal end bus; entered in MW.

PDES = 0.0 by default

QDES qdes Desired reactive power flow arriving at the terminal end bus; entered in MVAR.

QDES = 0.0 by default

VSET vset Voltage setpoint at the sending end bus; entered in pu.

VSET = 1.0 by default

SHMX shmx Maximum shunt current at the sending end bus; entered in MVA at unity voltage.

SHMX = 9999.0 by default

TRMX trmx Maximum bridge active power transfer; entered in MW.

TRMX = 9999.0 by default

VTMN vtmn Minimum voltage at the terminal end bus; entered in pu.

VTMN = 0.9 by default

VTMX vtmx Maximum voltage at the terminal end bus; entered in pu.

VTMX = 1.1 by default

VSMX vsmx Maximum series voltage; entered in pu.

VSMX = 1.0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
86
Power Flow Data File (RAW) FACTS Device Data

Field RAWX Key Description

IMX imx Maximum series current, or zero for no series current limit; entered in MVA at
unity voltage.

IMX = 0.0 by default

LINX linx Reactance of the dummy series element used during power flow solutions; en-
tered in pu.

LINX = 0.05 by default

RMPCT pmpct 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 the shunt
element; RMPCT must be positive. RMPCT is needed only if there is more than one
local or remote setpoint mode voltage controlling device (plant, switched shunt,
FACTS device shunt element, or VSC dc line converter) controlling the voltage at
bus FCREG.

RMPCT = 100.0 by default

OWNER owner Owner number (1 through 9999).

OWNER = 1 by default
SET1, SET2 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 (Vd) and imaginary (Vq) 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 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
FCREG fcreg Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of the bus for which voltage is to be regulated by the shunt element
of this FACTS device to the value specified by VSET. If FCREG specifies a remote
bus (i.e., a bus other than bus I), bus FCREG must be a Type 1 or 2 bus (if it 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). FCREG may be 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.

FCREG = 0 by default
NREG nreg A node number of bus FCREG. The bus section of bus FCREG to which node NREG
is connected is the bus section for which voltage is to be regulated by the shunt
element to the value specified by VSET. If bus FCREG is not in a substation, NREG
must be specified as 0.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
87
Power Flow Data File (RAW) FACTS Device Notes

Field RAWX Key Description

NREG = 0 by default
MNAME 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
characters.

MNAME is blank by default

FACTS device data input is terminated with a record specifying a FACTS device number of zero.

1.26.1. FACTS Device Notes

PSSE's 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).

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 1.28 shows the PSSE 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 FACTS Devices, and AC Voltage Control for other topological restrictions and for details on the handling
of FACTS devices during the power flow solution activities.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
88
Power Flow Data File (RAW) Switched Shunt Data

Figure 1.28. FACTS Control Device Setpoints and Limits

1.27. Switched Shunt Data

Automatically switched shunt devices may be represented on a network bus.

Figure 1.29. Switched Shunt Configuration

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
89
Power Flow Data File (RAW) Switched Shunt Data

The switched shunt elements at a bus may consist entirely of blocks of shunt reactors (each Bi is a negative
quantity), entirely of blocks of capacitor banks (each Bi is a positive quantity), or of both reactors and capac-
itors.

Each network bus to be represented in PSSE with switched shunt admittance devices must have a switched
shunt data record specified for it. The switched shunts are represented with up to eight blocks of admittance,
each one of which consists of up to nine steps of the specified block admittance.

RAW Record Format (on a single line)

I, ID, MODSW, ADJM, STAT, VSWHI, VSWLO, SWREG, NREG, RMPCT, RMIDNT, BINIT, NAME,
S1, N1, B1, S2, N2, B2, ..., S8, N8, B8

RAWx Record Format

"swshunt":{
"fields":["ibus", "shntid", "modsw", "adjm", "stat", "vswhi", "vswlo",
"swreg", "nreg", "rmpct", "rmidnt", "binit", "name", "s1", "n1", "b1",
"s2", "n2", "b2", "s3", "n3", "b3", "s4", "n4", "b4", "s5", "n5",
"b5", "s6", "n6", "b6", "s7", "n7", "b7", "s8", "n8", "b8"],
"data":[
[152, "1 ", 1, 0, 1, 1.045, 0.955, 152, 0, 100.0, "", -233.00, "SVD1"
1, 1, -15.0, 1, 2, -5.0, 1, 3, -10.0, 1, 4, -8.0, 1, 5, -7.0, 1, 6,
-5.0, 1, 7, -7.0, 1, 8, -4.0],
...

[93002, "1 ", 1, 0, 1, 0.99628, 0.99628, 93002, 0, 100.0, "", 1.44,"SVD2"

1, 1, 1.44, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null, null, null, null, null, null,
null]
]
}

Field RAWX Key Description

I ibus Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names).

No default allowed
ID shntid One- or two-character uppercase non-blank alphanumeric switched shunt iden-
tifier used to distinguish among multiple switched shunts at bus I. It is recom-
mended that, at buses for which a single switched shunt is present, the switched
shunt be designated as having the switched shunt identifier '1'.

ID = '1' by default
MODSW modsw Control mode:

• 0 - locked

• 1 - discrete adjustment, controlling voltage locally or at bus SWREG

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
90
Power Flow Data File (RAW) Switched Shunt Data

Field RAWX Key Description

• 2 - continuous adjustment, controlling voltage locally or at bus SWREG

• 3 - discrete adjustment, controlling the reactive power output of the plant at

bus SWREG

• 4 - discrete adjustment, controlling the reactive power output of the VSC dc

line converter at bus SWREG of the VSC dc line for which the name is specified
as RMIDNT

• 5 - discrete adjustment, controlling the admittance setting of the switched

shunt at bus SWREG

• 6 - discrete adjustment, controlling the reactive power output of the shunt el-
ement of the FACTS device for which the name is specified as RMIDNT

MODSW = 1 by default
ADJM adjm Adjustment method:

• 0 - steps and blocks are switched on in input order, and off in reverse input or-
der; this adjustment method was the only method available prior to PSSE-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 stat Initial status for entire switched shunt. Status of one for in-service and zero for
out-of-service.

STAT = 1 by default
VSWHI 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 control-
ling device.

VSWHI is not used when MODSW is 0.

VSWHI = 1.0 by default

VSWLO 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 control-
ling device.

VSWLO is not used when MODSW is 0.

VSWLO = 1.0 by default

SWREG swreg Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of the bus for which voltage or connected equipment reactive power
output is controlled by this switched shunt.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
91
Power Flow Data File (RAW) Switched Shunt Data

Field RAWX Key Description

When MODSW is 1 or 2, SWREG specifies the bus for which voltage is regulated.
If SWREG specifies a remote bus (i.e., a bus other than bus I), bus SWREG must be
a Type 1 or 2 bus (if it is other than a Type 1 or 2 bus, the switched shunt controls
its own voltage). SWREG may be entered as 0 if the switched shunt is to regulate
its own voltage.

When MODSW is 3, SWREG specifies the Type 2 or 3 bus where plant reactive
power output is to be regulated by this switched shunt. Set SWREG to I if the
switched shunt and the plant that it controls are connected to the same bus.

When MODSW is 4, SWREG specifies the converter bus of a VSC dc line where
converter reactive power output is to be regulated by this switched shunt. Set
SWREG 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, SWREG specifies the remote bus to which the switched shunt
for which the admittance setting is to be regulated by this switched shunt is con-
nected.

SWREG is not used when MODSW is 0 or 6.

SWREG = 0 by default
NREG nreg A node number of bus SWREG. The bus section of bus SWREG to which node
NREG is connected is the bus section for which voltage or connected equipment
reactive power output is controlled by this switched shunt. If bus SWREG is not in
a substation, NREG must be specified as 0.

NREG = 0 by default
RMPCT 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 there is more than one local or remote setpoint mode
voltage controlling device (plant, switched shunt, FACTS device shunt element, or
VSC dc line converter) controlling the voltage at bus SWREG. Only used if MODSW
= 1 or 2.

RMPCT = 100.0 by default

RMIDNT rmindt When MODSW is 4, the name of the VSC dc line containing the converter bus that
is specified in SWREG. When MODSW is 5, the identifier of the switched shunt
connected to the bus that is specified in SWREG. When MODSW is 6, the name of
the FACTS device where the shunt element's reactive output is to be controlled.
RMIDNT is not used for other values of MODSW.

RMIDNT is a blank name by default

BINIT binit Initial switched shunt admittance; entered in Mvar at unity voltage.

BINIT = 0.0 by default

NAME name Alphanumeric identifier assigned to the switched shunt. NAME may be up to forty
characters and may contain any combination of blanks, uppercase letters, num-
bers and special characters. NAME must be enclosed in single or double quotes if
it contains any blanks or special characters.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
92
Power Flow Data File (RAW) Switched Shunt Notes

Field RAWX Key Description

NAME must be unique within all switched shunts.

NAME is blank by default

Si s1, s2, s3, Initial switched shunt status of one for in-service and zero for out-of-service for
s4, s5, s6, block i (1 through 8)
s7, s8
Si = 1 by default
Ni n1, n2, n3, Number of steps for block i (1 through 8). The first zero value of Ni or Bi is inter-
n4, n5, n6, preted as the end of the switched shunt blocks for bus I.
n7, n8
Ni = 0 by default
Bi b1, b2, b3, Admittance increment for each of Ni steps in block i; entered in Mvar at unity
b4 ,b5, b6, voltage.
b7, b8
Bi = 0.0 by default

Switched shunt data input in the RAW file is terminated with a record specifying a bus number of zero.

1.27.1. 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 Bi is a negative quantity) or
entirely of capacitor banks (each Bi 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 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 switched shunts have admittance ranges
substantially wider than this minimum permissible range.

When MODSW is 3, 4, 5 or 6, VSWLO and VSWHI define a restricted band of the controlled device's 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, SNiBi
- SNjBj when MODSW is 5 where i are those switched shunt blocks for which Bi is positive and j are those
for which Bi 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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
93
Power Flow Data File (RAW) Switched Shunt Example

The reactive power band for switched shunt control is calculated by applying VSWLO and VSWHI to the re-
active power band extremes of the controlled plant or VSC converter. For example, with MINQ of -50.0 pu
and MAXQ of +50.0 pu, if VSWLO is 0.2 pu and VSWHI is 0.75 pu, then the reactive power band defined by
VSWLO and VSWHI is:

-50.0 + 0.2*(50.0 - (-50.0)) = -50.0 + 0.2*100.0 = -50.0 + 20.0 = -30.0 Mvar

through:

-50.0 + 0.75*(50.0 - (-50.0)) = -50.0 + 0.75*100.0 = -50.0 + 75.0 = +25.0 Mvar

The switched shunt admittance is kept in the working case and reported in output tabulations separately
from the fixed bus shunt, which is entered on the fixed bus shunt data record (refer to Fixed Bus Shunt Data).

Refer to Section 6.3.15, Switched Shunt Devices and Section 6.3.17, DC Lines and Switched Shunt Adjust-
ment for details on the handling of switched shunts during power flow solutions.

It is required that the data record for a switched shunt for which the control mode is 5 (i.e., it controls
the setting of another switched shunt) be placed in the file after the data record for the switched shunt
that it controls. Otherwise, a warning message indicating that the controlled switched shunt is not found is
printed, and control of the switched shunt will not be implemented. It is recommended that data records for
switched shunts for which the control mode is 5 be grouped together following all other switched shunt data
records. This practice will eliminate the behavior described above simply because the controlled switched
shunt record has not as yet been read.

1.27.2. Switched Shunt Example

Figure 1.30 shows the data record that may be specified to match the combination of switched elements on
Bus 791. Note that the quantity shown as Load is entered as Load Data, and the fixed bus shunt indicated
as B SHUNT and G SHUNT is entered as Fixed Bus Shunt Data.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
94
Power Flow Data File (RAW) GNE Device Data

Figure 1.30. Example Data Record for Combination of Switched Shunts

1.28. GNE Device Data

PSSE accepts data for Generic Network Element (GNE) devices that are modeled in BOSL ".mac" or ".xmac"
files. Each instance of a GNE device to be represented in PSSE is specified in a GNE device data record block.

RAW Record Format

NAME, MODEL, NTERM, BUS1, ..., BUSNTERM, NREAL, NINTG, NCHAR

STATUS, OWNER, NMET

REAL1, ..., REALmin(10, NREAL)

INTG1, ..., INTGmin(10, NINTG)

CHAR1, ..., CHARmin(10, NCHAR)

RAWx Record Format

"gne":{
"fields":["name", "model", "nterm", "bus1", "bus2", "nreal", "nintg",
"nchar", "stat", "owner", "nmet", "real1", "real2", "real3",
"real4", "real5", "real6", "real7", "real8", "real9", "real10",
"intg1", "intg2", "intg3", "intg4", "intg5", "intg6", "intg7",
"intg8", "intg9", "intg10", "char1", "char2", "char3", "char4",
"char5", "char6", "char7", "char8", "char9", "char10"],

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
95
Power Flow Data File (RAW) GNE Device Data

"data":[
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to this GNE device. Each GNE de-
vice instance must have a unique NAME. NAME may be up to twelve characters
and may contain any combination of blanks, uppercase letters, numbers and spe-
cial characters. NAME must be enclosed in single or double quotes if it contains
any blanks or special characters.

No default allowed
MODEL model The name of the BOSL model. NAME is the root name of the ".mac" or ".xmac" file
containing the BOSL model.

No default allowed
NTERM nterm The number of buses to which this instance of the model is connected. NTERM
may be either 1 or 2 for a variable admittance model, and must be 1 for a variable
power model and a variable current model.

NTERM = 1 by default
BUSi bus1, bus2 Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names).

For RAWX, if the value of nterm is equal to 1, data for bus2 will be ignored (treated
as null).

No default allowed
NREAL nreal Number of floating point data items required by model MODEL. NREAL must be
identical to the number required by the ".mac" or ".xmac" file.

NREAL = 0 by default
NINTG nintg Number of buses required in calculating the inputs required by model MODEL.
NINTG must be identical to the number required by the ".mac" or .".xmac" file.

NINTG = 0 by default
NCHAR nchar Number of two-character identifiers (e.g., machine identifiers, circuit identifiers,
etc.) required in calculating the inputs required by model MODEL. NCHAR must
be identical to the number required by the ".mac" or ".xmac" file.

NINTG = 0 by default
STATUS stat Device status of one for in-service and zero for out-of-service.

STATUS = 1 by default
OWNER owner Owner to which the device is assigned (1 through 9999). By default, OWNER is
the owner to which BUS1 is assigned (refer to Bus Data).
NMET nmet Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of the non-metered end bus. NMET is used for GNE devices with
NTERM > 1.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
96
Power Flow Data File (RAW) Induction Machine Data

Field RAWX Key Description

NMET = BUSNTERM by default
REALI real1, real2, NREAL floating point data items required by model MODEL.
real3, real4,
real5, real6, Data items are entered 10 per line, with as many lines as required to supply NREAL
real7, real8, data items. If NREAL is 0, no record is specified.
real9, real10
REALI = 0.0 by default
INTG I intg1, intg2, NINTG bus numbers or extended bus names required by model MODEL. INTG I =
intg3, intg4, BUS1 by default.
intg5, intg6,
intg7, intg8, Data items are entered 10 per line, with as many lines as required to supply NINTG
intg9, data items. If NINTG is 0, no record is specified.
intg10
INTG I = BUS1 by default
CHARI char1, NCHAR two-character identifiers required by model MODEL.
char2,
char3, Data items are entered 10 per line, with as many lines as required to supply NCHAR
char4, data items. If NCHAR is 0, no record is specified.
char5,
char6, CHARI = '1' by default
char7,
char8,
char9,
char10

GNE device data input is terminated with a record specifying a blank GNE device name or a GNE device name
of '0'.

GNE devices are not recognized in all forms of analysis available in PSS®E. For example, they are ignored
in the fault analysis activities. Those analysis functions from which they are excluded print an appropriate
message if any in-service GNE devices are present in the working case.

1.29. Induction Machine Data

Each network bus at which an induction machine is to be represented must be specified in at least one
induction machine data record. Multiple induction machines may be represented at a bus by specifying more
than one induction machine data record for the bus, each with a different machine identifier.

RAW Record Format (on a single line)

I, ID, STATUS, SCODE, DCODE, AREA, ZONE, OWNER, NAME, TCODE, BCODE, MBASE,
RATEKV, PCODE, PSET, H, A, B, D, E, RA, XA, XM, R1, X1, R2, X2, X3, E1, SE1,
E2, SE2, IA1, IA2, XAMULT

RAWx Record Format

"indmach":{
"fields":["ibus", "imid", "stat", "sc", "dc", "area", "zone", "owner",
"name", "tc", "bc", "mbase", "ratekv", "pcode", "pset", "hconst",

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
97
Power Flow Data File (RAW) Induction Machine Data

"aconst", "bconst", "dconst", "econst", "ra", "xa", "xm",

"r1", "x1", "r2", "x2", "x3", "e1", "se1", "e2", "se2", "ia1",
"ia2", "xamult"],
"data":[
[3010, "1", 1, 1, 2, 5, 4, 5, "", 1, 1, 1.0, 21.6, 1, 1.0, 1.0, 1.0, 1.0,
1.0, 1.0, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null],
...

[93002, "1 ", 1, 1, 2, 5, 6, 5, "", 1, 2, 5.62, 0.69, 2, -5.0, 1.00, 1.0,

1.0, -1.0, 1.0, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null]
]
}

Field RAWX Key Description

I ibus Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names).

No default allowed
ID imid One- or two-character uppercase non-blank alphanumeric machine identifier
used to distinguish among multiple induction machines at bus I. It is recommend-
ed that, at buses for which a single induction machine is present, it be designated
as having the machine identifier '1'.

ID = '1' by default
STATUS stat Machine status of 1 for in-service and 0 for out-of-service.

STATUS = 1 by default
SCODE scode Machine standard code:

• 1 - for NEMA

• 2 - for IEC

SCODE = 1 by default
DCODE dcode Machine design code. Following are allowed machine design codes:

• 0 - for Custom design with equivalent circuit reactances specified

• 1 - for NEMA Design A

• 2 - for NEMA Design B / IEC Design N

• 3 - for NEMA Design C / IEC Design H

• 4 - for NEMA Design D

• 5 - for NEMA Design E

DCODE = 2 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
98
Power Flow Data File (RAW) Induction Machine Data

Field RAWX Key Description

AREA area Area to which the induction machine is assigned (1 through 9999). By default,
AREA is the area to which bus I is assigned (refer to Bus Data).
ZONE zone Zone to which the induction machine is assigned (1 through 9999). By default,
ZONE is the zone to which bus I is assigned (refer to Bus Data).
OWNER owner Owner to which the induction machine is assigned (1 through 9999). By default,
OWNER is the owner to which bus I is assigned (refer to Bus Data).
NAME name Alphanumeric identifier assigned to the induction machine. NAME may be up
to forty characters and may contain any combination of blanks, uppercase let-
ters, numbers and special characters. NAME must be enclosed in single or double
quotes if it contains any blanks or special characters.

NAME must be unique within all induction machines.

NAME is blank by default

TCODE tcode Type of mechanical load torque variation:

• 1 - for the simple power law

• 2 - for the WECC model

TCODE = 1 by default
BCODE bcode Machine base power code:

• 1 - for 1 for mechanical power (MW) output of the machine

• 2 - for apparent electrical power (MVA) drawn by the machine

BCODE = 1 by default
MBASE mbase Machine base power; entered in MW or MVA. This value is specified according to
BCODE, and could be either the mechanical rating of the machine or the electrical
input. It is necessary only that the per unit values entered for the equivalent circuit
parameters match the base power.

MBASE = system base MVA by default

RATEKV ratekv Machine rated voltage; entered in kV line-to-line, or zero to indicate that machine
rated voltage is assumed to be identical to the base voltage of bus I.

RATEKV = 0.0 by default

PCODE pcode Scheduled power code:

• 1 - for mechanical power (MW) output of the machine

• 2 - for electrical real power (MW) drawn by the machine

PCODE = 1 by default
PSET pset Scheduled active power for a terminal voltage at the machine of 1.0 pu of the
machine rated voltage; entered in MW. This value is specified according to PCODE,
and is either the mechanical power output of the machine or the real electrical
power drawn by the machine. The sign convention used is that PSET specifies
power supplied to the machine:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
99
Power Flow Data File (RAW) Induction Machine Data

Field RAWX Key Description

A positive value of electrical power means that the machine is operating as a mo-
tor; similarly, a positive value of mechanical power output means that the ma-
chine is driving a mechanical load and operating as a motor.

No default allowed.
H hconst Machine inertia; entered in per unit on MBASE base.

H = 1.0 by default
A, B, D, E aconst, Constants that describe the variation of the torque of the mechanical load with
bconst, speed. If TCODE is 1 (simple power law model), only D is used; if TCODE is 2 (WECC
cconst, model), all of these constants are used.
dconst
A = B = D = E = 1.0 by default.
RA ra Armature resistance, Ra (> 0.0); entered in per unit on the power base MBASE and
voltage base RATEKV.

RA = 0.0 by default
XA xa Armature leakage reactance, Xa (> 0.0); entered in per unit on the power base
MBASE and voltage base RATEKV.

XA = 0.0 by default
XM xm Unsaturated magnetizing reactance, Xm (> 0.0); entered in per unit on the power
base MBASE and voltage base RATEKV.

XM = 2.5 by default
R1 r1 Resistance of the first rotor winding ("cage"), r1 (> 0.0); entered in per unit on the
power base MBASE and voltage base RATEKV.

R1 = 999.0 by default
X1 x1 Reactance of the first rotor winding ("cage"), X1 (>0.0); entered in per unit on the
power base MBASE and voltage base RATEKV.

X1 = 999.0 by default
R2 r2 Resistance of the second rotor winding ("cage"), r2 (> 0.0); entered in per unit on
the power base MBASE and voltage base RATEKV.

R2 = 999.0 by default
X2 x2 Reactance of the second rotor winding ("cage"), X2 (>0.0); entered in per unit on
the power base MBASE and voltage base RATEKV.

X2 = 999.0 by default
X3 x3 Third rotor reactance, X3 (> 0.0); entered in per unit on the power base MBASE
and voltage base RATEKV.

X3 = 0.0 by default
E1 e1 First terminal voltage point from the open circuit saturation curve, E1 (> 0.0);
entered in per unit on RATEKV base.

E1 = 1.0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
100
Power Flow Data File (RAW) Machine Electrical Data

Field RAWX Key Description

SE1 se1 Saturation factor at terminal voltage E1, S(E1).

SE1 = 0.0 by default

E2 e2 Second terminal voltage point from the open circuit saturation curve, E2 (> 0.0);
entered in per unit on RATEKV base.

E2 = 1.2 by default
SE2 se2 Saturation factor at terminal voltage E2, S(E2).

SE2 = 0.0 by default

IA1, IA2 ia1, ia2 Stator currents in PU specifying saturation of the stator leakage reactance, XA.

IA1 =IA2 = 0.0 by default

XAMULT xamult Multiplier for the saturated value. Allowed value 0 to 1.0.

XAMULT = 1.0 by default

Induction machine data input in the RAW file is terminated with a record specifying a bus number of zero.

1.29.1. Machine Electrical Data

The positive sequence steady state equivalent circuit for the induction machine is shown in Figure 1.31

Figure 1.31. Induction Machine Equivalent Circuit

The machine model is described by eight electrical elements: three resistive and five inductive. Values are
specified in per unit on the base power, MBASE, and rated voltage, RATEKV, which are also specified on the
data record.

The left side of the circuit is the machine armature: ra is the armature resistance and Xa is the armature leak-
age reactance. The armature and the rotor are linked through the magnetizing reactance X m; the unsaturated
value of the mutual reactance is specified.

The rotor is described by two parallel resistance and reactance branches, r1, X1 and r2, X2, that represent the
"cages" or windings in the rotor. To model a single cage machine, the resistance and reactance of the second

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
101
Power Flow Data File (RAW) Load Mechanical Data

of these parallel branches must both be specified as 999.0; i.e., to model a single cage machine, specify r2
= X2 = 999.0 on the data record.

The reactance X3 is included to allow a more general model.

The mutual reactance Xm saturates. The saturation curve is for the induction machine operating with no load.
Two points on the saturation curve must be specified. These are normally chosen such that E1 is near the
"knee" of the saturation curve and E2 is near its ceiling. Saturation is neglected if E1 * S(E1) = 0.0; therefore,
to neglect saturation, specify either E1 or SE1 as 0.0.

If a non-zero machine design code (DCODE) value is specified, all data items from RA to the end of the record
are ignored, and pre-programmed machine electrical and saturation data values are assigned to the machine.
If you wish to modify any of these data items after they have been assigned, you may change the machine
design code to 0 (custom).

1.29.2. Load Mechanical Data

Five data items (TCODE, A, B, D and E) are used to describe how the torque of the mechanical load varies with
speed. When TCODE is 1, a simple power law is applied that uses the constant specified as D. The equation is

where Tload0 is the load torque and S0 is the slip at a terminal voltage of 1.0 pu.

The WECC model applies the following equations:

2 E
Tload = Tload0 [A(1-s) +B(1-s)+D(1-s) +C 0] WECC Model
2 E
C0=1-A(1-s0) -B(1-s0)+D(1-s 0)

1.30. Load Type Data

The load type defines the name of load types and the comment information of each load type.

RAW Record Format

NAME, DESC

RAWx Record Format

"loadtype":{
"fields":["name" "desc"],
"data":[
["A", "industry load"]
]
}

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
102
Power Flow Data File (RAW) Load Type Data Notes

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to this load type. Each load type
must have a unique NAME of up to 40 characters.

No default allowed.
DESC desc The description string contains the information of the load type.

blank by default

The load type data input is terminated with a record specifying a bus number of zero.

1.30.1. Load Type Data Notes

Multiple loads can be assigned to a load type. The loads can be returned by load type with subsystem retrieval
APIs.

1.31. Interface Data

The Interface defines the interface name and ratings, MW or MVAr summation flow to be calculated and
monitored.

RAW Record Format

NAME, INUM, TYPE, RATMAX1, RATMAX2, RATMAX3, RATMAX4, RATMAX5, RATMAX6, RATMAX7,
RATMAX8, RATMAX9, RATMAX10, RATMAX11, RATMAX12, RATMIN1, RATMIN2, RATMIN3, RAT-
MIN4, RATMIN5, RATMIN6, RATMIN7, RATMIN8, RATMIN9, RATMIN10, RATMIN11, RATMIN12

RAWx Record Format

"interface":{
"fields":["name","inum","type",
"ratmax1", "ratmax2", "ratmax3", "ratmax4", "ratmax5", "ratmax6",
"ratmax7", "ratmax8", "ratmax9", "ratmax10","ratmax11","ratmax12",
"ratmin1", "ratmin2", "ratmin3", "ratmin4", "ratmin5", "ratmin6",
"ratmin7", "ratmin8", "ratmin9", "ratmin10","ratmin11","ratmin12"],
"data":[
["TEST",1,1,1000,1000, 1000,1000, 1000,1000, 1000,1000, 1000,1000,
1000,1000,0,0,0, 0,0,0, 0,0,0, 0,0,0]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to the interface. Each interface
must have a unique Name, NAME may be up to 40 characters and may contain
any combination of blanks, uppercase letters, numbers and special characters.
NAME must be enclosed in single or double quotes if it contains any blanks or
special characters. no default allowed.

No default allowed.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
103
Power Flow Data File (RAW) Interface Element Data

Field RAWX Key Description

INUM inum Interface number (1 through 999999). Each interface must have a unique NUM-
BER.

By default, program assigns the next available number when inum is not provided.
TYPE type Type defines which flow component (MW and MVAr) of the interface flow model
is calculated and monitored.

Flow type:

• 1 - MW

• 2 - MVAr

By default, flow type is 1. The quantities for ratings of interface are entered by
TYPE.
RATEMAXn/ ratemaxn/ Each Interface has 12 pairs of limits (max/min) which are specified in physical
RATEMINn rateminn units by TYPE. The MW or MVAr flows on the interface defined by TYPE are
checked against the limits. When TYPE is MW, the ratings are defined in MW; when
TYPE is MVAr, the ratings are defined in MVAr. for example: RATEMAX1/RATEMIN1

By default, RATEMAXn=9999.0, RATEMINn=-9999.0.

The interface data input is terminated with a record specifying zero.

1.32. Interface Element Data

An interface can include multiple interface elements, the MW or MVAr flow of the interface is the sum of
MW or MVAr flows on all in-service interface elements. The amount and direction of MW or MVAr flows on
interface elements are determined by their direction, weight factor and working case condition.

RAW Record Format

NAME, TYPE, INUM, JNUM, KNUM, NAMID, DIRCTN, IMET, WEIGHT

RAWx Record Format

"itfelmt":{
"fields":["name", "type", "inum", "jnum", "knum", "namid",
"dirctn", "imet", "weight"],
"data":[
["TEST",1,101,102,0, "1", 1, 1, 1.0]
]
}

Field RAWX Key Description

NAME name The alphanumeric name of the interface which the element belongs to.

No default allowed.
TYPE type The interface element can be one of ten element types:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
104
Power Flow Data File (RAW) Interface Element Data

Field RAWX Key Description

• 1-branch, two winding transformer, multi-section line

• 2-three winding transformer

• 3-load

• 4-generator

• 5-DC line

• 6-VSCDC line

• 7-area

• 8-area tie and load

• 9-zone

• 10-zone tie and load

No default allowed.
INUM inum bus number or extended bus name enclosed in single quotes or area number or
zone number

When TYPE is 1, from bus of the branch, two-winding transformer or the multiple
section line.

When TYPE is 2, from bus number of three winding transformer.

When TYPE is 3, load bus number.

When TYPE is 4, generator bus number.

When TYPE is 5, from AC bus number of DC line.

When TYPE is 6, from AC bus number of VSC DC line.

When TYPE is 7 or 8, from area number.

When TYPE is 9 or 10, from zone number.

No default allowed.
JNUM jnum bus number or , or extended bus name enclosed in single quotes, or area number,
or zone number.

When TYPE is 1, to bus number of the branch, tow-winding transformer, or the

multiple section.

When TYPE is 2, to bus number of three winding transformer.

When TYPE is 5, to AC bus number of DC line.

When TYPE is 6, to AC bus number of VSC DC line.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
105
Power Flow Data File (RAW) Interface Element Data

Field RAWX Key Description

When TYPE is 7 or 8, to area number.

When TYPE is 9 or 10, to zone number.

It is zero for other types.

JNUM is zero by default.

KNUM knum bus number or extended bus name enclosed in single quotes. When type is 2, the
last bus number of three-winding transformer. It is zero for other types.

KNUM is zero by default.

NAMID namid The device name or device ID of the element defined by TYPE.

When TYPE is 1, One- or two-character uppercase non-blank alphanumeric iden-

tifier of branch, two-winding transformer, multiple section line.

When TYPE is 2, One- or two-character uppercase non-blank alphanumeric iden-

tifier of a three-winding transformer.

When TYPE is 3, One- or two-character uppercase non-blank alphanumeric iden-

tifier of a load.

When TYPE is 4, One- or two-character uppercase non-blank alphanumeric iden-

tifier of a machine.

When TYPE is 5, Twelve-character uppercase non-blank alphanumeric identifier

(name) of a two-terminal DC line.

When TYPE is 6, Twelve-character uppercase non-blank alphanumeric identifier

(name) of a VSC DC line.

When TYPE is 7,8,9 or 10, it is blank.

NAMID is blank by default.

DIRCTN dirctn Direction defines the positive flow direction of the element:

• 1-from 'from bus'

• 2-to 'from bus'

When DIRCTN is 1 and the TYPE is 1, 2, 5 or 6, the flow on the specified branch/
three-winding transformer/DC line/VSC DC line is positive in the interface flow
summation when flowing out of the from bus I.

When DIRCTN is 1 and the TYPE is 3, the load consumption is positive.

When DIRCTN is 1 and the TYPE is 4, the generation output is positive.

When DIRCTN 1 and the TYPE is 7,8,9 or 10, the flow on the tie lines is positive in
the interface flow summation when flowing out of the bus in AREA I.

DIRCTN is 1 by default.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
106
Power Flow Data File (RAW) Substation Data Group

Field RAWX Key Description

IMET imet Metered bus end of the interface element:

• 0 - existing bus end

• 1 - from bus end

• 2 - not from bus end

For TYPE 1 element, when IMET is 0, the MW or MVAr flow is taken at the metered
bus defined in power flow case; when IMET is 1, the flow is taken at bus I; when
IMET is 2, the flow is taken at bus J.

For TYPE 2 element, when IMET is 0, the MW or MVAr flow is taken at the metered
bus defined in power flow case; when IMET is 1, the flow is taken at bus I; when
IMET is 2, the bus I is non-metered and flow is taken at both bus J and bus K.

For TYPE 5 elements, when IMET is 0, the MW or MVAr flow is taken at the metered
bus defined in power flow case; when IMET is 1, the flow is taken at bus I; when
IMET is 2, the flow is taken at bus J.

For TYPE 6 elements, when IMET is 0 or 1, the MW or MVAr flow is taken at bus
I; when IMET is 2, the flow is taken at bus J.

For TYPE 7,8,9 or 10 element, when IMET is 0, the MW or MVAr flow on a tie line
is taken at the metered bus of the line defined in power flow case; when IMET
is 1, the flow is taken at bus end in the area/zone I; when IMET is 2, the flow is
taken at bus end in the area/zone J.

IMET is 0 by default.
WEIGHT weight The weight factor of flow counted in the interface flow summation. It is from 0
to 1.0.

WEIGHT is 1.0 by default.

The interface element data input is terminated with a record specifying zero.

1.33. Substation Data Group

Each substation to be represented in PSS®E is introduced by reading a substation data record block. Each
substation block consists of:

• A substation data record

• Several node data records

• Several substation switching device data records

• Several equipment terminal data records

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
107
Power Flow Data File (RAW) Substation Data

1.33.1. Substation Data

The first record in each substation block is a substation data record. Exactly one such record is specified in
each substation block.

RAW Format

IS, NAME, LATI, LONG, SGR

RAWx Record Format

"sub":{
"fields":["isub", "name", "lati", "long", "srg"],
"data":[
[1, "SS01_NILE_TYP_3_DBDB", 34.61, -86.67, 0.1100],
...
[18, "SS18_PILCOMAYO_TYP_2_RB", 31.42, -81.02, 0.2900]
]
}

IS Substation number (1 through 99999).

No default allowed
NAME Substation name, NAME may be up to forty characters and may contain any combi-
nation of blanks, uppercase letters, numbers and special characters. NAME must be
enclosed in single or double quotes if it contains any blanks or special characters.

NAME is forty blanks by default

LATI Substation latitude in degrees (-90.0 to 90.0).

It is positive for North and negative for South, 0.0 by default

LONG Substation longitude in degrees. (-180.0 to 180.0).

It is positive for East and negative for West, 0.0 by default

SRG Substation grounding DC resistance in ohms.

Substation grounding DC resistance in ohms 0.1 ohms by default

Substation data input is terminated with a record specifying a substation number of zero.

1.33.2. Node Data

The substation data record is followed by substation node data. Each node in the substation is specified in
a node data record.

RAW Format

NI, NAME, I, STATUS, VM, VA

RAWx Record Format

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
108
Power Flow Data File (RAW) Node Data

"subnode":{
"fields":["isub", "inode", "name", "ibus", "stat", "vm", "va"],
"data":[
[1, 1, "SS_NILE_NODE_1", 101, 1, null, null],
...
[18, 2, "SS_PILCOMAYO_NODE_2", 3009, 1, null, null]
]
}

NI Node number (1 through 999).

No default allowed
NAME Node name, NAME may be up to 40 characters and may contain any combination of
blanks, uppercase letters, numbers and special characters. NAME must be enclosed in
single or double quotes if it contains any blanks or special characters.

Node names must be unique within the substation.

NAME is set to a combination of the station name and node number by default
I Electrical Bus number (1 through 999997) in bus branch model. The electrical bus
represents this node NI and others that are connected by closed switching devices.

No default allowed
STATUS Node status. One for in-service and zero for out-of-service.

STATUS = 1 by default
VM Node voltage magnitude; entered in pu.

VM = 1.0 by default
VA Node voltage phase angle; entered in degrees.

VA = 0.0 by default

Node data input for this substation is terminated with a record specifying a node number of zero.

Node Data Notes

VM and VA need to be set to their actual solved case values only under the following conditions:

• The network, as entered into the working case via activity READ, is to be considered solved as read in

• Substation bus “I” is represented in the bus branch model by multiple bus sections

The voltage of each bus representing one of the bus sections is set to the node voltage corresponding to the
bus section number (e.g., if bus 154 is represented by the bus sections154-1 and 154-4, the voltage at bus
154-1 is set to the voltage specified for node 1 and the voltage at bus 154-4 is set to the voltage specified
for node 4).

Otherwise, unless some better estimate of the solved voltage and/or phase angle is available, VM and VA
may be omitted. In this case, the voltage at each of the bus sections is set to the voltage specified for bus “I”.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
109
Power Flow Data File (RAW) Station Switching Device Data

1.33.3. Station Switching Device Data

The node data records are followed by substation switching device data. Each station switching device in the
substation is specified in a station switching device data record.

RAW Format

NI, NJ, CKT, NAME, TYPE, STATUS, NSTAT, X, RSETNAM

RAWx Record Format

"subswd":{
"fields":["isub", "inode", "jnode", "swdid", "name", "type", "stat",
"nstat", "xpu", "rsetnam"],
"data":[
[ 1, 1, 3, "1", "BREAKER_0103", 2, 1, 1, 0.0001, "BRK-MDL-123"],
...
[18, 1, 2, "1", "DISCONNECT_0102", 3, 1, 1, 0.0001, "DSW-MDL-456"]
]
}

NI From node number (1 through 999). The from node must be in the sub- station IS.

No default allowed
NJ To node number (1 through 999). The to node must be in the substation IS.

No default allowed
CKT Two-character uppercase non-blank alphanumeric switching device identifier.

CKT = '1' by default

NAME Switching device name, NAME may be up to 40-characters and may contain any com-
bination of blanks, uppercase letters, numbers and special characters. NAME must be
enclosed in single or double quotes if it contains any blanks or special characters.

Substation switching device names that are not blank must be unique within the sub-
station.

Name is blank by default.

TYPE Switching device type whose ratings are specified.

1 - Generic connector

2 - Circuit breaker

3 - Disconnect switch

TYPE=1 by default.
STATUS Switching device status

0 - Open

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
110
Power Flow Data File (RAW) Equipment Terminal Data

1 - Closed

2 - Stuck closed

STATUS = 1 by default
NSTAT Switching device normal status

0 - Open

1 - Closed

2 - Stuck closed

NSTAT = 1 by default
X Switching device reactance; entered in pu. A non-zero value of X must be entered for
each switching device. The value X is used only in loop flow calculations.

X = 0.0001 by default
RSETNAM Previously defined rating set Switching Device Rating Table name.

RSETNAM is blank by default.

Station switching device data input for this substation is terminated with a record specifying a from node
number of zero.

1.33.4. Equipment Terminal Data

The substation switching device data records are followed by equipment terminal data. Equipment items
that are connected to substation buses are specified in equipment terminal data records. The following para-
graphs describe the record formats of the various types of terminal equipment that may be specified. Within
the set equipment terminal data records specified for a substation, records maybe specified in any order.

Equipment terminal data input for this substation in the RAW file is terminated with a record specifying a
bus number of zero.

RAWX Data Table Format for Equipment Terminal Data

Unlike RAW, all terminal data have a common format in RAWX regardless of terminal device type. This has
the form:

RAWx Record Format

"subterm":{
"fields":["isub", "inode", "type", "eqid", "ibus", "jbus", "kbus"],
"data":[
[1, 25, "L", "SC", 201, null, null], // Load
[1, 16, "F", "F1", 151, null, null], // Shunt
[1, 4, "M", "1 ", 101, null, null], // Machine
[1, 11, "B", "1 ", 151, 152, null], // AC Line
[1, 14, "2", "T1", 151, 101, null], // 2-winding
[5, 49, "3", "3 ", 208, 205, 215 ], // 3-winding

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
111
Power Flow Data File (RAW) Equipment Terminal Data

[7, 19, "S", "1 ", 93002, null, null], // Sw Shunt

[7, 18, "I", "1 ", 93002, null, null], // Ind Mach
[2, 30, "D", "TWO_TERM_DC1", 3021, null, null], // 2-Term DC
[4, 17, "V", "VDCLINE2 ", 203, null, null], // VSC DC
[12, 3, "N", "MULTERM_DC_1", 212, null, null], // N-Term DC
[2, 19, "A", "FACTS_DVCE_1", 153, null, null] // FACTS
]
}

Where the following terminal device type codes and required field apply for each terminal type:

Terminal Type Type Code Required Fields in RAWX Record

Load "L" isub, inode, type, eqid, ibus
Fixed Shunt "F" isub, inode, type, eqid, ibus
Machine "M" isub, inode, type, eqid, ibus
AC Line or Two-wind- "B" or "2" isub, inode, type, eqid, ibus, jbus
ing Transformer
Three-winding Trans- "3" isub, inode, type, eqid, ibus, jbus, kbus
former
Switched Shunt "S" isub, inode, type, eqid, ibus
Induction Machine "I" isub, inode, type, eqid, ibus
Two-terminal DC Line "D" isub, inode, type, eqid (as 12 character name), ibus
VSC DC Line "V" isub, inode, type, eqid (as 12 character name), ibus
Multi-terminal DC "N" isub, inode, type, eqid (as 12 character name), ibus
Line
FACTS Device "A" isub, inode, type, eqid (as 12 character name), ibus

Load Terminal Data

Each load terminal data record has the following format in RAW:

I, NI, 'L', ID

I Bus number.

No default allowed
NI Node number (1 through 999). If the electrical bus has node breaker model, in other
words it represents a set of nodes in a substation, the node must be one node in the
set and indicates the connections of the load within the substation. If the electrical
bus has no node breaker model, it is zero.

No default allowed
L Single character 'L' to indicate the record contains terminal information for a Load.
ID One or two-character uppercase non-blank alphanumeric load identifier used to dis-
tinguish 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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
112
Power Flow Data File (RAW) Equipment Terminal Data

Fixed Shunt Terminal Data

Each fixed shunt terminal data record has the following format:

I, NI, 'F', ID
I Bus number.

No default allowed
NI Node number (1 through 999). If the electrical bus has node breaker model, in other
words it represents a set of nodes in a substation, the node must be one node in the
set and indicates the connections of the shunt within the substation. If the electrical
bus has no node breaker model, it is zero.

No default allowed
F Single character 'F' to indicate the record contains terminal information for a Fixed
Shunt.
ID One or two-character uppercase non-blank alphanumeric fixed shunt identifier used
to distinguish among multiple fixed shunts at bus I. It is recommended that, at buses
for which a single fixed shunt is present, the fixed shunt be designated as having the
fixed shunt identifier '1'.

ID = '1' by default

Machine Terminal Data

Each machine terminal data record has the following format in RAW:

I, NI, 'M', ID
I Bus number.

No default allowed
NI Node number (1 through 999). If the electrical bus has node breaker model, in other
words it represents a set of nodes in a substation, the node must be one node in the set
and indicates the connections of the machine within the substation. If the electrical
bus has no node breaker model, it is zero.

No default allowed
M Single character 'M' to indicate the record contains terminal information for a Machine.
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

Branch and two winding Transformer Terminal Data

Each non-transformer branch and two-winding transformer terminal data record has the following format
in RAW:

I, NI, 'B', J, CKT

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
113
Power Flow Data File (RAW) Equipment Terminal Data

or

I, NI, '2', J, CKT

I From bus number.

No default allowed
NI From node number (1 through 999). If the electrical from bus has node breaker model,
in other words it represents a set of nodes in a substation, the from node must be one
node in the set and indicates the connections of branch within the substation. If the
electrical from bus has no node breaker model, it is zero.

No default allowed
'B' or 2 Specifies that the record contains terminal information for a non-transformer or two-
winding transformer.
J To bus number.

No default allowed
CKT One or two-character uppercase non-blank alphanumeric switching device identifier.

CKT = '1' by default

Three winding Transformer Terminal Data

Each three winding transformer terminal data record has the following format in RAW:

I, NI, '3', J, K, CKT

I From bus number.

No default allowed
NI From node number (1 through 999). If the electrical from bus I has node breaker mod-
el, in other words it represents a set of nodes in a substation, the from node must be
one node in the set and indicates the connections of branch within the substation. If
the electrical from bus has no node breaker model, it is zero.

No default allowed
3 Single character ‘3’ to indicate the record contains terminal information for a three-
winding transformer.
J To bus number.

No default allowed
K To bus number.

No default allowed
CKT One or two-character uppercase non-blank alphanumeric switching device identifier.

CKT = '1' by default

Switched Shunt Terminal Data

Each switched shunt terminal data record has the following format in RAW:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
114
Power Flow Data File (RAW) Equipment Terminal Data

I, NI, 'S', ID

I Bus number.

No default allowed
NI Node number (1 through 999). If the electrical bus has node breaker model, in other
words it represents a set of nodes in a substation, the node must be one in the set and
indicates the connections of the switched shunt within the substation. If the electrical
bus has no node breaker model, it is zero.

No default allowed
S Single character ‘S’ to indicate the record contains terminal information for a switched
shunt.
ID One or two-character uppercase non-blank alphanumeric switched shunt identifier
used to distinguish among multiple switched shunts at bus I. It is recommended that,
at buses for which a single switched shunt is present, the switched shunt be designat-
ed as having the switched shunt identifier '1'.

ID = '1' by default

Induction Machine Terminal Data

Each induction machine terminal data record has the following format in RAW:

I, NI, 'I', ID

I Bus number.

No default allowed
NI Node number (1 through 999). Must be one of the nodes of the bus within the sub-
station to which the induction machine is to be connected to. If the bus has no node
breaker model, it is zero.

No default allowed
I Single character ‘I’ to indicate the record contains terminal information for an induction
machine.
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

Two-terminal DC Line Terminal Data

Each two-terminal DC line terminal data record has the following format in RAW:

I, NI, 'D', NAME

I Rectifier or Inverter converter bus number.

No default allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
115
Power Flow Data File (RAW) Equipment Terminal Data

NI Node number (1 through 999). Must be one of the nodes of the bus within the sub-
station to which one end of the two-terminal dc line is to be connected to. If the elec-
trical bus has no node breaker model, it is zero.

No default allowed
D Single character ‘D’ to indicate that the record contains terminal information for a two-
terminal dc line connection.
NAME The non-blank alphanumeric identifier of the two-terminal dc line.

No default allowed

Voltage Source Converter (VSC) DC Line Terminal Data

Each VSC DC line terminal data record has the following format in RAW:

I, NI, 'V', NAME

I Converter bus number.

No default allowed
NI Node number (1 through 999). Must be one of the nodes of a converter bus within a
substation to which one end of the VSC dc line is to be connected to. If the bus has
no node breaker model, it is zero.

No default allowed
V Single character ‘V’ to indicate that the record contains terminal information for a VSC
dc line connection.
NAME The non-blank alphanumeric identifier of the VSC dc line.

No default allowed

Multi-terminal DC Line Terminal Data

Each multi-terminal DC line terminal data record has the following format in RAW:

I, NI, 'N', NAME

I AC converter station bus number.

No default allowed
NI Node number (1 through 999). Must be one of the nodes of the ac converter station
bus within the substation to which the multi-terminal dc line is to be connected to. If
the bus has no node breaker model, it is zero.

No default allowed
N Single character ‘N’ to indicate that the record contains terminal information for a mul-
ti-terminal dc line connection.
NAME The non-blank alphanumeric identifier of the multi-terminal dc line.

No default allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
116
Power Flow Data File (RAW) End of Data Indicator

FACTS Device Terminal Data

Each FACTS device terminal data record has the following format in RAW:

I, NI, 'A', NAME

I Sending or terminal end bus number of the FACTS device.

No default allowed
NI Node number (1 through 999). Must be one of the nodes of the ac converter station
bus within the substation to which the FACTS device is to be connected to. If the bus
has no node breaker model, it is zero.

No default allowed
A Single character ‘A’ to indicate that the record contains terminal information for a FAC-
TS device connection.
NAME The non-blank alphanumeric identifier of the FACTS device.

No default allowed

1.34. End of Data Indicator

It is good practice to end the Power Flow Raw Data File with a Q Record. Then, if new data categories are
®
introduced in a point release of PSS E, no modification of the file is required.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
117
 Chapter 2
Power Flow RAW Format Change Summary
This chapter provides summary of power flow data changes from PSSE version 33 and later versions.

1. Case Identification Data

PSSE33 IC, SBASE, REV, XFRRAT, NXFRAT, BASFRQ

TITLE1

TITLE2
PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

2. System-Wide Data

PSSE33 did not exist

PSSE34 GENERAL, THRSHZ=0.0001, PQBRAK=0.7, BLOWUP=5.0

GAUSS, ITMX=100, ACCP=1.6, ACCQ=1.6, ACCM=1.0, TOL=0.0001

NEWTON, ITMXN=20, ACCN=1.0, TOLN=0.1, VCTOLQ=0.1, VCTOLV=0.00001,

DVLIM=0.99, NDVFCT=0.99

ADJUST, ADJTHR=0.005, ACCTAP=1.0, TAPLIM=0.05, SWVBND=100.0,

MXTPSS=99, MXSWIM=10

TYSL, ITMXTY=20, ACCTY=1.0, TOLTY=0.00001

SOLVER, FNSL, ACTAPS=1, AREAIN=0, PHSHFT=0, DCTAPS=1, SWSHNT=1,

FLATST=0, VARLIM=0, NONDIV=0

RATING, N, NAME, DESC

PSSE35 GENERAL, GENERAL, THRSHZ=0.0001, PQBRAK=0.7, BLOWUP=5.0, MAXISOL-
LVLS=4, CAMAXREPTSLN=20, CHKDUPCNTLBL=0

GAUSS, same as previous version

NEWTON, same as previous version

ADJUST, same as previous version

TYSL, same as previous version

SOLVER, same as previous version

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
118
Power Flow RAW Format Change Sum-
mary

RATING, same as previous version

PSSE36 GENERAL, same as previous version

GAUSS, same as previous version

NEWTON, same as previous version

ADJUST, same as previous version

TYSL, same as previous version

SOLVER, same as previous version

RATING, same as previous version

SWDRATNAM, RN, RNAM, RTYP, UNIT, DESC

3. Bus Data

PSSE33 I, NAME, BASKV, IDE, AREA, ZONE, OWNER, VM, VA, NVHI, NVLO, EVHI, EVLO
PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

4. Load Data

PSSE33 I, ID, STATUS, AREA, ZONE, PL, QL, IP, IQ, YP, YQ, OWNER, SCALE, INTRPT
PSSE34 I, ID, STATUS, AREA, ZONE, PL, QL, IP, IQ, YP, YQ, OWNER, SCALE,
INTRPT, DGENP, DGENQ, DGENM
PSSE35 I, ID, STATUS, AREA, ZONE, PL, QL, IP, IQ, YP, YQ, OWNER, SCALE,
INTRPT, DGENP, DGENQ, DGENM, LOADTYPE
PSSE36 I, ID, STATUS, AREA, ZONE, PL, QL, IP, IQ, YP, YQ, OWNER, SCALE,
INTRPT, DGENP, DGENQ, DGENM, LOADTYPE, NAME

5. Fixed Bus Shunt Data

PSSE33 I, ID, STATUS, GL, BL

PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 I, ID, STATUS, GL, BL, NAME

6. Voltage Droop Control Data

PSSE33 did not exist

PSSE34 did not exist
PSSE35 did not exist
PSSE36 NAME, STATUS, REGBUS, QDB, QMIN, QMAX, VDBLOW, VDBHIGH, VLOW, VHIGH

7. Generator Data

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
119
Power Flow RAW Format Change Sum-
mary

PSSE33 I, ID, PG, QG, QT, QB, VS, IREG, MBASE, ZR, ZX, RT, XT, GTAP, STAT,
RMPCT, PT, PB, O1, F1, ..., O4, F4, WMOD, WPF
PSSE34 I, ID, PG, QG, QT, QB, VS, IREG, MBASE, ZR, ZX, RT, XT, GTAP, STAT,
RMPCT, PT, PB, O1, F1, ..., O4, F4, WMOD, WPF, NREG
PSSE35 I, ID, PG, QG, QT, QB, VS, IREG, NREG, MBASE, ZR, ZX, RT, XT, GTAP,
STAT, RMPCT, PT, PB, BASLOD, O1, F1, ..., O4, F4, WMOD, WPF
PSSE36 I, ID, PG, QG, QT, QB, VS, IREG, NREG, MBASE, ZR, ZX, RT, XT, GTAP,
STAT, RMPCT, PT, PB, BASLOD, O1, F1, ..., O4, F4, WMOD, WPF, DROOPNAME,
NAME

8. Switching Device Rating Tables

PSSE33 did not exist

PSSE34 did not exist
PSSE35 did not exist
PSSE36 RSETNAM, DESCRIPTION, RATE1, ..., RATE12

9. Non-Transformer Branch Data

PSSE33 I, J, CKT, R, X, B, NAME, RATEA, RATEB, RATEC, GI, BI, GJ, BJ, ST,
MET, LEN, O1, F1, ..., O4, F4
PSSE34 I, J, CKT, R, X, B, NAME, RATE1, ..., RATE12, GI, BI, GJ, BJ, ST,
MET, LEN, O1, F1, ..., O4, F4
PSSE35 same as previous version
PSSE36 I, J, CKT, R, X, B, NAME, RATE1, ..., RATE12, GI, BI, GJ, BJ, ST,
BP, MET, LEN, O1, F1, ..., O4, F4

10. System Switching Device Data

PSSE33 did not exist

PSSE34 I, J, CKT, X, RATE1, ..., RATE12, STATUS, NSTATUS, METERED, STYPE, NAME
PSSE35 same as previous version
PSSE36 I, J, CKT, X, RSETNAM, STATUS, NSTATUS, METERED, STYPE, NAME

11. Transformer Data

PSSE33 Three winding

I, J, K, CKT, CW, CZ, CM, MAG1, MAG2, NMETR, NAME, STAT, O1, F1, ...,
O4, F4, VECGRP

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, NODE1, RMA1,
RMI1, VMA1, VMI1, NTP1, TAB1, CR1, CX1, CNXA1

WINDV2, NOMV2, ANG2, RATA2, RATB2, RATC2, COD2, CONT2, NODE2, RMA2,
RMI2, VMA2, VMI2, NTP2, TAB2, CR2, CX2, CNXA2

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
120
Power Flow RAW Format Change Sum-
mary

WINDV3, NOMV3, ANG3, RATA3, RATB3, RATC3, COD3, CONT3, NODE3, RMA3,
RMI3, VMA3, VMI3, NTP3, TAB3, CR3, CX3, CNXA3

Two winding

I, J, K, CKT, CW, CZ, CM, MAG1, MAG2, NMETR, NAME, STAT, O1, F1, ...,
O4, F4, VECGRP, ZCOD

R1-2, X1-2, SBASE1-2

WINDV1, NOMV1, ANG1, RATE11...RATE121, COD1, CONT1, NODE1, RMA1, RMI1,

VMA1, VMI1, NTP1, TAB1, CR1, CX1, CNXA1

WINDV2, NOMV2
PSSE34 Three winding

I, J, K, CKT, CW, CZ, CM, MAG1, MAG2, NMETR, NAME, STAT, O1, F1, ...,
O4, F4, VECGRP, ZCOD

R1-2, X1-2, SBASE1-2, R2-3, X2-3, SBASE2-3, R3-1, X3-1, SBASE3-1,

VMSTAR, ANSTAR

WINDV1, NOMV1, ANG1, RATE11, ..., RATE121, COD1, CONT1, NODE1, RMA1,
RMI1, VMA1, VMI1, NTP1, TAB1, CR1, CX1, CNXA1

WINDV2, NOMV2, ANG2, RATE12, ..., RATE122, COD2, CONT2, NODE2, RMA2,
RMI2, VMA2, VMI2, NTP2, TAB2, CR2, CX2, CNXA2

WINDV3, NOMV3, ANG3, RATE13, ..., RATE123, COD3, CONT3, NODE3, RMA3,
RMI3, VMA3, VMI3, NTP3, TAB3, CR3, CX3, CNXA3

Two winding

I, J, K, CKT, CW, CZ, CM, MAG1, MAG2, NMETR, NAME, STAT, O1, F1, ...,
O4, F4, VECGRP, ZCOD

R1-2, X1-2, SBASE1-2

WINDV1, NOMV1, ANG1, RATE11, ..., RATE121, COD1, CONT1, NODE1, RMA1,
RMI1, VMA1, VMI1, NTP1, TAB1, CR1, CX1, CNXA1

WINDV2, NOMV2
PSSE35 same as previous version
PSSE36 same as previous version

12. Area Interchange Data

PSSE33 I, ISW, PDES, PTOL, ARNAME

PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
121
Power Flow RAW Format Change Sum-
mary

13. Two-Terminal DC Transmission Line Data

PSSE33 NAME, MDC, RDC, SETVL, VSCHD, VCMOD, RCOMP, DELTI, METER, DCVMIN,
CCCITMX, CCCACC

IPR, NBR, ANMXR, ANMNR, RCR, XCR, EBASR, TRR, TAPR, TMXR, TMNR, STPR,
ICR, IFR, ITR, IDR, XCAPR

IPI, NBI, ANMXI, ANMNI, RCI, XCI, EBASI, TRI, TAPI, TMXI, TMNI, STPI,
ICI, IFI, ITI, IDI, XCAPI
PSSE34 NAME, MDC, RDC, SETVL, VSCHD, VCMOD, RCOMP, DELTI, METER, DCVMIN,
CCCITMX, CCCACC

IPR, NBR, ANMXR, ANMNR, RCR, XCR, EBASR, TRR, TAPR, TMXR, TMNR, STPR,
ICR, IFR, ITR, IDR, XCAPR, NDR

IPI, NBI, ANMXI, ANMNI, RCI, XCI, EBASI, TRI, TAPI, TMXI, TMNI, STPI,
ICI, IFI, ITI, IDI, XCAPI, NDI
PSSE35 NAME, MDC, RDC, SETVL, VSCHD, VCMOD, RCOMP, DELTI, METER, DCVMIN,
CCCITMX, CCCACC

IPR, NBR, ANMXR, ANMNR, RCR, XCR, EBASR, TRR, TAPR, TMXR, TMNR, STPR,
ICR, NDR, IFR, ITR, IDR, XCAPR

IPI, NBI, ANMXI, ANMNI, RCI, XCI, EBASI, TRI, TAPI, TMXI, TMNI, STPI,
ICI, NDI, IFI, ITI, IDI, XCAPI
PSSE36 same as previous version

14. Voltage Source Converter (VSC) DC Transmission Line Data

PSSE33 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
PSSE34 NAME, MDC, RDC, O1, F1, ... O4, F4

IBUS, TYPE, MODE, DCSET, ACSET, ALOSS, BLOSS, MINLOSS, SMAX, IMAX,
PWF, MAXQ, MINQ, VSREG, RMPCT, NREG

IBUS, TYPE, MODE, DCSET, ACSET, ALOSS, BLOSS, MINLOSS, SMAX, IMAX,
PWF, MAXQ, MINQ, VSREG, RMPCT, NREG
PSSE35 NAME, MDC, RDC, O1, F1, ... O4, F4

IBUS, TYPE, MODE, DCSET, ACSET, ALOSS, BLOSS, MINLOSS, SMAX, IMAX,
PWF, MAXQ, MINQ, VSREG, NREG, RMPCT

IBUS, TYPE, MODE, DCSET, ACSET, ALOSS, BLOSS, MINLOSS, SMAX, IMAX,
PWF, MAXQ, MINQ, VSREG, NREG, RMPCT
PSSE36 same as previous version

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
122
Power Flow RAW Format Change Sum-
mary

15. Transformer Impedance Correction Tables

PSSE33 I, T1, F1, T2, F2, T3, F3, ... T11, F11
PSSE34 I, T1, Re(F1), Im(F1), T2, Re(F2), Im(F2), ..., T6, Re(F6), Im(F6)

T7, Re(F7), Im(F7), T8, Re(F8), Im(F8), ..., T12, Re(F12), Im(F12)

...

...

Tn, Re(Fn), Im(Fn), 0.0, 0.0, 0.0

PSSE35 same as previous version
PSSE36 same as previous version

16. Multi-Terminal DC Transmission Line Data

PSSE33 NAME, NCONV, NDCBS, NDCLN, MDC, VCONV, VCMOD, VCONVN

IB, N, ANGMX, ANGMN, RC, XC, EBAS, TR, TAP, TPMX, TPMN, TSTP, SETVL,
DCPF, MARG, CNVCOD

IDC, IB, AREA, ZONE, DCNAME, IDC2, RGRND, OWNER

IDC, JDC, CKT, MET, RDC, LDC

PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

17. Multi-Section Line Grouping Data

PSSE33 I, J, ID, MET, DUM1, DUM2, ..., DUM9

PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

18. Zone Data

PSSE33 I, ZONAME
PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

19. Interarea Transfer Data

PSSE33 ARFROM, ARTO, TRID, PTRAN

PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version
PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
123
Power Flow RAW Format Change Sum-
mary

20. Owner Data

PSSE33 I, OWNAME
PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

21. FACTS Device Data

PSSE33 NAME, I, J, MODE, PDES, QDES, VSET, SHMX, TRMX, VTMN, VTMX, VSMX,
IMX, LINX, RMPCT, OWNER, SET1, SET2, VSREF, REMOT, MNAME
PSSE34 NAME, I, J, MODE, PDES, QDES, VSET, SHMX, TRMX, VTMN, VTMX, VSMX,
IMX, LINX, RMPCT, OWNER, SET1, SET2, VSREF, FCREG, MNAME, NREG
PSSE35 NAME, I, J, MODE, PDES, QDES, VSET, SHMX, TRMX, VTMN, VTMX, VSMX,
IMX, LINX, RMPCT, OWNER, SET1, SET2, VSREF, FCREG, NREG, MNAME
PSSE36 same as previous version

22. Switched Shunt Data

PSSE33 I, MODSW, ADJM, STAT, VSWHI, VSWLO, SWREM, RMPCT, RMIDNT, BINIT, N1,
B1, N2, B2, ..., N8, B8
PSSE34 I, MODSW, ADJM, STAT, VSWHI, VSWLO, SWREG, RMPCT, RMIDNT, BINIT, N1,
B1, N2, B2, ..., N8, B8, NREG
PSSE35 I, ID, MODSW, ADJM, STAT, VSWHI, VSWLO, SWREG, NREG, RMPCT, RMIDNT,
BINIT, S1, N1, B1, S2, N2, B2, ..., S8, N8, B8
PSSE36 I, ID, MODSW, ADJM, STAT, VSWHI, VSWLO, SWREG, NREG, RMPCT, RMIDNT,
BINIT, NAME, S1, N1, B1, S2, N2, B2, ..., S8, N8, B8

23. GNE Device Data

PSSE33 NAME, MODEL, NTERM, BUS1, ..., BUSNTERM, NREAL, NINTG, NCHAR

STATUS, OWNER, NMET

REAL1, ..., REALmin(10, NREAL)

INTG1, ..., INTGmin(10, NINTG)

CHAR1, ..., CHARmin(10, NCHAR)

PSSE34 same as previous version
PSSE35 same as previous version
PSSE36 same as previous version

24. Induction Machine Data

PSSE33 I, ID, STATUS, SCODE, DCODE, AREA, ZONE, OWNER, TCODE, BCODE, MBASE,
RATEKV, PCODE, PSET, H, A, B, D, E, RA, XA, XM, R1, X1, R2, X2, X3,
E1, SE1, E2, SE2, IA1, IA2, XAMULT
PSSE34 same as previous version

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
124
Power Flow RAW Format Change Sum-
mary

PSSE35 same as previous version

PSSE36 I, ID, STATUS, SCODE, DCODE, AREA, ZONE, OWNER, NAME, TCODE, BCODE,
MBASE, RATEKV, PCODE, PSET, H, A, B, D, E, RA, XA, XM, R1, X1, R2,
X2, X3, E1, SE1, E2, SE2, IA1, IA2, XAMULT

25. Load Type Data

PSSE33 did not exist

PSSE34 did not exist
PSSE35 did not exist
PSSE36 NAME, DESC

26. Interface Data

PSSE33 did not exist

PSSE34 did not exist
PSSE35 did not exist
PSSE36 NAME, INUM, TYPE, RATMAX1, RATMAX2, RATMAX3, RATMAX4, RATMAX5, RAT-
MAX6, RATMAX7, RATMAX8, RATMAX9, RATMAX10, RATMAX11, RATMAX12, RAT-
MIN1, RATMIN2, RATMIN3, RATMIN4, RATMIN5, RATMIN6, RATMIN7, RATMIN8,
RATMIN9, RATMIN10, RATMIN11, RATMIN12

27. Interface Element Data

PSSE33 did not exist

PSSE34 did not exist
PSSE35 did not exist
PSSE36 NAME, TYPE, INUM, JNUM, KNUM, NAMID, DIRCTN, IMET, WEIGHT

28. Substation Data

PSSE33 did not exist

PSSE34 IS, NAME, LATI, LONG, SGR
PSSE35 same as previous version
PSSE36 same as previous version

29. Node Data

PSSE33 did not exist

PSSE34 NI, NAME, I, STATUS, VM, VA
PSSE35 same as previous version
PSSE36 same as previous version

30. Station Switching Device Data

PSSE33 did not exist

PSSE34 NI, NJ, CKT, NAME, TYPE, STATUS, NSTAT, X, RATE1, RATE2, RATE3
PSSE35 same as previous version

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
125
Power Flow RAW Format Change Sum-
mary

PSSE36 NI, NJ, CKT, NAME, TYPE, STATUS, NSTAT, X, RSETNAM

31. Equipment Terminal Data

PSSE33 - did not exist

PSSE34 Load Terminal Data I, NI, 'L', ID

PSSE34 Fixed Shunt Terminal Data I, NI, 'F', ID
PSSE34 Machine Terminal Data I, NI, 'M', ID
PSSE34 Non-transformer Branch Terminal Data I, NI, 'B', J, CKT
PSSE34 Two Winding Transformer Terminal Data I, NI, '2', J, CKT
PSSE34 Three Winding Transformer Terminal Data I, NI, '3', J, K, CKT
PSSE34 Switched Shunt Terminal Data I, NI, 'S'
PSSE34 Induction Machine Terminal Data I, NI, 'I', ID
PSSE34 Two-terminal DC Line Terminal Data I, NI, 'D', NAME
PSSE34 VSC DC Line Terminal Data I, NI, 'V', NAME
PSSE34 Multi-terminal DC Line Terminal Data I, NI, 'N', NAME
PSSE34 FACTS Device Terminal Data I, NI, 'A', NAME

PSSE35 Switched Shunt Terminal Data I, NI, 'S', ID

PSSE35 all equipment except switched shunt same as previous version

PSSE36 all equipment same as previous version

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
126
 Chapter 3
Extensible Power Flow Data File (RAWX)

3.1. Overview
The RAWX format is a JSON-compliant, human-readable data storage and exchange format for PSS®E data.
Version 35 of PSS®E will support both the non-extensible, traditional RAW format along with RAWX. It is
expected that the RAWX format will become the standard text-based data format for PSS®E in the future, and
that updates to the functions that read and create the traditional RAW format will not be fully supported in a
future version of PSS®E. Therefore, it is recommended that your current use of the RAW format be migrated
to RAWX as soon as possible. PSS®E has tools for generating RAWX files from RAW and SAV files.

A RAWX files consist of two types of data objects, RAWX Parameter Sets and RAWX Data Tables. A minimal
example of the content of a RAWX file looks like the example below, where "caseid" section is an example of
a RAWX Parameter Set, and the "bus" section is an example of a RAWX Data Table (which has multiple data
rows, one for each bus record).

{
"network":{
"caseid":{
"fields": ["title1", "company:string", "modelyear:int"],
"data": ["SIMPLE EXAMPLE", "ElectroCorp", 2026]
},
"bus":{
"fields": ["ibus", "name", "rdfid:string", "baskv", "ide"],
"data":[
[101, "Bus1", "c9bca33c8fcb4df5bbfae15a9a9157c7", 500.0, 3]
[102, "Bus2", "8d4653380d374901bf856fa07c88c23a", 230.0, 1]
]
}
}
}

Note that the above example is not sufficient to create a viable power flow case in PSS®E, but simply shows
the general structure of the format. This document describes the specification of the underlying JSON format,
the details of the RAWX objects, and a complete field key reference.

3.1.1. Additional RAWX Documentation

Documentation for the Extensible Power Flow Data File (RAWX) is located in two places. While this chapter
contains the documentation for JSON, the RAWX specification, custom fields, and the RAWX Field Key refer-
ence, the Power Flow Data File (RAW) chapter contains consolidated syntax and data field documentation
for both RAW and RAWX. The purpose of the consolidated documentation in to provide a side-by-side com-
parison of the traditional RAW and the RAWX formats.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
127
Extensible Power Flow Data File Introduction to JSON
(RAWX)

3.2. Introduction to JSON

JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and
write. It is easy for machines to parse and generate. It has been chosen as the basis for the RAWX format
because it provides all the extensibility and data-tagging that XML provides, while also providing much more
efficient storage of large data tables than XML. The JSON format is also very close to the format of the Python
dictionary, and conversion between the two is straight-forward and JSON support is built into the Python
standard library. Because the preferred language for using the public API of PSS®E is Python, the similarity
of JSON to Python dictionaries is especially advantageous.

3.2.1. JSON Data Types

A JSON-compliant file consist of one or more JSON data types. These are the only data types allowed in a
JSON-compliant file.

• JSON Object

The JSON Object is an unordered collection of name–value pairs where the names (also called keys) are
strings. Since objects are intended to represent associative arrays, it is recommended, though not required,
that each key is unique within an object. Objects are delimited with curly brackets { }, and use commas to
separate each pair, while within each pair the colon ':' character separates the key or name from its value.

The RAWX format consist of two types of named JSON objects. These are referred to the RAWX Parameter
Set, and the RAWX Data Table. An example of a JSON Object used in RAWX is:

"area":
{
object attributes...
}

• JSON Array

A JSON array in an ordered list of zero or more values, each of which may be of any type. Arrays use square
bracket [ ] notation and elements are comma-separated.

In the RAWX Format, JSON Arrays are used for Field Lists and Data Rows. Field Lists are attributes of RAWX
Parameter Sets and Data Tables to indicate the order and subset of fields for which data is provided, for
example:

"fields": ["iarea", "isw", "pdes", "ptol", "arname"]

And Data Rows are JSON arrays that provide the data records for each element, for example:

"data": [
[1, 101, 250.000, 10.000, "FLAPCO"],
[2, 206, -100.000, 10.000, "LIGHTCO"]
]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
128
Extensible Power Flow Data File RAWX Format Specification
(RAWX)

• JSON String

A JSON string is a sequence of zero or more Unicode characters. Strings are delimited with double-quota-
tion marks " " and support a backslash escaping syntax for certain special characters.

JSON strings are used in RAWX data for data the field names in Field Lists, as well as values in Data Rows
that are encoded in PSS®E as character data, such as equipment ids, equipment names, etc.

• JSON Number

A JSON Number a signed decimal number that may contain a fractional part and may use exponential E
notation, but cannot include non-numbers such as NaN. The format makes no distinction between integer
and floating-point. JavaScript uses a double-precision floating-point format for all its numeric values, but
other languages implementing JSON may encode numbers differently.

Data values in Data Rows that correspond to either Integer or Real data in PSS®E are encoded as JSON
numbers in the RAWX file. Note that these number values are interpreted as either Fortran Integers or
Fortran Real values in PSS®E during the READX process that reads RAWX data into the PSS®E internal arrays.

• JSON Boolean

The JSON boolean can be either of the values true or false, denoted by the literal symbols true and false,
without quotes.

The RAWX format does not have any boolean fields in the native RAWX data schema. However, custom
fields may be included of type boolean, and these are stored as used as Fortran logical values in PSS®E.

• JSON Null

An empty value, using the word null, without quotes.

In RAWX, a value of null in a Data Row indicates a skipped value, which forces the data value to use the
appropriate default value. In other words

3.3. RAWX Format Specification

3.3.1. RAWX File Structure
A RAWX file is a JSON-compliant text file. Any application that can validate JSON data will be able to validate
a RAWX file. Therefore, the first step in validating the contents of a RAWX file is verifying that the file is valid
JSON. However, the requirements for a valid RAWX go beyond JSON compliance.

A valid RAWX contains:

• An outer, top-level, unnamed object denoted with an opening curly bracket { and ending with a closing
curly bracket }:

{
file contents...
}

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
129
Extensible Power Flow Data File RAWX File Structure
(RAWX)

• A named object within the top-level object in which the network data parameter sets and data tables
reside. This object is a data set with the key "network":

{
"network":
{
parameter sets and data tables...
}
}

• A comma-separated, unordered set of named objects within the "network" object. These objects are the
parameter sets and the data tables. The names (keys) of the object are the documented names of the
parameter sets and data tables, such as "caseid", "newton", "bus" or "generator":

{
"network":
{
"caseid":
{
parameter set contents...
},
"bus":
{
data table contents...
}

additional, comma-separated parameter set and data table objects...

}
}

The order of these does not matter, but when exporting RAWX data from PSS®E, the order will match the
prescribed order of the sections of the traditional RAW format. Not all parameter sets or data tables need
to be included, but only the subset of these objects need to be included in the file for which data will be
provided. For example, if not FACTS devices exist in the power flow case encoded in the RAWX file, the
data table object with key "facts" can be excluded completely in the file.

Additional considerations for the structure of the RAWX file:

• Additional objects included under the top-level object will be ignored and not stored or exported from
PSS®E during a RAWX export (RAWDX command). In other words, the RAWX system currently only supports
the data set "network".

• Any additional objects within the "network" object with unrecognized names will be ignored and not stored
or exported from PSS®E during a RAWX export (RAWDX command). In other words, custom tables and pa-
rameter sets are not supported (Custom fields within known parameter sets and data table are supported,
and will be discussed in the following sub sections).

• Indentation, additional whitespace, and new lines are all optional. The convention used in this document
and in the PSS®E RAWX export is based on JSON best-practices for readability.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
130
Extensible Power Flow Data File Parameter Sets
(RAWX)

• Commas are required between parameter sets and data tables. JSON validation will fail if these commas
are missing. Also, the last object in the set must not have a trailing comma.

As and example, A minimal working case in the form of a RAWX file, available as mincas.rawx in the PSS®E
EXAMPLE folder, is listed below.

{
"network":{
"caseid":{
"fields":["title1"],
"data":["PSS(R)E MINIMUM RAWX CASE"]
},
"bus":{
"fields":["ibus", "name", "ide"],
"data":[
[101, "Source", 3],
[102, "Sink", 1]
]
},
"load":{
"fields":["ibus", "loadid", "pl", "ql"],
"data":[
[102, "1", 500.0, 200.0]
]
},
"generator":{
"fields":["ibus", "machid"],
"data":[
[101, "1"]
]
},
"acline":{
"fields":["ibus", "jbus", "ckt", "xpu"],
"data":[
[101, 102, "1", 0.01]
]
}
}
}

Note that only the parameter sets and data tables for which data is provided are present in the file. Also, only
the parameters and fields for which data is provided are included in the field lists and data rows. The details
of the contents of the parameter sets and data tables are described in the following section.

3.3.2. Parameter Sets

Parameter sets are structures that contain values for various PSS®E parameters. Parameter sets consist of the
Parameter set name as the key of the JSON object, a field list, and a data array. The field list specifies the set
and order of fields for which data will be provided, and the data array provides the corresponding values.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
131
Extensible Power Flow Data File Data Tables
(RAWX)

The syntax of the parameter set is:

"parameter_set_name":
{
"fields": [ "key1", "key2", ... , "keyN" ],
"data": [ value1, value2, ... , valueN ]
}

An example with real field keys and data values looks like:

"solver":
{
"fields": ["method", "actaps", "phshft", "swshnt"],
"data": ["FDNS", 0, 0, 0]
}

3.3.3. Data Tables

RAWX data tables are similar to the parameter sets, but with the key difference that the data array is an array
of data rows, allowing multiple data rows (ie. element data records) to be defined.

The syntax of the data table is:

"data_table_name":
{
"fields": [ "key1", "key2", ... , "keyN" ],
"data": [
[ value1, value2, ... , valueN ],
[ value1, value2, ... , valueN ],

...

[ value1, value2, ... , valueN ]

]
}

An example with real field keys and data values is:

"fixshunt":{
"fields":["ibus", "shntid", "stat", "gl", "bl"],
"data":[
[151, "1", 1, 0.000, -600.0],
[201, "1", 1, 0.000, 300.0],
[205, "1", 1, 0.000, 300.0]
]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
132
Extensible Power Flow Data File Field List Customization
(RAWX)

3.3.4. Field List Customization

Field lists can be customized by changing the field order and by excluding unused fields. For example, the
default field list for the "fixshunt" data table is

["ibus", "shntid", "stat", "gl", "bl"]

This field list can be customized by excluding the "gl" field (which is typically zero) and moving the "stat" field
to the end. This customized field list specification is:

["ibus", "shntid", "bl", "stat"]

The rows must provide the data values according to the customized field list specification. For this example,
the new "fixshunt" data table object will appear as:

"fixshunt":{
"fields":["ibus", "shntid", "bl", "stat"],
"data":[
[151, "1", -600.0, 1],
[201, "1", 300.0, 1],
[205, "1", 300.0, 1]
]
}

Primary key fields, or the fields that are used to uniquely define a PSS®E element, may not be excluded and
must be present in the field list and data rows. For example, the primary key of the "bus" data table is the
"ibus" field, and the primary keys for the "acline" table are the "ibus", "jbus", and "ckt" fields. Whether a field
is a primary key can be determined from the "Is Primary Key" column in the RAWX Field Key Reference.

The only data values that can be excluded from the data rows, are trailing fields. In other words, if the number
of elements in a data row is less than the number of elements the field list, the RAWX parser will assume that
the data values matches the field list positionally, and the data values for the missing trailing data will be
null. The effect of excluding a field is to force PSS®E to assume the default value for that field. For example,
if one wishes to leave out the "stat" data for some rows, this can be achieved by simply excluding the data
value and inserting an explicit null. Both methods have the same effect:

"fixshunt":{
"fields":["ibus", "shntid", "bl", "stat"],
"data":[
[151, "1", -600.0],
[201, "1", 300.0, null],
[205, "1", 300.0, 1]
]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
133
Extensible Power Flow Data File Custom Field Definitions
(RAWX)

In order to skip fields that are not at the end of the field list, the data value must be null. Again, the effect
of skipping a field is to force PSS®E to assume the default value for that field. An example of this, where the
default value for the field "bl" is desired at bus 201, appears as:

"fixshunt":{
"fields":["ibus", "shntid", "bl", "stat"],
"data":[
[151, "1", -600.0, 1],
[201, "1", null, 1],
[205, "1", 300.0, 1]
]
}

The default value of a field can be determined from the "Default" column in the RAWX Field Key.

3.3.5. Custom Field Definitions

Custom field can be added to most RAWX Parameter Sets and Data Tables. Custom fields are defined in the
field list of the RAWX object, and their corresponding data values are adding in the data rows. Custom fields
are read into PSS®E, stored internally, and exported when saving network data as RAWX. In this way, custom
data can make a "roundup-trip" into and out of PSS®E.

The rules for defining and using custom fields are as follows:

• Custom fields may not have the same name as any known RAWX fields. See the RAWX Field Key Reference
for a full list of known fields and the PSS®E minor version in which they have been introduced.

• Custom fields have one of several data types. Data types are specified in the field definition, delimited
from the field name by a colon (eg. "myfield:integer"). Custom fields without a data type specification are
assumed to be of type string. For example, a custom field of "myfield" without a data type specification,
is interpreted and stored as a string.

• Custom fields may appear anywhere in the field list, however, the field order is not guaranteed to be
retained when exporting RAWX data from PSS®E.

• PSS®E will attempt to read and store the custom data according to the defined data type of the custom
field. If the data conversion fails, such as in the case of providing a String of characters for an integer field,
a warning will be given in progress, and the data value will be null.

• Custom data is currently not supported in the following Data Tables:

• Transformer Impedance Correction Tables (impcor)

• All Multi-terminal DC Line Component Tables (ntermdcconv, ntermdcbus, and ntermdclink). (Note that
the primary data record (ntermdc) does support custom fields)

• Generic Network Element (gne) records

A full description of the custom field data type specification and examples are shown in the below table.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
134
Extensible Power Flow Data File Partial Datasets (Read and Change)
(RAWX)

Data Type JSON Data Type Valid RAWX Example Field Example Da-
Keywords Definitions ta Values
String JSON String string "company" "ElectroCorp"

(default) strg "loadtype:string" "industrial"

str "fueltype:str" "solar"

character

char
Integer JSON Number int "normalstatus:int" 1

intg "modelyear:integer" 2030

integer
Floating Point JSON Number float "scalfact:float" 1.25

flt "sil:real" 869.3

real

double
Boolean JSON Boolean bool "baseload:bool" true

boolean "firm:boolean" false

logical

An example of a fixshunt data table with two custom fields is:

"fixshunt":{
"fields":["ibus", "shntid", "stat", "normalstat:int", "gl", "bl", "type:string"],
"data":[
[151, "1", 1, 1, 0.000, -600.0, "reactor"],
[201, "1", 1, 0, 0.000, 300.0, "capacitor"],
[205, "1", 1, 1, 0.000, 300.0, "capacitor"]
]
}

3.3.6. Partial Datasets (Read and Change)

A RAWX file can be used to import partial datasets. Partial datasets are RAWX tables that include data records
meant to be added to existing tables, or data records that include new or custom data to add to existing
records. This is similar to the behavior of activity Read and Change (RDCH). The key to using RAWX is this
way to set the "ic" field in the "caseid" parameter set to 1 (The default value of this field is 0). Therefore,
somewhere in the RAWX file, the following parameter set definition must be present and must at least include
the "ic" field:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
135
Extensible Power Flow Data File Partial Datasets (Read and Change)
(RAWX)

"caseid":{
"fields":["ic"],
"data":[1]
}

If "ic" is set to 1, all of the parameter sets and data tables in the RAWX file are interpreted as data to update
or add to the previously loaded loadflow data already in PSS®E.

For example, if one wishes to update only the area number of a few buses, the RAWX file contents would
read as follows:

{
"network":
{
"caseid":
{
"fields":["ic"],
"data":[1]
},

"bus":
{
"fields":["ibus", "area"],
"data":
[
[101, 10],
[102, 10]
]
}
}
}

Assuming a loadflow case that includes at least buses 101 and 102 has been loaded into PSS®E using READ,
READX, or CASE, when the above RAWX file is read into PSS®E using the activity READX, the existing loadflow
data remains intact, except the area number for buses 101 and 102 are updated to the value 10. If bus 101
or bus 102 are not present in the case, new bus record(s) will be added with default data (except for the area
number of 10). This is analogous to the behavior of the data change APIs (eg. psspy.bus_data) where some
arguments are the "default" or "do not change" values of _i or _f.

All or some of the fields included in partial datasets may be custom fields. For example, if one wishes to add
latitude and longitude data to the buses in a case while leaving all other data intact, the following RAWX
file could be used:

{
"network":
{
"caseid":
{

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
136
Extensible Power Flow Data File Custom Table Definitions
(RAWX)

"fields":["ic"],
"data":[1]
},

"bus":
{
"fields":["ibus", "lati:real", "long:real"],
"data":
[
[101, 81.34, -34.51],
[102, 81.85, -34.12],
[151, 82.31, -33.51],
[152, 82.87, -33.61],
[153, 83.33, -32.81],
... additional data rows...
]
}
}
}

3.3.7. Custom Table Definitions

Custom tables can be added to the RAWX file via READX, stored in PSS®E, and exported via RAWDX.

The rules for defining and using custom tables are as follows:

• The name of the table must be unique within the file. If there are more than one table in the network data
section of the rawx file with the same name, only one of the tables with that name will be stored in PSS®E.

• The field specifications in the field list follow the rules of the previous section (Custom Field Definitions).
Note that all fields in a custom table are by definition custom fields.

• User defined tables do not have to be located at the end of the rawx file. They can be located anywhere
within the network node. When rawx data is exported from PSS®E, however, the original order of the tables
may not be maintained.

An example of two customs tables that encode simple interface definitions:

"interface":{
"fields":["name", "rating:real"],
"data":[
["InterfaceA", 600.0],
["InterfaceB", 850.0]
]
},

"interfaceBranch":{
"fields":["intname", "ibus:int", "jbus:int", "ckt"],
"data":[
["InterfaceA", 152, 3004, "1"],

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
137
Extensible Power Flow Data File Importing/Exporting from CSV files
(RAWX)

["InterfaceA", 3005, 3006, "1"],

["InterfaceA", 154, 3008, "1"],
["InterfaceB", 151, 201, "1"],
["InterfaceB", 152, 202, "1"],
["InterfaceB", 154, 203, "1"],
["InterfaceB", 154, 205, "1"]
]
}

Once the custom tables are imported into PSS®E via readx, the data in the custom tables are accessible
using the Extension Data APIs (in the form get_ext_, set_ext_, etc.). An example of accessing the data using
Python is given below. In this example, the get_ext_rowcount api is used to get the number of rows of each
custom table, the get_ext_char, get_ext_int, and get_ext_real apis are used to get the ratings and flows of
an interface, and a message is printed if the interface flow exceeds its rating.

ierr, nrows = psspy.get_ext_rowcount("interface")

rating = 0.0

for irow in range(1, nrows+1):

ierr, name = psspy.get_ext_char("interface", "name", irow)
if name == "InterfaceA"
ierr, rating = psspy.get_ext_real("interface", "rating", irow)

ierr, nrows = psspy.get_ext_rowcount("interfaceBranch")

intflow = 0.0

for irow in range(1, nrows+1):

ierr, intname = psspy.get_ext_char("interfaceBranch", "intname", irow)
if intname == "InterfaceA"
ierr, ibus = psspy.get_ext_int("interfaceBranch", "ibus", irow)
ierr, jbus = psspy.get_ext_int("interfaceBranch", "jbus", irow)
ierr, ckt = psspy.get_ext_char("interfaceBranch", "ckt", irow)
ierr, sflow = psspy.brnflo(ibus, jbus, ckt)
intflow += sflow

if abs(intflow) > rating:

print("Interface A flow of {} MVA > rating of {} MVA".format(abs(intflow), rating))

3.4. Importing/Exporting from CSV files

3.4.1. Importing RAWX tables from CSV
RAWX data can be imported from Comma-separated values (CSV) files. Each CSV file imported cooresponds
to one RAWX parameter set or data table. Partial data sets, custom fields and custom tables are supported.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
138
Extensible Power Flow Data File Exporting RAWX tables to CSV
(RAWX)

The only required field(s) are the primary keys (unique identifiers) for the element for built-in (non-custom)
data tables (primary keys are shown in the RAWX Field Reference Section of this document for each data
table). Currently, the API CSV_TO_RAWX is the only method to perform this import. And example of an area
table before and after a CSV import is shown below.

Original RAWX Table:

"area":{
"fields":["iarea", "isw", "pdes", "ptol", "arname"],
"data":[
[1, 101, -2800.000, 10.000, "CENTRAL"],
[2, 206, -1600.000, 10.000, "EAST"],
[4, 401, 300.000, 15.000, "EAST_COGEN1"],
[5, 3011, 900.000, 10.000, "WEST"]
]
}

Imported CSV File Contents

iarea, ptol, companyname:char

1, 5.000, "ElectroCorp"
2, 5.000, "Tesla Power and Light"
4, 10.000, "Gigawatt Industries"
5, 5.000, "Electron Wholesalers"

Resultant RAWX Table after CSV Import:

"area":{
"fields":["iarea", "isw", "pdes", "ptol", "arname", "companyname:char"],
"data":[
[1, 101, -2800.000, 5.000, "CENTRAL" , "ElectroCorp" ],
[2, 206, -1600.000, 5.000, "EAST" , "Tesla Power and Light" ],
[4, 401, 300.000, 10.000, "EAST_COGEN1", "Gigawatt Industries" ],
[5, 3011, 900.000, 5.000, "WEST" , "Electron Wholesalers" ]
]
}

3.4.2. Exporting RAWX tables to CSV

Parameter sets and data tables loaded into PSS®E can be exported to Comma-separated values (CSV) files.
Each parameter set or data table is exported to its own CSV file one at a time. In otherwords, one CSV file
cooresponds to one RAWX parameter set or data table. Currently, the API RAWX_TO_CSV is the only method
to perform this export.

When exporting RAWX to CSV, all fields, built-in and custom, are included in the export, and the field order-
ing is identical to the ordering of RAWDX data export. Custom fields will retain their dataype specification

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
139
Extensible Power Flow Data File Exporting RAWX tables to CSV
(RAWX)

(eg. "latitude:real" vs. just "latitude") in the header row of the CSV file. An example of a Zone table and its
cooresponding CSV output is shown below:

RAWX Table:

"zone":{
"fields":["izone", "zoname", "loadfactor:real"],
"data":[
[1, "NORTH", 0.54],
[2, "MID", 0.47],
[3, "SOUTH", 0.56],
[4, "EAST", 0.59]
]
}

Exported CSV File Contents:

izone, zoname, loadfactor:real

1, "NORTH", 0.54
2, "MID", 0.47
3, "SOUTH", 0.56
4, "EAST", 0.59

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
140
 Chapter 4
Sequence Data File

4.1. Overview
The input stream to activity RESQ is a Sequence Data File containing 11 groups of records with each group
specifying a particular type of sequence data required for fault analysis work (refer to Table 4.1). Any piece
of equipment for which sequence data is to be entered in activity RESQ must be represented as power flow
data in the working case. That is, activity RESQ will not accept data for a bus, generator, branch, switched
shunt or fixed shunt not contained in the working case.

All data is read in free format with data items separated 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.

Table 4.1. Sequence Data Input Structure

Change Code

System Wide Data

Generator Sequence Data

Load Sequence Data

Zero Sequence Non-Transformer Branch Data

Zero Sequence Mutual Impedance Data

Zero Sequence Transformer Data

Zero Sequence Switched Shunt Data

Zero Sequence Fixed Shunt Data

Induction Machine Sequence Data

Non-Conventional Source Fault Contribution Characteristics Data

Non-Conventional Source - Generator Data

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
141
Sequence Data File Change Code

Q Record

4.2. Change Code

The first record in the Sequence Data File contains two data items as follows:

IC, REV

IC 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.

IC=0 by default.
REV PSSE revision number. REV = Current revision by default.

The use of the change case mode in activity RESQ is identical to its use in activity READ: for the addition
of equipment to the working case (e.g., to add a zero sequence mutual coupling to the working case). It
is not valid to set IC to one for the initial execution of activity RESQ for the network in the working case;
in this case, an appropriate message is printed and activity RESQ continues its execution as if IC had been
specified as zero.

4.3. System Wide Data

Through the system-wide data category, data that pertains to the case as a whole (rather than to individual
equipment items) may be included in the Sequence Data File to allow convenient transfer of it with the case.
Records may be included that define:

• Short Circuit Output Report Format

• Metal Var Oxide (MOV) Iteration Options

• Short Circuit Model

Generally, each record specified in the System-Wide Data category begins with a NAME that defines the type
of data specified on the record. The formats of the various records are described in the following paragraphs.

RPTFORMAT Record

The Short Circuit Output Report Format record begins with the name RPTFORMAT and contains unit and co-
ordinates option for reporting current, voltage and Thevenin impedance. Using keyword input, any or all of
the following report format parameters may be specified:

AMPOUT = 0, Current and Voltages in PU) (default)

= 1, Current in Amperes and Voltages in kV

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
142
Sequence Data File Generator Sequence Data

POLROU = 0, Currents and Voltages in Rectangular co-ordinates (default)

= 1, Currents and Voltages in Polar co-ordinates

AMPOUTZ = 0, Thevenin Impedance in PU (default)

= 1, Thevenin Impedance in ohms

POLROUZ = 0, Thevenin Impedance in Rectangular co-ordinates (default)

= 1, Thevenin Impedance in Polar co-ordinates

Those RPTFORMAT parameters that are specified may be entered n any order. The following is an example
of this record:

RPTFORMAT, AMPOUT=0, POLROU=0, AMPOUTZ=0, POLROUZ=0

MOV Record

The Metal Var Oxide (MOV) Iteration Options record begins with the name MOV and contains linearized MOV
model iteration parameters used by short circuit calculation methods. Using keyword input, any or all of the
following MOV iteration parameters may be specified:

ITERATIONS Maximum number of iterations (default=20)

TOLERANCE Tolerance (default=0.01)

MOVALPHA Acceleration factor (default=0.3)

Those parameters that are specified may be entered in any order. The following is an example of this record:

MOV, ITERATIONS=20, TOLERANCE=0.01, MOVALPHA=0.3

SCMODEL Record

The Short Circuit Model Options record begins with the name SCMODEL and contains fault analysis modeling
option setting. Using keyword input, SCMODEL parameters may be specified:

SCNRML = 0, center tapped two-phase modeling

= 1, Normal three-phase modeling (default)

The following is an example of this record:

SCMODEL, SCNRML=1

4.4. Generator Sequence 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 entered into the PSSE working case for all in-service
machines at the bus.

Each generator sequence impedance data record has the following format:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
143
Sequence Data File Generator Sequence Data

I, ID, ZRPOS, ZXPPDV, ZXPDV, ZXSDV, ZRNEG, ZXNEGDV, ZR0, ZX0DV, CZG, ZRG, ZXG,
REFDEG

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 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 bus
voltage base and MBASE).

ZRPOS = ZR (source resistance in raw data) by default.

ZXPPDV Generator positive sequence saturated subtransient reactance; entered in pu on ma-
chine base (i.e., on bus voltage base and MBASE).

ZXPPDV = ZX (source reactance in raw data) by default

ZXPDV Generator positive sequence saturated transient reactance; entered in pu on machine
base (i.e., on bus voltage base and MBASE).

ZXPDV = ZXPPDV by default

ZXSDV Generator positive sequence saturated synchronous reactance; entered in pu on ma-
chine base (i.e., on bus voltage base and MBASE).

ZXSDV = XPPDV by default.

ZRNEG Generator negative sequence resistance; entered in pu on machine base (i.e., on bus
voltage base and MBASE).

ZRNEG = ZRPOS by default

ZXNEGDV Generator negative sequence saturated reactance; entered in pu on machine base
(i.e., on bus voltage base and MBASE).

ZXNEGDV = ZXPPDV by default

ZR0 Generator zero sequence resistance; entered in pu on machine base (i.e., on bus volt-
age base and MBASE).

ZR0 = ZRPOS by default

ZX0DV Generator zero sequence saturated reactance; entered in pu on machine base (i.e., on
bus voltage base and MBASE).

ZX0DV = ZXPPDV by default

CZG Units of grounding impedance (ZRG and ZXG) values, = 1 for pu (on bus voltage base
and MBASE), = 2 for Ohms
ZRG Generator grounding resistance; entered in pu on machine base (i.e., on bus voltage
base and MBASE) when CZG=1 or in ohms when CZG=2.

ZRG = 0.0 by default

ZXG Generator grounding reactance; entered in pu on machine base (i.e., on bus voltage
base and MBASE) when CZG=1 or in ohms when CZG=2.

ZXG = 0.0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
144
Sequence Data File Generator Sequence Data

REFDEG Generator Reference Angle; entered in degrees.

This angle is used only when fault calculations with for "FLAT" voltage profile is select-
ed.

REFDEG = 0.0 by default

Throughout this Manual, the complex positive sequence generator impedance used in fault analysis will be
referred to as ZPOS. The real component of ZPOS is always ZRPOS. Its imaginary component is either ZXPPDV,
ZXPDV or ZXSDV, according to the selection made in selecting the fault analysis calculation activity. Similarly,
the negative sequence generator impedance, ZNEG, is ZRNEG + j ZXNEGDV, and the zero sequence generator
impedance, ZZERO, is ZR0 + j ZX0DV.

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 resistance set to ZR (the real component
of ZSORCE), and all three positive sequence reactances set to ZX (the imaginary component of ZSORCE).
ZSORCE is the generator impedance entered in activities READ, Section Activity, TREA, RDCH, and MCRE; it is
used in switching studies and dynamic simulations (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 values unchanged. Note
that the generator positive sequence impedance values entered in activity RESQ for fault analysis purposes
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 sets of positive sequence impedance data are specified in the
working case simultaneously at different locations.

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 set equal to ZRPOS
+ j ZXPPDV. 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.

For those machines at which the step-up transformer is represented as part of the generator data (i.e., XTRAN
is non-zero), ZZERO is not used and, in the fault analysis activities, the step-up transformer is assumed to be
a delta wye transformer. Refer to Modeling of Generator Step-Up Transformers (GSU).

For those machines that do not include the step-up transformer as part of the generator data (i.e., XTRAN is
zero), a zero sequence impedance(ZR0, ZR0DV) of zero and grounding impedance (ZRG, ZXG) of zero results
in the machine being treated as an open circuit in the zero sequence.

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 ZRPOS + j
ZXPPDV. 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 zero sequence generator impedance unchanged.Generator
sequence impedance data input is terminated with a record specifying a bus number of zero.

Figure 4.1 shows generator representation in sequence networks.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
145
Sequence Data File Load Sequence Data

Figure 4.1. Generator Sequence Networks

PSS®E calculates pu grounding impedance from ohm as below:

4.5. Load Sequence Data

Exceptional negative sequence loads (i.e., loads that, in the negative sequence, differ from the positive se-
quence loads) and zero sequence loads are entered into the working case in load sequence data records in
the Sequence Data File. Each load negative and zero sequence data record has the following format:

I, ID, PNEG, QNEG, GRDFLG, PZERO, QZERO

I Bus number, bus I must be present in the working case.

ID One or two character load identifier of the load at bus I for which the data is specified
by this record.

ID = '1' by default
PNEG Active component of negative sequence load; entered in MW at one per unit voltage.
If PNEG=0 or is not specified, PNEG = positive sequence load MW.
QNEG Reactive component of negative sequence load; entered in MVAR at one per unit volt-
age. If QNEG=0 or is not specified, QNEG = positive sequence load MVAR. QNEG is
specified as negative MVAR for lagging (reactive) power factor loads.
GRDFLG Grounding flag; 1 for grounded loads and 0 for ungrounded loads.

GRDFLG=0 by default
PZERO Active component of zero sequence load; entered in MW at 1 pu voltage. If PZERO is
non-zero and GRDFLG=1, PZERO is modelled. If GRDFLG=0, PZERO is ignored.

PZERO=0 by default
QZERO Reactive component of zero sequence load; entered in MVAR at 1 pu voltage. If QZE-
RO is non-zero and GRDFLG=1, QZERO is modelled. If GRDFLG=0, QZERO is ignored.
QZERO is specified as negative MVAR for lagging (reactive) power factor loads.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
146
Sequence Data File Zero Sequence Non-Transformer
Branch Data

QZERO = 0.0 by default

For any bus where no load sequence data record is specified, or PNEG and QNEG are both specified as zero,
the load elements are assumed to be equal in the positive and negative sequence networks. For any bus
where no load sequence data record is specified, or PZERO and QZERO are both specified as zero, or GRDFLG
is specified as zero (i.e., an ungrounded load), no load component is represented in the zero sequence.

The user is advised to exercise caution in specifying negative and zero sequence loads. In the fault analysis
calculations, constant power and constant current loads are converted to constant admittance at the pre-
fault voltage. Further, when positive sequence loads are changed, either directly by the user or by activities
such as SCAL, it may be appropriate to change previously specified negative and zero sequence loads. It is
the user’s responsibility to ensure that the positive sequence loading data, as contained in the working case,
is coordinated with the specified negative and zero sequence load data.

Load sequence data input is terminated with a record specifying a bus number of zero.

4.6. 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, CKT, RLINZ, XLINZ, BCHZ, GI, BI, GJ, BJ, IPR, SCTYP

I Bus number of one end of the branch.

J Bus number of the other end of the branch.
CKT One- or two-character branch circuit identifier; a non-transformer branch with circuit
identifier CKT between buses I and J must be in the working case.

CKT = '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 which is not a zero impedance line and whose RLINZ and XLINZ are
both 0.0 is treated as open in the zero sequence network. XLINZ must be negative for
a series capacitor branch.

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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
147
Sequence Data File Zero Sequence Mutual Impedance Data

IPR MOV rated current for a series capacitor branch; entered in kA. It must be positive.

IPR = 0.0 by default

SCTYP MOV Protection Mode

• 0 for normal branch (i.e., not a MOV protected branch)

• 1 for MOV Protection enabled

• 2 for MOV Protection disabled

• 3 for Spark Gap Protection enabled (information only, not used in any calculations)

SCTPY=0 by default

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 (ZIL) in the positive sequence (refer to Zero Impedance Lines
section) is treated as ZIL in the zero sequence, regardless of its specified zero sequence impedance (RLINZ
and XLINZ).

During the initial input of sequence data (i.e., IC = 0 on the first data record), any non-transformer 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 executions of activity RESQ (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.

4.7. Zero Sequence Mutual Impedance Data

Data describing mutual couplings between branches in the zero sequence network are entered into the
working case in zero sequence mutual impedance data records in the Sequence Data File. Each zero sequence
mutual impedance data record has the following format:

I, J, CKT1, K, L, CKT2, RM, XM, BIJ1, BIJ2, BKL1, BKL2

I Bus number of one end of the first branch

J Bus number of the other end of the first branch
CKT1 One- or two-character branch circuit identifier of the first branch; a non-transformer
branch with circuit identifier ICKT1 between buses I and J must be in the working case.

CKT1 = '1' by default

K Bus number of one end of the second branch
L Bus number of the other end of the second branch
CKT2 One- or two-character branch circuit identifier of the second branch; a non-trans-
former branch with circuit identifier ICKT2 between buses K and L must be in the
working case.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
148
Sequence Data File Zero Sequence Mutual Impedance Data

CKT2 = '1' by default

RM,XM Branch-to-branch mutual impedance coupling circuit CKT1 from bus I to bus J with
circuit CKT2 from bus K to bus L; entered in pu.

No default is allowed
BIJ1 Starting location of the mutual coupling along circuit CKT1 from bus I to bus J relative
to the bus I end of the branch; entered in per unit of total line length.

BIJ1 = 0.0 by default

BIJ2 Ending location of the mutual coupling along circuit CKT1 from bus I to bus J relative
to the bus I end of the branch; entered in per unit of total line length.

BIJ2 = 1.0 by default

BKL1 Starting location of the mutual coupling along circuit CKT2 from bus K to bus L relative
to the bus K end of the branch; entered in per unit of total line length.

BKL1 = 0.0 by default

BKL2 Ending location of the mutual coupling along circuit CKT2 from bus K to bus L relative
to the bus K end of the branch; entered in per unit of total line length.

BKL2 = 1.0 by default

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 PSSE is defined in Table 3-1 Standard Maximum PSS®E Program Capacities.

• The polarity of a mutual coupling is determined by the ordering of the bus numbers (I,J,K,L) in the data
record. The dot convention applies, with the from buses (I and K) specifying the two dot ends of the
coupled branches.

• RM+jXM specifies the circuit-to-circuit mutual impedance, given the polarity implied by I and K.

• The geographical B factors are required only if one or both of the two mutually coupled lines is to be
involved in an unbalance part way down the line, and only part of the length of one or both of the lines
is involved in the coupling. (Note that the default values of the B factors result in the entire length of the
first line coupled to the entire length of the second line.)

• The values of the B factors must be between zero and one inclusive; they define the portion of the line
involved in the coupling.

• BIJ1 must be less than BIJ2, and BKL1 must be less than BKL2.

• Mutuals involving transformers or zero impedance lines are ignored by the fault analysis solution activities.

Figure 4.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).

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
149
Sequence Data File Zero Sequence Transformer Data

Figure 4.2. Mutual Coupline - 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 in Figure 4.3

Figure 4.3. Mutual Coupline - Example 2

Zero sequence mutual impedance data input is terminated with a record specifying a from bus number of
zero.

4.8. Zero Sequence Transformer Data

Zero sequence transformer parameters are entered into the working case in zero sequence transformer data
records in the Sequence Data File. Each transformer data record has one of the following formats:

For two-winding transformers:

I,J,K,CKT,CZ0,CZG,CC,RG1,XG1,R01,X01,RG2,XG2,R02,X02,RNUTRL,XNUTRL

For three-winding transformers:

I,J,K,CKT,CZ0,CZG,CC,RG1,XG1,R01,X01,RG2,XG2,R02,X02,

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
150
Sequence Data File Zero Sequence Transformer Data

RG3,XG3,R03,X03,RNUTRL,XNUTRL

Notations used in Zero Sequence Networks

Z01=R01+jX01 Z02=R02+jX02 Z03=R03+jX03

Zg1=RG1+jXG1 Zg2=RG2+jXG2 Zg3=RG3+jXG3

Znutrl=RNUTRL+jXNUTRL

I Bus number of the bus to which a winding of the transformer is connected.

J Bus number of the bus to which another winding of the transformer is connected.
K Bus number of the bus to which another winding of the transformer is connected. Zero
is used to indicate that no third winding is present (i.e., that a two-winding transformer
is being specified).

K = 0 by default
CKT One- or two-character transformer circuit identifier; a transformer with circuit identi-
fier CKT between buses I and J (and K if K is non-zero) must be in the working case.

CKT = '1' by default

CZ0 The non-grounding impedance data I/O code defines the units in which the impedance
values Z01, Z02 and Z03 are specified. In specifying these impedances, the winding
base voltage values are always the nominal winding voltages (NOMV1, NOMV2 and
NOMV3) that are specified on the third, fourth and fifth records of the Transformer
Data block in the Power Flow Raw Data File; see Transformer Data for more details.
If no value for NOMVn is specified, the winding "n" voltage base is assumed to be
identical to the winding "n" bus base voltage.

Legacy Connection Codes

For those connection codes that existed prior to PSS®E-33, CZ0 must be specified as 1.

• For two-winding transformers, these are connection codes 1 through 9;

• for three-winding transformers, these are connection codes 1 through 6, as well as

the three digit connection codes where each digit refers to one of the two-winding
connection codes 1 through 7 that is to be applied to one of the three windings of
the transformer.

• For all two-winding transformers with legacy connection codes, Z01 is specified
in per unit on system MVA base and winding voltage base. Only for two-winding
transformers with connection code 9, Z02 is specified in per unit on system MVA
base and winding 2 voltage base.

• For all three-winding transformers with legacy connection codes, Z01, Z02 and Z03
are specified in per unit on system MVA base and winding "n" voltage base.

Connection Codes Introduced in PSS®E-33

For all two-digit connection codes for two- and three-winding transformers, CZ0 may
be specified as one of the following values:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
151
Sequence Data File Zero Sequence Transformer Data

• 1 for per unit on system MVA base and winding "n" voltage base

• 2 for per unit on a specified MVA base and winding "n" voltage base

These are the same units dictated by CZ values 1 and 2 on the transformer data record
of the Power Flow Raw Data File.
CZG The grounding impedance data I/O code defines the units in which the impedance val-
ues Zg1, Zg2, Zg3 and Znutrl are specified. In specifying these impedances, the wind-
ing base voltage values are always the nominal winding voltages (NOMV1, NOMV2
and NOMV3) that are specified on the third, fourth and fifth records of the Transformer
Data block in the Power Flow Raw Data File. If no value for NOMVn is specified, the
winding "n" voltage base is assumed to be identical to the winding "n" bus base volt-
age.

Legacy Connection Codes

For those connection codes that existed prior to PSS®E-33, CZG must be specified as 1.

• For two-winding transformers, these are connection codes 1 through 9;

• For three-winding transformers, these are connection codes 1 through 6, as well as

the three digit connection codes.

• For two-winding transformers with legacy connection codes 2, 3 and 9, Zg1 is spec-
ified in per unit on system MVA base and winding voltage base.

• For two-winding transformers with connection codes 5 through 8, Zg1 is specified

in per unit on system MVA base and winding voltage base.

• For two-winding transformers with connection code 8, Zg2 is specified in per unit
on system MVA base and winding 2 voltage base.

• For three-winding transformers with legacy connection code 1, Zg1 is specified in

per unit on system MVA base and winding 1 voltage base.

• For three-winding transformers with legacy connection code 5, Zg2 is specified in

per unit on system MVA base and winding 2 voltage base.

Connection Codes Introduced in PSS®E-33

For all two-digit connection codes for two- and three-winding transformers, CZG may
be specified as one of the following values:

• 1 for per unit on system MVA base and winding voltage base

• 2 for per unit on a specified MVA base and winding voltage base

• 3 for ohms

For three winding transformers, Zg1 is on SBASE12, Zg2 on SBASE23, Zg3 on SBASE31,
and Znutrl on SABSE12.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
152
Sequence Data File Zero Sequence Transformer Data

For CZG values of 1 and 2, these are the same units dictated by CZ values 1 and 2 on
the transformer data record of the Power Flow Raw Data File
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 and 11 through 23. They
define the following zero sequence connections that are shown in Section Two Wind-
ing Transformer Zero Sequence Network Diagrams and Connection Codes.

1, 11 series path, no ground path.

2, 12 no series path, ground path on Winding 1 side.

3, 13 no series path, ground path on Winding 2 side.

4, 14 no series or ground paths.

5, 15 series path, ground path on Winding 2 side (normally only used as part of a
three-winding transformer).

6, 16 no series path, ground path on Winding 1 side, earthing transformer on Winding

2 side.

7, 17 no series path, earthing transformer on Winding 1 side, ground path on Winding

2 side.

8, 18 series path, ground path on each side.

9, 19 series path on each side, ground path at the junction point of the two series
paths.

20 series path on each side, ground path at the junction point of the two series paths;
wye grounded - wye grounded core type transfromer

21 series path, no ground path; wye grounded - wye grounded non core type auto
transfromer

22 series path, no ground path; wye - wye ungrounded core type auto transfromer

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 Wind-
ing 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 Section
5.5.6, Three Winding Transformer Zero Sequence Network Diagrams and Connection
Codes.

Alternatively, several common zero sequence three-winding transformer connection

combinations may be specified using the single digit values 1 through 6. These are
defined the zero sequence transformer connections.

The following ' single digit three-winding connection codes are available, where the
connection codes of the three two-winding transformers comprising the three-wind-
ing transformer are shown in parenthesis in winding number order:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
153
Sequence Data File Zero Sequence Transformer Data

1, 11 series path in all three windings, Winding 1 ground path at the star point bus
(5-1-1).

2, 12 series path in Windings 1 and 2, Winding 3 ground path at the star point bus
(1-1-3).

3, 13 series path in Winding 2, ground paths from windings one and three at the star
point bus (3-1-3).
4, 14 no series paths, ground paths from all three windings at the star point bus
(3-3-3).

5, 15 series path in windings one and three, ground path at the Winding 2 side bus
(1-2-1).

6, 16 series path in all three windings, no ground path (1-1-1).

17 series path in Windings 1 and 2, Winding 3 ground path at the star point bus; wye
grounded - wye grounded - delta auto transfromer

18 series path in Windings 1 and 2, no ground path in Winding 3;wye - wye - delta
ungrounded neutral auto transfromer

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 trans-
formers.

CC = 14 by default
RG1, XG1 Zero sequence grounding impedance on for an impedance grounded transformer.

This data is specified in units specified by CZG.

Refer zero sequence network diagrams for each connection code for specifying this
value.

RG1 = 0.0 and XG1 = 0.0 by default

From two winding transformers connection codes ZG1=RG1+jXG1 is interpreted as:

• ZG1 is grounding impedance of winding 1 when CC>9

• ZG1 is grounding impedance of winding 1 when CC=2

• ZG1 is grounding impedance of winding 2 when CC=3

• ZG1 is grounding impedance at winding 2 bus when CC=5,6

• ZG1 is grounding impedance at winding 1 bus when CC=7,8

• ZG1 is grounding impedance at star point of zero-sequence network T-model when

CC=9
From three winding transformers connection codes ZG1=RG1+jXG1 is interpreted as:

• ZG1 is grounding impedance of winding 1 when CC are two digits, like, CC=12

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
154
Sequence Data File Zero Sequence Transformer Data

• ZG1 is grounding impedance at star point of zero-sequence network T-model when

CC=1 or User Code Digit=5

• ZG1 is grounding impedance of winding 1 when CC=2 or user code digit is 2.

• ZG1 is grounding impedance of winding 2 when CC=3 or user code digit is 3.

R01, X01 Refer zero sequence network diagram for each connection code for specifying this
value. This value could be:

• Two winding transformer: Z01 is equal to the transformer's zero sequence leakage
impedance. Z01 is equal to the transformer's positive sequence impedance by de-
fault.

• Three winding transformers and connection codes CC=11 and higher: Z01 is equal
to the transformer's winding 1 to winding 2 zero sequence impedance. Z01 is equal
to the transformer's winding 1 to winding 2 positive sequence impedance by de-
fault.

• For three winding transformers and connection codes CC=1 through 9 and User
Code: Z01 is equal to the transformer's winding 1 star-circuit equivalent zero se-
quence impedance. is equal to the transformer's winding 1 star-circuit equivalent
positive sequence impedance by default.

This data is specified in units specified by CZ0.

RG2, XG2 Zero sequence grounding impedance on winding 2 for an impedance grounded trans-
former. This data is applicable for connection codes CC=11 and higher.

This data is specified in units specified by CZG.

Refer zero sequence network diagram for each connection code for specifying this
value.

RG2 = 0.0 and XG2 = 0.0 by default

R02, X02 Refer zero sequence network diagram for each connection code for specifying this
value. This value could be:

• For two winding transformer:

Refer zero sequence network diagram for each connection code for specifying Z02
value. R02 = 0.0 and X02 = 0.0 by default.

• For three winding transformer and connection codes CC=11 and higher:

Z02 is equal to the transformer's winding 2 to winding 3 zero sequence impedance.

Z02 is equal to the transformer's winding 2 to winding 3 positive sequence imped-

ance by default.

• For three winding transformer and connection codes CC=1 through 9 and User
Code: Z02 is equal to the transformer's winding 2 star-circuit equivalent zero se-
quence impedance. Z02 is equal to the transformer's winding 2 star-circuit equiva-
lent positive sequence impedance by default.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
155
Sequence Data File Zero Sequence Transformer Data

This data is specified in units specified by CZ0.

RG3, XG3 Zero sequence grounding impedance on winding 3 for an impedance grounded trans-
former. This data is applicable for connection codes CC=11 and higher. This data is
specified in units specified by CZG.

Refer zero sequence network diagram for each connection code for specifying this
value. RG3 = 0.0 and XG3 = 0.0 by default.
R03, X03 Refer zero sequence network diagram for each connection code for specifyingthis val-
ue. This value could be:

• For three winding transformer and connection codes CC=11 and higher: Z03 is equal
to the transformer's winding 3 to winding 1 zero sequence impedance.

Z03 is equal to the transformer's winding 3 to winding 1 positive sequence impedance

by default.

• For three winding transformer and connection codes CC=1 through 9: Z03 is equal
to the transformer's winding 3 star-circuit equivalent zero sequence impedance.

Z03 is equal to the transformer's winding 3 star-circuit equivalent positive sequence

impedance by default. This data is specified in units specified by CZ0.
RNUTRL, XNUTRL Zero sequence common neutral grounding impedance. This data is applicable for con-
nection codes CC=11 and higher.

This data is specified in units specified by CZG.

Refer zero sequence network diagram for each connection code for specifying this
value.

RNUTRL = 0.0 and XNUTRL = 0.0 by default.

Refer Sections 5.5.4, 5.5.5 and 5.5.6 for transformer winding connections, zero sequence network diagrams
and connection codes.

In specifying zero sequence impedances for three-winding transformers, note that winding impedances are
required, and that the zero sequence impedances return to the default value of the positive sequence wind-
ing impedances. Recall that, in specifying positive sequence data for three-winding transformers (refer to
Transformer Data), measured impedances between pairs of buses to which the transformer is connected,
not winding impedances, are required. PSSE converts the measured bus-to-bus impedances to winding im-
pedances that are subsequently used in building 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 i’s 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 encoun-

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
156
Sequence Data File Zero Sequence Transformer Data

tered, all data pertaining to the out-of-service winding (i.e., pertaining to the two-winding transformer con-
taining 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 user’s 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.

Figure 4.4. Two-Winding Transformer Positive Sequence Connections

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
157
Sequence Data File Zero Sequence Switched Shunt Data

Figure 4.5. Three-Winding Transformer Positive Sequence Connections

4.9. 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, ID, BZ1, BZ2, ... BZ8

I Bus number; bus I must be present in the working case with positive sequence
switched shunt data.
ID One or two character identifier of the switched shunt at bus I for which the data is
specified by this record.

ID = '1' by default
BZi Zero sequence admittance increment for each of the steps in block i; entered in MVAR
at 1 pu unit voltage.

BZ i = 0.0 by default

Data specified on zero sequence switched shunt data records must be coordinated with the corresponding
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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
158
Sequence Data File Zero Sequence Fixed Shunt Data

Activity RESQ generates an alarm for 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 non-zero.

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.

4.10. Zero Sequence Fixed Shunt Data

Zero sequence fixed shunts are entered into the working case in zero sequence fixed shunt data records in
the Sequence Data File. Each zero sequence fixed shunt data record has the following format:

I, ID, GSZERO, BSZERO

I Bus number; bus I must be present in the working case.

ID One or two character identifier of the fixed shunt at bus I for which the data is specified
by this record.

ID = '1' by default
GSZERO Active component of zero sequence admittance to ground to represent this fixed shunt
at bus I; entered in MW at 1 pu voltage.
BSZERO Reactive component of zero sequence admittance to ground to represent this fixed
shunt at bus I; entered in MVAR at 1 pu voltage.

For any fixed shunt for which either no such data record is specified or GSZERO and BSZERO are both speci-
fied as 0.0, no zero sequence ground path is modeled for this fixed shunt. The zero sequence ground tie cre-
ated by a grounded transformer winding is automatically added to whatever zero sequence fixed shunt and
shunt load 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 fixed shunt data input is terminated with a record specifying a bus number of zero.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
159
Sequence Data File Induction Machine Sequence Data

4.11. Induction Machine Sequence Data

Each zero sequence induction machine data has the following format:

I, ID, CZG, GRDFLG, ILR2IR_SUB, R2X_SUB, ZR0, ZX0, ZRG, ZXG, ILR2IR_TRN, R2X_TRN,
ILR2IR_NEG, R2X_NEG

I Bus number; bus I must be present in the working case as an induction machine bus.
ID One or two character identifier of the induction machine at bus I for which the data
is specified by this record.

ID = '1' by default
CZG Units of grounding impedance (ZRG and ZXG) values, = 1 for pu (on bus voltage base
and MBASE), = 2 for Ohms
GRDFLG 1 for grounded machine, 0 for ungrounded machine (Most commonly, stator winding
is either delta connected or star connected with the neutral isolated.) GRDFLG=0 by
default.
ILR2IR_SUB Ratio of positive sequence subtransient locked rotor current to rated current.
R2X_SUB Ratio of positive sequence subtransient resistance to reactance. This is used only when
positive sequence impedance is calculated using ILR2IR_SUB.

R2X_SUB = 0.0 by default

ZR0 Zero sequence resistance; entered in pu on machine base (i.e., on bus voltage base
and MBASE).

ZR0 = 0.0 by default

ZX0 Zero sequence reactance; entered in pu on machine base (i.e., on bus voltage base
and MBASE). Induction machine is isolated in zero sequence if the stator winding is
either delta connected or star connected with the neutral isolated.

For a star connected stator winding with an earthed neutral, zero sequence imped-
ance is much smaller than motor starting impedance (subtransient or transient) and
does not vary with time. Induction machine zero sequence impedance can be assumed
equal to the stator ac resistance

ZX0 = ZXPPDV by default depending on generator impedance option

ZRG Grounding resistance; entered in pu on machine base (i.e., on bus voltage base and
MBASE) when CZG=1 or in ohms when CZG=2.

ZRG = 0.0 by default

ZXG Grounding reactance; entered in pu on machine base (i.e., on bus voltage base and
MBASE) when CZG=1 or in ohms when CZG=2.

ZXG = 0.0 by default

ILR2IR_TRN Ratio of positive sequence transient locked rotor current to rated current.
R2X_TRN Ratio of positive sequence transient resistance to reactance. This is used only when
positive sequence impedance is calculated using ILR2IR_TRN.

R2X_TRN = 0.0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
160
Sequence Data File Induction Machine Sequence Data

ILR2IR_NEG Ratio of negative sequence locked rotor current to rated current.

R2X_NEG Ratio of negative sequence resistance to reactance. This is used only when negative
sequence impedance is calculated using ILR2IR_NEG.

R2X_NEG = 0.0 by default

Application Notes:

Positive (ZP) and negative (ZN) sequence impedances are calculated as below.

1. When locked rotor current to rated current sequence data is provided, depending on activity "reactance"
option used:

2. When locked rotor current to rated current sequence data is not provided:

3. When ILR2IR_NEG and R2X_NEG are not provided, ZN=ZP.

Figure 4.6. Induction Machine Sequence Network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
161
Sequence Data File Non-Conventional Source - Fault Con-
tribution Characteristics Data

4.12. Non-Conventional Source - Fault Contribution

Characteristics Data
The fault contribution from non-conventional sources like Type 3 and Type 4 Wind Generators and Photo
Voltaic Sources is very much dependent on the voltage source converters and their controls. This is also true
with any other inverter based resources (IBRs) connected to the grid. The IBRs fault contributions is modeled
with following two different characteristics.

• Time dependent fault current contribution (TI Characteristics)

A source injects short circuit current and is independent of its terminal voltage. The amount of fault cur-
rent contribution is determined from its pre-fault loading condition and TI characteristics. For example,
activities ASCC and SCMU calculates momentary fault currents, so the fault current contribution specified
at Time=0.0 is used.

The active and reactive components of short circuit current, CiP and CiQ, are dependent on the pre-fault
active power of the source. Considering rated active power and power factor, specify C iP and CiQ in per
unit on rated voltage and base MVA of the source. The components CiP and CiQ do not include the source
pre-fault loadings.

• Voltage dependent fault current contribution (VI Characteristics)

A source injects short circuit current which is a function of its terminal voltage and mode of operation
[active power or reactive power priority]. The amount of fault current contribution is determined by iter-
ating over the positive sequence bus voltage and desired current as per its characteristics and pre-fault
loading condition. For faults at source bus, the fault contribution will be maximum and as fault moves
away from its bus the contribution will decrease. If the fault is farther enough such that its terminal voltage
remains same as pre-fault voltage or within dead-band voltage limits, the source will contribute only pre-
fault loading condition currents to the fault.

The active and reactive components of short circuit current, CiP and CiQ, are dependent on the pre-fault
active power of the source. Considering rated active power and power factor, specify C iP and CiQ in per
unit on rated voltage and base MVA of the source. The components CiP and CiQ do not include the source
pre-fault loadings.

As shown in Figure 4.7, the fault contribution characteristics may have up to 20 points. A minimum of one
point is required. This characteristics could be defined separately for each postive and negative sequence
components. Points are specified six per line in each source data block. As many records as needed (with
six points per record) are entered. The end of data for a source is specified by specifying an additional point
with the three values defining the point all specified as 0.0.

Each data record has following format:

NAME, CHRTYP, T1, C1P, C1Q, T2, C2P, C2Q, ... T6, C6P, C6Q
T7, C7P, C7Q, T8, C8P, C8Q, ... T12, C12P, C12Q
.
.
Tn, CnP, CnQ, 0.0, 0.0, 0.0

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
162
Sequence Data File Non-Conventional Source - Fault Con-
tribution Characteristics Data

NAME The non-blank alphanumeric identifier assigned to table. Each Fault Contribution Char-
acter- istics table must have unique NAME. The NAME may be up to 12 characteristics
and may contain any combination of blanks, uppercase letters, numbers and special
characters, but the first character must not be a minus sign. The NAME must be en-
closed in single or double quotes if it contains any blanks or special characters.

No default allowed.
CHRTYP Three character Fault Contribution Characteristics Type.

CHRTYP = 'TIM' for Time dependent fault current contribution

CHRTYP = 'VLT' for Voltage dependent fault current contribution

No default allowed.
Ti Time in seconds when curve is for Time dependent fault current contribution.

Source Terminal (Bus) Voltage in PU when curve is for Voltage dependent fault current
contribution.

Ti values must be specified in ascending order.

CiP The active component of the fault current contribution in pu on rated (1.0 pu) current
and rated voltage base (1.0 pu) at Ti.
CiQ The reactive component of fault current contribution in pu on rated (1.0 pu) current
and rated voltage base (1.0 pu) at Ti. When supplying reactive power, specify CiQ as
positive.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
163
Sequence Data File Non-Conventional Source - Fault Con-
tribution Characteristics Data

Figure 4.7. Non-conventional Source Fault Contribution Characteristics

Application Notes - The fault current (CiP+jCiQ) is limited to possible maximum amount of fault current con-
tribution, which is generally upto 1.3 pu. Refer Program Applicate Guide, Volume 1, Chapter "Fault Analysis"
for technical details.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
164
Sequence Data File Non-Conventional Source - Generator
Data

4.13. Non-Conventional Source - Generator Data

When a source in the network is not a conventional synchronous machine, but a non-conventional source
which is typically connected to the grid though voltage source converters, viz.,Type 4 WTG or PV, then the
fault contributions from such a source is specified using this data record. For these sources the fault response
is controlled by its converter control characteristics.

When a generator has non-conventional source data specified, its "generator sequence data" record, even
if present, is ignored.

This fault current contribution and its sequence network model is shown in Figure 4.8.

Figure 4.8. Non-conventional Source Sequence Network

Each data record has following format:

I, ID, CHRTYP, POSTBL, NEGTBL, IFMAX, DBVMIN, DBVMAX

I Bus number; bus I must be present in the working case as a generator bus.

No default is allowed
ID One or two character source identifier of the generator bus I for which the data is
specified by this record.

ID = '1' by default
CHRTYP Three character Fault Contribution Characteristics Type.

CHRTYP = 'TIM' for Time dependent fault current contribution

CHRTYP = 'VLT' for Voltage dependent fault current contribution

CHRTYP = 'TIM' by default

POSTBL Previously defined Fault Contribution Characteristics table name used to determine
fault current contribution.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
165
Sequence Data File Non-Conventional Source - Generator
Data

The POSTBL table name must be defined in "Non-Conventional Source Fault Contribu-
tion Characteristics Data" records.

No default allowed.
NEGTBL Previously defined Fault Contribution Characteristics table name used to determine
negative sequence impedance.

The NEGTBL table name must be defined in "Non-Conventional Source Fault Contribu-
tion Characteristics Data" records.

NEGTBL='' (blank) by default meaning this generator is treated as open circuit in neg-
ative sequence.

It is allowed to specifiy NEGTBL to be same as POSTBL.

IFMAX PU maximum total current magnitude allowed during a fault.

IFMAX = 1.3 pu by default

DBVMIN PU dead-band minimum and maximum voltage limits at the source bus.

DBVMAX In this voltage dead-band, the source is considered operating in normal state with ac-
tive power priority. Outside of this voltage dead-band, the source is considered oper-
ating with reactive power priority.

When DBVMIN=DBVMAX these limits are ignored and the source is considered oper-
ating with reactive power priority.

DBVMIN=0.9 pu be default

DBVMAX=1.1 pu be default

Application Notes:

• The characteristics type (CHRTYP) of POSTBL and NEGTBL tables must be the same. The names of POSTBL
and NEGTBL could be different.

• Two data record groups “NCS Fault Contribution Characteristics Data” and “NCS – Generator Data” are used
to specify NCS fault contributions. They provide following benefits.

• Ability to specify same “Fault Contribution Characteristics Data” to multiple sources.

• Ability to specify different fault contribution characteristics for positive sequence and negative se-
quence.

• Ability to specify voltage dependent fault contribution characteristics.

• Ability to specify voltage limits during which NCS contributes only pre-fault loading currents to the fault.

• Ability to specify maximum fault current contribution from NCS.

• Sequence file formats of version 35.0.x through 35.1.x and version 35.2.x are different. Version 36.0 [and
later] format is same as version 35.2.x format.

• For previous version 35.x sequence file, only version 35.2.x format sequence files are written.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
166
Sequence Data File Non-Conventional Source - Generator
Data

• For previous version 34.x sequence file, only positive sequence time dependent fault contribution charac-
teristics are written.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
167
Sequence Data File Application Notes - Transformers in the
Zero Sequence

4.14. Application Notes - Transformers in the Zero

Sequence
®
The fault analysis activities of PSS E handle the zero sequence representation of two- and three-winding
transformers automatically. Other nonstandard transformer types must be reduced to combinations of two-
winding transformers, three-winding transformers, and/or branches by the use of dummy buses and equiv-
alent circuits. Note again that the introduction of buses and branches needed for the modeling of nonstan-
dard transformers is accomplished by their addition to the positive sequence network via activities READ,
TREA, or RDCH, or the [Spreadsheet].

Transformer zero sequence data is entered into the working case by means of zero sequence transformer data
records in the Sequence Data File. Transformers are represented in the zero sequence as per their connection
codes. The establishment of the connections and ground paths is handled automatically on the basis of the
impedances and connection code entered and the winding turns ratios.

Zero sequence transformer default data is such that the transformer appears as an open circuit in the zero
sequence network. Therefore, zero sequence data must be entered for all grounded transformers.

Connection codes do not indicate the inherent phase shift due to the relative connection of delta and wye
windings. If this phase shift is to be represented, it must be specified in the positive sequence power flow
data.

Virtually any impedance grounded two-winding transformer may be modeled automatically by specifying
its winding and grounding impedances along with the appropriate connection code. Many three-winding
transformer configurations may be handled in a similar manner; others require the addition of 3Zg or other
impedances to one or more of the winding impedances.

The winding numbers specified in zero sequence network diagrams are not directly associated with the nom-
inal voltage levels of those windings. They are associated with corresponding winding connection only.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
168
Sequence Data File Auto Transformer Equivalent Circuit

4.14.1. Auto Transformer Equivalent Circuit

The equivalent circuit impedance of an auto transformer can be determined from a short circuit test per-
formed as shown in Figure 4.9.

Figure 4.9. Auto-transformer Equivalent Circuit

Auto transformer ohmic impedance measured across circuit 1 when circuit 2 is short circuited (winding im-
pedance) as shown in (b) and (c) is given by:

Auto transformer turns ratio are defined as:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
169
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

4.14.2. Two Winding Transformer Zero Sequence Networks

*
NOTE: * in grounding impedance notations (like Zg1 ) in zero seq/uence network diagrams means PSS®E will
automatically multiply that grounding impedance by a factor 3.

CC=1 and CC=11

Series Path, No Ground Path

Figure 4.10. YNyn transformer zero sequence network

Figure 4.11. YNyn with neutral impedance transformer zero sequence network
CC=11 PSS®E calculates pu Znutrl0 as below:

Set:

• R01+jX01 = Zt0

• RG1+jXG1 = Zg1

• RG2+jXG2 = Zg2

• RNUTRL+jXNUTRL = Znutrl

NOTE: When CC=1, data specified for Zg1 and Zg2 will be ignored. Hint instead use CC=11.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
170
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=2 and CC=12

No Series Path, Ground Path on Winding 1 side

Figure 4.12. YNd transformer zero sequence network

Figure 4.13. Znyn, Zny, or ZNd transformer zero sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
171
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

Figure 4.14. YNy core type transformer zero sequence network

NOTE: When CC=2, data specified for Zg1 will be used as grounding impedance of winding 1.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
172
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=3 and CC=13

No Series Path, Ground Path on Winding 2 side

Figure 4.15. Dyn transformer zero sequence network

Figure 4.16. YNzn, Yzn or Dzn transformer zero sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
173
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

Figure 4.17. Yyn core type transformer zero sequence network

NOTE: To make backward compatible, when CC=3, data specified for Zg1 will be used as grounding
impedance of winding 2. Hint instead use CC=13 and specify Zg2.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
174
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=4 and CC=14

No Series Path, No Ground Path

Figure 4.18. Yy, Yd, Dy, Dd, Yyn or YNy transformer zero sequence network

Figure 4.19. Ya ungrounded auto transformer zero sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
175
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=5 and CC=15

Series Path, Ground Path on Winding 2 side

Figure 4.20. CC=5 or CC=15 zero sequence network

NOTE: To make backward compatible, when CC=5, data specified for Zg1 will be used as grounding
impedance at winding 2 side. Hint instead use CC=15 and specify Zg2.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
176
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=6 and CC=16

Wye grounded - delta with an earting transformer

No Series Path, Ground Path on Winding 1 side, Earthing transformer on Winding 2 Side

Figure 4.21. YNd transformer with Zigzag or YNd earthing transformer on winding 2
side zero sequence network

Note: Activity IECS applies impedance correction factors to transformer impedances. When main and
earthing transformers are modeled separately with CC=2, impedance correction factors are applied
to both main and earthing transformers. This is incorrect. The impedance correction factors should
not applied to earthing transformer. So model main and earthing transformers correctly using CC=6
or CC=16.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
177
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

Figure 4.22. YNzn or Dzn core type transformer zero sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
178
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=7 and CC=17

Delta with an earting transformer - Wye grounded

No Series Path, Earting transformer on Winding 1 Side, Ground Path on Winding 2 side

Figure 4.23. Dyn transformer with Zigzag or YNd earthing transformer on winding 1
side zero sequence network
No Series Path, Ground Path on Winding 2 side through core magnetizing impedance

Figure 4.24. ZNyn or ZNd core type transformer zero sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
179
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=8 and CC=18

Wye grounded - wye grounded three legged core type auto transformer

Series Path, Ground Path each side

Figure 4.25. YNa core type auto transformer zero sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
180
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=8 CC=18

PSS®E calculates pu values as:

Calculate:

Z10, Z20, ZM0 from equations as in CC=18

Set:

- R01+jX01 = ZM0

- RG1+jXG1 = Z10

- RG2+jXG2 = Z20

CC=18

Set:

- R01+jX01 = Zto

- R02+jX02 = ZphiC

- RG2+jXG2 = Zg2

Where:

ZphiC is the magnetising (exciting) impedance as measured on the Common Winding with series winding on
the same core open circuited and zero sequence voltage is applied to Terminal 2.

Refer auto transformer equivalent circuit represention description for definition of N and Zto.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
181
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=9 and CC=19

• Series Path on each side, Ground Path at the junction point of the two series paths

• Wye grouned - wye grounded three legged core type auto transformer

Figure 4.26. YNa core type auto transformer zero sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
182
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=9 CC=19

Set:
Calculate:
- R01+jX01 = Zto
Z1S, Z2S, ZSG from equations as in CC=19
- R02+jX02 = ZphiC

Set: - RG2+jXG2 = Zg2

- R01+jX01 = Z1S
PSS®E calculates pu values as:
- R02+jX02 = Z2S

- RG1+jXG1 = ZSG

Where:

ZphiC is the magnetising (exciting) impedance as measured on the Common Winding with series winding on
the same core open circuited and zero sequence voltage is applied to Terminal 2.

Refer auto transformer equivalent circuit representation description for definition of N and ZCS.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
183
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=20

• Series Path on each side, Ground Path at the junction point of the two series paths

• Wye grouned - wye grounded core type transformer

Figure 4.27. YNyn with or without neutral impedance core type transformer zero
sequence network

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
184
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

Set: PSS®E calculates pu values as:

- R01+jX01 = Zt0

- R02+jX02 = Zphi0

- RG1+jXG1 = Zg1

- RG2+jXG2 = Zg2

- RNUTRL+jXNUTRL = Znutrl

Where:

Zphi1 is the magnetising (exciting) impedance as measured on Winding 1 with winding 2 on the same core
open circuited and zero sequence voltage is applied to Winding 1.

Zphi2 is the magnetising (exciting) impedance as measured on Winding 2 with winding 2 on the same core
open circuited and zero sequence voltage is applied to Winding 2.

Zphi0 = Zphi1 or Zphi2, if Zphi1 = Zphi2

Zphi0 = 0.5(Zphi1 + Zphi2) if Zphi1 ≠ Zphi2

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
185
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=21

Figure 4.28. YNa auto transformer zero sequence network

Set: PSS®E calculates pu values as:

- R01+jX01 = Zto

- RG2+jXG2 = Zg2

Refer auto transformer equivalent circuit represention description for definition of N and Zto.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
186
Sequence Data File Two Winding Transformer Zero Se-
quence Networks

CC=22

Wye - wye ungrounded core type auto transformer

Figure 4.29. Ya ungrounded core type auto transformer zero sequence network
Set: PSS®E calculates pu values as:

- R01+jX01 = ZphiS

Where:

ZphiS is the magnetising (exciting) impedance as measured on the Series Winding with all the other windings
on the same core open circuited and zero sequence voltage is applied to Terminal 1.

Refer auto transformer equivalent circuit representation description for definition of N.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
187
Sequence Data File Three Winding Transformer Zero Se-
quence Network

4.14.3. Three Winding Transformer Zero Sequence Network

Note:

Impedance Notations used in the Zero Sequence Networks:

0
Z12 = Zero sequence leakage impedance between winding 1 and winding 2
0
Z23 = Zero sequence leakage impedance between winding 2 and winding 3
0
Z31 = Zero sequence leakage impedance between winding 3 and winding 1

Zg1 = Winding 1 grounding impedance

Zg2 = Winding 2 grounding impedance

Zg3 = Winding 3 grounding impedance

Znutrl = Neutral grounding impedance

The three Winding transformer is modeled as T-model in zero sequence network. The impedances of this T-
model are calculated from transformer test report in-between winding impedances as below.
0 0 0 0
Zt1 = 0.5(Z12 + Z31 - Z23 )
0 0 0 0
Zt2 = 0.5(Z12 + Z23 - Z31 )
0 0 0 0
Zt3 = 0.5(Z23 + Z31 - Z12 )

where:
0
Zt1 = Zero sequence impedance between winding 1 and star point
0
Zt2 = Zero sequence impedance between winding 2 and star point
0
Zt3 = Zero sequence impedance between winding 3 and star point

The in-between winding impedances can be calculated from T-model impedances as below:

Z12 = Z1 + Z2

Z23 = Z2 + Z3

Z31 = Z3 + Z1

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
188
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=1 and CC=11 (511)

Series path in all three Windings, Winding 1 ground path at star point bus

Figure 4.30. YNynyn with magnetising impedance modelled transformer zero

sequence network
CC=1 or CC=511 CC=11

Calculate:
Set:
0 0 0
Z1 , Z 2 , Z3 from equations as in CC=11 0
- R01+jX01 = Z12
0
Set (pu): - R02+jX02 = Z23
0 0
- R01+jX01 = Z1 - R03+jX03 = Z31
0
- R02+jX02 = Z2 - RG1+jXG1 = Zg1
0
- R03+jX03 = Z3
PSS®E calculates pu values as:
- RG1+jXG1 = Zg1 0 0 0
- Zt1 , Zt2 , Zt3
0 0
Assigned: - Z1 = Zt1
0 0 0
- Z1 = R01+jX01 - Z2 = Zt2
0 0 0
- Z2 = R02+jX02 - Z3 = Zt3
0 0
- Z3 = R03+jX03 - Zg = 3(RG1+jXG1)

PSS®E automatically multiplies grounding imped-

ance by 3.
0
- Zg = 3(RG1+jXG1)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
189
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=2 and CC=12 (113)

Series path in Windings 1 and 2, Winding 3 ground path at star point bus

(For YNad, refer CC=17)

Figure 4.31. YNynd transformer zero sequence network

CC=2 or CC=113 CC=12 Calculated (pu):

Calculate: Set: (with Znutrl)

0 0 0 0
Zt1 , Z2 , Z3 from equations - R01+jX01 = Z12
as in CC=12 0
- R02+jX02 = Z23
0
Set (pu): - R03+jX03 = Z31
0
- R01+jX01 = Zt1 - RG1+jXG1 = Zg1
0
- R02+jX02 = Z2 - RG2+jXG2 = Zg2
0
- R03+jX03 = Z3
Calculated (pu):
- RG1+jXG1 = Zg3
(no Znutrl)
Assigned: 0 0 0
- Zt1 , Zt2 , Zt3
0
- Z1 = R01+jX01 0 0
- Z1 = Zt1 + 3Zg1
0
- Z2 = R02+jX02 0 0
- Z2 = Zt2 + 3Zg2
0
- Z3 = R03+jX03+ 3Zg3 0 0
- Z3 = Zt3

Note: When CC=2 or CC=113, Zg3 assigned is a fictious grounding impedance derived from T-model.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
190
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=3 and CC=13 (313)

Series path in Windings 2, ground paths from Windings 1 and 3 at star point bus

Figure 4.32. Dynd transformer zero sequence network

CC=3 or CC=313 CC=13

Calculate: Set:
0 0 0 0
Z1 , Z 2 , Z3 from equations as in CC=13 - R01+jX01 = Z12
0
Set (pu): - R02+jX02 = Z23
0 0
- R01+jX01 = Z1 - R03+jX03 = Z31
0
- R02+jX02 = Z2 - RG2+jXG2 = Zg2
0
- R03+jX03 = Z3
Calculated (pu):
- RG1+jXG1 = Zg1 0 0 0
- Zt1 , Zt2 , Zt3
Assigned: 0 0
- Z1 = Zt1
0
- Z1 = R01+jX01 + 3Zg1 0 0
- Z2 = Zt2 + 3(RG2+jXG2)
0
- Z2 = R02+jX02 0 0
- Z3 = Zt3
0
- Z3 = R03+jX03

Note: When CC=3 or CC=313, Zg1 assigned is a fictious grounding impedance derived from T-model.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
191
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=4 and CC=14 (333)

No series paths, ground paths from all three Windings at the star point bus

Figure 4.33. Ddd, Ddy, Dyd, Dyy, Ydd, Ydy, Yyd or Yyy transformer zero sequence
network
CC=4 or CC=333 CC=14

Calculate: Set:
0 0 0 0
Z1 , Z 2 , Z3 from equations as in CC=14 - R01+jX01 = Z12
0
Set (pu): - R02+jX02 = Z23
0 0
- R01+jX01 = Z1 - R03+jX03 = Z31
0
- R02+jX02 = Z2
Calculated (pu):
0
- R03+jX03 = Z3 0 0 0
- Zt1 , Zt2 , Zt3
Assigned: 0 0
- Z1 = Zt1
0
- Z1 = R01+jX01 0 0
- Z2 = Zt2
0
- Z2 = R02+jX02 0 0
- Z3 = Zt3
0
- Z3 = R03+jX03

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
192
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=5 and CC=15 (121)

Series path in Windings 1 and 3, ground path at Winding 2 side bus

Figure 4.34. Dynd auto transformer zero sequence network

CC=5 or CC=121 CC=15

Calculate: Set:
0 0 0 0
Z1 , Z 2 , Z3 from equations as in CC=15 - R01+jX01 = Z12
0
- R02+jX02 = Z23
Set (pu):
0
0
- R03+jX03 = Z31
- R01+jX01 = Z1
0
- RG2+jXG2 = Zg2
- R02+jX02 = Z2
0
- R03+jX03 = Z3 Calculated (pu):
0 0 0
- RG2+jXG2 = Zg2 - Zt1 , Zt2 , Zt3
0 0
- Z1 = Zt1
Assigned:
0 0
0
- Z2 = Zt2
- Z1 = R01+jX01
0 0
0
- Z3 = Zt3
- Z2 = R02+jX02
0
0
- Zg = 3(RG2+jXG2)
- Z3 = R03+jX03

Calculated (pu)
0
- Zg = 3(RG2+jXG2)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
193
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=6 and CC=16 (111)

Series path in all three Windings, no ground path

Figure 4.35. YNynyn transformer zero sequence network

CC=6 or CC=111 CC=16 Calculated (pu):

Calculate: Set: (with Znutrl)

0 0 0 0 0 0 0
Z1 , Z 2 , Z3 from equations as - R01+jX01 = Z12 - Calculate Zt1 , Zt2 , Zt3
in CC=16 0
- R02+jX02 = Z23
0
Set (pu): - R03+jX03 = Z31
0
- R01+jX01 = Z1 - RG1+jXG1 = Zg1
0
- R02+jX02 = Z2 - RG2+jXG2 = Zg2
0
- R03+jX03 = Z3 - RG3+jXG3 = Zg3

Assigned: Calculated (pu):

0
- Z1 = R01+jX01 (without Znutrl)
0 0 0 0
- Z2 = R02+jX02 - Zt1 , Zt2 , Zt3
0 0 0
- Z3 = R03+jX03 - Z1 = Zt1 + 3 (RG1+jXG1)
0 0
- Z2 = Zt2 + 3 (RG2+jXG2)
0 0
- Z3 = Zt3 + 3 (RG3+jXG3)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
194
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=17
Series path in Windings 1 and 2, Winding 3 ground path at star point bus

(For wye grounded - wye grounded - delta non auto transformer, refer CC=12)

Figure 4.36. Ynad (grounded) auto transformer zero sequence network

CC=17 Calculated (pu):

Set:
0
- R01+jX01 = Z12
0
- R02+jX02 = Z23
0
- R03+jX03 = Z31

- RG2+jXG2 = Zg2

For auto transformers with one/two neutral connections taken out, IEEE Std C57.12.90-2015 standard pro-
vides the test procedure and T-model impedance calculations from that test data.

Figure 4.37. Equivalent zero sequnce network for a transformer with two externally
o
available neutrals and 0 phase shift between windings 1 and 2
Following four test results are used to determine zero sequence network:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
195
Sequence Data File Three Winding Transformer Zero Se-
quence Network

• Test 1 - Apply voltage winding 1 and its neutral. All other windings are open-circuited. The measured zero
sequence is represented by Z1N0.

• Test 2 - Apply voltage winding 1 and its neutral. Short Winding 2 and its neutral. All other windings may
be open-circuited or shorted. The measured zero sequence is represented by Z 1Ns.

• Test 3 - Apply voltage winding 2 and its neutral. All other windings are open-circuited. The measured zero
sequence is represented by Z2N0.

• Test 4 - Apply voltage winding 2 and its neutral. Short Winding 1 and its neutral. All other windings may
be open-circuited or shorted. The measured zero sequence is represented by Z 2Ns.

The zero sequence network T-model impedances are calculated as below.

Set PSSE seqence data as below.

0
• R01 + j X01 = Z12 = Z1 + Z2
0
• R02 + j X02 = Z23 = Z2 + Z3
0
• R03 + j X03 = Z31 = Z3 + Z1

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
196
Sequence Data File Three Winding Transformer Zero Se-
quence Network

CC=18

Figure 4.38. Yad (ungrounded) auto transformer zero sequence network

Set:
0
- R01+jX01 = Z12
0
- R02+jX02 = Z23
0
- R03+jX03 = Z31

Calculated (pu):
0 0 0
Calculate Zt1 , Zt2 , Zt3

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
197
 Chapter 5
Optimal Power Flow Data File

5.1. Overview
The optimal power flow problem typically consists of several components: one or more objectives, a set of
available system controls and any number of system constraints. The purpose of this chapter is to present
the available controls and constraints for the optimal power flow problem statement.

The input stream to activity ROPF is an Optimal Power Flow Data File containing 17 groups of records with
each group specifying a particular type of OPF data or constraint definition required for OPF work. Any piece
of equipment for which OPF data is to be entered in activity ROPF must be represented as power flow data
in the working case. That is, activity ROPF will not accept data for a bus, generator, branch, switched shunt
or fixed shunt not contained in the working case.

All data is read in free format with data items separated 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 sections within this chapter are presented in the order in which the data categories must appear within
the PSSE OPF Raw Data File. The format of the file itself is outlined in the below figure. Each section of this
chapter fully describes the data elements associated with each data model.
Change Code

Bus Voltage Constraint Data

Adjustable Bus Shunt Data

Bus Load Data

Adjustable Bus Load Table Data

Generator Dispatch Data

Active Power Dispatch Data

Generation Reserve Data

Generation Reactive Capability Data

Adjustable Branch Reactance Data

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
198
Optimal Power Flow Data File Change Code

Piece-wise Linear Cost Data

Piece-wise Quadratic Cost Data

Polynomial and Exponential Cost Table

Period Reserve Constraint Data

Branch Flow Constraint Data

Interface Flow Constraint Data

Linear Constraint Dependency Data

Optimal Power Flow Raw Data File Structure

5.2. Change Code

The OPF data modification code indicates whether a new set of optimal power flow data records are to be
loaded into the working case, or whether the existing optimal power flow data is to be modified or appended
with updated information. This value is only used within the OPF Raw Data File.

Within the OPF Raw Data File, this record contains one data field entered as follows:

ICODE

ICODE ICODE = 0. All data within the OPF Raw Data File is treated as new data and entered
into the 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.

ICODE = 1. All data within the OPF Raw Data File is to supersede values that current-
ly 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 auto-
matically appended to the data records already within the current working case. Data
records which do correspond to an entry within the working case are simply updated
to reflect the new values.

5.3. Bus Voltage Constraint Data

OPF Bus Voltage Constraint records define lower and upper voltage limits at each bus existing within the
PSSE 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 asso-
ciated models (voltage constraints, bus shunts, loads, etc.) will not be utilized by the optimal power flow
solution process.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
199
Optimal Power Flow Data File Bus Voltage Attribute Record

5.3.1. Bus Voltage Attribute Record

The format for each OPF Bus Voltage Attribute record is:

BUS, VNMAX, VNMIN, VEMAX, VEMIN, LTYP, SLPEN

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 A bus number between 1 and 999997. The specified bus number must correspond to
a bus already defined within the power flow working case.
VNMAX The maximum bus voltage magnitude value, entered in pu. The normal and emer-
gency OPF bus voltage limits are independent of the normal and emergency bus volt-
age limits in the main network bus data. The OPF bus voltage limits may be initialized
to those of the network bus voltage limits through either the OPF bus and bus subsys-
tem spreadsheets, or through the OPF bus API commands.

VNMAX = 9999.0 by default

VNMIN The minimum bus voltage magnitude value, entered in pu.

VNMIN = -9999.0 by default

VEMAX 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. Otherwise
the normal voltage limits, as entered above, will be utilized. Refer to Impose Emer-
gency Bus Voltage Limits for more information.

VEMAX = 9999.0 by default

VEMIN The minimum emergency bus voltage magnitude value, entered in pu.

VEMIN = -9999.0 by default

LTYP 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 voltage falls outside of limits.

• Hard limit (1). Strictly enforce the specified bus voltage magnitude limits through
the use of barrier terms.

• Soft limit with a linear penalty (2). Permit bus voltages to go outside of their speci-
fied voltage magnitude limits, but penalize excursions linearly. The Soft limit penal-
ty weight, SLPEN, is used in conjunction with this penalty to indicate severity of
excursion.

• Soft limit with a quadratic penalty (3). Permit bus voltages to go outside of their
specified voltage limits, but penalize excursions along a quadratic curve. The Soft
limit penalty weight, SLPEN, is used in conjunction with this penalty to indicate
severity of excursion.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
200
Optimal Power Flow Data File Adjustable Bus Shunt Data

Refer to Section 14.7.2 Accommodating Inequality Constraints for more information

on the limit type options.

LTYP = 1 (Hard limit) by default

SLPEN The soft limit penalty weight value applied to either the linear or quadratic soft limit
penalty functions. The larger the number, the higher the penalty for voltage excursions
outside of limits.

SLPEN = 1.0 by default

5.4. Adjustable Bus Shunt Data

Adjustable Bus Shunt Records define candidate bus locations for shunt compensation. These records are
unique to the PSSE 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 PSSE 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 14.6.2 Adjustable Bus Shunt.

An individual bus may have one or more adjustable bus shunts defined, each differentiated by a unique bus
shunt identifier.

The format for each Adjustable Bus Shunt record is:

BUS, ID, BINIT, BMAX, BMIN, BCOST, STATUS, CTYP, CTBL

When entering records in the OPF Raw Data File, each field must be separated by either a space or a com-
ma 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 A bus number between 1 and 999997. The specified bus number must correspond to
an existing bus within the power flow working case.
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.
BINIT The initial additional shunt value, entered in Mvar at nominal voltage.

BINIT = 0.0 by default.

BMAX The maximum bus shunt limit, entered in Mvar. To define an initial fixed shunt com-
ponent, 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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
201
Optimal Power Flow Data File Bus Load Data

BMAX = 0.0 by default.

BMIN 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 induc-
tors or capacitors respectively.

BMIN = 0.0 by default.

BCOST 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.

BCOST = 1.0 by default.

STATUS The status switch determines whether the specified bus shunt control should be con-
sidered active or not. Only in-service bus shunts are recognized as candidates for var
control.

• In-service (1)

• Out of service (0)

STATUS = 1 (In-service) by default.

CTYP Cost curve type. This value is not currently utilized by the program.
CTBL Cost curve table number. This value is not currently utilized by the program.

5.5. Bus Load Data

Each OPF Bus Load Data record points to an Adjustable Bus Load table (Section 3.6 Adjustable Bus Load Table
Data) that, in turn, defines load limits for use in load adjustment studies (i.e., load shedding, power transfer).
These records are used in conjunction with the Minimize Adjustable Bus Loads objective function.

By default, all bus loads within the working case are initialized with default OPF Bus Load data. When a new
bus load is added to the power flow network, a corresponding OPF Bus Load data record will automatically
be created with default values. These data values may be updated. Bus loads connected to buses that are out
of service can have their OPF Bus Load Data modified, but the load will not be acknowledged by the optimal
power flow solution process.

5.5.1. Bus Load Record

The format for each OPF Bus Load record is as follows:

BUS, LOADID, LOADTBL

Within 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 adjustable bus load records are being entered.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
202
Optimal Power Flow Data File Adjustable Bus Load Table Data

The bus number and load identifier uniquely identify each adjustable bus load record. The values for the
record are described as follows:

BUS A bus number between 1 and 999997. The specified bus number must correspond to
an existing bus within the power flow working case.
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.
LOADTBL The adjustable bus load table reference number, as presented in Section 3.6 Adjustable
Bus Load Table Data.

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.

5.6. 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 3.5 Bus Load Data and
are used in conjunction with the Minimize Adjustable Bus Loads objective. Details of the load adjustment
model are covered in Section 14.6.3 Load Adjustment.

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.

5.6.1. Adjustable Bus Load Table Record

The format of each Adjustable Bus Load Table record is:

TBL, LM, LMMAX, LMMIN, LR, LRMAX, LRMIN, LDCOST, CTYP, STATUS, CTBL

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:

TBL Adjustable bus load table number is an integer number. A value less than four digits
in length is most suitable for reporting purposes.
LM Load multiplier. The initial load adjustment variable, as indicated by Yi in the load
adjustment model of Section 14.6.3 Load Adjustment.

LM = 1.0 by default
LMMAX The maximum load adjustment multiplier, used to establish an upper limit for the load
multiplier Y.

To represent a load shedding model, YMAX should be between 0.0 and 1.0 and larger
than YMIN. For a load addition model, YMAX should be greater than 1.0.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
203
Optimal Power Flow Data File Generator Dispatch Data

LMMAX = 1.0 by default

LMMIN The minimum load adjustment multiplier, used to establish a lower limit for the load
multiplier Y. This value should be less than or equal to the value defined for the max-
imum load multiplier.

LMMIN = 1.0 by default

LR Load ratio multiplier. This value is not presently utilized by the program.
LRMAX Maximum load ratio multiplier. This value is not presently utilized by the program.
LRMIN Minimum load ratio multiplier. This value is not presently utilized by the program.
LDCOST Cost scale coefficient. The cost, in $/pu MW, assigned to each OPF bus load participat-
ing in this adjustable bus load group.

LDCOST = 1.0 by default

CTYP Cost curve type. This value is not presently utilized by the program.
STATUS 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 as-
sociated OPF Bus Loads will be recognized as adjustable bus load candidates.

• In-service (1)

• Out of service (0)

STATUS = 1 (In-service) by default

CTBL Cost table cross-reference number. This value is not presently utilized by the program.

5.7. Generator Dispatch Data

Generator Dispatch Data records reference Active Power Dispatch Tables (Section 3.8 Active Power Dispatch
Data) which, in turn, reference Cost Curves (Sections 3.12 to 3.14). 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 unit’s capacity may be made available for dispatch. The active power dis-
patch model, including the minimum and maximum active power limits, is defined within the active power
dispatch table record, described in Section 3.8 Active Power Dispatch Data.

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.

5.7.1. 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:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
204
Optimal Power Flow Data File Active Power Dispatch Data

BUS A bus number between 1 and 999997. The specified bus number must correspond to
a bus already defined within the power flow working case.
GENID A one or two character machine identifier that uniquely identifies the machine at the
bus. If left blank, a default machine identifier of '1' is assumed.
DISP The fractional dispatch value of the machine's total active power output available for
participation 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-
tions for all of the generator dispatch records that reference the same active power
dispatch table should add up to 1.0 for typical applications.

DISP = 1.0 by default

DSPTBL The table number of the active power dispatch control table. Multiple generator dis-
patch records may reference the same active power dispatch table. An active power
dispatch table number of zero implies that the generator is not participating as an
active power control.

DSPTBL = 1 by default

5.8. Active Power Dispatch Data

Active Power Dispatch Table records define the maximum and minimum active power dispatch limits.

Each Active Power Dispatch Table references a Cost Curve (Sections 3.12- 3.14) that specifies the costs as-
sociated with dispatching generation between the defined active power limits. Active Power Dispatch Table
records in turn are referenced by Generator Dispatch records (Section 3.7 Generator Dispatch Data). The
combination of these data records are used in conjunction with the Minimize Fuel Cost objective to perform
dispatch studies.

5.8.1. Active Power Dispatch Record

The format for each Active Power Dispatch Table data record is:

TBL, PMAX, PMIN, FUELCOST, CTYP, STATUS, CTBL

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 table value of zero indicates that no further active
power dispatch table records are to be processed.

Each active power dispatch table is uniquely identified by a numerical identifier. The values of each record
are defined as follows:

TBL Active power dispatch table number is an integer number. A number less than four
digits is most suitable for reporting purposes.
PMAX The upper limit on the total amount of active power available for dispatch, specified
in MW.

PMAX = 9999.0 by default

PMIN The lower limit on the total amount of active power available for dispatch, specified
in MW.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
205
Optimal Power Flow Data File Generation Reserve Data

PMIN = -9999.0 by default

FUELCOST Fuel cost scale coefficient. 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.

FUELCOST = 1.0 by default

CTYP One of three cost curve models may be specified to represent the fuel dispatch curves
of the generator units.

1. Polynomial and exponential curve

2. Piece-wise linear curve

3. Piece-wise quadratic curve

CTYP = 1 (Polynomial and exponential curve) by default

STATUS 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
candidates.

• 1 - In-service

• 0 - Out of service

STATUS = 1 (In-service) by default

CTBL 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.

CTBL = 0 by default

5.9. Generation Reserve Data

Generation Reserve records define a generating unit’s MW output capability and ramp rate. These records
are used in conjunction with the Period Reserve Constraint records (Section 3.15 Period Reserve Constraint
Data) 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 14.6.6 Generator Period Reserve, 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.

5.9.1. Generation Reserve Record

The format for each Generation Reserve record is:

BUS, GENID, RAMP, RTMWMAX

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
206
Optimal Power Flow Data File Generation Reactive Capability Data

When entering records into the OPF Raw Data File, each field must be separated by either a space or a comma.
A bus number of zero indicates that no further generator reserve records are being entered. Any blank fields
must be delineated by commas.

The bus number and machine identifier uniquely identifies each Generation Reserve record. The values for
each record are defined as follows:

BUS A bus number between 1 and 999997. The specified bus number must correspond to
a bus defined within the power flow working case.
GENID A one or two character machine identifier that uniquely identifies the machine at the
bus. If left blank, a default machine identifier of '1' is assumed.
RAMP Unit ramp rate. The rate at which it takes the generator to reach its maximum MW
capability, specified in MW / minute.

RAMP = 9999.0 by default

RTMWMAX The maximum unit reserve contribution, specified in MW

RTMWMAX = 9999.0 by default

5.10. Generation Reactive Capability Data

Generation Reactive Capability records define the limits in the armature reaction and stator current magni-
tude.

Whereas the conventional generator model provides for constant reactive generation limits, the reactive ca-
pability model represents generator armature reaction (Efd) behind synchronous reactance (Xd). With limits
applied to armature reaction magnitude and stator current magnitude, the reactive power capability of the
unit is recognized in a manner which is independent of any assumptions in terminal voltage magnitude or
active power generation. This is further discussed in Section 14.6.5 Generator Reactive Capability.

5.10.1. Generation Reactive Capability Record

The format for each Reactive Capability record is:

BUS, GENID, XD, ISMAX, PFLAG, PFLEAD, QLIMIT, STATUS

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 with commas. A bus number of zero indicates that no further
generator reactive capability records are being entered.

A bus number and machine identifier is used to uniquely identify each Generation Reactive Capability record.
The values for each record are defined as follows:

BUS A bus number between 1 and 999997. The specified bus number must correspond to
a bus already defined within the power flow working case.
GENID 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.
XD The direct axis synchronous reactance of the machine, entered in pu on machine base.

XD = 1.0 by default
ISMAX The generator stator current limit, entered in pu on machine base.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
207
Optimal Power Flow Data File Adjustable Branch Reactance Data

ISMAX = 1.0 by default

PFLAG Real value generator rated lagging power factor.

PFLAG = 1.0 by default

PFLEAD Real value generator rated leading power factor.

PFLEAD = 1.0 by default

QLIMIT The maximum reactive absorption limit at zero power factor, entered in pu on machine
base.

QLIMIT = 1.0 by default

STATUS Reactive Capability Limit Status:

• 0 - Out-of-service. The program will employ reactive generation limits directly from
the power flow data.

• 1 - Enabled. The generator is fully enabled with no reactive generation limits.

• 2 - Enabled with +DEfd inhibited. The generator is in service and any increase in the
field voltage is inhibited.

• 3 - Enabled with -DEfd inhibited. The generator is in service and any decrease in the
field voltage is inhibited.

• 4 - Enabled with Efd fixed. The generator is in service with an invariant field voltage.

The limit status determines how the specified reactive capability record should be em-
ployed in the optimal power flow problem.

STATUS = 4 (Enabled with Efd fixed) by default

5.11. 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 Minimize Adjustable Branch Re-
actances objective to identify candidate branches for use in series var compensation studies. A full descrip-
tion of the adjustable branch reactance model is presented in Section 14.6.4 Adjustable Branch Reactance.

5.11.1. Adjustable Branch Reactance Record

The format for each Adjustable Branch Reactance record is:

IBUS, JBUS, CKT, XMLT, XMLTMAX, XMLTMIN, XCOST, CTYP, STATUS, CTBL

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 indicates that no further adjustable branch reactance records are being
entered.

The from bus, to bus and circuit identifier uniquely identify each Adjustable Branch Reactance record. The
values for each record are defined as follows:
IBUS The sending bus, specified by a number between 1 and 999997. The number must
correspond to a bus already contained within the power flow working case.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
208
Optimal Power Flow Data File Piece-wise Linear Cost Data

JBUS The receiving bus, specified by a number between 1 and 999997. The number must
correspond to a bus already contained within the power flow working case.
CKT The one or two character branch identifier of an existing branch between the from
bus and the to bus. If this field is left blank a default circuit identifier of '1' is assumed.
XMLT The multiplier applied to the current reactance of the branch to yield the initial series
compensation value. A value of 1.0 implies that the initial reactance will be the current
reactance of the branch as obtained from the working case.

XMLT = 1.0 by default

XMLTMAX The maximum multiplier value applied to the reactance of the branch. The calculated
value determines the upper limit on the amount of available branch reactance com-
pensation. It is specified as a fraction of the branch reactance. Values over 1.0 are al-
lowed for situations where a potential increase in reactance is desired.

XMLTMAX = 1.0 by default

XMLTMIN The minimum multiplier value applied to the reactance of the branch. The calculated
value determines the lower limit on the amount of available branch reactance com-
pensation. It is specified as a fraction of the branch reactance.

For example, if the minimum reactance multiplier is specified as 0.3 and the maximum
reactance multiplier is specified as 1.0 then 70% of the branch reactance is available
as compensation.

The minimum value cannot be less than 0.1 to ensure that compensation does not
exceed 90% of the branch impedance.

XMLTMIN = 1.0 by default

XCOST The adjustable branch reactance cost in cost units / pu ohms.

XCOST = 1.0 by default

CTYP This value is not presently utilized by the program
STATUS • 1 - In-service

• 0 - Out-of-service

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.

STATUS = 1 (In-service) by default

CTBL This value is not presently utilized by the program

5.12. Piece-wise Linear Cost Data

The Cost Curve data record provides essential information on the fuel cost characteristics of each participat-
ing generator unit. It is used specifically in conjunction with the Minimize Fuel Cost objective and the Active
Power Dispatch tables ( Section 3.8 Active Power Dispatch Data) 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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
209
Optimal Power Flow Data File Piece-wise Linear Cost Record

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.

5.12.1. Piece-wise Linear Cost Record

The format for each Piece-wise Linear Cost Table data record is a multi-line record as follows:

LTBL, LABEL, NPAIRS, X1, Y1...XN, YN

Each field must be separated by either a space or a comma and any fields left blank must be delineated by
commas.

The total number of pairs entered must equal the value specified for NPAIRS.

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:
LTBL The piece-wise linear cost table number is an integer number. A number less than four
digits in length is most suitable for reporting purposes.

Note that the same cost table number may be used for multiple cost curve tables,
provided that each table represents a different cost curve type (i.e., quadratic or poly-
nomial).
LABEL A descriptive label of the piece-wise linear cost table, containing at most, 12 charac-
ters. This label is strictly used for reporting purposes.

LABEL = '' by default

NPAIRS The number of cost pairs. The total number of xi, yi coordinate pairs being entered.
This value is only used when entering raw data records in the OPF Raw Data File format
or when using PSSE Automation commands.

NPAIRS = 0 by default
Coordinate Pairs The individual coordinate pairs. Each pair (X1, Y1 through X N, YN) defines one segment
of the piece-wise linear cost curve.

• X1... XN 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.

• Y1... YN The total cost or energy consumption. For the fuel cost model, this value
would typically be entered in cost units / hour.

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.

5.13. Piece-wise Quadratic Cost Data

The Cost Curve data record provides essential information on the fuel cost characteristics of each participat-
ing generator unit. It is used specifically in conjunction with the Minimize Fuel Cost objective and the Active
Power Dispatch tables ( Section 3.8 Active Power Dispatch Data).

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
210
Optimal Power Flow Data File Piece-wise Quadratic Cost Record

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.

5.13.1. Piece-wise Quadratic Cost Record

The format for each Piece-wise Quadratic Cost Table data record is a multi-line record as follows:

QTBL, LABEL, COST, NPAIRS, X1, Y1... XN, YN

Each field of the data record 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 NPAIRS.

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:

QTBL The piece-wise quadratic cost table number is an integer number. A number less than
four digits in length is most suitable for reporting purposes.

Note that the same cost table number may be used for multiple cost curve tables,
provided that each table represents a different cost curve type (i.e., quadratic or poly-
nomial).
LABEL A descriptive label of the piece-wise linear cost table, containing at most, 12 charac-
ters. This label is strictly used for reporting purposes.

LABEL = '' by default

COST 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.

COST = 0.0 by default

NPAIRS The number of cost pairs. The total number of xi, yi coordinate pairs being entered.
This value is only used when entering raw data records in the OPF Raw Data File format
or when using PSSE Automation commands.

NPAIRS = 0 by default
Coordinate Pairs The individual coordinate pairs. Each pair (X1, Y1 through X N, YN) defines one segment
of the piece-wise quadratic cost curve.

• X1... XN 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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
211
Optimal Power Flow Data File Polynomial and Exponential Cost Table

• Y1... YN The incremental cost or energy consumption. For the fuel cost model, this
value would typically be entered in cost units / MW.

The Piece-wise Quadratic Cost Table editor displays in the editor all Piece-wise Quadratic Cost Curve Tables
in the working case. The subsystem filter has no effect on the list displayed. If no Piece-wise Quadratic Cost
Curve Tables exist in the working case, the editor will be blank.

5.14. Polynomial and Exponential Cost Table

The Cost Curve data records provide essential information on the fuel cost characteristics of each participat-
ing generator unit. It is used specifically in conjunction with the Minimize Fuel Cost objective and the Active
Power Dispatch tables ( Section 3.8 Active Power Dispatch Data) for generator dispatch analysis.

The Polynomial and Exponential Cost Curve model describes the cost, in cost units (i.e., dollars, pounds,
etc.), as a polynomial equation in terms of a control variable value. Similar to the linear and quadratic cost
curve models, an active power dispatch model may reference a polynomial cost curve in order to obtain
the relative fuel cost to dispatch a participating generator unit at a certain active power dispatch level. The
following equation is employed:

Polynomial Cost Equation

5.14.1. Polynomial and Exponential Record

The format for each Polynomial and Exponential Cost Curve Table record is:

PTBL, LABEL, COST, COSTLIN, COSTQUAD, COSTEXP, EXPN

Each field of the data record 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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
212
Optimal Power Flow Data File Period Reserve Constraint Data

Each Polynomial and Exponential Cost Curve Table record is uniquely identified by a polynomial and expo-
nential cost table number.
PTBL The polynomial and exponential cost table number is an integer number. A number
less than four digits in length is most suitable for reporting purposes.

Note that the same cost table number may be used for multiple cost curve tables, pro-
vided that each table represents a different cost curve type (i.e., linear or quadratic).
LABEL A descriptive label of the piece-wise linear cost table, containing at most, 12 charac-
ters. This label is strictly used for reporting purposes.

LABEL = '' by default

COST The cost or energy integration constant used to calculate the total fuel cost.

COST = 0.0 by default

COSTLIN The linear cost coefficient as indicated by A in the equation given in Figure 3-2.

COSTLIN = 0.0 by default

COSTQUAD The quadratic cost coefficient as indicated by B in the equation given in Figure 3-2.

COSTQUAD = 0.0 by default

COSTEXP The exponential cost coefficient as indicated by C in the equation given in Figure 3-2.

COSTEXP = 0.0 by default

EXPN 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 3-2.

EXPN = 0.0 by default

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.

The Polynomial and Exponential Cost Table displays in the editor all Polynomial and Exponential Cost Curve
Tables that exist in the working case. The subsystem filter has no effect on the list displayed. If no Polynomial
and Exponential Cost Curve Tables exist in the working case, the editor will simply show a blank record.

5.15. Period Reserve Constraint Data

Period Reserve Constraint data records are used in conjunction with the Generation Reserve records ( Section
3.9 Generation Reserve Data) to impose MW reserve limits.

The period reserve constraint model, as described in Section 14.6.6 Generator Period Reserve, defines a MW
reserve that must be met within a stated time limit (i.e., 200 MW in 10 minutes). Some or all of a group of
participating generator units may be deployed to meet this requirement.The maximum reserve contribution
in MWand the unit ramp rate in MW/minute are defined for each participating generator unit as part of
the generation reserve data presented in Section 3.9 Generation Reserve Data. The period reserve records
described here define the desired reserve limit and the time limit in which the reserve limit must be met.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
213
Optimal Power Flow Data File Period Reserve Constraint Record

5.15.1. Period Reserve Constraint Record

The format for each Period Reserve data record is a multi-line record as follows:

RSVID, MWLIMIT, T, STATUS

BUS, GENID

...

BUS, GENID

Each field of the data record must be separated by either a space or a comma and any fields left blank must
be delineated by commas. For each complete period reserve record entered, a single zero must be placed on
the line immediately following the last generator unit entered, or immediately after the main RSVID record
if no participating units are specified. A RSVID value of zero indicates that no further period reserve records
are being entered.

Each Period Reserve record is uniquely identified by a reserve identification number between one and fifteen.
The values for each record are defined as follows:
RSVID The Reserve identifier is a number between one and fifteen, inclusive.
MWLIMIT The reserve requirement, in MW.

If the sum of maximum reserves for all of the units participating in the Period Reserve
data record is less than the specified reserve limit, then the constraint cannot be sat-
isfied. The solution will terminate if this situation arises.

If the reserve limit is set to 0.0, the reserve constraint will not be employed as part of
the optimal power flow problem statement.

MWLIMIT = 0.0 by default

T The time constraint for which the reserve requirement must be fulfilled, in minutes.

T = 9999.0 by default
STATUS • 1 - In-service

• 0 - Out-of-service

The status switch indicates whether the specified period reserve record should be in-
cluded within the OPF problem statement. Only in-service period reserve records will
be included as a reserve constraint.

STATUS = 1 (In-service) by default

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 - The bus number of the bus where the unit is located. When using the spread-
sheet, this value may need to be entered as a bus name, depending upon the input
mode currently in effect.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
214
Optimal Power Flow Data File Branch Flow Constraint Data

• GENID - The generator unit identifier of the participating generator. A default iden-
tifier of 1 is assumed if left blank.

The Period Reserve data editor displays all Period Reserve data records within the working case. The subsys-
tem filter has no effect on the list displayed. If no Period Reserve records exist in the working case, the editor
will be blank.

5.16. Branch Flow Constraint Data

Branch Flow Constraint records define upper and lower flow limits on selected non zero impedance branch-
es. 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.

5.16.1. Branch Flow Constraint Record

The format of each Branch Flow Constraint record is:

IBUS, JBUS, CKT, BFID, FMAX, FMIN, EFMAX, EFMIN, FTYP, LTYP, LPEN, KBUS

Each field of the data record 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 indicates 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 identify each
Branch Flow Constraint record. The values for each record are defined as follows:

IBUS The sending bus, specified by a number from 1 through 999997. The number must
correspond to an existing bus within the power flow working case.

If a three-winding transformer is being specified, the from bus defines the winding for
which the flow constraint is being introduced.
JBUS The receiving bus, specified by a number from 1 through 999997. The number must
correspond to an existing bus within the power flow working case.
CKT A one or two character identifier used to differentiate between multiple connecting
lines between the from bus, to bus and third bus (if three-winding transformer). If this
field is left blank, a circuit identifier of '1' is assumed.
BFID A single character identifier to differentiate between multiple branch flow constraints
defined at the same branch. If this field is left blank, a flow identifier of '1' is assumed.
FMAX The maximum normal flow limit on the specified branch. Values are specified in phys-
ical units appropriate to the flow limit type being specified; Ampere constraints are
specified in MVA.

If the difference between the specified upper and lower branch flow limits is less than
0.0001 then the specified flow constraint is fixed at the indicated limit.

This value, along with the minimum normal limit defined below, is used to define
one of two possible flow limits assigned to the branch. An alternate set of emergency
limits is defined below. By default, the normal flow limits are employed during the OPF
solution unless the Impose Emergency Branch Flow Limits solution option is selected.

FMAX = 0.0 by default

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
215
Optimal Power Flow Data File Branch Flow Constraint Record

FMIN The minimum normal flow limit on the specified branch. Values are specified in phys-
ical units appropriate to the flow limit type being specified; Ampere constraints are
specified in MVA.

If the difference between the specified upper and lower branch flow limits is less than
0.0001 then specified flow constraint is treated as fixed at the indicated limit.

FMIN = 0.0 by default

EFMAX The maximum emergency flow limit on the specified branch. This limit, in conjunction
with the minimum emergency limit, defines an optional alternate set of flow limits.
Values are specified in physical units appropriate to the flow limit type being specified;
Ampere constraints are specified in MVA.

To enforce recognition of the minimum and maximum emergency flow limits as op-
posed to the normal flow limits during the OPF solution, select the Impose Emergency
Branch Flow Limits solution option.

EFMAX = 0.0 by default

EFMIN 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.
Values are specified in physical units appropriate to the flow limit type being specified;
Ampere constraints are specified in MVA.

If emergency limits are employed during the OPF solution and the difference between
the specified upper and lower emergency branch flow limits is less than 0.0001, then
the specified flow constraint is treated as fixed at the indicated limit.

EFMIN = 0.0 by default

FTYP One of four different flow types specified for the constraint:

• 1 - MW

• 2 - MVar

• 3 - MVA

• 4 - Ampere (4)

FTYP is 4 (Ampere) by default

LTYP One of four constraint limit types enforced during the OPF solution:

• 0 - Reporting only. Only report on violations of the specified branch flow limits,
taking no action if the branch flow falls outside of limits.

• 1 - Hard limit. Strictly enforce the specified branch flow limits through the use of
barrier terms.

• 2 - Soft limit with a linear penalty. Permit branch flows to go outside of their speci-
fied 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 indi-
cate severity of excursion.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
216
Optimal Power Flow Data File Interface Flow Constraint Data

• 3 - Soft limit with a quadratic penalty. Permit branch flow limit to go outside of
their specified 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 14.7.2 Accommodating Inequality Constraints for more information

on the limit type options.

LTYP is 1 (Hard limit) by default

LPEN The penalty weight value applied to either the linear or quadratic soft limit penalty
functions. The larger the number, the higher the penalty for branch flow excursions
outside of limits.

LPEN is 1.0 by default

KBUS The third bus of a three-winding transformer, specified by a number from 1 through
999997. The number must correspond to an existing bus within the power flow work-
ing case.

If a three-winding transformer is not being entered, this value is zero.

5.17. Interface Flow Constraint Data

Interface flow records introduce MW or MVar flow constraints across a defined interface. These limits are
only enforced when the Constrain Interface Flows option is enabled, otherwise they are ignored during the
OPF solution. In conjunction with both the interface flow constraint records and the directive to Constrain
Interface Flows, the Minimize Interface Flows objective may be employed to either minimize or maximize
flows across an interface.

An interface consists of a collection of branches that may include the tie lines between two areas, the flows
through a particular transmission corridor, or the collection of lines emanating from an area. Each interface
flow constraint record defines a set of branches included in the interface and the flow limits that are to
be imposed on that set during the optimization process. By default, the interface flow definitions are for
informational purposes only. They do not automatically introduce constraint equations or objective terms
in the optimization problem unless one or both of the corresponding Constrain Interface Flows or Minimize
Interface Flows options are enforced.

The format for each Interface Flow Constraint data record is a multi-line record as follows:

IFLWID, LABEL, FMAX, FMIN, FTYP, LTYP, LPEN

IBUS, JBUS, CKT, KBUS

IBUS, JBUS, CKT, KBUS

...

Each field of the data record must be separated by either a space or a comma, with any blank fields delineated
by commas. For each interface flow record entered, a single zero must be placed on the line immediately
following the last participating branch entered, or immediately after the main IFLWID record if no participat-
ing branches are specified.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
217
Optimal Power Flow Data File Interface Flow Constraint Data

An IFLWID value of zero indicates that no further interface flow records are to be processed.

Each Interface Flow Constraint record is uniquely identified by an interface flow identifier. The values for
each record are defined as follows:

IFLWID The interface flow identifier is an integer number. A value less than four digits in length
is most suitable for reporting purposes.
LABEL A string containing a maximum of 32 characters used to describe the interface. This
label is only used for reporting purposes.

LABEL is '' by default

FMAX The maximum flow limit across the interface, specified in the physical units appropri-
ate 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 maximum interface flow limit is set to the average of the two interface
flow limit values plus 0.1.

FMAX is 0.0 by default

FMIN 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.

FMIN is 0.0 by default

FTYP One of two valid flow types:

• 1 - MW

• 2 - MVar

FTYP is 1 (MW) by default

LTYP One of four different limit types:

• 0 - Reporting only. Only report on violations of the specified interface flow limits,
taking no action if the interface flow falls outside of limits.

• 1 - Hard limit. Strictly enforce the specified interface flow limits through the use of
barrier terms.

• 2 - Soft limit with a linear penalty. Permit interface flows to go outside of the speci-
fied 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 indi-
cate severity of excursion.

• 3 - Soft limit with a quadratic penalty. 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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
218
Optimal Power Flow Data File Linear Constraint Dependency Data

Refer to Section 14.7.2 Accommodating Inequality Constraints for more information

on the limit type options.

LTYP is 1 (Hard limit) by default

LPEN The penalty weight value applied to either the linear or quadratic soft limit penalty
functions. The larger the number, the higher the penalty for interface flow excursions
outside of the defined interface flow limits.

LPEN is 1.0 by default

Participating Branch- A list of branches defining the interface. Each branch is individually specified by the
es following identifiers:

• IBUS - From bus number. 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.

• JBUS - To bus number. The receiving end 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.

• CKT - Circuit ID. The one or two character circuit identifier. If no circuit identifier is
entered, a default value of '1' is assumed.

• KBUS - Third bus number. The third bus number (1 through 999997) if a three wind-
ing transformer is specified; zero (0) otherwise. When using the spreadsheet, this
value may optionally be entered as a bus name, provided that names input mode
is in effect.

The Interface Flow Constraint editor displays all Interface Flow Constraint records within the working case
in the data table. The subsystem filter has no effect on the list displayed. If there are no Interface Flow
Constraint records in the working case, then the editor window will be blank.

5.18. Linear Constraint Dependency Data

Linear Constraint Dependency records provide a way to introduce customized linear constraint equations into
the optimal power flow problem statement. Each dependency equation may be comprised of any number of
variables, selected from a group of previously defined records. Details of the linear constraint dependency
equation model are discussed in Section 14.6.8 Linear Constraint Dependency Equation.

5.18.1. Linear Constraint Dependency Record

The format of each Linear Constraint Dependency data record is a multi-lined record as follows:

EQID, LABEL, SLKMAX, SLKMIN

VTYP, "ID FIELDS", COEFF

VTYP, "ID FIELDS", COEFF

...

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
219
Optimal Power Flow Data File Linear Constraint Dependency Record

Each field of the data record must be separated by either a space or a comma, with any blank fields delineated
by commas. For each Linear Constraint Equation record entered, a single zero must be placed on the line
immediately following the last participating variable record entered, or immediately after the main EQID
record if no participating variables are specified.

An EQID value of zero indicates that no further linear constraint dependency records are to be processed.

Each Linear Constraint Dependency record is uniquely identified by a constraint equation identifier. The val-
ues for each field within the record are defined as follows:
EQID The linear constraint equation identifier is an integer number. A value less than four
digits in length is most suitable for reporting purposes.
LABEL A string containing a maximum of 32 characters used to describe the linear constraint
dependency equation being defined. This label is only used for reporting purposes.

LABEL is '' by default

SLKMAX The constraint equation maximum slack variable limit

SLKMAX is 0.0 by default.

SLKMIN The constraint equation minimum slack variable limit

SLKMIN is 0.0 by default.

VTYP A number (1 through 10) corresponding to the type of dependency variable being
added to the constraint equation. The numerical values associated with each variable
type are as follows:

1. voltage magnitude, in pu

2. voltage angle, in radians (degrees/57.29578)

3. active power generation, in per unit of reactive power based on system base(i.e.
400 MW limit base on a system base of 100 is entered as 4.0)

4. reactive power generation, in per unit of reactive power based on system base(i.e.
400 Mvar limit base on a system base of 100 is entered as 4.0)

5. transformer tap ratio, entered as the inverse of the tap ratio; or transformer phase
shift angle, in radians

6. branch flow, in per unit flow value based on system base

7. interface flow, in per unit flow value based on system base

8. adjustable bus shunt, in per unit Mvar value based on system base

9. switched shunt, in per unit Mvar value based on system base

10. load adjustment, entered in terms of the load multiplier (i.e. 0.8 for 80% of load
or 1.8 for 180% of load
"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:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
220
Optimal Power Flow Data File Linear Constraint Dependency Record

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"]

Third bus number, if a three-winding transformer is specified; placed after the

Coeff value [0]

6. From bus number

To bus number

Circuit identifier [" 1"]

Branch flow identifier ["1"]

Third bus number, if a three-winding transformer is specified; placed after the

Coeff value [0]

7. Interface flow identifier

8. Bus number (1 through 999997) Adjustable bus shunt identifier [" 1"]

9. Bus number (1 through 999997)

10. Adjustable bus load table number

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:

When using the linear constraint equation table editor, bus identifiers may alternately
be entered as extended bus names instead of bus number, provided that the names
input mode option is in effect.
COEFF A real variable coefficient applied to the dependency variable specified above.

COEFF is 1.0 by default.

Any number of participating variables may be included in the linear constraint dependency equation. The
variable identifiers must correspond to a record that already exists within the working case.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
221
Optimal Power Flow Data File Linear Constraint Dependency Record

The Linear Constraint Dependency Equation data table displays in the editor all Linear Constraint Dependency
Equation records within the working case. The subsystem filter has no effect on the list displayed. If there
are no Linear Constraint Dependency Equation records in the working case, the editor window will be blank.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
222
 Chapter 6
GIC Data File

6.1. Overview
The geomagnetic induced currents can flow through transformer winding and substation ground paths.
For power flow calculations and substation ground paths data is not required. So this data is not available
in power flow data. This additional data is provided in GIC data file (extension .gic). The accuracy of GIC
calculations will depend on the data provided in GIC data file.

Depending on the size of the power flow network studied, this data could be large. It is recommended to
create a GIC data template with one of the following ways and edit/modify that:

1. Using activity GIC GUI, GIC data file from Excel GIC data templates

• GIC > Excel template for GIC data file

• GIC > Create GIC data file from Excel template

2. Python module “gicdata” (See PSSE Application Program Interface (API) manual)

All data is read in free format with data items separated 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.

File Identification Data

Substation Data

Bus Substation Data

Transformer Data

Fixed Bus Shunt Data

Branch Data

User Earth Model Data

Switched Shunt Data

Two-Terminal DC Data

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
223
GIC Data File File Identification Data

VSC DC Data

Multi-Terminal DC Data

FACTS Device Data

Load Data

Q Record

GIC Data Input Structure

6.2. File Identification Data

This record contains only one data item which is specified as:

GICFILEVRSN=vernum

GICFILEVRSN GICFILEVRSN is the keyword to specify the GIC data file version number.

vernum is an integer value specifying GIC data file version number. No default allowed.

Allowed, GICFILEVRSN = 4

GICFILEVRSN = 5

Note: The first release of the GIC data file did not have this record and is treated as
file version 1

At PSSE version 35.0.0, network equipment location information is consolidated in one source which is base
case data. To faciliate that:

• The substation location information is moved from the GIC data file to the Base Case data (power flow
data).

• When GIC data file version 4 is read, "Single Bus" substation configuration is added to each bus-substation
data record and non Node-Breaker base case is converted to Node-Breaker base case.

• For this to work without any data conflicts, GIC data file version 4 is allowed to be read into base case that
has no Node-Breaker configurations.

6.3. Substation Data

Each substation data record has the following format:

GICFILEVRSN 4

I, NAME, UNIT, LATITUDE, LONGITUDE, RG, EARTHMDL, RGFLAG

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
224
GIC Data File Substation Data

GICFILEVRSN 5

I, RG, EARTHMDL, RGFLAG

I Substation number (1 through 999997)

No default allowed.
NAME Alphanumeric identifier assigned to substation I. NAME may be up to 40 characters
and may contain any combination of blanks, uppercase letters, numbers and special
characters, but the first character must not be a minus sign. NAME must be enclosed
in single or double quotes if it contains any blanks or special characters.

NAME = "" by default.

UNIT Unit for geophysical location (longitude and longitude) data

• 0 - degrees

UNIT = 0 by default.
LATITUDE Substation latitude, positive for North and negative for South. When UNIT = 0, latitude
is specified in degrees.

No default allowed.
LONGITUDE Substation longitude, positive for East and negative for West. When UNIT = 0, longi-
tude is specified in degrees.

No default allowed.
RG Substation grounding DC resistance in ohms. If RG <= 0.0 or RG > = 99.0, it is assumed
that the substation is ungrounded.

RG = 0.1 by default.
EARTHMDL Name of the earth model. EARTHMDL may be up to 32 characters.

• When specified this earth model will be used in determining Benchmark GMD event
earth model scaling factor (beta) and Non-uniform GMD event calculations

• When not specified, the earth model specified in GIC API is used.

EARTHMDL = "" by default.

RGFLAG Method used to specify RG value. RGFLAG may be up to 40 characters. It is used for
informational purposes only.

Possible methods:

• "Assumed"

• "Measured"

• "Calculated"

• "Brief comment of your choice"

RGFLAG = "Assumed" by default.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
225
GIC Data File Bus Substation Data

6.4. Bus Substation Data

Each bus substation data record has the following format::

GICFILEVRSN 4

BUSNUM, SUBNUM

GICFILEVRSN 5

There is no bus substation data group.

BUSNUM Bus number. Bus BUSNUM must be present in the working case.

No default allowed.
SUBNUM Substation number (1 through 999997). This is the substation number to which bus
BUSNUM belongs to.

SUBNUM must be previously defined in “Substation Data” record group.

The following restrictions apply when assigning bus and its substation:

• Generally two buses connected by a transmission line (non-transformer branch) re-

side in two different substations. Exception to this would be short lines between two
buses of same substation. Those short branches are treated as zero length branches
with no GMD induced voltage in those.

• Two buses connected by a two winding transformer must be in same substation.

• Three buses connected by a three winding transformer must be in same substation.

• Two buses connected by zero impedance line must have same substation number.

No default allowed.

6.5. Transformer Data

The transformer specified by buses “I, J, K, CKT” must exist in the working case. Also the winding bus order
must be same as in the working case.

Note 1 : For two and three winding auto transformers WRI, WRJ and WRK could represent per phase dc
resistances of series winding (Rs) or common winding (Rc).

For example, as shown in figure below:

• Bus I is series winding bus, WRI=Rs

• Bus J is common winding bus, WRJ=Rc

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
226
GIC Data File Transformer Data

Note 2 : Figure below shows generic Phase Angle Regulator (PAR) connections where series unit has split
tap. It is represented as T model in GIC calculation DC network. The series unit is connected between Bus I
and Bus J. In GIC data file:

• WRI is dc resistance of series unit section connected to Bus I

• WRJ is dc resistance of series unit section connected to Bus J

• WRK is dc resistance of exciting unit

It is imperative that WRI, WRJ and WRK values are calculated and specified in GIC data file for correct modeling
of such a transformer.

Each transformer data record has the following format:

I, J, K, CKT, WRI, WRJ, WRK, GICBDI, GICBGJ, GICBDK, VECGRP, CORE, KFACTOR,
GRDWRI, GRDWRJ, GRDWRK, TMODEL

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
227
GIC Data File Transformer Data

I The bus number of the bus to which Winding 1 is connected. It must be same Winding
1 bus for the same transformer in the working case.

No default allowed
J The bus number of the bus to which Winding 2 is connected. It must be same Winding
2 bus for the same transformer in the working case.

No default allowed
K The bus number of the bus to which Winding 3 is connected. It must be same Winding
3 bus for the same transformer in the working case.

K = 0 for two winding transformers. No default allowed for three winding transform-
ers.
CKT One- or two-character branch circuit identifier.

CKT = '1' by default

WRI DC resistance of Winding 1 in ohms/phase. When WRI is not specified, working case
resistance is used to determine WRI.

DC resistance of series unit of PAR (see Note 2).

WRI = 0.0 by default

WRJ DC resistance of Winding 2 in ohms/phase. When WRJ is not specified, working case
resistance is used to determine WRJ.

DC resistance of series unit of PAR (see Note 2).

WRJ = 0.0 by default

WRK DC resistance of Winding 3 in ohms/phase. For three-winding transformers, when WRK
is not specified, working case resistance is used to determine WRK.

DC resistance of exiciting unit of PAR (see Note 2).

WRK = 0.0 by default

GICBDI GIC blocking device in neutral of Winding 1

• 0 - no GIC blocking device present

• 1 - GIC blocking device present

For an auto-transformers, if either GICBDI = 1 or GICBDJ = 1, that auto-transformer is

treated as if it has GIC blocking device present.

GICBDI = 0 by default
GICBDJ GIC blocking device in neutral of Winding 2

• 0 - no GIC blocking device present

• 1 - GIC blocking device present

For an auto-transformers, if either GICBDI = 1 or GICBDJ = 1, that auto-transformer is

treated as if it has GIC blocking device present.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
228
GIC Data File Transformer Data

GICBDJ = 0 by default
GICBDK GIC blocking device in neutral of Winding 3

• 0 - no GIC blocking device present

• 1 - GIC blocking device present

GICBDK = 0 by default. GICBDK = 0 for two-winding transformers.

VECGRP Alphanumeric identifier specifying vector group based on transformer winding con-
nections and phase angles.

If vector group is specified in power flow data that data will be used and it is not needed
to be specified here. As far as GIC calculations are concerned, winding grounding con-
nection information is used; its clock angles are not used. Refer to POM Sections “Two
Winding Transformer Vector Groups” and “Three Winding Transformer Vector Groups”
for allowed vector groups.

• When bus number orders in GIC data file record are different than the bus number
orders in power flow RAW data file, the bus number orders in power flow RAW data
file is used to assign winding configuration as per vector group specified.

• For auto-transformers, bus with lower base bus voltage is treated as common wind-
ing bus.

• For three-winding auto-transformers, windings on bus I and bus J form auto-trans-

former.

VECGRP = "" by default

CORE Number of cores in transformer core design. This information is used to calculate trans-
former reactive power loss from GIC flowing its winding.

• -1 - three phase shell form

• 0 - unknown core design

• 1 - single phase core

• 3 - three phase 3-legged core form

• 5 - three phase 5-legged core form

CORE = 0 by default
KFACTOR Factor to calculate transformer reactive power loss from GIC flowing its winding
(MVAR/AMP)

KFACTOR = 0.0 by default

GRDWRI Winding 1 grounding DC resistance in ohms

GRDWRI = 0.0 by default (no grounding resistance; solidly grounded)

GRDWRJ Winding 2 grounding DC resistance in ohms

GRDWRJ = 0.0 by default (no grounding resistance; solidly grounded)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
229
GIC Data File Fixed Bus Shunt Data

GRDWRK Winding 3 grounding DC resistance in ohms

DC resistance of exciting unit grounding of PAR (see Note 2).

GRDWRK = 0.0 by default (no grounding resistance; solidly grounded)

TMODEL Number of cores in transformer core design. This information is used to calculate trans-
former reactive power loss from GIC flowing its winding.

• 0 - two/three/auto transformer model as defined by its vector group

• 1 - transformer as T model in DC network (See Note 2)

TMODEL = 0 by default

6.6. Fixed Bus Shunt Data

Only in-service fixed bus shunts provided on this data record are modeled in the GIC DC network.

Each fixed bus shunt data record has the following format:

I, ID, R, RG
I Bus number of the bus to which the fixed shunt is connected. It must be present in
the working case.

No default allowed
ID One- or two-character non-blank alphanumeric fixed bus shunt identifier.

ID = '1' by default
R DC resistance in ohms/phase. It must be > 0.0. Fixed bus shunt records with R = 0.0
will be ignored.

No default allowed
RG Grounding DC resistance in ohms

RG = 0.0 by default (no grounding resistance; solidly grounded)

6.7. Branch Data

Only in-service branches are modeled in the GIC DC network.

Each user branch data record has the following format:

I, J, CKT, RBRN, INDVP, INDVQ, RLNSHI, RLNSHJ

I Branch from bus number

No default allowed
J Branch to bus number

No default allowed
CKT One- or two-character transformer circuit identifier; a transformer with circuit identi-
fier CKT between buses I and J must be in the working case.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
230
GIC Data File User Earth Model Data

CKT = '1' by default

RBRN Branch DC resistance in ohms/phase. When RBRN is not specified or RBRN=0.0, power
flow data branch resistance in pu is converted to ohms/phase and used. There is no
temperature correction applied.

RBRN = 0.0 by default

INDVP Real part of total branch GMD induced electric field in volts. See note below on how
to specify this value.
INDVQ Imaginary part of total branch GMD induced electric field in volts. See note below on
how to specify this value.
Note 1 : Total branch GMD induced electric field, INDUCEDV = INDVP + j INDVQ volts

Branch INDUCEDV is determined as below:

• When INDUCEDV is not specified, GIC activity calculates this according to its options
specified

• When INDUCEDV is specified, it is used as GMD induced on that branch

• When INDUCEDV is specified as INDVP = 0.0 and INDVQ = 0.0, then that branch is
treated as part of the GIC DC network but does not have GMD induced voltage, like
“underground pipe-type cables (cables enclosed in the steel pipe).”

For uniform filed modeling INDUCEDV will be real value, but for non-uniform field
modeling this will be complex value.

This voltage will have positive polarity at branch To Bus (J bus).

Note 2 :

• When the Branch INDVP + j INDVQ is specified, it is used as is. There are no other
scaling factors applied to this voltage.

• When INDVP + j INDVQ is specified for all branches, specified GMD event option is
ignored during GIC calculations.

• When INDVP + j INDVQ is specified for few branches, the induced Efield for remain-
ing branches in study subsystem is calculated using the GMD event option specified.
RLNSHI DC resistance in ohms/phase of the line shunt at the bus I end of the branch. It must be
> 0. When RLNSHI = 0 or not specified, there will be no ground path for this line shunt.

No default allowed
RLNSHJ DC resistance in ohms/phase of the line shunt at the bus J end of the branch. It must be
> 0. When RLNSHJ = 0 or not specified, there will be no ground path for this line shunt.

No default allowed

6.8. User Earth Model Data

Activity GIC models US and Canada Earth Models (Ref…). However, if any other Earth Model is required, use
this data to define such an earth model. A total of up to 50 user earth models are allowed. Also each earth

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
231
GIC Data File Switched Shunt Data

model may have up to 25 layers. Use as many records needed to specify the data. The thickness of the last
layer is infinity. This is specified as any value less than 0.0 (= -999.0 for example). The thickness value less
than 0.0 is also used as end of earth model data.

Each user earth model data record has the following format:

NAME, BETAFTR, DESC, RESISTIVITY1, THICKNESS1, RESISTIVITY2, THICKNESS2, ...,

RESISTIVITY24, THICKNESS24, RESISTIVITY25, THICKNESS25

NAME The non-blank alphanumeric identifier assigned to this earth model. Each earth model
must have unique name. NAME may be up to 32 characters. This name should be
different than the Standard US and Canada Earth Models defined (Refer …).

No default allowed
BETAFTR Earth Model scaling factor used when calculating branch induced electric field for
Benchmark GMD event.

BETAFTR = 1 by default
DESC Description of the earth model. NAME may be up to 72 characters. This is used for
information purpose only

DESC = "" by default

RESISTIVITY1 Layer 1 resistivity in ohm-m

No default allowed
THICKNESS1 Layer 1 thickness in km

No default allowed
RESISTIVITYN Nth layer resistivity in ohm-m. Up to 25 layers are allowed

No default allowed
THICKNESSN Nth layer 1 thickness in km. Up to 25 layers are allowed. The thickness of the last layer
is infinity. This is specified as any value less than 0 (= -999.0 for example).

No default allowed

6.9. Switched Shunt Data

Only in-service switched shunts provided on this data record are modeled in the GIC DC network.

Each switched shunt data record has the following format:

GICFILEVRSN 4

I, R, RG

GICFILEVRSN 5

I, ID, R, RG

I Bus number; bus I must be present in the working case with positive sequence
switched shunt data.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
232
GIC Data File Two-Terminal DC Data

ID One- or two-character non-blank alphanumeric switched shunt identifier.

ID = '1' by default
R DC resistance in ohms/phase. It must be > 0.0. Switched shunt records with R = 0.0
will be ignored.

No default allowed
RG Grounding DC resistance in ohms. No grounding resistance; solidly grounded.

RG = 0.0 by default

6.10. Two-Terminal DC Data

The rectifier and inverter converter stations are connected to ac network through converter transformers.
If these converter transformers are not explicitly modeled in the power flow, then use this data record to
specify the GIC DC network data for them.

Provide DC resistance data of grounded windings of converter transformers.

The status (blocked or in-service) of two-terminal DC lines from power flow data is not considered. The DC
data provided on this data record is modeled in the GIC DC network. Up to 10 GIC DC network elements are
allowed per DC line.

Each two-terminal DC data record has the following format:

NAME, I, ID, R, RG

NAME The non-blank alphanumeric identifier assigned to this DC line. It must be present in
the working case. NAME may be up to 12 characters.

No default allowed
I Bus number of the rectifier (IPR) or inverter (IPI) converter AC bus. It must be present
in the working case.

No default allowed
ID One- or two-character non-blank alphanumeric identifier. There could be more than
one ground path at rectifier or inverter ac bus. This ID is used to be able to specify
more than one ground path. This is specific to GIC data and it does not exist in the
working case.

No default allowed
R DC resistance in ohms/phase of grounded winding of converter transformers. It must
be > 0.0. R = 0.0 or not specified means there will be no ground path.

No default allowed
RG Grounding DC resistance in ohms

RG = 0.0 by default (no grounding resistance; solidly grounded)

Two-terminal DC data input is terminated with a record specifying a bus number of zero.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
233
GIC Data File VSC DC Data

6.11. VSC DC Data

The rectifier and inverter converter stations are connected to ac network through converter transformers.
If these converter transformers are not explicitly modeled in the power flow, then use this data record to
specify the GIC DC network data for them.

Provide DC resistance data of grounded windings of converter transformers.

The status (blocked or in-service) of VSC DC lines from power flow data is not considered. The DC data
provided on this data record is modeled in the GIC DC network. Up to 10 GIC DC network elements are allowed
per DC line.

Each VSC DC data record has the following format:

NAME, I, ID, R, RG
NAME The non-blank alphanumeric identifier assigned to this VSC DC line. It must be present
in the working case. NAME may be up to 12 characters.

No default allowed
I Bus number of the rectifier (IPR) or inverter (IPI) converter AC bus. It must be present
in the working case.

No default allowed
ID One- or two-character non-blank alphanumeric identifier. There could be more than
one ground path at rectifier or inverter ac bus. This ID is used to be able to specify
more than one ground path. This is specific to the GIC data and it does not exist in
the working case.

No default allowed
R DC resistance in ohms/phase of grounded winding of converter transformers. It must
be > 0.0. R = 0.0 or not specified means there will be no ground path.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
234
GIC Data File Multi-Terminal DC Data

No default allowed
RG Grounding DC resistance in ohms

RG = 0.0 by default (no grounding resistance; solidly grounded)

VSC DC data input is terminated with a record specifying a bus number of zero.

6.12. Multi-Terminal DC Data

The multi-terminal converters are connected to ac network through converter transformers. If these convert-
er transformers are not explicitly modeled in the working case, then use this data record to specify the GIC
DC network data for them.

Provide DC resistance data of grounded windings of converter transformers.

The status (blocked or in-service) of multi-terminal DC lines in the working case is not considered. The DC
data provided on this data record is modeled in the GIC DC network. Up to 10 GIC DC network elements are
allowed per DC line.

Each multi-terminal DC data record has the following format:

NAME, I, ID, R, RG

NAME The non-blank alphanumeric identifier assigned to this Multi-Terminal DC line. It must
be present in the working case. NAME may be up to 12 characters.

No default allowed
I Converter ac bus number (IB). It must be present in the working case.

No default allowed
ID One- or two-character non-blank alphanumeric identifier. There could be more than
one ground path at ac bus. This ID is used to be able to specify more than one ground
path. This is specific to the GIC data and it does not exist in the working case.

No default allowed
R DC resistance in ohms/phase of grounded winding of converter transformers. It must
be > 0.0. R = 0.0 or not specified means there will be no ground path.

No default allowed
RG Grounding DC resistance in ohms

RG = 0.0 by default (no grounding resistance; solidly grounded)

Multi-Terminal DC data input is terminated with a record specifying a bus number of zero.

6.13. FACTS Device Data

The FACTS device converters are connected to ac network through converter transformers. If these converter
transformers are not explicitly modeled in the working case, then use this data record to specify the GIC DC
network data for them.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
235
GIC Data File Load Data

Provide DC resistance data of grounded windings of converter transformers.

The status (in-service or out-of-service) of FACTS device from power flow data is not considered. The DC
data provided on this data record is modeled in the GIC DC network. Up to 10 GIC DC network elements are
allowed per DC line.

Each multi-terminal DC data record has the following format:

NAME, I, ID, R, RG

NAME The non-blank alphanumeric identifier assigned to this FACTS device. It must be
present in the working case. NAME may be up to 12 characters.

No default allowed
I FACTS device sending end bus number (IBUS). It must be present in the working case.

No default allowed
ID One- or two-character non-blank alphanumeric identifier. There could be more than
one ground path at ac bus. This ID is used to be able to specify more than one ground
path. This is specific to the GIC data and it does not exist in the working case.

No default allowed
R DC resistance in ohms/phase of grounded winding of converter transformers. It must
be > 0.0. R = 0.0 or not specified means there will be no ground path.

No default allowed
RG Grounding DC resistance in ohms

RG = 0.0 by default (no grounding resistance; solidly grounded)

FACTS device data input is terminated with a record specifying a bus number of zero.

6.14. Load Data

Only in-service loads provided on this data record are modeled in the GIC DC network.

Each load data record has the following format:

I, ID, R, RG

I Bus number of the bus to which load is connected. It must be present in the working
case.

No default allowed
ID One- or two-character non-blank alphanumeric load identifier.

ID = '1' by default
R DC resistance in ohms/phase of grounded loads. It must be > 0.0. R = 0.0 or not spec-
ified means there will be no ground path.

No default allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
236
GIC Data File Load Data

RG Grounding DC resistance in ohms

RG = 0.0 by default (no grounding resistance; solidly grounded)

Load data input is terminated with a record specifying a bus number of zero.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
237
 Chapter 7
Harmonics Data File (RAWX)

7.1. Overview
To perform harmonic analysis comprising network frequency scan and distortion calculations following data
is needed.

1. power flow data (.raw file)

2. sequence flow data (.seq file) [optional] When sequence data is provided, appropriate positive, negative
or zero sequence impedance is used to calculate impedance for each harmonics order and determine if
equipment is grounded to consider in triplen harmonic calculations.

3. harmonic models and network elements frequency dependency data [optional]. When this data is not
provided inductive or capacitive reactance is calculated for each harmonics order.

4. harmonic source data [optional] However, when harmonic current source data is not provided, voltage
and current distortion calculations are not performed.

These additional data items (3) and (4) are provided in extended raw file (.rawx) under "harmonics" domain.
The accuracy of harmonic analysis will depend on the quality this additional data provided. [Note - Harmonics
data is provided in RAWx format, not RAW format.]

This section describes the format of the harmonic .rawx file.

Impedance Characteristics Data

Voltage Sources Data

Current Sources Data

Load Data

Generator (Synchronous Machine) Data

Non-Transformer Branch Data

Transformer Data

Two-Terminal DC Data

VSC DC Data

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
238
Harmonics Data File (RAWX) Impedance Characteristics Data

FACTS Device Data

Induction Machine (Asynchronous Machine) Data

Multi-Terminal DC Data

Passive Filter Data

Q Record

7.2. Impedance Characteristics Data

The frequency dependency of various network elements is defined in this table. The resistance, inductive
reactance and capacitance reactance harmonic response is provided by this characteristics.

There is no limit on number of harmonics modeled in each impedance characteristics table.

Following two tables specify impedance characteristics data.

1. Impedance Characteristics

2. Impedance Characteristics Points

Each impedance characteristics data table has the following format:

"impchr":{
"fields":["name"],
"data":[
["ZTABLE1"],
...
["ZTABLE9"]
]
}

Each impedance characteristics points table has the following format:

"impchrpts":{
"fields":["name", "hn", "rn", "x1", "x2"],
"data":[
["ZTABLE1", 1.000000, 1.110000, 2.110000, 3.110000],
...
["ZTABLE9", 93.00000, 1.120000, 2.120000, 3.120000]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to table. Each Impedance Char-
acteristics table must have unique NAME. The NAME may be up to 40 characteris-
tics and may contain any combination of blanks, uppercase letters, numbers and
special characters, but the first character must not be a minus sign. The NAME

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
239
Harmonics Data File (RAWX) Voltage Sources Data

Field RAWX Key Description

must be enclosed in single or double quotes if it contains any blanks or special
characters.

No default allowed.
HN hn Harmonic Order

No default allowed.
RN rn Resistance in ohms at harmonic order 'N'.

No default allowed.
X1N x1n Inductive reactance (positive value) or Capacitive reactance (negative value) in
ohms at harmonic order 'N'.

No default allowed.
X2N x2n Inductive reactance (positive value) or Capacitive reactance (negative value) in
ohms at harmonic order 'N'.

No default allowed.

The total impedance at harmonic order 'N' is determined by series connection of RN, X1N and X2N.

7.3. Voltage Sources Data

The harmonic voltage sources are defined in this table.

There is no limit on number of harmonics modeled in each voltage sources table.

Following two tables specify voltage source data.

1. Voltage Source

2. Voltage Source Points

Each voltage sources data table has the following format:

"vltsrc":{
"fields":["name", "angoptn"],
"data":[
["VLTSRC1", 1],
...
["VLTSRC9", 1]
]
}

Each voltage sources points data table has the following format:

"vltsrcpts":{
"fields":["name", "hn", "vn_v0", "angn"],
"data":[
["VLTSRC1", 11.00000, 1.110000, 18.21000],
...
["VLTSRC9", 13.00000, 1.510000, -150.6100]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
240
Harmonics Data File (RAWX) Current Sources Data

]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to table. Each Voltage Sources
table must have unique NAME. The NAME may be up to 40 characteristics and
may contain any combination of blanks, uppercase letters, numbers and special
characters, but the first character must not be a minus sign. The NAME must be
enclosed in single or double quotes if it contains any blanks or special characters.

No default allowed.
ANGOPTN angoptn Default angle determination

• 0 - No

• 1 - Yes

ANGLE = 0 by default

SINCAL value = Flag_DefAngle

HN hn Harmonic Order

No default allowed.

HN = 0 means end of table data

VN/V0 vn_v0 Ratio of voltage at harmonic order 'N' to voltage at fundamental frequency.

No default allowed.
ANGN angn Angle in degrees at harmonic order 'N'.

No default allowed.

Voltage Sources modeling is not implemented at this time.

7.4. Current Sources Data

The harmonic current sources are defined in this table.

There is no limit on number of harmonics modeled in each current sources table. Each current source char-
acteristics must have fundamental harmonic order specified.

Each current source provided is treated as harmonic current injection at a bus. The pu value of this injection
is calculated as below.

1. When CURTYP=0 (currents in percent of fundamental): The fundamental current to derive its actual PU
contribution is calculated as below.

• Loads, generators, and induction motors - The power flow solution fundamental current (I0) is con-
sidered as 1 PU or 100%.

• Transformers - The base current calculated using system MVA base and bus base voltage of in-service
highest voltage winding bus is considered as 1 PU or 100%.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
241
Harmonics Data File (RAWX) Current Sources Data

• 2TDC, VSCDC and MTDC Lines - Power flow solution fundamental current (I0) at its specified AC bus
is considered as 1 PU or 100%.

• FACTS Device - Power flow solution fundamental current (I0) at its sending end bus is considered as
1 PU or 100%.

2. When CURTYP=1 (currents in amperes): The base current to derive its PU contribution is calculated as
below.

• Loads - System MVA base and bus base voltage

• Generators - Generator MVA base and bus base voltage

• Induction Motor - Induction motor MVA base and bus base voltage

• Transformers - System MVA base and bus base voltage of in-service highest voltage winding bus

• 2TDC, VSCDC, MTDC and FACTS Device - CURTYP=1 not allowed, specify data in terms of CURTYP=0

Following two tables tables specify current source data.

1. Current Source

2. Current Source Points

Each current sources data table has the following format:

"cursrc":{
"fields":["name", "curtyp", "angoptn"],
"data":[
["CURSRC1", 0, 1],
...
["CURSRC9", 0, 1],
]
}

Each current sources points data table has the following format:

"cursrcpts":{
"fields":["name", "hn", "in_i0", "angn"],
"data":[
["CURSRC1", 1.000000, 1.311000, 18.32100],
...
["CURSRC9", 18.00000, 1.359000, -150.3690],
]
}

For a specified equipment/network element, a fundamental current (I0) from power flow solution is ob-
tained. Then that current is used to derive harmonic current.

Each Current Sources data table has the following format. A harmonic current of this value is injected at the
specified bus.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
242
Harmonics Data File (RAWX) Load Data

Field RAWX Key Description

NAME name The non-blank alphanumeric identifier assigned to table. Each Current Sources
table must have unique NAME. The NAME may be up to 40 characteristics and
may contain any combination of blanks, uppercase letters, numbers and special
characters, but the first character must not be a minus sign. The NAME must be
enclosed in single or double quotes if it contains any blanks or special characters.

No default allowed.
CURTYP curtyp Current source type

• 0 - Current in percent of fundamental current

• 1 - Current in amperes

CURTYP = 0 by default
ANGOPTN angoptn Option to determine harmonic source injection phase shift relative to fundamen-
tal current

• 0 - Yes. The angle of harmonic current sources is adjusted/shifted relative to

fundamental frequency power flow solution equipment/network element cur-
rent flow.

• 1 - No. Use the angle specified.

ANGOPTN = 0 by default
HN hn Harmonic Order

Each current source table provided must have data points for fundamental har-
monic order HN=1.0. When there is no injection at HN=1.0, specify I1=0.0,
ANG1=0.0.

No default allowed.

HN = 0 means end of table data

IN or IHN/I0 in_i0 Harmonic current in amperes at harmonic order 'N' or

Percent ratio of harmonic current at harmonic order 'N' to current at fundamental

frequency.

No default allowed.
ANGN angn Harmonic current angle in degrees at harmonic order 'N'.

No default allowed.

7.5. Load Data

The frequency dependency behavior and harmonics contribution of only in-service loads provided on this
data record are modeled.

Each load data record has the following format:

"load":{

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
243
Harmonics Data File (RAWX) Load Data

"fields":["ibus", "id", "hstate", "htype", "hquality", "hireg", "hpk",

"zharm", "vharm", "iharm"],
"data":[
[152, "1", 1, 16, 1.000000, 0.000000, 0.000000,
"ZTABLE1", "VLTSRC1", "CURSRC1"],
...
[3010, "1", 0, 5, 1.000000, 0.000000, 0.000000,
"ZTABLE3", "VLTSRC3", "CURSRC3"]
]
}

Field RAWX Key Description

I ibus Bus number of the bus to which the load is connected. It must be present in the
working case.

No default allowed
ID id One- or two-character load identifier.

ID = '1' by default
HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
HTYPE htype Harmonic Model type

• 0 - No frequency dependency

• 1 - Quality - R constant (serial)

• 2 - Quality - X/R constant (serial)

• 3 - Impedance characteristics

• 4 - Quality - X/R constant (parallel)

• 5 - CIGRE Measurements model

• 6 - Quality - R constant (parallel)

• 7 - IEEE Measurements model

• 8 - IEEE RL Series Model

• 9 - IEEE RL Parallel Model

• 10 - Infinite, ignored in harmonics network

• 11 - IEEE Skin Effect Model

• 12 - IEEE Induction Motor Model

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
244
Harmonics Data File (RAWX) Generator Data

Field RAWX Key Description

• 13 - IEEE 2RL Parallel Model

• 14 - CIGRE Passive Model

• 15 - CIGRE Motive Model

• 16 - Large Area Asynchronous Motor Model

HTYPE = 0 by default

SINCAL value = Flag_Har

HQUALITY hquality Harmonic quality constant

HQUALITY = 1.0 by default.

HIREG hireg Control current

HCTRLCUR = 0.0 by default

SINCAL value = Ireg

HPK hpk Reference Compensation Power

HPK = 0.0 by default

SINCAL value = pk
ZHARM_TA- zharm Previously defined Harmonic Impedance Characteristics table name. The frequen-
BLE cy behavior of the load is modeled using the impedance characteristics specified
in this table when provided.

ZHARM_TABLE = '' by default.

VHARM_TA- vharm Previously defined Harmonic Voltage Source table name. When modeled the load
BLE will inject the voltage harmonics to the network at bus 'I'. The voltage source
value at harmonic order 'N' is calculated using the voltage source characteristics
specified in this table. When table is not found or specified as blank, the voltage
harmonics by the load are ignored.

VHARM_TABLE = '' by default.

VHARM_TABLE is not yet implemented and is ignored.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the load
BLE will inject the current harmonics in the network at bus 'I'. The Current source value
at harmonic order 'N' is calculated using the current source characteristics speci-
fied in this table. When table is not found or specified as blank, the current har-
monics by the load are ignored.

IHARM_TABLE = '' by default.

7.6. Generator Data

The frequency dependency behavior and harmonics contribution of only in-service generators provided on
this data record are modeled.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
245
Harmonics Data File (RAWX) Generator Data

Each generator data record has the following format:

"generator":{
"fields":["ibus", "id", "hstate", "htype", "hquality",
"zharm", "vharm", "iharm"],
"data":[
[101, "1", 0, 3, 1.000000, "ZTABLE1", "VLTSRC1", "CURSRC1"],
...
[3018, "2", 1, 5, 1.000000, "ZTABLE3", "VLTSRC3", "CURSRC3"]
]
}

Field RAWX Key Description

I ibus Bus number of the bus to which the generator is connected. It must be present
in the working case.

No default allowed
ID id One- or two-character generator identifier.

ID = '1' by default
HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
HTYPE htype Harmonic type

• 0 - No frequency dependency, R and X used as in power flow data

• 1 - quality constant R series

• 2 - quality constant X/R series ( generator R data if any, ignored and R calculated
from HQUALITY)

• 3 - Impedance characteristics

• 4 - Model 1: IEEE

• 5 - Model 2: CIGRE Electra 167

• 6 - Model 3: HQ (Hydro Quebec)

• 7 - Infinite, ignored in harmonics network

HTYPE = 0 by default
HQUALITY hquality Harmonic quality constant

HQUALITY = 1.0 by default.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
246
Harmonics Data File (RAWX) Non-Transformer Branch Data

Field RAWX Key Description

ZHARM_TA- zharm Previously defined Harmonic Impedance Characteristics table name. The frequen-
BLE cy behavior of the generator is modeled using the impedance characteristics spec-
ified in this table when provided.

ZHARM_TABLE = '' by default.

VHARM_TA- vharm Previously defined Harmonic Voltage Source table name. When modeled the gen-
BLE erator will inject the voltage harmonics to the network at bus 'I'. The voltage
source value at harmonic order 'N' is calculated using the voltage source charac-
teristics specified in this table. When table is not found or specified as blank, the
voltage harmonics by the generator are ignored.

VHARM_TABLE = '' by default.

VHARM_TABLE is not yet implemented and is ignored.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the gen-
BLE erator will inject the current harmonics in the network at bus 'I'. The Current
source value at harmonic order 'N' is calculated using the current source charac-
teristics specified in this table. When table is not found or specified as blank, the
current harmonics by the generator are ignored.

IHARM_TABLE = '' by default.

7.7. Non-Transformer Branch Data

The frequency dependency behavior of only in-service non-transformer branches provided on this data
record are modeled.

The branch is always modeled with branch resistance skin effect and long line effects considered except
when ZHARM table is specified.

The branch shunts are modeled as per the HTYPE specified below.

Each non-transformer branch data record has the following format:

"ntbranch":{
"fields":["ibus", "jbus", "ckt", "hstate", "htype", "hquality", "zharm"],
"data":[
[151, 152, "1", 1, 4, 1.000000, "ZTABLE1"],
...
[3008, 3009, "1", 0, 0, 1.000000, "ZTABLE6"]
]
}

Field RAWX Key Description

I ibus Branch from bus number. It must be present in the working case.

No default allowed
J jbus Branch to bus number. It must be present in the working case.

No default allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
247
Harmonics Data File (RAWX) Transformer Data

Field RAWX Key Description

CKT ckt One- or two-character non-transformer branch identifier. A branch with cicuit
identifier CKT between buses I and J must be in the working case.

CKT = '1' by default

HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
HTYPE htype Harmonic type. Used to specify branch shunt model.

• 0 - no frequency dependency, R and X used as in power flow data

• 1 - quality constant R series

• 2 - quality constant X/R series (applicable only when branch shunt is inductive),
(Line shunt R data if any, ignored and shunt R calculated from HQUALITY)

• 3 - quality constant R parallel

• 4 - quality constant X/R parallel (applicable only when branch shunt is induc-
tive), (Line shunt R data if any, ignored and shunt R calculated from HQUALITY)

HTYPE = 0 by default
HQUALITY hquality Harmonic quality constant

HQUALITY = 1.0 by default.

ZHARM_TA- zharm Previously defined Harmonic Impedance Characteristics table name. The frequen-
BLE cy behavior of the non-transformer branch is modeled using the impedance char-
acteristics specified in this table when provided.

ZHARM_TABLE = '' by default.

7.8. Transformer Data

The frequency dependency behavior and harmonics contribution of only in-service transformers provided
on this data record are modeled.

Each transformer data record has the following format:

"trbranch":{
"fields":["ibus", "jbus", "kbus", "ckt", "hstate", "htype", "hquality",
"zharm", "iharm"],
"data":[
[101, 151, 0, "T1", 1, 0, 1.000000, "ZTABLE1", "CURSRC1"],
...
[3008, 3012, 3010, "2", 0, 5, 1.000000, "ZTABLE4", "CURSRC4"]
]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
248
Harmonics Data File (RAWX) Transformer Data

Field RAWX Key Description

I ibus Transformer Winding 1 bus number. It must be present in the working case.

No default allowed
J jbus Transformer Winding 2 bus number. It must be present in the working case.

No default allowed
K kbus Transformer Winding 3 bus number. K is specified as 0 (zero) to indicate that no
third winding is present. When K specified is non-zero, it must be present in the
working case.

K = 0 by default.
CKT ckt One- or two-character transformer identifier. A transformer with circuit identifier
CKT between buses I and J (and K if K is non-zero) must be in the working case.

CKT = '1' by default

HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
HTYPE htype Harmonic type

• 0 - No frequency dependency, R and X used as in power flow data

• 1 - Model 1 - CIGRE Electra No. 167

• 2 - Model 2 – IEEE Std. 399

• 3 - Model 3 – CIGRE Electra No. 164

• 4 - Model 4 – Arrillaga

• 5 - Model 5 – Funk

• 6 - Impedance characteristics (allowed only for 2 winding transformers)

HTYPE = 0 by default
HQUALITY hquality Harmonic quality constant, not used
ZHARM_TA- zharm Previously defined Harmonic Impedance Characteristics table name. The frequen-
BLE cy behavior of the transformer is modeled using the impedance characteristics
specified in this table when provided.

ZHARM_TABLE = '' by default.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the
BLE transformer will inject the current harmonics in the network at in-service highest
voltage winding bus. The Current source value at harmonic order 'N' is calculated

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
249
Harmonics Data File (RAWX) Two-Terminal DC Data

Field RAWX Key Description

using the current source characteristics specified in this table. When table is not
found or specified as blank, the current harmonics by the transformer are ignored.

IHARM_TABLE = '' by default.

7.9. Two-Terminal DC Data

The voltage and current harmonics contribution of only in-service two-terminal dc lines provided on this data
record are modeled.

Each two-terminal dc line data record has the following format:

"2tdc":{
"fields":["name", "acbus", "hstate", "vharm", "iharm"],
"data":[
["TWO_TERM_DC1", 301, 1, "VLTSRC1", "CURSRC1"],
...
["TWO_TERM_DC2", 301, 0, "VLTSRC2", "CURSRC2"]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric two-terminal dc line name. It must be present in the
working case.

No default allowed
ACBUS acbus Two-terminal dc line rectifier or inverter converter AC bus number. A two-terminal
dc line 'NAME' with 'ACBUS' as one of the rectifier or inverter buses must be in
the working case.

No default allowed
HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
VHARM_TA- vharm Previously defined Harmonic Voltage Source table name. When modeled the two-
BLE terminal dc line will inject the voltage harmonics to the network at bus 'ACBUS'.
The voltage source value at harmonic order 'N' is calculated using the voltage
source characteristics specified in this table. When table is not found or specified
as blank, the voltage harmonics by the two-terminal dc line are ignored.

VHARM_TABLE = '' by default.

VHARM_TABLE is not yet implemented and is ignored.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the two-
BLE terminal dc line will inject the current harmonics in the network at bus 'ACBUS'.
The Current source value at harmonic order 'N' is calculated using the current

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
250
Harmonics Data File (RAWX) VSC DC Data

Field RAWX Key Description

source characteristics specified in this table. When table is not found or specified
as blank, the current harmonics by the two-terminal dc line are ignored.

IHARM_TABLE = '' by default.

7.10. VSC DC Data

The voltage and current harmonics contribution of only in-service VSC dc lines provided on this data record
are modeled.

Each VSC dc line data record has the following format:

"vscdc":{
"fields":["name", "acbus", "hstate", "vharm", "iharm"],
"data":[
["VDCLINE1", 3005, 1, "VLTSRC1", "CURSRC1"],
...
["VDCLINE2", 203, 0, "VLTSRC2", "CURSRC2"]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric VSC dc line name. It must be present in the working
case.

No default allowed
ACBUS acbus VSC dc line converter AC bus number. A VSC dc line 'NAME' with 'ACBUS' as one
of its converters AC buses must be in the working case.

No default allowed
HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
VHARM_TA- vharm Previously defined Harmonic Voltage Source table name. When modeled the VSC
BLE dc line will inject the voltage harmonics to the network at bus 'ACBUS'. The volt-
age source value at harmonic order 'N' is calculated using the voltage source char-
acteristics specified in this table. When table is not found or specified as blank,
the voltage harmonics by the VSC dc line are ignored.

VHARM_TABLE = '' by default.

VHARM_TABLE is not yet implemented and is ignored.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the VSC
BLE dc line will inject the current harmonics in the network at bus 'ACBUS'. The Current
source value at harmonic order 'N' is calculated using the current source charac-

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
251
Harmonics Data File (RAWX) FACTS Device Data

Field RAWX Key Description

teristics specified in this table. When table is not found or specified as blank, the
current harmonics by the VSC dc line are ignored.

IHARM_TABLE = '' by default.

7.11. FACTS Device Data

The voltage and current harmonics contribution of only in-service FACTS devices provided on this data record
are modeled.

Each FACTS device data record has the following format:

"facts":{
"fields":["name", "sendbus", "termbus", "hstate", "htype", "hquality",
"zharm", "vharm", "iharm"],
"data":[
["FACTS_DVCE_1", 153, 0, 0, 0, 1.000000, "ZTABLE1", "VLTSRC1", "CURSRC1"],
...
["FACTS_DVCE_2", 153, 155, 1, 1, 1.000000, "ZTABLE2", "VLTSRC2", "CURSRC2"]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric FACTS device name. It must be present in the work-
ing case.

No default allowed
SENDBUS sendbus FACTS device Sending End AC bus number. A FACTS device 'NAME' with 'SENDBUS'
as its sending AC bus must be in the working case. A SENDBUS value must be
provided as every FACTS device has as least one bus, making it a shunt device.

No default allowed
TERMBUS termbus FACTS device Terminal End AC bus number. A FACTS device 'NAME' with 'TERMBUS'
as its terminal AC bus must be in the working case. A TERMBUS value must be
provided if the FACTS device is operating as a serial device.

TERMBUS = 0 by default
HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
HTYPE htype Harmonic type

If TERMBUS = 0:

• 0 - No frequency dependency

• 1 - Quality - R constant (serial)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
252
Harmonics Data File (RAWX) FACTS Device Data

Field RAWX Key Description

• 2 - Quality - X/R constant (serial)

• 3 - Impedance characteristics

• 4 - Quality - X/R constant (parallel)

• 5 - CIGRE Measurements model

• 6 - Quality - R constant (parallel)

• 7 - Infinite

If TERMBUS != 0:

• 0 - No frequency dependency

• 1 - Quality - R constant (serial)

• 2 - Quality - X/R constant (serial)

• 3 - Impedance characteristics

HTYPE = 0 by default

SINCAL value = Flag_Har

HQUALITY hquality Harmonic quality constant

HQUALITY = 1.0 by default.

ZHARM_TA- zharm This item is required if the FACTS device is serial device, SENDBUS is not zero and
BLE TERMBUS is not zero.

Previously defined Harmonic Impedance Characteristics table name. The frequen-

cy behavior of the FACTS device is modeled using the impedance characteristics
specified in this table when provided.

ZHARM_TABLE = '' by default.

VHARM_TA- vharm Previously defined Harmonic Voltage Source table name. When modeled the FAC-
BLE TS device will inject the voltage harmonics to the network at bus 'SENDBUS'. The
voltage source value at harmonic order 'N' is calculated using the voltage source
characteristics specified in this table. When table is not found or specified as
blank, the voltage harmonics by the FACTS device are ignored.

VHARM_TABLE = '' by default.

VHARM_TABLE is not yet implemented and is ignored.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the FAC-
BLE TS device will inject the current harmonics in the network at bus 'SENDBUS'. The
Current source value at harmonic order 'N' is calculated using the current source
characteristics specified in this table. When table is not found or specified as
blank, the current harmonics by the FACTS device are ignored.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
253
Harmonics Data File (RAWX) Induction (asynchronous) Machine Da-
ta

Field RAWX Key Description

IHARM_TABLE = '' by default.

7.12. Induction (asynchronous) Machine Data

The frequency dependency behavior and harmonics contribution of only in-service induction machines pro-
vided on this data record are modeled.

Each induction machine data record has the following format:

"indmach":{
"fields":["ibus", "id", "hstate", "htype", "hquality",
"zharm", "vharm", "iharm"],
"data":[
[3010, "1", 1, 2, 1.000000, "ZTABLE1", "VLTSRC1", "CURSRC1"],
...
[93002, "1", 1, 9, 1.000000, "ZTABLE4", "VLTSRC4", "CURSRC4"]
]
}

Field RAWX Key Description

I ibus Bus number of the bus to which the induction machine is connected. It must be
present in the working case.

No default allowed
ID id One- or two-character induction machine identifier.

ID = '1' by default
HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
HTYPE htype Harmonic type

• 0 - No frequency dependency

• 1 - Quality - R constant

• 2 - Quality - X/R constant

• 3 - Impedance characteristics

• 4 - Infinite

HTYPE = 0 by default

SINCAL value = Flag_Har

HQUALITY hquality Harmonic quality constant

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
254
Harmonics Data File (RAWX) Multi-Terminal DC Data

Field RAWX Key Description

HQUALITY = 1.0 by default.
ZHARM_TA- zharm Previously defined Harmonic Impedance Characteristics table name. The frequen-
BLE cy behavior of the induction machine is modeled using the impedance character-
istics specified in this table when provided.

ZHARM_TABLE = '' by default.

VHARM_TA- vharm Previously defined Harmonic Voltage Source table name. When modeled the in-
BLE duction machine will inject the voltage harmonics to the network at bus 'I'. The
voltage source value at harmonic order 'N' is calculated using the voltage source
characteristics specified in this table. When table is not found or specified as
blank, the voltage harmonics by the induction machine are ignored.

VHARM_TABLE = '' by default.

VHARM_TABLE is not yet implemented and is ignored.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the in-
BLE duction machine will inject the current harmonics in the network at bus 'I'. The
Current source value at harmonic order 'N' is calculated using the current source
characteristics specified in this table. When table is not found or specified as
blank, the current harmonics by the induction machine are ignored.

IHARM_TABLE = '' by default.

7.13. Multi-Terminal DC Data

The voltage and current harmonics contribution of only in-service multi-terminal dc lines provided on this
data record are modeled.

Each multi-terminal dc line data record has the following format:

"mtdc":{
"fields":["name", "acbus", "hstate", "vharm", "iharm"],
"data":[
["MULTERM_DC_1", 402, 1, "VLTSRC4", "CURSRC4"],
...
["MULTERM_DC_1", 213, 1, "VLTSRC2", "CURSRC2"]
]
}

Field RAWX Key Description

NAME name The non-blank alphanumeric multi-terminal dc line name. It must be present in
the working case.

No default allowed
ACBUS acbus Multi-terminal dc line rectifier or inverter converter AC bus number. A multi-ter-
minal dc line 'NAME' with 'ACBUS' as one of the rectifier or inverter buses must
be in the working case.

No default allowed
HSTATE hstate Current control state

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
255
Harmonics Data File (RAWX) Passive Filter Data

Field RAWX Key Description

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
VHARM_TA- vharm Previously defined Harmonic Voltage Source table name. When modeled the mul-
BLE ti-terminal dc line will inject the voltage harmonics to the network at bus 'ACBUS'.
The voltage source value at harmonic 'N' is calculated using the voltage source
characteristics specified in this table. When table is not found or specified as
blank, the voltage harmonics by the multi-terminal dc line are ignored.

VHARM_TABLE = '' by default.

VHARM_TABLE is not yet implemented and is ignored.

IHARM_TA- iharm Previously defined Harmonic Current Source table name. When modeled the mul-
BLE ti-terminal dc line will inject the current harmonics in the network at bus 'ACBUS'.
The Current source value at harmonic 'N' is calculated using the current source
characteristics specified in this table. When table is not found or specified as
blank, the current harmonics by the multi-terminal dc line are ignored.

IHARM_TABLE = '' by default.

7.14. Passive Filter Data

The passive filter will be added as fixed bus shunt to PSSE working case only during harmonic analysis ac-
tivities.

For each harmonic frequency, the fixed bus shunt MW and MVAR are calculated and the working case updated
accordingly.

Given RG, XB1 and XB2 at the fundamental frequency and CZY, the units in which they are specified, the
passive filter equivalent impedance and corresponding fixed bus shunt MW and MVAR are calculated.

The passive filter specified with "I, ID" should not exist in the working case as the Fixed Bus Shunt "I, ID". If
Fixed Bus Shunt "I, ID" exists in the working case, the passive filter specified with "I, ID" will be ignored.

Each Passive Filter data record has the following format:

"pfilter":{
"fields":["ibus", "id", "hstate", "czy", "cfg", "rg", "xb1", "xb2"],
"data":[
[101, "FO", 0, 0, 1, 0.1000000, 0.2000000, 0.3100000],
...
[204, "YK", 0, 0, 2, 0.1000000, 0.2000000, 0.3200000]
]
}

Field RAWX Key Description

I ibus Bus number of the bus to which the passive filter is connected. It must be present
in the working case.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
256
Harmonics Data File (RAWX) Passive Filter Data

Field RAWX Key Description

No default allowed
ID id One- or two-character passive filter identifier.

No default allowed
NAME name Alphanumeric identifier assigned to the Passive Filter. NAME may be up to forty
characters and may contain any combination of blanks, uppercase letters, num-
bers and special characters. NAME must be enclosed in single or double quotes if
it contains any blanks or special characters.

NAME must be unique within all passive filters. By default name is generated as
string formed with bus number + filter ID.
HSTATE hstate Current control state

• 0 - Not active in harmonics

• 1 - Active in harmonics

HSTATE = 1 by default
CZY czy Units of RG, XB1 and XB2

• 0 - Impedance expressed in PU on bus voltage and system MVA base

• 1 - Admittance expressed in PU on bus voltage and system MVA base

• 2 - Admittance expressed in MW and MVAR at 1 PU voltage

• 3 - Impedance expressed in ohms. XB1 and XB2 are expressed as positive for
inductive reactance and negative for capacitive reactance. The filter per unit
impedance is calculated on bus voltage and system MVA base.

• 4 - RG is resistance in PU, XB1 in inductive reactance in PU, XB2 is capacitive

susceptance in PU on bus voltage and system MVA base

CZY = 0 by default
CFG cfg Configuration of RG, XB1 and XB2

• 0 - RG, XB1, XB2 are connected in series

• 1 - RG, XB1, XB2 are connected in parallel

• 2 - RG and XB1 are connected in parallel and that equivalent in series with XB2

• 3 - RG and XB2 are connected in parallel and that equivalent in series with XB1

CFG = 0 by default
RG rg Resistance, Conductance or MW as per CZY

RG = 0.0 by default.
XB1 xb1 Reactance, Susceptance or MVAR as per CZY

XB1 = 0.0 by default.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
257
Harmonics Data File (RAWX) Passive Filter Data

Field RAWX Key Description

XB2 xb2 Reactance, Susceptance or MVAR as per CZY

XB2 = 0.0 by default.

RG is positive for resistance, conductance and MW.

XB1 and XB2 are positive for inductive reactance and capacitive susceptance.

XB1 and XB2 are negative for inductive susceptance and capacitive reactance .

XB1 and XB2 are positive for capacitive MVAR.

XB1 and XB2 are negative for inductive MVAR.

When RG, XB1 and XB2 are 0.0 (zero), the record will be ignored.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
258
 Chapter 8
Machine Capability Curve Data File

8.1. Overview
The input stream to activity REGC consists of a Change Code record, followed by a group of capability curve
data records. One such record is specified for each machine whose capability curve is to be read into the
working case.

All data is read in free format with data items separated by a comma or one or more blanks. The capability
curve data category is terminated by a record specifying an I value of zero.

8.2. Change Code Data

The first record in the Capability Curve Data File contains two data items as follows:

IC, REV

IC New capability curve data flag:

IC = 0 indicates the initial input of capability curve data for the network contained in
the working case. Any capability curves in the case are deleted from the case before
adding the capability curves specified in the input file.

IC = 1 indicates change case input of capability curve data for the network contained
in the working case. If a record is specified for a machine that already has a capability
curve, default values for omitted data items are the existing values of the capability
curve.

IC = 0 by default
REV PSSE revision number

REV = current revision by default

8.3. Capability Curve Data

Each machine to be represented with its capability curve in PSSE must be specified in a capability curve data
record. Each data record in this file has the following format:

I, ID, P1, QT1, QB1, P2, QT2, QB2, ... P20, QT20, QB20

where:

I Bus number. Bus I must be present in the working case with a plant sequence number
assigned to it (refer to Section Plant and Machine Sequence Numbers in POM).

No default is allowed

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
259
Machine Capability Curve Data File Capability Curve Data

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
Pi Generator active power output along the MW axis of the machine's capability curve,
entered in MW

No default is allowed
QTi Maximum (i.e., overexcited) reactive power limit at P i MW, entered in Mvar

QTi = 0.0 by default

QBi Minimum (i.e., underexcited) reactive power limit at P i MW, entered in Mvar

QBi = 0.0 by default

At least two sets of points must be specified for each capability curve; up to 20 sets of points on the capability
curve may be entered. When the machine is a generator, the Pi values must be in ascending order with
P1greater than or equal to zero. When the machine is a motor, the Pi values must be in descending order
with P1 less than or equal to zero.

Capability curves may be specified for non-conventional as well as conventional machines. For a non-con-
ventional machines with machine control mode (WMOD) greater than 1, the capability curve will not be used
to update the machine's reactive power limits; the limits will be determined from the specified power factor
(WPF) for mode 2 and 3 machines, and from the machine's fixed reactive power (QG) for mode 4 machines.

Data input is terminated with a record specifying a bus number of zero.

®
In the PSS E EXAMPLE directory, there is an example capability curve established for the machines in the
savnw.sav power flow case. The data file is savnw.gcp, and the contents of the file are listed in Figure 8.1,
“Capability Curve Example file savnw.gcp for savnw.sav Case”.
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSS(R)E TUE, SEP 24 2019 12:29
PSS(R)E PROGRAM APPLICATION GUIDE EXAMPLE
BASE CASE INCLUDING SEQUENCE DATA

CAPABILITY CURVE CHECK:

X-- CAPABILITY CURVE --X X------- WORKING CASE -------X
BUS#-SCT X-- NAME --X BASKV ID PGEN QGEN QMAX QMIN PLIMIT QMAX QMIN PMAX PMIN
101 NUC-A 21.600 1 750.0 81.3 243.8 -37.5 900.0 600.0 -100.0 810.0 0.0
102 NUC-B 21.600 1 750.0 81.3 243.8 -37.5 900.0 600.0 -100.0 810.0 0.0
206 URBGEN 18.000 1 800.0 600.0 600.0 0.0 1000.0 600.0 0.0 900.0 0.0
211 HYDRO_G 20.000 1 600.0 17.3 583.3 -77.8 950.0 400.0 -100.0 616.2 0.0
3011 MINE_G 13.800 1 258.6 103.6 270.5 -100.0 1000.0 600.0 -100.0 900.0 0.0
3018 CATDOG_G 13.800 1 100.0 80.0 80.0 0.0 130.0 80.0 0.0 117.0 0.0

Figure 8.1. Capability Curve Example file savnw.gcp for savnw.sav Case

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
260
 Chapter 9
IEC Data File

9.1. Overview
The impedances and admittances of electrical equipment in the working case are modified according to the
correction factors defined in IEC 60909-0 (2016 Section 6 or 2001 Section 3).

Generators, equivalent generators, asynchronous motors, wind farms and photovoltaic (PV) farms are repre-
sented as sources in the working case. To calculate their impedance correction factors or correct contribution
to fault additional data is required. This additional data is provided in IEC data file (.iec).

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.

• If an induction machine base power (MBASE) is specified as mechanical power output (BCODE=1), then
power factor and efficiency are needed to calculate base MVA. If an induction machine scheduled active
power (PSET) is set as real electrical power drawn by the machine, efficiency is needed to calculate me-
chanical power output (MW) of the machine.

• If a generator in the working case is a Wind Farm or PV Farm.

There are six groups of records, with each group containing a particular type of data required. Each record
is terminated by specifying a bus number of 0.

9.2. File Identification Data

This record contains only one data item which is specified as:

IECFILEVRSN=vernum

IECFILEVRSN IECFILEVRSN is the keyword to specify the IEC data file version number.

vernum is an integer value specifying IEC data file version number. No default al-
lowed.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
261
IEC Data File GSU, Equivalent Generator and Motor
Data

Allowed, IECFILEVRSN = 2

Note: The first release of the IEC data file did not have this record and is treated as
file version 1

9.3. GSU, Equivalent Generator and Motor Data

(Induction Motors are specified as part of Generator data category.)

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 Induction machines specified as part of generator data category

MCTYPE =4, for Wind power station asynchronous generator

MCTYPE =5, for Wind power station double fed asynchronous generator

MCTYPE =6, for Wind or Photovoltaic power station generator with full size convert-
er
UrG Rated terminal voltage, line-to-line in kV r.m.s. (this need not be the rated bus volt-
age)
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 Generator rated power factor (used only if MCTYPE=1).

This is used in impedance correction factor calculations.

= 1.0 default
PolePair Number of pole pairs if machine is induction machine (used only if the machine is
modeled as induction machine)

Example: If the induction machine 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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
262
IEC Data File Transformer Nameplate Winding MVA
Data

GSUType =2, GSU without OLTC

Ix GSU transformer I bus number

= 0 by default to specify no GSU transformer

Jx GSU transformer J bus number

= 0 by default to specify no GSU transformer

Kx GSU transformer K bus number

= 0 by default to specify no GSU transformer

Ckt GSU transformer circuit identifier

= blank ('') by default to specify no GSU transformer

PT Tap range of GSU off-load tap-changer transformer in % of transformer winding rat-
ed voltage, e.g., if PT is ±5%, enter PT=5

= 0.0 by default to ignore off-load tap range

9.4. 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:

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)

9.5. Induction Machine Data

(Induction Motors are specified as part of Induction machine data category)

Each data record has the following format:

I, ID, PolePair, PFactor, Efficiency

where:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
263
IEC Data File Wind Power Station Asynchronous Gen-
erator Data

I Machine bus number

ID Machine ID
PolePair Number of pole pairs

Example: If the induction machine has a six pole construction then Polepair=3
PFactor Induction Machine rated power factor

= 1.0 default
Efficiency Induction Machine percent efficiency.

=100 by default

Example: Efficiency=96.5 for 96.5% efficiency.

9.6. Wind Power Station Asynchronous Generator Data

(These equipment are specified as part of Generator data category and modeled as MCTYPE=4 in IEC data
file.)

Each data record has the following format:

I, ID, ILR2IR_1, R2X_1, ILR2IR_2, R2X_2, ILR2IR_0, R2X_0

where:

I Machine bus number

ID Machine ID
ILR2IR_1 Ratio of Positive Sequence locked rotor current to rated current, no default allowed.
R2X_1 Ratio of Positive Sequence resistance to reactance =0.1 by default
ILR2IR_2 Ratio of Negative Sequence locked rotor current to rated current ILR2IR_2=ILR2IR_1
by default
R2X_2 Ratio of Negative Sequence resistance to reactance R2X_2=R2X_1 by default
ILR2IR_0 Ratio of Zero Sequence locked rotor current to rated current ILR2IR_0=ILR2IR_1 by
default
R2X_0 Ratio of Zero Sequence resistance to reactance R2X_0=R2X_1 by default

9.7. Wind Power Station Doubly Fed Asynchronous

Generator Data
(These equipment are specified as part of Generator data category, and modeled as MCTYPE=5 in IEC data
file.)

Each data record has the following format:

I, ID, IMAX_1, R2X_1, IMAX_2, R2X_2, IMAX_0, R2X_0, KWD, IKWDmax, IKWDmin

where:

I Machine bus number

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
264
IEC Data File Wind and Photovoltaic Power Station
Generator with Full Size Converter Data

ID Machine ID
IMAX2IR_1 Ratio of Positive Sequence highest instantaneous short circuit value in case of a
three-phase short circuit to rated current, no default allowed
R2X_1 Ratio of Positive Sequence resistance to reactance. R2X_1=0.1 by default
IMAX2IR_2 Ratio of Negative Sequence highest instantaneous short circuit value in case of an
unbalance short circuit to rated current, IMAX2IR_2=IMAX2IR_1 by default
R2X_2 Ratio of Negative Sequence resistance to reactance. R2X_2=R2X_1 by default
IMAX2IR_0 Ratio of Zero Sequence highest instantaneous short circuit value in case of an unbal-
ance short circuit to rated current, IMAX2IR_0=IMAX2IR_1 by default
R2X_0 Ratio of Zero Sequence resistance to reactance. R2X_0=R2X_1 by default
KWD Factor for the calculation of the peak short-circuit current, KWD=1.7 by default
IkWDmax Ratio of maximum steady state short circuit current to rated current, IkWDmax=I-
MAX2IR_1 by default. This is used in calculation of symmetrical breaking current.
IkWDmin Ratio of minimum steady state short circuit current to rated current, IkWDmin=I-
MAX2IR_1 by default. This is used in calculation of symmetrical breaking current.

9.8. Wind and Photovoltaic Power Station Generator

with Full Size Converter Data
(These equipment are specified as part of Generator data category, and modeled as MCTYPE=6, 7 in IEC
data file.)

Each data record has the following format:

I, ID, IMAX_1, R2X_1, IMAX_2, R2X_2, IMAX_0, R2X_0, IkPFmax, IkPFmin

where:

I Machine bus number

ID Machine ID
IMAX2IR_1 Ratio of Positive Sequence short circuit current value to rated current, no default al-
lowed
R2X_1 Ratio of Positive Sequence resistance to reactance. R2X_1=0.1 by default
IMAX2IR_2 Ratio of Negative Sequence short circuit current value to rated current,
IMAX2IR_2=IMAX2IR_1 by default
R2X_2 Ratio of Negative Sequence resistance to reactance. R2X_2=R2X_1 by default
IMAX2IR_0 Ratio of Zero Sequence short circuit value in case of an unbalance short circuit to
rated current, IMAX2IR_0=IMAX2IR_1 by default
R2X_0 Ratio of Zero Sequence resistance to reactance. R2X_0=R2X_1 by default
IkPFmax Ratio of maximum steady state short circuit current to rated current, IkPFmax=I-
MAX2IR_1 by default. This is used in calculation of symmetrical breaking current.
IkPFmin Ratio of minimum steady state short circuit current to rated current, IkPFmin=I-
MAX2IR_1 by default. This is used in calculation of symmetrical breaking current.

IEC File Data records for generators, transformers and motors are created only for those units that need IEC
data and they may be entered in any order and using a free format with blanks or commas separating each
data item in each record group.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
265
IEC Data File Wind and Photovoltaic Power Station
Generator with Full Size Converter Data

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
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 INDUCTION MACHINE DATA
0 / END OF TRANSFORMER DATA
7 M1 1 0.88 97.5
7 M2 2 0.89 96.8
7 M3 2 0.89 96.8
0 / END OF INDUCTION MACHINE DATA
Q

or

IECFILEVRSN=2
1 Q1 2
5 Q2 2
6 G3 6 10.5 0.0 0.8
41 G1 4 21.0 0.0 0.85 0 1 4 41 0 T1 12
31 G2 5 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
7 M1 1 0.88 97.5
7 M2 2 0.89 96.8
7 M3 2 0.89 96.8
0 / END OF INDUCTION MACHINE DATA
41 G1 5.0 0.2
0 / END OF WIND POWER STATION ASYNCHRONOUS GENERATOR DATA
31 G2 6.0 0.3
0 / END OF WIND POWER STATION DOUBLY FED ASYNCHRONOUS GENERATOR DATA
6 G3 7.0 0.4
0 / END OF WIND AND PHOTOVOLTAIC POWER STATION GENERATOR WITH FULL SIZE CONVERTER DATA
Q

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
266
 Chapter 10
SUB/MON/CON File Descriptions

10.1. Overview
This section contains details on the formats of the data input files used by activity DFAX. File Notational
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. Sec-
tion 10.2, “Subsystem Definition Data File” gives the record formats used in the Subsystem Definition data
file, Monitored Element Data File describes the Monitored Element data file, and Contingency Definition Data
File defines the Contingency Definition data file.

10.1.1. File Notational Conventions

In describing the input file syntax, the following notational conventions are used:

CAPITALS Keyword that must be specified exactly as shown. No

keyword abbreviations are allowed.
[…] Items enclosed in square brackets are optional key-
words and/or values.
|A| or A|B Specify one from the list separated by, or enclosed in,
|B| 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 ef-
fect (refer to Section 3.3.3, “Program Run-Time Op-
tion Settings” and activity OPTN). If an extended bus
name contains blanks or special characters, it must
be enclosed in single quotes.
bsid1 bsid2 A range of bus identifiers.
staid Substation identifier; this data value must be a sub-
station number.
ndid Substation node identifier; this data value must be
a valid substation node number for the substation
specified in the same context.
ckid One-or two-character circuit identifier.
mcid, ldid, shid, swid, imid One- or two-character equipment identifier for a ma-
chine, load, shunt, switched shunt, or induction ma-
chine, respectively.
devid FACTS device or dc line name; up to twelve charac-
ters. If a device name contains blanks or special char-
acters, it must be enclosed in single quotes.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
267
SUB/MON/CON File Descriptions Bus Input/Output Using Bus Numbers
and Names

i An integer value.
ij An range of integer values.
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).
r1 r2, or rlow rhigh A range of floating point values.
filename A filename. Up to 260 characters is allowed.
label A 32-character label identifier. If a label contains
blanks or special characters, it must be enclosed in
single quotes.
category-string Up to 160 characters are allowed. If the string con-
tains blanks or special characters, it must be enclosed
in single quotes.

The total size of all the category-strings in a CATEGO-

RY structure combined is limited. The limit depends
on a number of things, but is certainly less than 300
characters

Keywords and data values must be separated by one or more blanks.

10.1.2. Bus Input/Output Using Bus Numbers and Names

® ®
PSS E allows users to specify buses by using either bus numbers or names. PSS E's bus input/output mode
is set to bus numbers by default.
®
PSS E will automatically accept bus names of the format ‘nnnnnnnnnnnnvvvv’ (12-character name plus 4-
character voltage); where nnnnnnnnnnnn is the name portion and vvvv the voltage portion of the bus name.

Bus names have to be specified via a name and voltage level as shown below:

BUS ‘ALPHABETA 345’ / Bus name

BUS ‘GAMMAALPHAXX 169’ 11.000 / Bus name with participation factor
®
There are two ways to tell PSS E to use the bus name. It can be done by changing the BUS Input/Output
option or by directly using the BUSNAMES command in the input file.

Inputting by bus names provides independence from bus numbering, and allows bus renumbering, which
is done by some companies in the United States on a consistent basis when creating combined load flow
cases. It is quite common to use bus names in various transfer analysis/assessment reports.
®
To accommodate the advantages of both types of bus input, PSS E allows the user to alternate between the
two modes of bus input within the same input files. For example, one subsystem may be defined using a
bus name, the next one using bus numbers; or, define a subsystem file by using bus names, and then use
input by bus number to define monitored elements.

Changing bus input mode can be done anywhere in the subsystem, contingent, monitored, and/or exclude
data input files via BUSNAMES and BUSNUMBERS keywords. BUSNAMES and BUSNUMBERS records are spec-
ified on separate input lines.

BUSNAMES / will switch input to read by bus names

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
268
SUB/MON/CON File Descriptions Special Data Records

BUSNUMBERS / will switch input to read by bus number

The default mode for specifying the use of bus names or bus numbers can be set by selecting the BUS In-
put/Output option. If a user has redefined the input mode to bus name, this redefinition will propagate to
other input functions. For example, if a user used bus input by names to read in the subsystem file, then
®
PSS E will use bus names input mode when reading monitored element and contingency files. Only the ex-
plicit record BUSNUMBERS will switch the bus input mode to bus numbers.

10.1.3. Special Data Records

The following record types are allowed in each of the Linear Network Analysis data files:

TRACE Enable or disable input tracing. When enabled, each

line read from the input file is written to the Progress
tab or the user’s designated output file; refer to Sec-
tion 4.4, “Virtual Output Devices”. Tracing is initially
disabled.
ECHO filename Write each input line to the designated file; if the file-
name 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 specified here is completely independent of
®
any file specified to the PSS E activity ECHO (refer
to Section 19.12, “Running a Response File” and Sec-
tion 19.13, “Recording User Actions”). Refer to Sec-
tion 2.4.1, “File Usage ” for the file specification con-
ventions used by activity DFAX.
COM Comment line that is ignored during input process-
ing. 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 appro-
priate.

In addition, blank lines may be included anywhere in the file. These are ignored during the input file pro-
cessing.

10.2. Subsystem Definition Data File

Subsystems of the working case are defined via the Subsystem Definition data file. While format details
differ, the subsystem definition provided is functionally identical to the specification of subsystems via the
®
bus subsystem selector dialog and the optional suffixes of many PSS E reporting and processing activities
(refer to Section 4.8, “Subsystem Selection”).

The portion of the working case to be contained in each subsystem being defined is specified in the following
block structure:

SUBSYSTEM|SYSTEM [label]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
269
SUB/MON/CON File Descriptions Subsystem Definition Data File

(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
Definition 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 Definition 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.

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, “Program
Run-Time Option Settings” 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 j

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 j
OWNER i
OWNERS i j

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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
270
SUB/MON/CON File Descriptions Subsystem Definition Data File

KVRANGE r1 r2

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 user’s
convenience and is neither used by activity DFAX nor preserved in the Distribution Factor data file.

Each join group block structure must appear within the subsystem block structure described above. Both join
group block structures and the simple record types may be included within a subsystem block structure.

The following example defines the subsystem MY COMPANY, which consists of all buses in Area 5, along with
all buses in Area 6, which are in Zones 8 through 10:

SUBSYSTEM 'MY COMPANY'

AREA 5
JOIN 'GROUP 1'
AREA 6
ZONES 8 10
END
END

A single bus or a set of buses can be excluded from a subsystem with the SKIP commands as described below.
The commands must follow the simple subsystem specification records and/or join group block structures; in
other words they must be the last records or only appear before the participation block within the subsystem
specification block.

A single bus may be excluded from a subsystem with the data record in the form of:

SKIP BUS bsid

A set of buses may be excluded form a subsystem with the following data records:

SKIP BUS WITH [IN-SERVICE] |LOAD | |LESS | r |MW |

|GENERATION | |GREATER| |MVAR|

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
271
SUB/MON/CON File Descriptions Subsystem Definition Data File

|GENUPLIMIT | |MVA |
|GENLOWLIMIT|
|SHUNT |

When the optional IN-SERVICE keyword is present, only in-service components are considered in summation,
otherwise both in-service and out-of-service components are counted. The 'r' value is the threshold in the
specified unit of one of keywords MW, MVAR, or MVA. In using the LESS keyword, a bus is skipped from
a subsystem if the corresponding data quantity of the bus is less than the 'r' value. In using the GREATER
keyword, a bus is skipped from a subsystem if its data quantity is greater than the 'r' value.

At each bus that is assigned to the subsystem, in using LOAD keyword the total nominal load of loads is
compared against the 'r' value. When the GENERATION keyword is used, the total generation of the machines
is compared against the 'r' value. In using GENUPLIMIT or GENLOWLIMIT keyword, the corresponding total
upper or lower limit of machines is considered in the summation. When the SHUNT keyword is present, the
total nominal output of bus fixed shunts is used for comparing against the 'r' value.

The following data record can be used to exclude buses from a subsystem by comparing the current nominal
reactive power output from the switched shunt at the buses against the 'r' value.

SKIP BUS WITH [IN-SERVICE] SWSHUNT |LESS | r MVAR

|GREATER|

The following data record can be used to exclude buses by comparing the total active power settings of
induction machines at the buses against the 'r' value.

SKIP BUS WITH [IN-SERVICE] INDUCMACHINE |LESS | r MVAR

|GREATER|

A “SKIP” record can be used to exclude a single bus or a group of buses from a subsystem, as shown in the
following example.

SYSTEM MONITOR5
AREA 5
SKIP BUS 567
SKIP BUS WITH GENUPLIMIT LESS 10 MW
END

SKIP records must “follow” the simple subsystem specification records and/or join group block structures
within the subsystem specification block.

Activities TLTG, SPIL, and POLY and the PV Analysis calculation modify the generation/load profile within
designated subsystems to determine transfer capability. The participation block structure allows the user to
specify those buses that are to participate in the generation/load shift, along with their participation factors
that determine how the change in subsystem power injection is to be shared among the designated buses.
To establish the participating buses and their participation factors, the PARTICIPATE block structure is used.

The form of the participation block structure is:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
272
SUB/MON/CON File Descriptions Monitored Element Data File

PARTICIPATE
BUS bsid r
.
.
BUS bsid r
END

Each participation block structure must appear within the subsystem block structure described above, and
must follow the simple record types and/or join group block structures defining the SUBSYSTEM; that is, it
must be the last data record block in the SUBSYSTEM specification.

Each bus specified must be present in the subsystem being processed. Any bus that violates this requirement
or which is disconnected (i.e., its type code is four or greater) generates an alarm and is excluded from the
group of participating buses.

The r values are non-zero participation factors that are normally expressed in percent or per unit of the total
subsystem generation shift. While individual r values may be negative, the sum of the r values within a
participate block structure must be positive.

10.3. Monitored Element Data File

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.

10.3.1. Individual 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 substation switching device for monitoring, the following data record may be used:

MONITOR |BREAKER| |SUBSTATION| staid FROM NODE ndid TO NODE ndid [|CIRCUIT | ckid]
|SWITCH | |SUB | |CKT |
|SWD |

To specify a single branch for monitoring, the following data record may be used:

[MONITOR] |BRANCH| FROM BUS bsid TO BUS bsid [|CIRCUIT| ckid]

|LINE | |CKT |

To specify one winding of a three-winding transformer for monitoring, the bus to which the winding is con-
nected must be the first bus specified in the following data record:

[MONITOR] |BRANCH| FROM BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
273
SUB/MON/CON File Descriptions Group Flow Monitoring Records

|LINE | |CKT |

Example:

Monitor branch from bus 288 to bus 2000 to bus 398

The above example will only monitor flow into the winding of the three-winding transformer connected
to bus 288. If it is desired to monitor bus 2000 and bus 398 flows into the transformer additional monitor
statements are required.

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, “Program Run-Time Option
Settings” 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.

When the multi-section line reporting option is disabled, multi-section line groupings may not be specified
in the above records; in-service members of multi-section line groupings may be designated and are added
as specified to the monitored element list.

10.3.2. Group Flow Monitoring Records

The following four record types provide for the addition of a group of branches to the monitored element list
with a single record. When the keyword BRANCHES, LINES, or TIES is used, all branches in the grouping
except breakers and switches are added as monitored elements. When using the BREAKERS keyword, only
breaker and switch branches in the grouping are added as monitored elements. Any branch that is included
in the subset specified by the record, but which is already included in the monitored element list in either
direction, is skipped.

For these record types, when the multi-section line reporting option is enabled, multi-section line groupings
within the specified subset, but not the individual members of such groupings, are added to the monitored
line list. When the multi-section line reporting option is disabled, members of multi-section line groupings
within the specified subset, but not the multi-section line groupings, are added to the monitored line list.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
274
SUB/MON/CON File Descriptions Group Flow Monitoring Records

To place all branches in the monitored element list, the following data record may be used:

[MONITOR] ALL |BRANCHES|

|LINES |
|BREAKERS|

Branches are entered into the monitored element list in single entry form, with the lower ordered bus (num-
ber or name, according to the bus output option currently in effect) as the from bus.

The following data record may be used to select for monitoring all branches connected to a specified bus:

[MONITOR] |BRANCHES| FROM BUS bsid

|LINES |
|BREAKERS|

All branches within a specified subsystem may be monitored by entering the data record:

[MONITOR] |BRANCHES| IN |AREA i | [3WLOWVOLTAGE] [IN KVRANGE r1 r2]

|LINES | |AREAS i j |
|ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r1 |
|KVRANGE r1 r2 |
|SYSTEM label|
|SUBSYSTEM label|

When using the SYSTEM or SUBSYSTEM keywords, the label must correspond to a subsystem label specified
in a previously accessed Subsystem Definition data file (refer to Section 10.2, “Subsystem Definition Data
File”).

For a three-winding transformer to be included, without the keyword 3WLOWVOLTAGE specified all of its in-
service windings must be connected to subsystem buses; when using the keyword 3WLOWVOLTAGE, checking
on connection of its low voltage winding to a subsystem bus is disabled if all its three winding bus voltages are
specified as non-zero values. For any such three-winding transformer, all of its in-service windings connected
to subsystem buses are added to the monitored element list.

The IN KVRANGE keyword can be added to simplify defining monitored elements within a desired voltage
range. The first r1 is the lower bound of the voltage range, and the second r2 is the upper bound of the
voltage range. With IN KVRANGE keyword, all terminal buses of selected branches are within the desired
voltage range.

When AREAS, ZONES or OWNERS is specified, a range of items is selected based on the i and j values entered.

To place branches that are assigned to a line owner into the monitored element list, the following data record
can be used:

[MONITOR] |LINES | WITH LINE OWNER i

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
275
SUB/MON/CON File Descriptions Subsystem Tie Monitoring Records

|BRANCHES|
|BREAKERS|

10.3.3. Subsystem Tie Monitoring Records

The following record provides for the monitoring of all ties from a specified subsystem, or all ties between
a pair of subsystems:

[MONITOR] |TIES| FROM |AREA i | [TO |AREA i |] [IN KVRANGE r1 r2]

|TIE | |AREAS i j | |AREAS i j |
|ZONE i | |ZONE i |
|ZONES i j | |ZONES i j |
|OWNER i | |OWNER i |
|OWNERS i j | |OWNERS i j |
|KV r1 | |KV r2 |
|KVRANGE r1 r2 | |KVRANGE r1 r2 |
|SYSTEM label| |SYSTEM label|
|SUBSYSTEM label| |SUBSYSTEM label|

The main difference between the IN, FROM, and TO specifications is that IN specifies the kV requirement of
both terminal buses for the selected branches, while the FROM and TO specifications define only the from
or to selection, respectively.

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.

The following provides several examples of selecting monitored branches using the formats described above.

Example:

MONITOR BRANCHES IN AREA 1

MONITOR BRANCHES IN KVRANGE 200 999
MONITOR BRANCHES IN AREAS 40 42 IN KVRANGE 100 300
MONITOR BRANCHES IN AREA 1 IN KVRANGE 100 300
MONITOR TIES FROM AREA 1 IN KVRANGE 100 999}
MONITOR TIES FROM AREA 1 TO AREA 5 IN KVRANGE 100 999

The user must be aware that specification:

MONITOR BRANCHES IN AREAS 40 42 IN KVRANGE 100 300

includes not only branches within areas 40, 41, and 42, but also all ties between areas 40, 41, and 42.

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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
276
SUB/MON/CON File Descriptions Subsystem Tie Monitoring Records

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:

Bus Area Zone

1 1 10
2 1 5
3 2 5
4 1 5

Further, assume that a branch exists between each pair of buses. The following record would include branch-
es 1-3, 2-3, and 4-3, but not 1-2, 1-4, or 2-4:

TIES FROM AREA 1 TO ZONE 5

Conversely, the following record would include branches 2-1, 3-1, and 4-1, but not 2-3, 2-4, or 3-4:

TIES FROM ZONE 5 TO AREA 1

When the multi-section line reporting option is enabled (refer to Section 3.3.3, “Program Run-Time Option
Settings” 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.

The IN KVRANGE keyword can be added to simplfy defining monitored elements within a desired voltage
range. The first r1 is the lower bound of the voltage range, and the second r2 is the upper bound of the
voltage range. The KVRANGE is ignored if it is defined after the FROM KV r1 or TO KV r1 keywords. With
KVRANGE keyword, all terminal buses of selected branches are within the desired voltage range

To demonstrate the use of KVRANGE specifications, assume that subsystem COMPANY1 was defined as:

SUBSYSTEM COMPANY1
JOIN
AREAS 25 35
KVRANGE 200 999
END
END

The example below shows how to add all ties from COMPANY1, including step-up transformers within COM-
PANY2 and all ties from COMPANY1 to other neighbors:

MONITOR TIES FROM SYSTEM COMPANY1

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
277
SUB/MON/CON File Descriptions Subsystem Tie Monitoring Records

To avoid adding step-up transformers, a user should use:

MONITOR TIES FROM SYSTEM COMPANY1 TO KVRANGE 200 300

This specification excludes from the selection all 345-kV ties from COMPANY1.

A KVRANGE specification eliminates the need to create intermediate subsystems if a user wants to define
ties from some area(s)/zone(s) within some kV level as shown below:

MONITOR TIES FROM AREAS 40 45 IN KVRANGE 200 240

An INTERFACE is defined using the following block structure:

[MONITOR] INTERFACE label[|RATING r [MW] |]

[|RATINGS r1 r2 ...r12 [MW]|]
(branch specification record; see below)
.
.
(branch specification record; see below)
END

where the branch specification records may specify sets of tie lines:

[MONITOR] |TIES| FROM |AREA i | [TO |AREA i |] [IN KVRANGE r1 r2]

|TIE | |AREAS i j | |AREAS i j |
|ZONE i | |ZONE i |
|ZONES i j | |ZONES i j |
|OWNER i | |OWNER i |
|OWNERS i j | |OWNERS i j |
|KV r1 | |KV r2 |
|KVRANGE r1 r2 | |KVRANGE r1 r2 |
|SYSTEM label| |SYSTEM label|
|SUBSYSTEM label| |SUBSYSTEM label|

individual branches:

[MONITOR] |BRANCH| FROM BUS bsid TO BUS bsid [|CIRCUIT | ckid]

|LINE | |CKT |

individual three-winding transformer windings:

[MONITOR] |BRANCH| FROM BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]
|LINE | |CKT |

or, simply:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
278
SUB/MON/CON File Descriptions Subsystem Tie Monitoring Records

bsid bsid [ckid]

The 32-character interface labels are used to identify interfaces in the output reports of those activities that
use the Distribution Factor data file. As with ac branches, provision is made for up to twelve interface ratings.
Interface ratings that are entered as zero, or omitted, are handled in the same way as branch ratings of zero
in activities DCCC, TLTG, SPIL, POLY,IMPC, and ACCC.

If the optional specification of ratings is omitted, the sum of the appropriate rating set values of each of
the interface members is taken as the interface rating. An interface rating is usually specified as something
other than a thermal limit; for example, contractual or stability considerations may determine the interface
rating to be used.

The SKIP block structure is used to specify individual branches that are to be excluded from the monitored
element list generated as a result of subsequent specification records that are used to define a group of
branches.

SKIP
(branch specification record; see below)
(branch specification record; see below)
END

Non-transformer branches and two-winding transformers are specified on branch specification records using
the following record format:

bsid TO bsid [|CIRCUIT| ckid]

|CKT |

Three-winding transformers are specified on branch specification records using the following record format:

bsid TO bsid TO bsid [|CIRCUIT| ckid]

|CKT |

The default circuit identifier is '1' if this specification is omitted.

“SKIP blocks” can also be used to omit individual branches from the monitored element list generated by
subsequent automatic specification commands, as shown in the following example.

SKIP
3008 TO 154
100 TO 200 TO 300
END
MONITOR BRANCHES IN AREA 5

The SKIP block must be “above” the automatic specification records.

Branches specified in a SKIP block structure apply only to MONITOR ALL, MONITOR LINES and MONITOR TIES
records which define a group of branches and are below it in the Monitored Element data file. Multiple SKIP
block structures are allowed, and each SKIP block structure appends to the list of branches to be omitted
from monitoring as a result of subsequent group specification records.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
279
SUB/MON/CON File Descriptions Subsystem Switching Device Monitor-
ing Records

10.3.4. Subsystem Switching Device Monitoring Records

All switching devices within a specified subsystem may be monitored by entering the data record:

[MONITOR] |BREAKERS| IN |AREA i | [IN KVRANGE r1 r2]

|SWITCHES| |AREAS i j |
|SWDS | |ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r |
|KVRANGE r1 r2 |
|SYSTEM label|
|SUBSYSTEM label|
|SUB staid|
|SUBSTATION staid|

When using the SYSTEM or SUBSYSTEM keywords, the label must correspond to a subsystem label specified
in a previously accessed Subsystem Definition data file (refer to Section 10.2, “Subsystem Definition Data
File”).

When the keyword SWDS is used, all the system and substation switching devices will be included. Using
the keyword BREAKERS will limit the selected switching devices to those designated as breakers. Using the
keyword SWITCHES will limit the selected switching devices to those designated as switches.

10.3.5. Voltage Monitoring Records

Buses that are to be monitored for voltage violations by the AC Contingency Solution (refer to Section 6.12.1,
“AC Contingency Solution Options”) 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 | [|KV r |] rlow [rhigh]

|ALL NODES | |KVRANGE r1 r2|
|AREA i |
|AREAS i j |
|ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r |
|KVRANGE r1 r2 |
|BUS bsid |
|BUSES bsid1 bsid2 |
|SYSTEM label |
|SUBSYSTEM label |
|SUB staid NODE ndid|
|SUBSTATION staid NODE ndid|

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
280
SUB/MON/CON File Descriptions Voltage Monitoring Records

This example monitors all 500kV bus voltages in areas 1 through 5 within 0.98 to 1.10 per unit, all lower
voltage buses within 0.95 to 1.05 per unit and monitors bus number 1234 within 0.93 to 1.05 per unit.

Example:

monitor voltage range areas 1 5 .95 1.05

monitor voltage range areas 1 5 kvrange 500 9999 .98 1.10
monitor voltage range bus 1234 .93 1.05

[MONITOR] VOLTAGE RANGE NODES IN |AREA i | [|KV r |] rlow [rhigh]

|AREAS i j | |KVRANGE r1 r2|
|ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r |
|KVRANGE r1 r2 |
|BUS bsid |
|BUSES bsid1 bsid2|
|SYSTEM label |
|SUBSYSTEM label |
|SUB staid |
|SUBSTATION staid |

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 records define a set of buses to be monitored for voltage limit violations.

[MONITOR] VOLTAGE LIMIT |ALL BUSES |

|ALL NODES |
|AREA i |
|AREAS i j |
|ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r |
|KVRANGE r1 r2 |
|BUS bsid |
|BUSES bsid1 bsid2 |
|SYSTEM label |
|SUBSYSTEM label |
|SUB staid NODE ndid|
|SUBSTATION staid NODE ndid|

[MONITOR] VOLTAGE LIMIT NODES IN |AREA i |

|AREAS i j |

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
281
SUB/MON/CON File Descriptions Voltage Monitoring Records

|ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r |
|KVRANGE r1 r2 |
|BUS bsid |
|BUSES bsid1 bsid2|
|SYSTEM label |
|SUBSYSTEM label |
|SUB staid |
|SUBSTATION staid |

When multiple voltage limit records are used in a monitored element data file, buses that have already been
included in the set will be ignored. Bus data includes normal and emergency bus voltage limits. The desig-
nation of the voltage limit to be used is made at result post-processing stage.

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 | [|KV r |] rlow [rhigh]

|ALL NODES | |KVRANGE r1 r2|
|AREA i |
|AREAS i j |
|ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r |
|KVRANGE r1 r2 |
|BUS bsid |
|BUSES bsid1 bsid2 |
|SYSTEM label |
|SUBSYSTEM label |
|SUB staid NODE ndid|
|SUBSTATION staid NODE ndid|

[MONITOR] VOLTAGE DEVIATION NODES IN |AREA i | [|KV r |] rlow [rhigh]

|AREAS i j | |KVRANGE r1 r2|
|ZONE i |
|ZONES i j |
|OWNER i |
|OWNERS i j |
|KV r |
|KVRANGE r1 r2 |
|BUS bsid |
|BUSES bsid1 bsid2|
|SYSTEM label |
|SUBSYSTEM label |
|SUB staid |

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
282
SUB/MON/CON File Descriptions Contingency Definition Data File

|SUBSTATION staid |

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.

10.4. Contingency Definition Data File

Contingency cases are defined in a Contingency Definition data file. While activity OTDF allows only single
event contingencies, the remaining activities provide for contingency cases consisting of up to 32 events.

The Contingency Defintion data file provides two means by which contingency cases may be specified. In-
dividual 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 Automatic Contingency Specification). Default contingency
categories are defined with the following structure:

CATEGORY category-string
VALUE category-string
VALUE category-string
.
END

If the contingency cases below a contingency category structure do not have categories specified then they
are assigned to the contingency categories defined in the structure. Multiple category structures can be used
in a contingency description file to change default categories.

10.4.1. Contingency Case Block Structure

In this method, a contingency case is defined in a block structure as follows:

CONTINGENCY label | [r r] [CATEGORY category-string] |

| CATEGORY category-string r r |
(contingency event specification record; below)
.
.
(contingency event specification record; below)
END

The 32-character contingency label is printed in output reports to identify each contingency. The first r
value on the data record represents frequency in occurrence/year and the second r value on the data record
represents duration in hours of the contingency. They are used for probabilistic reliability assessment. The
category-string can be a single string or a quoted comma-delimited set of strings. Categories are used to
select elements of report tables. A contingency can contain up to 32 contingency event specification records

The remainder of this section describes the contingency event specification records supported.

The outaging of an in-service non-transformer branch or two-winding transformer is specified with the fol-
lowing record, where the default circuit identifier is '1' if this specification is omitted:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
283
SUB/MON/CON File Descriptions Contingency Case Block Structure

|DISCONNECT| |BRANCH| FROM BUS bsid TO BUS bsid [|CIRCUIT| ckid]

|OPEN | |LINE | |CKT |
|TRIP |

Similarly, an out-of-service non-transformer branch or two-winding transformer may be placed in-service

with a record of the form:

CLOSE |BRANCH| FROM BUS bsid TO BUS bsid [|CIRCUIT| ckid]

|LINE | |CKT |

When the multi-section line reporting option is enabled (refer to Section 3.3.3, “Program Run-Time Option
Settings” and activity OPTN), multi-section line groupings may be specified with the above records. If a mem-
ber of a multi-section line grouping is specified, switching the entire multi-section line (rather than the spec-
ified member) is treated as the contingency event.

When the multi-section line reporting option is disabled, multi-section line groupings may not be specified in
the above records; members of multi-section line groupings may be designated on OPEN and CLOSE records,
and only the specified member is switched.

The outaging of an in-service three-winding transformer is specified with the following record, where the
default circuit identifier is '1' if this specification is omitted:

|DISCONNECT| |BRANCH| FROM BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]
|OPEN | |LINE | |CKT |
|TRIP |

Similarly, all windings of an out-of-service three-winding transformer may be placed in-service with a record
of the form:

CLOSE |BRANCH| FROM BUS bsid TO BUS bsid to BUS bsid [|CIRCUIT| ckid]
|LINE | |CKT |

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:

|DISCONNECT|THREEWINDING AT BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]

|OPEN | |CKT |
|TRIP |

Similarly, one winding of a three-winding transformer may be placed in-service with a record of the form:

CLOSE THREEWINDING AT BUS bsid TO BUS bsid to BUS bsid [|CIRCUIT| ckid]
|CKT |

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.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
284
SUB/MON/CON File Descriptions Contingency Case Block Structure

An out-of-service two-terminal dc line may be placed in-service with a record of the form:

CLOSE TWOTERMDC devid AT r |MW |

|AMPS |

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.

An out-of-service VSC dc line may be placed in-service with a record of the form:

CLOSE VSCDC devid AT r MW

When keyword MW is used, the VSC dc line's power demand to be designated to r.

An in-service FACTS device or dc line may be blocked with a record of the form:

BLOCK |TWOTERMDC | devid

|MULTITERMDC|
|VSCDC |
|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 |
|OHMS|

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 ohms of two terminal dc line is changed when OHMS is employed.

The settings of an in-service VSC dc line may be specified with a record of the form:

SET VSCDC devid TO r |MW |

|KV |
|OHMS|

When keyword MW is used, the VSC dc line power demand is set to r. The scheduled VSC dc voltage is
changed to r when keyword KV is employed. The ohms of VSC dc line is changed when OHMS is employed.

The outaging of all in-service branches connected to a bus may be specified with a record of the form:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
285
SUB/MON/CON File Descriptions Contingency Case Block Structure

|DISCONNECT| BUS bsid

|OPEN |
|TRIP |

This command is converted to as many OPEN BRANCH commands as are required before it is passed to the
Distribution Factor data file.

When the multi-section line reporting option is enabled (refer to Section 3.3.3, “Program Run-Time Option
Settings” and activity OPTN), each in-service multi-section line connected to the specified bus is switched out
as a unit. If the specified bus is a dummy bus of a multi-section line, this command is converted to a single
OPEN BRANCH command that outages the corresponding multi-section line.

When the multi-section line reporting option is disabled, only the line section adjacent to the specified bus
is outaged for each multi-section line connected to the bus.

The next four record types allow the user to specify contingency events in which the load and generation
boundary conditions may be changed at a selected bus. Load and shunt are synonymous in the linearized
network model and specifying either results in identical contingency events. When changing generation, the
bus must have in-service generation connected to it and it may not be a swing bus.

The following data record is used to set the load or generation at a bus either to a designated value or to a
specified percentage of its initial value:

SET BUS bsid |GENERATION| TO r |MW | [DISPATCH]

|LOAD | |PERCENT|
|SHUNT |

The number r specified must not be a negative number when the PERCENT keyword is used.

When LOAD is set either by PERCENT or MW, the power factor of load is constant (i.e., the reactive power
is changed by the same ratio as the active power). When GENERATION or SHUNT is set either by PERCENT
or MW, only active power is changed.

When the optional keyword DISPATCH is included at the end of the SET record, the user may designate how
the change in the bus boundary condition is to be apportioned among selected network buses rather than
having it all assigned to the system swing bus(es). In this case, the SET data record must be followed by
records of the form:

BUS bsid r
.
.
BUS bsid r
END

The r values are positive participation factors that are normally expressed in percent or per unit of the total
MW change specified by the contingency event specification record.

When SET commands operate on the bus fixed shunt, an additional keyword MVAR can be used to change
reactive power component of a bus fixed shunt:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
286
SUB/MON/CON File Descriptions Contingency Case Block Structure

SET BUS bsid SHUNT TO r MVAR

The real power component of bus fixed shunts remains constant. DISPATCH keyword is not allowed to be
included in the above command.

The following data record is used to set an individual load either to a designated amount or by a specified
percentage of its initial value:

SET LOAD ldid AT BUS bsid TO r |MW |

|PERCENT|

When LOAD is set either by PERCENT or MW, the power factor of load is constant (i.e., the reactive power is
changed by the same ratio as the active power).

The following data record is used to set an individual machine's Voltage Scheduled/Active Power/Reactive
Power either to a designated amount or by a specified percentage of its initial value:

SET |MACHINE| mcid AT BUS bsid VSCHED TO r PERUNIT

|UNIT |
SET |MACHINE| mcid AT BUS bsid ACTIVE TO r |MW |
|UNIT | |PERCENT|
SET |MACHINE| mcid AT BUS bsid REACTIVE TO r |MVAR |
|UNIT | |PERCENT|
SET |MACHINE| mcid AT BUS bsid REACTIVE TO ACTIVE
|UNIT |

The following data record is used to set an individual shunt either to a designated amount or by a specified
percentage of its initial value:

SET SHUNT shid AT BUS bsid TO r |MW |

|MVAR |
|PERCENT|

The following data record is used to set an individual switched shunt's Voltage Scheduled/VMAX/VMIN/Reac-
tive Power either to a designated amount or by a specified percentage of its initial value (swid defaults to "1 "):

SET SWSHUNT [swid] AT BUS bsid |VSCHED| TO r PERUNIT

|VMAX |
|VMIN |

SET SWSHUNT [swid] AT BUS bsid |REACTIVE| TO r |MVAR |

|PERCENT|

The following data record is used to change the load/generation/shunt at a bus either by a designated amount
or by a specified percentage of its initial value:

|CHANGE| BUS bsid |GENERATION| BY r |MW | [DISPATCH]

|ALTER | |LOAD | |PERCENT|

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
287
SUB/MON/CON File Descriptions Contingency Case Block Structure

|MODIFY| |SHUNT |

When LOAD is changed either by PERCENT or MW, the power factor of load is constant (i.e., the reactive
power is changed by the same ratio as the active power). When GENERATION or SHUNT is changed either
by PERCENT or MW, only active power is changed.

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.,

Pnew = Porig + r x |Porig| / 100

When 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 datarecord.

When LOAD is changed either by PERCENT or MW, the power factor of load is constant (i.e., the reactive
power is changed by the same ratio as the active power). When GENERATION or SHUNT is changed either
by PERCENT or MW, only active power is changed.

Similarly, keyword MVAR can be used in CHANGE/INCREASE/DECREASE commands to change reactive power
component of bus fixed shunts, e.g.:

|CHANGE | BUS bsid SHUNT BY r MVAR

|ALTER |
|MODIFY |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

The following data record is used to change an individual load either by a designated amount or by a spec-
ified percentage of its initial value:

|CHANGE | LOAD ldid AT BUS bsid BY r |MW |

|ALTER | |PERCENT|
|MODIFY |
|INCREASE|

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
288
SUB/MON/CON File Descriptions Contingency Case Block Structure

|RAISE |
|DECREASE|
|REDUCE |

When LOAD is changed either by PERCENT or MW, the power factor of load is constant (i.e., the reactive
power is changed by the same ratio as the active power).

The following data record is used to change an individual machine's Voltage Schedule/Active Power/Reactive
Power either by a designated amount or by a specified percentage of its initial value:

|CHANGE | |MACHINE| mcid AT BUS bsid VSCHED BY r PERUNIT

|ALTER | |UNIT |
|MODIFY |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

|CHANGE | |MACHINE| mcid AT BUS bsid ACTIVE BY r |MW |

|ALTER | |UNIT | |PERCENT|
|MODIFY |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

|CHANGE | |MACHINE| mcid AT BUS bsid REACTIVE BY r |MVAR |

|ALTER | |UNIT | |PERCENT|
|MODIFY |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

The following data record is used to change an individual shunt's power either by a designated amount or
by a specified percentage of its initial value:

|CHANGE | SHUNT shid AT BUS bsid BY r |MW |

|ALTER | |PERCENT|
|MODIFY | |MVAR |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

The following data record is used to change an individual switched shunt's Voltage Scheduled/VMAX/VMIN/
Reactive Power either by a designated amount or by a specified percentage of its initial value (swid defaults
to "1 "):

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
289
SUB/MON/CON File Descriptions Contingency Case Block Structure

|CHANGE | SWSHUNT [swid] AT BUS bsid |VSCHED| BY r PERUNIT

|ALTER | |VMAX |
|MODIFY | |VMIN |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

|CHANGE | SWSHUNT [swid] AT BUS bsid |REACTIVE| BY r |MVAR |

|ALTER | |PERCENT|
|MODIFY |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

The following data record is used to change the two-terminal dc line either by a designated amount of power
or by a specified percentage of its initial value:

|CHANGE | TWOTERMDC devid BY r |MW |

|ALTER | |AMPS |
|MODIFY | |PERCENT|
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

When keyword MW is used, the two-terminal dc line must be in power control mode andr is the power
demand to be changed. When keyword AMPS is used, the two terminal dc line must be in current control
mode andr is the current demand to be changed. When the PERCENTkeyword is specified, the power demand
of two-terminal dc line is changed byr percent.

The following data record is used to change the VSC dc line either by a designated amount of power or by
a specified percentage of its initial value:

|CHANGE | VSCDC devid BY r |MW |

|ALTER | |PERCENT|
|MODIFY |
|INCREASE|
|RAISE |
|DECREASE|
|REDUCE |

When keyword MW is used, the VSC dc line power demand is increased byr. When the PERCENT keyword is
specified, the power demand of VSC dc line is changed by r percent.

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

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
290
SUB/MON/CON File Descriptions Contingency Case Block Structure

|PERCENT| |LOAD |
|SHUNT |

When LOAD is moved either by PERCENT or MW, the power factor of load is constant (i.e., the reactive power
is changed by the same ratio as the active power). When GENERATION or SHUNT is moved either by PERCENT
or MW, only active power is changed.

When transferring MW, the power shift, Pshift, is set to r; when the PERCENT keyword is specified, the power
shift is calculated as:

Pshift = r x Porig / 100

where Porig 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 following data record is used to transfer the active power and reactive power of load from one bus to
another:

MOVE r |MW | ACTIVE LOAD FROM BUS bsid TO BUS bsid

|PERCENT|

MOVE r |MVAR | REACTIVE LOAD FROM BUS bsid TO BUS bsid

|PERCENT|

The keyword MVAR can be used to transfer the reactive power component of bus fixed shunts with the data
record:

MOVE r MVAR SHUNT FROM BUS bsid TO BUS bsid

The following data record is used to transfer individual load from one bus to another:

MOVE LOAD ldid r |MW | FROM BUS bsid TO BUS bsid

|PERCENT|
|MVAR |
|MWPF |

When the keyword MW is used, only the active power of the individual load is moved; when the keyword
MVAR is used, only the reactive power of the individual load is moved; when the keyword PERCENT is used,
both active power and reactive power of the individual load is moved by r percent; when the keyword MWPF
is used, the active power of the individual load is moved by r MW, and the reactive power is changed by the
same ratio as the active power.

The following data record is used to transfer individual machine from one bus to another:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
291
SUB/MON/CON File Descriptions Automatic Contingency Specification

MOVE |MACHINE| mcid r |MW | FROM BUS bsid TO BUS bsid

|UNIT | |PERCENT|

The following data record is used to transfer individual shunt from one bus to another:

MOVE SHUNT shid r |MW | FROM BUS bsid TO BUS bsid

|PERCENT|
|MVAR |

The following data record is used to transfer individual switched shunt from one bus to another:

MOVE SWSHUNT swid r |MVAR | FROM BUS bsid TO BUS bsid

|PERCENT|

An in-service synchronous machine, induction machine, load or fixed bus shunt may be removed from service
using the following data record:

REMOVE |MACHINE mcid| FROM BUS bsid [DISPATCH]

|UNIT mcid|
|INDUCMACHINE imid|
|LOAD ldid|
|SHUNT shid|

Similarly, an out-of-service synchronous machine, induction machine, load or fixed bus shunt may be placed
in-service with a record of the form:

ADD |MACHINE mcid| TO BUS bsid [DISPATCH]

|UNIT mcid|
|INDUCMACHINE imid|
|LOAD ldid|
|SHUNT shid|

The presence of the optional keyword DISPATCH is handled as described above for the SET data record. The
machine status contingency events are not permitted at swing buses.

An in-service switched shunt may be removed form service with the following data record (swid defaults
to "1 "):

REMOVE SWSHUNT [swid] FROM BUS bsid

Similarly, an out-of-service switched shunt may be placed in-service with a record of the form (swid defaults
to "1 "):

ADD SWSHUNT [swid] TO BUS bsid

10.4.2. Automatic Contingency Specification

Automatic Single and Double Line Outage Contingency Specification

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
292
SUB/MON/CON File Descriptions Automatic Contingency Specification

When the keyword BRANCH, LINE, or TIE is used in automatic single and double line outage contingency
specification commands, all branches except breakers and switches are included in the contingencies. When
the keyword BREAKER is used, only breaker and switch branches are included in the contingencies.

The following data record provides for the designation of a series of single line outage contingency cases:

SINGLE |BRANCH | FROM BUS bsid

|LINE |
|BREAKER|

Each in-service branch connected to the designated bus is outaged, one at a time. Similarly, a series of double
line outage contingency cases may be specified with the data record:

DOUBLE |BRANCH | FROM BUS bsid

|LINE |
|BREAKER|

All branches within a specified subsystem may be outaged, either singly or in pairs, by entering the data
record:

|SINGLE | |BRANCH | IN |AREA i | [3WLOWVOLTAGE]

|DOUBLE | |LINE | |ZONE i |
|BUSDOUBLE| |BREAKER| |OWNER i |
|PARALLEL | |KV r |
|SYSTEM label |
|SUBSYSTEM label|

Without the token '3WLOWVOLTAGE', for a three-winding transformer to be included, all of its in-service
windings must be connected to subsystem buses. In using the token '3WLOWVOLTAGE', the three-winding
transformer is included if its in-service high and median voltage windings are connected to subsystem buses.

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 con-
tingencies only for parallel branches (i.e., for each contingency case, the two branches being outaged con-
nect the same pair of subsystem buses). Three-winding transformer contingencies 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 Definition data file (refer to Section 10.2, “Subsystem Definition Data File”).

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
293
SUB/MON/CON File Descriptions Automatic Contingency Specification

Branches that are assigned to a line owner can be outaged, either singly or in pairs by using the following
data record:

|SINGLE | |BRANCH| WITH LINE OWNER i

|DOUBLE | |LINE |
|BUSDOUBLE|
|PARALLEL |

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|

Only one machine can be outaged for each generator bus. When a generator bus has multiple in-service
machines, the machine with the biggest real power generation is chosen to be outaged.

Finally, the following data record provides for the outaging, either singly or in pairs, of all ties from a specified
subsystem or all ties between a pair of subsystems:

|SINGLE | TIE FROM |AREA i | TO |AREA i |

|DOUBLE | |ZONE i | |ZONE i |
|BUSDOUBLE| |OWNER i | |OWNER i |
|PARALLEL | |KV r | |KV r |
|SYSTEM label | |SYSTEM label |
|SUBSYSTEM label| |SUBSYTEM label|

The selection of tie branches in the case of overlapping subsystems is handled using the same criteria defined
in Monitored Element Data File for the monitoring of ties.

For these record types, when the multi-section line reporting option is enabled, the outaging of a multi-sec-
tion line grouping within the specified subset is treated as a contingency event; the entire multi-section line

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
294
SUB/MON/CON File Descriptions Node-Breaker Contingency Specifica-
tion

is outaged. When the multi-section line reporting option is disabled, individual members of multi-section
line groupings within the specified subset (rather than entire multi-section line groupings) are outaged.

The SKIP block structure is used to specify individual branches that are to be excluded from outaging in
contingencies generated as a result of subsequent SINGLE, DOUBLE, BUSDOUBLE, and PARALLEL contingency
specification records. Each SKIP block structure is specified as follows:

SKIP |LINE |
|BRANCH|
(branch specification record; below)
.
.
(branch specification record; below)
END

Non-transformer branches and two-winding transformers are specified on branch specification records using
the following record format:

bsid TO bsid [|CIRCUIT| ckid]

|CKT |

Three-winding transformers are specified on branch specification records using the following record format:

bsid TO bsid TO bsid [|CIRCUIT| ckid]

|CKT |

The default circuit identifier is ’1’ if this specification is omitted,

Branches specified in a SKIP block structure apply only to SINGLE, DOUBLE, BUSDOUBLE, and PARALLEL con-
tingency specification records which are below it in the Contingency Definition 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 specification 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.

10.4.3. Node-Breaker Contingency Specification

The following commands can be processed only when the PSS®E network case contains node breaker data,
otherwise they are ignored by the applications where they are simulated.

The following command will isolate an in-service branch, system switching device or two- winding trans-
former by breaker operations.

ISOLATE |BRANCH| FROM BUS bsid TO BUS bsid [|CIRCUIT| ckid]

|LINE | |CKT |

The processing of this and other isolate contingencies consists of:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
295
SUB/MON/CON File Descriptions Node-Breaker Contingency Specifica-
tion

• Using the full topology network model to systematically follow the circuits outward from the line to be
isolated, and identify and open breakers in order to clear the fault on the circuit. The operation may result
in one or multiple circuits (i.e. branches, transformers, etc.) being opened en route to the opening of
a breaker. Once a breaker is successfully opened, the search along that path terminates. If the process
extends along paths beyond a user specified number of bus levels outward (OPTN) and the line has not
been successfully isolated, then the process will terminate with a message.

• The breakers include those defined as both system switching devices and substation switching devices.
The operations may result in one or more breakers being opened.

• If a stuck breaker status is encountered, the process will continue without opening the breaker and a
message will be displayed. Refer to the Stuck Breaker command below.

• With the successful isolation of the line the following process are completed in order:

• The topology processor will automatically be run to update the bus branch model based the status of
switching devices.

• Once the topology processing is complete, the power flow solution will be run to solve the new contingency
state.

The following command will isolate an in-service three-winding transformer by breaker operations:

ISOLATE |BRANCH| FROM BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]
|LINE | |CKT |

The following command will isolate one winding of a three-winding transformer by breaker operations:

ISOLATE THREEWINDING AT BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]
|CKT |

Isolation of all in-service branches connected to a bus may be specified with a record of the form:

ISOLATE BUS bsid

The following commands will isolate in-service bus-connected equipment by breaker operations(swid de-
faults to "1 "):

ISOLATE |MACHINE mcid| AT BUS bsid

|UNIT mcid|
|LOAD ldid|
|SHUNT shid|
|SWSHUNT [swid]|
|INDUCMACHINE imid|

The following commands will isolate in-service dc lines or a FACTS device by breaker operations:

ISOLATE |TWOTERMDC | devid

|MULTITERMDC|

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
296
SUB/MON/CON File Descriptions Node-Breaker Contingency Specifica-
tion

|VSCDC |
|FACTS |

The following command opens an in-service switching device (SWD) in a substation:

|DISCONNECT| |SWD | |SUBSTATION| staid FROM NODE ndid TO NODE ndid [|CIRCUIT| ckid]
|OPEN | |SWITCH | |SUB | |CKT |
|TRIP | |BREAKER|

The following command closes an out-of-service switching device in a substation:

CLOSE |SWD | |SUBSTATION| staid FROM NODE ndid TO NODE ndid [|CIRCUIT| ckid]
|SWITCH | |SUB | |CKT |
|BREAKER|

The following command isolates an in-service switching device in a substation by breaker operations.

ISOLATE |SWD | |SUBSTATION| staid FROM NODE ndid TO NODE ndid

|SWITCH | |SUB |
|BREAKER|

The following command will isolate a single end of an in-service branch, system switching device or two-
winding transformer by breaker operations:

|DISCONNECT| TERMINAL FROM BUS bsid TO BUS bsid [|CIRCUIT| ckid]

|OPEN | |CKT |

The following command will isolate a single terminal of an in-service three-winding transformer by breaker
operations:

|DISCONNECT| TERMINAL FROM BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]
|OPEN | |CKT |

The following command will isolate a single node of a substation by breaker operations:

ISOLATE |SUBSTATION| staid NODE ndid

|SUB |

The following command will place a closed breaker in the status of “stuck”. It will fail to open in subsequent
isolation operations in that contingency:

STUCK BREAKER |SUBSTATION| staid FROM NODE ndid TO NODE ndid [|CIRCUIT| ckid]
|SUB | |CKT |

Automatic Contingency Specification

The following record will create contingencies for every in-service branch or transformer connected to a bus:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
297
SUB/MON/CON File Descriptions Node-Breaker Contingency Specifica-
tion

|SINGLE| |OPEN TERMINAL | FROM BUS bsid

|DOUBLE| |ISOLATE LINE |
|ISOLATE BRANCH|

The following records will create contingencies for every in-service branch or transformer in a subsystem:

|SINGLE | |ISOLATE LINE | IN |AREA i | [3WLOWVOLTAGE]

|DOUBLE | |ISOLATE BRANCH| |ZONE i |
|BUSDOUBLE| |OWNER i |
|PARALLEL | |KV r |
|SYSTEM label |
|SUBSYSTEM label|

|SINGLE| OPEN TERMINAL IN |AREA i |

|DOUBLE| |ZONE i |
|OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|

The following record will create contingencies for every in-service substation switching device (which can
be limited to switches or breakers) in a subsystem:

SINGLE |OPEN | |SWD | IN |AREA i |

|CLOSE | |SWITCH | |ZONE i |
|ISOLATE| |BREAKER| |OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|

The following record will create contingencies for every in-service bus in a subsystem:

SINGLE ISOLATE BUS IN |AREA i |

|ZONE i |
|OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|

The following record will create stuck breaker contingencies for a subsystem. For each substation in the sub-
system, for each node in that substation, all combinations of in-service branches or transformers and closed
breakers connected to that node will be found. Each combination will generate a contingency consisting of
a stuck breaker record for that breaker and an isolate record for that branch or transformer.

SINGLE STUCK BREAKER IN |AREA i |

|ZONE i |

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
298
SUB/MON/CON File Descriptions Node-Breaker Contingency Specifica-
tion

|OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|

The SKIP block structure is used to specify individual substation switching device that are to be excluded from
outaging in contingencies generated as a result of subsequent SINGLE, DOUBLE, BUSDOUBLE, and PARALLEL
contingency specification records. Each SKIP block structure is specified as follows:

SKIP SWD
(substation switching device specification record; below)
.
.
(substation switching device specification record; below)
END

Substation switching devices are specified on branch specification records using the following record format:

staid FROM ndid TO ndid [|CIRCUIT| ckid]

|CKT |

The default circuit identifier is ’1’ if this specification is omitted,

Substation switching devices (SWDs) specified in a SKIP block structure apply only to SINGLE, DOUBLE, BUS-
DOUBLE, and PARALLEL contingency specification records which are below it in the Contingency Definition
data file. Multiple SKIP block structures are allowed, and each SKIP block structure appends to the list of SWDs
to be omitted from outaging as a result of subsequent automatic contingency specification records.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
299
 Chapter 11
Advanced Linear Analysis/MUST SUB/MON/CON
File Extensions and Options

11.1. Description of Input Data

An effort has been made to harmonize the SUB, MON, and CON files between PSS®E and the Advanced Linear
Analysis/MUST module. To this end, items in these files that share the exact same syntax will only be found
in the previous chapter. This chapter will only contain the the elements that are different in their syntax.

The approach to harmonizing these files has taken three approaches:

1. Make sure that the SUB/MON/CON files for either module does not cause an issue when run in the other
module i.e. PSS®E files run in Advanced Linear Analysis/MUST and vice versa

If there are unsupported elements or syntax contained in the files when run in the opposing system
thengenerate an error message, ignorethe record, and continue execution.

2. Extend the supported syntax in both modules to close gaps

3. Extend, where practical, recognized elements to further close gaps. The caveat to this is approach is we
will not make both modules equal in their functionality. The Advanced Linear Analysis/MUST module
will support certain logical network elements that are key to its analysis. PSS®E will not support these
element where it is not key to its analysis. An example of this would be flowgates. These are key to the
Advanced Linear Analysis/MUST module calculations but play no part in PSS®E core calculations.

11.1.1. Input Data Types

Several types of input data files are required to run Advanced Linear Analysis/MUST

• A solved load flow case.

• Subsystems data file, which defines potential sources and sinks for transactions and subsystems that may
be used later for defining monitored elements and contingencies.

• Monitored element data file, which specifies monitored branches, interfaces and flowgates.

• Contingency data file, which defines user-specified contingencies.

• Optional exclude data file, which allows custom adjustments to the monitored element data file, excluding
specific pairs of monitored elements and contingencies, changing branch ratings, or interface limits.

11.1.2. Conventions and Special Data Records

In describing the input file syntax, the following notational conventions are used. Keywords and data values
must be separated by one or more blanks. As noted above, this table lists only those items are in addition to
those described in Section 1.1.1 or differ in some way.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
300
Advanced Linear Analysis/MUST SUB/ INCLUDE Record
MON/CON File Extensions and Options

label A 12- or 14-character (depending on the contents)

label identifier. If a label contains blanks or special
characters, it must be enclosed in single quotes.

This differs from the PSS®E label description.

contingency names The maximum contingency name length is 50 char-
acters

Contingency labels must be unique and can have a

maximum width of 42 characters.

This differs from PSS®E where the contingency name

field is not identified specifically but is a label field.
flowgate_id flowgate_id is an integer number in the range from
1 to 99999.
flowgate_label flowgate_label is the flowgate text descriptor with a
maximum width of 45 characters.
Contingencies The number of elementary events (excluding dis-
patch events) for a contingency is 100.

11.1.3. INCLUDE Record

The INCLUDE record allows the user to split large input files into several smaller ones, which are then
processed via the INCLUDE statement. The INCLUDE statement has the following format:

INCLUDE filename

Every INCLUDE statement should start from a new line. Included files may also contain another INCLUDE
record. The user is limited to 10 levels of nesting of INCLUDE statements.

Data files included via the INCLUDE statement can reside in different directories. The directory of the main
file (the file specified by the user for the MUST request) is considered the current directory. All paths provided
in the INCLUDE statement should be relative to this current directory or should provide an absolute path. If,
for example, c:\MUST\userdata\main contains the main subsystem file specified for the MUST requests, the
following two examples will be equivalent:

INCLUDE ..\pjmdata\pseg.sub
INCLUDE c:\must\userdata\pjmdata\pseg.sub

The INCLUDE statement simplifies data maintenance of large files especially if different parts of the data
come from different sources. The example below demonstrates how a large number of subsystem files can
be maintained by using a master subsystem file. As shown in the example below, the master subsystem file
contains several automatic subsystem specification records and INCLUDE statements for every control area
of interest.

Example:

ADD ALL AREAS FOR EXPORT SUFFIX _EXA WITH PMAX GREATER 50 MW

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
301
Advanced Linear Analysis/MUST SUB/ Subsystem Definition Data File
MON/CON File Extensions and Options

ADD ALL AREAS SCALE GENERATION SUFFIX _SCG WITH PMAX GREATER 50 MW
ADD ALL AREAS SCALE LOAD SUFFIX _LD
ADD ALL AREAS FOR IMPORT SUFFIX _IMA WITH PMAX GREATER 50 MW
/
INCLUDE aep.sub
INCLUDE ap.sub
INCLUDE cin.sub
INCLUDE cple.sub
.
.
INCLUDE southern.sub
INCLUDE tva.sub
INCLUDE vp.sub
/

The first four records result in creating up to four subsystems for every existing area in the load flow case.
Each of the included files should contain subsystem definitions specific to the corresponding control area.
The same multilevel approach can be used for maintaining large monitored element data files, including large
flowgate files and large contingency files because it distributes the data maintenance support functions.

11.2. Subsystem Definition Data File

11.2.1. General Description and Advanced Linear Analysis/MUST
Subsystem Extensions
Subsystems of the working case are defined via the subsystem data file. Currently, the notion of a subsystem
is used in two senses

1. Sources and sinks (or purchasing and selling entities) by defining the set of buses involved in the trans-
actions

2. Control areas defined as any groups of buses. Several Advanced Linear Analysis/MUST activities allow
evaluations of transaction impacts on defined subsystems. Also, defined subsystems can be used later
to specify monitored elements and contingencies.

Separating these two notions can increase flexibility of modeling and accounting for transactions.

Advanced Linear Analysis/MUST allows automatic definition of many subsystems on an area and zone basis.
A key feature of Advanced Linear Analysis/MUST is the independence of the subsystem definition and the
current load flow case data. The same subsystem definitions can be used simultaneously for different load
flow cases. For example, a single ADD ALL record defines one subsystem for each area existing in the current
load flow case, and automatically selects generator participation factors such that all generators would reach
their upper/lower limit simultaneously. This is a convenient shortcut for defining external systems and fast
screening studies.

Advanced Linear Analysis/MUST allows definition of participation factors on the fly according to current gen-
eration, generation minimum and maximum, and generator current status from the load flow. This makes
subsystem definitions less dependent on the current load flow case generation dispatch. Advanced Linear
Analysis/MUST provides automatic selection of only large generators with maximum or current generation
above a user-specified threshold. This provides, for example, a convenient approach for selecting all essential
generators on the area-wide basis for generator sensitivity analysis.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
302
Advanced Linear Analysis/MUST SUB/ Defining Buses within a Subsystem
MON/CON File Extensions and Options

Advanced Linear Analysis/MUST allows load scaling by areas, zones, or subsystems. When scaling load, Ad-
vanced Linear Analysis/MUST adjusts all selected load buses in the subsystems in proportion to the bus loads.

11.2.2. Defining Buses within a Subsystem

Advanced Linear Analysis/MUST allows many ways to define the buses of a subsystem, using the bus ids,
areas, zones, kV, owner or join blocks. It also allows several ways to show how buses participate and which
ones do participate using the PARTICIPATE command or some form of scaling (Section 3.2.6). However, in all
cases, buses making up the subsystem must be defined somehow. Just scaling is not enough.

This applies to all scaling methods (FOR EXPORT, FOR IMPORT, GENERATION and LOAD) methods. The PARTICI-
PATE command is an exception; buses defined by PARTICIPATE will also be included in the subsystem.

Bus Names can be of the format 'nnnnnnnnvvvv' (old format) or 'nnnnnnnnnnnnvvvv' (new format); where
nnnnnnnn or nnnnnnnnnnnn is the name portion and vvvv the voltage portion of the bus name. Bus names
have to be specified via a name and voltage level as shown below:

BUS '01PLEAS126.0' 140.000 /old format name with participation factor

BUS '02SAMMIS 345' 11.000 /old format name with participation factor
BUS 'ALPHABETA 345' /new format name
BUS 'GAMMAALPHAXX 169' /new format name

Below is an incorrect definition, and correct definitions for a subsystem. Generation scaling is used in the
example, but all scaling methods except for PARTICIPATE have the same requirement.

Example:

Incorrect Subsystem Definition (no buses defined)

SUBSYSTEM "MY GENERATORS"

SCALE GENERATION
BUS 11111
BUS 22222
BUS 33333
END
END

Example:

Correct Subsystem Definition (Subsystem consists of buses 11111,22222, and 33333)

SUBSYSTEM "MY GENERATORS"

BUS 11111
BUS 22222
BUS 33333
SCALE ALL GENERATION
END

Example:

Correct Subsystem Definition

SUBSYSTEM "MY GENERATORS"

BUS 11111

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
303
Advanced Linear Analysis/MUST SUB/ Defining Buses within a Subsystem
MON/CON File Extensions and Options

BUS 22222
BUS 33333
SCALE GENERATION
BUS 11111
BUS 22222
BUS 33333
END
END

Example:

Correct Subsystem Definition (same as above but more wordy)

SUBSYSTEM "MY GENERATORS"

any good definition of a subsystem
SCALE GENERATION
BUS 11111
BUS 22222
BUS 33333
END
END

To specify participation buses via the PARTICIPATE command, Advanced Linear Analysis/MUST users do not
have to specify buses within the subsystem definition. If Advanced Linear Analysis/MUST finds a bus defined
within a participate record but not defined in the subsystem above, it will add such bus to the subsystem
automatically.

The portion of the working case buses to be contained in each subsystem definition is specified in the fol-
lowing block structure:

SUBSYSTEM|SYSTEM [label]
(subsystem specification data record)
.
.
(subsystem specification data record)
END

where the subsystem specification data records allowed are as described below. Subsystem/system label
width in Advanced Linear Analysis/MUST can be up to 20 characters. If no label is specified on a SUBSYSTEM
record, the label "UNNAMED N" is assigned to the subsystem, where "N" is a unique integer.

Selected buses may be designated as part of a subsystem with data records of the following form:

BUS bsid
BUSES bsid bsid

Example:

BUS 200
BUSES 300 400

BUS and BUSES records are valid only when using bus input by bus numbers. The BUSES record assigns the
designated buses, as well as all buses whose bus numbers fall between the two bus numbers specified, to
the subsystem being defined.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
304
Advanced Linear Analysis/MUST SUB/ Defining Buses within a Subsystem
MON/CON File Extensions and Options

All buses in selected areas may be assigned to a subsystem with data records in the following format:

AREA i
AREAS i j

where "i" and "j" are area numbers. The AREAS record type assigns all buses in a range of area numbers to
the subsystem being defined.

Example:

AREAS 5 7

In the example above, 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 may be assigned to a subsystem with data records of the following form:

ZONE i
ZONES i j

where "i" and "j" are zone numbers.

Buses at designated voltage levels may be assigned to a subsystem with records of the following form, where,
the KVRANGE record defines a range of voltage levels:

KV r
KVRANGE r1 r2

Example:

KVRANGE 100 500

In specifying ranges of bus numbers, areas, zones, and voltage levels, the second specified value should be
a positive number greater than the first one.

Example:

AREAS 7 3 -wrong
KVRANGE 135 -500 -wrong

All buses with selected owners may be assigned to a subsystem with data records in the following format:

Example:

OWNER i
OWNERS i j

where "i" and "j" are owner numbers. The OWNERS record type assigns all buses in a range of owner numbers
to the subsystem being defined.

Example:

OWNERS 2 4

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
305
Advanced Linear Analysis/MUST SUB/ Subsystem Adjustments Methods
MON/CON File Extensions and Options

In the example above, the data record "OWNERS 2 4" may be used to assign all buses with owners two, three,
and four to the subsystem.

In addition, a JOIN specification block structure provides for the specification of a group of buses through
the logical "anding" of two or more of the four selection criteria described above. A JOIN specification 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, KV, or
the corresponding "range of" records) described above. The optional JOIN specification label is for the user's
convenience and is not used by Advanced Linear Analysis/MUST functions.

Each JOIN specification block structure must appear within the subsystem block structure described above.
Both JOIN specification block structures and the simple record types may be included within a subsystem
block structure.

Example:

SUBSYSTEM 'MY COMPANY'

AREA 5
JOIN 'GROUP 1'
AREA 6
ZONES 8 10
END
END

The above example defines the subsystem "MY COMPANY", that consists of all buses in area 5, along with
all buses in area 6, which are in zones 8 through 10.

11.2.3. Subsystem Adjustments Methods

There are several methods for adjusting power injection in sending and receiving systems. These methods
can be categorized into several groups:

• Adjustments according to user-specified participation factors using the PARTICIPATE record.

• Adjusting generation in proportion to available generator reserves in a load flow case. This is defined as
the difference between maximum and current generation (Pmax - Pcur). Several selected generators are
adjusted in such a way that all selected generators would reach their maximum simultaneously. This type
of adjustment can be defined using the EXPORT specification.

• Adjusting generation based on the current and minimum generation in a load flow case. For this method,
generators will be adjusted so that all generators would reach their minimum at the same time (but stay on
line if Pmin is greater than zero). This type of adjustment can be defined using the IMPORT specification.
Reaching zero generation will not change the generator status to OFF.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
306
Advanced Linear Analysis/MUST SUB/ Automatic Specifications Using the
MON/CON File Extensions and Options ADD Command

• The SCALE GENERATION specification defines generator participation factors in proportion to the current
generation. Generators will be adjusted in a way that, for example, all selected generators would reach
zero generation level simultaneously.

• The SCALE LOAD specification defines bus participation factors in proportion to the current bus load rela-
tive to the total load in the system.

Participation factors used for adjustments can be either explicitly specified by a user or selected automatically
according to the adjustment methods described above.

Report Notation
PartFactSpec Participating generators and factors are user specified
PartFactSpecOff Participating generators and factors are user specified, subsystem transfer limit
checking will consider offline generators.
PartFactDef Default PARTICIPATE type in case the PARTICIPATE record was omitted in the subsys-
tem specification and participation factors were selected in MBASE on the basis of
machine availability
ExportSpec Participating generators are user specified, but participation factors are selected au-
tomatically according to export specification
ExportSpecOff Participating generators are user specified, but participation factors are selected au-
tomatically according to export specification (off-line generators included)
ExportDef All available subsystem generators were selected to participate automatically with
export type participation factors
ExportDefOff All available subsystem generators were selected to participate automatically with
export type participation factors (off-line generators included)
ImportSpec Participating generators are user specified with import type participation factors
ImportDef All available subsystem generators were selected to participate automatically with
import type participation factors
ScaleGenSpec Participating generators are user specified with participation factors proportional to
generation in a load flow case.
ScaleGenDef All available subsystem generators were selected with participation factors propor-
tional to generation in a load flow case
ScaleLoadSpec Participation buses are user specified with adjustments proportional to load level in
a load flow case
ScaleLoadDef All load buses will be scaled in the subsystem
SingleBus Systems added by the BUS method.
SingleGen Systems added by the GENERATOR method.
SingleGenOff Systems added by the GENERATOR method (off-line generators included)

Advanced Linear Analysis/MUST transfer limit analysis calculation functions do not enforce generator limits.
A user can use the detailed subsystem report to identify the maximum shifts possible before violating gen-
eration limits.

11.2.4. Automatic Specifications Using the ADD Command

The ADD ALL command allows the addition of multiple subsystems based on the user-specified criteria using
areas and zones definitions. One record allows the addition of all subsystems with generation or load being
adjusted according to the record type. The ADD ALL command provides a convenient means for approximate

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
307
Advanced Linear Analysis/MUST SUB/ Automatic Specifications Using the
MON/CON File Extensions and Options ADD Command

definition of external systems for screening studies. For MMWG load flow cases, one ADD ALL areas command
adds 60 to 100 subsystems allowing transactions from or to any automatically created subsystem.

There are four different types of ADD ALL commands which define different ways of adjusting/scaling spec-
ified subsystems:

ADD ALL |AREAS| |FOR EXPORT | [SUFFIX label] [WITH_GROUP] [INCLUDE OFFLINE]
|ZONES| |FOR IMPORT |
|SCALE GENERATION|

and

ADD ALL |AREAS| SCALE LOAD [SUFFIX label]

|ZONES|

ADD ALL records add one subsystem for each valid area or zone existing in the current load flow case. For
adjusting generation, Advanced Linear Analysis/MUST creates subsystems for every area or zone that has
generation that can be adjusted without violating the corresponding limit. For example, an area with all
generators at maximum will not be considered as a valid EXPORT subsystem. Specifications FOR EXPORT
and FOR IMPORT result in creating subsystems with the maximum export/import capability before violating
generator limits.

For automatically specified contingencies, Advanced Linear Analysis/MUST uses area/zone to build a subsys-
tem name. An optional SUFFIX specification provides a simple solution for resolving possible name collision
problems. The specified suffix is added to subsystems area/zone names. If the SUFFIX specification is omit-
ted, the program will use the default suffixes EXA, EXZ, IMA, IMZ, SGA, SGZ, LDA, LDZ, which correspond to
EXPORT, IMPORT, SCALE GENERATION, and SCALE LOAD records by areas and zones. The user-defined suffix
can have up to six characters.

An optional WITH_GROUP specification allows the user to apply additional criteria to automatic generator se-
lection by selecting only generators with the current or maximum generation above a user-specified thresh-
old. The WITH GROUP record has the following format:

WITH |PMAX| GREATER r [MW]

|PGEN|

The extension INCLUDE OFFLINE allows the user to include off-line units in automatically defined subsys-
tems; INCLUDE OFFLINE is most useful within FOR EXPORT specifications. The INCLUDE OFFLINE specifica-
tion changes Advanced Linear Analysis/MUST logic for automatic participation factors definition. Advanced
Linear Analysis/MUST internally computes the maximum plant output for all units, including off-line units,
if FOR EXPORT was used. By default, Advanced Linear Analysis/MUST uses maximum plant output arrays,
which exclude off-line units.

The INCLUDE OFFLINE keywords belong after WITH_GROUP, if any, as shown in the ADD ALL definition above.

Example:

ADD ALL AREAS FOR EXPORT SUFFIX _EXA50 WITH PMAX GREATER 50 MW

As illustrated above, ADD ALL automatically selects all areas with available generation reserve for export
type scaling. Using this method, all generators reach their maximum level simultaneously. All export type
subsystem names have the suffix _EXA50. Only generators with available reserve and maximum generation
greater than 50 MW will be included. Areas without available export will not be added.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
308
Advanced Linear Analysis/MUST SUB/ Automatic Specifications Using the
MON/CON File Extensions and Options ADD Command

Example:

ADD ALL AREAS SCALE GENERATION SUFFIX _SCG

This command automatically selects all areas with nonzero generation for scaling in proportion to current
case generation.

Example:

ADD ALL ZONES SCALE LOAD SUFFIX _LD

This command selects all zones existing in the load flows as subsystems for scaling load in proportion to the
current bus loads.

Example:

ADD ALL AREAS FOR IMPORT SUFFIX _IMA WITH PGEN GREATER 50 MW
ADD ALL ZONES FOR EXPORT SUFFIX _50E WITH PMAX GREATER 50 MW

The above examples show how to select all areas/zones for import/export. Only generators with the cur-
rent/maximum generation above 50 MW will be selected for adjustments.

Example:

ADD AREAS 40 45 FOR EXPORT INCLUDE OFFLINE

ADD ALL ZONES FOR EXPORT SUFFIX _EXAOF INCLUDE OFFLINE

The above examples demonstrate how to include off-line generators in subsystem definitions. Participating
factors for off-line generators will be proportional to maximum generation at each generator.

Automatically selected participation factors can be reported using the detailed report for the subsystem of
interest.

ADD records allows the addition of several specified areas or zones using scaling methods similar to the ADD
ALL command based on the grammar rules shown below:

ADD |AREA i | |FOR EXPORT | [SUFFIX label][WITH_GROUP][INCLUDE OFFLINE]

|AREAS i j| |FOR IMPORT |
|ZONE i | |SCALE GENERATION|
|ZONES i j|

The SCALE LOAD record has a very similar format but does not use WITH_GROUP and INCLUDE OFFLINE
specification:

ADD |AREA i | SCALE LOAD [SUFFIX label]

|AREAS i j|
|ZONE i |
|ZONES i j|

Several restrictions are applied:

• Subsystems defined using the SCALE GENERATION record should have at least one generator bus among
selected buses with positive generation

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
309
Advanced Linear Analysis/MUST SUB/ Defining Buses Using the PARTICIPATE
MON/CON File Extensions and Options Command

• In the case of EXPORT and IMPORT records, only generators with available required reserves are accepted.
The area or zone is valid only if at least one generator has available reserve (correspondingly FOR EXPORT
or FOR IMPORT) depending on the type of ADD ALL record.

• Any area or zone with at least one bus with positive load will be accepted as a valid subsystem for load
scaling. Buses with negative load are not selected for load scaling.

• Automatically defined participation factors are calculated on the fly internally within Advanced Linear
Analysis/MUST. These factors can be reported using a detailed subsystem report, but cannot be edited by
the user.

11.2.5. Defining Buses Using the PARTICIPATE Command

These paragraphs describe the method to define participating buses via the PARTICIPATE command. The
participation block structure allows the user to specify those buses that are to participate in the generation
shift along with their participation factors, which determine how the change in subsystem generation is to
be shared among the designated buses.

The form of the participation block structure is:

PARTICIPATE [INCLUDE OFFLINE]

BUS bsid r
.
.
BUS bsid r
END

Each participation block structure must appear within the subsystem block structure described above, and
must follow the simple record types and/or JOIN specification block structures defining the subsystem. Each
bus specified must reside in the subsystem being processed. Any bus that violates this requirement or is
disconnected (i.e., its type code is four or greater) is alarmed, and ignored.

The "r" values are participation factors that are normally expressed in percent or per unit of the total subsys-
tem generation shift. The sum of the "r" values within a participate block structure must be positive.

Example:

PARTICIPATE
BUS 100 100 /* PGEN = 100 PMAX = 200
BUS 110 300 /* PGEN = 300 PMAX = 400
END

In the example above, the sum of the "r" values is 400, i.e,. total participation =400. BUS 100 participates at
25% (100/400), while BUS 110 participates at 75% (300/400).

For generation sensitivity analysis within Advanced Linear Analysis/MUST it is convenient to assign zero par-
ticipation factors for a generator that should be considered for worst dispatch scenarios, but not for study
transfers.

The optional [INCLUDE OFFLINE] specification has no impact on the defined participating factors, but will be
used for checking subsystem export capability. The maximum capability of all generators including offline
will be used for maximum generation output.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
310
Advanced Linear Analysis/MUST SUB/ Automatic Participation Factors Defini-
MON/CON File Extensions and Options tion within the SUBSYSTEM Group

11.2.6. Automatic Participation Factors Definition within the

SUBSYSTEM Group
The SCALE record specification within the SUBSYSTEM group provides an alternative to the PARTICIPATE
record method for defining participation buses. Only one PARTICIPATE or SCALE record can be defined for
each subsystem definition. The SCALE record does not require the user to specify hard-coded participation
factors, which represent the main advantage compared to the PARTICIPATE record. Participation factors are
computed automatically. SCALE records are only recognized by Advanced Linear Analysis/MUST.

The use of SCALE still requires that the user define the buses in the subsystem. Unlike PARTICIPATE, SCALE
does not do this for the user.

The SCALE record allows specification of either all generators (load buses) within a specified subsystem using
SCALE ALL specification or by specifying the user-defined list of participating buses.

The SCALE ALL specification has the following format:

SCALE ALL |FOR EXPORT [WITH_GROUP] [INCLUDE OFFLINE]|

|FOR IMPORT [WITH_GROUP] [INCLUDE OFFLINE]|
|GENERATION [WITH_GROUP] [INCLUDE OFFLINE]|
|LOAD |

Example:

SUBSYSTEM VACAR_LOAD
AREAS 40 45
SCALE ALL LOAD
END

The example above demonstrates the creation of a subsystem for scaling load within the group of areas.

Example:

SUBSYSTEM 'MY COMPANY'

AREA 5
JOIN 'GROUP 1'
AREA 6
ZONES 8 10
END
SCALE ALL FOR EXPORT INCLUDE OFFLINE
END

The above example demonstrates automatic creation of scaling factors using FOR EXPORT for subsystems
built by using the JOIN specification:

Optional EXCEPT specification for automatic scaling specifications allows the user to exclude several buses
from scaling using the following format:

SCALE ALL |FOR EXPORT [WITH_GROUP] [INCLUDE OFFLINE]| [EXCEPT]

|FOR IMPORT [WITH_GROUP] [INCLUDE OFFLINE]|
|GENERATION [WITH_GROUP] [INCLUDE OFFLINE]|
|LOAD |

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
311
Advanced Linear Analysis/MUST SUB/ Automatic Participation Factors Defini-
MON/CON File Extensions and Options tion within the SUBSYSTEM Group

bus bsid
bus bsid
...
bus bsid
END

It is quite convenient to exclude several generators that cannot participate in transfer or allow the user to
exclude non-conforming load buses from load scaling.

The following example will define the subsystem for import but exclude several plants from adjustments.

Example:

System AMEREN
Area 356
scale all for generation with pmax greater 100 MW except
Bus 12345 / excludes plant1
Bus 23456 / excludes plant2
End
End

The following example creates a subsystem for load scaling with the exclusion of several buses to simulate
non-conforming load adjustments.

Example:

System CE
Area 363
scale all load except
Bus 12345 / excluded
Bus 23456 / excluded
End
End

The SCALE command allows specification by individual buses with the following format:

SCALE |FOR EXPORT| [INCLUDE OFFLINE]

|FOR IMPORT|
|GENERATION|
|LOAD |
BUS bsid
.
.
BUS bsid
END

Assume that all three specified buses have on-line generation values of 100 MW at bus 12345, 200 MW at
bus 12346, and 100 MW at bus 12347. The SCALE GENERATION specification for these buses is shown below:

SUBSYSTEM NORTH
ZONE 1 2
SCALE GENERATION

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
312
Advanced Linear Analysis/MUST SUB/ Defining New Subsystems Based on Al-
MON/CON File Extensions and Options ready Defined Subsystems

bus 12345
bus 12346
bus 12347
END
END

Buses 12345 and 12347 have a normalized participation factor of 0.25, while bus 12346 has a participation
factor of 0.5.

The ADD ALL GENERATORS record allows users to select all generators as participation points in the user
defined subset of buses (normally control area). The format is similar to the SCALE ALL command within
subsystem definition as shown below:

SYSTEM SYS_LABEL
ADD ALL GENERATATORS [WITH_GROUP] [INCLUDE OFFLINE] [EXCEPT]
bus bsid
bus bsid
. . .
bus bsid
END
END

This option simplifies defining a subsystem for Advanced Linear Analysis/MUST sensitivity analysis when a
user would like to get the sensitivity report for all generators in a control area as shown in the example below.

Example:

SYSTEM PJM
AREA 1 99
Add all generators
END

11.2.7. Defining New Subsystems Based on Already Defined

Subsystems
Advanced Linear Analysis/MUST allows the use of previously defined subsystems for defining new subsystems
as described above.

SUBSYSTEM|SYSTEM [label]
(definition of subsystem buses)
PARTICIPATE
BUS bsid r
subsystem label r
subsystem label r
. . .
BUS bsid r
subsystem label r
END
END

There are various applications for this extension such as scaling loads in different areas/zones with different
proportions, and mixing scaled loads with scaled generation specifications as it shown in the next example.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
313
Advanced Linear Analysis/MUST SUB/ Adding Subsystems by Bus or Genera-
MON/CON File Extensions and Options tor

Example:

/ Next record will create a subsystem with the name AMRNl_GENEX

Add area 356 for export suffix GENEX
Add area 356 scale load suffix _LOAD
System AMRN_EXPORT
Participate
System AMRN_GENEX 70
System AMRN_LOAD 30
End
End

Advanced Linear Analysis/MUST allows the simultaneous use of bus and subsystem specifications within one
participate group as shown below.

Example:

System TEST
Participate
Bus 12345 40
System AMRN_LOAD 30
End
End

11.2.8. Adding Subsystems by Bus or Generator

Adding subsystems by BUS provides a convenient method for defining subsystems for every specified bus in
a user-provided list using the following format:

ADD SYSTEMS BY BUS

(subsystem specification data record)
.
.
(subsystem specification data record)
END

Subsystem names are built from bus name and number. If the current mode of bus input is input by numbers,
then subsystem names will be formed by concatenating first the bus number and then the bus name. If the
bus input mode is bus input by bus names, bus names will precede bus numbers in the automatically built
subsystem names.

Example:

ADD SYSTEMS BY BUS

BUS 12345
BUSES 12347 12350
JOIN
AREA 25
KVRANGE 300 999
END
END

The example above illustrates how a subsystem is created for every specified bus.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
314
Advanced Linear Analysis/MUST SUB/ Reporting Available Subsystems
MON/CON File Extensions and Options

Similarly, adding subsystems by GENERATOR specification provides a convenient method for defining sub-
systems for every generator bus using the following format:

ADD SYSTEMS BY GENERATOR [WITH_GROUP] [INCLUDE OFFLINE]

(subsystem specification data record)
.
.
(subsystem specification data record)
END

Example:

ADD SYSTEMS BY GENERATOR WITH PMAX GREATER 100 MW INCLUDE OFFLINE

AREAS 40 45
END

In the example above a subsystem is created for every generator with maximum generation greater than
100 MW, including off-line generators.

11.2.9. Reporting Available Subsystems

The report provides summary information for every existing subsystem including subsystem type and max-
imum import and export capability without violating generators limits.

11.2.10. Subsystem Detailed Report

The subsystem detailed report provides detailed information on a user selected subsystem including gener-
ator participation factors and generators that violate capability limits at the userspecified level of Export or
Import.

The subsystem detailed report is computed when a user selects a generator subsystem and a transfer level.

11.2.11. Saving Subsystem Adjustments in a Load Flow Case

Advanced Linear Analysis/MUST can be used to save subsystem adjustments in a load flow case. This feature
allows updating the load flow case by saving transaction dispatches in the load flow case without adjusting
individual buses.

Advanced Linear Analysis/MUST uses several rules when saving adjustments in load flow cases:

• For PARTICIPATE records, Advanced Linear Analysis/MUST attempts to save adjustments in the generation
array. If the PARTICIPATE record is used to specify load buses, for nongenerator buses or off-line generators,
Advanced Linear Analysis/MUST saves adjustments in the load arrays preserving the same power factor
(Q/P ratio).

• Generation scaling methods (SCALE GENERATION, FOR EXPORT, and FOR IMPORT methods) are accom-
plished by generation changes only. No load buses or buses with off-line generation can be assigned for
adjustments; scale generation records can select only generator buses and honor generation status.

• Load scaling will always be accomplished by scaling load with a fixed power factor (e.g., reactive load will
be adjusted too.)

When saving subsystem adjustments in the load flow case, Advanced Linear Analysis/MUST also adjusts the
change area interchange data for that load flow case.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
315
Advanced Linear Analysis/MUST SUB/ Monitored Element Data File
MON/CON File Extensions and Options

11.3. Monitored Element Data File

11.3.1. General Description and Advanced Linear Analysis/MUST
Extensions
The user designates those elements to be monitored via the monitored element data file. Advanced Linear
Analysis/MUST supports all flow type monitoring records available in PSS®E and also all voltage monitoring
records except for those involving SUBSTATION (and NODE), BREAKER, SWITCH, and SWD. This subsection
describes in full the flow monitoring records available within Advanced Linear Analysis/MUST.

Four types of monitored elements are supported by Advanced Linear Analysis/MUST:

1. Monitored branches

2. Monitored interfaces, where the flow on an interface is taken as the sum of the flows on the branches
comprising the interface. As many as 5000 interfaces can be specified within Advanced Linear Analy-
sis/MUST. The total number of branches contained in all interfaces may not exceed the total number of
branches in the load flow.

3. Monitored flowgates. Up to 5000 flowgates are allowed by Advanced Linear Analysis/MUST. The total
number of branches contained in all flowgates may not exceed the total number of branches in the
load flow.

4. Monitored bus voltages

Only in-service branches are processed; out-of-service branches, if specified, will be ignored. Branches closed
in contingencies are monitored for violations.

MUST uses two sets of ratings for every monitored branch and interface: base case and contingency. One
of the user-specified options allows the user to disable checking/reporting base case violations. By default,
MUST checks contingency violations (using the same contingency rating) for all specified contingencies. The
MUST EXCLUDE function allows the user to disable checking violations for some of defined contingencies,
and allows the user to specify different rating parameters for specified branches.

11.3.2. Monitored Branches Specifications

MUST does not support the Multisection Line Reporting option available within PSS®E. MUST does support
the outage of multi-sectionlines.

DC and Linear Analysis - Branch Limit Checking

The user specifies the percentage of ratings to be used by MUST in branch limit checking on the MUST Options
Menu. A typical specification would be to check against 100% of RATEA (Normal) in the base case and against
100% of RATEB (Long Term Emergency) post-contingency.

In the linear transfer and contingency analysis functions, MUST checks the MW loadings against the specified
ratings which are in MVA (if the user chooses not to Convert Branch Ratings To Estimated MW in MUST
Options). If the Convert Branch Ratings To Estimated MW option is chosen, MUST calculates a MW Rating
using the base case power factor to reduce the MVA rating to an estimated MW value. In all cases MUST will
use the flow at the branch metered end.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
316
Advanced Linear Analysis/MUST SUB/ Interface Specifications
MON/CON File Extensions and Options

Non-Linear AC Models - Branch Limit Checking

In the AC transfer and contingency analysis functions, the way MUST checks branch limits depends on the
branch type. For nontransformer branches, MUST checks the current loading against designated branch rat-
ings. Ratings are assumed to have been entered as:

MVArated = SQRT(3) x E base x Irated x 10-6

where:

• Ebase is the base voltage in volts of the bus to which the terminal of the branch is connected.

• Irated is the rated phase current in amps.

Any checked branch whose current loading, including line charging and line connected shunt components,
exceeds the percentage of rating, specified in MUST Options, is reported.

For transformers, MUST checks the MVA loading against designated branch ratings that are assumed to have
been entered as MVA ratings. Any checked transformer branch whose MVA loading, including line charging
and line connected shunt components, exceeds the percentage of rating, specified in MUST Options, is re-
ported.

MUST always checks both terminals of the monitored branches and reports the highest branch loading irrel-
evant of the metered end location.

11.3.3. Interface Specifications

An interface is defined using the following block structure:

[MONITOR] INTERFACE label [RATING_GROUP]

(branch specification record)
.
.
(branch specification record)
END

where RATING GROUP has one of the following formats:

|RATING r [MW] |
|RATINGS r r r [MW] |
|BIRATINGS AmaxImp AmaxExp BmaxImp BmaxExp CmaxImp CmaxExp [MW]|

RATING and RATINGS specifications assume that interface minimum flows (e.g., imports through the inter-
face) are negative and equal in absolute values to maximum flow (exports).

BIRATINGS specifications allows the user to specify bidirectional ratings (e.g., Pmin not equal to - Pmax); there
are no limitations on the sign of IMPORT and EXPORT. Using the RATING command provides that AmaxImp
= -AmaxExp.

Branch specification records allowing the user to specify sets of TIE lines are identical to the MONITOR TIES
command:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
317
Advanced Linear Analysis/MUST SUB/ Interface Specifications
MON/CON File Extensions and Options

[MONITOR] |TIES| FROM SUBSET [TO SUBSET] [IN KVRANGE r1 r2]

|TIE |

where SUBSET is one of the following:

AREA i
ZONE i
AREAS i j
ZONES i j
SYSTEM label
SUBSYSTEM label
KV r1
KVRANGE r1 r2

and individual branches:

[MONITOR] |BRANCH| FROM BUS bsid [|CIRCUIT | ckid ] TO BUS bsid

|LINE | |CKT |

or, simply:

bsid bsid [ckid]

The following provides two identical examples of defining interfaces.

MONITOR INTERFACE NORTHEAST RATINGS 1000 1100 1200 MW

MONITOR BRANCH FROM BUS 12345 TO BUS 23456 CKT 1
MONITOR BRANCH FROM BUS 12345 TO BUS 23456 CKT 2
END
MONITOR INTERFACE NORTHEAST BIRATINGS -1000 1000 -1100 1100 -1200 1200 MW
MONITOR BRANCH FROM BUS 12345 TO BUS 23456 CKT 1
MONITOR BRANCH FROM BUS 12345 TO BUS 23456 CKT 2
END
MONITOR INTERFACE "AEP_VP" BIRATINGS 0 1000 0 1100 0 1200 MW
TIES FROM AREA 5 TO AREA 45
END

To create an interface containing only 230kV lines as ties from system MAACEHV, a user should use:

MONITOR INTERFACE 'MAAC 230 TIES' RATING 12345 MW

MONITOR TIES FROM SYSTEM MAACEHV IN KVRANGE 200 240
END

A 12-character interface label is printed in the output reports of these activities to identify each interface. As
with AC branches, provision is made for three interface ratings. When the first form of the INTERFACE record
above is used (i.e., the keyword RATING and a single value are specified), the designated value is used for
each of the three interface ratings. When the second form of the INTERFACE record is used (i.e., the keyword

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
318
Advanced Linear Analysis/MUST SUB/ Flowgates Formats
MON/CON File Extensions and Options

RATINGS and three values are specified), the designated values are used as the interface's A, B, and C ratings,
respectively. Interfaces with ratings specified as zero are not checked by MUST violation analysis activities.

If the optional specification of ratings is omitted, the sum of the appropriate rating set values of each of
the interface members is taken as the interface rating. An interface rating is intended to be specified as
something different than a thermal limit; for example, contractual or stability considerations may determine
the interface rating to be used.

11.3.4. Flowgates Formats

Flowgates in MUST can be specified using the following format:

[MONITOR] FLOWGATE flowgate_id flowgate_label RATING r [MW]

{ monitored branch specification }
{ monitored branch specification }
. . .
{ monitored branch specification }
CONTINGENCY
{ contingency event }
{ contingency event }
. . .
{ contingency event }
END
[ CA LABEL [LABEL2] [LABEL3] [LABEL4] [LABEL5] ]
[ SC LABEL [LABEL2] [LABEL3] [LABEL4] [LABEL5] ]
[ TP LABEL [LABEL2] [LABEL3] [LABEL4] [LABEL5] ]
END

where:

• Contingency definition is optional. If omitted, MUST will consider the flowgate as the base case flowgate
and will use PTDF factors to update flowgate values. The contingency definition within the flowgate has
the same format as the contingency definitions within contingency files with the only exception that con-
tingency labels following the keyword contingency are ignored.

• If the flowgate limit is omitted, MUST determines the flowgate rating using the rating of the monitored
branches.

• Optional Flowgate properties (Control Area (CA), Security Coordinator (SC) and Transmission Provider (TP))
are optional and currently are used for reporting purposes only. Keywords CA, SC, and TP can be specified
in any order. CA, SC, and TP properties are used for reporting only.

There are no limitations on the number of monitored branches within one flowgate. MUST processes the
reading of monitored branches until it finds one of the following keywords: CONTINGENCY, TP, CA, SC or
END. Up to 100 elementary events can be specified within one contingency definition.

Bus IDs can be specified using either bus numbers or names. MUST allows switching between input from
bus name to bus number within input files using the BUSNUMBERS and BUSNAMES records. It appears that
bus names are more convenient for defining flowgates. The use of bus input by bus names tends to be more
stable (i.e., bus names don't change when buses are renumbered) than that of bus by numbers.

The following are several examples of flowgate definitions.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
319
Advanced Linear Analysis/MUST SUB/ Defining Rating Multiplier by Areas or
MON/CON File Extensions and Options Zones

Example 1 defines base case flowgate.

MONITOR FLOWGATE 1004 'MccTieAEC'

BRANCH FROM BUS 'MCCRED 7 345' TO BUS 'MCCREDIE 345' CKT 1
CA AECI AMRN
SC EES MAIN
TP AECI AMRN
END

Example 2 defines contingency (OTDF) flowgate with the single branch outage as the contingency. For this
type of flowgate MUST will provide various additional information describing the contingency impact on
monitored elements (LODF) and various other factors.

FLOWGATE 3133 'JOPPA-CAPE GIRARDEAU-SHAWNEE-KELSO'

BRANCH FROM BUS 'JOPPA S 161' TO BUS 'CAPE GIR 161' CKT 1
CONTINGENCY 999
OPEN BRANCH FROM BUS '7SHAWNEE 345' TO BUS 'KELSO 345' CKT 1
END
CA AMRN EEI
SC MAIN
TP AMRN EEI
END

Example 3 defines contingency (OTDF) flowgate with a multiple event contingency.

MONITOR FLOWGATE 3222 'Lock-LisleB for Lock-Li R +G'/ reliability(OTDF)

BRANCH FROM BUS 'LOCKP; B 345' TO BUS 'LISLE; B 345' CKT 1
CONTINGENCY 999
TRIP BRANCH FROM BUS 'LOCKP; R 345' TO BUS 'LISLE; R 345' CKT 1
CLOSE BRANCH FROM BUS 'MCCOO; B 345' TO BUS 'MCCOO; R 345' CKT 1
END
CA CE
SC MAIN
TP CE
END

Flowgates are reported in similar ways as branches and interfaces in all MUST reports.

11.3.5. Defining Rating Multiplier by Areas or Zones

Rating multiplier specification allows the user to redefine the base case and contingent branch rating speci-
fied via the MUST Options button. There are several applications of this format. MUST users report that when
rating B, usually used as a contingent rating, is not available for some control areas they have to use the base
case rating A with a multiplier. In some regions Transmission Reliability Margin (TRM) are modeled via rating
adjustments with a different multiplier factor for different control areas.

Rating multiplier specification has the following format:

rating multipliers '\n'

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
320
Advanced Linear Analysis/MUST SUB/ Defining Distribution Factors Cutoff by
MON/CON File Extensions and Options Control Areas and Zones

Area/Zone definition
Area/Zone definition
. . .
Area/Zone definition
end

where Area/Zone definition has one of the following formats:

|area i | BaseRateId BaseRateMult ContRateId ContRateMult

|areas i j|
|zone i |
|zones i j|

The rating multipliers adjustment may be used for either areas or zones, but not for both in the same monitor
file.

The example below shows the redefinition of the default ratings A and B as set in the MUST Options, i.e.,
base case and contingent ratings. In general, it defines a default of 100% (A) for base case and 100% (B) for
contingent ratings. Then, for area 151 it defines rating A with the 120% multiplier as the contingent rating.
Further, for areas 300-400 it reduces the base case ratings to 98% of A and the contingent ratings to 95% of B.

Example:

Rating multipliers
Areas 1 999 A 100 B 100
Area 151 A 100 A 120 / the second definition will overwrite
/ the previous definition for that area
Areas 300 400 A 98 B 95
End

11.3.6. Defining Distribution Factors Cutoff by Control Areas and Zones

The default distribution factor cutoff specified via MUST Options allows the user to skip reporting monitored
elements which are impacted by a study transfer below a user specified threshold. This single threshold
defines both the Base Case (PTDF) and Contingent Case (OTDF) distribution factor cutoffs. There are a few
examples when a user may need to apply different cutoff values for different control areas. The most common
example is in using a relatively large cutoff value for external control areas (3-5%) and a smaller value (2-3%)
for internal control areas. Also, this specification allows the user to use different distribution factor cutoff
values for the base and contingent cases constraints.

Distribution factors cutoff record has the following format:

Factors cutoff '\n'

Area/Zone definition
Area/Zone definition
. . .
Area/Zone definition
end

where Area/Zone definition has one of the following formats:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
321
Advanced Linear Analysis/MUST SUB/ Contingency Definition Data File
MON/CON File Extensions and Options

|area i | BaseCutoff ContCutOff

|areas i j|
|zone i |
|zones i j|

The example below redefines the default distribution factor cutoff of 0.05 (PTDF and OTDF) to the lower
values of 0.02 (PTDF) and 0.03 (OTDF) for the group of control areas with the area number in the range
between 300 and 400.

Example:

Factors cutoff
Areas 1 300 0.05 0.05
Areas 301 400 0.02 0.03
End

11.4. Contingency Definition Data File

Advanced Linear Analysis/MUST supports contingency records available in PSS®E except for those involving
SUBSTATION (and NODE), BREAKER, SWITCH, and SWD.

The contingency description data file provides two means by which contingency cases may be specified.
Individual contingency cases containing branches with status changes may be specified in a contingency case
block structure (described in the following subsections) or by using an automatic contingency specification
allowing the selection of a group of single- or doubleline/ generator/bus outage contingency cases within
a single data record.

MUST has a function that allows generation of new contingency files. MUST-generated contingency files
always contain only explicit individual contingency definitions without automatic specifications. This feature
allows a user to customize the contingency definition files originally created using automatic specifications.

Section 5.2.2, “Statistics on All Contingencies” and Section 5.2.6, “Details for Selected Contingencies” de-
scribes the MUST interactive facilities for examining specified contingencies and checking for dataerrors. The
MUST log file contains all errors and warnings about specified input data, mismatches between load flow
case and input files. It is strongly recommended that the user review this file after significant modification
to the load flow case.

11.4.1. Individual Contingency Specifications

Each contingency is defined by a contingency block which consists of a contingency label record, a number
of contingency event specification records, and an end record.

A contingency case block structure is of the form:

CONTINGENCY label
(contingency event specification record) [dispatch group]
.
.
(contingency event specification record) [dispatch group]
END

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
322
Advanced Linear Analysis/MUST SUB/ Automatic Contingency Specifications
MON/CON File Extensions and Options

MUST incorporates a duplicate contingency label checker. Duplicate contingency labels will be flagged as an
error and the duplicate contingency will be disabled.

Most of the elementary contingency events can be specified using DISPATCH_GROUP. Use of the DIS-
PATCH_GROUP option causes any power mismatch within the contingency event to be distributed among
the buses specified within the DISPATCH_GROUP.

The outaging of an in-service branch is specified with the following record where the default circuit identifier
is '1' if this specification is omitted:

|DISCONNECT| |BRANCH FROM BUS bsid TO BUS bsid | [|CIRCUIT| ckid]

|OPEN | |LINE FROM BUS bsid TO BUS bsid | |CKT |
|TRIP | |WND [WND_ID] FROM BUS bsid TO BUS bsid TO BUS bsid|
|OUTAGE |

Use of the record operator WND assumes that the FROM BUS bisd is bus number 1, the first TO BUS bsid
is bus number 2 and the second TO BUS bsid is bus number 3. The operator WND is followed by a number
WND_ID which can take on the values 1, 2, 3, or any two digit combinations of these values; ex 23, 13, 31, ...
indicating which buses are to be opened or closed.

Similarly, an out-of-service branch may be placed in service with a record of the form:

| CLOSE | | BRANCH FROM BUS bsid TO BUS bsid | [| CIRCUIT| ckid]

| LINE FROM BUS bsid TO BUS bsid | | CKT |
| WND [WND_ID] FROM BUS bsid TO BUS bsid TO BUS bsid|

Various record types allow the user to specify bus contingency events in which the load and generation
boundary conditions may be changed at a selected bus. When changing generation, the bus must have in-
service generation connected to it and it cannot be a swing bus.

A single bus outage record has the following format:

DISCONNECT BUS bsid [DISPATCH_GROUP]

A single DISCONNECT BUS specification results in defining several branch openings for all branches connect-
ed to a specified bus. Bus outage records provide a convenient means to specify multisection line outages
by specifying boundary bus outages. Bus outage specifications are shorter than branch outage records and
do not require testing the status of specified branches.

11.4.2. Automatic Contingency Specifications

All contingencies are labeled. Automatic contingency labels include the circuit identification code and in
the case of three-winding transformers, the transformer name. Automatic contingency labeling follows the
convention as shown below.

Single Automatic Contingency Labels – Single Branch

Automatic contingency labels referencing a single branch are labeled using an automatic branch name. The
automatic branch name includes the FROM bus number, FROM bus name, FROM bus voltage, TO bus number,
TO bus name, bus voltage and circuit identifier.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
323
Advanced Linear Analysis/MUST SUB/ Automatic Contingency Specifications
MON/CON File Extensions and Options

Example:

28354 Yolanda 315 35555 East Jibit 315 1

54941 HSL 4 138 54973 RENO 4 138 1

Single Automatic Contingency Labels – Three-Winding Transformer

The automatic branch name for a three-winding transformer consists of the three-winding star bus number,
the transformer name and circuit identifier. Automatic contingency labels referencing a three-winding trans-
former as labeled using the prefix, "3Wnd: OPEN", followed by the automatic branch name.

Example:

3Wnd: OPEN B$070 T3XXXX 3 1

Double Automatic Contingency Labels

Double automatic contingency labels are built using the automatic branch names of both contingency pairs.
Because the automatic branch name for a single branch is rather long as defined above, the automatic branch
name for the single branch (double automatic contingencies only) is shortened to be the FROM bus name,
the term "-", the TO bus name, and the circuit identifier.

The double automatic contingency label consists of the prefix, "D:", followed by the automatic branch name
for first contingency, the term "+", and the automatic branch name for second contingency.

Example:

(Double with two branches one on circuit 22, the other 33)

D:20ABCDEF-10XXXXXX22+001BBBBB-CCCCCCCC33

Example:

(Double with a single branch on circuit 44 and a three-winding transformer on circuit 22)

D:HAZEL -WALNUT 44+ B$211 TREES 1 22

Automatic IN Contingencies

All branches within a specified subsystem may be outaged, either singly or in pairs, by entering the data
record:

|SINGLE | |BRANCH| IN SUBSET [IN KVRANGE r1 r2] [DISPATCH_GROUP]

|DOUBLE | |LINE |
|BUSDOUBLE| |
|PARALLEL | |

where SUBSET is one of the following:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
324
Advanced Linear Analysis/MUST SUB/ Automatic Contingency Specifications
MON/CON File Extensions and Options

AREA i
ZONE i
AREAS i j
ZONES i j
SYSTEM label
SUBSYSTEM label
KV r1
KVRANGE r1 r2

When using the SYSTEM or SUBSYSTEM keywords, the label must correspond to a subsystem label specified
in a previously accessed subsystem description data file.

The DOUBLE, BUSDOUBLE, and PARALLEL contingency specification records all generate contingency cases
consisting of two simultaneous branch outages. The DOUBLE record generates all combinations of double
line outage contingencies for all branches whose 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 (e.g., stuck breaker events).

The PARALLEL record is more restrictive than the BUSDOUBLE record. It generates double line outage contin-
gencies only for parallel branches (i.e., for each contingency case, the two branches being outaged connect
the same pair of subsystem buses). PARALLEL may be viewed as considering single events on right-of-ways,
which affect pairs of branches on a right-of-way.

Example:

SINGLE BRANCH IN AREA 1

SINGLE BRANCH IN AREA 1 IN KVRANGE 100 9999
SINGLE BRANCH IN KVRANGE 100 9999
SINGLE BRANCH IN SYSTEM SOUTH IN KVRANGE 100 9999

The use of the SINGLE/DOUBLE/BUSDOUBLE/PARALLEL branch outages may result in the loss of load or gen-
eration, or island creation. The optional keyword DISPATCH allows a user to designate how the change in
the bus boundary condition is to be apportioned among selected network buses rather than having it all
assigned to the system swing bus(es). Without the DISPATCH specification, island mismatch causes swing
bus adjustments, which is most likely an erroneous solution. The DISPATCH_GROUP specification is only used
with single/double branch outages. The following example specifies how to adjust subsystem INERTIA in the
case of a single line outage resulting in the loss of load, generation, or island creation.

Example:

single branch in area 45 dispatch

subsystem INERTIA
end

The following data record designates a series of single/double line outage contingencies from a selected bus:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
325
Advanced Linear Analysis/MUST SUB/ Automatic Contingency Specifications
MON/CON File Extensions and Options

|SINGLE| |BRANCH| FROM BUS bsid

|DOUBLE| |LINE |

Automatic TIE Contingencies

The following data record creates a list of single/double outages encompassing all ties from a specified sub-
system or all ties between a pair of subsystems:

|SINGLE| |TIE | FROM SUBSET [TO SUBSET] [IN KVRANGE r1 r2]

|DOUBLE| |TIES|

where SUBSET is one of the following:

AREA i
ZONE i
AREAS i j
ZONES i j
SYSTEM label
SUBSYSTEM label
KV r1
KVRANGE r1 r2

The main difference between the IN, FROM, and TO specifications is that IN specifies the kV requirement for
both terminal buses for the selected branches, while FROM and TO specifications define only corresponding
FROM or TO selection. The selection of tie branches in the case of overlapping subsystems is handled using
the criteria described above for monitored ties between systems.

The KVRANGE specification selects single branch outages only if both terminal buses are within the selected
kV range. To select all transformers between two kV levels or ranges, the user should use the TIE command.
Optional DISPATCH_GROUP specifications are used only for single/double branch outages resulting in creating
an island.

The selection of tie branches in the case of overlapping subsystems is handled using the criteria described
for monitored element selection.

The following several examples show automatic contingency specifications records.

Example:

SINGLE TIE FROM AREA 1 IN KVRANGE 100 9999

SINGLE TIE FROM AREA 1 TO AREA 2 IN KVRANGE 100 9999
SINGLE TIE FROM SYSTEM SOUTH TO AREA 2 KVRANGE 100 9999
SINGLE TIE FROM ZONE 15 TO AREA 2 KVRANGE 100 9999

Automatic Generator and Bus Contingencies

The following data record creates a list of single unit/generator/bus outages in the specified subsystem:

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
326
Advanced Linear Analysis/MUST SUB/ DISPATCH Record Format
MON/CON File Extensions and Options

SINGLE |UNIT | OUTAGE IN SUBSET [DISPATCH_GROUP]

|GENERATOR|
|BUS |

where SUBSET is one of the following:

AREA i
ZONE i
AREAS i j
ZONES i j
SYSTEM label
SUBSYSTEM label
KV r1
KVRANGE r1 r2

In the case of a UNIT specification, MUST selects the single largest unit contingency at every generator bus
in the specified subset.

A GENERATOR specification creates the set contingencies for every single plant outage (all units) of all gen-
erator buses in the specified subsystem.

A BUS outage record allows the user to select as contingencies every single bus outage in the selected subset.

Example:

SINGLE UNIT OUTAGE IN AREA 45 DISPATCH

SUBSYSTEM INERTIA
END

11.4.3. DISPATCH Record Format

DISPATCH Record
When the optional keyword DISPATCH is included with the contingency event or automatic contingency spec-
ifications, a user may designate how the change in the bus boundary condition is to be apportioned among
selected network buses rather than having it all assigned to the system swing bus(es). DISPATCH records
can be used when specifying individual events and within automatic contingency specifications, involving
changes in bus boundary conditions. DISPATCH records may not be used with branch open/close specifica-
tions.

DISPATCH records have the following format:

(single event or automatic contingency specification record) DISPATCH

BUS bsid r
subsystem label r
system label r
.
.
BUS bsid r
subsystem label r

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
327
Advanced Linear Analysis/MUST SUB/ DISPATCH Record Format
MON/CON File Extensions and Options

system label r
END

The "r" values are positive participation factors that are normally expressed in percent or per unit of the
total MW change. MUST allows the user to use BUS and SYSTEM records simultaneously within one DIS-
PATCH_GROUP definition. If a user wants to specify only one subsystem within a subsystem group, then the
"r" value specification can be omitted.

Using bus dispatch records, as shown below:

REMOVE MACHINE A FROM BUS 12345 DISPATCH

BUS 12346 100
BUS 12347 100
END

If participating factors in subsystem INERTIA have been defined to simulate inertia redispatch, then the ex-
ample below will provide a simple solution to simulate inertia redispatch for every single largest generator
outage.

If only one subsystem has to be specified, then there is no need to specify "r" value.

SINGLE UNIT IN AREA 45 DISPATCH

SYSTEM INERTIA
END

BUS and SYSTEM records can be used within one DISPATCH_GROUP, as shown below:

SINGLE UNIT IN AREA 45 DISPATCH

SYSTEM INERTIA 100
BUS 12345 50
BUS 12346 50
END

In the above example, 50% of mismatch will be accomplished by adjusting subsystem INERTIA; 25% by ad-
justing generation at bus 12345; and 25% at bus 12346.

The following is an example of single bus outage event specification:

DISCONNECT BUS 123456 DISPATCH

BUS 2100 100
END

Default Dispatch

By default, for imbalanced contingencies (with the loss of load or generation) MUST will adjust the system
swing bus. Imbalanced contingencies are commonly created by using automatic contingency definition (sin-
gle branch in area, for example). In most cases system swing bus adjustment does not provide adequate
model. It is the user's responsibility to identify imbalanced contingencies and then improve contingency de-
finitions. MUST has several ways to identify imbalanced contingencies within DC contingency analysis

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
328
Advanced Linear Analysis/MUST SUB/ Multi-Section Line Outages
MON/CON File Extensions and Options

The DEFAULT DISPATCH specification described below provides a simple and convenient solution to defining
a "default dispatch" subsystem that would pick up the power mismatch introduced by contingency events. A
default dispatch subsystem can be defined using all features available for defining subsystems, for example,
proportional scaling of all generators in the LF case as the default subsystem.

Default Dispatch has the following format:

default dispatch
bsid x
subsystem x
. . .
End

For every imbalanced contingency MUST will apply the default dispatch. The default dispatch subsystem can
be redefined several times within one contingency file.

Example:

Subsystem file
subsystem inertia
areas 1 999
scale all generation with pmax greater 100 MW
end
Contingency file
default dispatch
system inertia
end

11.4.4. Multi-Section Line Outages

If the Multi-section Line option is ON, then for multi-section branches, the single branch contingency speci-
fication will outage the whole multi-section line instead of one segment at a time when using both single or
automatic contingency definitions as it is shown in the example below.

Example:

open branch from bus 123 to bus 234 ckt &1

single branch in area 1

If multi-section reporting is on, MUST will outage only multi-section lines.

11.4.5. Load Throwover

If a bus that has a connected load becomes isolated due to a contingency, the bus-load will be automatically
transferred from the FROM bus to the TO bus using the following format:

load throwover

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
329
Advanced Linear Analysis/MUST SUB/ Three-Winding Transformer Contin-
MON/CON File Extensions and Options gency

from_bus_id to_bus_id
. . .
End

where from_bus_id and to_bus_id are bus numbers.

In addition, a load throwover data file may be used as in the example below:

LOAD THROWOVER
include Ldthrowover.dat
END

The file Ldthrowover.dat contains from / to bus pairs in the format:

from_bus_id to_bus_id
. . .
0

the last entry being a bus number of zero "0".

The load throwover file is available within all MUST activities including DC and AC based contingency analysis
and transfer limit analysis.

11.4.6. Three-Winding Transformer Contingency

The syntax for three-winding transformer contingency specification is similar to that of single branch con-
tingency specification.

All windings of a three-winding transformer may be placed in/out of-service with a record of the form:

|CLOSE | BRANCH FROM BUS bsid TO BUS bsid TO BUS bsid [ | CIRCUIT | ckid ]
|OPEN | | CKT |
|TRIP |
|OUTAGE |
|DISCONNECT|

(where the default circuit identifier of '1 ' is assumed if omitted)

Each TO BUS bsid and the FROM BUS bsid must be unique and specific to the intended threewinding trans-
former.

Example:

Open branch from bus 288 to bus 2000 to bus 398

The above example will open all three windings of the in-service three-winding transformer connected to
bus 288, bus 2000 and bus 398. This single contingency will be internally registered as three single branch
events, one for each of the three winding buses of the transformer.

Three-winding transformers are modeled as three two winding transformers connected together by a com-
mon bus, known as the star bus. Star buses are indicated in MUST by the bus number B$xxx; where xxx is

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
330
Advanced Linear Analysis/MUST SUB/ EXCLUDE Data File
MON/CON File Extensions and Options

an artificial number assigned to the three-winding transformer. Report lines containing three-winding trans-
formers are highlighted in yellow.

11.5. EXCLUDE Data File

11.5.1. Why Use an Exclude Data File?
The exclude data file allows adjustment of monitored elements defined in the monitored element and con-
tingency specification files. The exclude data file can be read in at any time while running MUST activities.

A user can read in the file by using the exclude Data File button, which brings in the file selector. In command
line mode, a user can read the exclude data file by invoking function CONSTR/CHANGE.

If a user has restarted MUST with different options, data files, or a new load flow case, the user has to read
the exclude data file again to exclude elements or reactivate excluded elements.

Also, a user can exclude/include selected contingencies on the fly with a MUST session within contingency
analysis group functions. MUST can generate the new exclude data file based on the current selection of
excluded monitored elements, contingencies, and monitored/contingencies combinations.

For more detailed explanation for Exclusion see Section 7.1, “Overview Of Exclusion”

11.5.2. Exclude Input Data Formats

The BRANCH record has the following format:

|LINE | FROM BUS bsid TO BUS bsid [| CIRCUIT | CktId ]

|BRANCH| | CKT |

The INTERFACE record has the following format:

INTERFACE |NAME Label |

|NUMBER Number|

The difference between the above format of the INTERFACE record and that of the monitored element def-
inition file. The user must use one of the keywords (NAME or NUMBER) as there are two possible ways to
identify interfaces.

The CONTINGENCY record has the following format:

CONTINGENCY |NUMBER i |
|(BRANCH RECORD)|
|NAME Label |

The contingency number can be obtained from the list of contingencies and is also reported by many MUST
reports.

The RATING record has the following format:

|RATING r [MW]|

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
331
Advanced Linear Analysis/MUST SUB/ Exclude File
MON/CON File Extensions and Options

|RATINGS r r r [MW]|

The first record type assumes that all three ratings are equal.

11.5.3. Exclude File

EXCLUDE [INITIAL] VIOLATIONS

The EXCLUDE record above allows the user to exclude all initial overloads. This record provides a simple
solution when running MUST for the first time; a user can then create an explicit exclude data file at a later
date.

The following format allows excluding initial violations just in several selected areas and zones. It is quite a
common and simple solution to avoid reporting local problems in the external control areas.

EXCLUDE [INITIAL]VIOLATIONS IN |AREA i |

IN |AREAS i j|
IN |ZONE i |
IN |ZONES i j|

An exclude monitored element statement can have one of the following formats:

|EXCLUDE| |(BRANCH RECORD) | | | (1)

|INCLUDE| |(INTERFACE RECORD)| |IN BASE CASE | (2)
|IN ALL CONTINGENCIES | (3)
|IN [New Line](CONTINGENCY RECORD)| (5)

where:

• Type (1) excludes a monitored element from the base case and all contingencies

• Type (2) excludes a monitored element only from the base case

• Type (3) excludes a monitored element from all contingencies, but it is monitored in the base case

The include command in combination with exclude command allows the user to exclude a monitored ele-
ment under all contingencies and then to include checking that constraint back in for only a few contingen-
cies.

The following format should be used to exclude flowgates:

EXCLUDE flowgate fgate_ID

Example:

exclude branch from bus 70001 to bus 70003 circuit 2 in base case
exclude branch from bus 70001 to bus 70003 cktid 2 in all contingencies
exclude interface number 3 in base case
exclude interface name XYZ_1 3 in all contingencies
exclude branch from bus 70001 to bus 70003 circuit 2 in
contingency branch from bus 70001 to bus 70002 circuit 3

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
332
Advanced Linear Analysis/MUST SUB/ Summary of Advanced Linear Analy-
MON/CON File Extensions and Options sis/MUST File Extensions Not Available
in PSS®E
exclude branch from bus 10 to bus 20 in contingency number 527

The EXCLUDE BRANCH/INTERFACE in the contingency record specification can use one or two lines. In the
case of two lines, it is important that the IN keyword is the last keyword on the first line with a monitored
branch specification as shown above.

The EXCLUDE CONTINGENCY statement has the following format:

EXCLUDE (CONTINGENCY RECORD)

Example:

exclude contingency branch from bus 70001 to bus 70002 circuit 3

exclude contingency number 12

The CHANGE RATING statement has the following format:

CHANGE |(BRANCH RECORD) | (RATING RECORD)

|(INTERFACE RECORD)|

For branches, the CHANGE record changes A, B, and C ratings defined in the load flow case. For interfaces,
it changes limits specified in the monitored file.

When new ratings are specified, these ratings will be assigned to the load flow case ratings (A, B, C). These
ratings will be scaled according to the rating multiplier specified on the MUST Startup dialog.

Example:

CHANGE BRANCH FROM BUS 70001 TO BUS 70002 CIRCUIT 3 rating 120 MW
CHANGE BRANCH FROM BUS 70001 TO BUS 70002 CIRCUIT 3 ratings 100 110 120

Contingencies and branches can be excluded by circuit number.

Example:

exclude contingencies ckt 99

exclude branches circuit 99

Buses can be excluded from the monitored bus set. Buses can be excluded using the bus name or bus number.

exclude bus bsid

11.6. Summary of Advanced Linear Analysis/MUST File

Extensions Not Available in PSS®E
11.6.1. General Input Files Extensions
• INCLUDE records allow nesting while reading input files. This feature can essentially simplify the burden
of data maintenance.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
333
Advanced Linear Analysis/MUST SUB/ Subsystems Definition Extension
MON/CON File Extensions and Options

• Function EXCLUDE allows customizing specified monitored elements and contingencies

11.6.2. Subsystems Definition Extension

• Automatic subsystem definitions FOR EXPORT, FOR IMPORT, and SCALE GENERATION allow various new
types of subsystem adjustments. Automatic specifications minimize subsystem definition dependencies
on the current load flow conditions, which simplifies input data maintenance.

• SCALE LOAD for subsystem adjustments can be explicitly specified (e.g., "scale load in area …").

• Maximum number of subsystems is 5000, compared to 100 in PSS®E.

• INCLUDE OFFLINE specification provides simple solution to include off-line generators in subsystems and
enhances reporting/limit checking.

• Advanced Linear Analysis/MUST allows the automatic adding of subsystems by every bus or generator
within a user-defined subset of buses (areas, zones, bus ranges).

• Advanced Linear Analysis/MUST allows defining new subsystems by combining previously defined subsys-
tems with user defined participating factor.

11.6.3. Monitored Elements Files Extensions

• Advanced Linear Analysis/MUST allows modeling bidirectional ratings for interfaces, which provides effi-
cient modeling of bidirectional relay protection devices.

• Advanced Linear Analysis/MUST has the EMS Flows Method, which allows using flows provided by a user
(not obtained from the load flow case).

• Flowgates as an additional type of monitored parameters is not available within PSS®E.

• Advanced Linear Analysis/MUST allows to specify rating selection and multipliers on the area and zone
basis.

• Advanced Linear Analysis/MUST allows selective selection of the distribution factors cutoff on area and
zone basis.

• Optional exclude files allows to customize reporting violations. Primary objective of this function is to
reflect existing operating guides (in the very simplified form).

11.6.4. Contingency Data File Extensions

• All contingency definition formats are consistently available with all Advanced Linear Analysis/MUST ac-
tivities, allows for example, all type bus events, branch closing events within AC contingency analysis and
load throwover file support within linear transfer analysis.

• Default dispatch subsystem definition provides convenient approach to model imbalanced contingencies.
DISPATCH records can be used for automatic contingency specifications.

• Subsystems can be used to define dispatch records.

• Automatic unit/generator/bus contingency specifications.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
334
Advanced Linear Analysis/MUST SUB/ Contingency Data File Extensions
MON/CON File Extensions and Options

• Advanced Linear Analysis/MUST checks contingent violations for branches opened in the base case, but
closed in the contingencies; PSS®E does not do this.

• Advanced Linear Analysis/MUST provides better modeling of dynamic bus events in the case of interaction
between study transfer and the size of bus injections in contingencies.

• Advanced Linear Analysis/MUST allows generating a new contingency file for user-selected contingencies.
Advanced Linear Analysis/MUST always generates individual contingency definitions even if contingencies
are specified using automatic specifications.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
335
 Chapter 12
Simulation Run Assembler PSAS User’s Ready
Reference

|MWP |
|MWI |
|ALTER | |MWY | [ |MW | ]
|CHANGE| |MVARQ| LOAD [n] BUS (bus id) [L0AD(id)] TO (R) [ |MVAR|]
|MVARI|
|MVARY|

|ALTER | |MWG | |LOAD | [|MW | ]

|CHANGE| |MVARB| |SHUNT| [n] BUS (bus id) [SHUNT (id)] TO (R) [|MVAR| ]

|ALTER |
|CHANGE| BUS (bus id) CODE TO (I)

|ALTER | |R| [|CKT | ]

|CHANGE| |X| TO (R) [n] FROM [n] BUS (bus id) TO [n] BUS (bus id) [|CIRCUIT| (id)]
|B|

[|Y | |MVA | ]
APPLY FAULT [n] BUS (bus id) [n] [|ADMITTANCE| (R1) (R2) |MHO[S]| [BASEKV (R)]]

[|Z | ]
APPLY FAULT [n] BUS (bus id) [n] [|IMPEDANCE| (R1) (R2) OHM[S] [BASEKV(R)]]

|LINE | [|CKT | ]
APPLY FAULT [n] |TIE | [n] FROM [n] BUS (bsid) TO [n] BUS (bsid) [|CIRCUIT| (id)] [n]
|BRANCH|
[|Y | |MVA | ]
[|ADMITTANCE|(R1) (R2) |MHO[S]| [BASEKV (R)]]

|LINE | [|CKT | ]
APPLY FAULT [n] |TIE | [n] FROM [n] BUS (bsid) TO [n] BUS (bsid)[|CIRCUIT| (id)] [n]
|BRANCH|
[|Z | ]
[|IMPEDANCE|(R1) (R2) OHM[S] [BASEKV (R)]]

|L-G |
SCMU |L-L | FAULT [n] BUS (bsid) [n] [ZL-G (R1) (R2)] [n] [ZL-L (R3) (R4)]
|L-L-G|

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
336
Simulation Run Assembler PSAS User’s
Ready Reference

[n] [CONVERTDC] [n] [APPLYZCOREC]

|L-G |
|L-L | [|CKT | ]
SPCB |L-L-G | FAULT (R1) [n] FROM [n] BUS (bsid) TO [n] BUS (bsid)[n] [|CIRCUIT| (id)]
|3PHASE|
[n] [ZL-G (R2) (R3)] [n] [ZL-L (R4) (R5)][n] [CONVERTDC] [n] [APPLYZCOREC]

[|CKT | ]
SPCB 2PHASE OPEN [n] FROM [n] BUS (bsid) TO [n] BUS (bsid) [n] [|CIRCUIT|(id)]

[n] [CONVERTDC] [n] [APPLYZCOREC]

[|CKT | ]
SPCB 1PHASE OPEN [n] FROM [n] BUS (bsid) TO [n] BUS (bsid) [n] [|CIRCUIT|(id)]

[n] [PATH (R1) [ [n] [ZL-G (R2) (R3)] ][n] [CONVERTDC] [n] [APPLYZCOREC]

[|CKT | ]
SPCB BREAKER OPEN [n] AT [n] BUS (bsid) TO [n] BUS (bsid) [n] [|CIRCUIT|(id)]

[n] [PATH (R1) [ [n] [ZL-G (R2) (R3)]] [n] [CONVERTDC] [n] [APPLYZCOREC]

|BLOCK
|UNBLOCK| DCLINE (dc id)

CLEAR FAULT [n] [BUS (bus id)]

CLEAR BUS [FAULT] [n] [BUS (bus id)]

|LINE |
CLEAR |TIE | FAULT [n]
|BRANCH|

CONVERT [n] MW TO (R) (R) [MVAR TO (R) (R)]

|RECONNECT| |LINE | [|CKT | ]

|CLOSE | |TIE | [n] FROM [n] BUS (bus id) TO [n] BUS (bus id)[|CIRCUIT| (id)]
|RECLOSE | |BRANCH|

|DISCONNECT| |LINE | [|CKT | ]

|TRIP | |TIE | [n] FROM [n] BUS (bus id) TO [n] BUS (busid) [|CIRCUIT| (id)]
|OPEN | |BRANCH|

|RECONNECT| [|CKT ]
|CLOSE | THREEWINDING [n] FROM [n] BUS (bsid) TO [n] BUS (bsid) TO [n] BUS (bsid) [|CIRCUIT| (id)]
|RECLOSE |

|DISCONNECT| [|CKT ]
|TRIP | THREEWINDING [n] FROM [n] BUS (bsid) TO [n] BUS (bsid)TO [n] BUS (bsid) [|CIRCUIT| (id)]
|OPEN |

|DISCONNECT| [|CKT ]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
337
Simulation Run Assembler PSAS User’s
Ready Reference

|TRIP | THREEWINDING [n] AT [n] BUS (bsid) TO [n] BUS (bsid)TO [n] BUS (bsid) [|CIRCUIT| (id)]
|OPEN |

DISCONNECT BUS (bus id) [n]

|UNIT |
|GENERATOR|
DROP |MACHINE | (id) [n] BUS (bus id)
|LOAD |
|SHUNT |

|UNIT |
|GENERATOR|
RECONNECT |MACHINE | (id) [n] BUS (bus id)
|LOAD |
|SHUNT |

DROP PLANT [n] BUS (bus id)

RECONNECT PLANT [n] BUS (bus id)

[NOW ]
HOLD [n] IN (filename-1) AND (filename-2) [SIZE[S] (I1) (I2) (I3)(I4) (I5)]

|ON |
CONVERGENCE MONITOR |OFF|

|INITIALIZE| OUTPUT |(filename)| [SNAPSHOT |(filename)|]

|START | |NONE | [ |NONE |]

|INITIALIZE| EXTENDED [n] OUTPUT |(filename)| [n]

|START | |NONE |

NEXT [CHANNEL[S] (I)] [VAR[S] (I)] [ICON[S] (I)]

|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)]]

|3WNDFLOWP | [|CKT | ]
PLACE |3WNDFLOWPQ | [n] BUS (bus id) TO [n] BUS (bus id) TO [n]BUS (bus id) [|CIRCUIT| (id)]
|3WNDFLOWMVA|
|3WNDRELAY3 |
IN CHANNEL[S] [WITH IDENTIFIER[S] (ident) [AND (ident)]]

PLACE quantity [n] BUS (bus id) [MACHINE (id)] IN CHANNEL[S] [WITH IDENTIFIER[S] (ident) [AND (ident)]]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
338
Simulation Run Assembler PSAS User’s
Ready Reference

where "quantity" is one of the following mnemonics:

ANGLE PELEC QELEC ETERM ECOMP EFD PMECH VREF
SPEED XADIFD VOTHSG VUEL VOEL MACHITERM MACHAPPIMP

|PLOAD|
PLACE |QLOAD| [n] BUS (bus id) [LOAD (id)]IN CHANNEL [WITH IDENTIFIER (ident)]

|BSFREQ |
PLACE |VOLTAGE | [n] BUS (bus id) IN CHANNEL[S] [WITH IDENTIFIER[S] (ident) [AND (ident)]]
|VOLT&ANG|

PLACE quantity [n] BUSES (I1) THRU (I2) IN CHANNEL[S]

where "quantity" is one of the following mnemonics:

ANGLE PELEC QELEC ETERM ECOMP EFD PMECH VREF
SPEED XADIFD VOTHSG VUEL VOEL MACHITERM MACHAPPIMP
PLOAD QLOAD BSFREQ VOLTAGE VOLT&ANG

|VAR[S] |
PLACE |STATE[S]| (I1) [THRU (I2)] IN CHANNEL[S]

RECOVER [n] FROM (snapshot-filename) AND (saved-case-filename) [NOFACT] [NOTYSL] [NORETURN]

|TO | |CYCLE[S] |
RUN [n] |FOR| (R) |SECOND[S]| [PRINT (I)] [PLOT (I)] [CRTPLT (I)]

|POWER |
|CURRENT |
SET [n] DCLINE (dc id) |SETPOINT| TO (R)
|SCHEDULE|
|VOLTAGE |

|VAR
SET [n] |CON| (I) TO (R)

|(C)|
SET [n] ICON (I) TO |(I)|

|VAR[S]|
SET [n] |CON[S]| (I1) THRU (In) TO (R1) ... (Rn)

|(C1) ... (Cn)|

SET [n] ICON[S] (I1) THRU (In) TO |(I1) ... (In)|

[|CYCLE[S] |]
SET [n] STEP TO (R) (n) [|SECOND[S]|] [n]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
339
Simulation Run Assembler PSAS User’s NOTES:
Ready Reference

SHED LOAD [n] BUS (bus id)

|PSS |
|PASS |
|PASSTHRU|

FIN

ABORT

CHECK

WATCH |ON |
|OFF|

|USE |
|COPY| (response-file-filename) [arg1...[arg9]]
|IDEV|

EXECUTE (iplan-program-filename)

HELP [(command)]

END

12.1. NOTES:
1. [n] => Optional comments

2. | | => "or" - pick one from list

3. [ ] => optional argument

4. (I) => INTEGER value to be entered

5. (R) => REAL value to be entered

6. (C) => quoted CHARACTER value to be entered (1 or 2 characters)

7. Words in CAPITALS must be entered exactly as shown.

8. Commas and "=" can be used in lieu of spaces for clarity.

9. Default PSAS output file is PSASnnn.IDV.

10. If "CIRCUIT (ID)" is not specified, default is circuit "1". If "LOAD (id)" is not specified, default is load "1".

11. BASEKV optional with PU. BASEKV required with OHMS or MHOS unless BASEKV is stored with working
case.
®
12. BUS-ID is sensitive to the name/number input options switch of PSS E (names must be enclosed in quotes
and include the voltage field).

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
340
Simulation Run Assembler PSAS User’s PSAS Command Help
Ready Reference

13. A $ is used to continue a PSAS command on the following line.

®
14. Section 16.15.2 of the PSS E Program Operation Manual contains detailed instructions on the use of
each PSAS command.

12.2. PSAS Command Help

Entering the command "HELP" while executing PSAS will cause the list of PSAS commands to be displayed on
the user terminal. "HELP, command" will cause the format for that command to be displayed.
®
12.3. User-Entered PSS E Commands
®
To enter a series of PSS E commands into the output file, type "PSS". PSAS responds with the "PASSTHRU:"
prompt, indicting pass-thru mode. Each line entered is passed to the output file as ENTERED. To terminate
®
the PSS E pass-thru mode, type "FIN", the "PSAS:" prompt is then issued. This mode of input is accepted both
from the terminal and from input files.

12.4. PSAS Input Files

Commands may be taken from a file as well as from the terminal. If a file is to be used for input, the commands
are entered in the file exactly as they would be from the terminal. When PSAS has processed all input file
®
commands (the "END" command has been reached), PSAS exits to the PSS E dynamics activity selector. If
any errors are encountered while processing the input file, an error message is sent to the terminal and the
input line is ignored. Execution of the generated response file is not attempted if any errors are detected.

12.5. To Execute PSAS From PSSDS4

Type "PSAS" or "PSAS,CHECK" to the prompt "ACTIVITY?".

PSAS requests input and output filenames. To enter commands interactively, type a carriage return to the
input file request. PSAS prompts with "PSAS:" when ready for a new command. If the optional suffix "CHECK"
is included, PSAS does not attempt to execute the generated response file.

12.6. Sample PSAS Command File

RECOVER data FROM SNU1 AND SME2

PLACE PMECH at BUS 100 IN CHANNEL

START, OUTPUT=OUT1

RUN pre-fault conditions TO 0 SECONDS

APPLY FAULT at BUS 201 z=.05,0 OHMS

RUN with fault FOR 3 CYCLES, PLOT=1

CLEAR FAULT

TRIP LINE FROM BUS 200 TO BUS 201

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
341
Simulation Run Assembler PSAS User’s NOTES:
Ready Reference

RUN post-fault conditions TO.5 SECONDS

RECLOSE LINE FROM BUS 201 TO BUS 200

RUN TO 5 SECONDS

HOLD final conditions IN STEMP AND LTEMP

END

12.7. NOTES:
1. Optional text is shown in lower case.

2. Commas and equal signs are used only to clarify the dialog. They are not required.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
342
 Chapter 13
Engineering Basic PSEB User’s Ready Reference

ABORT

|MW |
|MWP |
|MWI |
|ALTER | |MWY | [ |MW | ]
|CHANGE| |MVAR | LOAD [n] BUS (bus id) [LOAD (id)] TO (R) [ |MVAR|]
|MVARQ|
|MVARI|
|MVARY|

|MW |
|ALTER | |MWG | [|MW |]
|CHANGE| |MVAR | SHUNT [n] BUS (bus id) [SHUNT (id)] TO (R) [|MVAR|]
|MVARB|

|ALTER |
|CHANGE| BUS (bus id) CODE TO (I)

|ALTER | |R| [|CKT | ]

|CHANGE| |X| TO (R) [n] FROM [n] BUS (bus id) TO [n] BUS (bus id)[|CIRCUIT| (id)]
|B|

|BLOCK |
|UNBLOCK| DCLINE (dc id)

CHECK

|RECONNECT| |LINE | [|CKT | ]

|CLOSE | |TIE | [n] FROM [n] BUS (bus id) TO [n] BUS (bus id)[|CIRCUIT| (id)]
|RECLOSE | |BRANCH|

|RECONNECT| [|CKT ]
|CLOSE | THREEWINDING [n] FROM [n] BUS (bsid) TO [n] BUS (bsid)TO [n] BUS (bsid) [|CIRCUIT| (id)]
|RECLOSE |

|UNIT |
DROP |GENERATOR| (id) [n] BUS (bus id)
|MACHINE |
|LOAD |
|SHUNT |

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
343
Engineering Basic PSEB User’s Ready
Reference

|UNIT |
RECONNECT |GENERATOR| (id) [n] BUS (bus id)
|MACHINE |
|LOAD |
|SHUNT |

DROP PLANT [n] BUS (bus id)

RECONNECT PLANT [n] BUS (bus id)

END

FIN

HELP [(command)]

HOLD [n] IN (saved-case-filename) [NOW]

|USE |
|COPY| (response-file-filename) [arg1...[arg9]]
|IDEV|

EXECUTE (iplan-program-filename)

|DISCONNECT| |LINE | [|CKT | ]

|TRIP | |TIE | [n] FROM [n] BUS (bus id) TO [n] BUS (busid) [|CIRCUIT| (id)]
|OPEN | |BRANCH|

|DISCONNECT| [|CKT ]
|TRIP | THREEWINDING [n] FROM [n] BUS (bsid) TO [n] BUS (bsid)TO [n] BUS (bsid) [|CIRCUIT| (id)]
|OPEN |

|DISCONNECT| [|CKT ]
|TRIP | THREEWINDING [n] AT [n] BUS (bsid) TO [n] BUS (bsid)TO [n] BUS (bsid) [|CIRCUIT| (id)]
|OPEN |

DISCONNECT BUS (bus id) [n]

|BUS |
NET GENERATION [n] |BUSES| (bus id) [(bus id)...[(bus id)]]

NET GENERATION [n] FOR BUSES (I) THRU (I)

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
344
Engineering Basic PSEB User’s Ready NOTES:
Reference

|PSS |
|PASS |
|PASSTHRU|

RECOVER [n] FROM (saved-case-filename)

|SETPOINT|
SET DCLINE (dc id) |SCHEDULE| TO (R)

SET LOADFLOW TITLE LINE |1| TO ‘(title)’

|2|

SET SOLUTION OPTION[S] TO DEFAULT

SET SOLUTION OPTION[S] TO [|DISCRETE-TAP|],[|AREA-LOCKED|],[FLAT-START],[|DC-LOCKED|],

[|DIRECT-TAP |] [|AREA-INTCHG|] [|DC-ADJUST|]
[|TAP-LOCKED |] [|TIES&LOADS |]
[|SHUNT-LOCKED|],[|PHASE-SHIFT |]
[|SHUNT-ADJUST|] [|PSHFT-LOCKED|]
[|SHN-ADJ-CONT|]

SHED LOAD [n] BUS (bus id)

|FNSL|
|FDNS| [ |AFTER (I) [ITERATION[S]]|]
SOLVE [n] USING |NSOL| [WITH VAR LIMITS [n] |IMMEDIATE[LY] |]
|SOLV| [ |IGNORED |]
|MSLV|
|INLF|

WATCH [OFF]

13.1. NOTES:
1. [n] => Optional comments

2. | | => "or" - pick one from list

3. [ ] => optional argument

4. (I) => INTEGER value to be entered

5. (R) => REAL value to be entered

6. Words in CAPITALS must be entered exactly as shown.

7. Commas and "=" can be used in lieu of spaces for clarity.

8. Default PSEB output file is PSEBnnn.IDV.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
345
Engineering Basic PSEB User’s Ready PSEB Command Help
Reference

9. If "CIRCUIT (id)" is not specified, default is circuit "1". If "LOAD (id)" is not specified, default is load "1".
®
10. BUS-ID is sensitive to the name/number input options switch of E (names must be enclosed in quotes
and include the base voltage field).

11. A $ is used to continue a PSEB command on the following line.

12. (title) => a quoted string specifying the 60 character title line.

13. Section 16.4.2 of the ®E Program Operation Manual contains detailed instructions on the use of each
PSEB command.

13.2. PSEB Command Help

Entering the command "HELP" while executing PSEB will cause the list of PSEB commands to be displayed on
the user terminal. "HELP, command" will cause the format for that command to be displayed.
®
13.3. User-Entered PSS E Commands
®
To enter a series of PSS E commands into the output file, type "PSS". PSEB responds with the "PASSTHRU:"
prompt, indicting pass-thru mode. Each line entered is passed to the output file as ENTERED. To terminate
®
the PSS E pass-thru mode, type "FIN", the "PSEB:" prompt is then issued. This mode of input is accepted both
from the terminal and from input files.

13.4. PSEB Input Files

Commands may be taken from a file as well as from the terminal. If a file is to be used for input, the commands
are entered in the file exactly as they would be from the terminal. When PSEB has processed all input file
®
commands (the "END" command has been reached), PSEB exits to the PSS E power flow activity selector. If
any errors are encountered while processing the input file, an error message is sent to the terminal and the
input line is ignored. Execution of the generated response file is not attempted if any errors are detected.

13.5. To Execute PSEB From PSSLF4

Type "PSEB" or "PSEB,CHECK" to the prompt "ACTIVITY?".

PSEB requests input and output filenames. To enter commands interactively, type a carriage return to the
input file request. PSEB prompts with "PSEB:" when ready for a new command. If the optional suffix "CHECK"
is included, PSEB does not attempt to execute the generated responses.

13.6. Sample PSEB Command File

RECOVER network FROM SAVNW.SAV

SET SOLUTION OPTIONS TO DIRECT-TAP, $

AREA-INT, SHUNT-LOCKED

TRIP BRANCH FROM BUS 153 TO BUS 154 CKT 2

SOLVE USING FDNS WITH VAR LIMITS applied $

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
346
Engineering Basic PSEB User’s Ready NOTES:
Reference

AFTER 2 ITERATIONS

HOLD network IN SAVNEW.SAV

END

13.7. NOTES:
1. Optional text is shown in lower case.

2. Commas and equal signs are used only to clarify the dialog. They are not required.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
347
 Chapter 14
Graphic Report Generator GRPG User’s Ready
Reference
ABORT

APPEND LINE [FROM x,y] TO x,y

APPEND LINE FOR x,y

APPEND VECTOR [FROM x,y] FOR length [c] ANGLE angle [c]

APPEND BOX FROM x,y TO x,y [c] [RADIUS rad]

APPEND BOX CENTERED AT x,y WITH SIDES length-x BY length-y [c] [RADIUS
rad]

APPEND CIRCLE [c] AT x,y [c] RADIUS rad

APPEND ARC [c] AT x,y [c] RADIUS rad [c] FROM angle [c] TO angle
[c]

|CLOCKWISE |
APPEND |CW | ELLIPSE FROM x,y TO x,y
|COUNTERCLOCKWISE|
|CCW |

APPEND POLYGON[S] FROM filename [c] [OFFSET x,y] [c] [SCALE scale]

CLOSE POLYGON

COMMENT string

DECLARE |REAL | &label [&label2...&label10]

|STRING|

DEFINE MACRO macroname

DRAW LINE [FROM x,y] TO x,y

DRAW LINE FOR x,y

DRAW LOGO AT x,y WITH SIZE size [c] [ANGLE angle] [c]

DRAW VECTOR [FROM x,y] FOR length [c] ANGLE angle [c]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
348
Graphic Report Generator GRPG User’s
Ready Reference

DRAW BOX FROM x,y TO x,y [c] [RADIUS rad]

DRAW BOX CENTERED AT x,y WITH SIDES length-x BY length-y [c] [RADIUS
rad]

DRAW CIRCLE [c] AT x,y [c] RADIUS rad

DRAW ARC [c] AT x,y [c] RADIUS rad [c] FROM angle [c] TO angle [c]

|CLOCKWISE |
DRAW |CW | ELLIPSE FROM x,y TO x,y
|COUNTERCLOCKWISE|
|CCW |

DRAW POLYGON[S] FROM filename [c] [OFFSET x,y] [c] [SCALE scale]

DRAW GRID FROM x,y TO x,y [c] DELTA x,y

ELSE

|&label| |&label|
ELSEIF |string| oper |string|
|real | |real |

where "oper" is "EQ", "=", "NE", "<>", "GT", ">", "GE",

">=", "LT", "<", "LE", or "<=".

END [c]

ENDIF

ENDMACRO

FLUSH ACCUMULATED POLYGON[S]

HELP [command]

|&label| |&label|
IF |string| oper |string|
|real | |real |

where "oper" is "EQ", "=", "NE", "<>", "GT", ">", "GE", ">=",
"LT", "<", "LE", or "<=".

INCLUDE filename [c] [OFFSET x,y] [c] [SCALE scale]

INCLUDE [BINARY] ONE-LINE [c] FROM filename

INVOKE MACRO macroname USING p1 [p2...p9]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
349
Graphic Report Generator GRPG User’s
Ready Reference

|LEFT |
JUSTIFY TEXT |RIGHT |
|CENTERED|

|real |
LET &label = |string|
|&label|

LET &label = |real | oper |real |

|&label| |&label|

where "oper" is "PLUS", "+", "MINUS", "-", "TIMES", "*", "OVER",

or "/".

LET &label = THE CABS OF |real | AND |real |

|&label| |&label|

LET &label2 = THE CASE TITLE

LET &label = THE NAME FOR |AREA| n

|ZONE|

LET &label2 = THE INTERCHANGE FROM AREA n TO AREA n

LET &label2 = THE INTERCHANGE FROM ZONE n TO ZONE n

LET &label2 = THE NET INTERCHANGE FROM |AREA| n

|ZONE|

|GENERATION|
LET &label2 = THE |LOAD | FOR |AREA| n
|LOSSES | |ZONE|

LET &label2 = THE GENERATION AT BUS busid

LET &label2 = THE LOAD AT BUS busid [LOADID lid]

LET &label = THE ANGLE AT BUS busid

|GENERATION|
LET &label2 = THE SYSTEM |LOAD |
|LOSSES |

LET &label = THE [EXTENDED] NAME FOR BUS busid

LET &label = THE BASE VOLTAGE FOR BUS busid

LET &label = THE VOLTAGE AT BUS busid [ IN |PU| ]

[ |KV| ]

LET &label = THE STATUS FOR |BRANCH| FROM BUS busid TO BUS busid

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
350
Graphic Report Generator GRPG User’s
Ready Reference

|LINE | [CIRCUIT
cid]

LET &label2 = THE FLOW FOR |BRANCH| FROM BUS busid TO BUS busid
|LINE | [CIRCUIT
cid]

LET &label2 = THE |INVERTER | FLOW FOR 2-TERMINAL DC LINE n

|RECTIFIER|

LET &label2 = THE |ACTUAL | |FIXED | SHUNT AT BUS busid

|NOMINAL| |SWITCHED|

LET &label2 = THE CONVERTER FLOW AT BUS busid FOR N-TERMINAL

DC LINE n

LET &label = THE MW TRANSACTION FROM AREA n TO

AREA n [IDENTIFIER id]

LET &label = THE CONTROL MODE FOR |2-TERMINAL| DC LINE n

|N-TERMINAL|

MOVE LINE TO x,y

MOVE LINE FOR x,y

MOVE VECTOR FOR length [c] ANGLE angle [c]

|SCATTER PLOT |
PLOT |STRAIGHT LINES| FROM filename
|SPLINE CURVES |

ROTATE PLOT angle [c] AROUND x,y

SET |X| COORDINATE |PAPER | LIMITS TO min AND max

|Y| |DATA |
|PLOTTING|

SET UNITS TO |INCHES |

|CENTIMETERS|

SET ANGLE TO |DEGREES|

|RADIANS|

|TYPE |
SET LINE |WIDTH| TO integer
|COLOR|

SET FONT TYPE TO |STANDARD |

|LOWERCASE|
|integer |

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
351
Graphic Report Generator GRPG User’s NOTES:
Ready Reference

SET PLOT ORIENTATION TO |PORTRAIT |

|LANDSCAPE|

SET PLOT SYMBOL TO integer

SET PRINT FORMAT TO integer,integer

SET |TEXT | [HEIGHT TO size] [c] [ANGLE TO angle] [c]

|SYMBOL|

SET SHADING PATTERN TO integer

SET SHADING OUTLINE |VISIBLE |

|INVISIBLE|

SHADE BOX FROM x,y TO x,y [c] [RADIUS rad]

SHADE BOX CENTERED AT x,y WITH SIDES length-x BY length-y [c] [RADIUS
rad]

SHADE CIRCLE [c] AT x,y [c] RADIUS rad

SHADE ARC [c] AT x,y [c] RADIUS rad [c] FROM angle [c] TO angle
[c]

|CLOCKWISE |
SHADE |CW | ELLIPSE FROM x,y TO x,y
|COUNTERCLOCKWISE|
|CCW |

SHADE POLYGON[S] FROM filename [c] [OFFSET x,y] [c] [SCALE scale]

SHADE ACCUMULATED POLYGON[S]

START NEW PLOT

WRITE item1 [item2...item10] [AT x,y]

Each "item" may be a string, a reserved symbolic name (%name%),

or an ampersand label (&label) which was previously declared
and assigned a value. Up to ten items may be output with a single
WRITE command.

14.1. NOTES:
1. [c] => Optional comments

2. | | => "or" - pick one from list

3. [ ] => optional argument

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
352
Graphic Report Generator GRPG User’s GRPG Command Help
Ready Reference

4. Lower case words are variable fields. For more information on a specific variable, refer to Section C.4.1
of the PSS®E Program Operation Manual.

5. Words in CAPITALS must be entered exactly as shown.

6. Commas and "=" can be used in lieu of spaces for clarity.

7. If "CIRCUIT cid" is not specified, default is circuit "1". If "LOADID lid" is not specified, default is load "1".

8. "busid" may be specified as either the extended bus name enclosed in single quotes or the bus number.

9. A $ is used to continue a GRPG command on the following line.

10. &label2 is used to show which statements will return 2 values.

11. If "IDENTIFIER id" is not specified for MW TRANSACTION, default is 1.

14.2. GRPG Command Help

Entering the command "HELP" while executing GRPG causes the list of GRPG commands to be displayed on
the user terminal. "HELP, command" causes the format for the specified command to be displayed.

14.3. GRPG Input Files

Commands may be taken from a file as well as from the terminal. If a file is to be used for input, the commands
are entered in the file exactly as they would be from the terminal. When GRPG has processed all input file
commands (the "END" command has been reached), the program prompts the user for a valid plotting device
on which the resulting picture will be generated. If any errors are encountered while processing the input
file, an error message is sent to the terminal and the input line is ignored. The resulting drawing, without
the erroneous commands, may be displayed.

14.4. To Execute GRPG From PSSLF4

Type "GRPG" to the prompt "ACTIVITY?".

GRPG requests input and output filenames. To enter commands interactively, type a carriage return to the
input file request. GRPG prompts with "GRPG:" when ready for a new command.

14.5. Sample GRPG Command File

DECLARE REAL &LOADP, &LOADQ, &GENP, &GENQ

DRAW LINE FROM 0,2.5 TO 0,4.5

DRAW LINE TO 1.5,4.5

DRAW LINE TO 1.5,6

DRAW LINE TO 7,6

DRAW LINE TO 7,2.5

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
353
Graphic Report Generator GRPG User’s Sample GRPG Command File
Ready Reference

DRAW LINE TO 0,2.5

SET TEXT HEIGHT TO 0.25

SET TEXT ANGLE TO 90.

JUSTIFY TEXT CENTERED

WRITE 'AREA 1' AT 2.5,4.25

SET TEXT HEIGHT TO 0.1

JUSTIFY TEXT LEFT

LET &LOADP = THE LOAD FOR AREA 1

LET &GENP = THE GENERATION FOR AREA 1

WRITE 'LOAD =',&LOADP,'MW<CR>', AT 4.25,3.25

WRITE ' ',&LOADQ,'MVAR<CR><CR>'

WRITE 'GEN =',&GENP,'MW<CR>'

WRITE ' ',&GENQ,'MVAR'

END

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
354
 Chapter 15
Locations Data File

15.1. Overview
Locations Data File (*.loc) allows the network element locations in the diagram to be specified from the same
Cartesian or GIS coordinates across repeated analyses or different working case subsystem configurations.

File data is used to position any network element drawn or Grown for which an entry exists in the file. Those
network elements in the working case that are not defined in the locations file are assigned default locations
in the diagram.

The Bus Location file does not require an entry for every component in the case. If a position record is not
found in the file when positioning a component on the diagram, default component positioning is used. If
a component is specified that does not exist in the case, that component's record will be ignored.

15.2. Record Block Format

The location data file is specified in terms of record blocks/groups. Each file could contain one or more of
these blocks. Each record block has following format.

End of record block is detected by any of the block identifer data.

• Block Identifier

• Block Locations Data Format

• (any number of) Block Locations Data

15.3. Block Identifier

The first record in the block specifies what kinds of network items are being given locations.

The file has following record blocks.

[ BUSES | BRANCHES | NODES ]

These record blocks can appear in any order in the file.

This can be left out of the first block as the default assumption is BUSES.

15.4. Block Locations Data Format

The optional second record in the block describes the format of all locations data in the block.

[ CARTESIAN [ SCALE ] | GEOPHYSICAL [ LATLON ] ]

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
355
Locations Data File Locations Data - BUSES

If this record is not specified, GEOPHYSICAL is assumed.

The locations data can be specified in two different formats.

• CARTESIAN with additional option SCALE

• GEOPHYSICAL with additional option LATLON

In the CARTESIAN format the locations are provided as X/Y coordinates on the diagram.

If CARTESIAN is specified, a SCALE can be specified to give more detail on how the CARTESIAN units translate
to physical units. By default the positions will translate into logical inches on the diagram.

In the GEOPHYSICAL format the locations are specified in GIS coordinates on the diagram.

If GEOPHYSICAL is specified, the optional keyword LATLON may be added to specify that LATITUDE will be
specified before LONGITUDE for each position record.

The GIS coordinates can be specified in the following format.

• Degrees - Degrees are specified as a set of 1 to 3 real numbers (degrees, minutes, seconds) followed by a
direction (E, W, N, S) (the direction can be omitted if all three numbers are specified). Positive values are
interpreted as E or N, negative values as W or S. The degree parts can be separated by spaces, commas,
apostrophes, or by the specific unit markers for degree, minutes, or seconds (in which case they must be
used in order).

• Decimal Degrees - decimal fractions of a degree.

For example, all the following formats represent the same value.

79°30'36W

-79 -30 -36

79.51W

-79.51,,,

15.5. Locations Data - BUSES

The format of a bus location record is as follows:

IBUS, XLOC, YLOC, ROTATION, LENGTH

where:

IBUS Bus number.

No default allowed.
XLOC Bus X location on the diagram.

No default allowed.
YLOC Bus Y location on the diagram.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
356
Locations Data File Locations Data - BRANCHES

No default allowed.
ROTATION Bus rotation in degrees.

0 degress by default.
LENGTH Length of the busbar, in inches. A point bus will be used if Length is zero.

0 inches by default.

15.6. Locations Data - BRANCHES

The format of a branch location record is as follows:

IBUS, JBUS, CKT, XLOC_IBUS, YLOC_IBUS, [XLOC_KP1, YLOC_KP1, ..., XLOC_KPn,

YLOC_KPn], XLOC_JBUS, YLOC_JBUS

Optional, n number of knee points and their locations can be specified.

where:

IBUS Branch from bus number or extended bus name enclosed in single quotes.

No default allowed.
JBUS Branch to bus number or extended bus name enclosed in single quotes.

No default allowed.
CKT Branch circuit identifier.

CKT = '1' by default

XLOC_IBUS IBUS X location on the diagram.

No default allowed.
YLOC_IBUS IBUS Y location on the diagram.

No default allowed.
XLOC_KP1 Optional, the first knee point X location on the diagram.

When specified, no default allowed.

YLOC_KP1 Optional, the first knee point Y location on the diagram.

When specified, no default allowed.

XLOC_KPn Optional, the nth knee point X location on the diagram.

When specified, no default allowed.

YLOC_KPn Optional, the nth knee point Y location on the diagram.

When specified, no default allowed.

XLOC_JBUS JBUS X location on the diagram.

No default allowed.
YLOC_JBUS YBUS Y location on the diagram.

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
357
Locations Data File Locations Data - NODES

No default allowed.

15.7. Locations Data - NODES

The format of a bus location record is as follows:

ISUB, INODE, XLOC, YLOC, ROTATION, LENGTH

The substation GIS coordinates are specified in the power flow data file. The node locations here specify
station node offsets from the station location.

where:

ISUB Substation number.

No default allowed.
INODE Node number in substation ISUB.

No default allowed.
XLOC Node X offset on the diagram.

No default allowed.
YLOC Node X offset on the diagram.

No default allowed.
ROTATION Bus rotation in degrees.

0 degress by default.
LENGTH Length of the busbar, in inches. A point bus will be used if Length is zero.

0 inches by default.

15.8. Location Data File - Example

BUSES
GEOPHYSICAL
101 73.971254W 42.533109N 90 1.20
151 73.967661W 42.528475N 90 4.00
102 73.963169W 42.533109N 90 1.20
BRANCHES
GEOPHYSICAL
101 151 T1 73.970356W 42.533026N 73.970356W 42.528558N
102 151 T2 73.962271W 42.533026N 73.962271W 42.528558N
201 211 T6 73.946999W 42.527896N 73.946999W 42.533026N
154 203 1 73.974847W 42.499340N 73.959576W 42.506625N 73.953288W 42.506625N

PSS®E 36.1.0
All material contained in this documentation is proprietary to Siemens Industry Inc., Siemens Power Technologies International
358