Chapter 4

PowerFactory Overview

The calculation program PowerFactory , as written by DIgSILENT , is a computer aided engineering

tool for the analysis of transmission, distribution, and industrial 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 optimiza-
tion.

“DIgSILENT " is an acronym for “DIgital SImuLation of Electrical NeTworks". DIgSILENT Version 7 was
the world’s first power system analysis software with an integrated graphical single-line interface. That
interactive single-line diagram included drawing functions, editing capabilities and all relevant static and
dynamic calculation features.

PowerFactory 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 results obtained with PowerFactory has been confirmed in a large number of implementations, by
organizations involved in planning and operation of power systems throughout the world.

To address users power system analysis requirements, PowerFactory was designed as an integrated
engineering tool to provide a comprehensive suite of power system analysis functions within a single
executable program. Key features include:

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 geometri-
cal or nameplate information).
5. Power system network configuration with interactive or on-line SCADA access.
6. Generic interface for computer-based mapping systems.

Use of a single database, with the required data for all equipment within a power system (e.g. line
data, generator data, protection data, harmonic data, controller data), means that PowerFactory can
easily execute all power simulation functions within a single program environment - functions such as
load-flow, short-circuit calculation, harmonic analysis, protection coordination, stability calculation, and
modal analysis.

Although PowerFactory includes some sophisticated power system analysis functions, the intuitive user
interface makes it possible for new users to very quickly perform common activities such as load-flow
and short-circuit calculations.

DIgSILENT PowerFactory 15, User Manual 9

CHAPTER 4. POWERFACTORY OVERVIEW

The functionality purchased by a user is configured in a matrix, where the licensed calculation functions,
together with the maximum number of busses, are listed as coordinates. The user may, as required,
configure the interface as well as some functions according to their requirements.

Depending on user requirements, a specific PowerFactory license may or may not include all the func-
tions described in this manual. As requirements dictate, additional functionality can be added to a
license. These functions can be used within the same program interface with the same network data.
Only additional data, as may be required by an added calculation function, need be added.

4.1 General Concept

The general PowerFactory program design concept is summarized as follows:

Functional Integration

DIgSILENT PowerFactory software is implemented as a single executable program, and is fully

compatible with Windows XP/Vista and Windows 7. The programming method employed allows
for fast selection of different calculation functions. There is no need to reload modules and
update or transfer data and results between different program applications. As an example, the
Load Flow, Short-Circuit, and Harmonic Load Flow analysis tools can be executed sequentially
without resetting the program, enabling additional software modules and engines, or reading and
converting external data files.

Vertical Integration

DIgSILENT PowerFactory software has adopted a unique vertically integrated model concept
that allows models to be shared for all analysis functions. Furthermore, studies relating to
“Generation", “Transmission", “Distribution", and “Industrial" analysis can all be completed within
PowerFactory . Separate software engines are not required to analyze separate aspects of
the power system, or to complete different types of analysis, as DIgSILENT PowerFactory can
accommodate everything within one integrated program and one integrated database.

Database Integration

Single Database Concepts:DIgSILENT PowerFactory provides optimal organization of data and

definitions required to perform various calculations, memorization of settings or software op-
eration options. The PowerFactory database environment fully integrates all data required for
defining Study Cases, Operation Scenarios, Single Line Graphics, textual and graphical Results,
calculation options, and user-defined models, etc. Everything required to model and simulate
the power system is integrated into a single database which can be configured for single and/or
multiple users.

Project Management: All data that defines a power system model is stored in “Project" folders
within the database. Inside a “Project" folder, “Study Cases" are used to define different stud-
ies of the system considering the complete network, parts of the network, or Variations on its
current state. This “project and study case" approach is used to define and manage power
system studies in a unique application of the object-oriented software principle. DIgSILENT
PowerFactory has taken an innovative approach and introduced a structure that is easy to use,
avoids data redundancy, and simplifies the task of data management and validation for users and
organizations. Additionally, the application of Study Cases and project Variations in PowerFactory
facilitates efficient and reliable reproduction of study results.

Multi-User Operation: Multiple users each holding their own projects or working with data
shared from other users are supported by a “Multi-user" database operation. In this case the
definition of access rights, user accounting and groups for data sharing are managed by a
database Administrator.

Offline Mode: In some instances, a network connection to a server database may not be

10 DIgSILENT PowerFactory 15, User Manual

 4.2. DATABASE, OBJECTS, AND CLASSES

available. To address this, PowerFactory provides functionality to work in Offline Mode. The
required project data is cached to the user’s local machine, which can then later be synchronized
to the server database. Offline Mode functionality includes the ability to lock and unlock projects,
edit projects as read-only, and limit the database size on the computer(s) working in offline mode.

Customization

