TSAT User Manual PDF

TSAT
Transient Security Assessment Tool
User Manual
A product of
Powertech Labs Inc.

Surrey, British Columbia
Canada
www.powertechlabs.com
www.DSATools.com
This document contains proprietary information and shall not be reproduced in whole or in part without the prior written permission of Powertech.
TSAT User Manual
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES
THIS SOFTWARE AND ITS DOCUMENTATION WERE PREPARED BY POWERTECH LABS, INC.
(PLI). NEITHER PLI, ANY COSPONSOR, NOR ANY PERSON ACTING ON BEHALF OF ANY OF
THEM:
(A) MAKES ANY WARRANTY OR REPRESENTATION WHATSOEVER, EXPRESS OR IMPLIED,

(I) WITH RESPECT TO THE USE OF ANY INFORMATION, APPARATUS, METHOD,
PROCESS, OR SIMILAR ITEM DISCLOSED IN THIS DOCUMENT, INCLUDING
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, OR (II) THAT SUCH
USE DOES NOT INFRINGE ON OR INTERFERE WITH PRIVATELY OWNED RIGHTS,
INCLUDING ANY PARTY'S INTELLECTUAL PROPERTY, OR (III) THAT THIS DOCUMENT IS
SUITABLE TO ANY PARTICULAR USER'S CIRCUMSTANCE; OR
(B) ASSUMES RESPONSIBILITY FOR ANY DAMAGES OR OTHER LIABILITY WHATSOEVER

(INCLUDING ANY CONSEQUENTIAL DAMAGES, EVEN IF PLI OR ANY PLI
REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES)
RESULTING FROM YOUR SELECTION OR USE OF THIS DOCUMENT OR ANY
INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM DISCLOSED IN THIS
DOCUMENT.
TSAT program and its documentation are confidential property of Powertech Labs Inc. This Program
is protected under the copyright laws and by application of international treaties. All Rights Reserved
under the Copyright Laws.
Except as expressly provided by the terms and conditions set forth in the License, the LICENSEE
shall not:
(a) distribute or disclose the Program, Documentation or Derivative Work thereof to others; or
(b) disclose the Proprietary Information associated with or embodied in the Program and
Documentation in any form whatsoever;
without prior written consent of Powertech Labs Inc.
The LICENSEE shall not use the program except as expressly provided by the conditions of
LICENSE TYPE in the License.
−2011
Copyright Powertech Labs Inc. 2001−
Portion of the TSAT code is copyrighted 1998 by Chris Maunder
Last modified – April 2011
Powertech Labs Inc. i

TSAT User Manual
CONTENTS
1 Introduction ............................................................................................................. 6
1.1 Main Features .................................................................................................. 6
1.2 Relationship with Other DSAToolsTM Programs ................................................ 9
1.3 Scope of This Manual ..................................................................................... 10
1.4 User Support Information ................................................................................ 10
2 Installation ............................................................................................................. 11
2.1 TSAT Distribution ........................................................................................... 11
2.2 System Requirements .................................................................................... 11
2.3 Installing TSAT ............................................................................................... 11
2.4 Installing Protection Dongles .......................................................................... 12
2.5 Customizing TSAT .......................................................................................... 16
2.6 Running the Test Cases ................................................................................. 16
3 TSAT Concepts ..................................................................................................... 18
3.1 Transient Security Assessment ...................................................................... 18
3.2 Time-domain Simulations ............................................................................... 20
3.3 Post-processing of Simulation Results............................................................ 22
3.3.1 Transient Stability Indices .................................................................................. 22
3.3.2 Damping Indices ................................................................................................. 23
3.3.3 Voltage Drop/Rise Duration Indices ................................................................... 24
3.3.4 Frequency Indices .............................................................................................. 24
3.3.5 Relay Margin Indices .......................................................................................... 25
3.3.6 Peak-To-Peak Angle Indices .............................................................................. 26
3.3.7 Closing Torque Indices ....................................................................................... 26
3.3.8 General Comment on Security Criteria .............................................................. 27
3.3.9 Critical Clearance Time (CCT) of Faults ............................................................ 27
3.3.10 Early Termination of Simulations ........................................................................ 28
3.4 Modelling Considerations ............................................................................... 28
3.5 Analysis Modes .............................................................................................. 31
3.5.1 Basecase Analysis ............................................................................................. 32
3.5.2 Transaction Analysis .......................................................................................... 32
3.5.3 Exciter step response test .................................................................................. 38
3.5.4 Governor step response test .............................................................................. 39
3.5.5 No disturbance test ............................................................................................ 41
3.6 Result Files Available From TSAT .................................................................. 41
3.7 TSAT Terminology.......................................................................................... 44
3.7.1 Scenario ............................................................................................................. 44
3.7.2 Case ................................................................................................................... 45
4 Understanding the TSAT Main Window ............................................................... 47
Powertech Labs Inc. ii

TSAT User Manual
4.1 Starting TSAT ................................................................................................. 47

4.2 Opening a TSAT Case.................................................................................... 48
4.3 Description of the TSAT Main Window ........................................................... 49
4.3.1 Main Menu and Tool Bar .................................................................................... 49
4.3.2 Scenario Table ................................................................................................... 54
4.3.3 Computation Progress/Result Summary Pages ................................................. 56
4.3.4 Status Bar ........................................................................................................... 58
5 Creating and Modifying a TSAT Case .................................................................. 59
5.1 Data Requirements......................................................................................... 59
5.2 Creating a TSAT Case.................................................................................... 60
5.2.1 Specifying Computation Parameters .................................................................. 72
5.2.1.1 Accessing Computation Parameter Dialogs ........................................................... 72
5.2.1.2 General Features.................................................................................................... 73
5.2.1.3 Parameters for Security Assessment ..................................................................... 74
5.2.1.4 Parameters for Simulation Control.......................................................................... 75
5.2.1.5 Parameters for Modelling ....................................................................................... 77
5.2.1.6 Parameters for Transaction Analysis ...................................................................... 78
5.2.1.7 Parameters for Early Termination ........................................................................... 79
5.2.1.8 Parameters for Sequence Network Formulation ..................................................... 80
5.2.1.9 Synchronization of Computation Parameters ......................................................... 81
5.2.2 Examining and Editing Powerflow Data ............................................................. 81
5.2.3 Examining and Editing Dynamic Data ................................................................ 82
5.2.4 Creating, Examining, and Editing Monitor Data ................................................. 85
5.2.5 Creating, Examining, and Editing Contingency Data ......................................... 86
5.2.6 Creating, Examining, and Editing Criteria Data .................................................. 92
5.2.7 Creating, Examining, and Editing Dynamic Representation Data ...................... 95
5.2.8 Creating, Examining, and Editing Transaction Data .......................................... 95
5.3 Modifying a TSAT Case .................................................................................. 97
5.4 Comparing Scenarios in a TSAT Case ......................................................... 100
5.5 Saving and Archiving a TSAT Case .............................................................. 100
5.6 Examining TSAT Case Details...................................................................... 101
6 Performing Basecase Analysis .......................................................................... 103
6.1 Starting Basecase Analysis .......................................................................... 103
6.2 Monitoring Basecase Analysis ...................................................................... 103
6.3 Examining Basecase Analysis Results ......................................................... 104
7 Performing Transaction Analysis ...................................................................... 108
7.1 Starting Transaction Analysis ....................................................................... 108
7.2 Monitoring Transaction Analysis ................................................................... 108
7.3 Examining Transaction Analysis Results ...................................................... 110
8 Performing Other Analyses ................................................................................ 113
8.1 Performing Exciter Step Response Test ....................................................... 113
8.1.1 Starting Exciter Step Response Test ............................................................... 113
8.1.2 Monitoring Exciter Step Response Test ........................................................... 114
Powertech Labs Inc. iii

TSAT User Manual
8.1.3 Examining Exciter Step Response Test Results .............................................. 115

8.2 Performing Governor Step Response Test ................................................... 116
8.2.1 Starting Governor Step Response Test ........................................................... 116
8.2.2 Monitoring Governor Step Response Test ....................................................... 117
8.2.3 Examining Governor Step Response Test Results .......................................... 118
8.3 Performing No Disturbance Test................................................................... 119
8.3.1 Starting No Disturbance Test ........................................................................... 119
8.3.2 Monitoring No Disturbance Test ....................................................................... 120
8.3.3 Examining No Disturbance Test Results .......................................................... 121
9 Other Features..................................................................................................... 123
9.1 Saving Results As ASCII Text Files .............................................................. 123
9.2 Program Help ............................................................................................... 124
9.3 Program Message Handling ......................................................................... 125
9.4 Using the Case Scheduler ............................................................................ 128
9.5 Distributing TSAT Computation .................................................................... 130
9.6 TSAT Snapshot ............................................................................................ 135
9.7 Configuring Text Editor ................................................................................. 139
9.8 Using the TSAT Batch Version ..................................................................... 140
9.9 Creating Plots In Batch Mode ....................................................................... 141
9.10 DSAToolsTM Contingency Converter ............................................................. 142
10 Appendix A – TSAT Case File Format................................................................ 143
10.1 Concept, Rules, and Structure ...................................................................... 143
10.2 Data Sections ............................................................................................... 145
10.2.1 Scenario Description ........................................................................................ 146
10.2.2 Scenario Parameters ........................................................................................ 146
10.2.3 Powerflow Data ................................................................................................ 150
10.2.4 Dynamic Data ................................................................................................... 152
10.2.5 Dynamic Representation Data ......................................................................... 152
10.2.6 Monitor Data ..................................................................................................... 153
10.2.7 Switching Data.................................................................................................. 154
10.2.8 Criteria Data ..................................................................................................... 155
10.2.9 Relay Data ........................................................................................................ 156
10.2.10 Transaction Data ............................................................................................ 157
10.2.11 Sequence Network Data ................................................................................. 158
11 Appendix B – Using Scripting Language To Perform Batch Plotting .............. 160
11.1 Background .................................................................................................. 160
11.1.1 Principles .......................................................................................................... 160
11.1.2 Overview of TSAT and SSAT Binary Result File Contents .............................. 161
11.2 BinReader Class........................................................................................... 162
11.3 Plotter Class ................................................................................................. 166
11.4 Examples...................................................................................................... 170
12 Appendix C – Description of Test Cases ........................................................... 176
Powertech Labs Inc. iv

TSAT User Manual
12.1 General Notes .............................................................................................. 176

12.2 Two-Area Case............................................................................................. 176
12.3 HVDC Case .................................................................................................. 179
12.4 Wind Generator Case ................................................................................... 183
12.5 SVC Case..................................................................................................... 183
12.6 TCSC Case .................................................................................................. 190
12.7 STATCOM Case........................................................................................... 197
Powertech Labs Inc. v

TSAT User Manual
1 Introduction
This manual describes the features and operation of the Transient Security Assessment Tool
(TSAT). Three additional manuals describe other details of TSAT:
• TSAT Model Manual shows the model details and data format of the dynamic device
models that TSAT supports.
• DSAToolsTM UDM Manual gives details on using the user-defined models of TSAT.
• DSAToolsTM DSAOA Manual contains instructions on how to perform analysis for the
TSAT simulation results using the DSAOA module included in TSAT package.
TSAT is a software tool developed by Powertech Labs Inc. This tool takes advantage of the state-
of-the-art in the Transient Security Assessment (TSA) development and offers powerful features
for both on- and off-line TSA applications. Its comprehensive analysis functions include,
• Detailed time-domain simulation engine that can process large and complex power
system models.
• Availability of security indices to indicate the stability status of the system, in terms of
different criteria such as transient stability, small-signal stability, voltage stability,
frequency stability, relay margin, and others.
• Determination of stability limits under specified system operation conditions.
• An output analysis module that allows the detailed analysis of simulation results.
• Capability of connecting to an EMS system to perform on-line TSA.
1.1 Main Features
Modelling
TSAT accepts powerflow data in the native format of DSAToolsTM (PSF and PFB), as well as
other commonly used format such as PTI PSS/E format, GE PSLF format, and BPA format.
Dynamic models of devices commonly represented for transient stability studies are available in
the native format of DSAToolsTM. Dynamic models in third party formats (such as PTI PSS/E,
GE PSLF, and BPA) can be read and converted. The details of these models and model
conversion are described in the TSAT Model Manual.
For non-standard and advanced controls (such as FACTS and HVDC), TSAT offers the capability
to create user-defined models (UDM). An extensive control function library is available to build
UDM. Customized control functions can also be provided by the user using the Dynamic Linked
Libraries (DLL) based on user-written code. Refer to TSAT Model Manual and DSAToolsTM
UDM Manual for details.
Powertech Labs Inc. 6

TSAT User Manual
The dynamic models specified for a system can be customized using the dynamic representation
data. This allows you to make a simplified or equivalent representation of the dynamics of a
portion of the system as required by studies. The details of dynamic representation data
specification are documented in the TSAT Model Manual.
Automatic relays, such as switchable shunt relay, under-voltage/under-frequency load shedding

relay, etc., and special protection systems can be modeled in TSAT with standard or user-defined
models. Details can be found in the TSAT Model Manual and the DSAToolsTM UDM Manual.
TSAT also supports a wide range of switching activities that can be used when specifying
contingencies. Unbalanced faults (single-line-to-ground fault circuit, single-pole switching, etc.)
can be simulated with the fault impedances computed automatically from the sequence network
data. Dependent contingencies that are executed depending on system security status can also be
specified. The details of contingency specifications are documented in the TSAT Model Manual.
When simulations are performed in the detailed analysis engine, various system quantities can be
monitored and saved for analysis. This is defined in the monitor data and described in the TSAT
Model Manual.
Simulation engines
The conventional numerical integration technique is used in TSAT as the time-domain simulation
engine. A number of advanced features are implemented in this simulation engine, including an
early termination option that can automatically stop the simulation as soon as the stability of the
system is known.
Refer to Section 3 for more descriptions on the simulation technique and the available
computational options.
Computation of security indices
One of the fundamental requirements for TSA is that a quantitative security index (also referred
to as stability index or stability margin) is derived for each contingency and for each stability
category, to indicate the degree of stability. In TSAT, seven types of security indices may be
computed:
• Transient stability: transient stability index (η) or critical clearing time (CCT) of the
fault
• Small-signal stability: damping index (σ)
• Transient voltage violation: voltage drop/rise duration indices (TVdrop and TVrise)
• Transient frequency violation: frequency drop/rise duration indices (TFdrop and TFrise) and
rate of change of frequency index (α)
• Relay margin violation: relay margin indices (M)
• Generator peak-to-peak relative angle: peak-to-peak angle index (δpp)
• Branch closing torque: closing torque index (∆PC)
Refer to Section 3.3 for their definitions and applications.
Derivation of stability limits

TSAT User Manual
Computing stability limits is an important task in power system stability studies. TSAT has a
feature to derive stability limits for specified power transactions. The stability limits can be
computed to satisfy criteria based on any or all of the security indices. Refer to Section 3.5.2 for
more on the stability limit computation and Section 7 on the use of this feature.
The power transactions for stability limit determination are specified using the source-and-sink
concept. They are included in transaction data described in the TSAT Model Manual.
Study mode
TSAT can be configured in one of three study modes: off-line interactive mode, off-line batch
mode, and on-line mode. In the off-line mode, it offers capabilities to perform various scenario
studies either interactively or in batches (using the Case Scheduler described in Section 9.4 or the
true batch mode described in Section 9.8). In the on-line mode, it can communicate with the EMS
system to work on the live data from EMS State Estimator (SE). The computation can be
activated whenever a new set of data is sent to TSAT, in a pre-specified time cycle.
The on-line TSAT mode requires an interface module (for example DSA Manager from
Powertech or a third party application) to manage the data exchange and result display in the on-
line system. Nevertheless, the operation of TSAT itself in the on-line mode is very similar to that
in the off-line mode. Therefore, this manual covers only the off-line operation of TSAT. A
separate document, DSA Manager User Manual, describes customization and operation of the on-
line mode.
Output analysis
TSAT has a DSAToolsTM Output Analysis (DSAOA) module for detailed analysis of the
simulation results. Common plotting, analysis, and data importing/exporting functions are
available. Refer to DSAToolsTM DSAOA Manual for details.
Other
TSAT incorporates many other useful features to assist you in using TSAT efficiently. These are
described in various sections in this manual. Among these features, the following, in particular,
are worth mentioning since they can significantly improve the productivity in using TSAT:
• The multi-contingency and multi-scenario approach to create and analyze study cases.
This allows the handling of multiple study objectives effectively.
• TSAT batch version. This version of TSAT has the same computational capabilities as
the GUI version, but it runs entirely in a batch mode. It is most suited for calling TSAT
within another application. The simulation results can also be extracted from the binary
result file in batch mode using a tool provided.
• Case Wizard. This is the tool to help set up and modify TSAT cases. Section 5 gives
details on how to work with TSAT cases using the Case Wizard.
• UDM Editor. This standalone tool allows you to create, examine, and modify user-
defined models graphically.

TSAT User Manual
• Support for batch plotting using scripting languages. This feature lets you create large
amount of plots or repetitive plots from different cases in ready-to-use formats such as
Word or PowerPoint.
• Distributed computation. This feature allows you to run multiple scenarios in a TSAT
case on multiple TSAT servers simultaneously in a computer network, thereby achieving
distributed processing of these scenarios.
• Simulation snapshots. Instead of starting a simulation from the steady state condition
which is specified by the powerflow, i.e. starting the simulation at time = 0, TSAT’s
snapshot feature allows you to save any intermediate system state during a simulation,
and start simulation(s) from this state.
• Exciter step response test and governor step response test. These two analysis modes
allow you to evaluate the step responses of generators in a single simulation.
• No disturbance test. With this feature, generators with problematic dynamic

models/parameters or problematic powerflow condition can be easily identified.
TM
1.2 Relationship with Other DSATools Programs
TSAT is a component in DSAToolTM suite which includes also Small Signal Analysis Tool
(SSAT), Voltage Security Assessment Tool (VSAT), and Powerflow and Short-circuit Analysis
Tool (PSAT). TSAT/SSAT/VSAT/PSAT use the same data formats for certain data sets and they
also share some computational modules, as illustrated in Figure 1-1.
Compatible data sets

• Powerflow data
• Dynamic data • Powerflow data
• Transaction data • Transaction data
• Dynamic
representation data
SSAT TSAT VSAT
Shared modules Shared modules
• Powerflow solver • Powerflow solver

• UDM Editor • Case Scheduler
• Case Scheduler • DSAOA

• Powerflow data
Shared modules
• Powerflow solver
PSAT
Figure 1-1: Relationship of TSAT, SSAT, VSAT, and PSAT

TSAT User Manual
1.3 Scope of This Manual
This manual provides the information related to the following topics:
• Installation of the program

• Descriptions of the solution methods and features
• Program operation
The accompanying TSAT Model Manual and DSAToolsTM UDM Manual contain the
descriptions of the models supported in TSAT, including dynamic models, contingency
specification data, monitor specification data, transaction data, sequence network data, and non-
TSAT model conversions.
The accompanying DSAToolsTM DSAOA Manual describes the functions of the DSAToolsTM
Output Analysis (DSAOA) module and gives the details on performing analysis for the
simulation results obtained from the simulations.
A file containing program release notes is included in the distribution package. This file includes
information with regard to the new features and bug fixes in this version of TSAT.
1.4 User Support Information
Powertech provides full technical support to TSAT users who subscribe to support services from
Powertech. Please direct your questions or comments to
Powertech Labs Inc.

Attention: Dr. Lei Wang
12388 – 88th Ave
Surrey, BC
Canada V3W 7R7
Telephone: (604) 590-7450

Fax: (604) 590-6656
Email: tsat@powertechlabs.com
The latest news on TSAT development, program releases, and user group activities is also posted
on DSAToolsTM website at www.DSATools.com.

TSAT User Manual
2 Installation
2.1 TSAT Distribution
The following items are included in the TSAT program distribution package:
(1) All programs and associated libraries, DLLs, and other auxiliary files (on TSAT CD)
(2) TSAT User Manual (PDF file on TSAT CD)
(3) TSAT Model Manual (PDF file on TSAT CD)
(4) DSAToolsTM DSAOA Manual (PDF file on TSAT CD)
(5) DSAToolsTM UDM Manual (PDF file on TSAT CD)
(6) Test cases (data on TSAT CD)
(7) Protection dongle(s)
If you receive TSAT upgrades, the program installation images can usually be downloaded from
Powertech’s FTP server. The TSAT manuals are distributed only in electronic form. Hard copies
can be ordered from Powertech at a nominal fee. If you have purchased SSAT/VSAT/PSAT, all
these programs share the same protection dongle(s).
2.2 System Requirements
The following computer system is recommended for TSAT:
• PC running any version of Windows operating system.

• Pentium processor or higher
• 1 GB RAM
• 150 MB free space on hard disk
• Adobe Acrobat Reader Version 4.0 or higher
• WinZip version 8.0 or higher
These are only recommended system requirements. The program should have better performance
on PCs of higher specifications. For the best display results, make sure that your monitor’s
display resolution is set at 1024×768 or higher and the system font size is set to small size. The
Acrobat Reader is necessary to view and print the documents included in the program.
WinZip is necessary to use the TSAT Archive feature (see Section 5.5).
2.3 Installing TSAT
Use the following procedure to install TSAT:
(1) Insert the TSAT CD into your CD-ROM drive. The installation program should start
automatically. Please follow the instructions to complete the installation.
(2) If the installation program does not start automatically, Select Run from the Start menu
and type
D:\setup.exe

TSAT User Manual
where D is the CD-ROM drive. Press Enter and follow the instructions to complete the
installation.
By default, the installation program will install the TSAT program in the folder
C:\DSATools_x\TSAT (or, C:\DSATools_xnet\TSAT for network version) where x is the version
number. You may change this default during the installation process, but in this manual TSAT is
also referred to as the folder where the TSAT program is located. Six test cases are included in
the TSAT distribution package:
• A two-area test case (all data files of this case are located in subfolder TSAT\2area)
• A case with a sample HVDC link (all data files of this case are located in subfolder
TSAT\dc)
• A case with sample DFIG models (all data files of this case are located in subfolder
TSAT\DFIG)
• A case with a sample SVC model (all data files of this case are located in subfolder
TSAT\SVC)
• A case with a sample STATCOM models (all data files of this case are located in
subfolder TSAT\STATCOM)
• A case with a sample TCSC model (all data files of this case are located in subfolder
TSAT\TCSC)
Section 12 gives detailed descriptions of these test cases.
Notes
(1) If your computer’s language setting is not English, you need to set it to English temporarily
for TSAT installation. Your native language can be restored after installation. The installation
program may not work correctly for a non-English language.
(2) If your computer is set to represent decimal with comma (or any other character), you must
reset this (in Control Panel). Otherwise, most of the data editing functions may not work
properly.
(3) The TSAT program runs only when the attached protection dongle is inserted into the parallel
or USB port of your PC. You might also need to install the dongle drivers included on the CD
(but not copied to your PC during the standard program installation). Refer to Section 2.4 for
details on installing the dongle drivers.
(4) After installation, do not move any files in the TSAT folder (including executables, DLLs,
and PDF files) to another folder, since this will disable some functions in TSAT or even
prevent TSAT from being started appropriately.
(5) If you have an earlier version of TSAT installed on your computer, it will not be removed
after the new version is installed. It is not recommended that you use the older version once
the new version is installed. You can manually remove the older version from your computer.
2.4 Installing Protection Dongles
Dongle types

TSAT User Manual
There are two types of dongles:
• Single-user dongles. A single-user dongle allows the unlimited application sessions for
all enabled applications on the computer where it is attached.
• Network dongles. A network dongle allows the specified application sessions for all
enabled applications on all computers in the same LAN as the computer where it is
attached. The number of sessions allowed for a normal DSATools network dongle is 10.
This means that if you have started PSAT and TSAT on your computer with this dongle,
there will be 8 additional sessions available for other users to use.
Depending on the license type that you have, you may have one or both of these dongles. Note
that TSAT is released in two versions: a single-user version that works with single-user dongles
and a network version that works with network dongles. The following modules in the TSAT
package require the dongle to run:
• TSAT executable (tsat.exe)

• TSAT batch executable (tsat_batch.exe)
Other modules (including TSAT server executable, TSATServer.exe) are not protected and thus
do not need dongle to run.
Installation of dongle drivers
The TSAT program CD includes all required dongle drivers. Occasionally, you may need to
download the latest drivers. To do so, go to http://www.dsatools.com/software/sentinel/ and
download the driver file (for example, “SPI 7.6.1 (Installer).zip”).
To install the dongle drivers, follow these steps:
(1) First be sure to remove the protection dongle from the computer.
(2) Either click on the link from the installation guide on the TSAT program CD or extract the
installer from the downloaded zip and run the installer.
(3) Perform a custom setup with the following options:
• Remove the “Sentinel Key Server”.

• Remove the “Sentinel Security Runtime”.
• For single-user dongles, the “Sentinel Protection Server” is not required and can be
removed. This is however required for network dongles and therefore must be included in
the installation.
• Ensure that both the Parallel and USB drivers are selected for installation.
(4) Once installation completes, insert the dongle to the computer. For network dongles, it may
take a few seconds for windows to recognize them and to load the drivers.
(5) It is suggested to reboot the computer after installing a driver update, but this is not always
necessary.

TSAT User Manual
Note:
• Dongle drivers should always be installed only on the computer where the dongle is
inserted. Therefore, for a computer to run the network version of TSAT, no dongle
drivers need to be installed on the computer if the dongle is attached to another computer.
• If you have already installed the dongle drivers for a previous version of TSAT, there is
no need to install the drivers again when you install a new version of TSAT.
• If you want to move the network dongle from one computer to another, you need to
install the dongle drivers on the new computer.
• After you install a dongle driver update, you don’t need to re-install TSAT.
• After you install the network dongle drivers and insert the dongle to the computer, you
can monitor the usage of the licenses by visiting port 6002 on the computer. For example,
go to http://127.0.0.1:6002/ in your Web browser to monitor the license usage for a
network dongle attached to your computer.
How to use single-user dongles
To use a single-user dongle, do the following:
• Install the single-user version of TSAT on your computer.

• Install the Sentinel Parallel and USB drivers on the same computer.
• Insert the dongle on the same computer.
• You can run TSAT on your computer now.
How to use network dongles
To use a network dongle, do the following:
• Install the network version of TSAT on your computer.

• If dongle drivers are not installed, install them on the computer where you want to attach
the network dongle. Make sure that this computer is in the same LAN as your computer.
• Ensure that the dongle is inserted on the computer where the dongle drivers are installed
• Ensure that you have license available from the dongle. See above on how to monitor the
license usage for a network dongle.
• You can run TSAT on your computer now.
When a network version of TSAT is started, it sends out a UDP broadcast over port 6001 to
request a license from a network dongle. If the Sentinel Protection Server installed on a computer
with a network dongle attached sees this broadcast, it will, if it has any available licenses, connect
(over TCP port 6001 ) to TSAT that sends the broadcast and issue it a license. Be sure there is no
firewall between the computer running TSAT and the computer with the dongle that is blocking
port 6001 or 6002. When TSAT closes, it frees the license back to the network dongle that issues
it.
In this manner the network dongle can be attached to any machine on the network. In some
network configuration there may be trouble because typically UDP broadcasts do not get

TSAT User Manual
forwarded past the local subnet. If TSAT and network dongle are located in two different subnets,
then you need to create an Environment Variable to help TSAT find the network dongle as its
broadcasts would go unanswered. On all TSAT computers that are outside the dongle subnet, the
Environment Variable “NSP_HOST” can be set to the IP address of the computer hosting the
network dongle. If TSAT sees the NSP_HOST variable, it will not broadcast to find a license, but
instead directly connect to the IP specified by the NSP_HOST variable.
Troubleshooting ideas
If you get a message windows indicating “Powertech SuperPro key not found…Try again?” when
you run TSAT, here are a few things you can try to fix the problem:
• This message indicates that TSAT is looking for a single-user dongle. So if you intend to
use a network dongle to run TSAT, install the network version of TSAT.
• Ensure that a single-user dongle provided by Powertech is inserted at the USB port of
your computer.
• Ensure that the dongle drivers are installed on your computer.
• Ensure that TSAT is enabled on the dongle you use. This may be the issue if you licensed
other software from Powertech and added TSAT later. Then the original dongles issued
for other software will not be enabled for TSAT. If you are not sure on this, please
contact Powertech for clarification.
• Occasionally, a dongle may break down after some time of use. Please contact Powertech
should this happens.
If you get a message window indicating “...Network key not found...?” when you run TSAT, here
are a few things you can try to fix the problem:
• This message indicates that TSAT is looking for a license from a network dongle. So if
you intend to use a single-user dongle to run TSAT, install the single-user version of
TSAT.
• Ensure that a network dongle provided by Powertech is inserted at the USB port of a
computer in the same LAN as your computer.
• Ensure that the dongle drivers are installed on the computer where the dongle is attached.
• Ensure that there is no firewall in the network for port 6001 and 6002.
• If the computer with the network dongle attached and the computer running TSAT are in
different subnet, you need to set a NSP_HOST variable as described above.
• Ensure that TSAT is enabled on the dongle you use. This may be the issue if you licensed
other software from Powertech and added TSAT later. Then the original dongles issued
for other software will not be enabled for TSAT. If you are not sure on this, please
contact Powertech for clarification.

TSAT User Manual
• Occasionally, a dongle may break down after some time of use. Please contact Powertech
should this happens.
2.5 Customizing TSAT
The standard TSAT version is shipped with the following configuration:
• The distributed computation manager is included

• The TSAT Case Scheduler is included
• TSAT batch version is included
• The UDM Editor is included
• The scripting engine for batch plotting is included
• The DSAToolsTM Output Analysis is included
• The Contingency Converter is included
• The on-line mode interface module (DSA Manager) is not included
Depending on the program license agreement, the actual TSAT shipped may be different from the
above standard configuration. Some functions for on-line application mode may be included in
the standard off-line version. This manual is written for the standard configuration. If information
not described in this manual is required, please contact Powertech.
After TSAT is installed, program customization may be needed to reset certain computation
parameters (such as base system frequency, zero impedance line tolerance, etc.). Refer to Section
5.2.1 for details on performing such customization.
2.6 Running the Test Cases
To start the TSAT program, double-click the file “TSAT.exe” in the TSAT\bin folder, or TSAT
in the Start menu, or the TSAT program icon on the desktop. Once TSAT starts, you can open
any of the TSAT case files in the test case folders to test the program (select the File | Open
function in the TSAT main window):
• For the two-area test case, the case file is named 2area.tsa in the folder TSAT\2area
• For the dc test case, the case file is named dc.tsa in the folder TSAT\dc.
• For the DFIG test case, the case file is named dfig.tsa in the folder TSAT\DFIG.
• For the SVC test case, the case file is named svc.tsa in the folder TSAT\SVC.
• For the STATCOM test case, the case file is named statcom.tsa in the folder
TSAT\STATCOM.
• For the TCSC test case, the case file is named tcsc.tsa in the folder TSAT\TCSC.
After a TSAT case file is opened, you may do any of the following:
• Perform the basecase analysis (for all test cases).

• Perform the transaction analysis (for the two-area case only).

TSAT User Manual
Refer to Sections 6 and 7 for details on using these features.
Note
It is not recommended to modify the test cases when testing the program, unless you are already
an experienced user of TSAT.

TSAT User Manual
3 TSAT Concepts
This section describes briefly the background of the transient security assessment problem and
the solutions provided by TSAT. In addition, the analysis modes available in TSAT and some
basic concepts in using TSAT are explained.
3.1 Transient Security Assessment
Secure operation of interconnected power systems has always been a challenging task because of
their intrinsic dynamic nature with constantly changing load, generation, topology, and key
operating parameters. Security assessment is primarily concerned with the following three issues:
(1) How well a particular system condition can withstand credible contingencies (degree of
stability)? Further, if there are potential security violations, where and what type of
violations are likely to occur?
(2) What is the maximum secure power transfers under these contingencies (stability limit)?
(3) What can be done to prevent the insecure conditions if the system will be insecure for a
critical contingency (remedial actions)?
For convenience of analysis and resolution of problems, power system security assessment is
normally performed using two separate concepts covering two different aspects of the power
system security [1]:
• Transient (angle) security

• Voltage security
TSAT deals primarily with the transient security assessment (TSA) problem, but its modelling
capabilities and computation features allow the extended simulations for studying dynamic
voltage security assessment (VSA) problem.
The center of the TSA problem is transient stability which is clearly defined and can be analyzed
using proven technical methods [1]. As a result, transient stability analysis has been traditionally
conducted off-line using step-by-step time-domain simulations of a wide range of possible system
conditions, under an exhaustive set of credible contingencies. Although this approach is able to
handle very large and complicated power system models with very good computation accuracy, it
cannot meet some of the critical TSA requirements. For example,
• Time-domain simulations cannot give stability margin and sensitivity information, which
are necessary for determining degree of severity for a contingency, power transfer limits,
and remedial control actions if the system is unstable at a particular system condition.
• Time-domain simulations do not directly provide security indices for various forms of the
transient security problem, such as transient angle stability, insufficient damping,
excessively voltage/frequency drop/rise, and relay margins.
• The end results of a transient security assessment are usually a set of the stability limits
within which the system must be operated for a particular system condition. In the

TSAT User Manual
conventional approach, these limits are often obtained using a trial-and-error method with
human interaction.
• The computation time needed to process all credible contingencies using the detailed
time-domain simulations could be excessive and unacceptable.
In order to meet the above requirements, and to still maintain the capability of analyzing
accurately large and complex power system models, TSAT is equipped with the following
modules to provide a realistic TSA solution:
• A full-featured time-domain simulation engine is used for the detailed analysis of critical
contingencies. The accompanying manual, TSAT Model Manual, describes the modelling
capabilities and other features of the simulation engine.
• A security computation module is used to obtain various transient security indices:
Transient stability indices

Damping indices
Voltage drop/rise duration indices
Frequency drop/rise duration and rate of change of frequency indices
Relay margin indices
Peak-to-peak angle indices
Closing torque indices
• If a large set of contingencies are to be analyzed, they can be screened by the early
termination technique and ranked by any of the transient security indices or critical
clearance time (CCT) of faults.
• A stability limit search module is used to compute power transfer limits for specified
power transactions. This allows a fast and systematic determination of stability limits.
In the on-line version of TSAT, additional functionalities are provided, for example, to
recommend preventative generator dispatch actions if the system is found to be insecure for a
given condition. Please refer to DSA Manager User Manual for details on these.
The overall solution structure of TSAT is shown in Figure 3-1.

TSAT User Manual
Input data
System initialization
Very stable contingencies

Time-domain are ignored if early
simulation engine
termination option is enabled
Powerflow dispatcher
Security computation
On-line version only
Basecase Preventative control

Transaction
action determination for
analysis analysis
insecure contingencies
Stability Limits Security Indices
Figure 3-1: TSAT solution structure
3.2 Time-domain Simulations
As mentioned earlier, the core technology of TSAT is a time-domain simulation engine.

Technically, time-domain simulations solve a set of nonlinear differential-algebraic equations of
the following form from a power system:
x& = f ( x , V )
I( x , V) = YN V
where x is the state vector, V is the voltage vector, and I is the current injection vector. YN is the
network admittance matrix mostly obtained from the powerflow data. f is a set of nonlinear
functions determined from the dynamic models (such as generators). This set of equations is
solved using step-by-step numerical integration techniques, for a given initial condition
(contained in the powerflow data) and the specified disturbances (contained in the contingency
data).
Solution of the differential equations
Several techniques [1] are available in TSAT to solve the differential equations:
• Modified Euler
• Second order Runge Kutta
• Third order Runge Kutta
• Fourth order Tunge Kutta
• Trapezoidal
The selection of the method and the integration step size are made in the contingency data.

