Power Factory Manual

DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
Publisher:
DIgSILENT GmbH
Heinrich-Hertz-Str. 9
72810 Gomaringen / Germany
Tel : +49 (0) 7072-9168-0
Fax : +49 (0) 7072-9168-88

Visit our homepage at:

www.digsilent.de

Copyright DIgSILENT GmbH.

All rights reserved. No part of this
publication may be reproduced or
distributed in any form without
permission of the publisher.
doc 2004 10 21 750 b252
Contents

Introduction to the Manual 2

A Introduction to the Tutorial A-1

A.1 Conventions Used In This Manual . . . . . . . . . . . . . . A-2

B Program Overview B-4

B.1 Philosophy of Use . . . . . . . . . . . . . . . . . . . . . . . B-5
B.2 Data Arrangement / Structure . . . . . . . . . . . . . . . . . B-5
B.3 DIgSILENT PowerFactory Windows . . . . . . . . . . . . B-10
B.4 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
B.5 Troubleshooting The Tutorial . . . . . . . . . . . . . . . . . B-16

C Step 0: Introducing the Tutorial Project C-17

C.1 Creating the Tutorial Project . . . . . . . . . . . . . . . . . . C-17

D Step 1: Creating Power System Elements D-23

D.1 The Tutorial Manager . . . . . . . . . . . . . . . . . . . . . D-23
D.2 Creating the Power System Components . . . . . . . . . . D-25
D.3 Editing the Power System Components . . . . . . . . . . . D-30
D.4 Performing a Load Flow . . . . . . . . . . . . . . . . . . . . D-34
D.5 Editing the Result Box Format . . . . . . . . . . . . . . . . D-36
D.6 Performing Short-Circuit Calculations . . . . . . . . . . . . D-39

E Step 2: The Data Manager E-42

E.1 The Database Manager: Basics . . . . . . . . . . . . . . . E-43
E.2 Using the Database Manager . . . . . . . . . . . . . . . . . E-44
E.3 Initializing Step 2 . . . . . . . . . . . . . . . . . . . . . . . . E-44
E.4 Performing Calculations . . . . . . . . . . . . . . . . . . . . E-51

F Step 3: Creation of a Second Subsystem F-53

F.1 Setting Up Step 3 . . . . . . . . . . . . . . . . . . . . . . . F-53
F.2 Creating the Topology . . . . . . . . . . . . . . . . . . . . . F-54
F.3 Editing the Elements . . . . . . . . . . . . . . . . . . . . . . F-55
F.4 Performing Calculations . . . . . . . . . . . . . . . . . . . . F-58
G Step 4: Connecting the Subsystems G-61
G.1 Setting Up Step 4 . . . . . . . . . . . . . . . . . . . . . . . G-61
G.2 Activation of the Two Subsystems . . . . . . . . . . . . . . G-61
G.3 Connecting Two Grids . . . . . . . . . . . . . . . . . . . . . G-63

H Step 5: Motor Start Simulation H-67

H.1 Setting up Step 5 . . . . . . . . . . . . . . . . . . . . . . . . H-67
H.2 Modelling the Power Plant . . . . . . . . . . . . . . . . . . . H-67
H.3 Editing the Power Plant . . . . . . . . . . . . . . . . . . . . H-68
H.4 Performing a Motor Start Simulation . . . . . . . . . . . . . H-70
H.5 Changing the MDM . . . . . . . . . . . . . . . . . . . . . . H-72

I Step 6: Transient Analysis I-74

I.1 Setting Up Step 6 . . . . . . . . . . . . . . . . . . . . . . . I-74
I.2 Composite Models Revisited . . . . . . . . . . . . . . . . . I-74
I.3 Setting Up a Transient Short-Circuit Simulation . . . . . . . I-76
I.4 Creating Plots . . . . . . . . . . . . . . . . . . . . . . . . . I-79
I.5 Running a Transient Simulation . . . . . . . . . . . . . . . . I-81
I.6 Closing Up Step 6 of the Tutorial . . . . . . . . . . . . . . . I-81
I Handling of Power Factory
1 About DIgSILENT PowerFactory 1-2
1.1 Database Management and Backups . . . . . . . . . . . . 1-3
1.2 Capability for all Users; Beginner to Advanced . . . . . . . 1-4
1.3 Conventions Used In This Manual . . . . . . . . . . . . . . 1-4

2 Program Overview 2-6

2.1 Philosophy of Use . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.2 Data Arrangement / Structure . . . . . . . . . . . . . . . . . 2-7
2.3 DIgSILENT PowerFactory Windows . . . . . . . . . . . . . 2-12
2.4 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2.5 Toolbar Definitions . . . . . . . . . . . . . . . . . . . . . . . 2-18

3 Logon, User Accounts and Program Settings 3-24

3.1 Program Configurations and Settings . . . . . . . . . . . . 3-24
3.2 License Key(s) . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
3.3 The Log On Page . . . . . . . . . . . . . . . . . . . . . . . 3-26
3.4 The User Account Management System . . . . . . . . . . . 3-27
3.5 Users and User Groups . . . . . . . . . . . . . . . . . . . . 3-31

4 User Settings 4-37

4.1 General Settings . . . . . . . . . . . . . . . . . . . . . . . . 4-38
4.2 Graphic Windows Settings . . . . . . . . . . . . . . . . . . 4-39
4.3 Data Manager Settings . . . . . . . . . . . . . . . . . . . . 4-39
4.4 Output Window Settings . . . . . . . . . . . . . . . . . . . . 4-40
4.5 Functions Settings . . . . . . . . . . . . . . . . . . . . . . . 4-41
4.6 Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
4.7 Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41

5 The Database and the Data Manager 5-43

5.1 Using the Data Manager . . . . . . . . . . . . . . . . . . . 5-45
5.2 Moving Around in the Database Tree . . . . . . . . . . . . . 5-47
5.3 Adding a New Item . . . . . . . . . . . . . . . . . . . . . . . 5-47
5.4 Deleting an Item . . . . . . . . . . . . . . . . . . . . . . . . 5-50
5.5 Cut, Copy, Paste and Move Objects . . . . . . . . . . . . . 5-51
5.6 Searching for Objects . . . . . . . . . . . . . . . . . . . . . 5-52
5.7 Editing Data Objects . . . . . . . . . . . . . . . . . . . . . . 5-57
5.8 Additional Features . . . . . . . . . . . . . . . . . . . . . . 5-62
5.9 The Flexible Data Page Tab . . . . . . . . . . . . . . . . . . 5-63
5.10 Variables and Variable Sets . . . . . . . . . . . . . . . . . . 5-64
5.11 Save and Restore Parts of the Database . . . . . . . . . . 5-74
5.12 Spreadsheet Format Data Import/Export . . . . . . . . . . 5-75
5.13 Importing Version 3.1x Files . . . . . . . . . . . . . . . . . . 5-81
5.14 The Input Window . . . . . . . . . . . . . . . . . . . . . . . 5-83
5.15 Input Window Commands . . . . . . . . . . . . . . . . . . . 5-83
5.16 The Database Manager Message Bar . . . . . . . . . . . . 5-86
 5.17 Special Folders in the Database . . . . . . . . . . . . . . . 5-86
5.18 Special Objects in the Database . . . . . . . . . . . . . . . 5-90

6 Project Management 6-93

6.1 Advanced Project Management . . . . . . . . . . . . . . . . 6-102

7 Graphic Windows 7-110

7.1 Introduction- the Basics . . . . . . . . . . . . . . . . . . . . 7-110
7.2 Active Graphics, Graphics Board and Study Cases . . . . . 7-110
7.3 Single Line Graphics and Data Objects . . . . . . . . . . . 7-112
7.4 Building from Predefined Objects . . . . . . . . . . . . . . . 7-116
7.5 Using the Graphic Windows . . . . . . . . . . . . . . . . . . 7-119
7.6 Graphic Layers . . . . . . . . . . . . . . . . . . . . . . . . . 7-123
7.7 Graphic Commands, Options and Settings . . . . . . . . . 7-125
7.8 Interconnecting Power Subsystems . . . . . . . . . . . . . 7-140

8 Creating and Using Simulated Power Systems 8-150

8.1 Introduction to Terminals, Busbars and Cubicles . . . . . . 8-150
8.2 Station and Busbar Systems . . . . . . . . . . . . . . . . . 8-151
8.3 Transmission Lines and Cables . . . . . . . . . . . . . . . . 8-161
8.4 Characteristics, Scales and Triggers . . . . . . . . . . . . . 8-165
8.5 Handling Scales and Characteristics . . . . . . . . . . . . . 8-177
8.6 Feeders and Feeder Objects . . . . . . . . . . . . . . . . . 8-180

9 Performing Calculations 9-186

9.1 Edit relevant Objects for Calculation . . . . . . . . . . . . . 9-187
9.2 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-187
9.3 Comparisons Between Calculations . . . . . . . . . . . . . 9-188

II Steady-State Power System Analysis

10 Load-Flow Calculations 10-192
10.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . 10-193
10.2 Active Power Control . . . . . . . . . . . . . . . . . . . . . . 10-194
10.3 Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-194
10.4 Low Voltage Analysis . . . . . . . . . . . . . . . . . . . . . 10-195
10.5 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . 10-195
10.6 Iteration Control . . . . . . . . . . . . . . . . . . . . . . . . 10-196
10.7 Advanced Simulation Options . . . . . . . . . . . . . . . . . 10-198
10.8 Troubleshooting Load-Flow Calculations . . . . . . . . . . . 10-199

11 Short-Circuit Calculations 11-201

11.1 General Remarks . . . . . . . . . . . . . . . . . . . . . . . 11-201
11.2 Starting Single-Fault Short-Circuit Calculations . . . . . . . 11-202
11.3 Faults on Lines . . . . . . . . . . . . . . . . . . . . . . . . . 11-203
 11.4 Multiple Faults Calculation . . . . . . . . . . . . . . . . . . 11-204
11.5 Short-Circuit Calculation with User-Defined Element Sets . 11-206
11.6 Short-Circuit Calculation Options . . . . . . . . . . . . . . . 11-206
11.7 Technical Background . . . . . . . . . . . . . . . . . . . . . 11-214

12 Protection 12-221
12.1 Creating a Protection Device . . . . . . . . . . . . . . . . . 12-221
12.2 Basic Protection Devices . . . . . . . . . . . . . . . . . . . 12-229
12.3 Short-Circuit Sweep . . . . . . . . . . . . . . . . . . . . . . 12-246
12.4 The Time-Distance Diagram . . . . . . . . . . . . . . . . . 12-248
12.5 Path Definitions . . . . . . . . . . . . . . . . . . . . . . . . 12-253
12.6 Protection Analysis Results . . . . . . . . . . . . . . . . . . 12-253
12.7 Time-Overcurrent Plots . . . . . . . . . . . . . . . . . . . . 12-254
12.8 The Curve-Input Command . . . . . . . . . . . . . . . . . . 12-262

13 Harmonics Analysis 13-265

13.1 Harmonic Load-Flow . . . . . . . . . . . . . . . . . . . . . . 13-266
13.2 Frequency Sweep . . . . . . . . . . . . . . . . . . . . . . . 13-268
13.3 Filter Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 13-270
13.4 Modelling Harmonic Sources . . . . . . . . . . . . . . . . . 13-271
13.5 Definition of Result Variables . . . . . . . . . . . . . . . . . 13-275

14 Network Reduction 14-277

III Optimization
15 Optimal Power-Flow 15-281

16 Optimal Capacitor Placement 16-282

16.1 Target Function . . . . . . . . . . . . . . . . . . . . . . . . . 16-282
16.2 Optimization Procedure . . . . . . . . . . . . . . . . . . . . 16-283
16.3 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . 16-284
16.4 Advanced Options Page . . . . . . . . . . . . . . . . . . . . 16-286
16.5 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-289

17 Open Tie Optimization 17-291

17.1 Optimization procedure . . . . . . . . . . . . . . . . . . . . 17-291
17.2 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . 17-292

IV Reliability Analysis
18 Reliability Assessment Functions 18-295
18.1 Contingency Analysis . . . . . . . . . . . . . . . . . . . . . 18-295
 18.2 Voltage Sag Analysis . . . . . . . . . . . . . . . . . . . . . 18-301
18.3 Network Reliability Assessment . . . . . . . . . . . . . . . 18-306
18.4 Calculated results . . . . . . . . . . . . . . . . . . . . . . . 18-318
18.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . 18-322
18.6 Stochastic Reliability Assessment: Basic Theory . . . . . . 18-327
18.7 Failure Models . . . . . . . . . . . . . . . . . . . . . . . . . 18-332

V Stability Analysis and Simulation of Transients

19 Time-Domain Simulations 19-354
19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-355
19.2 Calculation Methods . . . . . . . . . . . . . . . . . . . . . . 19-356
19.3 Setting up a Simulation . . . . . . . . . . . . . . . . . . . . 19-359
19.4 Result Objects . . . . . . . . . . . . . . . . . . . . . . . . . 19-367
19.5 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-369
19.6 Error Messages and Warnings . . . . . . . . . . . . . . . . 19-373
19.7 Run a Simulation . . . . . . . . . . . . . . . . . . . . . . . . 19-376

20 Models for Stability Analysis 20-378

20.1 System Modelling Approach . . . . . . . . . . . . . . . . . 20-378
20.2 The Composite Model . . . . . . . . . . . . . . . . . . . . . 20-382
20.3 The Composite Frame . . . . . . . . . . . . . . . . . . . . . 20-386
20.4 The Common Model . . . . . . . . . . . . . . . . . . . . . . 20-390
20.5 The Composite Block Definition . . . . . . . . . . . . . . . . 20-393
20.6 Drawing Composite Block Diagrams and Composite Frames 20-395

21 User Defined (DSL) Models 21-402

21.1 Modeling and Simulation Tools . . . . . . . . . . . . . . . . 21-404
21.2 DSL Implementation: an Introduction . . . . . . . . . . . . 21-405
21.3 Defining DSL Models . . . . . . . . . . . . . . . . . . . . . 21-410
21.4 The DIgSILENT Simulation Language (DSL) . . . . . . . . 21-414
21.5 DSL Functions . . . . . . . . . . . . . . . . . . . . . . . . . 21-427

22 Modal Analysis / Eigenvalue Calculation 22-432

22.1 Theory of Modal Analysis . . . . . . . . . . . . . . . . . . . 22-432
22.2 Performing Eigenvalue Analysis . . . . . . . . . . . . . . . 22-434
22.3 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-436

23 Model Parameter Identification 23-439

23.1 Target Functions and Composite Frames . . . . . . . . . . 23-440
23.2 Creating The Composite Identification Model . . . . . . . . 23-442
23.3 Performing a Parameter Identification . . . . . . . . . . . . 23-444
23.4 Identifying Primary Appliances . . . . . . . . . . . . . . . . 23-446
VI Tools & Utilities
24 Virtual Instruments 24-449
24.1 Virtual Instrument Panels . . . . . . . . . . . . . . . . . . . 24-452
24.2 Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-458
24.3 The Vector Diagram . . . . . . . . . . . . . . . . . . . . . . 24-469
24.4 The Voltage Profile Plot . . . . . . . . . . . . . . . . . . . . 24-472
24.5 Schematic Visualisation . . . . . . . . . . . . . . . . . . . . 24-474
24.6 The Waveform Plot . . . . . . . . . . . . . . . . . . . . . . . 24-476
24.7 Embedded Graphic Windows . . . . . . . . . . . . . . . . . 24-478
24.8 Tools for Virtual Instruments . . . . . . . . . . . . . . . . . 24-479
24.9 User-Defined Styles . . . . . . . . . . . . . . . . . . . . . . 24-489

25 Results, Graphs and Documentation 25-495

25.1 Result Objects . . . . . . . . . . . . . . . . . . . . . . . . . 25-495
25.2 The Output Window . . . . . . . . . . . . . . . . . . . . . . 25-499
25.3 The Form Editor . . . . . . . . . . . . . . . . . . . . . . . . 25-505
25.4 The DIgSILENT Output Language . . . . . . . . . . . . . . 25-508
25.5 The Output of Device Data . . . . . . . . . . . . . . . . . . 25-516
25.6 Output of Results . . . . . . . . . . . . . . . . . . . . . . . 25-517
25.7 The Annex for Documentation . . . . . . . . . . . . . . . . 25-519

26 DPL 26-521
26.1 The DPL Command Object . . . . . . . . . . . . . . . . . . 26-522
26.2 The DPL Script Editor . . . . . . . . . . . . . . . . . . . . . 26-524
26.3 The DPL Script Language . . . . . . . . . . . . . . . . . . . 26-525
26.4 Access to Other Objects . . . . . . . . . . . . . . . . . . . . 26-531
26.5 Access to Locally Stored Objects . . . . . . . . . . . . . . . 26-532
26.6 Accessing the General Selection . . . . . . . . . . . . . . . 26-533
26.7 Accessing External Objects . . . . . . . . . . . . . . . . . . 26-534
26.8 Remote Scripts and DPL Command Libraries . . . . . . . . 26-535
26.9 DPL Functions and Subroutines . . . . . . . . . . . . . . . 26-538

27 DOLE and On-Line Data Exchange 27-547

27.1 DOLE Interface . . . . . . . . . . . . . . . . . . . . . . . . . 27-547
27.2 DIgSILENT On-Line Operation Mode . . . . . . . . . . . . 27-562

28 Conversion from Graphical Information Systems 28-567

28.1 “.DGS”-File Creation by using the Excel Sheet . . . . . . . 28-567
28.2 The PowerFactory Import . . . . . . . . . . . . . . . . . . . 28-568
28.3 “.DGS”-File Format . . . . . . . . . . . . . . . . . . . . . . . 28-570

29 Converting/Importing PSS/E Files 29-572

29.1 Conversion Procedure . . . . . . . . . . . . . . . . . . . . . 29-572
29.2 General tab page . . . . . . . . . . . . . . . . . . . . . . . . 29-573
29.3 Options tab page . . . . . . . . . . . . . . . . . . . . . . . . 29-575
VII Glossary
Glossary 1

1
DIgSILENT PowerFactory Introduction to the Manual

Introduction to the Manual

This is the manual for the program PowerFactory, as written by DIgSILENT. It

consists of the Users Manual, and a tutorial to assist the user in getting started
with PowerFactory.

The Users Manual is intended to explain the ’how to’ of the program. How to run
a load-flow, for example. It is assumed that the user knows, or does not
immediately require an explanation of, what the program does to achieve the
end result.

Technical reference data is available to explain how PowerFactory performs the

command that the user has entered, for example, what algorithm is used to
perform a load flow and the assumptions that are made when performing that
load-flow.

When exploring new software there are two approaches that may be employed:
the functional approach and the project approach. The first method presents all
functional parts of the program one by one and explains their features, and how
and when to use them - the Users Manual has been written with this approach in
mind.

The project approach shows the program by example, and this approach is
contained in the tutorial under the ”Getting Started” section. The new user is
shown how to start a new project and how to build a simple power system, which
is then extended in a number of steps. The new user is thus guided along all
major features on a step by step basis.

Because the ”Getting Started” tutorial is presented in addition to the Users

Manual, much of what is explained here can also be found in the Users Manual.
However, whereas the Users Manual is meant to be accessed in a random order,
the tutorial is a sequential set of lessons.

For this tutorial, a small power system is built by the user. A tutorial manager
compares what has been entered by the user to a completed version of the
power system, which is contained within the DIgSILENT PowerFactory
database shipped on the installation CD. The tutorial manager then informs the
user where errors have been made and the user can correct these and continue.

The power system tutorial includes all important features of the DIgSILENT

2
DIgSILENT PowerFactory Introduction to the Manual

PowerFactory software and all major calculation functions will be covered.

However, DIgSILENT PowerFactory is a highly flexible and versatile program
and this ’Getting Started Tutorial’ must be looked upon as a first introduction. For
technical details about the models of power system components, or for more
details about certain power system calculations, please refer to the Users
Manual or the technical reference data sheets.

3
Getting Started Tutorial
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory Introduction to the Tutorial

Chapter A

Introduction to the Tutorial

This tutorial is intended to be used in a step by step manner, where each step
follows on from what has been done in the previous step. To assist the user a
Tutorial Manager may be used to either check the tutorial project at the start of a
Tutorial lesson, or to clean up at the end.

The tutorial manager will, by default, NOT install a project, but will try to
check the project that has been entered by the user. It issues error
messages when the tutorial project is not found or contains errors. Please
read the “Getting Started Tutorial” (see the main Help menu) for more help
on the PowerFactory Tutorial.

However, by disabling the Check option, the Tutorial Manager may also be used
to simply install the Tutorial System at any of its stages without having to enter
any data yourself. Although less educational, this mode may be used to skip
certain parts of the Tutorial.

The PowerFactory Tutorial philosophy is to guide the user through the features
of the software, during which the data for a small but complete power system
design will be entered. The Tutorial Manager’s main purpose is to check the data
that has been entered and issue error messages as required.

Prior to starting with the tutorial itself, it is useful to read an introduction to

PowerFactory itself in order to get an idea of how the program is structured in
terms of using it. This is explained in the main part of the manual, and is
reproduced here for your convenience.

Getting Started Tutorial A-1

DIgSILENT PowerFactory Introduction to the Tutorial

A.1 Conventions Used In This Manual

A.1.1 Terms and Abbreviations

Mouse and keyboard handling actions are abbreviated, and a ’shorthand’ is also
used to describe actions that the user should take. To assist the user these
shorthand descriptions are specifically formatted to stand out, as follows:
Key As in “Press the left mouse key”. A key is either one of the mouse keys or a
key on the keyboard. Mouse keys are sometimes called ’buttons’, as in ’the
mouse button.’
Button As in “Press the OK button”. The word “button” is used for screen
areas which perform some action when clicked using the mouse. In other
words, a ’virtual’ button. Buttons are usually described by the popup name
that you read when you hover the cursor over the button. For example,
press to open the user settings dialogue.

Buttons are also shown as seen on screen, as in the to open the user
settings dialogue.
Right/Left clicking As in “Right click the browser”. Means pointing the cursor at
the object described (the browser) and pressing the right/left mouse key.
Double Clicking As in “Double click the button”. Means pointing the cursor at
the object described and pressing the left mouse key twice within about
half a second (the time interval is as set in the Windows operating system).
Ctrl-B (key combination example) means that that the user should press the
combination of keys described. For example, “Press C TRL -B to toggle
between balanced/unbalanced case,” means that the user should press
and hold down the first keyboard key (the Control key on the keyboard in
this example) and then press the second key (B) as well.
Menu sequences When a user needs to select a command through cascaded
menu options the sequence is shown by arrows that indicate what option to
choose next, starting from the original menu button.
For example, setting the drawing format can be done by pressing the
O PTIONS button to access the options menu, then by choosing ”Graphic”
from the list offered, and finally ”Drawing Format ...” from the last list;
this series of actions is all simply described by Options →Graphic
→Drawing Format ...
” ” and ’ ’ ”These” quotes are used to indicate that the description is one that
can be found within the program- one that is not user definable, for
example, the balloon help description ”Calculate Load Flow” that you see
when you hover your cursor over the Load Flow button.

Getting Started Tutorial A-2

DIgSILENT PowerFactory Introduction to the Tutorial

’These’ are used to indicate data that a user has entered or should enter.
’These’ quotes are also used to indicate a process or series of objects that
have no discernible name, but which need to be described. For example,
the ’drawing tools panel,’ which is found on the right hand side of the
drawing canvas.

and [1] [2] [3], etc These show a sequence of events that should be
performed. Where they are numbered they will be associated with a
graphic in which the numbers appear.

left-clicking, right-clicking, clicking, double-clicking, etc Wherever the

instruction clicking or double-clicking appears it should be taken to mean
clicking and double-clicking using the left mouse button. When the right
mouse button is to be used it will be explicitly stated.

Getting Started Tutorial A-3

DIgSILENT PowerFactory Program Overview

Chapter B

Program Overview

DIgSILENT PowerFactory is a single-program package. This means that all

functionality that is used to

• enter new (parts of) a power system design, either in a text-based or in a

graphical way,

• us and print single-line graphics

• edit the power system components

• manage the database

• select design options

• perform calculations

• report and print the results

or any other function related to these tasks, is available directly in the main
program window.

The significance of this is that the users need only familiarize themselves with
one user interface as all activities are controlled and accessed via the main
program window.
More importantly, all data is kept in a central place, and the user need not
transfer, or copy, paste and modify the data from one part of the program to
another in order to perform a new type of calculation. The PowerFactory user
interface is fully compatible with Windows operating systems. For those users
who are not experienced in using these operating systems, some simple
instructions have been added to the tutorial. These are recognized by being
prefaced by a different icon.
For example, to practice a Windows feature:

Do this

Then do that

Users familiar to the Windows operating systems may want to skip these parts of
the tutorial.

Getting Started Tutorial B-4

DIgSILENT PowerFactory Program Overview

B.1 Philosophy of Use

In order to better understand how to use a program it is useful to first get an idea
of what the designers had in mind when they designed the user interface. In the
next few paragraphs we will attempt to explain what this philosophy is.

PowerFactory is intended to be initially used and operated in a graphical

environment. That is, data entry is accomplished by drawing the network under
study and then by editing the objects on the drawing canvas to assign data to
them.

As users progress and become more adept with the program, data will be
manipulated by using a data viewer called the Data Manager.

The following picture shows what PowerFactory looks like when a project is
active.

[1] Main window [3] Graphic window/s

[2] Data Manager window [4] Output window

The two means of accessing the data are thus via the graphics page/s and via
the Data Manager.
The graphics page is simple to understand and data is accessed by
double-clicking on an object in the graphic. An input dialogue pops up and the
user may then edit the data for the object as can be seen in the following picture.

All of the data that is entered for such objects is specifically structured in folders
to allow the user to navigate through it. To view this data a ”Data Manager” is
used. The data manager is similar in appearance and working to a Windows
Explorer.

As mentioned, data pertaining to a study is organized into several folders. Before

examining this structure we should understand the philosophy behind this
arrangement.

B.2 Data Arrangement / Structure

Firstly, it is clear that, for the study of any system, there are two distinct sets of
information that can be defined:

• data that pertains directly to the system under study, that is, electrical data

Getting Started Tutorial B-5

DIgSILENT PowerFactory Program Overview

Figure B.1: Main PowerFactory windows

• study management data, for example, which graphics should be displayed,

what options have been chosen for a load flow, which ’areas’ of the
network should be considered for calculation, etc.

The electrical data itself can also be further divided into logical sets. When we
construct a power system we make use of standardized materials or
components - a roll of cable for example. In simple terms we can describe the
cable electrically by its impedance per km length whilst it is still on the cable
drum; in other words, generic information about this cable, is called ”Type” data.

When we cut a length of the cable for installation the type data is retained in a
modified way, as follows:

600m of cable that has a Type impedance of ’Y’ Ohms/ km will now have an
impedance of ’0.6*Y’ Ohms.

We can thus see that the length of the cable, o.6 km, can be seen as a separate

Getting Started Tutorial B-6

DIgSILENT PowerFactory Program Overview

Figure B.2: Editing an Element

set of information. This set of information will contain all of that information
particular to the specific installation or application of the piece of cable we
are considering. Information such as the derating factor of the installed
cable, its local name, the nodes that it is connected to at either end; in other
words, all information that is non-generic, will fall into this information set.

In PowerFactory we call this ”Element Data.”

This means that there are now three distinct sets that we need to arrange the
data into. In ’Explorer’ terms this means three folders, which, in PowerFactory,
we call:

• ”Grid” folder: holds all the element data

• ”Library” folder: holds all the type data

• ”Study Case” folder: holds all the study management data

Of course we should also house these three folders within a higher folder so that
we can arrange our data for different networks that we may be studying; this we
then call the ”Project” folder.

Getting Started Tutorial B-7

DIgSILENT PowerFactory Program Overview

All of this can be visualized in the overview drawing shown in Figure Fig. B.3,
where:

[1] The graphic depicting the network is shown

[2] If the user edits the data for the element by double clicking on it this element
data is displayed in the element dialogue

[3] If the Type is edited the type dialogue is displayed. In this case you can see
that two different lines (’Cable A’ and ’Cable B’) have their own element
data but both refer to the same type data.

[4] The graphical object data is kept in the ’Grid’ folder- although the user
should refrain from editing this as these are automatically created and
require some experience to manipulate.

[5] Similarly, the element data objects are also kept in the ’Grid’ folder and may
be viewed by using the data manager, as well as by double clicking them
from the graphic.

[6] The type data objects are kept in the ’Library’ folder.

[7] All of these folders are kept inside a project folder, here called ’Simple Power
System.’

[8] Finally, all projects and other folders are housed in the user account folder,
here called ’Raj1.’ This folder is a system folder (the ’user account’) that is
created when the user starts PowerFactory.

The ’Study Case’ folder that can be seen in the data tree is the folder that
contains the study management data- the ’tools’ and ’tool settings’ that are used
to perform the calculations and the visualization of the results. This will be dealt
with in more detail at a later stage. Initially the user does not need to concern
himselve over the study case as it is created and assigned automatically.

Getting Started Tutorial B-8

DIgSILENT PowerFactory Program Overview

Figure B.3: Overview

Getting Started Tutorial B-9

DIgSILENT PowerFactory Program Overview

B.3 DIgSILENT PowerFactory Windows

The so-called ’windows’ are the users interface to the program and the means to
enter or manipulate data and/or graphics. DIgSILENT PowerFactory uses
several kinds of windows some of which have been shown previously. These will
now be described and explained.

Figure B.4: PowerFactory initial appearance

Consider Fig. B.4:

[1] The main PowerFactory window is described in the title bar- ”DIgSILENT
PowerFactory 13.1”

[2] Drop down menu selections are available.

[3] A tool bar is associated to the the main window (presently this is mostly
de-activated as there is no active project).

[4] Balloon help appears for buttons when the cursor is ’hovered’ over a button
for half a second or more.

[5] The title bar of this sub-window describes it as a ”Data Manager” and lists
the path of the object that has been selected in the data manager; here the

Getting Started Tutorial B-10

DIgSILENT PowerFactory Program Overview

project entitled ’Simple Power System,’ which is located in the (user) folder
’Raj1’, has been selected.
[6] When an object is right clicked a menu appears.
[7] This is the output window, which has its...
[8] ...own tool bar.

The data manager sub-window (this window is created by pressing the

button, which is the first button on the left of the main toolbar) is always floating
and more than one can be active at the same time. The database manager itself
has several appearances: it may only show the database tree for selecting a
database folder, or it may be the full version with the database tree, the data
browser, and all editing capabilities.

One of the major tasks for the data manager is to provide access to the power
system components. The power system components shown in the data
manager can be ’gang-edited’ (or ’group-edited’) within the data manager itself,
where the data is presented in a tabular format, for all the selected objects.
Alternatively each object may also be individually edited by double clicking on an
object (or right click →”Edit”).

The output window, at the bottom of the screen, is always there; it cannot be
closed although it can be minimized.

The output window can be “docked”, that is: fixed to a location on the bottom of
the main window. The docked state is the default, as shown in Fig. B.4.
When clicking the right mouse button, when the cursor is in the output window
area, the context sensitive menu of the output window appears. The output
window can then be undocked by deselecting the ”Docking View” (by clicking the
mouse onto ”Docking View” to ’untick’ it. The undocked output window is still
confined to the main window, but now as a free floating window. This sometimes
occurs ’accidentally’ when the user left clicks the tool bar for the output window
and drags the mouse (keeping the mouse button down) to somewhere outside of
the output window boundaries. To rectify this simply left click in the title bar of the
undocked window and drag it down to the bottom of the screen where it will dock
once more (if you have right clicked ’unticked’ ”Docking View” to right click and
select ”Docking View” once more.

The undocked state is not a normal situation for the output window. Because the
output messages that appear in this window are important at any stage while
using the program, the docked state is the best place because it will be visible
then and easy to locate.

The edge of the output window shows a splitter bar [a] which is used to change
the size of the output window. The ‘drag’ cursor, as shown at [a], appears
automatically when the cursor is placed on the splitter bar. The left mouse button

Getting Started Tutorial B-11

DIgSILENT PowerFactory Program Overview

can be pressed when the ‘drag’ cursor is visible. This will turn the splitter bar to
grey and the output window can now be resized by holding down the mouse
button and moving the mouse up or down.

The button “Maximize Output Window” ( ) on the main toolbar will enlarge the
output window to almost full-screen. Left click the button again to switch back to
the small output window.

B.3.1 Sizing Windows and Sub-Windows

On the right of the titlebar of any window or sub-window there are three buttons
that are used to ”Minimize”, ”Maximize”/”Restore Down” or ”Close” the window.

the button minimizes the window to a small object, somewhere on the

screen (usually in the lower left corner- this is the default position) in the
case of a sub-window, or to the task bar for your computer- at the bottom of
the screen.

the button ’opens’ the minimized window to full screen size.

the button reduces the window to a smaller size on the screen; initially
there is a default size for this window but the user may re-size it as desired.

the button will close the sub-window or end the program if this button
is clicked on the main window.

Sub-windows can be re-sized as follows. Place the cursor over the lower right
corner of the window and left click and hold the button down- now drag the
window to the size you require. You will find that each corner can be sized like
this, as well as each edge.

B.3.2 Menu Bar

The menu bar contains the main PowerFactory menus. Each menu entry has a
drop down list of menu options and each menu option performs a specific action.
To open a drop down list, either click on the menu entry with the left mouse
button, or press the A LT key together with the underlined letter in the menu. For
instance, to open the Help menu, press the A LT and the H key together. Menu
options that occur in grey are not available -these become available as the user
activates projects or calculation modes, as required.

press A LT-H to open the help menu. Use your keyboard to select the
Getting Started Tutorial. Press RETURN to open the Tutorial. The on-line
Getting Started Tutorial is exactly the same as the printed version.

close the Getting Started Tutorial help (Use the on the main bar). You
will return to the main PowerFactory program window.

Getting Started Tutorial B-12

DIgSILENT PowerFactory Program Overview

Figure B.5: Re-sizing sub-windows

Figure B.6: The Help Menu on the Menubar

left click the Help menu. Left click the option Users Manual. This opens the
on-line User’s Manual.

B.3.3 Toolbar
The toolbar shows the main PowerFactory command buttons. Buttons that
appear in grey only become active when appropriate.
All command buttons are equipped with balloon help text which pop up when the
cursor is held still at the button for a moment, and no key is pressed.

Getting Started Tutorial B-13

DIgSILENT PowerFactory Program Overview

Figure B.7: The main toolbar

find the button for User Settings by using the balloon help. Don’t use the
mouse keys: just point at the buttons, hold still, and a balloon text will pop
up. Scan all buttons until you find the right one.

Using a command button couldn’t be easier: just click on it with the left mouse
button. Those buttons that perform a task will automatically jump back when that
task is finished. Some command buttons however will switch between two
modes, for instance the one which will reserve more place for the output window
on the workspace ( ). This button will stay down to show the activated mode.
Click the command button again to switch back to the normal view.

When PowerFactory has just been started, the toolbar shows only the general
command buttons. The ’toolbar select’ button ( ) can be clicked to select
additional command buttons.

B.4 Getting Help

The PowerFactory software comes with a number of help facilities:

1. The commercial version comes with a hard copy of the Users Manual and
the Getting Started Tutorial.

2. All versions have on-line versions of the Users Manual and the Getting
Started Tutorial, which can be opened from the Help option on the main
menu.

3. All versions have a context sensitive help which will directly jump to the
right page of the on-line Users Manual when the F1 key is pressed. An
example for the two winding transformer is shown in Fig. B.8.

4. All versions have balloon help installed which will give the names of
command buttons, or input parameters, if the cursor is positioned over
these items and held still for about half a second. Fig. B.9 shows three
help balloons in the browser part of the data manager.

1. For help on buttons (available for all command buttons).

2. For help on class-icons.
3. For help on parameter fields (available for all parameters fields).

Getting Started Tutorial B-14

DIgSILENT PowerFactory Program Overview

Figure B.8: The Two-winding Transformer and its Context sensitive Help

Figure B.9: Balloon Help in the Data Manager

The Users Manual and Getting Started Tutorial are exactly the same in print and
in the on-line version. Command buttons are sometimes referenced by their
name, instead of by their image. For large buttons, this is normally the case. The
name of a button is either the name on the button itself ( OK , C ANCEL ), or
the name that appears in the balloon help ( = U SER S ETTINGS ).

Getting Started Tutorial B-15

DIgSILENT PowerFactory Program Overview

B.5 Troubleshooting The Tutorial

Although the tutorial has been thoroughly tested, the following list of questions
and answers have been found to be useful:

• The Tutorial Manager produces error messages like

Tutorial Project not found
The \obj{ElmNet} object ‘Part1’ is missing in folder ...
etc.etc.
The tutorial manager was never intended to simply install tutorial projects
without further action by the user. The user is requested to create all parts
of the power system actively and the tutorial manager is meant only for
checking the work done.
However, it is possible to (mis)use the tutorial manager for installing the
tutorial project as an example. This is done by disabling the ’Check user
defined project’ option in the tutorial manager’s dialogue.

• The background pattern is not visible in the single line graphic.

To make the pattern visible again:

press the “Show Layer” button ( ). The Graphics Layer dialogue

appears. The “Background” layer is shown in the right pane
(‘invisible’).
move the background layer it to the right pane: left click the
“Background” layer and press the button. This moves the
background to the list of visible layers.
close the layer dialogue.

• I want to continue the Tutorial, but it is not active. How to activate it

so I can continue the Tutorial there where I left it?
If you interrupted the Tutorial to work on another project, or to close the
PowerFactory program, you may reactivate the Tutorial by selecting it in
the File menu. That menu keeps a list of the last 5 active projects. The
Tutorial should be one of the choices. If you cannot find it there, you may
scan your User folder for the Tutorial folder by starting the Tutorial Manager
(option File - Setup Tutorial on the main menu) and select Activate Tutorial
Project. If this give the error message ‘Tutorial Project not found’, you will
have to start at the beginning on the tutorial step where you left the tutorial,
by selecting Initialize Step XX in the tutorial manager.

Getting Started Tutorial B-16

DIgSILENT PowerFactory Step 0: Introducing the Tutorial Project

Chapter C

Step 0: Introducing the Tutorial

Project

The first step in designing a new power system is to create a project. A project
offers the basic structure in which to define and store power system definitions,
together with their design stages and single line diagrams, type libraries,
calculation stages, calculation commands, etc.

This chapter describes how to create a new project and explains most of its
features.

Note that the tutorial manager will, by default, NOT install a project, but will
check the project that has been entered by the user. It issues error
messages when the tutorial project is not found or contains errors.

N OTE : The tutorial project is meant to be created in the ”Demo” user account
or folder (that is, when a user is logged on to PowerFactory as a
”Demo” user.
Although it is possible to perform the tutorial when you are logged in as
another user, i.e. ’Tutorial User’ or ’MyUser’. You will then need to have
a licensed version of PowerFactory to do this (a license capability of
least 30 nodes is required for this).

C.1 Creating the Tutorial Project

The location where the Tutorial Manager stores the tutorial projects is called the
U SER folder. For a “DEMO” version, this will be the \D EMO folder. For a licensed
version, the \U SER folder will be the folder created for you by the Administrator.
The active \T UTORIAL U SER folder is marked by a small blue screen icon. See
Fig. C.1 for an example with the user named “Tutorial User”.
To create a new project in your U SER folder,

open the File menu on the main menu bar.

select the New option. The dialogue shown in Fig. C.2 will pop up. This
dialogue, as most others in this Tutorial, is shown as it should look after we
have finished editing it.

Getting Started Tutorial C-17

DIgSILENT PowerFactory Step 0: Introducing the Tutorial Project

Figure C.1: Example of an active User folder

Figure C.2: The ComNew Command dialogue

select the Project option by clicking it. The red command line should now
read new/....
Enter the name of the project as “Tutorial”. Be sure to enter this name
correctly. All names for projects, study cases or other objects have to be
entered exactly as given, although capitalisation or spaces are not
important.
The “Target Folder” field should read the folder of your current user name,
i.e. \D EMO or \T UTORIAL U SER. If it shows something else:

– press the button to select the correct target. This will open a
database manager which shows, in the left window pane, a tree

Getting Started Tutorial C-18

DIgSILENT PowerFactory Step 0: Introducing the Tutorial Project

representation of the complete PowerFactory database.

The database manager will be explained in more detail at a later stage of

the tutorial. For now, we have to select the DATABASE\D EMO or
DATABASE\T UTORIAL U SER folder:

left click somewhere in the left pane to select the database tree
press the U P arrow key on the keyboard until the Database folder is
highlighted. This is the root folder.
when needed, press the + key to open the Database folder
press the D OWN key to walk down the database tree until the active
D EMO or T UTORIAL U SER folder is highlighted
click the OK button to close the database manager

The New dialogue should appear again, with the correct target.

left click the E XECUTE button.

The execution of the ComNew command causes the currently active project to
be deactivated (if one was active) and all related graphic windows to be closed.

A project needs at least one grid folder in which a power (sub)system is defined.
Therefore, a grid folder is created automatically and its edit dialogue, as depicted
in Fig. C.3, pops up.

Figure C.3: The Grid edit dialogue

set the name of the grid to “Part 1”. Again, this name is obligatory, but
capitals and spaces are not.

set the frequency to 50Hz. The PowerFactory tutorial system is designed

for 50Hz.

left click the OK button.

Getting Started Tutorial C-19

DIgSILENT PowerFactory Step 0: Introducing the Tutorial Project

The Owner field is optionally and is normally used to enter a project, company or
any other appropriate name. In this tutorial, the Owner name is not used.

In the background, the new grid “Part 1” is created in the project, together with a
’Study Case’ folder which is used to activate the grid and to perform calculations
for it. This study case is given a default name (which is, surprisingly, “Study
Case”).

The newly created project and the study case are activated automatically and
the empty single line graphic will be displayed. The PowerFactory workspace
should now look like figure C.4.

Figure C.4: The workspace after creation of a new project

In this figure, the following parts of the workspace are visible:

1. The empty single line graphics window with drawing grid

Getting Started Tutorial C-20

DIgSILENT PowerFactory Step 0: Introducing the Tutorial Project

2. The graphic toolbox which is displayed in its ’docked’ state on the right side
of the graphics window

3. The local graphics window toolbar with its buttons, which is displayed with
small ’up’ and ’down’ arrow buttons which bring more tools. These arrows
are only visible if there is not enough space to display all buttons.

4. The position of the cursor either in the graphics window or in the output
window is displayed in the message bar.

5. The name of the currently active project is shown in the message bar.

6. The Study Case List on the main toolbar which shows the name of
currently active study case and which may be used to switch to another
study case.

C.1.1 Renaming the Study Case

Although the created project may be used as it is, the name of the new study
case is normally changed to somewhat more original than “Study Case”.

select the Edit - Study Case... option on the main menu

The edit dialogue of the study is depicted in Fig. C.5.

Figure C.5: The study case edit dialogue

Change the name to “Case 1”

press OK

Getting Started Tutorial C-21

DIgSILENT PowerFactory Step 0: Introducing the Tutorial Project

The name in the study case list on the main menu should now have changed to
“Case 1” too. The study case list shows the currently active study case and may
be used to select another study case or to deactivate the study case by selecting
the empty line.

C.1.2 Closing and Restarting the DIgSILENT Program

The PowerFactory program does not have a “save” button. All changes made
to the system database are immediately stored in the database on disk. This
means that you may end the program at any time without having to save your
work first.

The software will not reactivate the last active project at start-up. However, the
last few active projects are kept in the main File menu. Reactivating a recently
active project is a matter of left clicking one of these entries.

This Tutorial may thus be interrupted at any moment without further actions, and
may be continued at any time later on by reactivating the Tutorial project.

Getting Started Tutorial C-22

DIgSILENT PowerFactory Step 1: Creating Power System Elements

Chapter D

Step 1: Creating Power System

Elements

The PowerFactory program allows for creating new (parts of) power system
designs ’by hand’, that is: by creating all components in a textual database
environment and by manually connecting them, thus defining the topology. The
more convenient method however, is to use the interactive single line graphics.

The single line graphics are used to create new power system components and
to insert them into the topological network. In this way, the power system
database and its single line graphic are build together in one action.

Editing the created power system components, for example to set the voltage
level or other electrical parameters, may also be done from the single line
graphic, by double clicking the graphical symbols. This will open the
corresponding data dialogue of the power system component. The following
chapter shows all this in more detail.

D.1 The Tutorial Manager

In the previous chapter, a Grid folder (“Part 1”) and a Study Case have been
created. This would normally be enough to start working. Some additional
folders and settings, however, which have been created for the Tutorial will make
some things a bit easier. To install these extra’s, a special “Tutorial Manager”
command dialogue is provided. This Tutorial Manager command principally does
the following:

• it installs a type library for busbars, lines, transformers and other objects

• it prepares the graphic window and sets a background pattern which

makes it easier to position the elements of the Tutorial power System grids.

But it is capable of doing a lot more.

To understand the working of the Tutorial Manager, it is important to realize that

it will not ‘enhance’ or ‘edit’ the user defined tutorial project, but will always
delete what has been made and copy what has been predefined. The following
warning is therefore given:

Getting Started Tutorial D-23

DIgSILENT PowerFactory Step 1: Creating Power System Elements

The Tutorial Manager will destroy all user defined experiments or

alterations made in the tutorial project by replacing the user defined
tutorial project by the corresponding predefined tutorial project

Of course, deleting experiments and reinstalling the predefined project is exactly

what we want the Tutorial Manager to do. We will activate it at the start and finish
of every Tutorial Step either to initialize or to clean up.

To activate the Tutorial Manager

open the File menu on the main menu list

select the option Setup Tutorial...

The Tutorial Manager dialogue now appears.

The Tutorial Manager dialogue is, as all other dialogues, equipped with an online
help:

press the F1 key on the keyboard. The Online help for the Tutorial
manager appears.

after having read the online help: close the help dialogue by selecting the
button in the help window.

For this first Tutorial Step,

select the option Initialize Step 1

enable the Check User Defined Project option

press E XECUTE

The Tutorial Manager will check the newly created project for correctness. It will
emit an error message if the Tutorial Project has not been created correctly. The
common error for this first step is to have entered different names for the tutorial,
grid or study case folders.

Correct the project in case of the following error messages:

• Tutorial Project not found:

– Select the Edit option in the main menu

– Select the Project option. This opens the project folder edit dialogue
– Change the name of the Project to “Tutorial”
– Close the dialogue with OK
– Start the Tutorial manager again

Getting Started Tutorial D-24

DIgSILENT PowerFactory Step 1: Creating Power System Elements

• The object “...” is missing in folder ... : This probably means that a
wrong name for the Grid ‘Part1’ was given. This error cannot be corrected
without introducing the database manager dialogue. Therefore, we
(mis)use the Tutorial Manager to let it install the first step without checking:

– Open the Tutorial Manager again

– select the option Initialize Step 1
– Disable the Check User Defined Project option
– press the E XECUTE

This brings you at the beginning of the first step of the Tutorial. Although all
other steps of the tutorial may be installed in the same way, the tutorial
manager is intended only to install new steps when the user has performed
the exercise correctly.

D.2 Creating the Power System Components

The tutorial manager has installed the additional features and has reopened the
single line graphic. A single line diagram, in grey, is now visible in the
background. This is just a pattern to show where to place the actual power
system components.

D.2.1 Creating Busbars

if the graphic toolbox is not visible on the right side, press the button.

left click the button in the graphic toolbox.

Use the balloon help to find the correct button. The cursor will show the
single busbar icon after the button has been pressed.

Use the background pattern to position the first busbar by left clicking on
the drawing surface. A busbar will be drawn (in black), and is given a
default name like B1.

If something else than a single busbar appears, press the undo-button (

) to undo your last action(s) and try again.

The button changes between graphical editing and parameter editing.

When pressed, the graphic toolbox will disappear and the single line diagram will
be ‘frozen’ and can not be changed anymore. Pressing it again will return the
graphics toolbox (‘un-freeze’).

Getting Started Tutorial D-25

DIgSILENT PowerFactory Step 1: Creating Power System Elements

N OTE : When the insert mode is activated and the symbol for e.g. the busbar
is attached to the mouse arrow, you can switch to the edit mode by
selecting the in the graphical toolbox, by pressing the E SC key
or simply by pressing the right mouse button once.

The busbar may be moved and resized to fit the background pattern:

select a busbar by left clicking it. This will mark the busbar by a thick grey
line with two small squares. If something is selected in a frozen diagram,
then a hatched crossed marking appears, without squares. If you have
double clicked the busbar accidentally, its edit dialogue will pop up. Close
that dialogue with the C ANCEL button.

move the busbar by left clicking on the solid grey line and dragging the
busbar. Releasing the mouse sets the new location.

resizing is done by left clicking one of the small black squares and dragging
it to the left or right, see Fig. D.1.

The cursor can also be used to show a balloon text when held still at the name of
the busbar or at any other text in the single line diagram. This is much more
convenient than having to zoom in and out in order to read something.

Figure D.1: Resizing a busbar

Create two other busbars in the same way:

select the button in the graphic toolbox again. Place the second and
third busbar.

move and/or resize the second and third busbar to fit the background
pattern.

The drawing may be too small to accurately position the busbars. To zoom in on
the three busbars:

left click the zoom button ( )

draw a square around the three busbars by left clicking the first corner,
holding the mouse key down, and dragging the mouse to the other corner.
The selection square will be zoomed when the mouse key is released.

The previous zoomed area can be restored by pressing the button. The
whole area is shown when the button is pressed.

Getting Started Tutorial D-26

DIgSILENT PowerFactory Step 1: Creating Power System Elements

D.2.2 Creating Branch Elements

The busbars are to be connected with transformers:

left click the button in the graphic toolbox.

To draw the first transformer, left click the upper busbar at the position
suggested by the background pattern. The transformer is now connected
to that busbar at that position.

left click the middle busbar to make the second connection.

Use the same method to connect a second transformer between the

middle and lower busbar.

To switch to the edit mode select the in the graphical toolbox, press
the E SC key or simply press the right mouse button once.

The single line diagram, without the background, should now look like Fig. D.2

Figure D.2: Three busbars and two transformers

If something else than a transformer appears or if the connection was not made
as intended, press the U NDO button ( ) to delete the created transformer.
Pressing the C ANCEL while drawing will cancel the drawing of the transformer.

The transformer may be moved in somewhat the same way as a busbar is

resized:

left click a transformer to select it.

left click the selected transformer, hold down the mouse key.

move the transformer one or two grid points left or right by dragging.

release the mouse button.

Getting Started Tutorial D-27

DIgSILENT PowerFactory Step 1: Creating Power System Elements

Normally, you cannot drag the transformer outside the range of the two busbars.
If you try this, it will be positioned at the busbars, as far to the right or left as
possible. If you try again from this position, you can drag it outside the range.

move the transformer back to its correct position. If the connections were
crippled during the first move, press the ( U NDO ) button to undo the move.

You can also draw the transformer symbol again by right clicking it, and selecting
Reconnect Graphically. This will mark the two busbars to which the transformer
is electrically connected. You can re-draw the transformer again, but you have to
connect it to the two marked busbars.
The option Reconnect Graphically is available for all symbols in the single line
diagram and it can be used to restore the diagram.

Left clicking the upper and then the lower busbar creates a straight connection.
The transformer symbol is placed in the middle. A non-straight connection would
have been made if we would

• First left click a busbar to make the first connection.

• Left click the drawing surface to define corners in the connection line.

• Double click on the drawing surface to place the transformer symbol.

• Left click the drawing surface again to draw the second connection line.

• and left click the second busbar to make the second connection.

You may want to practice this now, using the option Reconnect Graphically.

D.2.3 Creating Single Port Elements

Single port elements are power system elements which are connected to one
busbar: generators, motor, loads, external grids, etc.

The tutorial grid has two asynchronous machines:

press the button in the toolbox

connect the first machine to the lower busbar by left clicking it on the
position as shown by the background pattern.

connect the second machine to the middle busbar

Left clicking a busbar places the single port symbol with a straight connection.
Non-straight connections may be made by first left clicking the drawing area to
place the symbol, then to draw a non-straight connection and finally left clicking
the busbar to make the connection.

To finish off the tutorial grid, we need to place the external grid:

Getting Started Tutorial D-28

DIgSILENT PowerFactory Step 1: Creating Power System Elements

press the button in the toolbox

left click the upper busbar to connect the external grid
If the external grid is connected to the busbar at the same position as the
transformer, the external grid symbol is automatically positioned above the
busbar. Otherwise, it is placed in the default position under the busbar.

Figure D.3: Flipping a symbol

If the external grid symbol is drawn in the downwards position, it may be flipped
upwards. If the external grid symbol is already positioned correctly, you may
want to practice the following on the machine on the middle busbar:
right-click the external grid symbol or the asynchronous machine. The
context sensitive menu appears (see Fig. D.3)
left click the Flip At Busbar option. The symbol is rotated 180 degrees
around its busbar connection.
Flipping is also possible with non-straight connections.

This concludes the creation of the power system elements and the topology.
Please check that all symbols are positioned correctly. Use ‘move’, ‘resize’
and/or ‘flip at busbar’ to correct the single line diagram.

The elements, however, have not been edited yet, and are all using default
parameters. Entering the parameters is the next step.

We don’t need the background pattern anymore. To hide it, we have to disable
the graphical layer on which it is drawn. For every group of graphic symbols,
such a layer exists. To hide the background:

Getting Started Tutorial D-29

DIgSILENT PowerFactory Step 1: Creating Power System Elements

press the “Show Layer” button ( ). The Graphics Layer dialogue

appears. The “Background” layer is shown in the left pane (‘visible’).
hide the background by moving it to the right pane: left click the
“Background” layer and press the button. This moves the background
to the list of invisible layers.
close the layer dialogue with the OK button. The single line graphic will
now look more sharp.

D.3 Editing the Power System Components

The PowerFactory program offers several methods for editing the electrical
parameters of power system elements, from simple edit dialogues to flexible
spreadsheet-like environments where more than one element is visible at the
same time.

The most simple and direct method, however, is to double click the elements in
the single line graphic, which opens their edit dialogue.

To avoid unintended changes to the single line diagram, press the to freeze
the diagram.

Almost all of the power system elements are using “type” objects. A large group
of transformers, for instance, may all be of the same type. Most of the electrical
parameters are thus defined in a transformer “Type” object and each transformer
will reference that type.

Normally, this would mean that a library of user defined types has to be created
prior to defining power system elements. However, for this tutorial all needed
types have been predefined and are ready to use.

D.3.1 Editing Busbars

To edit the upper busbar:
double click the upper busbar. The edit dialogue for the busbar, as
depicted in Fig. D.4 will pop up
This dialogue shows:
• Page tabs which are used to enter calculation specific parameters (“Basic
data”, ”Load Flow”, etc.)
• The station to which this busbar belongs, with a button which opens the
edit dialogue of that station

Getting Started Tutorial D-30

DIgSILENT PowerFactory Step 1: Creating Power System Elements

Figure D.4: The busbar edit dialogue

• The name of the busbar

• Its type, with a button to select a type and one to edit the type

• A nominal voltage

• A section number, which cannot be edited.

To edit the upper busbar:
Name = “D1 Swab”

left click the type selection button ( ) and choose the Select Project
Type option. This opens the busbar library in the database tree, and the list
of the busbars types in that library is shown. See Fig. D.5. This busbar
library has been installed by the Tutorial Manager.

select the Bar 33 kV type by left clicking the small object icon as depicted
in Fig. D.5. Holding the mouse still above the object icon will bring a
balloon help.

press OK to select the busbar type. The busbar edit dialogue will
become active again.

set the nominal voltage to 33 kV. The nominal voltage of a busbar may be
different from that of its type. The selected busbar type is designed for 33
kV, but may be used for other (lower) voltage levels.

press OK
The middle busbar is edited in the same way:
Name = “D1 11a”

select the type: use ; Select Project Type; Bar 11 kV

nominal voltage = 11 kV

Getting Started Tutorial D-31

DIgSILENT PowerFactory Step 1: Creating Power System Elements

Figure D.5: Selecting a busbar type

press OK
The lower busbar is at 3.3 kV:
Name = “D1 3.3a”
type = project type: Bar 3.3 kV
nominal voltage = 3.3 kV
press OK

D.3.2 Jumping to Other Elements

All element edit dialogues are equipped with a J UMP TO... button. Pressing
this button either jumps directly to the connected element, if there is only one
such an element, or shows a list of connected elements from which one may be
selected.
To practice this:
double click the external net symbol to open its dialogue.
press the J UMP TO... button. The dialogue of the top busbar now
appears.
press the J UMP TO... button again. A list of connected elements appears.
Select the transformer. The edit dialogue of the transformer appears.
etc.
Press the C ANCEL button in any edit dialogue to exit without changes.

Getting Started Tutorial D-32

DIgSILENT PowerFactory Step 1: Creating Power System Elements

D.3.3 Editing Branch Elements

To edit the top transformer:
double click the transformer to open its dialogue

Name = “T1 33/11a”

the dialogue shows the connected busbars. These fields have been set
when the transformer was connected in the single line diagram. The
names of the busbars are shown in red.

type = project types: TR2 20;33/11;10%. Observe that the option Select
Project Type automatically opens the Types Transformers library.

open the Load Flow page by left clicking the page tab

check that the automatic tap changer is disabled and that the tap position
is set to zero.

press OK
An error message will be displayed if the HV and LV sides of the transformer are
connected wrongly. In that case:
press the F LIP C ONNECTIONS button on the Basic Data page.

press OK again
To edit the other transformer:
open its dialogue

Name = “T1 11/3.3a”

type = project types: TR2 5;11/3.3;5%

check on the Load-Flow page that the automatic tap changer is disabled
and that the tap position is set to zero.

D.3.4 Editing Single Port Elements

To edit the external net:
open the edit dialogue. The external grid element has no type. All electrical
data is stored in the element itself.

Load Flow data:

– Name = “Transmission Grid”

– Bus Type = “SL” (slack).
– Angle = 0.0 deg

Getting Started Tutorial D-33

DIgSILENT PowerFactory Step 1: Creating Power System Elements

– Voltage Set Point = 1.0 p.u.

VDE/IEC Short-Circuit:

– Short Circuit Power Sk” = 10000 MVA

– R/X ratio = 0.1

press OK

To edit the 11 kV asynchronous machine:

open its dialogue

Name = “ASM1a”

type = project types: “ASM 11kV 5MVA”

load flow page: Active Power = 4 MW.

press OK

To edit the 3.3 kV asynchronous machine:

open its dialogue

Name = “ASM1b”

type = project types: “ASM 3.3kV 2MVA”

load flow page: Active Power = 1 MW.

press OK

This concludes the definition of the first step of the power system definition. We
may now start a calculation.

D.4 Performing a Load Flow

A load flow calculation may be started from the main menu (Calculation - Load
flow...), or by pressing the Load Flow button ( ) on the main toolbar. This will
bring the load flow command dialogue to the front, as depicted in Fig. D.6
This command dialogue offers several options for the load flow calculations.

for this first tutorial load flow, check that the following options are set:

– Network representation: “Balanced, positive sequence”.

– Disable all other options on the basic options page. The red command
line should now read “ldf/lev/secc”.

Getting Started Tutorial D-34

DIgSILENT PowerFactory Step 1: Creating Power System Elements

Figure D.6: The load flow command dialogue

press the E XECUTE button

A load flow calculation is now started. If the tutorial power system was entered
correctly, the following message should appear in the output window:

DIgSI/info - Element ’Transmission Grid.ElmXnet’ is local reference

in separated area ’Station1\D1_Swab.StaBar’
DIgSI/info - Calculating loadflow
DIgSI/info - load flow iteration: 1
DIgSI/info - load flow iteration: 2
DIgSI/info ---------------------------------------
DIgSI/info - Loadflow converged with 2 iterations

If an error was found, an error message like the following could appear:

DIgSI/err - ’\User\Tutorial\Part 1\T1_11/3.3a.ElmTr2’:

DIgSI/err - missing type !

The load flow calculation may nevertheless continue! In this case (the
transformer has no type set), the load flow calculation is so intelligent as to
disconnect the transformer and to calculate a load flow for the two remaining
areas. Although this will not be the load flow that we’re after, the calculated
results are often useful for locating the problem.

Getting Started Tutorial D-35

DIgSILENT PowerFactory Step 1: Creating Power System Elements

To resolve the error, one should first find the element for which the error was
reported. With the interactive PowerFactory output window, this is easy: just
double click the line with the element’s name. This will automatically open the
element’s edit dialogue. Correct the error and try the load flow again.

The correct load flow message shows that the load flow command has found
one separate network in the system and recognized that the only possible power
source was the external net element.

The single line graphic shows the results of the loadflow in the result boxes, as is
depicted in Fig. D.7.

Figure D.7: Results of the load flow calculation

In this figure, the balloon text help which appears if the cursor is held still over a
result box is shown also. Especially when a larger part of a power system is
viewed, the result boxes may become hard to read. The balloon help may then
be used to view the results.

D.5 Editing the Result Box Format

The result boxes are not fixed to the currently visible result parameters, but may
be freely edited. PowerFactory offers highly flexible result box definition tools
with which about any possible result box format may be defined.

In this tutorial, only the most direct way of changing a result box definition is
used. For some users, this method may be sufficient for their needs. Other users
may want to read the parts about editing result box definitions in the User’s
Manual after they finished the tutorial.

To understand the way the format of the result boxes is managed and edited, its
important to understand the nature of the PowerFactory result boxes.

Getting Started Tutorial D-36

DIgSILENT PowerFactory Step 1: Creating Power System Elements

D.5.1 About Result Boxes

A PowerFactory result box is actually a tiny calculation report. In principle,
there is no difference between a complex multi page load flow report and the
small result box of a line. Both reports are generated by so-called result forms,
which use the DIgSILENT output language to define the contents of the report.

Just to get some idea about what this is all about, the following example of a part
of a result form is given. This example has been taken from a large load flow
report format, which included macros, loops and many other reporting
commands. The example shows a piece from the heading of the report, where
totals are reported for the generation and motor load active and reactive power.

Generation Motor |$HE

Load |$HE
[# ]/ [# ]/ |$HE,[c:Pgen,[c:Pmot
[# ] [# ] |$HE,[c:Qgen,[c:Qmot

Important here is to understand that we may also write such report forms for the
result box of a line. Because we want to see other results after we’ve performed
a short circuit calculation than after a load flow calculation, we may create two
small report forms; one for reporting, for instance, the initial short circuit current
and apparent power, and one for reporting the active power, the reactive power
and the power factor.

It is thus clear that it must be possible to create and select a result box format for
each available calculation function. Besides that, we generally want to see other
results for branch elements than for node elements. The flexibility of the
PowerFactory result box formats even extends these basic requirements by
offering the definition of results boxes for different projects, for a single edge
element or for all edge elements at once, for a single particular element or for
element classes (lines vs. transformers, for instance), etc., etc. This flexibility
leads to a high amount of result box formats. To manage all these formats,
without losing track, the following features are offered:

• The PowerFactory program is shipped with a complete range of default

result box formats, which are stored in a read-only folder

• New, user defined formats are stored in an user defined folder, and will be
based on the default formats.

• A very flexible Form Manager is used to assign result formats to all

elements or to all edge and node elements, as long as they have not been
assigned their own format before. It is therefore possible to use special
dedicated formats in some cases, without losing the ability to change the
overall format without much effort.

• The result box format of all edge or node elements may be chosen in the
main menu from a small, possibly user defined, selection.

Getting Started Tutorial D-37

DIgSILENT PowerFactory Step 1: Creating Power System Elements

In the following section, the result box format of the external network element will
be changed.

D.5.2 Editing the Result Box Format

The top result box of the top transformer shows P,Q and loading. For example,
we want to change this to P,Q and current. To change the result box definition:
Freeze the single line diagram ( )
right click result box. This pops up a small menu.
Holding the mouse still at one of the the Format for ... options will show a second
menu. You can select another result box format from this list. The menu shows
with a small which format is being used.

Selecting the option Edit format for ... will open the currently used form definition
dialogue.
select the option Edit Format for Edge Elements
Press the I NPUT M ODE button and select Predefined Variables if this is
not selected yet. Press OK .
The “Line” frame shows three drop-down boxes which show the currently
selected variables.
press the select button for the third line (which shows ”c:loading”) and
select the variable
“m:I: LOCALBUS kA Current, Magnitude”
press the OK button

Observe the change in the result box for the transformer. It now shows the
current. Try the balloon help: it has changed too.
Observe that all result boxes for the transformers have changed.
select the option Edit Format for Edge Elements again. Try setting the
number of digits to 3 or 4, or adding the unit by using the Unit check box.
If the result box becomes too small to display everything:
Un-freeze the diagram ( )
right click the result box and select the Adapt width option
It is often not necessary to add units or descriptions to the result box format
because these are also given in the single line legend, and are shown in the
balloon help. The legend in the lower left corner of the single line diagram is
automatically updated when the result box formats are changed.

The legend is shown or hidden by pressing the button.

Getting Started Tutorial D-38

DIgSILENT PowerFactory Step 1: Creating Power System Elements

Figure D.8:

D.6 Performing Short-Circuit Calculations

A short-circuit calculation may be started from the main menu (Calculation -

Short-Circuit), by pressing the short-circuit button ( ) on the main toolbar, or
directly from the single line graphic:
Freeze the diagram
right click the 11 kV busbar “D1 11a”, and select the Calculate -
Short-Circuit option. This opens the short-circuit command dialogue, as is
depicted in Fig. D.9

set the Method = “According to IEC”

set the Fault Type = 3-phase Short-Circuit
Check to have the Fault Location option “At All Busbars and terminals”
disabled
press the E XECUTE button

A short-circuit calculation is started for a short-circuit at the selected busbar only.

The results show the currents in the whole network, except for the load element,
which is neglected.
The output window should show the following message:
DIgSI/info - Short-circuit calculated at Busbar Station1\D1\_11a
DIgSI/info - Short-circuit calculation ready !

Getting Started Tutorial D-39

DIgSILENT PowerFactory Step 1: Creating Power System Elements

Figure D.9: The short-circuit command dialogue

To calculate short circuits for all busbars and terminals at once:

press the short-circuit button ( ) on the main toolbar
set the Method = “According to IEC”
set the Fault Type = 3-phase Short-Circuit
enable the Fault Location option “At All Busbars and Terminals”
press the E XECUTE button
A short-circuit analysis is made for all busses and terminals. The results are
given locally for each busbar or terminal as the short-circuit currents and power
that flows to that busbar or terminal in case of a short-circuit at that busbar or
terminal.

To calculate a multiple fault:

perform a balanced load flow
multi-select two busbars by using the C RTL -Key
right click the selection and select the Calculate→Multiple Faults... option.
The short-circuit command appears again. It should have the method set
to “complete” and the option “Multiple Faults” should be enabled.

Getting Started Tutorial D-40

DIgSILENT PowerFactory Step 1: Creating Power System Elements

press the E XECUTE button

The short-circuit currents and power in the network are calculated for the
simultaneous short-circuits.

Getting Started Tutorial D-41

DIgSILENT PowerFactory Step 2: The Data Manager

Chapter E

Step 2: The Data Manager

In the first step of the tutorial, the main menu, the main toolbar and the single
line graphics were used to
• create a new project and a new grid
• define and edit a new part of a power system
• calculate loads flows and short-circuits
• look at results
The database, in which all changes were stored, has not been used directly.

To view and use the database, we need to open a database manager:

press the button “new database manager” ( ) on the main toolbar. A
database manager window, as depicted in Fig. E.1 will open.

Figure E.1: The Database Manager

The database manager has two windows:

• The database tree window (left pane at “1”) which shows a tree
representation of the whole database
• The database browser window (right pane at “2”) which shows the contents
of the selected folder in the database

Getting Started Tutorial E-42

DIgSILENT PowerFactory Step 2: The Data Manager

E.1 The Database Manager: Basics

Users familiar with the Windows “Explorer” may want to skip this section.

The database tree window shows a hierarchical tree with ’Folder’ objects. If such
a folder contains other objects, it has a small plus sign ( ). This sign may be left
clicked to open the folder. The database browser in the right side panel will show
the contents of the open folder.

An open folder will show its status by a small minus sign ( ). Left clicking this
sign will close the folder. In Fig. E.1, the “User” and “Tutorial” folders are open,
all other folders are closed. The “Part 1” folder is selected in the tree, and its
contents are thus shown in the browser on the right.
Left click all minus signs until the database tree only shows the basic
DATABASE folder.

left click the plus signs until the folder DATABASE\U SER\T UTORIAL\PART 1
is open. The \U SER folder is your working folder; the one with the small
blue icon. It may have another name than U SER.
Double clicking a folder may also be used to expand and collapse folders.

Left clicking a folder in the database tree will show its contents in the database
browser:
left click the folder “Part1”. The browser now shows all objects created in
the first step of the tutorial.
The objects displayed in the browser may be sorted to the column field by left
clicking the column heads:
left click the column head “Name”. The objects are sorted to name.

left click the same head. The objects are sorted the other way around.

left click the empty first column head (above the icons, left of “2” in Fig.
E.1). This sorts the objects according to their class.
If the database manager is too small:
point the mouse at a border or corner of the database window. The mouse
cursor will change into a double arrow. The border/corner may now be
dragged to resize the window.

the whole database window can be moved by left clicking its title bar and
dragging the whole window (keeping the mouse button down).

the tree and browser window are separated by a vertical splitter bar. This
bar may be dragged to enlarge the tree or browser window

Getting Started Tutorial E-43

DIgSILENT PowerFactory Step 2: The Data Manager

E.2 Using the Database Manager

The database manager may be used to edit the power system components:

select the folder DATABASE\U SER\T UTORIAL\PART 1 (select it in the tree)

in the browser, double click the small icon for a transformer ( ). This will
open the same edit dialogue as was opened from the single line diagram.

close the edit dialogue with C ANCEL

The database manager is a very versatile object which may be used for many
things, i.e.

• create any kind of object ‘manually’, i.e. projects, calculation cases, type
libraries, calculation commands, design variant folders, etc. etc.

• copy and paste parts of the database from one folder into the other

• look at results in table format

• edit objects in table format

• import and export parts of the database

E.3 Initializing Step 2

The Tutorial manager is used again to install some additional settings for this
second step of the tutorial:

select the File - Setup Tutorial option on the main menu

select the Initialize Step 2 option in the Tutorial Manager

press E XECUTE

The single line diagram should disappear and reappear again with a different
background pattern.
In case of any reported errors:

• try to correct the problem and restart the Tutorial Manager

• if this doesn’t help: restart the Tutorial Manager and disable the Check
User Defined Project option. This will bring you to the start of step 2,
disregarding all errors.

Getting Started Tutorial E-44

DIgSILENT PowerFactory Step 2: The Data Manager

E.3.1 Adding a Branched-Off Line

We are now going to expand the system by adding a branched distribution cable
with loads, to the middle busbar.

We start by drawing the extra busbar right of the 11 kV busbar:

Un-freeze the single line diagram

select the button in the graphic toolbox and place the new busbar to
the right of “D1 11a”.
Because this busbar is electrically similar to “D1 11a”, we are going to copy the
data:
left-click “D1 11a”

Press and hold the “Ctrl”-key and left-click the new busbar. Both busbars
should now be selected.

right-click one of the selected busbars and select Edit Data. Alternatively,
double click the selected busbars. A database browser will open which
shows the two busbars.

select “D1 11a” by pressing the icon.

copy the busbar (either right click and select Copy, press the button or
press C TLR -C.

right-click the of the new busbar and select Paste Data

open the edit dialogue of the new busbar (by double clicking the icon)
and check that it has the “Bar 11kV” as type and 11 kV as the nominal
voltage.

close the dialogue and close the database browser ( OK buttons)

This method of copying data from the one to the other object can be used to
speed up the definition of networks and to reduce mistakes. A large distribution
system that uses many busbars which are electrically similar, for example, could
be drawn in the single line diagram. One of these busbars could then be edited
to have the correct type and voltage level. By selecting all similar busbars, and
opening a database browser as described above, the busbar data can be
copied, and pasted to all other busbars in one action.

Copying and pasting data is possible for all objects, including transformers, lines,
loads, generators, etc.

Of course, the new busbar needs a name of its own:

Open the dialogue of the new busbar (double click the busbar in the single
line graphics)

Getting Started Tutorial E-45

DIgSILENT PowerFactory Step 2: The Data Manager

Name = “D1 Swab”

To create the cable between the busbars “D1 11a” and “D1 Swab”:

select the “Line” from the toolbox

draw the line according to the background pattern: left click the first busbar,
left click the drawing area to create two corners, left click the other busbar

double click the line

Name = “L1 Swab”

Type = project type:“Cable 11kV800A” (the ’Line’ becomes a cable)
Length = 3 km

Press OK

We are now going to add a branched-off cable to the right 11 kV busbar:

select the “Short Terminal” element from the graphic toolbox

place the Short Terminal below the right busbar, at the end of the line
(between line end and load)

edit the terminal:

Name = “D1 Reut”

Type = “Bar 11kV”
Nominal Voltage = 11 kV.

select the “Line” from the toolbox

draw a straight line between busbar “D1 Swab” and the terminal

double click the line

Name = “L Swb Rt”

Type = project type:“Cable 11kV400A” (again a cable)
Length = 5 km

connect a load at the Short Terminal at the end of the line

Your single line graphic should now look like Fig. E.2.
To create the branches:

select the ‘Load” element from the toolbox

Getting Started Tutorial E-46

DIgSILENT PowerFactory Step 2: The Data Manager

Figure E.2: New cable, short terminal and load

left click ON THE LINE, at the position where the upper load is connected.
A ‘Branch-Off Element’ dialogue should pop up. If this doesn’t happen, but
a single load symbol is placed on the diagram, the line was missed. Press
C ANCEL to try again in that case, possibly after the area has been zoomed.
To insert the load into the line, a small terminal is inserted. The Place Feeder
dialogue is used to define the physical position of the terminal and if switches
should be inserted.
set the New Position to 4 km. The Place Feeder dialogue shows the valid
interval (0 to 5 km).
the Switch options (Right / Left Switch) should be disabled
press OK
The new load symbol is attached to the line 90 degrees turned.
The physical position of the line-branch has no relation to the graphical distance
of the branch to the top busbar, as seen in the single line diagram. Of course,
the order of the branches in the diagram equals the physical order, but the
graphical distances between them have no meaning.
insert the lower load in the same way. Set it at 4.8 km, also without
switches
It is also possible to connect a load on the left side of the line:
press the C TRL key on the keyboard
insert the third load between the two other ones while holding the C TRL
key down

Getting Started Tutorial E-47

DIgSILENT PowerFactory Step 2: The Data Manager

Set the load at 4.4 km

enable the left switch option.

The third load is now inserted 180 degrees turned. It is also possible to insert an
element normally, to right click it thereafter with cursor, and to select Flip At
Busbar. This will rotate the element 180 degrees around its busbar connection.

This concludes the topological changes for the second step of the tutorial. The
grey background pattern is not needed anymore:

press the Show Layers button ( ) on the single line toolbar. This opens
the layers edit dialogue.

the “Background” layer is in the “Visible’ pane. Left click it to select it and
press the button to move it to the “Invisible” pane. Double clicking the
“Background” layer does the same.

close the dialogue

The background is now invisible.

Freeze the diagram again

E.3.2 Editing the New Elements

Because we already set a type and a length for the branched-off line, we don’t
have to edit it again. However, by inserting the loads, we divided the line in
so-called line routes. These line routes automatically inherit the line type of the
divided line. For the first route, this would lead to overloading. For this route, we
need a bigger cable:

double click the first line route (the line between the top busbar and the first
branched off load). Make sure to click fast enough, because single clicking
the route twice will select the whole line (and three times selects the line
and all branches). In that case, left click somewhere outside the line and
try again.

edit the line route:

Name = “LR Tub”

Type = “Cable 11kV800A”

The other three line routes still have their default names:

Double click the second line route from above

Name = “LR Dus”

Name the third terminal:

Getting Started Tutorial E-48

DIgSILENT PowerFactory Step 2: The Data Manager

name = “LR Gom”

and the bottom one

name = “LR Reut”

The insertion of loads into the line not only created line routes, it also inserted
terminals between the routes. The loads were connected through those
terminals. We have to edit these terminals too. It would however be a nuisance
to edit them one by one, as they all are the same. We therefore are going to use
the “multi-edit” capabilities of the database browser.
left click somewhere on a route

left click the marked route again. The whole line will be marked

right click somewhere on the marked line. Select the Edit Data option from
the menu. A database browser appears, filled with all marked elements: 4
line routes and 3 terminals
Alternatively,
left click somewhere on a route, wait a moment

double click on the route. This also selects the whole line and opens the
data browser.
The browser shows, amongst other parameters, the names and types of the
elements. For the line routes it should show that “LR Tub” has the type “Cable
11kV800A”, and the other three have the “Cable 11kV400A”, as expected. The
types of the three terminals are not set yet. This we are going to change now:
double click one of the terminal icons in the browser ( ) in the first
column. This opens the terminal edit dialogue.

set the type to: project types:“Bar 11kV”

close the dialogue with OK

We now return in the browser, which now shows the selected type for the edited
terminal. The two other terminals should get the same type, which is the reason
why we are going to copy the type from the first terminal to the other two:
left click the type field of the edited terminal. This selects the field: See Fig.
E.3, left.

select the option Copy from the context sensitive menu or use C TRL + C

left click the empty type field of one of the other terminals and select the
option Paste from the context sensitive menu or use C TRL + V. This copies
the type. See Fig. E.3.

paste the type again for the other terminal

Getting Started Tutorial E-49

DIgSILENT PowerFactory Step 2: The Data Manager

Figure E.3: Copy and paste in the browser

The browser should now show all elements having their type field set.

close the browser with OK .

Of course, the end-terminal is not a part of the line and should be edited by
double clicking the symbol. Set its data to

Type = project types: Bar 11 kV

Nom. voltage = 11 kV

The end-terminal may already have the correct type and nominal voltage set.

The copy and paste method is now used to set the types of the four new loads.
In that way, the chance of leaving one load out or making a mistake is reduced.

multi select the four new loads (select the first, keep the C TRL down and
select the others)

right click the selection and choose Edit Data. A browser with the four
loads pops up. None of them should have its type field set yet.

open the dialogue of the first load (double click the icon), set its type to
project types:“General Load” and close the dialogue

copy and paste the type to the other loads

Copying and pasting data from one element to another is just one of the many
data editing features of the database browser. Every parameter may be copied
and pasted, and most of them may be edited directly without having to open the
edit dialogue, as if we were using a spreadsheet. However, we will now continue
to use the single line graphics:

close the browser

The new loads have to be edited now separately to set their power demand.

Edit the top load:

open its edit dialogue and open the load flow page.

Getting Started Tutorial E-50

DIgSILENT PowerFactory Step 2: The Data Manager

Name = “Tubin”
Balanced/Unbalanced = Balanced
Active Power = 4.0 MW
Power Factor = 0.9
Voltage = 1.0 p.u.

When the Active Power and/or the Power Factor are not visible, select “P,
cos(phi)” as “Input Mode” for the load. Then you can enter the power factor
“cos(phi)”. All loads are assumed to be inductive (standard).

edit the middle load:

Name = “Duslin”
Balanced/Unbalanced = Balanced
Active Power = 1.0 MW
Power Factor = 0.9
Voltage = 1.0 p.u.

the bottom load:

Name = “Goma”
Balanced/Unbalanced = Balanced
Active Power = 1 MW
Power Factor = 0.9
Voltage = 1.0 p.u.

and the load at the end terminal:

Name = “Reutlin”
Balanced/Unbalanced = Balanced
Active Power = 3 MW
Power Factor = 0.9
Voltage = 1.0 p.u.

This concludes the design of the second step of the tutorial power system.

E.4 Performing Calculations

perform a Load Flow calculation:

– Balanced, positive sequence

Getting Started Tutorial E-51

DIgSILENT PowerFactory Step 2: The Data Manager

– All other options disabled.

Observe that the branched-off line shows small percentage values beside each
line route. Use the zoom button to enlarge the area around the new line. If you
want to move the values a bit:

left click the values and drag them to a better position

These percentages show the line loading. Because the first route was set to be
a bigger cable, the loading of this route is less than the loading of the other
routes, although it carries a higher current.

Because we inserted a switch in the line just before the middle load, we may
switch off the last three loads:

enlarge an area around the middle load

right click the serial switch in the route

select Open. The switch symbol will turn white

zoom out and perform a load flow. Observe the differences

Alternatively,

Double click the switch to open it or to close it.

With the line open, a short-circuit on the end-terminal makes no sense:

right click the end-terminal

select Calculate - Short-Circuit

perform a short-circuit calculation according to

– Method : According to IEC

– Fault : 3-phase

This will lead to errors, because there is no generator unit found in the
separated network.

close the switch again in the same way as it was opened

perform the short-circuit calculation again. It will now execute normally.

This concludes the second step of the tutorial.

Getting Started Tutorial E-52

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

Chapter F

Step 3: Creation of a Second

Subsystem

In this third step, we will create the second part of the tutorial power system,
which is a high voltage transmission system.

F.1 Setting Up Step 3

For this third tutorial step, we need a new Grid folder:

If the Tutorial project is not active:

– select the File and select the Tutorial project from the list of recently
active projects.
– if you can not find an entry for the tutorial, refer to the ‘Trouble
Shooting’ list at section B.5, page B-16.

make sure that the study case “Case 1” is activated. It should be visible in
the Study Case List in the main menu. If no study case is shown, select
“Case 1”.

select the Edit - project option on the main menu. This opens the project
edit dialogue

press the N EW G RID button. This opens the ElmNet dialogue

enter the name of the new grid as “Part 2” and press OK . An “Open
Grid” query will ask what to do with the new grid

select the option add this Grid/System Stage to active Study Case?

press OK

As was done in the previous steps, we have to execute the Tutorial Manager to
do some preparations for the third step:

open the Tutorial Manager

select the Initialize Step 3

Getting Started Tutorial F-53

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

press E XECUTE

correct any errors

A new, empty single line graphic will pop up, which shows a background pattern
of a small transport system. You are now ready to enter that transport system.

F.2 Creating the Topology

The single line diagram shows a pattern with four double busbars and some
loads and generators attached to them. You are going to create these elements.

Zoom in on the background pattern and create the double busbar systems:

un-freeze the single line diagram

select the Double Busbar System (DBS) from the toolbox

place the upper DBS.

select both busbars of the DBS by drawing a rectangle over them: left click
the drawing sheet, drag the mouse to draw the rectangle, release the
mouse to select both busbars. The DBS does not have to fit in the square:
every element that is partly in the square will be selected. In Fig. F.1, two
busbars are about to be selected by dragging a small square over them.
Be sure to also select the buscoupler before moving.

move the DBS if it does not coincide with the background pattern.

enlarge the DBS by dragging one of the right side black squares, until it fits
the background pattern. Because both busbars are selected, both are
enlarged by dragging the black square.

Figure F.1: Selecting two busbars

place the left, middle and right busbar systems as shown in the background
pattern and enlarge and/or move them to cover the background pattern

Getting Started Tutorial F-54

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

create the loads at the four busbars, according to the background pattern.
The load at the upper DBS has to be placed above the DBS: press the
C TRL key when placing it or use the “Flip at Busbar” option.

create three synchronous machines at the upper, left and right DBS. The
machine at the upper DBS has to be placed upside down again.

Connect the busbars with lines:

create the 6 lines according to the background pattern.
The topology is thereby complete and the background pattern is not needed
anymore:
hide the background pattern ( button)

freeze the diagram again

F.3 Editing the Elements

All the busbars of the system (there are 8) are equal: they all are designed for
110 kV. It thus is a good idea to edit them by copying data:
press the button E DIT RELEVANT OBJECTS FOR CALCULATION on the
main toolbar ( ). This will show a list with icons for all object classes
found in the active project.

press the B USBAR (*.S TA B AR ) button ( )

a database browser appears with all busbars in the project

double click the first busbar icon ( ) and edit the busbar to have

– Type = project:Bar 110 kV

– Nom. Voltage = 110 kV

close the busbar dialogue. The browser now shows the type and nominal
voltage.

first left click, then right click the entered “Type”-field in the browser and
select Copy.

left click the empty “Type” field of the second busbar. Drag the mouse to
the empty Type field of the last busbar. Release the mouse key. All the
empty “Type” fields should now be selected.

right click the selected fields and select Paste. The busbar type is now
copied to all other busbars at once.

Getting Started Tutorial F-55

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

repeat the copy and paste for the Nominal Voltage.

close the browser

The copy and paste method is now used to enter the type for the 6 lines.

press the button again and select the line symbol ( )

edit the first line in the browser:

– Type = project:OHL 110 kV

copy the type to the other 5 lines

close the browser

Although the lines all share the same line type, they have different lengths. To
enter the line lengths:

edit the four vertical lines from the upper DBS to the left and right DBS, by
double clicking them

– Length = 60 km

edit the remaining two lines to the center DBS:

– Length = 20 km

Give each busbar its name:

double click each busbar to edit:

– Top Busbars : Name = “B110 1a” and “B110 1b”

– Left Busbars : Name = “B110 2a” and “B110 2b”
– Middle Busbars : Name = “B110 3a” and “B110 3b”
– Right Busbars : Name = “B110 4a” and “B110 4b”

Name the lines:

The lines between “B110 1x” and “B110 2x”

– Name = “L12a” and “L12b”

The lines between “B110 1x” and “B110 4x”

– Name = “L14a” and “L14b”

The line between “B110 2x” and “B110 3x”

– Name = “L23”

Getting Started Tutorial F-56

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

The line between “B110 4x” and “B110 3x”

– Name = “L43”

Edit the 6 loads:

press the button again and select the line symbol ( )

edit the first load:

– Type = “General Load”

– Active Power = 100 MW
– Power Factor = 0.95

You have to left click the “Load Flow” tab to get to the power demand
parameters.

paste the Type, Active Power and Power Factor to the other five loads. The
browser also has a “Load Flow” tab.

close the browser

Name the loads at the top, left and right busbar systems. Double click to edit
each of them.

Top load : Name = “Ld 1”

Left load : Name = “Ld 2”

Right load : Name = “Ld 4”

The loads at the middle busbar system have a different power demand. Double
click to edit each of them.

edit the left load:

– Name = “Ld 3a”

– Active Power = 40 MW

edit the right load:

– Name = “Ld 3b”

– Active Power = 40 MW

edit the center load:

– Name = “Ld Swab”

– Active Power = 20 MW
– Power Factor = 0.90

Getting Started Tutorial F-57

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

Finally, edit the generators one by one:

edit the top generator:

– Name = “SM 1”
– Type = project:SGEN150M/110kV

Load flow page:

– Reference Machine = enabled

– Voltage Control = Voltage
– Voltage = 1.0 p.u. for the Dispatch

edit the left generator:

– Name = “SM 2”
– Type = project:SGEN150M/110kV
– Reference Machine = disabled
– Voltage Control = Power Factor
– Active Power = 100.0 MW
– Power Factor = 0.95

edit the right generator:

– Name = “SM 4”
– Type = project:SGEN150M/110kV
– Reference Machine = disabled
– Voltage Control = Power Factor
– Active Power = 100.0 MW
– Power Factor = 0.95

When the Active Power and/or the Power Factor are not visible, press the
button on the “Dispatch” frame to select the power representation. You have to
disable a field in order to select another one. Here please deselect “Reactive
Power” and then select the power factor “cos(phi)”.
This concludes the definition of the second grid.

F.4 Performing Calculations

perform a load flow with the option “Consider Reactive Power Limits”
enabled

Getting Started Tutorial F-58

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

correct the system in case of errors

The secondary controller function for the power system (frequency control) is
performed by the top generator alone. The other two generators are fixed to a
certain PQ setpoint. Due to this control settings, the upper generator is heavily
overloaded. However, we cannot simply set all generators to the “SL” mode,
because this would create three reference busbars which would all have a
voltage angle of 0.0 degrees.

The solution is to select one reference busbar, for which the voltage angle will be
0.0, and to create a frequency controller object which will regulate the power
output of the generators.

edit all three generators:

– Reference Machine = disabled

– Local Voltage Controller = Voltage
– Active Power = 100.0 MW
– Voltage = 1.0 p.u.

This gives all generators a “PV” characteristic.

select the upper busbar system and the three generators

right click the selection and choose the Define... - Power Frequency
Controller option. The edit dialogue of a power frequency controller will
appear.

The frequency controller already has the “Bus Bar of Frequency Measurement”
field set. The selected generators are in the machine list.

Enable the option “According to Nom. Power”.

close the controller dialogue with OK

It is also possible to add generators to an existing frequency controller. This is

done from the single line diagram:

multi select the generators, right click the selection.

select the Add to - Power Frequency Controller. A list of existing frequency

controllers is shown from which the one must be selected to which we want
to add the generators.

the frequency controller dialogue appears. The generators are now added
to the machines list when they were not already in it.

close the frequency controller dialogue

The load flow will be different now:

Getting Started Tutorial F-59

DIgSILENT PowerFactory Step 3: Creation of a Second Subsystem

open the loadflow command. At the ‘Active Power Control” page, enable
‘according to secondary control’.

perform a load flow. Observe the changes: all generators are now
producing equal real power. The power contribution is not fixed but can be
changed in the frequency controller by setting it to “Individual active power”
and editing the percentages in the list.

The frequency controller can be reached by opening the dialogue of a

participating generator. The controller object is mentioned on the load flow page
at “external secondary controller”. The button beside it can be clicked to jump to
the controller.

This concludes the third step of the tutorial.

Getting Started Tutorial F-60

DIgSILENT PowerFactory Step 4: Connecting the Subsystems

Chapter G

Step 4: Connecting the

Subsystems

In the previous steps of the tutorial, a small distribution (“Part 1”) and a small
transmission system (“Part 2”) have been entered and tested. Load flow and
short circuit-calculations were performed for both systems. In this step, these
two networks are going to be connected to each other and calculations for the
resulting network will be performed.

G.1 Setting Up Step 4

To again install some additional objects and to check the tutorial project up until
this point, start the Tutorial Manager:

open the Tutorial Manager

select the option ”Initialize Step 4”

press E XECUTE

correct possible errors

The graphics board disappears, but nothing further happens! The grids are not
shown automatically this time.

G.2 Activation of the Two Subsystems

For the connection and analysis of the two subsystems, it should be possible to
switch from the one single line graphic to the other quickly and to perform
calculations for the combination of the two grids. Until now, only one subsystem
(“Part 1” or “Part 2”) was active at the same time. However, you may activate as
many grids, and add as many single line diagrams to the graphics board as
needed. For now, you need to activate and show the created “Part 1” and “Part
2”grids.

Getting Started Tutorial G-61

DIgSILENT PowerFactory Step 4: Connecting the Subsystems

A grid folder is activated by adding it to an active study case. The study case
keeps a reference to the active grids. The combination of the active grids will be
the target for all calculations. The study case will automatically deactivate all its
grids when it is deactivated itself, and will reactivate them again when it is
activated, using the grid references. You thus first have to activate the “Study
Case” by selecting it in the study case list in the main menu.

Figure G.1: Database tree

Grids can be added to a study case in a database manager:

open a database manager

open the Tutorial project in the tree. The tutorial projects should now look
like depicted in Fig. G.1. Both the tutorial project and the study case
should be active (red coloured icons).

Add the two grids to the study case by right clicking them and selecting
Add to Study Case. Their icons will also become red to signal their active
status.

close the database manager

The graphics board that will appear shows both single line diagrams. You can
switch between them by pressing the tabs on the bottom of the graphics board.

When a study case is deactivated, it will automatically close its graphics board.
When it is activated again, the graphics board will be shown again too.

We thus have two active grids, and two single line graphics. The background
pattern of the transmission system shows some alterations that are to be made.
First, check to see that both grids have been activated:

perform a load flow calculation with the following settings:

– Balanced network representation

– Consider reactive power limits
– All other options disabled

Getting Started Tutorial G-62

DIgSILENT PowerFactory Step 4: Connecting the Subsystems

The load flow command now sees one single network, which has two isolated
areas. It thus reports the following message:

DIgSI/info - Grid splitted into 2 isolated areas

Switch to the other single line diagram and observe that the load flow was
calculated for both grids. You may have to enlarge (zoom) the diagram a bit to
see the results in the result boxes, or point at a result box to get a balloon help.

You are now ready to connect the two grids.

G.3 Connecting Two Grids

The distribution grid (“Part 1”) is fed by an external net element, at 33 kV. The
transmission net has a load element in the middle which represents the
distribution grid.
In order to connect the two grids, we would need:

• to dispose of the external net object in the distribution grid, and the middle
load element in the transmission grid

• create a 110/33 kV transformer and connect the 110 kV double busbar

system in “Part 2” with the 33 kV busbar in “Part 1”

The first step is easy, because it concerns either the one or the other grid:

select and un-freeze the “Part 1” diagram.

left click the external net symbol and press the delete ( ) button. Answer
“Yes” to delete the object

select and un-freeze the “Part 2” diagram.

delete the load “Ld Swab” on the middle busbar system in the same way

The creation of the new transformer, however, is not possible. We cannot create
it because we need two busbars in a single line graphic in order to connect a
new transformer between them. The “Part 1” single line diagram doesn’t have
the 110 kV busbar system, and the “Part 2” doesn’t have the 33 kV busbar. At
least one of these busbars must be made visible in the other diagram.

We therefore have to create a second graphical representation of one of these

busbars:

Open the single line diagram “Part 1”, select the busbar “D1 Swab” and
copy it (either press the ( ) button, right click the selection and choose
copy, or press C TRL -C), as depicted in Fig. G.2.

Getting Started Tutorial G-63

DIgSILENT PowerFactory Step 4: Connecting the Subsystems

change to the single line diagram “Part 2”.

right click at the indicated position below the mid DBS in the diagram and
select Paste Graphic only, as depicted Fig. G.3.

Figure G.2: Copying a graphical object

Figure G.3: Pasting graphically

A new graphical symbol of the “D1 Swab” busbar is now created in the other
single line diagram. However, no new busbar is created in the database.
Electrically, there is still only one “D1 Swab” busbar.

Some additional aspects of the graphical copy and paste:

Getting Started Tutorial G-64

DIgSILENT PowerFactory Step 4: Connecting the Subsystems

• The same method for graphical copy and paste is available for all objects.

• Copy and Paste ‘graphically’ is also possible for more than one object at
the same time. The symbols are pasted in the same configuration as when
they where copied. Care must be taken to prevent symbols to be drawn
outside the drawing plane. A change to a larger paper size will bring these
objects back into focus.

• Only one graphical symbol of each object is allowed in each single line
diagram. It is not possible to graphically copy and paste inside the same
diagram.
To check upon the new busbar symbol:
Open its dialogue. Its name should be

...\Station 1\D1_Swab.StaBar

If the inserted busbar is called other than “D1 Swab”, you created a new busbar,
in stead of creating a new symbol for the existing “D1 Swab” busbar. In that
case:
press the “undo” button ( ) to dispose of the created busbar

try again
We have now created a second graphical representation of the busbar
“D1 Swab” in the single line diagram “Step 2”.

We may now connect the busbars by a transformer:

select the 2 winding transformer from the toolbox and draw a new
transformer between double busbar system and the copied busbar

edit the transformer:

Name = “T1 Swab”

Type = project:TR2 60;110/33

This concludes the topological changes for this step of the tutorial:
hide the background pattern

freeze both diagrams

The transformer now connects the two sub systems:

perform a load flow calculation.
The transmission system is now supplying the distribution network with about
14.5 MW. The whole system is regarded as a whole by all calculation modules:

Getting Started Tutorial G-65

DIgSILENT PowerFactory Step 4: Connecting the Subsystems

perform a short-circuit calculation for a 3 phase short circuit at the end

terminal of the branched-off line in the distribution system. The short-circuit
is now fed by the three generators in the transmission network.

This concludes the fourth step of the tutorial.

G.3.1 More About Multiple Graphical Representations

The method for pasting single power system elements from the database
manager into another single line diagram is just one of the methods of creating
single line representations of existing power system elements.

This method may be used as described for connecting two power system grids,
but it is not so suited for creating completely new single line diagrams for existing
grids. The PowerFactory software offers special tools for that.

If you are interested in creating single line diagrams from existing net data, you
may want to read the User’s Manual, chapter “Graphics Windows”, section
“Building From Predefined Objects”.

Getting Started Tutorial G-66

DIgSILENT PowerFactory Step 5: Motor Start Simulation

Chapter H

Step 5: Motor Start Simulation

Until now, only two calculation functions were used in this tutorial: the load flow
and the short circuit calculation. In this tutorial step, one of the generators in the
transmission network is going to be replaced by a more detailed model of a
power plant. This power plant has one large asynchronous motor. For the
resulting network, a motor start analysis will be performed.

H.1 Setting up Step 5

Start the Tutorial Manager:

close the database manager

activate the Tutorial manager

select the option Initialize Step 5

press E XECUTE

The graphics board should now show the two single line graphics from the last
step of the Tutorial.

perform a load flow to check the power system

H.2 Modelling the Power Plant

The top generator (“SM 1”) in the transmission system (Grid Part 2) is to be
replaced by a more detailed model of a power plant. That plant is already visible
in the background pattern. To delete the generator,

left click the generator and press the delete button ( )

answer the question by “Yes”

Getting Started Tutorial H-67

DIgSILENT PowerFactory Step 5: Motor Start Simulation

This generator, however, participated in the secondary control. This has to be

corrected:

open a browser with the secondary controls (press on the main

toolbar and ).

Open the secondary control dialogue.

The power-frequency control element is still using the deleted generator

“SM 1”, which is shown in red. Right click the row with this generator (right
click the number in the first column) and select Delete Rows. This clears
the generator from the power-frequency control element.

close the browser

To enter the model of the power plant:

use the background pattern to draw a new single busbar above the double
busbar system.

connect the busbar to the double busbar system by two lines

draw three short terminals above this busbar. Enlarge the right one

Connect the three short terminals to the single busbar with three
transformers

connect a synchronous generator to each of the left two terminals. Use the
Flip at Busbar utility (in the right mouse menu) if they are drawn
downwards

connect an asynchronous motor and a load to the right terminal. Press the
C TRL key while connecting to place them drawn upwards.

These elements form our power plant model.

This concludes the topological changes:

hide the background

freeze the diagram

H.3 Editing the Power Plant

multi-edit the two new lines to have

Name = “L pp1a” and “L pp1b”

Getting Started Tutorial H-68

DIgSILENT PowerFactory Step 5: Motor Start Simulation

Type = “OHL 110kV”

Length = 2 km

edit the single busbar:

Name = “PP110 1”
Type = “Bar 110kV”
Nom. Voltage = 110 kV

edit the three terminals:

Name = “Trm G1” (left at generator)

Name = “Trm G2” (right at generator)
Name = “Trm EB” (plant supply)
Type = “Bar 33kV”
Nom. Voltage = 33 kV

edit the two generator transformers:

Name = “Tpp1 G1” (left)

Name = “Tpp1 G2” (right)

Type = “TR2 60:110/33”

Flip the connections if needed.

edit the transformers for the plant supply

Name = “Tpp1 EB”

Type = “TR2 2;110/33”

Flip the connections if needed.

multi-edit the two generators:

Name = “PP1 G1” (left generator)

Name = “PP1 G2” (right generator)
Type = “SGEN 150M/33kV”
Reference Machine = Disabled
Voltage Control = Power Factor
Active Power = 50 MW
Power Factor = 0.95

edit the asynchronous machine:

Getting Started Tutorial H-69

DIgSILENT PowerFactory Step 5: Motor Start Simulation

Name = “PP1 ASM1”

Type = project:ASM 33kV 3MVA
Generator / Motor = “Motor”
Active Power = 2 MW (load flow page)

edit the load:

Name = “PP1 L1”

Type = “General Load”
Active Power = 0.5 MW
Power Factor = 0.80

perform a load flow to check the results.

The two new generators are set to 50 MW each and do not participate in the
secondary control. This is now changed:

multi select the generators, right click them and select Add To -
Power-Frequency Controller.... Select the Power-Frequency Control that is
shown in the browser. The secondary control adds the generators to its list.

Press the Control Mode = “Individual Active Power”. Edit the “Active Power
Percentages” in the list for the existing generators to have 33% and the
added generators (“SM 2” and “SM 4”) to have 17%.

perform a load flow to check the results.

H.4 Performing a Motor Start Simulation

You now have a system with four generators and a big asynchronous motor,
which is to be analyzed for its motor start capability.

To perform a motor start simulation:

multi select the asynchronous motor “PP1 ASM1” and up to three busbars
or terminals.

right click the asynchronous motor and select Calculate - Motor Startup

set a simulation time of 5 seconds.

A predefined motor startup calculation batch job is now started. This batch job
performs the following:

• it disconnects the asynchronous machine

Getting Started Tutorial H-70

DIgSILENT PowerFactory Step 5: Motor Start Simulation

• it calculates a new load flow

• it calculates the initial conditions for all dynamic elements

• it creates a new graphic board with several predefined output curves

• it starts a transient simulation and executes a “Switch Event” to switch on

the machine during simulation.

• it runs the simulation for 5 seconds. During the simulation, the result plots
are updated continuously.

The motor start batch job produces four graphs for the motor itself (showing
active power, current, etc) and one graph with the voltages of the selected
busbars / terminals. One of the resulting plots is displayed in Fig. H.1. It shows
the active power demand of the asynchronous machine during start up. If the
texts are too small to read, point at them and a balloon help will pop up, or use
the zoom buttons. From this graph, it is clear that the motor’s demands are
shortly more than 6 MW of active power.

Figure H.1: Active power demand during startup

After about 3.0 seconds, the motor reaches its nominal speed. The steady state
demand is about 2.4 MW and 1.1 MVar, which is also shown in the single line
diagram. This is somewhat surprising, because we did not define a mechanical
load for the machine. The 2.4 MW cannot be accounted for as losses, at least
not for a very long time. So, where’s the power used for?

The answer is found in the the motor dialogue.

double click the asynchronous motor to open its dialogue

At the RMS simulation” page, it shows parameters for a default mechanical load:

Proportional factor = 1.0 p.u. (=mdmlp)

Exponent = 2.0 (=mdmex)

Getting Started Tutorial H-71

DIgSILENT PowerFactory Step 5: Motor Start Simulation

These two parameters belong to the motor driven machine model ElmMdm 1,
which is described in the advanced technical reference manual. This is a fairly
simple model, determined by the power equation
xmdm = mdmlp · |speed|mdmex
The power demand is, with the exponent being 2, a quadratic function of speed.

Of course, this may not be the motor driven machine model that we want.

H.5 Changing the MDM

right click the asynchronous machine and select the option Define... -
Motor Driven Machine (mdm)
An “Element selection” dialogue will pop up, which is used to create new objects.
At this moment, it only shows a list of three predefined machine driven models
and one general dynamic model (“Common Model”).
select the Vers. 10.31-Model mdm 3 (ElmMdm 3) model
press OK
This creates a new ElmMdm 3 object. The dialogue of the MDM will pop up
automatically.
edit the values on the RMS-simulation page:
alf1 = 0.95 p.u.
slipm = 0.7 p.u.
exp1 = 2.0
alf2 = 0.35 p.u.
exp2 = 3.0
xkmm = 0.15 p.u.
press OK
The motor driven machine model is now automatically combined with the
asynchronous motor in a so-called “Composite Model”. The composite model
uses a Composite Frame, which is a block diagram which hard-wires controllers
and other models. The default Composite Frame for an asynchronous machine
is depicted in Fig. H.2. Although this Frame has four slots, only use the slots for
the asynchronous machine (“asm slot”) and the one for the motor driven
machine (“mdm slot”) are used in this step.
At this point, you do not have to worry about composite models, because adding
a MDM to an asynchronous motor is a standard action.

To see the implications of the new MDM,

Getting Started Tutorial H-72

DIgSILENT PowerFactory Step 5: Motor Start Simulation

Figure H.2: Composite Frame for asynchronous machine

repeat the motor start analysis

it takes now almost a second more for the machine to reach nominal speed.
This concludes this step of the tutorial.

Getting Started Tutorial H-73

DIgSILENT PowerFactory Step 6: Transient Analysis

Chapter I

Step 6: Transient Analysis

In step 5, we got a first glimpse of the transient analysis capabilities of the

PowerFactory software. The analysis, however, was more or less performed by
the software itself. In this sixth step of the tutorial, the more direct use of the
transient analysis features is shown.

I.1 Setting Up Step 6

Let the Tutorial Manager prepare the Tutorial step for you again:

activate the Tutorial manager

select the option Initialize Step 6

press E XECUTE

I.2 Composite Models Revisited

The active System Stage folder contains four generators, which are still lacking
any further models, such as prime mover models, primary controllers, voltage
controllers, etc. A realistic transient analysis is of course not possible with such
uncontrolled generators. In this step, you will add such controllers to the two
generators in the power plant and analyze the system for a short circuit at the
plant bus and the subsequent separation of the plant.

The default Composite Frame for a synchronous machine is depicted in Fig. I.1.
Although this Frame has six slots, we will only use the slot for the synchronous
machine (“sym slot”) and the ones for the voltage controller (“vco slot”), prime
mover unit (“pmu slot”) and primary controller (“pco slot”).

open and freeze the single line diagram for the transmission system (“Part
2”)

Getting Started Tutorial I-74

DIgSILENT PowerFactory Step 6: Transient Analysis

Figure I.1: Composite Frame for synchronous machine

right click generator “PP1 G2” and select

Define.. - Voltage Controller (vco)
select and edit the voltage controller according to the following data
Name = Vers. 10.31-Model vco 1
tvm = 0.011 s tst = 0.12 s
vssp = 50 p.u. efdmx = 3 p.u.
tspi = 0.5 s efdmn = -3 p.u.
ur mx = 3 p.u. kur = 1.0 p.u.
ur mn = -3 p.u. kui = 0.0 p.u.
terr = 0.12 s kir = 0.0 p.u.
vss = 0 p.u. kii = 0.0 p.u.
After you have defined the parameters of the Voltage Controller, the composite
model is shown with all the slots available in the frame and the already inserted
net elements. Here the elements are the VCO and the generator “PP1 G2”.

In a next step the generator “PP1 G1” gets a VCO, a primary mover unit, and a
primary controller:
right click generator “PP1 G1” and select
Define.. - Voltage Controller (vco)
select and edit the voltage controller according to the following data
Name = Vers. 10.31-Model vco 1
tvm = 0.01 s tst = 0.1 s
vssp = 50 p.u. efdmx = 3 p.u.
tspi = 0.5 s efdmn = -3 p.u.
ur mx = 3 p.u. kur = 1.0 p.u.
ur mn = -3 p.u. kui = 0.0 p.u.
terr = 0.1 s kir = 0.0 p.u.
vss = 0 p.u. kii = 0.0 p.u.

Getting Started Tutorial I-75

DIgSILENT PowerFactory Step 6: Transient Analysis

right click the generator “PP1 G1” again and select

Define.. - Primary Controller (pco)

select and edit the prime mover model according to the following data
Name = Vers. 10.31-Model pco 2
dband = 0.0 p.u. ty = 0.2 s
bp = 2 % tyo = 0.2 s
bt = 0.0 % tyc = 0.2 s
tp = 0.1 s yt mx = 1.0 p.u.
td = 0.1 s yt mn = 0.1 p.u.
tr = 0.1 s

right click the generator “PP1 G1” again and select

Define.. - Prime Mover Unit (pmu)

select and edit the primary controller according to the following data
Name = Vers. 10.31-Model pmu 6
tw = 0.1 s

I.3 Setting Up a Transient Short-Circuit

Simulation

We are going to test the behaviour of the controlled generators by simulating a

single phase short circuit at one of the lines which connect the power plant with
the transmission system. The single phase line fault results in the opening and
reclosing of the faulted phase and, because that does not clear the fault, the
complete separation of the line thereafter.

I.3.1 Defining Events

In order to define a short circuit at the line “L pp1a”, and the resulting switching
sequence, we have to define events:

• a short-circuit event

• switching events that will ultimately isolate the line

No protection devices are used.

The most easy way for defining events for a simulation is to initiate the simulation
and to create events by right clicking objects. Therefore:

activate the “Stability” toolbar by pressing the button on the main

toolbar (normally this toolbar is activated by standard)

Getting Started Tutorial I-76

DIgSILENT PowerFactory Step 6: Transient Analysis

press the button to open the initial calculation command

set the following options:

Method of simulation = Instantaneous Values (EMT)

Verify initial conditions = enabled
Automatic step size Adaptation = enabled

press E XECUTE

correct possible mistakes

With the simulation initiated, you may now start defining the events:
right click the line “L pp1a” and select Define ... - Short-Circuit Event. This
will create a new event and opens the event list

The new event is selected. Double click it to edit the short-circuit to have:

Execution Time = 0.0 s

Fault Type = Single Phase to Ground
Phase = a
Fault resistance = 0.0 Ohm
Fault Reactance = 0.0 Ohm

press the Edit button at the Object field ( ). The line dialogue appears.

At the EMT-simulation page, enable the option Short-Circuit at Line -

Available

close the line dialogue

close the event dialogue

close the event list

The Short-Circuit at Line option at the line object must be set to prepare the
calculation for a line with a short circuit event. This inserts an extra calculation
busbar at the fault location in the line.

To create the switching events:

Right click the top switch at line “L pp1a” and select Open. This will create
and show a new switch event.

Set the following data

Execution Time = 0.2 s

Action = Open
All Phases = disabled (press B ALANCED to get this option)

Getting Started Tutorial I-77

DIgSILENT PowerFactory Step 6: Transient Analysis

Phase b and c = disabled

Phase a = enabled

repeat this for the switch on the other side. If not the switch was right
clicked, but the line, an event for the other switch will automatically pop up
when the first is closed.

Right click the top switch again, and select Open.

Set the following data

Execution Time = 0.3 s

Action = Close
All Phases = disabled
Phase b and c = disabled
Phase a = enabled

Repeat for the other switch

and for a third time, right click the top switch, select Open and set

Execution Time = 0.4 s

Action = Open
All Phases = enabled

Repeat for the other switch

To check all this,
press the button to open the event list

check the events and correct mistakes

I.3.2 Defining Result Variables

In order to produce graphs from the transient simulation, we have to define
which variables are to be stored by that simulation. The PowerFactory software
has thousands of possible variables which could all be stored and analyzed.
However, storing them all would take too much time, would produce megabytes
of data and would make it very difficult to select a variable for displaying its
values in a graph.

The solution is to select a number of parameters prior to the simulation. This is

done by creating so-called “Variable Sets” for each power system element that
we are interested in. The Tutorial Manager has already defined some of those
sets, but, because this is a tutorial, the one for generator “PP1 G2” is missing.

To create the missing variable set:

Getting Started Tutorial I-78

DIgSILENT PowerFactory Step 6: Transient Analysis

freeze the single line diagram

right click generator “PP1 G2” and select Define..-Variable Set (sim). An
“Variable Set” object will pop up, like depicted in Fig. I.2.

Select the EMT-simulation page

Select “Variable Set” = “Currents, Voltages and Powers”

Select the variables

I:bus1:A kA Phase Current, Magnitude

I:bus1:B kA Phase Current, Magnitude
I:bus1:C kA Phase Current, Magnitude

press the button to move the variables to the right panel

Select “Variable Set” = “Signals”

Select the variables

psie p.u. Exitation-Flux

speed p.u. Speed
phi p.u. Rotor-angle
pt p.u. Turbine Power
xspeed p.u. Speed

Select “Variable Set” = “Calculation Parameter”

Select the variable

c:dfrotx deg Maximum Rotor Angle difference

close the variable set

I.4 Creating Plots

During the simulation, all variables defined in the variables sets are written to a
result file. That result file is used to define graphs and other kinds of virtual
instruments (VI’s).

Getting Started Tutorial I-79

DIgSILENT PowerFactory Step 6: Transient Analysis

Figure I.2: Defining a variable set

I.4.1 Adding Another Graph to a Subplot VI

To add another graph to an existing virtual instruments plot:

double click the Subplot to edit it.

right click the first, numbered, column of the Curves list

select “Append Cells”. A new line appears to define another curve

right click the empty Element field to select an element

double click the empty Variable field to select a variable

double click the Color, Linestyle or Linewidth field to set these parameters.

I.4.2 Adding a New Empty Graph on the VI Page

To add a new plot to an existing virtual instruments page:

press the “Append new VI’s” ( ) button

Getting Started Tutorial I-80

DIgSILENT PowerFactory Step 6: Transient Analysis

select the “Subplot (Visplot)” Object

set the number of new Subplot wanted (recommended is to start with 1)

at pressing OK , a new VI is added to the Virtual Instrument Panel

I.4.3 Creating a New Empty VI Page

To create a new virtual instruments page:

press the “Insert New Graphic” button ( ) on the Graphics Board toolbar
and select Virtual Instrument Panel

I.5 Running a Transient Simulation

The main toolbar shows two buttons for starting ( ) and stopping ( ) the
simulation.

press the start ( ) button. Enter an execution time of 3s.

press E XECUTE

The simulation is now started. The output window will show messages about the
events that are processed, when they are processed. The graphs will start
showing results.
All graphs can be scaled automatically in the x- respectively y-direction to the
best view by pressing the buttons and . Furthermore for a better
analysis of certain time period the x-axis can easily be zoomed in using the
’Zoom x-Axis’ button ( ).

I.6 Closing Up Step 6 of the Tutorial

In this step of the tutorial the following was explained:

• How to define Composite models for elements which were created in

different System Stages

• How to perform a transient analysis

• How to define new result variables

• How to change, create and modify Subplots

Getting Started Tutorial I-81

DIgSILENT PowerFactory Step 6: Transient Analysis

As with the other tutorial steps, it would now be possible to replace the user
defined sixth Tutorial Study Case by the prepared one. The advantage is that
small errors, or experiments, made in the system are replaced by the correct
versions of the networks. As this concludes the tutorial, there’s no need for
correction of the Study Case for further tutorial steps, however, it could be of
help when some difficulty was encountered during the construction of the sixth
tutorial step by the user, or if experiments led to an unclear situation, the Tutorial
Manager could (re)build the complete sixth step for you.

To replace the user entered sixth tutorial step by the prepared one:

select the option File - Setup Tutorial on the main menu to open the
Tutorial Manager

select the option Finish Step 6

press the OK button

Getting Started Tutorial I-82

Handling of Power Factory
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory About DIgSILENT PowerFactory

Chapter 1

About DIgSILENT
PowerFactory

The calculation program PowerFactory, as written by DIgSILENT, is a

computer aided engineering tool for the analysis of industrial, utility, and
commercial electrical power systems. It has been designed as an advanced
integrated and interactive software package dedicated to electrical power system
and control analysis in order to achieve the main objectives of planning and
operation optimization.

The name DIgSILENT stands for “DIgital SImuLation and Electrical NeTwork
calculation program”. DIgSILENT Version 7 was the world’s first power system
analysis software with an integrated graphical one-line interface. That interactive
one-line diagram included drawing functions, editing capabilities and all relevant
static and dynamic calculation features.

The PowerFactory package was designed and developed by qualified

engineers and programmers with many years of experience in both electrical
power system analysis and programming fields. The accuracy and validity of the
results obtained with this package has been confirmed in a large number of
implementations, by organizations involved in planning and operation of power
systems (please see the reference list).

In order to meet today’s power system analysis requirements, the DIgSILENT

power system calculation package was designed as an integrated engineering
tool which provides a complete ’walk-around’ technique through all available
functions, rather than a collection of different software modules. The following
key-features are provided within one single executable program:

1. PowerFactory core functions: definition, modification and organization of

cases; core numerical routines; output and documentation functions

2. Integrated interactive single line graphic and data case handling

3. Power system element and base case database

4. Integrated calculation functions (e.g. line and machine parameter

calculation based on geometrical or nameplate information)

5. Power system network configuration with interactive or on-line access to

the SCADA system

Handling of Power Factory 1-2

DIgSILENT PowerFactory About DIgSILENT PowerFactory

6. Generic interface for computer-based mapping systems

By using just a single database, containing all the required data for all equipment
within a power system (e.g. line data, generator data, protection data, harmonic
data, controller data), PowerFactory can easily execute any or all available
functions, all within the same program environment. Some of these functions are
load-flow, short-circuit calculation, harmonic analysis, protection coordination,
stability calculation and modal analysis.

1.1 Database Management and Backups

The PowerFactory database has been proven to be very stable. Nevertheless,

as is true for all electronic databases, it can be corrupted by external or internal
causes. External causes are such as power failures resulting in a sudden
system shutdown, harddisk crashes, computer viruses or inadvertent deletion of
files. To prevent any loss of data, please follow these instructions:

• Backup the database directory of all DIgSILENT PowerFactory

installations on a regular basis. A daily automatic backup is recommended.
This directory is named ”DB” and can normally (i.e. for a standard
installation) be found under C:
BS DI G SILENT\ PF XXX B YYY where XXX is the version number (e.g.
13.1) and YYY is the build number (e.g. 249) i.e. pf131b249

• Save all projects on a regular basis by right-clicking the project folder in the
database tree and selecting the Export Data option. This will prompt you
for a filename.
Note: By exporting a project, only the information in that project and all its
subfolders will be stored. If the exported objects use information (e.g.
power system types like line or transformer types) that is saved somewhere
else, then this information will not be stored. Please ensure that the power
system types and all other referenced information is exported as well. We
recommended limiting the use of “non-project objects” to one or two
non-project libraries; these should also be exported on a regular basis.

• Exported projects may be imported into a database tree by pressing the

button on the Data Manager’s toolbar. You will be prompted for the
exported filename (*.dz).

• Please make sure that you make backup copies of all the exported data, as
well as of the PowerFactory database on a regular basis.

• However, should you find yourself in the unhappy position of having a

corrupted database and no backup files please contact us for assistance;
all may not be lost!

Handling of Power Factory 1-3

DIgSILENT PowerFactory About DIgSILENT PowerFactory

1.2 Capability for all Users; Beginner to

Advanced

DIgSILENT PowerFactory has originally been designed as a complete package

for the high-end user. Consequently, there are no special ’lightweight’ versions,
no cut-outs of a ’heavy’ version. This does not, however, mean that non high end
users will find themselves at sea when using PowerFactory. The program is
also friendly to the basic user. Users who are learning about power systems are
able to easily and quickly perform load flows and short circuit calculations,
without needing to immediately master the mathematical intricacies of the
calculations. PowerFactory allows the user to learn primarily about power
systems and not PC quirks- all that is required is a reasonable working
knowledge of Windows applications such as Word and Excel.

The program is shipped with all of the engines and algorithms that are required
for high-end use. The functionality that has been bought by a user is configured
in a matrix, where the licensed calculation functions, together with the maximum
number of busses, are listed as coordinates. In addition, there are options
available which will allow the configuration and fine-tuning of the software
according to the user’s needs, for some of the functions.

In this manner the user need only purchase those calculation functions that are
immediately required, thereby reducing costs at the outset. As requirements
dictate further functionality may be purchased. The user thus does not have to
learn a whole new interface for new functions, but merely uses new commands
within the same environment. In addition, the original network data is used and
only extra data, as may be required by the new calculation function, needs to be
added.

1.3 Conventions Used In This Manual

1.3.1 Terms and Abbreviations

Mouse and keyboard handling actions are abbreviated, and a ’shorthand’ is also
used to describe actions that the user should take. To assist the user these
shorthand descriptions are specifically formatted to stand out, as follows:

Key As in “Press the left mouse key”. A key is either one of the mouse keys or a
key on the keyboard. Mouse keys are sometimes called ’buttons’, as in ’the
mouse button.’

Button As in “Press the OK button”. The word “button” is used for screen

Handling of Power Factory 1-4

DIgSILENT PowerFactory About DIgSILENT PowerFactory

areas which perform some action when clicked using the mouse. In other
words, a ’virtual’ button. Buttons are usually described by the popup name
that you read when you hover the cursor over the button. For example,
press to open the user settings dialogue.

Buttons are also shown as seen on screen, as in the to open the user
settings dialogue.
Right/Left clicking As in “Right click the browser”. Means pointing the cursor at
the object described (the browser) and pressing the right/left mouse key.
Double Clicking As in “Double click the button”. Means pointing the cursor at
the object described and pressing the left mouse key twice within about
half a second (the time interval is as set in the Windows operating system).
Ctrl-B (key combination example) means that that the user should press the
combination of keys described. For example, “Press C TRL -B to toggle
between balanced/unbalanced case,” means that the user should press
and hold down the first keyboard key (the Control key on the keyboard in
this example) and then press the second key (B) as well.
Menu sequences When a user needs to select a command through cascaded
menu options the sequence is shown by arrows that indicate what option to
choose next, starting from the original menu button.
For example, setting the drawing format can be done by pressing the
O PTIONS button to access the options menu, then by choosing ”Graphic”
from the list offered, and finally ”Drawing Format ...” from the last list;
this series of actions is all simply described by Options →Graphic
→Drawing Format ...
” ” and ’ ’ ”These” quotes are used to indicate that the description is one that
can be found within the program- one that is not user definable, for
example, the balloon help description ”Calculate Load Flow” that you see
when you hover your cursor over the Load Flow button.

’These’ are used to indicate data that a user has entered or should enter.
’These’ quotes are also used to indicate a process or series of objects that
have no discernible name, but which need to be described. For example,
the ’drawing tools panel,’ which is found on the right hand side of the
drawing canvas.
and [1] [2] [3], etc These show a sequence of events that should be
performed. Where they are numbered they will be associated with a
graphic in which the numbers appear.
left-clicking, right-clicking, clicking, double-clicking, etc Wherever the
instruction clicking or double-clicking appears it should be taken to mean
clicking and double-clicking using the left mouse button. When the right
mouse button is to be used it will be explicitly stated.

Handling of Power Factory 1-5

DIgSILENT PowerFactory Program Overview

Chapter 2

Program Overview

DIgSILENT PowerFactory is a single-program package. This means that all

functionality that is used to

• enter new (parts of) a power system design, either in a text-based or in a

graphical way,

• us and print single-line graphics

• edit the power system components

• manage the database

• select design options

• perform calculations

• report and print the results

or any other function related to these tasks, is available directly in the main
program window.

The significance of this is that the users need only familiarize themselves with
one user interface as all activities are controlled and accessed via the main
program window.
More importantly, all data is kept in a central place, and the user need not
transfer, or copy, paste and modify the data from one part of the program to
another in order to perform a new type of calculation. The PowerFactory user
interface is fully compatible with Windows operating systems. For those users
who are not experienced in using these operating systems, some simple
instructions have been added to the tutorial. These are recognized by being
prefaced by a different icon.
For example, to practice a Windows feature:

Do this

Then do that

Users familiar to the Windows operating systems may want to skip these parts of
the tutorial.

Handling of Power Factory 2-6

DIgSILENT PowerFactory Program Overview

2.1 Philosophy of Use

In order to better understand how to use a program it is useful to first get an idea
of what the designers had in mind when they designed the user interface. In the
next few paragraphs we will attempt to explain what this philosophy is.

PowerFactory is intended to be initially used and operated in a graphical

environment. That is, data entry is accomplished by drawing the network under
study and then by editing the objects on the drawing canvas to assign data to
them.

As users progress and become more adept with the program, data will be
manipulated by using a data viewer called the Data Manager.

The following picture shows what PowerFactory looks like when a project is
active.

[1] Main window [3] Graphic window/s

[2] Data Manager window [4] Output window

The two means of accessing the data are thus via the graphics page/s and via
the Data Manager.
The graphics page is simple to understand and data is accessed by
double-clicking on an object in the graphic. An input dialogue pops up and the
user may then edit the data for the object as can be seen in the following picture.

All of the data that is entered for such objects is specifically structured in folders
to allow the user to navigate through it. To view this data a ”Data Manager” is
used. The data manager is similar in appearance and working to a Windows
Explorer.

As mentioned, data pertaining to a study is organized into several folders. Before

examining this structure we should understand the philosophy behind this
arrangement.

2.2 Data Arrangement / Structure

Firstly, it is clear that, for the study of any system, there are two distinct sets of
information that can be defined:

• data that pertains directly to the system under study, that is, electrical data

Handling of Power Factory 2-7

DIgSILENT PowerFactory Program Overview

Figure 2.1: Main PowerFactory windows

• study management data, for example, which graphics should be displayed,

what options have been chosen for a load flow, which ’areas’ of the
network should be considered for calculation, etc.

The electrical data itself can also be further divided into logical sets. When we
construct a power system we make use of standardized materials or
components - a roll of cable for example. In simple terms we can describe the
cable electrically by its impedance per km length whilst it is still on the cable
drum; in other words, generic information about this cable, is called ”Type” data.

When we cut a length of the cable for installation the type data is retained in a
modified way, as follows:

600m of cable that has a Type impedance of ’Y’ Ohms/ km will now have an
impedance of ’0.6*Y’ Ohms.

We can thus see that the length of the cable, o.6 km, can be seen as a separate

Handling of Power Factory 2-8

DIgSILENT PowerFactory Program Overview

Figure 2.2: Editing an Element

set of information. This set of information will contain all of that information
particular to the specific installation or application of the piece of cable we
are considering. Information such as the derating factor of the installed
cable, its local name, the nodes that it is connected to at either end; in other
words, all information that is non-generic, will fall into this information set.

In PowerFactory we call this ”Element Data.”

This means that there are now three distinct sets that we need to arrange the
data into. In ’Explorer’ terms this means three folders, which, in PowerFactory,
we call:

• ”Grid” folder: holds all the element data

• ”Library” folder: holds all the type data

• ”Study Case” folder: holds all the study management data

Of course we should also house these three folders within a higher folder so that
we can arrange our data for different networks that we may be studying; this we
then call the ”Project” folder.

Handling of Power Factory 2-9

DIgSILENT PowerFactory Program Overview

All of this can be visualized in the overview drawing shown in Figure Fig. 2.3,
where:

[1] The graphic depicting the network is shown

[2] If the user edits the data for the element by double clicking on it this element
data is displayed in the element dialogue

[3] If the Type is edited the type dialogue is displayed. In this case you can see
that two different lines (’Cable A’ and ’Cable B’) have their own element
data but both refer to the same type data.

[4] The graphical object data is kept in the ’Grid’ folder- although the user
should refrain from editing this as these are automatically created and
require some experience to manipulate.

[5] Similarly, the element data objects are also kept in the ’Grid’ folder and may
be viewed by using the data manager, as well as by double clicking them
from the graphic.

[6] The type data objects are kept in the ’Library’ folder.

[7] All of these folders are kept inside a project folder, here called ’Simple Power
System.’

[8] Finally, all projects and other folders are housed in the user account folder,
here called ’Raj1.’ This folder is a system folder (the ’user account’) that is
created when the user starts PowerFactory.

The ’Study Case’ folder that can be seen in the data tree is the folder that
contains the study management data- the ’tools’ and ’tool settings’ that are used
to perform the calculations and the visualization of the results. This will be dealt
with in more detail at a later stage. Initially the user does not need to concern
himselve over the study case as it is created and assigned automatically.

Handling of Power Factory 2-10

DIgSILENT PowerFactory Program Overview

Figure 2.3: Overview

Handling of Power Factory 2-11

DIgSILENT PowerFactory Program Overview

2.3 DIgSILENT PowerFactory Windows

The so-called ’windows’ are the users interface to the program and the means to
enter or manipulate data/ graphics. DIgSILENT PowerFactory uses several
kinds of windows some of which have been shown previously. These will now be
described and explained.

Figure 2.4: PowerFactory initial appearance

Consider Fig. 2.4:

[1] The main PowerFactory window is described in the title bar- ”DIgSILENT
PowerFactory 13.1”

[2] Drop down menu selections are available.

[3] A tool bar is associated to the the main window (presently this is mostly
de-activated as there is no active project).

[4] Balloon help appears for buttons when the cursor is ’hovered’ over a button
for half a second or more.

Handling of Power Factory 2-12

DIgSILENT PowerFactory Program Overview

[5] The title bar of this sub-window describes it as a ”Data Manager” and lists
the path of the object that has been selected in the data manager; here the
project entitled ’Simple Power System,’ which is located in the (user) folder
’Raj1’, has been selected.

[6] When an object is right clicked a menu appears.

[7] This is the output window, which has its...

[8] ...own tool bar.

The data manager sub-window (this window is created by pressing the

button, which is the first button on the left of the main toolbar) is always floating
and more than one can be active at the same time. The database manager itself
has several appearances: it may only show the database tree for selecting a
database folder, or it may be the full version with the database tree, the data
browser, and all editing capabilities.

One of the major tasks for the data manager is to provide access to the power
system components. The power system components shown in the data
manager can be ’gang-edited’ (or ’group-edited’) within the data manager itself,
where the data is presented in a tabular format, for all the selected objects.
Alternatively each object may also be individually edited by double clicking on an
object (or right click →”Edit”).

The output window, at the bottom of the screen, is always there; it cannot be
closed although it can be minimized.

The output window can be “docked”, that is: fixed to a location on the bottom of
the main window. The docked state is the default, as shown in Fig. 2.4.
When clicking the right mouse button, when the cursor is in the output window
area, the context sensitive menu of the output window appears. The output
window can then be undocked by deselecting the ”Docking View” (by clicking the
mouse onto ”Docking View” to ’untick’ it. The undocked output window is still
confined to the main window, but now as a free floating window. This sometimes
occurs ’accidentally’ when the user left clicks the tool bar for the output window
and drags the mouse (keeping the mouse button down) to somewhere outside of
the output window boundaries. To rectify this simply left click in the title bar of the
undocked window and drag it down to the bottom of the screen where it will dock
once more (if you have right clicked ’unticked’ ”Docking View” to right click and
select ”Docking View” once more.

The undocked state is not a normal situation for the output window. Because the
output messages that appear in this window are important at any stage while
using the program, the docked state is the best place because it will be visible
then and easy to locate.

Handling of Power Factory 2-13

DIgSILENT PowerFactory Program Overview

The edge of the output window shows a splitter bar [a] which is used to change
the size of the output window. The ‘drag’ cursor, as shown at [a], appears
automatically when the cursor is placed on the splitter bar. The left mouse button
can be pressed when the ‘drag’ cursor is visible. This will turn the splitter bar to
grey and the output window can now be resized by holding down the mouse
button and moving the mouse up or down.

The button “Maximize Output Window” ( ) on the main toolbar will enlarge the
output window to almost full-screen. Left click the button again to switch back to
the small output window.

2.3.1 Sizing Widows and Sub-Windows

On the right of the titlebar of any window or sub-window there are 3 buttons that
are used to ”Minimize”, ”Maximize”/”Restore Down” or ”Close” the window.

the button minimizes the window to a small object, somewhere on the

screen (usually in the lower left corner- this is the default position) in the
case of a sub-window, or to the task bar for your computer- at the bottom of
the screen.

the button ’opens’ the minimized window to full screen size.

the button reduces the window to a smaller size on the screen; initially
there is a default size for this window but the user may re-size it as desired.

the button will close the sub-window or end the program if this button
is clicked on the main window.

Sub-windows can be re-sized as follows. Place the cursor over the lower right
corner of the window and left click and hold the button down- now drag the
window to the size you require. You will find that each corner can be sized like
this, as well as each edge.

2.3.2 Menu Bar

The menu bar contains the main PowerFactory menus. Each menu entry has a
drop down list of menu options and each menu option performs a specific action.
To open a drop down list, either click on the menu entry with the left mouse
button, or press the A LT key together with the underlined letter in the menu. For
instance, to open the Help menu, press the A LT and the H key together. Menu
options that occur in grey are not available -these become available as the user
activates projects or calculation modes, as required.

press A LT-H to open the help menu. Use your keyboard to select the
Getting Started Tutorial. Press RETURN to open the Tutorial. The on-line
Getting Started Tutorial is exactly the same as the printed version.

Handling of Power Factory 2-14

DIgSILENT PowerFactory Program Overview

Figure 2.5: Re-sizing sub-windows

Figure 2.6: The Help Menu on the Menubar

close the Getting Started Tutorial help (Use the on the main bar). You
will return to the main PowerFactory program window.

left click the Help menu. Left click the option Users Manual. This opens the
on-line User’s Manual.

Handling of Power Factory 2-15

DIgSILENT PowerFactory Program Overview

2.3.3 Toolbar
The toolbar shows the main PowerFactory command buttons. Buttons that
appear in grey only become active when appropriate.

Figure 2.7: The main toolbar

All command buttons are equipped with balloon help text which pop up when the
cursor is held still at the button for a moment, and no key is pressed.
find the button for User Settings by using the balloon help. Don’t use the
mouse keys: just point at the buttons, hold still, and a balloon text will pop
up. Scan all buttons until you find the right one.
Using a command button couldn’t be easier: just click on it with the left mouse
button. Those buttons that perform a task will automatically jump back when that
task is finished. Some command buttons however will switch between two
modes, for instance the one which will reserve more place for the output window
on the workspace ( ). This button will stay down to show the activated mode.
Click the command button again to switch back to the normal view.

When PowerFactory has just been started, the toolbar shows only the general
command buttons. The ’toolbar select’ button ( ) can be clicked to select
additional command buttons.

2.4 Getting Help

The PowerFactory software comes with a number of help facilities:

1. The commercial version comes with a hard copy of the Users Manual and
the Getting Started Tutorial.
2. All versions have on-line versions of the Users Manual and the Getting
Started Tutorial, which can be opened from the Help option on the main
menu.
3. All versions have a context sensitive help which will directly jump to the
right page of the on-line Users Manual when the F1 key is pressed. An
example for the two winding transformer is shown in Fig. 2.8.
4. All versions have balloon help installed which will give the names of
command buttons, or input parameters, if the cursor is positioned over
these items and held still for about half a second. Fig. 2.9 shows three help
balloons in the browser part of the data manager.

Handling of Power Factory 2-16

DIgSILENT PowerFactory Program Overview

1. For help on buttons (available for all command buttons).

2. For help on class-icons.
3. For help on parameter fields (available for all parameters fields).

Figure 2.8: The Two-winding Transformer and its Context sensitive Help

Figure 2.9: Balloon Help in the Data Manager

The Users Manual and Getting Started Tutorial are exactly the same in print and
in the on-line version. Command buttons are sometimes referenced by their
name, instead of by their image. For large buttons, this is normally the case. The

Handling of Power Factory 2-17

DIgSILENT PowerFactory Program Overview

name of a button is either the name on the button itself ( OK , C ANCEL ), or

the name that appears in the balloon help ( = U SER S ETTINGS ).

2.5 Toolbar Definitions

The main PowerFactory toolbar provides the user with quick access to the main
commands available in the program. This section provides a brief explanation of
the purpose of the buttons found on this toolbar. More detailed explanations for
each of the functions that the buttons command are provided in the next sections
of the manual. The main toolbar is depicted in two parts in Fig. 2.10 and Fig.
2.11.

Figure 2.10: Main Toolbar, left part

Figure 2.11: Main Toolbar, right part

New Database Manager Opens a new database manager. When the

option ”Use Multiple Data Manager” (see the User Settings→General) is
enabled in the user settings menu the user will be able to open as many
data manager windows as required. If ”Use Multiple Data Manager” is
disabled in the user settings menu, the user will be able to open only one
data manager window. For more information please refer to chapter 5,
page 5-43.

Edit Relevant Objects for Calculation Provides a list of elements

(coloured in green) or types (coloured in red) that are considered for
calculation: e.g. transformer types, line elements, composite models, etc.
The study case determines which objects are considered for calculation
(for more on study cases see 5.17.7). These objects are grouped by
’Class’ (see the Glossary for an explanation of ’Class’ in the PowerFactory
context. (’Cosmopolitan’ may perhaps be consulted for a general
explanation of ’class’)) If, for instance, no relay objects are used, then the
relay-button will not be shown. All objects from the selected class(es) will
be shown in a browser. For more information please refer to chapter 9.1,
page 9-187.

Handling of Power Factory 2-18

DIgSILENT PowerFactory Program Overview

Date/Time of Calculation Case Displays the date and time for the
calculation case. This option is useful when parameter characteristics of
specific elements (e.g. active and reactive power of loads) are set to
change according to a certain time scale. Modifying the date/time in this
dialogue adjusts those Parameters that have time based triggers/scales
accordantly.

Edit Trigger Displays a list of all triggers that are in current use by the
active study case. These triggers can be edited in order to change the
values for which one or more characteristics are defined. These values will
be modified with reference to the new trigger value. All triggers for all
relevant characteristics are automatically listed. If required, new triggers
will be created in the study case. For more information, see chapter 8.4,
page 8-165.

Calculate Load-Flow Activates the load flow command dialogue. For more
information about the specific settings, please refer to chapter 10, page
10-192.

Calculate Optimal Power Flow Activates the optimal power flow

command dialogue.

Calculate Short Circuit Activates the short circuit calculation command

dialogue. For more information, please refer to chapter 11, page 11-201.

Edit Short Circuits Edits Short Circuit events. Events are used when a
calculation requires more than one action or considers more than one
object for the calculation. Multiple fault analysis is an example of this. If, for
instance, the user multi selects two busbars (using the cursor) and then
clicks the right mouse button Calculate →Multiple Faults a Short circuit
event list will be created with these two busbars in it.

Execute DPL Scripts Displays a list of DPL scripts that are available. For
more information about DPL scripts, please refer to chapter 26, page
26-521.

Output Calculation Analysis Presents calculation results in various

formats. The output is printed to the output window and can be then used
in external reports, or may be of assistance to interpret calculation results.
Several different reports, depending on the actual calculation, can be
created. For more information about the output of results please refer to
section 25.6, page 25-517.

Documentation of Device Data Presents a listing of device data (a device

is the model of any physical object that has been entered into the project
for study). This output may be used in reports, or may be of use in checking
data that has been entered. Depending on the element chosen for report,
the user has two possibilities: to generate a short listing, or a detailed
report. For more information please refer to section 25.5, page 25-516.

Handling of Power Factory 2-19

DIgSILENT PowerFactory Program Overview

Comparing of Results On/Off Compares the differences between two or

more calculation results, for example, where certain settings or designs
options of a power system have been changed from one calculation to the
next. For more information please refer to chapter 9.3, page 9-188.

Edit Comparing of Results Enables the user to select the cases/

calculation results that are to be compared to one another, or to set the
coloring mode for the difference reporting. For more information please
refer to chapter 9.3, page 9-188.

Update database Utilizes the current calculations results (i.e. the

calculation ’output’ data) to change input parameters (i.e. that data that the
user has entered). An example is the transformer tap positions, where
these have been calculated by the load-flow command option ”Automatic
Tap Adjust of Tap Changers.” For more information please refer to chapter
9.3.1, page 9-189

Break Stops a transient simulation or DPL script that is running.

Reset Calculation Resets any calculation performed previously. This

button is only enabled after a calculation has been carried out.

User Settings User options for many global features of PowerFactory

may be set from the dialogue accessed by this button. For more
information please refer chapter 4, page 4-37.

Maximize Graphic Window Maximizes the graphic window. Pressing this

button again will return the graphic window to its original state.

Maximize Output Window Maximizes the output window. Pressing this

button again will return the output window to its original state.

Current Study Case This drop down window displays the name of the
study case that is currently activate. The user may also ’toggle’ between
study cases in the project by selecting them from this drop down list.

Select ToolBar Drops down when pressed to present sets of buttons (to
the right of it) for various calculation commands: e.g. Stability, Reliability,
Harmonics, Optimal Capacitor Placement and Data Acquisition.

Zoom In Changes the mouse mode to zoom; draw a zoom area by holding
the left mouse button down and dragging a zoom area on the graphic.
Everything in this area will be enlarged, with limits as defined by the zoom
area.

Zoom Back Steps the enlargement setting backwards to the last zoom
setting. The zoom can also be activated by holding the ALT key down
and pressing + or - to zoom in or out, respectively.

Handling of Power Factory 2-20

DIgSILENT PowerFactory Program Overview

N OTE :
The user may pan in the graphic, when it is zoomed. To activate the
pan mode place the cursor in a clear space in the graphic (i.e. where
there are no objects), right click →”Change Viewpoint.” Now hold the
left mouse button down and drag the cursor to an edge of the graphic
- the graphic will pan in that direction. To exit the pan mode right click
the mouse (this is a valid escape command for most mouse modes in
PowerFactory)

Zoom All Displays the graphic as a virtual full page (zoom=100%).

Zoom-level Displays the current zoom setting. The desired zoom setting
may be typed in directly if required; type the desired zoom level, e.g. 175%
as ’175’ and press ENTER
Print Prints the currently active graphics window.
N OTE :
If the the graphic is zoomed less than 200% it will be printed full size,
as determined by the drawing format

Set Drawing Format Defines the drawing area. This ’virtual’ drawing size
is independent of the physical paper size selected.
Rebuild Under some circumstances the drawing may not be updated
correctly. Press the rebuild button to update the currently page from the
database.
Insert New Graphic Creates a new graphic and displays it in the active
graphic board (the graphic board folder is held in the study case folder and
’remembers’ which graphics have been activated for display by the user).
For more information, please Refer to section 7.3.3, page 7-115.
Insert Existing Graphic Inserts an existing graphic page (e.g. from
another project) to the current graphics board.
Freeze Mode Freezes the single line diagram or the block diagram. In the
freeze mode the diagrams cannot be graphically altered. The underlying
data objects may however still be edited. The freeze mode may be
selected when the single line or block diagram has been completed,
thereby preventing accidental changes.
Graphic Options Activates the graphic options dialogue (includes options
such as ”Snap to Grid” or the cubicle representation). Each graphic
window has its own settings which can be changed using this button. For
more information, please Refer to chapter 7.7.1, page 7-129
Show layer... Activates the layers dialogue. The single line graphic and the
Block diagram graphic windows use transparent layers of drawing sheets

Handling of Power Factory 2-21

DIgSILENT PowerFactory Program Overview

to show the graphical symbols. Each of these layers may be set to be

visible or not. The names of devices, for example, are on a layer for called
”Object Names” and may be hidden by setting the layer to ’invisible’. For
more information, please refer to chapter 7.6, page 7-123.

Undo Undoes graphical changes and some data changes. Note that this
command is not a ’universal’ undo and that deleted elements are sent to
the ”Recycle Bin,” from where they may be restored. Parameters that have
been changed are not ’undone.’

Mark All Elements Marks (select) all objects in the drawing. This is helpful
for moving the whole drawing to another place or copying the whole
drawing into the clipboard. In block diagrams the surrounding block will not
be marked. CTRL + A will perform the same action.

Edit and Browse Data Edits the device data of all selected objects in the
drawing. If only one object is marked then the object edit dialogue will pop
up directly. When more than one object is marked, a Data Manager
window will show the list of marked objects. As with a normal Data
Manager, these objects can be double-clicked to open their edit dialogues.

Delete Element This button deletes all selected objects in the drawing.
The objects in the database which correspond with the graphical objects
will also be deleted, unless the elements are represented in more than one
graphic. In this case the use will be asked whether the data elements and/
or other graphics should also be deleted.

Cut Cuts all selected objects from the current graphic and places them into
the clipboard.

Copy Copies all marked objects from the current graphic and places them
into the clipboard.

Paste Pastes objects from the clipboard to the current/ active graphic.
Objects are inserted to the graphic at the cursor position.

Reconnect Element Pressing this button disconnects the selected

elements, and presents them for reconnection, one by one. The element is
entirely disconnected and may be connected elsewhere. Once the element
has been disconnected the cursor is seen to be connected to the element
via a ’rubber band.’ This action should not be confused with the
”Reconnect Graphically” command, which retains the connections but
allows the user to re-draw the element in a more convenient manner.

Select Graphic Attributes Sets the current line style, line width, brush
style, color and font. Note that in this instance ’line’ refers to annotation
lines and not to electrical lines. The brush style is used to fill solid symbols
like squares and circles.

Handling of Power Factory 2-22

DIgSILENT PowerFactory Program Overview

Color Representation Opens the colour representation dialogue. This

dialogue is used to select colouring modes which assist in assessing
results, for example, colouring by over or undervoltage and branch loading.
For more information,please refer to chapter 7.8.1, page 7-143.

Titel Block On/Off Shows or hides the title block for the graphic.

Legend Block On/Off Shows or hides the legend block for the graphic (the
legend block is the key to the results box configuration).

Draw existing Net Elements Opens a database browser listing all

elements considered for study (i.e. as determined by the active study case)
that are not shown on the current graphic. ”Draw Existing Net Elements” is
normally used to build single line graphics from imported data. For more
information, refer to chapter 7.4.1, page 7-117.

Station Feeder Options Displays the “Cubicle Parameter Settings”

dialogue. The settings in this dialogue determine the type of cubicle that
will be created automatically when a branch element is connected to a
busbar system, where no free cubicle is available, and when a completely
new station has been inserted.
See Selecting Cubicles , for more information about the creation of busbar
systems and cubicles.

Default voltage levels for Terminals and Busbars All nominal voltages
used in the current network are listed in this drop-down box (new voltages
are specified by placing a node and editing its dialogue; as soon as a new
voltage is entered it is added to the drop down list). It can be used to select
the nominal voltage for the next terminal or busbar that is created. This can
be used in combination with a coloring mode according to voltage levels, in
which case the creation of a new network is speeded up and the risk of
using incorrect nominal voltages is reduced at the same time.

Default Phase Technologies for Terminals Specifies the default phase

technology that will be used for the next terminal to be created.

Handling of Power Factory 2-23

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

Chapter 3

Logon, User Accounts and

Program Settings

PowerFactory is supplied with a user account managing system, which

provides the user with the possibility to create and maintain a secure folder in
which only he/ she may work. In the case of only a single user in a stand alone
application this security is of course provided by the PC log-on security.

However, in a multi-user environment, where users are accessing a central

database, separate accounts for all users may be created. Sophisticated user
account and project management tools allow the sharing of data whilst retaining
data integrity of the original project file.

N OTE : You will find a detailed description of the PowerFactory installation,

license configuration and the creation/administration of the multiple-
user environment in the Installation Manual.

3.1 Program Configurations and Settings

In general there are 3 different main questions to be answered before installing

the software. The answers to these will determine how the software is to be
installed:

• License: Where should the license key(s) reside?

• Installation: Where should PowerFactory be installed?

• Database: Where should the database reside?

3.2 License Key(s)

3.2.1 License Key Installations

Handling of Power Factory 3-24

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

PowerFactory may be run in a demonstration mode as a ”Demo” user, where

certain restrictions apply; in this case a ’soft’ licence key is required and will be
emailed to the user on request.

To install this menuDemo version of PowerFactory, go through the following

steps:

Place the installation CD into your CD-ROM-drive

The setup will start automatically. If this does not occur then the setup may
be manually started using S ETUP. EXE, located in the CD-ROM main
directory.

During the installation procedure select Demo-Version.

The ’full’ version requires a licence key and this may either be an individual,
discrete key (or several individual keys, or a special network key that administers
a number of licences from a central location. This network key will be placed on
a networked machine that runs continuously.

A detailed description of the types of possible installations of PowerFactory on

single PCs and in network environments can be found in the Installation
Manual on the PowerFactory-CD.

3.2.2 License Settings

After completion of the installation start the program. A IntLogon dialog will
appear. The License page of this dialog should read as shown in Fig. 3.1:
The Log on page of this dialog is used to log on as a specific user.

N OTE : To run the prepared examples please log on as Demo user. This user
requires no password to use and you have the possibility the demo
projects with the full functionality of PowerFactory.

Three types of license settings are possible:

• ”not available (Demo)”: no license at all; for the ”Demo” account

• ”on local port”, which means that a valid PowerFactory license key
(’hardlock’) must be connected to the USB or parallel port

• ”in network (file based communucation)”, which means that a connection to

a network computer, which has the PowerFactory network license service
running must be available.

• ”in network (protocol based communucation)”, which means that a

connection to a network computer, which has the PowerFactory network
license service running must be available.

Handling of Power Factory 3-25

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

Figure 3.1: License settings for demo user

Please find a detailed description of the different installation methods in the

Installation Manual on the PowerFactory-CD.

3.3 The Log On Page

3.3.1 Log on
A special account for administration of the user accounts is provided, as is a
special account for demonstration purposes; these accounts are named
”Administrator” and ”Demo”.

Since there is a user accounting system one needs to log on when starting
PowerFactory. The log-on dialogue presents various options that may be
configured for your particular system and installation.

To log on you will require a user name and password. If you are starting
PowerFactory for the first time you can create a user account by typing in your
name and a password of your own choice (this only holds true for a stand alone
installation; a multi user installation will have accounts that have been defined by
the user who has access to the Administrator account). When you see the ”Do
you really want to create a new user account” message press ”OK” to create
your own account (should you forget your password you can log on as the
Administrator user - the default password is ’Administrator’; and change the

Handling of Power Factory 3-26

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

password using a data manager).

3.3.2 Advanced Settings

The advanced program settings should only be changed under the guidance of
the DIgSILENT PowerFactory support at [email protected].

3.3.3 Appearance Settings

The appearance settings influence the way in which the toolbar buttons are
displayed and the way in which dialogues will open, close or move scroll bars
and other objects.

These settings may be changed to suit the users personal taste.

3.4 The User Account Management System

The user account philosophy of PowerFactory basically works in the same way
as is usual for larger computer systems. The first objectives of the user account
managing system are

• to protect the ’system’ parts of the database from changes by normal users

• to protect the part of the databases which belongs to user ’A’ from being
changed by user ’B’

• to allow users to share data

The effect of the user account managing system is to provide each user with the
their own ’private’ database, which is separate from other users. The user is
nevertheless able to use shared data, either from the common system database
or from other users, and may enable other users to share ’private’ data.
The user account managing system manages this whilst using only one single
database in the background, which allows for simple backup and management
of the overall database.

The basic PowerFactory database structure, as depicted in Fig. 3.2 consists of

the following folders:

The main Library folder contains all standard PowerFactory types and
models. The main library folder is read only for normal users.

Handling of Power Factory 3-27

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

The System folder contains all objects that are used by internally
PowerFactory. The system folder is read only for all normal users.
Changes are only permitted when logged on as the Administrator, and
should be conducted under the guidance of DIgSILENT customer support.
The Administrator folder contains all objects needed for creating and
managing user groups and user accounts and for changing global settings.
The Demo folder contains all demo projects that can be executed by the
demo-user. The demo projects are shared projects and can thus be read
and used by normal users.
User account folders contain the project folders and all other folders in which
the normal user defines his power systems and all accompanying objects
and settings.

Figure 3.2: Basic database structure

3.4.1 The Demo Account

The demo account is for demonstration or testing purposes only. The demo
account folder is filled with numerous demonstration projects. These projects are
accompanied by demonstration command scripts which can automatically
activate a demo project and perform commands such as load-flow, short-circuit
or transient analysis. Execution of these command scripts is started by selecting
a demonstration from the main menu option File →Examples. This menu option
has several sub-menus from which a demonstration may be selected. Selecting
a demonstration will start the appropriate command script.

Note that this menu option File →Examples is only available when one is logged
onto the ”Demo” account.

Handling of Power Factory 3-28

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

These projects may also be activated and observed in the manner normally
employed by PowerFactory. To learn how this is achieved it is best to work
through the on-line tutorial that is provided. See under Help →Getting Started.

The demo user has read and write permissions for all demonstration
projects. However, calculations will only be permitted for the
demonstration networks as long as they have not been changed in a
topological sense. This means that adding or deleting lines, transformers,
loads, machines, etc., will lead to error messages like
DIgSI err - demo version: only examples and tutorial available
DIgSI err - maximum number of busbars exceeded
Licensed users may log in as the Demo user, change the demonstration projects
in any way, and still be able to start a calculation (as long as their hardlock is
available to PowerFactory). Note that any changes that are made to the
demonstration projects will be kept (that is, the projects are not ’reset’ on logout
from the Demo account). This may result in errors when the Demo account is
used without a hardlock. Licensed users may simply copy and paste projects
that they are interested in, into their own account for modification.

As long as a user does not make any topological changes, these demonstration
projects may be used to experiment with PowerFactory. Such experimentation
may include:
• Changing and executing commands such as load-flow, short circuit or
transient analysis.
• Changing power system elements such as selecting other line types,
changing generator settings, etc.
• Creating new calculation cases
• Changing the appearance of the single line graphics except for adding or
deleting power system elements.
• Creating or changing virtual instruments panels such as defining graphs or
changing bar diagrams.

3.4.2 The Administrator Account

The administrator has full read and write permissions for all folders in the
database. This includes the system folders, the demo folder, and all user
account folders.

The main objectives for the administrator are

• Creating and managing user accounts.
• System database maintenance under the guidance of the DIgSILENT
customer support.

Handling of Power Factory 3-29

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

Creating and Managing User Accounts

In the case of an installation with a local database, the simplest way to create a
new user account is to enter an unknown account name in the log on dialogue.
The creation of the new account must be confirmed. The program will then
create and activate the new account. In this case no administrator intervention is
required for such local database installations.

For multi-user database installations, the administrator creates new user

accounts with the ”User Manager” object (IntUserman), found in the
Administrator account folder (use a Data Manager to see this). To add a new
user:

• Right click the ”User Manager” and select ”Edit”

• Press A DD U SER ...

The User edit dialogue will pop up:

• Enter the user account name, password and other details

• You may also make the new user part of any groups that you have created.
This allows selective sharing of projects amongst users.

• If a licensed version with a restricted number of functions is used (i.e. you

may have 4 licences with basic functionality, but only 2 stability licences),
the ”License” tab may be used to define the functionality that a user can
enjoy. Remember that the ”Multi User Database” option should be checked
for all users that will access the multi user database.
The administrator is the only one who may delete a user account. Although
users can delete all projects in their account folder, they cannot delete the
account folder itself or the standard folders that belong to it (i.e. the ”Recycle
Bin” or the ”Settings” folder).

3.4.3 Creating User Groups

Any user created project or folder in a user account may be shared for use by
others. This may be done selectively by sharing only with certain groups, or by
sharing for all.

The administrator can create new user groups with the ”User Manager” object
(IntUserman):

• Right click the ”User Manager” and select ”Edit”

• Press A DD G ROUP... . The identification number is automatically

assigned and does normally need to be changed.

• Enter the name of the group and, optionally, a description.

Handling of Power Factory 3-30

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

This will create a new group object (IntGroup) in the administrator account
folder. A group is deleted by deleting this group object.

How to use user accounts and user groups is described in the next section.

3.5 Users and User Groups

The user account folder is the basic environment for all users of PowerFactory.
Each user has full read and write permission in his own account folder.

A new user must first create a project in order to be able to define power system
designs and to perform calculations. A user account folder allows for an
unlimited amount of projects, each of which may contain several grid definitions
and calculation cases. Projects may also be grouped under folders created by
the user.

Please refer to “Project Management”, 6, page 6-93 for more information on

projects, grids and calculation cases.

3.5.1 Using Shared Data

In order to share projects (only projects may be shared and not individual grids
in a project) users must have access to a central database, and must also have
the multi user software installed.

It is of course possible to ’share’ projects by creating dz files of the project and

passing these to others users, however, sharing, in the sense described here,
means to share the data so that several users may make use of one original set
of data, contained in a project. This allows all users to begin their own projects
using the same ’base’ data.

In this manner, should the original project be modified or updated all users who
are utilising the shared data will have the updates reflected to their own project,
thus ensuring that their base data is always correct and up to date.

All of this is achieved by using what are known as ’remote system stages’ which
are essentially variants of the original project.

To understand remote system stages or variants, it is important to understand

normal system stages first. Please refer to ”Projects and System Stages”, 6.1.1,
page 6-102 for a description of project and system stage management.

For this introduction into remote variants, it is sufficient to know that a variant is
basically a temporarily image of the original grid (as the user will have seen, by

Handling of Power Factory 3-31

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

reading the section 2.2, data regarding the network is contained in the grid
folders, thus these are the folders that variants are created from). This image
exists as long as the remote variant is active. During this time, the remote variant
keeps track of all changes made to the original grid. The original grid itself is not
changed in any way. At deactivation, the remote variant destroys the image of
the original grid and keeps only the changes that have been made. At the next
activation of the remote variant, a new image of the original grid is made and all
saved changes are executed once more. This returns the remote variant back to
the state that it was in prior to de-activation. The advantage is that any changes
that have made to the original grid will now be carried over to the remote variant,
so keeping it up to date. Should the user who has made the variant have made
changes to an element that has also been changed in the original grid the
variant ’locks’ this element and will not allow changes from the original.

The process of sharing data is twofold:

• the user with the original or base project must set the sharing rules

• users wishing to use this base project data add the required grids to their
own projects inside their user accounts as remote system stages

Sharing the Original or Base Project Data

Any project may be shared but note that only ’top level’ folders may be shared.
Subfolders cannot be shared (top level folders are those that are the first level of
folders that are encountered below the user folder- for a project created in the
standard manner the project folder itself is the top level folder). If a user has
created a top-level folder in there are three projects, A,B and C, then only the
whole folder may be shared. The individual projects, A, B and C cannot be
separately shared as they are no longer the top level folder.

Sharing a project/ folder is achieved by right clicking it and selecting ”Sharing...”.

The dialogue that pops up shows the current settings.

Changing the share settings (the sharing rules - that is, which groups are
allowed to have access to the folder) is a matter of double clicking the user group
names to move them from the left to the right pane, or back again, in order to
change the user groups that have access to the project.

Sharing the project with all other user groups is possible by enabling the option
Share for Everyone.

Other users may now define remote variants for the shared projects once a
project has been shared. Once such remote variants have been defined, it
becomes potentially hazardous to remove or change the share settings. This is
because the projects of the other users using the shared (base) project for

Handling of Power Factory 3-32

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

remote variants will lose vital data when the shared data is suddenly no longer
available. However, if the shared data is not used, there is no danger in changing
the share settings. To check whether a grid has remote system stages right click
the grid when it is shown on the right hand side of a data manager →Output...
→Reference List. This will provide you with a list of all objects that are
referenced to the grid, including remote system stages.

How to use shared data is best explained by example. In Fig. 3.3, an example is
shown of a database as seen by an administrator. Three user accounts are
visible, for “User 1”, “User 2” and “User 3”. User 1 and 2 have both defined a
project.

Figure 3.3: Administrator view with three users

The administrator has created three user groups:

• “Group 12” has User 1 and 2 as members
• “Group 13” has User 1 and 3 as members
• “Group 23” has User 2 and 3 as members

Both user 1 and user 2 have shared their projects with a group:
• User 1 has shared its “Project A” with “Group 12”
• User 2 has shared its “Project B” with “Group 13”
User 2 thus has shared his project with a group of which he himself is not a
member. This is allowed.

The result of this sharing is depicted in Fig. 3.4:

Handling of Power Factory 3-33

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

• The left pane shows the database as it appears to User 2. He sees his own
projects, and Project A because he is a member of Group 12.

• The middle pane shows the view for User 3. He cannot see Project A,
because he is not a member of Group 12, but he can see the shared
project B.

• The right pane shows the view for User 1. He also can see the shared
project B.

Figure 3.4: User views with shared projects

Creating the Remote System Stages

Any ’base’ project that can be seen by a user (in other words, a project that
resides in another users folder that has been shared) may be used to create
remote system stages from.

Creation of the remote system stage will be shown by example. In Fig. 3.5 the
original project ’owner’ is a user called ’Raj1.’ He has shared the ’Simple Power
System’ project.

The second user, ’Raj2’, wishes to use the data from the ’Simple Power System’
project as created by Raj1. In this case we can consider the Simple Power
System in the Raj1 folder as the ’base’ project. In order to study any data Raj2
must have an active project and study case. As can be seen in the figure such a
project, entitled ’Simple Grid Raj2 Variant’ has been created. There is an active
study case and no grid folder (the grid folder that was created when the new
project command was executed may simply be removed from the study case and
deleted- alternatively, no grid folder is created if the user presses the C ANCEL
button when PowerFactory asks for a name for the grid).
Raj2 now right clicks the grid folder in the Simple Power System project in Raj1’s
account and selects Add to Study Case. The grid is added to Raj2’s project as a
remote system stage as shown in Fig. 3.6. Raj2 may now work on the base data

Handling of Power Factory 3-34

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

Figure 3.5: Remote system stage step 1

Figure 3.6: Remote system stage step 2

and make additions and changes as required, without affecting the data in the
base project.

Handling of Power Factory 3-35

DIgSILENT PowerFactory Logon, User Accounts and Program Settings

N OTE : Whilst system stages and remote system stages are very powerful
tools that assist the user in the creation of variants they do not ab-
solve the user from the need to think carefully as to how to create and
use the variants. Should topographical changes be made to the same
elements in both the system stage and then the original project Power-
Factory is not able to discern how these should be managed, thus the
use of system stages should be understood and carefully managed.
Please see 6 for more information on managing projects

Handling of Power Factory 3-36

DIgSILENT PowerFactory User Settings

Chapter 4

User Settings

The user settings dialogue offers options for many global features of
PowerFactory. This dialogue may be opened either by clicking the button
U SER S ETTINGS ( ) on the main tool bar, or by selecting the Options →User
Settings... menu item from the main menu.

The dialogue shown in Fig. 4.1 will appear.

Figure 4.1: User Settings Dialogue

Handling of Power Factory 4-37

DIgSILENT PowerFactory User Settings

4.1 General Settings

The general settings include

Confirm Delete Activity. Pops up a confirmation dialogue whenever something

is about to be deleted.

Open Graphics Automatically. Causes the graphics windows to re-appear

automatically when a project is activated. Without this is not checked, the
graphics window must be opened manually.

Beep on user errors. May be de-selected to suppress sounds.

Use Multiple Data Manager. When enabled, more than one data manager
dialogue can be opened at a time. When disabled only one data manager
may be opened at a time and pressing the ”New Data Manager” button will
pop up the minimised data manager.

Use operating system Format for Date and Time the operating system date
and time settings are used when this is checked.

Use Default Graphic Converter

Edit Filter before Execute Presents the filter edit dialogue when a filter is
selected, allowing the user to edit the filter before application. However,
this is sometimes irksome when a user is applying a filter several times.
Thus one may choose to go straight to the list of filtered objects when the
filter is applied by un-checking this option.

Always confirm Deletion of Grid Data When checked a confirmation dialogue

is popped up when the user deletes grid data.

Decimal Symbol Selects the symbol selected to be used for the decimal point.

Use Standard Database Structure In order to simplify the operation of

PowerFactory for users who do not use the program often, or who are just
starting out certain restrictions may be introduced into the database
structure, for example, allowing only ’Type’ data to be placed in Library
folders (when this option is un-checked). However, this may be irksome for
advanced users or those who are used to the standard database working
where a great deal of flexibility is permitted, so as to suit the users needs,
and thus the standard structure may be engaged by checking this option.

System Stage Profile The ability to create system stages may be limited by this
option. Existing system stages will still be visible but the right menu options
that create new revisions or system stages will be removed. This is once
again a tool that may be used to ’simplify’ PowerFactory for users not
familiar with the program by limiting the operations that they may use.

Handling of Power Factory 4-38

DIgSILENT PowerFactory User Settings

4.2 Graphic Windows Settings

The graphic windows has the following settings.

Cursor settings defines the cursor shape:
• ”Arrow”: a normal, arrow shaped cursor
• ”Crosshair”: a large, full screen cross
• ”Tracking cross”: a small cross
General Options are valid for all graphs:
• ”Show Grid only if stepsize will be least”: grid points smaller than the
selected size will not be shown.
• ”Show Text only if height will be least”: text smaller than the selected
size will not be shown.
• ”No. of columns in graphics floater”: specifies the width of the
graphics toolbar when this is a floating window.
• ”No. of columns in graphics docker”: specifies the width of the
graphics toolbar when it is docked on the right side of the drawing
space.
• ”Line factor when printing”: The width of all lines in the graphics will be
multiplied by the specified percentage when printing
Coordinate Output at statusbar in mm specifies that the status bar will
display the cursor position in millimeters.
Update Hidden pages always results in all graphical pages on a graphics
board being updated, even when they are not visible. Note that this can
slow the processing speed considerably. The advantage is that no
updating is required when a different graphics page is selected.
Exclude Feeder Colors may be used to exclude colors, by number code, which
are to be used for feeder definitions. This is used to prevent the use of
colors which are already used for other purposes. Ranges of color
numbers are entered as ’2-9’. Multiple ranges of colors must separated by
commas, as in ’2-9;16-23’.

4.3 Data Manager Settings

The data manager tab specifies which object types will be displayed or hidden in
the tree representation, and whether confirmation prompts will appear when
objects or data is changed in the data manager itself.

Handling of Power Factory 4-39

DIgSILENT PowerFactory User Settings

Show in Treelist. Object classes that are selected will be displayed in the
database tree.

Save data automatically. The data manager will not ask for confirmation every
time a value is changed in the data browser when this option is selected.

Sort Automatically. Specifies that objects are automatically sorted (by name)
in the data browser.

Export/Import Data configures the export and import of PowerFactory

’DZ’-files, as follows:

• ”Include Binary Data” saves binary data, such as results in the result
folders, to the ’DZ’ export files.
• ”Export References to Deleted Objects” will also export references to
objects which reside in the recycle bin. Normally, connections to these
objects are deleted on export.
• ”Enable export of activated projects” will permit the export of an
activated project.

Folders for Global Library. The default global type folder is the
S YSTEM\L IBRARY\T YPES folder. This default folder contains many
predefined object types, but objects within this folder may not be changed
by the user (read-only access). This option allows the user to specify a
different ’Global Type Folder’, possibly a company specific and defined
type library.

4.4 Output Window Settings

The output window settings control the way in which messages selected by the
user, in the output window are to be copied for pasting into other programs.

Whichever options are checked will determine what will be copied. The text in
the output window itself will not be influenced.

Escape sequences are special hidden codes which are used for colouring the
text, or other formatting commands. Some text processing programs are not
capable of using the PowerFactory escape codes. The Text Only option should
be set in such cases. The text in the output window itself will not be influenced
by the options chosen here.

The number of lines displayed in the output window may also be limited.

Handling of Power Factory 4-40

DIgSILENT PowerFactory User Settings

4.5 Functions Settings

The functions settings page provides check boxes for the function modules that
are accessible from the data manager or from the object edit dialogues. The
user may choose to see only ceratin modules in order to ’unclutter’ dialogues.

This may also be used to protect data by allowing only certain calculation
functionality to be seen by certain users. This is particularly useful in a
multi-user environment or in when inexperienced users utilise PowerFactory.

4.6 Directories

Compiled DSL Models. Pre-compiled DSL models may be available for use as
external models. The DSL directory should be directed to the correct
folder/ directory in order for PowerFactory to find these models.
Log On Settings. The log on dialogue may be viewed by pressing this button.
See section 3, page 3-24 for more information.

4.7 Editor

The editor which is used to enter large pieces of text (such as DPL scripts,
objects descriptions, etc.) can be configured on this page.

Enable Virtual Space allows the cursor to move into empty areas.
Enable Auto Indent automatically indents the next line.
Enable Backspace at Start of Line will not stop the backspace at the left-most
position, but will continue at the end of the previous line.
View blanks and tabs shows these spaces.
Show Selection Margin provides a column on the left side where bookmarks
and other markings are shown.
Show line Numbers shows line numbers.
Tab Size defines the width of a single tab.
Tabs toggles between the use of standard tabs, or to insert spaces when the
tab-key is used.

Handling of Power Factory 4-41

DIgSILENT PowerFactory User Settings

Language coloring defines the syntax-highlighting used when the type of text
is not known.

S HORT C UTS opens the short-cut definition dialogue.

Handling of Power Factory 4-42

DIgSILENT PowerFactory The Database and the Data Manager

Chapter 5

The Database and the Data

Manager

As has been explained previously data in PowerFactory is sorted into sets, for
example the Type and Element data set. This makes the management,
searching, sorting, editing, etc. of the data much simpler. Besides the two main
sets, data for each network object is further sorted into sets as required for
calculation functionality, such as Basic Data, Load Flow data, Short Circuit data,
and so forth.

Data that is required by the load flow function, which has already been entered
in the basic data set, is automatically used by the load flow function. Thus the
user only need enter any extra data that may be required by a calculation
function. If the user changes data in the short circuit data set, it is also changed
in the basic data set. This ensures that the user does not have to remember and
update data in various places in the database- only in one place.

The data can thus be described as non-redundant.

To manage/ browse the data a Data Manager is provided. The data manager is
very similar in operation to a Windows explorer. This section will provide
information on how to use the data manager, and will also explain in more detail
how the data is structured. Before reading this the user should ensure that they
are acquainted with the section entitled ”Data Arrangement/ Structure” (see 2.2).

Within the database we make reference to ’Objects.’ Objects are virtual ’things’
in the database ; they may be seen almost as we see an object in real life. For
example, consider a pencil; it is made of painted wood, with a graphite stylus, it
has a length, a diameter, a weight and it may be picked up and moved from one
location to another.

In the database the pencil is an object; its length, diameter, etc., are attributes or
parameters of that object.

These objects are then arranged into sets, of which we have so far seen the
Element and Type sets. Commands are also objects; their parameters are the
options, such as ”Balanced, positive sequence,” or, ”Unbalanced, 3-phase
(ABC).”

In PowerFactory objects are initially placed into ’Class’ sets; for example a line
element belongs to the ElmLne class. Classes are very similar to the file

Handling of Power Factory 5-43

DIgSILENT PowerFactory The Database and the Data Manager

extensions we see in Windows. If you edit a line element you will see the class in
the title bar of the dialogue - a line called ’Cable A’ will have ”Cable A.ElmLne” in
the title bar for example. We will see later that this allows us great flexibility in
sorting, and thus searching for and managing data. We can sort data by class,
or by elements, or by types, and so on.

To further complicate, or simplify (depending on your point of view!), matters

objects are also grouped by folders (a folder is an object in itself). Folders are
used to conveniently group a number of objects from different classes; for
example, the ”Grid” folder groups element class objects (*.ElmLne for lines,
*.ElmLod for loads, *.ElmTr2 for 2 winding transformers). The ”Library” folder is
used to group type class objects. Once again this does in fact make the
management of the data much simpler.

All of this information is somewhat academic to the user at first, as

PowerFactory will assign objects automatically. It is however useful to have a
background to this arrangement before using the Data Manager and its tools.

Later in the manual we will describe advanced data management philosophy

and techniques that allow variants or alternatives to be created, studied and
managed.

The PowerFactory database philosophy can thus be summarized into one

‘golden’ rule:

’Everything is an object and all objects are stored in the database tree’

This consistent, but flexible, structure of the database makes it possible to store
just about everything, without losing control. The big advantage is that dialogue
settings relating to certain projects can be stored together with those projects,
and consequently can be used over and over without having to re-enter the
settings each time.

A good example of project specific dialogue settings are the calculation

dialogues which are used to set, for instance, the short-circuit options. By storing
the dialogue mask inside the current project, the same short-circuit calculations,
using exactly the same settings, can be repeated by just recalling the saved
dialogue. This way of working also enables the user to store more than one copy
of short-circuit settings, for instance, for a certain set of fault-positions, and
running the same set of calculations by recalling the calculation dialogues one
by one. Comparing this way of working to having to enter a dozen fault positions
sequentially, clearly shows the advantages of being able to save and recall
commands or other settings.

This means of arranging the data is called a ’hierarchical, object oriented

database,’ and is created according to the German DVG-database format.

Handling of Power Factory 5-44

DIgSILENT PowerFactory The Database and the Data Manager

5.1 Using the Data Manager

The Data Manager provides the user with all the features required to manage
and maintain all projects and system stage data. It gives both an overview over
the complete data base as well as detailed information about the parameters of
single power system elements or other objects.
New case studies can be defined, new elements can be added, system stages
can be created, activated or deleted, parameters can be changed, copied, etc.
All of these actions can be instituted and controlled from a single data base
window.

The data manager uses a tree representation of the whole database, in

combination with a versatile data browser.

Figure 5.1: The data manager window

The data manager window has the following parts (see Fig. 5.1) :

[1] The title bar, which shows the name and path of the of the folder currently
selected in the database.

[2] The data manager local tool bar.

[3] The database window, which shows a symbolic tree representation of the
complete database

[4] The input line. The input line may be used by more experienced users to
enter commands directly, instead of using the interactive command
buttons/dialogues. By default it is not shown.

Handling of Power Factory 5-45

DIgSILENT PowerFactory The Database and the Data Manager

[5] The history list, which can be used to perform calculations in batchmode.

[6] The input window and history list are opened and closed by the
command button.

[7] The database browser which shows the contents of the folder currently
selected.

The browser in this example shows some additional database manager features:

[a] Balloon text: this is not only available for the buttons in the tool bar and the
active parts of the message bar or the browser window, but also for the
data fields.

[b] Title buttons: click on any title button to sort the items in the column; first
click- items are sorted in ascending order; second click - items are sorted
in descending order.

[c] Object buttons: each object is represented by a button (here a line object is
shown). One click selects the object and a double click presents the edit
dialogue for the object.

Figure 5.2: Context sensitive menus in the data manager

PowerFactory makes extensive use of the right mouse button. Each object or
folder may be ‘right-clicked’ to pop up a context sensitive menu. For the same
object the menu presented will differ depending on whether the object is
selected in the left or right hand side of the data manager (this is known as a
’context sensitive’ menu). Generally, the left hand side of the data manager will
show object folders only. That is, objects that contain other objects inside them.

Handling of Power Factory 5-46

DIgSILENT PowerFactory The Database and the Data Manager

The right hand side of the data manager shows object folders as well as
individual objects.

Using the right mouse button to access menus is usually the most effective
means of accessing features or commands. Fig. 5.2 Illustration of a context
sensitive right mouse button menu.
The symbolic tree representation of the complete database shown in the
database window may not show all parts of the database. The user settings offer
options for displaying hidden folders, or for displaying parts that represent
complete stations. Set these options as required.

It is useful to keep in mind that object folders, such as the grid ( ) folder are
merely common folders ( ), that have been designated to contain particular
classes of objects.

5.2 Moving Around in the Database Tree

There are several ways to ’walk’ up and down the database tree:

• Use the mouse: all folders that have a ”+” sign next to them may be
expanded by double clicking on the folder, or by single clicking the ”+” sign.

• Use the keyboard: the arrow keys are used to walk up and down the tree
and to open or close folders (left and right arrows). The PAGE U P and
PAGE D OWN keys jump up and down the tree in big steps and the ”-” and
”+” keys may also be used to open or close folders.

• Use the toolbar in combination with the browser window. Double click
objects (see ”C” in Fig. 5.1) in the browser to open the corresponding
object. This could result in opening a folder, in the case of a common or
case folder, or editing the object dialogue for an object. Once again, the
action resulting from your input depends on where the input has occurred
(left or right side of the data manager).

• The and buttons on the data manager tool bar can be used to
move up and down the database tree.

5.3 Adding a New Item

Generally, new objects are added to the database via the graphical user
interface, such as when a line is drawn between two nodes creating, not only the

Handling of Power Factory 5-47

DIgSILENT PowerFactory The Database and the Data Manager

graphical object on the graphics board, but also the corresponding element data
in the relevant grid folder. However, users may also create new objects
’manually’ in the database, from the data manager.

Certain new folders and objects may be created by right clicking on folders in the
data manager. A context sensitive menu is presented, offering a choice of
objects to be created that will ’fit’ the selected folder. For example, right clicking
a grid folder will allow the creation of a (under the New menu) System Stage,
Graphic or Folder object. The new object will be created in the folder that was
selected prior to the new object button being pressed. This folder is said to have
the ’focus’ for the commanded action. This means that some objects may not be
possible to create since the focused folder may not be suited to hold that object.
For instance: a synchronous machine should not go into a line folder. A line
folder should contain only line routes, line sections and cubicles. The cubicles in
their turn should contain only switches or protection elements.

To access the whole range of objects that may be created the button must
however be pressed (new object button). This is found the data manager toolbar
and presents the dialogue shown in Fig. 5.3.

Figure 5.3: The Element Selection dialogue

To simplify the selection of the new objects, a filter is used to sort the object list.
This filter determines what sort of list will appear in the drop-down list of the
”Element” field. If ”Branch Net Elements” is first selected, the selection of, for
instance, a 2-winding transformer is accomplished by then scrolling down the

Handling of Power Factory 5-48

DIgSILENT PowerFactory The Database and the Data Manager

element list.

The Element field is a normal edit field. It is therefore possible to type the identity
name of the new element, like “ElmTr3” for a three-winding transformer, or
”TypLne” for a line type directly into the field.

The possible list of new objects is therefore context sensitive and depends on
the type or class of the originally selected folder.

After the selection for a new object has been confirmed, the ”Element Selection”
dialogue will close, the new object will be inserted into the database and the edit
dialogue for the new object will pop up. If this dialogue is closed by pressing the
C ANCEL button, the whole action of inserting the new object will be cancelled:
the newly created object will be deleted from the active folder. The dialogue for
the new object may now be edited and the OK button pressed to save the
object to the database.

The following folder types are used in PowerFactory to store objects.

• A Project folder ( ) forms the root of a power system analysis project. A
project folder should normally only contain other folders. These subfolders
store all power system element and type data, single line diagrams, design
alternatives, calculation cases, results, etc.

• A Common folder ( ) is for general use and normally contains a mixture

of objects and other folders.

• A Library folder ( ) A library folder is a special common dedicated to

hold power system type data. A library folder is automatically created in
each new project. Recommended practice is to create new library
subfolders for each new group of type data (i.e. line types, transformer
types, etc.).

• A Grid ( ) folder should contain a logical part of the grid. This could be
the power system of a plant or a village, a part of a high voltage transport
system, etc.

• A Station ( ) folder contains the busbars, cubicles and switches that

belong to the station.

• A System Stage ( ) folder holds changes from a certain base case. All
these changes are carried out when the system stage is activated and
reverted again when it is deactivated.

• A Study Case ( ) folder holds connections to the grids, system stages,

calculation and tool settings for a particular study combination.

Each folder may have an owner name entered, for documentation or

organisational purposes. In this way it should be clear who has created the data.

Handling of Power Factory 5-49

DIgSILENT PowerFactory The Database and the Data Manager

Descriptions may also be added. An existing folder may be edited by using the
”Edit” button ( ) on the toolbar or by using the right mouse button.

Each folder may be set to be read-only, or to be a PowerFactory system folder.

The folder may be a ”Common” or ”Library” folder. These attributes can be
changed in the edit-folder dialogue. These settings have the following meaning:

• Common folders are used for storing non-type objects: elements,

command objects, settings, projects, etc.

• Type folders are used as ’libraries’ for type objects.

• System folders, which are read only folders

The use of Read-only folders is clear: they protect the data. In addition, folders
containing data that is not normally accessed may be hidden. Selecting the kind
of folders that you want to be hidden is done in the user settings dialogue (see
“User Settings”, section 4, page 4-37).

5.4 Deleting an Item

A folder or object which is selected may be deleted by pressing the D ELETE key
on the keyboard, or by clicking the button on the toolbar of the database
manager.

Because most power system objects that are stored in the database are
interconnected through a network topology or through type-element
relationships, deleting objects often causes anomalies in the database
consistency. Of course, PowerFactory knows at any moment which objects are
used by which others and could prevent the user from creating an inconsistency
by refusing to delete an object that is used by others. This, however, would
create a very stubborn program.
PowerFactory solves this problem by using a recycle bin folder. All deleted
objects are in fact moved to the recycle bin. All references to the deleted objects
will therefore stay valid (for example, the reference between element and type),
but will show that the referenced object has been ’deleted’

• by showing the path to the recycle bin and the name of the ’recycle object’
in stead of the original location and name.

• by colour: a reference to a deleted object will be colore red, i.e. a reference

to a type. Type references are found in the edit dialogues of all elements
which use a type like the line or the transformer object.

Handling of Power Factory 5-50

DIgSILENT PowerFactory The Database and the Data Manager

An object that has been deleted by mistake can be restored to the original
location by selecting the restore menu option on the recycle object’s context
sensitive menu. All references to the object will also be restored.

5.5 Cut, Copy, Paste and Move Objects

5.5.1 Cut, Copy and Paste

Cutting, copying and pasting may be achieved in four different manners:

1. By using the data manager tool bar buttons.

2. By using the normal ’MS Windows’ shortcuts :

• C TRL -X will cut a selection,

• C TRL -C will copy it,
• C TRL -V will paste the selection to the active folder.

Cutting a selection will colour the item-icons gray. The cut objects will
remain in their current folder until they are pasted. A cut-and-paste is
exactly the same as moving the object, using the context sensitive menu.
All references to objects that are being moved will be updated.
Cancelling a cut-and-paste operation is performed by pressing the C TRL -C
key after the C TRL -X key has been pressed.

3. By using the context sensitive menu. This menu offers a ‘Cut’, a ‘Copy’ and
a ‘Move’ item. The move item will pop up a small second database tree in
which the target folder can be selected. When the selected objects have
been Cut or Copied, the context sensitive menu will then show a ‘Paste’,
‘Paste Shortcut’ and a ‘Paste Data’ item.

• ‘Paste’ will paste the selection to the focused folder.

• ‘Paste Shortcut’ will not paste the copied objects, but will create
shortcuts to these objects. A shortcut object acts like a normal object.
Changes made to the shortcut object will change the original object.
All other shortcuts to this original object will reflect these changes
immediately.
• ‘Paste Data’ is only be available when just one object is copied, and
when the selected target object is the same kind of object as the
copied one. In that case, ‘Paste Data’ will paste all data from the
copied object into the target object. This will make the two objects
identical, except for the name and the connections.

Handling of Power Factory 5-51

DIgSILENT PowerFactory The Database and the Data Manager

4. By dragging selected objects to another folder. The ”Drag & Drop” option
must be enabled first by double clicking the ”Drag & Drop: off” message on
the data manager’s message bar. When the drag & drop option is on, it is
possible to copy or move single objects by selecting them and dragging
them to another folder. Dragging is done by holding down the left mouse
button after an object has been selected and keeping it down while moving
the cursor to the target/destination folder, either in the database tree or in
the database browser window.

N OTE : When dragging and dropping a COPY of the object will be made (in-
stead of moving it) if the C TRL key is held down when releasing the
mouse button at the destination folder

5.6 Searching for Objects

When searching for objects the first step should be to use the title buttons at the
top of columns; most objects can quickly be found by sorting according to one of
the criteria defined by the title buttons. The ”Edit Relevant Objects for
Calculation” ( )is also useful as it lists all objects that are considered by the
calculation, by class, i.e. all loads element data, or all 2 winding transformer
data, etc.

When using the title buttons to search, the search may be sorted by criteria, as
follows. When looking for, say, a terminal whose name begins with ’B’ and is a
nominal voltage of 11kV the sort criteria could be expressed as; sort by voltage,
then by name. To accomplish this sorting in the data manager start with the last
criteria. For example, I have a project with a number of grids (areas) and
terminals. I wish to find the terminal with the greatest overvoltage, in p.u., at the
11kV level, in a particular area.
After performing a load flow I open an object filter (”Edit Relevant Objects for
Calculation” button) and display all the terminals ( ). The sort criteria is; sort
by Grid, then by nominal voltage, then by calculated voltage level (as calculated
by a load flow).

The sort must be performed in reverse; first I go to the ”Flexible Data” tab to see
calculated voltages and press the ”u, Magnitude p.u.” title button, which sorts all
terminals from highest to lowest voltage. Next I go to the ”Basic Data” tab and
press the ”Nom.L-L Volt kV,” which sorts the terminals by nominal voltage level.
Lastly I press the ”Grid” title button.

Another means of searching is to display the objects through which you would
like to search and select one of the objects - note here that selecting the object
means that you click on the object button on the left hand side, as shown in Fig.

Handling of Power Factory 5-52

DIgSILENT PowerFactory The Database and the Data Manager

5.4. Place the cursor in position [1] and not in positions [2] or [3]. Now type in
the name of the object (the search is case sensitive) that you wish to find and
the selection will jump to objects that match your typing.

Figure 5.4: Selecting an Object

More particular search tasks may be performed using the ”Find ...” button ( ).
Pressing this button activates the ”General Filter” (the user is first offered the
option of using predefined filters or creating a new filter. The filter is used to
define search criteria and is normally used to find a group of objects, rather than
an individual object. It can also be used to define criteria such as, ’find all lines
longer than 700m.’ Even more usefully, the filter is stored and can then be used
to colour the search objects in the single line graphic.

We will use this example to demonstrate the use of the filter. A new filter
dialogue is called for preparation. This filter will be found in the
P ROJECT\C HANGED S ETTINGS\F ILTERS folder of the project.
The filter dialogue has the following fields (see Fig. 5.5):

[1] Name field.

[2] A drop down list provides a number classes in which the search will take
place.

[3] If the class that you wish to search in is not listed, or if you know the class
description (e.g. ElmLne for lines) this can be entered directly here.
Wildcards may be used for the search. For example, to search for all lines
enter ’*.ElmLne’
To search for an objects that have the name ’Lahney’ enter ’Lahney.*’
Searches can be performed across more than one specific class, for
example, to search for line and load objects that start with ’D’ enter

Handling of Power Factory 5-53

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.5: General Filter Dialogue

’D*.ElmLne, D*.ElmLod’ or if you want all elements that begin with D enter
’D*.Elm*’
[4] Select the folder to be searched.
[5] Check the search options as required.
”Include Subfolders” will search the root folder specified as as well as the
subfolders in the root folder.
”Relevant Objects for Calculation” will include only those objects
considered by the active study case (if no study case is active the search is
meaningless and no search results will be returned).
”Area Interconnecting Branches Only” will search through only the branch
elements that interconnect areas (note that ’grids’ are analogous to areas).

N OTE :
OK The OK button will close the search dialogue, but save the filter
object to the C HANGED S ETTINGS\F ILTERS folder. This makes it
available for further use.

CANCEL The CANCEL button will close the dialogue and delete the
filter object. This button can be used when a search criterion
(filter will only be used once.

APPLY The APPLY button starts the actual search. It will scan the
relevant folders and will build a list of all objects that match the
search criteria.

Handling of Power Factory 5-54

DIgSILENT PowerFactory The Database and the Data Manager

Once the search is complete a list of results is returned in the form of a new data
browser widow. From this browser, the returned objects can be marked (in the
graphic), changed, deleted, copied, moved, etc.

Advanced search options allow more sophisticated expressions as search

criteria, and these can naturally be specified in the ”Advanced” tab.
In PowerFactory each parameter has a unique name and this may be used to
access the parameter for a wide variety of uses. The parameter name may be
determined from the object dialogue and in our case we need to know the
parameter name for the line length, which is seen in Fig. 5.6. This parameter
name may be used in conjunction with a wide range of logical expressions, the
only restriction being that the expression used must result in a ’True’ or ’False’
answer.

Figure 5.6: Identifying a parameter name

In our case we are looking for lines longer than 700m, thus we can use ’dline >
0.7’ as shown in Fig. 5.7. The ”Relations”,”Std. Funct.”,”Log.Operat.” and
”Examples” buttons will provide lists of the functions that may be utilized (these
may of course be typed in directly as well).

”Search Literally” is used to search for specific user defined strings ’inside’
parameter fields. For example, perhaps the comment ’damaged but servicible’
has been entered for some elements in the network. This may be searched for
as shown in Fig. 5.8 and all parameter fields will be searched for this string.
The ’Graphic’ tab is used when the filter is applied by the Colour Representation
tool (choose the ”Userdefined Filter” option in the ”Coloring” field of the colour
representation dialogue and select the required filter).

Handling of Power Factory 5-55

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.7: Advanced Filter dialogue

Figure 5.8: Searching Literally

N OTE : When a filter has been created it is saved to the P ROJECT\C HANGED
S ETTINGS\F ILTERS folder in the project and is available for use directly
from the right mouse menu. If a search is to be performed in a partic-
ular area simply right click the area (grid) folder →Find →Local Filters
→Lines longer than 700m (for example). Remember to press the ”Ap-
ply” button to perform the search.

If you uncheck the ”Show Filter Settings before Application” box un-
der ”User Settings”→”General” then the filter will execute the search
as soon as it is selected from the menu. This is useful when you have
already defined several filters for regular use.
Handling of Power Factory 5-56
DIgSILENT PowerFactory The Database and the Data Manager

5.7 Editing Data Objects

The easiest way to edit power system components is from the single line graphic
windows. By double clicking a graphical component symbol, the edit dialogue of
that component will appear, allowing editing of not only the element data but
other, directly related, objects, such as type data, or internal objects such as
switches.

The database manager offers several ways to edit the power system
components, or any other object stored in the database, but not seen in the
single line graphic.
The basic method is to double click the object icons in the database browser.
This will open the same edit dialogue window as used with the single line
graphics. See Fig. 5.9.

Figure 5.9: Opening an edit window from the data manager

An open edit dialogue will disable the data manager window from which it was
opened. The edit dialogue has to be closed first in order to open another edit
dialogue.
However, it is possible to activate more than one data manager (by pressing the
button on the main toolbar) and to open an edit dialogue from each of these
data managers. This can be useful for comparing objects and parameters.

Handling of Power Factory 5-57

DIgSILENT PowerFactory The Database and the Data Manager

Using the full size edit dialogues has one major drawback: it separates the edited
object from the rest of the database, making it impossible to copy data from one
object to the other, or to look at other object parameter values while editing.
PowerFactory brings the big picture back in sight by offering full scale editing
capabilities in the data managers browser window itself. The browser window in
fact acts like a spreadsheet, where the user can edit and browse the data at the
same time. The browser window has two modes in which objects can be edited,

• Object mode

• Detail Mode

which are described in the following sections.

5.7.1 Editing in Object Mode

In data mode, the browser window only shows the icon, the name and the type
of the objects.

Figure 5.10: The browser window in ’object’ mode

The title buttons are used to sort the entries in the browser (see [2], [3] and [4] in
Fig. 5.10). The visible data fields can be double clicked to edit their contents [5],
or the F2 button can be pressed. The object will show a triangle in its icon when
it is being edited [1].

After the data field has been changed, move to the other fields of the same
object using the arrow-keys or by clicking on these data fields, and alter them
too.
The new contents of a data field are confirmed by pressing the RETURN key, or
by moving to another field within the same object. The triangle in the icon will
change to a small star to show that the object has been altered. The object itself
however has not been updated. Updating the changes is done by pressing

Handling of Power Factory 5-58

DIgSILENT PowerFactory The Database and the Data Manager

RETURN again, or by moving to another object in the browser. By default,

PowerFactory will ask you to confirm the changes. See the 4 section to disable
these conformation messages.

5.7.2 Editing in “Detail” Mode

If the button on the data manager toolbar is pressed (see [1] in Fig. 5.11),
the browser changes to ’detail’ mode. It will display only the objects from the
same class as the one which was selected when the button was pressed. In the
examples, this is a load object (ElmLod). The button may also be used to
engage detail mode- a list of objects classes in the selected folder is provided;
choose one of these to engage detail mode for that class.

Figure 5.11: The browser window in ’detail’ mode

In ’detail’ mode, the browser shows all data fields [2] for the selected calculation
function data set, which can be selected by clicking on a page tab [4]. If a page
tab is out of reach, then the page tab scrollers [5] will bring it within the browser
window again.

The list of objects may be sorted by any column by pressing the title field button.
The widths of the data fields can be adjusted by pointing the mouse between two
title fields [2] and dragging the field border by holding a mouse button down.

As with the browser in ’object’ mode, the data fields can be edited by double
clicking them. In the example the active power settings are being edited [3], but
from the star in the object icon it is clear that another field of the same object has

Handling of Power Factory 5-59

DIgSILENT PowerFactory The Database and the Data Manager

been edited too, but not confirmed, because this star would otherwise be a
triangle.

It is possible to change a parameter field for more than one object simultaneous.
This is, for instance, useful to raise a certain limit for a range of objects, in order
to get a better load-flow result i.e. by alleviating line overloads. An example is
shown in Fig. 5.12 where the nominal current for a range of line types is
changed at once.

Figure 5.12: Modify values dialogue

The parameter fields which have to be changed have to be multi-selected first.

Right-clicking the selection will pop up a case sensitive menu from which the
Modify Value(s) option opens the SetValue dialogue. See Fig. 5.12.

This dialogue can be used to:

• increase or decrease them by multiplication with a scale factor (“Relative”).

• increase or decrease them by multiplication with a scale factor with respect

to the sum of values selected (“Relative to Sum”).

• Set all the selected parameter fields to a new fixed (“absolute”) value.

It is not possible to simultaneously alter parameter fields from more than one
column, i.e. to change nominal currents and nominal frequencies simultaneous,
even if they would happen to take the same value or would have to be raised
with the same percentage.

Handling of Power Factory 5-60

DIgSILENT PowerFactory The Database and the Data Manager

5.7.3 Copy and Paste while Editing

One of the great advantages of editing data fields in the data manager’s browser
window is the possibility to copy data from one object to another. This is done by
selecting one or more objects or object fields, copying this selection to the
clipboard, and pasting the data back in another place.

To copy one or more objects,

1. select them (see [1] in Fig. 5.13).

2. press C TRL -C to copy or use the button on the data manager toolbox.

3. press C TRL -V to paste or use the button on the data manager toolbox.
The objects will be copies with data and all. Their names will automatically
be altered to unique names [2].

Figure 5.13: Copying an object in the browser

To copy one or more data fields,

1. Select them by clicking them once (see [a] in Fig. 5.14). Select more data
fields by holding down the C TRL key [b].

2. Copy the fields to the clipboard by pressing C TRL -C or the button.

3. Select one or more target objects data fields. If more than one field was
copied, make sure that the target field is the same as the first copied data
field [c].

4. Press C TR -V or the button. The contents of the data fields will be

copied to the target objects [d] and [e].

Handling of Power Factory 5-61

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.14: Copying data fields in the browser

5.8 Additional Features

Most of the data manager functionality is available through the context sensitive
menus (right mouse button).
The following items can also be found in the context sensitive menus:

Show Reference List. Produces the list of objects that have links, or references
(plus the location of the linked object), to the selected object. The list is
printed to the output window. In this manner for example, a list of elements
that all use the same type can be produced. The listed object names can
be double- or right-clicked in the output window to open their edit dialogue.
Select All. Selects all objects in the database browser.
Mark in Graphic. Marks the highlighted object(s) in the single line graphic. This
feature can be used to identify an object.
Show →Station. Opens the station graphic of the station to which the selected
object belongs. If the object belongs to more than one station, as might be
in the case of lines or other objects, a list of possible stations is shown first.
Goto Busbar. Opens the folder in the database browser that holds the busbar
to which the currently selected element is connected. If the element is

Handling of Power Factory 5-62

DIgSILENT PowerFactory The Database and the Data Manager

connected to more than one busbar, a list of possible busbars is shown

first.

Goto Connected Element. Opens the folder in the database browser that holds
the element that is connected to the currently selected element. In the
case of more than one connected element, which is normally the case for
busbars, a list of connected elements is shown first.

Calculate. Opens a second menu with several calculations which can be

started, based on the currently selected objects. A short-circuit calculation,
for example, will be performed with faults positioned at the selected
objects, if possible. If more than one possible fault location exists for the
currently selected object, which is normally the case for station folders, a
short-circuit calculation for all possible fault locations is made.

Other useful features:

• Relevant objects for calculations are tagged with a sign (this will only be
shown following a calculation). Editing one of these objects will invalidate
the calculation results.

5.9 The Flexible Data Page Tab

The data browser (this will be seen in the data manager when the ”Detail Mode”
has been engaged) has page tabs for all calculation functions. These tabs are
used to look at or edit object parameters for a particular calculation function and
have a fixed format.

The flexible data tab, normally used to display calculation results, also allows the
user to define a custom set of data to be observed.

The format for the calculation results is determined by the calculation function;
the variables displayed following a load flow calculation, for terminals, will be
Line-to-Line voltage in kV, per unit voltage and Voltage angle in degrees. A short
circuit calculation for terminals will use another format and variables such as
Initial Short Circuit Current, Initial Short Circuit Power, Peak Current, etc. are
displayed. Fig. 5.15 shows an example of the flexible data page tab.
The user may customise this list by either pressing the button on the
database manager toolbar or by right-clicking the flexible page tab. This pops up
the ”Flexible Page Selector” dialogue- note that the tab that is displayed in the
flexible page selector is the same as the calculation that has just been
performed- in this case the load flow tab. The ”Variables” may now be edited for
selection by pressing the ”Edit” button as shown in Fig. 5.16. The selection of
these variables is discussed in the next section.

Handling of Power Factory 5-63

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.15: The Flexible Data page tab

Figure 5.16: The Flexible Page Selector

5.10 Variables and Variable Sets

Although only a few variables are displayed on the single line diagram, or in the
Flexible Data tab PowerFactory uses a very large set of variables and all of
these are available to the user for display, or for use within analysis routines.

The ”Variable Set” object (*.IntMon) is used to manage these variables and
display or monitor a particular set or the complete variable set that is available.
The variable set object is accessed through various means, such as the ”Flexible
Page Selector” or the ”Form” object that is presented when editing results on the
single line diagram.

An example of the variable set object is shown in Fig. 5.17.

[1] This picture illustrates the variable set for the load object called ’Bulk Load,’
which is found in the ’Grid’ folder of the active project [1]. Since a load flow
calculation has just been performed the load flow tab has been selected [5].
Note that if the variable set dialogue has been accessed when editing a
results box or flexible page selector the variables that are chosen are
displayed for the entire class of variable selected in the ”object” field. In
other words, in this case the ’Bulk Load’ is the selected object so the

Handling of Power Factory 5-64

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.17: Example of a Variable Set dialogue

variable set will be applied to the ElmLod class.

[2] If no object has been selected the ”Class Name” field becomes active. This
is normally used for more advanced studies and need not be explained
further here.

[3] When performing simulation studies over time it is useful to sometimes have
the output values of the selected variables printed to the output window as
the simulation is running. This is achieved by checking this box.

[4] As mentioned previously, there are a large number of variables that may be
observed in PowerFactory. To be able to find and select these they are
sorted into sets. A series of filters allows the user to sort through the sets.

[5] The load flow tab has been automatically selected as a prior load flow
calculation was performed.

[6] All of the variables that are available for display are listed here (as sorted by
the filter).

[7] The selected variables are shown here. Variables are placed here by
highlighting (selecting) them on the ”Available Variables” side and then

Handling of Power Factory 5-65

DIgSILENT PowerFactory The Database and the Data Manager

pressing the button. Individual variables can also simply be double

clicked to transfer them from one column to the other.

[8] If this box is checked then all of the selected variables are shown in the
”Selected Variables” area. If it is not checked then the filter will also apply
to the ”Selected Variables” area and only those selected variables in the
filtered set will be shown.

The first sorting of the variables, as we have already seen, is by calculation

function (load flow, short circuit, etc.). Within these sets variables are sorted into
sub-sets as follows (these sub-sets may be found in the drop down list of the [a]
field):

• Currents, Voltages and Powers; almost self explanatory- these are the
outputs as calculated by a calculation function. The variable is preceded by
”m:” (representing ’monitored’ or ’measured’) as in ”m:P:bus1” for the
active power drawn by the load.

• Bus Results; variables for the bus/s that the element is connected to
(usually preceded by ”n:”). A branch element (having only one connection
to a bus) will obviously only have results for ”Bus1.” An edge element (two
connections, as in a line for example) will have ”Bus1” or ”Bus2.” This
means that you can access the results for objects that are connected to the
object that you are compiling the list for. An example of this variable is the
open end voltage at a line end. See following for a more complete
explanation of usage. Also see 5.10.1 for more on Bus1, Bus2, etc.

• Signals; variables that are used between models (inputs and outputs) and
are preceded by ”s:”. These should be used when creating a controller or
in a DPL script. These variables are accessible whilst an iteration is being
calculated, whereas the other variables sets are calculated following an
iteration.

• Calculation Parameter; variables (such as loading, or losses) that are

derived from the ’core’ calculation, or are derived from input data, such as
absolute line impedance (derived from impedance/ km * line length), or
have been transformed from input data to a format useful for calculation
(actual to per unit), or that are required for such transformation (e.g.
nominal power). Preceded by ”c:”

• Element Parameter; variables that belong to the directly to the object

selected in [1] (preceded by ”e:”). For general use, where the selected
object is an Element (as opposed to a Type) this will mean that these are
indeed Element variables and the user need not trouble themselves further.
For further explanation please see the note at the end of this section.

• Type Parameter; type variables that are linked to the element object under
consideration; for example, the current rating of a line type that a line
element is using.

Handling of Power Factory 5-66

DIgSILENT PowerFactory The Database and the Data Manager

• Reference Parameter; these are are variables from objects that are linked
or connected to the object under consideration (preceded by ”r:”). For
example, a line element may be part of a line coupling and the reference
parameter will allow us to display the name of the coupling element. The
use of reference parameters is explained following.

Buttons on the right of the dialogue are:

B ALANCED toggles between the balanced and unbalanced variable set.

goes to the manual input page for variables- for advanced use.

P RINT VALUES prints the current values for all the selected variables to
the output window.

VARIABLE L IST prints a list of all available variables to the output window.

VARIABLE L IST (PAGE ) prints a list of available variables for the current
tab (e.g. Basic Data) to the output window.

For general use it is sufficient to simply select the variables required and transfer
them to the selected variables column. To find a particular variable requires
some knowledge of where the variables are stored in the object under
consideration. As an example we will display the

type name

the tap setting

the nominal and calculated voltages at the HV node

for a particular transformer.

These variables may need to be displayed on the single line diagram so we will
start by creating a textbox and editing its format (this process is described in
@@@ CROSS REF REQUIRED). These variables may also be displayed in the
flexible data tab - the process is the same.

The name of the transformer type is entered in the type data so we select the
type parameters [1] in the filter- the name is also entered on the basic data tab
so we should select this tab [2], and the type name parameter is ”loc name,”
which is now selected [3]. Notice that the focus object for the variable set object
is a transformer [4]. This has been automatically selected since we created a
textbox for the transformer by right clicking it.
The tap setting will be found in the element data and the parameter is located on
the load flow tab (this information is gained as the user becomes more familiar
with PowerFactory and recalls where the data was entered; such recollection
directs the user to the correct variable sub-set). The variables seen in the
selected Variables column should now be:

Handling of Power Factory 5-67

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.18: Finding the type name

t:loc_name
e:nntap

To now be able to see the variables for the HV bus we use the reference
parameters. The reference parameters work like a ’refer to’ command. In Fig.
5.19 this is illustrated schematically. We have started by creating a variable set
for the object ’Supply TX1’ which is an element object. Using the reference
parameter we will refer to the object that the HV side of the transformer is
connected to [1], which is a cubicle. Since the nominal and calculated voltages
of the node are located in the node object itself we will next need to refer to this
node object [2].
In a step by step fashion the process will now be shown. We first need to refer to
or ’jump to’ the cubicle. If we picture the input dialogue for the transformer
element we recall that the connections for the HV and LV sides are listed on the
basic data tab, so this is where we will logically find the ’link’ to the connected
object (the cubicle). In Fig. 5.20 we can see that this selection has been made
[1]. We also notice that the object that is presently the focus is the transformer
element [2]. To affect the jump to the cubicle we choose the reference parameter
set [3] and then select the object that we want to jump to, the cubicle connected

Handling of Power Factory 5-68

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.19: ’Refering to’ with reference parameters

to the HV side [4].

Double clicking on this jumps us to another variable set object whose focus
object is the cubicle that the HV side of the transformer is connected to. It is not
immediately obvious that the jump has occurred as the new variable set object
appears directly on top of the original one. If you grab the one that appears
before you and drag it to one side it will become more obvious (you can also see
this by noting that the name in the ”Object” field has changed), and will look as
follows:
The second jump must now be affected - to the node that the cubicle is
connected to. In a logical fashion this ’connectivity’ is also found on the basic
data tab. Fig. 5.22 shows these jumps [1][2] in PowerFactory, as they were
schematically described in Fig. 5.19. Lastly, the parameter required must be
selected [3].
The parameter we wish to display is the nominal voltage of the connected node.
This will be found on the Basic data tab and we must choose the element
parameter set to find the parameter, as shown in Fig. 5.23. The parameter is
called

uknom kV Nominal Voltage: Line-line

At this point we could also add the calculated voltage for the node. This will be
found under ”Currents, Voltages and Powers” on the load flow tab.

Handling of Power Factory 5-69

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.20: Selecting the parameter to be displayed

Figure 5.21: Jumping to the next object using the reference parameter

Handling of Power Factory 5-70

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.22: Jumping to the node

After you have clicked OK until you are back at the original variable set object
you will see that these referenced variables have been added as:
r:bushv:r:cBusBar:e:uknom
r:bushv:r:cBusBar:m:U
which can be read as →’jump to the HV bus’ →’jump to the connected node’
→’display the selected variables.’

Once the user is more familiar with this nomenclature this jump may be typed in
directly to the variable set object. The understanding of this is also useful for
writing DPL scripts.

Note: in this particular example we have used a ’long’ method to show to the
node variables for illustration purposes. Typically, however, a user wishes to
display calculated variables such as the voltage at the end of a line where the
breaker at that end is open. In this case PowerFactory has a special ’shortcut’
set - the ”Bus Results.”

These bus results can only be seen in the calculation function tabs and they are
drawn from an internal node that is not displayed on the single line graphic. An
illustration of this node and its relationship to the cubicle is shown in Fig. 5.24.
An additional example on the use of reference parameters is the display of
conductor types (*.TypCon) for a line element (*.ElmLne) that uses a tower type
(*.TypTow). Once the variable set manager for the line is displayed, the basic
data tab is selected, then the reference parameter set, and the referenced

Handling of Power Factory 5-71

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.23: Jumps to the node

variables, of which the conductor types are one, is displayed. Once again this is
a convenient shortcut that has been made for this combination of element and
type.

Should the tower be close to another tower, and thus be coupled by a coupling
element however, the coupling element object must first be referenced. The
procedure would be:

select the reference parameter set on the basic data tab (assuming that
you have started at the variable set object for the line element)

double click the ”c ptow Line Couplings” variable (or select it and then
press the arrow button to transfer the variable to the ”Selected Variables”
column)

select the ”loc name Name” variable and transfer it to the ”Selected
Variables” column

Handling of Power Factory 5-72

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.24: Internal node

press ”OK” until you return to the graphic or flexible data tab

N OTE : In the above examples we have used the element parameter set to
access variables of the element class (*.Elm* - what we ’traditionally’
know as elements in PowerFactory). However, it should be borne in
mind that ”Element Parameter” actually refers to the parameters of the
focus object.
For example, if we have referenced the variable set from a line ele-
ment →(then to) line coupling →tower type →conductor type the focus
object is already a type and ”Element Parameters” refers to the param-
eters of the type object itself.

5.10.1 Bus1, Bus2, Bushv, Buslv and Localbus Explained

When selecting variables from the ”Currents, Voltages and Powers” set the user
will notice that there is a filter called ”Bus Name.” This is used to determine
which side of an edge element is to be considered.

To maintain standard nomenclature the objects at the ends of a line element are

Handling of Power Factory 5-73

DIgSILENT PowerFactory The Database and the Data Manager

named ”Terminal i” or ”Terminal j” and ”HVside” or ”LVside” in the case of a

transformer.

The ends of an edge element are named ”bus1” or ”bus2” and ”bushv” or ”buslv”
respectively (a three winding transformer will also have ”busmv”). These ends
are matched to the ”i” and ”j” sides so that i →bus1 or bushv and j →bus2 or
buslv. Thus, when choosing variables from the flexible page manager the user
should specify which side of the edge element the variables are to be taken
from. Note that ”bus1, bus2, bushv, buslv” are not references to the
connected node, they are in fact the ends of the edge element.

When a variable is selected for display from the single line graphic the user will
notice a further classification, that of ” LOCALBUS.” This classification merely
indicates the end of the edge element and describes internally which side of the
edge element the result box should access its variables from. That is the ’bus’
local to that end.

5.11 Save and Restore Parts of the Database

A selected part of the database can be written to a “DZ” Import/Export file with
the button E XPORT DATA ... ( ). This will bring a ’File Save’ dialogue where
a filename must be specified.

Alternatively, the folder or object that is to be exported can be right-clicked in the

database tree, after which the option Export Data .. is selected.

The exported part of the database may be a complete project, a library, or a

specific object in the browser window. Exporting a folder (i.e a project, grid,
library, etc.) will export the complete content of that folder, inclusive subfolders,
models, settings, single line graphics, etc.

It is even possible to export a complete user account. However, only the

administrator is able to import an user-account. Exporting the user-account on
a regular basis is a practical way to backup your data.
It is even possible to export data from another user account, or even to export
another user-account completely. However, only the shared, visible, data will be
exported.

The exported data file can be imported into the database again in any desired
folder by pressing the I MPORT DATA .. ( ) button. This will bring a ’File
Open’ dialogue where the “DZ” data-file can be selected.

The “DZ”-file will be analyzed and error messages will be displayed when the file
is not a genuine PowerFactory data file, or if it is corrupted. If the file format has

Handling of Power Factory 5-74

DIgSILENT PowerFactory The Database and the Data Manager

been found to be correct, a dialogue will appear which shows the data and
version of the file. The default target folder is shown also, which is the original
folder of the saved data. If this is not desired, another target folder can be
selected by pressing the D ROP D OWN button. This button will bring a small
version of the database tree. A new target folder can be selected from this tree.

5.11.1 Notes
By exporting a folder from the database, only the information in that folder and
all its subfolders will be stored. If the exported objects use information (e.g.
power system types like line or transformer types) that is saved somewhere else,
then that information will not be stored. Make sure that the used power system
types and all other referenced information is exported too.

When a file is imported which contains objects which use data outside the
import-file, then a search is started for that data.
For instance, assume a project is exported. One of the line-models uses a type
from a library outside the project. When exporting, the path and name of this
type is written in the export-file, but the type itself is not exported, as is does not
reside in the exported project.
At importing, the stored path and name of the ‘external’ type is used to find the
type again and to restore the link. However, if the ‘external’ type is not found,
then it will be created, using the stored path and name. Of course, the created
object has default data, as the original data was not exported. Additionally, an
error message is written to the output window.

Suppose that you are working with a large library, which is stored in a special
user-account to make it read-only. The library is made accessible by sharing it to
all users.
When you export your projects, then the objects from the external library are not
exported. However, a colleague which has access to the same library may still
import your projects without problems. The external objects used in your
projects will be found in the same location, and the links to these objects will be
correctly restored.

5.12 Spreadsheet Format Data Import/Export

The PowerFactory data browser in the data manager’s window looks and acts
like a spreadsheet program as far as creating and editing power system objects
is concerned. To enable and simplify the use of power system element data
which is stored in spreadsheet programs such as the Microsoft Excel or the
Lotus 123 programs, the data browser offers ’Spreadsheet Format’ import and
export facilities.

Handling of Power Factory 5-75

DIgSILENT PowerFactory The Database and the Data Manager

5.12.1 Export to Spreadsheet Programs

All data visible in the data browser may be exported as it is. The export format is
such that most common spreadsheet programs can read in the data directly
(space separated ASCII). Exporting data is performed as follows.
• Select a range of data in the data browser. Such a range may contain more
than one column and more than one row.
• Right click the selected range and select the Spread Sheet format option.
This opens a second menu which offers the choice between writing the
Spreadsheet export to a file, or to put it on the Windows Clipboard. See
Fig. 5.25.
• The exported data can now be imported into a Spreadsheet program.
When the Clipboard was used, pressing C TRL -C will Paste the data into
the spreadsheet.
• The imported data may now be edited, or additional calculations may be
made. The PowerFactory data is imported as numbers and descriptions.
The example in Fig. 5.26 calculates a mean value from a range of line
loading percentages.

Figure 5.25: Exporting a range of data

5.12.2 Import from Spreadsheet Programs

There are two methods available for importing data from a spreadsheet program.
The first method uses a direct import of ‘anonymous’ numerical data. This

Handling of Power Factory 5-76

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.26: Imported data in a spreadsheet program

method is used to change parameter of existing objects by importing columns of

parameter values.
The second method uses the versatile DOLE conversion module. This method
can be used to create new objects by importing all the data from a spreadsheet.

Importing Anonymous Values

Any range of parameter values can be copied from a spreadsheet program and
imported into the database manager. The import is performed by overwriting
existing parameter values by ‘anonymous’ values. The term ‘anonymous’
expresses the fact that the imported data has no parameter description. The
size of the imported value range and the required data are tested. Importing
invalid values (i.e. a power factor of 1.56) will result in an error message.

The import of anonymous values is explained by the following example.

In Fig. 5.27, a range of active and reactive power values is copied in a

spreadsheet program. In Fig. 5.28, this range is copied to the corresponding
fields of 10 load objects by right clicking the upper left most field which is to be
overwritten. The result of this action is shown in Fig. 5.29.

5.12.3 The DIgSILENT Object Language for data Exchange

(DOLE)
The DIgSILENT Object Language for data Exchange is the general language
used to import objects and data from other programs.

Handling of Power Factory 5-77

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.27: Copying a range of spreadsheet data

Figure 5.28: Pasting spreadsheet data from clipboard

Figure 5.29: Database browser with imported data

Handling of Power Factory 5-78

DIgSILENT PowerFactory The Database and the Data Manager

DOLE Spreadsheet Import of Objects and Parameter

The anonymous import of data does not need a parameter description. This
would complicate the import of complete objects, as we would have to enter all
parameters in the correct order. The DOLE import therefore uses a header line
with the parameter name. This header must have the following structure:

• The first header must be the class name of the listed objects.

• The following headers must state a correct parameter name.

This is shown in Fig. 5.30.

Figure 5.30: Excel required format

Fig. 5.31 shows an example of valid spreadsheet data of some line types and
some 2 winding transformer types.

Figure 5.31: Example of valid spreadsheet data

The import of the spreadsheet data into PowerFactory is performed as follows.

• Select the header line and one or more objects lines.

• Copy the selection. See Fig. 5.32 for example.

• Right click the folder browser in the database manager to which the objects
are to be imported. Select ‘Spread Sheet Format > Paste DOLE from
Clipboard’. See Fig. 5.33 for example.

Handling of Power Factory 5-79

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.32: Selecting DOLE data in spreadsheet

Figure 5.33: Importing DOLE from clipboard

The result of the DOLE import depend on whether or not objects of the imported
class and with the imported names already exist or not in the database folder. In
the example of Fig. 5.34, non of the imported objects existed in the database an
all where created new therefore. The example shows the database in detail
mode.

Figure 5.34: Result of DOLE spreadsheet import

New objects are created in the PowerFactory database folder only when no
object of the imported class and with the imported name is found in that
folder. If such an object is found then its data will be overwritten by the
imported data

Handling of Power Factory 5-80

DIgSILENT PowerFactory The Database and the Data Manager

Because new objects are only created when they do not exist already, and only
the imported parameters are overwritten when the object did exists already, the
import is always a save action.

Remarks

Object Names Object names may not contain any of the characters
* ? = " , \ ~ |
Default Data When an imported object is created newly, the imported data is
used to overwrite the corresponding default data. All parameters that are
not imported will keep their default value.

Units The spreadsheet values are imported without units. No conversion from
MW to kW, for example, will be possible. All spreadsheet values therefore
have to be in the same units as used by PowerFactory.

5.13 Importing Version 3.1x Files

Because the internal representation of mathematical models and single line

graphics has changed dramatically between previous versions and this version
of DIgSILENT PowerFactory, it is necessary to convert the previous version
data files to the new database format.

Converting files is done with the ComCv command dialogue, which can be
opened by selecting the Convert (version 10.3) item from the main
PowerFactory menu. See Fig. 5.35.
The ComCv command dialogue has a list of file formats to convert from:

1. DSL Model Library (modlib.dig)

2. System database, DIgSILENT Format (*.*)

3. System database, DBASE Format (select lne.dig)

4. Relay database File (*.*)

5. Calculation data (*.pbm)

6. Single Line Fonts (select ..10.3\CNF\fonts.dig)

7. Single Line (*.igf)

The target project has to be set at the option Save Converted Data In. All
created DIgSILENT PowerFactory objects will be stored in that project. To
import a complete 10.3 project normally means to convert databases, single

Handling of Power Factory 5-81

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.35: The Convert Command dialogue

lines, relay, etc. The ComCv command has to be opened more than once in
such a case for each conversion. Changing the target project in between these
successive conversions would break up the imported project into several useless
project parts. The target project should therefore be selected only once.

The conversion itself is performed by selecting a file format and pressing the
A DD F ILES button. This will bring a “File Open” dialogue with which a file can
be selected. The selected file will appear in the File Names list. More than one
file can be selected by pressing the A DD F ILES again. It is not possible to add
files of more than one format: selecting another file format will clear the file list.
All files in the list will be interpreted according to the selected file format,
independent of the actual filename extension.

When a file selection has been given, and the target folder has been specified,
the E XECUTE button can be pressed. DIgSILENT PowerFactory will start the
conversion and will report all errors to the output window.

The calculation data files (*.pbm) may be dependent on one ore more other files
of the first four listed formats. These files must therefore be converted first. The
file formats listed above (1..7) are listed in the recommended order of
conversion.

It is strongly advised to perform the conversion in the order as given by the

drop-down File Type list in the conversion dialogue. The conversion of a
complete project, comprising several file types and data files, should be done in
one session. It is recommended to copy and save the project files before
converting them. It is recommended to export the new converted
(PowerFactory) database folders as soon as the conversion has been
performed successfully and to store the exported file in a save place.

Handling of Power Factory 5-82

DIgSILENT PowerFactory The Database and the Data Manager

See section 5.11, page 5-74 for more information about exporting parts of the
PowerFactory database.

When converting the *.pbm files, the original name and the target folder of the
previously converted system database file and relay database file has to be
given in order to convert the inter-object dependencies correctly. If the files are
converted in the recommended order, these original names and target folders
will be selected automatically.

Besides dependent of the first four formats, calculation data files (*.pbm) may be
dependent on each other. If this is the case, then all *.pbm files that belong
together must be converted as a whole by adding them all to the file selection
box. The *.pbm files are converted in the order in which they appear in this box.

5.14 The Input Window

The input window is for the more experienced users of DIgSILENT

PowerFactory. It is closed by default. Almost all commands that are available in
PowerFactory through the menu bars, pop-up menus, icons, buttons, etc., may
also be entered directly into the input window, using the PowerFactory
commands.

The contents of the input window can be saved to file, and commands can be
read back into the window for execution.
PowerFactory also has special command objects which carry one single
command line and which are normally used to execute commands. In this way,
complex commands can be saved in the same folder as the power system for
which they were configured.

5.15 Input Window Commands

In principle, everything that can be done in DIgSILENT PowerFactory, can be

done from the command line in the input window. This includes creating objects,
setting parameters, performing load-flow or short-circuit calculations.

Some commands that are available are typically meant for command line use or
for batch commands. These commands are rarely used in another context and
are therefore listed here as “command line commands”, although they do not
principally differ from any other command.

Handling of Power Factory 5-83

DIgSILENT PowerFactory The Database and the Data Manager

Cd Command
Moves around in the database tree by opening another folder at a relative
position from the currently open folder.
Example:

cd ..\gridB\Load1

Cl Command
Stops the redirection of the output window to either a file or to a printer. All
following messages will again be shown only in the output window.

cl/out stops redirection to a file

cl/prn stops redirection to a printer

Cls Command
Clears the output or input window.

cls/out clears output window

cls/inp clears input window completely

cls/inp/done clears only previously executed commands

.../y asks for confirmation

Dir Command
Displays the contents of a folder.
Example:

dir Study Case

Ed Command
Pops up the dialogue of a default command, i.e. “ldf”, “shc”, etc.
Example:

ed ldf

Exit Command
Exits the program immediately without further confirmation.

Handling of Power Factory 5-84

DIgSILENT PowerFactory The Database and the Data Manager

Man Command
Queries or sets a variable.
Example:

man/set obj=Load_1.elmlod variable=plini value=0.2

Op Command
Redirects output to either a file or a printer.
Example:

op/out f=train3.out

Pause Command
Interrupts the execution of the command pipe until a next pause command is
executed.

Pr Command
Prints either the contents of the output window or the currently active graphics
window.

Rd Command
Opens and reads a file.

Stop Command
Stops the running calculation.

Sys Command
Executes a dos command.

Wr Command
Writes to a file.

Handling of Power Factory 5-85

DIgSILENT PowerFactory The Database and the Data Manager

5.16 The Database Manager Message Bar

The message bar shows the current status and settings of the database
manager. Some of the messages are in fact buttons which may be clicked to
change the settings.
The message bar contains the following messages.

• “Pause: on/off” (only in case of an opened input window) shows the status
of the message queue in the input window. With pause on, the command
interpreter is waiting which makes it possible to create a command queue.
The message is a button: double clicking it will toggle the setting.

• “N object(s) of M” shows the number of elements shown in the browser

window and the total number of elements in the current folder.

• “N object(s) Selected: “ shows the number of currently selected objects.

• “Drag & Drop: on/off” shows the current drag & drop mode. Double clicking
this message will toggle the setting.

5.17 Special Folders in the Database

The PowerFactory database contains simple objects and folder objects. Simple
objects are end-points in the database tree: they do not contain more
sub-objects. Examples are many power system elements and types: switches,
busbars, machines, loads. However, transmission lines, for example, are folder
objects, because they may contain sections, routes and feeders.

The following sections describe the most important folder objects and their use.

5.17.1 The Common Folder

A new common folder (IntFolder, ) can be created in the database tree from
the context sensitive menu of existing folders by selecting the New option and
subsequently the Folder option from the second menu.

The common folder object is the main building block of the database tree. It is
used to store a multitude of other (folder)objects and has therefore much in
common with a “subdirectory” on a normal computer hard disk. However, the
PowerFactory database tree does not show a hard disk file structure, but the
more abstract database structure.

Handling of Power Factory 5-86

DIgSILENT PowerFactory The Database and the Data Manager

The common folder has an user-defined name and an user-defined owner. The
owner field may be used for names of power system engineers, project names,
department names, or any other useful information.

The common folder may be set to be read-only to protect the contents from
unintentional changes.

5.17.2 The Grid Folder

A new grid folder (ElmNet, ) can be created in the database tree from the
context sensitive menu of existing project folders by selecting the New option
and subsequently the Grid option from the second menu. This will create a new
but empty grid folder. By selecting the File-New option from the PowerFactory
main menu and consequently selecting the “Grid” option from the ComNew
dialogue, a grid folder will be created together with a single line graphic. This
single line graphic will automatically open in order to create the grid topology.

The grid folder contains all information about a certain (part of a) power system.
This includes one or more single line graphics, the power system objects, the
station folders, the system stages, etc.

The grid folder dialogue, as depicted in Fig. 5.36, has a name, an owner and a
nominal frequency.

Figure 5.36: The Grid Edit dialogue

5.17.3 The Station Folder

A new station folder (ElmStat, ) is created by adding a new busbar (system)
in the single line graphic. Because all busbars must reside in a station, this will
automatically create a station folder in which the new busbar(s) will be stored.
Different stations may be combined into larger stations later on.

The station defining dialogue is explained in the section “Station and Busbar
Models” (sec. 8.2, page 8-151).

Handling of Power Factory 5-87

DIgSILENT PowerFactory The Database and the Data Manager

5.17.4 The Single Line Graphic Folder

A new single line graphic folder (IntGrfNet, ) is normally created
automatically when a new grid folder is created from the File-New option on the
main menu.

A new single line graphic folder may also be created from the option New from
the context sensitive menu of the folder in which the graphic should be stored by
selecting the Graphic option from the second menu.

The context sensitive menu of a graphic folder has a Show Graphic option which
will open a ’graphics board’ object in which the graphic will be shown.

More about single line and other graphics can be found in the chapter “Graphic
Windows” (sec. 7, page 7-110).

5.17.5 The Graphic Board Folder

A new graphics board folder (SetDesktop, ) is created as soon as a
graphics object (single line graphic, block diagram, etc.) has to be shown. A
graphics board has pages which acts as virtual paper on which the graphical
objects can be drawn.

A graphics board has icons for creating new graphic objects and for showing
existing ones. In these cases, no new graphics board will be created, but the
added graphic objects will be drawn on new pages in the same graphics board
object.
The graphics board has page tabs to quickly move from one graphic page to
another.

The graphic board folder stores references to the displayed graphics in case of
single line or block diagrams, and stores the actual information in case of a
virtual instrument panel.

5.17.6 The System Stage Folder

A new system stage folder (IntVariant, ) is created from the parent folder by
selecting the New option from the parent folder’s context sensitive menu and
consequently selecting the System Stage option.

A system stage is a special ‘administrator’ folder which is used in the hierarchical

and non-redundant system stage administration system. It is capable of stealing
the grid information of its parents and keeping track of all changes made to
these grids. At returning the information to the parents, the changes registered
by the system stage folder will be undone. The system stage folder uses special
registration objects to keep the changes made. The next time the system stage

Handling of Power Factory 5-88

DIgSILENT PowerFactory The Database and the Data Manager

folder is activated, it will reactivate all the changes made the last time it was
activated.

The System Stage folder has an user defined name, an optional user defined
owner name and an optional user defined description. The contents button will
show the current contents of the folder.

A system stage folder may be ‘reduced’ to one of its parent folders by activating
the parent and right clicking the system stage folder. The pop-up menu will now
show the Reduce system stage branch option. Selecting that option will gather
the changes stored in the system stage folders, starting with the reduced folder
and walking up the database path to the activated parent folder. The gathered
changes are used to permanently change the parent design, after which the
whole database path between the reduced system stage folder and the changed
parent is deleted.

For more information, see

Working with Study Case Folders, section 6.0.9, page 6-98
Working with System Stage Folders, section 6.1.2, page 6-103
Reducing System Stage Folders, section 6.1.5, page 6-107

5.17.7 The Study Case Folder

A study case folder (IntCase, ) is meant to hold one or more references to
Grid and/or System stage folders. These referenced folders together define the
studied system configuration and will automatically be (de)activated when the
study case folder is (de)activated.

Without calculation case folders, it would be necessary to manually activate the

correct Grid and/or System stage folders over and over again in order to analyze
the resulting power system configuration.

A Study Case folder with a reference to at least one Grid or system Stage folder
has to be activated in order to enable calculations.

The Study Case Folder has an user defined name, an user defined owner, and
has a flag to define it as the default Study Case folder in the current directory.
When no Study Case folder is active when a Grid or System Stage is activated,
the default Study Case folder is activated too, in order to create the reference to
the Grid or System Stage folder. When no default Study Case folder is available,
a new one is created automatically.
Disabling the Use as default option will protect the contents of the Study Case
folder.
For more information, see
Working with Study Case Folders, section 6.1.2, page 6-103
Working with System Stage Folders, section 6.0.9, page 6-98

Handling of Power Factory 5-89

DIgSILENT PowerFactory The Database and the Data Manager

5.18 Special Objects in the Database

Most objects in the database are explained in special sections in this manual.
Information about the line object ElmLne, for instance, can be found in section
8.3.1, page 8-162.

Some additional objects are present in the database which are used in various
ways, and which cannot be related to a specific task or features. These objects
are described here.

5.18.1 The Matrix Object

The Matrix object defines a matrix. This object is e.g. used for the graphical
curve input or for use in DPL scripts.
See also section 26.9.3, page 26-540 for details about DPL methods.

Figure 5.37: The matrix page

The Matrix page, as depicted in Fig. 5.37 holds the table with the matrix values.
The row and column labels are normally defined on the ‘labels’ page but are
enumerated by default.

The matrix is resized by right clicking either a row label or a matrix cell. In both
cases, the context menu will show options for inserting, appending or deleting
cells.

• If a row label was right clicked, new rows will be inserted or deleted at the
clicked row position, or appended at the bottom of the matrix.

• If a matrix cell was right clicked, new columns will be inserted or deleted at
the clicked column position, or appended at the right side of the matrix.

Handling of Power Factory 5-90

DIgSILENT PowerFactory The Database and the Data Manager

Figure 5.38: The labels page

Labels for rows or columns are defined on the labels page, as depicted in Fig.
5.38. “Row labels” holds the labels for the rows, “Col labels” defines the labels
for columns. It is not required to define exactly as many labels as there are
columns or rows. It is allowed to enter empty labels, or to define more labels.

5.18.2 The Object Set

The object set is in fact nothing more than a special folder which holds
references to one or more object in the database. Object sets are used for many
tasks and calculations. because it is often needed to find a specific set amongst
a range of set definitions, each set is normally assigned to a special task. Such
an assignment is possible for

(n-1) outage simulation , to store a specific set of objects to put on outage.

Short-circuit calculations , to store multiple fault locations.

Outputs , to store objects which are reported in the output of results.

DPL Commands , to define the DPL ‘general selection’

SHC Sweep , to define the set of relays which are regarded in the short-circuit
sweep

General , to define arbitrary sets which will not be changed automatically.

Cable sizing , to store cables or cable types

The set assignment is used to create or redefine a set definition in the database
browser or in the single line graphic. This is done by selecting one or more
objects. Right clicking the selection will show the menu option Define or Add to.
These menu options will show a second menu with possible sets to define or to
which the selected objects may be added. The

Set definitions which are assigned to a specific task may be changed

automatically. To prevent the change of a set definition, the ‘Used for”
assignment must be set to ‘General’.

Handling of Power Factory 5-91

DIgSILENT PowerFactory The Database and the Data Manager

5.18.3 The Object Reference

The object reference is used to create object set definitions (SetSelect), or to
create an additional access to an object. References to objects are made visible
in the database manager by the small additional arrow in the object symbol.

The object reference is normally created automatically, for instance when objects
are added to a set, or when the option Paste Shortcut is used in the database
browser. If a reference is explicitly created, the ‘Reference’ pointer must be set
to a database object manually.

An object reference will behave as the referred object. Double clicking the
reference will open the referred object dialogue. Storing a reference to an object
in a DPL script will have the same result as storing the actual object. However, it
is not possible to use references to objects when setting object types. It is, for
example, not possible to select a reference to a line type in the line object
definition.

Handling of Power Factory 5-92

DIgSILENT PowerFactory Project Management

Chapter 6

Project Management

In order to study a network or system in PowerFactory a specific data structure

has been developed to organise and manage the large amounts of data that are
required for the simulation of the system.
Project and data management tools in PowerFactory are arranged to take
advantage of this data structure and thus the user is advised to keep to this
pre-determined data structure, at least at first until sufficient experience in using
PowerFactory is gained.
As may be inferred, the user is not limited to the pre-determined structure and
may create, within certain limits, their own project structure for advanced or
particular studies.
HeadBBasic Project Organisation and Management
The basic data structure is explained in 2.2 and the user should familiarise
themselves with this before continuing.

As will have been seen from this section electrical system data is split into
’Element’ and ’Type’ data that is kept in folders called ’Grid’ and ’Library’
respectively.

All of this data is in turn is housed in a folder that is termed the ’Project’ folder,
together with further folders that have specific purposes, the purpose of which
will now be explained.

In understanding the project structure it is well to examine what we might wish to

do with the simulated system, as this will direct us to what may be required to
realise these actions.

• We will want to be able to sort the network data, and this may be into
logical or organisational and/ or geographical areas. In PowerFactory this
is achieved by use of a Grid folder/s.

• Once the network data has been entered we will want to perform various
studies, for example, load flow, various short circuits, stability or EMT
based simulations, etc. It would be useful if the results of these studies
could also be stored for review or repeat later. Study Cases are used to do
this.

• We may need to analyse the network at different times during the day,
week or year, where different load conditions exist for these different times.

Handling of Power Factory 6-93

DIgSILENT PowerFactory Project Management

Here we perform parametric studies by adding Characteristics to various

parameters.

• In order to plan or assess the network in different switching configurations,

or where the network has been expanded or changed we would like to be
able to create variations of the network. In this case it would be useful if
these variations are linked to the original data so that changes made in the
original are transferred to the variation so that we do not need to do this
manually. The variations are achieved using what are known as System
Stages.

6.0.4 Creating a new Project

A new project is created by selecting File →New from the main menu. This will
open the ComNew dialogue, as shown in Fig. 6.1.

Figure 6.1: The ComNew dialogue

It will be noticed that this dialogue may also used to create several other new
objects. Ensure thus, that the ”Project” option has been selected in order to
create a new project. The target folder determines where the new project will be
created. Normally, and by default, this is the \U SER folder. The name of the new
project may be entered as the user desires.

By pressing E XECUTE , a new project folder will be created. A project should

contain at least one Grid and at least one Study Case folder. Thus, a second
dialogue will pop up to create such a Grid. This dialogue is shown in Fig. 6.2.
If we are satisfied with the the default name and frequency for the grid no further
action is needed (these may be edited at a later stage). When the OK is
pressed, the following will happen:

Handling of Power Factory 6-94

DIgSILENT PowerFactory Project Management

Figure 6.2: The Grid Edit dialogue

• The new Project folder will be created, together with a library folder for the
project (for type data).

• The new grid folder will be created in the project folder (for element data).

• A new Study Case will be created in the project folder.

• The project, the study case and the grid will be activated.

• The (empty) single line diagram of the grid will be opened.

An example of a newly created project is shown in Fig. 6.3.

Figure 6.3: A new project

The new project may later be expanded by creating extra grids or system stages,
study cases, library folders, graphic windows, etc.

6.0.5 The Project dialogue

New power system grid definitions or study cases can be created by right
clicking the project folder in a database manager, and selecting the New →Grid
or New →Study Case option.
The more convenient way is to select Edit →Project... on the main menu or to
double click the project folder in the database manager. This will open the
dialogue as shown in Fig. 6.4.

Handling of Power Factory 6-95

DIgSILENT PowerFactory Project Management

Figure 6.4: The project dialogue

Pressing the N EW G RID button will create a new grid and will open the grid
edit dialogue. A second dialogue will ask for the study case to which the new
grid folder will be added. The N EW S TUDY C ASE button will create a new
study case and will open its dialogue. The new study case will not be activated
automatically.

Each project also has a special folder which stores all changed settings. These
may be changed result box definitions, changed report definitions, special filters,
flexible page definitions, etc.

The project dialogue allows the user to configure the input data units manually,
or to import settings from an existing project, or to revert to the default settings,
by pressing the relevant buttons.

N OTE : The unit SI prefix settings may also be accessed and changed by dou-
ble clicking on the unit description to the right of the input field

6.0.6 Grids
Grids are data folders in which element data pertaining to a network is
stored. These grid folders also contain the single line diagrams which were used
to create the power system design. Additionally, each grid folder may contain a
tree of system stage folders for alternative design options (these are known as
system stages). There may be one or several of these grid folders in the project
folder ( ), and these may also be seen as areas.

The user may divide their network as desired into these folders, however, a
typical arrangement for a network would be as shown in 6.5. A schematic sketch
on the right shows the network layout, and on the left is the PowerFactory grid

Handling of Power Factory 6-96

DIgSILENT PowerFactory Project Management

arrangement:

Figure 6.5: Typical network arrangement

Grouping of the data in this fashion is advantageous as the user embarks on

more advanced studies, such as stability or EMT type simulations. In this type of
study the phenomena under study is often localised and irrelevant network data
may be excluded from the study in order to speed up the simulation.

6.0.7 Adding a new Grid

For reasonable small designs, the whole power system may be stored in one
grid folder. However, it is normal practice to divide a power system design into
several subsystems and to create and store each subsystem separately, as has
been shown in 6.5.

To add a grid folder to the current project, various methods may be employed:

1. Select the Edit-Project option on the main menu. This will open the
dialogue of the project that is currently active. Press the N EW G RID
button.

2. Right click the project folder in a database manager and select Edit. Press
the N EW G RID button.

3. Right click the project folder in a database manager and select New →Grid
from the menu.

Handling of Power Factory 6-97

DIgSILENT PowerFactory Project Management

In each case, the dialogue to create a new grid will appear, as shown in Fig. 6.2,
where the grid name, frequency and owner may be specified. A second dialogue
will appear after the OK button has been pressed, where the study case that
the grid will be linked to must be selected. Three options are presented:

1. Add the new Grid folder to the study case currently activated. This option is
of course only available when a study case is active.

2. Create and activate a new study case and add the new Grid folder

3. Add the new grid folder to an existing, but not yet active study case.

Normally, the second option is preferred because this creates a new study case,
dedicated to the new grid only (remembering that any network requires a source
in order for a load flow to function). In that way, the new grid may be tested
separately by load-flow or other calculations. To analyse the combination of two
or more grids, new study cases may be created later on, or the existing ones
may be altered.

6.0.8 Study Cases

The study cases in a project are used to define and activate certain parts and
alternatives of the power system design, on the one hand, and to initialise a set
of calculations commands.

The inclusion or exclusion of grids is determined by the Study Case .

In/excluding grids from a study case determines what data will be considered for
calculation.
Several study cases for the same grid, or combination of grids, may be set up.
Since the study case saves the settings applied to the calculation tools it (the
study case) may be used as a record of what calculation the user last performed.

To replay whatever was last calculated in a study case first activate the study
case (right click the study case →Activate) and then press the appropriate
calculation command button, for example, ”Calculate Short-Circuit.”
PowerFactory will repeat whatever calculation, with all the settings (such as
fault location, type, fault impedance, etc) was last performed in the study case.
Study cases may also be activated by simply choosing the required study case
from the drop down ”Current Study Case” window, found on the right side of the
upper tool bar.

6.0.9 Creating and Using a Study Case

The primary task of a study case is to activate and deactivate a calculation
target, which is a combination of Grids and/or System Stages. Activating or
deactivating the study case folder is done by either:

Handling of Power Factory 6-98

DIgSILENT PowerFactory Project Management

• Activating a project. This will automatically activate the study case that was
active at the moment the project was deactivated. Deactivating a project
will also deactivate the study case.

• Selecting a study case from the study case selection list on the main
menu, as shown in Fig. 6.6. All study cases in the active project are listed
in this list. Selecting the empty line will deactivate the current study case.

• Right-clicking a study case folder will show either the Activate or

Deactivate option. Activating a study case will automatically activate the
project if a project is not already active.

Only one study case may be active at the same time. The active study case will
therefore be automatically deactivated before another study case is activated.
This will mean that any active project will be deactivated should the selected
study case be in another project.

Figure 6.6: Selecting a study case

The three small folders in the icon of an study case are coloured red in the
database tree when a study case is active. All of the grids and/or system stage
folders are also coloured red.

Grids or system stages may be added to, or removed from, the study case by
right clicking them in the database tree and selecting Add to Study Case or
Remove from Study Case.

A Grid or System Stage cannot be separately activated; a Study Case ( )

linked to the Grid or System Stage must be activated. The context sensitive
menu will show a Activate option when a grid or system stage folder is right
clicked if no Study Case folder is active. This will present a prompt dialogue
which request that either an existing study case be activated, or a new study
case be created first. The grid or system stage is then activate in conjunction
with whichever choice is made.

An example study case [1] has two active system stages and one active grid [2].
The database tree, showing the active study case, grid and system stages is
shown in Fig. 6.7.
The grids/ system stages that are linked to a study case may be viewed by
pressing the G RIDS /S YSTEM S TAGES button of the Study Case dialogue,
which may be accessed by selecting Edit →Study Case in the main menu, or by

Handling of Power Factory 6-99

DIgSILENT PowerFactory Project Management

Figure 6.7: Example of an active study case

right clicking the study case in the data manager and selecting Edit. This is
shown in Fig. 6.8.

Figure 6.8: Contents of the example study case

The study case itself contains several calculation commands, and the special
”Summary Grid” object. The Summary Grid is an internal, automatically created
object, as are its contents, and inexperienced users should avoid editing it.

Handling of Power Factory 6-100

DIgSILENT PowerFactory Project Management

6.0.10 Adding a new Study Case

A project that contains more than one grid, which has several system stage
design alternatives, or which uses triggers and scales to model the various
conditions under which the system should operate, calls for many different study
cases.

A new study case can be added to the project by various means:

1. Select Edit →Project from the main menu, or by right clicking the project
folder →Edit in a database manager. This will open the dialogue of the
active project. Press N EW S TUDY C ASE .

2. By right clicking the project folder in a database manager and selecting

New →Study Case from the menu.

Figure 6.9: The study case dialogue

In all cases, the dialogue for defining a new study case will appear, as depicted
in Fig. 6.9 will appear.

It may be seen that, in the study case dialogue, the output (that is, calculated)
variable units may be specified for load flow and short circuit. Each study case
may have its own settings in this regard.

Handling of Power Factory 6-101

DIgSILENT PowerFactory Project Management

6.1 Advanced Project Management

6.1.1 Projects and System Stages

The design of a new part of a power system normally calls for the analysis of
different design alternatives. Such alternatives can be created as variants
(optional designs) from ’base’ case design using System Stages. These special
folders keep record of the differences between a base case and an alternative
design. Changes made to the base case ’filter’ down to the system stage so that
the system stage is kept up to date with changes made to the base case.
Changes made to the system stage are of course kept only to the system stage
itself. The user may also later ’reduce’ the system stage to the base case and so
upload the new design to create a new base case.

The PowerFactory system stage management system is strictly hierarchical.

The root of each system stage tree is always a grid folder. The grid folder
contains the base case design and may contain one or more system stages.
Each system stage may again contain one or more system stages. Hierarchical
trees of system stages may thus be created.

The System Stage folders will only keep a record of changes. No part of the
base case design is actually copied. When a parameter of a generator model is
changed, for example, only a reference to that generator and the new value of
the parameter will be stored. The next time the System Stage is activated, the
only change made to the generator is that the parameter is set to the alternative
value. All other parameters will be defined by the base case.
Changes made when the grid or any of system stages in the system stage trees
are active will reflect themselves in all system stages further down the system
stage tree. This principle is depicted in Fig. 6.10.

Figure 6.10: System stage hierarchy example diagram

In this figure, a base case is defined with three parameters: A, B and C. Three

Handling of Power Factory 6-102

DIgSILENT PowerFactory Project Management

System Stage folders are created in this base case and each of them changes
one or more of these parameters (depicted by the ’:=’ symbol). Two second level
system stages are visible. The right columns, pointed to by the arrows, give the
parameter values when the grid folder or the System Stage folder would be
activated. These values will be used in the various calculations.

The third case in Fig. 6.10 shows that the change in the first system stage
(A:=11) stays valid when the second level system stage is activated (A:=11,
B:=23). In the sixth case, a change of the first stage (B:=21) is overruled by the
second level stage (B:=23). The sixth system stage also changes the ‘C’
parameter. If this parameter is changed in the base case, it will thus reflect that
change in all system stages, except for the sixth one (columns A’, B’ and C’).

The System Stage folders thus implement a flexible, non-redundant, hierarchical

System Stage administration system.

N OTE : If all of this seems too complex to grasp initially simply keep the follow-
ing in mind:

• information flow is from the higher folder to the lower folder only
(picture an ’information diode’)

• changes made in a higher folder will only be ’inserted’ into the

lower folder if that object has not already been changed in the
lower folder - in this case the lower folder object is ’locked.’

6.1.2 Working with System Stage Folders

A new System Stage folder is created by right clicking a folder in the database
tree (usually a grid or system stage folder, but remember that system stages
may also be made of library folders, for example). The new option in the context
sensitive menu will open a second menu which has a System Stage option. By
selecting that option, a new, empty, system stage folder ( ) is created.

The system stage only needs a name and (optionally) an owner. It must of
course also be added to a study case in order to activate it. A system stage can
be added to the active study case by right clicking it and selecting Add to Study
Case. This will only be possible if none of its parents in the database tree is
already active.

If you are making a system stage of a grid you will be presented with a graphic
that looks exactly like that for the grid that you have made the system stage for.
You may now begin work and make the changes/ additions required for the
alternative system.

When a system stage folder is activated, it will ‘collects’ all objects from the

Handling of Power Factory 6-103

DIgSILENT PowerFactory Project Management

’parent folders’ (higher folders), up to the base case grid folder. The database
will thus be altered temporarily. When the system stage folder is deactivated, it
will return the collected objects to the original parent folders. See Fig. 6.11 and
Fig. 6.12.

Figure 6.11: Database before activation of a system stage folder

Figure 6.12: Database after activation of a system stage folder

All changes made to the collected objects while the system stage folder is active
will be registered by the system stage object. Each change will create a ’change
object’ which will hold all information necessary to restore the changed object to
its original base case state.

When a System Stage folder is deactivated, only the collected objects are
returned. The objects that were created while the system stage folder was active
will stay in the system stage folder. See Fig. 6.13

Handling of Power Factory 6-104

DIgSILENT PowerFactory Project Management

Figure 6.13: Database after deactivation of a system stage folder, with added
object

Deletions of objects will also be registered. An object deleted while a system

stage was active will be returned to the original parent folder. The delete action
will be stored in the system stage folder, and the object will again be
(temporarily) deleted the next time the System Stage folder is activated.

Because the single line graphics are an integral part of the power system
designs which they represent, and because they are stored in the grid folder,
they will also be collected by the System Stage folders when these are activated.
This means that all changes made to the single line graphics will also be
automatically registered by the system stage folder.

6.1.3 Adding a new System Stage/ Revision

It is also possible to create system stages for all of the grids/ system stages that
are associated with a study case, in one go. Right click a study case and choose
New →Revision. You will be asked for a name for the new study case, and then
a name for the system stage.

PowerFactory will create system stages of all the grids that are associated with
the original study case. All of these system stages will have the same name and
will be associated with the new study case.

6.1.4 Remote Variants

Normally, the grids, system stages and study cases are all stored in the same
project. However, in some cases it becomes necessary to use grids and/or
system stages that belong to different projects.

Handling of Power Factory 6-105

DIgSILENT PowerFactory Project Management

This may happen when a user wishes to use data that is not ’owned’ by the user
themselves. An example are the example projects that are shipped with each
PowerFactory installation. These are normally only accessible when one is
logged in as a demo user, or if you copy a project to your user folder. Quicker
and easier than copying is to simply add the grids that you wish to work with to a
project that you have created in your own user folder; these grids are then added
as ’remote system stages.’

Another example is when calculations have to be performed in a multi-user

environment. In this case the power system may be broken up into several
sub-systems, each of which may be the responsibility of different users. When
the projects in which the sub-grids reside are shared amongst those users, each
of them will be able to see these projects folders in the user folders of the other
users, in the same way as each of them can see the projects defined in the
demo user folder. The grids in these shared projects may now be added to a
calculation case by creating remote variants of the shared grids.

A remote variant is created by activating a project and a study case as normal.

Only projects and study cases that are owned by the current user may be
activated. The active calculation target may now be changed by adding or
removing grids and/or system stages. A remote variant is created automatically
in the active project as soon as a grid or system stage from another project is
added. In the example of Fig. 6.14, the user ‘User’ has activated its project and
has added its own ‘Grid’ to the Study Case. Additionally, the remote grid from
‘Other User’ has been added to the active project belonging to ’User.’ This has
led to the creation of the ‘Remote Variant’ system stage in the ’User’ project
folder.

Figure 6.14: Example of a remote variant

A study case with remote variants acts like a normal study case. All calculations
will address all of the objects in the remote variant, as if they were local objects.
The remote design is protected against changes by the fact that the remote

Handling of Power Factory 6-106

DIgSILENT PowerFactory Project Management

variant is a normal system stage. All changes made in the remote grid will
therefore be removed as soon as the remote variant is deactivated.

6.1.5 Reducing a System Stage

The sophisticated project management system may be used to create a base
case design with a non-redundant, hierarchical tree of alternative design
variants. These design variants are stored in system stage folders.

One or more design variants can be created and used to analyse different
design options. After such analyses, one of these options may be selected and
used to permanently change the design. This is done by reducing the
corresponding system stage folder to a ‘target’ folder, which may be the base
case design folder or a system stage folder higher up in the hierarchical tree.

A system stage is reduced to one of its parent folders by first activating the
parent and subsequently right clicking the system stage to be reduced. The
pop-up menu will show Reduce System Stage Branch.

Reducing a system stage to higher level target folder is straight forward when it
is the only variant for that target folder. The reduction method becomes more
complex when a system stage is reduced to a level which has other system
stages parallel to the reduced system stage. Because the system stage
administration system is non-redundant, conflicts may arise as the parallel
system stages suddenly see their base case design changed after the reduction.

The PowerFactory variant administration system uses an intelligent reduction

algorithm which will reduce the complete system stage branch containing all
system stages between the one which is to be reduced and the target folder. All
system stage trees connected to that branch will be moved down the hierarchical
tree to the target folder.

The reduction principle is illustrated in Fig. 6.15. The original design variant tree
is shown on the left side. The system stage folder that is to be reduced is called
‘TO REDUCE’. All system stage folders which are to be reduced, because they
are part of the path up to the target folder are boxed. The branch to be reduced
is drawn in thick lines.
The reduced tree is shown on the right. All branches and system stage folders
connected to the reduced branch are transferred to the target folder, which in
this example is the base case ‘Grid’ folder.

6.1.6 Comparing Projects

In some stages of a system design study, more than one project version may
have been created. Such may be the case when several people are working on
the projects, but whom are all working on a stand-alone version of

Handling of Power Factory 6-107

DIgSILENT PowerFactory Project Management

Figure 6.15: Reducing a System Stage

PowerFactory. A typical example arises when people are working on the

projects on laptops while travelling. It is then necessary to update the original
project with an altered project version.

PowerFactory provides a special command object to compare projects. With

this command, it is also possible to create system stages in the original project
which contain all modifications made in the altered project.

Aside from updating a project using an altered version, the comparison

command is also used to create a single project with trees of system stages from
imported data. If such data is created by other programs, the import of different
project alternatives may result in separate redundant projects. By comparing the
‘base case’ project to the alternative projects, one by one, a single ‘base case’
project may be created, with non-redundant trees of system stages.

Figure 6.16: Comparing projects

Handling of Power Factory 6-108

DIgSILENT PowerFactory Project Management

The base project may contain system stages of its own, but as it is only possible
to activate one project, it is only possible to compare the non-active base with
the active project. This important, as the state of the project to compare to may
depend on the active study case. The base project will be compared to the
active project as it currently looks in its active state.

The compare command has the following options.

Difference Report only...: Reports missing objects in one or the other project,
or objects that have different data. Disabling this option will create system
stages in the base project.

Report additional cubicles: Reports any additional cubicles found in either of

the two projects.

Suppress output messages while comparing: Differences found during the

comparison are not shown.

Ignore cubicle names: Ignores the names of cubicles and will only search for
comparable connections to busbars and terminals.

Copy Graphics: copies graphics only from the compared project to the Base
Project.

Handling of Power Factory 6-109

DIgSILENT PowerFactory Graphic Windows

Chapter 7

Graphic Windows

7.1 Introduction- the Basics

Many commands and tools are available to edit and manipulate symbols in the
graphics. The underlying data objects may also be accessed and edited from
this point, and calculation results may be displayed and configured.

Many of these tools and commands are found in the drop down menus or as
buttons in the toolbars, but by far the most convenient manner of accessing the
tools is to use the right mouse button to display a menu. This menu is known as
a context sensitive menu; in other words, PowerFactory evaluates where the tip
of your cursor is, and then presents a menu that is appropriate to the cursor
location. Thus cursor position is important when selecting various menu options.
It is similarly important to keep the cursor in place when right clicking, as the
menu presented is determined from cursor position primarily, and not from the
selected or marked object.

7.2 Active Graphics, Graphics Board and Study

Cases

The graphics that are displayed in an active project are determined by the active
study case. Four types of graphic objects are used in PowerFactory:

• Single Line Diagrams for entering power grid definitions and for showing
calculation results

• Station Diagrams for showing station topologies and calculation results

• Block Diagrams for designing logic (controller) circuits and relays

• Virtual Instrument Pages for designing (bar) graphs, e.g. for the results of a
stability calculation, bitmaps, value boxes, etc.

(Block Diagram Graphics are explained in the advanced user’s manual).

Handling of Power Factory 7-110

DIgSILENT PowerFactory Graphic Windows

The study case folder contains a folder called the ”Graphics Board” folder
(SetDesktop) in which references to the graphics to be displayed are contained.
This folder, much like the ”Summary Grid” folder, is automatically created and
maintained and should generally not be edited by the user.

Similarly, the grid folder contains a sub-folder called the ”Graphic” folder
(’IntGrfnet’). This sub-folder should generally also not be edited by the user as it
is automatically created and maintained.

More than one graphic (single line diagram) may be created in/ for a grid, either
to display the different grid elements over several pages, or to display the same
grid elements in different graphical arrangements. Consider the ’Simple Power
System’ project that is shown in Fig. 7.1. The active study case is called ’Alt
Study Case’ [1] and the active grid has two single line graphics that have been
created for it, ’Grid’ and ’Alt Grid View’ [2]. The graphics board folder in the study
case has a reference to only the ’Alt Grid View’ graphic object [3] and thus only
this graphic for the grid will be shown when the study case is activated.

Figure 7.1: Relationship between the study case, graphics board and single line
diagrams

The references in the graphics board folder are created when the user adds a
grid to a study case. PowerFactory will ask the user which graphics of the grid
should be displayed. At any time later the user may display other graphics in the
grid by right clicking the grid →Show Graphic. Graphics may be removed by right
clicking the tab at the bottom of the page and right clicking →Remove Page(s).

The study case and graphics board folder will also contain references to any
other graphics that have been created when the study case is active.

Handling of Power Factory 7-111

DIgSILENT PowerFactory Graphic Windows

7.3 Single Line Graphics and Data Objects

One of the powerful features that PowerFactory has is the strong linkage
between the graphical representations and the data objects, where there is not a
1:1 relation between data objects and graphic symbols (where one data object
would mean only one graphical symbol). The key is in the references that are
used: a graphic symbol uses a reference to a data object and a data object may
thus appear in more than one graphic. Because the references are complete
(path and name), graphics may be moved and copied around, independent of
the data objects they refer to. The data objects on the other hand may also be
moved around freely, as the references to these objects are also automatically
updated. The linkage between graphic symbols and data objects is best
described as a ’rubber band’ relation, binding the two together without locking
them into place.

The graphics themselves are saved in the database tree, normally in the same
folder as the power grids to which they belong. This makes finding the correct
Single Line graphic representation of a particular grid, even in the case where
there are several graphic representations for one grid, easy.

Three of the four graphic classes may be used to create new objects. These are
the Single Line Diagram, the Block Diagram and the Virtual Instrument Page.
These are the main tools used to design new power systems, controller block
diagrams, or to design graphs and other virtual instruments that display results.
The fourth graphic class, the Station Graphics, is not used to define new objects,
but only to show stations and calculation results.

When the drawing tools are used to create a new graphical symbol (i.e. a line,
transformer, bar graph, etc.) a new data object is also created in the database
tree. A Single Line Graphic object therefore has a reference to a Grid folder. The
new data objects are stored into the ‘target’ folders that the graphics page is
associated with (this information may be determined by right clicking the graphic
→Graphic Options see 7.7.1 for more information.

Since data objects may have more than one graphic representation the deletion
of a graphic object should not mean that the data object will also be deleted.
Hence the user may choose to delete only the graphical object (right click menu
→Delete Graphical Object only. When a graphic object is deleted the user is
warned that the data object will not be deleted.

This suggests that a user may delete all graphical objects related to a data
object, with the data object still residing in the database and being considered for
calculation. This is indeed what will occur, and may even be done deliberately in
some cases.

When an element is deleted completely (right menu option →Delete Element) is

Handling of Power Factory 7-112

DIgSILENT PowerFactory Graphic Windows

used a warning message will confirm the action. This warning may be switched
off - see User Settings, General, ”Always confirm deletion of Grid Data”).

7.3.1 Editing and Selecting Objects

Once elements have been drawn on the graphic the data for the element may be
viewed and edited by either double clicking the graphic symbol under
consideration, or by right clicking it →Edit Data.

The option Edit and Browse Data will show the element in a data manager
environment. The object itself will be selected (highlighted) in the data manager
and can be double clicked to open the edit dialogue. A new data manager will be
opened if no data manager is presently active. If more than one symbol was
selected when the edit data option was selected, a data browser will pop up
listing the selected objects. The edit dialogues for each element may be opened
from this data browser one by one, or the selected objects can be edited in the
data browser directly (see Editing Data Objects, sec. 5.7, page 5-57).

Finding specific elements in a large project may be difficult if one had to look
through the single line diagram alone, thus PowerFactory has tools to assist the
user in finding elements in the graphic.

As will have been seen in the section 5.6 objects in the data manager may be
sorted in a number of ways. Once you have identified the object/ element you
are searching for it may be right clicked →Mark in Graphic. When performing
this command ensure that you select the object itself, as shown in Fig. 7.2. The
menu will be different to that seen when you select an individual field, as shown
in Fig. 7.3.
The position of an object in the database tree can be found by:

• Opening the edit dialogue. The full path is shown in the header of the
dialogue

• Right-clicking the object and selecting Edit and Browse. This will open a
new database browser when required, and will focus on the selected
object.

7.3.2 The Page Tab

The page tab of the graphic window displays the name of the graphics in the
graphics board. The sequence of the graphics in the graphics board may be
changed by the user. A page tab is clicked and moved by dragging and
dropping. An arrow marks the insert position during drag and drop. Another way
to change the order of the graphics is to select the option ”Move/Copy Page(s)”
of the context sensitive menu. In addition virtual instrument panels can be
copied very easily. To do so the C TRL key is pressed during drag and drop. The

Handling of Power Factory 7-113

DIgSILENT PowerFactory Graphic Windows

Figure 7.2: Selecting an object correctly

Figure 7.3: Selecting an object incorrectly

button copies a virtual instrument panel and inserts the copy alongside the
original panel.

Handling of Power Factory 7-114

DIgSILENT PowerFactory Graphic Windows

The Page Tab Menu

The page tab menu is accessed by a right click on the page tab of the graphic
windows. The following commands are found:
• Insert Page →Create New Page creates a new page (the button in the
toolbar will do the same).

• Insert Page →Open Existing Page opens a page or graphic that has
already been created but which is not yet displayed (the button in the
toolbar will do the same).

• Rename Page presents a dialogue to change the name of the graphic.

• Move/Copy Page(s) displays a dialogue to move or copy the selected page.

Copy is available only for virtual instrument panels.

7.3.3 New Graphic Window

A new graphics window can be created using the New command dialogue. This
dialogue may be opened:

• by pressing the button.

• by selecting the File →New item on the main menu

• by pressing the keyboard shortcut C TRL -N

The ComNew dialogue must be configured to create the desired new object and
the new object should be named. Ensure that the correct target folder for the
new object is selected.

Objects that may be created using this dialogue are:

Project Creates a new Project folder and another dialogue pops up to define a
Grid folder in the Project folder. Finally the Graphic page in which the
single line diagram may be drawn will appear.

Grid Creates a new Grid folder and a new Single Line Graphic object in that
folder. The (empty) single line graphic will pop up.

Block Diagram Creates a new Block Diagram folder in the selected folder and a
new Block Diagram Graphic object. The (empty) block diagram graphic will
pop up.

Virtual Instrument Panel Creates a new Virtual Instrument Page object. The
(empty) Virtual Instrument Page will pop up.

Single Line Graphic Creates a Single Line Graphic in the target folder. Before
the graphic can be created the Current Net Data pointer must be set (that
is, the relevant grid folder must be selected).

Handling of Power Factory 7-115

DIgSILENT PowerFactory Graphic Windows

The Target Folder will be set to the \U SER folder by default, but may be changed
to any folder in the database tree. The new Grid, Block Diagram or Virtual
Instruments folder will be created in the Target Folder.

In all cases, a new graphics board object is also created, because graphic pages
can only be shown as a page in a graphics board. An exception is the creation of
a new page, while in a graphics board. This can be done by pressing the
button on the graphics board toolbar. This will add the new graphics page to the
existing graphics board.

7.4 Building from Predefined Objects

Designing new (extensions to) power system grids, is preferably done

graphically. This means that the new power system objects should be created in
a graphical environment. After the new components are added to the design,
they are edited, either from the graphical environment itself (by double clicking
the objects), or by opening a database manager and using its editing facilities.

It is however possible, and sometimes even necessary, to work the other way
around. In that case, new data objects are first created and edited in the
database manager, or imported from other programs, and subsequently used in
one or more single line diagrams.

PowerFactory allows for this either by drag and drop facilities to drag power
system objects from the data manager to a graphic window, or by the ”Draw
Existing Net Elements” tool. The way this is done is as follows:
1. Select from the drawing tools toolbox the kind of object that is to be drawn
in the graphic.
2. Enable the drag & drop feature in the data manager by double clicking the
drag & drop message in the message bar.
3. Select the data object in the data manager by left clicking the object icon.
4. Hold down the left mouse button and move the mouse to the graphic
drawing area (drag it).
5. Position the graphical symbol in the same way as is done normally.
6. A new graphical symbol is created, the topological data is changed, but the
graphical symbol will refer to the dragged data object. No new data object
is created.
Dragging objects in this manner is supported, however, it is easier to use the
”Draw Existing Net Elements” tool to perform this action, as described in the next
section.

Handling of Power Factory 7-116

DIgSILENT PowerFactory Graphic Windows

7.4.1 Building Single line Diagram from Imported Data

When a power system design is imported from another program, only the
non-graphical information is regarded (only some of the converters that are
provided in PowerFactory will also import graphics files). Although this includes
the connection data in the form of ‘from-to’ data fields, the graphical single line
diagrams are usually not be imported. After the import, a new single line
diagram may be built using the imported database information (note that this
does not mean that the user will not be able to perform load flows and other
calculations immediately after import; this may be done).

This is done by first creating a new single line graphic folder, preferably in the
grid folder that contains the imported power system (right click the grid folder
→New →Graphic). This opens the single line graphic dialogue, where the
’Current Net Data’ pointer has should be set to the respective grid folder. See
section 7.7.1, page 7-129, for more information.

As soon as the correct folder has been set, and OK has been pressed, the
single line graphic folder ( ) is created and a blank graphic page,
appropriately named, pops up. The D RAW E XISTING N ET E LEMENTS ( )
button on the graphics toolbar may now be pressed. This opens a database
browser [1] listing all elements considered by the active study case (see Fig. 7.4)
and which have not yet been inserted into the new single line graphic.

This list may be filtered to show only particular grids or all grids by using the drop
down window [2] provided. Once a drawing tool is chosen, in this case the
Terminal tool [3], the list is further filtered to show only terminals, as can be seen
in the example. When the user now clicks on the graphic the highlighted terminal
[5](in the browser) will be removed from the list and placed onto the graphic, and
the next terminal down will be highlighted, ready for placement. In the example
two terminals have already been placed [4] in the graphic.
After all busbars have been inserted into the single line graphic, another branch
and edge elements may be selected in the graphic toolbox. In Fig. 7.5, the
2-winding transformer tool has been selected [1]. The database browser will now
show all 2-winding transformers which have not been inserted into the graphics
[2]. When one of these transformers is selected [3] in the browser, the
corresponding two busbars will be highlighted in the single line graphic [4]. The
insertion point and connections for the transformer is thus clear. This is also why
the nodes should first be placed on the graphic. Edge (lines, transformers) and
branch (loads, machines, etc) elements are placed once the nodes are in
position.

Handling of Power Factory 7-117

DIgSILENT PowerFactory Graphic Windows

Figure 7.4: Using the Draw Net Elements tool

N OTE : Before placing elements onto the graphic users may find it useful to
configure and display a background layer. This will be a bitmap of an
existing single line diagram of the system. It may be used to ’trace’
over so that the PowerFactory network looks the same as current
paper depictions; see 7.6 for more information on layers

Drawing line routes may be done in two ways:

• Connect the parent line first (this is the original line from which the line
routes were created; it is marked by the symbol ). In this case all
terminals and routes that belong to this parent line will automatically be
drawn. You may then move the terminals along the parent line. If the
terminal is selected and moved it may only be moved along the line itself,
however, if you wish to move the terminal to another point, and thus have
the line routes move as well then hold the C TRL and A LT keys down at the
same time and then move the terminal.

• First insert the terminals that lie between routes. Then the routes can be
added as usual.

More about how to draw busbars, 2-winding transformers, etc. is explained in the
following sections.

Handling of Power Factory 7-118

DIgSILENT PowerFactory Graphic Windows

Figure 7.5: Placing a transformer

7.5 Using the Graphic Windows

Each of the four graphic window types are edited and used in much the same
way. This section gives a description of what is common to all graphic windows.
Specific behaviour and functionality of the graphic windows themselves is
described in separate sections.

The single line graphic operates in a ’freeze’ and ’unfreeze’ mode. In freeze
mode the graphics may not be edited or changed and elements may not be
added or deleted. The freeze mode is controlled by the toggle button . The
freeze mode also affects the context sensitive menus and presents different
menus for each mode.

7.5.1 The Drawing Toolboxes

Each graphics window has a specific Drawing Tool Box. This toolbox has buttons
for new network symbols and for non-network symbols. See Fig. 7.6 for two
examples.

Handling of Power Factory 7-119

DIgSILENT PowerFactory Graphic Windows

Figure 7.6: Two tool boxes: left for Grids, right for Blocks

The toolboxes have

• Network or block diagram symbols, which are linked to a database object:

busbars, lines, transformers, switches, adders, multipliers, etc.

• Graphical add-on symbols: text, polygons, rectangles, circles, etc. (see “1”
in Fig. 7.6)

• The “Graphic Cursor” ( ) which is mainly used to select graphical

objects in order to change their appearance (see “2” in Fig. 7.6)

The toolboxes are only visible when the graphics freeze mode is off. The
graphics freeze mode is turned on and off with the button (found at the left
had side of the lower tool bar).

7.5.2 Adding New Power System Elements

Note that this may only be done when the graphic is not in freeze mode. To
create a new power system element, select the corresponding button in the
toolbox. As the cursor is positioned over the drawing surface, it will have a
symbol of the selected tool ’attached’ to it, showing that the cursor is, for
example, in ’Terminal’ drawing mode (to reset the mode either press the cursor
button at the bottom of the toolbox or right click). Power system elements are
placed and connected in the single line graphic by left clicking on empty places
on the drawing surface (places a symbol), and by left clicking busbars (makes a
connection). This is described in more detail later in this section. If you wish to
stop the drawing and connecting process press the E SCAPE key.

Handling of Power Factory 7-120

DIgSILENT PowerFactory Graphic Windows

There are basically three ways of positioning and connecting new power system
elements:

1. By left clicking on one or more nodes to connect and position the element
directly. Single port objects (loads, machines) will be positioned directly
beneath the nodes at a default distance (the symbol can later be moved if
required). Double or triple port objects (transformers) will be centered
between the first two busbar connections automatically. This ’single click
method’ will only work if the option Place Branch Objects With One
Connection Automatically in the User Settings is enabled.

2. By first left clicking on an empty place to position the symbol and then left
clicking a node to make the connections.

3. By first left clicking on an empty place, consequently clicking on the

drawing surface to define a non-straight connection line and finally clicking
on a busbar to make the connection.

Fig. 7.7 shows an example of a generator placed according to the first method
(left generator), one placed according to the second method (middle generator),
and one placed according to the third method (right generator with long
connection).

Figure 7.7: Three graphical objects

If a load or machine is connected to a busbar using the first method (single left
click on busbar), but a cubicle already exists at that position on the busbar, the
load or machine symbol will be automatically positioned on the other side of the
busbar, if possible.

All power system elements are positioned ’bottom down’ by default. However, if
the C TRL-key is pressed when the graphic symbol is positioned onto the drawing
surface, it will be positioned either turned 90 degrees (busbars and terminals) or
180 degrees (loads, machines). A node placed using the C TRL-key will be
placed vertically, and a load thus connected to a node will be positioned above
the node (in case of a horizontal busbar/ terminal), or to the left (vertical busbar/
terminal), instead of beneath or to the right. If the element has already been
placed and the user wishes to flip the element to the other side of the busbar/

Handling of Power Factory 7-121

DIgSILENT PowerFactory Graphic Windows

terminal then right click the element →Flip At Busbar. If you wish to first place a
symbol and then rotate or mirror it then click on the graphic to place the symbol
and then press the TAB key on the keyboard. This will ’jump’ the ’rubber band’ to
the next connection point (or port) of the element. Continual pressing of the TAB
key will leave the symbol placed on the graphic (and the data element in the
database, without being connected. Manipulate the symbol as required and then
right click it →Connect Element.

If the element has already been connected it must first be disconnected in order
to rotate or mirror it (right click the symbol →Disconnect Element. Fig. 7.8 shows
an example of rotated and flipped power system elements.

Figure 7.8: Flipped and rotated power system elements

7.5.3 Marking Power System Elements

To mark (select) a power system element click on it with the cursor. The element
is then highlighted and becomes the ’focus’ of the next action or command. The
element can be un-marked or de-selected by clicking on another element or by
clicking onto some free space in the graphic.

Figure 7.9: Marking/ Selecting elements

Astute users may notice that the element is highlighted using a different pattern,
depending on whether the graphic has been frozen or not, as seen in Fig. 7.9,
where [1] is the when the freeze mode is engaged and [2] when ’un-frozen.’

There are different ways to mark several objects at once:

Handling of Power Factory 7-122

DIgSILENT PowerFactory Graphic Windows

• To mark all graphical elements, press the ”All”-button ( ). The keyboard

short cut C TRL +A may also be used.

• To mark a set of elements at the same time click on a free spot in the
drawing area, hold down the mouse key and move the cursor to another
place where you release the mouse button. All elements in the so defined
rectangle will now be marked. A setting, found in the ”User Settings”
dialogue under the ”Graphic Windows” tab (on the second page of this tab
→press the button), can alter the manner in which objects are marked
using this marking method, as either ”Partial” or ”Complete”. ”Complete”
means that the whole object you want marked must lie inside the rectangle.

• To mark more than one object, hold down the C TRL key whilst marking the
object.

• Clicking once on an element belonging to a multiple busbar system will

only mark the chosen object. When you click on this object again all
elements that belong to this section will be marked. A third click on this
object will mark the whole busbar system.

• When clicking on an element and clicking on this element a second time

whilst holding down the A LT key will also mark all the elements connected
to the first element.

• If the C TRL and A LT key are pressed simultaneously whilst moving and
element then elements connected to it will also be moved.

7.6 Graphic Layers

The single line graphic and the Block diagram graphic windows use transparent
layers of drawing sheets on which the graphical symbols are placed. Each of
these layers may be set to be visible or not. The names of objects that have
been drawn, for example, are on a layer called ”Object Names” and may be
made visible or invisible to the user.

Which layers are visible and exactly what is shown on a layer is defined in the
”Graphical Layers” dialogue. This dialogue can be opened by pressing the
button on the local toolbar, or by right clicking on an empty spot of the graphic
area →Show Layer. The layers dialogue has a ”Visibility” tab to determine which
layers will be visible, and a ”Configuration” tab to define various attributes for the
layers. See Fig. 7.10.
In this figure, the three layers in the left pane (Base Level, Object Names,
Results) are visible in the graphical window. The six layers in the right pane are

Handling of Power Factory 7-123

DIgSILENT PowerFactory Graphic Windows

Figure 7.10: ”Graphical Layers” dialogue

invisible. Layers can be made visible by multi selecting them (hold the C TRL key
down whilst selecting) and pressing the button (alternatively, double click a
layer name and it will jump to the other pane). In the figure, the ”Tap Positions”
layer is about to be moved to the left (”Visible”) pane. A layer can be made
invisible again by selecting it in the left pane and pressing the button or by
double clicking it. You can also define, edit and delete your own layers and by
pressing the ”New” button.

Each graphic symbol in a single line diagram or block diagram is assigned to

default layer at first. All busbar symbols, for example, are drawn on the ”Base
Level” layer by default. Graphic symbols may be shifted onto other layers by
selecting them in the single line graphic right clicking. The context menu will now
offer the option Shift to Layer. This option will show a second menu with all
layers. Selecting a layer will move all selected symbols to that layer. Moving
symbols from one layer to another is normally only needed when only a few
symbols from a certain group should be made visible (for instance the result
boxes of one or two specific point-terminals), or when user defined layers are
used.

N OTE : Certain names and results boxes are, by default, assigned to the ”In-
visible Objects” layer. An example are the names and results boxes
for point terminals. This is done to unclutter the graphic. Should the
user wish to display names and/or results boxes for certain point ter-
minals simply make the ”Invisible Objects” layer visible and re-assign
the names and results boxes required to another layer, such as the
”Object Names” or ”Results” layers - then make the ”Invisible Objects”
layer invisible once more.

The ”Configuration” tab has a drop down list showing all layers that may be
configured by the user. Considering the ”Object Names” layer [1], as shown in
Fig. 7.11, it may be seen that a target or focus may be set [2]. This means that,
whatever has been selected as the target, will be the focus of the action that is
commanded. Various actions or settings may be performed, such as changing

Handling of Power Factory 7-124

DIgSILENT PowerFactory Graphic Windows

the font [3]. The configuration tab may also be used to mark (select/ highlight)
the target objects in the graphic using the M ARK button [4].

Figure 7.11: Graphical layers configuration page

As and example, suppose that a part of the single line graphics is to be changed,
for instance, to allow for longer busbar names. To change the settings, the
correct graphical layer is first selected. In this example, it will be the ”Object
Names” layer. In this layer, only the busbar names are to be changed, and the
target must therefore be set to ”All Nodes”. When the layer and the target has
been selected, the width for object names may be set in the Settings area. The
number of columns may be set using the V ISIBILITY /F RAME /W IDTH button.
Alternatively, the A DAPT W IDTH will adapt all of the object name placeholders
to the length of the name for each object.

Changing a setting for all nodes or all branches at once will overwrite the present
settings.

N OTE : Should an object disappear when it has been re-assigned to a layer,

that layer may be invisible. Layer visibility should be inspected and
changed if required

7.7 Graphic Commands, Options and Settings

7.7.1 All Graphic Windows

The following basic options are available in all graphic windows.

Handling of Power Factory 7-125

DIgSILENT PowerFactory Graphic Windows

Zooming
Zoom In Button :

Zoom Out Button :

Zoom All Button :

Press the button; the cursor changes to show a magnifying glass; the area to be
zoomed into must be selected. This is done by dragging a rectangle around the
area to be zoomed →picture the area to be zoomed and left click in the top right
hand corner of an imaginary rectangle framing the area [1] as shown in Fig.
7.12. Keep the mouse button held down and drag the cursor down and to the
right [2]. A frame is drawn as you do this; when the frame encompasses the area
you wish to zoom into let the mouse button go.

Figure 7.12: Using the mouse to ’drag’ a selection or zoom area

To zoom ’back’ press the ”Zoom Out” button - this will step the zoom back to the
last state.

To view the entire page press the ”Zoom All” button (100 percent zoom).

Handling of Power Factory 7-126

DIgSILENT PowerFactory Graphic Windows

N OTE : you can also type a zoom percentage directly into the ”Zoom Level”
window or use the drop down list to zoom

Print Graphic
Main Menu : File →Print

Keyboard : C TRL + P

Button :

This function will send the graphic to a printer. A printer dialogue will appear first.

N OTE : The function, Page Setup (accessible via main menu path File →Page
Setup), allow a subsize for printing to be set. This will, for example,
print an A3 graphic across two A4 pages. Special paper sizes or un-
usual printer insertion points may be entered as well by using the mar-
gins of the print-out. These margins have to be set with care as the
print-out will be stretched to the frame. If this remaining page frame
has a X/Y - ratio other than 0.707 (A3, A4), the drawing will be dis-
torted.

Rebuild
Right Click Drawing : Rebuild

Button :

The drawing may not be updated correctly in some circumstances. The rebuild
function updates the currently visible page by updating the drawing from the
database.

Insert New Page

Page Tab Menu : Insert Page →Create New Page

Button :

(The page tab menu is opened by right-clicking the page tabs)

Inserts a new graphic object into the ”Graphic Board” folder of the active study
case and presents a blank graphics page to the user. A dialogue to configure the
new graphics object will appear first.

Handling of Power Factory 7-127

DIgSILENT PowerFactory Graphic Windows

Insert Existing Page

Page Tab Menu : Insert Page →Open Existing Page

Button :

(The page tab menu is opened by right-clicking the page tabs)

Inserts existing graphics, which may be one of the following:

• Graphic folder object (IntGrfnet, ) →opens the selected graphic

• Station (ElmStat, ) →opens the station graphic of the selected station

(this may also be accessed by right clicking the station in a Data Manager,
or a busbar on the single line graphic →Show Station Graphic

• Terminal (ElmTerm, ) →opens the station graphic of the selected

terminal (this may also be accessed by right clicking the terminal in a Data
Manager, or a terminal on the single line graphic →Show Station Graphic

• Block Definition (BlkDef, ) →The graphic of the block definition is

opened. If there is no graphic defined for the block definitions the
command is not executed.

• Virtual Instrument Panels (SetVipage) →A copy of the selected virtual

instrument panel is created and displayed.

Graphic folder objects (IntGrfnet) may be opened in more than one Graphics
Board at the same time, even more than once in the same Graphics Board.
Changes made to a graphic will show themselves on all pages on which the
graphic object is displayed.

Remove Page
Page Tab Menu : Remove Page

(The page tab menu is opened by right-clicking the page tabs)

This function will remove the selected graphic from the Graphics Board. The
graphic itself will not be deleted and can be re-inserted to the current or any
other Graphics Board at any time.

Rename Page
Page Tab Menu : Rename Page

(The page tab menu is opened by right-clicking the page tabs)

This function will pop up a dialogue to change the name of the selected graphic.

Handling of Power Factory 7-128

DIgSILENT PowerFactory Graphic Windows

Graphic Options
Right Click Drawing : Graphic Options

Button :

Each graphic window has its own settings, which may be changed using the
graphic options function. This function presents a dialogue for the following
settings. See Fig. 7.13.

Figure 7.13: Graphic Options Editor

Basic Attributes tab:

Name The name of the graphic

Current Net Data The reference to the database folder in which new power
system elements created in this graphic will be stored.

Snap snaps the mouse onto the drawing raster.

Grid shows the drawing raster using small points.

Freeze switches on the freeze mode

Ortho-Type defines if and how non-orthogonal lines are permitted:

Ortho-Off Connections will be drawn exactly as their line points were set.
Ortho Allow only right-angle connections between objects.

Handling of Power Factory 7-129

DIgSILENT PowerFactory Graphic Windows

Semi-Ortho The first segment of a connection that leads away from a busbar or
terminal will always be drawn orthogonally.
Line Style for Cables is used to select a line style for all cables
Line Style for Overhead Lines is used to select a line style for all overhead
lines
Offset Factor for Branch Symbols defines the length of the connection when
a branch symbol is drawn by clicking on the busbar/terminal. This is the
default distance from the busbar/terminal in grid points.
Show Bus Couplers can be used to see all couplers, or to hide them
Allow Individual Line Style permits the line style to be set for individual lines.
The individual style may be set for any line in the graphic by right clicking
the line →Set Individual Line Style. This may also be performed for a group
of selected lines/cables in one action, by first multi selecting the elements.
Allow Individual Line Width as for the individual line style, but may be used in
combination with the ”Line Style for Cables/Overhead Lines” option. The
individual width is defined by selecting the corresponding option in the right
mouse menu (may also be performed for a group of selected lines/cables
in one action).
Equidistant Insertion of Terminals on Lines is used when an existing line
with line-routes is drawn. The terminals between the line-routes can then
be drawn either with distances according to the relative length of the routes,
or, when this option is enabled, at equidistant positions along the line. This
has no effect on the electrical models, only on the graphical representation.
Display Frame around Switches draws a frame around the switch itself
(Breakers, Disconnectors, etc). This only applies to user-drawn breakers
and disconnectors.
Support Line Routes Functionality Support Line routes functionality:
• Enabled →Two line routes are created when placing a terminal on a
LINE.
• Disabled →Two lines are created when placing a terminal on a LINE.

N OTE : When placing a terminal on a LINE-ROUTE two line routes will be

created, regardless of the ”Support Line Routes Functionality” setting.
This is the intent and can not be changed, as line routes are stored
inside lines.

Additional Attributes and Coordinates tabs: these should only be configured with
the assistance of DIgSILENT support staff.

Result Boxes tab:

Handling of Power Factory 7-130

DIgSILENT PowerFactory Graphic Windows

Cubicle representation Selects the switch representation (see Fig. 7.14:

• ”Permanent Box” shows a solid black square for a closed and an

frame line for an open switch.
• ”Old Style Switch” shows the switches as the more conventional
switch symbol.

Background of Result Boxes specifies the transparency of results boxes:

• ”Opaque” means that objects behind the results box cannot be seen
through the results box.
• ”Transparent” means that objects behind the results box can be seen
through the results box.

Show line from General Textboxes to referenced objects may be disabled to

unclutter the graphic.

Always show result boxes of detailed couplers self-explanatory

Space saving representation of result boxes on connection lines

self-explanatory

Reset textboxes completely textboxes and result boxes have reference points
(the point on the box at which the box will ’attach’ to its element) that may
be changed by the user. If this option is

• enabled, the default reference will be used,

• disabled, the user defined reference will be used,

when the Reset settings option in the right-click menu for moved result
boxes is selected.

Figure 7.14: Feeder representations

The settings for the cursor type for the graphic windows (large crosshair or small
tracking cross) may be set in the User Settings dialogue. See section 4.2, page

Handling of Power Factory 7-131

DIgSILENT PowerFactory Graphic Windows

4-39. This is because the cursor shape is a global setting, valid for all graphic
windows, while all graphic settings described above are specific for each graphic
window.

Page Setup for Drawing and Printing

The drawing area for single line diagrams, block diagrams and virtual
instruments is selected in the ”Drawing Format” dialogue ( button on the
graphics window). One of the predefined paper formats can be selected, each of
which can be edited, and new formats can be defined. The selected paper
format has ”Landscape” orientation by default and can be rotated by 90 degrees
by selecting ”Portrait”. The format definitions, which are shown when an existing
format is edited or when a new format is defined, also show the landscape
dimensions for the paper format.

It is not possible to draw outside the selected drawing area. If a drawing no

longer fits to the selected drawing size, then a larger format should be selected.
The existing graphs or diagrams are repositioned on the new format (use C TRL
+ A to mark all objects and then grab and move the entire graphic by left clicking
and holding the mouse key down on one of the marked objects; drag the graphic
to a new position if desired).

If no ”Subsize for Printing” format has been selected, then, at printing time, the
drawing area will be scaled to fit the paper size of the printer. If, for instance, the
drawing area is A3 and the selected paper in the printer is A4, then the
graphs/diagrams will be printed at 70% of their original size.

By selecting a subsize for printing, the scaling of the drawing at printing time can
be controlled. The dimensions of the sub-sized printing pages are shown in the
graphic page. If, for instance, the drawing size has been selected as A3
landscape, and the printing size as A4 portrait, then a vertical grey line will divide
the drawing area in two halves. The drawing area will be accordingly partitioned
at printing time and will be printed accross two A4 pages.

Make sure that the selected subsize for used for printing is available at the
printer. The printed pages are scaled to the available physical paper if this is not
the case.
For instance:

• The drawing area has been selected as A2 landscape.

• The subsize for printing has been selected as A3 portrait. The A2 drawing
is thus to be printed across two pages.

• Suppose that the selected printer only has A4 paper. The original A2
drawing is then scaled down to 70% and printed on two A4 sheets of paper.

Handling of Power Factory 7-132

DIgSILENT PowerFactory Graphic Windows

Mark All
Button :

This function marks (selects) all objects in the drawing. This is helpful for moving
the whole drawing to another place or copying the whole drawing into the
clipboard. In block diagrams the surrounding block will not be marked. The
keyboard short cut C TRL + A may also be used to perform this action.

7.7.2 Block Diagram and Single Line Graphics

The following basic functions are available in block diagram and single line
graphics.

Edit Data
Right Click Selection : Edit Data

Keyboard : A LT - R ETURN

Mouse : Double-click

Button :

This option lets you edit the device data of all marked objects in the drawing. If
only one object is marked, then this object’s edit dialogue will pop up directly.
When more than one object is marked, a Data Manager window will show the list
of marked objects. As with a normal Data Manager, these objects can be
double-clicked to open their edit dialogues. See the Data manager (sec. 5, page
5-43) for more information.

N OTE : Changes made in the device data of objects are not registered by the
graphical Undo Function. Undoing these changes is therefore not pos-
sible.

Delete
Right Click Selection : Delete Element

Keyboard : D EL

Button :

This function deletes all marked objects in the drawing. The database objects for
the graphical object will also be deleted (a warning message will pop up first -
this may be switched off in the ”User Settings” dialogue; see user settings, sec.
4, page 4-37).

Handling of Power Factory 7-133

DIgSILENT PowerFactory Graphic Windows

Delete Graphical Object only

Right Click Selection : Delete Graphical Object only
This function deletes all marked objects in the drawing. The database objects for
the graphical object will also be deleted (a warning message will pop up first -
this may be switched off in the ”User Settings” dialogue; see user settings, sec.
4, page 4-37).

Copy
Right Click Selection : Copy
Keyboard : C TRL - C
Button :
Copies all marked objects from the current drawing and puts them into the
clipboard.

Paste
Right Click Drawing : Paste
Keyboard : C TRL + V
Button :
Copies all objects from the clipboard and pastes them into the current drawing.
The objects are pasted at the current graphical mouse position. Objects that are
copied and so pasted create completely new graphic and data objects in the
graphic that they are pasted into.

Should you wish to represent a data object in another graphic (that is, one data
object that is drawn in two different graphics), in other words, you wish to copy
and paste just the graphic, then choose ”Paste Graphic Only” from the right click
menu. Similar results are obtained when using the ”Draw Existing Net Elements”
tool. (See section 7.4.1, page 7-117).

Undo
Right Click Selection : Undo
Keyboard : C TRL + Z
Button :
Undoes the last graphic action. Undo will restore deleted elements or delete
created elements when necessary. Note that data that has been deleted or
changed will not be restored.

Handling of Power Factory 7-134

DIgSILENT PowerFactory Graphic Windows

Define Graphics Attributes

Button :

This dialogue sets the line style, line width, brush style, colour and font, for
annotations (ie not for power system elements).
The line style includes several kinds of dashed or dotted lines and one special
line style: the TRUE DOTS style. This style will only put a dot at the actual
coordinates. In a single line graphic, this means only at the start and the end,
which does not make much sense. For result graphs, however, the TRUE DOTS
style will only show the actual data points.

The brush style is used to fill solid symbols like squares and circles. These
settings may also be accessed by simply double clicking an annotation.

7.7.3 Single Line Graphics

The following basic functions are available in single line graphics only.

Draw Existing Net Elements

Button :

This button opens a database browser which contains all objects in the Current
Net Data folder, which are not shown in the active single line graphic.
Draw Existing Net Elements is used mainly to build single line graphics from
imported data, but may also be used to create alternative graphical
arrangements for existing data. See section 7.4.1, page 7-117 for more
information.

Set Individual Colour

Right Click Selection : Set Individual Colour

Allows the user to choose a colour for individual elements. Only available when
the ”Colouring Representation” is set to ”Individual”.

Rotate
Right Click Selection : Rotate

Rotates symbols 90 degrees. Only unconnected symbols can be rotated. To

rotate a connected element: disconnect it, rotate it and connect it again.

Handling of Power Factory 7-135

DIgSILENT PowerFactory Graphic Windows

Disconnect Element
Right Click Selection : Disconnect Element

Disconnects the selected elements.

Reconnect Element
Right Click Selection : Reconnect Element

Disconnects the selected elements and then presents the element for immediate
re-connection. The branch to be connected will be ’glued’ to the cursor. Left
clicking a bar or terminal will connect the element.

Connect
Right Click Selection : Connect Element

Button :

Connects the selected unconnected elements one by one. The branch to be

connected will be ’glued’ to the cursor. Left clicking a bar or terminal will connect
the element.

Move
Marked objects can be moved by left clicking them and holding down the mouse
button. The objects can be moved when the cursor changes to an arrowed cross
( ).
Hold down the mouse button and drag the marked objects to their new position.
Connections from the moved part of the drawing to other objects will be adjusted.

Edit Line Points

Right Click Selection : Edit Line Points

The connection lines of graphical symbols may be edited separately. Selecting

the Edit Line Points option will show the black squares (’line points’) that define
the shape of the connection. Each of these squares can be moved by left
clicking and dragging them to a new position (see Fig. 7.15). New squares can
be inserted by left clicking the connection in between squares.
Line points are deleted by right-clicking them and selecting the Delete Vertex
option from the case sensitive menu. This menu also presents the option to stop
(end) the line point editing, which can also be done by left clicking somewhere
outside the selected lines.

Handling of Power Factory 7-136

DIgSILENT PowerFactory Graphic Windows

Figure 7.15: Editing line points

7.7.4 Drawing Power System Elements

Drawing elements on the single line graphic is a simple matter of choosing the
required tool from the Drawing Tools toolbar. This toolbar is only visible to the
user when:

a project and study case is active

the open graphic is unfrozen

By default the drawing toolbar is docked on the right side of the screen, but it
may be un-docked by grabbing it and dragging to the graphics board area. To do
this left click and hold your mouse down, in an area of the toolbar that does not
have any buttons, and move the mouse to the left. To re-dock the toolbar drag it
back to the right of the screen until it re-docks.

When starting to draw your system it is natural to first draw the nodes that are
required. Nodes may be represented by busbars or terminals in PowerFactory.
Terminals should be used as far as possible and there are several different
representations of terminals, shown and explained following.

Busbars are used to create more complex node clusters, such as a double
busbar with tie breaker, busbars with section breakers, and so forth. Busbars are
part of a ”Station” and their data elements are housed in a station folder in the
database, together with the switches that make the bus couplers, section
breakers, disconnecters, etc. Busbars are a quick and convenient way to
represent slightly more complex busbar systems but they have a fixed format in
terms of the breaker and disconnecter arrangement.
Should the user wish to create specific breaker and disconnecter arrangements
then terminals and discrete switches should be used for this purpose.

N OTE : When drawing objects the cursor may be reset by right clicking

Terminals

Handling of Power Factory 7-137

DIgSILENT PowerFactory Graphic Windows

Terminals are representations of nodes and there are six different terminals that
may be used. See Fig. 7.16:

This is the most common representation of a node.

Looks the same as a Terminal but is shorter and the results box and name
is placed on the ”Invisible Objects” layer by default. Typically used to save
space or to unclutter the graphic.

Typically used to represent a junction point, say between an overhead line

and cable. The results box and name is placed on the ”Invisible Objects”
layer by default.

Typically used for reticulation and/ or distribution networks.

Typically used for reticulation and/ or distribution networks.

Typically used for reticulation and/ or distribution networks.

Figure 7.16: Node Representation

Terminals should be placed in position and then, once the cursor is reset,
dragged, rotated and sized as required.

N OTE : When placing a terminal or a busbar in position these will be placed

vertically (rotated 90 deg anticlockwise) if the C TRL key is held down
as they are placed

Re-positioning is performed by first left clicking on the terminal to mark it, then
click once more so that the cursor changes to . Hold the mouse button down
and drag the terminal to a new position.

Handling of Power Factory 7-138

DIgSILENT PowerFactory Graphic Windows

Re-sizing is performed by first left clicking on the terminal to mark it. Sizing
handles appear at the ends of the terminal (see Fig. 7.17) and these may be
grabbed and dragged to the desired size.

Figure 7.17: Sizing handles

Busbars
The tools for single and double busbar systems with and without tie breakers will
produce pre-defined busbar systems.
The will pop up the dialogue to define new busbar systems. With this
dialogue, complex systems like ”Breaker And A Half” systems, with special
cubicle configurations may be defined. See Add Busbar Systems, sec. 8.2.1,
page 8-152, for more information.

Busbars are placed by left clicking on an empty space on the drawing area.
Busbars are sized and moved in the same manner as terminals.

Edge and Branch Elements

Single port elements (for loads, machines, etc.) can be positioned in two ways.
The simplest way is to left click the busbar where the element should be placed.
This will draw the element at a default distance under the busbar. In case of
multi busbar systems, only one of the busbars need be left-clicked. The
switch-over connections to the other busbars will be drawn automatically.
The ’free-hand’ method first places the element symbol wherever desired, that
is, first click wherever you wish to place the symbol. The cursor now has a
’rubber band’ connected to the element and when the cursor is left clicked onto a
node it will be connected. To create corners in the joining line left click on the
graphic. The line will snap to grid, be drawn orthogonally, as determined by the
”Graphic Options” that have been set.

Double port elements (for lines, transformers, etc.) are positioned in a similar
manner to single port symbols. By left-clicking the first busbar, the first

Handling of Power Factory 7-139

DIgSILENT PowerFactory Graphic Windows

connection is made. The second connection line is now held by the cursor.
Again, left-clicking the drawing area will create corners. Double clicking the
drawing area will position the symbol (if not a line or cable - eg a transformer).
The second connection is made when a node is left clicked.

Triple port elements (three-winding transformers) are positioned in the same

manner as two port symbols. Clicking the first, and directly thereafter the second
node, will place the symbol centered between the two nodes, which may be
inconvenient. Better positioning will result from left clicking the first busbar,
double clicking the drawing space to position the element, and then making the
second and third connection.
The ’free-hand’ method for two and triple port elements works the same as for
one port elements.

N OTE : Pressing the TAB key after connecting one side will leave the second
leg unconnected, or jump to the third leg in the case of three port ele-
ments (press TAB again to leave the third leg unconnected). Pressing
E SC will stop the drawing and remove all connections.

If the element being drawn seems as if it will be positioned incorrectly

or untidily there is no need to escape the drawing process. Make the
required connections and then right click the element and use Recon-
nect Graphically to re-draw the element whilst retaining the data con-
nections

Annotations are created by clicking one of the annotation drawing tools. Tools
are available for drawing lines, squares, circles, pies, polygons, etc. To draw
some of these symbols left click at some place and release the mouse
somewhere else (e.g. circles, lines, rectangles). Other symbols require that you
first set the vertices by clicking at different positions and finishing the input mode
by double clicking at the last position.

7.8 Interconnecting Power Subsystems

Interconnections between two different graphics is achieved using two methods:

• Representing a node in additional different graphics by copying and

pasting the graphic only and then by connecting branch and edge
elements to the graphical object in the additional graphic.

• By connecting an edge element between two graphics.

The first method is performed by copying the desired node (right click →Copy )
and then clicking on the other graphic in which it should be represented and right

Handling of Power Factory 7-140

DIgSILENT PowerFactory Graphic Windows

clicking →Paste Graphic Only. Only a graphical object is pasted into the second
graphic and no new data element is created.

The second method is as follows:

First ensure that you have node to connect to in both graphics that are to
be interconnected.

In this example we will use an autotransformer. Select an autotransformer

drawing tool from the toolbar and create the first connection as normal by
left clicking a node [1] (see Fig. 7.18).

Double click to place the symbol [2]. Your cursor is now attached to the
transformer by a ’rubber band’ [3].

Move the cursor to the bottom of the drawing page and click on the tab of
the graphic that the interconnection is to be made to [4] (see Fig. 7.19)

Once in the second graphic left click to place the transformer symbol [5]
(see Fig. 7.20) and then left click on the second node [6].

The interconnected leg is shown by an symbol. Right clicking on the

element presents a Jump to next page option.

Figure 7.18: First step to interconnecting

Handling of Power Factory 7-141

DIgSILENT PowerFactory Graphic Windows

Figure 7.19: Second step to interconnecting

N OTE : The first method of interconnection, that of representing a node in two,

or more, different graphics, may lead to confusion at a later point as
the ’inflow’ and ’outflow’ to the node will not appear correct when just
one graphic is viewed - especially if a user is not familiar with the sys-
tem. The node may be right clicked to show all connections in what is
known as the ’Station Graphic’ (menu option Show station graphic).

Thus, the second method may be preferred. To check for nodes that
have connections on other graphics the ”Missing graphical connec-
tions” colouring mode may be employed.

Handling of Power Factory 7-142

DIgSILENT PowerFactory Graphic Windows

Figure 7.20: First step to interconnecting

7.8.1 Colouring Mode

The Single line graphic window has an automatic colour representation mode.
The button on the local toolbar will open the colour representation dialogue.
This dialogue is used to select a certain colouring mode. This mode may be

None : this will redraw the graphic in black and white

Individual : each symbol may be assigned an individual colour as determined

by the user.

Functional : colours the graphic according to one of the following criteria.

• Low/High voltage or loading

• Voltage level

• Voltage regions

• Isolated Grids

• User defined filter

• Grids/ Original locations

• System stages

• Loading of Thermal/Peak Short Circuit Current

• Path definitions

• System Type AC/DC and Phases

Handling of Power Factory 7-143

DIgSILENT PowerFactory Graphic Windows

• Relay locations

• Fault Clearing Times

• Feeder Definitions

• Fault clearance and power restoration

• External measurement locations

• Missing graphical connections

• Zones

• Observability

Choose one of the options to colour the graphic accordingly.

7.8.2 Title Block

The button on the local toolbar will turn the title block (See Fig. 7.21) on and
off. The title block is placed in the lower right corner of the drawing area by
default.

Figure 7.21: Single Line Title Mask

The contents and size of the title mask can be changed by right clicking the title
block and selecting the Edit Data option from the context sensitive menu. The
Select Title dialogue that pops up is used to scale the size of the title block by
setting the size of the block in percent of the default size. The font used will be
scaled accordingly. To edit the text in the title block press the edit button ( )
for the ”Title Text” field.

All text fields have a fixed format in the title block. The data and time fields may
be chosen as automatic or user defined. Most text fields are limited to a certain
number of characters. When opening a new graphic the title will appear by
default.

7.8.3 Legend Block

The button on the local toolbar will turn the legend block on and off. The
legend block provides the key to the contents of result boxes.

Handling of Power Factory 7-144

DIgSILENT PowerFactory Graphic Windows

Because more than one type of result box is normally used in the Single line
graphic, for instance, one for node results and another one for branch results,
the legend box normally shows more than one column of legends. After
changing the result box definitions, it may be required to manually resize the
legend box in order to show all result box legends.

The Legend Box definition dialogue is opened by right clicking the legend block
and selecting Edit Data from the context sensitive menu. The font and format
shown may be configured. When opening a new graphic the legend will appear
by default.

7.8.4 Station feeder Options

In the context of this tool a feeder is a connection to a busbar, however, in a
general context a feeder is a connection to a node, be it a terminal or a busbar.

The button on the local toolbar presents the ”Cubicle Parameter Settings”
dialogue. The settings in this dialogue determine the type number and
configuration of switches that will be created automatically in a cubicle when a
branch element is connected to a busbar system, where no free cubicle is
available. Fig. 7.22 shows:

1 A single circuit-breaker connection with disconnecters on both the busbar

and feeder side.

2 A multiple circuit-breaker connection with disconnecters on both the busbar

and feeder side.

3 A multiple circuit-breaker connection with disconnecters only on the busbar

side.

4 A multiple circuit-breaker connection with disconnecters only on the feeder

side.

When creating a new station the option ”Automatically create and delete
Cubicles From Graphic” is set by default. This means that new cubicles will be
created whenever a connection is made to a busbar, and these will similarly be
deleted when a connection is removed - unless there is a protection device
located in the cubicle, in which case the cubicle will be retained. If the option is
’unset’ then it is only possible to connect as many branch elements as the
number of cubicles set for this station. Deleting a connected branch will leave
the cubicle unchanged.

When a new station is inserted the default number of cubicles per section may
be set by the administrator in the relevant SetStat object under
S YSTEM\L IBRARY\G RAPHIC When connecting branch elements to a station all
free cubicles will be used up.

Handling of Power Factory 7-145

DIgSILENT PowerFactory Graphic Windows

Figure 7.22: Various switch configurations

See Selecting Cubicles, sec. 8.2.1, page 8-154, for more information about the
creation of busbar systems and cubicles.

7.8.5 Result Boxes

PowerFactory uses result boxes in the Single line graphic to display calculation
results. Result boxes are generally set up so that there are a series of different
formats for each calculation function, with variables appropriate to that function.
In addition, the format differs for the objects class and/or for individual objects.
For example, following a load flow, branch and edge elements will have different
formats compared to nodes, and an external grid will have an individual,
different, format as compared to the branch and edge elements.

The result box itself is actually a small output report, based on a form definition.
This form definition, and the PowerFactory output language that is used to
define it, allows for the display of a wide range of calculated values, object
parameters, and even for colouring or user defined text.

Although the result boxes in the single line graphic are a very versatile and
powerful way for displaying calculation results, it is often not possible to display a
large (part of a) power system without making the result boxes too small to be
read. PowerFactory solves this problem by offering balloon help on the result
boxes. Positioning the mouse over a result box will pop up a yellow text balloon
with the text displayed in a fixed size font. This is depicted in Fig. 7.23. The
result box balloon always states the name of the variable, and may thus also be
used as a legend.

Handling of Power Factory 7-146

DIgSILENT PowerFactory Graphic Windows

Figure 7.23: Result Boxes Balloon Help

A result box is connected to the graphical object for which it displays the results
by a ’reference point’. Fig. 7.24 shows the default reference points for the
resultbox of a terminal. A reference point a connection between a point on the
result box (which has 9 optional points), and one of the ’docking’ points of the
graphical object. The terminal has three docking points: on the left, in the middle
and on the right. The reference point can be changed by:

• Right-clicking the resultbox with the graphics cursor (freeze mode off), and
selecting Change Reference Points.

• The reference points are shown: docking points in red, reference points in
green. Select one of the reference points by left-clicking it.

• Left-click the selected reference point, and drag it to a red docking point
and drop it.

• An error message will result if you drop a reference point somewhere else
than on a docking point.

Figure 7.24: Reference Points of a result Box

Result boxes can be freely moved around the diagram. They will remain
attached to the docking point, and will move along with the docking point. A
result box can be positioned back to its docking point by right-clicking it and
selecting Reset Settings from the menu.
If the option ”Reset textboxes completely” is set in the graphical settings, then
the default reference and docking points will be selected again, and the result
box is moved back to the default position accordingly.

Handling of Power Factory 7-147

DIgSILENT PowerFactory Graphic Windows

7.8.6 Editing Result Boxes

PowerFactory uses separate result boxes for different classes of power system
objects, such as node objects (i.e. busbars, terminals) or edge objects (i.e. lines,
loads). For each type of result box, a different result box definition is used.

A newly installed version of PowerFactory has pre-defined result box formats

for all object classes. These default formats cannot be changed, however, the
user may define other formats and save these for use. For the edge objects, for
example, the default box shows P and Q without units.

A number of these predefined formats are available for display and these may be
selected by right clicking a results box to get the Format for Edge Elements
option, which then presents a number of formats that may be selected- the
active format is ticked ( ).

Should the user wish to create a specific format that is different from the
pre-defined formats the Edit Format for Edge Elements option should be used,
which will be explained in detail following. Note that, when editing the format the
new format will be applied to the entire class of objects. Should you wish to
create a format to be used for just one instance then use the Create Textbox
option. An additional results box/ textbox will be created, using the current
format for the object. This may then be edited.

When the Edit Format option has been selected the user is presented with the
form manager dialogue (see Fig. 7.25). A name for the new form may be
entered [1]. Various options for the results box may be set [2] and the drop down
lists of pre-defined variables are used to configure the desired format [3]. Once
the format has been set and chosen the format may be saved for future use by
pressing the TO L IBRARY button [4]. The format is saved to
S ETTINGS\P ROJECT\C HANGED S ETTINGS\F ORMATS\G RF\R ESULT in the user
folder and is available for use in any project in the user folder (when right clicking
a results box for the same calculation functionality the new format will be seen in
the listing of formats).
Should the list of pre-defined variables not contain the required variable then the
I NPUT M ODE should be pressed; three input modes are available:

• Predefined Variables - a list of commonly used variables

• User Selection - lists all of the variables available in PowerFactory

• Text Editor - unlocks the text editor page for manual configuration of the
variables and their format; this should only be used by advanced users.
The text editor page is found on the ”View” tab [6].

The ”User Selection” mode changes the appearance of the form manager
slightly so that a S ELECT VARIABLES appears in place of the pre-defined

Handling of Power Factory 7-148

DIgSILENT PowerFactory Graphic Windows

Figure 7.25: The Form Manager

variables drop down listings. Press this button to access the variable set
dialogue. The selection and use of variables is fully described in 5.10.

Handling of Power Factory 7-149

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Chapter 8

Creating and Using Simulated

Power Systems

The chapter Graphic Windows (section 7, page 7-110), describes the

fundamentals of creating a power system in PowerFactory, by drawing the
various components of a network, i.e. by drawing busbars, lines, generators, etc.

This chapter shows how PowerFactory handles busbars and terminals, and
how they can be grouped into station definitions, how lines, line routes and line
sections relate to each other and the role of the terminal in this, how to create
parameter characteristics (for inserting load profiles for example), how to define
feeders, etc.

8.1 Introduction to Terminals, Busbars and

Cubicles

When the mathematical model of a power system is set up, the junction points
that lines, generators, loads, etc. are connected to are generally termed nodes.
In real world systems we normally term these ’busbars.’

When nodes are represented in PowerFactory objects called “Terminals” and

“Busbars” are used. Busbars have to be part of a station and several busbars
may be included in a station.

When other power system elements, such as lines, transformers or loads

(known generically as edge and branch elements) are connected to a node
PowerFactory uses what is known as a ”Cubicle” to affect this connection.
Cubicles may be visualised as the panels in a switchgear board, or bays in a
high voltage yard, to which the edge or branch element is connected.
Cubicles are normally created automatically when an element is connected to a
node.

Handling of Power Factory 8-150

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

8.2 Station and Busbar Systems

In PowerFactory nodes are represented either as ’Terminals’ or as ’Busbars’

and each of these is handled in a different manner in the database, although
they are mathematically the same. Generally, busbars are housed within a
‘station’ folder and are used for more complex node representations (such as
double busbars, busbars with section breakers, etc.). Several busbars may be
housed within one station folder. The disadvantage of using stations and
busbars is that the breaker and disconnecter configurations are not very flexible
and only certain arrangement are permitted. If particular arrangements, different
from those permitted in stations and busbars, are required then these should be
compiled using terminals and discrete switches.

The permitted breaker and disconnecter arrangements are shown in Fig. 8.1:
1 single breaker connected to two busbars with a line side disconnecter
2 multiple breaker connected to two busbars with line and busbar side
disconnecters
3 multiple breaker connected to two busbars with only line side disconnecters
4 multiple breaker connected to two busbars with only busbar side
disconnecters

Figure 8.1: Breaker and disconnecter arrangements for busbars

There are two methods used to define stations:

Handling of Power Factory 8-151

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

• graphically in the single line graphic

• ‘directly’ in the database manager

With the graphical method, all busbar systems that belong to the same station
are first created separately and grouped into one station later on. During the
direct method, a station is created first and filled manually with busbar systems.

In both methods, we have to define busbar systems with distinct properties and
cubicles to connect other objects to these systems.

8.2.1 Defining Busbar Systems

The simplest busbar system is just a single busbar. Such an object can be
created directly in the single line graphic (by using the button in the graphic
toolbox) and in the database manager (by pressing the button and adding a
StaBar object).

The graphical toolbox for the single line graphics also offers buttons for a:

• single busbar system with two sections and a tie breaker.

• double busbar system.

• double busbar system with two sections and two tie breakers.

• one and a half busbar system

Other busbar system configurations may be created using the “General Busbar
System” tool. This is a so-called ’Set’ dialog and not a normal ’Edit’ dialog (’Set’
dialogs are used to create new objects, whilst ’Edit’ dialogs are used to alter
existing ones) which means that you will first be presented with a dialogue in
which you must make selections in order to define the busbar system to be
drawn.

In the case of the busbar systems it will not be possible to change the basic
layout of these systems after they have been created. It will thus not be possible
to change, for instance, a three-bar, “TransferCombi” system into a two-bar
“Breaker-and-a-half” system later on. However, it will be possible to change the
electrical parameters like the nominal voltage, the busbar types, the number of
cubicles, the type of switches used, etc.
The Add Busbar dialog shows the current definitions for new busbar systems
and their cubicles. This definition has the following fields:

Busbar system : reference to a busbar system ’Set’ dialog

Cubicle parameters : reference to a cubicle ’Set’ dialog

Handling of Power Factory 8-152

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.2: ’Set’ dialog for creating a new busbar system

Voltage level : the voltage level for the generated busbar system

Use Busbar Type : a busbar type may be selected

Number of Sections : the number of busbar sections

Number of Cubicles in One Busbar Section : the number of cubicles per

busbar section

The ’Set’ dialog for the busbar system thus uses two other ’Set’ dialogs: one for
the busbars which have to be generated and one for the cubicles. At least one
cubicle must be generated per busbar section, but more may be generated
directly. When other objects are connected to the busbar system in the single
line graphic, the available free cubicles will be used first. When no free cubicles
are available a message will pop up if the Automatically Create Feeders From
Graphic option in the station edit dialog is disabled. The new cubicle will be
created according to the current settings in the cubicle ’Set’ dialog. If these
settings were changed since the busbar system was created, these new cubicles
will differ from the original ones. To ensure equal cubicle configurations, all
cubicles that are required should be generated with the busbar system at once,
or the cubicle ’Set’ dialog must be changed to the correct settings prior to
connecting an object to the busbar.

A new cubicle ’Set’ dialog may be selected and configured by pressing the
“Select” button ( ). A database browser will pop up which may be used to
select a SetCubop dialog. The selected ’Set’ dialog can be edited by pressing
the E DIT button ( ). The “Cubicle Parameters” (see sec. 8.2.1, page
8-154) dialog will then appear.

For the busbar ’set’ dialog, as with the cubicle reference, a database browser will
pop up when the S ELECT button is pressed to select a SetBussys object from

Handling of Power Factory 8-153

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

the database. If the E DIT button is pressed, the “Define Busbar System” (see
sec. 8.2.1, page 8-154) dialog will pop up.

For both the cubicle and busbar system ’Set’ dialog it is possible to create a new
dialog by pressing the “New” button ( ) in the database browser after the (
) button was pressed.

N OTE : Under most circumstances the user simply connects branch and edge
elements to the busbars and the required cubicles and switches will
be automatically created as the ”Automatically Create Feeders From
Graphic” option is enabled by default. Detailed and specific breaker
and disconnecter configurations may be configured as shown above,
however, such applications are usually quite particular and will proba-
bly need to be built using terminals and discrete switches

Defining a new busbar system

After a busbar system ‘Set’ dialog has been selected, it may be edited by using
the E DIT button. The Define Busbar System dialog will pop up in order to edit
the following parameters:
• The name of the (new) busbar system
• The basic configuration:
– A standard single busbar system
– An u-bar system with power switches between busbar sections
– A busbar transfer combination
– A Ring scheme system
– A “Breaker and a half” system
– A “Break through Method” system
• The number of busbars per section
• The kind of coupling between the busbar sections
• Whether or not a transfer bus should be used

More information about possible busbar configurations can be found in the

Technical Reference Manual.

Selecting Cubicles
After the busbar system itself has been defined, the kind of cubicles that will be
generated can be specified. After a cubicle definition has been defined, it may
be edited by using the “edit” button. The “Cubicle Parameters” dialog will pop up
in that case, which has the following parameters:

Handling of Power Factory 8-154

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

• Multiple or single circuit breakers

• The type of circuit breaker.

• The type and presence of disconnecting switches

• The type and presence of grounding switches

• The number and position of current transformer

• The number and position of voltage transformers

• The presence of a surge diverter

In order to generate a new busbar system, at least one cubicle per busbar
section has to be chosen. More cubicles, which may also differ from the first,
automatically created, cubicles, can be added manually later on by selecting
“Add Feeder” in the Station Edit dialog.

8.2.2 Defining Stations in the Single Line Graphic

After a single line graphic has been opened, all busbars systems belonging to
the station that is to be created have to be drawn separately. The simplest way
to draw one or more busbars is by use of the button in the drawing toolbox.
By left clicking on the single line graph area when this button has been pressed,
one or more single busbars can be placed. The busbar objects will automatically
be created in the correct data manager folder.

When the is pressed in the toolbox, the “Add Busbar System” dialog will pop
up the moment the drawing area is left clicked. This set dialog is used to define
the new busbar system, as has been explained in the forgoing section.

The single line graphic will first use up all free cubicles when objects are
connected to the new busbar system. When no free cubicle is available any
more, a message will pop up if the Automatically Create Feeders From Graphic
option in the surrounding station object edit dialog has been disabled. When this
option is enabled a new cubicle will be created, according to the settings of the
cubicle ’Set’ dialog. Each single line graphic has its own cubicle ’Set’ dialog. To
make sure that the cubicle configuration is set correctly, the settings for the
current cubicle configurations may be edited and/or altered by pressing the
button on the active graphics window toolbar.

Since it not known which station the busbars being drawn should belong to, and,
since each busbar must belong to a station, a new station for each new busbar is
created. After all or some of the busbars of the station have been drawn, they
can be transferred into one station. This is shown in the following example.

Handling of Power Factory 8-155

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Suppose a station with four interconnected busbars is to be defined. These four

busbars are drawn independently at first. Interconnecting lines or transformers
or other power system objects may be drawn as well. An example of the
resulting single line graph and corresponding database folder is depicted in Fig.
8.3 and Fig. 8.4. The database contains four stations.

Figure 8.3: Single line graphic with four interconnected busbars

Figure 8.4: Database Browser with four stations

The four busbars are each located in one of the station folders. The busbars are
automatically given names such as ’B1’, ’B2’, etc. Because all busbars will be
created in their own stations, they will normally all be given the same name. This
is seen in Fig. 8.3 where the station names and busbar names have been
automatically generated.

A new station configuration can be defined by grouping busbars into stations.

This is done by multi selecting the busbars and right clicking the selection. A
context sensitive menu will pop up from which the Define Station option will
pop-up a database browser showing all the station folders that are available in
the grid.
Normally, this list will show all stations defined for the grid being developed. This
includes the initial stations created when the selected busbars where drawn.
Anyone of these stations (for example ’Station1’ in the example) may be selected
as the target station.

Handling of Power Factory 8-156

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.5: Context sensitive menu for a selection of busbars

All selected busbars will be moved to the target station. During this transfer, the
names of the busbars will be changed, should that be necessary to ensure
unique naming. The default name B1 will be changed to B2, B3, B4, etc. User
defined names will normally not have to be changed because they should be
unique already, but a (1), (2), (3), etc. will be attached to the name if this isn’t so.
All stations that are ’emptied’ during the transfer of busbars and cubicles will be
deleted.

More information about stations can be found in The Station Folder, section
5.17.3, page 5-87 and Stations and Busbar Systems, section 8.2, page 8-151.

8.2.3 Defining Stations in the Database Manager

N OTE : Although new stations and other elements may be created from the
data manager it is preferable to create new elements by drawing them
in the graphic and then editing them.

Stations may be created directly in the data manager by pressing the new object
( ) button and selecting a ElmStat object. This will pop up the station edit
dialog, as shown in Fig. 8.6.

Figure 8.6: The station edit dialog

To configure the station, three buttons are provided in this dialog:

Handling of Power Factory 8-157

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

I NTERNAL E LEMENTS Presents a database browser showing a list of all

current elements in the station. These elements are either busbars,
switches or cubicles. The cubicles consist of separating switches, power
switches, surge diverters, etc. and have their own ‘internal elements’ button
in their edit dialog.

A DD B USBAR S YSTEM Presents a dialog with which a new busbar system

can be defined and added to the station. The basic busbar layout can be
chosen, as well as the type and number of cubicles that will be
automatically attached.

A DD F EEDER Presents a dialog to add individual cubicles to previously

defined busbar systems in the station.

When the A DD B USBAR S YSTEM button is pressed in the station edit dialog,
the “Add BusBar System” dialog pops up with which a new busbar system can
be defined, as has been explained in the section 8.2.1, page 8-152.

The second way to define a station is by gathering busbars systems in the single
line graphic. See section 8.2.2, page 8-155, .

More information about stations can be found in The Station Folder, section
5.17.3, page 5-87 and Stations and Busbar Systems, section 8.2, page 8-151.

8.2.4 Stations, Busbars and Terminals

A basic node object in PowerFactory is the busbar object. As has been shown
in this chapter, it may be used to form complex multi-busbar systems with
sections and corresponding cubicles.

However, the busbar object has two drawbacks: it must always be located in a
station and it is relatively inflexible in the configuration of particular
(non-’standard’) breaker and disconnecter arrangements. For high-voltage
transmission and distribution systems, busbars are normally part of a station, but
even in these systems lines may have branches or T-offs to other lines. Such a
’branch off’ may occur at an overhead line tower and it would make no sense to
define a station with one busbar just to model this branch off.

PowerFactory therefore has a simple element to represent a node, where a

station is not required. This node representation is called a ‘terminal’ (ElmTerm),
which may look similar to a normal busbar and is derived from the same type
(TypBar). Fig. 8.7 shows the possibilities with the busbar and terminal objects.
This figure shows the following features:

1. Normal busbar (systems) are mainly used for the HV and MV transmission
and distribution systems. Two two-bar systems are used as an example
here. These busbars must belong to a station.

Handling of Power Factory 8-158

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.7: Busbar and Terminal Options

2. Terminals may be used in a ring feeder to connect two or more loads. They
have a result box, but they do not belong in a station.

3. A short terminal object is used, for instance, to connect a motor or generator

through a cable to a busbar or to model a multi-load endpoint of a line. The
short terminal strip has no result box.

4. A special short terminal, displayed as a dot, is used to branch off a line.

These terminals may or may not use power switches to (dis)connect the
line routes. They always use a switch in the feeder to which any kind of
branch object is be connected: loads, machines, or other cables.

A terminal can be added to the single line graphic by using one of the
buttons in the drawing toolbox. Left clicking the drawing area will place a new
terminal.

Terminals are used in the same way as busbar objects. They can be scaled and
moved. All branch objects that can be attached to a busbar can be attached to a
terminal. The only difference is that the context sensitive menu lacks the station
option Define Station.

Terminals may also be drawn using other graphical symbols that may be more
convenient, such as the button. This is used to create the short terminal
without a result box. The short terminal has a default width for one double
cubicle, but can be scaled to make space for more (see [3] in Fig. 8.7). Other
terminal shapes are shown in Fig. 8.8.

When a line is branched off, a special ’dot’ or ’point’ terminal is created

automatically. This is a short terminal in another graphical form. These terminals

Handling of Power Factory 8-159

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.8: Various terminal graphic options

are stored in the line object, which thus acts as a folder object in the database
tree, in the case where a line is split into line routes.

Terminals created outside of lines are stored in the active grid folder for the
graphic.

8.2.5 The Station Graphic

All busbars and terminals in the single line graphics may be right clicked to
select Show Station Graphic. The station graphic shows the selected node with
ALL of the connections that have been made to it, independently of the graphic
that these connections have made in.

The station graphic cannot be used to change the station layout, but it can be
used to open or close the individual switches which are not visible in the single
line graphics of the complete grid. Elements in the station graphic may be
double clicked to open their edit dialog as normal.

The station graphic shows all the results from the last calculation, and may show
more detailed representations of the various connected elements. The single
line drawing of elements in the station graphic may thus show tap positions and
switching groups of the transformers, whether these are visible in the grid
graphics or not. The station diagram could thus be used to produce a more
detailed printout of, for instance, the load flows around specific busbars.

The station graphic is deleted from the graphics board by right-clicking the page
tab at the bottom of the graphics board and selecting Remove Page(s).

Handling of Power Factory 8-160

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

8.3 Transmission Lines and Cables

Transmission lines and cables are both treated alike, and they are both
instances of the generalised ‘transmission line’ element ElmLne. Therefore,
anywhere that ‘transmission line’ or simply ‘line’ is written in the following
chapter, ’lines and/or cables’ may be read, unless otherwise specified.

A transmission line may be modelled simply as an one to one connection

between two nodes and will refer to a line (TypLne), tower (TypTow) or tower
geometry (TypGeo) type, from which all the required electrical parameters are
derived.

Alternatively, lines may be subdivided into sections or line routes and may have
interconnecting feeder branches and the routes in their turn may also be
sectionalised.

The three basic line configurations possible are depicted in Fig. 8.9:
• Top line: the simplest transmission line is a single line object (ElmLne).
• Middle line: such a single line may be subdivided into line section objects.
(ElmLnesec) at any time. No terminals are allowed between two sections,
but the sections may have different line types.
• Bottom line: a single line may also be subdivided into line route objects
(ElmLneroute) where terminals are placed between the line routes. The
line routes in their turn may be subdivided into line sections.

Line

section 1 section 2 section 3 section 4

Terminal1 Terminal 2
Route 1 Route 2 Route 3
section 1 section 2 section 3
bus1 bus2

Figure 8.9: Three Basic Line Configurations

From a mathematical point of view the following is important:

• Lines and line routes may be modelled as a lumped Π model, or by a
distributed parameter model.

Handling of Power Factory 8-161

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

• Line routes are separated through terminals, which in fact are small
busbars. The terminals may have serial switches to open the line. Other
lines or loads may be connected to the terminals, each of them through a
cubicle with a switch.

The purpose of separating lines into routes and/or sections is:

• to allow T-offs or Branch offs from a ’main’ line, such that the main line
name is retained in the database (line route and sections are shown as
objects in the line folder).
• to sectionalise the line into parts so that different line types may be used
for the different sections (such as when a line uses two or more different
tower types, or when manual transpositions should be modelled - since the
”Transposed” option in the type object is a perfect, balanced, transposition)

More about the mathematical models of sectionalised lines and routes, and the
relations between lines and tower objects and types, can be found in the
Technical Reference Manual.

8.3.1 Creating a Transmission Line

The most simple line model is an one-to-one connection between two busbars.
This is normally done in the single line graphic by selecting the button and
by left clicking the first busbar, possibly clicking on the drawing surface to draw a
corner in the line and ending the line at the second busbar by left clicking it. This
will create a ElmLne object in the database.

When this object is edited, the following dialog will appear.

The dialog shows the two cubicles to which the transmission line is connected
(’terminal i’ and ’terminal j’). The example in Fig. 8.10 shows a line which is
connected between the nodes called ’Line End Terminal’ and ’Line Feeder Bus’.
The line edit dialog shows the name of the node (in red) in addition to the name
of the cubicle (in blue). The actual connection point to the node is the cubicle
and this may be edited by pressing the edit button ( ). The cubicle may be
edited to change the name of the cubicle, or to remove the breaker.

The two connections can also be chosen manually, by selecting the cubicles in
other nodes. This is achieved by pressing the buttons next to the ‘terminal i’
or ‘terminal j’ fields. However, this change will not be automatically reflected in
the single line graphic. To re-draw the line right click the line (which will now
appear with a >> symbol on one side) and use the Reconnect Graphically
option. The nodes that the line is connected to are now highlighted and the line
may be drawn between them.

The type of the line is selected by pressing the iconArrSelect next to the type
field. Line types for a line, line route or line sub-section are:

Handling of Power Factory 8-162

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.10: Editing a Transmission Line

• The straight forward TypLne object type.

• A tower type (TypTow) where the geometrical coordinates and conductor

electrical parameters are specified. The line parameters are calculated
from this data.

• A geometrical tower type (TypGeo) where the geometrical coordinates are

specified (a conductor type is then also required in the element).

Inserting a Branch or T off

Lines, loads, machines, or any other branch or edge element may be ’Teed’ into
an existing line, or ’branched off’ that line. Inserting such an element into a line
will split the line into what are known as line-routes. Simply put, this means that
the line will be split into two parts, separated by a point terminal. The two parts
are called line routes and are stored as sub-folders in the original line folder.

Handling of Power Factory 8-163

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

This is best achieved in the single line graphic by first selecting the branch object
from the drawing tools and then left clicking the line.

This will pop up a ”Branch Off Element” dialog as shown in Fig. 8.11.

Figure 8.11: the Branch Off Element Dialog

This dialog refers to the line which is about to be branched off, its total length
and the permissable length of the interval to be placed.

This permissable length interval is determined by the total line length and
connections made previously. The new insertion point must be within the
permitted limits.

Switches may be inserted on either side of the terminal that will be inserted. It
will not be possible to open the line at the insertion point if no switches are
inserted (see ‘Term 2’ in Fig. 8.9), however, switches may be inserted, or
deleted, later by right clicking at the switch position (or where the switch would
normally be) and selecting Create Circuit-Breaker or Remove Circuit-Breaker.
The branched off element (the inserted load, machine, etc.) is always connected
through a switch and may thus be disconnected from the line in all cases.
Inserting one or two switches enables the opening of the line from either the left,
the right or from both sides.

N OTE : It is also possible the utilise the convenience of simply ’dropping’ an el-
ement onto a line without creating line routes by disabling the ”Support
Line Routes Functionality” in the ”Graphic Options” dialogue. In this
case the line is simply split into two separate line instead of line routes

Handling of Power Factory 8-164

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Lines, Routes and Sections

A line or line route may be subdivided into line sections. This is achieved by
pressing the R OUTES /C UBICLES /S ECTIONS in the line dialog.

This will show a database browser with either line route (ElmLneroute) and
terminal (ElmTerm) objects, or with line subsection (ElmLnesec) objects, since
a line is either subdivided into line routes or subsections. Although line routes
may be subdivided into line sections, line subsections and line routes may not be
mixed on the same level.

A new subsection is created by pressing the button in the database browser.

This will present the Element selection dialog, which is set to the default element:
• In case of a line: a line route or line subsection object.
• In case of a line route: a line subsection object.

The third possibility is to select a line type, which makes it possible to store the
line type in the line element.

As soon as a line or line route is subdivided, its length is calculated as the sum
of the line sections and routes. The ”Length of Line” field in the edit dialog (see
Fig. 8.10) of the line itself will thus be disabled when the line is split.

8.4 Characteristics, Scales and Triggers

In any power electrical system there are two means in which the system
changes. Firstly by topological changes where new equipment is added or
where the system components are changed or upgraded.

Secondly, loads will change over time, perhaps daily, as loads peak and slump
through the day, or perhaps seasonally. Similarly, the rating values for
transformers and conductors may vary with temperature.

In PowerFactory any parameter may be assigned a range of values that will be

selectable by date and time, or by some user defined trigger, such as ambient
temperature, temporary overload limit, and so forth.

Such ranges of values are known as characteristics in PowerFactory. The

range of values may be in the form of a one dimensional vector, or a
two-dimensional matrix. The assignment of a characteristic may be made
individually to a parameter, or to a number of parameters by using a reference to
a characteristic. Studies that utilise characteristics are also known as parametric
studies.

Handling of Power Factory 8-165

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

The parametric techniques available in the PowerFactory use the flexible

generic ‘characteristic vector’ (ChaVec) or the generic ‘characteristic matrix’
(ChaMat). Both these characteristics use some sort of scale against which the
parameter is varied. Four kinds of these parameter scales are available:
Continuous Scale A continuous function, such as a temperature scale from 0
to 45 degrees.

Discrete Scale A discrete ‘case’ function, such as ’Temporary Overload’ and

Emergency Overload.’
Continuous Time Scale A continuous time dependent function
Discrete Frequency Scale A continuous frequency dependent function

When the scale is created a means to ’set’ the scale, and hence the parameter
to the corresponding value, is required. This is called a trigger.

When a scale is created, in the ”Scale” folder inside the library folder by default,
a trigger is simultaneously and automatically created in the active study case
folder.

When this trigger is edited and a ’current’ value set (the triggers are accessed by
pressing the button in the main toolbar) the scale is set and the parameter
value is changed.

When a different study case is activated, or a new study case is created, and a
load flow is performed, all relevant triggers are copied into the study case folder
and may be used in the new study case.

N OTE : When a characteristic is created by right clicking a parameter field this

characteristic is only visible from this parameter field itself and cannot
be copied to another parameter field. To use a characteristic for several
parameters create these characteristics in a common folder of your
project and use the menu option New Characteristic →Reference....
See the section 8.5

A characteristic for a parameter is created by right clicking the parameter in an

edit dialog. This presents the various options for creating a characteristic, as
shown for the active power settings of a general load object in Fig. 8.12.
If no other characteristics have been defined for the parameter yet, the pop up
menu will allow the New Characteristic option. This option will open a second
menu where the user may then:
• create a new scalar value
• create a discrete time characteristic
• create a new one-dimensional vector characteristic

Handling of Power Factory 8-166

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.12: Creating a Parameter Characteristic

• create a new two-dimensional matrix characteristic

• use an existing characteristic by reference.

Selecting the Reference... option presents a browser window and the user must
then select a pre-defined characteristic.

If one or more characteristics have already been defined for the parameter, the
pop up menu will show options to edit or delete existing characteristics or to
create another new one. The creation of these characteristics are described in
detail in the following sections.

8.4.1 Creating a Scalar Value

Scalar characteristics are used when a parameter should vary according to a
mathematical relationship, with reference to a scale value. In the Fig. 8.13 the
relationship ”2x + 3” has been defined, and a scale (only the *.TriVal scale object
may be used here) has been chosen, where ”x” refers to the scale variables.
Thus, if the ’Global Temperature’ scale has been set to 15 deg by the trigger
then the parameter that this characteristic is applied to will thus be multiplied by
2 ∗ 15 + 3 = 33

8.4.2 Creating a Discrete Time Characteristic

The discrete time characteristic uses an internally defined series of time scales
that are convenient to use in order to define the characteristic. The user simply
selects a scale and enters the corresponding values.

Handling of Power Factory 8-167

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.13: the Scalar Characteristic dialogue

The ”Usage” field at the bottom of the characteristic dialogue specifies how the
values entered in the ”Values” column will be applied to the parameter that the
characteristic is associated to.
Relative in % will multiply the parameter by the percentage value

Relative will multiply the parameter by the value

Absolute will replace the current parameter value by the absolute value
provided

A graph showing the values plotted against the scale can be seen on the
”Diagram” tab.

8.4.3 Creating an one-dimensional vector characteristic

When using a characteristic such as this one the user must also define a scale
to plot the values to. The dialogue for the characteristic is shown in Fig. 8.14.
The nature of the characteristic depends on the kind of scale that is selected. All
scales will have a range of values or cases which will be shown in the column to
the left of the ”Values” column [1]. Whatever appears in this column is
determined by the scale that has been chosen. The scale may have already
have been created or will need to be created (tip: use the “New Object” button
when selecting a scale to create a new scale and read more about scales in
the sections following).

The user now enters the range of values for the parameter [3].

The ”Usage” field at the bottom of the characteristic dialogue [4] specifies how
the values entered in the ”Values” column will be applied to the parameter that
the characteristic is associated to.
Relative in % will multiply the parameter by the percentage value

Handling of Power Factory 8-168

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.14: the Vector Characteristic dialogue

Relative will multiply the parameter by the value

Absolute will replace the current parameter value by the absolute value
provided

Interpolations between the values are determined by the setting in the

”Approximation” field [5]. A graph showing the values plotted against the scale
can be seen on the ”Diagram” tab [7].

8.4.4 Creating a two-dimensional vector characteristic

When using a characteristic such as this one the user must also define two
scales that will be used to plot the values against. The dialogue for the
characteristic is shown in Fig. 8.15.
The nature of the characteristic depends on the kinds of scale that are selected.
The first scale, that for columns [1], must be a discrete scale. The scale for rows
may be a discrete or continuous scale [2]. These scales may have already have
been created or will need to be created (tip: use the “New Object” button

Handling of Power Factory 8-169

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.15: the Matrix Characteristic dialogue

when selecting a scale to create a new scale and read more about scales in the
sections following).

The ”Usage” field at the bottom of the characteristic dialogue [3] specifies how
the values entered in the ”Values” column will be applied to the parameter that
the characteristic is associated to.

Relative in % will multiply the parameter by the percentage value

Relative will multiply the parameter by the value

Absolute will replace the current parameter value by the absolute value
provided

Interpolations between the values are determined by the setting in the

”Approximation” field [4]. A graph showing the values plotted against the scale
can be seen on the ”Diagram” tab [7].

A column calculator can be used to calculate the column values, as a function of

other columns. This is done by pressing the C ALCULATE ... button [5]. In the

Handling of Power Factory 8-170

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

example of Fig. 8.16, the first column is calculated as the average of the other
columns. The result is shown in Fig. 8.17.

Figure 8.16: Calculating column values

Figure 8.17: Result of a column calculation

Once the values have been entered and the triggers have been set the ”Current
Value” field will show you what the value that will be used to multiply the
parameter is.

8.4.5 Creating a Discrete Scale

A discrete scale is a list of cases. These cases are each defined by a short text
description. The scale dialog offers a text window in which each line defines a
new case. See Fig. 8.18.
As soon as at least one case has been defined, the trigger field will be enabled.

Creating a Discrete Parameter Characteristic

Handling of Power Factory 8-171

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.18: Example of a Discrete Scale

A discrete parameter characteristic is created by selecting a discrete scale. The

cases defined by that scale will automatically show in the list. See Fig. 8.19
where three cases (’No Ship’, ’One Ship’, ’Two Ships’) are defined.

Figure 8.19: Discrete Parameter Characteristic

The approximation field and accompanying polynomial degree field will be

disabled because interpolation cannot be performed for discrete scales. The
current percent value is shown, according to the case that is currently active .
The diagram page for the discrete characteristic shows a bar graph for the
available cases. See Fig. 8.20 for an example. The bar for the case that is
currently active is coloured black.

Handling of Power Factory 8-172

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.20: Discrete Characteristic Diagram

8.4.6 Creating a Continuous Scale

A continuous scale defines a list of ‘X’ values for which we may define ‘Y’ values
in a parameter characteristic. The trigger may take any value, even values
outside the X range. The ‘Y’ values in the characteristic will be interpolated for
the trigger value. The values in the ‘X’ scale must be rising.

An example is shown in Fig. 8.21 where six temperature values are defined.

Creating a Continuous Parameter Characteristic

A continuous parameter characteristic is created by selecting a continuous
scale. The ‘X’ values defined by that scale will automatically show up in the list,
together with their unit.

The scale ‘X-Y’ points will define a curve which is used to approximate ‘Y’ values
for trigger values in between, or even outside, the ‘X’ values. Various
approximation functions are available:
• Constant: holds the Y-value in between X-values

• Linear: uses a linear interpolation.

• Polynomial: uses a polynomial function with user defined degree.

• Spline: uses spline function

• Hermite: uses a Hermite interpolation

Handling of Power Factory 8-173

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.21: Example of a Continuous Scale

The approximation curve will be shown in the diagram page. Examples of these
approximation curves are shown in Fig. 8.22.

Figure 8.22: Approximated Characteristics

Handling of Power Factory 8-174

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

The interpolated Y-value may vary considerably between approximation

functions. This is shown in Fig. 8.22 where the linear and constant
approximations are drawn on top of each other. The black crosses, which have
been encircled in Fig. 8.22 for clarity, show the trigger setting and the resulting
different Y-values.

8.4.7 Creating a Time Scale

A time scale is a special kind of continuous scale that uses the global time
trigger of the active study case (a limited version of this scale is automatically
created when a ”Discrete Time Characteristic is created).

The unit of the time trigger is always an unit of time but may range from seconds
to years. This means that changing the unit from minutes to hours, for instance,
will stretch the scale 60-fold. The units ‘s’, ‘m’, and ‘h’ are respectively, the
second, minute and hour of normal daytime.

Fig. 8.23 shows an example where four equidistant moments in a year have
been created.

Figure 8.23: Time Scale

Setting the Time Trigger

The trigger of a time scale may be defined locally, although this method is
obsolete. The recommended practice is to use the time trigger of the active
study case. This time trigger may be accessed by pressing the button on
the main toolbar. This presents the SetTime object, as shown in Fig. 8.24.
The buttons in Fig. 8.24 have the following meanings:

Handling of Power Factory 8-175

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.24: The Time and Date setting object

Ignore Time Trigger all characteristics that use time scales will be set to their
100% entered value.

OK Closes the dialogue and sets the study case time trigger

Cancel Closes the dialog without setting or saving anything.

Descript.>> Opens the description page.

Date Sets the date to today as taken from the local PC.

Time Sets the time to now as taken from the local PC.

Creating a Time Characteristic

A time dependent parameter characteristic is created in exactly the same way as
creating a continuous parameter characteristic. See section 8.4.3, page 8-168.

8.4.8 Importing a Characteristic from an Existing File

When a series of data is available in an external file, such as an Excel file, or tab
or space separated file this data may be utilised as a characteristic if the
”Parameter Characteristic from File” (ChaVecfile object is used.

Handling of Power Factory 8-176

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

The external file must have the scale column for the data series in column 1.

Once the input data dialogue has been generated (see Fig. 8.25) a scale and
trigger must be set [1] and the link to the existing data file is created [2].

The column field [3] is used for specialised purposes and should generally be
left at the default figure of ’1’.

The factor fields, [4] and [5], may be used to adjust or convert the input data.
The data contained in column 2 of the external file will be adjusted by y=ax+b
where ”x” is the data in the external file and ”y” is what will be loaded into the
characteristic.

The ”Usage” field at the bottom of the characteristic dialogue [6] specifies how
the values entered in the ”Values” column will be applied to the parameter that
the characteristic is associated to.

Relative in % will multiply the parameter by the percentage value

Relative will multiply the parameter by the value

Absolute will replace the current parameter value by the absolute value
provided

Interpolations between the values are determined by the setting in the

”Approximation” field [7]. A graph showing the values plotted against the scale
can be seen on the ”Diagram” tab [8].

Once the file link has been set press the U PDATE button [9] to upload the data
from the external file to the characteristic.

8.5 Handling Scales and Characteristics

If only a few characteristics for some parameters are to be defined, the

characteristic may be directly defined using the menu options that are presented
when right clicking a parameter field. Characteristics that are defined in this
manner are stored in that object. This characteristic is normally hidden in the
database browser.

If you wish to apply the same characteristic to several parameters then it is

better to define the characteristic explicitly beforehand. Parameters may then be
’referred’ to the characteristic. This is what is meant by the New Characteristic
→Reference... option when right clicking a parameter.

Handling of Power Factory 8-177

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.25: The Parameter Characteristic from File dialogue

All ‘direct’ characteristics, and all references to characteristics are normally

hidden in the database browser to prevent accidental direct manipulation. A
special display mode is available in the database browser to check and edit the
characteristics for whole classes of objects. This ‘Scales’ mode must be enabled
in the User Settings, on the “Functions” tab. An example of a browser showing
the ‘Scales’ tab is shown in Fig. 8.26 (remember that the bowser must be in
’detail’ mode to see these tabs).
The browser in ‘Scales’ mode shows all characteristics defined for the displayed
objects, together with the original value and the current value as determined by
the characteristic. In the example, a one-dimensional characteristic called
’Loading Characteristic 1’ has been used for the load ’L-Baker’. The trigger has
set the scale to a value of 50% and thus the ”Current Value” is 0.025 which is
50% of the input value of 0.05. The current values will be used in all calculations.

The browser ‘Scales’ mode is not only used to quickly inspect all defined
characteristics, but may also be helpful in defining new characteristics, or in
selecting references. Fig. 8.27 shows the context sensitive menu that appears
when a characteristic field is right clicked.
The option Select Characteristic..., shown in Fig. 8.27, is used to define

Handling of Power Factory 8-178

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.26: Browser in ‘scales’ mode

Figure 8.27: Managing Characteristics

references to a characteristic and may also be used to create a range of

characteristics. This is shown in Fig. 8.28 where a reference is defined for three
loads at once.
The ”Scales” tab of the browser will only show the ”Characteristic” column when
at least one of the objects has a characteristic defined for a parameter. It is thus
necessary to define a characteristic for one object prior to using the browser,
when the user would like to assign characteristics, for the same parameter, for a
range of other objects. To define a ‘High-Low’ loading characteristic for all loads,
for instance, can thus be done by performing the following steps.

Create a discrete scale in the grid folder

Handling of Power Factory 8-179

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.28: Selecting a range of characteristics

Create a vector characteristic using this scale in the grid folder

Edit one of the loads, right click the active power field and assign the vector
characteristic to the relevant parameter

Open a browser with all loads, activate the ‘detail’ mode and select the
”Scales” tab

Select the characteristic column (right click →Select Column) and then
right click the selected column

Use the Select Characteristic... option and select the vector characteristic

8.6 Feeders and Feeder Objects

When analysing a system it is often useful to know where the various elements
are receiving their power supply from. We can of course discern this by looking
at the breaker status’ and the flow of power, however, it would be convenient if
the program could indicate this automatically. In PowerFactory this is achieved
by using Feeder Definitions. A feeder is defined at a line or transformer end
and the feeder definition algorithm then searches the system from the feeder
definition point to determine the extent of the feeder.

The feeder ends when:

• an open breaker is encountered

• the end of a line of supply is encountered

• a higher voltage is encountered

Handling of Power Factory 8-180

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Once a feeder has been defined it may be used to scale loads, according to a
measured current or power, to create voltage profile plots, to select particular
branches and connected objects in the network and for many other tasks.

See also Voltage Profile Plots, section 24.4, page 24-472

A feeder is created or defined by right-clicking on a cubicle (that is, when the

cursor is held just above the breaker in the single line diagram) and selecting
Define →Feeder..., as shown in Fig. 8.29.

Figure 8.29: Creating or defining a new feeder definition

Once the feeder has been defined a feeder dialog pops up, as shown in Fig.
8.30

8.6.1 Position and Colour

Name The feeder may be named as required

Cubicle Indicates the position of the feeder. The direction of the feeder is away
from the busbar/terminal towards the connected branch. The direction of
the feeder in Fig. 8.29 is thus downwards.

Zone Indicates the zone to which the feeder belongs. A feeder is assigned to
the zone of the local busbar/terminal.

Colour sets the colour that the feeder will be shown in when the Feeder
Definitions colouring mode is engaged.

Handling of Power Factory 8-181

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.30: The Feeder Dialog

8.6.2 Terminate Feeder when encountering higher Voltage

Levels
A feeder will, by default, terminate when a higher voltage level is encountered,
however, this may not always be desirous. This may be prevented by
un-checking this option. The feeder will now continue ’past’ a higher voltage
level and may be terminated at a user defined cubicle if desired. To manually
terminate a feeder right click a branch element above the breaker and select Edit
Cubicle. The dialogue shown in Fig. 8.31 will be presented, and the Terminate
feeder at this point option may be checked.

8.6.3 Load Scaling

In any system some loads values may be accurately known whilst others are
estimated. It is likely that measurement points exist for feeders in the system as
well, and thus the power that is drawn through this feeder is also known.

The load scaling tool assists the user in adjusting these estimated load values by
scaling them to match a the known feeder power or current that has been
measured in the real system.

To use this tool first define which loads may be scaled by enabling the Adjusted
by Load Scaling option on the Load Flow tab of the load dialogue. All of the
loads in a feeder may also be quickly viewed by editing the feeder from the

Handling of Power Factory 8-182

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

Figure 8.31: Manual termination of a feeder

feeders folder (see 8.6.4).

Load scaling is now performed by the load-flow calculation function when:

a. At least one feeder is defined with load scaling according to a current or

power.

b. The option Feeder Load Scaling is enabled in the load-flow command

dialog (basic options).

c. At least one load exists in the feeder area for which

– A change in operating point affects the load-flow at the feeder position

– The option Adjusted by Load Scaling has been enabled.

The load-flow calculation will then adjust the scaling of all adjustable loads in the
feeder areas in such a way that the load flow at the feeder equals the current or
power setpoint.

When the user is satisfied with the scaling the scaling factors can be updated to
the database by pressing the button.

The feeder setpoint is influenced by the zone scaling. This means that the
current or power flow as calculated by the load-flow could differ from the setpoint
in the feeder dialog when the busbar where the feeder is defined is part of a
zone.

Handling of Power Factory 8-183

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

For instance, a feeder has a setpoint of 1.22 MVA. The busbar is in a zone and
the zone-scale is set to 0.50. The flow at the feeder position will thus be 0.61
MVA.

8.6.4 The Feeders Folder

All feeder objects [2] are stored in the special IntFeeder folder, ”Feeders” [1], in
the active project (see Fig. 8.32). This folder is created automatically when the
first feeder in a project is defined.

The colouring command of the single line graphics looks for the feeder definitions
in the Feeders folder. See section 7.8.1, page 7-143 for more information.

Figure 8.32: Accessing and using the feeder dialogue

Once the feeder has been accessed from the feeder folder by double clicking a
feeder object [3] all of the elements in the feeder may be listed in a browser by
pressing the E LEMENTS button [4].

Handling of Power Factory 8-184

DIgSILENT PowerFactory Creating and Using Simulated Power Systems

When the S ELECT button [5] is pressed all of the elements in the feeder will be
marked in the graphic.

8.6.5 Zones
Elements in a system may be allocated to a zone and the graphic may be
coloured to show these zones. All of the loads may be quickly scaled in a zone
and the elements of a zone may be listed in a browser format for gang editing.

Zones are created by multi-selecting elements and right clicking →Define...

→Zone... or Add to... →Zone... when a zone(s) have already been defined.

As with feeders a Zone folder is automatically created when the first zone is
defined. Zones may be accessed and edited from this folder.

Handling of Power Factory 8-185

DIgSILENT PowerFactory Performing Calculations

Chapter 9

Performing Calculations

PowerFactory offers a wide variety of calculation commands, of which the

a Load-flow calculations

b Short-circuit calculations

c Transient simulations
are the most important.

Calculations are performed using data as defined by the active study case (see
6.0.8 for more information on study cases). Therefore a study case, having at
least one Grid or System Stage, should be activated prior to starting any
calculation function. See Project Management, section 6, page 6-93 for more
information.

The main menu calculation buttons will be enabled as soon as a correct study
case is active. These buttons will pop up the default calculation command
dialogs which are used to configure and execute a calculation. The default
calculation command objects are stored in the active study case.

The main toolbar shows the following calculation buttons.

Calculate Load-Flow

Calculate Short-Circuit

Break

Reset Calculation

Other command buttons are grouped together in sub-toolbars which are

selected by the toolbar selection list:
The toolbar selection button

Stability calculation commands

Reliability, sensitivity and various special calculation commands
Data acquisition commands

Handling of Power Factory 9-186

DIgSILENT PowerFactory Performing Calculations

Harmonics calculation commands

Optimal capacitor placement commands

9.1 Edit relevant Objects for Calculation

The button is used to gather and show all objects considered by the study
case, and which are of a certain class, in a browser in order to inspect their data
or to edit them.

Pressing the button will present a menu listing the icons of all classes of
objects currently used for the calculations, as depicted in Fig. 9.1. Pressing a
class icon will pop up an object filter browser, filled with all the objects of the
selected class, which are considered by the calculation.

Pressing the line icon, for instance, will open a filter browser which contains a list
of all lines. Pressing the transformer icon gives the list of all transformers, etc.
The filter browser can be used to inspect, select or edit selected objects.
Normally, the filter browser is closed after performing any of these actions. It is
possible to open more filter browser at the same time, by repeatedly pressing
the button.

Figure 9.1: Selecting calculation relevant objects

9.2 Results

Following calculations some messages are printed to the output window. These
generally consist of errors, warnings or information that may be useful when
interpreting the calculated data. The load-flow calculation function, for example,
will provide the following message when the power system under analysis is has
2 separated areas:
DIgSI/wrng - 1 area(s) are unsupplied.
DIgSI/info - Grid splitted into 2 isolated areas

Handling of Power Factory 9-187

DIgSILENT PowerFactory Performing Calculations

More extensive output is given in the output window, for example, by the (N-1)
outage calculation, which is an option in the load-flow command dialog. The
output given by that calculation is a list of load-flow calculations that were
performed, each with a table in which the element on outage and all overloaded
elements are provided.

The usual place, however, to visualise load-flow or short-circuit calculation

results is in the single line graphics, or the data manager and object filter (when
tabulated results are required). The results on view may configured using the
highly flexible, user-definable, variable sets. These are accessed from the
results boxes or flexible data tab. See section 7.8.5, page 7-146, and section
5.10, page 5-64, for more information.

Some calculations offer additional results in the form of bar-graphs, vector

diagrams or other graphical output. All such outputs are presented by so-called
virtual instruments, which are placed on a virtual instruments page in the current
graphics board.

9.3 Comparisons Between Calculations

At many stages in the development of a power system design, the differences

between certain settings or design options become of interest.

For a single calculation, the ‘absolute’ results are shown in the single line
graphics. The variables that are shown may be specified by the user by altering
the result-box definitions.

When comparing two cases, the results of the first calculation are ’frozen’. All
subsequent calculations will then show their results as deviations from the first
calculation made. The subsequent calculation results are stored together with
the first result. This allows the user to re-arrange the comparisons as desired by
pressing the button (see the next section).

The differences between cases are coloured according to the severity of the
deviation, making it possible to recognise the differences between calculation
cases very easily. The colouring and severity ranges may be set in the Edit
Comparing of Results... menu option, found by pressing (see the next
section).

A comparisons between cases is made as follows:

• Calculate the first case by activating a certain calculation case and, for
example, calculating a load-flow.

Handling of Power Factory 9-188

DIgSILENT PowerFactory Performing Calculations

• Press the button on the main toolbar. This will store the base case
results and prepares to store the results of forthcoming calculations.

• If relative results are also required for a particular calculation report, in a

formatted report, that report has to be generated for the first case by
pressing the button on the main toolbar and selecting the required
report. This step is necessary to let the comparison manager know which
parameters are to be compared.

• Change the power system or a calculation setting to create the next case.
Permitted alterations include opening/closing switches, altering load
settings or any other component parameter, changing calculation cases,
adding or deleting elements, etc.

• Repeat the calculations as performed for the first case.

• The result boxes in the single line graphic will now show the percentage
change as compared to the first case. If the calculation report, as
generated for the first case, is generated again, it will also show relative
results.

• Make and calculate the other cases. After each calculation, the
comparison to the first case is shown.

9.3.1 Editing a Set Of Comparison Cases

The set of calculated comparisons may be edited to select the cases which are
to be compared to each other or to set the colouring mode. When the button
on the main toolbar is pressed, the Compare dialog will open. See Fig. 9.2.
With the Compare dialog, the two cases which are to be compared can be
selected. Furthermore, a list of colours may be set which is then used to colour
the results displayed in the result boxes, according to certain levels of
percentage change.

9.3.2 Update Database

In PowerFactory input (data that has been entered by the user) and output
(parameters that have been calculated) data is kept separate and output data,
such as the new tap positions following an automatic tap adjustment calculation,
does not overwrite the settings that the user originally entered, unless the user
specifically commands this, using the button on the main toolbar.

N OTE : The corresponding input parameters of the database will be overwrit-

ten by the calculated values.

Updating the database may be performed for:

Handling of Power Factory 9-189

DIgSILENT PowerFactory Performing Calculations

Figure 9.2: The Compare dialogue

• Scaling factor of loads

• Transformer taps

• Capacitive Steps of Shunts/Filter

• P,Q of Loads

• P,Q of asynchronous machines

Example:
A load-flow is calculated with the options ”Automatic Tap Adjust of Transformers”
and ”Automatic Shunt Adjustment” enabled. The calculated tap and shunt
positions may be seen in the single line diagram, but it will be noticed that the
input data parameter in the element data dialogue is as originally entered. The
button is clicked, and the input parameters are now overwritten by the
calculated values found on the single line diagram.

Handling of Power Factory 9-190

Steady-State Power System
Analysis
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory Load-Flow Calculations

Chapter 10

Load-Flow Calculations

A load-flow calculation may be initiated by

• pressing the button on the main toolbar.
• selecting the Calculation →Load-Flow option on the main menu

An example of the load-flow command dialog is shown in Fig. 10.1.

Figure 10.1: ComLdf Command Dialogue

Please refer to the section Load-Flow Calculations in the Technical References

for a detailed description and the theory behind the load-flow calculations.

In the following pages the options that may be set for the load-flow calculation
will be explained. Following this, some tips on what to do if your load-flow is not
solving are presented.

Steady-State Power System Analysis 10-192

DIgSILENT PowerFactory Load-Flow Calculations

10.1 Basic Options

Network Representation
Balanced, positive sequence Performs load-flow calculations for a one-phase,
positive sequence network representation, valid for balanced symmetrical
networks. A balanced representation of unbalanced objects is used.

Unbalanced, 3 Phase (ABC) Considers load unbalances (if the user has
enabled the unbalanced option for the load in the case of ElmLod objects,
or if other unbalanced elements exist) for the load-flow calculation, using a
full 3-phase, unbalanced network representation. If no load unbalances are
defined in the loads and this option is selected, the results will reflect a
normal load-flow calculation. Unbalanced elements are also considered
using all three sequence networks (positive, negative and zero).

Reactive Power Control

Automatic Tap Adjust of Transformers adjusts the taps off all transformers
that have the option Automatic Tap Changing enabled on the Load-Flow
tab.

Automatic Shunt Adjustment adjusts the steps of all switchable shunts that
have the option Switchable enabled on the Load-Flow tab.

Consider Reactive Power Limits Ensures that generator reactive power

outputs remain within the limits defined in the generator element. A
message will be issued when the generator reaches these limits. When
disabled, the reactive power outputs limits may be violated, in which case a
warning is issued.

Load Options
Consider Voltage Dependency of Loads Voltage dependency of loads that
have voltage dependency factors kpu and kqu (as set on the Load-Flow
tab in the load type) set will be enabled.

Feeder Load Scaling Scales loads marked Adjusted by Load Scaling in the
load-flow tab of their element data to match the total load specified in the
Load Scaling option of the feeder object.

Consider Coincidence of Low-Voltage Loads Calculates a ’low voltage

load-flow’, where load coincidence factors are considered, so as to
produce maximum branch currents and maximum voltage drops. Since
coincidence factors are used the result of low voltage analysis will not obey
Kirchhoff’s current law.

Steady-State Power System Analysis 10-193

DIgSILENT PowerFactory Load-Flow Calculations

Scaling Factor for Night Storage Heaters is the factor by which the night
storage heater power (as found in ”Low Voltage load” elements - ) is
multiplied for all low voltage loads.

10.2 Active Power Control

Active Power Control

as Dispatched the total power unbalance will be controlled by the slack
generator/grid.

according to secondary Control generators/grids contribution towards the

total power unbalance will be according to the secondary controllers
defined in the system.

according to Primary Control generators/grids contribution towards the total

power unbalance will be according to the primary controller droop settings.

according to Inertias generator/grid contribution towards the total power

unbalance will be proportional to its mechanical inertia.

Consider Active Power Limits active power limits for generators, as defined by
the generator element data, will be applied. A message will be issued
when the generator reaches these limits. When disabled, the active power
outputs limits may be violated, in which case a warning is issued.

10.3 Outputs

Show Verification Report Produces a table in the output window with a list of
overloaded objects and voltage violations, according to the values
specified in ”Check devices”.

Show Convergence Progress Report will print detailed reports concerning

load-flow calculations during the iterations, which may be used to solve
convergence problems.

Calculate Power at Risk Calculates the SPAR (System Power At Risk)

parameter, which is shown in the “Total System Summary Report”. The
SPAR equals the minimum amount of power that will be shed in order to
make the highest branch loading equal to the ”Max. Loading of Edge
Element”. The SPAR calculation uses a linear optimisation technique to
calculate the least power that may be shed in order to alleviate all

Steady-State Power System Analysis 10-194

DIgSILENT PowerFactory Load-Flow Calculations

overloads. This minimum power that will be shed is called the ”Power At
Risk”.

Output is a pointer to the report definition that will be used. The arrow can be
pressed to edit or inspect the report settings.

10.4 Low Voltage Analysis

The following applies to all LV loads (ElmLodlv) and partial LV loads on lines
(ElmLodlvp):

Definition of Fixed Load per Customer

The fixed load is the non-stochastic part of the load, which is not subject to
coincidence factors.

Definition of Variable Load per Customer

The Max. Power per Customer is the independent maximum. Multiplied by the
coincidence factor, this gives the ”Average Power”, which is used in the load-flow
calculations, as the load-flow algorithm does not implicitly consider the
coincidence factors.

Voltage Drop Analysis

Choose between Stochastic Evaluation or Maximum Current Estimation.

10.5 Advanced Options

Load-Flow Method
Either a Newton Raphson Current iteration, a classical Newton Raphson, or a
linear approximation method can be selected for the load-flow calculations. The
classical method is the default method. The current iteration method should be
used for networks that have large unbalances or power electronic devices.

Steady-State Power System Analysis 10-195

DIgSILENT PowerFactory Load-Flow Calculations

Load-Flow Initialisation
No Topology Rebuilt Will speed up large sets of consecutive load-flow
calculations. It will not consider a topology rebuild when calculating the
next load-flow. If no topology changes will be made for the system then this
option may be enabled (the Jacobian Matrix thus stays the same and must
not be rebuilt which results in a faster calculation).

No Initialisation (no flat start) Speeds up large sets of consecutive load-flow

calculations. It will prevent the re-initialisation of the calculated results by
the input data.

Consideration of transformer winding ratio sets the manner in which voltage

initialisation takes place at nodes. When the transformer ratios are
considered the nominal winding ratio is used to multiply the ’supply’ side
node p.u. voltage in order to arrive at a initialisation voltage for the
load-flow. Turning this option on or off can assist in obtaining a
convergence.

Tap Adjustment
Method The direct method will include the tap controller models in the load-flow
calculations (in the internal loop within the Newton-Raphson iterations).
The new tap positions will then be calculated directly as a variable and thus
result after a single load-flow calculation.

The stepped method will calculate a load-flow with fixed tap positions, after
which the required tap changes are calculated from the observed voltage
deviations and the tap controller time constants. The load-flow calculation
is then repeated with the new tap positions, until no further changes are
required. The tap adjustment will then take place in the outer loop of the
iteration.

Min. Controller Relaxation Factor The tap controller time constants are used
in the automatic tap changer calculations to determine the relative speed of
the various tap controllers during the load-flow iterations. The relaxation
factor can be used to slow down the overall controller speeds (factor less
than 1.0, in case of convergence problems) or to speed them up (factor
more than 1.0, for a faster load-flow).

10.6 Iteration Control

Steady-State Power System Analysis 10-196

DIgSILENT PowerFactory Load-Flow Calculations

Max. Number of Iterations for

The load-flow calculation function uses an iterative Newton-Raphson method, for
which the maximal number of iterations may be set. Normal values are a
maximum of 25 iterations for the inner and 20 for the outer loop calculations.

For iteration control you can set

itrlx: Maximum Number of Iterations (typical: 25)

The inner loop of the load-flow is represented by the Newton-Raphson
iteration. The maximum number of iterations is set by this parameter.

ictrlx: Iteration Limit to Recompute Jacobian Matrix (typical: 20)

The outer loop of the load-flow iteration will determine changes in the tap
changer (depending on the tap adjustment method), the reactive power
limits of the generator, etc. These are adjusted in the outer loop and then a
new iteration of the inner loop is started again. The maximum number of
outer loop iterations is set by this parameter.

nsteps: Number of Stairs (typical: 1)

Problematic load-flows with slow or no convergence can be improved by
starting a load-flow calculation for a low load level, and then increasing the
load level in a number of steps. This is achieved by setting the Number of
Stairs to a value larger than one. For example nsteps=3 starts with
load-flow at a load/generation level of 1/3 and the increases the power in 2
further steps to 100%.

Max. Acceptable Load-Flow Error

A higher precision or a faster calculation can be obtained by changing the
maximal allowed errors. The values of either the calculated absolute fault for the
nodes, or the calculated relative faults in the model equations, may be changed.

For iteration control you can set

errlf: Maximum Iteration Error of Nodal Equations (typical: 1 kVA)

erreq: Maximum Error of Model Equations (typical: 0.1%)

Convergence Options
Relaxation Factor A Newton Raphson relaxation factor smaller than 1.0 will
slow down the convergence speed of the load-flow calculation, but may in
some cases result in better convergence.

Automatic Model Adaptation for Convergency. The PowerFactory load-flow

function will always first try to find a solution with the non-linear
mathematical power system models. If such a solution cannot be found,

Steady-State Power System Analysis 10-197

DIgSILENT PowerFactory Load-Flow Calculations

and this option is enabled, an adaptive algorithm will change these models
slightly to make them more linear, until a solution is found. Model
adaptations are reported in the output window.

10.7 Advanced Simulation Options

This page, as shown in Fig. 10.2 is not only important for load-flow but also for
other calculation functions like the transient simulation. Using the following
options i.e. a transient simulation can be sped up when the protection devices
will be neglected in the calculation.

Figure 10.2: Advanced Simulation Options in the ComLdf Command Dialogue

Consider Protection Devices calculates the tripping times for all relays and
fuses that have been modelled. This will also show the load currents in the
overcurrent plots and/or the measured impedance in the R-X diagrams.
Disabling this option will speed up the calculations.

Ignore Composite Elements disables all controller models.

Steady-State Power System Analysis 10-198

DIgSILENT PowerFactory Load-Flow Calculations

The panels ”Considered Models” and ”Ignored Models” are used to disable
specific groups of controller models. Models names can be moved
between panels by double-clicking or by using the arrow buttons.

10.8 Troubleshooting Load-Flow Calculations

In general, if a solution can be found (in other words, the network has a possible
solution) PowerFactory will find a solution. In some cases the user may have
made an error which will not allow a solution to be found, for example, a large
load causing volt drop so high that a voltage collapse results. In the real world
the same problem would be found.

When creating a network for the first time it is best to enter the data for just a
small part or ’path’ of the network and solve the network by calculating a
load-flow. PowerFactory has a data verification process in which certain
checks, such as whether a line is connected between nodes of the same voltage;
correct voltage orientation of transformers, etc, are performed. Error messages
regarding these issues are printed to the output window, listing the element and
error in question. These messages are interactive and the user may:

• right click →Mark in Graphic to show the element on the single line
graphic, or

• double click on the description of the element to present the element

dialogue (’South Grid\MV-K6.ElmLne’ in the example below)

In the following example the messages in the output window state that the line
element called ’MV-K6’, which is found in the ’South Grid’ folder is missing type
data.

DIgSI/wrng - Protection Devices are not considered.

DIgSI/err - ’South Grid\MV-K6.ElmLne’:
DIgSI/err - missing type !
DIgSI/err - last command leads to error(s), see output window !
DIgSI/err - Error in load-flow data!
DIgSI/info - Load-flow calculation not executed

Once these errors have been corrected and the load-flow still does not solve use
the ”Show Verification Report” and ”Show Convergence Progress Report”
options found in the ”Outputs” tab of the load-flow dialogue. These will print
messages to the output window and provide you with clues as to where you may
have problems.

Steady-State Power System Analysis 10-199

DIgSILENT PowerFactory Load-Flow Calculations

At this point you can also colour the graphic to show you low and high voltages
and overloading. This will also provide you with a good idea of where there may
be problems. Look at the undervoltage nodes and overloaded elements and
figure out why they are overloaded; look at load set points, line lengths and line
type data (the impedances may be too high).

N OTE : There are 3 different types of messages that are printed to the output
window; warning, error and information messages. Only error mes-
sages must be corrected for a load-flow to solve. Take note of the
warning messages and evaluate them in terms of your system, these
do not need to be corrected for the load-flow to solve. ”Unsupplied Ar-
eas” mean that a node or branch element has no supply (i.e. a breaker
is open)

If there is still no convergence then set most of the elements out of service and
bring these back one at a time, from the source element ’downwards’,
performing a load-flow each time.

When you have large unbalances, such as when there are a number of single or
dual phase elements, or when you have power electronics elements use the
”Newton Raphson Current Iteration” option in the ”Advanced” tab of the load-flow
dialogue.

Steady-State Power System Analysis 10-200

DIgSILENT PowerFactory Short-Circuit Calculations

Chapter 11

Short-Circuit Calculations

11.1 General Remarks

Short-circuit calculations may be used for different purposes. Therefore

PowerFactory supports different representation and various calculation
methods for the analysis of short-circuit currents.

Network Planning
One application is to check the rating of network equipment at planning stage. In
this case the planner is interested in knowing the expected maximum currents
(for the rating of the components) and the minimum currents (to make sure the
protection concept will work). Short-circuit calculation at planning stage mostly
will use calculation methods that require less detailed network modelling (e.g.
that do not require load information) and will apply extreme-case estimations.
Examples for these methods are the IEC/VDE calculation method and the ANSI
method.

Exact Calculation
A different field of application is the precise evaluation of the fault current in a
specific situation, e.g. to find out if the mal-function of a protection device was a
relay failure or was the consequence of wrong settings. This is the typical
application of exact methods like the superposition method (complete method),
which is based on a specific load-flow situation. This chapter presents the
handling of the short-circuit calculation methods as implemented in
PowerFactory. More information about the background on this topic can be
found in section 11.7.

The short-circuit calculation in PowerFactory is able to perform single faults as

well as multiple faults of nearly unlimited complexity. The handling of
PowerFactory, the different methods and the available options are presented in
the following.

Steady-State Power System Analysis 11-201

DIgSILENT PowerFactory Short-Circuit Calculations

11.2 Starting Single-Fault Short-Circuit

Calculations

A short-circuit calculation can be initiated from the single line graphic by

selecting one or more busbars and/or lines. Right-click the selection to access
the context-sensitive menu. This menu offers the option:
Calculate→Short-Circuit....

When confirming this menu option, the short-circuit command dialogue is

opened. Depending on whether a single element or a group of elements had
been selected before starting the calculation, the setup dialogue is configured in
two possible ways:

• When only one single busbar is selected, and Calculate→Short-Circuit is

chosen, the “Fault Location” reference is set to the selected busbar.

• When two or more busbars are selected and Calculate→Short-Circuit is

chosen, the “Fault Location” reference is set to a so-called “Selection Set”
(Setselect) object, which contains a list of references to the selected
busbars.

An example for the setup dialogue of the short-circuit command dialogue is

shown in Fig. 11.1.
In either case, the options for the calculation can be modified. Please refer to
section 11.6 for a detailed description of the available parameters. It should be
considered, that changing the option “multiple faults” may change the selection
of fault locations and may thus lead to a calculation for locations other than the
busbars selected in the single line graph. After pressing the button Execute, the
calculation is executed and, if successful, the results are shown in the network
diagram. Also a result report is available and may be printed out.

Once a selection of fault locations is made and the short-circuit calculation is

performed, it is easily possible to execute further calculations based on the same
selection of elements. This can be done by the following alternative actions:

• by pressing the button on the main toolbar

• by selecting the Calculation/Short-circuit option on the main menu

The short-circuit setup dialogue then shows the previously selected elements in
the section Fault Location under User Selection.

Steady-State Power System Analysis 11-202

DIgSILENT PowerFactory Short-Circuit Calculations

Figure 11.1: Short-Circuit Setup Dialogue

11.3 Faults on Lines

As described in 11.2 it is not only possible to calculate short-circuits on busbars

and terminals, but also on lines. To calculate a fault on a line, please proceed as
follows:
• Please select the line where the fault should be modelled
• Right-click on that line. The short-circuit setup dialogue opens and lets you
define the distance of the fault (see Fig. 11.2).
• When following the button , you may select if defining the fault location
in % of the line length or in absolute distance.

When a fault on a line is calculated, a box is shown next to the line presenting
the results of the calculation.

Steady-State Power System Analysis 11-203

DIgSILENT PowerFactory Short-Circuit Calculations

Figure 11.2: Setup section for line faults

11.4 Multiple Faults Calculation

To calculate multiple faults, that is the simultaneous occurrence of more than

one fault condition in the network, please do as follows:
• Please select two or more busbars and right-click.
• Please select the option Calculate-Multiple Faults, and confirm. The
short-circuit setup dialogue pops up, containing a pre-set ”Short-Circuit
Event List”. In this pre-set, a 3-phase fault is assumed at all selected
locations. The Multiple Faults option in the short-circuit command dialogue
is activated in combination with the complete short-circuit method.
• Next you will have to adapt the event list to reflect your intended fault
conditions. This is described below in detail.
• Finally, please press Execute to start the calculation.

The short-circuit event list is a special case of the general event list, which
contains the event definitions for dynamic simulations. It therefore contains
information that is not used by the short-circuit, like e.g. the times for each event.
In the application for the short-circuit special faults, these are set to zero.

To edit the list of events, please proceed in the following way:

• Please open the object for the short-circuit events. You have several
alternatives to access the list of events:
– In the short-circuit dialogue in the section Fault Locations, press the
button behind the Short Circuits. To access the events stored
within this object, please press C ONTENTS (see figure Fig. 11.3).
– Press the button on the main toolbar.
– Open the (IntEvtshc) object in a database manager.

• A window is opening up that presents you the list of events. When you
double-click on one line, a window with the description of the event is
opened.

Steady-State Power System Analysis 11-204

DIgSILENT PowerFactory Short-Circuit Calculations

Figure 11.3: Accessing the Event List

• You now can modify the settings of the short-circuit event. The list of fault
locations consists of a “Short-Circuit Event List” (IntEvtshc) object, which
holds one or more short-circuit events (EvtShc). Each of these events has
a reference to a fault location (a busbar) and carries a description of the
fault type. An example is shown in Fig. 11.4.

Figure 11.4: A Short-Circuit Event

N OTE : To re-use the event list (IntEvtshc) later, this object can be copied
to a user-defined folder in the database manager. This will prevent it
from being modified during the following calculations. When repeating
the calculation with the same configuration, the reference in Calculate-
Multiple Faults can be set to this object.

Steady-State Power System Analysis 11-205

DIgSILENT PowerFactory Short-Circuit Calculations

11.5 Short-Circuit Calculation with User-Defined

Element Sets

The easiest way of calculating several short-circuits one by one and of

combining the results in one diagram is to enable the option Fault Location - At
All Busbars and terminals.

It however may be considered useful to calculate S/C currents for a sub-set of

busbars, e.g. all busbars with generation connected. When two or more busbars
are selected in the single line graphic and Calculate Short-Circuit is chosen, a
“Selection Set” (Setselect) object is created automatically and used for the
calculation. This Selection Set is a list of references to network elements.

In the case of a selection of fault locations, this is a list of busbar objects. No

fault type is specified, only the location. You may copy this selection into a
user-defined folder within your project, so that it becomes a permanent selection
for later re-use.

11.6 Short-Circuit Calculation Options

11.6.1 Basic Options (All Methods)

Calculation Method
PowerFactory provides the following calculation methods for short-circuit
calculation:

• According to the German VDE standard

• According to the International IEC standard

• According to the American ANSI/IEEE standard

• A ’complete’ method which considers the pre-fault load-flow results

The specific options for the selected methods are discussed in section 11.6.1.

Fault Type
The following fault types are available:

• 3-Phase Short-Circuit

Steady-State Power System Analysis 11-206

DIgSILENT PowerFactory Short-Circuit Calculations

• 2-Phase Short-Circuit

• Single Phase to Ground

• 2-Phase to Ground

• 1-Phase to Neutral

• 1-Phase Neutral to Ground

• 2-Phase to Neutral

• 2-Phase Neutral to Ground

• 3-Phase to Neutral

• 3-Phase Neutral to Ground

The fault types with neutral conductor only make sense when the lines are
modelled using neutral conductors.

Output
A text report is automatically written to the output window when the On option is
enabled. The reference to the report generating command can be used to select
which type of report will be printed out. Its name is written in blue colour behind
the button .

Fault Location
Either the option At all Busbars and Terminals is enabled, or a reference must be
given to either

• a single busbar object

• a fault event container (an IntEvtShc object)

• a selection of busbars (a SetSelect, see Creating a List of Objects,sec.

5.18.2, page 5-91).

Multiple faults will only be calculated for the complete method, when the option
Multiple Faults is enabled. In other cases when more than one fault location has
been selected, a sequence of short-circuit calculations is performed, once for
each fault location.

Steady-State Power System Analysis 11-207

DIgSILENT PowerFactory Short-Circuit Calculations

11.6.2 Verification
The verification option will, when enabled, write a loading report to the output
window which shows the various maximum and calculated currents for rated
devices. rated devices are, for instance,

• Lines which have a rated Short-Time Current at their line type which is
larger than zero.

• Breakers or coupling switches which have a type with a valid rated current.

11.6.3 Basic Options (IEC/VDE Method)

Published
This offers a sub-selection for the method, where the version of the used
standard can be selected by the year in which it was issued. The most recent
standard is 2001, however 1990 is still available for the verification of
documented results.

Calculate
The pull-down list offers the choice between the minimal or maximal short-circuit
current.

Max. Voltage tolerance for LV systems

In accordance with the IEC/VDE standard, this voltage tolerance is used to
define the respective voltage correction factor c. The voltage tolerance is not
used when a user-defined correction factor is defined.

Fault Impedance
The fault impedance is defined as the reactance and resistance of the fault itself
(i.e. the impedance of the arc or of the shortening path).

Short-Circuit Duration
The value for the Breaker Time is used to calculate the breaking current of a
circuit breaker. The value for the Fault Clearing Time (Ith) is required for the
equivalent thermal current.

Steady-State Power System Analysis 11-208

DIgSILENT PowerFactory Short-Circuit Calculations

11.6.4 Advanced Options (IEC/VDE method)

The advanced short-circuit options are used to tune the short-circuit
calculations. It is recommended to make yourself familiar with the IEC/VDE
standard read before modifying these options. A brief summary of the standard
can be found in the technical reference of the short-circuit.

Grid Identification
The calculation of the factor κ is different for meshed or radial feeding of the
short-circuit. Normally PowerFactory will automatically find the appropriate
setting. The option always meshed will force a meshed grid approach.

c-Voltage Factor
The standard defines the c-voltage factor to be used for the different voltage
levels. In special cases the user may want to define himself the correction factor.
In this case please activate the box “Userdefined”, then you can enter a specific
c-factor.

Asynchronous Motors
The influence on the short-circuit currents of the asynchronous motors may be
always considered, automatically neglected when possible, or neglected when
possible and confirmed by the user.

Conductor Temperature
When activating this option, the initial (pre-fault) conductor temperature can be
set manually. This will influence the calculated maximum temperature of the
conductors, as caused by the short-circuit currents.

Decaying Aperiodic Component

Allows for the calculation of the DC current component for which the decaying
time has to be given. According to the IEC/IEC standard, the methods B, C and
C’ can be selected.

Peak-Shc Current (Meshed network)

In accordance with the IEC/VDE standard, the following methods for calculating
kappa can be selected:

method “B” : uses the ratio R/X at the short-circuit location.

Steady-State Power System Analysis 11-209

DIgSILENT PowerFactory Short-Circuit Calculations

method “C(1)” : uses the ratio R/X calculated at a virtual frequency of 40% of
nominal frequency (20 Hz for fn = 50 Hz, or 24 Hz for fn=60 Hz), based on
the short-circuit impedance in the positive sequence system.

method “C(012)” : like C(1), but uses the correct short-circuit impedance
based on positive-, negative- and zero-sequence system.

Calculate Ik
The steady state short-circuit currents can be calculated with different ways of
considering asynchronous machines:

Without Motors will disconnect all asynchronous motors before calculating the
current Ik .

DIgSILENT Method will consider all asynchronous motors by their breaker

current. The breaker opens after the maximum possible time.

Ignore Motor Contributions will consider asynchronous motor impedances

during the calculation, but will reduce the calculated results for the motor
contributions. currents.

Consider Protection Devices

This option will calculate measured currents for all protection devices and will
evaluate tripping times. This option can be disabled to increase the calculation
speed when protection devices do not need to be analysed.

Calculate max. Branch Currents = Busbar Currents

This option is used to check the rating of the circuit breakers against the system
breaker currents. Normally the breaker currents are calculated as
max{(Ibus-Ibranch, Ibranch}. If this option is activated, the busbar short-circuit
current is used as the breaker current, which in fact is an over-estimation of the
currents.

Automatic Power Station detection

The IEC/VDE standard forces a different impedance correction factor to be
applied for separate generators and transformers than for a unit/block (power
station) consisting of a generator including its step-up transformer. PowerFactory
tries to detect power stations itself. When this option is disabled, then the block
transformers have to be marked as such by setting the unit Transformer option in
the transformer dialogue.

Steady-State Power System Analysis 11-210

DIgSILENT PowerFactory Short-Circuit Calculations

11.6.5 Basic Options (ANSI Method)

Prefault Voltage
Value of the pre-fault voltage as required by the ANSI standard.

Fault Impedance
The fault impedance is defined as the reactance and resistance of the fault itself
(i.e. the impedance of the arc or of the shortening path).

Consider Transformer Taps

The ANSI standard optionally allows the current tap positions of the transformers
to be considered. This can be selected here.

NACD Mode
The NACD factor is the ratio of remote current contribution and the total fault
current: NACD = Iremote/Ifault. This NACD factor is used to calculate the
breaker currents, including the DC component of the current. The remote current
contribution required to evaluate the NACD factor is the sum of all remote
generator contribution (induction generators, synchronous machines, external
grids).

The calculation of the NACD factor may be very time consuming, as the
contribution of each generator is calculated one by one. Therefore different
approximative methods can be selected, which represent the most common
interpretations of the ANSI Standards:
predominant: The the NACD factor is calculated. If the resulting factor is
greater as or equal to 0.5, then the “dc decay only” curve is used, which
means that the remote generation is higher than the local generation.
interpolated: The NACD factor is calculated and the correction factor for the
asymmetrical fault current is interpolated between the ”dc decay only” and
”AC/DC decay” curves with the following equation:

M F = AC/DCf actor + (DCf actor − AC/DCf actor) ∗ N ACD

If (NACD = 1) then only the DC factor is used, if (NACD = 0) then only the
AC/DC factor is used.
all remote: All contributions are set to remote, the NACD factor is not calculated
but assumed equal to 1 and only the “DC decay only” curve is used.
all local: All contributions are set to local the NACD factor is not calculated but
assumed equal to 0 and only the ”AC/DC decay” curve is used.

Steady-State Power System Analysis 11-211

DIgSILENT PowerFactory Short-Circuit Calculations

Current/Voltages for
The calculation mode for the currents and voltages to be evaluated:

LV/Momentary: evaluates the sub-transitory S/C currents.

LV/Interrupting: evaluates the breaker currents

30 Cycle: evaluates the 30-cycle (steady-state) current.

11.6.6 Advanced Options (ANSI Method)

Calculate
This option is used to select the various currents according to the ANSI
standard, which are to be calculated.

• Momentary Current

• Interrupting Current

• 30 Cycle Current

• Low-Voltage Current

Bypass Series Capacitance

Series capacitances may not be considered for the ANSI short-circuit
calculation. They may be always considered, always bypassed/neglected or this
option may be set depending on the type of short-circuit calculated.

The available options are:

• No bypassing

• All currents

• LV & interrupting & 30 cycle current

• 30 cycle currents

Consider Protection Devices

This option will calculate measured currents for all protection devices and will
evaluate tripping times. This option can be disabled to increase the calculation
speed when protection devices do not need to be analysed.

Steady-State Power System Analysis 11-212

DIgSILENT PowerFactory Short-Circuit Calculations

Calculate max. Branch Currents = Busbar Currents

This option is used to check the rating of the circuit breakers against the system
breaker currents. Normally the breaker currents are calculated as
max{(Ibus-Ibranch, Ibranch}. If this option is activated, the busbar short-circuit
current is used as the breaker current, which in fact is an over-estimation of the
currents.

11.6.7 Basic Options (Complete Method)

As opposed to the calculation methods according to IEC/VDE and ANSI, which
represent approximative approaches of the correct short-circuit currents, the
complete method evaluates the accurate currents. It takes into account the
precise conditions right before the fault and treats the short-circuit problem as a
special case of the load-flow calculation.

Load-Flow
As the complete method considers the pre-fault condition in the system, it has to
evaluate a load-flow. The load-flow command (setup) initially is taken from the
currently active study case. To modify the settings, the button should be
pressed.

Fault Impedance
The fault impedance is defined as the reactance and resistance of the fault itself
(i.e. the impedance of the arc or of the shortening path).

Short-Circuit Duration
The value for the Breaker Time is used to calculate the breaking current of a
circuit breaker. The value for the Fault Clearing Time (Ith) is required for the
equivalent thermal current.

11.6.8 Advanced Options (Complete Method)

Decaying Aperiodic Component
Allows for the calculation of the DC current component for which the decaying
time has to be given. As proposed by the IEC/VDE standard, the methods B, C
and C’ can be selected.

Steady-State Power System Analysis 11-213

DIgSILENT PowerFactory Short-Circuit Calculations

Use Generator Impedances

Using this option it can be selected from which time domain the generator
impedances should be used. The possible choices are:

• subtransient

• transient

Calculate Ik
The steady state short-circuit currents can be calculated with different ways of
considering asynchronous motor contributions:

Without Motors will disconnect all asynchronous motors before calculating the
current Ik .

DIgSILENT Method will consider all asynchronous motors by their breaker

current. The breaker opens after the maximum possible time.

Ignore Motor Contributions will consider asynchronous motor impedances

during the calculation, but will reduce the calculated results for the motor
contributions. currents.

Consider Protection Devices

This option will calculate measured currents for all protection devices and will
evaluate tripping times. This option can be disabled to increase the calculation
speed when protection devices do not need to be analysed.

Calculate max. Branch Currents = Busbar Currents

This option is used to check the rating of the circuit breakers against the system
breaker currents. Normally the breaker currents are calculated as
max{(Ibus-Ibranch, Ibranch}. If this option is activated, the busbar short-circuit
current is used as the breaker current, which in fact is an over-estimation of the
currents.

11.7 Technical Background

Apart from the load-flow calculation, short-circuit analysis is the most frequently
used calculation function when dealing with electrical networks. It is used in
system planning as well as system operations (see Fig. 11.5).
Applications in system planning are for example:

Steady-State Power System Analysis 11-214

DIgSILENT PowerFactory Short-Circuit Calculations

Figure 11.5: Areas of Application for Short-Circuit Calculations

• Ensuring that the defined short-circuit capacity of equipment is not

exceeded with system expansion and system strengthening.
• Co-ordination of protective equipment (Fuses, over-current and distance
relays).
• Dimensioning of earth grounding systems
• Verification of sufficient fault level capacities at load points (e.g. uneven
loads like arc furnaces, thyristor-driven variable speed drives or dispersed
generation).
• Verification of admissible thermal limits of cables and transmission lines.

Applications in system operations are for example:

• Ensuring that short-circuit limits are not exceeded when changing the
system configuration
• Determining protective relay settings as well as fuse sizing
• Calculation of fault location for protective relays, which store fault
disturbance recordings.
• Analysis of system faults, e.g. mal-operation of protection equipment.
• Analysis of possible mutual interference of parallel lines during system
faults.

Steady-State Power System Analysis 11-215

DIgSILENT PowerFactory Short-Circuit Calculations

The fundamental difference for the calculation assumptions is that for system
planning studies the system operating conditions are not yet known, and
therefore estimates are necessary. For this purpose the method of the
equivalent voltage source at the fault location has generally become accepted in
Western Europe according to IEC 909 (VDE 0102). A revised version of this was
published as IEC 60909 in July 2001. This method works independent of the
load-flow of a system. It is based on the nominal and/or calculated dimensions
of the operating plant of a system and uses correction factors for voltages and
impedances, to ’push’ the results towards the safe side. For the calculation of
minimum and maximum short-circuit currents, different correction factors are
applied.

For short-circuit calculations in a system operation environment the exact

network operating conditions are well known. If the accuracy of the calculation
according to IEC 60909 is not sufficient - or to verify the results of this method -
the superposition method can be used. It calculates the expected short-circuit
currents in the network on the basis of the existing network operating condition.
If the system models are correct, the results from this method are always more
exact than the results of the method according to IEC 60909. The system
analyst is, however, responsible that he has chosen the most unfavourable
conditions with respect to the sizing of plant. In individual cases, this might result
in extensive studies required.

11.7.1 The Complete Method

The superposition method is (in terms of system modeling) an accurate
calculation method. The fault currents of the short-circuit are determined by
overlaying the healthy load-flow condition before short-circuit inception with a
condition where all voltage supplies are set to zero and the negative operating
voltage is connected at the fault location. The procedure is shown in Figure Fig.
11.6.

The initial point is the operating condition of the system before short-circuit
inception (see Figure Fig. 11.6 a). This condition represents the excitation
conditions of the generators, the tap positions of regulated transformers and the
breaker/switching status reflecting the operational scheme.

From these pre-fault conditions the pre-fault busbar voltage of the faulted busbar
can be calculated. For the pure fault condition the system condition is calculated
for the situation where, the negative pre-fault busbar voltage for the faulted bus is
connected at the fault location and all other sources / generators are set to zero
(see Figure Fig. 11.6 b).

Since network impedances are assumed to be linear, the system condition after
fault inception can be determined by overlaying (complex adding) both the
pre-fault and pure fault conditions (see Fig. 11.6 c).As the complete method is a

Steady-State Power System Analysis 11-216

DIgSILENT PowerFactory Short-Circuit Calculations

Figure 11.6: Illustration of the Complete Method (Superposition Method)

superposition of two special cases for the load-flow, the data necessary for the
model network elements are exactly the same as for the load-flow calculation.

11.7.2 The Method of IEC/VDE (Equivalent Voltage Source)

Deriving the IEC method from the Complete Method
Similar to the explanation of the complete method, the IEC/VDE method is
described in Fig. 11.7.
The method of the equivalent voltage source at the faulted bus is a simplification
of the superposition method with the goal of accomplishing a close-to-reality
short-circuit calculation without the need for the preceding load-flow calculation

Steady-State Power System Analysis 11-217

DIgSILENT PowerFactory Short-Circuit Calculations

Figure 11.7: Illustration of the Method according to IEC/VDE

and the associated definition of actual operating conditions. Fig. 11.7 shows,
how the method of the equivalent voltage source can be derived from the
superposition method. The steps a to c are very similar, however a simplified
network model is used.

In comparison, the main simplifications in comparison to the superposition

method are the following:
• Nominal conditions are assumed for the whole network, i.e. Ui = Un,i .
”
• Load currents are neglected, i.e. IOp = 0.
• A simplified simulation network is used, i.e. loads are not considered in the
positive and negative sequence network.

Steady-State Power System Analysis 11-218

DIgSILENT PowerFactory Short-Circuit Calculations

• To ensure that the results are estimated on the safe side, a correction
factor c is applied to the voltage at the faulted busbar. This factor differs for
the calculation of the maximum and the minimum short-circuit current of a
network.

The short-circuit calculation based on these simplifications proves not to be

sufficient for the practical applications. Therefore additional impedance
correction factors are applied to the physical impedances of the network
elements. The idea behind is discussed in the next section.

The IEC Impedance Correction Factors

The IEC method uses only the rated parameters of network elements. The
advantage is, that only little information is necessary to perform a S/C
calculation. But as e.g the S/C contribution of a synchronous generator depends
significantly on the excitation voltage and on the unit transformer tap changer
position, the worst-case value of this impedance is considered by applying a
correction factor (¡ 1).

This idea is shown in Fig. 11.8. The correction Factor K should be determined
so that Ik” = Ik,IEC
”
. The standard defines an equation for the correction factor
applying to each element type.

Figure 11.8: Impedance correction (IEC/VDE) in principle

As the IEC standard includes a worst-case estimation for minimum and

maximum S/C currents, some elements require additional data. The mainly
affected elements are:

Lines In their type you have to indicate the maximum admissible conductor
temperature (for min. S/C currents). Line capacitances are not considered
in positive/negative sequence system, but must be used in the
zero-sequence system.

Transformers They require a flag if they are unit or network transformers.

Network transformers may be assigned additional information about
operational limits which is used for a more precise calculation of the

Steady-State Power System Analysis 11-219

DIgSILENT PowerFactory Short-Circuit Calculations

impedance correction factor. Unit transformers are treated different if

having a on-load or a no-load tap changer.

Synchronous Machines Sub-transitory impedances are used, besides that

information about the voltage range must be given.

Asynchronous Machines The ratio of starting current to rated current is used

to determine the S/C impedance.

Please see the standard IEC 60909 to find detailed information about the
specific model and the correction factors of each element.

Steady-State Power System Analysis 11-220

DIgSILENT PowerFactory Protection

Chapter 12

Protection

The PowerFactory protection modeling features have been implemented with

the following philosophy in mind.

• The protection modeling should be as realistic as possible

• The user must be able to create new complex protection devices or alter
existing ones

• Although the protection models may show high complexity, their use must
be kept easy

• All protection models will act on switches.

These specifications led to the following principles.

• A fuse is modeled as a time-overcurrent relay acting on a switch

• A distinction is made between defining or altering new relay models, which

is described in the technical reference, and the use of those models, which
is described in this chapter.

12.1 Creating a Protection Device

Protection devices are normally stored in the object which they act upon, but they
may be stored elsewhere when needed. Recommended, and by default, is that

• protection devices which act upon a single switch are stored in the cubicle
which contains that switch (highly recommended)

• protection devices which act upon two or more switches connected to the
same busbar are stored in that busbar

• protection devices which act upon two or more switches connected to the
same busbar system, are stored in the station containing that busbar
system

Steady-State Power System Analysis 12-221

DIgSILENT PowerFactory Protection

• protection devices which act upon switches connected to more than one
busbar system are stored in the station containing those busbar systems,
or in the power system grid folder if more than one station is involved

As a rule, the relay is best stored in the same folder as the voltage and/or current
transformers which it uses.

Editing or creating protection devices in a cubicle can be done in several ways:

• by right clicking a switch-symbol in the single line graphic. This will bring a
pop up menu with the options Edit Protection Devices and New Protection
Devices

• by editing the object which is connected to the cubicle (line, transformer,

load, etc.) and pressing the button at the cubicle field. See Fig. 12.1
for example. The option Edit Relays will bring a list of all protection devices
in the cubicle. New devices may be then created with the button.

Figure 12.1: Editing line protection devices

In all cases, selecting the option to create a new protection device will bring a list
with the following options:

• Relay Model (ElmRelay)

• Fuse (RelFuse)

• Current Transformer (StaCt)

• Voltage Transformer (StaVt)

Each of these options will open a dialogue to specify the device that is to be
created or to select the one that is to be edited.

Steady-State Power System Analysis 12-222

DIgSILENT PowerFactory Protection

12.1.1 Example: a Time-Overcurrent Relay

Protection devices form a group of highly complex and non-uniform power
system devices. This places any program for modeling them for a difficult
dilemma. On the one hand, the relay models should be as flexible and versatile
as possible, to ensure that all types of protection relays can be modeled with all
of their features. On the other hand, the relay models should be as simple as
possible in order to reduce the amount of work and knowledge needed to define
power system protection devices.

This dilemma is solved by PowerFactory by separating the process of definition

a protection type definition from the process of creating a specific protection
element. Although the definition of a new protection type asks for a good
understanding of composite frames, DSL, time overcurrent plot definitions, etc.,
the use of a protection element is more or less a ’take of the shelf’ process.

This separation between defining new or using existing relay types led to the
global relay object hierarchy as shown in Fig. 12.2.

Figure 12.2: Global Relay Object Hierarchy

The relay frame is a graphically defined composite frame which defines the
functional parts of the relay and their connections. The relay frame can be
compared with an empty printed circuit board.
The relay type is based on the relay frame and defines the type of parts which
are allowed to be put in the relay slots. The relay type can be compared with a
printed circuit board with specific, but still empty, chip or relay sockets.
The relay itself models a specific protection element, based on the relay frame
and the relay type. The relay model uses specific functional elements where the
relay type defines only the allowed type of elements. These specific elements

Steady-State Power System Analysis 12-223

DIgSILENT PowerFactory Protection

must be based on those element types. The relay object can be compared with
a finished printed circuit board, where specific relays and chips have been
inserted in the sockets.

The Fig. 12.2 also shows that most of the work of defining a protection device is
done by the Relay Type Designer. A large set of common relays types is
available in the database and these types are ready for use.

How to use a relay type, that is: how to create a relay element, how to add it to
the power system, how to adjust the relay settings, how to perform calculations,
etc., is shown by the example of a simple time-overcurrent relay. This relay
measures the currents in three phases, but calculates a single maximum current
Imax. The relay trips a breaker when Imax violates either the time-overcurrent
or the instantaneous overcurrent conditions.

The Relay Frame

The example relay frame is shown inFig. 12.3. This is not a symbolic
representation of the relay, but the actual Composite Frame which defines the
relay type. The design of these relay frames is described in the technical
reference manual. The block diagram is only shown here to explain the example
relay.

Figure 12.3: Composite frame of a time-overcurrent relay

In the relay frame, the following slots can be distinguished:

• A current transformer slot (StaCt), which outputs are the real and
imaginary parts of the three phase currents (IrA, IiA, IrB, etc.) and the real
and imaginary parts of the zero sequence current (I0x3r,I0x3i).
• A measurement unit slot (RelMeasure), which output is Imax, which is the
maximum of the three phase currents.
• A slot for a time-overcurrent relay unit (RelToc) and one for an
instantaneous overcurrent relay unit (RelIoc), with the tripping signals as
outputs.
• A logic unit slot (RelLogic), which combines the tripping signals in a logical
way to produce a single tripping signal.

Steady-State Power System Analysis 12-224

DIgSILENT PowerFactory Protection

The Relay Type

The example relay type that is defined on the basis of the time-overcurrent relay
frame is shown in Fig. 12.4.

Figure 12.4: The Relay Type dialogue

The “Relay Definition” field points to the relay frame. The slot definition list will
automatically show all slots defined by that relay frame. In the example, these
are the five slots described in the previous section. The “Category” field is only
used to help selecting a relay type.

An object type is normally selected for each slot, except for the slots for the
current and voltage transformers. A relay based on the relay type may not use
elements other than such which are based on the given object types. The fact
that, in the example, no type is specified for the current transformer, means that
all current transformers may be used.

Normally, relay types are only selected but not changed or edited. The
PowerFactory relay database offers a wide variety of relay types.

Creating a Relay Model

This is where we leave the domain of the relay designer enter that of the relay
user. As soon as a new relay is inserted in the power system, which is normally
done by right clicking a switch and selecting New Protection Device - Relay
Model, an empty relay model (ElmRelay) appears. The example relay model is
depicted in Fig. 12.5.

Steady-State Power System Analysis 12-225

DIgSILENT PowerFactory Protection

Figure 12.5: Relay Model dialogue

The relay model has a reference to a relay type, a location, a device number and
a list of slots. The location is normally set automatically when a relay is defined
in the single line graphic by right clicking a cubicle. The cubicle then defines the
location. The device number is only relevant for the device documentation. The
slot list is defined by the relay type.

As is shown in Fig. 12.2, the relay model should define objects for all the slots in
the relay type. Each of these ‘slot elements’ must use the corresponding ‘slot
type’, when such a type is defined in the relay type.

Luckily, the tedious work of creating the correct elements, selecting the correct
type and assigning the element to the correct slot, is performed by the relay
element itself.
The whole process of creating a specific relay model thus only asks for selecting
a relay type from the database. What follows then can best be compared by an
automatic assembly process:

• as soon as a new relay type is selected, the slot definition list is updated

• all slot elements for which a slot type has been defined will be created
automatically. No elements will be created for those slots for which no slot
type has been defined. Normally, these are only the voltage and current

Steady-State Power System Analysis 12-226

DIgSILENT PowerFactory Protection

transformer slots. However, if already existing and valid objects are found
in the relay model or the cubicle in which it resides, they will be assigned to
the slots automatically.

• the created slot elements are inserted in the slot definition list

The result is a new and complete relay model with all slots filled (except maybe
for the transformer slots). Of course, all relay settings are still set to their default
values.

All slot elements created by the relay model are stored in the relay model itself.
Fig. 12.6 shows the database tree with the example relay model.

Figure 12.6: Example relay model with slot elements

The current transformer in the example is not stored in the relay model but in the
cubicle.

When, again, a new relay type is selected, the slot elements created for the
previous relay type will in most cases not be suited for the new type. However,
the ‘automatic assembly process’ will try to reuse as much data as possible from
the old settings:

• Slot elements that are also suited for the new rely type will be reused as
they are

• Slot elements which are correct except for their type will be assigned the
correct slot type

• Slot elements which cannot be reused will be deleted

• Missing slot elements will be created automatically

Pressing the C ANCEL button after the Relay Type has been changed will
not restore the old slot elements.

Normally, the relay type will not define any current and/or voltage transformer
types. The corresponding transformer element will thus not be created

Steady-State Power System Analysis 12-227

DIgSILENT PowerFactory Protection

automatically. However, if these measurement transformers were created prior

to creating the relay element, they will be assigned to the correct slot
automatically. This is the recommended practice. If the measurement
transformers were not created yet, they may be created by pressing the
C REATE VT or C REATE CT buttons. That will create a new transformer in the
cubicle were the relay element is stored.

Editing the Relay Elements

After a relay element has been defined and all slot elements have been created,
we may start editing the relay settings by editing the slot elements.

In the example we have to enter settings for

• The CT “Current Transformer 0”

• The Measurement object “Measurement”

• The time overcurrent relay “Toc”

• The instantaneous overcurrent relay “Ioc”

• The logic object “Logic”

For the current transformer, the tap settings and the connection type have to be
selected. The possible tap range is limited by the type. See Fig. 12.7.
The measurement object only needs the Nominal Current and Nominal Voltage.
Their range is limited by the measurement type. The nominal values are only
needed if the relay uses p.u. values. In the example, the measurement object
needs no data at all. See Fig. 12.8.
The time overcurrent relay allows for setting

• The time overcurrent characteristic

• The pickup current

• The time dial

All three settings are limited by the relay type: only those characteristics
available for this type of relay can be selected and not every possible values for
the pickup current or time dial may be entered. See Fig. 12.9.
The instantaneous overcurrent relay allows for setting the pickup current. See
Fig. 12.10.
The logic unit dialogue shows a list of all switches that will be opened as soon as
the logic unit trips. The logic unit combines the tripping signals of the sub relays
(the Toc and Ioc relays in this example), in an AND/OR expression (Toc OR Ioc
in this example). All switches in the list will be opened. If the relay to which the
logic unit belongs is stored in a cubicle, the three-phase breaker in that cubicle
will be opened by default if no switches are been specified. See Fig. 12.11.

Steady-State Power System Analysis 12-228

DIgSILENT PowerFactory Protection

Figure 12.7: A current transformer dialogue

Figure 12.8: A measurement object

12.2 Basic Protection Devices

As has been explained in the introduction of this chapter, the whole hierarchy of
objects that is used to build protection devices can be divided into

• objects which are needed to define new types of protection devices

• objects which are needed to define specific relay models.

The first group of objects are treated in detail in the technical reference manual.
The second group of objects are treated in this section.

Steady-State Power System Analysis 12-229

DIgSILENT PowerFactory Protection

Figure 12.9: A Time overcurrent relay

Figure 12.10: An instantaneous overcurrent relay

12.2.1 The Current Transformer

A new current transformer (CT) can be created by right clicking a cubicle in the
single line diagram and selecting “New Protection Device - Current Transformer”.
The dialogue as depicted in Fig. 12.12 will then pop up.
A thus created CT will be stored in the cubicle that was right clicked. The
“Location” fields “Busbar” and “Branch” will be set automatically in that case.

A current transformer always needs a current transformer type.

The top “Location” field is used either

• to select a cubicle when the CT is created from outside the cubicle

• to select the preceding CT in the case of an auxiliary CT

In the case of auxiliary CT, the complete transformer ration over all CT’s in series

Steady-State Power System Analysis 12-230

DIgSILENT PowerFactory Protection

Figure 12.11: A logic relay object

Figure 12.12: The Current Transformer dialogue

is shown in the edit dialogue. In the example of Fig. 12.12, the shown CT itself
has a ration of 5.00 to 1, but the complete ration (up to this CT) is 500.00 to 1.
The primary connection type is only available in the case of an auxiliary CT.

The number of phases can be set to 3, 2 or 1. For a 3- or 2-phase CT, the

Steady-State Power System Analysis 12-231

DIgSILENT PowerFactory Protection

secondary connection type can be set to D or Y. For a 1-phase CT, the phase
can be set to

• a,b or c phase current

• N = 3*I 0

• I0=I0

The primary and secondary tap settings are limited to the values defined in the
current transformer type.

Steady-State Power System Analysis 12-232

DIgSILENT PowerFactory Protection

The Current Transformer Type

The current transformer type dialogue, as depicted in Fig. 12.13, defines the
single phases of a CT. The information about the connection of these phases (Y
or D) is defined in the CT element that uses the CT type.

Figure 12.13: The Current Transformer Type dialogue

The current transformer type defines the primary and secondary taps of the
transformer. The “Additional Data page” is used only when saturation is
considered, to set the accuracy parameters:

• The accuracy class

• The accuracy limit factor
• either
– The apparent power (acc. to IEC)
– The burden impedance (ANSI-C)
– The voltage at the acc. limit (ANSI-C)

12.2.2 The Voltage Transformer

A new voltage transformer (VT) can be created by right clicking a cubicle in the
single line diagram and selecting “New Protection Device - Voltage Transformer”.
The dialogue as depicted in Fig. 12.12 will then pop up.
A thus created current transformer will be stored in the cubicle that was right
clicked.

Steady-State Power System Analysis 12-233

DIgSILENT PowerFactory Protection

Figure 12.14: The voltage transformer dialogue

A voltage transformer always needs a voltage transformer type.

The “Location” field is used either

• to select a cubicle when the VT is created from outside the cubicle
• to select the preceding VT in the case of an auxiliary VT
In the case of auxiliary VT, the complete transformer ration over all VT’s in series
is shown in the edit dialogue. In the example of Fig. 12.14, the shown VT itself
has a ration of 50.00 to 1, but the complete ration (up to this VT) is 5000.00 to 1.

The primary winding is defined by selecting a tap and a connection type. The
available tap range is defined in the voltage transformer type.

The secondary winding is defined by the secondary winding type, the tap setting
and the connection type. The available tap range is defined in the secondary
winding type. A voltage transformer requires at least one secondary winding.
More windings can be defined by pressing the button
A DDITIONAL S ECONDARY W INDINGS . This will bring a list of all previously
defined secondary windings. New windings can be created by pressing the
button.

The connection type “O” for the secondary windings is the “Open Delta”
connection, as depicted in Fig. 12.15.
The connection type “V” for the primary and secondary windings is depicted in
Fig. 12.16. Selecting a “V” connection for the primary winding automatically sets
the secondary winding to a “V” too.

Steady-State Power System Analysis 12-234

DIgSILENT PowerFactory Protection

Figure 12.15: The Open Delta (O) winding connection

Prim. Sec.
A A

B B

C C
Figure 12.16: The “V” winding connection

The VT Secondary Winding

A secondary winding element is needed when a voltage transformer with two or
more secondary windings has to be modeled. The edit dialogue for the voltage
transformer provides parameters to define the first secondary winding.

Figure 12.17: The VT secondary winding dialogue

The secondary winding element requires a type and a reference to the voltage
transformer. The tap settings range is defined by the windings type.

See The Voltage Transformer, section 12.2.2, page 12-233 for more information.

The VT Secondary Winding Type

The secondary winding type, as depicted in Fig. 12.18, defines the burden and
tap range for one phase of a voltage transformer. The phase connection type (Y,
D, etc.) is defined in the secondary winding element.
The secondary tap settings defined in the secondary winding type determine the
available tabs for the secondary winding element.

Steady-State Power System Analysis 12-235

DIgSILENT PowerFactory Protection

Figure 12.18: The VT secondary winding type dialogue

The Voltage Transformer Type

The voltage transformer type, as depicted in Fig. 12.19 defines the primary
winding of the voltage transformer.

Figure 12.19: The voltage transformer type dialogue

The secondary windings are defined in the voltage transformer element.

Steady-State Power System Analysis 12-236

DIgSILENT PowerFactory Protection

12.2.3 The Relay Model

The relay model (ElmRelay) is a general ‘frame-object’ which consists of a relay
frame with slots and one or more elements which occupy those slots. All
protection relays, except for the fuse models, are modeled as relay models.

Figure 12.20: The Relay Model dialogue

The relay element is defined by selecting a relay type. The relay type defines the
relay frame and the slot types which may be used with that frame. After a relay
type has been selected, the “Slot Definition” list will be filled automatically with
the correct slot elements. The current and voltage transformers, however, are
not created automatically, although available CT’s and VT’s are selected
automatically. See “Creating a Relay Model”, section 12.1.1, page 12-225 for
more information.

Editing the settings of the relay model is done by editing the settings of the listed
slot elements. Double clicking a slot element in the “Slot Definition” list will open
the dialogue of that element.

For more information about slot elements, see

• Directional Relay, section 12.2.4, page 12-238
• The Frequency Measurement Unit, section 12.2.5, page 12-239
• The Frequency Relay, section 12.2.6, page 12-239

Steady-State Power System Analysis 12-237

DIgSILENT PowerFactory Protection

• The Instantaneous Overcurrent Relay, section 12.2.8, page 12-240

• The Fuse Model, section 12.2.7, page 12-240

• The Logic Unit, section 12.2.9, page 12-242

• The Measurement Unit, section 12.2.10, page 12-243

• The Time Overcurrent Relay, section 12.2.11, page 12-244

• Under-/Overvoltage relay, section 12.2.12, page 12-245

12.2.4 Directional Relay

The directional relay cannot be used ‘as-is’, but is always a part of a relay model.
For more information about relay models, see section 12.2.3, page 12-237).

The directional relay calculates the angle between a ‘polarisation’ voltage or

current and an ‘operating’ current. The polarisation current or voltage is rotated
to the amount of the expected angle first. The relay trips if the remaining angle is
smaller than 90◦ and if both the polarisation and the operating voltage/currents
are large enough. This principle is shown in Fig. 12.21.

Figure 12.21: Directional relay principle diagram

The polarisation quantity Apol is rotated over the angle MT , which is the “Max.
Torque Angle” set in the relay edit dialogue. The rotated polarisation quantity A0pol
defines a half plane which forms the first tripping condition. Further conditions
are the projection of the operating quantity on A0pol , which must be larger than
the operating current setting, and the polarisation quantity, which must be larger
than the polarisation setting. More details about the polarization methods and
the tripping conditions can be found in the basic technical reference manual.

The choice for the type of operating and polarisation quantity is made in the
Directional Relay Type object. The relay object itself allows for the setting of the

Steady-State Power System Analysis 12-238

DIgSILENT PowerFactory Protection

tripping direction, the polarisation method when both methods (voltage and
current) are available, and the polarisation criteria. See Fig. 12.22.

Figure 12.22: Directional Relay

Selecting a ‘Reverse Tripping Direction’ will invert the used operating current.
The voltage or current polarisation allow for setting the “Operating Current”, the
“Polarisation Voltage/Current” and the “Max.Torque Angle”.

12.2.5 The Frequency Measurement Unit

The frequency measurement unit cannot be used ‘as-is’, but is always a part of a
relay model. For more information about relay models, see section 12.2.3, page
12-237).

The frequency measurement unit is used to calculate the momentary electrical

frequency for the given “Measured Voltage”.
The Nominal Voltage is needed for per unit calculations. The Frequency
Measurement Time defines the time used for calculating the frequency gradient.

12.2.6 The Frequency Relay

The frequency relay cannot be used ‘as-is’, but is always a part of a relay model.
For more information about relay models, see section 12.2.3, page 12-237).

The frequency relay either trips on an absolute under-frequency (in Hz), or on a

frequency gradient (in Hz/s). Which condition is used depends on the selected
relay type. The relay type also defines the reset time, during which the frequency
condition must be met again for the relay to reset.

Steady-State Power System Analysis 12-239

DIgSILENT PowerFactory Protection

Figure 12.23: Frequency Measurement

The time delay set in the relay element defines the time during which the
frequency condition must be violated for the relay to trip. See Fig. 12.24.

Figure 12.24: Frequency

12.2.7 The Fuse Model

The fuse model is implemented as a special instantaneous overcurrent relay
which does not need a current transformer. A fuse is always located in a cubicle
and will trip the phase which current exceeds the melt curve. Optionally, all three
phases will be tripped if one of the phase currents exceeds the melt curve.
The calculation of the trip time is eiter based on the minimum melt curve or on
the total clear curve. An example of these curves are shown in Fig. 12.26.

12.2.8 The Instantaneous Overcurrent Relay

The instantaneous overcurrent relay cannot be used ‘as-is’, but is always a part
of a relay model. For more information about relay models, see section 12.2.3,
page 12-237).

Steady-State Power System Analysis 12-240

DIgSILENT PowerFactory Protection

Figure 12.25: The Fuse Model dialogue

Figure 12.26: Fuse Melt Characteristics

The instantaneous overcurrent relay allows for the setting of the pickup current
and the time dial. Both entries are limited by the relay type. See Fig. 12.27.
The instantaneous overcurrent relay is a combination of a direct overcurrent
relay and an optional time delay. The pickup time T s is the minimum time
needed for the relay to react. Additionally, a time dial T set may be specified. The
relay will not trip unless the current exceeds the pickup current T setr for at least

Steady-State Power System Analysis 12-241

DIgSILENT PowerFactory Protection

Figure 12.27: Instantaneous Overcurrent

T s + T set. See Fig. 12.28.

Figure 12.28: Instantaneous overcurrent tripping area

The relay will nor reset until the current drops under the reset level, which is
Kr
specified by the relay type in percent of the pickup current: Ireset = Ipset 100% .
See Fig. 12.29 for a typical timing diagram.

Figure 12.29: Instantaneous overcurrent timing diagram

12.2.9 The Logic Unit

The logic unit is the front end part of a relay configuration. It combines all internal
trigger signals by successive AND and OR operations and produces one single

Steady-State Power System Analysis 12-242

DIgSILENT PowerFactory Protection

output. The logic unit type specifies the logical operation, the logic unit itself
specifies the switches which will be opened when the relay trips. See Fig. 12.30.

Figure 12.30: Relay Logic

If the relay is located in a cubicle and no switch has been specified, the breaker
in the cubicle will be opened by default.

12.2.10 The Measurement Unit

The measurement unit uses the ’raw’ signals produces by the current or voltage
transformers to calculate ’measured signals’. Which signals are being calculated
depends on the measurement unit type.

The measurement unit allows for setting the nominal current and voltage. Both
are limited by the measurement unit type. If a relay does not need a nominal
voltage (i.e. in the case of an overcurrent relay), the nominal voltage field will
normally be disabled.

Figure 12.31: Measurement

Steady-State Power System Analysis 12-243

DIgSILENT PowerFactory Protection

12.2.11 The Time Overcurrent Relay

The time-overcurrent relay cannot be used ‘as-is’, but is always a part of a relay
model. For more information about relay models, see section 12.2.3, page
12-237).

The time-overcurrent relay allows for the selection of one of the I-t curves
(‘characteristic’) which are available for the selected relay type. The I-t curve is
further specified by the pickup current and the time dial. Both values must be in
the range specified by the I-t curve definition. See Fig. 12.32 for an example.

Figure 12.32: The time overcurrent relay dialogue

The time dial settings will scale the I-t curve in the Time vs. I/Ip plot, according to
the curve definition. See Fig. 12.33 for example.
The pickup current defines the nominal value Ip which is used to calculate the
tripping time. The I-t curve definition states a minimum and a maximum per unit
current. Lower currents will not trip the relay (infinite tripping time), higher
currents will not decrease the tripping time any further. These limits are shown in
Fig. 12.34.
The pickup current may be defined by the relay type to be a per unit value, or a
relay current. The nominal current defined by the measurement unit (see section
12.2.10, page 12-243) is used to calculate Ip in the case of a per unit value. The
relay current value already equals Ip.

Altering the pickup current will thus not change the I-t curve, but will scale the
measured current to different per unit values. The following example may
illustrate this:

• Suppose the minimum current defined by the I-t curve is imin = 1.1 I/Ip.

• Suppose the measurement unit defines Inom = 5.0 rel.A.

• Suppose pickup current Ipset = 1.5 p.u.

→ relay will not trip for I < 1.1 ∗ 1.5 ∗ 5.0 rel.A = 8.25 rel.A

Steady-State Power System Analysis 12-244

DIgSILENT PowerFactory Protection

Figure 12.33: I-t curves for different Time Dials

Figure 12.34: I-t curve limits

• Suppose pickup current Ipset = 10.0 rel.A

→ relay will not trip for I < 1.1 ∗ 10.0 rel.A = 11.0 rel.A

12.2.12 Under-/Overvoltage relay

The under- or overvoltage relay cannot be used ‘as-is’, but is always a part of a
relay model. For more information about relay models, see section 12.2.3, page
12-237).

The under-/overvoltage relay type may define the relay to trip on either

Steady-State Power System Analysis 12-245

DIgSILENT PowerFactory Protection

• Either one of the three phase line to line voltages

• One particular line to line voltage

• The ground voltage UO .

• The positive sequence voltage U1

• The negative sequence voltage U2

The relay element allows only for setting the pickup voltage and the time delay.
See Fig. 12.35.

Figure 12.35: Under-/Overvoltage

12.3 Short-Circuit Sweep

The “Short-Circuit Sweep” command as depicted in Fig. 12.36 is used to

calculate a short-circuit sweep along a defined path. Short-circuits are
calculated along a given path and the results at each short-circuit location are
written to a Results object. The position in km relative to the beginning of the
path is always written to the results. The sweep command is used e.g. by the
time-distance diagram (see section 12.4, page 12-248) to record the trigger
times of distance relays.

12.3.1 Options
Path
Short-Circuits are calculated along this path. Path is set automatically and
grayed out if the command is called by the “Time Distance Plot”.

Steady-State Power System Analysis 12-246

DIgSILENT PowerFactory Protection

Figure 12.36: The short-circuit sweep dialogue

Additional Relays
If the option “Iterate Tripping Times” on the advanced page is set, the positions
where a relay trips is interpolated and written to the results. The relays whose
tripping times are checked are the relays found in the path and, in addition, the
relays given by the selection referenced in “Additional Relays”. Additional relays
is grayed out and set if the command is called by the “Time Distance Diagram”.

Results Frame
The variables written to the results object can either be defined by the user or by
the “Time Distance Diagram”. If the results are defined by the “Time Distance
Diagram” all “Monitor Variable Sets” in the results object are ignored. Otherwise
the variables found in the “Monitor Variable Sets” stored in the results object are
written. The result frame is grayed out if the command is accessed through the
time-distance diagram.

Results
Reference to result object, see also Result Frame, grayed out if the sweep
dialogue is accessed through the time-distance diagram.

Steady-State Power System Analysis 12-247

DIgSILENT PowerFactory Protection

Locations
A short-circuit is calculated on each busbar/terminal found in the path. If “Buses
and Branches” is selected short-circuits on the branches between the busbars
are calculated.

Short-Circuit Frame
“Command” is a reference to the short-circuit command. Except the short-circuit
location the short-circuit settings are not changed by the sweep. The type of
failure, the method of calculation and other settings can be modified there.
“Calculation” is just displaying the “Fault Type” set in the short-circuit command.

12.3.2 Advanced Options

Step Size
The relay tripping positions in the path can either be iterated or calculated with a
continuous step size. In the constant mode a short-circuit is calculated at the
beginning of the branch. The distance between the following short-circuits on the
branch is “Continuous Step Size”. There is always a short-circuit calculated at
the end of the branch. In the “Iterate Tripping Times” method the relay tripping
positions are iterated. If the tripping time of a relay changes continuously (like
overcurrent relays) the sweep changes to continuous mode automatically.
Iteration mode is used again when the tripping time remains unchanged at the
next short-circuit position. The step size frame is grayed out if the command is
accessed by the time-distance diagram.

Precision and Step Size

The “Precision (Steps)” defines the maximum iteration error at the relay tripping
position. The “Continuous Step Size” defines the step size for the sweep with
constant steps. “Precision and Step Size” is unused (hidden) if location is set to
buses.

12.4 The Time-Distance Diagram

The time-distance plot shows the tripping times of the relays in dependence of
the short-circuit location. It is normally calculated by the short-circuit sweep
command. See section 12.3, page 12-246 for more information.

The most easy way of creating a time-distance plot is to define such a plot in the
single line graphic.

Steady-State Power System Analysis 12-248

DIgSILENT PowerFactory Protection

A previous defined path can be right clicked. The context sensitive menu will
show the option Path.. - Create time-distance Plot. This option can also be found
in the Output.. submenu of the context sensitive menu. The option will not be
shown if there is no distance relay available in the selected path.

Figure 12.37: A time-distance plot

The time-distance plot in Fig. 12.37 is separated in two different diagrams. The
forward diagram shows all relays at the beginning of the line in path direction.
The reverse diagram shows the relays at the beginning of the line in reverse path
direction. The upper diagram is in forward direction, the lower one in backward
direction. There are three different styles for the time-distance plot.These are:
Forward/Reverse: Both diagrams are shown.
Forward: Only forward direction diagram
Reverse: Only reverse direction diagram

Steady-State Power System Analysis 12-249

DIgSILENT PowerFactory Protection

12.4.1 The Path Axis

Figure 12.38: A path axis

The path axis in Fig. 12.38 shows the complete path with busbar and relay
locations. Busbars/Terminals are marked with a tick and the name. The boxes
above and below the line show the relay locations in forward and in backward
direction. The reference relays in both directions are marked with an arrow.

12.4.2 Methods for calculation of tripping times

There are several methods to calculate the tripping times shown in the plot. To
change the method, select the Method option in the context sensitive menu or
edit the R ELAYS page of the time-distance plot dialogue. The methods differ in
exactness and speed. The set of possible units for the x-Axis depends on the
method used. The methods are:

Short-Circuit Sweep Method The short-circuit sweep method is the most

accurate method for calculating the short-circuit locations. A short-circuit
sweep is calculated over the branches between the first and the last busbar
in the path. At each short-circuit location the relay tripping times are
established. The disadvantage of this method is it’s low speed. Whenever
the rebuild button of the graphics window is pressed the sweep is
recalculated. The possible units for the short-circuit location are position in
km or reactance in primary or relay ohm.
Linear Impedances This method is faster than the sweep method but more
inaccurate. Short-circuits are calculated on each busbar on the path. After
each short-circuit the impedances measured by the relays are recorded.
The impedances of the branches between the busbars are established
using the recorded impedances. Tripping time and position are determined
by intersection of these impedances and the relay characteristic. If there is
more than one intersection at the same impedance the relay step with the
smallest tripping time is used. The possible units for the short-circuit
location are position in km or reactance, resistance and impedance, each
in primary or relay ohm.
Kilometrical Method This method is the fastest but most inaccurate one.
Tripping time and location are determined with the intersection of the
impedances and the relay characteristic. The impedances used for
calculation are the impedances of the device. If there is more than one
intersection at the same impedance the smallest tripping time is used. The
possible units for the short-circuit location are position in km or reactance,
resistance and impedance, each in primary or relay ohm.

Steady-State Power System Analysis 12-250

DIgSILENT PowerFactory Protection

The kilometrical method is applicable only for the following paths

• There are no parallel branches in the path.

• The path is fed from only one side or there is no junction on the path.

12.4.3 Short-Circuit Calculation Settings

The Short-Circuit Sweep command object is used for calculating the
“Short-Circuit Sweep” and the “Linear Impedance” methods. There is either the
option Calculate... in the context menu of the plot or the Calculate... button in the
“Time Distance Plot” dialogue for access to the sweep command. Some of the
settings in the command are predefined by the time-distance plot. These
settings are grayed out when the sweep command is accessed through the plot.
The short-circuit command for the calculation is set in the sweep command. To
change the short-circuit method, e.g. “IEC” or “Complete”, open the sweep
command and edit the short-circuit dialogue.

See 12.3, page 12-246 for more information.

12.4.4 The x-Unit

There is a set of possible x-units depending on the method used. See the
methods description for details. The short-circuit sweep method needs a relay to
measure the impedance, named the reference relay. If there is no reference
relay selected the first relay in the diagram’s direction is used as reference relay.

12.4.5 The Impedance setting

The reactance on the x-Axis using the sweep method is measured by the
reference relay. There are different impedances measured, depending on the
relay and the type of fault. “Impedance” specifies which impedance is used for
the x-Axis. “According to Short-Circuit” will display the impedance depending on
the short-circuit fault.

A-B for a 3-phase short-circuit

B-C for a 2 phase short-circuit

A for a single phase to ground short-circuit

B for a 2 phase to ground short-circuit

Steady-State Power System Analysis 12-251

DIgSILENT PowerFactory Protection

12.4.6 The Reference Relay

The x-Axis positions or impedances are calculated relative to the beginning of
the path. If a reference relay was set the positions/impedances are relative to the
reference relay. The sweep method needs always a reference relay. If no
reference relay was set the first relay in the diagram’s direction is taken for
reference relay.
The busbar connected to the reference relay is marked with an arrow pointing in
the diagrams direction.

The reference relay is set either using the graphic or by editing the “Time
Distance Diagram” dialogue. Changing the reference relay graphically is done by
clicking with the right mouse button on the relay symbol and selecting “Set
reference relay” in the context menu. If there is more than one relay connected
to the selected busbar PowerFactory prompts for the relay to use. In the
dialogue of the ”Time Distance Relay” the “Reference Relay” frame is located on
the bottom. Change the “Relay” reference to set or reset the reference relay.

12.4.7 Double Click Positions

The following positions can be double clicked for a default action.
Axis Edit scale
Curve Edit step of relay
Relay box Edit relay(s)
Path axis Edit Line
Any other Open the “Time Distance” dialogue

12.4.8 The Context Sensitive Menu

The functions available in addition to the basic VI-methods for the time-distance
plot are:
Grid Shows dialogue to modify the grid-lines
Edit Path Shows dialogue of displayed path
x-Scale Modify x-Scale; Autoscale and edit
y-Scale Modify y-Scale; Autoscale and edit
Method Set the used method
x-Unit Set the unit for the x-Axis, km impedances,...
Diagrams Select diagrams shown forward, reverse or both
Calculate Show “Short-Circuit Sweep” command dialogue

Steady-State Power System Analysis 12-252

DIgSILENT PowerFactory Protection

12.4.9 Set Relays Buttons

The “Set Relays” buttons in the dialogue of the time-distance plot fills the table
with the relays in forward or reverse direction of the path.

12.5 Path Definitions

A path in a single line diagram is defined by selecting a chain of two or more

busbars or terminals and inter-connecting objects. The pop-up menu which
opens when the selection is right clicked will show a Path... option. This menu
option has the following sub-options:
Edit this option is enabled when an existing path is right clicked. It opens a
dialogue to alter the color and direction of the path
New this option will create a new path definition
Add To this option will add the selected objects to a path definition. The end or
start of the selected path must include the end or start of an existing path.
Remove Partly This will remove the selected objects from a path definition, as
long as the remaining path is not broken in pieces
Remove This will remove the firstly found path definition of which at least one of
the selected objects is a member
Editing, adding objects to or removing objects from path definition is only
possible when the option coloring “Path Definitions” was chosen in the Color
Representation of Graphic dialogue (SetColgr). This dialogue is opened by
pressing the button on the graphics toolbar.

A path may be used as a selection for a calculation by selecting one or more

objects from the path definition. This will select the whole path.

12.6 Protection Analysis Results

12.6.1 Reports
The button “Output Calculation Analysis” ( ) in the main menu, will open the
“Output” dialogue (ComSh). The results of the load-flow or short-circuit analysis,
for a range of relays, can be generated in the output by selecting the options
• Results

Steady-State Power System Analysis 12-253

DIgSILENT PowerFactory Protection

• Relays

To generate a report for one or more relays, or for one or more previously
defined paths, the data manager may be used to select one or more relays or
paths and right clicking the selection. The menu will show the option
Output-Results if at least one relays was found amongst the selected objects or
in one of the selected paths. If a busbar was selected, then all relays in
connection with that busbar are selected too.

12.6.2 Results in Single Line Graph

The names of the relays or the tripping times may be made visible in the single
line graphic by selecting the following options in the main menu.

1. Output - Results for Edge Elements - Relays

2. Output - Results for Edge Elements - Relay Tripping Times

The first option (“Relays” ), which is always available, will show the names of the
relays in all cubicles. The second option will show the tripping times of the relays
after a load-flow or short-circuit calculation has been made. If a relays does not
trip, then a tripping time of 9999.99 s is shown.

12.6.3 Plots
The time-overcurrent plots offer many features for displaying the settings of
relays and the results of short-circuit or load-flow calculations.

The time-overcurrent plots may also be used for changing the settings of relays
and fuses, by simply moving the tripping characteristics. Especially the
possibility of changing the curves in combination with a short-circuit or load-flow
result, and with the help of transformer or line damage curves, ensures a clear
and comprehensible setting of the relay parameters.

The following section explains the special features of the time-overcurrent plots.

12.7 Time-Overcurrent Plots

The most easy way of creating a time overcurrent plot is to define such a plot in
the single line graphic. Three different ways are possible:

• A previous defined path can be right clicked. The context sensitive menu
will show the option Path.. - Create Overcurrent Plot.

Steady-State Power System Analysis 12-254

DIgSILENT PowerFactory Protection

• One or more switches are selected and right clicked. The context sensitive
menu will show the option Create Overcurrent Plot
• One or more Transformers are selected and right clicked. The context
sensitive menu will show the option Output Data.. - Create Overcurrent
Plot

In all these cases, it is also possible to select the option Add to Overcurrent plot.
This will pop up a list of previously defined over current plots from which one has
to be selected.

The overcurrent plot shows

• the time-overcurrent characteristics of relays
• the damage curves of transformers or lines
• motor starting curves
• the currents calculated by a short-circuit or load-flow analysis and the
resulting tripping times of the relays
See Fig. 12.39 for an example.

Figure 12.39: A time-overcurrent plot with short-circuit results

The time-overcurrent plot shows the results of the short-circuit or load flow
analysis as a vertikal ‘x-value’ line across the graph. Because the currents differ

Steady-State Power System Analysis 12-255

DIgSILENT PowerFactory Protection

for each particular relay, a current line is drawn for each relay. The intersection of
the calculated current with the time-overcurrent characteristic is labeled with the
tripping time. A ‘grading margin’ line, which shows the difference between the
tripping times, may be added by right clicking the plot and selecting “Show
Grading Margins”.

It is also possible to create an user defined ‘x-value’ by right clicking the graph
and selecting the Set x-value option. The vertikal line will show the values at the
intersections of all displayed characteristics. To move the line left, drag it with the
mouse.

12.7.1 Changing Tripping Characteristics

The time overcurrent plots may also be used to change the relay characteristics
graphically. Because a relay characteristic is normally the minimum of two or
more sub-characteristics, it has to be split first in order to change the
sub-characteristics.

A characteristic is split by
• right clicking the characteristic
• enable the split option
The sub-characteristics are now visible. Each of them can be left clicked and
dragged along the time-overcurrent plot area. However, they cannot be dragged
outside the allowed range which has been defined for the relay type. After the
relay sub-characteristics have been changed, they can be combined again into
one single characteristic by disabling the split option again.

The plot option dialogue, which is opened by right clicking the plot area and
selecting Options, has an option for showing the grading margins when the time
overcurrent characteristics are dragged. The grading margin may be set to a
fixed time. The grading margins are shown as two lines, plus and minus the
grading margin above and below the dragged tripping characteristic. See Fig.
12.40 for an example: the original characteristic is labeled “1”, the new position
as “2”, and the grading margins are labeled “a”.

Conductor/Cable Damage Curve

The conductor and cable damage curves are used to evaluate a protection
coordination scheme and as guides for positioning the time-overcurrent
characteristics.
To add a damage curve to a time-overcurrent plot, right-click the plot area and
select Add Damage Curve.

Typical values for the conductur, insulation factor, K, are given in the following
tables. These tables show the temperature range for the cables:

Steady-State Power System Analysis 12-256

DIgSILENT PowerFactory Protection

Figure 12.40: Moving a Characteristic with Grading Margins

Figure 12.41: Conductor/Cable Damage Curve

• T1 = maximum operating temperature in ◦ C

• T2 = maximum short-circuit temperature in ◦ C

and the K factor for a cross section in mm2 , CM , M CM and inch2 .

Steady-State Power System Analysis 12-257

DIgSILENT PowerFactory Protection

COPPER CONDUCTOR
T 1 T 2 mm2 CM M CM inch2
Rubber isolated 60 200 141 0.0714 71.4 90968
PVC, flexible cable:
≤ 300mm2 70 150 109 0.0552 55.2 70323
PVC, mounted:
≤ 300mm2 70 160 115 0.0583 58.3 74194
2
> 300mm 70 140 103 0.0522 52.2 66452
PVC. high T 90 160 100 0.0507 50.7 64516
EPR. 90 250 143 0.0725 72.5 92258
EVA 120 250 126 0.0638 63.8 81290
ETFE 135 250 117 0.0593 59.3 75484
SiR 180 350 132 0.0669 66.9 85161
VPE-cable 90 250 143 0.0725 72.5 92258
PE-cable 70 150 109 0.0552 55.2 70323
Paperisolated shielded cable:
0.6/1 or 3.6/6kV 80 180 119 0.0603 60.3 76774
6/10kV 65 165 121 0.0613 61.3 78065
Three phase shielded cable / radial field cable:
0.6/1 or 3.6/6kV 80 180 119 0.0603 60.3 76774
6/10kV 70 170 120 0.0608 60.8 77420
12/20kV 65 155 116 0.0588 58.8 74839
18/30kV 60 140 111 0.0562 56.2 71613
Oilcable 85 170 110 0.0557 55.7 70968
Pressured Gas cable 85 170 110 0.0557 55.7 70968
ALUMINIUM CONDUCTOR
T 1 T 2 mm2 CM M CM inch2
VPE-Cable 90 250 94 0.0476 47.6 60645
PE-Cable 70 150 72 0.0365 36.5 46452
PVC:
≤ 300mm2 70 160 76 0.0385 38.5 49032
2
> 300mm 70 140 68 0.0345 34.5 43871
Paperisolated shielded cable:
0.6/1 or 3.6/6kV 80 180 78 0.0395 39.5 50323
6/10kV 65 165 80 0.0405 40.5 51613
Three phase shielded cable / radial field cable:
0.6/1 or 3.6/6kV 80 180 78 0.0395 39.5 50323
6/10kV 70 170 80 0.0405 40.5 51613
12/20kV 65 155 77 0.0390 39.0 49678
18/30kV 60 140 73 0.0370 37.0 47097
Oilcable 85 170 73 0.0370 37.0 47097
Pressured Gas cable 85 170 73 0.0370 37.0 47097

Transformer Damage Curve

Steady-State Power System Analysis 12-258

DIgSILENT PowerFactory Protection

The transformer damage curves are used to evaluate a protection coordination

scheme and as guides for positioning the time-overcurrent characteristics.

Figure 12.42: Transformer Damage Curve

To add an ANSI/IEEE C57.109 damage curve to a time-overcurrent plot,

right-click the plot area and select Add Damage Curve. An example of a
time-overcurrent plot with two relay characteristics and a transformer damage
curve is shown in Fig. 12.43.

Figure 12.43: Transformer damage curve

To add the damage curves of specific transformers in the power system, right

Steady-State Power System Analysis 12-259

DIgSILENT PowerFactory Protection

click the transformer object in the single line graphic or the database manager
ans select the option Output.. - Add to Overcurrent Plot. This will pop up the list
of defined overcurrent plots from which one has to be selected. A damage curve
will then be calculated from the electrical transformer data, according to the
ANSI/IEEE C57.109 standard, and added to the selected time over-current plot.

It is also possible to add a two-winding or three-winding transformer object to the

graph manually. This is done by editing the graph and adding the transformer
object to the list of displayed relays.

Motor Start Curve

The motor start curves are used to evaluate a protection coordination scheme
and as guides for positioning the time-overcurrent characteristics.

Figure 12.44: Motor start curve edit dialogue

The characteristic currents and durations given in the edit dialogue result in a
step wise motor start current plot, as depicted in Fig. 12.45.

Overcurrent Plot Settings

The time-overcurrent plot settings shows the following options

Current Unit , The current unit may be set to either primary or relay ampere.

Show Relays , This option sis used to display only certain types of relay
characteristics.

Steady-State Power System Analysis 12-260

DIgSILENT PowerFactory Protection

Figure 12.45: The motor start curve

Display automatically This option is used to select how the calculated

load-flow or short-circuit currents will be displayed. Either the current lines,
the grading margins, both or none may be selected.

Voltage Reference Axis. More than one current axis may be shown, based on
a different voltage level. All voltage levels found in the path when a time
overcurrent plot is constructed are shown by default. An user defined
voltage level may be added. Optionally, only the user defined voltage level
is shown.

Figure 12.46: Overcurrent Plot Settings

The advanced options are:

Drag & Drop Step Sizes These are used to set the step change in the relay
settings when a time-overcurrent plot is dragged with a continuous time
dial or pickup current.

Steady-State Power System Analysis 12-261

DIgSILENT PowerFactory Protection

Brush Style for Fuses This defines the fill style for fuse curves

‘Color for Out of Service’ Units The characteristics for units that are out of
service are drawn invisible by default. However, a visible color may be
selected.

Nr. of points per curve The number of points can be changed to either refine
the plotted curves for more detail, or to speed up the drawing of the
diagram.

12.8 The Curve-Input Command

The curve input command is used for measuring printed curves. The original
curves must be available in windows metafile (*.wmf) or in bitmap (*.bmp)
format. The graphics file is displayed as background in a curve input plot. This
plot then allows for defining plot points by successive mouse clicks.

The curve input plot allows for measuring and editing single curves of group of
curves at once. The measured curve points are stored in a Matrix object
(5.18.1). The positions of the axis in the curve input plot can be set by the user.
Special functions for groups of curves allow for x-value synchronisation and
many other facilities to make their input easier and faster.

12.8.1 Creating a Curve-Input Plot

The special ‘Curve Input’ virtual instrument plot is needed for measuring curves.
Such a plot, like al other virtual instruments, is displayed on a Virtual Instrument
Panel. A new virtual instrument panel is created with the new command in the
file menu or the new button of the graphics window.

A new Curve Input plot is created by right clicking the empty panel, or by
pressing the on the panel button bar and subsequently selecting the Curve
Input. The curve input option dialogue is opened by double clicking the curve
input plot.

The Input Options

The input options are used to select the graphics file which is to be measured.
Only windows metafile (*.wmf) or bitmap (*.bmp) formats are allowed. The
x-Scale and y-Scale settings are used to set the range and type of the axes of
the curves as they are in the graphics file.

Two different types of curves can be input:

Steady-State Power System Analysis 12-262

DIgSILENT PowerFactory Protection

Single ; each matrix input defines a single curve. The first column in the matrix
holds the x-values, the second one the y values. Other columns are
ignored.

Set of Curves ; only the first matrix is used for input. The first column in the
matrix holds the x-values, the other columns hold the y-values of each
curve in the group of curves.

The measured curve is drawn between the measured points by interpolation.

This is important when the measured curve is later used with a specific
interpolation. Setting the correct interpolation mode when measuring the curve
causes a better fit while avoiding excess curve point definitions. Available modes
of interpolation:

• Linear

• Cub. Spline

• Polygon

• Hermite

The Context Sensitive Menu

The case sensitive menu is opened by right clicking the curve input plot. The
menu is used to select the curve for which points are to be measured or edited,
to select the measurement mode, to synchronize x-values by interpolation, etc.

Grid Opens the grid layout dialogue

Curves Used to switch from ‘single’ to ‘set of curves’ mode.

Interpolation Selects the interpolation mode

Interpolate All interpolates undefined y values for all curves for all defined
x-values

Interpolate N interpolates undefined y values of curve N for all defined x-values

Delete Curve N removes curve N from the matrix

Add Curve appends a new curve

Input specifies the input mode:

• Off: switches off the measurement mode

• x/y-Pairs: each left mouse click adds a point to the curve.
• Drag & Drop: turns on the ’edit’ mode: all points can be dragged and
dropped to change their y-position or left clicked and deleted with the
’Del’ key.

Steady-State Power System Analysis 12-263

DIgSILENT PowerFactory Protection

• y at defined x: turns on the x-synchronized mode in which new points

can only be defined for already defined x-positions. This option is not
available for ’single’ curve mode.

Active Curve sets the curve to modify

How to Scan curve(s) using the curve-input plot:

Create a virtual instrument panel with a curve input plot

Open the curve-input dialogue with a double-click and set the following
options

Select the background file

Select “Single” or “Set of Curves” in the “Curves Listbox”
Select the interpolation mode
Select on or more Matrix objects in the table named “Curves”. At least
two columns must be already present in the matrix object.

Close the dialogue.

Define the axis position to adapt the curve input to the background plot:

Select the graphic cursor

Right click the plot and select Set Axis - Origin. Left click the origin of
the plot
Right click the plot and select Select Set Axis - x-Axis. Left click the
end of the x-axis of the background plot.
Right click the plot and select Select Set Axis - y-Axis. Left click the
end of the y-axis of the background plot.

Open the curve-input dialogue and adapt the scale of the curve input plot
to the scale of background plot

Right click the plot and select the Active Curve option and activate the first
curve. The option is not available when

– There is no Matrix object selected in the ‘Curves’ table of the dialogue

– One of the matrix object(s) has less than two columns

Right click the plot and select the Input option. Select the input mode. With
the first curve, select the with x/y-Pairs option.

Left click the curve to set x/y values.

Right click the plot and select the Input - Off option to finish the definition of
the curve

Steady-State Power System Analysis 12-264

DIgSILENT PowerFactory Harmonics Analysis

Chapter 13

Harmonics Analysis

There are two possible calculation functions for analysing harmonics in power
systems:

• Harmonics Load-Flow

• Frequency Sweep

The harmonic load-flow calculates harmonic indices for a single frequency, or for
all frequencies at which harmonics sources are defined. In the latter case, the
set of frequencies is determined automatically.
The frequency sweep calculates harmonic indices for all frequencies in the given
frequency range.

There is a special tool bar available for accessing the different commands for the
harmonic analysis. This toolbar can be displayed (when not already active) by
selecting the button on the main tool bar and then choosing the bar for
Harmonics from the pull-down menu.

The button bar on the main menu now offers two buttons to open a
pre-configured command dialogue:

• : Calculate harmonic load-flow

• : Calculate impedance frequency characteristics (Frequency Sweep)

The command dialogues can be also accessed through the main menu by

• selecting the Calculation →Harmonics →Voltage/Current Distribution...

option.

• selecting the Calculation →Harmonics →Impedance Frequency

Characteristic... option.

Furthermore if a harmonic load-flow is calculated a third button on this tool bar

as activated. The button opens the command dialogue for the ”Filter
Analysis“ (ComSh). All functions and their usage are described in this chapter.

Steady-State Power System Analysis 13-265

DIgSILENT PowerFactory Harmonics Analysis

13.1 Harmonic Load-Flow

To calculate the harmonic load-flow, use the to open the dialogue of the
command ComHldf. Fig. 13.1 shows the dialogue of the harmonic load-flow
command.

Figure 13.1: Harmonic load-flow command

For a detailed description of the harmonic calculations, see the section

Harmonics Analysis in the technical reference, where the analysis and the
harmonic indices are described in detail.

The following sections describe the different options available in the harmonic
load-flow.

Network-Representation, Harmonic Load-Flow

Balanced, positive sequence This option will use a one-phase, positive
sequence, network representation, valid for balanced symmetrical
networks. A balanced representation of unbalanced objects is used.

Unbalanced, 3 Phase (ABC) This option will use a full 3-phase, unbalanced
network representation.

Calculate Option
Single Frequency will perform a single harmonic load-flow calculation at the
given ”output“ frequency fshow or harmonic order respectively. A common
application for this mode is the analysis of ripple control systems. The

Steady-State Power System Analysis 13-266

DIgSILENT PowerFactory Harmonics Analysis

results of the analysis are shown in the single line diagram, in the same
way as for a normal load-flow at the fundamental frequency.

All Frequencies will perform harmonic load-flow calculations for all frequencies
for which harmonic sources are defined. These frequencies are gathered
automatically prior to the calculation. The results are stored in a result file,
which can be used to create harmonic bar graphs (see also section ??).

Nominal and Output Frequency, Harmonic Load-Flow

Nominal Frequency is the fundamental frequency of the system and the base
frequency for the harmonic orders (usually 50 or 60 Hz)

Output Frequency is the frequency for which the result is shown. In the case of
a Single Frequency calculation, this is the frequency for which an harmonic
load-flow is calculated. In case All Frequencies is selected, the calculation
itself is not influenced but only the shown results in the single line
diagrams, which are the results for the selected frequency.

Harmonic Order is used to check or to alter the output frequency. It is the

harmonic order equivalent of the output frequency. The harmonic order
times the nominal frequency always equals the output frequency. Here not
only integer numbers are valid.

Load-Flow and Results Variables

Result Variables is used to select the result object which will store the results
of the harmonic frequency sweep. See section 13.5, page 13-275 for more
information about specifying result variables.

Load-Flow is used to inspect and/or to adjust the load-flow command that is

used for the harmonic load-flow calculations.

Advanced Options, Harmonic Load-Flow

Rated Fundamental Frequency Values (IEEE) All values are rated on the
basis of the fundamental frequency values according to the IEEE
standards.

Rated Total RMS-Values (DIN) All values are rated on the basis of the RMS
values according to the DIN standards.

Steady-State Power System Analysis 13-267

DIgSILENT PowerFactory Harmonics Analysis

13.2 Frequency Sweep

To calculate impedances depending on the frequency, the impedance

characteristic can be computed for a given frequency range using the
ComFsweep by selecting the button.

An example of a harmonic frequency sweep command is shown in Fig. 13.2.

Figure 13.2: Harmonic frequency sweep command

The harmonic analysis by frequency sweep is normally used for analysing self
and mutual network impedances.

But not only self- and mutual-impedances can be analysed and shown. The
available voltage source models allow the definition of any spectral density
function. Hence, impulse or step responses of any variable can be calculated in
the frequency domain. Especially the analysis of series resonance problems is a
very common application.

The following sections describe the different options available in the harmonic
frequency sweep.

13.2.1 Network-Representation, Frequency Sweep

Balanced, positive sequence This option will use a one-phase, positive
sequence, network representation, valid for balanced symmetrical
networks. A balanced representation of unbalanced objects is used.

Steady-State Power System Analysis 13-268

DIgSILENT PowerFactory Harmonics Analysis

Unbalanced, 3 Phase (ABC) This option will use a full 3-phase, unbalanced,
network representation.

13.2.2 Impedance Calculation

The frequency sweep will be performed for the frequency range from “Start
Frequency” to the “Stop Frequency”, with the given “Step Size”.

An option is available for allowing an adaptive step size. Enabling this option will
normally speed up the calculation, and enhancing the results by using a smaller
step size where more detail is needed. The settings for the step size adaptation
can be changed on the “Advanced Options” page.

13.2.3 Nominal and Output Frequency, Frequency Sweep

Nominal Frequency is the fundamental frequency of the system and the base
frequency for the harmonic orders (usually 50 or 60 Hz)

Output Frequency is the frequency for which the result is shown in the single
line diagram. This value has no effect on the calculations itself.

Harmonic Order is used to check or to alter the output frequency. It is the

harmonic order equivalent of the output frequency. The harmonic order
times the nominal frequency always equals the output frequency. Here not
only integer numbers are valid.

Advanced Options, Frequency Sweep

A good way to speed up the simulation considerably is using the option
”Automatic Step Size Adaption” on the basic page of the ComFsweep
command. This option will enable the step size adaptation algorithm for the
frequency sweep.

With this algorithm the frequency step between two calculations of all variables
is not held constant but will be adapted according to the shape of the sweep.
When no resonances in the impedance occur, the time step can be increased
without loosing accuracy. If the impedance will start to change considerably with
the next step, the step sizes will be reduced again. The frequency step is set
that the prediction error will be according to the given values.

The parameters to adapt this algorithm are:

errmax Maximum Prediction Error (typical 0.01)

Steady-State Power System Analysis 13-269

DIgSILENT PowerFactory Harmonics Analysis

errinc Minimum Prediction Error (typical 0.005)

ninc Delay for Step Size Increase (typical 10 frequency steps)

The results of the continuous harmonic analysis are the same as for the discrete
analysis, except for the fact that they have been calculated for more frequencies.
The results are stored in the selected result object (“Result Variables”). See
section 13.5, page 13-275 for more information about specifying result variables.

13.3 Filter Analysis

The ”Filter Analysis“ command is a special form of the ”Output Calculation

Analysis“ command (ComSh). It is used to analyse the results from the previous
harmonic load-flow to the PowerFactory output window.

It outputs a summary of the harmonics for the terminals/busbars and for branch
elements at a specified frequency, which is given as the output frequency in the
ComHldf command. Also it reports the parameters and different variables for
the installed filters.

The filter analysis report generator can be activated with the button or by
using the output button in the main menu (see also chapter 25.6, page
25-517). This will open the same dialogue for the report of the harmonic results,
shown in Fig. 13.3.

Figure 13.3: Filter Analysis Report Command Dialogue

In the dialogue the output frequency, specified in the harmonic load-flow

command, is shown. There are four different reports to be chosen:

Busbars and Branches This option displays the results of the harmonic
load-flow for all node and branch element in the network. The distortion for
various electrical variables is printed and summarised.

Steady-State Power System Analysis 13-270

DIgSILENT PowerFactory Harmonics Analysis

Busbars/Terminals For the electrical nodes the rated voltage, the voltage at the
calculation frequency as well as RMS values and distortion at the nodes is
displayed.

Filter Layout The filter layout of all active filters in the network are calculated for
the given frequency. The rated values and impedances of the filter as well
as type and vector group are printed to the output window. Furthermore
the currents through the different components and the losses are shown.

Filter Results The filter results show the main layout of all filters in the network
for the calculation frequency. For a set of frequencies the voltages and the
currents through the filter are shown in a table format.

The default format used for the report in the output window is defined in Used
Format and can be set or changed by selecting the ”edit“ button .

13.4 Modelling Harmonic Sources

Every switched device produces harmonics and must therefore be modelled as a

harmonic source. In DIgSILENT PowerFactoryharmonic sources can be both
current or voltage sources.

The following models can generate harmonics:

• General loads, as far as they are modelled as a current source (which is

defined in the load type)

• Thyristor rectifiers

• PWM-converters which are generally modelled as harmonic voltage

source.

• Voltage sources, which are normally used for ripple control applications.

The spectrum of harmonic infeeds have to be defined using the “Harmonic

Source” type object (TypHmcCur). The spectrum may be entered as a balanced
or unbalanced spectrum. See Fig. 13.4 and Fig. 13.5. This object is a ‘type’
object, which signals that it may be used by many elements. More than one
current source load may, for example, use the same TypHmcCur object. No
ElmHmcCur object exists.
The spectrum object is independent of the kind of harmonic source, which may
be either a voltage or a current source. The decision whether harmonic sources
are fed into the system as harmonic voltages or as harmonic currents is
exclusively taken by the element to which the spectrum type is associated.

Steady-State Power System Analysis 13-271

DIgSILENT PowerFactory Harmonics Analysis

Figure 13.4: Balanced harmonic source type

Figure 13.5: Unbalanced harmonic source type

The quantities of the spectrum type are rated to current/voltage at fundamental

frequency in the balanced case. Hence, in case of a harmonic current source,
the actual harmonic current at frequency fh is calculated by

I h = kh e∆ϕh I1 eϕ1

Steady-State Power System Analysis 13-272

DIgSILENT PowerFactory Harmonics Analysis

where


I h/I 1 if balanced

Ia h/Ia 1 if unbalanced phase a
kh =

 Ib h/Ib 1 if unbalanced phase b


Ic h/Ic 1 if unbalanced phase c


 phi h - phi 1 if balanced

phiA h - phiA 1 if unbalanced phase a
∆ϕh =

 phiB h - phiB 1 if unbalanced phase b


phiC h - phiC 1 if unbalanced phase c

The values at the fundamental frequency, I1 and ϕ1 , are taken from a preceding
load-flow calculation. A normal load-flow calculation is therefore required prior to
a harmonic load-flow calculation.

In case of balanced systems in which only characteristic harmonics of orders 5,

7, 11, 13, 17, etc., occur, the option “Balanced/Unbalanced Sources” should be
set to “Balanced”. In this context, “Balanced” stands for characteristic harmonics.
In the balanced case, the harmonic frequencies are determined by the program,
while in the unbalanced case, the rated frequencies can be defined freely.

The user can now enter magnitude and phase angle of each harmonic
component. In case of harmonic sources which produce non-characteristic,
unbalanced or inter-harmonics, the option “Balanced/Unbalanced Sources” has
to be set to “Unbalanced”.

For the “Unbalanced” case, harmonic frequency, magnitude and phase angle of
each phase can be chosen individually for each harmonic frequency. This mode
thus covers every possible kind of harmonic source.

13.4.1 Frequency Dependent Parameters

Due to skin effect and variations of the internal inductance, resistances and
inductances are usually frequency dependent. This can be modeled by
associating a “frequency characteristic” to these parameters on the “Harmonics”
page of the corresponding dialogue. Two types of characteristic may be used:
either a polynomial characteristic (ChaPol), or an user defined frequency table
(TriFreq and ChaVec).
For the polynomial characteristic object, as depicted in Fig. 13.6, the following
formula is used: µ ¶b
fh
y(fh ) = (1 − a) + a
f1
The parameters a and b are specified in the ChaPol dialogue. The unit of y is
usually % of the corresponding parameter specified in the input mask. For

Steady-State Power System Analysis 13-273

DIgSILENT PowerFactory Harmonics Analysis

Figure 13.6: The frequency polynomial characteristic

example, the resulting line resistance is obtained by:

R(fh ) = R × y(fh )

Fig. 13.7 shows an example of the use of the polynomial characteristic for a line
type.

Figure 13.7: Frequency dependencies in a line type

The following objects have frequency dependent parameters which may be

defined by a frequency characteristic:

TypLne : Line Type

TypAsm : Asynchronous Machine Type

TypSym : Synchronous Machine Type

ElmShnt : Shunt/Filter

ElmVac : AC Voltage Source

ElmNec : NEC/NER

13.4.2 Waveform Plot

Steady-State Power System Analysis 13-274

DIgSILENT PowerFactory Harmonics Analysis

The waveform plot is used to display the waveform of a voltage or current after a
harmonics load-flow calculation. These harmonics are typically emitted by an
harmonic voltage or current source described in this chapter.

Using this plot a waveform is generated from the magnitude and the phase angle
of the harmonic frequencies. With this diagram a variable like the voltage or
current, which is defined in a harmonic source e.g. a power electronic device or
a load, can easily be shown as a time dependent variable. So the real shape of
the voltage can be seen and analysed.
For a more detailed description see section 24.6, page 24-476.

13.5 Definition of Result Variables

Before a frequency scan is performed, all variable of interest must be defined for
recording. This can be done by right-clicking an object, either in the single line
diagram or in the data manager, and selecting the option Define→Variable Set
(Harmonics Load-Flow) or Define→Variable Set (Frequency Sweep). This will
add a new, but still empty, variable set for the selected object to the result object
which is selected in the harmonic command dialogue.

All results of the harmonic analyses, except for the single frequency harmonic
load-flow, are stored in a normal result object (ElmRes). Such a result object
stores graphs of result variables vs. frequency. For more information about the
result object see chapter 25.1.

New result variables may also be added by pressing the button “Edit Result
Variable” ( ). This will bring the list of all variable sets which have been
defined already. Each variable set contains variables for a single object. See Fig.
13.8 for an example. A new variable set is defined by pressing the “New” button (
). The variable set manager (IntMon) will open when a new variable set is

created. The variable set manager is used to define the variables in the set. The
“Object” reference in the variable set manager must first be set to the object for
which result variables are to be added to the set. Secondly, the “Harmonic” page
has to be selected. This will show the list of all results that are available for the
selected object, for the harmonic analysis. See Fig. 13.9 for an example.
Result variables may be added or removed from the set of selected variables by
pressing the or buttons.

As the results of the discrete harmonic analysis are discrete, the plots made
from the result file should have the “Bars” option enabled in the Advanced page
of the SubPlot definition dialogue.

Steady-State Power System Analysis 13-275

DIgSILENT PowerFactory Harmonics Analysis

Figure 13.8: Example of a list of variable lists

Figure 13.9: Harmonic result variables for a terminal

Steady-State Power System Analysis 13-276

DIgSILENT PowerFactory Network Reduction

Chapter 14

Network Reduction

The network reduction command is able to create an equivalent network from

the current network definition. It writes the equivalent definition to a specified
folder in the current project.

To avoid a loss of data, the folder to which the equivalent network definition is
written is empty, for instance a new variant folder created by creating a new
project revision.

The network reduction is typically performed as described in the following

example.

A example network definition as depicted in Fig. 14.1 (transmission system) and

Fig. 14.2 (distribution system) is to be reduced.

Figure 14.1: Example transmission system

The distribution network is fed by the two busbars “Bus 5” and “Bus 6” in the

Steady-State Power System Analysis 14-277

DIgSILENT PowerFactory Network Reduction

Figure 14.2: Example distribution system

center of the transmission system.

To reduce the network,

• Activate the base case Study Case. This activates the original network.

• Create a new revision in order to keep the the original network definition. A
new revision is created by right-clicking the active project folder an
selecting New - Revision. The new revision creates variant folders in all
active grids, and creates a new study case.

• Run a load-flow

• Open the network reduction dialogue by entering ed red in the input

window (you can open and close the input window by clicking the “Input
Window” ( ) button in the data-manager).

• Select one of the new system stages. The reduced network definition will
be stored in this system stage.

• click on the E XECUTE button for starting the reduction.

The result of the network reduction is shown in Fig. 14.3. The transmission
network has been reduced to the equivalent representation by two AC Voltage
Sources (ElmVac) and a common impedance (ElmZpu).

Steady-State Power System Analysis 14-278

DIgSILENT PowerFactory Network Reduction

Figure 14.3: Reduced network

A load-flow calculation in the reduced network gives the same results for the
distribution network as for the original network.

Steady-State Power System Analysis 14-279

Optimization
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory Optimal Power-Flow

Chapter 15

Optimal Power-Flow

To be done.

Optimization 15-281
DIgSILENT PowerFactory Optimal Capacitor Placement

Chapter 16

Optimal Capacitor Placement

The button bar on the main menu bar offers four buttons to open a
pre-configured command dialogue:
• Setup of Optimization and execution

• Showing and setting up the list of available capacitor types

• Result output for nodes with new capacitors installed

• Result output for new capacitors recommended for installation

• Result output as a pre-configured text report

These buttons become available when the flexible tool bar is opened and the
symbol for optimal capacitor placement is selected. The idea for optimal
capacitor placement is to determine the location, type and the size of capacitors
to be installed in the nodes of the radial distribution network. The economic
benefits due to energy loss reduction are weighted against the cost of
installation of such capacitors while keeping the voltage profile of the system
within defined limits. The optimal capacitor placement problem has many
parameters, such as: the location, type, and the cost of capacitors, voltage
constraints, and load variations in the system.

16.1 Target Function

The optimization algorithm minimizes the annual total network cost. These cost
contain the following components:
• annual cost of capacitors (investment, maintenance, insurance), as
indicated on the description page of the capacitor type;
• cost of energy losses in the network, which can be reduced by the
capacitors due to the improved voltage profile and due to avoided transport
of reactive power;
• fictitious penalty cost for network nodes with a voltage outside the allowed
band (see figure 16.1).

Optimization 16-282
DIgSILENT PowerFactory Optimal Capacitor Placement

cmax

cmin

Umin Umax
Figure 16.1: Fictitious cost assigned by voltage band violations

16.2 Optimization Procedure

To find the optimal configuration of capacitors, PowerFactory applies 2 different

steps:

a. Sensitivity analysis to select the candidate buses for capacitor installation

b. Optimization step to determine the actual locations and sizes of the shunt
capacitors

The optimization is not only performed for a single load level, but for all load
levels described in a discrete scale that is handed over to PowerFactory. For
each of these load levels the voltage at the buses must be kept within the
allowed bandwidth. An additional vectorial characteristic describes the
probability of each of these load levels in hours/year, so that the cost of losses
can be calculated accordingly. The final result of the optimization process are
the locations for the installation of capacitors, the types and sizes of capacitors
to be installed and the capacitor switch positions for the different load levels.

16.2.1 Sensitivity Analysis

In this step test capacitors are installed at all busbars in the system and the
effect of the installation on the total annual system cost is evaluated. The size of
the test capacitors used to evaluate the cost benefit can be selected according
to 4 different options:

Optimization 16-283
DIgSILENT PowerFactory Optimal Capacitor Placement

• minimum available capacitor size is used;

• maximum available capacitor size is used;

• the capacitor size is determined by the peak reactive power requirements

of the load;

• the capacitor size best fitting to the reactive energy consumption of the
load is used;

16.2.2 Final optimization step

This step implements 2 different optimization procedures to determine the
optimum location of capacitors:

a. Gradient search - this search is fast and mostly will find a solution that
performs well - even if not the mathematically exact global optimum

b. Tabu Search - this search finds the exact optimum, but may be more
time-consuming.

16.3 Basic Options Page

Feeder
Please select the feeder for which the optimum capacitor placement should be
performed. The feeder is a special PowerFactory element which has to be
created before selecting it in this dialogue.

Optimization Level
The Optimization Level List offers 4 options:

• Remove previous solution - deletes any capacitors placed in the network

during the previous run of the optimization function

• Sensitivity only: Performs the sensitivity analysis and shows the result in
the text output window, but does not place any capacitors

• Fix Capacitors: Optimizes the network for fix capacitors, that is capacitors
without any voltage control

• Switched Capacitors: Optimizes the network for switched capacitors

performing voltage control.

Optimization 16-284
DIgSILENT PowerFactory Optimal Capacitor Placement

Figure 16.2: Basic Options Page

Sensitivity Analysis

• Min Shunt: the minimum available capacitor size is used

• Max. Shunt: the maximum available capacitor size is used

• Best fit to load: the capacitor size best fitting to the reactive energy
consumption of the load is used

• Depend on load: the capacitor size is determined by the reactive power

requirements of the load

Optimization Approach

• Gradient Search: Newton-Raphson-Optimization to detect local optimum

• Reactive Tabu Search: Tabu search to detect global optimum of reactive

power installation

Max. Number of Iterations

Optimization 16-285
DIgSILENT PowerFactory Optimal Capacitor Placement

Max. number of iterations as criterion for interrupting before termination of

optimization process.

Max. Execution Time

Max. duration until interrupting before termination of optimization process.

Connect Candidate Shunts

The optimization always generates a report describing the proposed capacitor
locations. If this field is checked, the capacitors are added to the data of the
network.

Outside Energy Cost

If this option is checked, the cost of losses are not considered in the target
function

Energy Cost
Energy cost applied (in specific cost per kWh)

Constraints - Allowed voltage

Voltage band, defined by lower limit (min. voltage) and upper limit (max. voltage)
in %. Different penalty cost apply for voltages within the allowed band and
outside.

Constraints - Reactive Power of all capacitors

If the sum reactive power of all capacitors is limited, the value is entered in this
field

Available Capacitors
When pushing this button, the list appears with all capacitor types available for
the optimization. The recommended way of entering types to this list is by
copy/paste from type libraries

16.4 Advanced Options Page

Discrete Scale and Trigger

Scale with discrete steps of the loading
The correct consideration of the load levels makes it necessary to have defined
a vectorial characteristic with scaling factors for each load during the defined

Optimization 16-286
DIgSILENT PowerFactory Optimal Capacitor Placement

Figure 16.3: Advanced Options Page

Figure 16.4: Example of Discrete Scale for loading level

load level. It is good practise to refer to this characteristic in the scaling factor on
the load-flow page of each load.

Time Vector

Optimization 16-287
DIgSILENT PowerFactory Optimal Capacitor Placement

Figure 16.5: Load characteristic

Vectorial Characteristic to describe the probability of each discrete loading level

(in hrs/yr)

Candidate Buses
Percentage of all candidate buses from the sensitivity analysis that are used for
the actual optimization process

Fix number of capacitors

If checked, each capacitor type in the list is used once only.

Penalty factor 1: dv > dvmax

Penalty cost for buses with voltage values outside the admissible band

Penalty factor 2: dv < dvmax

Penalty cost for buses with voltage values inside the admissible band

Optimization 16-288
DIgSILENT PowerFactory Optimal Capacitor Placement

Figure 16.6: Example of load curve

16.5 Results

The last three tool-bar buttons give access to the optimization results.

16.5.1 Result output for nodes with new capacitors

installed
When pressing the button , a list appears with all nodes named where
capacitors are listed.

16.5.2 Result output for new capacitors recommended for

installation
Pressing the button generates a list of capacitors distributed in the grid.

Optimization 16-289
DIgSILENT PowerFactory Optimal Capacitor Placement

16.5.3 Result output as a pre-configured text report

This button ( ) generates a report with the results of the sensitivity analysis
and the final optimization procedure.

Optimization 16-290
DIgSILENT PowerFactory Open Tie Optimization

Chapter 17

Open Tie Optimization

The open tie optimization is started when pressing the button for general tools
and selecting the button for open tie-point optimization:

• Open-Tie-Optimization

17.1 Optimization procedure

Input data for the optimization algorithm is a network with - in general - a

meshed topology. The optimization algorithm will proceed in the following way:

• A search is started for possible meshes in the network. Each found mesh
is closed first by closing all open switches in the loop. A load flow
calculation is then made, after which the loop is opened at the position with
the lowest current. Normally, the switch with the lowest current is opened,
but alternatively, the element with the lowest current can be taken out of
service when that current is lower than the lowest switch current.

• When opening a loop at the optimum location for active losses leads to an
overload on any line in the network, the algorithm will open a different line
instead.

• This is continued until no more closed loops can be found.

A final optimization step is following to search for further improvement.

The impact of opening disconnectors on voltage band violations is not checked.
The typical case in open-tie optimization however is that the open-tie-location
optimum for loss reduction also performs best for keeping the defined voltage
band.

Optimization 17-291
DIgSILENT PowerFactory Open Tie Optimization

17.2 Basic Options Page

Figure 17.1: Basic Options Page

Feeding points
The section of the network where the optimum open-tie points should be
determined is defined by a set of ”feeding points”.
Such feeding points can be

• external grids;

• the source-side switchbay of Lines (Overhead lines and cables);

• the source-side switchbay of transformers (if the complete transformer is

selected, the HV side is considered the feeding side);

• the combination of a busbar/terminal and a branch, in which case the

feeding direction towards the branch;

• a feeder object.

The feeding points are the positions where power is assumed to flow into the
network. Only meshes between the feeding points will be optimized. Meshes
connecting points in already optimized meshes are optimized also.

Update Database

Optimization 17-292
DIgSILENT PowerFactory Open Tie Optimization

If this box is unchecked, the proposals for opening disconnectors are listed in the
output report. If the box is checked, the status of the respective disconnectors is
also modified in the data of the network.

Force elements on outage when not switchable

The search for the position with the lowest current, which is to be opened, can
be extended by allowing the command to force and opening by setting an
element out of service, when no switch is available at the specific location.

Selection
The possible options are:

• Whole System: the complete system fed by the feeding points is radialized;

• One Grid: If the network is composed of several grids (e.g. transmission

and distribution), the grid to be optimized can be selected;

• User-defined: an user defined set is selected, the lines in this set are used
for radializing the network. The selection can be used to further limit the
area which is to be optimized. The first limitation is by defining feeding
points. Only meshes for which all elements are in the selection will be
optimized.

Load-Flow Command
Reference to the load-flow settings used by the optimization.

Output On
If this box is checked, the result report is directly written to the message window.

Output
Reference to the configuration dialogue of the output available after termination
of the optimization routine.

Optimization 17-293
Reliability Analysis
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory Reliability Assessment Functions

Chapter 18

Reliability Assessment
Functions

In general, the assessment of reliability indices for a power system network, or of

parts of a network, is the assessment of the ability of that network to provide the
connected customers with electric energy of sufficient quality.

Three different reliability assessment functions are provided:

Contingency analysis: The non-stochastic assessment of maximum/minimum

loadings and voltages for specific combinations of component outages

Voltage sag assessment: The assessment of the frequency of occurrence of

voltage sags.

Network reliability assessment: The assessment of statistical interruption

data for individual loads and busbars in the network.

Each of these calculation methods has it own typical applications. Contingency

analysis can be used to determine power transfer margins or for detecting risky
loading conditions. Network reliability assessment can be used to calculate
expected interruption frequencies and annual interruptions costs, or to compare
alternative network designs. Voltage sag assessment can be used to determine
the expected number of equipment trips due to deep sags.

18.1 Contingency Analysis

The contingency analysis will perform load-flow calculations for an user-defined

set of outage definitions. Each outage definition will take one or more primary
components out of service, after which a load-flow calculation is started. The
contingency analysis combines the results of all these load-flow calculations.

The contingency analysis is performed by the “Outage Simulation” command

(ComSimoutage). This command will perform load-flow calculations for all
stored “Outage Case” objects (ComOutage). Each outage case may define one
or more elements in the power system which will be taken out of service
simultaneously.

Reliability Analysis 18-295

DIgSILENT PowerFactory Reliability Assessment Functions

To quickly define a set of outage cases, a special “Prepare N-K Simulation”

command (ComNmink) is available. This command will pop-up when a
selection of elements is right clicked in the single line diagram, and Calculate -
Outage Simulation is selected. References to the selected elements will be
created in the preparation command automatically. Either an “n-1” or an “n-2”
outage simulation for the selected elements can then be prepared. Optionally, all
lines/cables, transformers or generators may be added to the selected elements.

18.1.1 Prepare N-K Simulation

The N-K preparation command will prepare and start the outage simulation
command (ComSimoutage) in the currently active study case.

The preparation command creates outage cases from a list of selected objects.
This list consist of

• All objects stored by shortcuts in the preparation command itself

• Optionally all lines and cables

• Optionally all transformers

• Optionally all asynchronous generators

Options:

Outage Level n-1: This will create a single outage case for each selected object

Outage Level n-2: This will additionally create outage cases for each unique
combination of two selected objects.

The preparation command will issue a warning when more than 100 outage
cases will be generated.

The preparation command will change the outage simulation command in the
currently active calculation case. It will replace all present outage cases by the
new set of outage cases. The preparation command will then pop-up the outage
simulation command.

The preparation command will pop-up when a selection of objects is right clicked
in the single line diagram, and Calculate - Outage Simulation is selected.
Shortcuts to the selected objects will then be stored in the preparation command
automatically.

In stead of right-clicking a selection in a single line diagram, it is possible to

create short-cuts to network elements manually. One or more objects in a
database manager can be copied, and short-cuts can be created in the

Reliability Analysis 18-296

DIgSILENT PowerFactory Reliability Assessment Functions

preparation command by right clicking the contents of the preparation command

and selecting Paste Shortcut. The selection of elements to outage in the
preparation command can also be created by the use of DPL scripts. The DPL
interface comprises the methods

• ComNmink.AddRef(object O), which will add a shortcut to object O

• ComNmink.Clear(), which will remove all shortcuts

• ComNmink.GetAll(), which will return all objects stored (by shortcuts) in the
preparation command.

18.1.2 Outage Simulation

The Outage Simulation command (ComSimoutage) will perform load-flow
calculations for all stored outage cases (ComOutage). Each outage case may
define one or more objects which will be taken on outage simultaneously prior to
calculating the load-flow for that outage case.

The outage cases stored in the outage simulation command are normally
automatically created by the N-K preparation command (ComNmink), but new
ones may be added by hand.

The outage simulation may also be controlled from a DPL script. It offers the
following DPL interfacing methods:

Execute(): executes the outage simulation, after resetting the results.

Reset(): resets the results.

ExecuteCntcy(ComSimoutage O): performs additional load-flows for all

outage cases stored in the object O, without resetting the results.

AddCntcy(ComOutage O): performs an additional load-flow for the outage

case in object O.

SetLimits(double Umn, double Umx, double Lmx): sets the voltage limits to
Umn and Umx and the loading limit to Lmx.

set ReportObjs(set s, int mode) returns the objects which are normally given
to the reporting command to produce the contingency reports. These are
ComOutage objects with the following parameters

Reliability Analysis 18-297

DIgSILENT PowerFactory Reliability Assessment Functions

Obj Monitored element

Elms Outaged Elements
Loading Loading
OutDisF Outage Distribution Factor
U voltage
Uarc angle
OutGen1 first outaged generator
OutGen2 second outaged generator
These objects can be used to generate user-defined reports.

The outage simulation calculates maximum loading, minimum and maximum

voltage levels, and outage distribution factors (ODF). The outage distribution
factor is defined as
∆Iij
ODFij,mn = (18.1)
Imn
where ∆Iij is the current change in branch i − j due to the outage of line m − n,
Imn is the pre-fault current in line m − n and all currents are single-base per-unit
values (Inet ).

The outage distribution factors are also calculated for generator outages, in
which case
∆Iij
ODFij,m =
Im
is used, where ∆Iij is the current change due to the outage of generator m and
Im is the pre-fault current in that generator.

The outage simulation produces 4 types of reports:

• Maximum circuit loading, see Fig. 18.2.

• Voltage ranges, see Fig. 18.3.

• Overloaded circuits, see Fig. 18.4.

• Voltage violations, see Fig. 18.5.

In addition, a contingency report can be printed for each analyzed outage case,
as depicted in Fig. 18.1.
The maximum loading report shows the highest loading found for all contingency
cases, for all branches. Additionally, the ODF for each branch, for the
corresponding contingency. Multiple contingencies (i.e. with more than one
outage) produce ODF’s of zero. The contingency case for which the highest
loading was found is given by number, and the outaged objects are listed. The
columns “Gen1” and “Gen2” show the first and second synchronous generator
on outage. The columns “Element ...” show the first, second, third, etc.

Reliability Analysis 18-298

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.1: Example of a contingency report

Figure 18.2: Example of a maximum loading report

non-generator object on outage. The maximum loadings are sorted from high to
low.
The voltage ranges report shows the highest and lowest voltage found for all
contingency cases, for al busbars and terminals. The outage case for both the
highest as well as for the lowest voltage are shown.

Figure 18.3: Example of a voltage ranges report

The overloaded circuit report shows all the outage cases for which a branch’s
loading exceeded the maximum loading. Additionally, the ODF for each branch,
for the corresponding contingency. Multiple contingencies (i.e. with more than
one outage) produce ODF’s of zero. More than one contingency case may be

Reliability Analysis 18-299

DIgSILENT PowerFactory Reliability Assessment Functions

shown for a single branch.

Figure 18.4: Example of an overloaded circuits report

The voltage violations report shows all outages cases for which a nodes voltage
was outside the specific range. More than one contingency case may be shown
for a single node.

Figure 18.5: Example of a voltage violations report

18.1.3 Outage Case

The Outage Case defines one or more objects which are to be taken on outage
simultaneously. The outage cases are normally analyzed by the outage
simulation command (ComSimoutage) in which they are stored. Each outage
case is a command on itself too, however. Pressing the E XECUTE button will
call the outage simulation command to analyze this sole outage case only. The
result of the outage analysis is shown in the single line graphics.

Reliability Analysis 18-300

DIgSILENT PowerFactory Reliability Assessment Functions

Possible objects to add to the outage case include

• Synchronous generators

• Lines, line routes, line sections

• Transformers

• Loads, motors

Line sections will be replaced by the line or line route of which they are a part.
Lines which have line routes are replaced by the first line route.

The outage of busbars/terminals is not supported. A single outage case, which

takes out all objects connected to the busbar/terminal can be used in stead.

18.2 Voltage Sag Analysis

An assessment of voltage sag tables for a selection of load points can be started
by

• Selecting one or more busbars and/or loads in the single line diagram or
the data manager, right clicking the selection and selecting ”Calculate
Voltage sag table...”

• clicking the button on the main toolbar to activate the reliability toolbar
(when not already visible), then clicking the button.

In both cases, the dialogue window of the voltage sag table command will open,
as depicted in Fig. 18.6.

Figure 18.6: Voltage Sag Analysis dialogue

The voltage sag table assessment command has the following options:

Basic Options.

Reliability Analysis 18-301

DIgSILENT PowerFactory Reliability Assessment Functions

Load selection points to the set of load points. A load point can be
defined by a busbar or terminal, or by a load.
Short-circuit command points to the short-circuit command that is used.
The options for the short-circuit type will be changed during the
voltage sag calculation, but other settings may be changed at will.
Results points to the result file that is filled with intermediate results.
Exposed area limit is the minimum remaining voltage for the voltage sag
calculation to continue calculating short-circuits at busbars further
away from the selected load points. If short-circuits at all busbar at a
certain distance away from all load points result in remaining voltages
at the load points higher than this limit, then no further short-circuit will
be analyzed.

Advanced Options. The advanced options page shows the various short-circuit
types that can be analyzed by the voltage sag assessment command. All
components for which a failure model has been defined, have only an
overall short-circuit frequency. It is not possible to define various
frequencies of occurrence for single phase, two-phase or three-phase
short0cicruits independently for each component. The relative frequency
for each type of short-circuit is entered for all components at the same time.

The voltage sag assessment works by analyzing various faults at all relevant
busbars. It starts with the selected load-points, and proceeds to neighbouring
busbars until the remaining voltage at all load-points does not drop below the
exposed area limit. The remaining voltages and the short-circuit impedances for
all load-points are written to a result file.

After all relevant busbars have been analyzed, the sag table assessment
continues by analyzing short-circuits at the middle of all lines and cables that are
connected between the relevant busbars. Again, all remaining voltages and
short-circuit impedances for all load-points are written to the result file.

After the whole exposed area has been analysed in this way, the result file
contains the values for ZF 1 , ZF 2 , ZF 0 , ZS1 , ZS2 , ZS0 and ura, uia, urb, uib, urc, uic
for the two ends of all relevant lines and cables and at their middle.
The written impedances are interpolated between the ends of a line and the
middle with a two-order polynomial. From them, and from the written remaining
voltages, the various source impedances are estimated. These estimated
impedances are also interpolated between the ends and the middle.
The interpolated impedances are then used to estimate the remaining voltages
in between the ends and the middle of the lines or cables. This quadratic
interpolation gives very good results also for longer lines, and also for long
parallel or even triple parallel lines.
The main advantage is, of course, a substantial increase of the overall
calculation speed.

Reliability Analysis 18-302

DIgSILENT PowerFactory Reliability Assessment Functions

18.2.1 Performing a Voltage Sag Table Assessment

A voltage sag table assessment is performed in two phases:
1. A result file with remaining voltages and short-circuit impedances is
created by executing the ComVsag command. This can be done by by
selecting one or more nodes and executing the Calculate / voltage sag
table ... option.

2. A voltage sag curve is created by selecting one or more of the nodes for
which the ComVsag command was executed and executing the option
Output Data / Create voltage sag plot ...
Alternatively,
• The ”Load selection” can be filled manually with objects. A load point is
defined by a terminal, a busbar, or by a single-connection element (a load,
motor, generator, etc.).

• A ”Voltage Sag Plot” can be created on a virtual instrument page manually,

and the load points can then be selected from the list of analyzed load
points.
If several objects are selected which are all connected to the same busbar, then
that busbar will be added only once to the set of load points.

The voltage sag assessment command will default to the selection which has the
”Used for : Voltage sag table” flag set. However, any other selection may be
used.

The voltage sag tables are not calculated until a voltage sag plot is constructed.
At reading the remaining voltages, short-circuit frequencies and short-circuit
impedances fro the result file, a voltage sag table is constructed for each
selected load point. Fig. 18.7 shows the part of the plot dialogue that is specific
to the voltage sag plot.
Because there is no single definition of a voltage sag, the plot offers a selection
of sag definitions:
• Minimum of Line-Neutral Voltages

• Minimum of Line-Line Voltages

• Minimum of Line-Line and Line-Neutral Voltage

• Positive Sequence Voltage

Secondly, the x-variable against which the sag frequency will be shown has to be
selected. Possible x-variables are
• Remaining Voltage

• Nom. Voltage at Shc-Busbar

Reliability Analysis 18-303

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.7: Voltage Sag Plot dialogue

• Fault clearing time

• Short Circuit Type

Additionally, the x-variable can be sub-divided according to a split-variable.

Possible split variables are

• no split

• any of the possible x-variables

It is not allowed to select the same parameter for the x-variable and the
split-variable.
An example of the resulting voltage sag plot, in accordance with the settings
shown in Fig. 18.7 is shown in Fig. 18.8.
The voltage sag plot always shows the annual frequency of occurrence on the
y-axis.

The example plot shows a bar for each load point for each x-variable, which is
the Remaining Voltage. All three loads seem to suffer either deep sags
(remaining voltage less than 0.4 p.u.), or very shallow sags, although the values
for 0.8 p.u. are also significant. Each bar is subdivided to the Nom. Voltage at
Shc-Busbar. Apparently, the shallow sags are cause by low voltage network, as
well as the very deep sags. The high voltage network seems to cause moderate
voltage sags. This is cause by the fact that the low voltage networks are radially
operated and the higher voltage networks are meshed.

More detailed information about a certain value in the voltage sag plot can be
obtained by pointing at a bar or part of a bar and holding the mouse to let the
balloon help pop up. Fig. 18.9 shows and example of the information that the
balloon help provides.

Reliability Analysis 18-304

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.8: Example Voltage Sag Plot

Figure 18.9: Balloon Help in the Voltage Sag Plot

The Voltage Sag Plot dialogue offers a R EPORT button, which cause the
voltage sag plots to be written to the output window. A table for each selected
load point will be written in accordance to the selected voltage sag definition,
x-variable and split-variable. An example of a voltage sag table is shown below.
The reported voltage sag tables also show the totals for each row and column.

DIgSI/info - ’Grid\TA2.ElmTerm’
col : Remaining Voltage (Volt.Sag) [p.u.]
row : Nom. Voltage at Shc-Busbar (Unom Shc) [kV]
val : Frequency of Shc (Sag Freq.) [1/a]
-------------------------------------------------------------------------------
| 0.20 0.40 0.60 0.70 0.80 0.85 0.90 0.95 1.00 |
-------|----------------------------------------------------------------|------
10.0 | 1.56 0.94 0.00 0.00 0.00 0.00 0.00 2.25 6.75 | 11.50
50.0 | 1.45 1.52 0.00 0.00 0.83 0.09 0.12 1.08 5.57 | 10.66
150.0 | 3.50 2.32 1.67 0.00 0.00 0.00 0.00 0.00 0.00 | 7.50
380.0 | 0.00 1.25 0.00 0.00 1.25 0.00 0.00 0.00 0.00 | 2.50
-------|----------------------------------------------------------------|------
| 6.52 6.04 1.67 0.00 2.08 0.09 0.12 3.33 12.32 | 32.16
-------------------------------------------------------------------------------

Reliability Analysis 18-305

DIgSILENT PowerFactory Reliability Assessment Functions

18.3 Network Reliability Assessment

An analytical assessment of the network reliability indices (transmission,

sub-transmission or distribution level) is started by

• clicking the button on the main toolbar to activate the reliability toolbar
(when needed)

• clicking the button

The Reliability Analysis dialogue, as depicted in Fig. 18.10 will now appear.

Figure 18.10: Reliability Analysis dialogue

A reliability assessment will be started when the ”Execute” button is pressed.

The calculation time required for a reliability assessment can range from a few
seconds to several hours for a large network. A running reliability assessment
can be interrupted by pressing the Break button ( ) on the main toolbar.

18.3.1 Calculations Options

Basic Options
The following options are available:

Mode This parameter determines the calculation method.

Reliability Analysis 18-306

DIgSILENT PowerFactory Reliability Assessment Functions

State Enumeration This will start an analytical reliability assessment in

which all relevant system states are analyzed one by one. The results
of all these analysis are summed together, using the failure statistics.
Monte Carlo simulation . This will start a sequential simulation of the
network, during which failures will be introduced at random. All
encountered system states are analyzed. The results are summed
together, using the duration of each system state. The simulation is
repeated many times to reach a statistical accuracy.

Analysis

Generator - Load This will start an analysis in which only the available
generator capacity is compared to the load demand at actual. The
network is not considered.
Network, connectivity analysis This will start an analysis in which the
whole network will be involved. A load is assumed to be supplied
when it is still connected to a source of power. Possible overloading of
components is not regarded.
Network, load-flow analysis This will start an analysis during which
load-flow calculations are made to check for possible overloading.
Generator re-dispatch, load transfer and load shedding will be used to
alleviate overloads.

Loads Load curves The given area load demand curves will be used during
the reliability assessment.
Single Peak Load The single peak load levels as entered for the load-flow
calculations will be used.

The Monte Carlo simulation comes with some additional parameters:

Start time The start time for the simulation.

Stop Time This stop time for the simulation.

Max. Runs The maximum number of simulations. Lower values (< 100) are
used mainly for checking.

Max. Error The maximum allowed relative error in the results. The simulation
from ”start time” to ”end time” will be repeated until all relative errors in the
averaged results drop under this level, or when the number of simulation
equals ”Max. Runs”.

Random Numbers The letters ”A..K” each stand for a pre-defined random
number ”seed”, ”auto” will start each simulation with a different random
”seed”. An identical simulation will re-produce exactly the same results
when ”A..K” is selected, because the same quasi-random numbers will be
used during the simulation. Slightly different results will be obtained when
”auto” is selected.

Reliability Analysis 18-307

DIgSILENT PowerFactory Reliability Assessment Functions

Confidence The confidence level determines the probability for which the
correct results lay within the confidence interval around the calculated
results. A high value (> 95%) may dramatically increase the calculation
time.

A selection can be made for the failures that are to occur and analyzed in the
state enumeration or the Monte Carlo simulation. A selection of objects that may
fail can be made, and certain types of failures can be enabled or disabled.

Selection
Whole System will regards failures in all components.
One Grid will only regards failures in the components residing in the
selected grid folder
User Defined will only regard failures in the selected components
Common mode, Busbars / terminals, etc. each of these types of failures can
either be enabled or disabled. Disabling the transformer failures, for
instance, which assume 100 /reliable transformer, by disregarding all
transformer failure models.

FEA options
A failure effect analysis is made for each system state that occurs either during
the state enumeration of during the Monte Carlo analysis.
Available options:

Use power restoration switches. Enabling this option will enable the fault
isolation and power restoration by network reconfiguration (switching).
Use all separation switches This option will make the fault separation
functions to use all available fault isolation switches.
Only use marked separation switches This option will make the fault
isolation functions to only use those separation switches which have
been marked as ”available for fault separation”.
Outage definitions.
Ignore existing will ignore any user defined power restoration scheme
stored in the reliability assessment command. Only default power
restoration schemes will thus be used. Disabling this options will
make the reliability assessment to use the power restoration schemes
stored inside, overruling.
Create definitions will write all power restoration schemes as used in the
reliability assessment in the calculation command as ComOutage
objects. These schemes can be replayed, edited, and reused in the
next analysis (by disabling the ”Ignore”option).

Reliability Analysis 18-308

DIgSILENT PowerFactory Reliability Assessment Functions

Important outages only this will only write restoration schemes in case
power to some loads could be restored by network reconfiguration, or
in case of a load-flow problem.
Overloading is used when the ”Analysis” option on the ”Basic Options”page is
set to ”Network, load-flow analysis”.
Max. Loading of Edge Element Defines the overload limit which is used
for the calculation of energy at risk and for overload alleviation.
load-flow command is the used load-flow command.

Advanced Options
The following advanced options are available.

Accuracy of characteristic Load states This options is only available when

the
”Loads” option on the ”Basic Options”is set to ”Load Curves”. The area
load models normally contain a high number of load points (an annual
hourly peak load curve contains 8760 point). The reliability assessment
does not analyze each and every point, but uses the redundancy in the
load point data to cluster all load values into a number of characteristic load
points. The maximum error made by using clusters is set here. Thanks to
the progressive clustering technique, this accuracy will be met by clusters
with lower load values whereas clusters with higher load demand will have
lower error. A value of 10 % is therefore normally good enough.
Number of contingency cases in report The ‘Contingency’ report for the
network reliability assessment shows contingencies and the contributions
of these contingencies to the overall reliability indices. For larger networks,
or for higher max. contingency levels, the number of analyzed
contingencies will be very high. Therefore only the top N contingencies,
sorted to the ENS index, will be reported. The number N is entered here.
Result Object points to the used result object in which the results of the Monte
Carlo simulation are stored.
Output of Results points to the reporting command object in which the report
can be selected.
Colors for Isolated grids coloring mode This colors are only used in the
‘mode FEA’ and are used to show the reaction of the system to the
selected faults.

18.3.2 System State Enumeration

The enumeration method analyses all relevant possible states of the system one
by one. A fast “topological” state enumeration method is used which ensures

Reliability Analysis 18-309

DIgSILENT PowerFactory Reliability Assessment Functions

that each possible system state is only analyzed once. Realistic state
frequencies (average occurrences per year) are calculating by considering only
the transitions from a healthy situation to an unhealthy one and back again. This
is important as the individual system states are analyzed one by one, and the
(chronological) connection between them is therefore lost.

The enumerated calculation method is fast enough for quick investigation of

large distribution networks and yet does not compromise accuracy. Exact
analytic averages are calculated. Distributions of reliability indices, however,
cannot be calculated. The average annual unavailability in hours/year can be
calculated, but the probability that this unavailability is less than 15 minutes for a
certain year cannot.

The state enumeration algorithm may include independent overlapping failures

as well as common mode failures and maintenance schedules. Due to the use of
the Weibull-Markov model, annual interruption costs can also be assessed
accurately.
The principle flow diagram for the whole reliability assessment by state
enumeration is depicted in Fig. 18.11.

Figure 18.11: Principle flow diagram

18.3.3 Monte Carlo Simulation

The Monte Carlo simulation performs a chronological simulation of the failures in
the system, using a stochastic number generator. By drawing numbers from this
generator, the stochastic time of the following failures are determined, and the
simulation advances from failure time to failure time, whilst drawing new random
numbers to determine the next failure after a repair has been finished.

After each failure, the system state is analyzed in the same way as it is analyzed
during the state enumeration method. In fact, there is no real difference between

Reliability Analysis 18-310

DIgSILENT PowerFactory Reliability Assessment Functions

a system state reached during a state enumeration or during a Monte Carlo

simulation.

The Monte Carlo simulation is much slower than the state enumeration, but has
the advantage that distributed results can be obtained.

After the Monte Carlo simulation has finished, it is possible to select one or more
loads in the single line diagram or the database manager and to select ’Output
data - Crate Probability Density Plot”. A list of reliability indices will appear, and
selecting one will create a probability density plot for the selected loads.

18.3.4 Failure Effect Analysis

The kernel of the reliability assessment is the analysis of the reaction of the
system to specific contingencies. This analysis is performed by the failure effect
analysis (FEA) function. The FEA function is a stand-alone function which can
also be started separately.

Basically, a FEA analysis consists of 4 steps

• Fault clearance
• Fault isolation
• Power Restoration
• Overload alleviation

The failure effect analysis for the network assessment may be carried out with or
without overload alleviation. Overload alleviation is performed by calculating an
AC load-flow, searching for overloaded branches and performing load transfer
and load shedding. Disabling the overload alleviation for networks where
overloads due to contingencies are not expected to occur may speed up the
calculations considerably.

The failure effect analyses will be performed for each contingency, for each
characteristic load point and for each year or load growth. For each of the
system states, one or more failures are present in the system. All failures are
assumed to be active, i.e. they will cause an intervention by the protection
system. The system is assumed to react to these short-circuits by the immediate
opening of one or more protection switches, followed by manual or automated
separation of the faulted equipment and the restoration of power to the
remaining part of the protected area. This is illustrated in Fig. 18.12. This figure
shows protection breakers, restoration switches and separators.

Fault Clearance
The fault clearance functions assumes 100% selectivity of the protection. In the
pre-processing phase of the reliability assessment, all breakers in the system

Reliability Analysis 18-311

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.12: Fault clearance and power restoration

that can be tripped by an overcurrent or distance relay, fuse, or any other kind of
relay, are marked as “protection breakers”. Fig. 18.13 shows a simple network
with four loads, a breaker and a back-stop switch. The current system state
which is to be analyzed for possible load interruptions is the one with a
short-circuit on line route “LR2”.

Figure 18.13: Short circuit on line

At fault clearance, a topological search is started at all faulted components. This

search will find the smallest network area around each faulted component which
is confined by protection breakers only. This smallest area will be isolated from
the rest of the network if these protection breakers are opened. This set of
protection breakers is further reduced by regarding only those breakers which
would actually interrupt a fault current. Breakers further down a feeder past the
fault position, i.e. breakers that would not see a fault current, will not be opened.

The fault clearance phase is ended by opening the found minimum set of
protection breakers. If it is found impossible to isolate the faulted component
from all synchronous generators or external networks by protection breakers
only, then an error message will be written and the reliability assessment will
terminate.

Reliability Analysis 18-312

DIgSILENT PowerFactory Reliability Assessment Functions

The area around the faulted components which is isolated by the protection
breakers is called the “protected area”. Fig. 18.14 shows the example network
after the fault clearance functions have opened the protection breaker. The
protected area is the whole bottom line feeder, and load 1, 2, and 3 are
interrupted.

Figure 18.14: Protected area

Fault Isolation
If the option Use Power Restoration Switches has been enabled in the command
dialogue, and one or more separation and one or more power restoration
switches have been found, an attempt is made to minimize the effects of the
faults by re-connecting as many loads back to the healthy part of the system as
possible.

After the protected area and the tripped breakers have been determined during
the fault clearance phase, a search is started for the minimum separated area.

The fault separation and power restoration both make use of the same
topological search for switches as has been used to find the protection breakers
during the fault clearance phase. The fault separation phase starts a topological
search at the faulted components for the smallest area around these
components which is confined by separating breakers. This smallest area will be
isolated from the remaining network by opening these separating switches.
Either all closed switches qualify for separator, or only those switches which
have been marked as ‘use for fault separation’, when the option “Only use
marked separating switches” was enabled in the reliability command dialogue.

The result of the search for the separation switches is a set of separating
switches which will, when opened, isolate the smallest possible area around the
faulted elements from the rest of the network. This area is called the “separated
area”. The separated area is smaller than or equal to the protected area. It will
never extend beyond the protected area.

The area between the protected and the separated area is called the “restorable
area” because, principally, power may be restored to those areas. Fig. 18.15
shows the example network with the opened separation switches. The
separated area now only contains the faulted line route. Two restorable areas

Reliability Analysis 18-313

DIgSILENT PowerFactory Reliability Assessment Functions

result from the fault separation; the area which contains load 1, and the area
which contains load 2 and 3. Power to load 1 is restored by (re)closing the
protection breaker. The left-most separation switch is remote controlled and has
a switching time of 3 minutes. The protection breaker is also remote controlled,
and load 1 is therefore restored in 3 minutes (=0.05 hours). Load 2 and 3 are still
to be restored.

Figure 18.15: Fault isolation and power restoration

Power Restoration
If the option Use Power Restoration Switches has been enabled in the command
dialogue, then a search will be started for the minimum number of restoration
switches needed to restore as large a part of the protected area as possible.
During this search, only the opened protection switches and the normally open
switches that have been marked as ’available for power restoration’, are
considered.

The power restoration phase uses a topological search for all power restoration
switches along the borders of the restorable areas. Each of these switches
which are connected to a still supplied area are marked as possible candidates
for power restoration. For each restorable area, only the fastest candidate switch
is closed. Each restorable area that is reconnected to the supplied network
again is called a “restored” area. Fig. 18.16 shows the example network in which
power to load 1 is restored by (re)closing the protection breaker. Power to load 2
and 3 is restored by closing the back-stop switch. Because the back-stop switch
has a switching time of 30 minutes, load 2 and 3 are restored in 0.5 hours. The
network is now in the post-fault condition.
All loads and busbars in a separated area are considered to be interrupted for
the duration of the repair, which normally is in the order of hours. All loads and
busbars in a restored area are considered to be interrupted for the time needed
to open all separators and to close all power restoration switches. Each switch
can be given an individual actuation time. Effects of automation and remote
control can thus be analyzed by lowering the actuation times for the remote
controlled switches.

In order to enhance the transparency of the network reliability assessment, the

Reliability Analysis 18-314

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.16: Power restoration by back-stop switch

system reaction to user selected faults can be made visible in the single line
graphs. The different areas and the protection, separation and restoration
switches will be colored differently. This gives a quick insight in the possible
impact of certain faults or fault combinations.

18.3.5 Overload Alleviation and Power at Risk

Many reliability calculations in radial distribution systems may be carried out by
assuming that an overloading of lines due to the outage of one or more
components are seldom. In such a case, the overload verification may be
disabled, thus increasing the calculation speed. A connection algorithm is used
to check if a certain busbar or load is still physically connected to a generator or
external network. When so, the load or busbar is considered to be supplied.

In meshed structures, or in cases where overloading is important, i.e. when

there is a risk that increasing loads would lead to overloads, an overload
verification must be used. For all contingencies which are analyzed in the
reliability assessment, an AC load-flow is made for the post-fault system state.
The post-fault system-state is reached after the fault clearance, fault separation
and power restoration processes have finished.

Fig. 18.17 shows that the example network does have a line overload in the
post-fault condition: line “LnA” is loaded to 122%.

Figure 18.17: Overloaded post-fault condition

Reliability Analysis 18-315

DIgSILENT PowerFactory Reliability Assessment Functions

Load Transfer
In many distribution systems, it is possible to transfer loads from the one feeder
to the other. If both feeders are being considered in the reliability assessment,
and when the normally open switch between them is marked for power
restoration, the transfer will be automatically performed in the power restoration
phase.

In some cases, however, the transfer switch and/or the alternative feeder are not
included in the network model for which the reliability assessment is made. Such
may be the case when a (sub-)transmission network is analyzed, where the
connected distribution networks are modeled as single lumped loads. Transfer
switches that connect two distribution networks will then not be visible. In that
case, the possibility to transfer parts of the lumped load model to other feeders
can be modeled by entering a transfer percentage at each lumped load. This
transfer percentage defines what part of the lumped load can be transferred
‘away’ from the analyzed network, without specifying to which feeder(s) that part
is transferred.

The use of the load transfer percentage is only valid when load transfer is not
expected to result in an overloading of the feeders which pick up the transferred
loads.

Load transfer is used in the overload alleviation prior to the calculation of power
at risk (see the next section). The power at risk is considered to be zero if al
overloads in the post-fault condition can be alleviated by load transfers alone.

Load Shedding
In the example network of Fig. 18.17, loads 2, 3 and 4 all contribute to the line
overload. Some of these loads therefore have to be shed. There are three basic
shedding schemes that can be used:

• Optimal load shedding

• Priority optimal load shedding
• Discrete optimal load shedding

Optimal load shedding presumes that all loads can be shed to any amount. The
target is then to find a shedding scheme in which as little load is shed as
possible. In the example network, it does not matter which load is shed, as a
MW reduction of any load will result in equal reduction of the line overloading. In
more complex (meshed) networks, with more than one overloaded branch, a
reduction of the one loads may have a higher impact on the total overloading
than a reduction of another load.

The reliability assessment functions use linear sensitivity indices to first select
those loads which have a contribution to the overloads at all. A linear

Reliability Analysis 18-316

DIgSILENT PowerFactory Reliability Assessment Functions

optimization is then started to find the best shedding scheme for alleviating all
overloads, which will minimize the total amount of shed load. The resulting
minimum amount of shed load is called the “Power at Risk”, because it equals
the minimum amount of load that has to be shed in case of the initial network
fault occurring. The power at risk is multiplied by the duration of the system state
to get the “Energy at Risk”. The total energy at risk for all possible system states
is reported after the reliability assessment has finished as the “System Energy
At Risk” (SEAR). Fig. 18.18 shows the calculated energy at risk. Because the
line was overloaded by 0.53 MW and the faulted line has an outage expectancy
of 0.15 h/a, the energy at risk is 0.08 MWh/a.

Figure 18.18: Energy at Risk

The priority load shedding is performed after the power at risk has been
determined. The priority optimal load shedding considers the load priorities
defined for each load. The overload alleviation functions will use the load
sensitivity indices to calculate the lowest possible shedding priority in such a way
that when all loads which have equal or lower priority would be shed, then all
overloads would be alleviated. From this, it is clear that loads with higher
priorities are not needed to alleviate the overloading. The priority load shedding
is performed by repeating the linear optimization for the lower priority loads only.
Fig. 18.19 shows that when load 4 is set to a higher priority, load 2 is shed in
stead.

Figure 18.19: Priority load shedding

The discrete optimal load shedding is performed together with the priority load
shedding. Mixing discrete and priority load shedding does not require additional
calculations. The discrete load shedding scheme uses the fact that each load
can only be shed in a fixed amount of steps. The number of possible steps is
entered at each load. The discrete shedding scheme is calculated by
transforming the linear optimization problem into a discrete optimization
problem. Solving this linear optimization problem results in a higher or equal

Reliability Analysis 18-317

DIgSILENT PowerFactory Reliability Assessment Functions

total shed power. Fig. 18.20 shows the example network where all loads can
only be shed completely. As load 3 only demands 0.35 MW, and the overload is
0.53 MW, it cannot contribute to overload alleviation. Shedding load 2 therefore
leads to the minimum amount of shed load.

Figure 18.20: Discrete load shedding

18.4 Calculated results

The network reliability assessment produces two sets of indices:

• Load point indices

• System indices

Load point indices are calculated for each individual load point. Many system
indices are calculated from these load point indices.

This section gives the principle equations for the various reliability indices. The
actual reliability assessment calculations use somewhat more complex
calculation methods. Nevertheless, the shown principle equations can be used
for hand calculations or for getting a better understanding of the produced
reliability assessment results.

In the definitions for the various reliability indices, the following parameters are
used:

Ci : The number of customers supplied by load point i

Ai : The number of affected customers for an interruption at load point i

Frk : The frequency of occurrence of contingency k

Prk : The probability of occurrence of contingency k

C : number of customers

A : number of affected customers

Reliability Analysis 18-318

DIgSILENT PowerFactory Reliability Assessment Functions

The load point frequency and expectancy indices

ACIF : Average Customer Interruption Frequency

ACIT : Average Customer Interruption Time

LPIF : Load Point Interruption Frequency

LPIT : Load Point Interruption Time

are defined as
X
ACIFi = Frk ·fraci,k [1/a]
k
X
ACITi = 8760 · Prk · fraci,k [h/a]
k
LP IFi = ACIFi · Ci [1/a]
LP ITi = ACITi · Ci [h/a]
ACITi
AIDi =
ACIFi
where i is the load point index, k is the contingency index, and fraci,k is the
fraction of the load which is lost at load point i, for contingency k. For lost loads,
or for loads that are shed completely, fraci,k = 1.0. For loads that are shed only
partly, 0.0 ≤ fraci,k < 1.0.

For the analyzed system:

SAIFI : System Average Interruption Frequency Index, in [1/C/a], is the mean

interruption frequency found by dividing by the total amount of customers in
the analyzed system.

CAIFI : Customer Average Interruption Frequency Index, in [1/A/a], is the mean

interruption frequency found by dividing by the total amount of affected
customers. i.e. customers that will suffer interruptions, in the analyzed
system.

SAIDI : System Average Interruption Duration Index, in [h/C/a], is the mean time
per year that customers are interrupted, by dividing by all customers.

CAIDI : Customer Average Interruption Duration Index, in [h], is the mean

duration per interruption.

ASAI : Average Service Unavailability Index, is the probability of having one ore
more loads interrupted.

ASUI : Average Service Unavailability Index, is the probability of having all load
supplied.

Reliability Analysis 18-319

DIgSILENT PowerFactory Reliability Assessment Functions

P
ACIFi · Ci
SAIF I = P [1/C/a]
Ci
P
ACIFi · Ci
CAIF I = P [1/A/a]
Ai
P
ACITi · Ci
SAIDI = P [h/C/a]
Ci
SAIDI
CAIDI = [h]
SAIF I
ASAI = 1P− ASU I
ACITi · Ci
ASU I = P
8760 · Ci

The load point energy indices

LPENS : Load Point Energy Not Supplied

LPES : Load Point Energy Shed [MWh/a]

are defined as

LP EN Si = ACITi · (Pcdi + P
csi ) [MWh/a]
LP EARi = ACITi · Pcri [MWh/a]
LP ESi = ACITi · Pcsi [MWh/a]

Where

• Pcdi is the weighted average amount of power disconnected

• Pcri is the weighted average amount of power at risk
csi is the weighted average amount of power shed
• P

at load point i.

For the analyzed system,

ENS : Energy Not Supplied, in [MWh/a], is the total amount of energy which is
expected not to be delivered to the loads.

SEAR : System Energy At Risk, in [MWh/a], is the total amount of energy at risk
for the system.

SES : System Energy Shed, in [MWh/a], is the total amount of energy which is
expected to be shed in the system.

AENS : Average Energy Not Supplied, in [MWh/C/a], is the average amount of

energy not supplied, for all customers.

ACCI : Average Customer Curtailment Index, in [MWh/A/a], is the average

amount of energy not supplied, for all affected customers.

Reliability Analysis 18-320

DIgSILENT PowerFactory Reliability Assessment Functions

X
EN S = LP EN Si [MWh/a]
X
SEAR = LP EARi [MWh/a]
X
SES = LP ESi [MWh/a]
EN S
AEN S = P [MWh/C/a]
Ci
EN S
ACCI = P [MWh/A/a]
Ai

The load point interruption costs are defined as

X
LP EICi = LP EICi,k [M$/a]

where LP EICi,k is the average interruption costs for load point i and
contingency case k, considering the load point interruption costs function and
the assessed distribution of the durations of the interruptions at this load point for
contingency case k. The interruption costs are calculated differently for different
cost functions. All costs functions express the costs as a function of the
interruption duration. For cost functions expressed in money per interrupted
customer, the number of interrupted customers is estimated for each interruption
as the highest number of customers interrupted at any time during the whole
interruption duration.

For the analyzed system,

EIC : Expected Interruption Cost [M$/y], is the total expected interruption costs.

IEAR : Interrupted Energy Assessment Rate [$/kWh], is the total expected

interruptions costs per not supplied kWh.

X
EIC = LP EICi [M$/a]
EIC
IEAR = [$/kWh]
EN S
Additional calculated indices for the load points:

AID : Average Interruption Duration [h]

Additional calculated indices for the busbars/terminals:

AID : Average Interruption Duration [h]

LPIF : Yearly Interruption Frequency [1/y]

LPIT : Yearly Interruption Time [h/y]

Reliability Analysis 18-321

DIgSILENT PowerFactory Reliability Assessment Functions

18.5 Application Notes

These application notes are meant to get you starting with your reliability
analysis. Basically, a reliability assessment project has the following phases

• Specification of targets. The selected targets will determine which kind of

calculation has to be made.

• Data collection. In addition to the electrical data, a stochastic reliability

analysis asks for failure data, power restoration schemes, maintenance
schedules, load forecasts, interruption costs, etc. It is important not to start
by searching for the most accurate data that one could find, but to start a
preliminary calculation with some best-guess data.

• Performing preliminary calculations, adjusting the analysis, checking input

data. Interpreting results and changes in results. This phase is mainly to
let you gather experience, and to find out how the results are being
influenced by the input data.

• Data collection. In this phase, the search is for the best data that is
available. The results of the previous phase are determining which data is
important and which is not.

• Performing analysis and reporting.

The first decision to make is about the kind of reliability assessment that is to be
performed. If no stochastic failure data is available, or when a “n-1” analysis has
to be made, then a contingency analysis is required.

Generator reliability assessment is suited for calculations in a relatively small

network or smaller networks with on-site generation in parallel to a weak or
unreliable connections to external networks. If failure and maintenance data is
available for the on-site generators and when load forecasts can be made for all
major loads, then the ability of the on-site generators to feed the loads in island
conditions, or a minimum loading of the external feeders, can be assessed. This
is a typical case for medium size or large industrial complexes in remote areas.

Stochastic network reliability assessment is required for assessing load-point

reliability indices as well as overall network indices in regard to network
adequacy. Network reliability assessment is more demanding then either
contingency analysis or generator reliability assessment, in terms or required
input data as well as in terms of required computation time and the amount of
produced results.
Stochastic network reliability assessment is used to analyze small, medium size
and large distribution networks, (sub-)transmission and industrial networks.

Reliability Analysis 18-322

DIgSILENT PowerFactory Reliability Assessment Functions

18.5.1 Contingency Analysis

This part of the manual is in preparation.

18.5.2 Network Reliability Assessment

The minimal required data for network reliability assessment are
• A valid electrical model of the electrical power system including all relevant
primary equipment

• Failure models for all relevant equipment

• Common mode failure models

• Basic description of the protection schemes

• Switching times for emergency network reconfigurations

Additionally, the following data can be used
• Maintenance schedules for all relevant equipment

• Load forecasts

• Interruption costs functions (“customer damage functions”)

• Load priorities, transfer percentages and shedding steps

After the electrical model of the electrical power system has been tested by
load-flow calculations or - preferably - by running a “n-1” contingency analysis,
the preparations for stochastic reliability assessment can start with the entering
of failure data for lines and cables. The required failure model is described in
section 18.7.2, page 18-334.

A new line failure model can be created by opening the dialogue window of a
line/cable element (ElmLne) or a line/cable type (TypLne). On the reliability
page, you can select a failure model. This will open a database browser where
you can select a failure models. A new failure model will be created when you
press the “New Object” button ( ) in that browser.

In most applications it is efficient to select failure data for the line/cable types,
rather than for the elements. Assigning a failure model to a type means that all
elements that use that type will automatically inherit the failure data. In some
cases, as for lines and cables, the failure model is entered in per-length units,
which will be multiplied by the lengths of the elements. In other cases, as for
transformers, the failure data is entered as-is.

If a certain type is used by many elements, then all these elements will inherit
the same failure model from that type. When some elements require specific

Reliability Analysis 18-323

DIgSILENT PowerFactory Reliability Assessment Functions

failure data, then the inherited failure model can be overruled by specifying an
element failure model.

After failure data has been entered, you must enter the basic protection scheme.
If no protection data has been entered at all, then the fastest way is to create a
“dummy” fuse object in one of the cubicles after which this fuse is copied to other
cubicles.
To create a dummy fuse:

• Right-click a cubicle in the single line diagram with the data cursor. Select
“New device - Fuse ...”

• Select a new type: choose “Select project Type”. This brings a browser
with all previously defined fuses. Press the “new object” button, name the
new fuse type to something like “Dummy Type”.

• Select a new melt Curve: choose “Select project Type”. This brings a
browser with all previously defined met curves. Press the “new object”
button again, name the curve to something like “Dummy Curve”. Select
some dummy values: for instance Function=“IEC 255-3”, a1=1, a2=2,
a3=3. Press the ... button of the time dial, and press OK . Press OK
to accept the dummy curve.

• Press OK to select the dummy curve.

• Press OK to accept the dummy type.

• Press OK to select the dummy type.

• Press OK to accept the dummy fuse.

To copy a dummy curve to other cubicles:

• Open the Color Representation dialogue of the single line diagram (

button). Select “Relays and Restoration switches” to color the
corresponding switch symbols.

• Right-click a cubicle with a dummy curve. Select “Edit devices”. This shows
the contents of the cubicle. Copy the dummy fuse. Close the browser.

• Right-click another cubicle. Select “Edit devices”. Paste the dummy fuse.
Close the browser. Repeat this for all cubicles that should get the dummy
fuse.

In all cubicles in which protection equipment is installed, the minimum

requirement is the existence of a dummy fuse object. All equipment failures, as
defined by the failure models, must be cleared by a protection device. If such is
not the case, i.e. when a failure cannot be cleared during the reliability
assessment, then this will result in an error message and the calculation will be
interrupted.

Reliability Analysis 18-324

DIgSILENT PowerFactory Reliability Assessment Functions

Required Failure Models

For an accurate network reliability assessment, failure models should be
assigned to al least all relevant lines, cables and transformers. Additionally,
failure models may be assigned to busbars and synchronous generators.
Asynchronous generators are not considered relevant for the network reliability,
as they are not capable of running in island conditions. The possible reduction in
feeder loading due to local asynchronous generation is nevertheless captured in
the reliability assessment.

During a reliability assessment with a contingency level of 1, only one single

failure model will be allowed to become active at the same time. This means that
only single failures will be analyzed. There are two ways to extend the analysis
into considering overlapping outages:
• Performing reliability assessment for higher contingency levels

• Defining “Common-Mode” failure models

Higher contingency levels will cause the analysis of all relevant combinations of
1, 2, 3, etc. failures at the same time. This, however, may seriously slow down
the calculations, as is clear from the following example.

Suppose we have a distribution network with 50 possible faulting elements. For

a contingency level of 1, we thus have to analyze the results of 50 faults.
Suppose that takes an acceptable 3 seconds. For a contingency level of 2, we
would have to analyze the effects of 50*49/2=1225 faults and fault combinations.
That would take about 73 seconds. A contingency level of 2 asks for
50*49*48/6=19600 fault combinations, which would take about 20 minutes to
solve. For smaller networks, this may still be acceptable. For larger networks,
calculation times may run into hours or even days.

The analysis of higher contingency levels may be necessary in very robust

networks where loads can only suffer interruptions when two or more
independent faults have occurred. In most cases, either the loads will suffer
interruptions for single faults and/or for faults with a common cause, which are
called “dependent faults”. Examples of dependent faults are
• Lighting flash-over at a multi-circuit tower

• Pole and tower damage, for instance caused by car accidents.

• Multi-cable damage due to excavation works

The “Common Mode” approach does model for dependent faults like the ones in
these examples. The main difference between independent and dependent
faults is that the probability of occurrence of independent faults equals the
probability of the one fault times the probability of the other fault. The probability
of occurrence of a dependent fault is just the probability of the common mode
event to happen. In most cases, the probability of dependent faults are much

Reliability Analysis 18-325

DIgSILENT PowerFactory Reliability Assessment Functions

higher than the probability of independent faults. This is illustrated by the

following example.

Suppose we have a cable feeder with two parallel identical cables. The failure
model for each cable is:
• Failure frequency = 0.1 1/a

• Repair duration = 10 hours

• Unavailability = 10 hours * 0.1 1/a = 1 hour/a

An independent failure of both cables will occur when the one cable suffers a
short-circuit while the other is in repair. The fact that the short-circuit happens
during the repair is just “bad luck”. Using simple mathematics, we find for the
independent combination of failures:
• Frequency of occurrence = 1/43800 1/a

• Mean time to finish the repair on one of the two cables = 5 hours

• Unavailability of the feeder = 0.41 SECONDS/a

Suppose that we have a risk of damaging both cables during excavation works
(“common mode”) of once every 500 years, with an average repair time of 10
hours. That would result in an unavailability of 72 seconds per year, which is 175
times higher than the unavailability due to independent failures. From this, it is
clear that it is far more important to model for common mode failures as to model
for the independent overlapping failure.
It is also clear that is wrong to believe that the overlapping outage of both cables
is captured in an analysis with contingency level = 2. In such an analysis, the
effect of the overlapping outage will be analyzed, but the frequency and duration
will not reflect the frequency and duration of the common cause event, but of the
independent event.

Common cause failure models will be analyzed during an analysis with

contingency level = 1. A common cause may create faults in more than 2
elements at the same time, but will always remain a single event.

In most reliability studies, independent overlapping failure can be neglected

because they are far less frequent as single failures or common mode failures.
The large amount of required extra calculation time for independent failures will
often have only a negligible effect on the produced results.

Common mode failure models are created by pressing the “New Object” ( )
button in the database manager and selecting/entering the StoCommon class
name. Common mode failure models must reside in an active Grid folder in
order to become calculation relevant. Common mode models in a library folder,
for instance, will be ignored even when the objects which are affected are in an
active grid folder.

Reliability Analysis 18-326

DIgSILENT PowerFactory Reliability Assessment Functions

Specifying Fault Effect Analysis

The fault effect analysis will perform the following tasks:
• Fault clearance by protection

• Fault isolation by opening isolators

• Power restoration by closing normally open points

For these tasks, the following data must be entered:
• Basic protection equipment models must be created.

• Either all switches may be opened to isolate a fault, or all switches that may
be opened must be marked as “Use for fault separation”

• All normally open switches that may be closed for power restoration must
be marked as “Use for power restoration”
The reliability assessment command has an option on the “Advanced Options”
page to “Use power restoration switches”. If this option is disabled, then no fault
isolation or power restoration is performed. This means that all loads that are
interrupted by protection will remain interrupted during the repair of the faulted
component.
If the power restoration option is enabled, then either all switches can be used for
fault isolation, or only the ones that have been marked as “Use for fault isolation”.

The required time for power restoration to certain loads in case of a fault is
determined by the actuation times of the switches. This actuation time is not to
be interpreted as the time needed to operate a single switch, but as the average
time required until the operator can open/close this switch. This average time
includes required fault location, decision and traveling times. To determine the
actuation time for a certain switch, the following question must be answered:
“When this switch has to be opened/closed for the purpose of power restoration
following the occurrence of a fault, then how much time passes on average
between the occurrence of such faults and the actuation of this switch?”

18.6 Stochastic Reliability Assessment: Basic

Theory

The assessment of reliability indices, or “reliability analysis”, basically comprises

the following steps :
• Failure modeling
• Load modeling

Reliability Analysis 18-327

DIgSILENT PowerFactory Reliability Assessment Functions

• System state production

• Failure Effect Analysis (FEA)
• Statistical analysis
• Reporting

Figure 18.21: Basic flow diagram

The basic calculation flow diagram is depicted in Fig. 18.21. The failure models
describe the way in which the system components may fail, how often they will
fail and how long it takes to repair them. The load models may consists of only a
few possible load demands, or may be based on precise load forecast and
growth scenarios.

The combination of one or more simultaneous faults and a specific load

condition is called a ‘system state’. The system state production module will use
the failure and load models to build a list of relevant system states. Each of
these system states may have one or more faults. It is the task of the FEA
module to analyze the faulted system states by imitating the system reactions to
these faults, given the current load demands. The FEA will normally take the
power system through a number of operational states which may include

• Fault clearance by tripping protection breakers

• Fault separation by opening separating switches
• Power restoration by closing normally open switches
• Overload alleviation by load transfer and load shedding

The basic task of the FEA functions is to find out if the system faults will lead to
loads interruptions and when such is the case, which loads will be interrupted for
how long.

The results of the FEA are combined by the data that is provided by the system
state production module to update the statistics. The system state data

Reliability Analysis 18-328

DIgSILENT PowerFactory Reliability Assessment Functions

describes the expected frequency of occurrence of the system state and its
expected duration. The duration of these system state should not be mistaken
for the interruption duration. A system state with a single line on outage, due to a
short-circuit in that line for instance, will normally have a duration equal to the
time needed to repair that line. In case of a double feeder, however, no loads
may suffer an interruption at all. In the case that loads are interrupted by the
outage, the power may be restored by network reconfiguration (i.e by fault
separation and closing a back-stop switch). The interruption duration will then
equal the restoration time, and not the repair duration (=system state duration).

18.6.1 Stochastic Models

A stochastic model describes how and how often a certain object changes. A
line, for example, may suffer an outage due to a short-circuit. After such an
outage repair will be started and the line will be taken into service again after the
repair has been finished. If we define the two states for the line as “in service”
and “in repair”, a monitoring of the line could could result in a graph as depicted
in Fig. 18.22.

R1 R2 R3
in service
S1 S2 S3 S4
in repair time
T1 T2 T3 T4 T5 T6

Figure 18.22: Example of a monitored component state in time

The line in this example fails at time T1 after which it is repaired and put back into
service at T2 . It fails again at T3 , is repaired again, etc. The repair durations
R1 = T2 − T1 , R2 = T4 − T3 , etc. are exaggerated in this example.

The repair durations are also called the “Time To Repair” or “TTR”. The service
durations S1 = T1 , S2 = T3 − T2 , etc. are called the “life-time”, “Time To Failure”
or “TTF”.

Both the TTR and the TTF are stochastic quantities. By gathering failure data
about a large group of similar appliances in the power system, statistical
information about the TTR and TTF, such as the mean value and the standard
deviation, can be calculated. The statistical information is then used to define a
stochastic model.

There are many ways in which to define a stochastic model. The so-called
“homogenous Markov-model” is a highly simplified but generally used model. A
homogenous Markov model with two states is defined by

• A constant failure rate λ (‘lambda’)

• A constant repair rate µ (‘mu’)

Reliability Analysis 18-329

DIgSILENT PowerFactory Reliability Assessment Functions

these two parameters can be used to calculate the

• mean time to failure, TTF = 1/λ

• mean time to repair, TTR = 1/µ
• availability, P = TTF/(TTF+TTR)
• unavailability Q, = TTR/(TTF+TTR)

The availability gives the fraction of time during which the component is in
service, the unavailability the fraction of time during which it is in repair and P+Q
= 1.0.

For example, if 7500 monitored transformers where to show 140 failures in 10

years time during which a total of 7360 hours is spend repairing, then
140
λ = = 0.0019 [1/a]
10 · 7500
1
TTF = = 530 [a]
λ
7360
TTR = = 52.6 [h] = 0.006 [a]
140
1
µ = = 167 [1/a]
TTR
530
P = = 0.999989
530 + 0.006
0.006
Q = = 6 [min/a]
530 + 0.006
These equations also introduce some of the units used in the reliability
assessment:

• frequencies are normally expressed in [1/a] = “per annum” = per year

• lifetimes are normally expressed in [a] = “annum”
• repair times are normally expressed in [h] = “hours”
• probabilities or expectancies are expressed as a fraction or as time per
year ([h/a], [min/a]).

Of course, it is also possible to define a homogenous Markov model with more

than two states. Such may be needed to distinguish between faults that can be
repaired reasonably fast, and faults that will require more time. Two repair states
are then needed, each with a different mean repair time.

A peculiarity of the homogenous Markov model is that it is completely

memory-less. This means that, if we would perform preventive maintenance to
improve the reliability of a component, it does not make any change if the last
maintenance has been performed one week or 5 years ago, or even if
maintenance was performed at all. The probability for the component to fail in
the next period of time will be equal in all cases. Effects of changing preventive

Reliability Analysis 18-330

DIgSILENT PowerFactory Reliability Assessment Functions

maintenance can therefore not be calculated when using the homogenous

Markov model.

The same memory-less quality makes that all repairs will behave in the same
way, apart from their mean duration. And only mean durations can be
determined when using homogenous Markov models. Interruption costs,
however, may be dependent on the fraction of repairs that take longer then a
certain amount of time. A certain repair may take 2 hours on average, for
example, but when compensation has to be paid for interruptions longer than 3
hours, and when such long repairs occur in 20% of all cases, using the mean
duration alone will not produce correct results. A realistic assessment of
interruption costs is therefore not possible when using the homogenous Markov
model.

All reliability assessment functions in DIgSILENT PowerFactory are therefore

based on the “Weibull-Markov” model (WM-model). This more advanced
stochastic model has the following features.

• It uses Weibull distributions for all stochastic durations. This distribution

uses a shape factor and a characteristic time. By setting the shape
parameter “beta” to 1.0, a homogenous Markov model results.

• The Weibull-Markov model is therefore 100% backwards compatible with

the homogenous Markov model, and existing ‘homogenous Markov data’
may be used directly without a need for conversion.

• It allows for addressing the effects of maintenance and ageing of

equipment.

• It allows for a fast and correct calculation of interruption costs in all cases.

A Weibull-Markov model with three states is depicted in Fig. 18.23.

State 0 Pr10 State 1

λο, β 0 λ1, β 1
Pr 01
Pr 20
Pr12 Pr21
Pr02
State 2
λ 2, β 2

Figure 18.23: A Weibull-Markov model

This example shows all parameters needed for defining a Weibull-Markov model.
If the example model would describe the behaviour of a generator, then

• State 0 could describe the state with 100% capacity

• State 1 could describe a derated state with limited capacity

Reliability Analysis 18-331

DIgSILENT PowerFactory Reliability Assessment Functions

• State 2 could describe the repair state

The parameters β (‘beta’) and η (‘eta’) are used to define the stochastic duration
of each state, i.e. the stochastic TTF (State 0) or TTR (State 2). The “Transition
Probabilities” Prij define the probability of the generator to change to another
state. The probability Pr01 , for example, equals the fraction of failures where the
generator is not tripped but kept on line with derated capacity. The probability
Pr02 equals the fraction of failures that cause the generator to trip, and
Pr01 + Pr02 = 1.0 in this example.

In the example of the 7500 monitored transformers, a Weibull-Markov model

would result in
10 · 7500
η0 = = 530 [a]
140
TTF = η0 = 530 [a]
7360
η1 = = 0.006 [a]
140
TTR = η1 = 52.6 [h]
β0 = 1.0
β1 = 1.0

The form factors β0 and β1 where left at their default values as no data is
available for calculating them. The raw data, however, could be analyzed to get
more realistic values.

18.7 Failure Models

Failure models are available for the following objects:

• Busbars and terminals

• Lines and cables, routes and sections
• Transformers
• Synchronous generators

In addition to the line or cable failure model, a common mode failure model is
available too.

All failure models define how often a component will suffer an active failure. All
active failures have to be cleared by protection. When a failure cannot be
separated from all generators or external networks by protection, it will cause the
reliability assessment to stop with an error message. Repair of the faulted
component is assumed to start directly after the fault has been cleared. The
repair duration which is also defined in the failure models equals the time

Reliability Analysis 18-332

DIgSILENT PowerFactory Reliability Assessment Functions

needed to restore the functionality of the component. The time needed to start
the repair (for instance because spare parts have to be ordered first) and all
other delays are thus to be included in the total repair time.

18.7.1 Busbar and Terminal Failures

The failure model for busbars and terminals is normally selected at the bar type
model. The bar type model (TypBar) has a reference to a failure model of which
an example is depicted in Fig. 18.24.

Figure 18.24: Bar type failures

The bar failure model defines a failure frequency for the busbar itself and an
additional failure frequency for each connection to the busbar. The repair
duration is independent of the number of connections. The total failure
frequency for a triple busbar system with six feeders is for instance calculated as
Ftot = 3 ∗ Fbar + 6 ∗ Fconnection [1/a]
which would add up to 0.24 per year for the shown failure model.

The bar or terminal elements will show the total failure frequency, outage
expectancy and mean outage duration at the reliability page. See Fig. 18.25 for
an example.
The bar or terminal element may overrule the failure model that it receives
through the bar type by selecting an element model.

Reliability Analysis 18-333

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.25: Reliability data for the busbar/terminal

18.7.2 Line Failures

The line and cable failure model is normally selected at the line type. The line
type model (TypLne) has a reference to a line failure model of which an example
is depicted in Fig. 18.26.

Figure 18.26: The line type failure model

The line failure model uses a failure frequency or expectancy per unit length.
The repair duration is independent of the length. Both the time to failure and the
repair duration have a shape factor Beta. The outage expectancy equals the
mean repair duration times the failure frequency and is thus also defined as per
100 km length.

The actual failure frequency for a particular line or cable is calculated by using
the length of the line/cable. The used failure frequency, outage expectancy and
mean outage duration are shown in the reliability page of the line/cable element,
as depicted in Fig. 18.27. The line or cable element may overrule the failure

Reliability Analysis 18-334

DIgSILENT PowerFactory Reliability Assessment Functions

model that it receives through the line/cable type by selecting an element model.
All line and cable failures are assumed to occur equally often for each position
along the length of the line/cable.

Figure 18.27: Reliability data for the line/cable

18.7.3 Transformer Failures

A single transformer failure model is available for both the two- and the
three-winding transformers. The transformer failure model is normally defined at
the transformer type. The transformer type (TypTr2 or TypTr3) has a reference
to a failure model of which an example is depicted in Fig. 18.28.

Figure 18.28: The transformer failure model

The transformer failure model has a failure frequency or expectancy and a repair
duration distribution. Both the time to failure and the repair duration have a
shape factor Beta. The outage expectancy equals the mean repair duration
times the failure frequency.

Reliability Analysis 18-335

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.29: Reliability data for a transformer

The used frequency, outage expectancy and mean outage duration are shown in
the reliability page of the transformer element, as depicted in Fig. 18.29. The
transformer element may overrule the failure model that it receives through the
transformer type.

All transformer failures are assumed to be active Failure.

18.7.4 Synchronous Machines Failures

The failure models for busbars, lines or transformers have a fixed amount of
possible states. Basically, these elements can only be available or not. The
failure models for the synchronous generator, however, allows for any number of
states. So-called ‘derated’ states, in which the generator is still available but with
reduced capacity, can thus easily be modeled.

This makes the failure model, however, somewhat more difficult to define. The
first step is to append one or more states to the model, as the default model only
has one state. This is done by right clicking the number of an existing state in the
state duration matrix and selecting Append Cells, as depicted in Fig. 18.30.

Figure 18.30: Appending a state

The second step is to name the created states and to enter the capacity in each

Reliability Analysis 18-336

DIgSILENT PowerFactory Reliability Assessment Functions

state. The stochastic synchronous machine has the following state attributes:

• Relative Nominal Apparent Power percentage

• Machines On Outage

A fully available machine has

• Nominal Power = 100%

• Machines On Outage = 0

A fully unavailable machine has

• Nominal Power = 0%

A derated state can be defined by defining a nominal power less than 100%, or
by setting ‘Machines On outage’ > 0. A nominal power or 50%, for example, will
half the capacity of all parallel machines, but all machines will remain running. A
number of machines on outage larger than zero will also reduce the total
capacity, but will also change the electric properties because of less remaining
machines running.

The definition of the Weibull-Markov model for the synchronous machine, i.e. the
definition of the state duration matrix, transition probability matrix, or the
transition rate matrix, is described in section 18.7.6, page 18-346.

A failure model is selected for a synchronous machine by setting the “stochastic

model” reference on the reliability page of the synchronous machine, as
depicted in Fig. 18.31.

Figure 18.31: Assigning a stochastic model to a machine

Each failure model may be used by more than one synchronous machine at the
same time. The synchronous machines that use the same failure model will
nevertheless behave stochastically independent of each other.

18.7.5 Load Modeling for Reliability Assessment

Two types of load models may be used:

Reliability Analysis 18-337

DIgSILENT PowerFactory Reliability Assessment Functions

• Local load models

• Area load models

The local load model is defined by creating a stochastic Weibull-Markov model.

This stochastic model will have two or more load levels with frequencies and
probabilities of occurrence and transition probabilities.

The area model may be defined by a peak load curve, a load duration curve or a
stochastic Weibull-Markov model. The peak load or load duration curves may be
defined by an one-dimensional vector characteristic (ChaVec), or by an external
data file object (ElmFile).

The main difference between a local load model and an area load model is that
a local load will behave independent of all other loads, even when loads share
the same local load model. Loads which share the same area load model,
however, will all change their demand in the same way at the same moment in
time. The area load model defines all load changes as percentage change. A
load of 100MW and one of 5MW which both use the same area model will both
change to 80% when the area model changes to 80%. The 100MW load will
then change to 80MW and the 5MW load to 4MW at the same moment in time.

The various ways in which to model a load for reliability assessment are depicted
in Fig. 18.32.

Figure 18.32: Load Models

Stochastic Load Models

The stochastic load model is meant mainly for defining local load models. Local
load models are suited for modeling single large (industrial) loads in the system
for which a load forecast is hard to make. Examples of such loads are larger
industries which are modeled as a single load, large pumping stations, etc.

The local load model uses the Weibull-Markov stochastic model. The definition
of the Weibull-Markov model, i.e. the definition of the state duration matrix, the
transition probability or transition rate matrix, etc., is described in section 18.7.6,
page 18-346.

Reliability Analysis 18-338

DIgSILENT PowerFactory Reliability Assessment Functions

In addition to the Weibull-Markov model, the stochastic local load has the
following state attributes:

• Relative Active Power demand percentage

• Relative Reactive Power demand percentage

In stead of defining the Weibull-Markov model by hand, it may be created

automatically from a peak load curve. The “Extra” page on the stochastic load
model provides a button C REATE M ODEL for this. The Weibull-Markov model
may be created from a load curve or from a measurement file.

An example of a load curve is the load duration curve of the IEEE test system,
which is depicted in Fig. 18.33.

Figure 18.33: IEEE daily peak load curve

A load curve is defined as a parameter characteristic (ChaVec), with a time

scale (TriTime). The example curve uses a time scale which has the 365 days in
the year, but time scales with 52 weeks or 12 months, or any other unit of time,
are also possible. See “Creating an one-dimensional vector characteristic” and
“Creating a Time Scale” in the basic user’s manual for more information. The
parameter characteristic is not suited for holding larger load curves, i.e. hourly
peak curves which would have 8760 points or more. Such curves can be used
by using an external data file.

The peak load curve which is used for creating a stochastic load model will be
converted to percent changes, relative to the highest value. The relative value is
used for both active and reactive power. This means that it does not make a
difference if either current measurements are used, active power, or apparent
power. All load points will be converted to the percent values, relative to the
highest value. Converting, for instance, current measurements to power values
by use of a nominal voltage and a presumed power factor is therefore not
required. Only the form of the load curve is used.

Reliability Analysis 18-339

DIgSILENT PowerFactory Reliability Assessment Functions

After the load curve has been defined and selected, the number of states for the
Weibull-Markov must be set. In the example of the IEEE load curve a number of
5 states was taken. After pressing the C REATE M ODEL button, the
Weibull-Markov model is calculated from the load data. The model for the
example IEEE curve is depicted in Fig. 18.34.

Figure 18.34: A calculated 5-state WM model

The load states are chosen in such a way as to bring the Weibull-Markov model
as close to the original load curve as possible. Fig. 18.35 shows the IEEE load
duration curve and the calculated 5 states of the Weibull-Markov model.

Area Load Models

A power system may include independent stochastic loads, such as large
industrial loads, pumping stations, etc. In most applications, however, the
behaviour of the loads is modeled by defining area load models.

An area load model can be used to define an annual area load forecast, an area
load growth scenario for a range or years, or both. The “characteristic” option in
the load edit dialogue has to be set to Area Model first, after which the area

Reliability Analysis 18-340

DIgSILENT PowerFactory Reliability Assessment Functions

100

90

80

70
Load Duration Curve

60

50

40

30

20

10

0
0 730 1460 2190 2920 3650 4380 5110 5840 6570 7300 8030 8760
Hour in Year

Figure 18.35: The IEEE load duration curve with N=5 step curve

model can be selected. A new area model is created by pressing the button
in the object browser that appears when an area model is to be selected. An
example of an area model is depicted in Fig. 18.36, which defines both a load
curve and a load growth curve.

Figure 18.36: Example of an area load definition

The annual load forecast can be defined by a chronological peak load curve, a
load duration curve, or a stochastic load model. As depicted in Fig. 18.32, the
peak load curve and the load duration curve may be defined by an
one-dimensional vector characteristic or by an external measurement file. The
load growth scenario is defined by an one-dimensional vector characteristic.

Reliability Analysis 18-341

DIgSILENT PowerFactory Reliability Assessment Functions

The load forecast curve which is used will be converted to percent changes,
relative to the highest forecast value. These relative changes are used for both
active and reactive power. This means that is does not make a difference if
either current measurements are used, active power, or apparent power.
Converting, for instance, current measurements to power values by use of a
nominal voltage and a presumed power factor is therefore not required. Only the
form of the load curve is used.

The selected load curve in Fig. 18.36 uses a time scale which has the 365 days
in the year, but time scales with 52 weeks or 12 months, or any other unit of
time, are also possible. See “Creating a one-dimensional vector characteristic”
and “Creating a Time Scale” in the basic user’s manual for more information.
The one-dimensional vector characteristic is not suited for holding larger load
curves, i.e. hourly peak curves which would have 8760 points per year. Such
curves can be used by using an external data file.

External data files can be used by creating an “External File” object (ElmFile).
This is done by first selecting the measurement file characteristic in the area
load model. Selecting the measurement file will now open a database browser.
A new file object is created by pressing the button. The measurement file
object (ElmFile) has a “FileName” field which is used to select the data file on
disk. The data file may contain up to 24 independent load curves. The
conversion factors ‘a’ and ‘b’ are normally not changed for reliability purposes.
See “The Measurement File” in the basic user’s manual for more information
about the measurement file object.

Because the external file may contain up to 24 columns with 24 different load
curves, the area model must specify a column number. If less than 24 different
area models are to be created for the reliability assessment, it is recommended
to create one single external data file which contains all area load curves. Only
one single measurement file object (ElmFile) is then required. Each area model
will then use this single file object. This makes it very easy to change the load
forecast for all areas by just changing the filename in the one measurement file
object.

An example of a load growth scenario is shown in Fig. 18.37. Area growth

scenarios must be defined as an one-dimensional vector characteristic
(ChaVec). The growth values are to be entered as percentage values for each
year, and not as percentage growth from year to year. The example in Fig. 18.37
shows a scenario which has 3% growth each year.
During the reliability assessment, the loads which use the area model are
changed by multiplying the load forecast and load growth values. For an hourly
load curve p(h) and a growth curve r(y), the resulting relative load value for hour
h in year y equals p(h) ∗ r(y).

Each area load model is normally used by more than one load. All loads that use
the area load model will have their active and reactive power multiplied by

Reliability Analysis 18-342

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.37: Area growth scenario

p(h) ∗ r(y) at the same time. They will all behave simultaneously, i.e. they are
100% statistically dependent.

Interruption Cost Functions

Interruption cost functions are defined as one-dimensional vector characteristics
(ElmVec) with time scales (TriTime). An example is shown in Fig. 18.38. The
time scale is free to choose, but must be monotonous rising. More than one
interruption cost function may be used at the same time for different loads, and
each function may use a different time scale.
Interruption costs functions are not interpolated in any way. The used
interruption costs for a certain interruption duration will remain constant in
between durations. This means that an interruption functions like

30min. − 7.5 $
60min. − 20.0 $
180min. − 80.5 $
(18.2)

means

Reliability Analysis 18-343

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.38: Customer damage function

0min. ≤ t < 30min. − 0.0 $

30min. ≤ t < 60min. − 7.5 $
60min. ≤ t < 180min. − 20.0 $
180min. ≤ t − 80.5 $
(18.3)

Selecting an interruption cost function for a particular load is done by setting the
interruption costs reference on the reliability page of the load dialogue, as
depicted in Fig. 18.39. The type of interruption costs function must be set at the
load element. Three types of interruption cost functions can be used:

$/kW : cost per interrupted power (kW), versus the interruption duration.

$/customer : cost per interrupted customer, versus the interruption duration.

$ : cost versus the interruption duration.

Reliability Analysis 18-344

DIgSILENT PowerFactory Reliability Assessment Functions

The selected interruption cost function will be interpreted according to the

selected type.

Figure 18.39: Load with interruption cost

Load Shedding and Transfer

Load transfer and load shedding is performed for overload alleviation. If
overloads are detected in the post-fault system condition, a search is started for
those loads that contribute to these overloads. The overloads are then alleviated
by either

• Transferring some of these loads, if possible

• Shedding some of these loads, starting with the lowest priority loads, when
needed

Each load model uses three values to describe the load transfer and load
shedding possibilities:

• The number of load shedding steps define the minimum amount of load
that can be shed. Four shedding steps means that the load can only be
shed to 25%, 50%, 75% or 100%. Zero shedding steps means that the
load can be shed up to any amount.

• The load priority is used to determine which loads to shed. Only the loads
with the lowest priority will be shed.

• The load transfer percentage defines the amount of load that can be
transferred away from the current network. The network that picks up the
transferred load is not considered. A transfer percentage of 30% would
mean that the load can be transferred away up to 30%. A percentage of
zero means no transfer.

The load transfer for overload alleviation must be distinguished from the load
transfer for power restoration. Load transfer by isolating a fault and closing a
back-stop switch is already considered during the fault separation and power
restoration phase of the failure effect analysis.

Reliability Analysis 18-345

DIgSILENT PowerFactory Reliability Assessment Functions

18.7.6 Defining a Weibull-Markov Model

All failure and load models needed for the reliability assessment calculations are
based on the advanced Weibull-Markov model. For most failure models,
however, a simple interface is offered for entering the failure data. For a
transformer, for instance, it is sufficient to enter a failure frequency and a mean
repair duration.

For some cases, the Weibull-Markov model can be defined freely. Examples are
the failure model for the synchronous generator and the stochastic load model.
The advantage of a free definition of the failure or load model is that it allows for
any number of states. A failure model for a synchronous generator may thus
also contain so-called derated states, in addition to the “in-service” and the
“out-or-service” state. The possibility to define any amount of states is even
more important for creating realistic load models. The available interface for
creating a Weibull-Markov model is treated in this section.

The Weibull-Markov model allows for entering the stochastic data in various
ways. The following parameters may be used.
Mean : the mean state duration
Variance : the variance of the state duration
Beta : the form factor of the Weibull probability distribution
Lambda : the characteristic time of the Weibull probability distribution
Transition Rates : the rates at which the element changes to the other states.
Transition Probabilities : the probabilities for going to the other states.
Because these parameters are redundant – we can calculated each of them
from the others – there is more than one way to define a WM-model. Two basic
methods may be used:
• Specifying transition rates
• Specifying state duration parameters and transition probabilities
The choice of what to enter is made by pressing the O PTIONS button. The
state duration parameters Mean, Variance, Beta and Lambda are 2-out-4
redundant. Two of them will determine the other two.

The combination of mean state durations and transition probabilities will

determine the transition rate matrix. The transition rate matrix alone determines
both mean state durations and transition probabilities. The Variance or Beta
must be specified additionally when the transition rate matrix is used. The Beta
parameter defaults to 1, which gives a standard homogenous Markov model.

In Fig. 18.40, an example is shown for a model which was defined by entering
state duration parameters (Mean duration and Beta), and transition probabilities.

Reliability Analysis 18-346

DIgSILENT PowerFactory Reliability Assessment Functions

The example shows a generator model with a derated state. The first state (“in
service”) has a mean duration of 2850 hours. There is a 65% probability that,
when a failure occurs, the generator will go to state 2 (“single burner”) and a
35% that it will go to state 3.

Figure 18.40: Example of a Weibull-Markov Model

The Weibull-Markov model is determined completely by the state duration

parameters and the transition probabilities. The use of form-factors (Beta)
different from 1.0 is optional.

The button O PTIONS may be used to switch to the transition rate matrix at any
time. The transition rate matrix is calculated from the state durations and
transition probabilities. Fig. 18.41 shows the transition rate matrix for the model
depicted in Fig. 18.40.

Figure 18.41: The calculated transition rate matrix

When the transition rate matrix is changed, then the state duration matrix and
the transition probability matrix are changed in turn. Fig. 18.42 shows the failure
model after the transition rates have been rounded.
A Weibull-Markov model may thus be defined as

Reliability Analysis 18-347

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.42: The Weibull-Markov model by transition rates

• a Weibull-Markov model, by state durations and transition probabilities

• a homogenous Markov model, by transition rates only.

In addition to the transition rates, the Beta’s of the state durations may be
changed to other than 1.0, thus creating a Weibull-Markov model from
‘homogenous data’.
A Weibull-Markov model with all Beta’s set to 1.0 will equal a standard
homogenous Markov model, which is fully determined by its transition rates.

As soon as a Weibull-Markov model has been defined, all statistic parameters

for each state are calculated automatically:

• The state Probability, which is the long-term probability to find the element
in the state

• The state Frequency, which is the mean number of times per year the
element enters or leaves the state

• The state Expectancy, which is overall mean number of hours per year the
element spends in the state

• The Mean Time Between, which is the mean time between entering the
state

These state statistics are shown, together with the duration distribution, on the
“Graph” page as depicted in Fig. 18.43.

Reliability Analysis 18-348

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.43: Example state statistics

18.7.7 Maintenance
Maintenance is included in the reliability analysis by defining one or more
maintenance blocks. A maintenance block consists of

• A list of objects to maintain

• A maintenance schedule

Al objects in the list of objects will be taken out of service for maintenance by this
maintenance block together. See Fig. 18.44 for an example.
The maintenance schedule is a list of deterministic moments in time for which
the maintenance will start. For each planned maintenance, the duration must be
given. See Fig. 18.45 for an example.

18.7.8 Common Mode Failures

All component failure models are independent models. Two or more objects may
share the same failure model, but their failure behaviour will be independent.
From the failure models, the outage expectancy can be calculated as the
average fraction of time, or the average time per year, during which the
component is not available.

Two parallel lines on the same tower or in the same trench will normally share
the same failure data. The probability of both lines on outage at the same time

Reliability Analysis 18-349

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.44: Defining a maintenance block

Figure 18.45: Defining a maintenance schedule

will be the product of the individual outage probabilities, because the failures that
lead to the outages are independent. The following example illustrates this.

• suppose each line suffers an outage ones every 5 years, for 10 hours.
Their outage expectancy is therefore 2 h/y, their individual outage
probability is 2.3 · 10−4 .

• the probability of the overlapping events which result in both lines on

outage is 5.2 · 10−8 , and the outage expectancy is thus a mere 1.6
SECONDS per year. The overlapping outage occurs on average once
every 21900 years

The double outage, however, may be much more frequent due to causes that
effect both lines. Examples of such causes are dredging, lightning, storms, cars

Reliability Analysis 18-350

DIgSILENT PowerFactory Reliability Assessment Functions

Figure 18.46: The Common Mode basic data

Figure 18.47: The Common Mode failure data

hitting poles, etc. The common mode object which is used to model such
common mode causes is depicted in Fig. 18.46 and Fig. 18.47.
The basic page of the common mode model shows a list where all objects that
are outaged by the common cause can be entered. The failure data is entered in
the failure data page. The example shows a common cause which outages two
lines once every 5 years on average, for an average of 52 hours. Common mode
failure models can be defined for lines or cables and for line or cable routes.

The common mode failures will not cancel the individual failure models, but will
cause addition outages of all listed components at the same time.

Common mode failure models are created in the following way:

• In the database manager, open the grid folder in which the elements for

Reliability Analysis 18-351

DIgSILENT PowerFactory Reliability Assessment Functions

wich a common mode failure is to be defined are located.

• Create a new StoCommon object in this grid folder (press button)

• Add two or more lines in the model and select the elements that will fail.

• Enter the failure frequency etc., as described above.

Reliability Analysis 18-352

Stability Analysis and Simulation of
Transients
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory Time-Domain Simulations

Chapter 19

Time-Domain Simulations

With the transient simulation functions of DIgSILENT PowerFactory the

dynamic behaviour of small systems up to large power systems can be analysed
in time domain. So it is possible to model complex systems from industrial
networks up to large transmission grids in detail taking into account electrical as
well as mechanical parameters.

Transients as well as stability and control problems in modern power systems

constitute important considerations during the planning, design and operation of
these complex systems. The effects which are to be examined are for example
electro-magnetic transients and different aspects of stability in power systems.
These can be analysed with PowerFactory using different methods like various
functions of time-domain simulations for varying time periods as well as dynamic
or small-signal stability analysis tools using e.g. the powerful eigenvalue
analysis.

There is a very large range of systems which can be analysed. For example it is
easily possible to analyse AC or DC systems (e.g. motor start-up, transmission
systems with detailed models of the power plants, complex HVDC systems) as
well as a combination of both. Also new study fields like wind-power or power
electronics applications constitute new challenges in the analysis of power
systems and new models and techniques are provided to meet these
requirements.

For modelling different machines and various controller units as well as the
electrical and mechanical parts of power plants, etc., there is the possibility of
using a variety of predefined models in the global library of PowerFactory. This
model library includes various models of generators, motors, controllers, motor
driven machines, dynamic loads and passive network elements. For example
you will find here the IEEE standard models of controllers of power plants.
Furthermore specific models of controllers and block diagrams of power plants
can be modelled with a high degree of freedom.

Stability Analysis and Simulation of Transients 19-354

DIgSILENT PowerFactory Time-Domain Simulations

19.1 Introduction

To study and analyse power system stability the behaviour of power systems
under conditions before and after sudden changes in load or generation or
during faults or outages of elements have to be examined. The robustness of a
system is defined by the ability of the system to maintain stable operation under
normal and perturbed conditions. Therefore it is necessary to design and
operate a power system so that transient events, e.g. probable contingencies in
the system, can be sustained without the loss of load or loss of synchronism in
the power system. Transients in electrical power systems can mainly be divided
into three time domains:

• short-term, or electromagnetical transients.

• mid-term, or electromechanical transients.

• long-term transients

Because of the sophisticated multilevel modelling of power-system elements and

the use of advanced algorithms, PowerFactory covers the whole range of
transient phenomena in electrical power systems. Consequently, there are three
different simulation functions available:

1. a basic function which uses a symmetrical steady-state (RMS) network

model for mid-term and long-term transients under balanced network
conditions.

2. a three-phase function which uses a steady-state (RMS) network model for

mid-term and long-term transients under balanced and unbalanced
network conditions e.g. for analysing the dynamic behaviour after
unsymmetrical faults.

3. an electromagnetic transient (EMT) simulation function using a dynamic

network model for electromagnetical and electromechanical transients
under balanced and unbalanced network conditions especially suited for
analysing short-term transients.

In addition to the time-domain calculations, two additional and more specific

analysis functions can be performed:

• Parameter Identification

• Modal Analysis or Eigenvalue Analysis

Based on the results of a valid load-flow calculation of the studied system, the
PowerFactory time-domain simulation functions determine the initial conditions

Stability Analysis and Simulation of Transients 19-355

DIgSILENT PowerFactory Time-Domain Simulations

of all power system elements including all controller units and the mechanical
parts of the system as well. These initial conditions represent the equilibrium
operation point at the beginning of the simulation, fulfilling the requirements that
the derivative of all state variables of loads, machines, controllers, etc. are zero.

Before the start of the simulation process, it is also determined what type of
network representation must be used for further analysis, what step sizes to use,
which events to handle and where to store the results.

The simulation uses an iterative procedure to solve AC and DC network

load-flow and dynamic model state variable integrations simultaneously.
Non-linear and highly accurate system models result in exact solutions also
during high-amplitude transients. Various numerical integration routines with
different integration step sizes for the electromechanical systems (including
voltage regulators and power system stabilisers) and the hydro-mechanical or
thermo-mechanical models produce best results within a justifiable period of
time.

The whole process of performing an transient simulation typically takes the

following steps:

1. Calculation of Initial Values, which includes a load-flow calculation.

2. Defining result variables and/or simulation events.

3. Optionally defining result graphs and/or other virtual instruments.

4. Run Simulation

5. Creating additional result graphs / virtual instruments or editing existing

ones.

6. Changing settings, repeating calculations.

7. Printing results

19.2 Calculation Methods

The time-domain simulations can be divided into three different time periods to
be analysed, so there are three different simulation functions available:

• the symmetrical steady-state (RMS) network model for mid-term and

long-term transients under balanced network conditions.

• the three-phase steady-state (RMS) network model for mid-term and

long-term transients under balanced and unbalanced network conditions.

Stability Analysis and Simulation of Transients 19-356

DIgSILENT PowerFactory Time-Domain Simulations

• the electromagnetic transient (EMT) simulation function using a dynamic

network model for electromagnetical and electromechanical transients
under balanced and unbalanced network conditions.

in the following sections these three analysis functions in the time domain are
described and the usage is explained in detail.

19.2.1 Balanced RMS Simulation

The balanced RMS simulation function considers dynamics in
electromechanical, control and thermal devices. It uses a symmetrical,
steady-state representation of the passive electrical network. Using this
representation, only the fundamental components of voltages and currents are
taken into account.

Depending on the used models of generators, motors, controllers, power plants

and motor driven machines, the following studies may be carried out:
• transient stability (e.g. determination of critical fault clearing times)
• mid-term stability (e.g. optimisation of spinning reserve and load shedding)
• oscillatory stability (e.g. optimisation of control device to improve system
damping)
• motor start-up (e.g. determination of start-up times and voltage drops)

Various events can be introduced. As an example the following event types are
listed:
• start-up and/or loss of generators or motors
• stepwise variation of loads
• load shedding
• line and transformer switching/tripping
• symmetrical short-circuit events
• insertion of network elements
• power plant shut down
• variations of controller setpoint
• change of any system parameter

Because of the symmetrical network representation, the basic simulation

function allows only the insertion of symmetrical faults.

Stability Analysis and Simulation of Transients 19-357

DIgSILENT PowerFactory Time-Domain Simulations

19.2.2 Three-Phase RMS Simulation

If asymmetrical faults or unbalanced networks have to be analysed, the three
phase RMS simulation function must be used. This simulation function uses a
steady-state, three-phase representation of the passive electrical network and
can therefore deal with unbalanced network conditions, either due to unbalanced
network elements or due to asymmetrical faults. Dynamics in electromechanical,
control and thermal devices are represented in the same way as in the basic
RMS simulation function.

Asymmetrical electromechanical devices can be modelled as well as single

phase and two-phase networks can also be analysed using this analysis
function.

In addition to the balanced RMS simulation events, unbalanced fault events can
be simulated, such as:

• single phase and two phase (to ground) short-circuits

• phase to phase short-circuits

• intercircuit faults between different lines

• single and double phase line interruptions

All of these events can occur simultaneously or in cascades so that any

combination of symmetrical and asymmetrical faults can be calculated.

19.2.3 Three-Phase EMT Simulation

Voltages and currents are represented in the EMT simulation by their
instantaneous values, so that dynamic behaviour of passive network elements is
also taken into account. This ability is necessary for carrying out the following
applications:

• DC and harmonic components of currents and voltages.

• Exact behaviour of inverter driven machines.

• Exact behaviour of HVDC transmission systems.

• Nonlinear behaviour of passive network elements such as transformer

saturation.

• Overvoltage phenomena in switching devices.

• Lightning strikes and travelling waves.

• Analysis of the exact behaviour of protection devices during faults.

Stability Analysis and Simulation of Transients 19-358

DIgSILENT PowerFactory Time-Domain Simulations

Due to the electrical network being represented in detail including all phases, all
described events, symmetrical and asymmetrical, can be simulated. The EMT
function can also be used for the simulation of longer-term transients, but due to
the passive network elements being represented dynamically, the integration
step size has to be much smaller than in case of a steady-state representation
and therefore, calculation time increases.

19.3 Setting up a Simulation

Based on the results of a load-flow calculation of the network, all internal

variables and the internal operation status of connected machines, controllers
and other transient models have to be determined. As a result of this calculation,
the synchronous generator excitation voltages and load angles as well as all
state variables of controllers and power plant models, or any other device, which
is active and will affect the time-domain simulation are calculated.

The calculation of initial conditions is started by

• either pressing the on the main toolbar

• or selecting the Calculation →Stability →Initial Conditions... option from

the main menu.

In the upcoming dialogue of the initial conditions command dialogue all

simulation settings are defined. Here the type of simulation (RMS or EMT,
balanced or unbalanced) can be chosen and different setting like the time steps
are specified, which are important for executing the simulation.

These settings include

Basic Options the simulation type is selected here (RMS vs. EMT, balanced vs.
unbalanced), and the load-flow command, the result object and the event
list are defined.

Step Sizes maximum and minimum step size or different step sizes for various
classes of models are specified for the available step size algorithms.

Step Size Adaption can be defined when using automatic step size adaption.

Advanced Options including various error margins, iteration limits, damping

factors, etc.

Noise Generation defines the generator for random numbers.

Stability Analysis and Simulation of Transients 19-359

DIgSILENT PowerFactory Time-Domain Simulations

Figure 19.1: The Initial Conditions Dialogue

19.3.1 Basic Options

The basic options are used to select the type of simulation and the network
representation.

References to the result object, the event list and the load-flow command are
available for inspecting or editing these objects.

Verify Initial Conditions

If the required operation status allows to fulfill the initial conditions, the power
system will be in steady-state conditions. When the Verify Initial Conditions is
enabled, then the condition dx/dt = 0 is checked for all state variables. If one or
more of the state variable derivatives does not equal zero, the power system

Stability Analysis and Simulation of Transients 19-360

DIgSILENT PowerFactory Time-Domain Simulations

may start to ’moving’ from the very beginning, even without the application of an
external event. In this case the user should analyse the relevant controller or
model and its defined initial conditions carefully.

All warnings or error messages should be checked carefully. Typical problems

are devices which are overloaded or operate above or below signal limitation
from the beginning of the simulation.

The error message displayed in the output window might look as follows:

DIgSI/err - Some models could not be initialised.

Please check the following models:
DIgSI/err - ’Simple Grid\AVR Common Model.ElmDsl’:
DIgSI/err - Initial conditions not valid !

Long-Term Stability
The term ”long-term stability” is slightly misleading. It describes a special
numerical integration algorithm, with which it is possible to use large integration
step sizes compared to the characteristic time constants (eigenvalues) of a
system (A-stable integration algorithm).

When using a conventional, explicit numerical integration algorithm, such as

Runge-Kutta, the integration step size must be adjusted to the eigenvalues of a
system and the numerical solution becomes unstable if too large step sizes are
used, even if fast modes have fully decayed and are not apparent in the system.
In the PowerFactory ’long-term algorithm’, the step size can be adjusted to the
actual course of all state variables without considering numerical stability. When
fast transients have decayed, the step size can be adjusted to the speed of
slower transients etc.

If some very fast modes are not of interest, a large step size can be selected
from the beginning and the algorithm is automatically smoothing fast variations.
The term ”long-term” comes from the classical application of this type of
algorithm, the simulation of long-term phenomena, where it is necessary to
increase the simulation step size to the range of minutes, even if fast modes are
present in the system.

However, if power electronics are involved, characteristic time constants can be

extremely short (e.g. 1ms), even if a stability model with steady-state equations
for the electrical network is used. Hence, using a classical integration algorithm
would require to use step sizes much below the smallest time constant of the
system, otherwise it would be numerically instable.

With the long-term algorithm, these systems can be analysed with reasonable
step sizes.

Stability Analysis and Simulation of Transients 19-361

DIgSILENT PowerFactory Time-Domain Simulations

Hence, the long-term algorithm can not described as using simplified models but
as different type of numerical integration algorithm.

19.3.2 Fixed Step Size

When using a fixed step size for the simulation (deactivate ”Automatic Step Size
Adaption” on the basis options page), the integration step size for
electromagnetic transients (EMT) respectively for electromechanical transients
(RMS) has to be set.

It is often not necessary and resulting in reduced simulation time not to plot
every single calculated time step. So additionally the step size for the output
graphs can be set, so not every point of simulation time will be drawn on the
virtual instruments plot. By selecting a higher output step size, the simulation
process will speed up without influencing the calculation process. Nevertheless
faster changes may be lost in the reported results.

Also the start time of the simulation can be set. This point of time is typically
negative, so the first event to be analysed can take place at t = 0s.

Furthermore two different algorithms can be used with the fixed step size:

Single Rate all model variables will be calculated at the same points in time

Multi Rate to speed up simulation you can set different fixed time steps for
different types of models. These are:

• electromagnetic transients
• electromechanical transients and controllers with small time constants
• controllers and machines with relatively large time constants (pco,
pmu)

Hence the parameters which are available for the step size are:

dtemt Electromagnetic Transients (typical 0.0001 sec)

dtgrd Electromechanical Transients (sym, asm, vco, pss) (typical 0.01 sec)

dtpmu Medium-Term Transients (pco, pmu, mdm) (typical 0.1 sec)

dtout Output (typical equal to dtemt for EMT respectively dtgrd for RMS
simulation)

Stability Analysis and Simulation of Transients 19-362

DIgSILENT PowerFactory Time-Domain Simulations

N OTE : When setting up time-domain simulations, it is very important to use

the correct time steps for the simulations in order to observe the right
phenomena in the results.
For the RMS simulation the minimum time step should always be
smaller then the time constants in the system. In controllers you have
to consider not only the open-loop up also the closed-loop time con-
stants.
For electromagnetic transients e.g. when analysing travelling waves,
the smallest travelling time would set the upper limit for the minimum
time step.

In addition to the Newton-Raphson based algorithm for the solution of weak

nonlinearities as for example saturation effects in synchronous and
asynchronous machines, the EMT simulation function allows interrupts for the
simulation of strong nonlinearities as for example switches, tow-slope
transformer saturation or thyristors. These interrupts can also occur in between
time steps.

In case of such an interrupt, all time dependent variables are interpolated to the
instant of interrupt and the simulation restarts at that point. This prevents
numerical oscillations and allows much a lower integration stepsize in case of
power electronics devices.

The dynamic model equations of the voltage-controllers (vco) and the power
system stabilisers (pss) are solved simultaneously with the electrical generator
and passive network equations (stepsize dtgrd).

Other non-electrical model equations like prime mover systems (pmu), primary
controllers (pco) and motor driven machines (mdm) are solved using the
integration stepsize dtpmu in case of a multi-rate simulation.

N OTE : The smallest stepsize has to be specified for dtgrd. All other step sizes
must be multiples of dtgrd.

19.3.3 Automatic Step Size Adaption

A good way to speed up the simulation considerably is using the option
”Automatic Step Size Adaption” on the basic page of the ComSim command.
This option will enable the step size adaptation algorithm.

With this algorithm the time step between two calculations of all variables is not
held constant but will be enlarged, when no incidences, like external events or
variables reaching limitations, are encountered during this period until the
maximum time step is reached.

Every time an external or internal event occurs between two time steps, the

Stability Analysis and Simulation of Transients 19-363

DIgSILENT PowerFactory Time-Domain Simulations

system variables are calculated for the exact point of time, when the event is
tanking place and the time step is automatically reduced to its minimum value.
So the behaviour of the system during a transient event is represented in the
best way.

If this option is activated, on the page ”step size” there will be the two integration
step sizes available:

dtemt / dtgrd minimum step size for EMT respectively RMS simulations

dtemt max / dtgrd max maximum step size for the method of simulation

Further parameters to adapt this algorithm can be found and the ”Step Size
Adaptation” page:

errmax Maximum Prediction Error (typical 0.01)

errinc Minimum Prediction Error (typical 0.01)

ninc Delay for Step Size Increase (typical 10 time steps)

finc Speed Factor for increasing the time step (default value 1.5)

fdec Speed Factor for decreasing the time step (default value 2)

ddtemt max Maximum increase of the time step only for EMT simulations
(typical 0.001 sec)

N OTE : The simulation time can be very sensitive to some of the parameters.
For example when you increase the maximum time step the duration
of calculating the transients may only increase to a certain point an
then decrease again due to variables reaching their limits and thus
decreasing time steps. So please observe the simulation time and the
results critically for different simulation parameters.

19.3.4 Advanced Options

The advanced options may be used to tailor-tune the performance of the
simulation algorithm. Less experienced users are recommended to use the
typical values.

The ”Resolution Factor” kres of the event control determines the time span
which is used to synchronise events. Every time an internal or external event
occurs during the simulation between time step i and i + 1, PowerFactory will
reduce the time step and to the minimum step size after step i. Then the time
span between the steps will be divided according to the resolution factor and the
event will take place at the nearest fraction of the time step.

Stability Analysis and Simulation of Transients 19-364

DIgSILENT PowerFactory Time-Domain Simulations

If two or more events are all found to occur within that time span, they will be
considered as happening simultaneously, all at the same moment in time. Hence
the maximum time difference between two events is the (minimum) simulation
step size dtgrd times kres.

The all system variables are then interpolated to the point in time, when the
event is taking place, and the simulation is started from there. A higher
resolution factor decreases the minimum time span between events. The typical
value of 0.001 is normally sufficient.
After the event PowerFactory can re-initialise all variables again, when the
option is activated.

Further parameters can be changed to control the simulation algorithm.

For integration control:

errseq: Maximum Error of State Equations (typical: 0.1%)

itrpx: Maximum Number of Successive State Iterations (typical: 10)

alpha rms: Damping Factor (RMS) (typical: 1)

alpha emt: Damping Factor (EMT) (typical: 0.9)

For iteration control:

errsm: Maximum Iteration Error of Nodal Equations (typical: 10*errlf )

erreq: Maximum Error of Model Equations (typical: 1%)

itrlx: Maximum Number of Iterations (typical: 25)

itrjx: Iteration Limit to Recompute Jacobian Matrix (typical: 5)

• itrpx specifies the max. number of iterations at each integration step which
are allowed to reach the max. tolerable bus-error errsm. During the
transient simulation process, the typical number of iterations required is 1
to 5. Under certain conditions - i.e. after switching operations - up to 25
iterations may be observed.

• The iteration error errsm depends on the nominal power of the machines
and voltage levels. As an adequate starting value, errsm should be set to:
errsm = 10 ∗ errlf , where errlf is the “Max. Allowable Load-Flow Error for
each Bus”. Checking is done best by plotting some voltages at generator
busbars. If there are voltage steps observed, the value of errsm should be
reduced.

The signal buffer defines ... ToDo

Stability Analysis and Simulation of Transients 19-365

DIgSILENT PowerFactory Time-Domain Simulations

You can chose between two different options for the reference system in your
network. The ”Local Reference System” will automatically set up different
reference machines for the rotor angle when separate systems exist or a part of
the system becomes isolated during the simulation. Otherwise one reference will
be used for the global system.
PowerFactory can also calculate the maximum deviation between the rotor
angles between the synchronous machines in the system. This variable is then
called dfrotx and can be chosen and displayed from the variables of all
synchronous generators in the system. This variable can be used as an indicator
for the synchronous operation of a large transmission system.

19.3.5 Noise Generation

The element “Noise Generator” (ElmNoise) can be used in a transient
simulation to produce a noise signal based on random numbers. On the Noise
Generation page the type of this generator can be selected for producing these
random numbers. The random number generator can be automatically chosen
with auto, which is the default value and most often used.

Also the option renew may be chosen. Then the random seed of the noise
generator can be selected manually from ”A” to ”K”. Thus the noise signal will
look the same in every simulation, i.e. the results of a former simulation can be
reproduced exactly.

19.3.6 Advanced Simulation Options - Load-Flow

There are further options, which can influence the simulation process and its
results. In the load-flow command dialogue (ComLdf, see also section 10.7) on
the page for the advanced simulation options, the influence of protection devices
or various controller models can be neglected. Hence the chosen models or
protection devices will be ignored during the simulation as well as in load-flow
and other calculations.
The protection devices considered can be chosen between:

none no protection devices are considered in the calculations

all all protection devices are considered

main only the protection devices are in operation, which are defined as ’main’
devices

backup only the ’backup’ protection devices are considered

According to the controller models, there is the possibility to ignore all controllers
and mechanical elements with the option ”Ignore Composite Elements”. If there
are only some model types you want to neglect in the simulation, you may move

Stability Analysis and Simulation of Transients 19-366

DIgSILENT PowerFactory Time-Domain Simulations

Figure 19.2: Advanced Simulation Options in the ComLdf Command Dialogue

them from the left window ”Consider Elements” to the right windows ”Ignored
Elements”.

19.4 Result Objects

During an EMT or RMS simulation a high number of signal variables is changing

in time. To reduce the available data and to narrow down the number of variables
to those necessary for the analysis of every special case, a selection of these
signals for later use has to be defined.

Therefore one or more result objects, containing the result variables, can be
configured. The simulation function needs the reference to a result object to
store the results.

The command dialogues for calculation functions, that produce signals, have
result object references, as depicted in Fig. 19.3 for the initial conditions
dialogue.
Such a result object reference is referring to the currently used result object. The

Stability Analysis and Simulation of Transients 19-367

DIgSILENT PowerFactory Time-Domain Simulations

Figure 19.3: Result object reference

downward arrowed button is used to select, or reset the reference or to edit the
contents of the referenced result object.
The right-arrowed button is used to edit the result object itself. When editing the
output variables press this E DIT button and then C ONTENTS to get access to
the list of variables stored inside the result object. This will pop up the
corresponding ElmRes edit dialogue.

An easier way to edit the result object is to press the button on the main
toolbar, or to select the Data →Stability →Result Variables option on the main
menu. This will enable the user to edit the contents of the currently selected
Result object in the Initial Conditions command dialogue. Result objects
(ElmRes) are treated in detail in chapter 25.1.

To add variables of different elements to the result object for RMS and EMT
simulations, right-click on the preferred element in the graphic and select
Define... and Variable Set (Sim)... as shown in figure Fig. 19.4.

Figure 19.4: Defining a Variable Set for an Element

Stability Analysis and Simulation of Transients 19-368

DIgSILENT PowerFactory Time-Domain Simulations

Then this element is monitored during the simulation. The result object is
automatically opened. By double-clicking on the variable set you can then
select the desired variables (see also section ??).

N OTE : Most of the variables for RMS and EMT simulations are identical. Nev-
ertheless there may exist variables that are valid for EMT but not for
RMS calculations. It is advisable only to use variables for the calcula-
tion you are performing.

19.4.1 Saving Results from previous Simulations

The variables to be monitored are stored in the result object All calculations.
Here the results of the variables of the current simulation are stored as well. If
you want to see the results of two different simulations e.g. in one virtual
instrument, there is the possibility to save the result object of a previous
simulation simply by copying and renaming the result object All calculations .

This can easily be done in the data manager. You will find the result object in the
currently active study case. Just copy the result object and paste it into the same
study case. Then a second result object will be created with the name All
calculations(1). You may also rename the object.

In the next simulation, the default result object All calculations will be
overwritten with the new results, but the copied results will not be modified and
can be displayed together with the new simulation results in one plot (see also
section 24.2.1).

19.5 Events

Besides the reference to a result object the simulation function needs a

reference to an event object to determine the simulation events. The default
event object in PowerFactory is Simulation Events and, like the result object, it
is also stored inside the study case.
External events are used in steady-state calculations (e.g. short-circuit
calculations) as well as for transient calculations (Simulations).

PowerFactory offers several kinds of events for time-domain simulations:

1. Control switch events (EvtSwitch)

2. Set parameter events (EvtParam)

Stability Analysis and Simulation of Transients 19-369

DIgSILENT PowerFactory Time-Domain Simulations

3. Short-circuit events (EvtShc)

4. Intercircuit fault events (EvtShcll)

5. Events of synchronous machines (EvtSym)

6. Events of loads (EvtLod)

7. Set integration step size (EvtStep)

8. Outage of element (EvtOutage)

The different events are stored in the event object. The contents of the currently
selected Event Object, which can be found in the dialogue of the initial
conditions command ComInc, can be edited by using the right-arrowed ( E DIT )
button and then the C ONTENTS button to get access to the event list stored
inside the event object.

You can easier access the event object from the main toolbar by pressing the
button. You will the see a list of the currently defined events including the
time, when the event will occur, and the related object. Figure Fig. 19.5 shows
an example for a set of events.

Figure 19.5: The event object including a set of events

When creating a new event, use the button in the toolbar of the Simulation
Events object. You can then chose the kind of event from the list in the dialogue.

Stability Analysis and Simulation of Transients 19-370

DIgSILENT PowerFactory Time-Domain Simulations

You can also modify the events during a simulation by stopping the calculation,
editing the events and continuing the simulation.

Another way of defining events is - when the initial conditions ( ) are

calculated or the simulation is already running - to double-click on the cubicles to
create switching events respectively to right-click on an element and then select
a element related event such as Define... →Control Switch, Define... →Event of
Load or Define... →Short-Circuit Event.

During a simulation all previous events, which already occurred, are displayed in
a grey font style and can’t be changed anymore. When the simulation is finished
or is stopped manually, the events which are still to come in the simulation can
be altered and new events can be created as well.

N OTE : At the ’end’ of a simulation the event list shows all the events, which
are now in a grey colour. Thus they can’t be modified again for this
simulation, because the simulation could be restarted from this point
on. To change the events for a new simulation you have first to initialise
the calculation again ( ), so the simulation time is set back to the
beginning.

19.5.1 Switching Events

Switching events are used only in transient simulations. To create a new
switching event, the button on the main menu can be pressed, if this button
is enabled, which will bring a browser with all defined simulation events to the
front. Pressing the button in this browser will show a ComNew dialogue
which can be used to create a new switching event.

The reference to the switch has to be set by hand. Any switch in the power
system may be selected, thus enabling the switching off lines, generators,
motors, loads, etc. Here you are free to select the switches/breakers of all
phases or only of one or two phases.

More than one switching event has to be created if, for instance, a line has to be
opened at both ends. These switching events should then have the same
execution time.

19.5.2 Set Parameter Events

With this event you can set or change an input parameter of any element or DSL
model.
First you may insert a specified time of the simulation, when the event will occur.
You have then to specify/select an element using the button and then
choosing Select ... for the context menu. Afterwards insert the name and the
new value of a valid element parameter.

Stability Analysis and Simulation of Transients 19-371

DIgSILENT PowerFactory Time-Domain Simulations

19.5.3 Short-Circuit Events

This event causes a short-circuit on a busbar, terminal or on a specified point on
the line. You can specify the fault type (three phase, two phase or single phase
faults) as well as the fault resistance and reactance and the phases which are
affected.

There is no possibility to define the duration of the fault. To clear the fault,
another short-circuit event has to be defined, which will clear the fault in the
same place. You can see an example in Figure Fig. 19.5.

19.5.4 Intercircuit Fault Events

This event is similar to the short-circuit event described before. Two different
elements and their phase can be chosen between which the fault occurs. Equal
to the EvtShc four different elements can be chosen:

• a busbar (StaBar)

• a terminal (ElmTerm)

• a overhead-line or cable (ElmLne)

• a line routes (ElmLnerout)

Here only single phase faults are allowed.

19.5.5 Events of Synchronous Machines

For synchronous machines there is a special event to easily change the
mechanical torque of the machine. A point in time in the simulation and an active
synchronous machine ElmSym has to specified. Then you can define the
additional mechanical torque supplied to the generator. The torque can be
positive or negative and is entered in per unit values.

19.5.6 Events of Loads

For a certain load the point in time in the simulation and a load element
(ElmLod, ElmLodlv or ElmLodlvp) has to specified. The value of the load can
then be altered using the load event.

There are different ways to change the power of the selected load:

Incremental Change adds additional power (positive or negative) to the current

value in % of the nominal power of the load

Stability Analysis and Simulation of Transients 19-372

DIgSILENT PowerFactory Time-Domain Simulations

Absolute Change changes the current value of the power to the given value in
% of the nominal power of the load

Nominal Change changes current and nominal value of the power to the
specified value in % of the nominal power of the load

19.5.7 Set Integration Step Size

With this event the integration step size of the current simulation can be
changed. Depending on the type of time-domain simulation the parameter of the
step size dtemt max for EMT or dtgrd max for RMS simulation is affected.

19.5.8 Outage of Element

This event can only be used during a RMS simulation, when an element shall be
put out of service at a certain point in time. Then the option ”take element out of
service” is to be used. It is not possible to bring back the outaged elements into
service in the transient simulation. This option is active only in steady-state
calculation functions, e.g. short-circuit calculation or reliability assessment. IN
time-domain simulation the following error message will occur in the output
window:

DIgSI/err (t=000:000 ms) - Outage Event in Simulation not available.

Use Switch-Event instead!

19.5.9 Save Results

This event is only used in the PowerFactory Monitor part of the programm. It
can’t be used during time-domain simulations.

19.6 Error Messages and Warnings

The dynamic model equations of the voltage-controllers (vco) and the power
system stabilisers (pss) are solved simultaneously with the electrical generator
and passive network equations (stepsize ’dtgrd’).

In case of simulations with the quasi-steady network model, the integration step
size varies between 1 [ms] for small networks with very small machines of some
[kVA] rated power and 20 – 200 [ms] for high- voltage networks with large
machines of some hundreds of [MVA]. If during the simulation process the error
message “integration failed to converge” occurs permanently, the user is advised
to reduce the integration stepsize ’dtgrd’.

Stability Analysis and Simulation of Transients 19-373

DIgSILENT PowerFactory Time-Domain Simulations

DIgSI/info - ’\Holger.IntUser\DFIG-Example.IntPrj\WTG1.ElmNet\ASM
and Rotor-side Converter.ElmComp\Pitch Control.ElmDsl’:
DIgSI/info - Derivative of x1 not equal 0!

DIgSI/err - Some models could not be initialised.

Please check the following models:
DIgSI/err - ’Simple Grid\AVR Common Model.ElmDsl’:
DIgSI/err - Initial conditions not valid !

The reason for this error message very frequently is a common model which is
not connected to a frame, thus it can’t be initialised and the error occurs. For
instance the DSL element AVR Common Model is in service, but the frame it
belongs to is out of service. Then PowerFactory can not calculate the initial
conditions of the model. This will only happen, when the common model is not
stored inside the composite model.

Another possibility would be to execute a “Slot Update” or remove a DSL

element from a slot of active ElmComp element. Then the common model is in
service but not connected to a frame, hence this error message will occur.

DIgSI/wrng - variable never used: ’speed_gen’

DIgSI/info - Variable may be used in output(),fault(),event()

The message is only a warning informing you, that a variable is defined in a DSL
model but never used in this block. You can choose, if you want to remove it. But
there might be a mistake, so check if this variable is redundant.

DIgSI/err - State variable without derivative: ’speed_state’

DIgSI/err - Variable without initial conditions: ’speed_state’

DIgSI/info - Check initial conditions of ’\Holger.IntUser\Pitch Ctrl

.IntPrj\Library\Blade Control.BlkDef’:
DIgSI/err - algebr. loop: variable ’beta’
DIgSI/err - Algebr. loop: definition of ’yi’: ’beta_ref-beta’
DIgSI/err - Algebr. loop: definition of ’dx1’: ’Ka*yi/Ta’
DIgSI/err - algebr. loop: parameter 1 of function ’lim’:’y1+Tr*dx1’
DIgSI/err - Algebr. loop: definition of ’yi1’: ’lim()’
DIgSI/err - algebr. loop: parameter 1 of function ’lim’: ’yi1’
DIgSI/err - algebr. loop found: definition of ’beta’: ’lim()’
DIgSI/err - Model ’Blade Control’ contains fault !

If you get an algebraic loop, you should thoroughly check your block definition
and the equations for this. This error message means that PowerFactory can’t
calculate a variable which is depending on another variable and vice versa.
Check carefully your equations and the naming of your variables. Often this error
occurs when two variables have the same name or have a wrong typing. The
message shows you where to look at.

A simple example of an algebraic loop is:

Stability Analysis and Simulation of Transients 19-374

DIgSILENT PowerFactory Time-Domain Simulations

a = b+5
b = 2*a
DIgSI/err - Arguments in call and definition do not match !
DIgSI/err - Argument in call ’Kc’, argument in macro ’x’
DIgSI/info - Macro call in model: ’uerrs=’\Holger.IntUser\DFIG-
Example.IntPrj\Library\Block Definitions\
Controller.BlkDef’(yi;;Kc,Tc;)’
This error message refers to the reason, that a different number of parameters,
internal variables or limiting parameters do exist in the block reference and in the
block definition.
You can select the U PDATE button in the dialogue of the block reference. Then
all variables and parameters will be reset to their default name.
DIgSI/err - Variable without initial conditions: ’x’
DIgSI/info - Properties of variable ’x’: ’state’,’double’,’local’
DIgSI/err - Model ’Controller’ contains fault !
DIgSI/wrng - Intern variable ’o13’ missing in header of macro
definition!
DIgSI/wrng - Intern variable without definition: ’bias’
DIgSI/info - This variable keeps its initial value.
DIgSI/err - Intern variable without definition and initial
condition: ’Kudc’
DIgSI/err - Model ’DC Voltage Control’ contains fault !
A parameter or internal variable used for calculating initial conditions is not
defined in one of the blocks. Often the spelling of the parameter/variable on the
”additional equations” page is wrong or a S LOT U PDATE of a block changed
the name of parameter.
DIgSI/err - ’\Holger.IntUser\Windpark\Library\Block\Ctrl.BlkDef’:
DIgSI/err - Intern variable without definition and initial
condition: ’up’
DIgSI/err - Intern variable without definition and initial
condition: ’uq’
DIgSI/err - Model ’PQ Controller’ contains fault !
DIgSI/err - Initialization of ’\Holger.IntUser\Windpark.IntPrj\
Grid.ElmNet\Control.ElmDsl’ failed !
DIgSI/err - Calculation not possible !
DIgSI/err - Initial conditions not valid !
This error message states, that the internal variable/signals upand uqcan not be
initialised. This may often happen, when the input or output definition of the slot
do not match to the inputs and outputs defined in the DSL model inserted into
the slot. Check the name of these variables/signals in the frame and in the block
diagram.

Stability Analysis and Simulation of Transients 19-375

DIgSILENT PowerFactory Time-Domain Simulations

DIgSI/wrng - ’\Holger.IntUser\Windpark.IntPrj\Grid.ElmNet\
Controller.ElmDsl’:
DIgSI/wrng - Unnecessary inputs have been left unchanged
(arbitrary choice)!

An output of the DSL model is not equal zero, although it is not used, i.e. the
output is not connected to an input to another DSL model.

Unbalanced simulation needs an unbalanced load flow, grid

contains unbalanced objects.

When the investigated system does include elements, which are unbalanced,
then the load-flow command must be executed with the option unbalanced
activated. Otherwise in a balanced load-flow these elements are neglected and
thus can not be initialised when calculating the initial conditions.

Input ’...’ not initialized!

Output ’...’ not initialized!

Signal Buffer Size exceeded!

Increase Parameter signal buffer on page: Advanced Options
in Calculation of Initial Conditions.
Simulation can be restarted after program restart.

no convergence in simulation !

No convergency in iteration-loop

System matrix could not be solved

DIgSI/err (t=07:788 s) - ’\Holger.IntUser\WindPark\Grid.ElmNet\

WT.ElmAsmsc’:
DIgSI/err (t=07:788 s) - System-Matrix Inversion failed !

19.7 Run a Simulation

When the initial values have been calculated successfully, the button on the
main toolbar will be activated and can be pressed to start the simulation.

The simulation is performed for the time interval between the start time defined
in the initial conditions command ComInc and stop time tstop, which can be
specified in the simulation dialogue. After a simulation has finished, it may be
continued by pressing the button again and entering a new stop time. In the
latter case, the stop time may also be entered as relative to the current
simulation time.

Stability Analysis and Simulation of Transients 19-376

DIgSILENT PowerFactory Time-Domain Simulations

A running simulation may be interrupted by pressing the or the button

on the main toolbar. Additional events can be created, while the simulation
pauses and results may be viewed. The simulation is then continued by pressing
the button again. Pausing and continuing the simulation may be done as
often as needed.

Stability Analysis and Simulation of Transients 19-377

DIgSILENT PowerFactory Models for Stability Analysis

Chapter 20

Models for Stability Analysis

Stability analysis calculations are typically based on predefined system models.

In the majority of cases the well known IEEE definitions for controllers, prime
movers and other associated devices and functions are in use.
For planning purposes, this approach might be acceptable. The predefined sets
of parameters will allow a favourable and reasonable behaviour of the analysed
system. This approach, however, is often also applied for the purpose of
operation analysis. For such analysis, the standard IEEE models are only
seldom applicable.

The lack of more accurate controller models has even led to manufacturers
being asked to deliver block diagrams and parameters according to a list of
available IEEE models, although these manufacturers were able to supply exact
controller model to perform highly accurate system modelling studies.

Utilities and consultants with an in-depth knowledge and tradition of conducting

system operation performance and optimisation studies have a clear need for
adequate methods and tools for creating accurate transient models for stability
analysis.

This includes complex operation analysis and special component planning

problems. All this led to the development of the highly flexible and accurate
DIgSILENT PowerFactory time-domain modelling features, which are
introduced in this chapter.

20.1 System Modelling Approach

System modelling for stability analysis purposes is one of the most critical issues
in the field of power system analysis. Depending on the implemented model
accuracy, large-signal validity, available system parameters and applied faults or
tests, nearly any result could be produced and arguments could be found for
their justification.

This is one aspect of the complexity of a transient stability study. The other
aspect results from the often large set of time-domain models that are required,

Stability Analysis and Simulation of Transients 20-378

DIgSILENT PowerFactory Models for Stability Analysis

each of which may be a combination of other models. All these time-domain

models are ultimately wired together into one single large transient model from
which the basic set of system differential equations can be obtained.

Given this complexity of a transient analysis problem, the PowerFactory

modelling philosophy targeted towards a strictly hierarchical system modelling
approach, which combines both graphical and script-based modelling methods.

The basis for the modelling approach is formed by the basic hierarchical levels of
time-domain modelling:

• The DSL block definitions, based on the ”DIgSILENT Simulation

Language” (DSL), form the basic building blocks, to represent transfer
functions and differential equations for the more complex transient models.

• The build-in models and common models. The build-in models are the
transient models for standard primary and secondary power system
equipment, i.e. for generators, motors, static VAr compensators, voltage
controllers, prime mover units, etc.
The common models are based on the DSL block definitions and are the
front-end of the user-defined transient models.

• The composite models are based on composite frames and used to

combine and interconnect several build-in and/or common models. The
composite frames enable the reuse of the basic structure of the
composite model.

The relation between these models and the way that they are used is best
described in the following example.

Suppose the frequency deviations due to the sudden loss of a fully loaded 600
MW unit in a particular network is to be analysed. Depending on the network and
the required detail in the calculated results, such analysis may ask for a detailed
modelling of the voltage controllers, prime movers and primary controllers, or
any other important equipment for all large generators in the system.

power voltage
system controller
stabilizer (vco) Uerrs
(pss) Upss
synchronous
generator
PG
(ElmSym)
prime
primary mover ∆f
controller unit
(pco) at (pmu) PT

Figure 20.1: Example of a composite generator or power plant model

Stability Analysis and Simulation of Transients 20-379

DIgSILENT PowerFactory Models for Stability Analysis

An typical configuration of a synchronous generator with power system

stabiliser, voltage controller, primary controller, and prime mover model is shown
in Fig. 20.1. To create such a model, the following actions are required:

1. Transient models for each required controller type or unit type have to be
defined (Model/Block Definition).

2. For each generator, the transient models of the individual controller must
be customised by setting the parameters to the correct values (Common
Model).

3. A diagram has to be made defining the connections between the inputs

and outputs of the various models (Composite Frame).

4. For each generator, the diagram and the customised transient models are
to be grouped together to define an unique ’composite’ generator model
(Composite Model).

It may seem unnecessary to include point 2 and 3: it would be possible to create

customised transient models for each generator directly, with ‘burned-in’
parameter settings, and to link these models to a generator without having to
define a diagram first. This, however, would mean that we would have to create
a new voltage controller, e.g. for each generator in the system.

Often the design of many of these voltage controllers will be similar. To omit the
need of creating copies of these controllers for each generator and to avoid
redundant copies of controllers or also of whole generator models.

N OTE : Here the same relationship between individual controller (Common

Model) and controller definition (Model Definition) respectively be-
tween the generic power plant diagram (Composite Frame) and the
individual power plant (Composite Model) is used, as the relationship
between element and type definition (see also chapter ??).

DIgSILENT PowerFactory uses two key objects in creating composite models,

which can be compared to the element definition of the different elements:

• The Common Model (ElmDsl) combines general time-domain models or

model equations (a block definition) with a set of parameter values and
creates a integrated time-domain model.

• The Composite Model (ElmComp) connects a set of time-domain models

inside a diagram (a composite frame) and creates a ‘composite model’.

The principle diagram for the composite model and the relation between the
different types of models are displayed in Fig. 20.2.

Stability Analysis and Simulation of Transients 20-380

DIgSILENT PowerFactory Models for Stability Analysis

Figure 20.2: Example of a composite model

Stability Analysis and Simulation of Transients 20-381

DIgSILENT PowerFactory Models for Stability Analysis

[1] The Composite Model (ElmComp) has a reference to a a definition of a

composite frame. This composite frame is basically a schematic diagram
containing various empty slots, in which controller or elements can be
assigned. These slots are then interconnected according to the diagram
(see section 20.3). The slots in the composite frame are pre-configured for
specific transient models.
[2] The schematic diagram in Fig. 20.2 shows a Composite Frame (BlkDef)
which has one slot for a synchronous machine, one for a primary controller
(pco slot), one for the prime mover unit (pmu slot), and one for a voltage
controller (vco slot). The composite model, which uses this composite
frame, shows a list of the available slots and the name of the slot. Now the
specific synchronous generator, voltage controller or prime mover model
can be inserted into these slots.
[3] The synchronous machine, the primary controller and the prime mover unit
that are used in the Composite Model are both Build-In Models. This
means the elements are pre-configured elements which do not need a
specific model definition. Into the slots all kinds of elements can be
inserted, which are able to input or output variables, e.g. converters,
busbars, etc.
[4] The voltage controller, however, is an user-defined Common Model. The
‘front-end’ of all user-defined transient models is always such a common
model (ElmDsl), which combines a model definition with specific
parameter settings.
[5] The common model has a reference to the Model Definition (BlkDef),
which looks similar to the composite frame. Here different blocks are
defined and connected together according to the diagram. The input and
output variables have to fit to the slot definition of the slot the model is
defined to.

N OTE : Not all slots of the composite model have to be used. There can also
be empty slots. Then the input of this slot is not used and the output
will be assumed to be constant over the complete simulation.

The usage of composite models with its composite frame as well as the common
model with its block definitions are described in the next sections.
The design and creation of user defined common models using the ”DIgSILENT
Simulation Language” (DSL) can be found in chapter 21.

20.2 The Composite Model

Stability Analysis and Simulation of Transients 20-382

DIgSILENT PowerFactory Models for Stability Analysis

A composite model element (ElmComp, ) can created by using the ”New

Object” ( ) button in the toolbar of the database manager and selecting
Composite Model. The next step is to select the composite frame. The
composite frame can either be stored in the global or in the local library and can
be compared to the type definition of the electrical elements. The composite
model then shows the list of slots in the composite frame as shown in Fig. 20.3.

Existing controllers or models can be assigned to a slot manually by

right-clicking the slot and selecting Select Element/Type, as depicted in Fig.
20.3. A data manger window will pop up and you can then browse the grid for
the element to insert into the selected slot.

Figure 20.3: Editing the Composite Element Folder

If inserting controller models into a slot often the controller element has not yet
been created. To create a new controller select New Element/Type from the
context menu of the slot. This will show a list of available build-in controller
models, which will fit into the slot or user defined models (ElmDsl).

Selecting a build-in model will open the element dialogue of that model in order
to define the parameters, similar to e.g. a transformer element. You will find the
required parameters for the model on the RMS/EMT page. In the case of a
common model, a block definition has to be selected prior to setting the model
parameters (see section 20.4 and Fig. 20.2).

If a element is assigned to a slot, you have then the possibility to edit the
assigned element by simply selecting Define... →Edit Element/Type. The menu

Stability Analysis and Simulation of Transients 20-383

DIgSILENT PowerFactory Models for Stability Analysis

command Define... →Reset Element/Type will reset the slot, so it is empty again.

N OTE : Depending on the settings of the individual slot the menu command
Define... →Reset Element/Type will not only clear the marked slot but
also delete the build-in model, if it is stored inside the composite model
in the data manager. These settings are explained in the section 20.3
in more details.

A faster method for defining standard composite models is to right click an object
in the single line diagram and selecting Define... from the context menu of the
element.

When a standard composite model is available for the selected object, a list of
the available controllers is shown. Selecting a controller will add it to the
composite model, which is automatically created when no composite model
exists yet for the selected object.

In Fig. 20.4, the menu is shown for the synchronous machine. Standard
composite models are available for

• The synchronous motor and generator

• The asynchronous motor and generator

• The static VAr system

Figure 20.4: Defining a standard composite model

Stability Analysis and Simulation of Transients 20-384

DIgSILENT PowerFactory Models for Stability Analysis

20.2.1 Slot Update

The S LOT U PDATE button in the composite model will re-read the slot
definitions from the composite frame and will cancel all invalid slot assignments.
A slot assignment is invalid when a model has been assigned to a slot which is
not suited to receive such a model, i.e. a voltage controller cannot be assigned
to a slot defined for a primary controller model.

All build-in or common models which have been created for a specific composite
model are stored in that composite model itself. The contents of a composite
model are shown in the database manager where the composite model is
treated as a normal database folder. Basic power system equipment, such as
synchronous machines or static VAr compensators, are normally not stored in
the composite folder, but in the grid itself.

The slot update will try to re-assign each model found in its contents to the
corresponding slot. Hereby the options defined for each slot are important.
These are described in the paragraph ‘Classification’ in section 20.3.

20.2.2 Step Response

The S TEP R ESPONSE button in the composite model will activate the Step
Response Command ComStepres. The dialogue can be seen in Fig. 20.5.

Figure 20.5: Dialogue of the Step Response Command

Stability Analysis and Simulation of Transients 20-385

DIgSILENT PowerFactory Models for Stability Analysis

Next to the references to the composite model, the template and the target
directory, the two step response tests, which will be created, can be specified.
Also the study case to be activated can be chosen. When the E XECUTE is
activated, PowerFactory will create a new folder in the current project named
”Step Response Test”. Fig. 20.6 shows this folder in the data manager.

Figure 20.6: Step Response Folder in the Data Manager

Inside this folder a second folder with the name of the composite model, which is
to be tested, is created. Here you can found the simple test grid including only
the generator, the complete composite model and a load. Additionally there will
be two new study cases in which a step response for the AVR and the PCU
respectively of the composite model can be tested.

You can change between the two study cases and your old cases by activating
and deactivating them.

N OTE : There now doesn’t exist any connection between the original and the
new elements of the composite model anymore. So you can change
all settings of the controller without changing your network.

After testing the controller, the folder ”Step Response Test” can be deleted
completely without loss of information in the original network.

20.3 The Composite Frame

A composite frame is a block diagram which defines two or more slots, their
input and output signals, and the connections between them. A composite frame
is defined graphically by drawing it.

Drawing a composite model frame is similar to drawing a normal block diagram.

The main difference is that in stead of common blocks, only slots may be used.

To create a new composite frame select the ”Insert New Graphic” button on
the main toolbar and then selecting Block/Frame Diagram and pressing
E XECUTE as shown in Fig. 20.7. This new block definition will then be
automatically created in the local library.

Stability Analysis and Simulation of Transients 20-386

DIgSILENT PowerFactory Models for Stability Analysis

Figure 20.7: Creating a new Composite Frame

An empty diagram of the frame will appear in the graphics window. A slot is then
created by selecting the button in the graphics toolbox and positioning the
slot on the drawing surface by once clicking at the appropriate position. This is
similar to placing elements in the single line diagram.

An empty slot will be drawn on the page. To define the input and output signals
and different parameters of the slot, edit the slot by double-clicking it. The slot
edit dialogue will pop up as depicted in Fig. 20.8.

Name and Sequences

The name of the slot will appear later in the dialogue of the composite model
and should be given according to the element that is to be assigned (e.g. ’vco
slot’). The ”Sequence” parameter defines the order of the slots appearing in the
composite model dialogue.

Input and Output Signals

The input and output signals have to be defined for each slot. The available
signal names for the build-in transient models can be found in corresponding
technical reference of the elements. The given input and output signal names in
this slot dialogue have to match the input/output signals of the given transient
model exactly, or the signals will not be connected properly and an error
message will occur.

Only after one or more input and output signals have been defined for a slot, it
becomes possible to connect the slot with signal lines to other slots. It is

Stability Analysis and Simulation of Transients 20-387

DIgSILENT PowerFactory Models for Stability Analysis

Figure 20.8: Slot dialogue

therefore recommended to first position and edit all slots and draw the signal
connections thereafter.

Limiting Signals
Also there is the possibility to enter ‘limiting signals’. These signals are handled
from PowerFactory exactly like the normal input signals. The difference is only
in the graphical representation in the block diagram. These signals will be shown
as inputs on the top or bottom of the slot.

Class/Name Filter
Additionally there is the possibility to specify a filter for the class name and/or for
the model name to be inserted. This makes sense e.g. when only synchronous
machines should be assigned to the slot. Then you would enter ElmSym* for
the class name. PowerFactory then will only allow the element class
“synchronous machine” to be inserted into the slot. A filter for a specific (part of
an) element name can also be defined.

Stability Analysis and Simulation of Transients 20-388

DIgSILENT PowerFactory Models for Stability Analysis

Classification
The classification options does only affect the external behaviour of the slot.

Linear The slot representation in the frame diagram will be as a linear or

non-linear model.

Automatic, model will be created When this option is activated, the function
’Slot Update’ (see sectionSlotUpdate) will automatically create a DSL
model and ask for a block definition from the library.

Local, Model must be stored inside This option is activated by default. This
means that when a S LOT U PDATE is executed in the composite model,
PowerFactory will only search for elements, which are stored inside the
ElmComp. A reference to models, which are stored outside, i.e. like the
synchronous generator in a plant model, will be removed from the slot.

N OTE : Not all input or output signals of build-in elements or common models
have to be used and defined in the slot. Also a slot may only have input
or output signal.
For example the voltage or frequency of a AC voltage source ElmVac
may be controlled by an external function. So the slot for the source
will only have two input signal u0 and f0.

More information about drawing composite frame diagrams can be found in

section 20.6, page 20-395.

20.3.1 Assigning a Block Definition to a Slot

There is the possibility to assign a block definition (BlkDef) directly to a slot. This
option will simplify the handling of the slot and prevent errors due to not
matching signal names of slot and assigned block.

To assign the external form of a block definition to the selected slot, edit the slot
by double-clicking it and choose the ”select” button for the ”Block Definition”
in the dialogue. Now you can select the block definition, e.g. the type of
controller or build-in element, which should be assigned to this slot later on.

For example if the new defined slot ought to represent a synchronous machine
in the frame diagram, you can choose a predefined block definition to insert the
input and output signals to this slot available for the element ElmSym. A
controller for example should only assigning to a slot, when only this type of
controller is to be inserted into this slot but no other model.

Some predefined block definitions can be found in the global library in the path
L IBRARY\M ODELS\B UILD - IN.

Stability Analysis and Simulation of Transients 20-389

DIgSILENT PowerFactory Models for Stability Analysis

When you select the block definition (in our example the ElmSym.BlkDef), the
input and output as well as limiting signals will disappear from the dialogue of
the slot. The filter for the class name will automatically be entered. When
selecting the OK button, the slot will then show the right inputs and output of
the block definition.

N OTE : When a block definition is assigned directly to a slot, only the

input/output signals is set automatically. The internal equa-
tions/definitions of the block definition are not implemented into the
slot and the slot itself remains empty. There is always the need to cre-
ate a common model, which is the inserted into slot of the composite
model.
When the slot refers to an outside block definition, take care that this
reference is also inside your project. If the reference to the definition is
invalid or changed, the slot may be changed as well. So use the option
of assigning a block very carefully.

20.4 The Common Model

The common model element (ElmDsl, ) is the front-end object for all
user-defined block definitions. This means that user-defined transient models,
but also the block diagrams that are ready shipped with the PowerFactory
program, cannot be used other than through a common model. The common
model combines a model or block definition with specific set of parameter values.

The general structure of the common model and its block definition is depicted in
Fig. 20.9.

The block definition may either be a ‘primitive’, or a composite block definition

(model definition). A model definition contains block references which may in
turn either point to a primitive block definition or to a another composite block
definition. The structure of the block definition is thus recursive and it should be
watched that this recursive structure does not contain circular references to
composite block definitions.

A primitive block definition contains one or more DSL expressions and forms a
basic block for more complex transient models. A description of how to use and
create DSL models can be found in chapter 21.

Each block definition generally has one or more parameters which can be
changed to define the model’s behaviour. Two kinds of parameters are
supported:

• Scalar parameters, i.e. amplification factors, offsets, setpoints, etc.

Stability Analysis and Simulation of Transients 20-390

DIgSILENT PowerFactory Models for Stability Analysis

Figure 20.9: Structure of the Common Model

• Two and three dimensional array parameters, which are used in the DSL
lapprox()/lapprox2() and sapprox()/sapprox2() functions.

To create a common model, use the ”New Object” ( ) button in the toolbar of
the data manager and select Common Model. The block/model definition has to
be selected first. Similar to the composite frame, this definition is either stored in
the global or in the local library.

The common model then displays the list of available parameters and arrays
from the block diagram, as shown in Fig. 20.10. All parameters are listed on the
first page of the common model, and their values be specified there.
If the selected block definition uses one or more arrays in its definition, then
these arrays are displayed on the second page (for simple characteristics) and
third page (for two-dimensional characteristics) of the ElmDsl object. In Fig.

Stability Analysis and Simulation of Transients 20-391

DIgSILENT PowerFactory Models for Stability Analysis

Figure 20.10: Common model with Parameter List

20.11 an example example is shown for a simple 2x2 array definition.

Figure 20.11: Common model with Array List

The characteristics are defined as follows:

Characteristic In row ‘Size’ insert the number of rows in the first cell, the
number of columns is automatically set to 2 and can’t be inserted. If the
number of rows is changed, jump to the previous page and back again
to update the characteristic.

Two-Dimensional Characteristic In row ‘Size’ insert the number of rows in the

first cell and the number of columns in the second cell. If the a number is
changed, jump to the previous page and back again to update
this characteristic.

Stability Analysis and Simulation of Transients 20-392

DIgSILENT PowerFactory Models for Stability Analysis

20.5 The Composite Block Definition

A composite block diagram of the model definition is a graphical representation

of a mathematical transfer function, which produces one or more output signals
as function of one or more input signals. A block diagram may also have limits
(minimal and maximal values) as input signals.

A block diagram may thus be described as

(y0 , y1 , ...) = f unction(u0 , u1 , ...)

where y0 , y1 , ... stands for output signal 0, 1, ... and u0 , u1 , ... stands for input
signal 0, 1, .... All these signals are functions of time.

Block diagrams consist basically of the following elements:

Summation Points which produces the single output y = (u0 + u1 + ...)
Multipliers which produces the single output y = (u0 ∗ u1 ∗ ...)
Divisors which produces the single output y = (u0 /u1 /...)
Switches which produces the single output y = u0 or y = u1
Signal Lines which produces one or more outputs from one input:
y0 = y1 = ... = u
Block References which are used to include other block definitions.
Block references can be looked upon as macro’s that insert a low-level block
definition inside a composite block diagram definition. A block reference may
either point to another composite block definition or to a primitive block definition.

The PowerFactory program is shipped with a large set of primitive block

diagrams for most common controller elements like PID-controllers, Dead
Bands, Valve Characteristics, etc. and can be found in
DATA B ASE\L IBRARY\M ODELS\G LOBAL M ACROS. These predefined DSL
primitives may be copied and altered to specific needs.

A block reference is created by using the button in the graphics toolbox.

This creates an empty square which can then refer to any existing block
definition in the library.

N OTE : The composite frame and the model definition are very similar and the
usage is nearly identical. When creating one or the other PowerFac-
tory recognises the class, when you place the first slot or block. If you
place a block ( ) first, the button for the slot will become in-
active, so you can’t mix up slots and block sin one diagram. See also
section 20.6

Stability Analysis and Simulation of Transients 20-393

DIgSILENT PowerFactory Models for Stability Analysis

If the block type is selected, PowerFactory inserts all available parameters of

the referred block. You may change the name of the parameter but make sure,
you do not change the order of the parameters. The order is important so the
right parameter is assigned to the parameters inside the block definition.

Signal lines are directed branches, connecting input and output signals. A single
output line may be branched off and connected to more than one input terminal.

After the block reference has been edited, the it will show the input, output and
limiting signal connection points of the referenced block definition as one or
more coloured dots on the left and right side respectively on the upper and lower
side of the box. Signal lines may then be connected to these points. It is allowed
to refer to the block definition more than once in the same block diagram. In that
way, it is possible to use a particular PID-controller, for instance, twice or more in
the same model definition.

An example of a simple block diagram, comprising a multiplier, a summation

point and a standard PI block, is shown in Fig. 20.12

Figure 20.12: Example of a simple block diagram

When rebuilding a diagram, by pressing the button, the DSL representation

of the block diagram is written to the output window. For the example block
diagram in Fig. 20.12, this results in

model o1 = ’MyBlock’(i1,i2;x1;Kp,Ti;yi)
s1 = ’\System\Library\Models\DSL\PI.BlkDef’(xe;x1;Kp,Ti;yi)
xe = i1*i2
o1 = s1+i2+i1

This simple example shows the whole meaning of the block diagram graphics: it
is a convenient way to define specific controllers, based on standard
components.

However, it would also be possible to define exactly the same block diagram by
entering the above DSL script manually and so create a primitive block definition.

Stability Analysis and Simulation of Transients 20-394

DIgSILENT PowerFactory Models for Stability Analysis

20.6 Drawing Composite Block Diagrams and

Composite Frames

Although the composite block diagram and the composite frame diagram should
be distinguished from each other, they are drawn in about the same way.

The basic distinction between a block diagram and a frame diagram is that the
latter contains only slots and signals, whilst the block diagram must not contain
any slots.

A new block or frame diagram can be created in various ways:

• by the main menu entry File →New or S TRG -N and then selecting the
option Block/Frame Diagram from the ”New” command dialogue
(ComNew).

• by the button ”Insert new Graphic” on the toolbar of an opened

graphic, and selecting the option Block/Frame Diagram.

• by right-clicking a or inside a (library) folder in the active project in the data

manager and selecting New... →Block/Frame - Diagram from the context
menu.

• by using the ”New Object” button in the database manager and

selecting Block Definition (BlkDef).

N OTE : The two later options only create a block definition object (BlkDef), but
no graphic. This method is therefore not suited to create a composite
block or frame diagram, but only for creating primitive block definitions
by entering the DSL code.

In the first two methods, a graphic will be created and will appear in the opened
graphics board. A new graphics board will be created when no graphics board is
open. The new block/frame diagram graphic will show a single rectangular block,
which visualises the block or frame. The name of the new diagram will appear on
top of the frame.

Inside this rectangle the following objects can be placed from the graphic toolbox
for the block diagram:

node objects :

• block references
• summation points
• multipliers

Stability Analysis and Simulation of Transients 20-395

DIgSILENT PowerFactory Models for Stability Analysis

• divisors
• switches
• different kinds of graphical objects

branch object :

• signals lines

Inside a frame diagram only the following elements are allowed:

node objects :

• slots
• different kinds of graphical objects

branch object :

• signals lines

These objects can be selected from the Drawing Tool Box. The toolbox also has
buttons for pure graphical add-on objects (lines, polygons, rectangles, texts, etc.)
as shown in Fig. 20.13.

Figure 20.13: Block/frame diagram objects

N OTE : When creating a frame or a bock definition, PowerFactory recognises

the type of definition, when you place the first slot or block. Because
a composite frame diagram may only contain slots and signal lines,
creating a slot will disable all other node objects in the drawing toolbox.
If you place a block ( ) first, the button for the slot will become
inactive, so you can’t mix up slot and block elements in one diagram.

20.6.1 Adding a Block Reference

Drawing the block objects and connecting them with signals is done in very
much the same way as in the single line graphics. A block reference is first

Stability Analysis and Simulation of Transients 20-396

DIgSILENT PowerFactory Models for Stability Analysis

displayed as an empty square which has to be edited in order to assign a (low

level) block diagram to it.

Because of lack of information about the number of inputs and outputs of the
new block reference before a (lower level) block definition is assigned to it, it will
not be possible to connect signals to the empty block. It is therefore
recommended to first draw all block references and to assign block definitions to
them. Then the blocks references show all available input and output signal
connections.

A block reference is edited by right-clicking it and selecting Edit from the context
menu, or simply by double-clicking on it. The dialogue as displayed in Fig. 20.14
will pop up.

Figure 20.14: Edit Dialogue of the Block Reference

Use the Select button (see the cursor in Fig. 20.14) to select a model definition.
Predefined standard block diagrams for your usage are located in the folder
DATA B ASE\L IBRARY\M ODELS.

20.6.2 Adding Calculation Blocks

Summation Point
Every dot can be used as an input to the summation point. The sign of signals at
summation points can be changed by editing the summation point object. The
”edit” dialogue will pop up, where any connected input connection can be
inverted. Mind that not all dots have to be used and only one dot can be defined
as an output.

Stability Analysis and Simulation of Transients 20-397

DIgSILENT PowerFactory Models for Stability Analysis

Multiplier
Every grey dot of this block can be used as input or output of the multiplier. An
output of three input signals will thus be out = (in0 ∗ in1 ∗ in2 ). Mind that not all
dots have to be used and only one dot can be defined as an output.

Divisor
Every grey dot of this block can be used as input or output for the divisor. The
first input will be the numerator and thus be divided by the second (and if existing
the third) input. The order of the signals will be clockwise beginning on the left.
An output of three input signals will then be out = (in0 /in1 /in2 ). Mind that not all
dots have to be used and only one dot can be defined as an output.

Switch
Two input signals can be applied to this block, which will be connected to the
output according to the position of the switch. Additionally a control signal has to
be connected to the top, which will define the operation of the switch. If the
control signal is zero or negative, the switch will stay in the displayed state,
whereas a positive signal will cause the switch to change to the upper signal and
the other way round. In the edit dialogue you can alter the zero position of the
switch.

20.6.3 Connecting Signals

After drawing and defining the block references or slots, or other node elements,
they can be connected with signal lines. After selecting the button from the
graphical toolbox, a signal line is drawn by first clicking on a ’from’ node (output
of a block/slot), optionally clicking on the drawing surface to make a non-straight
connection, and finally clicking on a ’to’ node (input to a block/slot). The input
and output terminals of common blocks and other node elements are depicted
with coloured dots (see Fig. 20.15).

Figure 20.15: Block signal connections

Green: Input

Red: Output

Blue: Min. Limitation

Pink: Max. Limitation

Stability Analysis and Simulation of Transients 20-398

DIgSILENT PowerFactory Models for Stability Analysis

Gray: Every Signal can be connected

The signals lines can also be edited in the corresponding dialogue, which gives
the possibility to change the name of the signal.

Multi-Signal Connections
Signals normally connect a single output parameter with a single input
parameter. Especially in the case of three phase signals, such as is often the
case of voltage or current signals, multi-signal connections may be used.

A multi signal is defined by writing two or more signal names together, separated
by semicolons, e.g “I A;I B;I C”. In Fig. 20.16, the multi signal output and input of
two block definitions are shown. Both blocks will show a single input or output
connection point. They can be connected to each other by a single signal line,
as is shown in Fig. 20.17.

Figure 20.16: Inputs and outputs of two block definitions

Figure 20.17: Multi signal connection

N OTE : The number of variables and their order in the output signal must equal
the number of signals in the input signal.

Block Diagram Input and Output Definitions

The composite block diagram normally has input, output and limiting signals of
its own. Input signal points are defined by starting a new signal line on the left,
top or bottom side of the frame enclosing block diagram. This will create a new
input signal for the composite block definition.

Stability Analysis and Simulation of Transients 20-399

DIgSILENT PowerFactory Models for Stability Analysis

New output signals are defined by ending a signal line by clicking on the right
side of the enclosing rectangle frame.

Signals, which are thus connected to the rectangular frame, have the following
meaning:

• connected to the left side: Input

• connected to the right side: Output

• connected to the bottom side: Minimum Limitation

• connected to the top side: Maximum Limitation

N OTE : The names of the input and output signals must equal the names of the
input and output signals defined in the slot/block, you intend to assign
the definition.

20.6.4 Resize
If a marked symbol has small black squares at its corners, it can be resized by
left clicking one of the squares. The cursor will change to a double diagonal
arrow and moving it (while holding down the left mouse button) resizes the
object. Release the mouse when the new size is correct.

Figure 20.18: Resizing an object

It is also possible to pull the object(s) to a new size by clicking at one side of the
marking box. The marked object(s) will only resize in one direction in that case.
This is not possible for all objects. Some objects may only be resized with a fixed
X/Y- ratio, some other objects cannot be resized at all.

20.6.5 Additional Equations

After the internal structure of the block diagram has been defined graphically, the
block diagram itself can be edited. This can be done without having to close the
graphical representation of the block diagram. By left or double clicking the
enclosing rectangular frame, the block diagram edit dialogue will pop up. This

Stability Analysis and Simulation of Transients 20-400

DIgSILENT PowerFactory Models for Stability Analysis

dialogue will show all input, output and internal signals as have been defined
graphically.

On the second page of the dialogue, which can be accessed by pressing the
button, information and equations for the initialisation of the block can/has to be
entered. Also the name and the unit of the parameters to be defined in the
common model can be specified (see also chapter 21).

Additional DSL equations can be defined at the second page of the block
diagram edit dialogue.

Stability Analysis and Simulation of Transients 20-401

DIgSILENT PowerFactory User Defined (DSL) Models

Chapter 21

User Defined (DSL) Models

System modeling for stability analysis purposes is one of the most critical issues
in the field of power system analysis. Depending on the implemented model
accuracy, large signal validity, available system parameters and applied faults or
tests, nearly any result could be produced and arguments could be found for
their justification.

A simple example may illustrate this fact. In a 10 GW power system the

expected steady-state frequency deviation when losing a fully loaded 2000 MW
unit depends highly on the frequency dependency Kf of loads. Assuming a total
system droop of 7% and Kf to be 0, the steady-state frequency deviation will be
700 mHz approximately.
Now, with a more realistic coefficient of Kf = 5 %/Hz, the steady-state frequency
deviation is expected to be 596 mHz only. On the other hand, the frequency
dependency might be slightly higher or lower, but the nonlinear characteristics of
hydro turbine efficiencies and steam valve nonlinearities could be more relevant
at a certain unit loading point. Consequently, as long as only one or two different
loading scenarios are considered, average values with reasonable simple
models may give acceptable results by tuning only some key parameters like the
frequency dependency of loads or droop settings.

Thus system model structures and parameter settings are to be best evaluated
against the following main criteria:

System size: Big systems and small system have different “key parameters”.
Referring to the above example, for a smaller power system the frequency
dependency of loads is not relevant at all, whilst in big systems like UCTE
or UPS/IPS, frequency dependency may cover the spinning reserve
requirements totally.

Unit size: Steady-state and transient behaviour of big units are more decisive
for the overall system response than smaller ones which might practically
not affect the total system.

System structure: Independent of system and unit size, the system structure
may be more relevant than any other factor. This can easily be
demonstrated when weak systems with a longitudinal geographical
extension or appropriate substructures are analysed.

Stability Analysis and Simulation of Transients 21-402

DIgSILENT PowerFactory User Defined (DSL) Models

System fault: Most relevant to system modeling considerations are the applied
faults and related problems which are to be analysed. The analysis of
system damping and PSS tuning will not necessarily require the boiler
dynamics to be considered. On the other side, load shedding optimisation
and frequency restoration would not give appropriate results if mid and
long-term characteristics of relevant system elements are neglected.
Study purpose: In general, for systems which are in a planning stage, typical
models and parameters could be applied as long as there is no specific
additional information available. However, a more and detailed
representation is necessary for system extensions, where a detailed model
representation should form part of the performance specification. Special
attention has to be paid to the analysis of operational problems and the
operation optimisation. For these cases, a detailed modeling of the
relevant components is indispensable.

As soon as a detailed analysis and representation of system models is required,

the immediately arising questions are:
• How can the structures and parameters of the model be determined ?
• Are IEEE models and additional manufacturers block diagrams adequate
and accurate?
• How could the available information be used within the power system
analysis software?

The approach which is presented here and successfully applied in various

projects can be called the “Advanced System Modeling Approach (ASMA)”.
Typical applications are
• the analysis of controller problems and relevant malfunctions, especially
under disturbance conditions
• optimisation of control parameter settings
• modeling of unconventional system structures and control concepts often
found in industrial systems
• study applications for the design and specification phase of components
and systems (e.g. power system stabiliser, generator and HVDC
controllers).

For the ASMA approach, the following steps are of crucial importance:
Setup of system models: Based on the fundamental equations of engineering
and physics, the basic algebraic and differential equations are to be set up
within the required degree of accuracy. In addition, all parameters like time
constants and gains which could be also derived from these basics, are
likewise to be calculated.

Stability Analysis and Simulation of Transients 21-403

DIgSILENT PowerFactory User Defined (DSL) Models

Performance of system tests: In order to define all other parameters and

especially nonlinear characteristics, system performance tests are the best
method. In the majority of cases, frequency response tests will not permit
the determination of any nonlinear structure and its parameters. Special
test procedures, which do not interfere with normal operation, have to be
applied to focus on the steady-state characteristics, gains and time
constants. These measurements are preferably executed with a highly
accurate digital transient performance measurement system.

System Identification: Nonlinear, multi-input and multi-output identification

techniques are applied for system identification procedures. Typically, the
mismatch between measured and identified curves should be smaller than
2%.

Comparison of measurements and simulations: Besides the analysis of

subsystems and components, overall system performance is to be
compared with the theoretical model for all relevant operating modes.

Of course, very strict application of the ASMA approach is not necessary for
modeling relays and the less complex or digital control functions, as these are
clearly defined by their appropriate general and acceptance test documentation.
But independently of the analysed system, where the system representation
cannot be matched to a classical IEEE or any other standard model, there is a
substantial need for an easy to use and flexible method for the realisation of
individual models.

21.1 Modeling and Simulation Tools

As already indicated, the most critical and decisive factor for reliable simulation
results is the accuracy and completeness of system model representation for
identification and simulation purposes. Methods for solving this task range from
the classical and traditional way of using software which allows interfacing of
user-defined models at the FORTRAN/C level - typically via connection lists - to
the block-oriented approach which is based on the provision of predefined low
level block macros being connected at the case definition level.

In addition, most modern commercially available general purpose simulation

tools may be used for flexible and specific system representation. Unfortunately,
this approach does not cover adequately the special electrical system load-flow
characteristics.

In order to provide a very flexible modeling and simulation tool, which forms part
of a stability program, a control system based simulation language was

Stability Analysis and Simulation of Transients 21-404

DIgSILENT PowerFactory User Defined (DSL) Models

developed. The following main features of the DIgSILENT Simulation

Language (DSL) have been to be relevant:

• The simulation tool falls into the category of a Continuous System

Simulation Languages (CSSL)

• DSL includes a complete mathematical description of (time-) continuous

linear and nonlinear systems.

• The simulation tool is based upon common control and logic diagrams
leading to a non-procedural language as the sequence of elements could
be chosen arbitrarily. In other words, a DSL model can be converted into a
graphical representation.

• Provision of a flexible definition of macros, which could be: algebraic

equations, basic control elements like PID, PTn or even complete physical
subsystems like valve groups or excitation systems.

• Provision of various intrinsic functions like: “select”, “lim”, “limits”, “lapprox”,

“picdrop” in order to provide a complete control of models.

• Provision of various formal procedures for error detection and testing

purposes like: algebraic loop detection, reporting of unused and undefined
variables and missing initial conditions.

21.2 DSL Implementation: an Introduction

The ”DIgSILENT Simulation Language” is used to define new dynamic

controllers which receive input signals from the simulated power system and
which react by changing some other signals.

DSL itself can be looked upon as an add-on to the transient analysis functionality
of PowerFactory. During the simulation, the model equations of the DSL
models are combined with those describing the dynamic behaviour of the power
system components. These equations are then evaluated together, leading to an
integrated transient simulation of the combination of the power system and its
controllers.

The DSL main interfacing functions are:

Signal input and output channels: Any variable defined within the kernel
(actually more than 2500) and in a DSL model, can be accessed in a
read-and-write mode. Main and sub-address features are implemented
allowing the access of any signal existing in the system or to build up

Stability Analysis and Simulation of Transients 21-405

DIgSILENT PowerFactory User Defined (DSL) Models

variable addresses
program internal signals and parameters element:variable

Interrupt signals;
approx. 3000 FAULT (expression, command)
predefined signals
Output signals; DSL
(voltages, currents, OUTPUT(expression, command) Model 1
impedances, parameters,
switches, log variables. . .)

DSL control line

interrupt handling
Interrupt signals
DSL
numerical integration Output signals
Model 2
output processing

Automatic generation
Interrupt signals
of Jacobian elements
DSL
and system sub-matrices Output signals
Model n

Figure 21.1: Structure of the PowerFactory DSL system

complex structures like hardware-based modules taking equipment “rack”

and “function card” structures into account.
Events: Conditions evaluated by DSL models may cause events to be sent to
the program kernel where they will be scheduled within the event queue.
Output and Monitoring: Conditions may trigger user-defined messages to be
displayed in the output window.

The structure of a DSL model is best explained by example. The used example
is that of a prime mover unit model of a simple hydro turbine. This DSL model
has been defined graphically, and contains one embedded DSL macro. That
embedded macro models a single integrator and is defined by programming it.

This is the basic method for designing new DSL models:

1. A set of basic DSL models is created. These models implement simple,
’primitive’ controllers like a ’first order time lag’ or a ’PID’ controller.
PowerFactory program shipped with a large number of these primitive
controller models. New primitives are created by programming their
differential equations and signal settings, using the DSL language.
2. The more complex controller is created graphically by drawing its block
diagram. Such a block diagram normally uses references to other DSL

Stability Analysis and Simulation of Transients 21-406

DIgSILENT PowerFactory User Defined (DSL) Models

models which are thus combined into a more complex controller. Controller
references may be used to include DSL primitive models into the complex
model, but may also refer to other graphically defined complex models.
Highly complex controllers may thus be designed in a hierarchical way, by
designing sub-models and sub-sub-models, where the DSL primitives form
the lowest level (in sections 20.4 to 20.6 these procedures are described in
detail).

A t i2 P t
i1 x e 1 p t_ x
i3 - s T -
C i4

Figure 21.2: Diagram of a simple model of a hydro turbine

In Fig. 21.2, the model definition that was used to define the hydro turbine model
is depicted. The resulting DSL code, as shown in the output window when a
“graphics rebuild” is performed is:

1. model Pt = ’pmu_hydro’(At,C;x1;Ti;)
2. pt_x = ’I.BlkDef’(xe;x1;Ti;)
3. i3 = i1/i2
4. i1 = At*At
5. i2 = pt_x*pt_x
6. i4 = xe*pt_x
7. xe = i3-C
8. Pt = pt_x-i4

The line numbers have been added for convenience. The corresponding block
definition shows:

Output Signals : Pt
Input Signals : At, C
State Variables : x1
Parameter : Ti
Internal Variables :

The example describes a simple hydro turbine model with the input signals At
and C and the output signal Pt .

Stability Analysis and Simulation of Transients 21-407

DIgSILENT PowerFactory User Defined (DSL) Models

Figure 21.3: Graphical representation of a DSL model of an integrator

In Fig. 21.3, the graphical representation of the embedded primitive DSL model
is depicted. This primitive model is included in the hydro turbine (in line 2 of the
hydro’s definition). The DSL primitive implements a single integrator and is
programmed by:
1. model y = ’I’(xe;x1;Ti;)
2. [Ti] = ’s’
3. limits(Ti) = (0,)
4. inc(x1) = y
5. inc(xe) = 0
6. x1. = xe/Ti
7. y = x1
Line 1 is generated by pushing the E QUATIONS button in the block diagram
dialogue. Line 2..7 were entered manually.

The block definition dialogue was used to set

Output Signals : y
Input Signals : xe
State Variables : x1
Parameter : Ti
Internal Variables :

21.2.1 Parts of a DSL Model

Both example DSL models show the two basic parts of any DSL model, primitive
or complex:
1. The interface definitions
2. The DSL model description

Interface description
The interface defines the model name, names of input and output signals, model
parameters and state variables. These are shown in the output window in the
model heading.

Stability Analysis and Simulation of Transients 21-408

DIgSILENT PowerFactory User Defined (DSL) Models

Example (line 1 from the hydro turbine model):

1. model Pt = ’pmu_hydro’(At,C;x1;Ti;)

The block diagram dialogue further allows for the definition of limiting parameters
and input signals, and the classification of the model as a linear model and/or as
a DSL macro.

Model description
The model description describes the DSL model, based on the signals defined in
the interface. The DSL description includes

• Parameter descriptions: name and unit

• Allowed parameter ranges

• Initial conditions and functions which are used to calculate initial values.

• The algebraic relations which define the controller.

Example (the integrator):

2. [Ti] = ’s’ ! the unit of Ti is seconds
3. limits(Ti) = (0,) ! Ti > 0
4. inc(x1) = y ! initially x1=y
5. inc(xe) = 0 ! initially xe=0
6. x1. = xe/Ti ! equation 1: δx1 / δt = xe/Ti
7. y = x1 ! equation 2: y=x1

21.2.2 Advanced Features

The numerical integration of DSL models, interrupt scheduling and input-output
signal processing is handled automatically by the program kernel. In addition, if
the output of a DSL model is an electric current being added to the appropriate
total bus current - which is the case if a load or generator model is created - all
Jacobean elements necessary for the iterative simulation procedure will be
calculated automatically.

Another useful feature of the DSL is the implemented algorithm for numerical
setup of the system matrix for eigenvalue calculation purposes. Consequently,
any model implemented at the DSL level will automatically be taken into
consideration when calculating the system eigenvalues or when applying the
modal network reduction approach (MRT). Of course, any signal limiting
functions will be disabled automatically for this calculation procedure.

In addition, inputs and outputs of model parameters, its organisation via

windows menus etc. is also derived automatically from the DSL model.

Stability Analysis and Simulation of Transients 21-409

DIgSILENT PowerFactory User Defined (DSL) Models

21.3 Defining DSL Models

A new DSL model is created either by entering the DSL code in the equation
part of a “Block Definition” (BlkDef) object, or by creating a new Graphical Block
Diagram (see also section 20.6 on how to create a new block definition). Both
methods will result in a Block Definition Object which holds the definition of the
DSL model.

The block definition objects thus serve two purposes in the process of
constructing a DSL model:

• They hold the definitions and parts of a graphically constructed composite

block definition, and the diagram graphic which was used to define the
model.

• They provide the surrounding in which a new “DSL primitive” or ’primitive

block definition’ can be defined.

21.3.1 Composite Block Definitions

To create a new composite block definition

• use the main menu entry File →New or S TRG -N and then select the option
Block/Frame Diagram from the ”New” command dialogue (ComNew).

• use the button ”Insert new Graphic” on the toolbar of an opened

graphic, and select the option Block/Frame Diagram.

To access the dialogue of the block definition (BlkDef), double-click on the frame
box surrounding the diagram.

Complex Block Definition objects may be compared with the “Grid Folders” in the
PowerFactory database tree. They are defined by graphically defining a
controller block diagram of which they will store the graphical information and all
logic parts. These parts include signals, small standard components (adders,
multipliers, etc.) or DSL primitives.

Although a complex Block Definition object is created graphically, it allows for

additional DSL equations to define those aspects of the controller that would be
difficult to enter in a graphical way.

The graphical environment in which a complex Block Diagram is constructed, is

not treated here. Please refer to section 20.6 for more information.

Stability Analysis and Simulation of Transients 21-410

DIgSILENT PowerFactory User Defined (DSL) Models

21.3.2 Primitive Block Definitions

To create a primitive DSL block definition

• right-click a or inside a (library) folder in the active project in the data

manager and selecting New... →Block/Frame - Diagram from the context
menu.

• use the ”New Object” button in the database manager and selecting
Block Definition (BlkDef).

• double-click an new/empty block reference in an open block diagram and

then use the button to select a block definition. Then you can use the
button to create a new block definition inside the local library.

DSL primitives are the building blocks from which the more complex controller
diagrams are composed. A DSL primitive, for example, might implement a Low
Pass filter, which may then be used to graphically construct more complex
controllers which include such a filter.

Unlike transformers or other power system components, which may be looked

upon as ’power system primitives’, a DSL primitive is only referred to by a
complex block diagram and may thus be used in more than one complex DSL
model at the same time.

21.3.3 Block Definition Dialogue

When creating a primitive DSL model or by double-clicking on the frame of a
composite block definition, a dialogue will appear, where input and output
variables, parameters, state variables and limiting signals can be defined.
Furthermore additional equations, initial conditions of variables as well as names
and units of parameters can be inserted.

Fig. 21.4 shows an example dialogue of a PI controller including limiting

parameters and a ’switch’ signal:

• The name and title will appear in the library folder, where the model is
stored.

• The level of the model representation is only important when using or

changing old models. For new created models “Level 3” should be used
always.

• “Automatic Calculation of Initial Conditions”: PowerFactory can calculate

the initial conditions automatically. However if there is no sequence found
(because of e.g. dead lock situations) there will be an error message.

• “Classification”:

Stability Analysis and Simulation of Transients 21-411

DIgSILENT PowerFactory User Defined (DSL) Models

Figure 21.4: Dialogue of the Block Definition

Linear This option will only effect the graphical representation of the block
in the diagram. If this option is enabled, the block will be represented
as a linear block, otherwise as a not-linear block with two lines.
Macro This option is used to identify the block definition as a macro inside
the library.
Matlab Enabling the ‘Matlab’ tag will show am input dialogue, where you
can define a Matlab (*.m) file with which the block definition can
communicate during a simulation. For more information about the
Matlab interface see also chapter ??.

• You my define constant limiting parameters, which are defined in the

dialogue of the Common Model, as well as limiting signals, which are
similar to input signals. The difference is the graphical representation in the
block diagram.

• Input and output signals have to be defined for the internal use inside the
block definition. The number and their name will then appear in the

Stability Analysis and Simulation of Transients 21-412

DIgSILENT PowerFactory User Defined (DSL) Models

graphical diagram when the block is used.

• State variables are needed when not only linear but also differential
equations are used. Then for every first-order derivative one state variable
has to be specified.
• The parameters will appear in the dialogue of the common model and can
then be specified. The parameter defined in here the block definition will
automatically be inserted in the block reference. The names of the
parameters can be different in the block reference and in the block
definition. Only the order has to be identical.
• Internal variables are only used inside the block definition but can not be
set from outside.

There are several buttons on the right side of the dialogue:

C ONTENTS This button will display the (possible) contents of the block
definition. This can be the graphically inserted objects, further block
references or the packed macros. Additionally this may be e.g. internally
defined events.
E QUATIONS The ”Equations” button will print the DSL equations to the output
window, independently if they are defined graphically or on the ”Additional
Equations” page, as well as variable definitions.
M ACRO E QUAT. This button prints the DSL equations of the current block
definition including the equations in the used macros to the output window.
C HECK ”Check” will verify the model equations and output error messages, if
fault have occurred. Otherwise the following message will occur:

DIgSI/info - Check ’\Holger.IntUser\Windparks.IntPrj\Library

\Block Definitions\DFIG\Voltage Control.BlkDef’:
DIgSI/info - Block is ok.

C HECK I NC . The initial conditions of the block definition will be printed and
checked.
PACK Pack will copy all used DSL models (macros) of a composite model
definition to the folder ”Used Macros” inside the block definition. In this way
there will be now references to other projects or libraries outside the model.
Beware: Any further changes in the macro library has no influence, the
macros are copied and no longer linked to the library. So if there is an error
in a certain macro it has to be fixed separately in each packed block.
PACK -> M ACRO This command will reduce the whole model including DSL
blocks and additional equations and macros into one DSL model
containing only equations. All graphical information will be lost. This
command is irreversible.

Stability Analysis and Simulation of Transients 21-413

DIgSILENT PowerFactory User Defined (DSL) Models

E NCRYPT The ”Encrypt” button is available when PACK -> M ACRO is

activated before. This command encrypts all equations inside the model,
so the equations can not be seen or outputted anymore. In this way a
model containing sensitive or restricted device equations can be delivered
without showing the internal equations. This command is irreversible and a
decrypt function is not available.

By clicking on the button the second page of the dialogue can be accessed.
Here the (additional) equations of the DSL model can be defined. Also further
information e.g. the initial conditions of state variables and the name and unit of
parameters can be specified.

Fig. 21.5 shows the additional equations of the DSL model of the PI controller.

Figure 21.5: dialogue of the Block Definition - Page 2

The next section will show the handling and usage of the DSL language in detail.

21.4 The DIgSILENT Simulation Language (DSL)

The DSL language is used to program models for the electrical controllers and
other components used in electrical power systems. As for any other simulation
or programming language, a special syntax is provided for the model formulation.

This syntax is explained in the following order:

a. Terms and Abbreviations
b. General DSL syntax
c. DSL Variables
d. DSL Structure
e. DSL syntax (definition and equation code)
f. Intrinsics

Stability Analysis and Simulation of Transients 21-414

DIgSILENT PowerFactory User Defined (DSL) Models

21.4.1 Terms and Abbreviations

The following terms and abbreviations are used to describe the DSL syntax:

expr = arithmetic expression, not to be terminated with a ’;’

• arithmetic operators: +, -, *, /
• constants: all numbers are treated as real numbers
• standard functions: sin(x), cos(x), tan(x), asin(x), acos(x), atan(x),
sinh(x), cosh(x), tanh(x), exp(x), ln(x), log(x) (basis 10), sqrt(x)
(square root), sqr(x) (power of 2), pow(x,y), abs(x), min(x,y), max(x,y),
modulo(x,y), trunc(x), frac(x), round(x), ceil(x), floor(x).
These standard functions are described in detail in the last chapter.
• Parenthesis: (arithmetic expression)

All trigonometric functions are based on radians (RAD).

example: A = x1+2.45*T1/sin(3.14*y)

boolexpr = logical expression, not to be terminated with a ’;’

• Logical relations: <, >, <> (inequality), >=, <=, =.

• Unary operators: .not.
• Binary operators: .and. .or. .nand. .nor. .eor.
• Parentheses: {logical expression}

example: A = {x1 > 0.and..not.x2 ≤ 0.7}.or.T1=0.0

string = anything within ”.

example: A = ’this is a string’

21.4.2 General DSL Syntax

Line length: The maximal line length is 80 characters. Longer lines have to be
broken by using the ’&’ sign in the first column. A ’&’ sign at the first column
joins the row and the preceding row.

Example:

y = lapprox(x, 1.674, 7.367, 2.485, 12.479, 5.457, 18.578

& 6.783, 15.54, 8.453, 12.589, 9,569, 6.478)

Line breaking cannot be used within names or strings.

Case sensitivity: All keywords, names, functions, variables, models, macros,

etc. are case sensitive.

Stability Analysis and Simulation of Transients 21-415

DIgSILENT PowerFactory User Defined (DSL) Models

Blanks: All blanks are removed when the DSL code is processed. Exception:
blanks in strings are kept.

Comments: The ’!’ sign causes the remaining line to be interpreted as a

comment. Comments are removed when the DSL code is processed.

Example:

! comments may start at the beginning of a line

x1. = select(at<>0, ! comments may be used in broken lines
& (1-sqr(x1)/sqr(at))/Tw, 0)

21.4.3 DSL Variables

A DSL model may use 5 types of variables:
Output signals Output signal variables are available as input signals to more
complex DSL models.

Input signals Input variables may origin from other DSL models or from a
power system elements. In the latter case, currents and voltages, as well
as any other signal available in the analysed power system, become
available to the DSL model.

State variables State variables are time dependent signals generated and used
within the DSL model itself.

Parameters Parameters are ’read only’ numbers which are set to alter the
behaviour of the DSL model.

Internal variables Internal variables are defined and used in the DSL model to
ease the construction of a DSL set of equations.

N OTE :
• A state variable may not be at the same time an output variable; if
required, the use of an assignment like y = x1 is recommended.

• All parameters are real numbers.

• A special parameter ’array iiii’ (with up to 4 digits i), with 2*iiii el-
ements is provided to define characteristics (see procedure “lap-
prox”).

• Only the derivatives of state variables can be assigned an ex-

pression.

Stability Analysis and Simulation of Transients 21-416

DIgSILENT PowerFactory User Defined (DSL) Models

21.4.4 DSL Structure

DSL models are built up of three parts:

• The interface part, which states the model name, title, classification and
variable set. This part is set in first page of the block diagram edit dialogue
(see also the previous section).

• Definition code

• Equation code

The definition and equation code form the actual controller network definition
and are treated in the next chapters.

21.4.5 Definition Code

A Definition code in the equation part of a DSL model is used to define
parameter properties and initial conditions.

Unit and Parameter Description

vardef(varnm) = unitstring;namestring Unit and name for variable varnm.
examples:
vardef(Ton) = ’s’;’Pick up time for restart’ ! defines unit and
name
vardef(Ton) = ;’Pick up time for restart’ ! only defines name
vardef(Ton) = ’s’; ! only defines unit

[varnm] = unitstring Unit for variable varnm, maximal 10 characters width.

example:
[Ton] = ’s’ ! defines unit
remark: a macro call causes error messages, if the units of the substituted
variables do not match the defined units.

Valid Value Ranges

limits(varnm) = [/( minimum value, maximum value ]/) Defines the valid
interval for variable varnm. Violations of the interval limits during simulation
will be reported:

limits(yt)=(,1] is equivalent to
output(yt>1,’Maximum exceeded: yt=yt>1’)
The ’(’ and ’)’ braces exclude the minimum or maximum value. The ’[’ and
’]’ braces include them from the interval.

Stability Analysis and Simulation of Transients 21-417

DIgSILENT PowerFactory User Defined (DSL) Models

Examples:
limits(x)=[min,max] ! min ≤ x ≤ max
limits(x)=(min,max] ! min < x ≤ max
limits(x)=(,max] ! x ≤ max
limits(x)=(min,) ! min < x

If required and possible, the program automatically determines the smallest

interval under several intervals of the same variable. E.g. limits(x)=(1,3) and
limits(x)=(2,4] results in 2 < x < 3.
Macro models often define limits for certain variables. The model which uses the
macro might also define limits for the variables which are used in the macro
calls. The ’smallest interval’ method gives the calling model thus the freedom to
redefine parameter limits without violating the internal macro limit definitions.

Initial Conditions

Direct Setting of Initial Conditions

inc(varnm) = expr Definition of the initial condition of variable varnm. If

inc(varnm) is not defined, the normal assignment expression will be
evaluated (only possible if varnm is of the intern or input type). If
inc(varnm) is defined, it will be evaluated when the model resets.

inc0(varnm) = expr Definition of the initial condition of variable varnm, for

unconnected output or input variables. This variant of the inc() statement is
used only when the variable varnm could not be initialised through the
initial condition of the connected input or output signal. The inc0()
statement is thus used to make open input or output terminals possible.

incfix(varnm) = expr This variant of the inc() statement is valid only in

connection with automatic initialization and is used to determine the initial
values in ambivalent situations. With the incfix, one or more variables can
be directly initialized so that other variables can be initialized automatically.

Example:
AVR model has two inputs, [upss, usetp], and one output, [uerrs]. Both
inputs cannot both be initialised automatically by the single output value,
which is determined by the connected machine. Therefore one of the
inputs must be initialised fix, e.g. by incfix(upss)=0. The initial value of
usetp is now automatically determined, using upss=0.

Iterative Setting of Initial Conditions

Stability Analysis and Simulation of Transients 21-418

DIgSILENT PowerFactory User Defined (DSL) Models

Three functions are available in order to determine initial values iteratively:

loopinc, intervalinc, newtoninc.

These functions are used to find the initial value for one set of parameters if the
initial values of another set of parameters, which are functions of the first set of
parameters, are known.

The iterative functions are used to find the (approximated) values for the
unknown parameters for which the known parameter take their initial value.

loopinc(varnm, min, max, step, eps) Performs a simple linear search for a
single value for which the parameter varnm is closest to its known initial
value

varnm = targetvariable, which initial value is known

min = lower limit, max = upper limit, step = stepsize, eps = maximum error

example: inc(a) = loopinc(b, -5, 5, 0.01, 0.001)

The initial value of variable a is searched by evaluating parameter b,
beginning at a = −5, ending at a = 5, with an increment of 0.01.

Return value: the value for a for which the deviation of b to its known initial
value takes the smallest value. A warning is given if the smallest deviation
is greater than eps.

Restriction: Can only be used as the right side of an inc()-statement

intervalinc(varnm, min, max, iter, eps) Performs an ’interval-division search’

for a single value for which the parameter varnm is closest to its known
initial value.

varnm = targetvariable, which initial value is known

min = lower limit, max = upper limit, iter = maximum number of iterations
eps = maximum error

example: inc(a) = intervalinc(b, -5, 5, 40, 0.001)

explanation: the initial value of the variable a is searched for, within the
interval [−5, 5] by successively dividing the interval as long as the deviation
of the variable b to its initial value is less than eps. The iteration stops if the
maximum number of iterations is reached, and a warning is given if the
smallest deviation is greater than eps.

restriction: may only be used as the right side of an inc()-statement

newtoninc(initexpr, start, iter, eps) Performs a newton iterative search for one
or more parameters by minimising the errors in a set of coupled equations.

initexpr = the expression which must equal the parameters whose initial

Stability Analysis and Simulation of Transients 21-419

DIgSILENT PowerFactory User Defined (DSL) Models

value is sought
start = the starting value for the parameter whose initial value is sought
iter = the maximum allowed number of iterations
eps = the maximum allowed absolute error between initexpr and the
parameter whose initial value is sought.

example:

qt0 = 0.5
eps = 0.000001
maxiter = 100

inc(hedr) = newtoninc(hw-sqr(qedr)*(Rds+Rdr), hw, maxiter, eps)

inc(qt1) = newtoninc(Pt1/(4*dh*eta1), qt0, maxiter, eps)
inc(qt2) = newtoninc(Pt2/(4*dh*eta2), qt0, maxiter, eps)
inc(qt3) = newtoninc(Pt3/(4*dh*eta3), qt0, maxiter, eps)
inc(qt4) = newtoninc(Pt4/(4*dh*eta4), qt0, maxiter, eps)

This example shows a part of the initial value definitions for a model where
the initial values of 5 parameters (hedr,qt1,..,qt4) are sought
simultaneously by setting up a system of coupled equations and solving
that system by newton iteration so that, eventually,

hedr ≈ hw − sqr(qedr) ∗ (Rds + Rdr)

qt1 ≈ P t1/(4 ∗ dh ∗ eta1)
qt2 ≈ P t2/(4 ∗ dh ∗ eta2)
qt3 ≈ P t3/(4 ∗ dh ∗ eta3)
qt4 ≈ P t4/(4 ∗ dh ∗ eta4)

Stability Analysis and Simulation of Transients 21-420

DIgSILENT PowerFactory User Defined (DSL) Models

N OTE :
• Add the initial conditions to the complex block not to each primi-
tive (like a first-order time lag).

• The general initialisation ’direction’ is from right to left, i.e. the

outputs are normally known and the inputs or setpoints have to
be determined.

• If initial conditions are not defined for a certain variable the simu-
lation equations are used instead. It should be therefore enough
to specify the initial conditions of the state variables and input
variables.

• The option Automatic Calculation of Initial Conditions needs

some configuration work, but does not require correct initial con-
ditions for each state/input variables. The initial values are only
used to initialise the iteration process. The incfix-function can be
used to determine the initial values in ambivalent situations.

• Use the option Verify Initial Conditions to check, if the initial con-
ditions lead to the correct result.

21.4.6 Equation code

Within the equation code, all equations necessary to build up the simulation
models are included. The set of equations defines a set of coupled differential
equations which describes the transfer functions between the input and the
output signals. These transfer functions may range from simple linear,
single-input single-output functions, to highly complex nonlinear, non continuous
multi-input multi-output functions.

DSL is used to describe direct relations between signals and other variables.
Expressions may be assigned to a variable itself, or to the first derivative of a
state variable. Higher order differential equations have thus to be spit up into a
set of single order equations by the introduction of additional state variables.

21.4.7 Equation statement

The equation statements are used to assign expressions to parameters, thus
relating all parameters in a set of differential equations.

Syntax:

varnm = expr Assigns expression ’expr’ to variable ’varnm’.

Examples:

Stability Analysis and Simulation of Transients 21-421

DIgSILENT PowerFactory User Defined (DSL) Models

y = sin(a) + 3 ∗ x1
y = .not.x1 > 2.or.a <= 3

varnm. = expr Assigns expression expr to the first order derivative of the
variable varnm.
Examples:
x1. = (xe − x1)/T 1
x2. = x1

Remarks:

• DSL assignments may occur in any sequence. The sequence does not
influence the evaluation of the assignments.

• All variables are of type floating point, even if assigned to a boolean

expression, in which case the value will be 0.0000 or 1.0000;

• When a variable z is used in a logical expression (i.e. y=.not.z), the

logical 1 of z is tested by evaluating (z > 0.5):
y1 = .not.z is interpreted and equal to y1 = (z =< 0.5)

• There is no warning against mixing logical and non-discrete variables in

expressions.
Consequently:
y = .not. x1>2 .or. a<=3
z = 4.0*y + x1
will cause no message: depending on y, z will take the value x1 + 4.0 or
just x1.

• The assignment of a value to a variable is taking place in an order which

recognises the connections between these variables. In the case of:
1. a = b+5
2. b = x1
3. x1. = 1
The second line will be evaluated first, then line 1.

• Algebraic loops are not supported. In the following example, an error

message will be displayed:
a = b+5
b = 2*a

• If there is no assignment to a variable varnm, varnm will keep its initial

value.

• The right side expression may not contain derivatives. Derivatives may
only appear on the left side of the equation sign:
Correct is: x1. = asin(a)
Wrong is: a = sin(x1.)

Stability Analysis and Simulation of Transients 21-422

DIgSILENT PowerFactory User Defined (DSL) Models

DSL Macros
A DSL macro is a predefined DSL model, complex or primitive, which is primary
meant to be included in higher level DSL models. The block diagram edit
dialogue offers a ’Macro’ classification option which can be set to mark the
model as a macro.

A DSL macro is included in a higher level DSL model either by creating a block
reference in the block diagram graphics or by explicit inclusion in a DSL equation.

Syntax:

varnm1, varnm2,... = macroname (i1,i2,... ; s1,s2,... ; p1,p2,... ; i1,i2,...)

Assigns the output signals of the DSL macro macroname to the variables
varnm1, varnm2, ... Assigns the input signals of DSL macro to the
variables i1, i2, ... The macro uses the state variables s1, s2, ... the
parameters p1, p2, ... and the internal variables i1, i2, ...
Example:
P1,P2 = ’\User\I.BlkDef’(i1,i2;s1,s2;T1,T2)
This example assigns to P1 and P2 the output of DSL model
\U SER\I.B LK D EF.

Macro calls are not supported within expressions, even if they only have one
output variable:

correct example:
y = my\_macro(x1, s1, p1, i1)

incorrect:
y = 3 * my\_macro(x1, s1, p1, i1) + 4

should be replace by:

y1 = my\_macro(x1, s1, p1, i1)
y = 3 * y1 + 4

DSL Internal Macro Handling

A preparser substitutes each macro call with the equation code of the macro.
The variables of the macro DSL model are then replaced by the variables used
in the macro call. The local variable names of macros thus disappear after the
preparse process.
DSL Models
In general, there are two basic types of DSL models possible:

1. Models of electrical devices like generators, loads or HVDC systems.

These models are characterized by their principal output signal “complex
device current”, which is injected to the electrical grid at a certain busbar.

Stability Analysis and Simulation of Transients 21-423

DIgSILENT PowerFactory User Defined (DSL) Models

However, in addition to the electrical device currents, there may be any

other variable defined as an output signal. A summary of the available
variables can be seen in the corresponding Technical References of the
element.

2. Models with output signals which are not directly injected to the electrical
network (general devices). Among these types of models are prime mover
units, voltage controllers, relays, calculation procedures, etc.

Events and Messages

The DSL language provides procedures to generate an interrupt event or to
send a message to the output window:

• The procedure fault(boolexpr, event string) generates an event and is

evaluated at the beginning of each time step

• The procedure output(boolexpr, message string) outputs a message

and is evaluated at the end of each time step.

The ”fault” and ”output” procedures are evaluated at each time step during the
simulation of a model. The first time that boolexpr is found to be true, the string
will be processed and a message is send to the output window or an event is
added to the PowerFactory event queue. The ’”fault” or ”output” procedures will
be disabled thereafter, to prevent an avalanche of messages or events, until the
DSL model will be reset again.

Both procedures are explained in detail in the following paragraphs.

Output(boolexpr, message string)

The message string may contain variables and the special function
num(boolexpr) or num(expr):

• variable names which appear directly after an ’=’ sign will be substituted by
their actual values;
e.g.: output(yymax,’maximum exceeded: yt=yt > ymax=ymax’)
may generate the message: maximum exceeded: yt=1.2 > ymax=1.0

• the num(expr) or num(boolexpr) will be substituted with the calculated

value of the expression;
e.g.: value=num(a+b) may produce value=3.5000

Fault(boolexpr, event string)

Each DSL model has the capability to add events to the event list. A DSL model
of a distance relay, for instance, can open the power switch of a line by adding

Stability Analysis and Simulation of Transients 21-424

DIgSILENT PowerFactory User Defined (DSL) Models

the correct switch event. ’Adding an event’ is done by executing an existing event
object in the PowerFactory database.

Consequently, all events that may be used by the DSL model have to be created
together with the DSL model. They must all be stored inside the common model
(ElmDsl). These ’DSL events’ will thus form an integrated part of the DSL model.

N OTE : The events are accessed or created by opening the edit dialogue of
the common model (double-click on the DSL model in the Data
Manager), and then pressing the button E VENTS . You get now a list
of already defined events inside this model.
The events are not added to the global event list of the project unless
the event is ’activated’ by the DSL model.

The event string in the fault expression must refer to the name of one of these
events. At evaluation, the event will be thrown onto the event stack if boolexpr is
true. As soon as the simulation reaches the event, it will execute it.
Consequently, a delayed event may be thrown by the DSL model by setting the
execution time ahead of the current time.

The parameters of the event can be modified in the fault string by assigning a
new value. The mechanism is the same as described above in the output
procedure.

Example:

fault(u>1.1,’name=MySwitchEvent1 dtime=0.15’)

If the variable u exceeds 1.1 the event named ’MySwitchEvent1’ will be thrown
onto the event stack and its variable dtime (relative event time) will be set to 15
milliseconds. The event will thus be delayed for that amount of time, which, in
this case, mimics the time needed to open a switch. Which switch will open is
defined in the event object ’MySwitchEvent1’.

21.4.8 Example of a Complete DSL Model

Thermal Double Reheat Turbine with Steam Storage
Controller Model:

model pt,ptmw =
’pmu_1’(at,sgn,cosn,ngnum;x1,x2,x3,x4;Thp, Tip,Tlp,alflp,Tspi)
[T1] = ’s’
limits(T1) = [0,)
limits(alfhp) = [0,1]
vardef(alfhp) = ;’High pressure turbine ratio’;
limits(alflp) = [0,1-alfhp]

Stability Analysis and Simulation of Transients 21-425

DIgSILENT PowerFactory User Defined (DSL) Models

vardef(alflp) = ;’Low pressure turbine ratio’;

vardef(Tspi) = ’s’;’Boiler capacity time constant’;
limits(Tspi) = (0,)
vardef(Thp) = ’s’;’High pressure turbine time constant’;
vardef(Tip) = ’s’;’First reheater time constant’;
vardef(Tlp) = ’s’;’Second reheater time constant’;

inc(x1) = y/K
inc(xe) = y/K
inc(x4) = 1.0
inc(at) = pt
inc(steamflow0) = pt
inc(ylp) = pt

x1. = select(T1>0,(xe-x1)/T1,0)
y = K*select(T1>0,x1,xe) ! if T1=0 => y=xe
steamflow = at*x4
x4. = (steamflow0 - steamflow)/Tspi ! boiler
yhp = PT1(steamflow;x1;Thp) ! high pressure part
yip = PT1(yhp;x2;Tip) ! medium pressure part
ylp = PT1(yip;x3;Tlp) ! low pressure part
pt = yhp*alfhp + ylp*alflp+ yip*(1.0-alfhp-alflp)
ptmw = pt*sgn*cosn*ngnum ! only for output purposes

The used macro ’PT1’ is defined as:

model y = ’PT1’(xe;x1;K,T1;)
x1. = select(T1>0,(xe-x1)/T1,0)
y = K*select(T1>0,x1,xe) ! if T1=0 => y=xe
inc(x1) = y/K
inc(xe) = y/K
[T1] = ’s’
limits(T1) = [0,)

Stability Analysis and Simulation of Transients 21-426

DIgSILENT PowerFactory User Defined (DSL) Models

21.5 DSL Functions

21.5.1 Standard DSL Functions

function description example
sin(x) sine sin(1.2)=0.93203
cos(x) cosine cos(1.2)=0.36236
tan(x) tangent tan(1.2)=2.57215
asin(x) arcsine asin(0.93203)=1.2
acos(x) arccosine acos(0.36236)=1.2
atan(x) arctangent atan(2.57215)=1.2
sinh(x) hyperbolic sine sinh(1.5708)=2.3013
cosh(x) hyperbolic cosine cosh(1.5708)=2.5092
tanh(x) hyperbolic tangent tanh(0.7616)=1.0000
exp(x) exponential value exp(1.0)=2.718281
ln(x) natural logarithm ln(2.718281)=1.0
log(x) log10 log(100)=2
sqrt(x) square root sqrt(9.5)=3.0822
sqr(x) power of 2 sqr(3.0822)=9.5 All
pow (x,y) power of y pow(2.5, 3.4)=22.5422
abs(x) absolute value abs(-2.34)=2.34
min(x,y) smaller value min(6.4, 1.5)=1.5
max(x,y) larger value max(6.4, 1.5)=6.4
modulo(x,y) remainder of x/y modulo(15.6, 3.4)=0.58823
trunc(x) integral part trunc(-4.58823)=-4.0000
frac(x) fractional part frac(-4.58823)=-0.58823
round(x) closest integer round(1.65)=2.000
ceil(x) smallest larger integer ceil(1.15)=2.000
floor(x) largest smaller integer floor(1.78)=1.000
time() current simulation time time()=0.1234
pi() 3.141592... pi()=3.141592...
twopi() 6.283185... twopi()=6.283185...
e() 2,718281... e()=2,718281...

trigonometric functions use RADIANS.

21.5.2 Special DSL Functions

lim
lim ( u, min, max)

Stability Analysis and Simulation of Transients 21-427

DIgSILENT PowerFactory User Defined (DSL) Models

Nonlinear limiter function:



min if u < min
returns max if u > max


u if min ≤ u ≤ max

limstate
limstate ( x1, min, max)
Nonlinear limiter function for creating limited integrators.
Example:

x1. = xe/Ti;
y = limstate(x1,min,max);
This was previously realized by using “select” and “lim” functions:
x1. &=& select({x1$>$=max.and.xe$>$0}
& .or.{x1$<$=min.and.xe$<$0}, 0, xe/Ti);
y &=& lim(x1,min,max);

delay
delay ( x, Tdelay)
Delay function. Stores the value x(Tnow) and returns the value x(Tnow-Tdelay).
Tdelay in seconds and larger than 0.0. The expression Tdelay must evaluate to
a time independent constant and may therefore only consist of constants and
parameter variables. The expression x(t) may contain other functions.
Example:
y = delay(xe + delay(x1, 1.0), 2.0)

Resetting a DSL model initializes its delay functions with x(Treset).

select
select ( boolexpr, x, y)
Returns x if boolexpr is true, else y.
Example:
x1.=select(T 1 > 0, xe/T 1, 0.0) !to avoid division by zero

time
time ( )
Returns the current simulation time.
Example:
t=time(), y = sin(t) or y = sin(time())

Stability Analysis and Simulation of Transients 21-428

DIgSILENT PowerFactory User Defined (DSL) Models

file
file ( ascii-parm, expr)
! OBSOLETE ! Use an ElmFile object in the composite model in stead.

picdro
picdro ( boolexpr, Tpick, Tdrop)
Logical pick-up-drop-off function useful for relays. Returns the internal logical
state: 0 or 1.
Return value:
The internal state:

• changes from 0 to 1, if boolexpr=1, for a duration of at least Tpick seconds

• changes from 1 to 0, if boolexpr=0, after Tdrop seconds

• remains unaltered in other situations.

flipflop
flipflop ( boolset, boolreset)
Logical flip-flop function. Returns the internal logical state: 0 or 1.
Return value:
The internal state:

• changes from 0 to 1, if boolset=1 and boolreset=0 (SET)

• changes from 1 to 0, if boolset=0 and boolreset=1 (RESET)

• remains unaltered in other situations. (HOLD)

Initial value: boolset.

The initial condition boolset=boolreset=1 will cause an error message.

aflipflop
aflipflop ( x, boolset, boolreset)
’Analog’ flip-flop function. Returns the (old) value for x at SET-time if internal
state=1, else returns the current value of x.
Return value:
The internal state:

• changes from 0 to 1, if boolset=1 and boolreset=0 (SET)

• changes from 1 to 0, if boolset=0 and boolreset=1 (RESET)

• remains unaltered in other situations. (HOLD)

Stability Analysis and Simulation of Transients 21-429

DIgSILENT PowerFactory User Defined (DSL) Models

lapprox
lapprox ( x, array iiii)
Returns the linear approximation y = f (x), where f is defined by the array iiii.
Example:

y = lapprox(1.8, array\_valve)

invlapprox
invlapprox ( y, array iiii)
Inverse lapprox with array.

lapprox2
lapprox2 ( xl, xc, matrix iiii)
Returns the linear approximation y = f (xl, xc) of a two-dimensional array,
where f is defined by the matrix iiii. xl represents the line value and xc the
column of the matrix.
Example:

y = lapprox2(2.5, 3.7, matrix\_cp)

sapprox
sapprox ( x, array iiii)
Returns the spline approximation y = f (x), where f is defined by the array iiii.
Example:

y = sapprox(1.8, array\_valve)

sapprox2
sapprox2 ( xl, xc, matrix iiii)
Returns the spline approximation y = f (xl, xc) of a two-dimensional array,
where f is defined by the matrix iiii. xl represents the line value and xc the
column of the matrix.
Example:

y = sapprox2(2.5, 3.7, matrix\_cp)

Stability Analysis and Simulation of Transients 21-430

DIgSILENT PowerFactory User Defined (DSL) Models

DSL event
event ( MaxTrig, x, ’ name=ThisEvent, dtime=delay, value=val,
variable=var)
Immediately executes the command, bypassing the command pipe in the input
window. The DSL command will continue after the command has been exe-
cuted. The ‘Exe’ command is provided for compatibility and testing purposes
only and should only be used by experienced users.

This function creates a parameter event for the own DSL model, if the input
signal x changes sign from - to + with a time delay of dtime.
The function will trigger each time when the input changes from a negative to a
positive value, but for maximum of MaxTrig times
Arguments:
int MaxTrig (obligatory) : Maximum number of trigger events; if M axT rig is set
to 0, you will get unlimited triggering.
double x (obligatory) : Input signal.
string ThisEVent (obligatory) : Name of the external event to be started. The
event must be stored locally inside the DSL model.
If ’name=this’ is set, no event has to be created but a parameter event (Evt-
Param) will be created and executed automatically.
double delay (obligatory) : Delay time of the event after triggering.
double val (optional) : Value of the parameter event (only when ’name=this’ is
set).
double var (optional) : Parameter to which the value is set (only when
’name=this’ is set).
Return value:
void (no return value)
Example:
The example shows a counter made with DSL using event( , ,’name=this ...’)
which automatically creates and configures a parameter event. The variable
named ”counter” will be set to value val within dtime. The input signal is a
sine-wave.
inc(x) = 0
inc(u) = amp0*sin(10*x)
inc(counter) = 0

x.=1
u = amp0*sin(10*x)
yo = u-trigval

cadd = counter+1
event(0,yo,’name=this dtime=0.0 value=cadd variable=counter’)
event(0,yo,’name=OpenBreaker dtime=0.2’)

Stability Analysis and Simulation of Transients 21-431

DIgSILENT PowerFactory Modal Analysis / Eigenvalue Calculation

Chapter 22

Modal Analysis / Eigenvalue

Calculation

The modal analysis calculates the eigenvalues and eigenvectors of a dynamic

multi-machine system including all controllers and power plant models.

The Eigenvalue analysis allows for the computation of modal sensitivities with
respect to generator- or power plant controllers, reactive compensation or any
other equipment.

The calculation of eigenvalues and eigenvectors is the most powerful tool for
oscillatory stability studies. For its application it is highly recommended to first
compute the ‘bare natural’ system oscillation modes. These are the oscillation
modes of the system without taking any controller or power plant model into
consideration, i.e. with constant turbine power, constant excitation voltage etc.
Starting from these ‘bare natural’ modes, the effects of controllers (structure,
gain, time constants etc.) and other additional models can be calculated as a
second step.

22.1 Theory of Modal Analysis

After the initial conditions have been calculated successfully, which means that
all time-derivatives of the state variables are zero, the modal analysis calculates
the complete system A-matrix by means of numerical, iterative algorithms. The
representation of the electrodynamic network model is equivalent to the
representation used for the balanced RMS simulation, except for the general
load model, for which the frequency dependencies are neglected.

The computation time for the models analysis is approximately proportional to

the squared number of state space variables.

A multi-generator system exhibits oscillatory stability, if all conjugate complex

eigenvalues, making up the rotor oscillations have negative real parts. This
means they will lie in the left complex half-plane. The individual generator
oscillations will then be stable.

Stability Analysis and Simulation of Transients 22-432

DIgSILENT PowerFactory Modal Analysis / Eigenvalue Calculation

Assuming that one of the conjugate complex pair of eigenvalues is given by:
λi = σi ± ω
then the oscillatory mode will be stable, if
σi < 0
The period and damping of this mode are given by
2∗π
Ti =
ωi
µ ¶
1 An
di = −σ = ln
Tp An+1
where An and An+1 are amplitudes of two consecutive swing maxima or minima
respectively.

The oscillatory periods of local generator oscillations are typically in the range of
0.5 to 5 Hz. Higher frequency of the natural oscillations, i.e. those which are
normally not regulated out, are often damped to a greater extent than slower
oscillations. The oscillatory period of the oscillations of areas (inter-area
oscillations) is normally a factor of 5 to 20 times greater than that of the local
generator oscillations.

The absolute contribution of an individual generator to the oscillation mode

which has been excited as a result of a disturbance can be calculated by:
n
X
ω(t) = βi νi eλi t
i=1

ω(t) = generator speed vector

λi = i’th eigenvalue
νi = i’th right hand eigenvector
where βi = i’th absolute contribution In the following, β
(depending on the disturbance)
n = number of conjugate complex eigenvalues
(i.e. number of generators - 1)

is set to the unit vector, i.e. β = [1, · · · , 1], which corresponds to a theoretical
disturbance which would equally excite all generators with all natural resonance
frequencies simultaneously. The elements of the eigenvectors νi then represents
the amplitudes of the generators in relationship to an eigen-frequency, whereby
those generators with opposite signs in νi oscillate in opposite phase. The right
hand eigenvectors νi can thus be termed the “relative contribution vectors”. The
number of elements in νi is the same as the number of relative contribution
factors.

Normalisation is performed by assigning the generator with the greatest

amplitude contribution the relative contribution factor 1 or -1 respectively.

Stability Analysis and Simulation of Transients 22-433

DIgSILENT PowerFactory Modal Analysis / Eigenvalue Calculation

For a n-machine power system, n-1 generator oscillation modes will exist and
n-1 conjugate complex pairs of eigenvalues lambdai will be found. The
mechanical speed ω of the n generators will then be described by:
       
ω1 ν11 ν21 νn1
 ω2   ν12   ν22   νn2 
       
 ..  = β1  ..  eλ1 t + β2  ..  eλ2 t + · · · + βn  ..  eλn t
 .   .   .   . 
ωn ν1n ν2n νnn

The relative participation factors give a good indication of the general system
dynamic oscillation pattern. They may be used easily to determine the location
of eventually needed stabilising devices in order to influence the system
damping efficiently.

The relative participation factors can be calculated not only for the generator
speed variables, but also for the following variables:

name unit Description

s:speed p.u. Speed
s:phi rad Rotor-angle
s:psie p.u. Excitation-Flux
s:psiD p.u. Flux in D-winding
s:psix p.u. Flux in x-winding
s:psiQ p.u. Flux in Q-winding

22.2 Performing Eigenvalue Analysis

A modal analysis can be started when a balanced steady-state condition is

reached in a dynamic calculation. Normally, such a state is reached by a
balanced load-flow calculation, followed by a calculation of initial conditions.
However, it is also possible to perform a balanced RMS simulation and start a
modal analysis thereafter.

When a load-flow is calculated the becomes active. The modal analysis

command dialogue can then be opened by

• either pressing the button on the Stability toolbar, as shown in Fig. 22.1

• or selecting the Calculation →Stability →Modal Analysis... option from the

main menu.

Now the dialogue for executing the modal analysis command ComMod will pop
up.

Stability Analysis and Simulation of Transients 22-434

DIgSILENT PowerFactory Modal Analysis / Eigenvalue Calculation

Figure 22.1: The Modal Analysis Buttons

On the ”Basic Options” page the default is to calculate ”All Eigenvalues” of the
system. This option can take quite a while, when analysing large power systems.
So there is the option to calculate only a selected range of eigenvalues. This
option is not yet available, but will be implemented soon to reduce calculation
time.

Using the S ETTINGS button the options of the command for calculating the
initial conditions used by the modal analysis can be specified individually.

On the ”Participation” page, the state variable and the result file for the
Eigenvalue analysis can be defined. The default state variable is the speed
signal of the generators. The default result file is ”Eigenvalue (s:speed)” and is
stored inside the active study case.

The relative participation factors can be calculated not only for the generator
speed variables, but you have so following variables to select from:

name unit Description

s:speed p.u. Speed
s:phi rad Rotor-angle
s:psie p.u. Excitation-Flux
s:psiD p.u. Flux in D-winding
s:psix p.u. Flux in x-winding
s:psiQ p.u. Flux in Q-winding

Fig. 22.2 shows the command dialogue of the modal analysis with the different
possibilities for the state variable.
When executing the command by pressing E XECUTE , the initial conditions of
all elements is calculated first. Then the modal analysis constructs a system
matrix from the load-flow and the dynamic data. The eigenvalues and
eigenvectors are calculated directly from that matrix. Since eigenvalue
calculations require linearised models, PowerFactory automatically performs
the linearisation of all relevant system elements.

The following information is printed to the output window, when the eigenvalues
are calculated:

DIgSI/info (t=-100:000 ms) - Initial conditions calculated.

Stability Analysis and Simulation of Transients 22-435

DIgSILENT PowerFactory Modal Analysis / Eigenvalue Calculation

Figure 22.2: Command Dialogue of the Modal Analysis

DIgSI/info (t=-100:000 ms) - Starting Modal Analysis. Please wait...

DIgSI/info (t=-090:000 ms) - Modal Analysis ready !

22.3 Results

The results of the modal analysis are separated into two parts:
• The system eigenvalues and eigenvectors
• The relative generator participation factors

The results are printed to the output window with the ComSh output command
by activating the ”Output Calculation Analysis”-button . After a modal
analyses has been executed, the ComSh shows the active option Eigenvalues
in the LoadFlow/Simulation report selection.

Selecting Eigenvalues will then enable the selection Output of Eigenvalues, as

shown in Fig. 22.3.
Either the eigenvalues may be reported, or the participation factors. When the
option Eigenvalues is selected all calculated eigenvalues of the system are

Stability Analysis and Simulation of Transients 22-436

DIgSILENT PowerFactory Modal Analysis / Eigenvalue Calculation

Figure 22.3: Output of Eigenvalues with Participation Factors Selected

printed in a report style into the output window. Fig. 22.4 shows the results of a
small example power system.

Figure 22.4: Output of System Eigenvalues

Selecting the option Participations, either detailed or not, will further enable the
selection of the state variables and the a certain eigenvalue as can be seen in
Fig. 22.3. For the your convenience there is also the possibility to define a filter
for the eigenvalues (“system modes”). The filter for eigenvalues is used to show
only the participation factors for specific system modes, if Select Eigenvalue(s) is
set to Filtered. Otherwise the selected specific eigenvalue will be used and the
filter will be ignored.

The system modes and participating generators can be filtered by using the
following options:

Maximal Damping The damping of the system mode will be below the defined
value in [1/s].

Stability Analysis and Simulation of Transients 22-437

DIgSILENT PowerFactory Modal Analysis / Eigenvalue Calculation

Maximal Period System modes oscillating below the defined periodic time in [s]
will be shown.

Min. Participation Only generators with a participation factors above the

specified limit will by outputted.

The results of the participation factors of the generators in the small example
power system are shown in Fig. 22.5.

Figure 22.5: Output of Participation Factors

Stability Analysis and Simulation of Transients 22-438

DIgSILENT PowerFactory Model Parameter Identification

Chapter 23

Model Parameter Identification

The process of parameter estimation for power system elements for which
certain measurements have been made is performed with the ”Parameter
Estimation” function using the button .

The ComIdent command object is a high performance non-linear optimization

tool, which is capable of a multi parameter identification for one or more models,
given a set of measured input and output signals. This identification is principally
performed in the following way:

• A “Measurement File” object (ElmFile) is created which maps the raw

measured data onto one or more “measurement signals”. These signals
may contain measured excitation and response signals.

• The measurement signals are used as inputs by the models of the power
system elements for which one or more parameters have to be identified,
or they may be used to control voltage or current sources.

• The output signals of the power system elements are fed into a
comparator, just as the corresponding measured signals. The comparator
is thus given the measured response on the excitation and the simulated
response of the element models.

• The comparator calculates an objective function, which is the weighted

sum of the differences between the measured and the simulated response,
raised to a whole power (by default to the power of 2).

• The ComIdent command will collect all objective functions from all
comparator objects in the currently active study case and will minimize the
resulting overall objective function. To do this, the ComIdent command is
given the list of parameters which are to be identified. The objective
functions are minimized by altering these parameters.

This whole process is visualized in Fig. 23.1

Of course, this picture only visualizes the principle of the identification. To

connect measurement files, power system models and comparator objects to
each other, a composite frame is used. This, and all other details of the
PowerFactory identification functions, is described in the following sections.

Stability Analysis and Simulation of Transients 23-439

DIgSILENT PowerFactory Model Parameter Identification

ElmWin
ElmDsl
Time Window

Xmeas
ElmFile
Measurement
File 1 Component
Xsim
ElmCompare
Model 1 Comparator

Σ ( Xsim -X m e a s)2
Xsim
Component
ElmFile Model 2..n
Measurement Xmeas
File 2

∆param

ComIdent
Optimizer

Figure 23.1: The Identification Principle

23.1 Target Functions and Composite Frames

The parameter identification process is performed by minimizing objective

functions. These objective functions are calculated by ElmCompare objects
from the difference between measured responses and calculated responses of
one or more power system elements.

To define an objective function, the measured excitation signals must be

connected to the component models or to voltage or current sources, and the
measured and calculated response signals must be connected to the compare
object. All this is done graphically by drawing a Composite Frame, using a block
definition (BlkDef) with slots.

A simple example of an identification block diagram, for the objective function for
a voltage controller, is visible in Fig. 23.2.

The block diagram uses slots which reserve space for the measurement files,
the comparator and the element models.

23.1.1 The Measurement File Slot

The measurement file object (ElmFile) has the following signals available:

• Number of Input Signals : 0

• Number of Output Signals : 10

• Input Signals Names : -

Stability Analysis and Simulation of Transients 23-440

DIgSILENT PowerFactory Model Parameter Identification

Figure 23.2: Simple Identification Block Diagram

• Output Signals Names : “y1,..,y10”

The measurement file slot in the example of Fig. 23.2 has the following settings:
• Class Name Filter : “ElmFile”
• Output Signals : “y1,y2”

The measurement file object itself is described in the DSL section of the
Technical Reference manual.

The fact that we speak of “output” signals in the case of the measurement file
does not implicate that the parameter identification only regards measured
response signals (“measured outputs”) from power system elements. It only
means that the measured excitation signals will be mapped onto ElmFile
signals. The ElmFile will reproduce the measured excitation and response
signals during the identification process.

23.1.2 Power System Element Slot

Power system element slots are used in the identification block diagram in the
same way as they are used to define composite models.

As in the case of a composite model diagram, the element slots may use any of
the available parameters of the power system element model as input or output.
The in- and output signals are defined by stating the exact variable name (see
also chapter 20.3).

In the case of the example in Fig. 23.2, the “Vco1” slot has the following
parameters set:
• Class Name Filter : “ElmVco*”
• Output Signals : “uerrs”
• Input Signals : “u”

Stability Analysis and Simulation of Transients 23-441

DIgSILENT PowerFactory Model Parameter Identification

23.1.3 Comparison Slot

The comparison object ElmCompare has the following properties:

• Number of Input Signals : 21

• Number of Output Signals : 0

• Measured Response Signal Names : “in1mea,..,in10mea”

• Simulated Response Signal Names : “in1sim,..,in10sim”

• Weighting Factor : qzpf

• Output Signals Names : -

The calculated value of the objective function will be multiplied by the weighting
factor before it is put out. The weighting factor may be used, for instance, to
connect a time-window to the comparison object which forces the objective
function to zero for those moments in time which are not to be used in the
identification process.

In the case of the example in Fig. 23.2, the Comparison slot has the following
parameters set:

• Class Name Filter : “ElmCompare”

• Input Signals : “in1meas,in1sim”

23.2 Creating The Composite Identification

Model

The identification block diagram only defines a generalized ‘workbench’ that is

needed for the identification process. Its function is similar to that of the
“Composite Frame” object and we also need to create a composite model, based
on the block diagram, to identify particular parameters of particular objects.

Suppose we have a voltage controller model of which we want to identify the

parameters ka” and ta. Measurements of the behavior of the physical appliance
are available as measured voltage-curves on the input and output of the
controller during a disturbance.

Assuming the example identification block diagram of Fig. 23.2, we have to

create a composite model (an ElmComp) in the active grid folder.

Stability Analysis and Simulation of Transients 23-442

DIgSILENT PowerFactory Model Parameter Identification

N OTE : If the identification process only addresses secondary power system

element, which are not directly connected to busbars, the identification
process does not require a power system grid.
However, all calculation functions like load-flow or EMT simulation re-
quire a calculation target in the form of an activated grid of system
stage folder. Therefore, a grid folder with at least one ‘DUMMY’ busbar
has to be created when secondary element models are to be identified.

The composite model must be set to use the identification block. It will then
show the slots that have been defined in that block. In the current example, the
composite model dialogue will look like Fig. 23.3.

Figure 23.3: The Example Composite Identification Model

In this figure, the three slots have been assigned already. Visible is that the
comparison object “Compare Signals” is selected, as well as a measurement file
and the voltage controller of which we want to find the best possible values for ka
and ta.

23.2.1 The Comparison Object

The comparison object calculates the objective function from the connected
measured and simulated responses. It allows for the use of weighting factors and
for other powers to raise to. The example in Fig. 23.4 shows the default settings.

Stability Analysis and Simulation of Transients 23-443

DIgSILENT PowerFactory Model Parameter Identification

Figure 23.4: The Comparison Object dialogue

In this figure, the 10 difference signals are listed, with their weighting factor. By
default, these are one, but they may be edited freely. The power factor equals 2
by default but may be set to any other positive whole number from 2 to 10.

The objective function calculated by the comparison object equals

n
X
[(Mi − Si ) ∗ wi ]p
i=1

where
• Mi is the measured response (i.e. “in1mea”)

• Si the simulated response (i.e. “in1sim”)

• wi is the weighting factor (i.e. for the difference signal nr.1)

• p is the power

23.3 Performing a Parameter Identification

The identification process is executed by the ComIdent command. This

command can be opened by the button on the main menu. This button can
be found on the “Stability” toolbar which ca be accessed by selecting the button
.

Stability Analysis and Simulation of Transients 23-444

DIgSILENT PowerFactory Model Parameter Identification

The Comident dialogue is depicted in Fig. 23.5.

Figure 23.5: The ComIdent dialogue

This dialogue shows references to the following objects:

Composite Model This reference is normally not needed. When left open, the
identification process will automatically gather all composite identification
models and will minimize all objective functions.
When the composite model reference is set, then the identification will only
minimize that model’s objective function.

Load-Flow Settings This reference is automatically set to the load-flow

command that will be used during the identification process.

Initial Conditions This reference is automatically set to the initial conditions

command that will be used during the identification process.

Simulation This reference is automatically set to the simulation command that

will be used during the identification process.

The identification process allows for the use of load-flow calculations and/or
dynamic simulations.

The “Load-Flow” and “Simulation” pages shows the variables that are to be
identified, in case of a load-flow or a dynamic identification. See for example Fig.
23.6.
In this example, two parameters of the voltage controller element “vco IEEEX1”
from the Composite Identification Model are listed. The identification process will
alter these parameters in order to minimize the objective functions.

The “Mode” field in the parameter list determines the parameter constraints:

Stability Analysis and Simulation of Transients 23-445

DIgSILENT PowerFactory Model Parameter Identification

Figure 23.6: Setting Identification Parameters

0 means not to change the parameter, but to leave it at its initial conditions. This
option may be used to temporarily exclude some parameters from the
identification process.

1 mean to optimize the parameter without restrictions

2 means to optimize the parameter, given the constraint that the parameter
value must always be greater than zero.

Although the object for which the parameters are optimized in this example is the
same object as is used in the Composite Identification Model, it is allowed to
enter any other parameter from any other element, as long as that element
belongs to the active study case. Such may be used to optimize secondary
appliance, where only the behaviour of the primary appliance has been
measured.

23.4 Identifying Primary Appliances

A primary appliance, such as a general load, an asynchronous machine or a

static var system, do not have an input signal like a voltage controller or any
other secondary appliance. It would therefore not be possible to connect a
measured signal directly to a load model in order to simulate its response.

To identify a primary element model, a small grid model is used to which one or
more controllable voltage sources may be connected. These voltage sources will
translate the measured voltage signals from the measurement file into a normal
busbar voltage which will be used in the load-flow or simulation calculations. The

Stability Analysis and Simulation of Transients 23-446

DIgSILENT PowerFactory Model Parameter Identification

response of the primary element models connected to that busbar may then be
compared to a measured response.

An example of this method is shown in the following pictures.

Figure 23.7: Identification Diagram with Primary Element

In Fig. 23.7, a simple Identification Block Diagram is shown in which the

measurement file is no longer connected to the element slot, but to the voltage
source slot. The voltage at the busbar at which the voltage source will be
connected will thus be forced to the measured values during the identification
process.

Figure 23.8: Primary Element and Voltage Source

In Fig. 23.8, a very simple grid is shown to which the load which is to be
identified and a voltage source element are connected. As with the normal
identification process, a Common Identification Model has to be created which
uses the Identification Diagram with Primary Element as shown in Fig. 23.7. In
the ComIdent command dialogue, the unknown parameters of the load may
then be listed.

It is of course possible to mix the identification of both primary and secondary

power system elements at the same time.

Stability Analysis and Simulation of Transients 23-447

Tools & Utilities
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory Virtual Instruments

Chapter 24

Virtual Instruments

The virtual instrument (or short ‘VI’) is a graphical tool to visualise variables from
various simulations or calculations. These VIs can be used in different ways to
show the results from nearly all calculation functions and packages of
PowerFactory. So their functionality and relationship to the other parts or the
software justifies their description in an own special chapter.

A virtual instrument is basically a tool for displaying calculated results. The most
common use of a VI is to look at the results of a time-domain simulation like an
EMT or RMS simulation, by defining one or more plotted curves showing the
variables changing with time.

But there are various applications of the virtual instruments, for example to
graphically display voltage profiles, FFT plots or the results of a harmonic
analysis. This could be in the form of a bar graph, a plotted curves, single
displayed variables, tables of values, etc.

To visualise results from a calculation, two different parts are important:

The Virtual Instrument Panel: The Panel is basically a page in the active
graphics board, where different plots or graphs are stored and displayed.
Also the basic information about the included virtual instruments is stored
here.

The Virtual Instruments: The virtual instruments are shown on the VI panel.
They display the results of one or more variables or parameters in various
ways. Every VI on a panel can be set up individually to the need of the
variable(s) which is to be displayed.

So all signals, parameters, variables or other magnitudes can be chosen to show

in a virtual instrument. These are normally floating point numbers, but you can
also show discrete variables as well as binary numbers, like e.g. a binary
variable, a ”out of service” flag or the switching operation of a circuit-breaker.

To show these magnitudes there are various designs of virtual instruments

available. These can be divided into several groups, which are described in the
sections of this chapter:

Plots are the ’basic’ diagrams to show all sorts of time-domain variables or

Tools & Utilities 24-449

DIgSILENT PowerFactory Virtual Instruments

magnitudes depending on other variables. The plots can be used in the

following ways:

• Subplot (VisPlot)
• Subplot with two y-axis (VisPlot2)
• X-Y plot (VisXyplot)
• FFT plots (VisFft)

Bar Diagrams are similar to the plots. The results are then not shown as a line,
but as single bars for every data point.

Vector Diagrams easily show different variables - like voltage, current or power
- in a vector diagram using polar or cartesian coordinates.

Meter Panels can display variables or parameters using different panels like:

• digital display
• horizontal scale of a meter
• vertical scale of a meter
• measurement VI
• interactive button/switch

Curve Inputs are used to conveniently convert graphical information (graphs or

curves) into a set of data by scanning and sampling the data points.

Bitmaps can be inserted as a remark or to provide further information.

Additionally to these options there are further types of diagrams for a specific
usage are e.g. the time-overcurrent plot or the time distance diagram used for
protection studies. These plots are not described in this chapter but directly in
the part of the manual dealing with the individual calculation method.

The usage of the plots and the available tools like labels, constants, etc. for the
virtual instruments can be used in either one of the diagrams described above or
below. In the following list these virtual instruments are described shortly:

VIs for Protection Studies

Time-Overcurrent Plot When studying overcurrent relays their characteristic is

often displayed depending on the magnitude of the current and the
specified tripping time. Here also the characteristic curves of power system
elements which are to be protected can be inserted into the diagram.
See also section 12.7, page 12-254

Tools & Utilities 24-450

DIgSILENT PowerFactory Virtual Instruments

R-X Plot This plot is used specially for showing the characteristics of distance
relays. The tripping characteristic of one or more relays can be visualised
in a R-X diagram. Also the impedance of adjacent elements can be shown
graphically inside the diagram.
See also section 12.4, page 12-248

Time-Distance Diagram For studying the selectivity of distance protection the

time-distance protection is often used. So PowerFactory provides a
convenient method to automatically show all distance relays in a specified
protection path in one specified diagram.

Feeder Definitions

Voltage Profile shows voltage profile of a complete subsystem belonging to a

defined feeder in the power system depending on the distance or the node
number.
See also chapter ??, page ??

Schematic Path With this plot a meshed or a radial network can easily be
shown in a brief schematic way without result boxes but with optical
information like colours for overloading, etc.

Voltage Sag Analysis

Voltage Sag Plot is especially designed to show the results of a voltage sag
analysis. Here the probability of a voltage sag depending on outage
information of elements can be displayed graphically.
See also section ??, page ??

Harmonics

Waveform Plot Using this plot a waveform is generated from the magnitude
and the phase angle of the harmonic frequencies. With this diagram a
variable like the voltage or current, which is defined in a harmonic source
e.g. a power electronic device or a load, can easily be shown as a time
dependent variable. So the real shape of the voltage can be seen and
analysed.
A more detailed description see section 24.6, page 24-476.

Tools & Utilities 24-451

DIgSILENT PowerFactory Virtual Instruments

24.1 Virtual Instrument Panels

Virtual instruments are created and edited on a Virtual Instrument Panel

(SetViPage) which is one of the possible types of pages on a Graphics Board.
Other page types are single line graphics and block diagram or frame graphics.

A new virtual instrument panel can be created by

• selecting the File→New option on the main menu and subsequently

selecting a ”Virtual Instrument Page” in the ComNew. This will create a
new new page in the ”Graphics Board” of the currently active study case.

• selecting the ”Insert New Graphic” button on the graphics board’s

toolbar and selecting ”Virtual Instrument Panel”. This will also create a new
VI panel in the current graphics board.

All virtual instrument panels are stored in graphics boards. A graphic board
holds default settings for plots and other diagrams. The button is clicked or
the Edit Actual Virtual Instrument Panel option is selected from the context
sensitive menu to edit the dialogue.

N OTE : If a a new virtual instrument panel is created, while there is no Graphics

Board opened already, a new Graphics Board in will be added to the
current study case.

The dialogue is build of several pages. These are

x-Axis holds the default x-Axis for plots without local axis stored in pages
without local axis.

Advanced holds the advanced settings like the arrangements of the plots or
their specific style.

Results stores a reference to the default results object used by the plots

Once a VI panel has been created, the ”Append new VI(s)” button ( ) can be
clicked or the option Create VI→... from the context menu of the SetVipage can
be selected to add new virtual instruments to the VI panel.

Virtual instrument panels usually set the size and position of new virtual
instruments like plots automatically. But it is possible to turn on user defined
moving and resizing of the plots. In this modes the plots can be moved or
resized by the user. Also the and buttons are used to tile the Virtual
Instruments horizontal or to arrange the VIs automatically.

Tools & Utilities 24-452

DIgSILENT PowerFactory Virtual Instruments

A ViPage uses a predefined style which set line-styles, line-width, fonts and
other graphical settings. Own styles can be created and selected. A different
style can be selected on each VI panel of a Graphics Boards.

These different options are described in the following sections.

24.1.1 Editing the Virtual Instrument Panel dialogue

There are several ways to access the graphics board dialogue from
PowerFactory

• When the panel is empty you can access the dialogue by simply
double-clicking the empty VI panel or an empty area on the panel.

• Right-click the background of the VI panel besides the shown plots and
choose Edit actual Virtual Instrument Panel from the context menu.

• The simplest way to edit the dialogue is to click the button.

The button is clicked or the “Edit Actual Virtual Instrument Panel” option is
selected from the context sensitive menu to edit the dialogue. The dialogue is
split into three different pages named:

• x-Axis holds the settings for x-Axis of plots and Waveform Plots

• Advanced holds graphical settings like Style and Background

• Results contains the reference to the default results object for plots.

Automatic Scale Buttons

The buttons or are clicked to scale the x-axis respectively the y-axis of
all plots on the virtual instrument panel automatically. Plots on other panels in
the same graphics board are unchanged if their axes are local.

The buttons are inactive, if there are no plots shown at all or if the x or y axes
can not be scaled automatically. That applies e.g. for bar-diagrams showing the
distortion after a harmonics load-flow calculation, where the x-axis is given by
the harmonic frequencies. Different types of plots, like the subplot and the
waveform plot, can be scaled simultaneously.

With the button ”Zoom X-Axis” a certain range of the x-axis or of several
x-axes can be zoomed easily. Thereto activate this button on the toolbar. Then
click on a plot, hold the right mouse button and ’drag’ the mouse to the right or to
the left to mark the desired range on the x-axis. If you release the mouse button,
PowerFactory will then show the marked x ranged zoomed.

Tools & Utilities 24-453

DIgSILENT PowerFactory Virtual Instruments

Automatic Arrangement of VIs

Virtual instrument panels usually set the size and position of new virtual
instruments like plots automatically. Then the VIs can not be resized or moved.
So the position of these VIs is set automatically and their size remains
unchanged.

There are two different modes for automatically arranging the VIs. You can
choose to arrange the VIs using either

• “Arrange Subplots on Top of Each Other” with the button or

• “Arrange Subplots automatically” with the button .

The modes can easily be changed by pressing the one or the other button. In
addition the position of VIs can easily be exchanged. Thereto mark the VI by
clicking it. Then you can ’drag’ the VI onto another plot. Thus the position of the
VIs will be exchanged.

N OTE : This option of exchanging the plots by dragging is only possible, when
one of the arrangement buttons are active. If you deactivate both but-
tons by unselecting them in the toolbar, the plots can freely be moved
by dragging them on the panel. See also ”Moving and Resizing”.

Another way to rearrange the VIs is to open the dialogue of the VI panel by
pressing the button and then use the Arrangement options on the
”Advanced” page. Here the option User defined can be activated. So the VIs will
no longer be arranged automatically but can be resized and moved inside the
panel. So you are free to arrange the VIs ’ad libitum’. This mode is also
activated by disabling the selected button or .

Moving and Resizing

Moving and resizing of VIs in the standard virtual instrument panels is turned off.
Both can be activated by deactivating the ’auto-arrangement’ modes by disabling
then currently active button or . Also the option User defined can be
activated on the ”Advanced” page of the ”edit” dialogue of the VI panel.

A VI is clicked to mark it. The VI is ’dragged’ inside the panel by clicking it with
the mouse button pressed. Then the VI can be move across the panel. The
mouse is released to set the new position. A VI is clicked on the border to resize
it. A VI is clicked on the border to resize it.

N OTE : Please note that some VIs can not be resized at all because their size
is set automatically. This applies e.g. for the bitmap VI with the option
”Adapt Size of VI to Size of Bitmap” enabled.

Tools & Utilities 24-454

DIgSILENT PowerFactory Virtual Instruments

Page Format
The page format is modified using the in the toolbar of the graphics board.
VI panels use the page format set in the graphics board. In addition a local page
format can be created for each VI panel. The option “Create local Page Format”
is selected in the context sensitive menu to create a local page format. The VI
panel now uses a local page format independent of the page format set in the
graphics board.

“Set default Page Format” is selected in the context sensitive menu to reset the
local page format. The VI panel now uses the default format of the graphics
board again.

Editing Variables of Plots

The button is clicked to open the “Edit Plots on Page” dialogue for defining
curves of several plots. If you want to change the variables of only one subplot it
is suggested to edit the dialogue of the plot itself by double-clicking it. This
procedure is more convenient.

This dialogue gives a very good overview over the diagrams on the VI panel and
the variables, axis and curve styles. Fig. 24.1 shows an example of the dialogue.

Figure 24.1: Editing all Plots on the Page

Each line of the table named Curves defines a variable shown on the panel. The
variables definition applies to the plot shown in the first column. When the
dialogue is opened the plots are sorted from left to right and from top to bottom
and are numbered accordingly.

All data and settings of each variable is displayed in the table, and the columns
are used exactly like the columns in the table of a plot. To move a variable from

Tools & Utilities 24-455

DIgSILENT PowerFactory Virtual Instruments

one plot to another, simply change the Plot Nr. of the variable to move.

In this table not only subplots (VisPlot) are shown but also plots with two y-axis
(VisPlot2) can be modified. Here additionally in the column y the y-axis can be
defined to which the variable is related. In Fig. 24.1 this can be seen in the to
last rows of the table. Here both variables are shown in one plot number 4 with
two different axis. If the number in this row is grey, only one y-axis is available in
this plot.

Like in most tables new rows can be add. Default File for Page is a reference to
the results element of the virtual instrument panel. The F ILTER ... button opens
the filter dialogue. The selected filter will be applied to all plots on the current
virtual instrument panel.

Default File for Page is a reference to the default results element of the virtual
instrument panel. This is exactly the same setting like the one displayed on the
Results page of the dialogue box of the virtual instrument panel.

Title Block
All virtual instrument panels in a Graphics Board show the same title by default.
The only difference of the title blocks on the VI-Panels are the panel name and
the page number which are unique for each panel. To create a local title for a
VI-Panel simply right-click on the title and select Create local Title from the
context sensitive menu.

Like in the single line graphics the button in the toolbar is clicked to show or
hide the title block. You can define or change the title by double-clicking on them
or use the button to modify the title text. For details about the settings of the
title object refer to section 7.8.2, page 7-144.

Results
Some VIs like the most frequently used class ”subplot” show curves stored in
one ore more result objects (ElmRes). The curves are selected in a table where
the result element, the element and a variable have to be selected.

The result column of VIs needs not to be set for most calculations. The VI itself
will look for the results element to display automatically. The default results
element is either:
1. Results reference on page Results of the VI Panel accessed by pressing
the button.
2. If 1. is empty the Results reference on the Results page of the Graphics
Board will be used by pressing the button.
3. If both (1. and 2.) are not empty, the results element used for the last
calculation will be applied. If there is no calculation the appropriate results
element in the study case will be used (if any).

Tools & Utilities 24-456

DIgSILENT PowerFactory Virtual Instruments

Background
The default background of virtual instrument panels is empty. The background
settings for the panel can be found in the frame Background on the “Advanced”
page of the virtual instrument panel dialogue.

The Filename defines the background file, which can be either a Windows
Metafile (*.wmf), a Bitmap (*.bmp) or a AutoCad DXF file. If the selected file
does not exist, or if the filename is not set the background remains empty. VIs
can be transparent or opaque. Graphics are transparent must be activated to
make all graphics transparent. If an opaque graphic fills the complete panel area
the background will be invisible.

The Context Sensitive Menu

The options in the context sensitive menu of the VI panel may vary depending on
the cursor and the settings of the panel. The options are listed below:

• Edit Actual Virtual Instrument Panel opens the virtual instrument panel
dialogue.

• Create local Page Format creates a page format for the current panel.

• Paste Text inserts text from the from the clipboard into the panel.

• A VI can be selected from the list shown in the Create VI→... option to
create a new VI on the panel.

• Style→Select Style is clicked to select a style for the panel.

• Style→Create new Style is selected to create a new style for the panel.

• Style→Edit Style of clicked Element is selected to modify the style of the

selected element only.

• Select All is selected to mark all VIs.

• Export Results... exports the shown result into e.g. the output window, a
ASCII file, a Comtrade file or the clipboard.

24.1.2 Creating Virtual Instruments

New VIs can easily be created with the ”Append New VI(s)” button . A small
dialogue will pop up, where the class of VI can be selected from the available
Object and the number of VIs to be added to the current VI panel.

Another way to create VIs is to select the option Create VI→... from the context
menu of the SetVipage. Then a class of virtual instrument can be selected to be
added to the current VI panel.

Tools & Utilities 24-457

DIgSILENT PowerFactory Virtual Instruments

24.1.3 The Default Styles

Each virtual instrument panel uses a style where line-widths, fonts, brushes and
other graphical settings are defined. There are six predefined styles available in
DIgSILENT PowerFactory, which are:

• Default - Standard English Text and Symbols

• Gr Default - Greek Symbols

• Tr Default - Turkish Symbols

• Paper

• Gr Paper

• Tr Paper

The ”Default” styles uses smaller line-widths and smaller fonts than the ”Paper”
styles. It was designed to get nice printouts. The paper style was designed for
reports and papers where meta-files are included in text-programs. In addition to
the layout the styles hold predefined VIs.

There are several ways to select a predefined or user-defined style for the
current virtual instrument panel. The easiest way to change the style is using the
toolbar.

• The list-box in the toolbar is clicked and an available style is selected.

• A style is selected from the Style→Select Style→... in the context sensitive

menu of the VI panel.

• A style is selected in the VI-Style list-box on the “Advanced” page of the

SetVipage dialogue.

The user-defined styles are described in detail in section 24.9 later in this
chapter.

24.2 Plots

Plots are the most used diagrams to show all sorts of parameters, states, signals
or variables depending on the time or on another variable. To show these
time-domain variables or to visualise a magnitude depending on other variables,
there are the following plots available:

• SubPlot (VisPlot)

Tools & Utilities 24-458

DIgSILENT PowerFactory Virtual Instruments

• SubPlot (2y) with two y-axis (VisPlot2)

• X-Y plot (VisXyplot)
• FFT plots (VisFft)

24.2.1 The Subplot

SubPlots are the ’basic’ diagrams and are e.g. used to display one or more
plotted curves from the results of a EMT or RMS simulation.

A new subplot is created on the current VI panel by pressing the button and
selecting a Subplot (VisPlot) from the pull down list. More than one subplot
may be created at once by setting the Number of VI(s). The new empty subplots
appear with standard settings, as is shown in Fig. 24.2.

Figure 24.2: Creating a new SubPlot (VisPlot)

To edit the subplot either

• right-click it, and select the Edit option from the context sensitive menu
• double-click it.

Editing Subplots
The edit dialogue of a subplot, as shown in Fig. 24.3 has pages for the y-axis
and x-axis of the individual subplot as well as an additional Advanced page for
auxiliary settings. The y-axis page is normally used to set the curves in the
subplot, while the x-axis normally, and by default, shows time.
The subplot edit dialogue has the following features:

Tools & Utilities 24-459

DIgSILENT PowerFactory Virtual Instruments

Figure 24.3: The SubPlot Edit Dialogue

Scale The y-axis may be defined for more than one subplot at the same time,
or, and by default, may be defined as a “local Axis” format. When the
option Use local Axis is disabled, a reference to the used ‘global’ axis type
is shown and can be edited by pressing the .

Automatic The colour, line style, and line width of all new curves in the subplot
will be set automatically when the corresponding option is enabled. The
S ET NOW button will apply automatic line formats all existing curves
again.

Shown Results This is a reference to the currently active result file (ElmRes).
This object will be used, if no result file is specified in the Curves definition
table.

Tools & Utilities 24-460

DIgSILENT PowerFactory Virtual Instruments

Curves The definition table for the curves is used to specify the result file
(optional), object and parameter for each of the curves as well as their
representation.

These available options are described in more detail below.

Setting the X-Axis

The x-axes often have to be synchronised for all subplots or for all subplots on
one VI panel, for instance to show the same time-scale in all plots. In order to
synchronise the x-axes without losing the freedom to manually set each subplot,
a hierarchy of x-axes is used in the Graphics Board:

• The Graphics Board contains the basic x-axis definition. This definition is
used by default by each new subplot.

• A VI panel, however, may define a local x-axis definition, which will then be
the default for each new subplot created on that panel.

• The subplot thus uses the Graphics Board or the panel SetViPage
definition by default, but may also use a local x-axis definition.

N OTE : If you change the settings of the x-axis, which uses the definition stored
in the graphics board, all x-axis are changed using the same definition
in the whole project. These are also affected, if the x-axis is automati-
cally scaled or zoomed.

The following list describes how to edit the definition of the different x-axes:

• For editing the graphics board definition, you may select the option
Graphics Board and go to the x-Axis page of the edit dialogue of the plot.
Using the button you can access the dialogue for changing the x-axis
definition for the complete graphics board.
Another way is to click the button for the graphics board dialogue and
then go to the x-Axis page.

• Similar to the graphics board definition, the x-axis definition of the VI panel
is changed by selecting the option Page. This will open the dialogue of the
of the VI panel (SetVipage).
Another way is to go to the panel dialogue by clicking the button or
selecting Edit actual Virtual Instrument Panel from the context menu and
then go to the x-Axis page.

• The local x-axis definition is simply accessed by selecting the option Local.
Then the options for specifying the x-axis is shown in this dialogue.

Tools & Utilities 24-461

DIgSILENT PowerFactory Virtual Instruments

The options available for the x-axis are similar to the one for the y-axis. They are
described in the following section. The only difference is in selecting the variable
of the axis.

For the x-axis there is a list to choose the x-Axis Variable shown in Fig. 24.4.
The Default value is depending on the type of simulation and the result object
created during the previous simulation. Then for time-domain simulations
different representations of the time scale are available. For the FFT plot e.g. the
x-axis can be scale using the frequency respectively the harmonic order.

Figure 24.4: The Variable List available for the x-Axis

The option User defined enables you to choose any variable for the x-axis, which
is selected to be stored in the result object. As shown in Fig. 24.4 an element
and a variable can be selected for the x-axis. In this way a x-y plot can be
created. There is also an own plot type for a more convenient way to create x-y
plot: the VisXyplot is described in more detail in section 24.2.4.

Setting the Y-Axis

The y-axes are normally not synchronised like the x-axis, because they all show
different parameter values and thus need parameter-specific settings. By
default, the Graphics Board’s default plot type is used, but more plot types may
be created and used, i.e. plot types for voltages, power, factors, slip factors, etc.
By using the same plot type, different plots can be compared more easily,
without the risk of mis-interpreting a difference in curve amplitude.

Although the x- and y-scale definitions thus use somewhat other synchronising
schemes, the way a particular axis is set is quite similar. Both the y-axis and the
x-axis page in the subplot edit dialogue have the option to Use local Axis or
simply Local.
• If this option is disabled, a reference is shown which points to the used axis
definition as described in the last section.
• If the option is enabled, the axis is defined locally and the edit dialogue
changes in order to do so. See Fig. 24.3.

Tools & Utilities 24-462

DIgSILENT PowerFactory Virtual Instruments

The local definitions of an axis has three parts:

• the axis limits (minimum and maximum)

• the kind of axis (linear, logarithmic)

• the auto scale options
• the settings to adapt the scale to a setpoint.

The axis limits can be given manually, or can be auto scaled by pressing the
S CALE button. With this button the limits are defined automatically from the
curve shape once.

The options to Auto Scale the plot are

Off Turns any auto scaling function off and will display the results in the range
between the given limits.

On This option will automatically scale the plot at the end of a simulation.

Online This option will automatically scale the plot during the simulation.

The x-axis additionally features a Chart option. If ticked a range and a start
value can be set. This will set the x-axis to the specified range. During the
simulation only a x-range, set in the options, is shown and will ’wander’ along
with the calculation time.

The Adapt Scale settings are used to force a tick mark on the axis at a particular
value. This is the Offset value. Other tick marks will be drawn at ‘nice’ distances
from this offset. The default value for both x- and y-axis is an active adapt scale
with Trigger equal to zero. So the main ticks of the axes start at zero.

To see the deviations from the offset, the Show Deviations from Offset option will
draw a second axis on the right, which has its zero baseline at the offset value.
The Show Deviations from Offset option is available for the y-axis only.

An example of two subplots is given in Fig. 24.5 where a voltage sag is shown
with both an instantaneous and a RMS value curve. The top curve has the
Adapt option disabled, and both axes autoscaled.
The bottom subplot has a smaller x-axis, to show only the interesting part, and
has the Adapt option set on both axes.

The y-axis has its offset set to the nominal voltage level (11kV) and also shows
the deviations from that level in the right vertical axis. From this deviation, it is
directly clear that the RMS voltage initially drops more than 5kV. The x-axis has
its offset set to the event time, which in this case is 100ms when a short-circuit
was simulated. From the x-axis, it is now directly clear that this short-circuit was
cleared after 200ms, at t=300ms.

Tools & Utilities 24-463

DIgSILENT PowerFactory Virtual Instruments

Figure 24.5: Two Subplots with Different Axis Definitions

24.2.2 Specifying Curves for Plots

The curves in a subplot must be taken from a result object (ElmRes), which is
created by a power system calculation function like the RMS or EMT simulation.
How to create such a result object is explained in section 25.1, page 25-495.

The selection of the variables to be plotted in the current plot is done in the
y-axis page of the edit dialogue. This is easily accessed by double-clicking the
background of the plot. The dialogue is shown in Fig. 24.3 and Fig. 24.6 in
detail.

Figure 24.6: Defining a New Curve

Each line in the shown matrix has the definition of a curve.

• The first column states the result object from which the data to plot the
curve will be read. If it is empty, the standard result file will be used defined

Tools & Utilities 24-464

DIgSILENT PowerFactory Virtual Instruments

in the reference Shown Results in the same dialogue.

• The second column states the power system element (here: the generator
“G1d”), which is selected from the available elements in the result object.
• The third column states the actual variable for the curve (“xspeed”),
selected from the variables in the result object, belonging to the selected
element.
• The next columns specify the style of the individual curve.
• With the last two columns the user can norm the values of the variable to a
nominal value given.
A new result object, element or parameter is selected by double-clicking the field
or by right-clicking it and selecting Select Element/Type or Edit from the context
sensitive menu. A list of possible result objects resp. elements or parameters will
pop up from which a new entry can be selected.

The colour, line style and line width settings are edited in the same way: double
clicking or right clicking and selecting Edit.

New curve definition lines can be created by right-clicking on the column number
(on the far left) (see cursor arrow in Fig. 24.6) and selecting Insert Rows or
Append (n) Rows. Marked curve definitions can similarly be deleted from the list
by selecting Delete Rows.

N OTE : If you want to see changes between to consecutive simulations, you

can run the first simulation. These results will be stored inside the
result object Results.ElmRes, which can be found in the active study
case. Copy this object, paste it and rename it to e.g. ”old Results”.
Then you can add the same variable to a plot twice and select the ”old
Results” result object for one of them (as shown in Fig. 24.6). This will
show the old and the new results in one plot.

If more than one curve is to be specified for the same result file and element, this
may be done in one action by selecting more than one variable from the variable
list. This will automatically create new entries in the curve definition table for all
additionally selected variables. The entered Result File and Element are copied
automatically. This very convenient procedure is shown in Fig. 24.7 and Fig.
24.8.

Similarly several elements can be selected. Then PowerFactory will

automatically insert the according number of rows. The variables are then set
automatically to the one selected in the first row.

24.2.3 The Subplot with two Y-Axis

Tools & Utilities 24-465

DIgSILENT PowerFactory Virtual Instruments

Figure 24.7: Defining Subplots with minimum effort, step 1

Figure 24.8: Defining Subplots with minimum effort, step 2

A plot with two y-axes can be seen in Fig. 24.5. To create this plot you have to
press the button and select a Subplot (2y) (VisPlot2) from the pull down
list. This will add a subplot with two y-axes to the current VI panel.

The second axis can then be defined and curves for this axis can be specified
similar to the ’basic’ subplot VisPlot. In the edit dialogue of this plot, as shown in
Fig. 24.9, there will now appear a page for y1-Axis and for y2-Axis.
On the page for the second y-axis, this additional axis can be deactivated by
unticking the option Use second y-Axis.

24.2.4 The X-Y Plot

A further type of plot is the x-y plot. This plot will show one variable depending
on a second variable in one diagram. The two variables can be completely
independent from each other and do not have to belong to one element.

Tools & Utilities 24-466

DIgSILENT PowerFactory Virtual Instruments

Figure 24.9: The Definition of the Second y-Axis

To create a x-y plot you have to press the button and then select a X-Y Plot
(VisXYPlot) from the pull down list. This will add a new x-a plot to the current VI
panel.

Fig. 24.10 shows the edit dialogue of the plot.

Figure 24.10: Defining Variables for a X-Y Plot

On the variables page the variables for the x- and y-axis are specified. Both
variables have to be stored in one result file of a simulation. To select variables
of two different elements the option Show x-Element in Table has to be activated.
The options and the tools for the curves are similar to the ones described in
section 24.2.2.

Tools & Utilities 24-467

DIgSILENT PowerFactory Virtual Instruments

On the second page Scales of the dialogue the scales of the two axis can be set
automatically or global definitions can be used for them.

The plot is drawn for a certain time range. On page Time Range this range can
be set to the whole simulation time, or you can select only a specified range to
show these results.

24.2.5 The FFT Plot

The FFT plot (VisFft) is similar to the normal subplot (VisPlot) from the handling
point of view. This plot will not show variables depending on the simulations time
but on the frequency. A time range of signal can be selected and then be
transformed from the time domain into the frequency domain using the
Fast-Fourier Transformation (FFT). This then will shown the harmonic contents
of this signal depending on the nominal frequency of the system.

Like other plots it can be created by using the ”Append VI(s)” button . An
much easier way is to click on a plotted curve and then selecting Create FFT
Plot from the context sensitive menu. Then you can ’drag’ the mouse pointer
from the selected point on the curve to the left or right. When holding the mouse
still, a quick-help box shows you the range, beginning and end of the curve to be
transformed.

By clicking the diagram again, a range for the FFT is set and the FFT is
calculated and shown in a newly created plot.

When entering the ”edit” dialogue by double-clicking the plot, the x- and y-axis
can be defined on the different pages similar to the VisPlot. Additional options
are:

Calculate This additional option on the page y-Axis modifies the Fast-Fourier
Transformation and the time range of the signal the FFT is applied to. The
S YNCHRONIZE will synchronise the time range with a given frequency.
Furthermore the different parts of the variable and the number of samples
for the FFT can be selected.

Unit The unit of the x-axis can be set to Frequency or Harmonic Order. For the
Harmonic Order the nominal frequency can be set different to the network
frequency.

Display On the Advanced page the display of the FFT results can be toggled
between the Spectral Line and a solid Curve.

Tools & Utilities 24-468

DIgSILENT PowerFactory Virtual Instruments

24.3 The Vector Diagram

Using a vector diagram complex values such as voltages, currents and apparent
power can be visualised as vectors in one or more diagrams. A complex variable
can be defined and then shown in two different representations:
• Polar coordinates, i.e. magnitude and phase of the current
• Cartesian coordinates, i.e. active-and reactive power

There are predefined vector diagrams for calculation results. The predefined
vector diagrams can easily be created using the context menu of a branch:
right-click a branch in the single line graphic or in the data manager.
select the option Show→Vector Diagram→... from the menu
select one of the predefined variable, i.e. Voltage/Currents

The example Fig. 24.11 shows the voltage and current on one terminal of a line.

N OTE : A vector diagram can only be shown when branch elements like lines,
load, transformers, etc. are selected. Then the vectors of the voltage,
current or power across the elements or at the nodes connected to the
elements are shown in diagrams.
The vector can be shown after a load-flow calculation or before and
after a transient RMS simulation.

Another way of creating a vector diagram VecVis to the current VI panel is -

equal to adding a subplot - by pressing the button and selecting a Vector
Diagram (VecVis) from the pull down list. In the edit dialogue the variables can
then be shown as described in section 24.3.2.The objects and variables of the

vector diagram can be changed manually by editing the dialogue, which is

opened by double-clicking the vector diagram. The more convenient method is
to right-click the diagram and selecting
• Default Vectors→... to select a predefined vector from the list.
• Label of Vectors changes the label of the displayed elements shown in the
diagram.
• Jump to Element to select one of the elements that is connected to the
currently displayed element.
• Set Origin set the origin of the diagram to the position selected with a
mouse-click.
• Center Origin set the origin of the diagram in the middle of the plot.

Tools & Utilities 24-469

DIgSILENT PowerFactory Virtual Instruments

Figure 24.11: Vector diagram of Voltage and Current on a Line

24.3.1 The X And Y Axes

In most plots, the x and y scale are given by the minimum and maximum value of
each scale. A vector diagram can’t be defined using minimum and maximum for
each scale because the x- and the y-ratio must be equal. The ratio for each unit
is therefore set as the parameter units per axis tick. In addition the location of
the origin can be defined.

If all shown variables have the same unit, the axis are labelled with values and
unit. If there is more than one unit, the labels show ticks. A legend showing the
ratio of the units is add at the right bottom of the plot. The balloon help of the
scale labels always the absolute values for each unit.

Editing the Unit/Tick

To modify the scale of an axis the table Scales in the edit dialogue can be
changed. The column “Unit” shows the unit, the column “Scale” shows the ratio
in unit per tick. A higher ratio then shortens the vector.

If the “Auto Scale” option in the dialogue is turned on, the scales are adapted
whenever a new calculation is ready. Turn off “Auto Scale” to keep the scale

Tools & Utilities 24-470

DIgSILENT PowerFactory Virtual Instruments

limits.

Setting the Origin

The origin position of the vector plot can be changed either graphically or with
the dialogue:

• Right click the vector plot and select Set Origin. This will move the origin to
the right clicked position.

• Modify the “x-Min.” and “y-Min.” values in the plot dialogue to the starting
value of the x-and y scale.

Changing Coordinates
The plot displays the vectors in cartesian or in polar representation. The grid of a
polar plot is shown as circles and can be altered as described in section 24.2.
The representation setting is also used for the mouse position display in the
status bar.

The option Polar in the context menu toggles between representation in polar
and cartesian coordinates. On the Advanced page in the edit dialogue this
representation can also ba changed.

Label of Vectors
In the edit dialogue as well as from the context menu of the plot the label of the
vector can be displayed in the different coordinate representation, so the real
and imaginary value or the magnitude and phase angle can be shown.

24.3.2 Changing the Object

There are two different ways to change the objects for which the vector plot is
made by:

• Right-clicking one of the vector plots and select Jump To. This shows a list
of all connected elements from which one can be selected. Here the side
of a branch element is automatically checked. The Jump To option is not
available if there is more than one element shown in the same plot or if
there are no calculation results available.

• The “Element” column in the variables table in the plot dialogue, as

depicted in Fig. 24.12, is double clicked to select a new object.

Tools & Utilities 24-471

DIgSILENT PowerFactory Virtual Instruments

Figure 24.12: Variable list of a vector diagram

24.3.3 Changing the Variables

There are two different ways to change the displayed variables:

• Right-click the vector plot and select the Default Variables option. This will
show a list of predefined variables. This option is not available if there is
more than one element shown in the same plot or if there are no
calculation results available.

• The “Var. x-Axis” column in the variables table in the plot dialogue, as
depicted in Fig. 24.12 is double clicked to select a new variable from a list.
The variables shown in the list are either the magnitude or the real-part of
the vector. The angle or the imaginary part are set automatically. The
selection list is empty when no calculation result are available.

24.4 The Voltage Profile Plot

This plot VisPath shows the voltage profile of a radial network based on the
load-flow results. It is directly connected to a defined feeder in the network, so it
can only be created for the part of the system a feeder is assigned to.

The voltage profile plot needs a successful load-flow calculation. It can not be
created if there is no load-flow calculated. The most easy way of creating a
voltage path plot is to define such a plot in the single line graphic.

To create a voltage profile:

• First you have to define a feeder for the radial network you would like to
create a voltage profile for by right-clicking on a switch and then select
Define→Feeder.... A new feeder object is created.

• A branch of an already defined feeder is right-clicked. The context

sensitive menu will show the option Show→Voltage Profile. PowerFactory
will then create a new object VisPath showing the voltage profile for the
defined feeder.

Tools & Utilities 24-472

DIgSILENT PowerFactory Virtual Instruments

• In the ’calculation relevant objects’ or in the data manager select the feeder
object you just created or you want to show the voltage profile of.
Right-click on it and select Show→Voltage Profile from the context
sensitive menu.

N OTE : The option Show→Voltage Profile is only available when a load-flow

calculation is performed or the results of the last calculation are valid.

The voltage profile plot shows the voltage of terminals or busbars along a feeder.
The variable(s) shown by the plot can be changed. If there is no valid load-flow
calculation the plot remains empty. A voltage profile is shown in Fig. 24.13.

Figure 24.13: Example of a Voltage Profile Plot

The curve shown can be clicked and marked at the busbar positions (points).
Like most plots available in DIgSILENT PowerFactory the voltage profile plot
can be labelled. See the context sensitive menu or the description of the result
graphs for details.

The plot in the example shows the voltage m:u with the unit “p.u.”. The position
of the busbars (x axis) is shown as the distance from the beginning of the feeder.
The unit is “km”. The variables shown for the busbars can be changed by the
user through the edit dialogue of the plot.

The x-Variable of the voltage profile can be changed by editing the dialogue of
the plot. On the Scales page of the Edit dialogue a list box defines the x-axis
variable. There are two predefined x axis.

Tools & Utilities 24-473

DIgSILENT PowerFactory Virtual Instruments

Distance shows the distance of the busbar away from the feeder in “km”.

Bus Index numbers the busbars so the distance on the plot between the
busses is constant.

Other prompts for random variable input. Each variable available at all busbars
in the feeder can be input there.

The y-Variable(s) can be user-defined. The predefined variable for the plot is the
voltage m:u with the unit “p.u.”. Any other variable available at all busbars in the
feeder can be set. To change the shown variable, edit the voltage profile dialogue
and change the variable name in the table. Resize the table to append variables.

The Branch Colouring settings define a different colouring of the plot. For
example the overloading of a branch element can be defined and shown in the
plot. In Fig. 24.13 to line elements are loaded over 80%, so they are displayed in
red. Also either the maximum or the minimum values of parallel branches can be
shown.

On the Advanced page the Colouring of the busnames shown in the plot can be
defined additionally.

Off does not display any busnames.

Black simply shows all names in black font style.

Coloured acc. to Feeder Colours the bus names according to the colour of the
different feeders.

The context sensitive menu shows now additional functions regarding the
voltage profile plot, when right-clicking on the plot or on the profile:

Edit Feeder opens the ”edit” dialogue of the feeder related to the plot.

Edit Data opens the ”edit” dialogue of the selected line, transformer or other
element.

Edit and Browse shows the selected element in the data manager.

Mark in Graphic marks selected element in the single line graphic(s).

24.5 Schematic Visualisation

24.5.1 Schematic Diagram

Tools & Utilities 24-474

DIgSILENT PowerFactory Virtual Instruments

Besides the voltage profile the object VisPath can also be used to show the
schematic diagram of a radial network. The usage and the different options
available for this plot are similar to the voltage profile plot in section 24.4.

The diagram shows a schematics of a radial network. It is also directly

connected to a defined feeder in the network, so it can only be created for the
part of the system a feeder is assigned to. It can only be shown or created, if a
load-flow is calculated for the system

To create a schematic diagram,

• you have to define a feeder a the radial network by right-clicking on a
switch in the single line graphic or in the data manager and then select
Define→Feeder....
• The context sensitive menu of a branch with a defined feeder will now
show the option Show→Schematic Visualisation→Plot. PowerFactory will
create a new VisPath and the schematic diagram showing the profile for
radial network.
• In the ’calculation relevant objects’ or in the data manager select the feeder
object and select Show→Schematic Visualisation→Plot from the context
sensitive menu.

In the plot you will see the terminals and busbars as well as the electrical
elements belonging to the feeder depending on the real distance of the network
or on the bus index, where the distance between every node is constant.

24.5.2 Schematic Single Line Diagram

There are further functions to show the schematics of radial networks. These
functions are applied especially when no single line graphics of a network exists
and one wants to let PowerFactory draw the schematic of a radial network
automatically in a very convenient way.

These functions can be activated from the context sensitive menu of the branch
element with a defined feeder similar to the voltage plot or the schematic plot
described above. Using the option Show→Schematic Visualisation→... you can
use two slightly different operations:
Distance PowerFactory will draw automatically from the database a single line
diagram for the radial network defined by the feeder. The distances
between the terminals/busbars in “km” are set automatically according to
the distances specified in the lines.
Bus Index Similar to the schematic diagram the distances between the
terminals/busbars will be neglected and a standard value will be used for
all terminals.

Tools & Utilities 24-475

DIgSILENT PowerFactory Virtual Instruments

Remember to run a load-flow prior to activating these functions. Otherwise you

will not have access to the options.

24.6 The Waveform Plot

The waveform plot VisHrm is used to display the waveform of a voltage or

current after a harmonics load-flow calculation. These harmonics are typically
emitted by an harmonic voltage or current source described in chapter 13.4,
page 13-271. The waveform is calculated according to the following formula:
n
X
u(t) = u(i) · cos(2πf (i) · t + ϕ(i))
i=1

where
i = Index of frequency
n = Number of frequencies
t = Time
f (i) = Frequency at index i
u(i) = Magnitude at frequency i
ϕ(i) = Angle at frequency i

For the If a successful harmonic load-flow calculation with the option All
Frequencies is performed, the waveform plot will show the results of any
distorted or pure sinusoidal variable, e.g. voltages or currents, from any element
in the network. It can also be created if there is no load-flow calculated.

To create a waveform plot on the current VI panel, press the button and
selecting a Waveform Plot (VisHrm) from the pull down list. More than one
subplot may be created at once by setting the Number of VI(s). The new empty
subplots appear with standard settings.

Usage, settings and tools of this plot are similar to the subplot. A detailed
description can be found in section 24.2.1, page 24-459. Although the definition
of the variables is slightly different. Besides the result object and the element,
there can be defined the magnitude of the variable, which is to be shown in the
plot, and additionally the angle related to the magnitude can be inserted when
this information is needed.

The appropriate angle is automatically matched to the selected magnitude, if

such angle is available in the results and if the variable is a voltage or a current.

Tools & Utilities 24-476

DIgSILENT PowerFactory Virtual Instruments

When no appropriate angle is found, one may be selected manually.

Nevertheless it is not obligable to insert an angle to shown the waveform plot.

Fig. 24.14 shows an example for defining a variable in the VisHrm.

Figure 24.14: Defining Variables in a Waveform Plot (VisHrm)

24.6.1 The Waveform Plot Settings

Most other settings/options of the waveform plot act exactly like the settings of
the Subplot (VisPlot). See section 24.2.1 for more information. Additionally to
the standard settings of the plots there are specified settings of the waveform
plot. Step size and range for time t are specified at the waveform plot settings
object stored in the “Changed Settings” of the active project.

To change the waveform plot settings either press the C ALCULATION button in
the dialogue of the plot or select Calculation in the context menu on the plot. The
Settings Waveform Plot object SetWave holds the Step Size and the Range for
the calculation of waveforms in the Waveform Plots.

Figure 24.15: The waveform plot settings dialogue

Step Size
The waveforms seen in the plot are calculated by the waveform plot itself. To
avoid errors the Step Size must be smaller than half the period of the highest

Tools & Utilities 24-477

DIgSILENT PowerFactory Virtual Instruments

frequency calculated by the harmonics load-flow. To guarantee that this criteria

is always fulfilled, independent of the harmonics calculation, the Step Size is
entered in Number of Samples in Highest Frequency. The Highest Frequency
and the resulting Step Size are shown just for information.

Range
To be independent of the basic frequency the time range of the waveform is
entered in Number of cycles of Basic Frequency. Basic Frequency and the
resulting Range are shown just for information.

24.7 Embedded Graphic Windows

Some dialogues contain embedded graphic windows to visualise input settings.

An example is shown in Fig. 24.16 for the parameter characteristic dialogue.
Many other dialogues have also such embedded graphs. An embedded graph
shares much of its functionality and features with the ‘normal’ graphs in the
Virtual Instruments, like the subplot in section 24.2.1.

Figure 24.16: Example of an Embedded Graphs

Tools & Utilities 24-478

DIgSILENT PowerFactory Virtual Instruments

Similar to the plots on a VI page the mouse position in the embedded graphic is
shown in the status bar. The context sensitive menu of the embedded graphs
offers commands for printing and zooming.
Print Picture This option opens the print dialogue. The default print format for
embedded graphs is A4. The printer orientation is set to the orientation of
the embedded graph. The print dialogue offers to preview the printed area.
Zoom In This option changes the cursor to a magnifying glass. Drawing a
rectangle with the cursor will enlarge that area.
Zoom Back This option restores the previous zoom area.
Zoom All This option zooms out to the complete window.
Change Viewpoint This option changes the arrow to the move arrow .
Press the left mouse button, hold it down and move the mouse outside the
window. This will move the zoomed area in that direction. Press the right
mouse button or E SC to change the cursor back again.

Additionally there may be a L IMITS available in the dialogue. Pressing this

button will open a small dialogue where the minimum and maximum of the x-axis
can be changed, or the S CALE button will reset the settings and scale the axis
automatically.

24.8 Tools for Virtual Instruments

Different kinds of plots are used to display calculation results or device data.
There are a lot of tools, which will help you interpreting and analysing these data
or results of calculations. Most of them are accessible directly through the
”status bar” of PowerFactory or through the context sensitive menu. This is
activated by right-clicking on the curve or an the plot background depending on
the function you want to choose.

24.8.1 Edit Dialogues

The ”Edit” dialogue of the plots can be accessed through double-clicking on the
background of each plot or by selecting Edit in the context sensitive menu. A
faster way to access special information of the plot is to double-click directly on
the element you want to change. This can be the:
Legend: the legend text and representation can be edited directly.
X-Axis: to edit the x-axis limits, scales and variable representation and auto
scaling options of the current graphics board or panel.

Tools & Utilities 24-479

DIgSILENT PowerFactory Virtual Instruments

Y-Axis: to edit the y-axis limits, scales and variable representation and auto
scaling options as well as the variable to be shown.

A double-click on other positions will open the plot dialogue.

24.8.2 The Status Bar

In the status bar of PowerFactory on the bottom of the program window useful
information of the data shown in the curves can be obtained.

• First the value of the mouse position in the diagram is displayed in the
status bar, similar to the information shown with an open single line
diagram.

• When a curves is clicked and marked with a cross, the cross value is also
displayed in the status bar and remains unchanged until the cross is set to
a different position. If there is no cross on the active page the status bar
value is reset and no longer displayed.
Some plots have different scales on one axis, therefore these plots can not
display a value in the status bar.

• You will find the option Curve-Tracking in the status bar, normally in a grey
font style. When double-clicking this option the ”Curve-Tracking” mode will
be activated. Then a cross will appear if the mouse arrow will be near a
curve. If the mouse is hold still for one second, the x- and y-value will be
shown in a balloon window.

24.8.3 Labelling Plots

There are different styles of labels available for labelling curves and graphics.
Setting labels is possible in most of the different plots, although some of the
labels are not available in all kinds of plots. The labels are created the same way.

The label option is available from the context sensitive menu whenever a curve
or graphic was clicked and marked with a cross. The option Label→Insert ...
Label can be selected for the different labels. In addition there are two buttons
and in the toolbar, which can be used to create labels.

After selecting the appropriate label from the sub-option of label, a rubber band
from the cross to the mouse is shown. A click with the left mouse button sets the
label, the right mouse button cancels. The following different labels are available.

The Text-Label The text-label displays an user defined text above and below a
line connected to the curve with a rubber band. Edit the label to change the
text shown.

Tools & Utilities 24-480

DIgSILENT PowerFactory Virtual Instruments

The Value-Label The value-label displays the x/y coordinates of the cross. The
label is a text-label filled with the coordinates. Edit the label to change the
text.

The Form-Label The form-label uses a form to print the displayed text. The
form is local for each label or common to all plots of the same type in the
active project.

The Text and Value Label

The text and the value label (VisValue) is used to label curves or graphics
displayed in plots. The text of the label is written above and below a horizontal
line. The line is connected to the curve/graphic with a ’rubber band’.

After creating the labels, they can freely be dragged across the plot while staying
connected to the data point on the curve. The text can also be changed by
double-clicking the label or the rubber band. The edit dialogue of these two
labels is depicted in Fig. 24.17.

Figure 24.17: X/Y Value dialogue

Value: Value displays the connected curve position of the label. For labels
created as value this position is displayed as label text. “x-Axis” displays
the x axis value, “y-Axis” the y axis value. “Time” is visible only for plots
showing a trajectory.

Text on Top: Text written above the horizontal line.

Text on Bottom: Text written below the horizontal line.

Tools & Utilities 24-481

DIgSILENT PowerFactory Virtual Instruments

Delete Label when a new Simulation is started: Some plots show simulation
results. Labels in plots showing simulation results are deleted when the
simulation is started again. To keep labels in such plots, e.g. to compare
curves with the last run, turn off this option. The default of this option is
“on”.

The Format Label

Like the “text/value label”, the format label (VisLabel) is set in plots to label
curves or graphics. This label displays text printed using a form. The form is
different for each type of diagram. It is either defined local at the label or defined
for all diagrams of the same type in the activated project.

Figure 24.18: The form-label dialogue

The different information and parameters for this label are described below:

Value Value displays the connected curve position of the label. “x-Axis” displays
the x axis value, “y-Axis” the y axis value.

Data Object “Data Object” is a reference to the shown object. If “Data Object”is
not set the label itself is taken as shown object.

Shown Object The object output by the form, see “Data Object” described
above.

Edit Used Format “Edit Used Format” shows the used “Form Manager”. The
used format is either the local format or the one defined for all plots of the
same type in the active project.

Create Local Format “Create Local Format” creates a new “Form Manager”
valid for the current label only. The forms can be edit without influencing
other labels in the same plot or in the active project. The “Create Local

Tools & Utilities 24-482

DIgSILENT PowerFactory Virtual Instruments

Format” button is replaced by the “Set Default Format” when a local format
was defined.

Set Default Format “Set Default Format” removes the local format. The format
used is the one used for all plots of the same type in the active project. The
“Set Default Format” button is replaced by the “Create Local Format” when
the local format was reset.

Delete Label when a new Simulation is started Some plots show simulation
results. Labels in plots showing simulation results are deleted when the
simulation is started again. To keep labels in such plots, e.g. to compare
curves with the last run, turn off this option.

Form the context sensitive menu of the format labels more options can be
selected

Border A simple border of the selected label can be turned on or off.

Form The format options can be directly accessed by Edit used Format and
Create Local Format for the marked format label.

Reconnect with... Reconnects the format label to another curve or data point.

24.8.4 The Constant Value

The constant label (VisXvalue) is used to display y-values for a constant
x-quantity or x-values for a constant y. In some plots like the overcurrent plot,
constant labels are created and deleted automatically e.g. to visualise the
short-circuit current for relays.

The look of constant labels may vary because of different settings like the label
location, the intersection values and other options. The dialogue of the constant
label is depicted in Fig. 24.19.
To insert a constant label into a diagram or plot, the option Set
constant→x-Value or Set constant→y-Value places a constant x- or a constant
y-value into the current plot. Thus the dialogue for constant the VisXvalue object
will pop up (shown in Fig. 24.19) and a horizontal respectively vertical line will
then be displayed at the value specified in the dialogue. Also the constant value
and (if exist) the value of intersections with the curves will be shown.

There are different options and styles for the constant label:

Name defines the name of the constant line and will be displayed in the plot.

Style changes the representation of the constant label:

Line Only displays only the solid line and the related label.
Line with Intersections shows a solid line including label and indicates
the values when intersections with the curves of the plot.

Tools & Utilities 24-483

DIgSILENT PowerFactory Virtual Instruments

Figure 24.19: The Constant Label dialogue

Short Line Only (Left/Right) indicates the constant value at the

bottom/top respectively at the right/left side of the plot.
Short Line/Intersection (Left/Right) indicates the constant value at the
bottom/top respectively at the right/left side of the plot and the
intersections with curves.
Intersection Only shows only the intersection points with the curves.

Label defines the position of the constant value label:

None displays no label at all.

Outside of Diagram creates the label between the border of the VI and
the diagram area. Labels of constant x values are created above the
diagram area, labels of constant y values are created right of the
diagram area.
Above Line (right) shows a label above the line if y is constant, the label
will be on the right hand side.
Below Line (left) shows the label below the line on the left hand side.
Left of Line (top) shows a label on the left side of the line if x is constant,
the label will be on the top end.
Right of Line (bottom) shows the label right of the line on the bottom end.

Tools & Utilities 24-484

DIgSILENT PowerFactory Virtual Instruments

Value defines the constant value, either X or Y. The dialogue shows if either a X
or Y is set. Also the actual position of the cross will be shown as a x-
respectively y-value. It is not possible to change a constant X into a
constant Y label other than by removing the old and creating the new one.

Colour specifies the colour of the line and the labels/intersections.

Linestyle and Width specifies the line style and line width for the line shown.
Invisible if “Show Values” is set to “Intersections Only”.

For constant x-values in time-overcurrent diagrams there exist additional options:

x-Value is Displays the type of current displayed. Visible only for constant x
values in time overcurrent diagrams.

Show Values The constant value can be displayed as a line, as intersections

with the curves/graphics or both. “Line Only” shows a vertical or horizontal
line without labels for the intersections with the curves. “Line with
Intersection” creates crosses at the intersection of the line with the curves.
For constant x values the y value is displayed at the crossing ant the other
way round. The values and their unit are colored like the curve crossed.

Intersections Constant x values created automatically in the overcurrent plot

are displaying the short circuit current. To get the tripping times
“Intersections” can be set to SHC Currents. “All” would display the
intersection of the relay curve ignoring the type of current. Visible only for
automatic constant x values showing currents in the time overcurrent
diagrams.

Set User Defined The button “Set user defined” is visible for constant values
created by the short circuit in overcurrent plots. Labels showing this button
display the short circuit current. The labels are deleted whenever a new
short circuit was calculated. If one wants to modify and keep the label even
if a new short circuit was calculated the label must be changed to user
defined.

24.8.5 The Straight Line

There are various ways of inserting lines into a plot. With the option Straight
Line→... there can be used a

Set Secant to add a line directly through the selected data point.

Through Point defines a graphic line through the selected data point with a
defined gradient and gives back the function of the line.

User Defined defines a line independent from the curves shown with a defined
gradient and y-offset.

Tools & Utilities 24-485

DIgSILENT PowerFactory Virtual Instruments

The function of the inserted line can also be seen, when holding the mouse
arrow over the line for 1 second. The options of the line dialogue or similar to the
options for the constant value in section 24.8.4.

24.8.6 Curve Filter

Curves shown in the plots and diagram can be filtered using the ”Curve Filter”.
The option Filter... from the context sensitive menu displays the filters available
to be applied to the data read from the result object. Another way to access this
function is from the ”edit” dialogue of the plot. Here you may press the
F ILTER ... button. Fig. 24.20 shows the dialogue of the function.

Figure 24.20: Defining a Curve Filter

The “Curve Filter” specifies the type of filter applied to the data read from the
result object. This object is a filter applied to curves in plots. There are different
filter types available. The following filter settings are available. (N=number of
points in the original curve, K=number of points in the filtered curve)

Disabled No filtering will be performed. K=N.

Average The filtered curve is the running average of the last n points. The first
n-1 points are omitted. K=N-n+1.

Balanced Average The filtered curve is the running average of the last (n-1)/2
points, the current point and the next (n-1)/2 points. This filter thus looks
ahead of time. The first and last (n-1)/2 values are omitted, n must be an
odd number. K=N-n+1.

Purge Points by averaging The filtered curve contains the averages of each
block of n values. K=N/n. This filter may be used to speed up the display of
large curves.

Purge Points The filtered curve only contains every n-th value. All other values
are omitted. K=N/n. This filter may be used to speed up the display of large
curves.

Tools & Utilities 24-486

DIgSILENT PowerFactory Virtual Instruments

N OTE : A curve filter can only be applied at the end of the simulation or mea-
surement, points added during a simulation or measurement are not
filtered.
The option Filter... is not available in all plots.

24.8.7 Border
The option Border in the context sensitive menu will insert or change the border
of the selected plot or diagram. The options available are

• Off

• Simple

• 3D

• 3D with label

The border with 3-dimensional effect and label will insert an additional label on
the bottom of the selected plot. You can now define the label by double-clicking
on it. Furthermore the text style can be altered by choosing the option Select
Font for Border.

24.8.8 Export of Curve Graphic

The whole diagram or plot can also be exported for further usage in reports.
Thereto first mark the plot you want to export to a graphic file. Then select the
option File→Export...→... from the main menu.

You can choose now between the export into a Windows MetaFile (*.wmf) or into
a Bitmap File (*.bmp).

24.8.9 Export of Curve Data

The export of curve data is available for a single VI or for the variables of the
entire VI panel. Hence there are different ways to access the ”ASCII Results
Export” command ComRes of curve data, described in the following paragraph.
The export directly from the result file gives you the opportunity to directly export
several variables at once and is described in more detail in section 25.1.1.

Exporting curves of a single VI:

• Press the E XPORT... button in the right side of the dialogue box of a
virtual instrument.

• Right-click on the VI and select Export... from the context sensitive menu.

Tools & Utilities 24-487

DIgSILENT PowerFactory Virtual Instruments

Exporting curves of the entire VI panel:

• Press the E XPORT R ESULTS ... button on the ”Results” page of the VI
panel.
• Right-click on an empty area of the VI panel and select Export Results...
from the context sensitive menu.

N OTE : If in one plot or on one VI panel variables are shown from several result
objects, a dialogue will appear before the export command, where you
have to select one result file from the list.

This function will export the data from the displayed curve with the given time
range as ASCII text to the following programs/files:
• Output Window
• Windows Clipboard
• Measurement File (ElmFile)
• ComTrade
• Textfile

In this dialogue you can also set the individual step size, the columns of the
result file and the header for the export as can be seen from Fig. 24.21

24.8.10 Various VI Tools

Grid This option in the context sensitive menu displays a dialogue to turn on/off
the available grid lines. For both x- and y-axis a main grid and a help grid
can be displayed in the plots. Furthermore - depending on the type of plot -
the representation of the different ticks on the axes can also be specified.
Autoscale X, Autoscale Y Changes the autoscale settings of the plot. Off
turns off the auto-scale mode. On performs an auto-scale at the end of the
simulation or calculation. Online is available in simulation plots only and
tests the plot limits after each new simulation point.
These settings can also be defined in the ”edit” dialogue of the x- and
y-axes.
x-Scale(s), y-Scale(s) There are two options in the x-scale or y-scale entry.
Edit displays a dialogue to modify the scale settings like minimum,
maximum and other settings. Scale Automatic calculates the minimum and
maximum of the curve and adapts the scale limits.
These settings can also be defined in the ”edit” dialogue of the x- and
y-axes or by double-clicking on the corresponding axis.

Tools & Utilities 24-488

DIgSILENT PowerFactory Virtual Instruments

Figure 24.21: Command Dialogue of the ASCII Result Export

Show dx/dy Right-click on data point on a curve and select Show dx/dy from
the menu. The two lines will appear, which are connected to the tip of the
mouse pointer. A balloon window will show you the x- and y-difference
between the selected data point and the point where the tip of the mouse
pointer is in the diagram. Additionally the gradient is displayed.

24.9 User-Defined Styles

Each VI panel, each virtual instrument and every single plot uses a style where
line-widths, fonts, brushes and other graphical settings are defined. These
objects normally use predefined styles. In PowerFactory there are six
predefined styles available:
• Default - Standard English Text and Symbols

• Gr Default - Greek Symbols

• Tr Default - Turkish Symbols

Tools & Utilities 24-489

DIgSILENT PowerFactory Virtual Instruments

• Paper

• Gr Paper

• Tr Paper

These styles can be modified for all VIs or only for single plots. For this
user-defined styles can easily be created and specified. The base for an user
defined style is always the previous default style.

There are several ways to select a predefined or user-defined style or change

between the available styles.

• The easiest way is using the list-box in the toolbar by clicking and selecting
one of the available styles.

• A style can be selected from the Style→Select Style→... in the context

sensitive menu of the VI.

• A style is selected in the VI-Style list-box on the “Advanced” page of the VI

dialogue.

The user-defined styles are stored in the changed settings element of the active
project. Therefore each project has its own \C HANGED
S ETTINGS\S TYLES\U SER S TYLE\... path and user defined styles. Only the
changed elements are stored in the project, the unchanged ones are the ones
predefined in the default style.

You can see the ”changed settings” elements in the database in Fig. 24.22.

Figure 24.22: The changed Settings in the Database

24.9.1 Defining Styles for the VI Panel

Tools & Utilities 24-490

DIgSILENT PowerFactory Virtual Instruments

The Style→Create new Style option in the context sensitive menu of the VI panel
SetVipage or every plot on the panel is selected to create a new style for the
actual virtual instrument panel. Insert a name for the style to be created in the
input dialogue. Then the new style is added to the predefined styles and is
automatically selected for the current VI panel. The created style is not set
automatically in other VI panels of the project.

If a user-defined style is selected for the current VI panel, the Style→Edit Style
option of the context sensitive menu of the panel may be selected to open the
dialogue of the new panel style. Fig. 24.23 shows the dialogue for editing the
layout of the panel.

Figure 24.23: Editing the Panel Style

With the settings shown in the figure, mainly the layout of the title block of the VI
panel is edited. Here you can define
• the different font styles for the various entries of the block by clicking on the
BUTTONS

• the height and the width of the columns of the title block
• the line width of the title block and of the page frame

24.9.2 Defining Styles for the Virtual Instruments

There is the possibility to define the x- and y-axis of the plots inside on one
page. These settings then are valid every plot on panels using this style.

Tools & Utilities 24-491

DIgSILENT PowerFactory Virtual Instruments

To change the styles, right-click on a virtual instrument on the panel and select
the option Style→Edit Style in the context menu. Then a dialogue will pop up
containing the settings for
• all x-axis of VIs using this style

• all y-axis

• the selected object VIsplot

Double-click on the object you want to change. As shown in Fig. 24.24 the
dialogue of the selected axis will be opened and can then be modified.

Figure 24.24: Editing the Styles of Y- and X-Axis

In the dialogue you can then specify the following settings of the axes for the
selected style:

Tools & Utilities 24-492

DIgSILENT PowerFactory Virtual Instruments

Axis Here the style and width of the axis itself can be changed. Also the
number of small ticks shown between the divisions can be chosen.

Text The number of characters and the digits behind the decimal point as well
as the font type and size can be specified.

Distance between Axis and Text

Arrow The representation can be altered between the normal style and a style
with an arrow at the end of the axis with a certain width and length of its tip.

24.9.3 Defining Styles for Single Plots

In addition to the axes the presentation of the plot itself can be chosen by the
user. These settings can be accessed through the dialogue described in 24.9.2
and then double-clicking on the settings of the VisPlot object.

Another and simpler way to change the settings of the style is to directly select
the option Style→Edit Style of clicked Element from the context sensitive menu.
These are the same dialogues shown in Fig. 24.24 and can directly be accessed
by right-clicking on the

• x-axis in the plot to access the settings of the x-axis

• y-axis in the plot to access the settings of the y-axis

• on the plot itself to access the settings plot style, i.e. the grid, legend, etc.

Fig. 24.25 shows all different settings available for the plots on a VI panel. Thus
you can

Grid Options to alter the width, line style and colour of the main grid and the
help grid.

Legend Edit the distances from the legend to axis and between the different
legends.

Margins Set spaces between the diagram and the surroundings.

24.9.4 Saving Predefined Styles for Plots

If the settings of the x- and y-axis, of the plot itself as well as the size of a
particular plot shall be saved and then reused for further plots, there is the option
Style→Save as predefined VI form the context menu of every plot or VI.

Tools & Utilities 24-493

DIgSILENT PowerFactory Virtual Instruments

Figure 24.25: Editing the Settings of the Plot

This option saves the setting of the plot and stores a new VI in the list of all VIs.
Hence if adding a plot you can now select the newly created VI from the list by
pressing the button and selecting the e.g. NewName (VisPlot) from the pull
down list or by using the option Create VI→... from the context menu of the
SetVipage to add new virtual instruments to the VI panel. The new empty
subplots appear with new defined settings.

Tools & Utilities 24-494

DIgSILENT PowerFactory Results, Graphs and Documentation

Chapter 25

Results, Graphs and

Documentation

DIgSILENT PowerFactory is a power system analysis program, and a large set

of objects, commands, interactive diagrams and database tools are dedicated to
the task of defining and handling power system designs, their design variants
and their analyses.

Another set of objects, commands and tools are dedicated to the handling and
presentation of results, either in text or in a graphical format. These objects,
commands and tools are the subject of this chapter.

25.1 Result Objects

The result object (ElmRes, ) is used by the PowerFactory program to store

tables of results. The typical use of a result object is in writing specific variables
during a transient simulation, or during a data acquisition measurement. Result
objects are also used in DPL scripts, in reliability calculations, for harmonic
analysis, etc.

An example of the result object dialogue is depicted in Fig. 25.1.

The result object shows the following fields:
Name the name of the result object

Database ID its database ID and the date, when it was changed the last time

Default for its default use

Info information about the currently stored data, ie.e the time interval, step
sizes, number of variables, etc

Trigger-Times trigger times (in case of a Triggered default use)

The information about the stored data shows

• the time interval

• the average time step

Tools & Utilities 25-495

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.1: The Result Object

• the number of points in time

• the number of variables

• the size of the database result-file

The U PDATE button will recalculate these parameters and update the shown
information if necessary. The C LEAR DATA will clear all result data.

N OTE : Clearing the data will delete the result-file and will reset the database
ID. This will destroy all calculated or measured data in the result file. It
will not be possible to restore the data.

The default type settings are used for two purposes:

1. Creating a new result object and setting the default type to Harmonics, for
instance, will cause the harmonics command dialogue to use this result
object by default.

2. Setting the Default type to Triggered will cause the calculation module to
copy and temporarily store signals in that copied result object, every time a
Trigger Event becomes active. The Triggered default type enables the
trigger time fields.

When the P ROTOCOL O UTPUT is activated, all events that happened during

Tools & Utilities 25-496

DIgSILENT PowerFactory Results, Graphs and Documentation

the simulation, recorded by the result object, will be written again into the output
window. So you can check what events took place during the last simulation.

The contents of a result object are determined by one or more monitor variable
set (IntMon) objects. These monitor objects can be edited by pressing the
C ONTENTS button. This will show the list of monitor sets currently in use by the
result object.

Selecting a set of result variables, trough the use of monitor objects is necessary
because otherwise all available variables would have to be stored, which is
practically impossible.

25.1.1 Exporting Results

The stored results for the monitored result variables can be exported by pressing
the E XPORT button in the result object. This will activate the “ASCII Results
Export” command ComRes and will pop up the ASCII-results export dialogue,
which allows for exporting to the output window, to the windows clipboard, to a
file or to other export formats.

This command is the same command for exporting curve data form a VI plot.
This is described further in section 24.8.9.

In this dialogue you can also set the individual step size, the columns of the
result file and the header for the export as can be seen from Fig. 25.2
This function will export the data from the displayed curve with the given time
range as ASCII text to the following programs/files:
• Output Window
• Windows Clipboard
• Measurement File (ElmFile)
• ComTrade
• Textfile

The export command allows for exporting an interval of results only and to
export every n-th result. So you can define an additional step size n for the
export. Additionally a User defined interval for the time/x-scale can be set as the
minimum and maximum value of the first recorded variable (in time domain
simulations this is of course the time).

By default, all the results for all monitored variables are exported. But also a
selection of variables can be made by entering column numbers under the
section Columns (Variables). The header of the exported result table can include
either the variable name or its long or short description.

Tools & Utilities 25-497

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.2: Command Dialogue of the ASCII Result Export

25.1.2 Selecting Results Definitions

When a new calculation has to be made and no result object has been selected
yet, the in the calculation command dialogue can be pressed to show a
database browser with available result object definitions. Pressing the
button in the database browser will create a new result object.

To create a new list of parameters or to edit an existing list in a result object, the
C ONTENTS button can be pressed, which will pop up a browser with all monitor
variable sets that have already been defined. To define a new variable set, the
button in the browser can be pressed.

The result object thus combines one or more monitor variable sets, which allows
for a very flexible and highly transparent result definition. In fact, by using monitor
variable sets, just about every parameter used in the PowerFactory program
comes available as calculation result, together with a description and a unit.

The variables selected with the IntMon dialogue in the result object become
available to the subplot objects in the virtual instrument panels. In these
subplots, one or more result objects can be selected and from those result
objects a power system element and one of its variables can be chosen, if that

Tools & Utilities 25-498

DIgSILENT PowerFactory Results, Graphs and Documentation

element and that variable was selected in one of the IntMon objects. The
subplot will then show the calculated curve of that variable.

For more information about defining result objects with monitor variable sets, see
Monitor Variable Sets, section 5.10, page 5-64.

25.2 The Output Window

All textual output of DIgSILENT PowerFactory will be written to the output

window. This includes all error messages or warnings, command messages,
device documentation, result of calculations, generated reports, etc.. The
output window, at the bottom of the screen, is always there; it cannot be closed
although it can be minimised. The output window can be “docked”, that is: fixed
to a location on the bottom of the main window. The docked state is the default,
as shown in Fig. 25.3.

Figure 25.3: The PowerFactory Output Window

When clicking the right mouse button, when the cursor is in the output window
area, the context sensitive menu of the output window appears. The output
window can then be undocked by deselecting the “Docking View” (by clicking the
mouse onto ”Docking View” to ’untick’ it). The undocked output window is still
confined to the main window, but now as a free floating window.

N OTE : This sometimes occurs ’accidentally’ when the user left clicks the tool
bar for the output window and drags the mouse (keeping the mouse
button down) to somewhere outside of the output window boundaries.
To rectify this simply left click in the title bar of the undocked window
and drag it down to the bottom of the screen, where it will dock once
more (if you have right clicked ’unticked’ ”Docking View” to right click
and select ”Docking View” once more.

The undocked state is not a normal situation for the output window. Because the
output messages that appear in this window are important at any stage while

Tools & Utilities 25-499

DIgSILENT PowerFactory Results, Graphs and Documentation

using the program, the docked state is the best place because it will be visible
then and easy to locate.

The edge of the output window shows a splitter bar [a] which is used to change
the size of the output window. The ‘drag’ cursor, as shown at [a], appears
automatically when the cursor is placed on the splitter bar. The left mouse button
can be pressed when the ‘drag’ cursor is visible. This will turn the splitter bar to
grey and the output window can now be resized by holding down the mouse
button and moving the mouse up or down.

The output window may be moved and resized by:

• Dragging the splitter bar as shown in Fig. 25.3, when the output window is
in the ’docking’ mode
• Double-clicking the frame of the output window to dock/undock it from the
main window.
• Pressing the on the main toolbar, which enlarges the graphics board
by hiding the output window.
• Pressing the buttons on the main toolbar, which enlarges the output
window

The contents of the output window may be stored, edited, redirected, etc., using
the following buttons:
Opens an editor and pastes any selected or complete text from the output
window
Opens a different output file

Either saves the selected text to an ASCII file, or the complete contents of
the output window if no selection was made
Copies the selected text to the Windows Clipboard for use in other
programs
Clears the output window by deleting all messages

Searches the text in the output window for the occurrences of a given text.
A “?” wild cart may be used
Changes the font used in the output window

Redirects everything to a file on disk. The output window will stop

displaying messages while this button is down
Acts like ”redirect to disk”, but all messages will now be printed directly

Either prints the selected text or all buffered text if no selection was made

Tools & Utilities 25-500

DIgSILENT PowerFactory Results, Graphs and Documentation

25.2.1 The Output Window Settings

The user settings (see section 4, page 4-37) has options for different kinds of
output messages: errors, warnings and informations. See Fig. 25.4.

Figure 25.4: The Output Window Settings

To enable the copy and paste of other than normal messages, the corresponding
message categories have to be checked. Only the selected messages will be
copied. This means, for example, that when the information texts are disabled
and a block of text is copied in which the following 4 lines are present:

DIgSI/info - Calculating load-flow

DIgSI/info - load-flow iteration: 1
DIgSI/info ------------------------------------------
DIgSI/info - Load-flow converged with 1 iteration

then these 4 lines will not be copied.

In most cases only the calculation results are of interest, not the messages that
surround them. The errors, warnings, information and protocol messages are
therefore disabled by default.

Tools & Utilities 25-501

DIgSILENT PowerFactory Results, Graphs and Documentation

The other option is to disable all escape sequences in the ASCII export to file,
printer or other editors. These escape sequences are used by PowerFactory to
code for text colour and special characters. Other programs may not be able to
display the exported text correctly. The escape sequences have to be disabled in
that case.

Additionally you can define the maximum number of lines in the output window.
This means that if this number is exceeded due to further information displayed
in the window, the oldest messages will be deleted. The value “-1” will disable
the limit for the number of lines.

25.2.2 Using the Output Window

The output window is more than just a dumb message viewer. It is an interactive
tool, which helps in preparing your data for calculations and it improves any
search for errors or bugs in your projects.

Every line in the output window with a full folder and object name can be
double-clicked with the left mouse button. This will open the appropriate edit
dialogue for the shown object. See the example in Fig. 25.5.

Figure 25.5: The interactive output window

In this example, a calculation function reported an error because a transformer

element has not been given a transformer type. Double-clicking the error
message opens the edit dialogue of the transformer.

Context Sensitive Menu inside the Output Window

Tools & Utilities 25-502

DIgSILENT PowerFactory Results, Graphs and Documentation

It is also possible to press the right mouse button while pointing at the object
name. The context sensitive menu will will pop-up and show entries to easily find
and edit objects, if the printed objectname was found to be an existing object in
the database tree.

These option are

Edit Object will open the edit dialogue of the printed object, which is i.e. the
reason for the error message

Edit and Browse Object will open the data manager and show the element
and its parameters there.

Mark in Graphic will mark the clicked element in the single line diagram and
zoom into the region of its place.

The interactive feature of the output window is extremely convenient when

‘debugging’ a new or changed power system design. Faulty elements don’t have
to be searched for in order to correct their parameters.

25.2.3 Output Window Legend

The output window uses colors and other formatting to distinguish between
different types of messages or for specials like bar diagrams.

Text messages formats:

“DIgSI/err - ...” Error messages. Format: red coloured.

“DIgSI/info - ....” Information messages. Format: green coloured.

“DIgSI/wrng - ...” Warning message. Format: brown coloured.

“DIgSI/pcl - ...” Protocol message. Format: blue coloured.

Text only Output text. Format: black coloured.

Reports of calculation results may contain bar graph information. The “voltage
profiles” report after a load-flow command, for instance, produces bar graphs of
the per-unit voltages of busbars. These bars will be coloured blue, green or red if
the “Verification” option in the load-flow command dialogue has been enabled.
They will be hatch-crossed if the bars are too large to display.

An part of a bar graph output is shown in Fig. 25.6. The following formatting is
visible:

Green Solid Bar Used when the value is in the tolerated range.

Blue Solid Bar Used when the value is too low.

Tools & Utilities 25-503

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.6: Output window bar diagram

Red Solid Bar Used when the value is too high

Hatch-crossed Bar Used when the value is out of reach and cannot be
displayed correctly.

25.2.4 Copying from the output window

The contents of the output window, or parts of its contents, may be copied to the
build-in editor of PowerFactory or to any other program.

Normally, not all selected lines will be copied and the format of the copied text
may undergo changes. The latter is caused by the fact that the PowerFactory
output window uses special formatting ‘escape sequences’. Other programs
may not be capable of dealing with these formatting commands.
Which lines will be copied is determined by the output window settings. See
section 25.2.1 for more information. When text from the output window is about
to be copied, an info message will pop up, informing the user about the current
settings. See Fig. 25.7. A button is supplied which brings the user directly to the
user settings dialogue. The info message may be disabled, in which case it will
never show up again.

Tools & Utilities 25-504

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.7: The Output Window Info Message

25.3 The Form Editor

The form editor within DIgSILENT PowerFactory is used to define text reports,
from very small result boxes, to more complex and comprehensive reports.

For a detailed technical description of the report generating language, see

section 25.4, page 25-508.

The form editor (IntForm) will be used in most cases to change the contents of
the result boxes in the single line graphic. PowerFactory offers three ways in
which to change a result box definition:
• selecting three variables out of three predefined lists
• selecting one or more variables out of all available variables
• writing a new user defined format, using the PowerFactory output format.
Because of all these, the result boxes are used as example to introduce the
nature and use of the form editors.

As has been explained in section 7.8.6, page 7-148, the result boxes may be
right clicked to select a particular format. When this format is selected, the “Form
Select” edit dialogue pops up which shows a reference to a form for each
calculation function (load-flow, short-circuit, etc.). Editing the reference will show
the Form Editor of the current result box definition. See Fig. 25.8.
This form editor has a page to change the format by selecting variables, and a
page to manually define a format. What is displayed on which page depends on
the input mode of the Form Editor, which can be change using the button
I NPUT M ODE .
As shown in Fig. 25.9 the three modes are:

Tools & Utilities 25-505

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.8: The Form Editor

Figure 25.9: The Form Editor

Predefined Variables This mode lets the user select three variables from three
predefined lists of variables. This is visible in Fig. 25.8 as the three
listboxes at the bottom (’Line 1,2,3’).

User Selection This mode lets the user select any amount of parameters out of
all available parameters for the selected object or class of objects. This
includes model parameters as well as calculated values.

Text editor This is the most flexible, but also the most difficult mode. In this
mode, any text and any available variable, in any color, can be entered in
the Form. The highly flexible DIgSILENT output language allows for highly
complex automatic reports. This mode also offers a fast append of
predefined lines. The F ROM L IST button is used to select a variable from
the list shown in “Predefined Variables” mode. A standard line with that
variable is appended to the form. The U SER DEFINED button acts like the
input mode “User Selection” with one important difference. Where the

Tools & Utilities 25-506

DIgSILENT PowerFactory Results, Graphs and Documentation

“User Selection” mode is used to redefine the complete form text, the
U SER DEFINED button appends a line for each selected variables to the
existing form text.

N OTE : To use the “Predefined Variables” is the easiest way to select variables,
if they are accessible from the pull-down list.
If not only the standard variables should be shown, but also additional
ones shall be defined, the best way is to use the option “User Selec-
tion”.

In Fig. 25.8, the editor is in the default ‘Predefined Variables’ mode. The three
listboxes show the names of the variables [1], their units [2] and their description
[3].

The three listboxes used for the ‘Predefined Variables’ mode are replaced by a
S ELECT VARIABLES button in the ‘User Selection’ mode. Pressing this button
will pop up a ‘Monitor Variable Set’ dialogue (IntMon) which is used to define a
set of variables. The IntMon dialogue is explained in the next section.

The example in Fig. 25.8 shows that the active and reactive power at the
element Xnet have been selected as well as the loading percentage. This
selection will produce three lines of DIgSILENT output language code. This
code can be viewed by selecting the View page. The text editor in this page will
be disabled, because we are selecting a format in stead of typing in the codes
ourselves. However, it still shows the format of our selection as:

#.## $N,@:m:P:_LOCALBUS
#.## $N,@:m:Q:_LOCALBUS
#.## $N,@:c:loading

This example shows the basic syntax of the DIgSILENT output language:

• The ’#’ sign is a placeholder for generated text. In the example, each line
has a placeholder for a figure with two digits after the decimal point
(’#.##’). The first ’#’-sign stands for any whole number, not necessary
smaller than 10.

• The ’$N’ marks the end of a line. A line normally contains one or more
placeholders, separated by non-’#’ signs, but may also contain normal
text or macro commands.

• After the ’$N’, the list of variable names that are used to fill in the
placeholders have to be added. Variable names must be separated with
commas. Special formatting characters, like the ’@:’-sign, are used to
select what is printed (i.e. the name of the variable or its value) and how.

The mentioned example will produce an result box like

Tools & Utilities 25-507

DIgSILENT PowerFactory Results, Graphs and Documentation

12.34
4.84
103.56
The form editor offers options for the unit or name of the selected variable. If the
Unit-show option is enabled, a second placeholder for the unit is added:
#.## # $N,@:m:P:_LOCALBUS,@:[m:P:_LOCALBUS
#.## # $N,@:m:Q:_LOCALBUS,@:[m:Q:_LOCALBUS
#.## # $N,@:c:loading,@:[c:loading
The ‘[’-sign encodes for the unit of the variables, in stead of the value.

The same goes for the variable name, which is added as

# #.## $N,@:~m:P:_LOCALBUS,@:m:P:_LOCALBUS
# #.## $N,@:~m:Q:_LOCALBUS,@:m:Q:_LOCALBUS
# #.## $N,@:~c:loading,@:c:loading
Where the ‘~’-sign encodes for the variable name.

With both options on, the produced format line

# #.## # $N,@:~m:P:_LOCALBUS,@:m:P:_LOCALBUS,@:[m:P:_LOCALBUS
Will lead to the following text in the result box:
P 12.34 MW
Other often used format characters are ‘%’, which encodes for the full variable
description, and ‘&’, which decodes for the short description, if available.

25.4 The DIgSILENT Output Language

When more than just the variable name, value and unit has to be displayed, or if
we want to use colors, or other special formats, we have to use the DIgSILENT
Output Language.

By selecting the Text Editor input mode, all entries on first page of the Form
Editor disappear, except for the form name, and the editor on the second page is
activated. (see Fig. 25.10).
Almost all textual output that is produced in PowerFactory, is defined by a
report form. The use of report forms range from the simple and small result
forms that specify the contents of the single line result boxes to large and
complex forms that are used to print out complete system reports.

In all cases, the text in the editor field of a IntForm object specifies the report
that is to be generated. For result boxes, that text is normally created

Tools & Utilities 25-508

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.10: The Form Text Editor

automatically in the IntForm dialogue by selecting “Predefined Variables”, or any

other set of variables, and some extra’s such as the number of decimals and if
an unit or name should be shown. These options will automatically create a
report form. That automatic form is normally used as it is, but it may be altered
manually. This is shown in Fig. 25.10, where report format is changed such that
the variable name of the loading factor is deleted and replaced by the fixed text
‘ld’, because the variable name “loading” is felt too long compared with the
names of the other two variables (“P” and “Q”). The shown format will produce
result boxes like

P 12.34 MW
Q 4.84 MVAr
ld 103.56 %

Defining single line result boxes only asks for a basic understanding of the
DIgSILENT output language. For more complex reports, many different
variables from all kinds of objects have to be printed as listings or tables. Such a
report would require macro handling, container loops, selection of parameters,
headers, footers, titles, colors, etc. The DIgSILENT output language offers all
this, and more.

The basic syntax, which is primary used for defining result boxes is given in the
following overview.

Tools & Utilities 25-509

DIgSILENT PowerFactory Results, Graphs and Documentation

25.4.1 Format string, Variable names and text Lines

A standard line consists of three parts (see Fig. 25.11):

1. A format string, containing placeholders, macros and/or userdefined text.

2. An ‘end of line’ character like ’$N’, ’$E’ or ’$F’

3. Variable names, separated by commas, which are used to fill in the

placeholders.

Figure 25.11: Basic Parts of the report format

The format string is normally much longer.

Placeholders
A placeholder for strings like variable names or whole numbers is a single
’#’-sign. For real numbers, the placeholder consists of

• a single ’#’ for the integer part

• a point or comma

• one or more ’#’-signs for the fractional part

The number of ’#’-signs after the decimal point/comma defines the number of
decimals.

The ’#’-sign itself can be included in user-defined text by typing ’\#’.

Variables, Units and Names

The variable name can be used to display the name of the variable, its value or
its unit. The possible formats are (’xxx’ = name of variable):

xxx returns the value

%xxx returns the long variable name, as used in the edit dialogues

&xxx returns the short variable name, as used in the database browser

[xxx returns the unit

˜xxx the object dependent name of the variable (default name)

Tools & Utilities 25-510

DIgSILENT PowerFactory Results, Graphs and Documentation

“%width.precision,xxx” uses special formatting

The special formatting %width.precision is explained by the following

examples:

• “%.60,TITLE:sub1z” outputs TITLE:sub1z 60 column width, left aligned.

• “@:”%1.0,s:nt” inserts s:nt as an integer at the placeholder’s position

• “”%1.3,s:nt” writes s:nt with 3 digits precison at the placeholder’s position

The centering code | may be used in front of the formatting code for centering at
the placeholder, for example “|%.60,TITLE:sub1z”.

The insertion code @ is used to switch to insert mode, for example,

|#|$N,@:loc_name
will output
|aElmSym|.

The cformat string may be used to alternatively reserve place for a value or text.
A cformat of ‘%10.3’ will reserve 10 characters for a figure, with 3 decimals. The
first number can be omitted for text: ‘%.6’ will reserve 6 characters for the text
field. The cformat syntax allows for centering text by adding the ‘|’-sign to the
‘%’-sign:
‘|%.10’ will reserve 10 characters and will center the text.

Free, language dependent text can be defined by use of the format

{E|a text;G|ein Text}. This will produce ‘a text’ when the user has selected
the English language (see the user settings dialogue), and ‘ein Text’ when the
language has been chosen to be German.

Special commands for access of Elements

OBJECT(cls) Gets Element of class cls. Used to access a variable name or unit
without actually accessing such an object. Used in header lines.

argument: cls (obligatory): The name of the class

example: [OBJECT(StaBar):m:Skss
writes the unit of the busbar variable Skss

EDGE Gets an arbitrary object with at least one connection, i.e. a Load, a Line,
etc. Used to access a variable name or unit without actually accessing
such an object.

example: %EDGE:m:U1:bus1
writes description of the variable U1

CUBIC(idx) Returns the cubicle (StaCubic) at bus index idx of branch

Tools & Utilities 25-511

DIgSILENT PowerFactory Results, Graphs and Documentation

argument: idx: index of branch, the currently set bus index is used when
idx¡0
example: CUBIC(0):e:loc_name
returns name of cubicle at busindex 0

TITLE Gets the title that is set in the output command (ComSh or ComDocu)

example: TITLE:e:annex
writes annex of title

VARIANT Gets the active variant in which the current object is stored

example: VARIANT:e:loc_name
writes the name of the variant

NET: Gets the grid in which the current object is stored

example: NET:e:loc_name
writes the name of the grid

CMD: Returns the last calculation command, i.e. a Short-Circuit (ComShc),

Load-flow (ComLdf),...

example: CMD:pabs
writes the short circuit position on the line after calculation of a
short-circuit.

CASE: Returns the currently active calculation case

example: CASE:e:loc_name
writes the name of the active calculation case

DEF: Returns the default object. The default object depends on the currently
processed output.

example: DEF:e:loc_name
writes the name of the default object

STALNE: Returns the station if the current object is a busbar. Returns a line if
the current object is a terminal between line routes. Otherwise, nothing is
returned, and the entry will be ignored.

example: STALNE:e:locname
writes the name of the line or station.

RES: Returns the currently active results object (ElmRes) used by simulation,
harmonics or other calculation modules

example: RES:e:desc
writes the first line of the description of the results object

Tools & Utilities 25-512

DIgSILENT PowerFactory Results, Graphs and Documentation

Colour
A line can be set to another color by adding a ’_LCOL(c)’ command directly after
the ’$N,’ marker. This will color the whole line according to the color number c:

a black i gray
b black j lightgray
c red k bordeaux
d green l darkred
e blue m darkgreen
f brown n lightgreen
g cyan o marine
h magenta p darkblue

A single item can be coloured by using the ‘ COLOR(Variable name; color

code)’.

25.4.2 Advanced Syntax Elements

The advanced syntax is mainly used for writing forms for larger and more
complex reports. An example is a short-circuit result form, which lists all the
short-circuit parameters for all busbars and for each busbar for all connected
elements.

Line Types and Page Breaks

The character ‘$’ ends a format line. A line without this ending will be interpreted
as a normal ‘$N’ line type. The following line type are available:

’$N’ Normal line

’$H’ Header on the top of each page

’$F’ Footer on the bottom of each page

’$T’ Title line, only appears on top of the first page

’$C’ Comment line (not used for output)

’$R’ Marker that make that the line will only be used when the specified results
are valid

The line type ’$H’, ’$F’ and ’$T’ will be treated as normal (’$N’) line types
when used inside a loop command. Line type codes may be made language
dependent by adding a ’E’, for English lines or a ’G’ for German lines, i.e.
’$HG’ specifies a German header line.

Tools & Utilities 25-513

DIgSILENT PowerFactory Results, Graphs and Documentation

A report format must at least contain one normal ($N) line.

The following commands are used for page and line controls. They can only be
used directly behind the line type codes ‘$N’, ‘$F’ or ‘$H’.

PAGEBREAK Forces a page break after the current line

AVAILBREAK Enables page breaking after the current line (default)

NOBREAK Disables page breaking directly after the current line

LCOL(c) Changes the colour of the current line, c is the colour code.

OBJ(ClsNam) The current line will only be used for objects from the class
“ClsNam”.

BUS(inum) The current line will only be used for objects which connect to
exactly inum nodes

FIRST The current line will only be used when the loop index is 0 (first passage)

NFIRST The current line will only be used when the loop index is not 0 (all but
the first passages)

IF(boolean expression) The current line will only be written when the
expression is true. Example: _IF(m:u:bus1>0.95)

IFNOT(boolean expression) The current line will only be written when the
expression is false. Example: \IF(m:u:bus1<0.95)

Example:

| #.## # #.## # #.## |$R,_NOBREAK, ...

Predefined Text Macros

The following macros will produce specific names or other texts.

DATE(c) present date: c=’e’ give the English format, c=’g’ the German one.

TIME present time

VERSION version number of the DIgSILENT PowerFactory software.

BUILD build number of the DIgSILENT PowerFactory software.

VERBUILD combines VERSION and BUILD

ORDER order title, if a title has been defined previously

CLASS class name of the object

Tools & Utilities 25-514

DIgSILENT PowerFactory Results, Graphs and Documentation

LINE current line number in page

ALLLINE current line number in report

PAGE current page number

LOCALBUS name of the local busbar

CALC(c) name of last performed calculation. c=1 returns a long description.

SHORT short object name

FSHORT short name of parent object

CLS class name without the ‘Elm’, ‘Sta’, ‘Typ’, etc. part.

ANNEX the annex number

NGB neighborhood depth

TEXT(E | text;G | Text) language dependent text (E=English, G=German)

Object Iterations, Loops, Filters and Includes

To create a report that creates a table with the voltages for all busbars, command
are needed to filter the busbar objects and to create a loop that outputs a line of
text for each busbar. A loop or filter command consists of the following parts:

• the keyword “$LOOP” or “$CLOOP”

• the filter or loop name

• the format text

• the keyword “$END”

Example:

$LOOP,_LROUTES()
| # |,$N,loc_name
$END

This example uses the filter “_LROUTES()”, which filters line route objects
(ElmLneroute). The format text has one line, which prints the object name.

Tools & Utilities 25-515

DIgSILENT PowerFactory Results, Graphs and Documentation

25.5 The Output of Device Data

The ComDocu command (“Output of Device Data”) is used to produce an

output of device data. The output can be used in reports or may help to check
the entered data. Reports of calculated results can be made with the ComSh
command. See section 25.6, page 25-517 for more information.

There are two types of reports. These are either the “Short Listing” or the
detailed report. The “Short Listing” is not defined for all elements.

25.5.1 The Short Listing

The “Short Listing” reports only the most important device data. Each element in
the report needs only one line for the output. This allows a small but clear
documentation. Like the “Output of Results” the “Short Listing” report uses a
form to generate the output. This form can be modified by the user. When the
report form is changed, it is stored in the “Changed Settings” object of the active
project. This does not influence the reports of other projects. The output of
objects without a defined short listing will produce warnings like:
DIgSI/wrng - Short Listing report for StoMaint is not defined.

25.5.2 The Detailed Report

The detailed report outputs all device data of the elements selected for output. In
addition, type data can be included (“Print Type Data in Element”). Device Data
is split into the different calculation functions like “Load-Flow” or “Short Circuit”.
The “Basic Data” is needed in all the different calculations. “Selected Functions”
shows a list of the functions whose data will be output. If you want to report the
device data for all functions move all functions from left to right. If “Selected
Functions” is empty no device data will be output.

Device Data
Use Selection The set of reported elements depends on the “Use Selection”
setting. If “Use Selection” is checked one element or a “Set” object must be
chosen for output. If “Use Selection” is not checked the “Filter/Annex” page
specifies the set of elements for the report. This page is described further
down. Another way to select object for the report is to select the objects in
the “Data Manager” or the “Single Line” graphics and select
“Documentation” in the “Output” entry of the context menu. The “Output of
Device Data” command will pop up.
Annex Each class uses it’s own annex. There is either the default annex or the
individual annex. To use the default annex check “Use default Annex”.

Tools & Utilities 25-516

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.12: Device data page

Changes of the annex are stored in the “Changed Settings” of the active
project. The local annex is stored in the “Output of Device Data” command.
To modify the local annex press the “Change Annex” button. See section
25.7, page 25-519 for details.

Title Most reports display a title on top of each page. The reference “Title”
defines the contents of the header.

Filter/Annex
If one wants to report elements without defining a set of objects “Use Selection”
on the “Device Data” page must not be checked. The objects in the list “Selected
Objects” will be filtered out of the active projetcs/grids and reported. “Available
Objects” shows a list of elements which can be add to the “Selected Objects” list.
The list in “Available Objects” depends on the “Elements” radio button. Elements
in the left list are moved to the right by double-clicking them. The text in the
“Annex” input field will be set as default annex for the selected class.

25.6 Output of Results

The command ComSh (“Output of Results”) is used to produce an output of

calculation results. The output can be used in reports or may help in interpreting

Tools & Utilities 25-517

DIgSILENT PowerFactory Results, Graphs and Documentation

Figure 25.13: Filter/Annex page

Figure 25.14: Output of results

the results. To generate a report with input data use the ComDocu command
(“Output of device data”, see section 25.5, page 25-516).

Several different reports, depending on the actual calculation, can be created.

The radio button on the upper left displays the different reports possible for the

Tools & Utilities 25-518

DIgSILENT PowerFactory Results, Graphs and Documentation

active calculation (Fig. 25.14 shows a load-flow). Some reports may be inactive,
depending on the object(s) chosen for output. In Fig. 25.14, a station was
selected for output. “Used Format” displays the format(s) used for the report.
Some reports are a set of different outputs. For these reports more than one
form is shown. If the form is modified it will be stored automatically in the
“Changed Settings” folder of the active project. The changed form does not
influence the reports of other projects. If “Use Selection” is active a set of objects
(selection) or a single object must be chosen. The report is generated only for
these elements. All relevant objects are used if “Use Selection” is not selected.
The relevant objects depend on the chosen report. Most reports display a title on
top of each page. The reference “Title” defines the contents of the header.

For some reports additional settings are required. These settings depend on the
chosen report, the selected objects for output and the calculation processed
before. The calculation (left top) and the used format(s) (right top) are always
shown.

25.7 The Annex for Documentation

The “Annex for Documentation” stores the annex for the documentation of
results. The annex number and the page number for the first page are unique for
each class.

Figure 25.15: The annex dialogue

Objects This column shows the different classes with their title.
Annex This column stores the annex number shown in the Annex field of the
report.

Tools & Utilities 25-519

DIgSILENT PowerFactory Results, Graphs and Documentation

First Page This column defines the start page for the class in the report. The
first page number depends on the class of the first element output in your
report. The page number of its class is the page number of the first page.

Tools & Utilities 25-520

DIgSILENT PowerFactory DPL

Chapter 26

DPL

The DIgSILENT Programming Language DPL serves the purpose of offering an

interface for automating tasks in the PowerFactory program. The DPL method
distinguishes itself from the command batch method in several aspects:
• DPL offers decision and flow commands
• DPL offers the definition and use of user-defined variables
• DPL has a flexible interface for input-output and for accessing objects
• DPL offers mathematical expressions

The DPL adds a new dimension to the DIgSILENT PowerFactory program by

allowing the creation of new calculation functions. Such user-defined calculation
commands can be used in all areas of power system analysis, such as
• Network optimizing
• Cable-sizing
• Protection coordination
• Stability analysis
• Parametric sweep analysis
• Contingency analysis
• etc. etc.

Such new calculation functions are written as program scripts which may use
• Flow commands like ‘if-then-else and ‘do-while’
• PowerFactory commands (i.e. load-flow or short-circuit commands)
• Input and output routines
• Mathematical expressions
• PowerFactory object procedure calls
• Subroutine calls

Tools & Utilities 26-521

DIgSILENT PowerFactory DPL

26.1 The DPL Command Object

The DPL command object ComDpl holds a reference to a remote DPL

command when it is not a root command. The example depicted in Fig. 26.1 is
apparently a referring command, since its “DPL script” reference is set to the
remote command \L IBRARY\DPL C OMMANDS\C HECK VL OADING.

Figure 26.1: A DPL command

• A root command has its own script on the “script” page of the dialogue.

• A referring command uses the script of the remote DPL command.

Creating a new DPL Command

A DPL Command ComDpl can be created by using the ”New Object” ( )
button in the toolbar of the data manager and selecting DPL Command and
more. Then press OK and a new DPL command is created. The dialogue is
now shown and the parameters, objects and the script can now be specified.

This dialogue is also opened by double-clicking a DPL script, by selecting Edit

from the context sensitive menu or by selecting the script from the list when
pressing the button .

Tools & Utilities 26-522

DIgSILENT PowerFactory DPL

Defining a DPL Commands Set

The DPL command holds a reference to a selection of objects (General
Selection). At first this general selection is empty, but there are several ways to
define a special set of object used in the DPL command. This “DPL Commands
Set” (SetSelect) can be specified through:

Select one or more elements in the single line diagram. Then right-click the
selection (one of the selected elements) and choose the option
Define...→DPL Commands Set... from the context sensitive menu.

It is also possible to select several elements in the data manager.

Right-click the selection and choose the option Define...→DPL Commands
Set... from the context sensitive menu.

Executing a DPL Command

To execute a DPL command or to access the dialogue of a script, the button
can be activated. This will pop up a list of available DPL scripts from the global
and local library.

The easiest way to start a DPL command AND define a selection for it is

to select one or more elements in the single line diagram or in the data
manager and then right-click the selection.

Choose the option Execute DPL Scripts from the context sensitive menu.

Then select a DPL script from the list. This list will show DPL scripts from
the global as well as from the local library.

Select a DPL script, insert/change the variables and then press the button
E XECUTE

In this way the selection is combined into a DPL Commands Set and the set is
automatically selected for the script chosen.

Only one single DPL command set is valid at a time for all DPL scripts. This
means that setting the DPL command set in one DPL command dialogue, will
change the DPL command set for all DPL commands in the database.

N OTE : To choose different sets for various DPL scripts you can either use
different selection object SetSelect like the “General Set”. Or new DPL
command sets can be created and selected inside the active study
case. This is done by pressing , selecting “other” and the element
“Set (SetSelect)” and then selecting the set type.

Tools & Utilities 26-523

DIgSILENT PowerFactory DPL

The interface section Input Parameters is used to define variables that are
accessible from outside the DPL command itself. DPL commands that call other
DPL commands as subroutines, may use and change the values of the interface
variables of these DPL subroutines.

The list of External Objects is used to execute the DPL command for specific
objects. A DPL command that, for example, searches the set of lines for which a
short-circuit causes too deep a voltage dip at a specific busbar, would access
that specific busbar as an external object. Performing the same command for
another busbar would then only require setting the external object to the other
busbar.

DPL Advances Options

On the Advanced Options page a Remote script can be selected, which is then
used by this script instead of a local defined script on the next page Script. This
is a so called “referring command”. The “root command” as described above in
the example uses the local defined script.

Also there can be Result parameters defined. These parameters are results
from the script and they are stored inside the result object. Hence it is possible
to access them through the variable monitor and display them in a plot.

DPL Script Page

The most important part of a DPL root command is of course the actual DPL
program script. That script is written on the Script page of a DPL root command
dialogue, if no Remote script is selected.

On this page you will see the DPL code of a already defined script and/or you
can insert new command lines for modifying this script or writing a new script.
The available commands and the DPL language are described in the following
sections.

The edited program code also features a highlighting specially suited for
handling DPL scripts.

26.2 The DPL Script Editor

There is also an own editor available for conveniently writing a DPL script. To
activate this editor press the button on the bottom side of the Script page of
a DPL command dialogue.

Now a new window will be opened in PowerFactory. Here the script can be

Tools & Utilities 26-524

DIgSILENT PowerFactory DPL

written in a very convenient way similar to the programming language C++. The
highlighting will be activated automatically.

There are several tools which can be used in this editor:

With this button “Edit Object” the edit dialogue of the script is opened and
you can C HECK your script for errors or you can E XECUTE it.

The script inside the editor and in the dialogue are synchronised each time
you save the script or the script is edited in the dialogue. If this
“Disconnect” button is pressed, the scripts will not be synchronised
anymore.

With the “search” button you can activate a Find, a Replace or also a Go
To function inside the editor.

With the “search next” button find/replace/go to the next matching word.

With the “search previous” button find/replace/go to the previous matching

word.

With the these buttons bookmarks can be set in the editor. You can also
jump from one bookmark to the next or previous as well as clear all
bookmarks.

When finished editing, press the button and the script will be synchronised
with the main dialogue. You can also jump to the main graphics board by
selecting the option Window→Graphic ... form the main menu.

26.3 The DPL Script Language

The DPL script language uses a syntax quite similar to the C++ programming
language. This type of language is intuitive, easy to read, and easy to learn. The
basic command set has been kept as small as possible.

The syntax can be divided into the following parts:

• variable definitions

• assignments and expressions

• program flow instructions

• method calls

Tools & Utilities 26-525

DIgSILENT PowerFactory DPL

The statements in a DPL script are separated by semicolons. Statements are

grouped together by braces.

Example:
statement1;
statement2;
if (condition) {
groupstatement1;
groupstatement2;
}

26.3.1 Variable Definitions

DPL uses the following internal parameter types
• double, a 15 digits real number

• int, an integer number

• string, a string

• object, a reference to a PowerFactory object

• set, a container of objects

Vectors and Matrices are available as external objects.

The syntax for defining variables is as follows:

[VARDEF] = [TYPE] varname, varname, ..., varname;

[TYPE] = double | int | object | set

All parameter declarations must be given together in the top first lines of the DPL
script. The semicolon is obligatory.

Examples:
double Losses, Length, Pgen;
int NrOfBreakers, i, j;
string txt1, nm1, nm2;
object O1, O2, BestSwitchToOpen;
set AllSwitches, AllBars;

26.3.2 Constant parameters

DPL uses constant parameters which cannot be changed. It is therefore invalid
to assign a value to these variables. Doing so will lead to an error message.

Tools & Utilities 26-526

DIgSILENT PowerFactory DPL

The following constants variables are defined in the DPL syntax:

SEL is the general DPL selection.

NULL is the ’null’ object

this is the DPL command itself

Besides these global constants, all internal and external objects are constant too.

26.3.3 Assignments and Expressions

The following syntax is used to assign a value to a variable:

variable = expression
variable += expression
variable -= expression

The add-assignment “+=” adds the right side value to the variable and the
subtract-assignment “-=” subtracts the right-side value.

Examples:

double x,y;
x = 0.5*pi(); ! x now equals 1.5708
y = sin(x); ! y now equals 1.0
x += y; ! x now equals 2.5708
y -= x; ! y now equals -1.5708

The following operators and functions are available:

• Arithmetic operators: +, -, *, /

• Standard functions:
sin(x) cos(x) tan(x) asin(x)
acos(x) atan(x) sinh(x) cosh(x)
tanh(x) exp(x) ln(x) log(x) (basis 10)
abs(x) min(x,y) max(x,y) sqrt(x) (square root)
trunc(x) frac(x) round(x) sqr(x) (power of 2)
pow(x,y) modulo(x,y) ceil(x) floor(x)
where all trigonometric functions are based on radians (RAD).

• Constants:
pi() π
twopi() 2π
e() e

Tools & Utilities 26-527

DIgSILENT PowerFactory DPL

26.3.4 Program Flow Instructions

The following flow commands are available.

if ( [boolexpr] ) [statlist]
if ( [boolexpr] ) [statlist] else [statlist]
do [statlist] while ( [boolexpr] )
while ( [boolexpr] ) [statlist]
for ( statement ; [boolexpr] ; statement ) [statlist]

in which

[boolexpr] = expression [boolcomp] expression

[boolcomp] = ”<” | ”>” | ”=” | ”>=” | ”>=” | ”<>”
[statlist] = statement; | { statement; [statlist] }

• Unary operators: ”.not.”

• Binary operators: ”.and.” | ”.or.” | ”.nand.” | ”.nor.” | ”.eor.”

• Parentheses: {logical expression}

Examples:

if (a<3) {
b = a*2;
}
else {
b = a/2;
}

while (sin(a)>=b*c) {
a = O:dline;
c = c + delta;
}

if ({.not.a}.and.{b<>3}) {
err = Ldf.Execute();
if (err) {
Ldf:iopt_lev = 1;
err = Ldf.Execute();
Ldf:iopt_lev = 0;
}
}

for (i = 0; i < 10; i = i+1){

x = x + i;

Tools & Utilities 26-528

DIgSILENT PowerFactory DPL

for (o=s.First(); o; o=s.Next()) {

o.ShowFullName();
}

Break and Continue

The loop statements ‘do-while’ and ‘while-do’ may contain ‘break’ and ‘continue’
commands. The ‘break’ and ‘continue’ commands may not appear outside a
loop statement.

The ‘break’ command terminates the smallest enclosing ‘do-while’ or ‘while-do’

statement. The execution of the DPL script will continue with the first command
following the loop statement.

The ‘continue’ command skips the execution of the following statements in the
smallest enclosing ‘do-while’ or ’while-do’ statement. The execution of the DPL
script is continued with the evaluation of the boolean expression of the loop
statement. The loop statement list will be executed again when the expression
evaluates to TRUE. Otherwise the loop statement is ended and the execution will
continue with the first command following the loop statement.

Examples:

O1 = S1.First();
while (O1) {
O1.Open();
err = Ldf.Execute();
if (err) {
! skip this one
O1 = S1.Next;
continue;
}
O2 = S2.First();
AllOk = 1;
DoReport(0); !reset
while (O2) {
err = Ldf.Execute();
if (err) {
! do not continue
AllOk = 0;
break;
} else {
DoReport(1); ! add
}

Tools & Utilities 26-529

DIgSILENT PowerFactory DPL

O2 = S2.Next();
}
if (AllOk) {
DoReport(2); ! report
}
O1 = S1.Next();
}

26.3.5 Input and Output

The “input” command asks the user to enter a value.

input(var, string);

The input command will pop up a window with the string and an input line on
which the user may enter a value. The value will be assigned to the variable
“var”.

The “output” command writes a line of text to the output window.

output(string);

The string may contain “=”-signs, followed by a variable name. The variable
name will then be replaced by the variable’s value.

Example:

input(diameter, ’enter diameter’);

output(’the entered value=diameter’);

The example results in the pop up of a window as depicted inFig. 26.2.

Figure 26.2: The input window

The following text will appear in the output window:

DIgSI/dpl - the entered value=12.3400

The output command is considered obsolete and has been replaced by the more
versatile “printf” and “sprintf” functions.

Tools & Utilities 26-530

DIgSILENT PowerFactory DPL

26.4 Access to Other Objects

With the syntax for the parameter definitions, program flow and the input and
output, it is already possible to create a small program. However, such a script
would not be able to use or manipulate variables of ‘external’ objects. It would
not be possible, for instance, to write a script that replaces a specific line by
possibly better alternatives, in order to select the best line type. Such a script
must be able to access specific objects (the specific line) and specific sets of
objects (the set of alternative line types).

The DPL language has several methods with which the database objects and
their parameters become available in the DPL script:
• The most direct method is to create an object, or a reference to an object,
in the DPL command folder itself. Such an object is directly available as
“object” variable in the script. The variable name is the name of the object
in the database.
• The DPL command set may be used. This method is only useful when the
order in which the objects are accessed is not important. The DPL
command set is automatically filled when a selection of elements is
right-clicked in either the single line graphic or the data manager and the
option Execute DPL Script is selected.
• The list of external objects is mainly used when a script should be
executed for specific objects or selections. The list of external objects is
nothing more than a list of ‘aliases’. The external object list is used to
select specific objects for each alias, prior to the execution of the script.

26.4.1 Object Variables and Methods

If a database object is known to the DPL command, then all its methods may be
called, and all its variables are available. For example, if we want to change a
load-flow command in order to force an asymmetrical load-flow calculation, we
may alter the parameter “iopt net”. This is done by using an assignment:
Ldf:iopt_net = 1; ! force unbalanced
In this example, the load-flow objects is known as the objects variable “Ldf”.

The general syntax for a parameter of a database object is

objectname:parametername

In the same way, it is possible to get a value from a database object, for instance
a result from the load-flow calculations. One of such a result is the loading of a
line object, which is stored in the variable “c:loading”. The following example
performs the unbalanced load-flow and reports the line loading:

Tools & Utilities 26-531

DIgSILENT PowerFactory DPL

00. int error;

01. double loading;
02. Ldf:iopt_net = 1; ! force unbalanced
03. error = Ldf.Execute(); ! execute load-flow
04. if (error) {
05. exit();
06. } else {
07. loading = Line:c:loading; ! get line loading
08. output(’loading=loading’); ! report line loading
09. }

This examples is very primitive but it shows the basic methods for accessing
database objects and their parameters.

26.5 Access to Locally Stored Objects

Locally stored objects (also called ’internal objects’) can be accessed directly.
They are known in the DPL script under their own name, which therefore must
be a valid DPL variable name. It will not be possible to access an internal object
which name is “My Load-flow\~{}1*”, for instance.

Internal objects may also be references to objects which are stored elsewhere.
The DPL command does not distinguish between internal objects and internal
references to objects.

An example is shown in Fig. 26.3, where a DPL script is shown on the left which
has a load-flow command and a reference to a line in its contents folder on the
right.

Figure 26.3: DPL contents

The example DPL script may now access these objects directly, as the objects
“Ldf” and “Line”. In the following example, the object “Ldf”, which is a load-flow
command, is used in line 01 to perform a load-flow.

00. int error;

01. error = Ldf.Execute();
02. if (error) {

Tools & Utilities 26-532

DIgSILENT PowerFactory DPL

03. output(’Load-flow command returns an error’);

04. exit();
05. }

In line 01, a load-flow is calculated by calling the method “Execute()” of the

load-flow command. The details of the load-flow command, such as the choice
between a balanced single phase or an unbalanced three phase load-flow
calculation, is made by editing the object “Ldf” in the database. Many other
objects in the database have methods which can be called from a DPL script.

The DPL contents are also used to include DPL scripts into other scripts and
thus to create DPL “subroutines”.

26.6 Accessing the General Selection

Accessing database objects by storing them or a reference to them in the DPL

command would create a problem if many objects have to be accessed, for
instance if we want to search the line with the highest loading. It would be
impractical to create a reference to each and every line.

A more elegant way would be to use the DPL global selection and fill it with all
lines. The data manager offers several ways in which to fill this object DPL
Command Set with little effort. The selection may then be used to access each
line indirectly by a DPL “object” variable. In this way, we may create a loop in
which we search for the highest loading. This is shown in the following example.

00. int error;

01. double max;
02. object O, Omax;
03. set S;
04.
05. error = Ldf.Execute(); ! execute a load-flow
06. if (error) exit(); ! exit on error
07.
08. S = SEL.AllLines(); ! get all selected lines
09. Omax = S.First(); ! get first line
10. if (Omax) {
11. max = Omax:c:loading; ! initialize maximum
12. } else {
13. output(’No lines found in selection’);
14. exit(); ! no lines: exit
15. }
16. O = S.Next(); ! get next line
17. while (O) { ! while more lines

Tools & Utilities 26-533

DIgSILENT PowerFactory DPL

18. if (O:c:loading>max) {
19. max = O:c:loading; ! update maximum
20. Omax = O; ! update max loaded line
21. }
22. O = S.Next();
23. }
24. output(’max loading=max for line’); !output results
25. Omax.ShowFullName();

The object SEL used in line 08 is the reserved object variable which equals the
General Selection in the DPL command dialogue. The SEL object is available in
all DPL scripts at all times and only one single “General Selection” object is valid
at a time for all DPL scripts. This means that setting the General Selection in
the one DPL command dialogue, will change it for all other DPL commands too.

The method “AllLines()” in line 08 will return a set of all lines found in the general
selection. This set is assigned to the variable “S”. The lines are now accessed
one by one by using the set methods “First()” and “Next()” in line 09, 16 and 22.

The line with the highest loading is kept in the variable “Omax”. The name and
database location of this line is written to the output window at the end of the
script by calling “ShowFullName()”.

26.7 Accessing External Objects

The DPL contents make it possible to access external object in the DPL script.
The special general selection object (“SEL”) is used to give all DPL functions and
their subroutines access to a central selection of objects. i.e. the DPL Command
Set.

Although flexible, this method would create problems if more than one specific
object should be accessed in the script. By creating references to those objects
in the DPL command itself, the DPL command would become specific to the
current calculation case. Gathering the objects in the general selection would
create the problem of selecting the correct object.

To prevent the creation of calculation-specific DPL commands, it is

recommended practice to reserve the DPL contents for all objects that really
‘belong’ to the DPL script and which are thus independent on where and how the
script is used. Good examples are load-flow and short-circuit commands, or the
vector and matrix objects that the DPL command uses for its computations.

If a DPL script must access a database object dependent on where and how the
DPL script is used, an “External Object” must be added to the external object list

Tools & Utilities 26-534

DIgSILENT PowerFactory DPL

in the DPL root command. Such an external object is a named reference to an

external database object. The external object is referred to by that name.
Changing the object is then a matter of selecting another object.

In Fig. 26.4, an example of an external object is given. This external object may
be referred to in the DPL script by the name “Bar1”, as is shown in the example.

Figure 26.4: DPL external object table

Example:

sagdepth = Bar1:u;

26.8 Remote Scripts and DPL Command

Libraries

To understand the DPL philosophy and the resulting hierarchical structure of

DPL scripts, the following is important to understand:

• A DPL command either executes its own script or the script of another,
remote, DPL command. In the first case, the DPL command is called a
‘root command’ and the script is called a ‘local script’. In the second
case, the DPL command is called a ‘referring’ command and the script is
called a ’remote script’.

• A root command may define interface variables that are accessible from
outside the script and which are used to define default values.

• Each root command may define one or more external objects. External
object are used to make a DPL command run with specific power system
objects, selections, commands, etc.

• A referring command may overrule all default interface values and all
selected external objects of the remote command.

Tools & Utilities 26-535

DIgSILENT PowerFactory DPL

• Each DPL command can be called as a subroutine by other DPL

commands.

The use of remote scripts, external objects and interface variables makes it
possible to create generic DPL commands, which may be used with different
settings in many different projects and study cases.

The easiest way to develop a new DPL command is to create a new ComDpl in
the currently active study case and to write the script directly in that DPL object.
In such a way, a DPL “root command” is made. If this root command needs DPL
subroutines, then one or more DPL command objects may be created in its
contents. Each of these subroutines will normally also be written as root
functions.

The newly written DPL command with its subroutines may be tested and used in
the currently active study case. However, it cannot be executed when another
study case is active. In order to use the DPL command in other study cases, or
even in other projects, we would have to copy the DPL command and its
contents. This, however, would make it impossible to alter the DPL command
without having to alter all its copies.

The solution is in the use of ‘remote scripts’. The procedure to create and use
remote scripts is described as follows.

Suppose we have created and tested a new DPL command in the currently
active study case. We would like to store this DPL command in a save place and
make it possible to use it in other study cases and projects.

This is done by the following steps:

• copy the DPL command to a library folder. This will also copy the contents
of the DPL command, i.e. with all it’s DPL subroutines and other locally
stored objects.

• “Generalize” the copied DPL command by resetting all project specific

external objects. Set all interface variable values to their default values. To
avoid deleting a part of the DPL command, make sure that if any of the
DPL (sub)commands refers to a remote script, all those remote scripts are
also stored in the library folder.

• Activate another study case.

• Create a new DPL command object (ComDPL) in the active study case.

• Set the “DPL script” reference to the copied DPL command.

• Select the required external objects.

• Optionally change the default values of the interface variables

Tools & Utilities 26-536

DIgSILENT PowerFactory DPL

• Press the C HECK button to check the DPL script

The C HECK or E XECUTE button will copy all parts of the remote script in the
library that are needed for execution. This includes all subroutines, which will
also refer to remote scripts, all command objects, and all other objects. Some
classes objects are copied as reference, other classes are copied completely.

The new DPL command does not contain a script, but executes the remote
script. For the execution itself, this does not make a change. However, more
than one DPL command may now refer to the same remote script. Changing the
remote script, or any of its local objects or sub-commands, will now change the
execution of all DPL commands that refer to it.

26.8.1 Subroutines and Calling Conventions

A DPL command object may be included in the contents of another DPL
command. In that case, the included DPL “subroutine” may be called in the
script of the enclosing DPL command. In principle, this is not different from
calling, for example, a load-flow command from a DPL script.

As with most other command objects, the DPL command only has one method:

int Execute() ; executes the DPL script.

The difference is that each DPL subroutine has different interface parameters,
which may be changed by the calling command. These interface parameters can
also be set directly at calling time, by providing one or more calling arguments.
These calling arguments are assigned to the interface parameters in order of
appearance. The following example illustrates this.

Suppose we have a DPL sub-command “Sub1” with the interface section as

depicted in Fig. 26.5.

Figure 26.5: Interface section of subroutine

The calling command may then use, for example:

! set the parameters:

Sub1:step = 5.0;
Sub1:Line = MyLine;

Tools & Utilities 26-537

DIgSILENT PowerFactory DPL

Sub1:Outages = MySelection;
! execute the subroutine:
error = Sub1.Execute();
However, using calling arguments, we may also write:
! execute the subroutine:
error = Sub1.Execute(5.0, MyLine, MySelection);

26.9 DPL Functions and Subroutines

The DPL syntax is very small because it mainly serves the purpose of basic
operations like simple calculations, if-then-else selections, do-while loops, etc..

The strength of the DPL language is the possibility to call functions and to create
subroutines. A function which can be called by a DPL command is called a
“method”. Four types of methods are distinguished:
Internal methods These are the build-in methods of the DPL command. They
can always be called.

Set methods These methods are available for the DPL ‘set’ variables.

Object methods These methods are available for the DPL ‘object’ variables.

External methods These are the methods which are available for certain
external PowerFactory objects, such as the load-flow command, the line
object, the asynchronous machine, etc.

26.9.1 DPL Internal Methods

The DPL program language has a small set of DPL-specific internal commands:

Exe Executes a command

AllRelevant Returns all calculation relevant objects
ClearCommands Clears the command pipe
ClearOutputs Clears the output window
Delete Deletes the object
Format String Syn- Uses same format string for all syntax
tax
printf Outputs a formatted string
sprintf Returns a formatted string
fprintf Outputs a formatted string to a file
Write Writes a report
Error Outputs a formatted error

Tools & Utilities 26-538

DIgSILENT PowerFactory DPL

Warn Outputs a formatted warning

Info Outputs a formatted information
EchoOn Re-activates the user interface
EchoOff Freezes (de-activates) the user-interface
NoFinalUpdate Prevents “EchoOn()” at end of execution
strstr Searches for a substring in a string
strcpy Copies a substring from a string
strcmp Compares two strings
strlen Returns the length of a string
strtok Finds a token in a string
strftime Creates a formatted time string
sscanf Assigns fields in string and returns number of fields
fscanf Assigns fields in file and returns number of fields
ActiveCase Returns the active calculation case
SummaryGrid Returns the summary grid
ActiveProject Returns the active project
validLDF Checks for a valid load-flow result
validRMS Checks for a valid simulation result
validSHC Checks for a valid short-circuit result
validSIM Checks for a valid simulation result
SetLineFeed Sets the automatic line feed for “printf()”
GetPageLen Returns the number of lines per page
GetCaseObject Returns the found class object from current case
GetCaseCommand Returns default command objects
GetGraphBoard Returns the currently active Graphics Board
GetTime Returns current processor time
GetLanguage Returns the current language
GetLocalLib Returns a local library folder
GetGlobalLib Returns a global library folder
PostCommand Adds a command to the command pipe
ResIndex Returns column number of variable in result object
GetResData Returns a value from a certain result curve
ResNval Returns number of values stored in certain result curve
ResNvars Returns the number of variables (columns) in result file
LoadResData Loads the data of a result file in memory
ResetCalculation Resets the calculations
fopen Opens a file from a path
fclose Closes an open file
Random Returns a random number
SetRandSeed Initializes the random number generator
fRand Returns a stochastic number according to a probability distribution

More information and detailed descriptions as well as examples of the usage of

these commands can be found in the on-line manual.

Tools & Utilities 26-539

DIgSILENT PowerFactory DPL

26.9.2 DPL Set Methods

Set methods are functions for the set type parameters.

set . [SETMETHOD] ( arguments ) ;

The following [SETMETHOD] methods are available:

Add Adds an object

Remove Removes an object
Clear Removes all objects from the set
First Returns the first objects
Next Returns the next object
Firstmatch Returns the first matching object
Nextmatch Returns the next matching object
FirstFilt Returns the first matching object
NextFilt Returns the next matching object
IsIn Searches for an object in the set
Count Returns the number of stored objects
Obj Returns the object at index i
SortToVar Sorts the objects to a variable value
SortToClass Sorts the objects to their class
SortToName Sorts the objects to their names
MarkInGraphics Marks the objects in the graphic

More information and detailed descriptions as well as examples of the usage of

these commands can be found in the on-line manual.

26.9.3 DPL Object Methods

The object methods are specific for each type of object class. A result file object
(ElmRes), for instance, has a “Write” method, which would not make sense for a
load-flow command object.

The general syntax for an object method equals that of the set method:

object . [OBJMETHOD] ( arguments ) ;

The following overview lists all the non-specific [OBJMETHOD] methods which
are available for all classes.

CreateObject Creates a new object

ShowFullName Prints the full database path and name
GetFullName Returns the full database path and name
GetContents Returns the stored objects
GetClass Returns the class name of an object
IsClass Checks for a certain class

Tools & Utilities 26-540

DIgSILENT PowerFactory DPL

GetParent Returns the parent folder

GetNode Returns the node(s) connected to an object
IsNode Checks if the object is a busbar or terminal
GetCubicle Returns the object’s cubicle
HasResults Returns if the object has result parameters
GetConnectedElms Returns the set of connected elements
GetConnectionCountReturns the number of electrical connections
Edit Opens the object dialogue
Move Moves an objects to this folder
AddCopy Adds a copy of an object
IsRelevant Returns if the object is used for calculations
IsOutOfService Returns if the object is out of service
IsInFeeder Returns if the object belongs to the feeder
VarExists Checks a variable name
GetSize Get the size of a vector or matrix variable
GetVal Returns the value of a parameter
lnm Returns the long name of a variable
snm Returns the short name of a variable
unm Returns the unit of a variable
Unom Returns the nominal voltage
Inom Returns the nominal current
MarkInGraphics Marks the object in the graphic
StochEvt Returns the first or the next state of a stochastic object

More information and detailed descriptions as well as examples of the usage of

these commands can be found in the on-line manual.

26.9.4 DPL External Methods

The external methods are available for external PowerFactory objects, such as
the load-flow command, the line object, the asynchronous machine, etc. as well
as additional functions dealing with classes and virtual instruments.

DPL Class Methods

ComOutage Methods
SetObjs Sets the list of objects according to S
GetObj Returns the object at position i

ComSimoutage Methods
Reset Resets the intermediate results
ExecuteCntcy Executes an ComSimoutage without resetting results
AddCntcy Executes an ComOutage without resetting results
SetLimits Sets the limits for the outage simulation

Tools & Utilities 26-541

DIgSILENT PowerFactory DPL

IntCase Methods
Activate Activates the study case
Deactivate De-activates the study case

IntPrj Methods
Activate Activates the project
Deactivate De-activates the project

TypAsm Methods
CalcElParams Calculates the electrical parameters

TypAsmo Methods
CalcElParams Calculates the electrical parameters

ElmFeeder Methods
GetAll Returns all objects in this feeder
GetNodesBranches Returns all buses and branches in this feeder
GetObjs Returns all objects of class ‘ClassName” in this feeder

ComNmink Methods
AddRef Adds shortcuts
Clear Empties the selection
GetAll Returns all objects of class ‘ClassName’

ElmComp Methods
Slotupd Performs a slot update

ComRes Methods
ExportFullRange Exports the whole data range
FileNmResNm Sets the filename for the data export

ComEcho Methods
On Turns on the user interface
Off Turns off the user interface

SetTime Methods
SetTime Sets the time
Date Sets the date at actual
Time Sets the time at actual

IntMon Methods

Tools & Utilities 26-542

DIgSILENT PowerFactory DPL

PrintVal Prints the values of the selected variables

PrintAllVal Prints a description for all variables
NVars returns the number of selected variables
GetVar Returns the n’th selected variable name
RemoveVar De-selects a variable
ClearVars Clears the selected variable names
AddVar Selects a variable name

SetFilt Methods
Get Returns a container with the filtered objects

ComDpl Methods
Execute Executes an external DPL script as a subroutine

IntMat Methods
Get Returns the (row, col) value
Set Set the value at position (row,col)
Init Initializes the matrix
Resize Resizes the matrix
NRow Returns the number of rows in the matrix
NCol Returns the number of columns in the matrix
RowLbl Sets the label of the R’th row
ColLbl Sets the label of the C’th column

IntVec Methods
Get Returns the value at index i
Set Sets the value at index i
Init Initializes the vector
Resize Resizes the vector
Size Returns the size of the vector

ElmCoup Methods
Close Closes the buscoupler
Open Opens the buscoupler
IsOpen Returns 1 when the coupler is open
IsClosed Returns 1 when the coupler is closed

ElmLne Methods
HasRoutes Returns if the line is subdivided into routes
HasRoutesOrSec Returns if the line is subdivided into routes or sections
GetType Returns the line type object
IsCable Returns if this is a cable
IsNetCoupling Returns if the line connects two grids
SetCorr Sets the correction factor of the line

Tools & Utilities 26-543

DIgSILENT PowerFactory DPL

CreateFeederWithRoutes
Splits the line in 2 routes

ElmLneroute Methods
IsCable Returns if the route is a cable
HasSections Returns if the line route is subdivided into sections

TypLne Methods
IsCable Returns if the line type is a cable type
SetNomCurr Sets the nominal current of the line type

ElmRes Methods
Init Initializes the result object
Clear Clears the result object
Write Writes the current results
Draw Updates all relevant plots
WriteDraw Writes results and updates all plots
SetAsDefault Sets this as default results
AddVars Adds to the list of monitored variables
GetObj Returns objects used in the result file

ElmZone Methods
GetAll Returns all objects in this zone
GetBuses Returns all buses in this zone
GetNodes Returns all nodes in this zone
GetBranches Returns all branches and buses in this zone
GetObjs Returns all objects of the given class in this zone

ComInc Methods
Execute Executes the command

ComLdf Methods
Execute Executes the command

ComShc Methods
Execute Executes the command

StaSwitch Methods
Close Closes the switch
Open Opens the switch
IsOpen Returns if the switch is open
IsClosed Returns if the switch is closed

SetFeeder Methods

Tools & Utilities 26-544

DIgSILENT PowerFactory DPL

GetAll Returns all objects in the feeder

GetBuses Returns all nodes in the feeder
GetBranches Returns all branches in the feeder

SetPath Methods
GetAll Returns all objects in the path
GetBusses Returns all nodes in the path
GetBranches Returns all branches in the path
AllBreakers Returns all breakers in the path
AllClosedBreakers Returns all closed breakers in the path
AllOpenBreakers Returns all open breakers in the path

SetSelect Methods
All Returns all objects
GetAll Returns all of the given class
AddRef Add references
Clear Empties the selection
AllElm Returns all elements
AllLines Returns all lines
AllBars Returns all busbars and terminals
AllLoads Returns all loads
AllAsm Returns all asynchronous machines
AllSym Returns all synchronous machines
AllTypLne Returns all line types
AllBreakers Returns all breakers
AllClosedBreakers returns all closed breakers
AllOpenBreakers returns all open breakers

IntForm Methods
SetText Sets the format text
WriteOut Write the report to the output window

DPL VI Methods

SetDesktop Methods
Show
WriteWMF
GetPage
SetResults
SetXVar
SetScaleX
SetAutoScaleX
SetAdaptX

Tools & Utilities 26-545

DIgSILENT PowerFactory DPL

SetVipage Methods
GetVI
SetStyle
SetTile
SetResults
SetXVar
SetScaleX
SetDefScaleX
SetAutoScaleX
SetAdaptX
GetScaleObjX

VisPlot Methods
AddVars
AddResVars
Clear
SetXVar
SetScaleX
SetScaleY
SetDefScaleX
SetDefScaleY
SetAutoScaleX
SetAutoScaleY
SetAdaptX
SetAdaptY
GetScaleObjX
GetScaleObjY
SetCrvDesc

IntPlot Methods
SetScaleY
SetAutoScaleY
SetAdaptY

Tools & Utilities 26-546

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

Chapter 27

DOLE and On-Line Data

Exchange

The DIgSILENT PowerFactory program offers sophisticated dynamic data

import and export possibilities for the use of other programs and for dynamic
data exchange for SCADA interfacing.

Both data exchange features, DOLE and SCADA interfacing, are based on a
small set of interfacing commands. Yet, these commands enable the import and
export of a wide range of parameters in an object oriented way.

The DOLE language and the SCADA interface are treated separately in the
following sections.

27.1 DOLE Interface

The DOLE interface is a common ASCII interface for all kind of data transfer to
DIgSILENT PowerFactory. Creating new objects, changing values of existing
objects and drawing single line graphics are the main features of the interface.
Use the option Open Dole File ... of the context sensitive menu by right clicking
the the input window of the data manager.

27.1.1 File Definition

The first line of a DOLE file configures the DOLE interface and must have the
following definition:

dole [/fkey][/dbupd][/gupd][/mm] langue= level=

/fkey use for all DOLE commands foreign keys. You

must set option /dbupd

/dbupd update database while reading dole file

/gupd update graphic while reading dole file

Tools & Utilities 27-547

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

/mm graphic coordinates in mm (command Com-

Grp), PowerFactory uses internally coordi-
nates in mm/87.5 !

langue 0 = English, 1 = German

level 0 = old DOLE interface compatible, 1 = new

DOLE interface (recommended)

Default: dole no options set !

The switches /dbupd and /gupd are time consuming.
To insert comments in the DOLE file set the first character in the line to ’*’.

Each line must contain one of the following commands:

• create • buscnf • grp

• set • ac • ifupd

• connect • new • echo

These commands are described in the next sections.

27.1.2 Create - Command

The Create command creates new objects in the PowerFactory database and
has following definition:

create [/sec][/rou][/noswt] objname.classname

[name=....]

objname name of the new object

classname class type of the new object, i.e. ElmLod

(General Load), ElmSym (Synchronous Ma-
chine), TypSym (Type of Synchronous Ma-
chine), etc.

/sec creates Line Sub-Sections

/rou creates Line Routes

Tools & Utilities 27-548

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

/noswt in combination with /rou, set switch insert

mode to false, default = true

name Names of Line Routes, Line Sub-Sections,

with /sec : name=section name 1,section
name 2, ... with /rou : name=[term. x],route
1,term 1,route 2 ...

Example for the Create - Command:

create .\Example 1.ElmNet
creates a grid with name Example 1
create .\Example 1\Load 1.ElmLod
create a general load in the Example 1 folder with name Load 1
create .\Example 1\Line 1.ElmLne
create a line in the Example 1 folder with name Line 1
create .\Grid 2.ElmNet\Gen 1.ElmSym
create a grid with name Grid 2 if not exists and create a synchronous ma-
chine in the folder Grid 2 with name Gen 1
Example for creating Line Sub-Sections
create .\Example 1.ElmNet
creates a grid with name Example 1
create .\Example 1\Line 1.ElmLne
create a line in the Example 1 folder with name Line 1
create/sec .\Example 1\Line 1 name=Sec 1,Sec 2
create/sec .\Example 1\Line 1 name=Sec 3
appends line sub-sections into the line

Example for creating Line Routes

create .\Example 1.ElmNet
creates a grid with name Example 1
create .\Example 1\Line 1.ElmLne
create a line in the Example 1 folder with name Line 1
create/rou .\Example 1\Line 1 name=,Route 1,Term 1,Route 2
creates line routes named Route 1 and Route 2 with terminals named Term
1into the line
Attention !! If the line contains no routes or terminals, the name list must
start with a comma indicating that the next name is a line route.
create/rou .\Example 1\Line 1 name=Term 2,Route 3
Appends line routes with terminals into the line. The name list must start
with a terminal name.

Tools & Utilities 27-549

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

Additional functions
By default the command inserts switches between line routes. With the option
/noswt the command does not insert switches. You can change the default if
you insert a tilde (‘~’) before or/and behind the name of the terminals.

Default switch insert

create/rou .\Example 1\Line 1 name=,Route 1,Term 1~,Route 2
A switch is inserted between Route 1 and Term 1
No switch is inserted between Term 1 and Route 2
create/rou .\Example 1\Line 1 name=,Route 1,~Term 1,Route 2
No switch is inserted between Route 1 and Term 1
A switch is inserted between Term 1 and Route 2
Option /noswt, no switch insert
create/rou/noswt .\Example 1\Line 1 name=,Route 1,Term 1~,Route 2
No switch is inserted between Route 1 and Term 1
A switch is inserted between Term 1 and Route 2
create/rou/noswt .\Example 1\Line 1 name=,Route 1,~Term 1,Route 2
A switch is inserted between Route 1 and Term 1
No switch is inserted between Term 1 and Route 2

27.1.3 Set - Command

The Set command is used for defining variable sets and modify values of these
sets. The command has the following definition:
set [/def][/fkey][/cls] obj=name [var=...][val=...]

/def Define a variable set for all elements from type

name

/cls Clear all variable sets

/fkey Interpret ’name’ as foreign key, this switch is

ignored with dole/fkey

var= List of variable names etc. var=plini,qlini,...

val= List of values etc. val=,10.3, 2.5, .... (first char-

acter = used delimiter)

obj=’name’ Name or foreign key of element or class name

(option /def)

Tools & Utilities 27-550

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

Example for the data section of an update file

set/def obj=ElmLod var=plini,qlini
Define a variable set for all Loads
set/def obj=ElmSym var=pgini,qgini
Define a variable set for all synchr. machines.
set obj=Load1 val=, 10.5, 1.3
Element Load1: plini = 10.5, qlini = 1.3
set obj=Sym 1 val=, 102.4, 10.45
Element Sym 1: pgini = 102.4, qgini = 10.45

Additional functions
The set command takes the last object created with the create - command when
“obj=blank” is used.

set/def obj=ElmLod var=plini,qlini

create .\Grid 1\Load 1.ElmLod
set obj= val=10.5, 1.3
set plini, qlini of the object Load 1 to 10.5 and 1.3

Set values and size of a vector (table):

set/def obj=ElmStactrl var=qsym:SIZE,qsym:ALL

SIZE: change the size of the vector
ALL: set all values of the vector
set obj=Stactrl 1 var=5,20,25,35,7,13
Element Stactrl 1: qsym[0]=20,qsym[1]=25 ...
size of qsym = 5

Set DSL Parameter:

set/def obj=ElmDsl var=params:LIST:table1_R

special syntax of ElmDsl
set obj=Dsl 1 val=No,vname1:2,vname2:1.25,vname3:2.3,vname4:125
No: number of following parameters (here No=4)
name of parameter : value of parameter, ....

27.1.4 Connect - Command

The Connect command connects edge elements (Lines, Loads, Machines, etc.)
to busbars and terminals and has the following definition:

Tools & Utilities 27-551

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

connect name [b1=bus1][ib1=] ... [b4=bus4][ib4=]

name name of element

b1 bus1 = name of the terminal or busbar

ib1 connection mode (0 or 1)

b2 bus2 = name of the terminal or busbar

ib2 connection mode (0 or 1)

b3 bus3 = name of the terminal or busbar

ib3 connection mode (0 or 1)

b4 bus4 = name of the terminal or busbar

ib4 connection mode (0 or 1) mode=0: switch

opened, mode=1: switch closed

PowerFactory connects the edge elements to the busbars or terminals (bus1,

bus2,...) and creates (if necessary) for all busbars automatically cubicles and
switches.

Examples for the Connect command

connect .\Line_10kV b1=.\SS1 ib1=1 b2=.\SS2 ib2=1
Connect a line (Line 10kV) to the terminals SS1 and SS2
connect .\Tr_10_15 b1=.\SS2 ib1=1 b2=.\STAT_1\SS3 ib2=1
Connect a Transformer (Tr 10 15) to the terminal SS2 with the high voltage
side and to the busbar SS3 in station STAT 1 with the low voltage side.

27.1.5 Buscnf - Command

The Buscnf command is used for renaming switches and cubicles which are
created with the connect command or the create/rou command.
buscnf cubn=cubicle name swtn=switch name

cubn set the name of the cubicle to cubicle name

swtn set name of the switch to switch name

Example for the Buscnf - Command

Tools & Utilities 27-552

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

connect .\Line_10kV b1=.\SS1 ib1=1 b2=.\SS2 ib2=1

busncf cubn=Cub 0.1 swtn=S 0.1
renames the cubicle and switch which connecting SS1 with Line 10kV (ter-
minal i)
busncf cubn=Cub 0.2 swtn=S 0.2
renames the cubicle and switch which connecting SS2 with Line 10kV (ter-
minal j)
connect .\trf_10/100 b1=.\SS10 ib1=1 b2=.\SS20 ib2=1
busncf cubn=Cub_1 swtn=S_1
renames the cubicle and switch connecting SS10 with trf 10/100 (HV - Side)
busncf cubn=Cub_2 swtn=S_2
renames the cubicle and switch connecting SS20 with trf 10/100 (LV - Side)
create/rou .\Example 1\Line name=,Route 1,Term 1,Route 2, ...
... Term 2,Route 3
busncf cubn=C_R1 swtn=S_R1
renames the cubicle and switch which connecting Route 1 with Term 1
busncf cubn=C_R2 swtn=S_R2
renames the cubicle and switch which connect Term 1 with Route 2
busncf cubn=C_R3 swtn=S_R3
renames the cubicle and switch which connect Route 2 with Term 2
busncf cubn=C_R4 swtn=S_R4
renames the cubicle and switch which connect Term 2 with Route 3

Ifupd Command
The Ifupd command is used for composite models to update the interface and
insert references.

ifupd mod=name objs=object1,object2,object3...

mod name of the composite model

objs list of object names to insert references into

the composite model

Example for the Ifupd - Command

ifupd mod=Comp1 objs=Gen 1,Busbar 1
inserts into the composite model Comp1 two references points to Gen 1 and
Busbar 1 and updates the interface.

27.1.6 Echo Command

The Echo Command is used for printing information messages into the Output
Window of PowerFactory. Example for the Echo- Command:

Tools & Utilities 27-553

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

echo Reading Transformer Data

Prints into Output Window:
“DIgSI/Info Reading Transformer Data”

27.1.7 Activate Command

The Activate Command is used to activate or deactivate projects and study
cases. Calculations are only possible after a study case has been activated.

ac [/de] name

name name of the project or study case

/de deactivate

Remark
ac/de all
Deactivates the currently active project and study case

Examples
ac \User\Factory\20kV
Activates the project or study case 20kV in the folder \U SER\FACTORY
ac/de \User\Distribution\Shc1
Deactivates the project or study case Shc1 in the folder \U SER\-
D ISTRIBUTION

27.1.8 New Command

The New Command is used to create a new visual object. Visual objects are all
objects which can be displayed graphically in a single line or a block diagram.

Syntax:

new /sgl | /blk | /vis [pTarget=target]

[sName=name]

/sgl Creates a new grid with a corresponding sin-

gle line graphic.

/blk Creates a new block diagram.

/vis Creates a new virtual instrument panel.

Tools & Utilities 27-554

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

pTarget= Specifies the folder in which the new object

should reside. The default value for this pa-
rameter is ’\U SER’

sName= Specifies the name of the object to create.

The default value for this parameter is “non-
ame”

Remarks
The new command with the option /sgl will automatically activate the newly
created grid.

Example
new/sgl pTarget=\User\Factory sName=20kV
This will create the new grid with the name 20kV and the corresponding
single line graphic in the folder \U SER\FACTORY.

27.1.9 Graphic Command

The graphic command allows to create or modify all necessary objects for
single line graphics or block diagrams from a DOLE input file. It is one of the
most powerful commands within PowerFactory. An appropriate graphic window
must be opened before this command can be used. Such can be done either
with the new or activate command. The use of the graphic command is similar
to the interactions of the user when creating or modifying a diagram with the
mouse. Therefore you should have to be familiar with the basic interactions in
PowerFactory graphic windows (see PowerFactory Users Manual - Chapter
’Graphic Windows’). If you never have created a drawing interactively in
PowerFactory you might get some problems to understand the structures and
principles of this command.

The graphic command can be used in three different modes specified by the
first option.

Mode 1: Creating objects (grp/new)

This mode is designed for creating new graphic objects.

Syntax:

Tools & Utilities 27-555

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

grp/new [obj=] [sFKey=] symbol= pos= [size=]

[iRot=] [sAttr=] [iNamVis=] [iResVis=]

obj= Specifies the complete name (incl. path) of

the corresponding data object. If this data
object exists it will be linked to the created
graphic object, if not it will be created, too.

sFKey= Specifies the value for the foreign key (pa-

rameter ’for name’) of the data object. This
parameter can be used to identify the cre-
ated object by later commands or interactions.
Therefore it must be unambiguous in the com-
plete database and can be considered as an
unique foreign key for all objects in the Pow-
erFactory database.

symbol= The identifier name for the graphical symbol

which is used to represent the created object
in the graphic.

• “symbol=__HGRAF__” is used to create auxiliary graphic objects for

illustrating purposes.

• “symbol=__BREAKER__” is used to insert breaker switches in single line

graphics. Breakers in single lines are not represented by real graphic
objects. They are only virtual instruments which show the summary switch
mode of a complete feeder.

• In PowerFactory the insertion of compound objects into a graphic is

possible by specifying a compound symbol. This means, that with one
grp/new command it is possible to insert several graphic objects
representing a complex data object. This is, for example, used in single line
graphic windows to insert a complex busbar system into the drawing.

Tools & Utilities 27-556

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

pos= A list of coordinates used to insert the created

object into the drawing. The coordinates are
separated by a comma. Each coordinate con-
sists of two values (one for the dimension x
and one for the dimension y), separated by a
comma. For node objects only one position
is necessary. For branch objects the coor-
dinate list should contain the same positions
as if the object will be interactively entered
into the graphic window (see PowerFactory
Users Manual - Chapter ’Graphic Windows’,
’Adding New Power System Elements’). ’Dou-
ble clicks’ are simulated by entering the same
position twice.

size= This options allows to specify a graphical size

different from the default for the created ob-
ject. The default value is determined by the
used symbol.

iRot= This options allows to specify a graphical ro-

tation angle different from the default for the
created object. The value for the angle must
be entered in degrees (0-360) and is counted
counterclockwise. The default value is deter-
mined by the used symbol.

iNamVis= Specifies whether the name attribute of the

created object is visible in the drawing. Name
attributes are defined by the appropriate sym-
bol definition. The possible values for this pa-
rameter and their meaning are:

0 Do not show name attributes

1 Show name attributes

-1 Take the default value from the symbol def-

inition

Tools & Utilities 27-557

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

iResVis= Specifies whether the result attribute(s) of

the created object are visible in the drawing.
These attributes are defined by the appropri-
ate symbol definition. The possible values for
this parameter and their meaning are:

0 Do not show result attributes

1 Show result attributes

-1 Take the default value from the symbol def-

inition

sAttr= In the create mode of the Graphic command

this parameter can contain a definition of an
additional geometry object to visualise the
created objected. The syntax for the geom-
etry object definition is the same as is used by
the symbol definition (see syntax description
of the symbol definition).

Hint: to transform coordinates from mm to

the internal coordinate space, please divide
by 87.5, even if dole/mm was set.

Examples
grp/new sFKey=99/KT05 symbol=ShortTermStrip size=0.1 ...
... pos=0.65,1.25
This will create a new graphic object with according to the definition of the
symbol ’ShortTermStrip’. The graphic object will get the position (0.65/1.25)
and the size 0.1. If the PowerFactory database contains an appropriate
data object (a Terminal) with the foreign value ’99/KT05’ it will be linked to
the created graphic object, otherwise it will be created and linked, too.

grp/new obj=User\Factory\20kv\TR015 symbol=d_tr2 ...

... iResVis=0 pos=0.65,0.75,0.65,1.05,0.65,1.05,0.65,1.25

Tools & Utilities 27-558

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

This will create a new graphic object according to the definition of the sym-
bol ’d tr2’. The object (a Transformer) will be connected with the busbar or
terminal referenced by the position (0.65/0.75) and the busbar or terminal
referenced by the position (0.65/1.25). The position of the created object will
be (0.65/1.05) using a simulated double click. Result attributes for the object
will not be visible. If the PowerFactory database contains an appropriate
transformer with the specified complete name (inclusive the path) it will be
linked to the created graphic object, otherwise it will be created and linked,
too. If it is created, the topology of the data objects will be taken from the
graphical topology, otherwise the graphical topology must match the given
topology at data object level.

grp/new symbol=d_lin pos=2.55,0.35,2.75,0.35,2.75,0.80, ...

... 3.1,0.8
This will create a new graphic object and a new data object according to the
definition of the symbol ’d lin’. The object (a Line) will be connected with the
busbar or terminal referenced by the position (2.55/0.35) and the busbar or
terminal referenced by the position (3.1,0.8). The other given coordinates
represent intermediate line points.

Mode 2: Modify =Objects (grp/mod)

This mode allows to modify existing graphic objects. To reference objects there
are three possibilities:

• Identify the object by entering the complete name (incl. path) of the object
with the parameter ’obj’

• Identify the object by entering the foreign key value of the object with the
parameter ’sFKey’

• Identify objects by entering the positions of the object in the drawing with
the parameter ’pos’.

• If only one coordinate is entered, the coordinate will have to lay inside the
surrounding rectangle of the desired object. By entering more than one
coordinate you can reference more than one object. Then the coordinates
are interpreted as points of an imaginary polyline in the drawing. Objects
are referenced if their surrounding rectangles will be intersected by this
imaginary polyline.

Syntax:

Tools & Utilities 27-559

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

grp/mod obj= | sFKey= | pos= [size=] [iRot=] [iN-

amVis=] [iResVis=]

obj= Used to identify a graphic object via the com-

plete name (incl. path) of the linked data ob-
ject or the complete name (incl. path) of the
graphic object itself.

sFKey= Used to identify a graphic object via the for-

eign key of the linked data object or the foreign
key of the graphic object itself.

pos= A list of coordinates used to identify the ob-

ject(s) in the drawing. The coordinates are
separated by a comma. Each coordinate con-
sists of two values (one for the dimension x
and one for the dimension y), separated by a
comma (see description above).

size= This options allows to specify a new graphical

size for the referenced object(s).

iRot= This options allows to specify a new graphi-

cal rotation angle for the referenced object(s).
The value for the angle must be entered in
degrees (0-360) and is counted counterclock-
wise.

iNamVis= Specifies whether the name attribute of the

object(s) is(are) visible in the drawing. Name
attributes are defined by the appropriate sym-
bol definition. The possible values for this pa-
rameter and their meaning are:

0 Do not show name attributes

1 Show name attributes

-1 Take the default value from the symbol def-

inition

Tools & Utilities 27-560

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

iResVis= Specifies whether the result attribute(s) of the

created object(s) is(are) visible in the drawing.
These attributes are defined by the appropri-
ate symbol definition. Possible values for this
parameter and their meaning are:

0 Do not show result attributes

1 Show result attributes

-1 Take the default value from the symbol def-

inition

Examples
grp/mod size=1.15 pos=0.65,0.8
This will change the size of the graphic object whose surrounding rectangle
is referenced by the position (0.65/0.8).

grp/mod obj=\User\Factory\20kv\bus23 iRot=90

This will change the rotation angle of the graphic object whose linked data
object has the complete name (incl. path) \U SER\FACTORY\20 KV\BUS 23.

Mode 3: Set Foreign Key Values (grp/sfk)

This mode allows to set the foreign key values of the linked data objects for
existing graphic objects. The graphic objects have to be referenced by entering
the positions of the object in the drawing with the parameter ’pos’. If only one
coordinate is entered, the coordinate will have to lay inside the surrounding
rectangle of the desired object. By entering more than one coordinate you can
reference more than one object at once. Then the coordinates are interpreted as
points of an imaginary polyline in the drawing. Objects are referenced if their
surrounding rectangles will be intersected by this imaginary polyline. With this
command it will be possible to set the foreign key values for objects created
automatically from PowerFactory by inserting a compound object into the
drawing via the grp/new command (see description above). Automatically
created objects are, for example, the several busbars in a busbar system or the
routes of a line.
Syntax:
grp/sfk [symbol=] pos= {sAttr:index=}

symbol= If given this parameter will limit the group of referenced objects via the
parameter ’pos’ to objects which graphical symbol names matches the
value of this parameter.

Tools & Utilities 27-561

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

pos= A list of coordinates used to identify the object(s) in the drawing. The
coordinates are separated by a comma. Each coordinate consists of two
values (one for the dimension x and one for the dimension y), separated by
a comma (see description above).

sAttr:index= For every referenced object the specification of this parameter will
set the foreign key parameter of the linked data object to the given value.
Therefore the term :index specifies the index in the list of all referenced
objects, beginning with the value ’0’. Note that it is not necessary that you
specify values for all identified objects. The list of referenced objects is
sorted in increasing order according to their intersection with the points of
the imaginary polyline given by the parameter ’pos’.

Example
grp/sfk symbol=d_bus_h pos=0.25,0.7,0.25,1.0 sAttr:0=99/2b ...
... sAttr:1=99/1a
This will set the foreign key values for two data objects whose linked graphic
objects are first intersected by the imaginary polyline with the start point
(0.25/0.7) and end point (0.25/1.0) and whose symbol name is ’d bus h’.

27.2 DIgSILENT On-Line Operation Mode

The PowerFactory-software can be operated in an on-line mode with a direct

connection to a SCADA system. This feature enables to access real measured
system data, either the last actual ones, or any set which has been saved
previously by the SCADA interfacing system.

By activating the last measured system status which will comprise generation,
loads, transformer tap settings, shunt reactor switching and system
configuration, this option allows the analysis of the actual system operation with
respect to:

• active and reactive power flow, voltage profile, system losses and reactive
power compensation requirements

• general fault analysis

• system losses optimization

• spinning reserve and load shedding supervision and optimization

• analysis of measures for system oscillation stabilization

Tools & Utilities 27-562

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

The access to previously stored data allows the analysis of any occurred fault or
otherwise specific situation needed to be studied. In this case, the main
advantage of accessing SCADA history files is the ability of updating power
system data easily without being forced to edit any data manually.
PowerFactory SCADA interfacing has been realized in a very general manner,
ensuring that a PowerFactory SCADA on-line link can be realized with nearly
any SCADA hardware and software.

27.2.1 DIgSILENT Method For SCADA Interfacing

The procedure implemented for SCADA interfacing is as follows:

1. The operated power system must be set up in PowerFactory using the

single line graphic editor or the data manager. This configuration must
reflect the general structure of the operated system, including the existing
busbars (substations) installed lines, cables, transformers, shunt-reactors
etc. Specific operation information like loads, generation or any general
”on/off” information concerning bus-couplers, circuit breakers or isolators
will later be overwritten.

2. Data transfer files (*.dle) have to be generated, organized and stored

periodically by a SCADA interfacing program, which may run on the
PowerFactory computer system or the SCADA system itself. The
generated update files can be best described as ”incremental files”
containing the operated system actual data.

Access to a specific system status is done by the following procedure:

1. Start the PowerFactory program

2. Activate the case or grid containing the power system configuration

3. Read in one of the transfer files using the main menu ”File/Import”.

This will automatically update the operation information. The program is then
ready to execute any available command concerning power flow, fault analysis,
stability calculation etc.

27.2.2 Description Of The Generalized Update-File

The update-file consists of two different sections containing

1. definition for the data - variable link

2. operation data

Tools & Utilities 27-563

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

which are both using the set command. The Set-Command has the following
definition:

set [/def][/fkey][/cls] obj=name [var=...][val=...]

/def Define a variable set for all elements from type

name

/cls Clear all variable sets

/fkey Interpret ’name’ as foreign key

var= List of variable names etc. var=plini,qlini,...

val= List of values etc. val=,10.3, 2.5, .... (first char-

acter = used delimiter)

obj=’name’ Name or foreign key of element or class name

(option /def)

Example for the definition section of an update file

set/def obj=ElmLod var=plini,qlini
Define a variable set for all Loads
set/def obj=ElmSym var=pgini,qgini
Define a variable set for all synchr. machines.

Example for the data section of an update file

set obj=Load1 val=, 10.5, 1.3
Element Load1: plini = 10.5, qlini = 1.3
set/fkey obj=L32 val=, 10.5, 1.3
Element Load1 with foreign key L32

a) 2-winding transformer
set/def obj=ElmTr2 var=nntap
Define variable set
nntap = tap position
b) General load
set/def obj=ElmLod var=plini,qlini
Define variable set
plini = active power [MW]
qlini = reactive power [MVAr]

Tools & Utilities 27-564

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

c) Synchronous Machine
set/def obj=ElmSym var=pgini,qgini
Define variable set
pgini = active power [MW]
qgini = reactive power [MVAr]
d) Switch
set/def obj=StaSwitch var=on_off
Define variable set
on off (1=closed, 0=opened)

27.2.3 Create - Command

The Create command creates new objects in the PowerFactory database and
has following definition:

create [/sec][/rou][/noswt] objname.classname

[name=....]

objname name of the new object

classname class type of the new object, i.e. ElmLod

(General Load), ElmSym (Synchronous Ma-
chine), TypSym (Type of Synchronous Ma-
chine), etc.

/sec creates Line Sub-Sections

/rou creates Line Routes

/noswt in combination with /rou, set switch insert

mode to false, default = true

name Names of Line Routes, Line Sub-Sections,

with /sec : name=section name 1,section
name 2, ..., with /rou : name=[term. x],route
1,term 1,route 2 ...

Example for the Create - Command:

create .\Example 1.ElmNet
creates a grid with name Example 1
create .\Example 1\Load 1.ElmLod
create a general load in the Example 1 folder with name Load 1

Tools & Utilities 27-565

DIgSILENT PowerFactory DOLE and On-Line Data Exchange

create .\Example 1\Line 1.ElmLne

create a line in the Example 1 folder with name Line 1
create .\Grid 2.ElmNet\Gen 1.ElmSym
create a grid with name Grid 2 if not exists and create a synchronous ma-
chine in the folder Grid 2 with name Gen 1

27.2.4 Connect - Command

The Connect command connects edge elements (Lines, Loads, Machines, etc.)
to busbars and terminals and has the following definition:

connect name [b1=bus1][ib1=] ... [b4=bus4][ib4=]

name name of element

b1 bus1 = name of the terminal or busbar

ib1 connection mode (0 or 1)

b2 bus2 = name of the terminal or busbar

ib2 connection mode (0 or 1)

b3 bus3 = name of the terminal or busbar

ib3 connection mode (0 or 1)

b4 bus4 = name of the terminal or busbar

ib4 connection mode (0 or 1), mode=0: switch

opened, mode=1: switch closed

PowerFactory connects the edge elements to the busbars or terminals (bus1,

bus2,...) and creates for all busbars automatically cubicles and switches.

Examples for the Connect command

connect .\Line_10kV b1=.\SS1 ib1=1 b2=.\SS2 ib2=1
Connect a line (Line 10kV) to the terminals SS1 and SS2
connect .\Tr_10_15 b1=.\SS2 ib1=1 b2=.\STAT_1\SS3 ib2=1
Connect a Transformer (Tr 10 15) to the terminal SS2 with the high voltage
side and to the busbar SS3 in station STAT 1 with the low voltage side.

Tools & Utilities 27-566

DIgSILENT PowerFactory Conversion from Graphical Information Systems

Chapter 28

Conversion from Graphical

Information Systems

The conversion of system data from a GIS (Graphical Information System) is

performed by the ComGis command. The dialogue of this command is opened
by selecting the Conversion... - Gis... option on the main File menu.

The ComGis conversion command takes a special “.DGS” format file and
creates a single graph and a list of electrical models from that file. The syntax of
the “.DGS”-file, which is in plain ASCII, is explained further on in this section.

The GIS conversion uses millimeter units with respect to the bottom-left origin
and a limit up A0 paper format (1188 x 840 mm). It could therefore be necessary
to transform the GIS coordinates before creation of the “.DGS”-file file.

28.1 “.DGS”-File Creation by using the Excel

Sheet

A special Microsoft Excel spreadsheet is shipped with the PowerFactory

program, which can be used to create the “.DGS”-file in a more user-friendly
way. This Excel spreadsheet is named “Gis2Dole.xls” and is found in the
subdirectory “\Dole” of the installation path of DIgSILENT PowerFactory.

The first sheet of “Gis2Dole.xls” is called ’Description’. All the parameters of the
different conversion elements and types are described here. The actual data is
entered in the other worksheets:

• ‘Terminals’

• ‘Loads’

• ‘Lines’

• ‘Transformers

• ‘LV Transformers’

• ‘DigSI Lines’

Tools & Utilities 28-567

DIgSILENT PowerFactory Conversion from Graphical Information Systems

The ‘DigSI Lines’ worksheet is for internal use only.

The button C REATE C ONVERSION F ILE is used to generate the “.DGS”-file. The
created “.DGS”-file is stored in the current directory and will receive the same
named as the excel file (but with the extension ‘DGS’).

Alternatively, the “.DGS”-file can be generate by the GIS itself, without using the
Excel spreadsheet. The format of the “.DGS”-file is described hereinafter for that
purpose.

28.2 The PowerFactory Import

The import of the GIS data from the “.DGS”-file is performed in the following
steps.
• Create a new project in the PowerFactory database or activate an existing
project or study case.
• Within the File - Conversion... menu, select the GIS... option to open the
GIS conversion command dialogue.

In most cases, the default settings of the conversion command can be used. The
general page of the conversion command is depicted in Fig. 28.1.
The “New Grid” option are used to select
• Graphic Name: optionally select an existing single line graphic to which the
new graphic objects will be added.
• Grid Name: Either enter the name of an existing grid, or a new name. The
new electrical models will be created in the given grid.
If no single line graphic is selected, then the default graphic in the selected grid
will be used to draw the new graphic symbols.

The “GIS Conversion File” option is used to enter the name and path of the
“.DGS”-file on disk.

The “Predefined Terminals” option is used to optionally select an existing Grid

which contains previously defined terminals to which branches that are imported
from the “.DGS”-file are to be connected.

28.2.1 Conversion Options

Several conversion options are available on the Options page of the conversion
command dialogue, as depicted in Fig. 28.2.

Tools & Utilities 28-568

DIgSILENT PowerFactory Conversion from Graphical Information Systems

Figure 28.1: The GIS conversion dialogue

Figure 28.2: The GIS conversion options

The “Conversion Elements” option is used to disable the import of specific

classes. Disabling the Transformers-option, for instance, will disregard all
transformer data in the “.DGS”-file. No transformers will thus be imported.

Tools & Utilities 28-569

DIgSILENT PowerFactory Conversion from Graphical Information Systems

The “Line Types” option is used to generate routes and sections, dependent on
the selected type libraries:

• Overhead Line (OHL) Type Library (optional): Existing PowerFactory

Library path

• Cable Line Type Library (optional): Existing PowerFactory Library path

The option “Automatical Drawing of Branch Net Elements” can be disabled to

switch off the automatic drawing of lines and transformers.

28.3 “.DGS”-File Format

The “.DGS”-File syntax uses special sections for defining all graphical and
electrical information for all power system objects. Comment lines are started
with an asterisk.

Each new section must start at a new line that starts with two dollar characters
’$$’ followed by the section name:

$$<section_name>[: parameter descriptions]

[element_parameters]

Each line within a section must start with a line number, followed by comma
separated fields. The line numbers are the the adjacent sheet row number of the
spreadsheet, when the “.DGS”-File was created by the Excel spreadsheet. The
available parameters are found on the “Description” page of the “Gis2Dole.xls”
spreadsheet.

Example:

$$Version
1.1

$$Terminals:xlsLineNumber,Name,uknom,X,Y,Length,Rotation,GrType
2,X3177,11,250,350,60,90,1
3,X3702,11,150,350,60,90,1

$$Loads:xlsLineNumber,Name,Busbar,Type,App Power (kVA),Power Factor

2,Load1,X1531,Loads\GLT,100,0.95
3,Load2,X1058,Loads\GLT,500,0.95

$$Lines:xlsLineNumber, Name, GIS Name, Station1, Busbar1, Conn1,

Station2, Busbar2, Conn2, Switch 1, Switch 2, OoS, Par.no.,

Tools & Utilities 28-570

DIgSILENT PowerFactory Conversion from Graphical Information Systems

Type?, Length?,
3,Line(001),C-3177__C-3702,,C-3177,1,,C-3702,1,2284,8120,0,1,
Cables\300 Al,0.0067108,OHL\185 Cu,0.017003,OHL\300 Al,
0.08713,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

$$Transformers:xlsLineNumber,Name,Type,Busbar1,Conn1,Busbar2,Conn2,OoS,
Par.no.,TapPos
2,2WTr1,Transformer\300 kVA,C-3462 H,1,C-3462 L,0,1,2,0
3,2WTr2,Transformer\300 kVA,C-3462 H,1,C-3462 L,1,0,1,0

$$LV Transformers :xlsLineNumber, Name, LV uknom(kV), Type of Load,

App Power (kVA), Pow. Factor, Type of Transformer, Busbar HV, Conn1,
Conn2, SwitchHV, HV FuseRating, HV FuseType, OoS, Par.no., Tap
2,X1058_1,0.415,Loads\GLT,1000,0.95,Transformers\1000 kVA,X1058,0,0,
S1058_1,,,1,1,0
3,X1112_2,0.415,Loads\GLT,1000,0.95,Transformers\1000

Tools & Utilities 28-571

DIgSILENT PowerFactory Converting/Importing PSS/E Files

Chapter 29

Converting/Importing PSS/E
Files

In the previous PowerFactory versions, the Converting/Importing of PSS/E files

was accomplished in two steps: First by applying an auxiliary PSS2DOLE
program and second by importing the resulting file into the PowerFactory
software.

This however has changed in the latest versions, allowing the user to
Convert/Import directly all type of PSS/E files (supporting versions 23 to 26)
from the software itself, making it even more user friendly.

In the foregoing a detailed procedure for Converting/Importing PSS/E files will be

explained.

29.1 Conversion Procedure

If the user would like to convert dynamic data files, it is suggested to first copy
the IEEE library folder located in the main database into the user directory. The
IEEE folder has the structure defined in figure Fig. 29.1.
The following subdirectories are of importance in the Conversion/Importing.

Model Library Folder This folder contains a PowerFactory representation

(DIgSILENT Simulation Language-DSL) of most typical models, e.g.
AVR’s, PSS, PCO, etc. It can also contain user defined models.

Frame Library Folder This folder contains the composite frame’s which are
basically wired diagram.

It is also important to note that the DSL models defined in the model library
folder should not be in different subdirectories (e.g. AVR’s, PSS, etc). If this is
the case the user must copy all of the models into one specific library folder.
After the conversion, the user can then arrange the specific models according to
his projects (recommended).

Before following the next steps, the user must verify that no projects are currently
activated.

Tools & Utilities 29-572

DIgSILENT PowerFactory Converting/Importing PSS/E Files

Figure 29.1: IEEE Library

Select from the main menu File → Conversion → PSS/E → Import Afterwards
the window of the import command will pop-up, asking for the user to fill up more
specific details about the PSS/E file Conversion/Import to take place.

29.2 General tab page

Nominal Frequency Nominal frequency of the file to be Converted/Imported.

PSS/E Raw data Location on the hard disk of the PSS/E raw data file. By
default the program searches for *.raw extensions. The user may consider
all types of files by typing *.*.

Add Graphic Files Location on the hard disk of the PSS/E drw files. Again by
default the programs searches for files with extension *.drw. The user may
consider all types of files by typing *.*. Important Note: After the
Conversion/Importing has finished, the resulting project will contain a
graphics folder where all of the PSS/E drw converted graphics will be
stored. The user must therefore relocate each one of them in the
corresponding grids.

Save converted data in:

Project The project name that the Converted/Imported file will have in the data
manager window.

in Location in the data manager tree where the imported file will be stored.

Tools & Utilities 29-573

DIgSILENT PowerFactory Converting/Importing PSS/E Files

Figure 29.2: General tab page

Sequence Data Location on the hard disk of the PSS/E sequence data file. By
default the program searches for *.seq extensions. The user may consider
all types of files by typing *.*.

Dyn Models Data Location on the hard disk of the PSS/E Dynamic Models data
file. By default the program searches for *.dyn extensions. The user may
consider all types of files by typing *.*.

Parameter Mapping Location on the hard disk of the PowerFactory mapping

file. The mapping file is distributed with the programm itself and is
generally stored in the DOLE directory. This file maps the dynamic data
between PSS/E and PowerFactory.

Composite Frame Path Location in the PowerFactory data manager tree

where the composite frames are stored(IEEE/Frames...).

DSL - Model Path Location in the PowerFactory data manager tree where the
DSL models are stored (IEEE/Models....).

Tools & Utilities 29-574

DIgSILENT PowerFactory Converting/Importing PSS/E Files

29.3 Options tab page

Figure 29.3: Options tab page

Unit of ‘LEN’ for lines in miles instead of km With this option enabled, all
lengths will be interpreted in miles in the PSS/E raw files.

Convert only sequence data file With this option enabled, the converter will
add only the sequence data to an existing project.

Convert Induction Machines (P < 0) With this option enabled, all generators
in the raw data file that have negative active power will be converted to
asynchronous machines.

Consider transformer phase shift With this option enabled, transformer phase
shifts will be considered.

Convert only dynamic model file With this option enabled, the converter will
add only the dynamic model file to an existing project.

Tools & Utilities 29-575

DIgSILENT PowerFactory Converting/Importing PSS/E Files

Convert only graphic file With this option enabled, the converter will add only
a graphic to an existing project.

Only convert file Internal option. Not intended for the normal user (this box
should be unchecked).

Output only used dynamic models Displays a list of used dynamic models.

Automatic 3-W. Transformer detection/conversion The converter will try to

detect the existence of three 2-Winding Transformers connected to a
busbar. If any candidates are available, PowerFactory will replace them
by a 3-Winding Transformer. The detection is made by checking the
impedances and the voltage control of the transformers.

Busbar naming: ‘PSSE NAME’ With this option enabled, the busbars are
named similar as in the PSS/E raw data file (without bus number).

Branch naming: ‘BUSNAME1 BUSNAME2 ID’ With this option enabled, the
branches are named as the name of the busbars + ID.

Convert capacitive line shunts to line susceptance B’ If a line has line

shunts the converter adds automatically the line shunt capacitance to the
C1’ (B1’) in the PowerFactory line type.

Graphical Conversion Settings:

Rotate with respect to busbar The converter will rotate the graphical layout in
case of the majority of busbars being in vertical or horizontal position.

Snap coordinates to grid The converter will snap to grid all objects in the
single line graphics.

Scaling factor The graphic files are scaled according to the showed scaling
factor.

Additional Parameters: For additional features in the conversion command, the

user can access special codes to fulfill his needs. Recommended only for
advanced users.

Tools & Utilities 29-576

Glossary
DIgSILENT PowerFactory
Version 13.1

DIgSILENT GmbH
Gomaringen, Germany

2004
DIgSILENT PowerFactory Glossary

Glossary

Device A certain kind of physical power system components: certain

synchronous machines, two-winding transformers, busbars, or other kinds
of equipment. Example: a NKBA 0.6/1kV 4 x 35sm cable.

Appliance A specific physical, installed, power system component: a specific

generator, transformer, busbar, etc. Example: a piece of NKBA 0.6/1kV 4 x
35sm cable, 12.4 meters long.

Type A mathematical model for devices: general models for two-winding

transformers, two-winding transformers, busbars, etc. A type model only
contains the non-specific data valid for whole groups of power system
elements. Example: a NKBA 0.6/1kV 4 x 35sm cable type, named
”NKBA 4x35.TypLne”

Element A mathematical model for specific appliances. Most element models

only hold the appliance-specific data while the more general type-specific
data comes from a type-reference. Example: a model of a piece of NKBA
0.6/1kV 4 x 35sm cable, 12.4 meters long, named ”FC 1023.ElmLne”

Cubicle A cubicle is the connection point between a edge or branch element

and a node (represented by a busbar or terminal). It may be visualised as
a bay in a switch yard or a panel in a switchgear board. Elements such as
CT’s, protection equipment, breakers and so forth, are housed in the
cubicle, as one would expect to find in reality.

Node The mathematical or generic description for what are commonly known as
busbars in the electrical world. In PowerFactory nodes may be
represented by ”Busbars” or ”Terminals” of various kinds. These are
treated in the same manner in mathematical terms but treated slightly
differently in the database. As far as possible the user should use terminals
as Busbars can be somewhat inflexible. See also Busbars, Edge
Elements, Branch Elements.

Busbars Busbars are particular representations of nodes. Busbars are housed

in a Station folder and several busbars may be part of a station.

Edge Elements The elements between two nodes. May also be termed ’two
port element.’ Source, topological studies; picture a 3 dimensional box, the
corners of the box would be called the nodes, and the edges between
corners are hence ’edges.’ See also nodes, branch elements.

Glossary 1
DIgSILENT PowerFactory Glossary

Branch Elements A one port element connected to a node, such as a load or a

machine. See also nodes, edge elements.
Class A class is a template for an element, type or other kind of objects like
controller block diagrams, object filters, calculation settings, etc. Examples:
• The ’TypLne’ class is the type model for all lines and cables
• The ’ElmLne’ class is an element model for a specific line or cable
• The ’ComLdf’ class is a load-flow command
• The ’EvtSwitch’ class is an event for a switch to open or close during
simulation
Object An object is a specific item stored in the database. Examples are
specific type or element models which have been edited to model specific
devices or appliances. Examples: the element ”FC 1023.ElmLne”, the type
”NKBA 4x35.TypLne”, the load-flow command ”3Phase.ComLdf”
Grid A Grid is a collection of power system elements which are all stored in one
so-called “Grid Folder” in the database. Normally, a grid forms a logical
part of a power system design, like a the MV distribution system in a
province, or the HV transport system in a state.
System Stage A system stage is an alternative design or variation for a
particular grid. A system stage is stored in a system stage folder, which
keeps track of all differences from the design in the higher hierarchical
level. The highest level is formed by the base case grid folder. It is possible
to have system stages of system stages.
Base Case A base case is the highest level in a tree of hierarchical system
stage designs. It is the basic power system design, for which one or more
alternative designs may be created and analyzed. The base case is always
stored in a grid folder.
Study Case A study case is a folder which stores a list of references or
shortcuts to grid or system stage folders. These folders are (de)activated
when the calculation case folder is (de)activated.
Elements in the grid folders that are referenced by the study case form the
’calculation target’ for all calculation functions. Elements in all other,
non-active, grid folders are not considered for calculation.
Besides the list of active folders, the calculation case also stores all
calculations commands, results, events, and other objects which are, or
have been, used to analyze the active power system.
Project All power system definitions and calculations are stored and activated in
a project. The project folder therefore is a basic folder in the user’s
database tree. All grids that make out the power system design, with all
design variants, study cases, commands, results, etc. are stored together
in a single project folder.

Glossary 2
DIgSILENT PowerFactory Glossary

Result Object A result object keeps one or more lists of parameters which are
to be monitored during a calculation. Results objects are used for building
calculation result reports and for defining virtual instruments.

Virtual Instrument A virtual instrument is a graphical representation of

calculation results. It may be a line or bar graph, a gauge, a vector
diagram, etc.
A virtual instrument gets its values from a result object.

Block Definition A block definition is a mathematical model which may be used

in other block definitions or in a composite model. Examples are all default
controllers (i.e. VCO’s, PSS’s, MDM’s), and all additional user-defined DSL
models. A block definition is called “primitive” when it is directly written in
DSL, or “complex” when it is build from other block definitions, by drawing a
block diagram.

Block Diagram A block diagram is a graphical representation of a DSL model,

i.e. a voltage controller, a motor driven machine model or a water turbine
model. Block diagrams combine DSL primitives and block definitions
created by drawing other block diagram.
The block models thus created may (again) be used in other block
diagrams or to create composite frames.

DSL primitive A DSL primitive is the same as a primitive block definition. A

DSL primitive is written directly in DSL without the use of a block diagram.
Examples are PID controllers, time lags, simple signal filters, integrators,
limiters, etc. DSL primitives are normally used to build more complex block
definitions.

Slot A slot is a place-holder for a block definition in a composite frame. A

composite model is created from a composite frame by filling one or more
slots with an appropriate object.

Composite Frame A composite frame is a special block diagram which defines

a new stand-alone model, mostly without in- or outputs. A composite frame
is principally a circuit in which one or more slots are connected to each
other.
A composite frame is used to create composite models by filling the slots
with appropriate objects. The composite frame thus acts as template for a
specific kind of composite models.

Composite Model A composite model is a specific combination of

mathematical models.These models may be power system elements such
as synchronous generators, or block definitions, such as voltage
controllers, primary mover models or power system stabilizers.
Composite models may be used to create new objects, such as protection
devices, to ‘dress-up’ power system elements such as synchronous

Glossary 3
DIgSILENT PowerFactory Glossary

machines with controllers, prime movers models, etc., or for the

identification of model parameters on the basis of measurements.
Virtual Instrument Panel Virtual instrument panels ((ViPage)) are one of the
possible types of pages in a Graphics Board Window. Virtual instrument
panels are used to create and show virtual instruments. Each virtual
instrument panel may contain one or more virtual instruments.
Graphics Board Window The graphics board window is a multi document
window which contains one or more graphical pages. These pages may be
single line graphics, virtual instrument pages, block diagrams, etc.
The graphics board shows page tabs when more than one page is present.
These tabs may be used to change the visible page or to change the page
order by dragging the page tab.
Page Tabs Page tabs are small indexes at the edge (mostly on the top or
bottom) of a multi-page window. The tabs show the titles of the pages.
Left-clicking the page tab opens the corresponding page. Page tabs are
used in object dialogues, which often have different pages for different
calculation functions, and in the Graphics Board Window, when more than
one graphical page is present.
Drag and Drop “Drag and Drop” is a method for moving an object by left clicking
it and subsequently moving the mouse while holding the mouse button
down (“dragging”). Releasing the mouse button when the new location is
reached is called “dropping”. This will move the object to the new location.
DAQ Abbreviation for “Data Acquisition”.
DPL Abbreviation for “DIgSILENT Programming Language”.
Lost load A system load that is disconnected from the supply as a direct result
of one or more system failures by intervention of automatic protection
devices. A system load cannot be lost partly.
Shed load A system load that is disconnected from the supply as result of one
or more system failures by intervention of a system operator. A system
load may be shed up to a certain percentage.
Stochastic A quantity is said to be stochastic when its value is random and thus
unknown. The range of possible values, however, is known as well as the
likelihood of these possible values. The number of eyes thrown with a dice
is random, the possible outcomes are {1,2,3,4,5,6} and the likelihood is
f rac16 for each outcome. For a continuous range of possible outcomes,
the likelihood is a continuous function, which is called the Probability
Density Function or “PDF”.
Statistic Statistic calculation methods are used to analyze stochastic quantities.
A simple example is the method for calculating a mean repair duration by
dividing the total time spend repairing by the number of repairs performed.

Glossary 4
DIgSILENT PowerFactory Glossary

Information obtained by using statistic methods on measured data can be

used to build stochastic models of the observed equipment.

Outage The removal of a primary component from the system.

Forced Outage The unplanned removal of a primary component from the

system due to one or more failures in the system. A failure does not have
lead to lead to an outage, for instance the failure of a transformer tap
changer.

Scheduled Outage The planned removal of a primary component from the

system.

Maintenance The planned removal of one or more primary components from

the system.

Spare Unit A reserve component, not connected to the system, which may be
used as a replacement for a component on outage by switching or
replacing.

Failure The event in which a component does not operate as intended or stops
operating as intended. An example of the first kind is a circuit breaker that
fails to strip, an example of the second kind is a transformer that is tripped
by its Buchholz relay.

Hidden Failure An undetected change of a component which will lead to the

failure of the component the next time it is required to operate, unless it is
inspected and repaired first.

Active Failure A failure of a component which activates the automatic

protection system. Active failures are always associated by short-circuits.

Passive Failure A failure of a component which does not activate the automatic
protection system.

Repair The restoration of the functionality of a component, either by replacing

the component or by repairing it.

Interruption An unplanned zero-voltage situation at one or more load points

due to outages in the system.

Contingency The state of a system in which one or more primary components

are on outage. The level of a contingency is determined by the number of
primary components on outage. A “k-Level” contingency is thus the state of
a system in which exactly k primary components are on outage.

Adequacy The ability of the electrical power system to meet the load demands
under various steady state system conditions.

Security The ability of the system to meet the loads demands during and after a
transient or dynamic disturbance of the system.

Glossary 5
DIgSILENT PowerFactory Glossary

Availability The fraction of time a component is able to operate as intended,

either expressed as real fraction or as hours per year.

Redundant Unit A component which outage will never lead to an interruption in

the base state which cannot be restored by normal switching actions (i.e
normal network reconfiguration) alone.

Base State The state of the system were all components are able to operate as
intended.

(n-1) system A system for which all relevant components are redundant units.

(n-k) system A system for which the outage of any k or less components will
never lead to an interruption which cannot be restored by normal switching
actions (i.e normal network reconfiguration) alone.

Distribution Function The distribution function for the stochastic quantity X

equals the cumulative density function CDF(x).
CDF(x) = the probability of X to take a value smaller than x.

Probability Density Function The function PDF(x), describing the probability

of the stochastic quantity to take a value from an interval around x, divided
by the length of that interval. The PDF(x) is the derivative of the CDF(x).

Hazard Rate Function The function HRF(x), describing the probability of a

stochastic quantity to be larger than x+dx, given the fact that it is larger
than x, divided by dx. The hazard rate may thus describe the probability of
an element to fail in the next period of time, given the fact that it is still
functioning properly. The hazard rate is often used to describe ageing and
wear out. A famous example is the so-called “bath-tub” function which
describes the probability of a device to fail in the next period of time during
wear-in, normal service time and wear-out.

Glossary 6
Index
Index
Index

(n-1) system, 6 ASCII Result Export, 24-487

(n-k) system, 6 asin
DPL, 26-527
abs DSL, 21-427
DPL, 26-527 Assignment, 26-527
DSL, 21-427 ASUI, 18-318
ACCI, 18-318 atan
ACIF, 18-318 DPL, 26-527
ACIT, 18-318 DSL, 21-427
acos Automating tasks, 5-83, 26-521
DPL, 26-527 Availability, 6, see Reliability
DSL, 21-427 assessment (18-295)
Active Failure, 5
Active Power Control Background,VI Panels, 24-457
Load-Flow Calculations, 10-194 Backup data, 5-74
Add Base Case, 2
VIs, 24-457 Base State, 6
Adding a Grid, 6-97 Basic Options
Adding a Study Case, 6-101 Load-Flow Calculations, 10-193
Adequacy, 5 Batch Commands, 5-83
Adjusted by load scaling, 8-180 BlkDef, 21-411
Administrator, 3-27 Block Definition, 20-393
Advanced Options Composite Frame, 20-386
Load-Flow Calculations, 10-195 Drawing, 20-395
Advanced Simulation Options Model Definition, 20-393
Load-Flow Calculations, 10-198 BlkDiv, 20-397
AENS, 18-318 BlkMul, 20-397
Affected customers, 18-318 BlkRef, 20-396
aflipflop, 21-429 BlkRSwt, 20-397
DSL, 21-429 BlkSlot, 20-386
AID, 18-318 BlkSum, 20-397
Annex Documentation, 25-519 Block Definition, 3, 20-393
ANSI/IEEE damage curves, 12-258 Block Diagram, 3
Appearance of user-interface, 3-27 Block diagram
Append VIs, 24-457 Composite Frame, 20-386
Appliance, 1 Drawing, 20-395
Arguments, 26-537 Model Definition, 20-393
ASAI, 18-318 Block Reference, 20-396

Index
 BlockGraph, 20-395 ChaMat, 8-165, 8-169
Boolean expression, 26-528 Change Directory, 5-84
Branch Elements, 2 ChaPol, 13-273
Branch elements, 7-139 Characteristic, 8-165
Branch off, 8-163 Continous, 8-173
Branches Discreet, 8-171
creating, D-27 Discrete time, 8-167
Editing, D-33 Handling, 8-177
Break, 26-529 Importing, 8-176
Browser window, 5-57 One dimensional, 8-168
Busbar Reference, 8-177
Failure model, 18-333 Scalar, 8-167
Types, 8-154 Time, 8-176
Busbar Systems, 8-158 Two dimensional, 8-169
Cubicles, 8-154 ChaRef, 8-165, 8-177
Defining, 8-152 ChaScalar, 8-167
In station, 8-151 ChaVec, 8-165, 8-168, 8-171, 8-173,
Busbars, 1, 7-139, 8-150 8-176, 13-273
Connecting, D-27 ChaVecfile, 8-176
creating, D-25 Class, 2
Editing, D-30 Class Methods (DPL), 26-541
Buscoupler Classification
Methods, 26-543 BlkSlot, 20-386
Buttons, 2-18 Clear Data
Result Object, 25-495
Cable Clear Window, 5-84
Damage curve, 12-256 Coloring
Failure model, 18-334 feeder, 8-180
CAIDI, 18-318 Colour Representation Mode, 7-143
CAIFI, 18-318 ComCapo, 16-282
Calculate, 9-186 ComCd, 5-84
Calculation ComCl, 5-84
Comparison between cases, ComCls, 5-84
9-188 ComCv, 5-81
EMT Simulation, 19-356 ComDiff, 9-189
Initial Conditions, 19-359 ComDir, 5-84
RMS Simulation, 19-356 ComDocu, 25-516
Run Simulation, 19-376 ComDpl, 26-522
Simulation of Transients, 19-354 ComEd, 5-84
Calculation Blocks, 20-397 ComExit, 5-84
Calculation of Initial Conditions, ComFsweep, 13-268
19-359 Advanced Options, 13-269
Calling conventions, 26-537 Frequency, 13-269
ceil Impedance Calculation, 13-269
DPL, 26-527 Network-Representation, 13-268
DSL, 21-427 ComHldf, 13-266
ChaDisctime, 8-167

Index
 Advanced Options, 13-267 ComRel3, 18-306
Calculate, 13-266 ComRes, 25-497
Frequency, 13-267 Plot Data, 24-487
Network-Representation, 13-266 ComSh, 25-517
THD, 13-267 Filter Analysis, 13-270
ComIdent, 23-444 ComShc, 11-201
ComInc, 19-359 ComShcsweep, 12-246
ComLdf, 10-192 ComSim, 19-376
Troubleshooting, 10-199 ComSimoutage, 18-297
ComMan, 5-85 ComStop, 5-85
Command Line, 5-83 ComSys, 5-85
Commands ComTieopt, 17-291
Cd, 5-84 ComWr, 5-85
Cl, 5-84 Conductor Temperature, 11-209
Cls, 5-84 Connect, 7-136
Dir, 5-84 Connecting Blocks, 20-398
Ed, 5-84 Connecting Slots, 20-398
Exit, 5-84 Connecting subsystems, 7-140
Man, 5-85 Consider Protection Devices, 10-198
Op, 5-85 Constant Value, 24-483
Pause, 5-85 Constant X-Value, 24-483
Pr, 5-85 Constant Y-Value, 24-483
Rd, 5-85 Constants
Stop, 5-85 DPL, 26-527
Sys, 5-85 DSL, 21-427
Wr, 5-85 Contingency, 5
ComMod, 22-432 Contingency Analysis, 18-295
Common Model, 20-390 Continue, 26-529
Common model failures, 18-349 Continuous Scale, 8-173
ComNew, 6-94, 7-115 Controllers Modelling, 20-378
ComNmink, 18-296 conversion, GIS, 28-567
ComOp, 5-85 Converting Data
ComOutage, 18-300 PSS/E, 29-572
Comparing case results, 9-188 Copy, 7-134
ComPause, 5-85 cos
Composite Block Definition, 20-393 DPL, 26-527
Drawing, 20-395 DSL, 21-427
Composite Frame, 3, 20-386 cosh
Drawing, 20-395 DPL, 26-527
Composite Model, 3, 20-382 DSL, 21-427
Composite models, I-74 Coupler
ComPr, 5-85 Methods, 26-543
ComPrjdiff, 6-107 Create FFT Plot, 24-468
ComPsse, 29-572 Create local page format, 24-457
ComRd, 5-85 Create new Style, 24-457
ComRed, 14-277 Create VI, 24-457

Index
 Creating DiaGrfopts, 7-135
Step Response, 20-385 DiaLnefeed, 8-163
Creating a DSL Model, 21-402 dialogue Diagrams, 24-478
Creating DSL Models, 21-410 dialogue Drawings, 24-478
Creating VIs, 24-457 dialogue Plots, 24-478
Cubicle, 1 DiaPagetyp, 7-127
Options, 7-145 DIgSILENT Output Language,
Cubicles, 8-150 25-508
Current Transformer, 12-230 DIgSILENT Programming Language,
Current Transformer Type, 12-233 26-521
Curve-Input, 12-262 DIgSILENT Simulation Language
Curve-Tracking, 24-480 (DSL), 21-414
Directional Relay, 12-238
Damage Curve Directories
Conductor/Cable, 12-256 settings, 4-41
Motor start, 12-260 Disconnect Element, 7-136
Transformer, 12-258 Discrete Scale, 8-171
DAQ, 4 Display a List of Objects, 5-84
Data interface, 27-547 Distance-time diagram, 12-248
Data Manager Distortion Analysis, 13-265
Database, 5-43 Distribution Function, 6
settings, 4-39 Distribution system
Data manager, E-42 Reliability assessment, 18-306
Data reports, 25-495 Divisor, 20-397
Database do, 26-528
multi-user, 3-24 Docking View
database update, 9-189 Output Window, 25-499
DataManager, 5-45 Documentation, 25-495, 25-516
Datamode, 5-59 Documentation Annex, 25-519
Define DOLE, 5-77, 5-79, 27-547, 29-572
Feeder, 8-180 Dos command, 5-85
Defining a DSL Model, 21-402 double (DPL variable), 26-526
delay, 21-428 Double port elements, 7-139
DSL, 21-428 DPL, 4
Delete, 5-50, 7-133 Access to Objects, 26-531
Deleting graphics only, 7-134 Advances Options, 26-524
Demo account, 3-27 Assignement, 26-527
Dependent failures, 18-349 Boolean expression, 26-528
Device, 1 calling subroutines, 26-537
Device Data Documentation, 25-516 Class Methods, 26-541
DiaAnx, 25-519 Command Object, 26-522
DiaCalctab, 8-169 Command Set, 26-523
Diagram Constant Parameters, 26-526
Results, 24-479 Creating a Command, 26-522
Tools, 24-479 Execute, 26-523
Voltage Profile, 24-472 Expressions, 26-527
Diagram Vector, 24-469

Index
 External Methods, 26-541 Language, 21-414
external objects, 26-534 Macros, 21-423
Flow instructions, 26-528 Messages, 21-424
input, 26-530 Model Primitives, 21-410
Internal Methods, 26-538 Models, 21-423
internal objects, 26-532 Special Functions, 21-427
Macros, 26-537 Stability analysis, 20-378
Methods, 26-543 Standard Functions, 21-427
Object Methods, 26-540 Structure, 21-417
output, 26-530 Terms and abbreviations, 21-415
Remote Scripts, 26-535 Variable Units and Descriptors,
Script Editor, 26-524 21-417
Script Page, 26-524 Variables, 21-416
SEL, 26-533 DSL Model
Set Methods, 26-540 Creating, 21-402
Subroutines, 26-537 DSL primitive, 3
Syntax, 26-525
Variable Definition, 26-526 e()
VI Methods, 26-545 DPL, 26-527
DPL Command Set, 26-523 DSL, 21-427
DPL Editor, 26-524 Edge Elements, 1
DPL General Selection, 26-533 Edge elements, 7-139
Drag and Drop, 4 Edit and Browse, 7-113
Database to graphic, 7-116 Edit Data, 7-133
Draw existing net elements, 7-117 Edit Line Points, 7-136
Draw Radial Network Automatically, Edit Relevant, 9-187
24-475 Editing
Drawing area, 7-132 detail mode, 5-59
Drawing generators and machines, In browser window, 5-57
7-139 object mode, 5-58
Drawing lines, transformers and Editing a Block Definition, 21-411
loads, 7-139 Editor
drwbrowse, 7-135 settings, 4-41
DSL, 21-414 EIC, 18-318
Common Model, 20-390 Eigenvalue Calculation, 22-432
Defining Models, 21-410 Background, 22-432
Definition Code, 21-417 Perfoming a Calculation, 22-434
Equation code, 21-421 Theory, 22-432
Equation statement, 21-421 Eigenvalues, 22-432
Events, 21-424 Eigenvectors, 22-432
Example, 21-425 Element, 1
Functions, 21-427 ElmComp, 20-382
General syntax, 21-415 Slot assignment, 20-382
Initial conditions, 21-418 ElmCompare, 23-443
Inserting Equations, 21-411 ElmDsl, 20-390
Introduction, 21-405 ElmFeeder, 8-180
ElmLne, 8-162

Index
 ElmNet, 5-87, 6-94, 6-97 Export data, 5-74
Elmrelay, 12-237 Expressions, 26-527
ElmRes, 19-367, 25-495 External Methods (DPL), 26-541
ElmStat, 8-151 External objects, 26-534
ElmTerm, 8-158
else, 26-528 Failure, 5
Embedded Graphs, 24-478 Failure Effect Analysis, 18-311
Encrypt a Macro, 21-411 Failure Model
ENS, 18-318 Busbar, 18-333
Equivalent Network, 14-277 Cable, 18-334
Euler Constant Line, 18-334
DPL, 26-527 Synchronous machine, 18-336
DSL, 21-427 Terminal, 18-333
event, 21-431 Transformer, 18-335
Event Function Fault clearance, 18-311
DSL, 21-431 Fault separation, 18-311
Event Object, 19-369 FEA, 18-311
Events, I-76 Feeder
Events of Loads, 19-372 Methods, 26-545
Events of Synchronous Feeder Folder, 8-184
Machines, 19-372 Feeder Object, 8-180
Intercircuit Faults, 19-372 Feeder options, 7-145
Outage of Element (Sim), 19-373 Feeder Position, 8-163
Save Results (Sim), 19-373 Feeder scaling, 8-180
Set Integration Step Size, 19-373 Feeders, 8-180
Set Parameter, 19-371 FFT Plot, 24-468
Short-Circuit, 11-204, 19-372 File
Switching, 19-371 Restore data, 5-74
EvtLod, 19-372 Save data, 5-74
EvtOutage (Sim), 19-373 file, 21-429
EvtParam, 19-371 DSL, 21-429
EvtShc, 19-372 Filter
EvtShcll, 19-372 Methods, 26-543
EvtStep, 19-373 Filter for Curves, 24-486
EvtSwitch, 19-371 Find Object, 5-52
EvtSym, 19-372 Flexible page tab, 5-63
EvtTrigger (Sim), 19-373 flipflop, 21-429
Exit DIgSILENT, 5-84 DSL, 21-429
exp floor
DPL, 26-527 DPL, 26-527
DSL, 21-427 DSL, 21-427
Export Flow instructions, 26-528
Result Object, 25-497 Folder for Feeders, 8-184
Export Data for, 26-528
settings, 4-39 Forced Outage, 5
Spreadsheet Format, 5-75 Form
Methods, 26-545

Index
 Formatted Labels, 24-482 methods, 26-545
Forms, 25-505 Graphics Board Window, 4
frac Graphs, Embedded, 24-478
DPL, 26-527 Grid, 2
DSL, 21-427 Adding to Project, 6-97
Frame, Composite, 20-386 Creating Project, 6-94
Frame, composite
Drawing, 20-395 Harmonic Load-flow
Freeze mode, 7-119 Advanced Options, 13-267
Frequency Analysis, 13-265 Calculate, 13-266
Frequency Dependency, 13-273 Command, 13-266
Frequency Relay, 12-239 Frequency, 13-267
Frequency Sweep Network-Representation, 13-266
Advanced Options, 13-269 THD, 13-267
Command, 13-268 Harmonic Sources
Frequency, 13-269 Modelling, 13-271
Impedance Calculation, 13-269 Harmonics, 13-265
Network-Representation, 13-268 Defining Results, 13-275
Functions Filter Analysis, 13-270
DPL, 26-527 Frequency Dependency, 13-273
DPL Class, 26-541 Harmonic Load-flow, 13-266
DPL external, 26-541 Harmonic Sources, 13-271
DPL internal, 26-538 Results Variables, 13-275
DPL objects, 26-540 Waveform Plot, 13-274, 24-476
DPL sets, 26-540 Hazard Rate Function, 6
DPL VI, 26-545 Hidden Failure, 5
DSL, 21-427 HMC, 13-265
settings, 4-41 Results, 13-275
Fuse Model, 12-240 Icons, 2-18
General Filter, 5-52 Identification of parameter, 23-439
General selection IEAR, 18-318
DPL, 26-533 if, 26-528
GIS conversion, 28-567 Ignore Composite Elements, 10-198
Gis2Dole, 28-567 Impedance Frequency
Global library Characteristics
settings, 4-39 Command, 13-268
Graphic, 7-110 Import Data
Graphic Board, 7-110 Build Single Line Graphic, 7-117
Layers, 7-123 Older Versions, 5-81
Options, 7-125, 7-129 PSS/E, 29-572
Right mouse menus, 7-125 Spreadsheet Format, 5-75
Settings, 4-39, 7-125 Import data, 5-74
Graphic Windows Imported power systems, 7-116
Basic functions, 7-110 Importing
PageTab, 7-113 Characteristic, 8-176
Graphics Board inc, 21-418

Index
 Inc(), 21-418 Load-Flow Calculations, 10-196
inc0, 21-418
Inc0(), 21-418 Label
incfix, 21-418 Border, 24-482
IncFix(), 21-418 Form, 24-482
Individual Colour, 7-135 Format Label, 24-482
Initial conditions (DSL), 21-418 Reconnect with..., 24-482
Input instruction, 26-530 Text Label, 24-481
Input of Curves, 12-262 Value Label, 24-481
Input Window, 5-83 Language
Insert a branch off, 8-163 Output, 25-508
Insert a T-off, 8-163 Language dependent text, 25-511
Inserting DSL Equations, 21-411 lapprox, 21-430
Instantaneous Overcurrent Relay, DSL, 21-430
12-240 lapprox2, 21-430
int (DPL variable), 26-526 DSL, 21-430
IntCase, 5-89, 6-101 Level of DSL Models, 21-411
Interactive instructions, 26-530 License key, 3-24
Internal DPL objects, 26-532 License server settings, 3-24
Internal Methods (DPL), 26-538 lim, 21-427
Internal Variables, 21-416 DSL, 21-427
Interruption, 5 Limiting Signals
Interruption costs, 18-343 BlkSlot, 20-386
intervalinc, 21-418 Limits, 21-417
Intervalinc(), 21-419 Limits Function (DSL), 21-417
IntEvt, 19-369 limits(), 21-417
IntEvtshc, 11-204 limstate, 21-428
IntFeeder, 8-184 DSL, 21-428
IntFolder, 5-86 Line
IntForm, 25-505 Failure model, 18-334
Output Language, 25-508 Methods, 26-543
IntGrfnet, 7-129 Line Route
IntLogon, 3-24 Methods, 26-544
IntMat, 5-90 Line Type
IntMon, 5-64, 5-73 Methods, 26-544
Methods, 26-542 Linkage between data and graphics,
IntMonsel, 5-63 4-39
Intnewobj, 5-47 ln
IntPlot DPL, 26-527
methods, 26-546 DSL, 21-427
IntPrj, 6-95, 6-97, 6-101 Load
IntRef, 5-92 Interruption costs, 18-343
IntVariant, 5-88, 6-105 Shedding, 18-345
invlapprox, 21-430 Transfer, 18-345
DSL, 21-430 Load damage functions, 18-343
Iteration Control Load level
store, 9-189

Index
 Load Profiles, 8-165 Maintenance, 5
Load Scaling, 8-182 Mark All, 7-133
Load state estimation, 8-180 Markov Model, 18-329
Load-Flow Mathematical Functions, 21-427
Active Power Control, 10-194 Matrix
Advanced Options Page, 10-195 Methods, 26-543
Advanced Simulation Options, Matrix object, 5-90
10-198 max
Basic Options Page, 10-193 DPL, 26-527
Command Ldf, 10-192 DSL, 21-427
Iteration Control, 10-196 Measurement and identification,
Low Voltage Analysis, 10-195 23-439
Optimal, 15-281 Method
Outputs Page, 10-194 Definition, 26-538
Troubleshooting, 10-199 min
Loadflow, D-34 DPL, 26-527
Local DPL objects, 26-532 DSL, 21-427
Local load model, 18-338 Modal Analysis
log Performing a Calculation, 22-434
DPL, 26-527 Modal analysis, 22-432
DSL, 21-427 Background, 22-432
Log On Page, 3-26 Theory, 22-432
logarithm Model Definition, 20-393
DPL, 26-527 Drawing, 20-395
DSL, 21-427 modulo
Logon, 3-24 DPL, 26-527
Advanced Settings, 3-27 DSL, 21-427
Appearance, 3-27 Motor start, H-67
License, 3-24 Motor Start Curve, 12-260
Log on, 3-26 Move, 7-136
Log On Page, 3-26 Multi-user Database, 3-24
LOOP, 25-515 Multiplier, 20-397
Loop control, 26-529
loopinc, 21-418 N-K simulation, 18-295
Loopinc(), 21-419 Network Equivalent, 14-277
Lost load, 4 Network Reduction, 14-277
Low Voltage Analysis New DPL Command, 26-522
Load-Flow Calculations, 10-195 New Position, 8-163
LPEAR, 18-318 newtoninc, 21-418
LPEIC, 18-318 Newtoninc(), 21-419
LPENS, 18-318 Node, 1
LPES, 18-318 Num(), 21-424
LPIF, 18-318 Number of customers, 18-318
LPIT, 18-318 Object, 2
Macros, 21-411, 26-537 object (DPL variable), 26-526
Main toolbar, 2-18 Object Methods (DPL), 26-540

Index
 Object mode, 5-58 Creating a new subplot, 24-458,
Open File, 5-85 24-459
Open Tie Optimization Curve-Tracking, 24-480
Command, 17-291 Editing a Subplot, 24-459
Optimal Capacitor Placement Export Data, 24-487
Command, 16-282 Export Graphic, 24-487
Optimal Load-Flow, 15-281 FFT Plot, 24-468
Outage, 5 Filter, 24-486
Outage simulation, 18-295 Grid, 24-488
Output instruction, 26-530 Insert Label, 24-480
Output Language, 25-508 Results, 24-479
Output Results, 25-517 Schematic Diagram, 24-474
Output Window, 25-499 Schematic Visualisation, 24-474
settings, 4-40 Setting the X-Axis, 24-461
Outputs Setting the y-Axis, 24-462
Load-Flow Calculations, 10-194 Specifying Curves, 24-464
Overcurrent Relay SubPlot, 24-459
Instantaneous, 12-240 SubPlot (2y), 24-465
Time, 12-244 Tools, 24-479
Overview, 2-6, B-4 Two y-Axes, 24-465
Overvoltage relay, 12-245 Various Tools, 24-488
Vector Diagram, 24-469
Pack a Macro, 21-411 Virtual instruments, 24-449
Page Tab Graphic Windows, 7-113 Voltage Profile, 24-472
Page Tab Graphic Windows, Menu, Waveform, 24-476
7-115 Window, 24-452
Page tab, flexible, 5-63 X-Y Plot, 24-466
Page Tabs, 4 Plotting, I-79
Paper size, 7-132 Pop up dialogue Box, 5-84
Parameter Characteristics, 8-165 Position Feeder, 8-163
Parameter identification, 23-439 pow
Parameter Range, 8-165 DPL, 26-527
Passive Failure, 5 DSL, 21-427
Paste, 7-134 Power Quality, 13-265
Path Power restoration, 18-311
Methods, 26-545 Print, 5-85
pi() Print Graphic, 7-127
DPL, 26-527 Printing paper, 7-132
DSL, 21-427 Probability Calculation, see
twopi() (DPL), 26-527 Reliability assessment
twopi() (DSL), 21-427 (18-295)
picdro, 21-429 Probability Density Function, 6
DSL, 21-429 Program appearance, 3-27
Place Feeder Dialog, 8-163 Programming language, 26-521
Placing Signals, 20-398 Programming Language DPL,
Plot 26-525
Border, 24-487

Index
 Project, 2 State Enumeration, 18-306
restore, 5-74 Reliability Indices, 18-318
save, 5-74 RelIoc, 12-240
Projects, 6-93 RelLogic, 12-242
Add a grid, 6-97 RelMeasure, 12-243
Add study case, 6-101 RelToc, 12-244
Add System Stage, 6-105 RelUlim, 12-245
Comparing, 6-107 Remote system stage, 6-105
Creating, 6-94 Repair, 5
Expanding, 6-95 Report Language, 25-508
Protection Relay, 12-237 Reporting, 25-505
Protocol Output Reports, 25-495
Result Object, 25-495 Reset settings
PSS/E, 29-572 result box, 7-146
PSS/E conversion, 29-572 Resize, 20-400
Restore, 5-50
RAM Calculations, see Reliability Result box
assessment (18-295) move, 7-146
Range of Values, 8-165 reference points, 7-146
Rebuild, 7-127 reset settings, 7-146
Reconnect Element, 7-136 Result box format, D-36
Recycle Bin, 5-50 Result Boxes, 7-146
Redirect output, 5-85 Editing, 7-148
Reducing Network, 14-277 Result Object, 3
Redundant Unit, 6 Result Report Language, 25-508
Reference Result variables, I-78
Characteristic, 8-177 Results, 25-495
Reference points Eigenvalue Calculation, 22-436
result box, 7-146 Methods, 26-544
Reference to object, 5-92 Modal Analysis, 22-436
Relay Results Output, 25-517
Directional, 12-238 Revision, 6-105
Frequency, 12-239 Risk assessment, 18-306
Fuse Model, 12-240 root
Instantaneous Overcurrent, DPL, 26-527
12-240 DSL, 21-427
Time overcurrent, 12-244 Rotate, 7-135
Under/Over voltage, 12-245 round
Relay Model, 12-237 DPL, 26-527
RelDir, 12-238 DSL, 21-427
Relevant Objects, 9-187
RelFmeas, 12-239 SAIDI, 18-318
RelFrq, 12-239 SAIFI, 18-318
RelFuse, 12-240 sapprox, 21-430
Reliability Assessment, 18-295 DSL, 21-430
Introduction, 18-295 sapprox2, 21-430
Network, 18-306 DSL, 21-430

Index
 Save Project, 5-74 SetGrfPage, 7-132
SCADA, 27-547 SetLevelvis, 7-123
Scales, 8-165 SetMotorst, 12-260
Continuous, 8-173 SetOcplt, 12-260
Discrete, 8-171 Setselect, 5-91
Time, 8-175 SetTime, 8-175
Scaling paper, 7-132 Settings
Scheduled Outage, 5 Calculation, 24-477
Schematic Diagram, 24-474 data manager, 4-39
Schematic Visualisation Directories, 4-41
Bus Index, 24-475 Editor, 4-41
Distance, 24-475 functions, 4-41
Plot, 24-474 General, 4-38
Script (DPL), 26-525 Graphics, 4-39
SEAR, 18-318 output window, 4-40
Search and find, 5-52 SetTitm, 7-144
Secondary Winding (VT), 12-235 SetTrfdmg, 12-258
Secondary Winding Type (VT), SetUser, 4-37
12-235 SetViPage, 24-452
Sector customer damage function, SetVipage, 24-449
18-343 methods, 26-546
Security, 5 SetWave, 24-477
SEL, 26-533 Shed load, 4
select, 21-428 Shedding of load, 18-345
DSL, 21-428 Shift to Layer, 7-123
Select Style, 24-457 Short-Circuit
Selection, 5-91 Options, 11-206
Methods, 26-545 Sweep, 12-246
Sequence Short-circuit, D-39
BlkSlot, 20-386 Short-Circuit Calculation
Serial number, 3-24, 3-25 Advanced Options, ANSI
SES, 18-318 Method, 11-212
set (DPL variable), 26-526 Advanced Options, Complete
Set Constant Method, 11-213
X-Value, 24-483 Advanced Options, IEC/VDE
Y-Value, 24-483 Methods, 11-209
Set Methods (DPL), 26-540 Basic Options, 11-206
Set of objects, 5-91 Basic Options, ANSI Method,
SetBussys, 8-154 11-211
SetColgr, 7-143 Basic Options, Complete
SetCondmg, 12-256 Method, 11-213
SetCrvfilt, 24-486 Basic Options, IEC/VDE Method,
SetCubop, 8-154 11-208
SetDesktop Command, 11-201
methods, 26-545 Complete Method Theory,
SetFilt, 5-52 11-216

Index
 EvtShc, 11-204 limstate(), 21-428
Fault on line, 11-203 picdro(), 21-429
IEC Method Theory, 11-217 sapprox(), 21-430
Multiple Faults, 11-204 sapprox2(), 21-430
Options, 11-206 select(), 21-428
SetSelect, 11-206 time(), 21-428
Technical Background, 11-214 Special Functions
Show DSL, 21-427
Graphics, 24-449 Specifying Curves, 24-464
Show Results from two Simulations, Spectrum, 13-271
19-369 Spreadsheet
Signals Export To, 5-76
Connecting, 20-398 Import From, 5-76
Simulation, 19-354 sqr
Initial Conditions, 19-359 DPL, 26-527
Run, 19-376 DSL, 21-427
Simulation Language, 21-414 sqrt
Simulation of Transients, 19-354 DPL, 26-527
Initial Conditions, 19-359 DSL, 21-427
Run Simulation, 19-376 square root
sin DPL, 26-527
DPL, 26-527 DSL, 21-427
DSL, 21-427 Stability Analysis, 19-354, 20-378
Single port elements, 7-139 Initial Conditions, 19-359
sinh Run Simulation, 19-376
DPL, 26-527 StaCt, 12-230
DSL, 21-427 Standard Functions
Size, paper, 7-132 DSL, 21-427
Slot, 3, 20-386 Starting PowerFactory, 3-24
Assigning a Block Definition, State Enumeration
20-389 Reliability assessment, 18-306
Assignment, 20-382 State Variables, 21-416
Slots, 20-382 StatGraph, 8-160
Solving Load-Flows, 10-199 Stations, 8-158
Sources of Harmonics, 13-271 Cubicles, 8-154
Spare Unit, 5 Defining in data manager, 8-157
Special DSL Functions Defining in SLG, 8-155
aflipflop(), 21-429 Edit dialog, 8-157
delay(), 21-428 Feeder options, 7-145
event(), 21-431 Folder, 5-87
file(), 21-429 Statistic, 4
flipflop(), 21-429 StaVt, 12-233
invlapprox(), 21-430 StaVtsec, 12-235
lapprox(), 21-430 Step Size, 19-362
lapprox2(), 21-430 StoChaLod, 18-340
lim(), 21-427 Stochastic, 4

Index
 Stochastic Load Model, 18-338 DSL, 21-427
Stochastic Model, 18-329 tanh
StoCommon, 18-349 DPL, 26-527
StoLod, 18-338 DSL, 21-427
StoMaint, 18-349 Tap positions
Stop Redirect Output, 5-84 store, 9-189
Store results, 9-189 Temperature
StoSym, 18-336 Pre fault, 11-209
StoTypbar, 18-333 Terminal
StoTyplne, 18-334 Failure model, 18-333
StoTypTrf, 18-335 Terminals, 7-137, 8-150, 8-158
Straight Line, 24-485 Time
Secant, 24-485 Methods, 26-542
string (DPL variable), 26-526 time, 21-428
Study Case, 2 DSL, 21-428
Adding to Project, 6-101 Time Overcurrent Relay, 12-244
Defining, 6-98 Time Scale, 8-175
Renaming, C-21 time()
Study Cases DPL, 26-527
Active Graphics, 7-110 DSL, 21-427
Style, 24-489 Time-distance diagram, 12-248
Create new Style, 24-490 Toolbar definitions, 2-18
Edit Style, 24-491 Transfer of load, 18-345
Edit Style of clicked Element, Transformer
24-493 Current, 12-230
Save as Predefined VI, 24-493 Current Type, 12-233
User Defined, 24-489 Damage curve, 12-258
Subplots, 24-459 Failure model, 18-335
Subplots (2y), 24-465 Voltage, 12-233
Subsystem interconnections, 7-140 Voltage Type, 12-236
Summation Point, 20-397 Transient Analysis, 19-354
Sweep short-circuit, 12-246 Initial Conditions, 19-359
Switch Run Simulation, 19-376
Methods, 26-544 Transient analysis, I-74
Switch for Block Diagrams, 20-397 Transition Rates, 18-329
Synchronous machine TriCont, 8-173
Failure model, 18-336 TriDisc, 8-171
Syntax (DPL), 26-525 TriFreq, 13-273
System Stage, 2 Trigger
Adding to Project, 6-105 Scale, 8-165
Reducing, 6-107 trigonometric
System stage DPL, 26-527
Remote, 6-105 DSL, 21-427
Trigonometric Functions, 21-427
T-off, 8-163 TriTime, 8-175
tan trunc
DPL, 26-527

Index
 DPL, 26-527 VI, 24-449
DSL, 21-427 VI Methods (DPL), 26-545
Tutorial Errors, B-16 VI Panel
Tutorial Manager, D-23 Background, 24-457
twopi() Context Sensitive Menu, 24-457
DPL, 26-527 Creating VIs, 24-457
DSL, 21-427 Edit Variables, 24-455
TypCt, 12-233 Graphics Board, 24-452
Type, 1 Moving, Resizing, 24-454
Types Page Format, 24-455
Busbar, 8-154 Results, 24-456
Cubicle, 8-154 Scale Axes automatically, 24-453
TypHmcCur, 13-271 Styles, 24-458
TypStat, 8-151 Tile, 24-454
TypVt, 12-236 Title Block, 24-456
TypVtsec, 12-235 Virtual Instrument, 3
Tools, 24-479
Undervoltage relay, 12-245 Virtual Instrument Panel, 4
Undo, 7-134 Virtual Instruments, 24-449
Undock VisDefcrv, 12-262
Output Window, 25-499 VisFft, 24-468
Update VisHrm, 24-476
Result Object, 25-495 Visibility, 7-123
Update database, 9-189 VisLabel, 24-482
Updating Slots, 20-385 VisLegend, 7-144
User Accounts, 3-24, 3-27 VisOcplot, 12-254
User Interface, 2-7, B-5 VisPlot, 24-459
User Settings, 4-37 methods, 26-546
User-interface appearance, 3-27 VisPlot2, 24-465
Value Range, 8-165 VisPlottz, 12-248
Vardef(), 21-417 VisTitle, 7-144
vardef(varname), 21-417 VisValue, 24-481
Variable Definitions, 26-526 VisVec, 24-469
Variable Manager, 5-85 VisXvalue, 24-483, 24-485
Variable Set VisXyplot, 24-466
Methods, 26-542 Voltage Profile Plot, 24-472
Variable units and descriptors, Voltage Sag Assessment, 18-295
21-417 Voltage Transformer, 12-233
Variant, 6-103 Secondary Winding, 12-235
Creating, 6-105 Secondary Winding Type,
Reducing, 6-107 12-235
System Stage Folder, 6-102 Voltage Transformer Type, 12-236
Varnm, 21-417 VT, 12-233
Vector Secondary Winding, 12-235
Methods, 26-543 Secondary Winding Type,
Vector Diagram, 24-469 12-235

Index
 Waveform Plot, 24-476
Calculation Settings, 24-477
Weibull distribution, 18-329
Weibull-Markov Model, 18-329
while, 26-528
Write File, 5-85

X-Y Plot, 24-466

Zones, 8-185
Zoom All, 7-126
Zoom In, 7-126
Zoom Out, 7-126
Zooming, 7-126

Index