By default, “Base Package" and “Standard" user profiles are available in PowerFactory . Profiles
can be selected from the main menu under Tools → Profiles. The “Base Package" profile limits
the icons displayed on the main toolbar to those typically used by new users, such as load-flow
and short-circuit commands. The database Administrator can create and customize user profiles,
in particular:

• Customize the element dialogue pages that are displayed.

• Customize element dialogue parameters. Parameters can be Hidden (not shown) or Disabled
(shown but not editable).
• Fully configure Main Toolbar and Drawing Toolbar menus, including definition of custom DPL
Commands and Templates with user-defined icons.
• Customize Main Menu, Data Manager, and context-sensitive menu commands.

Chapter 6: User Accounts, User Groups, and Profiles (Section 6.5 Creating Profiles) details the
customization procedure.

Note: When right-clicking with the mouse button, the available menu options depend on the location of
the mouse pointer. For example, if a load is selected, the menu options are those appropriate for
loads, whereas when the mouse pointer is over the Output Window, the menu options are those
appropriate for the Output Window. These menus are collectively referred to as ’Context sensitive
menu’s’.

4.2 Database, Objects, and Classes

PowerFactory uses a hierarchical, object-oriented database. All the data, which represents power sys-
tem Elements, Single Line Graphics, Study Cases, system Operation Scenarios, calculation commands,
program Settings etc., are stored as objects inside a hierarchical set of folders. The folders are arranged
in order to facilitate the definition of the studies and optimize the use of the tools provided by the
program.

The objects are grouped according to the kind of element that they represent. These groups are
known as “Classes" within the PowerFactory environment. For example, an object that represents a
synchronous generator in a power system belongs to a Class called ElmSym, and an object storing the
settings for a load flow calculation belongs to a Class called ComLdf. Object Classes are analogous
to computer file extensions. Each object belongs to a Class and each Class has a specific set of
parameters that defines the objects it represents. As explained in Section 4.8 (User Interface), the edit
dialogues are the interfaces between the user and an object; the parameters defining the object are
accessed through this dialogue. This means that there is an edit dialogue for each class of objects.

Note: Everything in PowerFactory is an object, all the objects belong to a Class and are stored accord-
ing to a hierarchical arrangement in the database tree.

DIgSILENT PowerFactory 15, User Manual 11

CHAPTER 4. POWERFACTORY OVERVIEW

4.3 PowerFactory Simulation Functions

PowerFactory incorporates a comprehensive list of simulation functions, described in detail in Volume II

of the manual, including the following:

• Load Flow Analysis, allowing meshed and mixed 1-,2-, and 3-phase AC and/or DC networks
(Chapter 21: Load Flow Analysis).
• Low Voltage Network Analysis (Section 21.2.3: Advanced Load Options).

• Short-Circuit Analysis, for meshed and mixed 1-,2-, and 3-phase AC networks (Chapter 22: Short-
Circuit Analysis).
• Harmonic Analysis (Chapter 23: Harmonics Analysis).
• RMS Simulation (time-domain simulation for stability analysis, Chapter 26: Stability and EMT
Simulations).
• EMT Simulation (time-domain simulation of electromagnetic transients, Chapter 26: Stability and
EMT Simulations).
• Eigenvalue Analysis (Chapter 27: Modal Analysis / Eigenvalue Calculation).

• Model Parameter Identification (Chapter 28: Model Parameter Identification).

• Contingency Analysis (Chapter 29: Contingency Analysis).
• Reliability Analysis (Chapter 30: Reliability Assessment).
• Generation Adequacy Analysis (Chapter 32: Generation Adequacy Analysis).

• Optimal Power Flow (Chapter 33: Optimal Power Flow).

• Distribution Network Optimization (Chapter 35: Distribution Network Tools).
• Protection Analysis (Chapter 39: Protection).

• Network Reduction (Chapter 40: Network Reduction).

• State Estimation (Chapter 41: State Estimation).

4.4 General Design of PowerFactory

PowerFactory is primarily intended to be used and operated in a graphical environment. That is, data is
entered by drawing the network Elements, and then editing and assigning data to these objects. Data
is accessed from the graphics page by double-clicking on an object. An input dialogue is displayed and
the user may then edit the data for that object.

Figure 4.4.1 shows the PowerFactory Graphical User Interface (GUI) when a project is active. The GUI
is discussed in further detail in Section 4.8

12 DIgSILENT PowerFactory 15, User Manual

 4.4. GENERAL DESIGN OF POWERFACTORY

Figure 4.4.1: PowerFactory Main Window

All data entered for objects is hierarchically structured in folders for ease of navigation. To view the data
and its organization, a “Data Manager" is used. Figure 4.4.2 shows the Data Manager window. The
Data Manager is similar in appearance and functionality to a Windows Explorer window.

Within the Data Manager, information is grouped based on two main criterion:

1. Data that pertains directly to the system under study, that is, electrical data.
2. 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.

Figure 4.4.2: PowerFactory Data Manager

DIgSILENT PowerFactory 15, User Manual 13

CHAPTER 4. POWERFACTORY OVERVIEW

Note that most user-actions can be performed in both the Single Line Graphic and the Data Manager.
For example, a new terminal can be added directly to the Single Line Graphic, or alternatively created
in the Data Manager. In the latter case, the terminal could be shown in the Single Line Graphic by
“drawing existing net elements", by “dragging and dropping" from the Data Manager, or by creating a
new Graphical Net Object in the Data Manger (advanced).

4.5 Type and Element Data

Since power systems are constructed using standardized materials and components, it is convenient to
divide electrical data into two sets, namely “Type" data and “Element" data sets.

• Characteristic electrical parameters, such as the reactance per km of a line, or the rated voltage of
a transformer are referred to as Type data. Type objects are generally stored in the Global Library
or Project Library, and are shown in red. For instance, a Line Type object, TypLne ( ).
• Data relating to a particular instance of equipment, such as the length of a line, the derating
factor of a cable, the name of a load, the connecting node of a generator, or the tap position of a
transformer are referred to as Element data. Element objects are generally stored in the Network
Data folder, and are shown in green. For instance, a Line Element object, ElmLne ( ).

Consider the following example:

• A cable has a Type reactance of “X" Ohms/ km, say 0.1 Ohms/ km.

• A cable section of length “L" is used for a particular installation, say 600 m, or 0.6 km.
• This section (Element) therefore has an reactance of X * L Ohms, or 0.06 Ohms.

Note that Element parameters can be modified using Operation Scenarios (which store sets of network
operational data), and Parameter Characteristics (which can be used to modify parameters based on
the Study Case Time, or other user-defined trigger).

4.6 Data Arrangement

The PowerFactory database supports multiple users (as mentioned in 4.1) and each user can manage
multiple projects. “User Account" folders with access privileges only for their owners (and other users
with shared rights) must then be used. User accounts are of course in a higher level than projects.
Figure 4.6.1 shows a snapshot from a database as seen by the user in a Data Manager window, where
there is a User Account for “User", and one project titled “Project". The main folders used to arrange
data in PowerFactory are summarized below:

14 DIgSILENT PowerFactory 15, User Manual

 4.6. DATA ARRANGEMENT

Figure 4.6.1: Structure of a PowerFactory project in the Data Manager

4.6.1 Global Library

This global Library contains a wide range of pre-defined models, including:

• Type data for standard components such as conductors, motors, generators, and transformers.
• Standard control system frames, models, and macros (i.e. transfer functions and logic blocks,
etc).
• Standard CT, VT, fuse, and relay models.
• Pre-defined model templates, including:
– Battery System with frequency control (10 kV, 30 MVA).
– Double Fed Induction Wind Turbine Generator (0.69 kV, 2 MW).
– Fully Rated Converter Wind Turbine Generator (0.4 kV, 2 MW).
– Variable Rotor Resistance Wind Turbine Generator (0.69 kV, 0.66 MW).
– Photovoltaic System (0.4 kV, 0.5 MVA)

DIgSILENT PowerFactory 15, User Manual 15

CHAPTER 4. POWERFACTORY OVERVIEW

• Standard DPL scripts, including scripts to:

– Produce PV and QV curves.
– Minimize the Net Present Value of project (Variation) costs by varying the project service
date.
– Conduct time-sweep load flow calculations.

4.6.2 Project Library

The project Library contains the equipment Types, network operational information, DPL scripts, tem-
plates, and user-defined models (generally) only used within a particular project. A particular project
may have references to the project Library and / or global Library. The Project Library folder and sub-
folders are discussed in detail in Chapter 12 (Project Library).

4.6.3 Diagrams

Single Line Graphics are defined in PowerFactory by means of graphic folders of class IntGrfNet ( ).
Each diagram corresponds to a IntGrfNet folder. They are stored in the Network Diagrams folder
( ) of the Network Model. Single line diagrams are composed of graphical objects, which represent
components of the networks under study. Graphical components reference network components and
symbol objects (IntSym).

The relation between graphical objects and network components allows the definition and modification
of the studied networks directly from the Single Line Graphics. Network components can be represented
by more than one graphical object (many IntGrf objects can refer to the same network component).
Therefore, one component can appear in several diagrams.

These diagrams are managed by the active Study Case, and specifically by an object called the
Graphics Board. If a reference to a network diagram is stored in a Study Case’s Graphics Board,
when the Study Case is activated, the diagram is automatically opened. Diagrams can be easily added
and deleted from the Graphics Boards.