TSAT User Manual
It is commonly known that solving differential equations by numerical integrations may be

subject to numerical stability issues, particularly when an explicit method (such as Kunge Kutta
methods) is used. In TSAT, such issues are handled with two techniques:
• In control systems where large gains and small time constants exist (thus numerical
instability is prone to occur), an inner integration loop is performed with smaller
integration step sizes.
• An option is available to set very small time constants to a minimum consistent with the
frequency spectrum (0.1 to 5.0 Hz) of transient stability problem.
Solutions of the algebraic equations
Technically, the algebraic equations to be solved during simulations are nonlinear, due to the
presence of nonlinear algebraic models, such as nonlinear loads, generator saliency, etc.
However, the network model is linear and represented by the admittance matrix YN. To simplify
the solution process and to take the advantage of the linear network equations, all nonlinear
algebraic models are separated from the network and treated as current injections when the
network equations are solved. The solution of the algebraic equations then involves an iterative
process:
• The current injections are updated with existing voltages from all dynamic models and
nonlinear algebraic models;
• The linear network equations are solved to update the voltages.
Solution of the network equations is performed by using the standard L-U decomposition method.
The solution algorithm takes the advantage of very sparse network admittance matrix YN so as to
achieve fast computation time.
Solution of the entire differential-algebraic equation sets
The overall system differential and algebraic equations are solved using a partitioned approach:
• Numerical integration is performed to solve the differential equations.
• Iterative solution is performed to solve the algebraic equations.
• The current injections and the bus voltages are the interface variables.
This is shown in Figure 3-2.

TSAT User Manual
Algebraic equations
Generator
(V, I) Other
stator equations (V, I)
generators
Transmission Induction
network (V, I)
motors
Excitation system Generator rotor equations
equations circuit equations Other dynamic
(V, I)
models
Prime mover / Generator (V, I) (V, I)
governor equations swing equation
Nonlinear Other static

Differential equations loads models
Figure 3-2: The Overall system model of time domain simulations
3.3 Post-processing of Simulation Results
The results from the time-domain simulations are processed in TSAT’s security computation
module to obtain valuable transient security indices. These are described in the following
sections.
3.3.1 Transient Stability Indices
As mentioned earlier, the conventional time-domain simulation is able to give accurately the
trajectory of a system following a disturbance. The interpretation of this trajectory (i.e., how
severe is the contingency) has traditionally however been left largely to the engineer’s judgment.
In TSAT, two methods are provided to assess the severity of a contingency, each of which gives a
transient stability index:
Power swing-base stability margin or index (SM)
This is based on an approach described in reference [2]. This method consists of three steps in
determining the stability index:
(1) Step 1: Identify critical cluster of generators (CCG). This is the group of generators that
become unstable or will likely become unstable at the more stressed system condition.
(2) Step 2: Form parametric one-machine-infinite-bus (OMIB) equivalent. The parameters of

this equivalent are constantly updated using simulation results of the full system.
(3) Step 3: Determine stability of the system and compute stability margin (index).
The full derivation and description of this method is contained in [2] and the associated literature
on the subject.

TSAT User Manual
Power angle-based stability margin or index (AM)
This index is defined as follows for each island in the system:
360 − δ max
η= × 100 − 100 < η < 100
360 + δ max
where δmax is the maximum angle separation of any two generators in the island at the same time
in the post-fault response. The transient stability index for the system is taken as the smallest
index among all islands. Thus, η>0 and η≤0 correspond to stable and unstable conditions
respectively. Figure 3-3 illustrates the definition of this index. AM is directly proportional to
system angle separation so it gives a good indication of how severe a system is following a
contingency. Table 3-1 shows the relationship between δmax and η.
Generator relative angle (deg) : Reference Generator = 30151 [SCP--#1G22.0] ' 1'
62
44
δ max 26
-10
-28
0.000 2.000 4.000 6.000 8.000 10.000
Ti me (sec)
Figure 3-3: Illustration of AM
Table 3-1: Relationship between δmax and η

δmax (degrees) η (%)
90 60.0
120 50.0
180 33.3
360 0.0
3.3.2 Damping Indices
The small-signal stability problem commonly appears as a problem of insufficient damping in a

power system. It is well known (see [1]) that the most effective way to analyze this problem is by
the modal analysis approach based on the eigenvalue analysis of the linearized system model. For
transient security assessment (particularly in on-line applications), however, this approach has

TSAT User Manual
limitations, mainly because of its intensive numerical computation requirements. Therefore,

alternative method needs to be used.
One such method is the Prony analysis [3] that decomposes a time-domain signal into a number
of modes. Each mode is characterized with frequency, damping ratio, and the amplitude in the
signal. In TSAT, a four-channel Prony analysis algorithm is implemented to identify the worst
damping σ from modes that satisfy the following conditions:
• They are within a specified frequency range

• They have sufficiently large amplitudes
• They are most visible from a set of generators
In the worst damping identification algorithm, the Prony method is applied simultaneously to the
relative rotor angles of up to four generators in a time window you specify. σ is used as the
damping index to determine the degree of small-signal stability for a contingency.
In order to ensure that the signals used for Prony analysis is free of nonlinear interaction, a feature
is available in TSAT to extend the simulation if the damping is poor. Please refer to Section
5.2.1.3 for details.
3.3.3 Voltage Drop/Rise Duration Indices
Voltage drop/rise duration indices (TVdrop and TVrise) are used to catch non-permissible under-
and/or over-voltages during the simulation. These indices are defined as the maximum time
duration for which the voltage drop/rise threshold is violated, as shown in Figure 3-4.
Voltage rise threshold

Voltage magnitude
TVrise
Voltage drop threshold
TVdrop
TVdrop = Max. drop duration

TVrise = Max. rise duration
Time
Figure 3-4: Voltage drop/rise duration index definition
3.3.4 Frequency Indices
The frequency security indices are defined similarly to the voltage security indices and these are
used to catch frequency violations in the system during the simulation. There are three frequency
security indices:
(1) Frequency drop duration index (TFdrop): this is defined as the maximum time duration for
which the frequency drop threshold is violated.

TSAT User Manual
(2) Frequency rise duration index (TFrise): this is defined as the maximum time duration for which
the frequency rise threshold is violated.
(3) Rate of change of frequency index (α): this is defined as the minimum rate of change of
frequency (i.e., the fastest frequency decay).
3.3.5 Relay Margin Indices
The relay margin indices measure the distances between the apparent impedance trajectories of a
transmission line and the impedance circles of user-defined distance relay characteristics, thereby
determining whether or not the relay might operate for the given contingency. The contingency is
considered insecure if the relay margin is not sufficient.
Two relay margin indices are provided (for zone 1 and zone 2 settings). For each setting, the relay
margin (%) of any point on the apparent impedance trajectory of the transmission line is defined
as follows:
 ST
 × 100 If CS ≥ CT
 OS
M=
− ST × 100 If CS < CT
 OS

where
S is a point on the apparent impedance trajectory of the transmission line (Figure 3-5 and
Figure 3-6)
T is the point on the relay characteristic closest to S
O is the origin of the R-X plane
C is the center of the relay characteristic
The relationship is shown in Figure 3-6 below. The relay margin index is taken to be the smallest
margin computed for all transmission lines monitored.
The following relay characteristic parameters are used to define the impedance circle:
• Reach (RCH) in percentage of the transmission line impedance: typically 80% for Zone 1 and
120% for Zone 2
• Center Distance (C) from origin in percentage of the transmission line impedance: if this
parameter is one-half of RCH, the impedance circle passes through the origin.
• Centerline angle (θ): default θ = tan-1(X/R), the angle of the transmission line impedance.
It is also possible to specify a relay margin threshold which determines what relay margins (M
from above) are considered insecure.

TSAT User Manual
V
I
V
S=
I
Figure 3-5: Transmission line apparent impedance definition
X Apparent impedance
trajectory
RCH S
T
C
θ
O R
Relay characteristic
Figure 3-6: Relay margin definition
3.3.6 Peak-To-Peak Angle Indices
For many utilities, system stability is measured by simply examining the maximum peak-to-peak
generator relative angle. The peak-to-peak angle index is calculated to meet such requirement.
This index is calculated as follows:
δpp = max(δmax(i ) − δmin(i ) )
where δmax(i) is the maximum relative angle of generator i and δmin(i) is the minimum relative angle
of the same generator during a simulation.
3.3.7 Closing Torque Indices
When a branch is closed, a torque will be applied to the shaft of generators nearby. This may
cause concern if this suden change in torque is too large. An index (∆PC) can be calculated to
measure this. This index is simply the instantaneous change of the electric power (in per unit on
generator MVA base) on generators in the specified region. The index is calculated only for the
following two types of contingencies:
• Add a branch (line, pi line, or transformer)

• Reconnect a branch (line, sectional line)

TSAT User Manual
3.3.8 General Comment on Security Criteria
The seven security criteria described above can be applied with the following method:
• They are defined in the Criteria Data file (described in TSAT Model Manual).
• Multiple criteria sets can be defined for one case; each set of criteria can include selected
or all criteria.
• One criteria set can be applied for a specified subsystem and/or for a specified set of
contingencies.
These rules allow for very flexible applications of the security criteria. For example, the
following can be defined for a TSAT computation scenario:
• Application of different transient voltage drop criteria for different types of buses.
• Application of damping criteria to selected generators.
• Application of peak-to-peak angle criteria to selected region of a system.
3.3.9 Critical Clearance Time (CCT) of Faults
The critical clearance time (CCT) of fault is rarely used in actual system design; however, it is
generally considered as the best measurement of severity of a contingency and thus widely used
for ranking contingencies in terms of their severity. TSAT can compute CCT automatically as a
transient stability index.
Obviously, this index applies only to contingencies that have faults (contingencies without faults
are ignored). In TSAT, this can be a three-phase, one-phase-to-ground, or two-phase-to-ground
fault, at a bus or on a transmission circuit. If multiple faults are applied in a contingency, CCT is
computed for the first one.
By definition, CCT is the longest fault clearance time without losing stability. This is obtained,
using a binary search method, within a specified fault clearance range with a set threshold, as
illustrated in Figure 3-7. The stability margin and its threshold applied to check the system
stability can be based on either SM or AM.
Stability margin
More stable
Search threshold
Stability boundary
More unstable
Search range
Fault clearance
CCT
Figure 3-7: CCT computation

TSAT User Manual
3.3.10 Early Termination of Simulations
In order to speed up computations in specific applications, such as the on-line TSA, the
assessment of contingencies must be done as quickly as possible. A feature is available in TSAT
to do so by terminating the simulation of a contingency once it can be definitely classified as
stable or unstable. The early termination algorithm works as follows:
• A time point during the simulation is specified for initiating the early termination check.
This can be any time (say 2.5 seconds) during transients. The main consideration is to let
the first swing pass.
• For early termination on stable condition, SM and the maximum peak-to-peak power
angle swing in the system are computed and compared with the specified thresholds. The
simulation is terminated only if SM is larger than the set threshold and the maximum
angle swing is less than the set threshold. Early terminated stable contingencies are
ignored for further process and result visualization.
• For early termination on unstable condition, SM and AM are computed and compared
with the specified thresholds. The simulation is terminated only if both margins are less
than the set thresholds simultaneously. Results of early terminated unstable contingencies
are fully kept in the binary result file and in all result reports.
Note that since the early termination algorithm checks only for the transient stability index, its
use should be cautious if other forms of security are of concern for a particular case.
3.4 Modelling Considerations
Reading PSF/PFB powerflow data
PSF/PFB is the native powerflow format of DSAToolsTM. Only the binary format of PSF/PFB can
be read by TSAT. When using PSF/PFB powerflow data, dynamic data can be in any supported
format (however, third party dynamic data formats cannot be mixed; for instance, PSS/E and
PSLF models cannot be mixed in one case).
Reading PSS/E powerflow data
TSAT can read PSS/E powerflow data in RAWD format format. TSAT supports this format up to
PSS/E Rev. 32.
Note that although the three-winding transformer models in PSS/E format are fully supported in
TSAT, you have limited access in simulations to these transformers. For instance, they cannot be
monitored, cannot be accessed in some switching commands, cannot have dynamic ULTC
models, and cannot be used to obtain remote signals (such as line power) in user defined models.
If any of the above is needed for a three-winding transformer, it must be represented by
equivalent two-winding transformer models.
When using PSS/E powerflow data, dynamic data can be in any supported format except for the
BPA format (however, third party dynamic data formats cannot be mixed; for instance, PSS/E
and PSLF models cannot be mixed in one case).

TSAT User Manual
Reading PSLF powerflow data
TSAT can read the powerflow in PSLF EPC format. The PSLF EPC format powerflow data can
be readily exported from a working case of the PSLF program. It is recommended to always solve
the powerflow using the PSLF program before exporting the powerflow data to be used in TSAT.
The following PSLF powerflow data sections are ignored when importing to TSAT:
• GCD data
• Interface Data
• Interface Branch Data
• Transaction Data
The following solution parameters in a PSLF powerflow are preserved and used when solving
powerflow:
• tap
• phas
• area
• svd
• jump
• toler
• sbase
It has been found that some PSLF powerflow cases may require careful tuning to obtain valid
solutions. It is recommended to use PSAT to convert the PSLF powerflow to PSF/PFB format
and solve it. Then use the PSF/PFB file in TSAT. Using PSF/PFB file in TSAT will also increase
the performance of TSAT.
When using PSLF powerflow data, dynamic data can be in any supported format except for the
BPA format (however, third party dynamic data formats cannot be mixed; for instance, PSS/E
and PSLF models cannot be mixed in one case).
Reading BPA powerflow data
TSAT can read the powerflow in BPA format. When using powerflow data in BPA format, it is
recommended to always provide the solution file (*.pfo) created by the BPA program so that
TSAT can use the solved powerflow as the starting point for the simulation. Otherwise, a flat-
start powerflow solution is required in TSAT, which may require careful tuning to obtain a valid
solution.
Refer to Section 10 for details on specifying the powerflow solution file when using BPA
powerflow data.
When using BPA powerflow data, dynamic data can only be in BPA format.
Matching powerflow and dynamic model data
TSAT matches the powerflow and dynamic model data using the following principles:

TSAT User Manual
(1) A generator model in dynamic data is included in the overall system dynamic model only if it
is matched with
• a generator with both generator bus number and unit ID in powerflow of PSF/PFB,
PSS/E, or PSLF format
• a generator with generator bus name in powerflow of BPA format
If no such match is found, the generator model in dynamic data is ignored.
(2) When using BPA powerflow and dynamic data, the generator IDs in powerflow are ignored
and the total generation at a bus is shared by all generators matched for the bus in dynamic
data by the sharing percentages specified in dynamic data.
(3) If a generator in powerflow does not have a matching dynamic model, the generator is netted
out as constant impedance.
(4) The MVA base of a generator may be taken from either powerflow or dynamic data,
depending on the data format:
• For dynamic data in DSATools format, the generator MVA base is taken from dynamic
data unless it is not provided.
• For dynamic data in PSS/E format, the generator MVA base is taken from powerflow
data.
• For dynamic data in PSLF format, the generator MVA base is taken from dynamic data if
it is provided; otherwise, the MVA base in powerflow data is used.
• For dynamic data in BPA format, the generator MVA base is taken from dynamic data.
(5) The generator stator resistance included in powerflow is used in the generator model, but the
source reactance (X”d) included in powerflow is not used for the generator model except for
the classical model in PSS/E format (GENCLS model).
The dynamic model match determined using the above rules can be customized by using dynamic
representation data. Refer to TSAT Model Manual for details on how to use dynamic
representation data.
TSAT can read PSS/E IDEV files that contain the GNET command to net generators. Please refer
to Section 5.2 for details.
Powerflow solution
TSAT has a built-in powerflow solver that uses the fast de-coupled powerflow solution algorithm.
This powerflow solver is used to solve the working case when any of the following happens:
(1) The Solve Base Powerflow command in the powerflow data section of the case file is set
to YES.
(2) A pre-simulation outage or dispatch is specified (see the switching command At Time in the
TSAT Model Manual).

TSAT User Manual
(3) A transaction analysis is to be performed.
When solving the powerflow, an optional solution parameter file can be provided to control the
solution process. Refer to Section 10 for details.
Load models
Loads are modelled in TSAT as follows.
In powerflow solutions of the base case and pre-simulation outages/dispatches, constant MVA
model is used.
In the dynamic simulations, TSAT default load models are used (refer to Section 5.2.1 on how to
set the default load models), with two exceptions: (i1) if load models are specified in dynamic
data for some or all of loads, these loads will be modeled by the specified models; (2) if PSS/E
IDEV files that contain the CONL command to convert loads are specify in the dynamic
representation data section (refer to Section 5.2.7 for details). In these cases, the TSAT default
models will be ignored for these loads.
When performing the powerflow dispatches in a transaction analysis, constant MVA model is
always used for all loads, regardless the load models specified in powerflow and dynamic data
(this is necessary in order to obtain accurately the required dispatch levels).
Generator load angle definition
By default, TSAT provides absolute load angles of all monitored generators. This angle is defined
as the angle between the generator rotor q-axis and the system reference D-axis which is rotating
at the synchronized speed, as shown in Figure 3-8.
q
d-q generator rotor d-q axes reference
Q D-Q synchronizing rotating system reference
V generator terminal voltage
φ voltage angle with respect to the synchronizing
V rotating system reference; this is the voltage
D
angle in the powerflow at the pre-fault condition
δ’ generator internal load angle
δ generator load angle with respect to the
δ
δ' synchronizing rotating system reference
φ
d
Figure 3-8: Definition of absolute load angle of generator
3.5 Analysis Modes
There are five basic analysis modes in TSAT for each computational scenario:

TSAT User Manual
(1) Basecase analysis

(2) Transaction analysis
(3) Exciter step response test
(4) Governor step response test
(5) No disturbance test
They are described in the following subsections. Please see Section 3.7 for the descriptions of
TSAT case and scenario concepts that are referred to in this section.
3.5.1 Basecase Analysis
Basecase analysis is used to perform the transient security assessment at one system operating
condition for all critical contingencies specified (this is referred to as a basecase analysis
scenario). The security of the system for each contingency is assessed using time-domain
simulations and the post-processing which calculates any or all of the following security indices:
• Transient stability index (SM or AM) or critical clearing time (CCT)

• Damping index (σ)
• Voltage drop/rise duration indices (TVdrop and TVrise)
• Frequency drop/rise duration indices (TFdrop and TFrise) and rate of change of frequency
index (α)
• Relay margin indices (M)
• Peak-to-peak angle indices (δpp)
• Closing torque indices (∆PC)
If any of the specified criteria for these stability indices is violated, the system is considered
insecure for the contingency, and thus the scenario is insecure. If the contingencies have been
ranked prior to the basecase analysis, only those contingencies considered as critical by the
ranking criterion will be submitted to the basecase analysis.
3.5.2 Transaction Analysis
Transaction analysis is used to determine the stability limit of a power system with respect to a
given power transfer under all critical contingencies (this is referred to as a transaction analysis
scenario). The objective of a transaction analysis is to search iteratively for the stability limit that
satisfies the following conditions:
• The system is secure at this power transfer under all critical contingencies. The security
can be measured by any or all of the indices available in the basecase analysis (except for
CCT).
• The system will become insecure (note that powerflow insolvability is considered as one
form of insecurity) if the power transfer is increased by an amount equal to a specified
threshold (“Power Limit Search Threshold”).
Power transfer
A power transfer is defined as a set of powerflow dispatches in which the generation and/or loads
are changed to meet specific system dispatch conditions. A power transfer is described in TSAT

TSAT User Manual
using the source-and-sink concept, as shown in Figure 3-9 in which a combination of generation
and load dispatches in the Source is applied to meet the load increase in the Sink. TSAT Model
Manual contains the format specifications of data required to define a power transfer.
Source Sink
Increased power transfer
Figure 3-9: An example of a power transfer
In general, a power transfer can be described with two variables: an independent variable and a
dependent variable, one of which can be used to specify the source and the other the sink in the
transfer. Either independent or dependent variable may consist of a combination of load and/or
generation dispatches (increase or decrease), as long as they do not conflict (for example, they
cannot both consist of load increases only). When dispatching the powerflow for the transfer, the
required dispatches for the independent variable are made first, and the dispatches for the
dependent variable are then adjusted to solve the powerflow.
A transaction analysis process may be complicated, depending on a number of factors including

different system conditions and limit search requirements. These are described in the following.
Search direction
The limit search can be performed in two possible directions:
• Forward search. This applies if the base system condition is secure for all contingencies
to be considered. In this case, the stability limit is higher than the value in the base case
so the transfer needs to be increased.
• Backward search. This applies if the base system condition is insecure for at least one of
the contingencies to be considered. In this case, the stability limit is lower than the value
in the base case so the transfer needs to be decreased.
Although backward search can be considered as the “reverse” operation of forward search,
different power transfer definitions are usually required for searches on either direction, since it is
likely that the system dispatch requirements are different for increase or decrease of transfrers.

TSAT User Manual
Forward search Backward search

• Base system condition secure • Base system condition insecure
Stability • Stability limit is the largest Stability • Stability limit is the smallest
margin transfer increase without margin transfer decrease without
stable violating any security criteria violating any security criteria
stable
More
More
Stability boundary Stability boundary
unstable
unstable
More
More
Stability limit Transfer Stability limit Transfer
increase decrease
Figure 3-10: Stability limit search direction
Search method
After the stability limit search direction is determined, the next decision to make is the search
method to use for a specified power transfer and one contingency. A power transfer definition
tells only how powerflow should be dispatched to increase or decrease the transfer. Since the
stability limit search is an iterative process, the search method determines how much the transfer
should be adjusted in the iterations so as to most efficiently find the stability limit. TSAT
provides three options to choose from (all the illustrative examples assume forward limit search):
• Automatic method: refer to Figure 3-11 (a). In this method, the amount of transfer
adjustment for the next iteration is determined using a combination of linear and
quadratic interpolation/ extrapolation. This is therefore best suited if the relationship
between stability margin and power transfer is smooth.
• Binary method: refer to Figure 3-11 (b). In this method, the amount of transfer adjustment
for the next iteration is determined using the bisection method. This is best suited if the
relationship between stability margin and power transfer is unknown or complicated. This
method guarantees the convergence within a maximum number of iterations. If the target
power transfer increase is P, after N iterations (N≥2), the range to be searched is reduced
P
to N −2
. In other words, if P=1000 MW, it takes a maximum of 8 iterations to narrow the
2
transfer limit within 20 MW.
• Fixed step method: refer to Figure 3-11 (c). In this method, the amount of transfer
adjustment for the next iteration is determined using fixed steps specified in power
transfer data. This is best suited if the approximate range of the stability limit is known.
Two search steps can be specified in the power transfer data: a large step for quickly
increasing the transfer and a small step for fine-tuning the stability limit.

TSAT User Manual
Stability Searched points

margin
Next search point using
linear/quadratic extrapolation
Stability limit Transfer

increase
(a) Automatic method
Stability First searched point Stability First searched point

margin margin Second searched point
Next search point
Second Next search point

searched
point
Refinement using
small search step
Stability limit Transfer Stability limit Transfer
increase increase
(b) Binary method (c) Fixed step method
Figure 3-11: Stability limit search method
Search strategy
This is related to the handling of multiple contingencies in the stability limit search. Transaction
analysis always considers one contingency at a time, and the final stability limit for the given
power transfer is the smallest of the limits found for all contingencies. To meet requirements of
different applications, two search strategies are available in TSAT to handle multiple
contingencies (all the illustrative examples assume forward limit search):
• Search for each contingency: with this strategy, stability limit is computed for each
contingency sequentially and independently. The final limit is taken as the smallest of the
limits from all contingencies. This is illustrated in Figure 3-12 (a). The advantage of this
method is that it gives limit for each individual contingency. The disadvantage is the
computation speed – a complete limit search is necessary for each and every contingency.
If on average N iterations (simulations) are required to find the stability limit for one
contingency, the total number of simulations required for processing M contingencies
would be N×M.
• Search for entire scenario: with this strategy, a full stability limit search is performed
only if necessary. The strategy works as follows (illustrated in Figure 3-12 (b)):

TSAT User Manual
A full stability limit search is always performed for the first contingency. The limit
found is assumed to be the system limit.
The system limit is tested for all subsequent contingencies by performing simulations
for these contingencies at the transfer level corresponding to the system limit.
If a subsequent contingency is stable, it is ignored – the system limit remains the

same as before.
If a subsequent contingency is unstable, a complete stability limit search is performed

again for the contingency to obtain the new system limit.
This process continues until all contingencies are processed.
When this strategy is used, it is obvious that the order of contingencies by which they are
processed is critical in order to reduce the computation time. In the ideal situation, the
most critical contingency should be placed as the first contingency in the contingency list.
This would imply a full limit search for the first contingency. For all remaining
contingencies, only one simulation is needed to confirm the limit. Thus, if N iterations
(simulations) are required to find the stability limit for the first contingency, the total
number of simulations required for processing M contingencies would be N+M-1.
Fully searched for

any subsequent
contingencies only
if the limit is lower
Scenario limit is verified
for other contingencies
Stability Stability
margin Each contingency margin
is fully searched
Fully searched for
the first contingency
System Transfer System Transfer

limit increase limit increase
(a) Search for each contingency (b) Search for entire scenario
Figure 3-12: Stability limit search strategy
Factors terminating a transaction analysis
When a transaction analysis is terminated, it may be caused by one of the following factors:
• The required power transfer increase or decrease target is reached. In other words,
stability limit is higher than the required increase target, or stability limit is below the
decrease target.

TSAT User Manual
• At least one of the security criteria is violated. The stability limit is found.
• Either independent or dependent variable reaches the dispatch limit (for example, all
generators that can be dispatched reach their output limits) before the required transfer
target is met. In this case, the power transfer is limited by system resources.
• The powerflow is not solvable. If the powerflow cannot be solved because of improper
controls used in the solution process, the control parameters should be reviewed and
adjusted. If the powerflow solution does not exist (i.e., the post-contingency powerflow is
beyond the nose point of the P-V curve), voltage stability may be the limiting factor for
the transaction.
A transaction analysis example
In the following, a forward power transfer limit search using binary method is illustrated using an
example. Three contingencies are considered and the search strategy is for the entire scenario.
Referring to Figure 3-13, assume that the power transfer target is Pr. The computation is carried
out as follows.
Stability margin
a
Contingency 1 iteration
A Contingency 2 iteration
2
Contingency 3 iteration
Secure
3
b
5
4
Insecure
Maximum feasible
power transfer level,
1 beyond which either
the generation
dispatch limit is
reached or powerflow
Final power transfer limit is not solvable
Pb Pf Pm Pr
Power transfer
Figure 3-13: A power transfer limit search example
Contingency 1
The iteration for Contingency 1 starts at the base powerflow transfer level Pb. The stability
margin (point ‘a’) at this condition indicates that the system is secure. Therefore, the iteration
continues to point ‘b’ at which the maximum feasible power transfer Pm is reached (Pm≤Pr). Since
point ‘b’ is also a secure point, Pm is taken as the power transfer limit for Contingency 1.
Contingency 2

TSAT User Manual
The iteration for Contingency 2 starts at where Contingency 1 ends – the power transfer level at
Pm. The stability index (point ‘A’) indicates that the system is secure at this condition. Therefore,
no further iteration is necessary, and the power transfer limit stays at Pm for both Contingency 1
and 2.
Contingency 3
The iteration for Contingency 3 follows the same rule – starting at Pm. This time, however, the
stability index (point ‘1’) shows that the system is insecure at this condition. Therefore, the
iteration is re-started from the beginning – the base powerflow transfer level Pb. With the binary
search method, the iteration goes through points ‘2’, ‘3’, ‘4’, and ‘5’. Finally, the difference
between the largest secure power transfer (point ‘5’) and the least insecure power transfer (point
‘4’) is within the specified threshold. The iteration stops and the final power transfer limit Pf is
taken to be the last secure transfer at point ‘5’.
3.5.3 Exciter step response test
Exciter step response test is used to evaluate the transient responses of a generating unit to a step
change at the reference point of the voltage regulator. Such transient responses can be simulated
with one of two possible system configurations:
(1) The generator is connected to an infinite bus (Single-Machine-Infinite-Bus or SMIB)

through a Thevenin equivalent impedance computed by TSAT. Two options are available
to set the generator operating condition:
• Using the generator operating condition specified in the powerflow data

• Using the rated generator operating condition
(2) The generator is operated in open-circuit condition.
When performing the exciter step response test, the contingency data included in the scenario is
ignored.
In this analysis, the exciter step responses of a group of generating units can be evaluated in a
single simulation. The main characteristics of the responses of each unit will be listed in a table
which includes the following quantities:
• Rise time
• Overshoot
• Settling time
• Frequency and damping factor of the dominant oscillatory mode (computed using Prony
analysis)
These quantities are calculated from the generator terminal voltages and are defined in Figure
3-14 which shows a typical exciter step response for a generating unit.

TSAT User Manual
Figure 3-14: A typical exciter step response
3.5.4 Governor step response test
Governor step response test is used to evaluate the transient responses of a generating unit to two
types of disturbances:
(1) A step change applied to the reference point of the governor when the generator is
operating in the single-machine-infinite-bus (SMIB) condition.
(2) A partial load rejection test.
When performing the governor step response test, the contingency data included in the scenario is
ignored.
In this analysis, the governor step responses of a group of generating units can be evaluated in a
single simulation. The main characteristics of the responses of each unit will be listed in a result
table. For the governor reference step change test, the following quantities are obtained from the
simulations:
• Rise time
• Overshoot
• Settling time
• Frequency and damping factor of the dominant oscillatory mode (computed using Prony
analysis)

TSAT User Manual
These quantities are calculated from the generator mechanical torques and are defined in Figure
3-15 which shows a typical exciter step response for a generating unit (this curve does not show
overshoot which is defined similarly to the exciter step response curve shown in Figure 3-14).
Figure 3-15: A typical governor step response
In the partial load rejection test, the generator is connected to a load to form an island. Part of the
load is shed in the simulation and the transient responses of the generator are calculated.
A typical partial load rejection response is shown in Figure 3-16. For the partial load rejection
response test, TSAT gives the following in the result table:
• Amount of load rejected

• Mechanical power of the generator prior to load rejection
• Final mechanical power of the generator
• Final speed of the generator

TSAT User Manual
Figure 3-16: A typical load rejection response
3.5.5 No disturbance test
No disturbance test provides a convenient way to perform the sanity check of the data in a
simulation case. This analysis is especially useful when assembling a new base case. In this
analysis, a simulation is performed with no disturbance applied to the system. TSAT will list, in
the result table, the generators with the largest speed and angle deviations from the simulation. If
significant deviations are shown with It would be advisable to check the powerflow conditions
and the dynamic data of the generators which show significant speed deviations in the no
disturbance test before doing any further studies.
3.6 Result Files Available From TSAT
The previous subsections describe the computation options available in TSAT and the results they
give. The following is a summary of the different result files that can be obtained from TSAT.
Binary result file
This file is created if any of the five basic analyses is performed. This file has the name specified
in the Output Files command in the TSAT case file. An extension of .bin is always
appended to the binary result file. If no Output Files command exists in the TSAT case file,
the TSAT case file name (without the extension) is used as the name of the binary result file. For
example, if the TSAT case file is named as mycase.tsa, then the default binary result file name
will be mycase.bin.
For basecase analysis, simulation results in all scenarios and all contingencies processed are
stored in the binary result file of the case. When a case is re-run with the same output file
specification, TSAT has an option (see Section 4.3.1) to either start a new binary result file or
append results to the existing binary result file.

TSAT User Manual
For transaction analysis, only results from at most two iterations for each contingency or scenario
(depending on which limit search method is used) are stored (an “iteration” is defined here as a
complete simulation for one contingency at a specific power transfer level). Results at these
iterations are stored as separate "contingencies" in the binary result file. The two iterations are,
• The iteration at the last secure power transfer level. The contingency title written in the
binary result file has “Stable” inserted at the beginning of the contingency's title. The
results of this iteration are not available if the system is insecure at the base powerflow
transfer level.
• The iteration at the first insecure power transfer level. The contingency title written in the
binary result file has “Unstable” inserted at the beginning of the contingency's title. The
results of this iteration are not available if the system is secure at the maximum required
power transfer level.
For exciter step responses analysis, governor step responses analysis, no disturbance test,
simulation results stored in the binary result file are straightforward.
When running TSAT in the distributed computation mode, scenarios are processed individually in
each server and their results are sent to the client where results from all scenarios are
concatenated in the binary result file of the case.
A binary result file can be examined using the DSAToolsTM Output Analysis (DSAOA) module.
Refer to DSAToolsTM DSAOA Manual for details on using the DSAOA.
Computation result summary file(s)
An ASCII text result summary file is created when any of the five basic analyses is performed.
This file contains the summary of the computations performed, including security assessment
results or power transfer limit search results. These files are named using the following
convention:
xxxx_base.txt for basecase analysis result summary file

xxxx_tran.txt for transaction analysis result summary file
xxxx_excstep.txt for exciter step response test result summary file
xxxx_govstep.txt for governor step response test result summary file
xxxx_nodist.txt for no disturbance test result summary file
where xxxx is the output file name specified in the TSAT case.
The result summary files can also be created manually. Refer to Section 9.1 on using this feature.
Security violation report files
These files are created only if any specified security criteria are violated. They all have file
extension of *.rpt with special keywords in the file names:
xxxx_dmp.rpt damping violation report file

xxxx_tvlt.rpt transient voltage violation report file
xxxx_frq.rpt transient frequency violation report file

TSAT User Manual
xxxx_frt.rpt rate of change of frequency violation report file

xxxx_rly.rpt relay margin violation report file
xxxx_ppa.rpt peak-to-peak angle violation report file
xxxx_clt.rpt closing torque violation report file
where xxxx is the output file name specified in the TSAT case. Note that transient stability
violation report is already included in the *.txt file so it is not created again with a *.rpt file.
These violation report files can be opened and examined in DSAOA.
Message file
This file is created during a TSAT session. It is an ASCII text file and contains the messages from
computation engine. The message file can be opened by DSAOA where various message reports
can be created.
Progress file
This file is created during a TSAT session. It is an ASCII text file and contains the computation
progress reported from computation engine. The progress file can be opened by DSAOA where
various computation progress reports can be created.
Output log file
This file contains the names and locations of all output files created in a TSAT simulation
session. When using DSAOA to examine results from a simulation, it is recommended that this
file (*.olf) be opened.
Exported simulation result file
This refers to the simulation result file exported from a binary result file. It can be in two possible
formats:
• ASCII text format

• MS Excel format
This file is created in the DSAOA module. Refer to DSAToolsTM DSAOA Manual for details on
exporting the simulation results.
Saved plot file
This refers to the file containing the plot(s) created in the DSAOA module. It can be in three
possible formats:
• Enhanced Window Metafile (EMF) format

• Postscript format
• VB Script format for creating Excel charts
Refer to DSAToolsTM DSAOA Manual for details on creating this file.

TSAT User Manual
Using a scripting language (such as VBScript or JScript), plots can be created in Word or
PowerPoint format directly.
Powerflow dispatch files
After each transaction analysis scenario, up to two powerflow files will be created, one for the
last secure dispatch level and the other for the first insecure dispatch level (corresponding to the
two iterations stored in the binary result file described earlier). These powerflows are in either
PSF/PFB or PSS/E RAWD format (depending on the format of the base powerflow), named
using the output file name from the Output Files command (or the default output file name).
For example, if the output file name is mycase and the base powerflow is in PSF/PFB format,
then the powerflow dispatch files will be named mycase_xxxx_stable.psf and
mycase_xxxx_unstable.psf. Here, xxxx is a four-digit integer with leading zeros
corresponding to the scenario number of the transaction analysis scenario. Under the same
situations as described for transaction analysis binary result files, there may be only one of these
powerflow dispatch files created.
Note that the load models included in these powerflow dispatch files depend on a few factors.
The following are the details:
• If the base powerflow is in RAWD or PSF/PFB format, the load models in the powerflow
dispatch files (in either RAWD or PSF/PFB format) are all converted to constant MVA
model. Exception: when the base powerflow happens to be one of the powerflow dispatch
files (this happens when the base system condition is the last stable point or is an unstable
point during the transaction analysis), the load models in the base powerflow are preserved.
3.7 TSAT Terminology
Two concepts are adopted in organizing analysis tasks in TSAT and thus used often in this
manual: scenario and case. These terms are described in the following subsections. For details on
creating TSAT scenarios and cases, refer to Section 5.2 and also the Appendix A – TSAT Case
File Format.
3.7.1 Scenario
A TSAT scenario defines an analysis target such as basecase analysis and transaction analysis.
All required data files should be explicitly or implicitly specified for an analysis scenario.
The first scenario in a TSAT case is called the base scenario. All mandatory data sets required for
the scenario must be explicitly specified for the base scenario. Non-base scenarios are called
subsequent scenarios, for which specifications of data sets are optional; if a mandatory data set is
not specified, one in the base scenario will be used (some exceptions exist; see Section 10.1 for
details).
Under the normal circumstances, scenarios in a TSAT case can be used to specify different
computation objectives for a study, for example,
• Different powerflow conditions

TSAT User Manual
• Different contingency sets

• Different computation parameters
However, scenarios in a TSAT case are not necessarily set for the same system. In fact, they can
be used to define TSA for completely different systems, provided that all data sets are specified
appropriately for each scenario.
3.7.2 Case
A TSAT case is a collection of one or more scenarios and it is specified using a case file that
contains all necessary information (data files and parameters) to run TSAT.
During a TSAT computation session, only one case can be loaded and analyzed. To open a
different case while a case is already loaded, the existing case must be closed first.
A case can be created using the case wizard tool included in TSAT. The case wizard tool can also
be used to examine and modify any information contained in a case.
When running TSAT, all scenarios (except for the disabled ones) are processed sequentially and
the simulation results for each scenario are written into the binary result file specified for the
case. An optional text result file can also be created to include summaries of results from all
scenarios that are processed. Figure 3-17 shows the relationship of scenario, case, and various
data sets that are needed for TSAT.
Optional data:
• Criteria
• Dynamic
Mandatory data: representation
• Powerflow Scenario 1 • Transfer
• Dynamics (base scenario) • Generator capability
• Contingency • Generator coupling
• Monitor • Control mode
Scenario 2 • Load conversion
(subsequent scenario) • Generator netting
• Sequence network
• • Computation
Separate mandatory • parameters
data sets • • Powerflow solution
parameters
Scenario n
(subsequent scenario)
Separate optional
data sets
Figure 3-18: TSAT case structure
References
[1] P. Kundur, Power System Stability and Control, McGraw-Hill, 1994.

TSAT User Manual
[2] M. Pavella, D. Ernst, and D. Ruiz-Vega, Transient Stability of Power Systems – A Unified
Approach to Assessment and Control, Kluwer Academic Publishers, 2000.
[3] J.W. Pierre, D.J. Trudnowski, and M.K. Donnelly, “Initial Results in Electromechanical
Mode Identification from Ambient Data”, IEEE Trans. Vol. PWRS-12, No. 3, pp.1245-
1251, August 1997.

TSAT User Manual
4 Understanding the TSAT Main Window
This section describes the TSAT main window and the basic functions available.
4.1 Starting TSAT
The TSAT program is started by double-clicking the TSAT executable, tsat.exe, or the TSAT
program icon on the desktop (you need to place the icon first on the desktop using the standard
Windows Paste Shortcut function). If the TSAT program is associated with the file extension type
.tsa, double-clicking any TSAT case file (with extension name .tsa) will start TSAT and then
subsequently open the case.
When the program is started without a TSAT case opened, the TSAT main window is empty, and
only the following functions are available:
• Create a new TSAT case. This is done by selecting the File | New function in the menu.
The case wizard is launched to help create a new TSAT case. Refer to Section 5 for
details on creating and modifying TSAT cases.
• Open an existing TSAT case. This is done by selecting the File | Open function in the
menu. Refer to Section 4.2 for details on opening a TSAT case.
• Open an existing TSAT case archive. This is done by selecting the File | Open Archive .
. . function in the menu. Refer to Section 4.2 for details on opening a TSAT case archive.
• Open an existing TSAT snapshot. This is done by selecting the File | Open Snapshot . . .
function in the menu. Refer to Section 4.2 for details on opening a TSAT snapshot.
• Set up engine servers to enable distributed computations. This is done by selecting the
View | Servers function in the menu. Refer to Section 9.5 for details on distributing
TSAT analyses.
• Start the DSAOA module to plot results from previous TSAT simulations. This is done
by selecting the View | Results function in the menu. Refer to DSAToolsTM DSAOA
Manual for details on analyzing the results using the DSAOA module.
• Enable the TSAT batch mode. This is done by selecting the Auto | Enable function in the
menu. Refer to Section 9.4 for details on running TSAT in batch mode using the Case
Scheduler.
• Configure the TSAT on-line mode. This is done by selecting the Auto | Configure
function in the menu. Refer to the separate document, TSAT Auto Features, for details on
how to use this function.
• View TSAT manuals. This is done by selecting the Help and one of the manuals listed in
the menu. Refer to Section 9.2 for details on viewing TSAT manuals from the program.

TSAT User Manual
4.2 Opening a TSAT Case
There are two options to open a TSAT case:
Open a TSAT case file
This is very straightforward. Select the File | Open function in the menu and this launches a file
selection dialog box from which a TSAT case can be chosen and opened.
Open a TSAT case archive
If you have archived a TSAT case (see Section 5.5 on how to do this), or if you have received a
TSAT case archive, you can open the archive (in *.zip format) directly without unzipping it. This
provides a quick way to look at an archived case. When you open a TSAT case archive by
selecting the File | Open Archive . . . function in the menu, TSAT does the following:
• A subfolder named after the TSAT case archive is created under the folder where the
TSAT case archive is located (if a subfolder with the TSAT case archive name exists
already, a text string of the form _01, _02, etc., will be appended at the end of the
subfolder name).
• All files in the TSAT case archive are unzipped (except for the result files) and copied to
the subfolder.
• The TSAT case file is then opened in TSAT.
• If you change any data in the case, it will be saved, by default, as individual data files to
the same subfolder (unless you specify otherwise). Note that the original TSAT case
archive is not updated for the changes.
• When you archive the case again, the archive will also be saved in the subfolder.
• When you finish working on the case, TSAT does not delete the subfolder or any data in
it. Therefore, be cautious when opening directly a TSAT case archive, since it basically
copies the entire case on the hard disk.
Open a TSAT snapshot
If you have saved a TSAT snapshot (see Section 9.6 for details of TSAT snapshot), to open the
snapshot is straightforward. Select the File | Open Snapshot… function in the menu and this
launches a file selection dialog box from which a TSAT snapshot can be chosen and opened.
Remarks
Note that if a TSAT case has already been opened in the TSAT main window, it must be closed
before another TSAT case can be opened. In other words, there can be only one TSAT case
opened in the TSAT main window.
When opening a case file, critical case file syntaxes and contents are checked to ensure that the
case is valid. If any problem is found during the case file reading, the case will be rejected with

TSAT User Manual
an error message. Non-critical errors found in a case file are displayed in a message window after
the case is opened.
4.3 Description of the TSAT Main Window
Once a TSAT case is opened, the TSAT main window is shown in Figure 4-1. This window has
the following components:
• Main menu and tool bar

• Scenario table
• Computation progress/result summary pages
• Status bar
Main menu Tool bar

menu
Scenario table
menu
Computation
progress/result
summary pages
Status bar
Figure 4-1: TSAT main window
4.3.1 Main Menu and Tool Bar
The TSAT main menu contains the following functions (the commonly used ones have function
buttons in the tool bar). Note that, unless otherwise specified, the menu functions apply
exclusively to the active case loaded in TSAT already (in other words, they would not be
available if no TSAT case is opened in the main window).

TSAT User Manual
File Menu
• New . The case wizard is launched to help create a new TSAT case. Refer to Section
5.2 for details on creating a new TSAT case. This function is available only when no
TSAT case is opened in the main window.
• Open . This function opens a TSAT case and prepares it for computation. Refer to
Section 4.2 for details on opening a TSAT case. Once a TSAT case is opened, it becomes
the active case in the TSAT main window. This function is available only when no TSAT
case is opened in the main window.
• Open Archive … . This function opens a TSAT case archive and prepares it for
computation. Refer to Section 4.2 for details on opening a TSAT case archive. Once a
TSAT case archive is opened, it becomes the active case in the TSAT main window. This
function is available only when no TSAT case is opened in the main window.
• Open Snapshot … This function opens a TSAT snapshot and prepares it for
computation. Refer to Section 9.6 for details on TSAT snapshot. This function is
available only when no TSAT case is opened in the main window.
• Close. This function closes the active TSAT case, but does not exit the TSAT program.
After closing the active TSAT case, a new case can be opened. You will be prompted to
save the case if changes have been made to the case after the last Save or Save As
function is performed.
• Save . This function saves all customized computation parameters and data file
information of the active TSAT case (including all scenarios it contains) into its case file.
Current computation parameter settings will be saved relative to the default parameter
settings (i.e., only those parameters with values different from the default settings are
saved; refer to Section 10.2.3 for a description on the default parameter settings). All
filenames will include absolute paths.
• Save As. This function saves the active TSAT case to a new case file. A file specification
dialog box appears for you to specify or choose the new case file. By default, a TSAT
case file has a file extension name .tsa, but you can use any other extension names. See
notes above for Save function.
• Archive . This function allows you to archives the active TSAT case. All data files
and the parameter settings used in the case are preserved in a compressed file. Refer to
Section 5.5 for details on using this feature.
• Reports. This function allows you to create the computation result summary file
(including basecase analysis results, transaction analysis results, exciter step response test
results, governor step response test results, and no disturbance test results). Refer to
Section 9.1 for details on using this function.

TSAT User Manual
• Case Wizard. This function launches the case wizard tool that allows you to create,
examine, and modify the computation parameters and data file information of individual
scenarios. Refer to Section 5 for details on using the case wizard tool.
• Compare Scenarios. You can use this function to compare multiple scenarios in the
TSAT case opened. Refer to Section 5.4 on how to use this function.
• Synchronize Parameters. You can use this function to synchronize computation

parameters for all scenarios in the TSAT case opened. Refer to Section 5.2.1.9 on how to
use this function.
• Edit Files. You may edit the data files specified in the active TSAT case (except for
powerflow and dynamic data files) within TSAT with the text editor you specify. You
need to configure the text editor (using the Options | Configure Text Editor function)
before using this feature. Refer to Section 9.7 for details on using this feature. Remark: it
is highly recommended that you edit all data using case wizard.
• Exit. This function exits the TSAT program. You will be prompted to save the case if
changes have been made to the case after the last Save or Save As function is performed.
Run Menu
• Basecase Analysis . This function submits the TSAT case to the computation engine
for basecase analysis. The computation progress and result summaries are displayed on
the TSAT main window as they become available. Refer to Section 3.5 for an overview
of basecase analysis and Section 6 for details on performing basecase analysis.
• Transaction Analysis . This function submits the TSAT case to the computation
engine for transaction analysis. The computation progress and results summaries are
displayed on the TSAT main window as they become available. Refer to Section 3.5 for
an overview of transaction analysis and Section 7 for details on performing transaction
analysis.
• Exciter Step Response Test . This function submits the TSAT case to the
computation engine for the exciter step response test. The computation progress and
results summaries are displayed on the TSAT main window as they become available.
Refer to Section 3.5 for an overview of the exciter step response test and Section 8.1 for
details on performing the exciter step response test.
• Governor Step Response Test . This function submits the TSAT case to the
computation engine for the governor step response test. The computation progress and
results summaries are displayed on the TSAT main window as they become available.
Refer to Section 3.5 for an overview of the governor step response test and Section 8.2
for details on performing the governor step response test.
• No Disturbance Test. This function submits the TSAT case to the computation engine
for the no disturbance test. The computation progress and results summaries are
displayed on the TSAT main window as they become available. Refer to Section 3.5 for

TSAT User Manual
an overview of the no disturbance test and Section 8.3 for details on performing the no
disturbance test.
• Pause . This function pauses an analysis option (basecase analysis, transaction

analysis, etc.). Computation may be resumed by selecting Run | Continue function in the
menu. For basecase analysis, while a simulation is paused, you can skip the contingency
if desired. Refer to Section 6.2 for more details.
• Continue . This function resumes a paused analysis option (basecase analysis or

transaction analysis).
• Stop . This function stops an analysis option (basecase analysis or transaction

analysis). Note that after selecting this function, there may be a noticeable delay for large
system models before the analysis is actually stopped. It is not recommended to attempt
to perform other TSAT functions or to attempt to exit the program during this delay as it
may put the program in an unstable state. Delays are most lengthy during the model
initialization.
View Menu
• Toolbar. This enables/disables the tool bar. This function is always available in the
TSAT main window, no matter if a TSAT case is opened.
• Status Bar. This enables/disables the status bar. This function is always available in the
• Servers . This opens up the server dialog for you to set up the servers available for
distributing the TSAT analyses. Refer to Section 9.5 for details on using this feature.
• Case Details . This opens up the case details dialog box displaying the information of
the active TSAT case. Refer to Section 5.6 for details on the information available in this
dialog box.
• Results . This function launches the DSAOA module. The DSAOA module can be
used to plot, view, print, and export the simulation data stored in TSAT binary result
files. The module can also be used to view, customize, and export the messages from
TSAT during an analysis. Refer to DSAToolsTM DSAOA Manual for details on using the
DSAOA module. This function is always available in the TSAT main window, no matter
if a TSAT case is opened.
• Messages . This function opens up the TSAT messages dialog box. This dialog box
contains the messages from TSAT during an analysis. Refer to Section 9.3 for details on
using the messages dialog box.
• Basecase Analysis Details. This function opens up the basecase analysis details dialog
box. This dialog box shows additional computational results from the basecase analysis.
Refer to Section 6.3 for details on the contents of this dialog box.

TSAT User Manual
• Transaction Analysis Details. This function opens up the transaction analysis details
dialog box. This dialog box shows additional computational results from the transaction
analysis. Refer to Section 7.3 for details on the contents of this dialog box.
• Powerflow Data . This function launches the Powerflow & Short-circuit Analysis
Tool (PSAT) for examining powerflow data. Note that when starting PSAT from the
View menu, you can view and edit powerflow data from any scenario or any powerflow
cases on your computer. The changes you make to the powerflow data, however, will not
be passed back to the active case. To change the powerflow data in the active case, you
need to start PSAT in the case wizard. Refer to Section 5.2.2 for details.
• Dynamic Data . This function launches the dynamic data editing module for
examining dynamic data. Note that when starting the dynamic data editing module from
the View menu, you can only view dynamic models and data but not edit them. If you
want to edit data, you need to do so in the case wizard. Refer to Section 5.2.3 for details.
Options Menu
• Computations. This function opens up the computation parameter dialog box. Since
each scenario can have an independent set of parameters, a scenario must be selected in
the scenario table to enable this function if the case contains multiple scenarios.
Computation parameters associated with the selected scenario can be viewed and
modified in this dialog box. Refer to Section 5.2.1 for details on using the computation
parameter dialog box.
• Auto. This function opens up the on-line mode options dialog box in which the analysis
options required in an on-line processing loop are specified. This function is available
only in the on-line version of TSAT.
• Invert Run Status. This function toggles the action status (Run or Don’t Run) for all
scenarios. Once an analysis has started, this option becomes inactive. But it is still
possible to change the the action status for those scenarios that have not been run, by
manually checking the action box of the scenario in the scenario table
• Configure Text Editor. This function allows you to configure a text editor for editing
data files included in the active case. Refer to Section 9.7 for details on using this feature.
• Simulation Result File. This function allows you to specify whether or not the binary
result file from a previous run of the case (assuming the same file name is still used)
should be deleted before starting the simulation. If the previous binary result file is to be
kept, the new results will be appended to this file. This allows the flexibility to run
different scenarios in a case in several independent program executions and to store the
results in the same binary result file.
Auto
• Enable/Disable. This function enables/disables the off-line batch mode and on-line mode
for TSAT. Once these modes are enabled, all controls in the TSAT main window are
disabled (except for disabling these modes) and TSAT execution is directed by either the

TSAT User Manual
Case Scheduler for the off-line batch mode or the EMS for the on-line mode. Section 9.4
describes the TSAT off-line batch mode operation.
• Configure. This function allows the customization of the TSAT on-line mode. Refer to
the separate document, TSAT Auto Features, for details on how to use this function.
Help Menu
• Open User Manual. This opens the TSAT Users Manual. Adobe Acrobat Reader 4.0
or higher is required in order to view this manual. This function is always available in the
• Open Model Manual. This opens the TSAT Model Manual. Adobe Acrobat Reader
4.0 or higher is required in order to view this manual. This function is always available in
the TSAT main window, no matter if a TSAT case is opened.
• Open DSAOA Manual. This opens the DSATools Output Analysis (DSAOA) Manual.
Adobe Acrobat Reader 4.0 or higher is required in order to view this manual. This
function is always available in the TSAT main window, no matter if a TSAT case is
opened.
• Open UDM Manual. This opens the DSATools User-Defined Model (UDM) Manual.
Adobe Acrobat Reader 4.0 or higher is required in order to view this manual. This
function is always available in the TSAT main window, no matter if a TSAT case is
opened.
• About TSAT. This function displays information related to TSAT including the
copyright declaration and TSAT version numbers. There is also a link to Powertech’s
Web site. This function is always available in the TSAT main window, no matter if a
TSAT case is opened.
4.3.2 Scenario Table
Figure 4-2 shows an example of the scenario table. Each row of the scenario table contains one
scenario in the active TSAT case. Information for a scenario is displayed in a number of fields
arranged in four groups, as described below.
Click on the cell to toggle

the Action status
Figure 4-2: Scenario table

Scenario
Two fields are displayed in this group:

TSAT User Manual
• No. (#). This is the scenario number counted by the sequence in which scenarios appear
in the TSAT case file. Therefore, scenario #1 is the base scenario and the rest the
subsequent scenarios. Note that scenarios defined in a TSAT case file are not explicitly
numbered and the numbers in this field are added by the program for visual
identification.
• ID. This is the scenario title entered in the scenario description data section of the TSAT
case file.
Basecase Analysis
There is only one field in this group:
• Security Status. This field displays the security status of the scenario after the basecase
analysis is performed for the scenario. The status can be either secure (in black) or
insecure (in red). An insecure status indicates that one or more security criterion for the
scenario is violated for at least one contingency associated with the scenario. If a
basecase analysis has not been performed for a scenario, this field is left blank.
Transaction Analysis
There are four fields in this group. These fields are populated only if the transaction data is
provided in a scenario.
• Name. This field displays the transaction name as entered on the SCRNAM record in the
dispatch description file. The format of this file is described in the TSAT Model Manual.
• Base. This field displays the value of the dependent variable in the transaction definition
in the base powerflow (refer to the TSAT Model Manual for a definition of the dependent
variable). Note that it is not displayed until the first iteration of the transaction analysis
has been completed.
• Increase. This field displays the desired increase of the independent variable in the
transaction definition (refer to the TSAT Model Manual for a definition of the
independent variable). This value is taken from the third argument on the SRXAXS record
in the dispatch description file.
• Limit. This field displays the independent variable increase limit (relative to the base
value) below which no security indices will be violated for all contingencies considered.
This corresponds to the power transfer limit and is determined at the end of the
transaction analysis for the scenario.
Action
There is only one field in this group. This field allows you to set the execution option for the
scenario. The content of this field toggles between "Run" and "Don't Run". If a "Don't Run" is
shown, the scenario will be skipped for the basecase analysis or transaction analysis. You may
use the Options | Invert Run Status function in the menu to invert the action status of all
scenarios that have not been run.

TSAT User Manual
4.3.3 Computation Progress/Result Summary Pages
There are two pages, selectable by the page tab, in this area. They show the computation progress
and result summary respectively. The contents on these two pages change for different analysis
option (basecase analysis, transaction analysis, exciter step response test, governor step response
test, or no disturbance test). Figure 4-3 and Figure 4-4 show typical computation progress and
result summary pages for basecase analysis using full integration simulation and the detailed
description of these pages are given in the appropriate sections in this manual. The following
describes the common features of these two pages.
Click on the tab to

select scenario
Copy, save, or print

Green checkmarks indicate simulation progress
enabled security criteria
Use the spinner to

navigate the contingencies
Figure 4-3: Computation progress page example
Click on the tab to

select scenario
Double-click on a row to open
analysis details dialog box
Double-click on a
field header to sort
Figure 4-4: Result summary page example


TSAT User Manual
Computation Progress Page
This page is divided into two parts:
• Left part. This side of the page consists of a number of bars to show the progress by
which scenarios are processed. Each bar represents one scenario. An unfilled bar
indicates that the corresponding scenario has not been processed and a fully filled bar (in
blue) denotes a completed scenario. During the computation, the scenario being
processed is easily visible and the percentage of completed computation for the scenario
is shown on the bar. When the computations are distributed on multiple servers, the
computation progress on each server is indicated by the respective progress bar.
Above the progress bar are boxes with one-letter labels to indicate which security criteria
are enabled for the scenario. A green check appears in the box when the corresponding
security criteria is enabled. The one-letter labels correspond to the following security
criteria:
A – transient stability
D – dampinp
V – transient voltage
F – transient frequency
F& - rate of change of frequency
R – relay margin
Note that the peak-to-peak angle criteria and closing torque criteria are considered as part
of transient stability criteria and therefore is covered under A.
If a no disturbance test is being performed, the left part of the computation progress page
lists ten generators which have largest speed deviations during the simulation.
• Right part. This side contains two plots for each scenario, showing the progress of
simulations for typical quantities or progress of a power transfer limit search process.
Spinners are included to allow navigation among all available results. The three buttons
at the lower right corner can be used to copy, save, or print the simulation progress plot
for a specific scenario and contingency.
Result Summary Page
This page shows tabular result summary for all scenarios for the specified analysis option.
• Results for different scenarios are separated using tabs.
• Each row in the table contains the results for one contingency, with the contingency title
shown in the last field.
• When performing the exciter step response test or the governor step response test, each
row in the table contains the main characteristics of the step responses of one generating
unit.

TSAT User Manual
• When performing the no disturbance test, the table lists ten generators with the largest
speed deviations during the simulation.
• The contents of the table can be sorted on any field by double-clicking on the field
header.
• Double-clicking on any contingency (i.e., anywhere on the corresponding row) which has
been processed will bring up an analysis details dialog box.
• Similarly to the Computation Progress Page, the three buttons at the upper left corner can
be used to copy, save, or print the result summary for a specific scenario.
4.3.4 Status Bar
The status bar shows the following program status:
• Time information: day, date, year, and time
• Operation mode indicator: on-line mode or study mode (off-line mode)
• Engine status indicator: when the computation engine is processing a scenario, a moving
green bar appears.

TSAT User Manual
5 Creating and Modifying a TSAT Case
This section describes the methods for creating, modifying, and examining TSAT cases.
5.1 Data Requirements
Before creating a TSAT case, you should have the following data files ready in the specified
format(s):
• Powerflow data. The powerflow data can be in PSF/PFB format, PSS/E RAWD format,
PSLF EPC format, or BPA format.
• Dynamic data. The dynamic data can be in DSATools, PSS/E format, PSLF format, or
BPA format. Note that it is possible to create the entire set of dynamic data within TSAT
using Case Wizard. This however could take long time even for small systems.
The PSF/PFB powerflow format is described in PSAT user manual and DSATools dynamic data
format is described in the TSAT Model Manual. Data of other format(s) are described in user
manuals of the respective programs.
Two additional data sets are mandatory to run simulations (they can be created in TSAT):
• Contingency data. This is used to specify contingencies to be applied in the simulations.

This data must be in TSAT format.
• Monitor data. This is used to specify the quantities to be monitored from simulations.
This data must be in TSAT format.
Optionally, you may also use the following data for advanced modelling and solution features of
TSAT:
• Criteria data. This is used to specify customized security criteria. This data must be in
TSAT format.
• Dynamic representation data. This is used to customize the dynamic models for the case.
This data must be in TSAT (or SSAT) format.
• Sequence network data. This is used to compute sequence impedances when unbalanced
fault is to be simulated and the fault impedances are not provided. This data must be in
PTI PSS/E format, unless the dynamic data is in BPA format in which case the BPA
sequence network data entered in the dynamic data file is used for unbalanced fault
simulations.
• Powerflow solution parameter data. This is used to control the powerflow solution at the
pre-simulation and during the transaction. This data must be in TSAT format.
• Load conversion data. If load conversion data is available in the PSS/E IDEV format, it
can be included in a TSAT case to specify the load models for simulations.

TSAT User Manual
• Generation netting data. If generator netting data is available in the PSS/E IDEV format,
it can be included in a TSAT case to specify the generation netting in simulations.
If transaction analysis is to be performed, the following additional data is required:
• Transaction data. This further includes transfer file, parameter file, interface and circuit
file, generator capability file, and generator coupling file. Refer to Section 10.2.10 for
details.
All of the above data is described in the TSAT Model Manual (except for non-TSAT format).
5.2 Creating a TSAT Case
As mentioned earlier, a TSAT case is described by a TSAT case file which is an ASCII text file.
Section 10 (Appendix A) contains the full description of the TSAT case file format. Therefore, a
TSAT case file can always be created or modified by using any text editor.
TSAT also includes a tool, Case Wizard, to help you create and modify a TSAT case and most of
the data files required. This section describes the method to create a TSAT case. Using the case
wizard to modify a TSAT case is described in the next section.
Principle
The case wizard can be launched to create a new TSAT case in one of two possible situations:
• If there is no TSAT case opened in the TSAT main window (i.e., the TSAT main window
is empty), select the File | New function in the main menu. The case wizard dialog box
shown in Figure 5-1 appears. Note that in this situation, the case wizard is automatically
configured for creation of a new TSAT case (the functions for modifying a TSAT case
are disabled). When the new TSAT case is created and saved, it is automatically opened
in the TSAT main window.
• If a TSAT case is already opened in the TSAT main window, select the File | Case
Wizard function in the main menu. This launches the case wizard which is configured,
by default, for modifying the active TSAT case (see Figure 5-2). If you want to create a
new TSAT case, simply click on the “Create A New TSAT Case” radio button. When the
new TSAT case is created and saved, it is not opened in the TSAT main window (the
original active TSAT case is still opened).

TSAT User Manual
Figure 5-1: Creating a new TSAT case from an empty TSAT main window
Click on this radio

button to create a
new TSAT case
Figure 5-2: Creating a new TSAT case when an active TSAT case is already opened
From the dialog in Figure 5-1 (or Figure 5-2), clicking on the Next button will start creating the
case. The case wizard will open up a series of dialogs for you to enter different types of
information required by TSAT. In each dialog box, the required information is grouped in two
areas:
• Mandatory data area. You must provide all required information in the mandatory data
area, or else the Next button will be disabled so you will not be able to proceed. If there
is no mandatory data area in a dialog, the information required in the dialog is optional to
TSAT.
• Optional data area. The information in this area is optional. If not provided, it is either
not used or default is available for it.

TSAT User Manual
Each dialog box has a Back button, which allows you to go back to any previous dialogs to
modify the information you have entered, and a Next button (enabled when all information in the
mandatory data area is provided), which allows you to go ahead to the next dialog. If you want to
abort the case wizard, simply click on the Cancel button at any time.
Note that, when the case wizard is used to create a new TSAT case, it actually only creates the
base scenario. Once the base scenario is created, subsequent scenarios can be added to it by using
the case wizard again. This is described in Section 5.3.
Entering powerflow data
Figure 5-3 shows the dialog box for entering powerflow information. The powerflow data is
mandatory so it must be provided before the Next button is enabled to proceed to the next dialog.
After a powerflow data is specified, you may examine or edit it using the Edit In PSAT button
(details in Section 5.2.2).
Specify powerflow
format
Figure 5-3: Entering powerflow data in the case wizard
In the optional data area, you may provide the following data in this dialog box:
• A powerflow solution parameter data file. This is used to control the powerflow solution
at the pre-simulation. The format of this data is described in the TSAT Model Manual. If
this file is not provided, the powerflow will be solved with the default parameters shown
in the TSAT Model Manual. You may perform the following additional tasks associated
with the powerflow solution parameter data:
Create a new powerflow solution parameter data file by pressing the Create button.

TSAT User Manual
Modify the powerflow solution parameter data file you specify by pressing the Edit
button.
• The flag for the solution of powerflow at the pre-simulation. If this option is checked, the
base powerflow is solved before proceeding to the simulation. Note that, if the
contingency specification contains pre-simulation events (such as opening a line before
the simulation starts, referring to the switching command At Time in the TSAT Model
Manual), the powerflow is always solved after applying the pre-fault events, no matter
whether or not this option is checked.
• If the powerflow is provided in BPA format, you may specify a solution data file (*.pfo)
that is created by the BPA program. TSAT uses the powerflow solution included in this
data file as the starting point when solving the powerflow. Otherwise, a flat start is used.
Entering dynamics data
Figure 5-4 shows the dialog box for entering dynamic data. You need to specify the files that
contain the dynamics data and the default data format. It is possible to specify dynamic data in
multiple data files. You must also make sure that component identification method (Name
Option) is set correctly. After dynamic data files are selected, you can edit the dynamic models
and their parameters by pressing the Edit button. This is described in Section 5.2.3.
Once the dynamic data files are specified, the Next button is enabled to proceed to the next
dialog.
Figure 5-4: Entering dynamics data in the case wizard
Entering monitor data

TSAT User Manual
Figure 5-5 shows the dialog box for entering monitor data. You have two options to enter the
monitor data:
• Select existing monitor data files which can be edited by pressing the Edit button.
• Create new monitor data by pressing the Create button.
The monitor data creation and editing functions are described in Section 5.2.4.
Figure 5-5: Entering monitor data in the case wizard
It is possible to specify monitor data in multiple data files. You must also make sure that
component identification method (Name Option) is set correctly. Once the monitor data files are
specified, the Next button is enabled to proceed to the next dialog.
In the optional data area, a reference generator can be specified from the monitor data. This
reference generator is used to plot the relative generator rotor angles on the computation progress
page of the TSAT main window, and it is also stored in the binary result file during simulations
so that relative generator rotor angles can be plotted in the DSAOA module too.
To specify a reference generator, either type the generator bus number and ID in the text boxes
provided, or select a generator in the system by pressing the Search button.
If the reference generator is not specified, the generator with the largest MVA rating in the
system will be selected as the default reference.
Entering contingency data
Figure 5-6 shows the dialog box for entering contingency data. You have two options to enter the
contingency data:

TSAT User Manual
• Select existing contingency data files which can be edited by pressing the Edit button.
• Create new contingency data by pressing the Create button.
The contingency data creation and editing functions are described in Section 5.2.5.
It is possible to specify contingency data in multiple data files. You must also make sure that
component identification method (Name Option) is set correctly. Once the contingency data files
are specified, the Next button is enabled to proceed to the next dialog.
In the optional data area, you can specify two additional data files:
• A Must-Run contingency file

• A Don’t-Run contingency file
The use of the Must-Run and Don’t-Run contingency files is described below.
Figure 5-6: Entering contingency data in the case wizard
If you do not have Must-Run and Don’t-Run contingency files, they can be created from the
contingency files specified. To do this, press the appropriate Create button in Figure 5-6 and the
dialog box shown in Figure 5-7 appears (for creating the Must-Run contingency file). In this
dialog, the “Available List Of Contingencies” list box contains the contingency titles obtained
from all contingencies in the specified contingency files (excluding those that have already been
selected as Must-Run contingencies). Any contingencies in this list can be selected and then
added to the “Must-Run List” list box by pressing the −> button. Similarly, any contingencies in
the “Must-Run List” list box can be selected and then removed from the list by pressing the <−
button. When all desired Must-Run contingencies are selected, specify a Must-Run contingency

TSAT User Manual
file name and press the OK button to save the data. The similar process can be applied to create a
Don’t-Run contingency file.
If you already have Must-Run and Don’t-Run contingency files, they can be modified using an
approach similar to that described above.
Must-Run and Don’t-Run contingency files simply contain the titles of the respective
contingencies. If a contingency appears in both Must-Run and Don’t-Run files, it is ignored from
both lists, i.e., it will be submitted to the simulation engine.
There is another way to specify “don’t run” contingencies, by using the Application command in
a contingency. Refer to the TSAT Model Manual for details on how to use this command.
Figure 5-7: Creating Must-Run contingency file
Entering criteria data
Figure 5-8 shows the dialog box for entering criteria data. All information required in this dialog
is optional for a TSAT case. You have two options to enter the criterisa data:
• Select an existing criteria data file which can be edited by pressing the Edit button.
• Create new criteria data by pressing the Create button.
You must also make sure that component identification method (Name Option) is set correctly.

TSAT User Manual
Figure 5-8: Entering criteria data in the case wizard
Entering dynamic representation data
Figure 5-9 shows the dialog box for entering dynamic representation data. All information
required in this dialog is optional for a TSAT case. You have two options to enter the dynamic
representation data:
• Select an existing dynamic representation data file which can be edited by pressing the
Edit button.
• Create new dynamic representation data by pressing the Create button.
Figure 5-9: Entering dynamic representation data in the case wizard

TSAT User Manual
The dynamic representation data creation and editing functions are described in Section 5.2.7.
In addition to dynamic representation data in TSAT native format, you can also provide two sets
of data in PSS/E IDEV format to
• Convert the load model (with PSS/E CONL command)

• Net generators (with PSS/E GNET command)
Entering transaction data
Figure 5-10 shows the dialog box for entering transaction data. All information in this dialog is
optional for a TSAT case; however if you intend to perform transaction analysis, the Transfer File
must be provided. The Parameter File and Interface And Circuit File are used to customize
transaction analysis. Details of these files are described in the TSAT Model Manual.
You have two options to enter the associated data files for transaction analysis:
• Select an existing data file which can be edited by pressing the Edit button.
• Create new data by pressing the Create button.
The data creation and editing functions are described in Section 5.2.8.
Figure 5-10: Entering transaction data in the case wizard

TSAT User Manual
Entering sequence network data
Figure 5-11 shows the dialog box for entering sequence network data. All information required in
this dialog is optional for a TSAT case.
Figure 5-11: Entering sequence network data in the case wizard
Entering scenario description data
Figure 5-12 shows the dialog box for entering scenario description data. All information required
in this dialog is optional for a TSAT case. Note that a default scenario description (“Base
Scenario”) is provided.
It is recommended to always enter a meaningful scenario description, since it is used in TSAT to

identify the scenario.

TSAT User Manual
Figure 5-12: Entering scenario description data in the case wizard
Checking and saving the new TSAT case
Once all data dialogs have been completed, a final checking dialog box shown in Figure 5-13
appears. This dialog shows all types of data (mandatory or optional) required by TSAT and the
types of data actually provided during the case creation process. If you want to add or modify a
specific type of data, simply click the data item in the tree and work on the dialog shown in the
left half of the window. After the case is finalized, click on the Save button to save the case.
Note that the computation parameter dialog box was not included in the series of dialog boxes
during the new case creation. This is to simplify the initial case setup process, since the
computation parameter dialog box includes some of the most important and frequently changed
information required to run a TSAT case. The method to examine and modify computation
parameters is separately described in Section 5.2.1. Therefore, when a new case is created, it is
always assumed that default computation parameters are used.

TSAT User Manual
This area displays the

data editing dialogs for
the data items selected.
Click on any data item

to examine and edit
the associated data
Figure 5-13: Checking information specified for a new TSAT case

TSAT User Manual
5.2.1 Specifying Computation Parameters
The computation parameters of a scenario determine many computational features available in

TSAT. As described in Section 10, the determination of computation parameters obeys the
following rules:
(1) If a computation parameter is not specified in the TSAT case file for a scenario, the default
value is used.
(2) TSAT comes with a set of pre-determined default values for all parameters (called Original
Settings). You can, however, re-set these default values after TSAT is installed to fit your
specific needs (for instance, to change the default system frequency from 60 Hz to 50 Hz).
(3) The values of computation parameters of a subsequent scenario are not inherited from those
of the base scenario; they are individually determined.
The computation parameters of TSAT are organized in six groups:
(1) Parameters for security assessment

(2) Parameters for simulation control
(3) Parameters for modelling
(4) Parameters for transaction analysis
(5) Parameters for early termination of simulations
(6) Parameters for sequence network formulation
The descriptions and features of all the computation parameters are described in the following
subsections.
5.2.1.1 Accessing Computation Parameter Dialogs
The computation parameter dialogs can be accessed from three functions in TSAT:
(1) From the case wizard. This is done using the approach described in Section 5.3. When a
scenario is selected from the case wizard and the scenario editing window shown in Figure
5-32 is opened up, clicking on the Parameters item in the tree launches the computation
parameter dialog box for the scenario.
Figure 5-14 shows an example of the computation parameter dialog.
(2) From the TSAT main window. In this approach, select a scenario from the scenario table and
then select the Options | Computations function in the main menu. A computation
parameter dialog box similar to the right half of the window in Figure 5-14 will be opened up.

TSAT User Manual
Figure 5-14: An example of the computation parameter dialog
5.2.1.2 General Features
As mentioned earlier, the dialog for each group of computation parameters applies only to the
scenario selected. When a parameter is modified, the change does not apply to any other
scenarios. Therefore, if a change is to be made for all scenarios in a TSAT case, it has to be
repeated for all scenarios.
There are several buttons and a check box at the bottom of the Computation Parameter dialog,
which apply to all groups of the computation parameters. The use of these functions is described
below.
Save As Default
If you need to change the default values for some parameters (for instance default system
frequency), you can do so by following these steps:
(1) Change the parameters to the values you want
(2) Select the Save As Default check box
(3) Press the OK button
TSAT will then save or update the TSAT initialization file located in C:\TSA.INI. This file is
read every time TSAT is started to provide the default values to computation parameters. If this
file is not found in your computer system, the original setting in TSAT will be used for all
parameters.

TSAT User Manual
Note that after you change the default value of a parameter, that default value will be used for all
other scenarios in the active TSAT case and also for every other TSAT case. This is important to
realize so you can avoid any unexpected results. In general, it is not recommended that the
defaults be changed very often. They should normally be changed after the initial program
installation to set critical parameters.
Restore Defaults
Pressing this button will discard the existing values for all parameters and restore the default
values for them. This is a way to examine the default setting.
Original Settings
Pressing this button will discard the existing values for all parameters and restore the original
values from the TSAT distribution package.
Cancel
Pressing this button will discard any changes that you have made in the parameter dialog and
close the dialog.
OK
Pressing this button will accept the changes that you have made in the parameter dialog and close
the dialog. Note that the changes are effective only for the selected scenario in the active TSAT
case. You should always save the case after any changes made to a scenario to keep the changes
permanently.
5.2.1.3 Parameters for Security Assessment
Figure 5-15 shows the dialog to specify the basic security assessment parameters.
Note: starting from TSAT version 11, most of the security criteria must be specified in the criteria
data file (described in Section 5.2.6). Only the following two basic security critera can be
specified in Figure 5-15 (this is due to the fact that these are available only as system-wide critera
and therefore cannot be included in the criteria data):
• Transient stability criteria

• CCT criteria
The definitions of these criteria are explained in Section 3. The following are the remarks on
some implied aspects when specifying the parameters.
• Inclusion of transient stability index is mandatory. You can use a single stability index
(SM or AM) or CCT.
• You can assign a stability margin threshold associated with the stability index for security
check. For example, if you set the stability margin threshold at 10%, any contingencies
that have a security index less than 10% will be declared as insecure contingencies.

TSAT User Manual
• CCT is not applicable to transaction analysis. Therefore, if this is selected, it is ignored in

transaction analysis (i.e., the stability margin index is used to determine the transient
stability of the system).
• When CCT is selected, the fault clearance time of all contingencies is varied until the
critical clearance time is found, subject to the minimum and maximum clearance time
search range and the search threshold specified in the dialog. The contingency is
considered as secure if its CCT is larger than the CCT security criterion and vice versa.
Fault clearance time is defined as the time from the first fault application in the
contingency (a fault may be three-phase, one-phase-to-ground, or two-phase-to-ground at
a bus or on a line) to the first fault clearance. Therefore, if a contingency contains no fault
(for instance only a circuit tripping), CCT is not applicable and no stability index will be
reported from the computation engine.
Figure 5-15: Parameters for transient stability assessment
5.2.1.4 Parameters for Simulation Control
Figure 5-16 shows the dialog to specify parameters for simulation control. The parameters in this
dialog are interpreted as follows.

TSAT User Manual
Figure 5-16: Parameters for simulation control
Lower Voltage Threshold For Load Model Conversion
When loads are represented by nonlinear static models (i.e., non-constant impedance model),
these models are converted to constant impedance model when the bus voltage goes below this
level. Refer to the TSAT Model Manual for more information on this conversion.
Upper Voltage Threshold For Load Model Conversion
When loads are represented by nonlinear static models (i.e., non-constant impedance model), and
these models are converted to constant impedance model at low voltages, the original load
models are resumed when the bus voltage recovers at this level. Refer to the TSAT Model
Manual for more information on this conversion.
Max Generator Speed Deviation
When the maximum generator speed deviation exceeds this value, the simulation will be stopped.
This check is applied to all generators that have dynamic models.
Switching Data Overrides
You can override some simulation parameters globally. When a parameter is changed, it is
applied to all contingencies for the scenario (however, the original contingency data is not
modified). The following parameters can be changed:
• Simulation length
• Integration step size
• Integration method

TSAT User Manual
5.2.1.5 Parameters for Modelling
Figure 5-17 shows the dialog to specify parameters for modelling. The parameters in this dialog
are interpreted as follows.
Figure 5-17: Parameters for modelling
Default Load Model For P and Q
These two parameters set the default models for active (P) and reactive (Q) loads for simulations.
One of three models can be specified for each of the P and Q components independently: constant
MVA, constant current, and constant impedance. Note that the default load model is ignored for a
load if the powerflow includes non-constant power load, or a load model is specified in the
dynamic data.
Note that these default models do not apply when solving powerflow at the pre-simulation and
during the powerflow dispatches for a transaction. Refer to Section 3.4 for details on default
models in these computations.
Include Induction Motor In Load Shedding
If this option is enabled, TSAT will shed a fraction of the induction motor, whenever load
shedding is required. By default, it is not enabled. This load shedding may come from a Shed
Load switching command or from relay/SPS action. For the Shed Load command , the fraction
of induction motor to be shed is equal to the active power percentage. The compensat ing shunt
capacitor for the motor is shed in equal proportion. Note induction generators are not shed, even
if they are located at the same bus as the load shedding.
Threshold Value Of Zero Impedance Line

TSAT User Manual
Any branch in the network whose line impedance is less than this threshold value is treated as
“zero impedance line” (ZIL), i.e., the line is short-circuited during all computation. Note that this
value must be consistent with the ZIL threshold used when solving the powerflow.
Solution Option For Generator Swing Equation
When solving the generator swing equations, the output power from the turbine model can be
either used directly (this is referred as the “power option”) or converted to torque (this is referred
to as the “torque option”) in the swing equation. Mathematically, the torque option effectively
adds a small damping to the generator.
Automatic Dynamic Data Correction
The dynamic models may sometimes contain controls that are too fast for the conventional
transient stability analysis. This might cause, under some conditions, numerical problems for the
integration algorithm. To avoid possible errors, TSAT automatically scans the dynamic models
and makes necessary adjustments to unreasonable parameters. It is suggested that this option be
always turned on, unless you are absolutely sure that the data must not be adjusted.
Common MVA Base
This is the MVA base value used to per unitize the system parameters and quantities. It must be
the same as the MVA base used in the powerflow data.
Common Frequency Base
This is the frequency base (in Hz) of the system.
5.2.1.6 Parameters for Transaction Analysis
Figure 5-18 shows the dialog to specify parameters for transaction analysis. All options
associated with the transaction analysis are discussed in Section 3.5.2. In addition, you can select
the security criteria that will be applied in the determination of stability limits. This can be done
in one of two ways:
• If a security criterion is checked in this dialog and it is also enabled in the security criteria
dialog, the criterion is fully applied in the limit search iteration. This means that the limits
obtained will meet all such criteria.
• If a security criterion is checked in this dialog but it is not enabled in the security criteria
dialog, the criterion is only monitored in the limit search iteration. This means that the
security criterion is computed and shown in the iteration summary results but it is not
enforced when determining the stability limits.
Power Transfer Limit Search Threshold is used to check the limit search convergence. To avoid
excessive iterations around the solution point, this threshold should not be set to a value less than
10 MW.

TSAT User Manual
Figure 5-18: Parameters for transaction analysis
5.2.1.7 Parameters for Early Termination
Figure 5-19 shows the dialog to specify parameters for early termination. Most of the parameters
in this dialog are discussed in Section 3.3.10. Note that you can apply early termination option
separately for basecase analysis and transaction analysis.
Figure 5-19: Parameters for early termination

TSAT User Manual
5.2.1.8 Parameters for Sequence Network Formulation
Figure 5-20 shows the dialog to specify parameters for sequence network data interpretation. The
parameters in this dialog are interpreted as follows.
Figure 5-20: Parameters for sequence network formulation
Sequence Network Formulation Method
This sets the zero sequence network formulation method. Two options are available:
• Classical. In this method, bus shunts and loads are ignored in the zero sequence network
formulation.
• Shunt/load included. In this method, bus shunts and loads are included in the zero
sequence network formulation.
Primary Source For Generator Impedance
This determines the choice of generator impedances to be used in the zero sequence impedance
calculation. The available options are:
• Use sequence network data

• Use Xd from dynamic data
• Use X’d from dynamic data
• Use X”d from dynamic data

TSAT User Manual
Please refer to Section for 10.2.11 for more details on interpretation and usage of sequence
network data.
5.2.1.9 Synchronization of Computation Parameters
If there are multiple scenarios defined in a TSAT case and all scenarios shall use the same
computation parameters, you can define the parameters for one scenario and then use the scenario
synchronization feature to set the same parameters for all other scenarios. To use this feature,
select the File | Synchronize Parameters function in the main menu and then follow the prompts
in the dialog.
5.2.2 Examining and Editing Powerflow Data
It is assumed in TSAT that a powerflow case in a supported format is provided as the base case.
Therefore, it is not possible to create a powerflow case within TSAT. The task of creating and
adjusting powerflow is in the scope of the powerflow program. To provide flexibility to examine
and edit powerflow data within TSAT, however, a connection is made between TSAT and
Powertech’s powerflow program PSAT. In order to use this feature, PSAT must be installed on
your computer.
PSAT can be started in TSAT at one of two points, with different application capabilities:
• From the View | Powerflow Data menu function or the button. When PSAT is
launched at this point, the powerflow of the selected TSAT scenario will be loaded in
PSAT. You can do any of the following:
Browse the powerflow data and powerflow solution reports

Make changes to powerflow data and solve the powerflow. However, when you save
the changed or solved powerflow, the changes and the new solution are not passed
back to the TSAT case. If you want to get the changed powerflow into the active
case, either manually change the powerflow file name or use the second method to
start PSAT.
Load another powerflow case and examine its data
Keep PSAT active during the case setup, simulations, and result analysis
• From the Edit In PSAT button in Case Wizard (similar to Figure 5-3). When PSAT is
launched at this point, the powerflow of the corresponding TSAT scenario will be loaded
in PSAT. You can do any of the following:
Browse the powerflow data and powerflow solution reports

Make changes to powerflow data and solve the powerflow. When the powerflow is
saved, it is automatically passed back to the active case so the simulation will use the
changed powerflow.
There are two restrictions in this mode:
You cannot load another powerflow case into PSAT at this point to avoid possible
conflict
You must quit PSAT before existing the Case Wizard (and thus running the
simulations)

TSAT User Manual
When in PSAT, you can use any features available in PSAP except for the above restrictions. For
example, you can open the one-line diagram to manipulate powerflow graphically.
5.2.3 Examining and Editing Dynamic Data
Similarly to the powerflow data, it is usually assumed in TSAT that the dynamic models and data
associated with the powerflow case are provided. Therefore, it is normally not required to create
the complete dynamic models for a case within TSAT (it is however possible to do so if
necessary). To provide the capability of examining and editing dynamic data in TSAT, a dynamic
data editor is available.
The dynamic data editor can be started in TSAT at one of two points, with different application
capabilities:
• From the View | Dynamic Data menu function or the button. At this point, the
dynamic data from all data files specified for a scenario can be examined altogether. You
cannot, however, edit the dynamic data.
• From the Edit button in Case Wizard (similar to Figure 5-4). At this point, you can not
only examine but also add new models or make changes to the dynamic data.
The main window of the dynamic data editor is shown in Figure 5-21. Note that the case in this
dialog includes dynamic data in a third party format. This allows you to only edit the data with
models included in the case but not create new models. If DSATools data format is used in a case,
you can actually add new models to the case.
Double clicking on the +

sign to open editing window
for specific model
Figure 5-21: Main window of dynamic data editor

TSAT User Manual
Most of the features in the dynamic data editor are straightforward. The following describes the
salient ones:
• Each column of the data sheet for a model is sortable. This can help spot unusual values
for specific parameters among the same models.
• Double clicking on the + sign (Figure 5-21), an editing window for the specific model
appears (as shown in Figure 5-22). You can change values of any editable parameters.
The model diagram can be shown in this window using the following approach:
The model diagram must be digitized and saved in *.bmp format. The bmp file must
be named after the model name. For example, for the ESAC4A exciter model, the
bmp file must be named as esac4a.bmp.
Create a folder \bmp at the same level as the TSAT program folder. Place the model
bmp files in this folder.
When the editing window for the model is started, the model bmp file will be
displayed automatically in the window.
Figure 5-22: Edit window for specific model

TSAT User Manual
Figure 5-23: The Model flag for PSLF models
• For PSLF dynamic models, each model has a Model flag as shown in Figure 5-23. This
flag can be set to IN or OUT to enable or disable the model. Note that this flag is
different from the Status flag (also shown in Figure 5-32) which indicates the status (in or
out of service) of the device in the powerflow and thus is non-editable in the dynamic
model editor.
• Add and delete models: select any model and press the right mouse button, a floating
menu appears (as shown in Figure 5-24). From this menu, you can delete the selected
model or create a new model of the same type (actually duplicate the selected model).
Figure 5-24: Add or delete a dynamic model
• Two options are available to save changes made to the dynamic models:
Save all models. This will write all models in the associated format.
Save only changes made. This will save only the changes to a specified data file. This
option has the advantage that the original data file can be kept intact after data
changes. However, for certain types of data changes, “Save Changes” option is not
effective. For example, when the Model flags are changed, or when an existing
model is deleted. In such cases, you must use the “Save All” option to save changes.
With either option, the saved data is passed to the case and used in the simulations.
• Certain dynamic models may not be shown in the dynamic data editor. These include
models not converted in TSAT and the TSAT native user-defined models.

TSAT User Manual
5.2.4 Creating, Examining, and Editing Monitor Data
When setting up a case, you can create or edit the monitor data in TSAT using the monitor data
editor shown in Figure 5-25. This editor allows you to create, view, and edit monitor data of all
output types. Most of the features in the monitor data editor are straightforward. The following
describes the salient ones:
• For each device to be monitored (bus, generator, branch, etc.), you can either enter the
device identification (bus numbers, ID, etc.) directly, or select from the devices available
in the case (the devices available in the case are obtained after analyzing the powerflow
and dynamic data specified).
• For some output types (such as generator, bus, branch, etc.), there are optional quantities
that can be monitored. To include any of these, you must check the appropriate quantities
(Figure 5-25).
• Some of the security criteria are applied only to monitored quantities (for example,
generators for computing damping index are selected only from the monitored generator
list). So, make sure that all important devices are monitored for the security criteria
specified. On the other hand, if a set of monitored quantities should be excluded from the
computation of a security index, the associated security application option should be
specified (Figure 5-25). It is for instance often required when computing transient
voltage drop index that certain voltage levels are not included. In this case, the security
application option should be disabled for all buses at these voltage levels.
When a created or modified monitor data is saved, it will be automatically passed to the TSAT
case and used in the simulations.

TSAT User Manual
Specify security
application options
Specify optional output quantities
Figure 5-25: Monitor data editor
5.2.5 Creating, Examining, and Editing Contingency Data
When setting up a case, you can create or edit the contingency data in TSAT using tools
provided:
• A set of contingency creation wizards. This allows you to create groups of contingencies
with specific rules.
• A contingency editor. This allows you to create customized contingencies and to edit
contingencies
The relationship of the contingency creation wizards and the contingency editor are shown in
Figure 5-26.
Create groups of Further
contingencies by rules Contingency customization
Contingency
specification creation wizards
Contingency
dialog in TSAT editor
Case Wizard
Create customized contingencies
or edit existing contingencies
Figure 5-26: Relationship of contingency creation wizards and contingency editor

TSAT User Manual
Figure 5-27: Contingency creation wizard selection
When creating contingencies (pressing the Create button in Figure 5-6), a contingency creation
wizard selection window appears (Figure 5-27). You have four options:
• Create customized contingencies using the contingency editor.
• Create a nofault contingency. The nofault simulation is normally required when

assembling a new base case.
• Create contingencies associated with a bus. This allows you to create a group of
contingencies with different faults located around a bus. Faults can be cleared by various
clearance options. In this wizard, contingencies are created in three steps:
(1) Select a bus (substation) of focus
(2) Specify events, faults, and clearance options: you can select the event types to be
considered around the substation:
Fault at the substation with primary clearance only: this assumes that the
specified fault occurs at the bus and the fault is cleared at the primary clearance
time by tripping simultaneously both ends of a circuit (including transmission
line, transformer, zero impedance line) connected at the bus. If the bus is
connected to N circuits, this event will create N contingencies.
Fault at the substation with primary and backup clearance: this assumes that the
specified fault occurs at the bus and the remote end of a circuit (including
transmission line, transformer, zero impedance line) connected at the bus is
tripped at the primary clearance time. The circuit breakers at the near end of the
circuit are assumed stuck (thus the fault is still on). The backup breakers clear the
fault as well as an additional circuit (however no one-port element such as
generator or shunt is lost). If the bus is connected to N circuits, this event will
create N×(N-1) contingencies.

TSAT User Manual
Fault at a bus connected to the substation through a circuit with primary

clearance only: this assumes that the specified fault occurs at a bus connected to
the substation and the fault is cleared at the primary clearance time by tripping
simultaneously both ends of the circuit (including transmission line, transformer,
zero impedance line) connecting the bus and the substation. If the bus is
connected to N circuits, this event will create N contingencies.
Fault on a circuit connected to the substation with primary clearance only: this
assumes that the specified fault occurs on a line (normal transmission line only,
excluding multiple sectional line, transformer, zero impedance line); the fault
location on the line can be specified as percentage of the line from the substation.
The fault is cleared at the primary clearance time by tripping simultaneously both
ends of the line. If the bus is connected to N normal transmission lines, this event
will create N contingencies.
Fault on a circuit connected to the substation with primary and delayed

clearance: this assumes that the specified fault occurs on a line (normal
transmission line only, excluding multiple sectional line, transformer, zero
impedance line); the fault location on the line can be specified as percentage of
the line from the substation. The remote end of the line is tripped at the primary
clearance time (fault is still on), but the primary clearance (zone 1 relay) at the
near end of the line is assumed no action. The delayed clearance (zone 2 relay)
reacts to trip the near end of the line (thus the fault) at delayed clearance time. If
the bus is connected to N normal transmission lines, this event will create N
contingencies.
For each event, you can specify any or all of the following faults:
Three-phase
One-phase-to-ground
Two-phase-to-ground
Depending on the events you selected, you can specify the fault clearance times:
Primary clearance time

Backup clearance time: this must be longer than the primary clearance time
Delayed clearance time: this must be longer than the primary clearance time
(3) Specify other contingency parameters: you can finalize the contingencies with the
following parameters:
Contingency title
Starting time of the fault
Total simulation time
Simulation step size
Integration intervals at which simulation results are saved
• Create contingencies associated with a subsystem. This allows you to create a group of
contingencies with the same fault and clearance option in a specified subsystem. In this
wizard, contingencies are created in four steps:

TSAT User Manual
(1) Specify the subsystem to apply contingencies: this may be specified by the
combination of areas, zones, vicinities (within a specified number of buses) to
selected buses, or entire system.
(2) Specify the contingency type: the following choices are available
Three-phase fault at bus cleared with loss of any element

Three-phase fault at bus cleared by single circuit tripping
Three-phase fault at generator high-tension bus cleared by single circuit tripping
Three-phase fault at bus cleared by parallel circuit tripping
One-phase-to-ground fault at bus cleared without loss of any element
One-phase-to-ground fault at bus cleared by single circuit tripping
Two-phase-to-ground fault at bus cleared without loss of any element
Two-phase-to-ground fault at bus cleared by single circuit tripping
Three-phase fault on line cleared by single circuit tripping
One-phase-to-ground fault on line cleared by single circuit tripping
Two-phase-to-ground fault on line cleared by single circuit tripping
Single circuit tripping without fault
Double circuit tripping without fault
Parallel circuit tripping without fault
Single generator tripping without fault
For any of the above contingency type, you can specify a circuit to be outaged at pre-
simulation condition. This effectively creates N-1-x type contingencies.
(3) Specify contingency application option: these are associated with kV range within
which the fault and circuit tripping should be considered, fault clearance time (if
applicable), and minimum MVA rating for which generator tripping should be
considered.
(4) Specify other contingency parameters: you can finalize the contingencies with the
following parameters (whenever applicable):
Contingency title
Starting time of the fault
Total simulation time
Simulation step size
Integration intervals at which simulation results are saved
Note: when using the above wizards to create unbalanced faults, it is assumed that the fault
impedances are to be computed by TSAT from the sequence network data provided. If the fault
impedances must be specified individually for each contingency, you must edit these
contingencies in the contingency editor to do so.
Example for creating contingencies associated with a bus
For the bus configuration shown in the figure, the following contingencies will be created using
the contingency creation wizard for the bus:

TSAT User Manual
3
• Contingency event: three-phase fault at
the substation with primary clearance
only: 2 4
1
(1) Three-phase fault at bus 1 cleared by
tripping circuit 1-2 at the primary
clearance time G
(2) Three-phase fault at bus 1 cleared by tripping circuit 1-3 at the primary clearance
time
(3) Three-phase fault at bus 1 cleared by tripping transformer 1-4 at the primary
clearance time
• Contingency event: one-phase-to-ground fault at the substation with primary and backup
clearance:
(1) One-phase-to-ground fault at bus 1; remote end of circuit 1-2 (at bus 2) is tripped at
the primary clearance time (fault is still on), but the circuit breakers at the near end of
the circuit (at bus 1) are assumed stuck. The backup breakers clear the fault (circuit
1-2 is tripped completely) as well as circuit 1-3 at the backup clearance time.
1-2 is tripped completely) as well as transformer 1-4 at the backup clearance time.
1-3 is tripped completely) as well as circuit 1-2 at the backup clearance time.
1-3 is tripped completely) as well as transformer 1-4 at the backup clearance time.
(5) One-phase-to-ground fault at bus 1; remote end of transformer 1-4 (at bus 4) is
tripped at the primary clearance time (fault is still on), but the circuit breakers at the
near end of the transformer (at bus 1) are assumed stuck. The backup breakers clear
the fault (transformer 1-4 is tripped completely) as well as circuit 1-2 at the backup
clearance time.
(6) One-phase-to-ground fault at bus 1; remote end of transformer 1-4 (at bus 4) is
tripped at the primary clearance time (fault is still on), but the circuit breakers at the
near end of the transformer (at bus 1) are assumed stuck. The backup breakers clear
the fault (transformer 1-4 is tripped completely) as well as circuit 1-3 at the backup
clearance time.