Each diagram is related to a specific Grid (ElmNet). When a Grid is added to an active Study Case, the
user is asked to select (among the diagrams pointing to that grid) the diagrams to display. References
to the selected diagrams are then automatically created in the corresponding Graphics Board.

Chapter 9 (Network Graphics (Single Line Diagrams)), explains how to define and work with single line
graphics.

4.6.4 Network Data

The Network Data folder holds network data (Element data) in “Grid" folders, network modification
information in “Variation" folders, and object Grouping information.

Grids

In PowerFactory , electrical network information is stored in “Grid" folders (ElmNet, ). A power system
may have as many grids as defined by the user. These grids may or may not be interconnected. As long
as they are active, they are considered by the calculations. Data may be sorted according to logical,
organizational and/or geographical areas (discussed further in Section 4.7: Project Structure).

An example of this approach is the Tutorial project provided with the Getting Started Manual. In this
project, a distribution network and a transmission network are created and analyzed separately. At a
later stage both networks are connected and the analysis of the complete system is carried out.

16 DIgSILENT PowerFactory 15, User Manual

 4.6. DATA ARRANGEMENT

Note: A Grid (and in general any object comprising the data model) is active when it is referred to by
the current study case. Only objects referred in the current (active) Study Case are considered for
calculation. In the Data Manager, the icon of an active Grid is shown in red, to distinguish it from
inactive Grids.

For details of how to define grids refer to Chapter 8.Basic Project Definition, Section 8.2 (Creating New
Grids).

Variations

During the planning and assessment of a power system, it is often necessary to analyze different vari-
ations and expansion alternatives of the base network. In PowerFactory these variations are modelled
by means of “Variations". These are objects that store and implement required changes to a network,
and can be easily activated and deactivated. The use of Variations allows the user to conduct studies
under different network configurations in an organized and simple way.

Variation objects (IntScheme, ) are stored inside the Variations folder ( ) which resides in the
Network Model folder. Variations are composed of “Expansion Stages" (IntStage), which store the
changes made to the original network(s). The application of these changes depends on the current
study time and the activation time of the Expansion Stages.

The study time is a parameter of the active Study Case, and is used to situate the current study within a
time frame. The activation time is a parameter given to the Expansion Stages, to determine whether or
not, according to the study time, the changes contained within the Expansion Stages are applied to the
network. If the activation time precedes the study time, the changes are applied to the original network.
The changes of a subsequent expansion stage add to the changes of its predecessors.

In order that changes to the network configuration are applied and can be viewed, a Variation must be
activated. These changes are contained in the expansion stage(s) of this active Variation. Once the
Variation is deactivated, the network returns to its original state. Changes contained in an Expansion
Stage can be classified as:

• Modifications to network components.

• Components added to the network.
• Components deleted from the network.

Note: If there is no active Operation Scenario, modifications to operational data will be stored in the
active Variation.

Grouping Objects

In addition to Grid folders, the Network Data folder contains a set of objects that allow further grouping
of network components. By default, when a new project is created, new empty folders to store these
grouping objects is created inside the Network Model folder.
For details of how to define grouping objects, refer to Chapter 13: Grouping Objects.

4.6.5 Operation Scenarios

Operation Scenarios may be used to store operational settings, a subset of Element data. Operational
data includes data that relates to the operational point of a device but not to the device itself e.g. the tap
position of a transformer or the active power dispatch of a generator. Operation Scenarios are stored in
the Operation Scenarios folder.

DIgSILENT PowerFactory 15, User Manual 17

CHAPTER 4. POWERFACTORY OVERVIEW

4.6.6 Study Cases

The Study Cases folder holds study management information. Study Cases are used to store informa-
tion such as command settings, active Variations and Operations Scenarios, graphics to be displayed,
and study results. See Chapter 11 (Study Cases) for details.

4.6.7 Settings

Project settings such as user-defined diagram styles for example, which differ from global settings, are
stored inside the Settings folder.

4.7 Project Structure

The structure of project data depends on the complexity of the network, use of the model, and user
preferences. The user has the flexibility to define network components directly within the Grid, or to
organize and group components in a way that simplifies management of project data.

Consider the example network data arrangement shown in Figure 4.7.1 In this case, two busbar systems
(ElmSubstat in PowerFactory ) have been defined, one at 132 kV, and one at 66 kV. The two busbar
systems are grouped within a Site, which includes the 132 kV / 66 kV transformers (not shown in
Figure 4.7.1). A Branch composed of two line sections and a node connects “132 kV Busbar" to
“HV terminal". Grouping of components in this way simplifies the arrangement of data within the
Data Manager, facilitates the drawing overview diagrams, and facilitates storing of Substation switching
configurations.

Figure 4.7.1: Example Project Structure

The following subsections provide further information regarding the PowerFactory representation of key
network topological components.

4.7.1 Nodes