TSAT User Manual
Note: some of the above contingencies may not be practical based on the actual
bus/breaker configuration. You have two options to handle this; (i) manually edit the
resulting contingency list to remove the non-practical ones; (ii) perform the security
assessment for the complete set of contingencies, and for those (assuming a short list)
that violate the criteria, ensure that they are practical before accepting the results.
• Contingency event: three-phase fault at a bus connected to the substation through a

circuit with primary clearance only:
time
time
(3) Three-phase fault at bus 4 cleared by tripping transformer 1-4 at the primary
clearance time
• Contingency event: three-phase fault on a circuit connected to the substation with

primary clearance only:
(1) Three-phase fault on circuit 1-2 cleared by tripping circuit 1-2 at the primary
clearance time
(2) Three-phase fault on circuit 1-3 cleared by tripping circuit 1-3 at the primary
clearance time
• Contingency event: one-phase-to-ground fault on a circuit connected to the substation

with primary and delayed clearance:
(1) One-phase-to-ground fault on circuit 1-2; remote end of circuit 1-2 (at bus 2) is
tripped at the primary clearance time (fault is still on), but the primary clearance
(zone 1 relay) at the near end of the circuit (at bus 1) is assumed no action. The
delayed clearance (zone 2 relay) reacts to trip the near end of the circuit (thus the
fault) at the delayed clearance time.
(2) One-phase-to-ground fault on circuit 1-3; remote end of circuit 1-3 (at bus 3) is
tripped at the primary clearance time (fault is still on), but the primary clearance
(zone 1 relay) at the near end of the circuit (at bus 1) is assumed no action. The
delayed clearance (zone 2 relay) reacts to trip the near end of the circuit (thus the
fault) at the delayed clearance time.
Figure 5-28 shows the main window of the contingency editor. With this editor, you can
• Add (at the end of the current switching events) any new switching event
• Insert (before the selected switching event) any new switching event
• Modify an existing switching event
• Delete an existing switching event
• Specify the application option for the contingency

TSAT User Manual
• Cut, copy, paste, comment, uncomment existing switching events (using the floating
menu from right mouse clicking)
The use of this edit is straightforward.
Figure 5-28: Contingency editor
When a created or modified contingency data is saved, it will be automatically passed to the
TSAT case and used in the simulations.
5.2.6 Creating, Examining, and Editing Criteria Data
When setting up a case, you can create or edit the critera data in TSAT using the criteria data
editor shown in Figure 5-29. This editor allows you to create, view, and edit criteria data. It is
recommended that you review the criteria data descriptions in TSAT model manual to get
familiar with the concepts and terminology used in this data set, before creating or editing the
data.
When a created or modified criteria data is saved, it will be automatically passed to the TSAT
case and used in the simulations.
The definitions of the security criteria are explained in Section 3. The following are the remarks
on some implied aspects when specifying the parameters.

TSAT User Manual
Figure 5-29: Criteria data editor
General comments
Each set of criteria require a unique name (Category Name). You can also specify a time window
for which the criteria shall be applied.
A set of criteria must be included in at least one subsystem definition. Otherwise, that set of
criteria will not be used.
Note that the basic transient stability criterion is always enabled, with either swing or angle
margin specified in the scenario parameter section. All criteria available in the criteria data file
are optional.
Parameters for transient stability criteria
• For peak-to-peak angle index, the threshold commonly used to check for instability is 180
degrees. If, however, a margin is required, a smaller value should be specified. The
calculation of the relative generator rotor angles can be made with reference to a
generator specified for each subsystem.
• For closing torque index, the value recommended by IEEE as the safety threshold is 0.5
pu.
Parameters for damping assessment

TSAT User Manual
• Damping index is computed from the relative rotor angles of up to four generators with
the Prony method. The generators that can be used for damping index computation must
be included in the monitor data.
• You can customize the damping index computation with these parameters:
Minimum damping: this is the damping index threshold. For example, if you set the
minimum damping at 3%, any contingencies that have a damping index less than 3%
will be declared as insecure contingencies.
Frequency range to check for critical modes: if you know the rough frequency range
of the most critical modes in your system, it is a good idea to specify such a range.
For example, if the most critical mode in the system is an inter-area mode at about
0.8 Hz, this range can be set for (0.6, 1.0) Hz. This helps avoid the possibility that
some poorly damped local modes far from the region of interest dominate in the
damping index computation.
Trim threshold: this is used to truncate the modes of very small amplitudes found by
the Prony method. This helps focus the damping index computation on more
significant modes. The recommended value is between 1 and 5 degrees (for the
generator rotor angles which are used in the Prony analysis).
Damping window length: the damping index is computed from the system response
in a specified time window that is counted backward at the end of the simulation. In
order to obtain good results, this window should avoid switching activities in the
contingency, any known significant nonlinearity in the system, and should be at least
twice the period of the dominant mode. For example, if the most critical mode in the
system is an inter-area mode at about 0.8 Hz, this time window should be at least 2.5
seconds.
You can enable an option to extend the simulation (by an amount equal to damping
window length) if the damping criterion is violated for a contingency.
Parameters for transient voltage assessment
• These indices are computed from the following list of quantities included in the
subsystem for the criteria set:
Buses
Generator buses
Induction machine buses
Load buses
Parameters for transient frequency assessment
• These indices are computed from the following list of quantities included in the
subsystem for the criteria set:
Buses
Generator buses
Induction machine buses

TSAT User Manual
Load buses
Parameters for relay margin security assessment
• These indices are computed from the monitored branches included in the subsystem for
the critera set.
5.2.7 Creating, Examining, and Editing Dynamic Representation Data
When setting up a case, you can create or edit the dynamic representation data in TSAT using the
dynamic representation data editor shown in Figure 5-30. This editor allows you to create, view,
and edit dynamic representation data. Most of the features in the dynamic representation data
editor are straightforward. However, it is recommended that you review the dynamic
representation data descriptions in TSAT model manual to get familiar with the concepts and
terminology used in this data set, before creating or editing the data.
When a created or modified dynamic representation data is saved, it will be automatically passed
to the TSAT case and used in the simulations.
Figure 5-30: Dynamic representation data editor
5.2.8 Creating, Examining, and Editing Transaction Data
When setting up a case, you can create, edit, or simply read existing transaction data in TSAT.
Transfer data, Powerflow Solution Parameter data, and Interface and Circuit Data can be edited
using interfaces provided in TSAT as shown in Figure 5-10. The editing features are similar to
those in the editors for other types of data and are straightforward to use. However, it is
recommended that you review the transaction data (particularly transfer data) descriptions in
TSAT model manual to get familiar with the concepts and terminology used, before creating or
editing the data. For Generator Capability data and Generator Coupling data, no editing capability
is provided in TSAT so you will have to prepare the data before running TSAT (for example
using VSAT’s data editing functions) and then bring the data to the TSAT case.

TSAT User Manual
When created or modified transaction data sets are saved, it will be automatically passed to the
TSAT case and used in the simulations.

TSAT User Manual
5.3 Modifying a TSAT Case
Using the case wizard, a TSAT case can be modified to
• Add more scenarios

• Delete existing scenarios
• Split a scenario with multiple contingencies
• Change the data specifications and/or computation parameters
• Edit most of the data sets
This section describes the method to modify a TSAT case.
To modify a TSAT case, open the case first to make it the active case in the TSAT main window.
Then start the case wizard using one of two methods:
• Select the File | Case Wizard function in the main menu. This brings up the main dialog
of the case wizard shown in Figure 5-31 (this is also shown in Figure 5-2). From this
dialog, you can add new scenarios, delete existing scenarios, or modify any scenario in
the case.
• Double click a scenario in the scenario table. This directly brings up the scenario editing
window shown in Figure 5-32.
The main dialog of the case wizard allows you to do two tasks:
• Create a new TSAT case. This is enabled by selecting the “Create A New TSAT Case”
radio button. Refer to Section 5.2 for details on using this option.
• Modify the active TSAT case. This is enabled by selecting the “Work On The Active
TSAT Case” radio button. This option is described in this section.
Scenario list
Click on this
radio button to
modify the active
TSAT case Select a scenario
from the scenario list
and click on this
Click on this button to split it
check box to
create a new Select a subsequent
scenario scenario from the
scenario list and
click on this button
to delete the scenario
Type a new
output file name Figure 5-31: Main dialog of the case wizard
here

TSAT User Manual
Adding a new scenario
To add a new scenario to the active TSAT case, click on the “Create A New Scenario In The
Active TSAT Case” check box and then press the Next button. You will be prompted to decide
whether or not the computation parameters in the base scenario shall be used as defaults for the
new scenario. After this, the scenario editing window appears as shown in Figure 5-32.
Figure 5-32: Scenario editing window
At this point, TSAT has created a new scenario that is merely a copy of the base scenario (i.e., the
new scenario contains the same data as the base scenario, but with the default parameters as
described in Section 5.2.1). A default title is assigned to the new scenario (refer to Section 10.2.1
for the convention used). Therefore, if you press the OK button without any more changes, the
new scenario should be exactly the same as the base scenario.
In most cases, you may want to change some or all specifications for the new scenario. To do
this, click the data item in the tree. The dialog box for that data item will appear in the left half of
the window, for example, as shown in Figure 5-33 for the powerflow data. Note that the
powerflow dialog in Figure 5-33 is very similar to that in Figure 5-3 for the base scenario, except
that an additional check box labeled “Use Data From Base Scenario” is available. This check box
is included in all other data entry dialog boxes for any subsequent scenarios (the exception is for
computation parameters; refer to Section 5.2.1). It allows a subsequent scenario to inherit the data
specification from the base scenario and thus provides flexibility when creating multiple
scenarios in a TSAT case for a base system model. It is certainly possible to specify separate data
by unchecking this check box.

TSAT User Manual
Click on this check

box to inherit data
specification from
the base scenario
Figure 5-33: Specifying the powerflow data for a subsequent scenario
Splitting an existing scenario
This option is used only if you want to do the following:
• One scenario in your case has multiple contingencies.
• You want to distribute the simulations of these contingencies among multiple TSAT
computation servers (refer to Section 9.5 on how to use distributed computation feature in
TSAT).
You can split a scenario for a specified number of computation servers or for all servers available
in the system. Each new scenario created after the splitting has the same number of contingencies.
Deleting an existing scenario
To delete an existing scenario from the active TSAT case, select the scenario from the scenario
list in Figure 5-31 and then press the Delete Scenario button. Once a scenario is deleted and the
modified case is saved, the deleted scenario cannot be recovered.
Note that only subsequent scenarios can be deleted from a TSAT case. The base scenario can be
modified but not deleted.

TSAT User Manual
Modify the specifications of an existing scenario
To modify an existing scenario in the active TSAT case, select the scenario from the scenario list
in Figure 5-31 and press the Next button, or double click the scenario in the scenario table of the
TSAT main window. This brings up the scenario editing window shown in Figure 5-32 from
which you can modify any data specifications for the scenario.
Generally, you can do the following in the scenario editing window for each data set in the TSAT
case:
• Change any parameters directly shown in the scenario editing window, including
selection of different data files.
• Edit data in dynamic data, contingency data, monitor data, dynamic representation data,
and transaction data. Editing dialogs are provided for each type of data and working with
these editing dialogs is very straightforward.
• Create data for contingency data, monitor data, dynamic representation data, and
transaction data. Editing dialogs are provided for each type of data and working with
these editing dialogs is very straightforward.
5.4 Comparing Scenarios in a TSAT Case
If a TSAT case has multiple scenarios, you can compare selected scenarios for the data and
computation options defined for the scenarios. To use this feature, select the File | Compare
Scenarios function in the main menu. This will show all differences in the scenarios selected.
5.5 Saving and Archiving a TSAT Case
Saving a TSAT case
After the active TSAT case is modified, you should save the case by using the File | Save or File |
Save As function in the main menu. This will save all data and computation parameter
specifications in the active case to a TSAT case file you specify.
TSAT has a built-in procedure to check if the active case might have been modified when you
close the case or exit the TSAT program. A prompt dialog box opens up to remind you to save the
case, if
• The case wizard has been launched
• The computation parameters dialog box has been launched and the parameters updated by
the OK button (refer to Section 5.2.1)
Archiving a TSAT case
When a TSAT case is opened, you can archive the case to backup the case or to send the case to
another user. To archive a case,
(1) make sure that the WinZip software is installed on your computer

TSAT User Manual
(2) select the File | Archive function in the main menu
When archiving is completed, a file named TSAT_Archve_yyyymmdd_hhmmss.zip is created

in the TSAT case folder, where yyyy, mm, dd, hh, mm, ss are year, month, day, hour, minute, and
second when the archiving is done. A TSAT archive contains the TSAT case file, all data files
used, and the binary result file (if it is available). Note that the TSAT case file included in the
archive is modified to ensure that the case will run appropriately after unarchiving:
• All file paths for data files are removed from the case file. When running the case after
unarchiving, it is assumed that all data files are located in the same folder as the case file
(this is how the case is unarchived).
• Values for all parameters are included in the case file, so if the unarchived case is run
using a version of TSAT with different default parameter settings, same results should be
expected.
To unarchive the case, you can use WinZip or any other software that can uncompress a zip file.
5.6 Examining TSAT Case Details
During a TSAT session, you may want to examine some of the details of the active TSAT case.
This can certainly be done using the case wizard, but a simpler method is available. Select the
View | Case Details function in the TSAT main menu. A dialog box shown in Figure 5-34 opens
up. The use of this dialog is very straightforward.
Click on the tab

to select scenario
Click on the tab to

select and view
different data type
Figure 5-34: Examining TSAT case details

TSAT User Manual
Note the following two limitations for this dialog:
• It only displays the active TSAT case information; it does not allow any changes to be
made for the data. If you want to change any data in the case, use the case wizard
described in Section 5.3.
• The computation parameters are not displayed in this dialog, since they are already
directly accessible from the TSAT main window.
There is another function available in the View menu (View | Dynamic Data). This function
launches the dynamic data editing window for you to browse through the dynamic models and
their parameters. Similarly to the case details window, you can only view but not change the
dynamic data at this point.

TSAT User Manual
6 Performing Basecase Analysis
This section describes the method for performing basecase analysis.
6.1 Starting Basecase Analysis
Before starting a basecase analysis, make sure that all computation parameters are specified
appropriately (refer to Section 5.2.1 for details on specifying computation parameters).
Basecase analysis can be performed for any TSAT case that is successfully opened. To start a
basecase analysis, select the Run | Basecase Analysis function in the TSAT main menu. Once
the basecase analysis is started, it is applied to all scenarios in the active TSAT case, unless the
scenario is disabled by setting its action field to Don’t Run.
During a basecase analysis, you can always pause/continue or stop the computation by selecting
appropriate functions from the TSAT main menu. Refer to Section 4.3.1 for details.
6.2 Monitoring Basecase Analysis
After a basecase analysis is started, the following will happen in the TSAT main window.
On the Computation Progress Page
The computation progress bars on the left half of the page show the computation progress. When
a scenario is being processed, the bar is gradually being filled with blue colour, with a text string
under the bar indicating the contingency being processed. When the distributed computation
feature is enabled with multiple engine servers available, multiple scenarios may be processed
simultaneously. This is visible when multiple bars show simulation progress.
The plots on the right half of the page monitor two sets of quantities from the simulation:
• Relative generator rotor angles (the specification of the reference generator is described
in Section 5.2)
• Bus voltage magnitudes
The quantities plotted are those specified in the monitor data of the scenario. A spinner is
available below the plots for selecting the plots for the contingencies that have been completed.
The time axes (x-axis) of these plots are automatically scaled to be the simulation length specified
for the contingency. If the early termination option is enabled for the simulation, the simulation
may end before it reaches the full simulation length specified.
Figure 4-3 shows a typical computation progress page after the analysis is completed for a
scenario.
During a simulation, you can pause the simulation by clicking the Pause button (see Section
4.3.1). While the simulation is paused, you can skip the rest of the simulation for the contingency
and continue with the next contingency. This is a useful feature for large cases for which you wan

TSAT User Manual
to terminate the lengthy simulation of a contingency after the simulation clearly shows it is very
stable or very unstable. Note however that a skipped contingency will not have any security
indices computed, although the results of the completed simulation will be available in the binary
result file. To skip a contingency, pause the simulation first, and then click the Skip Contingency
button located at the lower right corner on the computation progress page (see Figure 6-1). Only
the contingency being simulated can be skipped at run-time. To skip a contingency in the
contingency data set before simulation starts, use the Application command in the contingency
(refer to TSAT Model Manual for details).
Figure 6-1: Skip a contingency feature
On the Result Summary Page
Before the basecase analysis starts, only two fields are populated on the result summary page for
each scenario: Cont No. and Contingency Description. After the analysis is completed for a
contingency, the security indices are computed and shown in the appropriate fields on the result
summary page. Depending on the security indices specified, some or all of the index fields will be
filled. The Status field will also be determined, as either Secure or Insecure, based on the indices.
During the analysis for a scenario, all completed contingencies are always listed together at the
beginning of the table, sorted by the Transient Stability Index field.
Figure 4-4 shows a typical result summary page after the analysis is completed for a scenario (in
this figure all security indices were specified and thus shown).
On the Scenario Table
When the analysis is completed for a scenario, the Basecase Analysis | Security Status field is
updated with the overall security status for the scenario (either Secure or Insecure).
On the Program Status Bar
The green bar starts moving, indicating that the computation engine is processing the case.
6.3 Examining Basecase Analysis Results
The results from the basecase analysis can be examined and analyzed in three levels:

TSAT User Manual
(1) On the computation progress and result summary pages: These pages show the summary of
the analysis for all contingencies in all scenarios. Particularly, all security indices computed
are included in the result summary page. Any indices below the specified threshold are shown
in red colour, indicating an insecure situation. If a contingency has at least one insecure
index, the contingency is insecure, and if a scenario has at least one insecure contingency, the
scenario is insecure.
(2) From the basecase analysis details dialog: on the Result Summary page, additional results are
available for each contingency, by double-clicking on the contingency. A dialog shown in
Figure 6-2 opens up. Up to four sheets are available in this dialog for different types of
security assessment.
• Transient stability (Figure 6-2). This sheet is always available and it gives the following
information if stability margin is specified as the transient stability criterion:
Transient stability index

Critical cluster of generators (CCG) identified for this contingency
If CCT is specified as the transient stability criterion, this sheet gives the CCT
computation iteration details.
• Damping estimate (Figure 6-3). This sheet is available only when the damping criterion is
specified and it gives the following information in addition to the damping index:
The generators whose responses are used to obtain the minimum damping.
All modes obtained from the minimum damping computation algorithm within the
frequency range and the trim threshold.
Choose tab to view

results for different type
of security criterion
Use the slider to select

different contingency
Figure 6-2: Basecase analysis details dialog – transient stability

TSAT User Manual
Figure 6-3: Basecase analysis details dialog – damping estimate
• Voltage violation (Figure 6-4). This sheet is available only when the voltage criterion is
specified and it gives the following information in addition to the voltage drop/rise
duration indices:
The buses at which the voltage drop/rise duration indices are obtained.
Number of buses for which the specified transient voltage violation criterion is
violated.
• Frequency violation (Figure 6-5). This sheet is available only when the frequency
criterion is specified and it gives the following information in addition to the frequency
indices:
The buses or generators at which the frequency drop/rise duration indices are
obtained.
Number of buses and generators for which the specified transient frequency violation
criterion is in violation.
Bus or generator which has the minimum rate of change of frequency.

TSAT User Manual
Figure 6-4: Basecase analysis details dialog – voltage violation
Figure 6-5: Basecase analysis details dialog – frequency violation
(3) In the DSAOA module: you can examine all monitored simulation results and all messages in
the DSAOA module. Refer to DSAToolsTM DSAOA Manual for details on using the DSAOA
module.
The basecase analysis results (security indices and the results contained in the basecase analysis
details dialogs) are also written to the computation result summary file. Refer to Section 9.1 for
details on creating this file.
Using one of the three buttons on the Computation Progress and Result Summary pages of the
TSAT main windows, you can copy, save, or print the information on these two pages during
and/or after the basecase analysis.

TSAT User Manual
7 Performing Transaction Analysis
This section describes the method for performing transaction analysis.
7.1 Starting Transaction Analysis
Before starting a transaction analysis, all computation parameters are specified appropriately
(refer to Section 5.2.1 for details on specifying computation parameters).
Transaction analysis can be performed for any TSAT case that is successfully opened and that
contains valid transaction data. To start a transaction analysis, select the Run | Transaction
Analysis function in the TSAT main menu. Once the transaction analysis is started, it is applied
to all scenarios with the transaction data in the active TSAT case, unless the scenario is disabled
by setting its action field to Don’t Run.
During a transaction analysis, you can always pause/continue or stop the computation by
selecting appropriate functions from the TSAT main menu. Refer to Section 4.3.1 for details.
7.2 Monitoring Transaction Analysis
After a transaction analysis is started, the following will happen in the TSAT main window.
By default, the computation progress page is set for the basecase

analysis. It is automatically switched for the transaction analysis when
a transaction analysis starts. The default can be changed to the
transaction analysis format by selecting the Transaction Analysis from
the Display combo list located on the tool bar (shown at the right side).
The computation progress bars on the left half of the page show the computation progress. When
a scenario is being processed, the bar is gradually being filled with blue colour, with a text string
under the bar indicating the contingency being processed. When the distributed computation
feature is enabled with multiple engine servers available, multiple scenarios may be processed
simultaneously. This is visible when multiple bars show simulation progress.
The plots on the right half of the page monitor the relative generator rotor angles from the
simulation and the limit search progress as described in Figure 3-8. The relative generator rotor
angles are plotted for those generators specified in the monitor data of the scenario (the
specification of the reference generator is described in Section 5.2). Two spinners are available
below the rotor angle plot, one for selecting a contingency and the other for selecting a
powerflow iteration.
The time axis (x-axis) of the rotor angle plot is automatically scaled to be the simulation length
specified for the contingency. If the early termination option is enabled for the simulation, the
simulation may end before it reaches the full simulation length specified. The power axis (x-axis)
of the limit search progress plot is automatically scaled to be from 0 (base powerflow level) to the
maximum power transfer increase required for the transaction.

TSAT User Manual
Occasionally, the required power transfer increase may not result in a solvable powerflow. In this
case, the range of power transfer increases for which powerflow does not converge will be
coloured in red on the limit search progress plot (as shown in Figure 7-1). If the limit search for a
contingency is terminated as a result of either the dependent or the independent variable hitting
the dispatch limit (defined in the Transfer File), the range of power transfer increases beyond
these limits are coloured in yellow and orange, respectively, on the limit search progress plot.
Figure 7-1 shows a typical computation progress page after the analysis is completed for a
scenario.
Only one iteration is

A full search for the required for subsequent
first contingency contingencies
Power transfer
increase range without
solvable powerflow
Figure 7-1: Computation progress page for transaction analysis
Before the transaction analysis starts, only two fields are populated on the result summary page
for each scenario: Cont No. and Contingency Description (if this page shows the basecase
analysis format, you may change it to the transaction analysis format using the method described
for switching the computation progress page format).
After the analysis is completed for a contingency in a scenario, the limit search results are shown
in the appropriate fields on the result summary page:
• The value in the “Transfer At The Last Secure Level (MW)” field shows the maximum
secure power transfer level for the contingency.
• The value in the “Monitored Interface Flow (MW)” field shows the flow in the monitored
interface (defined in the interface and circuit file in transaction data) at the maximum secure
power transfer level for the contingency.

TSAT User Manual
• Depending on the security indices specified, some or all of the index fields will be filled. The
value shown again corresponds to the maximum secure power transfer level for the
contingency.
During the analysis for a scenario, all completed contingencies are always listed together at the
beginning of the table, sorted by the “Transfer At The Last Secure Level (MW)” field.
Figure 7-2 shows a typical result summary page after the analysis is completed for a scenario (in
this figure only the transient stability and transient frequency indices were specified and thus
shown).
Figure 7-2: Result summary page for transaction analysis
On the Scenario Table
After the first powerflow iteration is completed for the first contingency, the Transaction Analysis
| Base field in the scenario table is filled up with the dependent value of the transaction obtained
from the base powerflow.
When the entire analysis is completed for a scenario, the Transaction Analysis | Limit field is
updated with the computed power transfer limit. This limit is interpolated as the average of the
last secure power transfer and the first insecure power transfer. If the value in the Limit field is
less than the value in the Increase field, the limit is shown in red.
The green bar starts moving, indicating that the computation engine is processing the case.
7.3 Examining Transaction Analysis Results

TSAT User Manual
Similar to the basecase analysis, the results from the transaction analysis can also be examined
and analyzed in three levels:
the analysis for all contingencies in all scenarios. Particularly, the maximum power transfer
level, monitored interface flow, and all security indices for each contingency are included on
the result summary page.
(2) From the transaction analysis details dialog: On the result summary page, additional results
are available for each contingency, by double-clicking on the contingency. A dialog shown in
Figure 7-3 opens up. This dialog shows the limit search iteration summary for the
contingency.
Use the slider to select

another contingency
Figure 7-3: Transaction analysis details dialog
(3) In the DSAOA module: You can examine all monitored simulation results in the DSAOA
module for up to two iterations saved during a transaction analysis. Refer to Section 3.6 on
the description of these binary result files. You can also examine all messages in the DSAOA
module. Refer to DSAToolsTM DSAOA Manual for details on using the DSAOA module.
The transaction analysis results (power transfer limits) are also written to the computation result
summary file. Refer to Section 9.1 for details on creating this file.
Up to two powerflow dispatch files are created after transaction analysis in either PSF/PFB or
PSS/E RAWD format. Refer to Section 3.6 for details on these power dispatch files (including the
load models).

TSAT User Manual
and/or after the transaction analysis.

TSAT User Manual
8 Performing Other Analyses
This section describes the methods for performing the exciter step response test, the governor step
response test and the no disturbance test.
8.1 Performing Exciter Step Response Test
The basic concepts of the exciter step response test are explained in Section 3.5.3.
8.1.1 Starting Exciter Step Response Test
Before starting an exciter step response test, all computation parameters must be specified
The exciter step response test can be performed for any TSAT scenario that is successfully
opened. To start an exciter step response test, a scenario must be first selected from the TSAT
scenario table, and then select the Run | Exciter Step Response Test … function in the TSAT
main menu, this will launch a dialog shown in Figure 8-1.
Figure 8-1: Exciter step response test dialog
In this dialog, the “Available Generator Buses” list box contains all generator buses available in
the system after applying all filters. Any generator bus in this list can be selected and added to the
“Selected Generator Buses” list box. Similarly, any generator in the “Selected Generator Buses”
list box can be selected and removed from the list. Note that if a generator does not have an
exciter model, its exciter step response will not be computed even if the generator is added to the
“Selected Generator Buses” list.

TSAT User Manual
The options of the exciter step response test can also be specified in this dialog:
• Step To Be Added At AVR Reference: the magnitude (in pu) of the step change to be
applied at the voltage regulator reference point. This step is always applied at 1 second in
the simulation.
• Simulation Length: TSAT assumes the generator terminal voltage at the end of the
simulation as the steady state value (VS). So the simulation length should be long enough
for the generator to reach steady state. It is recommended that the simulation length be no
shorter than 10 seconds. Since the step is always applied at 1 second and the time
window for the Prony analysis (to compute modal information from the responses) is set
to be the last 5 seconds of the simulation, the simulation length must be longer than 6
seconds.
• Generator Output: this sets the initial output of the generator:
Open Circuit: the generator will be set to operate in open circuit condition.
Powerflow Condition: the generator will be set to operate in the Single-Machine-

Infinite-Bus (SMIB) condition. The initial P, Q outputs are set as in the powerflow of
the scenario.
Rated MVA: the generator will be set to operate in the Single-Machine-Infinite-Bus

(SMIB) condition. The initial output of the generator is set to be the rated MVA and
the power factor can be specified by you.
• Generator Terminal Voltage: this sets the initial voltage of the generator and is applied
to both open circuit condition and the SMIB:
Voltage of x PU: the generator initial voltage will be set at a value specified by you.
Powerflow Voltage: the generator initial voltage will be the same as in the
powerflow of the scenario.
Once the above options are specified, you can click Run button to start the exciter step response
test.
During the simulation, you can always pause/continue or stop the computations by selecting
8.1.2 Monitoring Exciter Step Response Test
After an exciter step response test is started, the following will happen in the TSAT main
window.
The computation progress bar on the left half of the page shows the computation progress.

TSAT User Manual
• Generator terminal voltage magnitudes
• Generator field voltages
The quantities plotted are of those generators specified in the “Selected Generator Buses” list.
After an exciter step response test is completed, the main characteristics of the response are
calculated for each selected generator and shown in the appropriate fields on the result summary
page.
Figure 8-2 shows a typical result summary page after an exciter step response test is completed.
Figure 8-2: Result summary page example for an exciter step response test
There are two assumptions in the calculations of the main characteristics:
• If a voltage has not settled at the end of the simulation, a settling time of 9999.9 seconds
will be displayed.
• If there is no significant voltage variation during the last 5 seconds of the simulation, a
damping factor of 100% and a frequency of 0 Hz will be displayed.
The green bar starts moving, indicating that the computation engine is processing the test.
8.1.3 Examining Exciter Step Response Test Results
The results from the exciter step response test can be examined and analyzed in two levels:
(1) On the computation progress and result summary pages: these pages show the summary of
the analysis for all selected generators.

TSAT User Manual
(2) In the DSAOA module: you can examine the simulation results of all processed generators
and all messages in the DSAOA module. Refer to DSAToolsTM DSAOA Manual for details
on using the DSAOA module.
The exciter step response test results (the main characteristics of the step responses) are also
written to the computation result summary file. Refer to Section 9.1 for details on creating this
file.
and/or after the exciter step response test.
8.2 Performing Governor Step Response Test
The basic concepts of the governor step response test are explained in Section 3.5.4.
8.2.1 Starting Governor Step Response Test
Before starting a governor step response test, all computation parameters must be specified
The governor step response test can be performed for any TSAT scenario that is successfully
opened. To start a governor step response test, a scenario must be first selected from the TSAT
scenario table, and then select the Run | Governor Step Response Test … function in the TSAT
main menu, this will launch a dialog shown in Figure 8-3.
Figure 8-3: Governor step response test dialog
In this dialog, the “Available Generator Buses” list box contains all the generator buses available
in the system after applying all filters. Any generator bus in this list can be selected and added to

TSAT User Manual
the “Selected Generator Buses” list box. Similarly, any generator in the “Selected Generator
Buses” list box can be selected and removed from the list. Note that if a generator does not have a
governor model, its governor step response will not be computed even if the generator is added to
the “Selected Generator Buses” list.
The options of the governor step response test can also be specified in this dialog:
• Simulation Length: TSAT assumes that generators reach steady state at the end of the
simulation for this test. Considering that governor responses are generally slow, the
simulation length should be sufficiently long for generators to reach steady state. It is
recommended that the simulation length be no shorter than 50 seconds. For the same
reason as the exciter step response test, the simulation length must be at least 6 seconds.
• Response Calculation Type: you can specify the type of simulations to be performed:
Add A Step of x PU to Reference Point: the generator will be set to operate in the
Single-Machine-Infinite-Bus (SMIB) condition. The initial P, Q outputs are set as in
the powerflow of the scenario. A step will be applied to the reference point of its
governor.
Load Rejection of x% of Powerflow Loading: the generator will be set to operate

in an island to feed a load. The initial P, Q outputs are set as in the powerflow of the
scenario. A specified percentage of its load will be shed.
Once the above options are specified, you can click Run button to start the governor step
response test.
During the simulation, you can always pause/continue or stop the computation by selecting
8.2.2 Monitoring Governor Step Response Test
After a governor step response test is started, the following will happen in the TSAT main
window.
The computation progress bar on the left half of the page shows the computation progress.
• Generator speeds
• Generator mechanical torques
The quantities plotted are of those generators specified in the “Selected Generator Buses” list.

TSAT User Manual
After the computation is completed, the main characteristics of the response are calculated for
each selected generator and shown in the appropriate fields on the result summary page.
Figure 8-4 shows a typical result summary page after a governor step response test is completed.
Figure 8-4: Result summary page example for a governor step response test
Figure 8-5 shows a typical result summary page after a partial load rejection test is completed.
Figure 8-5: Result summary page example for a load rejection test
There are two assumptions in the calculation of the main characteristics:
• If the generator has not settled at the end of the simulation, a settling time of 9999.9
seconds will be displayed.
• If there is no significant variation during the last 5 seconds of the simulation, a damping
factor of 100% and a frequency of 0 Hz will be displayed.
8.2.3 Examining Governor Step Response Test Results
The results from the test can be examined and analyzed in two levels:

TSAT User Manual
the analysis for all selected generators.
(2) In the DSAOA module: you can examine the simulation results of all processed generators
and all messages in the DSAOA module. Refer to DSAToolsTM DSAOA Manual for details
on using the DSAOA module.
The test results (the main characteristics of the step responses) are also written to the computation
result summary file. Refer to Section 9.1 for details on creating this file.
and/or after the test.
8.3 Performing No Disturbance Test
The basic concepts of a no disturbance test are explained in Section 3.5.5.
8.3.1 Starting No Disturbance Test
Before starting a no disturbance test, all computation parameters must be specified appropriately
(refer to Section 5.2.1 for details on specifying computation parameters).
No disturbance test can be performed for any TSAT scenario that is successfully opened. To start
a no disturbance test, a scenario must be first selected from the TSAT scenario table, and then
select the Run | No Disturbance Test … function in the TSAT main menu, this will launch a
dialog as shown in Figure 8-6.
Figure 8-6: No disturbance test dialog
The following parameters can be specified in this dialog for a no disturbance test:
• Simulation Length
• Simulation Step Size
• Integration Method
Refer to section 3.2 for details of these parameters. It should be noticed that the contingency file
of the scenario is ignored in a no disturbance test.

TSAT User Manual
Once the options are specified, you can click OK button to start the test.
During the test, you can always pause/continue or stop the computation by selecting appropriate
functions from the TSAT main menu. Refer to Section 4.3.1 for details.
8.3.2 Monitoring No Disturbance Test
After a no disturbance test is started, the following will happen in the TSAT main window.
Figure 8-7 shows a typical computation progress page when the no disturbance test is in progress.
• Relative generator rotor angles (the specification of the reference generator is described
in Section 5.2)
• Bus voltage magnitudes
The quantities plotted are those specified in the monitor data of the scenario.
Up to ten generators with the largest speed deviations will be listed on the left half of the page.
The number in the bar shows the speed deviation of each generator in radius per second. The text
string under the bar indicates the generator and the time that the maximum speed deviation
occurs. When the no disturbance test is in progress, the list will be automatically updated.
Generator Maximum speed deviation

occurring time
Maximum speed
deviation (rad/s)
Figure 8-7: Computation progress page for no disturbance test

TSAT User Manual
It should be noticed that any generator in the system can be picked up by the program, not
necessarily be the generators specified in the monitor data.
After the computation is completed, the generators with the largest relative angle deviations are
shown on the result summary page.
Figure 8-8 shows a typical result summary page after a no disturbance test is completed.
Figure 8-8: Result summary page example for no disturbance test
8.3.3 Examining No Disturbance Test Results
The results from a no disturbance test can be examined and analyzed in two levels:
the analysis.
(2) In the DSAOA module: you can examine all monitored simulation results and all messages in
the DSAOA module. Refer to DSAToolsTM DSAOA Manual for details on using the DSAOA
module.
The test results are also written to the computation result summary file. Refer to Section 9.1 for
details on creating this file.

TSAT User Manual
and/or after the test.

TSAT User Manual
9 Other Features
This section describes the miscellaneous features available in TSAT.
9.1 Saving Results As ASCII Text Files
After an analysis (basecase analysis, transaction analysis, etc.) is completed in TSAT, the security
assessment results (i.e., those available on the result summary page and the result details dialogs
of the TSAT main window) are automatically saved in the following ASCII text file(s):
xxxx_base.txt for basecase analysis results

xxxx_tran.txt for transaction analysis results
xxxx_excstep.txt for exciter step response test results
xxxx_gvstep.txt for governor step response test results
xxxx_nodist.txt for no disturbance test results
You may also manually create a text result summary file by selecting the File | Reports function
in the main menu. A dialog box similar to that in Figure 9-1 will appear with types of available
results shown. All selected types of results will be written to the same output file you specify.
Figure 9-1: Creating ASCII text result summary file

TSAT User Manual
9.2 Program Help
TSAT manuals can be accessed within the TSAT program under the Help menu. The following
manuals are available:
• TSAT User Manual

• TSAT Model Manual
• DSATools UDM Manual
• DSATools DSAOA Manual
In UDM Editor, a context sensitive help system is available. This help is available at the main
menu and also in each control/end block property dialog.
The DSATools DSAOA Manual can also be accessed within the DSAOA program.

TSAT User Manual
9.3 Program Message Handling
TSAT creates messages when certain conditions happen during case file reading, simulation
engine execution, powerflow solution, and some other operations. These messages are stored in
the message buffer and can be viewed by selecting the View | Messages function in the main
menu. The message viewer window is shown in Figure 9-2.
Figure 9-2: Message viewer
There are two parts in the message viewer:
(1) Message type selection buttons: these allow you to select the type of messages to view:
• Messages: this stores the informative and abnormal messages created when processing
the case
• Progress: this stores the computation progress messages created in the computation
engine
• Dispatch: this stores the messages created in the powerflow solution
(2) Message window: the message window consists of a few sheets: a General sheet and sheets
for every scenario. The General sheet contains messages when reading the case file, and each
scenario sheet contains specific messages for the scenario.
The message viewer has the following features accessible from its menu:
• Save: the File | Save function saves the message buffer contents of the selected message
type and sheet to an ASCII text file.
• Print: the File | Print function prints the message buffer contents of the selected message
type and sheet.

TSAT User Manual
• Clear contents: the File | Clear Page function clears up the message buffer of the
selected message type and sheet, and the File | Clear All function clears up the entire
message buffer for the case. Once the messages are cleared up, they cannot be recovered
again.
• Update: the File | Update function updates the message display. While the message
viewer is opened, the messages displayed are not changed even if new messages are
created, unless the message update function is performed.
• Message filter: the Tools | Filter function can be used to limit the messages in the
window to specific messages. The filtering can be based on message type (Error,
Warning, or Notice), and/or specific text strings (up to two strings can be searched). The
filter specifications can be entered in the dialog box shown in Figure 9-3.
Figure 9-3: Message filter
• Message filter: the Tools | Search function can be used to find specific messages in the
specified message. This function uses the standard Windows Find dialog, and its
operation should be straightforward.
When TSAT is running in the off-line batch mode (using the Case Scheduler or the batch
version), all messages are automatically written to the following ASCII text files:
xxxx_msg.out for message information of all scenarios

xxxx_prg.out for progress information of all scenarios
xxxx_disp.out for dispatch information of all scenarios
Important
To reduce the volume of messages, the default message filter setting in the message viewer
window is to exclude all Notice messages (as shown in Figure 9-3). This should in most cases be
able to catch important messages. However, when you run a new case for the first time, it is

TSAT User Manual
strongly recommended that you take a look at the entire messages to ensure that no any real
problems are missed.
The message files created in the batch mode do include all messages.

TSAT User Manual
9.4 Using the Case Scheduler
TSAT provides a batch operation mode which is able to queue and to run sequentially a number
of cases. This can be done using the Case Scheduler program (scheduler.exe) included in the
TSAT distribution. To run TSAT in batch mode, follow these steps:
(1) Create a folder named ems under the TSAT folder where TSAT and the Case Scheduler
executables are located. Leave this folder empty.
(2) Start TSAT and select the Auto | Enable function without a case opened. This will put TSAT
in the batch mode and effectively disable all controls in the TSAT main window (except for
disabling the Auto function and for examining the TSAT servers if the distributed
computation manager is installed).
(3) Start the Case Scheduler. A dialog shown in Figure 9-4 appears.
(4) Use the Add Case and Remove functions in the Case Scheduler to specify the cases to be run
sequentially. At any time, you may press the Test button to check the validity of the cases
included.
(5) Pressing the Start button to start the batch processing. Again, during the batch processing, all
controls in TSAT are disabled.
Figure 9-4: Case Scheduler dialog
A few notes for the TSAT batch mode operation:
• The Case Scheduler works also for SSAT and VSAT.

TSAT User Manual
• You will need to specify the TSAT installation folder when using the Case Scheduler for
the first time. To do so, press the Options button. In the Options dialog, you can also
specify that TSAT outputs the case archive when simulation is finished.
• If you want to stop a batch job, press the Stop button in the Case Scheduler dialog. The
case being run in TSAT will be stopped and the Case Scheduler will not submit any
further cases to TSAT.
• During the batch processing, you may add new cases to the case list, remove any
unprocessed cases from the case list, or change the order of the unprocessed cases.
However, you cannot remove, or change the order of, the cases that have already been
processed.
• During the batch processing, the Case Execution Summary list box in the Case Scheduler
dialog shows the progress of the cases being processed.
• When a case is completed, all messages from TSAT are automatically written into the
messages files as described in Section 9.3.
• A Delay Time for each case can be set by selecting a case in the list and pressing the
Delay Time button. The Delay Time Editing window will appear (Figure 9-5). By
adjusting the sliders, delay time can be set to any value up to 23 hours 59 minutes. This
Delay Time is the minimum amount of time that must pass before the case is submitted to
TSAT. Once this time passes, the case will be submitted as soon as TSAT becomes
available.
Figure 9-5: Changing the Delay Time for a case in the Scheduler

TSAT User Manual
9.5 Distributing TSAT Computation
If the distributed computation manager is included in your TSAT version (i.e., the View | Servers
function in the main menu is enabled and the icon is on the tool bar), you can distribute the
TSAT computations among multiple computer servers in a local network.
Principle
The TSAT computation can be distributed over a local area network consisting of a TSAT client
and multiple TSAT servers, as shown in Figure 9-6.
Client
Server Server Server
Figure 9-6: Client and servers for TSAT distributed computation
By default, a server (called the local server) is always attached to the TSAT client. Therefore,
TSAT should run with its local server without needing installing any additional servers in the
network. The local server can, however, be disabled if remote server(s) are available in the
network. Servers can be installed in any networked computers running Microsoft Windows
system, including the TSAT client computer. Multiple servers can be installed on a single
computer (this makes sense if the server computer has multiple CPUs or cores).
TSAT computations can be distributed only at the scenario level (regardless how many
contingencies are included in each scenario). In other words, if a case has only one scenario, it
will be run entirely on one server. There is an option in the on-line version of TSAT that enables
distributed computation at the contingency level.
For a multi-scenario case, scenarios will be distributed among all available servers. The following
example shows how scenarios are typically distributed.
Assume that a case contains five scenarios and there are three servers available. When a TSAT
analysis (for instance, basecase analysis) is started, the first three scenarios will be distributed
among three available servers. The server on which a scenario is completed first will then pick up
the fourth scenario, and the fifth scenario will be submitted to the next server that becomes
available after finishing its computations.

TSAT User Manual
When the computations are completed, results obtained from remote servers are sent to the client
and consolidated. The resulting binary result file should be in the same format as produced by the
non-distributed version of TSAT.
In order to have reasonable speed performance when TSAT computations are distributed, it is
recommended that the computer network speed should be at 10 Mbit/s or higher.
To run TSAT in distributed mode, the protection dongle should only be inserted at the client
computer.
Client and server installation
The TSAT distribution package should be installed on the TSAT client. The folder where the
TSAT client is installed is called “TSAT folder” or “TSAT client folder”. There is a subfolder
\server under the TSAT client folder, called “TSAT server folder”. This subfolder contains all
files for the TSAT server. Both the TSAT client and server should be ready to run on the client
computer after the TSAT installation.
To install the TSAT servers on other computers, create a folder (“remote TSAT server folder”) on
the computer to which a server is to be installed, and then copy all files from the TSAT server
folder to the remote TSAT server folder.
Running TSAT servers
To start a TSAT server, double-clicking on the TSAT server executable, TSATServer.exe. A

server dialog shown in Figure 9-7 appears.
When there is no computation being run on a server, the server executable uses very little system
resource. Therefore, it does not hurt to have a server idle on a computer.
To terminate a TSAT server, simply close the server dialog.
Figure 9-7: Server window
Setting up client/servers and running distributed computations

TSAT User Manual
In a computer network, there might be multiple TSAT clients and servers running at a given time.
It is sometimes required to configure these clients and servers so that they work in a coordinated
way. For example,
• The on-line TSAT system usually needs dedicated clients and servers, and they should not
interfere with any off-line TSAT installations in the network.
• It may be desirable that a TSAT client uses servers only on computers available for common
use, rather than those assigned to individual persons.
The above can be done with appropriate client/server configuration, as described in the following.
On the client side, you can set up a server list file to specify the servers to which the client can or
cannot talk. The server list file must be named “ServerList.ial” and must be located in the TSAT
program folder (a sample file is included in the TSAT release package). This file has two data
sections, {Allowed Addresses} and {Restricted Addresses}, as shown below:
{Allowed Addresses}
123.45.67.890:6055 / Specific Server (6055) running on this machine
123.45.67.890:* / Port Wildcard - Any server running on this machine
123.45.67.*:* / IP Wildcard - Any server running on this subnet
123.45.*.*:* / IP Wildcard - Any server running on this subnet
"Comp1234":* / IP Name aliases must be enclosed in double quotes
{Restricted Addresses}
987.65.43.210:6055 / Specific Server (6055) running on this machine
987.65.43.210:* / Port Wildcard - Any server running on this machine
987.65.43.*:* / IP Wildcard - Any server running on this subnet
987.65.*.*:* / IP Wildcard - Any server running on this subnet
"Comp9876":* / IP Name aliases must be enclosed in double quotes
When the server list file is set up, you can enable it by selecting the check box labelled “Enable
Server List” in the View Servers dialog (Figure 9-8).
Find new servers Add new server
Toggle server
Configure
server list
Enable/disable
local server
Figure 9-8: View Server dialog