In PowerFactory , nodes connecting lines, generators, loads, etc. to the network are generally called
“Terminals" (ElmTerm). Depending on their usage within the power system, Terminals can be used to
represent Busbars, Junctions, or Internal Nodes (their usage is defined by a drop down menu found in
the Basic Data page of the terminal dialogue). According to the selected usage, different calculation
functions are enabled; for example the short-circuit calculation can be performed only for busbars, or
for busbars and internal nodes, and so on.

18 DIgSILENT PowerFactory 15, User Manual

 4.7. PROJECT STRUCTURE

4.7.2 Branches

Elements with multiple connections are referred to “Branches" (as distinct from a “Branch Element",
which is a grouping of elements, discussed in Section 4.7.7). Branches include two-connection el-
ements such as transmission lines and transformers, and three-connection elements such as three-
winding transformers, AC/DC converters with two DC terminals, etc.

For information about how to define transmission lines (and cables) and sections refer to Chapter 9: Net-
work Graphics, Section 9.2(Defining Network Models with the Graphical Editor). Technical information
about transmission line and cable models is provided in Appendix C (Line (ElmLne)).

4.7.3 Cubicles

When any branch element is directly connected to a Terminal, PowerFactory uses a “Cubicle" (StaCubic)
to define the connection. Cubicles can be visualized as the panels on a switchgear board, or bays
in a high voltage yard, to which the branch elements are connected. A Cubicle is generally created
automatically when an element is connected to a node (note that Cubicles are not shown on the Single
Line Graphic).

4.7.4 Switches

To model complex busbar-substation configurations, switches (ElmCoup) can be used. Their usage
can be set to Circuit-Breaker, Disconnector, Switch Disconnector, or Load Switch. The connection of
an ElmCoup to a Terminal is carried out by means of an automatically generated Cubicle without any
additional switch (StaSwitch) object.

4.7.5 Substations

Detailed busbar configurations are represented in PowerFactory as Substations (ElmSubstat). Separate

single line diagrams of individual substations can be created. Substation objects allow the use of
running arrangements to store/set station circuit breaker statuses (see Chapter 12: Project Library,
Section 12.3: Operational Library). For information about how to define substations refer to Chapter 9:
Network Graphics, Section 9.2(Defining Network Models with the Graphical Editor) and Chapter 10,
Section 10.3(Defining Network Models with the Data Manager).

4.7.6 Sites

Network components including Substations and Branches can be grouped together within a “Site"
(ElmSite). This may include Elements such as substations / busbars at different voltage levels. For
information about how to define sites refer to Chapter 10, Section 10.3(Defining Network Models with
the Data Manager).

4.7.7 Branch Elements

Similar to Substations, Terminal Elements and Line Elements can be stored within an object called a
Branch Element (ElmBranch). Branches are “composite" two-port elements that may be connected to
a Terminal at each end. They may contain multiple Terminals, Line sections (possible including various
line types), and Loads etc, but be represented as a single Branch on the Single Line Graphic. As for
Substations, separate diagrams for the detailed branch can be created with the graphical editor.

DIgSILENT PowerFactory 15, User Manual 19

CHAPTER 4. POWERFACTORY OVERVIEW

For information about how to define branches refer to Chapter 9: Network Graphics, Section 9.2(Defin-
ing Network Models with the Graphical Editor) and Chapter 10, Section 10.3(Defining Network Models
with the Data Manager).

4.8 User Interface

An overview of the PowerFactory user interface is provided in this section, including general discussion
of the functionality available to enter and manipulate data and graphics. Aspects of the user interface
are discussed in further detail in the following chapters, in particular:

• Chapter 6 (User Accounts, User Groups, and Profiles).

• Chapter 9(Network Graphics (Single Line Diagrams)).
• Chapter 10 (Data Manager).

4.8.1 Overview

The main PowerFactory window is shown in Figure 4.8.1

Figure 4.8.1: PowerFactory user interface

Key features of the main window are as follows:

1. The main window includes a description of the PowerFactory version, and standard icons to
Minimize, Maximize/Restore, Resize, and Close the window.

20 DIgSILENT PowerFactory 15, User Manual

 4.8. USER INTERFACE

2. The main menu bar includes drop-down menu selections. The main menu is discussed further in
section 4.8.2 (Menu Bar).
3. The Main Toolbar includes commands and other icons. The Main Toolbar is discussed in further
detail in section 4.8.3 (Main Toolbar).
4. The Graphical Editor displays single line diagrams, block diagrams and/or simulation plots of the
active project. Studied networks and simulation models can be directly modified from the graphical
editor by placing and connecting elements.