TSAT User Manual
Three options are available:
• “Use Allowed Servers”: the current TSAT client will use only the servers listed in the
{Allowed Addresses} section of the server list file. Exception: if any of the servers listed
have been instructed to reject the current client (see server configuration below), those
servers are not used for distributing simulations.
• “Use Allowed Servers (Excluding Restricted)”: the current TSAT client will use only the
servers listed in the {Allowed Addresses} section of the server list file. In addition, it will
reject any servers listed in the {Restricted Addresses} section. Exception: if any of the
servers listed in the {Allowed Addresses} section have been instructed to reject the current
client (see server configuration below), those servers are not used for distributing simulations.
• “Use All Servers (Excluding Restricted)”: the current TSAT client will use any servers in the
network but those listed in the {Restricted Addresses} section of the server list file.
Exception: if any of the servers in the network have been instructed to reject the current
client (see server configuration below), those servers are not used for distributing simulations.
If the “Enable Server List” check box is not selected, the current TSAT client will use any server
in the network for distributing the simulations, except for those servers that are instructed to reject
the current client (see server configuration below).
In addition to the above configuration, the View Server dialog has a couple of other functions:
• The server list available to the current client can be refreshed by using the Find New Servers
button or by Add New Server button (this is required when multiple servers are available
from one IP address).
• The local server of the current TSAT can be disabled (thus all simulations will be done at
remote servers). This can be handy if you do not want the local PC to be loaded with
simulations.
There are two important flags for a server:
• Status: either Free or Busy. This indicates if the server is available for the client or it is
already being used by another client. Obviously, the server will not be available to the client
if it is already being used by another client. This status cannot be controlled by the client.
• State: either Enabled or Disabled. This indicates if the server should be used (if it is
available) for the client. A server can be disabled by double-clicking on the server row, or
selecting the server and then pressing the Toggle Server button. This provides an additional
level of server configuration.
On the server side, there is a client list file that you can set up to specify the clients to which the
server can or cannot talk. The client list file must be named “SvrAddressList.ial” and must be
located in the TSAT server folder (a sample file is included in the TSAT release package). This
file has two data sections with the similar syntax to those in the server list file.
When configuring servers, six check boxes are available on the Server window (Figure 9-7):

TSAT User Manual
• Enable Server: when this is not selected, the server is disabled for any client
• Local Client Only: when this is checked, the server is available only to the clients on the
same IP address
• Online Clients: when this is checked, the server is available only to clients set in online mode
(i.e., the Auto option is enabled)
• Offline Clients: when this is checked, the server is available only to clients set in offline
mode (i.e., the auto option is disabled)
• Use Allowed Clients Only: when this is checked, the server is available only to those clients
listed in the {Allowed Addresses} section of the client list file.
• Reject Restricted Clients: when this is checked, the server is not available to those clients
listed in the {Restricted Addresses} section of the client list file.

TSAT User Manual
9.6 TSAT Snapshot
Normally a TSAT simulation starts from a steady state (denoted as time=0). The initial condition
of the system at time=0 is specified by the powerflow data and all the initial states of the system
are calculated during the system initialization (refer to section 3.2 for principles of time domain
simulations).
Instead of starting a simulation from time=0, TSAT snapshot allows you to save an intermediate
system state (i.e., a snapshot of the system) during a simulation, and start separate simulation(s)
from this intermediate state.
Taking a snapshot
You need to specify the action of taking a snapshot in the contingency file. Refer to TSAT Model
Manual for details of the command of taking a snapshot.
A snapshot can be taken at any time during a simulation. However no other switching event is
allowed at the time when a snapshot is taken. For example, the contingency shown in Figure 9-9
includes an action to take a snapshot at time = 5 seconds between the two three-phase faults as
shown in Figure 9-10 (it would not be allowed if any switching event occurs at 5 seconds). A
snapshot is saved with a file named “xxxx.tsn”, where xxxx is the file name specified in the
Snapshot command in the contingency (in the above example, the file name will be “SS.tsn”).
Figure 9-9: TSAT snapshot command

TSAT User Manual
Bus voltage magnitude (pu)

1.10
0.92
0.74
Take a snapshot
and save to
0.56
“SS.tsn”
0.38
0.20
0.00 2.50 5.00 7.50 10.00 12.50 15.00 17.50 20.00
Time (sec)
Figure 9-10: Taking a TSAT snapshot
Opening a snapshot
A snapshot can be opened in two ways: in the TSAT main menu (described in Section 4.3.1) or in
a contingency file (refer to TSAT Model Manual for the details on loading a snapshot in a
contingency file).
Running simulation from a snapshot
Opening a snapshot submits a special case to the TSAT simulation engine. This case contains a
single scenario and a single contingency. Notice that only the basecase analysis option is
available to this case. A snapshot file contains all the information necessary for continuing a
simulation for the contingency saved in the snapshot. The simulation can be started by selecting
the Run | Basecase Analysis function in the TSAT main menu, and TSAT will output the same
results as if the simulation starts from time = 0. Note that the results between time = 0 and the
time at which the snapshot is taken (TSNAP, in the example shown in Figure 9-9 and Figure 9-10,
TSNAP=5 seconds) are stored in the snapshot file. TSAT just “loads” them instead of “simulating”
them when the contingency is restarted.
After a snapshot is opened, you cannot do any modifications to this special case, except for the
following:
• Change the descriptions of the case.

TSAT User Manual
• Edit the contingency details and/or add new contingencies. This is one of the powerful
features for using the snapshot.
Modifying the contingency data of the snapshot
After a snapshot is opened, you can modify the contingency data by double clicking the scenario
in the scenario table and choose Contingency Data in the Scenario Data editing dialog. You can
work on the contingency included and/or add new contingency.
A few notes for working on the existing contingency and/or adding new contingencies to a TSAT
snapshot:
• Any switch commands added prior to TSNAP will be ignored.
• The simulation length of a contingency must be longer than TSNAP.
• When adding a new contingency, the simulation results between time = 0 and TSNAP will
be the same as those from the contingency for which the snapshot is taken.
• The integration method and step size can be changed, but they will only take effect after
TSNAP.
Viewing the powerflow at time = 0
After a snapshot is opened, the powerflow at time = 0 (i.e. the powerflow provide to the original
scenario for which the snapshot is taken) can be examined by selecting View | Powerflow Data
function in the TSAT main menu. It should be noticed that the snapshot file does not include the
powerflow data at time = 0. TSAT simply tries to open the powerflow file specified in the
original scenario. Modifying this powerflow will not have any effect on the snapshot.
Viewing the powerflow at TSNAP
When TSAT saves a snapshot to xxxx.tsn, a powerflow file named xxxx.raw is also saved. The
powerflow file is in PSS/E RAWD Rev. 26 format. This file contains the powerflow condition at
TSNAP. You can load this powerflow in a powerflow program to examine the system condition at
TSNAP (such as voltages, branch flows, etc.). Note the following when using this powerflow:
• The powerflow should be solved. In fact, you can use it in a totally new TSAT case.
• Some powerflow data that is not used in simulations but essential for powerflow solution
is not written back to this powerflow. Therefore, do not try to solve the powerflow again.
• For the same reason, modifying this powerflow is not recommended since it is unlikely to
be solved. However, modifying this file will not have any effect on the snapshot.
Viewing the dynamic data
After a snapshot is opened, the dynamic data can be opened by selecting View | Dynamic Data
function in the TSAT main menu. It should be noticed that the snapshot file does not include the

TSAT User Manual
dynamic data at time = 0. TSAT simply tries to open the dynamic files specified in the original
scenario. Modifying the dynamic data will not have any effect on the snapshot.
Model compatibility of TSAT snapshot
TSAT snapshot supports all dynamic models in the native format of DSAToolsTM and most
dynamic models in third party formats (such as PTI PSS/E, GE PSLF, and BPA), as well as User-
Defined Models which contain standard control blocks. However dynamically linked control
blocks (DLB) are generally not supported. Refer to TSAT Model Manual and DSAToolsTM UDM
Manual for details.

TSAT User Manual
9.7 Configuring Text Editor
To facilitate the editing of TSAT data files, you can configure your preferred text editor for use
within TSAT. To do this, select the Options | Configure Text Editor function in the main menu.
A dialog shown in Figure 9-11 appears. You can specify the editor executable (Windows Notepad
by default) and any special command line options for the editor (blank by default).
Figure 9-11: Configuring a text editor
You can edit data files in a case (except for powerflow and dynamic data) using the editor after
the case is opened. The data file can be selected from the File | Edit Files menu in the main
TSAT menu. Note that if a change is made to one of the files and you exit the editor, TSAT
automatically reload the case in order for the case settings to remain consistent with the data files.
This has the effect of clearing the plot windows and program messages. It is recommended
therefore that you save all desired results before editing a file. If no changes are made to the
edited file, TSAT does not reload the case, and thus all current results remain unchanged.

TSAT User Manual
9.8 Using the TSAT Batch Version
The TSAT batch version can be started from the DOS command line or from another application.
The command syntax is:
tsat_batch case-file-name
In the case file, the Auto Option command should be specified for the required analysis (default is
basecase analysis). Refer to Section 10.1 for details.
TSAT batch version has the same features and modelling capabilities as the GUI version. At the
end of the simulations, the messages and computation progress are automatically saved as output
files.
If there are free TSAT computation servers available in the network, TSAT batch version will use
these servers (if possible) to distribute the computations.

TSAT User Manual
9.9 Creating Plots In Batch Mode
If you need to do any of the following:
• Repetitively create plots of specified quantities from different study cases

• Automatically create large number of plots from specified study cases
• Directly create plots compatible with third party applications (such as Word or
PowerPoint)
• Create plots in batch mode (for example in another application that calls TSAT)
you can use scripts to perform such tasks. The TSAT distribution package includes a DLL
(ResultScript.dll) that contains necessary classes for such applications. Appendix B provides
detailed descriptions of these classes and examples of using these classes in VBScript to create
sample plots.
Once a script has been prepared, use the following procedure to create the plots:
1. Make sure that the COM Objects in ResultScript.dll are registered. This should be done
automatically if TSAT is installed using the standard installation procedure from the
distribution CD. You can however always manually do this by entering the following
command in a DOS command window (issued in the TSAT program folder):
regsvr32 ResultScript.dll
Note: you need to have the administration right on the computer you use to do this.
2. If you want to create plots in Word or PowerPoint format, make sure that MS Office is
installed on your computer.
3. If you are using a scripting language other than VBScript or JScript, you may need to have
the associated scripting engines or software installed. Please consult the scripting language
documents for details.
4. Double click the script file (or executing the script) to create the plots.

TSAT User Manual
9.10 DSAToolsTM Contingency Converter
DSAToolsTM Contingency Converter is a standalone tool for converting contingency data in

various formats to TSAT format. The following formats are supported:
• VSAT (Voltage Security Assessment Tools) contingency data format

• PSS/E MUST contingency data format
• Powerworld contingency data format
• Text format for N-1 contingencies
• Text format for N-2 contingencies
Refer to DSAToolsTM Contingency Converter Manual for details.

TSAT User Manual
10 Appendix A – TSAT Case File Format
This appendix describes the format of TSAT case file. The objective is to explain the TSAT case
file structure and various options available, so you can understand it. It is, however,
recommended that you modify a TSAT case always using the Case Wizard (refer to Section 5)
rather than editing the case file directly. This can effectively avoid possible mistakes causing the
rejection of the case by TSAT.
10.1 Concept, Rules, and Structure
The following are the basic rules of TSAT case file:
• It is an ASCII text file.
• Most of the contents are case-insensitive except for
file names
any text descriptions
any system information such as bus names and IDs.
• Any line starting with a slash / will be treated as a comment line. Blank lines are ignored.
• The first line of a case file must be the program identifier:
[TSAT 8.0]
where the version number (8.0) may change in different releases.
• TSAT case file has the default file extension .tsa.
• If a data file contained in a TSAT case file is specified with a relative file path (such as
.\data\mydata.dat), the reference is made to the folder where the TSAT case file is
located.
A TSAT case file contains the information necessary to run TSAT, which includes the following:
• Scenario specifications
• Computation parameters
• Input data specifications
• Output files specifications
The above information is organized in two layers:
• The first layer defines the scenarios and the output files for the case.
• The second layer contains all data sections for individual scenarios.
A scenario is a collection of various data sets that are used to perform required analyses in TSAT.
There are two types of scenarios in TSAT:

TSAT User Manual
• Base scenario. The base scenario defines a complete computation case. The following
rules apply to the base scenario:
It must be the first scenario in a case file.

There must be one and only one base scenario in a case file.
All mandatory data must be specified (refer to each data subsections for definition of
mandatory data).
• Subsequent scenario. A subsequent scenario is a computation case derived from the base
scenario. It follows these rules:
If a data set is not specified in a subsequent scenario, the data defined in the base
scenario will be used. In other words, a subsequent scenario can inherit data from the
base scenario. This inheritance does not however apply to
- Computation parameters (refer to Section 10.2.3)
There may be any number of subsequent scenarios in a case file.
Using the above rules, a subsequent scenario can be made to be a derivative computation
case from the base scenario (for example, performing the analysis for the same system
model but using different contingencies), or it can represent a new computation case for a
different system.
Computationally, the base scenario and all subsequent scenarios are treated the same. Note that
the analysis objectives are not specified in a scenario. Any computation functions (basecase
analysis, transaction analysis, etc.) can be applied to any scenarios in a TSAT session, as long as
all required data is provided.
In a TSAT case file, the scenario identifiers in the first layer are as follows:
[TSAT 8.0]
Output Files = output_file_base

Auto option = auto_opt
[Base Scenario]
... ...
[End Base Scenario]
[Scenario]
... ...
[End Scenario]
... ...
... ...
[Scenario]
... ...
[End Scenario]
The Output Files command is optional (the full file path can be included if necessary). If it is
not specified, then the case file name (without its extension) will be taken as the
output_file_base. By running basecase or transaction analysis, a TSAT binary file will be
created with the name output_file_base.bin. A TSAT case cannot be opened if it is
impossible to create a file with this name (this is usually caused by an invalid file path). In
addition, when running transaction analysis, two output powerflow files of the form

TSAT User Manual
output_file_base_xxxx_stable.psf and output_file_base_xxxx_unstable.psf

(or with the *.raw extension) will be created, where xxxx is the scenario number (assigned by
TSAT) with leading zeros.
The Auto Option command is optional; it is used only in the Case Scheduler and TSAT batch
version to specify the required analysis:
Auto Option = basecase to perform basecase analysis

= transaction to perform transaction analysis
In the above, scenarios are not numbered, but a title can be entered for each scenario in the Case
Description data section.
The data structure for each scenario is the same. They constitute the second layer of a TSAT case
file:
{Scenario Description}
... ...
{End Scenario Description}
{Scenario Parameters}
... ...
{End Scenario Parameters}
{Powerflow Data}
... ...
{End Powerflow Data}
{Dynamic Data}
......
{End Dynamic Data}
{Dynamic Representation Data}
......
{End Dynamic Representation Data}
{Monitor Data}
......
{End Monitor Data}
{Switching Data}
......
{End Switching Data}
{Criteria Data}
......
{End Criteria Data}
{Relay Data}
......
{End Relay Data}
{Transaction Data}
......
{End Transaction Data}
{Sequence Network Data}
......
{End Sequence Network Data}
In the above, the order of data sections can be random. If there is no data for one data section, the
section can be ignored. Details of the format for each data section are described in the next
section.
10.2 Data Sections

TSAT User Manual
10.2.1 Scenario Description
This data section is used for visual recognition of the scenario. The format is as follows.
Title = scenario_title
Author = author
Date = date
Descriptions = scenario_description
In the above,
scenario_title
A string for scenario identification. This title is passed to the computation engine
and saved in the binary result file as the first line of the study title.
author A string containing the name of the author who creates the scenario.
date Date and time the scenario is created.
scenario_description
The descriptions of the scenario. This may span multiple lines by using the
continuation mark (%). The first five lines of descriptions will be passed to the
computation engine and saved in the binary result file as study titles.
The following example illustrates the format:
Title = ABC Company Case
Author = John Smith
Date = Mar 10 2002 18:45
Description = %
Base scenario for ABC Company 2005 summer peak load. %
System representation includes all details.
All data in the Scenario Description section is optional for both base and subsequent scenario,
with no default values except for the title. The following default is used for the scenario title:
• For the base scenario, the default is “Base Scenario”
• For any subsequent scenario, the default depends on the base scenario title:
If the base scenario has a non-default title, string “(Scenario x)” is appended to the
base scenario title, where x is the sequential number of the scenario.
If the base scenario has the default title (“Base Scenario”), string “Scenario x” is used
as the default, where x is the sequential number of the scenario.
Every time that the case file is saved, the date information is automatically updated.
10.2.2 Scenario Parameters

TSAT User Manual
This data section is used to specify all computation parameters. The format is as follows.
{Scenario Parameters}
/
Transient security index for base case analysis = value
Stability margin threshold = value
Transient Stability Margin Algorithm = value
Maximum CCT Search Value = value
Minimum CCT Search Value = value
CCT Security Criterion = value
CCT Search Threshold = value
Unit For CCT Calculation Parameters = value
/
Early termination for base case analysis = value
Early termination for transaction analysis = value
Swing Margin Threshold For Stable Early Termination = value
Early termination check threshold = value
Time Window Start For Early Termination = value
Time Window End For Early Termination = value
Swing Margin Threshold For Unstable Early Termination = value
Unstable early termination check threshold = value
Max generator speed deviation allowed = value [PU]
/
Simulation Length Override = value [SECONDS]
Integration Step Override = value [SECONDS]
Integration Method Override = value
/
Power limit search threshold = value [MW]
Transaction analysis search method = value
Per Contingency Transaction Limit Search = value
Reverse Transfer Search = value
/
Lower threshold voltage of nonlinear load = value [PU]
Upper threshold voltage of nonlinear load = value [PU]
Threshold value of zero impedance line = value [PU]
Solution option for generator swing equation = value
Automatic dynamic data correction = value
Common MVA base = value [MVA]
Common frequency base = value [Hz]
Default load model for real power = value
Default load model for reactive power = value
Include Induction Motor In Load Shedding = value
/
Sequence network computation method = value
Primary source for generator impedance = value
/
Enforce Transient Stability For Transaction = value
Enforce Damping For Transaction = value
Enforce Voltage Violation For Transaction = value
Enforce Frequency Violation For Transaction = value
Enforce Rate Of Change Of Frequency For Transaction = value
Enforce Relay Margin For Transaction = value
/
Data Error Correction Level = value
Island Count Threshold = value
{End Scenario Parameters}
The values of the above parameters take one of three forms:
• Numerical form. In this form either an integer or a real number should be provided. A
unit is usually implied for such a parameter, which can also be added after the value.

TSAT User Manual
• Logical form. In this form the value of the parameter is either YES or NO (without
quotes).
• Character string form. In this form a character string should be provided. No quotes
should be used for the string.
Table 10-1 shows the allowable data ranges and default values of all parameters. Note that the
default values listed in Table 10-1 are the original settings in the TSAT distribution package.
They can be customized to any desired values using the method described in Section 5.2.1.
Table 10-1: TSAT parameter table
Parameter Name Data Range Default

Transient security index for MARGIN | CCT MARGIN
base case analysis
Stability margin threshold Positive real number (< 100) 0.0
Transient Stability Margin ANGLE | SWING ANGLE
Algorithm
Maximum CCT Search Value Positive real number 30.0 cycles
Minimum CCT Search Value Positive real number 0.5 cycles
CCT Security Criterion Positive real number 5.0 cycles
CCT Search Threshold Positive real number 0.5 cycles
Unit For CCT Calculation Cycles | Seconds Cycles
Parameters
Early termination for base case NO | YES NO
Early termination for NO | YES NO

transaction analysis
Swing Margin Threshold For Real number 1.0
Stable Early Termination
Early termination check Positive real number 1.0
threshold (used for peak-to-peak angle
check in stable early termination
algorithm)
Time Window Start For Early Positive real number 1.0
Termination
Time Window End For Early Positive real number 2.5
Termination
Swing Margin Threshold For Real number -1.0
Unstable Early Termination
Unstable early termination Real number -20.0
check threshold
Max generator speed deviation Positive real number 0.1
allowed
Simulation Length Override Positive real number 0.0
Integration Step Override Positive real number 0.0
Integration Method Override = RK4 | RK2 | ME | TRAP | NONE
NONE NONE
Power limit search threshold Positive real number 20.0

TSAT User Manual
Table 10-1: TSAT parameter table
Parameter Name Data Range Default

Transaction analysis search AUTOMATIC | FIXED | BINARY AUTOMATIC
method
Per Contingency Transaction YES | NO NO
Limit Search
Reverse Transfer Search YES | NO NO
Lower threshold voltage of Positive real number 0.7

nonlinear load
Upper threshold voltage of Positive real number 0.7
nonlinear load
Threshold value of zero Positive real number 0.0001
impedance line
Solution option for generator POWER | TORQUE POWER
swing equation
Automatic dynamic data YES | NO YES
correction
Common MVA base Positive real number 100.0
Common frequency base Positive real number 60.0
Default load model for real MVA | CURRENT | IMPEDANCE CURRENT
power
Default load model for reactive MVA | CURRENT | IMPEDANCE IMPEDANCE
power
Include Induction Motor In Load YES | NO NO
Shedding
Sequence network computation CLASSICAL | SHUNT/LOAD CLASSICAL
method INCLUDED
Primary source for generator SEQUENCE DATA | DYNAMIC SEQUENCE DATA
impedance DATA Xd | DYNAMIC DATA X’d
| DYNAMIC DATA X’’d
Enforce Transient Stability For YES | NO YES
Transaction
Enforce Damping For Transaction YES | NO YES
Enforce Voltage Violation For YES | NO YES

Transaction
Enforce Frequency Violation For YES | NO YES
Transaction
Enforce Rate Of Change Of YES | NO YES
Frequency For Transaction
Enforce Relay Margin For YES | NO YES
Transaction
Data Error Correction Level Positive integer 0
(this parameter is used primarily in on-line
version of TSAT; be cautious when
specifying any value). See note below.
Island Count Threshold Positive integer 0 (when 0, TSAT
calculates the
threshold to be
0.5% of the total
number of buses)
Parameter Data Error Correction Level takes a binary combination of the following flags:

TSAT User Manual
Bit 0: fix governor limits (1 = yes; 0 = no)

Bit 1: fix power factor (1 = yes; 0 = no)
Bit 2: fix MVA rating (1 = yes; 0 = no)
Bit 3: fix SVC (1 = yes; 0 = no)
Bit 4: neglect invalid initial field current
Bit 5: fix bad line drop compensation (1 = yes; 0 = no)
Bit 6: reserved
Bit 7: ignore O/S generators and branches in contingency (1 = yes; 0 = no)
Bit 8: allow inconsistent switchable shunt initial value (1 = yes; 0 = no)
Bit 9: disconnect generators isolated during simulation (1 = yes; 0 = no)
Bit 10-31: reserved
Reserved bits should not be used.
Example: if the following options are to be enabled:
• Fix governor limits

• Fix MVA rating
• Fix SVC
• Disconnect generators isolated during simulation
The value for this parameter would be set to 1+4+8+512=525.
Parameter Island Count Threshold takes effect only when bit 9 for parameter Data Error
Correction Level is set to yes.
The default value of a parameter is determined depending on the information provided for the
parameter:
• If the parameter does not appear in the scenario parameter data section for a scenario
(either base or subsequent), or if the parameter appears in an open statement, e.g.
Threshold value of zero impedance line =
the default value is used.
• If the default value is to be used for a parameter, the value in the TSAT initialization file
C:\TSA.INI will be used. The TSAT initialization file is created/updated every time when
customized defaults are saved.
• If there is no TSAT initialization file in your system (i.e., file C:\TSA.INI doe not exist),
the value in Table 10-1 is used.
10.2.3 Powerflow Data
This data section specifies the powerflow data information. The format is as follows.
{Powerflow Data}
Format = format
File = file
Parameter File = param_file

TSAT User Manual
Solution File = sol_file

Control Mode File = CM_file
Solve Base Powerflow = PF_opt
In the above,
format Powerflow format:

= PSF Number PSF/PFB format using bus number identification
= PSF Name PSF/PFB format using bus name identification
= PSS/E RAWD PSS/E RAWD format - Rev. 26 or earlier (bus number
identification)
= PSS/E RAWD 28 PSS/E RAWD format - Rev. 27/28 (bus number
identification)
= PSS/E RAWD 29 PSS/E RAWD format - Rev. 29 (bus number
identification)
identification)
identification)
identification)
= BPA BPA format (bus name identification)
= PSLF EPC PSLF format (bus number identification)
file Powerflow file name, including the path if necessary.
param_file Powerflow solution parameter file to be used when solving the powerflow at the
pre-simulation. Refer to the TSAT Model Manual for the format of this file
sol_file Powerflow solution file. This applies only to powerflow data in BPA format. The
solution provided will be used as the starting point in the TSAT powerflow
solution. The solution file (*.pfo) created by the BPA program should be used.
CM_file Control Mode file that sets the control options for ULTC. The format and usage
of this file is compatible with VSAT Control Mode file. Refer to VSAT user
manual for details on the format and usage.
PF_opt Option to solve base powerflow at the pre-simulation:
= YES To solve the base powerflow
= NO Not to solve the base powerflow
Note that if pre-fault switching events (refer to the switching command At Time
in the TSAT Model Manual) are specified in a contingency, the base powerflow
after applying the pre-fault events is always solved.
The following example illustrates the format with the default values (there is no default value for
file name):
{Powerflow Data}
Format = PSF Name
File = basecase.psf
Solve Base Powerflow = NO
The powerflow data is mandatory for the base scenario. For subsequent scenarios, the powerflow
data of the base scenario is used if it is not specified.

TSAT User Manual
10.2.4 Dynamic Data
This data section specifies the dynamic data information. The format is as follows.
{Dynamic Data}
Format = format
Name Option = name_option
File = file_1
File = file_2
... ...
{End Dynamic Data}
In the above,
Format Dynamic data format:

= DSATools DSATools format (default)
= PSE/E PSS/E format
= PSLF PSLF format
= BPA BPA format
Dynamic data format refers to the format for the base data (for generators and
their controls). It is always possible to include additional data in DSATools
format for special models such as user-defined models, load models, etc. Since
these additional models must be in DSATools format, no additional data format
code is required in this data section.
Name_option Method for component identification:
=0 Bus number (default)
=1 Bus name
=2 Equipment name
file_1, etc. Dynamic data files. Dynamic data can be split in multiple files and entered
separately. All dynamic data files must use the same component identification
method specified. Refer to the TSAT Model Manual for details on the dynamic
data models and formats.
{Dynamic Data}
Format = PSS/E
file = dyn.dat
file = ..\dc\dc_data.dat
file = ..\facts\facts.dat
{End Dynamic Data}
The dynamic data is mandatory for the base scenario (at least one dynamic data file must be
provided). For subsequent scenarios, the dynamic data of the base scenario is used if it is not
specified.
10.2.5 Dynamic Representation Data
This data section specifies the dynamic representation data information. The format is as follows.

File = file
Load Conversion Or Generator Netting File = OP_File

TSAT User Manual
In the above,

= 0 Bus number (default)
= 1 Bus name
= 2 Equipment name
File Dynamic representation data file name, including the path if necessary.
OP_File Load conversion or generator netting file names. These must be in PSS/E IDEV
format containing CONL and GNET commands. Multiple files can be entered.
Note that the order of CONL commands in IDEV scripts is important when
converting loads.
For details on the dynamic representation data format and interpretation, refer to TSAT Model
Manual.

File = dyn_rep.dat
The dynamic representation data is optional for either the base scenario or subsequent scenarios.
The following interpretation is used if this data is not provided:
• For the base scenario, all valid dynamic models read from dynamic data file(s) are used.
• For subsequent scenarios, if the delimiters of this data section are specified and the file
specification statement is open:

File =
all valid dynamic models for this scenario are used . Otherwise, the dynamic
representation data in the base scenario will be inherited.
10.2.6 Monitor Data
This data section specifies the monitor data information. The format is as follows.
{Monitor Data}
File = file_1
File = file_2
... ...
Reference generator = ref_gen
Generator for damping estimate = damp_gen
... ...
{End Monitor Data}
In the above,

TSAT User Manual

=1 Bus name
=2 Equipment name
file_1, etc. Monitor data files. Monitor data can be split in multiple files and entered
separately. Refer to the TSAT Model Manual for details on the monitor data
format.
ref_gen Reference generator for plotting relative generator rotor angles. This is a text
string in which the generator information is entered in the same format as that for
monitoring generator in the monitor data.
damp_gen Generators whose responses are to be used for the minimum damping estimate
algorithm. This is a text string in which the generator information is entered in
the same format as that for monitoring generator in the monitor data. There can
be up to 4 generators specified for damping estimate in one scenario.
{Monitor Data}
File = monitor.dat
Reference generator = ‘ 2 1’
Generator for damping estimate = ‘ 1 1’
{End Monitor Data}
The monitor data (excluding reference generator and generators for damping estimate) is
mandatory for the base scenario (at least one monitor data file must be provided). For subsequent
scenarios, the monitor data and reference generator of the base scenario is used if it is not
specified, but the generators for damping estimate are not inherited.
10.2.7 Switching Data
This data section specifies the switching (contingency) data information. The format is as
follows.
{Switching Data}
File = file_1
File = file_2
... ...
Must-run File = file_M
Don’t-run File = file_D
In the above,

=1 Bus name
=2 Equipment name

TSAT User Manual
file_1, etc. Contingency data file names. Contingency data can be split in multiple files and
entered separately. Refer to the TSAT Model Manual for details on the
contingency data format.
file_M This file contains the Must-Run contingencies. Only one such file is allowed in
the contingency data section. For each contingency, only the Description
command is required (i.e., each Description command is matched with those in
the contingencies to determine the Must-Run contingency list) and the rest of
commands are ignored.
file_D This file contains the Don’t-Run contingencies. Only one such file is allowed in
the contingency data section. For each contingency, only the Description
command is required (i.e., each Description command is matched with those in
the contingencies to determine the Don’t-Run contingency list) and the rest of
commands are ignored.
{Switching Data}
File = switch.dat
Must-run File = must-run.dat
Don’t-run File = dont-run.dat
The contingency data is mandatory for the base scenario (the Must-Run and Don’t-Run files are
optional). For subsequent scenarios, the contingency data (excluding the Must-Run and Don’t-
Run files) of the base scenario is used if it is not specified. If either of the Must-Run and Don’t-
Run files is not specified in a subsequent scenario, the interpretation depends on the information
provided:
• If the file specification statement is missing, the specification for the base scenario is
used for the scenario.
• If the file specification statement is open, the corresponding file is set to null. For
example, if the following statement appears:
Must-run File =
no Must-Run contingencies will be specified for the scenario, even if a Must-Run file is
provided for the base scenario.
10.2.8 Criteria Data
This data section specifies the criteria data information. The format is as follows.
{Criteria Data}
File = file
{End Criteria Data}
In the above,

= 0 Bus number (default)

TSAT User Manual
= 1 Bus name
= 2 Equipment name
File Criteria data file name, including the path if necessary.
For details on the critieria data format and interpretation, refer to TSAT Model Manual.
{Criteria Data}
File = n-1_crt.dat
{End Criteria Data}
The criteria data is optional for either the base scenario or subsequent scenarios. The following
interpretation is used if this data is not provided:
• For the base scenario, only transient stability criteria is checked.
• For subsequent scenarios, if the delimiters of this data section are specified and the file
specification statement is open:
{Criteria Data}
File =
{End Criteria Data}
only transient stability criteria is checked . Otherwise, the criteria data in the base
scenario will be inherited.
10.2.9 Relay Data
This data section specifies the relay data information. The format is as follows.
{Relay Data}
File = file
{End Relay Data}
In the above,
file Relay data file name.
{Relay Data}
File = relay.dat
{End Relay Data}
The relay data is optional for both base and subsequent scenario. If the relay data is not provided
for a subsequent scenario, the interpretation depends on the information provided:
• If the file specification statement is missing, the relay data specified for the base scenario
is used for the scenario.

TSAT User Manual
File =
no relay data will be used for the scenario, even if a valid relay data file is provided for
the base scenario.
Note: the relay data that can be entered in this data section refers to the relay data in TSAT
version 5.1 or earlier. The relay models and data in the current TSAT version should be included
in the dynamic data file, together with the data of other dynamic models.
10.2.10 Transaction Data
This data section specifies the transaction data information. The format is as follows.
{Transaction Data}
Transfer File = trf_file
Parameter File = prm_file
Interface And Circuit File = itf_file
Generator Capability File = gcc_file
Generator Coupling File = ccpp_file
In the above,

=1 Bus name
=2 Equipment name
trf_file Transaction transfer file name. Refer to the TSAT Model Manual for details on
the transfer file format. This file is mandatory for transaction analysis.
prm_file Transaction parameter file name. Refer to the TSAT Model Manual for details on
the parameter file format. This file is optional; if not specified, the parameter file
specified in the powerflow data section (refer to Section 10.2.3) is used. If no
parameter file is specified in the powerflow data section, the default parameters
are used, in which case you should check to ensure that the default parameters
are appropriate for the desired powerflow solution.
itf_file Transaction interface and circuit file name. Refer to the TSAT Model Manual for
details on the interface and circuit file format. This file is optional for transaction
analysis. If it is specified, it should contain an interface definition, which you
wish to have monitored in transaction analysis.
gcc_file Generator capability file name. Refer to the TSAT Model Manual for details on
the generator capability file format. This file is optional for transaction analysis.
If it is specified, it should contain generator reactive power capability data.
ccpp_file Generator coupling file name. Refer to the TSAT Model Manual for details on
the generator coupling file format. This file is optional for transaction analysis.
If it is specified, it should contain generator coupling data for combined cycle
power plants.
{Transaction Data}
Transfer File = transaction.trf

TSAT User Manual
Parameter File = transaction.prm

Interface And Circuit File = tielines.itf
The transaction data is required only for transaction analysis, i.e., if this data is not provided, only
basecase analysis can be performed.
If the transaction data is not provided in a subsequent scenario, the interpretation depends on the
information provided:
• If the file specification statement is missing, the transaction data specified for the base
scenario is used for the scenario.
Transfer File =
no transaction data will used for the scenario, even if a valid transaction file is provided
for the base scenario.
10.2.11 Sequence Network Data
This data section specifies the sequence network data information. The format is as follows.

File = file
Format = format
In the above,
file Sequence network data file name. Refer to the TSAT Model Manual for details
on the sequence network data format.
format = PSS/E. If no format is specified, the format is assumed to be PSS/E.

File = seq-net.dat
The sequence network data is required only for unbalanced fault simulation. Use of sequence
network data follows these rules:
• If dynamic data is provided in BPA format and it includes the sequence network data, the
sequence network data will be used and the data specified in this data section will be
ignored.