5. When an object is right clicked (in the graphical editor or in the data manager) a context sensitive
menu with several possible actions appears.
6. When an object is double clicked its edit dialogue will be displayed. The edit dialogue is the
interface between an object and the user. The parameters defining the object are accessed
through this edit dialogue. Normally an edit dialogue is composed of several “pages". Each
page groups parameters that are relevant to a certain function. In Figure 4.8.1 the Load Flow
page of a generator is shown, where only generator parameters relevant to load flow calculations
are shown.
7. The “Data Manager" is the direct interface with the database. It is similar in appearance and
functionality to a Windows Explorer window. The left pane displays a symbolic tree representation
of the complete database. The right pane is a data browser that shows the content of the currently
selected folder. The data manager can be accessed by pressing the Data Manager icon ( )
on the left of the main toolbar. It is always ’floating’, and more than one can be active at a
time. Depending on how the user navigates to the Database Manager, it may only show the
database tree for selecting a database folder, or it may show the full database tree. The primary
functionality of the Data Manager is to provide access to power system components/objects. The
data manager can be used to edit a group of selected objects within the data manager in tabular
format. Alternatively, objects may be individually edited by double clicking on an object (or right-
click → Edit).
8. The output window is shown at the bottom of the PowerFactory window. The output window cannot
be closed, but can be minimized. The output window is discussed in further detail in section 4.8.4
(The Output Window).

9. The “Project Overview" window is displayed by default on the left side of the main application
window between the main toolbar and the output window. It displays an overview of the project
allowing the user to assess the state of the project at a glance and facilitating easy interaction with
the project data.

4.8.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 Alt key together with the underlined letter in the
menu. Menu options that are shown in grey are not available, and only become available as the user
activates projects or calculation modes, as required.

DIgSILENT PowerFactory 15, User Manual 21

CHAPTER 4. POWERFACTORY OVERVIEW

Figure 4.8.2: The help menu on the Menu bar

For example as show in Figure 4.8.2:

• To access PowerFactory tutorials: Press Alt-H to open the help menu. Use the keyboard to select
Start Tutorial. Press Execute to open the Tutorial. Note that the on-line Getting Started Tutorial is
identical to the printed version.
• To access the User Manual: Left click the Help menu. Left-click the option User Manual to open
the electronic User Manual.

4.8.3 Main Toolbar

The main PowerFactory toolbar provides the user with quick access to the main commands available
in the program (see Figure 4.8.1). Buttons that appear in grey are only active when appropriate. All
command icons are equipped with balloon help text which are displayed when the cursor is held still
over the icon for a moment, and no key is pressed.

To use a command icon, click on it with the left mouse button. Those icons that perform a task will
automatically return to a non-depressed state when that task is finished. Some command icons will
remain depressed, such as the button to Maximise Output Window. When pressed again, the button
will return to the original (non-depressed) state.

This section provides a brief explanation of the purpose of the icons found on the upper part of the
toolbar. Icons from the lower part of the toolbar are discussed in Chapter 9(Network Graphics (Single
Line Diagrams)). Detailed explanations for each of the functions that the icons command are provided
in the other sections of the manual.

Open Data Manager

Opens a new instance of the Database Manager. When the option “Use Multiple Data Manager"
is enabled in the user settings menu (User Settings → General) the user will be able to open
as many instances of the data manager as required. If “Use Multiple Data Manager" is disabled
in the user settings menu, the first instance of the data manager will be re-opened. For more
information on the Data Manager refer to Chapter 10.

Edit Relevant Objects for Calculation

Provides a list of elements (coloured in green) and types (coloured in red) that are in an active
Grid: e.g. transformer types, line elements, composite models, etc. When an object icon is
selected, all objects from the selected class(es) will be shown in a browser.

22 DIgSILENT PowerFactory 15, User Manual

 4.8. USER INTERFACE

Date/Time of Calculation Case (SetTime)

Displays the date and time for the case calculation. This option is used when parameter charac-
teristics of specific elements (e.g. active and reactive power of loads) are set to change according
to the study time, or a Variation status is set to change with the study time.

Edit Trigger

Displays a list of all Triggers that are in 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 16: Parameter Characteristics, Load States, and Tariffs. Section 16.2
(Parameter Characteristics).

Data Verification (ComCheck)

Performs model data verification, see Section 21.5 (Troubleshooting Load Flow Calculation Prob-
lems).

Calculate Load-Flow (ComLdf)

Activates the load-flow command dialogue. For more information about the specific settings, refer
to Chapter 21 (Load Flow Analysis).

Calculate Short-Circuit (ComShc)

Activates the short-circuit calculation command dialogue. For more information, refer to Chap-
ter 22 (Short-Circuit Analysis).

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. See section 4.9 for a general description of DPL
scripts, and Chapter 19 (The DIgSILENT Programming Language - DPL) for detailed information.

Output Calculation Analysis (ComSh)