TSAT User Manual
• If powerflow data is provided in PFB format and it includes the sequence network data,
the sequence network data in this data section is optional. If provided, it will be used in
simulations; if not provided, the data in powerflow will be used.
• In all other cases, the sequence network data must be provided in this data section if fault
impedance is not provided for an unbalanced fault command in contingency data.
Otherwise, an error will be issued by TSAT.
If the sequence network data is not provided in a subsequent scenario, the interpretation depends
on the information provided:
• If the file specification statement is missing, the sequence network data specified for the
base scenario is used for the scenario.
File =
no sequence network data will used for the scenario, even if a valid sequence network
data file is provided for the base scenario.

TSAT User Manual
11 Appendix B – Using Scripting Language To Perform Batch Plotting
This section describes how to prepare scripts for creating plots in batch mode by using a scripting
language (such as VBScript and JScript). Refer to Section 9.9 for further information on using
such scripts.
11.1 Background
11.1.1 Principles
Batch plotting to create customized T-X and X-Y plots is possible by using scripts. The TSAT
distribution package includes a DLL (ResultScript.dll) that contains necessary classes for such
applications. These classes can be used in a number of scripting languages:
• VBScript
• JScript
• Python
• MATLAB
• Other
Since VBScript and JScript engines are included in MS Windows, these languages are
recommended for preparing batch plotting scripts. Use of other scripting languages requires either
specific scripting engines or software. Please refer to the associated language documents for
details.
The choice of using VBScript or JScript is insignificant: those more familiar with a Visual Basic-
like syntax would probably prefer VBScript, while those more familiar with a C/C++-like syntax
might favor JScript. A full discussion of these languages is beyond the scope of this manual.
Documentation and books for these languages are widely available (for example,
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/vbsvariables.asp
contains useful information on VBScript).
For VBScript, use the following method to create objects required for using the classes provided
in TSAT:
Set reader = CreateObject("ResultScript.BinReader")

Set graph = CreateObject("ResultScript.Plotter")
For JScript, use the following method to create objects required for using the classes provided in
TSAT:
var reader = new ActiveXObject("ResultScript.BinReader");

var graph = new ActiveXObject("ResultScript.Plotter");
The batch plotting feature is mainly designed for TSAT. However, since SSAT binary result file
may contain time-domain step response simulation results, this feature has been made compatible
with SSAT. The descriptions in this section therefore apply to both TSAT and SSAT; however
for SSAT a script can only be used to plot time-domain step response results.

TSAT User Manual
Preparing scripts to create plots requires two key tasks:
• To obtain information from TSAT or SSAT binary result files, such as header
information and data series. This is accomplished by using the BinReader class in
ResultScript.dll.
• To render plots according to custom specifications. This is accomplished by using the

Plotter class in ResultScript.dll.
These classes are described in Sections 11.2 and 11.3.
In a plotting script, you can use features provided in the above classes to manipulate TSAT/SSAT
results and to customize plots, together with other features available in the scripting language.
The resulting plots can include multiple pages and can be created in different formats, including:
• MS Word
• MS PowerPoint
• Postscript
• Screen view
11.1.2 Overview of TSAT and SSAT Binary Result File Contents
Before describing the features of two classes, it is necessary to review the structure of a TSAT or
SSAT binary result file. This helps understand the details on how results can be retrieved from
these files.
In general, a TSAT binary result file contains only the time-domain simulation results for the
scenarios and contingencies specified and executed for the TSAT case. Thus,
• A TSAT binary result file may contain results for multiple scenarios. Each scenario has a
scenario title. Results in different scenarios in one binary result file can be considered as
entirely independent (i.e., the number of contingencies and quantities monitored may be
different for different scenarios). Note that the number of scenarios contained in a TSAT
binary result file may not be the same as the number of scenarios in the corresponding
TSAT case, since scenarios may not be run during simulations.
• Each scenario may contain results for multiple contingencies. Each contingency has a
contingency title. Since only one set of monitor data is used for all contingencies in a
scenario, same output quantities are available for all contingencies in the scenario. Again,
the number of contingencies for a scenario in a TSAT binary result file may not be the
same as the number of contingencies specified for the scenario in the corresponding
TSAT case, since contingencies may be specified as don’t-run or may be skipped due to
errors.
• For each contingency, TSAT stores simulation results of all monitored quantities
specified in the monitor data. Quantities monitored and thus available for each output
category are described in TSAT Model Manual.
A similar concept applies to SSAT binary result file. In order to be able to retrieve results using
scripts, the computation option for the scenario must be response computation (for step response

TSAT User Manual
simulations). Under each of such scenarios, there might be a number of contingencies for which
the specified output quantities are stored.
When retrieving data from binary result files, remember that the time series values for all
quantities in one contingency are the same. However, quantities for different scenarios or
contingencies generally have different time series values.
11.2 BinReader Class
The BinReader Class is used to obtain data from TSAT and SSAT binary result files. In the case
of SSAT binary files, only data from step-response scenarios can be obtained.
Properties
The properties of the BinReader class are shown in Table 11-1.
Table 11-1: Properties of the BinReader Class

Property Type Default Description
file string N/A Name of the binary result file. Unless the script is
launched from the command prompt, absolute path is
generally required.
scen integer 1 Scenario number:
• For TSAT: actual scenario number. If a case has three
scenarios but only scenario 3 is run, scen should be
set to 3.
• For SSAT: sequential number of scenario. If a case has
four scenarios and scenarios 1 and 4 are run, scen
must be set to 2 in order to retrieve the results from
scenario 4.
ctg integer 1 for Contingency number:
TSAT • For TSAT: sequential number of contingency, i.e.
0 for contingencies skipped due to dependencies or errors
SSAT are not included in the count.
• For SSAT: sequential number of contingency. Results
obtained at no fault condition are counted at
contingency 0.
quan string N/A Quantity type. Quantity types are listed in Table 11-2.
bus1 integer N/A Bus 1 number (optional - see Table 11-2 for further
information)
string N/A Bus 1 name (optional - see Table 11-2 for further
information)
bus2 intege N/A Bus 2 number (optional - see Table 11-2 for further
information)
string N/A Bus 2 name (optional - see Table 11-2 for further
information)
id string N/A ID (optional - see Table 11-2 for further information)
curvename string N/A Name of curve (optional - see Table 11-2 for further
information)

TSAT User Manual
block string N/A Name of UDM block - only required for user-defined
model block output quantities
Methods
The following methods can be called to obtain the required information from the binary result
file.
timeValues()
This method returns an array corresponding to the time values for the selected
scenario and contingency in the specified binary result file.
curveValues()
This method returns an array corresponding to the curve values (simulation

results) based on the selected scenario, contingency, quantity type, and necessary
curve identification properties (see Table 11-2 for more information) in the
specified binary result file.
scenList()
This method returns an array of the scenario titles available from the specified
binary result file.
ctgList()
This method returns an array of the contingency titles based on the selected
scenario in the specified binary result file.
quanList()
This method returns an array of the quantity types based on the selected scenario
in the specified binary result file. As mentioned earlier, all contingencies in this
scenario will have the same quantity types. Each element in the array is a string
with the Quantity Identifier and the Quantity Name (see Table 11-2 for
definitions), separated by a colon.
curveList()
This method returns an array of curves (as strings) available for the selected
quantity, contingency, scenario, and the binary result file. The format of the
string depends on the quantity type.
Quantity Types
Table 11-2 shows the quantity types available to the BinReader class. In the script code, Quantity
Identifiers (which are case sensitive) should be used to set the quan property (see Table 11-1).
Program indicates whether this quantity type applies to binary result files from TSAT, SSAT, or
both. The values under Required Properties show which properties must be set correctly to

TSAT User Manual
identify the curve in the binary result file. For example, assume that in your VBScript script
reader is set as the BinReader class. To obtain simulation results for generator terminal voltage
at bus 123 ID ‘1’ from contingency #2 in scenario #1 of binary result file test.bin (in C:\mycase),
the following can be used:
reader.file = “C:\mycase\test.bin”
reader.scen = 1
reader.ctg = 2
reader.quan = “gen_v”
reader.bus1 = 123
reader.id = “1”
x_var = reader.curveValues()
Table 11-2: Output quantity types available

Quantity Required Properties
Quantity Name Program
Identifier bus1 bus2 id curvename block
Time (sec) time TSAT
SSAT
Generator Terminal Voltage (pu) gen_v TSAT Y Y
SSAT
Generator Terminal Voltage Angle gen_va SSAT Y Y
(pu)
Generator Active Power (MW) gen_p TSAT Y Y
SSAT
Generator Reactive Power (MVAR) gen_q TSAT Y Y
SSAT
Generator Absolute Angle (deg) gen_ang TSAT Y Y
SSAT
Generator Relative Angle (deg) gen_relang TSAT Y Y
Generator Speed (Hz) gen_spd TSAT Y Y
SSAT
Generator Speed Rate (Hz/s) gen_spdrat TSAT Y Y
Generator Mechanical Torque (MW) gen_tm TSAT Y Y
Generator Air-gap Torque (pu) gen_tm SSAT Y Y
Genertor Field Voltage (pu) gen_efd TSAT Y Y
Generator Field Current (pu) gen_ifd TSAT Y Y
Generator Terminal Current real part gen_ir TSAT Y Y
(pu)
Generator Terminal Current gen_ii TSAT Y Y
imaginary part (pu)
Generator Apparent Impedance real gen_rapp TSAT Y Y
part (pu)
Generator Apparent Impedance gen_xapp TSAT Y Y
imaginary part (pu)
Stabilizer Output (pu) stab_vs TSAT Y Y
Induction Motor Terminal Voltage mot_v TSAT Y Y
(pu)
Induction Motor Active Power (pu) mot_p TSAT Y Y
Induction Motor Reactive Power (pu) mot_q TSAT Y Y
Inductior Motor Speed (Hz) mot_spd TSAT Y Y
Induction Motor Current Magnitude mot_i TSAT Y Y
(pu)

TSAT User Manual
Induction Motor Mechanical Torque mot_tm TSAT Y Y

(pu)
SVC Terminal Voltage (pu) svc_v TSAT Y Y
SVC Sensing Bus Voltage (pu) svc_vsens TSAT Y Y
SVC Reactive Power (MVAR) svc_q TSAT Y Y
Nonlinear Load Terminal Voltage load_v TSAT Y
(pu)
Nonlinear Load Current Magnitude load_i TSAT Y
(pu)
Nonlinear Load Active Power (MW) load_p TSAT Y
Nonlinear Load Reactive Power load_q TSAT Y
(MVAR)
Nonlinear Load Bus Frequency (Hz) load_frq TSAT Y
Line Active Power Flow (MW) line_p TSAT Y Y Y
SSAT
Line Reactive Power Flow (MVAR) line_q TSAT Y Y Y
SSAT
Line Current Magnitude (pu) line_i TSAT Y Y Y
SSAT
Line Current Angle (deg) line_ia TSAT Y Y Y
Line Apparent Impedance real part line_rapp TSAT Y Y Y
(pu)
Line Apparent Impedance imaginary line_xapp TSAT Y Y Y
part (pu)
Interface Active Power Flow (MW) iface_p TSAT Y
Interface Reactive Power Flow iface_q TSAT Y
(MVAR)
Bus Voltage Magnitude (pu) bus_v TSAT Y
SSAT
Bus Voltage Angle (deg) bus_va TSAT Y
SSAT
Bus Frequency (Hz) bus_frq TSAT Y
Bus Frequency Rate (Hz/s) bus_frqrat TSAT Y
Region Reactive Reserve (MVAR) qrsv_mvar TSAT Y
Region Reactive Reserve (%) qrsv_pct TSAT Y
Region Active Reserve (MW) prsv_mw TSAT Y
Region Active Reserve (%) prsv_pct TSAT Y
Region Active Generation (MW) rggn_mw TSAT Y
Region Reactive Generation rggn_mvar TSAT Y
(MVAR)
Region Accelerating Power (MW) rggn_acc TSAT Y
Region Load Active Power (MW) rgld_mw TSAT Y
Region Load Reactive Power rgld_mvar TSAT Y
(MVAR)
Region Active Power Export (MW) rgex_mw TSAT Y
Region Reactive Power Export rgex_mvar TSAT Y
(MVAR)
Region Center Of Speed (Hz) rgcn_spd TSAT Y
Region Center Of Angle (deg) rgcn_ang TSAT Y
Zone 1 Relay Margin (%) rel_zone1 TSAT Y Y Y
Zone 2 Relay Margin (%) rel_zone2 TSAT Y Y Y
Converter AC Voltage (pu) conv_acv TSAT Y
Converter DC Voltage (kV) conv_dcv TSAT Y
Converter DC Current (kA) conv_dcc TSAT Y

TSAT User Manual
Converter Alpha (deg) conv_alp TSAT Y

Converter Gamma (deg) conv_gam TSAT Y
Converter Active Power Injection conv_p TSAT Y
(MW)
Converter Reactive Power Injection conv_q TSAT Y
(MW)
DC Bus Voltage (pu) dcbus_v TSAT Y
EXCUDM block excudm TSAT Y Y Y
SSAT
PSSUDM block pssudm TSAT Y Y Y
SSAT
UELUDM block ueludm TSAT Y Y Y
SSAT
OELUDM block oeludm TSAT Y Y Y
SSAT
WTGUDM block wtgudm TSAT Y Y Y
SSAT
GOVUDM block govudm TSAT Y Y Y
SSAT
SHCUDM block shcudm TSAT Y Y Y
SSAT
SHCUDM block for P shcudm_p TSAT Y Y
SECUDM block secudm TSAT Y Y Y Y
SSAT
SERUDM VMR block serudm_vmr TSAT Y Y Y Y
SSAT
SERUDM PAR block serudm_par TSAT Y Y Y Y
SSAT
SPSBUS block spsbus TSAT Y Y Y
SPSGEN block spsgen TSAT Y Y Y
SPSBRN block spsbrn TSAT Y Y Y Y
SPSUDM block spsudm TSAT Y Y
Note:
(1) Quantity identifier is case sensitive and must be entered exactly as shown in the above.
(2) For SPSBUS and SPSUDM, ID refers to the SPS ID.
(3) For SPSGEN and SPSBRN, ID has the format of ID : SID where ID is the generator or
branch ID, SID is the SPS ID.
11.3 Plotter Class
The Plotter class can be used to render plots based on the data available to a variety of document
formats. This class's main focus is the ability to produce multiple-page documents with a simple
API that works well together with the data obtained using the BinReader class. If you want more
flexibility in plot customization, please examine the sample script in Section 11.4 which shows
how to use Microsoft Excel's scripting facilities to create a chart.
Properties

TSAT User Manual
Property Type Default Description

PlotsPerPage integer 4 Number of plots per page. Valid values are 1, 2, or 4. If 1 is
specified, the page layout is landscape; otherwise, it is
portrait. Changes to this property after the first DoPlot
method is called have no effect; i.e. each document can only
have one PlotsPerPage setting.
DoColor boolean false Colour flag:
= true: color will be used to distinguish curves for plots
with 6 or less curves. For plots with more than 6 curves, no
colour will be used no matter what this flag is set to.
= false: colour will not be used to distinguish curves (i.e.,
all curves are printed in black).
DoMark boolean true Marker flag:
= true: markers will be used to distinguish curves for plots
with 6 or less curves. If DoColor is set to false, then
markers will be used regardless. For plots with 1 curve or
more than 6 curves, no marker will be used no matter what
this flag is set to.
= false: markers will not be used to distinguish curves.
XTick integer 5 Number of labeled tick marks for X-axis
XSubTick integer 2 Number of unlabeled tick marks between each labeled tick
mark on the X-axis
YTick integer 5 Number of labeled tick marks for Y-axis
YSubTick integer 2 Number of unlabeled tick marks between each labeled tick
mark on the Y-axis
toffset float 0 Offset for the time values. If a non-zero value is set, the time
values will be shifted by this amount. This may be used to
align simulation results with data measured from field or
obtained from other sources.
maxpts integer -1 Data re-sampling flag:
> 3: all curves will be re-sampled to this number of points,
using linear interpolation, before being added to the plot.
This may help reduce the resulting file size.
≤ 3: no re-sampling is performed.
Methods
The following methods can be called to create plots with different customization options.
SetOutput(filename, format)
filename Name of the output file, including extension and preferably full path.
format A string enclosed in double quotes to indicate the format for the output file:
= ppt Microsoft PowerPoint presentation
= doc Microsoft Word document
= ps Postscript document

TSAT User Manual
= prev Screen view mode. The filename parameter specifies the name of a
temporary file (any file extension can be used). When the screen view
window appears, a key must be pressed to proceed to the next window.
This method should be called before any other in the Plotter class. In order to
use the ppt or doc format, MS Office software must be installed in the computer.
SetGrid(majtype, subtype)
Majtype A string enclosed in double quotes to set grid lines at the labeled tick marks:
= None no grid lines
= solid solid grid lines
= dash dashed grid lines
Subtype A string enclosed in double quotes to set grid lines at the unlabeled tick marks:
= None no grid lines
= solid solid grid lines
= dash dashed grid lines
If this method is not called, the default is no grid lines.
AddTYCurve(label,t,y)
label A string enclosed in double quotes to specify the label for the curve in the legend
t Array of floating point numbers for the time data
y Array of floating point numbers for the curve data
This method adds a curve to the current plot, in which Y is plotted against time.
An error will result if, for the current plot, the AddTXYCurve method has been
used. Note that the quantity types of the curves added to a plot are not required to
be the same.
AddTXYCurve(label,t,x,y)
label A string enclosed in double quotes to specify the label for the curve in the legend
t Array of floating point numbers for the time data
x Array of floating point numbers for the curve data for x-axis
y Array of floating point numbers for the curve data for y-axis
This method adds an X-Y curve to the current plot. The two data series, X and Y,
must share the same time data (this is the case if both of them are retrieved from
the same contingency). An error will result if, for the current plot, the
AddTYCurve method has been used. Note that the quantity types of the curves
added to a plot are not required to be the same.
XAxisRange(mn, mx)
mn Minimum value for X-axis as floating point number, or the string “auto” to
specify automatic scaling.
mx Maximum value for X-axis as floating point number; ignored if mn is set to
“auto”.

TSAT User Manual
If this method is not called, the default is automatic scaling. The values specified
in this method are used for every subsequent plot, until this method is called
again.
YAxisRange(mn, mx)
mn Minimum value for Y-axis as floating point number, or the string “auto” to
specify automatic scaling, or the string “range” to specify a minimum range for
the minimum and maximum values used for the Y-axis.
mx Maximum value for Y-axis as floating point number if minimum is a floating
point number; ignored if mn is set to “auto”; used to specify the minimum range
of the Y-axis if mn is set to “range”.
If this method is not called, the default is automatic scaling. The values specified
in this method are used for every subsequent plot, until this method is called
again.
The range option may be useful to set scaling in some situations. For instance, if
three interface active power flows are plotted with the
YAxisRange(“range”, 1000) method and the minimum/maximum
values of all three curves are denoted as min/max. The following scaling
possibilities may occur:
• If max-min<1000, the minimum Y-axis value is set to (max+min)/2−500 and

the maximum Y-axis value is set to (max+min)/2+500.
• If max-min>1000, the minimum and maximum Y-axis values are set to min
and max.
Such scaling allows easy comparison of multiple plots if (max-min) in all plots
are less than 1000, since the Y-axis lengths are 1000 MW for all plots, regardless
of the min/max of each individual curves.
DoPlot(title, xlabel, ylabel, ylabel2)
title Title for the plot shown above the plot frame (a string enclosed in double quotes)
xlabel Label for the X-axis (a string enclosed in double quotes)
ylabel Label for the Y-axis (a string enclosed in double quotes)
ylabel2 Allows a second line of text to be specified for the Y-axis (a string enclosed in
double quotes)
This method is called after all desired curves have been added to the plot via the
AddTYCurve or AddTXYCurve methods.
PageBreak()
This method forces a page break, if necessary, so that the subsequent plot will
begin on a new page.
Finish()