Presents calculation results in various formats. The output is printed to the Output Window
and can be viewed, or copied for use in external reports. Several different reports, depending
on the calculation, can be created. For more information about the output of results refer to
Chapter 17:Reporting and Visualizing Results, Section 17.2.3 (Output of Results).

Documentation of Device Data (ComDocu)

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, and for checking data
that has been entered. Depending on the element chosen for the report, the user has two
options; generate a short listing, or a detailed report. For more information please refer to
Chapter 17:Reporting and Visualizing Results, Section 17.2.3 (Output of Results).

Comparing of Results On/Off

Turns on/off comparing of calculation results. Used to compare results where certain settings

DIgSILENT PowerFactory 15, User Manual 23

CHAPTER 4. POWERFACTORY OVERVIEW

or designs options of a power system have been changed from one calculation to the next. For
more information please refer to Chapter 17:Reporting and Visualizing Results, Section 17.3
(Comparisons Between Calculations).

Edit Comparing of Results (CommDiff)

Enables the user to select the cases/ calculation results that are to be compared to one another,
or to set the colouring mode for the difference reporting. For more information please refer to
Chapter 17:Reporting and Visualizing Results, Section 17.3 (Comparisons Between Calcula-
tions).

Update Database

Utilizes the current calculations results (i.e. the calculation ’output’ data) to change input param-
eters (i.e. data 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 Chang-
ers." For more information refer to Chapter 17:Reporting and Visualizing Results, Section 17.3
(Comparisons Between Calculations).

Save Operation Scenario

Saves the current operational data to an Operation Scenario (e.g. load values, switch statuses,
etc.). See Chapter 14 (Operation Scenarios).

Break

Stops a transient simulation or DPL script that is running.

Reset Calculation

Resets any calculation performed previously. This icon is only enabled after a calculation has
been carried out.

Note: In User Settings, on the General page, if ’Retention of results after network change’ is set to
’Show last results’ in the User Settings (see Chapter 7: User Settings, section 7.1), results will
appear in grey on the Single Line Diagram and on the Flexible Data tab until the calculation is
reset, or a new calculation performed.

User Settings (SetUser)

User options for many global features of PowerFactory may be set from the dialogue accessed
by this icon. For more information refer to Chapter 7 (User Settings).

Maximize Graphic Window

Maximizes the graphic window. Pressing this icon again will return the graphic window to its
original state.

Maximize Output Window

Maximizes the output window. Pressing this icon again will return the output window to its original
state.

Change Toolbox

In order to minimize the number of icons displayed on the taskbar, some icons are grouped based
on the type of analysis, and are only displayed when the relevant category is selected from the
Change Toolbox icon. In Figure 4.8.3, the user has selected RMS/EMT Simulation, and therefore
only icons relevant for RMS and EMT studies are displayed to the right of the Change Toolbox
icon. If, for example, Reliability Assessment were selected then icons to the right of the Change

24 DIgSILENT PowerFactory 15, User Manual

 4.8. USER INTERFACE

Toolbox icon would change to those suitable for a reliability assessment.

Figure 4.8.3: Change Toolbox selection

4.8.4 The Output Window

In addition to results presented in the Single Line Graphics and / or Data Manager, the Output Window
displays other textual output, such as error messages, warnings, command messages, device docu-
mentation, result of calculations, and generated reports, etc. This section describes Output Window
use and functionality.

Sizing and Positioning the Output Window

The default location of the Output Window is “docked" (fixed) at the bottom of the main window, as
shown in Figure 4.8.1 It can be minimized, but not closed. When right-clicking the mouse button with the
cursor in the output windows area, the context sensitive menu of the output window appears. The output
window can then be undocked by deselecting the Dock Output Window. The undocked output window
is still confined to the main window, but now as a free floating window. This can occur unintentionally
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 and unticked “Docking View" then right click and select “Docking View"
once more).

The upper edge of the output window shows a splitter bar which is used to change the size of the output
window. The “drag" cursor 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 (grey bar at the upper edge of the output window) when the output window
is in “docking mode".
• Double-clicking the frame of the output window to dock/undock it from the main window.
• Pressing the Maximize Graphic Window icon ( ) on the main toolbar to enlarge the graphics
board by hiding the output window.

DIgSILENT PowerFactory 15, User Manual 25

CHAPTER 4. POWERFACTORY OVERVIEW

• Pressing the Maximize Output Window icon ( ) icons on the main toolbar to enlarge the output
window.

Output Window Options The contents of the output window may be stored, edited, redirected, etc.,
using the icons shown on the right-hand pane of the output window. Some commands are also available
from the context sensitive menu by right-clicking the mouse in the output window pane.

Opens an editor. The user can copy and paste text from the output window to the editor, and
manually type data in the editor.
Opens a previously saved output file.

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. Text may then be pasted in other programs.

Clears the output window by deleting all messages. Note that when the user scrolls through previous
messages in the output window, the output window will no longer automatically scroll with new
output messages. The Clear All icon will “reset" scrolling of the output window.
Searches the text in the output window for the occurrences of a given text.

Changes the font used in the output window.

Redirects the output window to a file. The output window will not display messages while this icon
is depressed.
Redirects the output window to be printed directly.

Redirects the output window to be printed directly.

Using the Output Window

The Output Window facilitates preparation of data for calculations, and identification of network data
errors. Objects listed in the output window (with a folder name and object name) can be double-clicked
with the left mouse button to open an edit dialogue for the object. Alternatively, the object can be
right-clicked and then Edit, Edit and Browse Object, or Mark in Graphic selected. For example, if
a Synchronous Machine Element does not have a Type defined, the load-flow will not solve and a
message will be reported. (see Figure 4.8.4). This simplifies the task of locating objects in the Single
Line Graphic.

Figure 4.8.4: Output Window Context Sensitive Menu

Output Window Context Sensitive Menu

As mentioned in the previous section, to show the Output Windows context sensitive menu, right-click
the mouse button whilst pointing at the object name. The available option are as follows:

26 DIgSILENT PowerFactory 15, User Manual

 4.8. USER INTERFACE

• Edit Object: Opens the edit dialogue of the selected object.

• Edit and Browse Object: Opens a Data Manager and displays the Element and its parameters.

• Mark in Graphic: Marks the selected element in the Single Line Graphic and zooms into the region
it is placed.

Output Window Legend

The Output Window uses colours and other formatting to distinguish between different types of mes-
sages, and for bar graph results. Used text message formats are as follows:

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.

Output Window Graphical Results

Reports of calculation results may contain bar graphical 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.

Part of a bar graph output is shown in Figure 4.8.5 The following formatting is visible:

Figure 4.8.5: Output window bar diagram

• Green Solid Bar: Used when the value is in the tolerated range.

• Blue Solid Bar: Used when the value is below a limit.

• Red Solid Bar: Used when the value is above a limit.
• Hatch-crossed Bar: Used when the value is outside the range.

DIgSILENT PowerFactory 15, User Manual 27

CHAPTER 4. POWERFACTORY OVERVIEW

Copying from the Output Window

The contents of the Output Window, or parts of its contents, may be copied to the built-in editor of
PowerFactory , or to other programs. 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", which other programs may not support.

The lines that are to be copied is determined by the Output Window settings. When text from the output
window is copied, an info message will be displayed, informing the user about the current settings (see
Figure 4.8.6). From this dialogue, the Output Window User Settings may be modified, and the Info
message may be disabled.

Figure 4.8.6: The output window Info Message

4.9 DIgSILENT Programming Language (DPL) Scripts

The DIgSILENT Programming Language DPL offers an interface to the user for the automation of tasks
in PowerFactory . By means of a simple programming language and in-built editor, the user can define
automation commands (scripts) to perform iterative or repetitive calculations on target networks, and
post-process the results.

To find the name of an object parameter to be used in a DPL script, simply hover the mouse pointer
over the relevant field in an object dialogue. For example, for a General Load, on the Load Flow page,
hover the mouse pointer over the Active Power field to show the parameter name “plini".

User-defined DPL scripts can be used in all areas of power system analysis, for example:

• Network optimization.
• Cable-sizing.
• Protection coordination.
• Stability analysis.
• Parametric sweep analysis.
• Contingency analysis.

DPL scripts may include the following:

28 DIgSILENT PowerFactory 15, User Manual

 4.9. DIGSILENT PROGRAMMING LANGUAGE (DPL) SCRIPTS

• Program flow commands such as ’if-else’ and ’do-while’.

• PowerFactory commands (i.e. load-flow or short-circuit commands: ComLdf, ComShc).

• Input and output routines.

• Mathematical expressions.
• PowerFactory object procedure calls.
• Subroutine calls.

DPL command objects provide an interface for the configuration, preparation, and use of DPL scripts.
These objects may take input parameters, variables and/or objects, pass these to functions or subrou-
tines, and then output results. DPL commands are stored inside the Scripts folder ( ) in the project
directory.

Consider the following simple example shown in Figure 4.9.1 to illustrate the DPL interface, and the
versatility of DPL scripts to take a user-selection from the Single Line Graphic. The example DPL script
takes a load selection from the Single Line Graphic, and implements a while loop to output the Load
name(s) to the Output Window. Note that there is also a check to see if any loads have been selected
by the user.

Figure 4.9.1: Example DPL Script

For further information about DPL commands and how to write and execute DPL scripts refer to Chap-
ter 19 (The DIgSILENT Programming Language - DPL), and Appendix D DPL Reference.

DIgSILENT PowerFactory 15, User Manual 29