TSAT User Manual
This method must be called at the end of all plotting activities. Failure to do so
will result in corrupted output files.
11.4 Examples
The starting point to write a VBScript for creating plots is perhaps to use the tool available in
DSAOA (refer to DSAToolsTM DSAOA manual for details of DSAOA). When a plot is created in
DSAOA, select the Create Script function in the Tools menu. This creates the VBScript code
that can be run later to obtain the same plot. For example, this function creates the following code
when relative rotor angles of all generators are plotted in DSAOA for the two-area case:
Set g = CreateObject("ResultScript.Plotter")
call g.setOutput("","prev")
g.PlotsPerPage = 1
reader.quan = "gen_relang"
dim xarr
dim arr
reader.file = "C:\tsat\V4.1_latest\2area\2area.bin"
reader.scen = 1
reader.ctg = 1
xarr = reader.timeValues()
reader.bus1=1
reader.id=" 1"
arr = reader.curveValues()
Call g.AddTYCurve("1 GEN BUS116.5 1",xarr,arr)
reader.bus1=2
reader.id=" 1"
reader.bus1=3
reader.id=" 1"
reader.bus1=4
reader.id=" 1"
call g.DoPlot("","Time (sec)","Generator relative angle

(deg)","Reference Generator = 1 [GEN BUS116.5] ' 1'")
g.Finish()
It is certainly possible to customize this code to meet specific requirements when using it for
other purposes.

TSAT User Manual
The following VBScript example creates two plots on one page in Word format from the results
of the two-area test case included in TSAT distribution package. The created plots are shown in
Figure 11-1.
Set graph = CreateObject("ResultScript.Plotter")

dim T
dim X
dim ctg
Call graph.setOutput("C:\tsat\2area\plot.doc","doc")
reader.file = "C:\tsat\2area\2area.bin"
graph.PlotsPerPage = 2
graph.DoColor = True
graph.DoMark = False
Call graph.XAxisRange(0.0,10.0)
Call graph.YAxisRange(0.6,1.2)
' plot #1
reader.scen = 1
reader.ctg = 1
reader.quan = "gen_v"
reader.bus1= 4
reader.id= " 1"
ctg = reader.ctgList()
qname = "Generator terminal voltage (pu)"
T = reader.timeValues()
X = reader.curveValues()
Call graph.AddTYCurve("Contingency: "&ctg(1),T,X)
reader.ctg = 2
Call graph.DoPlot("4 GEN BUS413.8 1","Time (sec)",qname,"")
' plot #2
Call graph.YAxisRange(-100.0,0.0)
reader.scen = 1
reader.ctg = 1
reader.quan = "gen_relang"
reader.bus1= 4
reader.id= " 1"
qname = "Generator relative angle (degrees)"
reader.ctg = 2

TSAT User Manual

Call graph.DoPlot("4 GEN BUS413.8 1","Time (sec)",qname,"")
graph.Finish()
4 GEN BUS413.8 1
1.2000
Generator terminal voltage (pu)
1.0800
0.9600
0.8400
0.7200
0.6000
0.00 2.00 4.00 6.00 8.00 10.00
Time (sec)
Contingency: BUS 6-MLINE
Contingency: BUS 8 3P-1
4 GEN BUS413.8 1
-0.0
Generator relative angle (degrees)
-20.0
-40.0
-60.0
-80.0
-100.0
0.00 2.00 4.00 6.00 8.00 10.00
Time (sec)
Contingency: BUS 6-MLINE
Contingency: BUS 8 3P-1
TSAT
Figure 11-1: Plots created using VBScript

TSAT User Manual
The next example shows how to use the BinReader class and Microsoft Excel's scripting classes
to create a chart. In the example, the absolute path is necessary for the binary result file in order
for the example to succeed. Also, since Excel requires 2-dimensional arrays to set the values for
the cells, while the BinReader class returns only 1-dimensional arrays, a subroutine named
“AddArr” is used to perform the required data conversion. As can be seen, Excel scripting classes
offer lots of flexibility in terms of plot customization, and they can be used when such levels of
details are required for the plots.
Some lines in the code are broken due to width limitations of this document. However, these
statements should appear as one line in an actual VBScript file. The continued lines are shown in
shade.
Set ex = CreateObject("Excel.Application")
reader.file = "C:\tsat\2area\2area.bin"
ex.Visible = True
'
' A few utility routines to reduce repetition
' Main code starts below
'
Sub AddArr(sheet,arr,pos)
npts=UBound(arr,1)-LBound(arr,1)
dim xtmp
redim xtmp(npts,0)
For II=LBound(arr,1) To UBound(arr,1)
xtmp(II-LBound(arr,1),0)=arr(II)
Next
Set xrng = sheet.Range(pos).Resize(npts+1,1)
xrng.value = xtmp
End Sub
Sub AddCurve(sheet,chart,xpos,ypos,title,arr)
Call AddArr(sheet,arr,ypos)
npts=UBound(arr,1)-LBound(arr,1)
Set xrng = sheet.Range(xpos).Resize(npts+1,1)
Set yrng = sheet.Range(ypos).Resize(npts+1,1)
chart.SeriesCollection.NewSeries
With chart.SeriesCollection(chart.SeriesCollection.Count)
.Name = title
.XValues = xrng
.Values = yrng
End With
End Sub
Sub SetupAxis(ax,title,fmt,mn,mx,tickmaj,tickmin)
ax.HasTitle = True
ax.AxisTitle.Characters.Text = title
ax.AxisTitle.Font.Name = "Times New Roman"
ax.AxisTitle.Font.FontStyle = "Bold"
ax.AxisTitle.Font.Size = 16
ax.HasMajorGridlines = True
ax.MajorTickMark = 3 'xlTickMarkOutside
ax.MajorUnit = tickmaj
ax.TickLabels.NumberFormat = fmt
ax.TickLabelPosition = -4134 'xlTickLabelPositionLow
ax.HasMinorGridlines = False

TSAT User Manual
ax.MinorTickMark = 2 'xlTickMarkInside
ax.MinorUnit = tickmin
ax.MinimumScale = mn
ax.MaximumScale = mx
End Sub
With ex
'
' Create a chart
'
Set wb = .Workbooks.Add
Set nm = .ActiveSheet
.Charts.Add
.ActiveChart.ChartType = 75 'xlXYScatterLinesNoMarkers
.ActiveChart.Location 2, nm.Name '2 = xlLocationAsObject
'
' Get data from binary result file and add to chart
'
dim xarr
dim arr
reader.quan="gen_v"
xarr = reader.timeValues()
Call AddArr(.ActiveSheet,xarr,"A1")
reader.bus1=1
reader.id=" 1"
Call AddCurve(.ActiveSheet,.ActiveChart,"A1","B1","1 GEN BUS116.5 1",arr)
reader.bus1=2
reader.id=" 1"
Call AddCurve(.ActiveSheet,.ActiveChart,"A1","C1","2 GEN BUS218.4 1",arr)
reader.bus1=3
reader.id=" 1"
Call AddCurve(.ActiveSheet,.ActiveChart,"A1","D1","3 GEN BUS313.8 1",arr)
reader.bus1=4
reader.id=" 1"
Call AddCurve(.ActiveSheet,.ActiveChart,"A1","E1","4 GEN BUS413.8 1",arr)
'
' Nudge the chart a little closer to the top-left
'
.ActiveSheet.Shapes("Chart 1").IncrementLeft -200
.ActiveSheet.Shapes("Chart 1").IncrementTop -120
'
' Widen the chart
'
.ActiveSheet.Shapes("Chart 1").ScaleWidth 1.5, 0, 0
.ActiveSheet.Shapes("Chart 1").ScaleHeight 1.0, 0, 0
'
' Customize legend and axes
'
With .ActiveChart
.Legend.Font.Name = "Times New Roman"
'.Legend.Font.FontStyle = "Bold"
.Legend.Font.Size = 16
.ChartArea.Font.Name = "Times New Roman"
.ChartArea.Font.Size = 16
.HasTitle = True
.ChartTitle.Characters.Text = "Example Chart"
.ChartTitle.Font.Name = "Times New Roman"
.ChartTitle.Font.FontStyle = "Bold"
.ChartTitle.Font.Size = 20

TSAT User Manual
Call SetupAxis(.Axes(1,1),"Time (sec)","0",0.0,10.0,2.0,1.0)

Call SetupAxis(.Axes(2,1),"Generator terminal voltage (pu)",
"0.000",0.6,1.2,0.12,0.06)
'.PlotArea.Interior.ColorIndex = -4142 'Make Plot area unfilled
End With
End With
Use of the BinReader class to retrieve data from a binary result file in an MATLAB session is
possible as presented in the example below. Note that it is necessary to use the cell2mat
function to access the curve data as plain arrays, which many MATLAB functions (such as plot)
require.
>> r= actxserver('ResultScript.BinReader');
>> r.file='C:\tsat\2area\2area.bin';
>> r.ctg=1;
>> r.scen=1;
>> r.quan='bus_v';
>> t=r.timeValues();
>> size(t)
ans =
403 1
>> r.bus1=1;
>> y=r.curveValues();
>> size(y)
ans =
403 1
>> plot(cell2mat(t),cell2mat(y));

TSAT User Manual
12 Appendix C – Description of Test Cases
This section describes the test cases that are included in the TSAT distribution package.
12.1 General Notes
There are six test cases included with the TSAT distribution package:
• A two-area test case. This test case is ideal for studying angle stability and damping
problems. It is derived from slightly modified version of the system that was published in
Power System Stability and Control, McGraw-Hill, 1994, by Dr. P. Kundur.
• An HVDC test case. This test case includes a sample model for a two-terminal dc link.
• A wind generator test case. This test case shows the options to model wind turbine
generators.
• An SVC test case. This test case includes an SVC model and shows how an SVC model can
be created and interfaced with powerflow.
• A TCSC test case. This test case includes a thyristor-controlled series compensator (TCSC)
model and shows how a TCSC model can be created and interfaced with powerflow.
• A STATCOM test case. This test case includes a STATCOM model and shows how such a
model can be created and interfaced with powerflow.
They are created to show some of the capabilities of TSAT for modelling and for performing
different types of transient security assessment of power systems.
12.2 Two-Area Case
The data of this case is located in the subfolder TSAT\2area. The TSAT case file is named
2area.tsa. This case file can be used for both basecase and transaction analyses.
This case represents two areas with two generators in each area. The two areas are connected by
several parallel tie lines. The single line diagram of the system is shown in Figure 12-1. At the
base powerflow, area 1 is exporting 400 MW to area 2.
Table 12-1 to Table 12-4 contain the network data of the system. The four generators have the
same dynamic model and similar data: detailed two-axis synchronous machine model with static
exciter and PSS. The loads are modeled as constant impedance. Figure 12-5 contains the
generator data and Figure 12-2 gives the exciter/PSS model and data.
Figure 12-6 contains the description for the contingencies used in both basecase and transaction
analysis. The fault duration is 6 cycles in all contingencies.
In the transaction analysis, the stability limit is to be found when generators in area 2 are
dispatched to meet a 500 MW of load increase at bus 7.

TSAT User Manual
1 5 6 10 11 3
G1 7 8 9 G3
G2 G4
2 4
Area 1 Area 2
Figure 12-1: Two-area system
Table 12-1: Branch data of the two-area system (all data in pu on 100 MVA base)
From bus To bus ID R X B/2
1 5 1 0.0 0.01666 0.0
2 6 1 0.0 0.01666 0.0
3 11 1 0.0 0.01666 0.0
4 10 1 0.0 0.01666 0.0
5 6 1 0.0025 0.025 0.04375
6 7 1 0.001 0.01 0.0175
6 7 2 0.002 0.02 0.017
7 8 1 0.0075 0.075 0.12833
7 8 2 0.0075 0.075 0.12833
7 8 3 0.0075 0.075 0.12833
7 8 4 0.0075 0.075 0.12833
8 9 1 0.018 0.18 0.1925
8 9 2 0.018 0.18 0.1925
8 9 3 0.018 0.18 0.19
9 10 1 0.001 0.01 0.0175
10 11 1 0.0025 0.025 0.04375
Table 12-2: Bus shunt data of the two-area system

Bus G (MW at 1 pu voltage) B (MVAR at 1 pu voltage)
7 0.0 200.0
9 0.0 350.0
Table 12-3: Load data of the two-area system

Bus P (MW) Q (MVAR)
7 967 100
9 1767 100

TSAT User Manual
Table 12-4: Generation outputs of the two-area system

Bus ID P (MW) Q (MVAR)
1 1 684 136
2 1 700 124
3 1 719 154
4 1 700 149
Table 12-5: Generation model data of the two-area system

Generator unit
Parameter
1 2 3 4
R 0.0025 0.0025 0.0025 0.0025
Xd 1.8 1.8 1.8 1.8
Xq 1.7 1.7 1.7 1.7
X’d 0.3 0.3 0.3 0.3
X’q 0.55 0.55 0.55 0.55
X”d 0.25 0.25 0.25 0.25
X”q 0.25 0.25 0.25 0.25
Xl 0.2 0.2 0.2 0.2
T’d0 8.0 8.0 8.0 8.0
T’q0 0.4 0.4 0.4 0.4
T”d0 0.03 0.03 0.03 0.03
T”q0 0.05 0.05 0.05 0.05
S(1.0) 0.0392 0.0392 0.0392 0.0392
S(1.2) 0.2670 0.2670 0.2670 0.2670
H 6.5 6.5 6.175 6.175
D 0.0 0.0 0.0 0.0
MVA Rating 900.0 900.0 900.0 900.0
* All pu data on generator MVA base
Vref 7.0
0.5
+
– 100
VT Σ Efd
1 + 0.02s
+
–0.5
0.1
–7.0
ω 2.0 s 1 + 0.08s 1 + 0.08s

3 .0
1 + 2.0 s 1 + 0.04s 1 + 0.04s
–0.1
Figure 12-2: Exciter/PSS model and data of the two-area system

TSAT User Manual
Table 12-6: Contingencies for the two-area system

Contingency Name Contingency Description
BUS 6-MLINE Three phase fault at bus 6; fault cleared and impedance on the line
between buses 5 and 6 is doubled
BUS 8 3P-1 Three phase fault at bus 8; fault cleared and open one of the lines
between buses 7 and 8
BUS 8 3P-2 Three phase fault at bus 8; fault cleared and open two of the lines
BUS 8 3P-3 Three phase fault at bus 8; fault cleared and open three of the lines
12.3 HVDC Case
The data of this case is located in the subfolder TSAT\dc. The TSAT case file is named dc.tsa.
This case file can be used for basecase analysis only.
Figure 12-3 shows the single line diagram of the system. A 500 kV dc link is connected between
buses 8 and 11. At the base powerflow, the dc link carries 500 MW of power. Figure 12-4 shows
the powerflow model of the dc network.
Table 12-7 to Table 12-10 contain the ac network data of the system. Table 12-11 contains the dc
network data. The two generators have the same dynamic model and same data: classical machine
model. The loads are modeled as constant impedance. Table 12-12 contains the generator data.
Figure 12-5 shows the dc VDC-IDC characteristics. Figure 12-6 and Figure 12-7 show the dc master
and pole controls respectively.
One contingency is included with this test case: a three-phase fault is applied at bus 10 at 0.5
seconds and cleared at 0.567 seconds by tripping circuit from bus 10 to bus 1 ID 1. It is possible
to apply faults in the dc system (including commutation failure and dc blocking), as described in
the dc model data.
8 11
500 MW
Inverter HVDC Line Rectifier
~ ~
6 9
7 1 10
Figure 12-3: DC test system

TSAT User Manual
Ls R L Ls
Vi Vr
C/2 C/2
GROUND
Pi Pr
Qi Qr
Inverter Rectifier
Figure 12-4: Powerflow model of the dc network
Table 12-7: Branch data of the dc test system (all data in pu on 100 MVA base)
From bus To bus ID R X B/2
1 7 1 0.0 0.01 0.0
1 10 1 0.0 0.013 0.0
6 7 1 0.0 0.0005 0.0
7 8 1 0.0 0.0005 0.0
7 10 1 0.0 0.0086 0.0
9 10 2 0.0 0.0005 0.0
10 11 1 0.0 0.0005 0.0
Table 12-8: Bus shunt data of the dc test system

Bus G (MW at 1 pu voltage) B (MVAR at 1 pu voltage)
8 0.0 150.0
11 0.0 150.0
Table 12-9: Load data of the dc test system

Bus P (MW) Q (MVAR)
7 21789.0 5856.0
10 11289.0 2200.0
Table 12-10: Generation outputs of the dc test system

Bus ID P (MW) Q (MVAR)
6 1 14871.0 8660.7
9 1 18225.5 5802.6

TSAT User Manual
Table 12-11: DC system data

Parameter Value
Line resistance (ohm) (R) 15.0
Smoothing reactance (mH) (LS)
500.0
(at rectifier and inverter respectively)
Line reactance (mH) (L) 1000.0
Capacitance (µF) (C/2) 10.0
Number of bridges 2
Transformer ratio 0.6
Transformer tap adjusted
Commutating reactance (ohm) 15.0
Desired rectifier power (MW) 500.0
Desired rectifier firing angle (degree) 15.0
Desired inverter current (amp) -1000.0
Desired inverter extinction angle (degree) 18.0
Table 12-12: Generation model data of the dc test system

Generator unit
Parameter
6 9
X’d 0.258 0.258
H 5.45 5.45
KD 3.0 3.0
MVA Rating 18000.0 19000.0
* All pu data on generator MVA base
V DC
Rectifier Minimum
Firing Angle
Inverter Minimum
Margin Angle
Inverter Maximum
Firing Angle
Rectifier Reduced Inverter Constant Inverter Constant

Voltage DC Current DC Voltage
Rectifier Constant
DC Current
Voltage Dependent
Current Order Limit
Minimum DC Current
Inverter Minimum Firing Angle
IDC
0 IMARGIN IMARGIN
Figure 12-5: VDC-IDC characteristics

TSAT User Manual
Voltage-Dependent Current Order Limiter (V DCOL)
VAC1 1 IH
(PU) FV > 0 1+sTUP Up IMA X (A)
FV < 0 IL
VDC1 1 Down
(PU) 1+sTDN 0 VL VH
IPDES
PDES
÷ VDCM > VPMODE IDES
(MW)
IORD (A)
IIDES VDCM < VIMODE
VDC1 0.001 (A)
(kV) 1+sTPC IL
VDCM
VDC1 1
(PU) 1+sTM
Figure 12-6: Master control
HVDC1A
αMA X1
+
1 +
IDC1 Σ K1 Σ α1 (rectifier firing angle)
1+sTM + αMA X1
– +
αMIN1
1
sT1
I ORD (A)
αMIN1
αMA X2
–
1 + +
IDC2 Σ K2 Σ
1+sTM αMA X2 α21
+ + αMIN2
IMARGIN 1
sT2 COS
αMIN2
– COS α22 COS α21
γMIN2 COS Σ
+
COS α MIN2
2
3 XC2 IDC2 MA X COS–1 α2 (inverter firing angle)

1
π VDO2 1+sTM
COS α MA X2
+
VDC20 / VDO2 Σ γ20 > γMIN2

–
–1.0 γ20 < γMIN2 COS α23
Figure 12-7: Pole control

TSAT User Manual
The dc link is blocked:

• If either rectifier or inverter measured terminal voltage drops below VBL for TBLD seconds
• If the unblocking voltage VUB and delay TUBD are not satisfied
• If simulation time is between TBLS and TBLE
Inverter mode is set to commutation failure:

• If inverter terminal voltage is below VCF
• If simulation time is between TCFS and TCFE
HVDC1A is the modulation signal (the modulation control is based on the angular difference
signal of ac bus voltages at two ends of the dc link).
12.4 Wind Generator Case
The data of this case is located in the subfolder TSAT\DFIG. The TSAT case file is named
DFIG.tsa. This case file can be used for basecase analysis only.
This case consists of one generator (modeled as wing turbine) connected to a very large generator
(modeled as a classical machine), so it is effectively a single-machine-infinite-bus (SMIB) case.
The wind turbine is a DFIG-type similar to the one described in the following report:
GE Energy, Modeling of GE Wind Turine-Generators for Grid Studies, Version 3.4b, March 4,
2005.
Three models are included in this case for the wind generator, all of which represent the same
DFIG; thus the results are the same:
• A detailed user-defined model (in Generic DFIG UDM.dat).

• A user-defined model using default WTG block (in Generic DFIG DFM.dat).
• A standard model (in Generic DFIG DSA.DAT).
12.5 SVC Case
Static VAR Compensator (SVC) is commonly used to regulate the voltage at a bus by rapidly
adjusting the effective susceptance connected to that bus. An SVC typically consists of a
thyristor-controlled reactor, a number of thyristor-switched capacitors and a number of fixed
capacitors. The connection to the controlled bus is through a step-up transformer. By
manipulating the firing angle of thyristors, it is possible to continuously vary the effective
fundamental susceptance within a range determined by the rating of the device. Outside this
range, however, the SVC becomes a fixed capacitor or inductor.
The single-line diagram of the system is shown in Figure 12-8 with the base case voltage
magnitude shown at each bus.
Table 12-13, Table 12-14, Table 12-15, Table 12-16 and Table 12-17 list the powerflow data of
this case. The SVC is connected to bus 11 and interfaced with the switchable shunt.

TSAT User Manual
Table 12-13 - Powerflow Bus Data

Bus Voltage
Number Name Base kV Type kV PU Angle
1 BUS1 500. 500 Load Bus 494.47 0.9889 -7.4675
2 BUS2 500. 500 Load Bus 499.84 0.9997 -4.2092
6 BUS6 13.8 13.8 Gen. Bus 13.80 1.0000 -12.0146
7 BUS7 500. 500 Load Bus 496.95 0.9939 -12.5478
8 BUS8 345. 345 Load Bus 343.04 0.9943 -12.4668
9 BUS9 13.8 13.8 Swing Bus 13.80 1.0000 0.0000
10 BUS10 500. 500 Load Bus 497.53 0.9951 -0.8642
11 BUS11 345. 345 Load Bus 345.00 1.0000 -4.3755
6
1
7
10
1850.00
1229.91
3000.00
9
0.9889 pu
1200.00
1.0000 pu
2 1550.00 3001.57
11
900.00 1011.44
8
0.9939 pu
0.9951 pu 1.0000 pu
0.9997 pu
300.00
0.9943 pu 92.19 100.00
1.0000 pu
Figure 12-8: Single line diagram of the SVC case
Table 12-14 – Powerflow Generator Data

Bus MW MVAr Terminal Base Generator
Number Name Type Output Output Voltage kV MVA Resistance Reactance
6 BUS6 13.8 Gen. Bus 1850.00 1229.91 1.0000 13.8 2200 0.00000 0.25800
9 BUS9 13.8 Swing Bus 3001.57 1011.44 1.0000 13.8 4000 0.00000 0.25800
Table 12-15 – Powerflow Load Data

Bus Actual Load
Number Name Type MW MVAr
7 BUS7 500. Load Bus 3000.00 1200.00
10 BUS10 500. Load Bus 1550.00 900.00
11 BUS11 345. Load Bus 300.00 100.00

TSAT User Manual
Table 12-16 – Powerflow Line Data

From Bus To Bus Series Charging From Bus To Bus
Number Number Status R X B MW MVAr MW MVAr
1 7 In 0.00000 0.01000 0.00000 870.38 -10.38 -870.38 87.85
1 10 In 0.00010 0.01300 0.00000 -870.38 10.38 871.16 90.33
6 7 In 0.00000 0.00050 0.00000 1850.00 1229.92 -1850.00 -1205.24
7 8 In 0.00000 0.00050 0.00000 -279.62 -82.62 279.62 83.05
7 10 Out 0.00000 0.00860 0.00000 0.00 0.00 0.00 0.00
8 11 In 0.00100 0.05000 1.96500 -279.62 -83.06 280.41 -72.68
9 10 In 0.00000 0.00050 0.00000 3001.57 1011.43 -3001.57 -961.27
10 2 In 0.00000 0.01000 0.00000 580.41 -29.06 -580.41 63.17
11 2 In 0.00000 0.00050 0.00000 -580.41 64.89 580.41 -63.19
Table 12-17 – Powerflow Swichable Shunt Data

Bus Control Actual Shunt Terminal Block 1 Block 2
Number Name Type Mode MVAr Voltage MVAr/Step MVAr/Step
11 BUS11 345. Load Bus SVC 92.19 1.0000 -300.00 500.00
As Table 12-17 shows the SVC in this example can deliver a maximum of 500 MVAr
(capacitive), or absorb a maximum of 300 MVAr (inductive). Initially, SVC is delivering 92
MVAr to regulate the voltage of bus 11.
For dynamical simulation, additional data is specified for generators, loads and the SVC.
The generator and the load dynamics are given in the dynamics.dyr file. The dynamical models
of the generator at bus 6 include an exciter and a PSS. The generator and its controllers have the
same per unit parameters as the one used in the two-area test case. The MVA rating of this
generator is 2200.
The generator at bus 9 is represented by the classical model of a constant internal voltage behind
transient reactance. Table 12-18 lists the relevant data of this generator.
Table 12-18 – Dynamical Data of the Generator at BUS 9

BUS H D MVA R X’d
9 5.45 3.0 4000 0.0 0.2580
H, D, and x’d are in per unit based on machine MVA base.
Loads are modeled as constant impedance.
The SVC controller is specified by a block diagram which is realized using the User-Defined
Model (UDM) facility in TSAT.
A schematic drawing of the SVC is shown in Figure 12-9. It consists of a fixed or mechanically
switched shunt and a variable shunt. Figure 12-10 and Figure 12-11 show how the steady-state
characteristics of SVC changes when the fixed shunt is considered.

TSAT User Manual
QISSVC1 QSSVC1
VSSVC1
TCR TSC FC
Figure 12-9: Schematic of SVC
BF = 0 VSSVC1
1.0
VREF
–1.0
IISSVC1
–1.0 1.0
Produce Q Absorb Q
Figure 12-10: V-I Characteristics of SVC without the fixed shunt

TSAT User Manual
BF < 0 VSSVC1
BF
ISSVC1
–1.0 1.0
Produce Q Absorb Q
Figure 12-11: V-I Characteristics of SVC with the fixed shunt
The fixed shunt is rated at -100 MVAr, while the variable shunt range is ±400 MVAr. There is a
controller associated with the variable part which adjusts the susceptance of the branch based on
the terminal voltage measurement. The UDM implementation of the controller is shown in
Figure 12-12. Some explanation is due to understand the function of the controller and the way it
is interfaced with the simulation.
The block “Remote Bus Volt. Mag. (pu)” brings in the voltage of bus 11 to which the SVC is
connected. After passing through a low-pass filter, this voltage is compared to the reference value
“REF”, and the error then proceeds to the PI controller. Finally the value of the fixed capacitive
shunt (-0.25 pu) is added to the susceptance, the result is multiplied by 0.5 (to change the base of
the per unit system as explained below), and passed to the end block “END BLK” which is the
interface between this controller and the shunt in power system model.
The logical switch, “VLOW”, blocks the controller if the voltage of bus 11 falls below 0.7 pu.
The block “IIDV” provides the droop of 0.02 for the SVC characteristic. The gain blocks on the
right-hand side are for monitoring.

TSAT User Manual
0.0
SW DVREF
0.0 GN QSSVC1
T0 0.5
2QSHC
-400.0
I2
-REF
PI TIV
LSW VLOW GN BMAX
50.0 0.02 LL TSVC
GN VREF I1 THR -0.7 GN KPV 1.0 GN BF END BLK
1.0 1.0 B
1.0 T1 0.0 1.5 1.0 0.5 T SR+TSC
1 1 + 0.05 s
s
T2 0.0 -1.0
LL VRMES -1.0
-0.25
1.0
I3 GN VSSVC1
1 + 0.01 s VSHC
1.0
Remote Bus
Volt. Mag. (pu) GN VRSSVC1
1.0 1.0
Bus
VSHC
11
GN IIDV 0.25 GN BISSVC1
-0.02 1.0
Remote Line
GN BSSVC1
GN Real Power (pu)
SSVC1A
WO SSVC1A2 WO SSVC1A1
2BSHC
LL SSVC1A3
1.0
0.1 1.0
1 + 0.09 s 3.0 s 0.02 s
-0.005 1.0 1.0 50.0 From Bus 10
1 + 0.03 s 1 + 3.0 s 1 + 0.02 s GN QISSVC1
To Bus 2
-0.1 VSHC
ID 1 -400.0
Figure 12-12: Block diagram of the SVC controller in UDM
The MVA base used for the calculation blocks in the controller is 400 which is the range in which
the variable shunt of SVC can change,
-400 ≤ BSVC ≤ 400 MVA.
Therefore, the fixed capacitive shunt of -100 MVA will be -0.25 pu. This base value is different
from the base value used for interfacing the controller to the shunt in the simulation. The latter is
specified in the end block “TCR+TSC”, and is 800 MVA (Figure 12-13).
Figure 12-13: End Block parameter menu. QT is the base value used for the interface.

TSAT User Manual
This is why the value of susceptance is multiplied by 0.5 before passing it to the End Block. Also
the value of the shunt BSHC has to be multiplied by 2 before using it in the block calculations.
The blocks at the bottom of Figure 12-12, add a modulation signal derived from the MW flow in
line 10-2-1 to damp the power oscillations.
The contingency applied to this system is a three-phase to ground fault at bus 10 at time 0.5 s.
Then the line between bus 1 and bus 10 is removed and the fault is cleared at time 0.567 s. Figure
12-14 shows the dynamic response of voltage at bus 11 once with the SVC controller active (red
curve), and once with a fixed shunt equal to pre-contingency value of 92 MVAR (blue curve).
The SVC increases the capacitive susceptance connected to the bus, and hence injects more
reactive power to support the voltage. See Figure 12-15 for a comparison of active power in
Line 10-2-1 with and without SVC action.

1.10
0.88
0.66
0.44
0.22
0.00
0.00 3.00 6.00 9.00 12.00 15.00
Time (sec)
Figure 12-14: Comparison of bus 11 voltage with and without SVC

TSAT User Manual
Line active power flow (MW)

1900
1500
1100
700
300
-100
0.00 3.00 6.00 9.00 12.00 15.00
Time (sec)
Figure 12-15: Comparison of active power in Line 10-2-1 with and without SVC
12.6 TCSC Case
The Thyristor Controlled Series Capacitor (TCSC) can improve the stability of a power system
by damping power oscillations, alleviating subsynchronous resonance, and preventing voltage
collapse.
The test system is shown in Figure 12-16 and the powerflow data is shown in Table 12-19,
Table 12-20, Table 12-21 and Table 12-22. The line between bus 8 and bus 11 is compensated
by a TCSC. Note that the reactance of 0.0843 pu of this branch represents the total series
reactance including that of the line and its series compensation.

TSAT User Manual
Table 12-19 – Powerflow Bus Data

Bus Voltage
1 BUS1 500. 500 Load Bus 471.23 0.9425 6.7297
6 BUS6 13.8 13.8 Swing Bus 13.80 1.0000 0.0000
7 BUS7 500. 500 Load Bus 480.03 0.9601 -4.4419
8 BUS8 345. 345 Load Bus 331.22 0.9600 -4.2950
9 BUS9 13.8 13.8 Gen. Bus 13.80 1.0000 26.4375
10 BUS10 500. 500 Load Bus 487.77 0.9755 21.0813
11 BUS11 345. 345 Load Bus 336.52 0.9754 20.9383

6 BUS6 13.8 Swing Bus 14871.00 8563.63 1.0000 13.8 18000 0.00000 0.25800
9 BUS9 13.8 Gen. Bus 18212.98 5743.13 1.0000 13.8 19000 0.00000 0.25800

Bus Actual Load
7 BUS7 500. Load Bus 21789.00 5856.00
10 BUS10 500. Load Bus 11289.00 2200.00
BUS1 500.
BUS7 500.
BUS6 13.8
6
1
7
BUS10 500.
10
14870.99
8563.61
BUS9 13.8
9
21789.00
5856.00
BUS11 345.
11289.00 18212.98
BUS8 345.
11
2200.00 5743.13
8
Figure 12-16: Single line diagram of the TCSC case

TSAT User Manual
Table 12-22 – Power Flow Line Data

Number Number Status R X B MW Flow MVAr Flow MW Flow MVAr Flow
1 7 In 0.00000 0.01000 0.00000 1753.09 5.60 -1753.09 340.40
1 10 In 0.00010 0.01300 0.00000 -1753.09 -5.60 1756.55 455.41
6 7 In 0.00000 0.00050 0.00000 14871.00 8563.60 -14871.00 -7091.19
7 8 In 0.00000 0.00050 0.00000 -472.44 4.74 472.44 -3.53
7 10 In 0.00000 0.00860 0.00000 -4692.46 890.00 4692.46 1238.37
8 11 In 0.00100 0.08430 1.96500 -472.44 3.54 474.96 24.67
9 10 In 0.00000 0.00050 0.00000 18212.98 5743.11 -18212.98 -3919.63
10 11 In 0.00000 0.00050 0.00000 474.96 25.85 -474.96 -24.66
For dynamical simulation, additional data is specified for generators, loads and the TCSC. The
generator and the load dynamics are given in the dynamics.dyr file.
Both generators are represented by the classical model of a constant internal voltage behind
transient reactance. Table 12-23 lists the relevant data of the generators.
Table 12-23 – Dynamical Data of the Generators

BUS H D MVA R X’d
6 5.45 3.0 18000 0.0 0.2580
9 5.45 3.0 19000 0.0 0.2580
The TCSC controller is specified by a block diagram which is realized using the User-Defined
Model (UDM) facility in TSAT.
The block diagram of the TCSC controller is shown in Figure 12-17. Note that no feedback from
the line current or device reactance is provided to adjust the output. This open-loop scheme is
primarily used for power-flow control. It is interesting to note that TCSC still exhibits
subsynchronous resonance mitigation through its passing damping capability.
The series compensator current, ISEC, is used to build the capability curve of the TCSC. Using
this capability curve the reactance of TCSC is dynamically limited depending on the line current.

TSAT User Manual
Outputs
Capacitive Limit Inductive Limit GN ITCSC1
1.0
I2
I2
2.3015ISEC
I1
-2.0 0.6 GN QTCSC1
I1 2.3015QSEC
I2 -500.0
Step
Change GN VIOI
SW DXREF MIN Thyristor GN P1TCSC1
0.0 1.0
P1
T0 0.5 Bypass 100.0
I1 I3
-1.0 Rating MSC
GN XREF LSW IMAXT
1.7 LL XRAT
2.0 I1 THR 2.0
GN XTCSC1 END BLK
REF MAX MIN 2.3015 X
1.0 T1 0.025 1.0 TCSC Or SSSC
1 + 0.015 s
T2 0.01
-3.0
SW XMS
I2
T0 100.5
GN V1TCSC1
V1
0.1 1.0
0.18
Remote Bus
GN V2TCSC1
Modulation Volt. Ang. (rad)
V2
GN TCSC1A 1.0 1.0
WO TCSC1A2 WO TCSC1A1
1.0 Bus 11
3.0 s 0.02 s
-0.15 1.0 50.0
Remote Bus
1 + 3.0 s 1 + 0.02 s
-1.0 Volt. Ang. (rad)
-1.0
Bus 8
Figure 12-17: Block diagram of the TCSC controller in UDM

Powertech Labs, Inc.
In order to understand the numerical values used in the block diagram, first the END Block is
examined (Figure 12-18). The parameter XINI determines the initial series reactance of TCSC in
percentage of the uncompensated branch series reactance (positive for inductive and negative for
capacitive). The parameter XC, on the other hand, specifies the fixed capacitive reactance in
percentage of the uncompensated branch series reactance (positive for capacitive, cannot be
negative). The series compensation consists of this fixed part and the variable part from the
TCSC. If the total series reactance of the branch is denoted by XEQ, then:
XINI − X C
XEQ = XLINE + XLINE (1)
100
Figure 12-18: End block of the TCSC controller
Using (1) the uncompensated line reactance, XLINE, can be calculated. Referring to the load
flow, the equivalent reactance of the line 8, 11, 1 is XEQ = 0.0843 p.u. (Base: 100 MVA, 345 kV).
Therefore
100 100
XLINE = XEQ = 0.0843 = 0.0869 (2)
100 + XINI − X C 100 − 3 − 0.0
The TCSC interface blocks, for example the END Block, the current input (ISEC), and reactance
input (XSEC), use a different per unit system. In this per unit system, the uncompensated line
reactance is taken as the base value for the reactance calculations. This means that the base of the
current is
100
ISECBASE = 1000 = 1925.7 A (3)
3 ⋅ XLINE ⋅ VLL BASE
194 of 206
Where ISECBASE is the current base in Amperes. It is important to note that the capability curve of
the TCSC in this UDM model is per unitized based on the device ratings, and a change of bases is
necessary. The TCSC in the example is rated at 500 MVAr and 345 kV. So the rated current is
500
IRATED = 1000 = 836.7 A (4)
3 ⋅ 345
To change the series compensator current from UDM per unit system to TCSC per unit system,
ISEC has to be multiplied by 1925.7/836.7 = 2.3015.
So to recap, there are 3 per unit systems used in this example:
• Main power system: 100 MVA, with the relevant voltage level (500, 345, 13.8 kV)
• TCSC Interface: 100/XLINE MVA, 345 kV, where XLINE is per unit on the main power
system base values
• TCSC capability curve: 500 MVA, 345 kV
The TCSC steady-state X-I characteristics is shown Figure 12-19. The values of the parameters
are as follows:
XLLIM = 2.0
XCLIM = -3.0
XBP = 0.18
IMAXT = 2.0
VMAXT = 2.0
IH = 0.6
VH = 1.7
The “Modulation” blocks act upon the angle difference between Bus 8 and Bus 11. The washout
filters block the average value and only pass the variations of the angle difference. The output
signal is modulated into the reference value of the reactance and helps damp the power
oscillations.
195 of 206
XTCSC
(Ratio of TCSC Capacitor XC)
Inductive XLLIM Voltage Limit Due to Harmonics

Limit (VH / ITCSC1)
Thyristor Current Limit

(VH / ITCSC1 + IH / ITCSC1 – 1.0)
VH/IH
Thyristor XBP
ITCSC1 (PU)
0 1.0 IH IMAXT
Thyristor Block Line Current Limit

–1.0
(Single Module
Limit)
Voltage Limit Due to MOV

(–VMAXT / ITCSC1)
Capacitive XCLIM
Limit
Figure 12-19: TCSC X-I Characteristics
A three-phase to ground fault is applied to bus 10 at time 0.5 s. Then the line between bus 1 and
bus 10 is removed and the fault is cleared at time 0.567 s. Figure 12-20 shows the dynamic
response of the active power flowing through Line 10-7-1 once with the TCSC controller in
service (red curve), and once out of service (blue curve). The TCSC action increases the damping
of power oscillations.
196 of 206

7900
6160
4420
2680
940
-800
0.00 3.00 6.00 9.00 12.00 15.00
Time (sec)
Figure 12-20: Comparison of the MW flow in Line 10-7-1, with TCSC controller in service (red)
and out of service (blue)
12.7 STATCOM Case
Static Synchronous Compensator (STATCOM) is a voltage-sourced converter that is used to

regulate the voltage at a bus by rapidly injecting or absorbing reactive power. A STATCOM
typically consists of a DC voltage source, self-commutated switches, and a step-up transformer.
By manipulating the turning on and off of switches, the reactive current injection from the device
is continuously varied over a range determined by the device ratings. Outside this range,
however, the STATCOM becomes a constant current source or is switched off.
The single-line diagram of the system is shown in Figure 12-21 with the base case voltage
magnitude shown at each bus. Table 12-24 to Table 12-28 list the powerflow data. The
STATCOM is connected to bus 11 and interfaced with the switchable shunt.
197 of 206
Table 12-24 - Powerflow Bus Data

Bus Voltage
1 BUS1 500. 500 Load Bus 494.47 0.9889 -7.4676
2 BUS2 500. 500 Load Bus 499.82 0.9996 -4.2093
6 BUS6 13.8 13.8 Gen. Bus 13.80 1.0000 -12.0147
7 BUS7 500. 500 Load Bus 496.95 0.9939 -12.5480
8 BUS8 345. 345 Load Bus 343.04 0.9943 -12.4669
9 BUS9 13.8 13.8 Swing Bus 13.80 1.0000 0.0000
10 BUS10 500. 500 Load Bus 497.53 0.9951 -0.8642
11 BUS11 345. 345 Load Bus 344.99 1.0000 -4.3756
6
1
7
10
1850.17
1229.84
3000.00
9
0.9889 pu
1200.00
1.0000 pu
1550.00 3001.39
2
11
900.00 1011.39
8
0.9939 pu
1.0000 pu
0.9951 pu
0.9997 pu
0.9943 pu 300.00
100.00
92.20
1.0000 pu
Figure 12-21: Single line diagram of the STATCOM case

6 BUS6 13.8 Gen. Bus 1850.00 1230.03 1.0000 13.8 2200 0.00000 0.25800
9 BUS9 13.8 Swing Bus 3001.57 1011.78 1.0000 13.8 4000 0.00000 0.25800

Bus Actual Load
7 BUS7 500. Load Bus 3000.00 1200.00
10 BUS10 500. Load Bus 1550.00 900.00
11 BUS11 345. Load Bus 300.00 100.00
198 of 206
Table 12-27 – Powerflow Line Data

Number Number Status R X B MW MVAr MW MVAr
1 7 In 0.00000 0.01000 0.00000 870.39 -10.39 -870.39 87.86
1 10 In 0.00010 0.01300 0.00000 -870.39 10.39 871.17 90.33
6 7 In 0.00000 0.00050 0.00000 1850.00 1230.01 -1850.00 -1205.33
7 8 In 0.00000 0.00050 0.00000 -279.61 -82.56 279.61 82.99
7 10 Out 0.00000 0.00860 0.00000 0.00 0.00 0.00 0.00
8 11 In 0.00100 0.05000 1.96500 -279.61 -82.99 280.40 -72.75
9 10 In 0.00000 0.00050 0.00000 3001.57 1011.78 -3001.57 -961.61
10 2 In 0.00000 0.01000 0.00000 580.40 -28.72 -580.40 62.83
11 2 In 0.00000 0.00050 0.00000 -580.40 64.54 580.40 -62.84
Table 12-28 – Powerflow Switchable Shunt Data

Bus Actual Shunt Terminal Block 1 Block 2
Number Name Type MW MVAr Voltage Steps MVAr/Step Steps MVAr/Step
11 BUS11 345. Load Bus 0.00 91.79 1.0000 1 -300.00 1 500.00
As Table 12-28 shows the STATCOM in this example can deliver a maximum of 500 MVAr
(capacitive), or absorb a maximum of 300 MVAr (inductive). Initially, STATCOM is delivering
92 MVAr to regulate the voltage of bus 11.
For dynamical simulation, additional data is specified for generators, loads and the STATCOM.
The generator and the load dynamics are given in the dynamics.dyr file.
The STATCOM controller is specified by a block diagram which is realized using the User-
Defined Model (UDM) facility in TSAT.
The dynamical model of the generator at bus 6 includes an exciter and a PSS. The generator and
its controllers have the same per unit parameters as the one used in the two-area example. The
MVA rating of this generator is 2200.
The generator at bus 9 is represented by the classical model of a constant internal voltage behind
transient reactance. Table 12-29 lists the relevant data of this generator.
Table 12-29 – Dynamical Data of the Generator at BUS 9

BUS H D MVA R X’d
9 5.45 3.0 4000 0.0 0.2580
A schematic drawing of the STATCOM is shown in Figure 12-22. It consists of a fixed or

mechanically switched shunt and a voltage-sourced converter. Figure 12-23 and Figure 12-24
show how the steady-state characteristics of STATCOM are varied with a fixed shunt.
199 of 206
Voltage-Sourced Converter
(Shunt VSC) NT
jXt IISCOM1
+
QISCOM1 QSCOM1
–
VSCOM1
Fixed
and/or Initial
Mechanically
Equivalent Initial Susceptance in Power Flow -
(May Be Controlled for a Desired Voltage) Switched
Susceptance
–jBF
Figure 12-22: Schematic of STATCOM
BF = 0 VSCOM1
Overload
VREF
VBL
IISCOM1
–IMAXT –1.0 1.0 IMAXT
Produce Q Absorb Q
Figure 12-23: Steady-state V-I Characteristics of STATCOM without fixed shunt
200 of 206
BF < 0 VSCOM1
Overload
VBL
BF
ISCOM1
–IMAXT –1.0 1.0 IMAXT
Produce Q Absorb Q
Figure 12-24: Steady-state V-I Characteristics of STATCOM with fixed shunt
In the example considered here, the fixed shunt is rated at -100 MVAr, while the converter range
is ±400 MVAr.
There is a controller associated with the variable part which adjusts the current of the branch
based on the terminal voltage measurement. The UDM implementation of the controller is shown
in Figure 12-25. Some explanation is due to understand the function of the controller and the way
it is interfaced with the simulation.
The block “Remote Bus Volt. Mag. (pu)” brings in the voltage of bus 11 to which the STATCOM
is connected. After passing through a low-pass filter, this voltage is compared to the reference
value “REF”, and the error then proceeds to the PI controller. The result is multiplied by 0.5 (to
change the base of the per unit system as explained below), and passed to the end block “END
BLK” which is the interface between this controller and the shunt in power system model.
The logical switch, “VBL”, blocks the controller if the voltage of bus 11 is very low (below 0.3
pu). If the voltage of BUS 11 falls below 0.7 pu, the logical switch “VLOW” lets the 0.0 value
into the PI controller, and as a result the controller goes into constant current mode. The block
“IIDV” provides the droop of 0.02 for the STATCOM characteristics. The gain blocks on the
right-hand side are for monitoring.
201 of 206
0.0 2IVSC 0.0

GN IISCOM1
2IVSC
1.0
SW I2
DVREF GN IIDV I2
T0 0.5 0.02 GN QISCOM1
2QVSC
-400.0
PI TIV
GN IMAXT
LSW VLOW LSW VBL
50.0 0.02
GN VREF I1 GN KPV 1.2 I1 GN IRAT END BLK
THR -0.7 THR -0.3
-REF 1.2 I
1.0 T1 0.0 1.5 1.0 T1 0.0 0.5 STATCOM
1
T2 0.0 s T2 0.0
-1.2
LL VRMES -1.2
1.0
GN VSCOM1
1 + 0.01 s I3 VSHC
GN VI3 I3
1.0
-1.0
Remote Bus
Volt. Mag. (pu) GN VRSCOM1
1.0 1.0
Bus 11
Remote Line
GN QSCOM1
GN SCOM1A Real Power (pu)
LL SCOM1A3
WO SCOM1A2 WO SCOM1A1 2QSHC
-400.0
0.1 1.0
1 + 0.09 s 99999.0 s 0.02 s
-0.004 1.0 1.0 50.0 From Bus 10
1 + 0.03 s 1 + 0.02 s GN BSCOM1
1 + 99999.0 s To Bus 2
-0.1 2BSHC
ID 1 1.0
Figure 12-25: Block diagram of the STATCOM controller in UDM
202 of 206
TSAT Users Manual
The MVA base used for the calculation blocks in the controller is 400 which is the rating of the voltage-
sourced converter.
Therefore, the fixed capacitive shunt of -100 MVA will be -0.25 pu. This base value is different from the
base value used for interfacing the controller to the shunt in the simulation. The latter is specified in the
end block “STATCOM”, and is QL+QC = 800 MVA (Figure 12-26).
Figure 12-26: End Block parameter menu
This is why the value of current is multiplied by 0.5 before passing it to the End Block. Also the value of
the shunt IVSC has to be multiplied by 2 before using it in the block calculations.
The blocks at the bottom of Figure 12-27, add a modulation signal derived from the MW flow in line 10-
2-1 to damp the power oscillations.
A three-phase to ground fault is applied to bus 10 at time 0.5 s. Then the line between bus 1 and bus 10 is
removed and the fault is cleared at time 0.567 s. Figure 12-27 shows the dynamic response of voltage at
bus 11 once with the STATCOM controller active (red curve), and once with a fixed shunt equal to pre-
contingency value of 92 MVAR (blue curve). Figure 12-28 shows the comparison of Line 10-2-1 with
and without STATCOM action
Powertech Labs Inc. Page 1

TSAT Users Manual

1.10
0.88
0.66
0.44
0.22
0.00
0.00 3.00 6.00 9.00 12.00 15.00
Time (sec)
Figure 12-27: Comparison of bus 11 voltage with and without STATCOM.

TSAT Users Manual

1900
1500
1100
700
300
-100
0.00 3.00 6.00 9.00 12.00 15.00
Time (sec)
Figure 12-28: Comparison of Line 10-2-1 with and without STATCOM.

TSAT User Manual PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TSAT User Manual PDF

Caricato da

Copyright:

Formati disponibili

TSAT

Transient Security Assessment Tool

Powertech Labs Inc.

DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES

(A) MAKES ANY WARRANTY OR REPRESENTATION WHATSOEVER, EXPRESS OR IMPLIED,

(B) ASSUMES RESPONSIBILITY FOR ANY DAMAGES OR OTHER LIABILITY WHATSOEVER

Portion of the TSAT code is copyrighted 1998 by Chris Maunder

Last modified – April 2011

Powertech Labs Inc. i

Powertech Labs Inc. ii

4.1 Starting TSAT ................................................................................................. 47

Powertech Labs Inc. iii

8.1.3 Examining Exciter Step Response Test Results .............................................. 115

Powertech Labs Inc. iv

12.1 General Notes .............................................................................................. 176

Powertech Labs Inc. v

• Determination of stability limits under specified system operation conditions.

• Capability of connecting to an EMS system to perform on-line TSA.

1.1 Main Features

Powertech Labs Inc. 6

Automatic relays, such as switchable shunt relay, under-voltage/under-frequency load shedding

Computation of security indices

Refer to Section 3.3 for their definitions and applications.

Derivation of stability limits

Powertech Labs Inc. 7

Powertech Labs Inc. 8

• No disturbance test. With this feature, generators with problematic dynamic

Compatible data sets

SSAT TSAT VSAT

Shared modules Shared modules

• Powerflow solver • Powerflow solver

Compatible data sets

Figure 1-1: Relationship of TSAT, SSAT, VSAT, and PSAT

Powertech Labs Inc. 9

1.3 Scope of This Manual

This manual provides the information related to the following topics:

• Installation of the program

1.4 User Support Information

Powertech Labs Inc.

Telephone: (604) 590-7450

Powertech Labs Inc. 10

2.1 TSAT Distribution

2.2 System Requirements

The following computer system is recommended for TSAT:

• PC running any version of Windows operating system.

2.3 Installing TSAT

Use the following procedure to install TSAT:

Powertech Labs Inc. 11

Section 12 gives detailed descriptions of these test cases.

2.4 Installing Protection Dongles

Powertech Labs Inc. 12

There are two types of dongles:

• TSAT executable (tsat.exe)

Installation of dongle drivers

To install the dongle drivers, follow these steps:

(3) Perform a custom setup with the following options:

• Remove the “Sentinel Key Server”.

Powertech Labs Inc. 13

How to use single-user dongles

To use a single-user dongle, do the following:

• Install the single-user version of TSAT on your computer.

How to use network dongles

To use a network dongle, do the following: