UserManual en Parte1
UserManual en Parte1
DIG
PowerFactory
I N T E G R AT E D P O W E R S Y S T E M A N A LY S I S S O F T W A R E
DIgSILENT
PowerFactory 15
User Manual
DIgSILENT PowerFactory
Version 15
User Manual
Online Edition
DIgSILENT GmbH
Gomaringen, Germany
October 2015
Publisher:
DIgSILENT GmbH
Heinrich-Hertz-Straße 9
72810 Gomaringen / Germany
Tel.: +49 (0) 7072-9168-0
Fax: +49 (0) 7072-9168-88
October 2015
r2216
Contents
I General Information 1
2 Contact 5
4 PowerFactory Overview 9
4.6.4 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.6.8 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.7.1 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.7.2 Branches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.7.3 Cubicles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7.5 Substations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7.6 Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
II Administration 33
5 Program Administration 35
5.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.2.2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.2.3 Licence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.2.4 Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.2.7 Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.5 Housekeeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.5.6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7 User Settings 59
7.6 Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.7 Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.8 StationWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
III Handling 65
9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
10.6 The Flexible Data Page Tab in the Data Manager . . . . . . . . . . . . . . . . . . . . . . 151
11.13Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
13.2.3 Inserting a Generator into a Virtual Power Plant and Defining its Virtual Power
Plant Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
13.10Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
13.11Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
14.4.1 How to view objects missing from the Operation Scenario data . . . . . . . . . . 219
14.4.4 How to transfer data from one Operation Scenario to another . . . . . . . . . . . 220
14.4.5 How to update the default data with operation scenario data . . . . . . . . . . . . 221
14.4.6 How exclude a grid from the Operation Scenario data . . . . . . . . . . . . . . . 221
14.5.1 How to change the automatic save settings for Operation Scenarios . . . . . . . 223
16 Parameter Characteristics,
Load States, and Tariffs 239
18.2.4 How to Check if a Version is the Base for a Derived Project . . . . . . . . . . . . 326
18.4.2 How to Merge or Compare Two Projects Using the Compare and Merge Tool . . 330
18.4.3 How to Merge or Compare Three Projects Using the Compare and Merge Tool . 332
18.5.3 Tips for Working with the Compare and Merge Tool . . . . . . . . . . . . . . . . . 340
19 Scripting 343
20 Interfaces 369
22.4.2 Verification (Except for IEC 61363, IEC 61660 and ANSI/IEEE 946) . . . . . . . . 492
24 Flickermeter 543
25.3.1 Defining the variables for monitoring in the Quasi dynamic simulation . . . . . . . 555
27.3.2 Viewing Modal Analysis Results using the built-in Plots . . . . . . . . . . . . . . . 665
27.3.3 Viewing Modal Analysis Results using the Modal Data Browser . . . . . . . . . . 671
32.6.4 Summary of variables calculated during the Generation Adequacy Analysis . . . 790
40 Protection 913
40.4.5 Adding a user defined permanent current line to the time-overcurrent plot . . . . 946
40.4.8 Altering protection device characteristic settings from the time-overcurrent plot . 948
40.5.2 Primary or secondary Ohm selection for distance relay parameters . . . . . . . . 965
40.6.4 Modifying the relay settings and branch elements from the R-X plot . . . . . . . . 981
40.10.3 Prerequisites for using the distance protection coordination tool . . . . . . . . . . 996
40.10.6 How to output results from the protection coordination assistant . . . . . . . . . . 998
V Appendix 1059
A Glossary 1061
Bibliography 1447
Index 1449
General Information
Chapter 1
This User Manual is intended to be a reference for users of the DIgSILENT PowerFactory software. This
chapter provides general information about the contents and the used conventions of this documenta-
tion.
The first section of the User Manual provides General Information, including an overview of PowerFac-
tory software, a description of the basic program settings, and a description of the PowerFactory data
model.
The next sections describe PowerFactory administration, handling, and power system analysis func-
tions. In the Power System Analysis Functions section, each chapter deals with a different calculation,
presenting the most relevant theoretical aspects, the PowerFactory approach, and the corresponding
interface.
The online version of this manual includes additional sections dedicated to the mathematical description
of models and their parameters, referred to as Technical References. To facilitate their portability,
visualisation, and printing, the papers are attached to the online help as PDF documents. They are
opened by clicking on the indicated links within the manual. References for DIgSILENT Programming
Language functions are also included as appendices of the online manual.
It is recommended that new users commence by reading Chapter 4 (PowerFactory Overview), and
completing the PowerFactory Tutorials.
Buttons and Keys Dialogue buttons and keyboard keys are referred to with bold and underline text
formatting. For example, press the OK button in the PowerFactory dialogue, or press CTRL+B on
the keyboard.
Menus and Icons Menus and icons are usually referenced using Italics. For example, press the User
Settings icon , or select Tools → User Settings. . .
Other Items "Speech marks" are used to indicate data to be entered by the user, and also to refer to
an item defined by the author. For example, consider a parameter "x".
Contact
For further information about the company DIgSILENT , our products and services please visit our web
site, or contact us at:
DIgSILENT GmbH
Heinrich-Hertz-Str. 9
www.digsilent.de
DIgSILENT experts offer direct assistance to PowerFactory users with valid maintenance agreements
via telephone or online via support queries raised on the customer portal.
To register for the on-line portal, select Help → Register. . . or go to directly to the registration page (link
below). Log-in details will be provided by email shortly thereafter.
To log-in to the portal, enter the email (or Login) and Password provided. When raising a new support
query, please include the PowerFactory version and build number in your submission, which can be
found by selecting Help → About PowerFactory. . . from the main menu. Note that including relevant
*.dz or *.pfd file(s) may assist with our investigation into your query. The customer portal is shown in
Figure 2.1.1.
For general information about DIgSILENT or your PowerFactory license, please contact us via:
Phone: +49-(0)7072-9168-0
Fax: +49-(0)7072-9168-88
E-mail: [email protected]
DIgSILENT PowerFactory is provided with a complete help package to support users at all levels of
expertise. Documents with the basic information of the program and its functionality are combined with
references to advanced simulation features, mathematical descriptions of the models and of course
application examples.
• Installation Manual: PowerFactory installation guide, describes the procedures followed to install
and set the program. It is available in the PowerFactory installation CD and from the DIgSILENT
download area:http://www.digsilent.de/index.php/downloads.html
Also in this manual is described how to configure PowerFactory for local caching of projects when
an external server connection is unavailable (Offline Mode). The Offline mode guide is available
in section 5.4: Offline Mode User Guide.
• Tutorial: Basic Information for new users and hands-on tutorial. Access via Help menu of
PowerFactory, and for registered users in the DIgSILENT download area:
http://www.digsilent.de/index.php/downloads.html
• User Manual: This document. Access via Help menu of PowerFactory. Current and previous
manuals (PDF files) can also be found on the in the DIgSILENT download area.
• Technical References: Description of the models implemented in PowerFactory for the different
power systems components. The technical reference documents are attached to the online help
(Appendix C: Technical References of Models).
• Context Sensitive Help: Pressing the key F1 while working with PowerFactory will lead you
directly to the related topic inside the User Manual.
• PowerFactory Examples: The window PowerFactory Examples provides a list of application ex-
amples of PowerFactory calculation functions. Every example comes with an explaining document
which can be opened by pressing the corresponding document button. Additional videos are
available for demonstrating the software handling and its functionalities.
The PowerFactory Examples window will “pop up” automatically every time the software is open,
this could be deactivated by unchecking the Show at Startup checkbox. PowerFactory Examples
are also accessible on the main menu, by selecting File → Examples. . . .
• Release Notes: For all new versions and updates of the program Release Notes are provided,
which document the implemented changes. They are available from the DIgSILENT download
area.
• FAQs: Users with a valid maintenance agreement can access the FAQ section, on the DIgSILENT
download area: http://www.digsilent.de/index.php/downloads.html. In this section you will find
interesting questions and answers regarding specific applications of PowerFactory.
• Website: www.digsilent.de
PowerFactory Overview
The calculation program DIgSILENT PowerFactory , is a computer-aided engineering tool for the anal-
ysis 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 optimisation.
“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 computer programming. The accuracy and
validity of results obtained with PowerFactory has been confirmed in a large number of implementations,
by organisations involved in the 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 organisation of cases; core numerical
routines; output and documentation functions.
2. Integrated interactive single line graphic and data case handling.
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 analysis, short-circuit calculation, harmonic analysis, protection coordination, stability analysis,
and modal analysis.
Although PowerFactory includes highly-sophisticated power system analysis functions, the intuitive user
interface makes it possible for new users to very quickly perform common tasks such as load flow and
short-circuit calculations.
The functionality purchased by a user is configured in a matrix-like format, where the licensed calcu-
lation functions, together with the maximum number of buses, are listed as coordinates. The user can
then, as required, configure the interface and functions according to their requirements.
Depending on user requirements, a specific PowerFactory license may or may not include all of the
functions 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.
Functional Integration
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 analyse 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
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
organisations. 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
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 synchronised
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.
Customisation
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 customise user profiles,
in particular:
Chapter 6: User Accounts, User Groups, and Profiles (Section 6.5 Creating Profiles) details the
customisation 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’.
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 optimise 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 dialogs are the interfaces between the user and an object; the parameters defining the object are
accessed through this dialog. This means that there is an edit dialog 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.
• 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).
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 dialog 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
All data entered for objects is hierarchically structured in folders for ease of navigation. To view the data
and its organisation, 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.
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).
Since power systems are constructed using standardised 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 ( ).
• 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).
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 summarised below:
• 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)
Sometimes it is useful to share a Library with another PowerFactory user in a Global Library. This re-
quires the creation of a Library folder, which can be done by the Administrator as shown in Figure 4.6.2.
To do this, the Administrator must proceed as follows:
The new Library is now created at the same level of the hierarchy as the Global Library. Every user of
this database has full read access, however the Types within this Library must be created and edited by
the Administrator.
Note: The user-defined Library should not be named “Library”, as this name is reserved for the standard
Global Library. Furthermore, the data within the standard Global Library should not be changed
by the User, as this folder will be overwritten when installing a new PowerFactory version. This
also applies to the Library folder within the standard Global 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.4 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.
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,
organisational 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 analysed separately. At a
later stage both networks are connected and the analysis of the complete system is carried out.
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 analyse 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 organised 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:
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.
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.
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.8 Settings
Project settings such as user-defined diagram styles for example, which differ from global settings, are
stored inside the Settings folder.
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
organise 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.
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 dialog). 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.
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 visualised 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
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).
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.
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).
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
4.8.1 Overview
1. The main window includes a description of the PowerFactory version, and standard icons to
Minimise, Maximise/Restore, Resize, and Close the window.
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 dialog will be displayed. The edit dialog is the interface
between an object and the user. The parameters defining the object are accessed through this edit
dialog. Normally an edit dialog 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 minimised. 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.
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.
• 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.
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.
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.
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.
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).
Activates the Network Data Assessment command dialog to generate selected reports on net-
work data or to perform model data verification. For more information see Section 22.6 (Capaci-
tive Earth-Fault Current) or Section 21.5 (Troubleshooting Load Flow Calculation Problems).
Activates the Load Flow Calculation command dialog. For more information about the specific
settings, refer to Chapter 21 (Load Flow Analysis).
Activates the short-circuit calculation command dialog. For more information, refer to Chapter 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 Scripts
Displays a list of scripts that are available. See section 4.9 for a general description of DPL
scripts, and Chapter 19(Scripting) for detailed information.
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 Visualising Results, Section 17.2.3 (Output of Results).
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 Visualising Results, Section 17.2.3 (Output of Results).
Turns on/off comparing of calculation results. Used to compare results 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 17:Reporting and Visualising Results, Section 17.3
(Comparisons Between Calculations).
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 Visualising Results, Section 17.3 (Comparisons Between Calcula-
tions).
Update Database
Utilises 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 Visualising Results, Section 17.3
(Comparisons Between Calculations).
Saves the current operational data to an Operation Scenario (e.g. load values, switch statuses,
etc.). See Chapter 14 (Operation Scenarios).
Break
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 options for many global features of PowerFactory may be set from the dialog accessed by
this icon. For more information refer to Chapter 7 (User Settings).
Maximises the graphic window. Pressing this icon again will return the graphic window to its
original state.
Maximises the output window. Pressing this icon again will return the output window to its original
state.
Change Toolbox
In order to minimise 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
Toolbox icon would change to those suitable for a reliability assessment.
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.
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 minimised, 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.
• 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 Maximise Graphic Window icon ( ) on the main toolbar to enlarge the graphics
board by hiding the output window.
• Pressing the Maximise 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.
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.
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.
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 dialog 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.
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:
• 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.
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:
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 dialog 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:
• Green Solid Bar: Used when the value is in the tolerated range.
• Blue Solid Bar: Used when the value is below a limit.
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 dialog, the Output Window User Settings may be modified, and the Info
message may be disabled.
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 dialog. 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 optimisation.
• Cable-sizing.
• Protection coordination.
• Stability analysis.
• Parametric sweep analysis.
• Contingency analysis.
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.
For further information about DPL commands and how to write and execute DPL scripts refer to Chap-
ter 19 (Scripting), and Appendix E DPL Reference.
Administration
Chapter 5
Program Administration
This chapter provides information on how to configure PowerFactory , and how to log on. More de-
tailed descriptions of the installation, database settings and additional information can be found in the
PowerFactory Installation Manual.
In general there are 3 primary questions to consider before installing PowerFactory software, which will
determine the installation settings:
Once PowerFactory has been installed, it can be started by clicking either on the Desktop or by selecting
PowerFactory in the Windows Start menu. PowerFactory will then start and create a user account upon
the initial user log-in. If the user is working in a single-user-database environment, PowerFactory will
take the username from Windows by default. In the case that several user accounts have been created,
a log-on dialog will pop up allowing the user to select their username. The user will be asked to enter a
password if one has been defined for that particular account.
In a multi-user-database installation (see Chapter 6: User Accounts, User Groups, and Profiles) new
accounts and passwords are created by the administrator. The ’Administrator’ account is created when
installing PowerFactory and is used to create and manage users’ accounts in a multi-user environment
(see Chapter 6: User Accounts, User Groups, and Profiles). To log on as Administrator, the shortcut
from the Windows Start Menu can be used. By default the administrator account password is Adminis-
trator. When already running a PowerFactory session, the user can select Tools → Switch User in the
main menu to log-on as Administrator.
For further information about the roll of the database administrator please refer to Section 6.2: The
Database Administrator.
Changes to the default installation settings can be made using the PowerFactory Configuration dialog.
Once PowerFactory is started, the Configuration dialog can be accessed via Tools → Configuration in
PowerFactory ’s main menu. The Database and Licence tabs of the Configuration dialog provide options
to determine how the program installation should be configured. Administrator rights are necessary to
perform changes to these settings.
A detailed description of the installation procedure and the program configuration alternatives is pro-
vided in the PowerFactory Installation Manual.
The Configuration (SetConfig) dialog is used to apply changes to the configuration settings. Windows
Administration rights are required.
5.2.1 General
On this page the user can select the application language for the session.
5.2.2 Database
This page allows the selection of how the database will be used. The options are:
DIgSILENT PowerFactory provides drivers for the following multi-user database systems:
• Oracle
• Microsoft SQL Server
For further information regarding the database configuration please refer to the PowerFactory Installa-
tion Manual.
5.2.3 Licence
In order to run PowerFactory , the user is required to define licence settings on the Licence page of the
Configuration dialog. The options are described below, and more information regarding licence types is
available in the PowerFactory Installation Manual.
Demo request
When starting PowerFactory for the first time using this option, the DIgSILENT Licence Activation dialog
is opened containing instructions on how to activate the installation.
PowerFactory Workstation
This option is for single-user clients with a licence key (also known as a ’dongle’ or ’hardlock’).
PowerFactory Server
This option is for multi-user clients with a network licence key which allows multiple users access over
a network.
The network licence key requires an additional program which is also part of the installation package:
Licence Server.
When using PowerFactory Server, the computer name or the IP network address of the licence server
is required.
Advanced RPC-Settings
If a network licence key with protocol-based communication is used, advanced RPC settings must be
provided. These input fields are available on the Advanced tab of the Licence page.
The RPC settings must be those specified on the licence server. For detailed information, the network
administrator should be consulted. Additional information is available in the PowerFactory Installation
Manual.
5.2.4 Workspace
The Workspace page allows the user to set the workspace directory and the workspace backup direc-
tory. The workspace is used to store the local database, result files and log files. For further information
regarding options for configuring and using the workspace, please refer to Chapter 5.3.
The External Applications page is used to set the Python editor path. This setting is used by Python.
On the Map Server page, the default settings for background maps can be changed. The following
parameters can be set:
• Directory: Map cache directory where downloaded map tiles are stored (default: workspace
directory). A custom directory can be specified if the cache should be shared across different
PowerFactory installations.
• Preferred tile size [pixels]: Pixel dimensions of map tiles.
• Max server connections: Maximum number of map tiles that are downloaded simultaneously.
• Download time-out: Timespan after which a non-finished tile download is cancelled. This value
may need to be increased for slow/unstable internet connections.
• HTTP proxy: Needs to be specified in the case the user’s computer connects to the internet via a
proxy server. Format: host:port , e.g.: “myproxy:1234”
If Google Maps©should be used as the map provider, the “Google Maps for Business account” data
must be set on this page as well. To acquire a licence, please contact Google sales: (http://www.
google.com/enterprise/mapsearth).
5.2.7 Advanced
Settings on the Advanced page should only be changed under the guidance of the DIgSILENT Power-
Factory support (see Chapter 2 Contact).
By selecting Tools → Workspace from the main menu, the options described below are available.
The workspace directory can be seen by clicking Tools → Workspace→ Show workspace directory.
To import the workspace, select Tools → Workspace→ Import Workspace.... This is a convenient
way to import the entire workspace after a new installation. To export the workspace, select Tools →
Workspace→ Export Workspace.... The package will be saved as a .zip file.
The selection Tools → Workspace→ Show Default Export Directory from the main menu shows the
user the directory that is used for the export.
This option allows the migration of the database from an older PowerFactory version (e.g 14.X, 15.0. . . )
to the newest version.
This can be selected from the main menu, under Tools → Workspace→ Import Workspace from 14.x
or 15.0. . . . After “Import Workspace from 14.x or 15.0. . . ” has been selected, the user can choose the
working directory. The database that is saved in selected working directory will be migrated.
Depending on the database size, a migration may take several hours. Figure 5.3.1 shows the two
different migration types available.
Migration Types
Complete: the database structure and all projects will be altered and migrated immediately upon
pressing the OK button.
Minimal: the database structure will be altered immediately, but the project migration will occur upon
activation.
This section describes working in offline mode. Installation of the offline Mode is described in the
PowerFactory Installation Manual.
Preconditions:
• A PowerFactory user account must already exist in the online database. The PowerFactory “Ad-
ministrator” user is able to create user accounts.
• The user must not be logged-on to an online session. In the example in Figure 5.4.1, User 2 and
User 3 are able to start an offline session, but User 1 is not, as s/he is already logged-on to an
online session.
Note: the Administrator user is only allowed to work in online mode (not in offline mode).
• Start PowerFactory . In the Log-on dialog enter the user name and password.
• On the Database page, enter the Offline Proxy Server settings (see figure 5.4.2)
• Press OK
• An info message is shown. (fig. 5.4.3)
• Press OK
• From the main menu, select File → Offline→ Terminate Offline session
Synchronises global data (new users, projects added, projects removed, projects moved) and all sub-
scribed projects.
The project will then be retrieved from the Offline Proxy Server and stored in the local Offline DB cache.
A new project is created in offline mode. It is available only in this offline session. Later this project
should be published to other users and synchronised to the online database.
Synchronises a subscribed project. If the project is subscribed for reading only, the local project will be
updated from the online database. If the project is subscribed for reading and writing, the changes from
the local offline database will be transferred to the online database.
The session status for each user is shown in the Data Manager.
In Figure 5.4.4:
• User 1 and Administrator are logged on to an online session. They are indicated by the
green ONLINE icon.
• User 2 has started an offline session. It is indicated by the red OFFLINE icon.
• Public, Demo, and User 3 are not logged on.
There may occasionally be cases which require that an offline session be terminated by the Adminis-
trator; e.g. if the computer on which the offline session was initialised has been damaged and can no
longer be used, and the user wants to start a new offline session on a different computer.
5.5 Housekeeping
5.5.1 Introduction
Housekeeping automates the administration of certain aspects of the database; in particular purging
projects, emptying user recycle bins and the deletion of old projects. Housekeeping is triggered by the
execution of a Windows Scheduled Task; this can be set up to run at night, thus improving performance
during the day by moving regular data processing to off-peak times. An additional benefit to housekeep-
ing is that users will need to spend less time purging projects and emptying recycle bins, something that
can slow down the process of exiting PowerFactory .
Housekeeping is only available for multi-user databases (e.g. Oracle, SQL Server). For details on
scheduling housekeeping, see the PowerFactory Installation Manual.
Normally, housekeeping will not process data belonging to logged-on users; however, some user
accounts (e.g. those for a control room) may be connected to PowerFactory permanently. These users
can be configured to allow housekeeping to process their data while they are logged-on. This is done
from the User Settings dialog (see Figure 5.5.1). Regardless of this setting, housekeeping will not
operate on a user’s active project.
Figure 5.5.1: The User Settings dialog: housekeeping for connected users
The Housekeeping command (SetHousekeeping) is used to control which housekeeping tasks are
enabled (see figure 5.5.2). It is recommended that the user move this object from Database \Sys-
tem\Configuration\Housekeeping to Database∖Configuration∖Housekeeping, in order to preserve the
user’s configuration throughout database upgrades.
The following sections discuss the different housekeeping tasks available in the Housekeeping dialog.
• Immediate archiving by the user: by selecting “Archive” from the context menu, the project will
be immediately archived and placed in the vault directory.
• Deferred archiving by Housekeeping job: by selecting “Archive” from the context menu, the
project will be immediately archived, but not placed in the vault directory. This will happen
automatically depending on the Housekeeping settings.
Important: The vault directory can be defined under “Tools\Configuration\Database \Vault Directory”
A project cannot be archived unless it is deactivated. By right-clicking on the project a context menu
will appear. By selecting “Archive”, the project will be moved to the Archived Projects folder of the user
(IntUser ). If specified in the Housekeeping archiving options, the project will be immediately placed in
the vault directory.
Conversely, archived projects may also be restored. To restore an archived project, the user must select
“Restore” from the context menu which appears after right-clicking on a deactivated project.
If the option Remove projects based on last activation date has been selected in the Housekeeping
dialog, when the Housekeeping is executed, for each user, each project will be handled according to
the selected Action.
The project properties determine whether a project can be automatically deleted or archived, as shown
in Figure 5.5.3. The default setting for “Housekeeping project deletion” is disabled. When enabled, the
default retention period is 60 days. These defaults can be changed for new projects by using a template
project (under Configuration/Default in the Data Manager tree).
The settings for multiple projects may be selected using the tabular pane of the Data Manager window
(select the relevant column, right-click and select Modify Values). A value of ’1’ is equivalent to the
Housekeeping option Delete project being selected (see Figure 5.5.4). Many projects can be changed
via the tabular window which appears following a Find operation, though it should be noted that execut-
ing a Find is potentially a lengthy operation.
A project will be deleted/archived by the housekeeping task if it meets the following criteria:
1. The project is configured for automatic deletion/archiving on the Storage page of the project
properties.
2. The last activation of the project is older than the retention setting on the project.
3. It is not a base project with existing derived projects.
4. It is not a special project (e.g. User Settings, or anything under the System or Configuration trees).
5. The project is not locked (e.g. active).
6. The owner of the project is not connected, unless that user is configured to allow concurrent
housekeeping (see Section 5.5.2).
If Purge projects has been ticked in the Housekeeping dialog, when the Housekeeping is executed,
each project will be considered for purging. A project that is already locked (e.g. an active project) will
not be purged.
• If the project is considered to have invalid metadata (e.g. is a pre-14.0 legacy project, or a PFD
import without undo information).
Once housekeeping has been configured to purge projects, the automatic purging of projects on acti-
vation may be disabled by the user, thus preventing the confirmation dialog popping up. To do this, the
option Automatic Purging should be to Off on the Storage page in the Project Properties dialog. This
parameter can also be set to Off for multiple projects (see Section 5.5.5 for details).
If Delete recycle bin objects is set in the Housekeeping dialog, when Housekeeping is executed, each
user’s recycle bin will be examined. Entries older than the number of days specified in the Housekeeping
dialog (as shown in Figure 5.5.2) will be deleted.
In order to ensure that housekeeping is working correctly, it should be regularly verified by an adminis-
trator. This is done by inspecting the HOUSEKEEPING_LOG table via SQL or the data browsing tools of
the multi-user database. For each run, housekeeping will insert a new row to this table showing the start
and end date/time and the completion status (success or failure). Other statistics such as the number
of deleted projects are kept. Note that absence of a row in this table for a given scheduled day indicates
that the task failed before it could connect to the database. In addition to the HOUSEKEEPING_LOG
table, a detailed log of each housekeeping run is stored in the log file of the housekeeping user.
2. Configure those users expected to be active during housekeeping, as described in Section 5.5.2.
3. Configure the Housekeeping dialog as described in Section 5.5.3.
4. If using the project deletion/archiving task, configure automatic deletion/archiving properties for
new projects, as described in Section 5.5.5.
5. If using the project deletion/archiving task, configure automatic deletion/archiving properties for
existing projects, as described in Section 5.5.5.
6. Regularly monitor the HOUSEKEEPING_LOG table to verify the status of housekeeping runs, as
described in Section 5.5.8.
This chapter provides details of how to create and manage user accounts, user groups, and profiles.
Key objectives of the user account managing system are to:
• Protect the ’system’ parts of the database from changes by normal (non-Administrator) users.
• Protect parts of the databases belonging to user “A” from changes by user “B”.
• Facilitate sharing of user data.
The user account managing system provides each user with their own “private” database space. 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 use data from their private database.
The user account managing system manages this whilst using only one single database in the back-
ground, which allows for simple backup and management of the overall database.
The default name for a PowerFactory user is the Windows user name, which is automatically created
when PowerFactory is started for the first time.
A brief introduction to the top level structure of the PowerFactory database is convenient before present-
ing the user accounts and their functionality.
The data in PowerFactory is stored inside a set of hierarchical directories. The top level structure is
constituted by the following folders:
The Configuration folder Contains company specific customising for user groups, user default set-
tings, project templates and class templates for objects. Configuration folder is read only for
normal users.
The main Library folder Contains all standard types and models provided with PowerFactory. The
main library folder is read only for normal users.
The System folder Contains all objects that are used internally by 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.
User account folders Contain user project folders and associated objects and settings.
A database administrator account is created with the PowerFactory installation. The main functions of
the administrator are:
Under a multiuser database environment, the administrator is the only user with permissions to:
The administrator is also the only user that can modify the main library and the system folders. Although
the administrator has access to all the projects of all the users, it does not have the right to perform any
calculation.
• Select the Shortcut in the Windows Start Menu PowerFactory 15.1 (Administrator).
• Log into PowerFactory as a normal User and select via the Main menu Tools → Switch User. Se-
lect Administrator and enter the corresponding password. By default the administrator password
is Administrator.
For further information about the administrator roll, refer to the PowerFactory Installation Manual.
In the case of an installation with a local database, the default name for a PowerFactory user is the
Windows user name, which is automatically created when PowerFactory is started for the first time. (see
chapter 5: Program Administration). In this case the program will automatically create and activate the
new account, without administrator intervention. In order to create other PowerFactory users if required,
the ’User Manager’ object can be used as described below:
In multi-user database installations, the administrator creates new user accounts by means of a tool
called the ’User Manager’, which is found in the Configuration folder.
• Log on as Administrator. You can do so by starting the PowerFactory Administrator shortcut in the
Windows Start menu or by switching the user via Tools → Switch User in the main tool bar.
• In the left pane of the Data Manager click on Configuration folder to display its contents.
• Double click on the User Manager icon ( , right pane) and press the Add User. . . button.
• In the General page, enter the new user name and password.
• 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
functions that a user can access. The Multi User Database option (bottom of the tab) should be
checked for all users that will access the multi user database.
The administrator can edit any user account to change the user name, set new calculation rights or
change the password. To edit an existing user account:
• Right-click on the desired user and select Edit from the context sensitive menu. The User edit
dialog will be displayed.
Any user can edit her/his own account by means of the User edit dialog. In this case only the full name
and the password can be changed.
Note: The Administrator is the only one who may delete a user account. Although users can delete
all projects inside 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).
Any project or folder in a user account may be shared. This action can be performed selectively by
sharing only with certain user groups. User groups are created by the administrator via the User
Manager. To create a new user group:
• Log on as Administrator.
• In the Data Manager open the Configuration folder and double click on the User Manager icon( ).
• The new group is automatically created in the User Groups directory of the Configuration folder.
The Administrator can change the name of an existing group by means of the corresponding edit dialog
(right clicking on it and selecting Edit from the context sensitive menu). Via the context sensitive menu,
groups can also be deleted.
• Copying the user in the Data Manager (right click on the user and select Copy from the context
sensitive menu).
• Selecting a user group in the left pane of the Data Manager.
• Pasting a shortcut of the copied user inside the group (right-click the user group and select Paste
Shortcut from the context sensitive menu).
Users are taken out of a group by deleting their shortcut from the corresponding group.
The Administrator can also set the Groups Available Profiles on the Profile tab of the Group dialog.
For information about sharing projects, refer to section 18.6 (Sharing Projects).
Profiles can be used to configure toolbars, menus, dialog pages, and dialog parameters. By default,
PowerFactory includes “Base Package” and “Standard” profiles, selectable from the main menu under
Tools → Profiles. Selecting the “Base Package” profile limits icons shown on the Main Toolbar to those
that are used with the Base Package of the software. The “Standard” profile includes all available
PowerFactory icons.
Profiles are created in the Configuration → Profiles folder by selecting the New Object icon and then
Others → Settings→ Profile. An Administrator can create and customise profiles, and control User/User
Group selection of profiles from the Profile tab of each group.
Figure 6.5.1 shows the Profile dialog for a new profile, CustomProfile, and figure 6.5.2 illustrates
aspects of the GUI that may be customised using this profile. This section describes the customisation
procedure.
Definition of Icons
Icons can be defined in the Configuration → Icons folder by selecting the New Object icon and then
Others → Other Elements→ Icon (IntIcon). From the Icon dialog, icon images can be imported and
exported. Icons should be 19 pixels by 19 pixels in Bitmap format (recommended to be 24-bit format).
Command Configuration
• Command: This is the selected DPL script (which should generally be located in the Configuration
→ DPL commands folder), or selected Com* object.
• Edit: If selected, the DPL command dialog will appear when a Command is executed. If de-
selected, the DPL command dialog will not appear when a Command is executed.
• Icon: Previously created icons can be selected, which will be shown on the menu where the
command is placed. If no icon is selected, a default icon will appear (a Hammer, DPL symbol, or
default Com* icon, depending on the Class type).
Template Configuration:
• Template The name of the template. The name may be for a unique template, or include wildcards
(such as *.ElmLne) for selection of a group of templates. Templates should be in ’System/Li-
brary/Busbar Systems’ folder, or in the ’Templates’ folder of the active project.
• Drawing modeThe drawing mode can be set where there are multiple diagrammatic representa-
tions for a template (such as for a substation). Three options are available:
• Symbol name Sets the representation of templates with a composite drawing mode (e.g. Gener-
alCompCirc or GeneralCompRect).
• Icon Previously created icons can be selected, which will be shown on the menu where the
template is placed. If no icon is selected, a default icon will appear (a Template symbol or custom
icon).
• Description This description will be displayed when a user hovers the mouse pointer over the
icon. If left blank, the template name will be displayed.
The Main Toolbar and Drawing Toolbars can be customised using the Toolbar Configuration. The field
Toolboxes may either refer to a Toolbox Configuration (SetTboxconfig) or a Toolbox Group Configuration
(SetTboxgrconfig), which may in-turn refer to one or more Toolbox Configurations.
Figure 6.5.5 shows an example where there is a main toolbox, and a toolbox group. The toolbox group
adds a Change Toolbox icon to the menu, which allows selection of Basic Commands and Custom
Commands groups of commands.
Each toolbox can be customised to display the desired icons, such as illustrated in figure 6.5.6
Prior to customising the displayed buttons and menu items etc, the user should first define any required
custom Commands and Templates. A Tool Configuration object can be created in the Configuration →
Profiles folder, or within a user-defined Profile, by selecting the New Object icon and then Others →
Settings→ Tool Configuration. If created in the Profiles folder, the commands will be available from the
“Standard” profile. Conversely, if the Tool Configuration object is created within a profile (SetProfile) the
commands and templates will only be available for use in this profile. If there is a Tool Configuration
within a user-defined profile, as well as in the Profiles folder, the Tool Configuration in the user-defined
profile will take precedence. Optionally, customised icons can be associated with the Commands and
Templates.
The Main Menu, Data Manager, Graphic, Virtual Instruments, and Output Window menus can be
customised from the Menu Configuration dialog. The Change to Configuration View button of the Profile
dialog is used to display description identifiers for configurable items, such as illustrated in the context-
sensitive menu shown in figure 6.5.7. The Menu Configuration includes a list of entries to be removed
from the specified menu. Note that a Profile may include multiple menu configurations (e.g. one for
each type of menu to be customised).
The Dialog Page Configuration may be used to specify the Available and Unavailable dialog pages
shown when editing elements, such as illustrated in figure 6.5.8. Note that Users can further customise
the displayed dialog pages from the Functions tab of their User Settings.
The dialog Configuration may be used to customise element dialog pages, such as illustrated for a
Synchronous Machine element in figure 6.5.9. “Hidden Parameters” are removed from the element
dialog page, whereas “Disabled Parameters” are shown but cannot be modified by the user. A Profile
may include multiple dialog configurations (e.g. one for each class to be customised).
Note that if a there is a dialog Configuration for say, Elm* (or similarly for ElmLne,ElmLod), as well as a
dialog Configuration for ElmLne (for example), the configuration settings will be merged.
Note: Configuration of dialog parameters is an advanced feature of PowerFactory , and the user should
be cautious not to hide or disable dependent parameters. Seek assistance from DIgSILENT
support if required.
6.5.6 References
Profiles can also contain references to configurations. This allows several profiles to use the same
configurations. These referenced configurations can either be stored in another profile or in a subfolder
of the “Profiles” folder (e.g. a user-defined profile can use configurations from a pre-defined profile).
User Settings
The User Settings dialogue, shown in Figure 7.0.1, offers options for many global features of Power-
Factory. This chapter is dedicated to describe this options. The User settings dialogue may be opened
either by clicking the User Settings button ( ) on the main tool bar, or by selecting the Options → User
Settings. . . menu item from the main menu.
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. When 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 this option 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.
Retention of results after network change when the option “Show last results” is selected, modifica-
tions to network data or switch status etc. will retained the results, these will be shown on the
single line diagram and on flexible data pages in grey until the user reset the results (e.g. by
selecting Reset Calculation, or conducting a new calculation).
Cursor settings
General Options
• 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 Drawing Tools Floater Specifies the width of the graphics toolbar when this
is a floating window.
• No. of Columns in Drawing Tools 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.
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.
May be used to exclude colours, by number code, which are to be used for feeder definitions. This
is used to prevent the use of colours which are already used for other purposes. Ranges of colour
numbers are entered as ’2-9’. Multiple ranges of colours must separated by commas, as in ’2-9;16-23’.
If the option is enabled, the user can define the background colour of the single line graphics by using
the pop up menu and then pressing OK.
In the Advanced tab of the Graphic Window page more graphic setting options are available:
If the option is enabled, the user can left click a branch element within the single line graphic and then
resize it.
Defines how objects within an user defined region of the single line graphic (defined by left clicking and
then drawing a rectangle) are selected:
• Complete Only the objects, that are completely enclosed in the defined region, are selected.
• Partial All the objects within the defined area are selected.
For information about the Graphic Window refer to Chapter 9(Network Graphics (Single Line Diagrams)).
The data manager page specifies which object types will be displayed or hidden in the tree representa-
tion, and whether confirmation prompts will appear when objects or data is changed in the data manager
itself.
Show in Treelist
Object classes that are selected will be displayed in the database tree.
Browser
• 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.
Operation Scenario
If the Save active Operation Scenario automatically is enabled, the period for automatic saving must be
defined.
Export/Import Data
• Binary DataSaves binary data, such as results in the result folders, to the ’DZ’ export files
according to selection.
• 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.
The default global type folder is the System/Library/Types 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.
For information about the PowerFactory Database Manager refer to Chapter 10 (Data Manager).
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.
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 certain modules in
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 .
7.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.
• PFM-DSM
7.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.
Options
• Enable Virtual Space Allows the cursor to move into empty areas.
• 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.
Language colouring
Defines the syntax-highlighting used when the type of text is not known.
ShortCuts
7.8 StationWare
When working with DIgSILENT ’s StationWare , connection options are stored in the user settings.The
connection options are as follows:
Service Endpoint Denotes the StationWare server name. This name resembles a web page URL and
must have the form:
• http://the.server.name/psmsws/psmsws.asmx or
• http://192.168.1.53/psmsws/psmsws.asmx
http denotes the protocol, the.server.name is the computer name (or DNS) of the server computer
and psmsws/psmsws.asmx is the name of the StationWare application.
Username/Password
Username and Password have to be valid user account in StationWare . A StationWare user account
has nothing to do with the StationFactory user account. The very same StationWare account can be
used by two different PowerFactory users.The privileges of the StationWare account actually restrict the
functionality. For device import the user requires read-access rights. For exporting additionally write-
access rights are required.
Contingency Analysis
A confirmation dialogue is showed when the Remove Contingencies option is selected in the Contin-
gency Analysis dialogue.
Handling
Chapter 8
The basic database structure in PowerFactory and the data model used to define and study a power
system is explained in Chapter 4 (PowerFactory Overview). It is recommended that users become
familiar with this chapter before commencing project definition and analysis in PowerFactory . This
chapter describes how to define and configure projects, and how to create grids.
There are three methods to create a new project. Two of them employ the Data Manager window and
the third employs the main menu. Whichever method is used the end result will be the same: a new
project in the database.
Method 2: Using the element selection dialog from the Data Manager:
• In the field at the bottom of the New Object window (IntPrj) (after selecting option Others in the
Elements field). Note that names in PowerFactory are case-sensitive.
• Press Ok. The project folder dialog will then open. Press Ok.
• Locate the active user in the left-hand pane of the Data Manager.
• Place the cursor on the active user’s icon or a folder within the active user account and right-click.
• From the context-sensitive menu choose New → Project. Press Ok. The project folder dialog will
then open. Press Ok.
Note: The ComNew command is used to create objects of several classes. To create a new project it
must be ensured that the Project option is selected.
In order to define and analyse a power system, a project must contain at least one grid and one
study case. After the new project is created (by any of the methods described), a new study case
is automatically created and activated. A dialog used to specify the name and nominal frequency of a
new, automatically-created grid pops up. When the button OK is pressed in the grid dialog:
The newly-created project has the default folder structure shown in Figure 8.1.1. Although a grid folder
and a study case are enough to define a system and perform calculations, the new project may be
expanded by creating library folders, extra grids, Variations, Operation Scenarios, Operational Data
objects, extra study cases, graphic windows, etc.
Projects can be deleted by right-clicking on the project name in the Data Manager and selecting Delete
from the context-sensitive menu. Only inactive projects can be deleted.
Note: The default structure of the project folder is arranged to take advantage of the data model
structure and the user is therefore advised to adhere to it. Experienced users may prefer to
create, within certain limits, their own project structure for specific advanced studies.
The project dialog shown in Figure 8.1.2 pops up when selecting Edit → Project. . . on the main menu or
when right-clicking the project folder in the Data Manager and selecting Edit from the context-sensitive
menu.
The Basic Data page contains basic project settings and allows the creation of new study cases and
grids:
• Pressing the button in the Project Settings field opens a dialog where the validity period of
the project, the input units to be used within the project (i.e. units and the decimal prefixes for
input dialogs) and the calculation settings (i.e. base apparent power and the minimal value of the
resistances and conductances in p.u) are defined.
• Pressing the New Grid button will create a new grid and will open the grid edit dialog. A second
dialog will ask for the study case to which the new grid folder should be added. For additional
information about creating a new grid please refer to Section 8.2(Creating New Grids).
• The New Study Case button will create a new study case and will open its dialog. The new study
case will not be activated automatically. For further information about creating study cases please
refer to Chapter 11: Study Cases, Section 11.2 (Creating and Using Study Cases).
• When a project is created, its settings (i.e. result box definitions, report definitions, flexible page
selectors, etc.) are defined by the default settings from the system library. If these settings are
changed, the changes are stored in the project’s Settings folder. The settings from another project
or the original (default) ones can be taken by using the buttons Take from existing project or
Set to default in the Changed Settings field of the dialog. The settings can only be changed
when a project is inactive.
• The name of the active study case is shown in the lower part of the dialog window under Active
Study Case. Its dialog can be opened by pressing the button.
• Pressing the Contents button on the dialog will open a new data browser displaying all the folders
included in the current project directory.
The Sharing page of the dialog allows the definition of the project sharing rules. These rules are
particularly useful when working in a multi-user database environment. Further information is given in
Chapter 18 (Data Management).
The Derived Project page provides information if the project is derived from a master project.
The Storage page provides information about the data stored inside the project. By default all changes
within the last 7 days will be stored. This is called the retention period and can be changed on this page.
The Description page is used to add user comments and the approval status.
The Project Overview is illustrated in Figure 8.1.3. It is a dockable window, 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 facilitates
easy interaction with the project data. The window is docked by default, but can be undocked by the user
and displayed as a floating window that can be placed both inside and outside of the main application
window. If required, the window can be closed by the user. To close or reopen the window, toggle the
option Window → Project Overview from the main menu.
The following objects and information can be accessed via the Project Overview.
• Study Cases
– Active Study Case
– Inactive Study Cases
– Current Study Time
• Operation Scenarios
– Active Scenario Schedulers
– Active Scenarios
– Inactive Scenarios
• Variations
– Recording Expansion Stage
– List of active Variations with active and inactive Expansion Stages as children
– List of inactive Variations with inactive Expansion Stages as children
• Grid/System Stages
– List of active Grids or System Stages
– List of inactive Grids or System Stages
• Trigger
– Active triggers
Entries for active objects are displayed with bold text, entries for inactive objects are displayed as
disabled/grey.
A context-sensitive menu can be accessed by right-clicking on each of the tree entries. The following
actions are available for each of the entries:
In the project settings, the validity period of the project can be defined, as can the method used for
calculation of symmetrical components for untransposed lines, amongst other settings.
PowerFactory 15 extends the idea of a model into the dimension of time. The project may span a period
of months or even years considering network expansions, planned outages and other system events.
The period of validity of a project specifies the time span the network model is valid for.
The validity period is defined by the Start Time and End Time of the project (see Figure 8.1.2). The
study case has study time, which must fall inside the validity period of the project.
• Open the Data Manager and browse to the project folder (IntPrj).
• Right-click on it and select Edit from the context-sensitive menu.
• On the Basic Data tab press the project settings button ( ). The project settings dialog will open.
• On the Validity Period page adjust the Start Time and End Time of the project.
• Press OK to accept the changes and close the window.
To activate a project use the option File → Activate Project from the main menu. This shows a tree with
all the projects in the current user’s account. Select the project that should be activated. Alternatively,
a project may be activated by right-clicking on it in the Data Manager and using the context-sensitive
menu.
The last 5 active projects are listed under File in the main menu. The currently active project is the first
entry in this list. To deactivate the currently active project, select it in the list. Alternatively, you may
choose the option File → Deactivate Project from the main menu. To activate another project, select it
in the list of the 5 last active projects.
Projects (or any folder in the database) can be exported using the *.dz or the *.pfd (PowerFactory Data)
file format. It is recommended to use the new PFD format (*.pfd) whenever possible. This format is
ideal for handling even very large projects. The performance of the import/export using the *.pfd has
been optimised and the consumption of memory resources is significantly lower than with the old file
format (*.dz). All new functions available in the PowerFactory database, e.g. time stamps and versions,
are fully-supported by the new PFD file format.
To export a project, select File → Export. . . → Data. . . from the main menu or click on the icon of the
Data Manager. Alternatively projects can be exported by selecting the option Export. . . on the project
context-sensitive menu (only available for inactive projects). The dialog is shown in Figure 8.1.4.
• Objects to export: This table shows all objects that will be exported within the *.pfd file.
• Export current state: This option is visible if the project (or, object in the Objects to export
table) has Versions defined. If enabled (default), the current state of the project will be exported.
Otherwise, only the state of the selected Version/s will be exported.
• Versions to export: This table shows all Versions of the Objects to export, if any are available. By
disabling the checkbox for specific Versions, the user can define which Version should or should
not be exported. For master projects, the corresponding Version for the derived project must be
selected. See Section 18.3.1 for further details.
• Export data in retention period: If enabled, data changes from within the retention period will
be exported. See Section 8.1.1 for further details.
• Export external data files (e.g. result files): If enabled, calculation results (i.e. result files, plot
data, etc.) will be exported. Otherwise, the calculation must be repeated after importing.
• Export derived project as regular project (only available for derived projects, see Section 18.3.1):
If enabled, a derived project will be exported as an ’adequate’ project. In this case no master
project is required. It should be noted that this project can no longer be reused as a derived
project.
• Export to former PowerFactory version: If the project is intended to be imported into a former
PowerFactory version, this flag must be activated and the version specified.
• PFD file: The path where the *.pfd file will be saved.
Projects can be imported by selecting File → Import. . . → Data. . . from the main menu or by clicking
on the icon in the Data Manager. The user can select the type of file to import from the Files of type
field in the Open dialog which pops up. Alternatively, projects can be imported by selecting Import. . .
on the project context-sensitive menu (only available for inactive projects).
Additionally, several import/export filters are available for other data formats.
In order to avoid problems when exporting/importing projects, it is recommended to check for external
references before exporting the project. This can be done by selecting the option Check for external
References via the project context-sensitive menu.
If external references are found, these can be packed before exporting by selecting the option Pack
external References in the project context-sensitive menu.
The user can define the source of the External References (i.e. Global Library, Configuration folder,
etc). A new folder, called “External” containing all external references will be created inside the project.
Electrical networks can be defined in PowerFactory using the graphical editor or the Data Manager.
The graphical method is simple; it consists of selecting the desired network components from the
drawing toolbox and placing them at the desired location on the single line graphic. In this case,
PowerFactory automatically creates the network components represented by the graphical objects in
the active grids/expansion stages. The connections and the corresponding cubicles are automatically
created as the new component is placed (and connected). Using the Data Manager requires the manual
definition of the cubicles within the terminals and the selection of the specific cubicle where a branch
element is to be connected. This manual definition is more suitable for large networks whose graphical
representation becomes complicated. Advanced users may combine both graphical and Data Manager
methods to define and modify their network models more efficiently.
In addition to describing the basic methods used to define and edit network models, this section is
intended to explain practical aspects related to the creation and management of network grouping
objects. The procedures used to create and manage additional network diagrams are also presented
here. Information about defining and working with Variations and Expansion Stages is provided in a
separate section. To begin, a description of the network model definition, and how new grid folders are
created, is required.
Note: Experienced users may define networks combining the Data Manager and the graphical editor.
Good practice is to create and connect the network components in the single line graphic and
multi-edit them in the Data Manager.
To add a grid folder to the current network model, various methods may be employed:
1. Select Edit → Project on the main menu. This will open the dialog of the currently-active project.
Press the New Grid button.
2. Select Insert → Grid . . . on the main menu.
3. Right-click the project folder in the Data Manager and select Edit. Press the New Grid button.
4. Right-click the Network Data folder (in the active project) in a Data Manager window and select
New → Grid from the context-sensitive menu.
The dialog to create a new grid will then pop up. There the grid name, the nominal frequency and a grid
owner (optional) may be specified. A second dialog will appear after the Ok button has been pressed.
In this dialog the study case that the grid will be linked to must be selected. Three options are given:
1. add this Grid/System Stage to active Study Case: Only available when a study case is active.
2. activate a new Study Case and add this Grid/System Stage: Creates and activates a new study
case for the new grid.
3. activate an existing Study Case and add this Grid/System Stage: Add the new grid folder to
an existing, but not yet active study case.
After the Ok button in the second dialog has been pressed, the new grid is created in the Network Model
folder and a reference in the Summary Grid object of the selected study case is created. Normally,
the second option (from the list above) is preferred because this creates a new study case which is
dedicated to the new grid only. This means that the new grid may be tested separately using a load flow
or other calculation. To analyse the combination of two or more grids, new study cases may be created
later, or the existing ones may be altered.
As indicated in Chapter 11(Study Cases), grids can be later added or removed from the active study
case by right-clicking and selecting Add/Remove from Active study case.
9.1 Introduction
PowerFactory works with three different classes of graphics which constitute the main tools used to
design new power systems, controller block diagrams and displays of results:
Diagrams are organised in Graphic Boards for visualisation (see Section 9.5.2 for more information).
In this section it is explained how the tools of the Graphical Editor are used to define and work with
network models.
Drawing power system elements is a simple matter of choosing the required element representation in
the Drawing Toolbox located in the right hand pane of the PowerFactory GUI. Input parameters of the
element are edited through the element and type dialog. Complete information about the element and
type parameters are given in the Appendix C Technical References of Models.
To create a new power system element, select the corresponding button in the Drawing Toolbox. This
toolbar is only visible to the user when a project and study case is active and the open graphic is
unfrozen by deselecting the Freeze Mode button ( ). 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 one of the cursor icons (rectangular or
free-form selection) or press ESC or right-click with the mouse).
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 nodes (makes a connection). If
wishing to stop the drawing and connecting process press the Escape key or right click at the mouse.
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
elements (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
centred between the first two terminal connections automatically.
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 terminal to make the connection.
Note: Nodes for connecting branches are usually defined before placing them on the single line dia-
gram. However, it is possible to place ’connection free’ branch element on the single line diagram
by pressing the Tab key once for each required connection (e.g. twice for a line, three times for a
three winding transformer)
Figure 9.2.1 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).
If a load or machine is connected to a terminal 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 terminal, if possible.
Note: By default all power system elements are positioned “bottom down”. However, if the Ctrl key
is pressed when the graphic symbol is positioned onto the drawing surface, it will be positioned
either turned 90 degrees (terminals) or 180 degrees (edge elements). If the element has already
been placed and the user wishes to flip it to the other side of the terminal, it can be done by
selecting the element and the right-click → Flip At Busbar.
Once drawn, an element can be rotated by right-click and selecting from the Rotate commands. Fig-
ure 9.2.2 shows an example of rotated and flipped power system elements.
The connection between edge elements and terminals is carried out by means of cubicles. When work-
ing with the graphical editor, the cubicles are automatically generated in the corresponding terminal.
Note: When connections to terminals are defined with switch elements of the class ElmCoup (circuit
breakers), cubicles without any additional switches (StaSwitch) are generated.
When commencing a single line diagram, it is common to first place the required nodes / terminals
(ElmTerm) on the graphic. There are several symbol representations available for busbar type terminals,
from the drawing toolbox on the right-hand pane of the PowerFactory GUI.
Busbar (Short) Looks the same as a Busbar 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.
Junction / Internal Node 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.
Busbars (terminals) should be placed in position and then, once the cursor is reset, dragged, rotated
and sized as required. Re-positioning is performed by first left clicking on the terminal to mark it, and
then click once more so that the cursor changes to . Hold the mouse button down and drag the
terminal to a new position. Re-sizing is performed by first left clicking on the terminal to mark it. Sizing
handles appear at the ends.
Single port elements (loads, machines, etc.) can be positioned in two ways. The simplest method is
to select the symbol from the toolbar and then left click the busbar where the element is to 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 (i.e. a
dashed line), left-clicking on another node will connect it to that node. 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 (lines, transformers, etc.) are positioned in a similar manner to single port
symbols. By left-clicking the first busbar, the first 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 - e.g. a transformer). The second connection
is made when a node is left clicked.
Triple port elements (e.g. 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 centred
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.
Note: 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 elements (press Tab again to leave the third leg unconnected).
Pressing Esc or right-click 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 Redraw the element
whilst retaining the data connectivity.
Annotations are created by clicking one of the annotation drawing tools. Tools are available for drawing
lines, squares, circles, pies, polygons, etc. To draw these symbols left click at on an empty space on
the single line diagram and release the mouse at another location (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.
For further information on defining lines, see section 9.3 (Defining and Working with Lines and Cables).
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.
The element is highlighted with a different pattern depending on whether the graphic has been frozen
or not, as seen in Figure 9.2.3, where 9.2.3a is the when the Freeze Mode is selected and 9.2.3b when
Freeze Mode is deselected.
• To mark all graphical elements, press the All button ( ). The keyboard short cut Ctrl+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
dialog under the ’Graphic Windows’ page, on the Advanced tab, can alter the manner in which
objects are marked using this marking method, as either ’Partial’ or ’Complete’. ’Complete’ means
that the whole object marked must lie inside the rectangle.
• To mark more than one object, hold down the Ctrl key whilst marking the object.
• Holding down the Alt-key while clicking on the same object again marks all the adjacent objects.
Doing this several times marks more and more connected objects.
• In PowerFactory it is possible to place a terminal on an existing line in the single line diagram by
placing the terminal on the line itself. Moving the terminal to a different location on the single line
diagram may move line sections in an undesirable manner. By holding the Ctrl+Alt keys whilst
moving the terminal, the line sections will not be moved. However, note that this does not change
the actual location of the terminal along the line.
The data of any element (its edit dialog) may be viewed and edited by either double-clicking the graphic
symbol under consideration, or by right-clicking it and selecting Edit Data.
When multiple objects are selected, their data can be viewed and edited trough a data browser by
right-clicking the selection and choosing Edit Data from the context sensitive menu.
Interconnections between two different graphics can be achieved using two methods:
1. 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.
This 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-click → Paste Graphic Only. Only a graphical
object is pasted into the second graphic and no new data element is created.
2. Ensure that there is a node to connect to in the graphics that are to be interconnected. Then
connect an edge element between the two graphics.
Example
In this example a line will be used to interconnect two regions according to the second method.
1. Select a line drawing tool from the toolbar and create the first connection as normal by left clicking
a node (see Figure 9.2.4).
2. Double-click to place the symbol. Your cursor is now attached to the line by a ’rubber band’.
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 (see Figure 9.2.5).
3. Once in the second graphic left click to place the line symbol (see Figure 9.2.6) and then left click
on the second node.
The interconnected leg is shown by an symbol. Right-clicking on the element presents a Jump to
next page option.
Note: 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 system. 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 connections” diagram colouring may
be employed.
Substations and Secondary Substations from existing templates are created using the network dia-
grams. The substations are represented in these diagrams by means of composite node symbols.
Overview diagrams are single line diagrams without detailed graphical information of the substations.
Substations and Secondary Substations are illustrated as “Composite Nodes”, which can be coloured
to show the connectivity of the connected elements (“Beach Ball”). Substations and Secondary Sub-
stations from pre-defined templates (or templates previously defined by the user) are created using the
network diagrams. The substations are represented in these diagrams by means of composite node
symbols.
• Click on the symbol of the composite node ( or ) for Substations or ( ) for Secondary
Substations listed among the symbols on the right-hand drawing pane.
• Select the desired substation template from the list.
• Click on the overview single line diagram to place the symbol. The substation is automatically
created in the active grid folder.
• Right click the substation, select Edit Substation, and rename the substation appropriately.
• Close the window with the templates.
• Press Esc or right click on the mouse to get the cursor back.
• Resize the substation symbol in the overview diagram to the desired size.
A diagram of the newly created substation can be opened by double clicking at the composite node
symbol. In the new diagram it is possible to rearrange the substation configuration and to connect the
desired components to the grid.
For further information on templates please refer to Chapter 12: Project Library, Section 12.4 (Templates
Library).
Press the button to open the colouring dialog. Select the ’Function’ for which the colouring mode
is relevant (for example, select the ’Basic Data’ tabpage). Under ’Other’ select ’Topology’, and then
’Station Connectivity’.
There are two ways to open the graphic page of a substation. The first is to double-click on the
corresponding composite node in the overview diagram. The second is to go to the graphic object
of the substation in the data manager, right-click and select Show Graphic.
Switching Rules ( ) (IntSwitching) store switching actions for a selected group of switches that are
defined inside a substation. The different switching actions (no change, open or close) are defined by
the user considering different fault locations that can occur inside a substation. By default, the number
of fault locations depends on the number of busbars and bay-ends contained inside the substation;
although the user is allowed to add (and remove) specific fault locations and switches belonging to the
substation. The switch actions will always be relative to the current switch positions of the breakers.
The selection of a Switching Rule for a substation is independent of the selection of a Running Arrange-
ment and if required, the reference to the switching rule in a substation can be stated to be operational
data; provided the user uses the Scenario Configuration object. For more information on the scenario
configuration refer to Chapter 14 (Operation Scenarios).
A typical application of Switching Rules is in contingency analysis studies, where there is a need to
evaluate the contingency results considering the “actual” switch positions in a substation and compare
them to the results considering a different substation configuration (for the same contingency).
• Edit a Substation, either by right-clicking on the substation busbar from the single line graphic,
and from the context-sensitive menu choosing Edit a Substation, or by clicking on an empty place
in the substation graphic, and from the context-sensitive menu choosing Edit Substation. This will
open the substation dialog.
• Press the Select button ( ) in the Switching Rule section and select New. . .
• The new Switching Rule dialog pops up, where a name and the switching actions can be specified.
The switching actions are arranged in a matrix where the rows represent the switches and the
columns the fault locations. By default the fault locations (columns) correspond to the number of
busbars and bay-ends contained inside the substation, while the switches correspond only to the
circuit breakers. The user can nevertheless add/remove fault locations and/or switches from the
Configuration page. The switch action of every defined breaker in the matrix can be changed by
double clicking on the corresponding cell, as illustrated in Figure 9.2.7. Press afterwards Ok.
• The new switching rule is automatically stored inside the substation element.
A Switching Rule can be selected in the Basic Data page of a substation dialog (ElmSubstat) by:
• Pressing the Select button ( ) in the Switching Rule section. A list of all Switching Rules for the
current substation is displayed.
• Selecting the desired Switching Action.
A Switching Rule can be applied to the corresponding substation by pressing the Apply button from
within the switching rule dialog. This will prompt the user to select the corresponding fault locations
(busbars) in order to copy the statuses stored in the switching rule directly in the substation switches.
Here, the user has the option to select either a single fault location, a group or all of them.
The following functional aspects must be regarded when working with switching rules:
• A switching rule can be selected for each substation. By default the selection of a switching rule
in a substation is not recorded in the operation scenario. However, this information can defined
as part of an operational scenario by using the Scenario Configuration object (see Chapter 14:
Operation Scenarios).
• If a variation is active the selection of the Switching Rule is stored in the recording expansion
stage; that is considering that the Scenario Configuration object hasn’t been properly set.
The Assign button contained in the switching rule dialog allows to set it as the one currently selected
for the corresponding substation. This action is also available in the context-sensitive menu in the data
manager (when right-clicking on a switching rule inside the data manager).
The Preview button contained in the switching rule dialog allows to display in a separate window the
different switch actions for the different fault locations of the corresponding substation.
New composite branches can be created in the Data Manager using the procedure described in Chap-
ter 10, Section 10.3.4 (Defining Composite Branches in the Data Manager). The definition and con-
nection of the branch components can then be carried out in the relevant single line diagram, which is
automatically generated after the creation of the new branch.
Branches from previously defined templates are created using the single line diagram. The branches
are represented in these diagrams by means of the Composite Branch symbol ( ). To create a new
branch from a template:
• Click on the Composite Branch button ( ) listed among the symbols on the right-hand drawing
pane. A list of available templates (from the Templates library) for branches will appear. If only
one Branch template exists, no list is shown.
• From this list choose the template that you want to create the branch from.
• If the branch is to be connected with terminals of the same single line graphic, simply click once
on each terminal.
• If the branch is to be connected with a terminal from another single line diagram, you have to
’Paste graphically’ one of the terminals on the diagram where you want to represent the branch,
or connect across pages as discussed in section 9.2.5 (Interconnecting Power Subsystems).
• If the branch is to be connected with terminals from a substation, click once on each composite
node to which the branch is to be connected. You will be automatically taken inside each of those
composite nodes to make the connections. In the substation graphic click once on an empty spot
near the terminal where you want to connect the branch end, and then on the terminal itself.
A diagram of the newly created branch can be opened by double clicking at the composite branch
symbol. In the new diagram it is possible to rearrange the branch configuration and to change the
branch connections.
It is possible to define the phase technology of elements such as terminals, lines, and loads. In
instances where the number of phases of a connecting element (e.g. a circuit breaker or line) is equal
to the number of phases of the terminal to which it connects, PowerFactory will automatically assign
the connections. However, when connecting single-phase elements to a terminal with greater than one
phase, or two-phase elements to terminals with greater than three phases, it is sometimes necessary to
adjust the phase connectivity of the element to achieve the desired connections. The phase connectivity
can be modified as follows:
• Open the dialog window of the element (by double-clicking on the element).
• Press the Figure >> button to display a figure of the elements with its connections on the bottom
of the dialog window.
• Double-click on the dark-red names for the connections inside this figure.
• Specify the desired phase connection/s.
Alternatively, click the right arrow ( ) next to the Terminal entry and specify the desired phase connec-
tion/s.
Note: It is possible to colour the grid according to the phases (System Type AC/DC and Phases). For
more information about the colouring refer to Section 9.7.6 (Graphic Attributes and Options).
This section describes specific features and aspects of line and cable data models used in PowerFactory
. Detailed technical descriptions of the models are provided in Appendix C (Technical References of
Models).
In PowerFactory , lines and cables are treated alike, they are both instances of the generalised line
element ElmLne. A line may be modelled simply as a point-to-point connection between two nodes and
will refer to a line (TypLne), tower (TypTow), a tower geometry (TypGeo), a line coupling (ElmTow), or a
cable system coupling (ElmCabsys) type. Alternatively, lines may be subdivided into sections referring
to different types.
Note: Anywhere that ’line’ is written in this section, ’lines and/or cables’ may be read, unless otherwise
specified.
The purpose of separating lines into sections is to obtain different line parts, with different types (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).
The simplest line model is a point-to-point connection between two nodes. This is normally done in the
single line graphic by selecting the ( ) icon and by left clicking the first terminal, possibly clicking on
the drawing surface to draw a corner in the line and ending the line at the second terminal by left clicking
it. This will create an 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 Figure 9.3.2 shows a line which is connected between the nodes called ’Line End
Terminal’ and ’Line Feeder Bus’ from a grid called ’ North’. 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, add/remove the breaker, or change phase connectivity as discussed in
section 9.2.8 (Working with Single and Two Phase Elements).
The type of the line is selected by pressing the ( ) next to the type field. Line types for a line/ line route
are:
• The TypLne object type, where electrical parameters are directly written (the user can select if the
type is defined for an overhead line or a cable).
• Tower types (TypTow and TypGeo), where geometrical coordinates and conductor parameters are
specified, and the electrical parameters are calculated from this data. Selection of the tower type
will depend on the user’s requirement to link conductor type data to the line element as in TypGeo
(for re-use of the one tower geometry with different conductors), or to link conductor type data to
the tower type as in TypTow (for re-use of one tower geometry with the same conductors).
Once the lines (or cables) have been created it is possible to define couplings between the circuits that
they are representing by means of line coupling elements ElmTow (for overhead lines) and cable system
coupling elements ElmCabsys (for cables).
Details of how to create Line Sections, Cable Systems, and Line Couplings are provided in the fol-
lowing sections, and further information about line/cable modelling is given in the respective Technical
References.
• Press the Sections/Line Loads button in the line dialog. This will open a data browser showing
the existing line sections (if the line has not been sectioned, it will be empty).
• Click on the new object icon ( ) and select the element Line Sub-Section (ElmLnesec).
• The edit dialog of the new line section will pop up. There it is possible to define the type and length
of the new section.
Consider a three-phase underground cable comprised of three single-core cables with sheaths. The
cable system is created within the active project by taking the following steps.
1. Create a Single Core Cable Type (TypCab) and Cable Definition Type (TypCabsys):
• Navigate to the ’Equipment Type Library’ and select the New Object icon, or on the right-hand
side of the data manager right-click and select New → Others.
• Select ’Special Types’, ’Single Core Cable Type’, and then Ok.
• Enter the Type parameters and select Ok. (Note that in this example, a Sheath is also
selected, and therefore a separate line will later be defined in the Network Model to represent
the sheath.)
• Again select the New Object icon, or on the right hand side of the data manager right-click
and select New → Others.
• Select ’Special Types’, ’Cable Definition’, and then Ok.
• Enter type parameters including ’Earth Resistivity’, and ’Coordinates of Line Circuits’ (note
that positive values indicate the depth below the surface). Select the Single Core Cable Type
defined in the previous steps and press Ok.
Note that the steps above could be conducted in an alternative order. For example, item 2 could be
completed before 1. Also, item 3 could be completed before item 1, and Cable Types could be created
at the time the Cable System Element is created. However, the recommended approach is to first define
the Type data that is to be used in the Network Model, then to create the Network Model with particular
instances of the cable as in the example.
Figure 9.3.3 illustrates the interrelationship between the elements and types used to define cable
systems inPowerFactory. Note that by right-clicking the line that represents the sheath and selecting
’Edit Graphic Object’ the Line Style can be modified to indicate graphically that this line represents the
sheath.
Consider an example where there are two parallel transmission lines, each with a three-phase HV (132
kV) circuit, three-phase MV (66 kV) circuit, and two earth conductors. The tower element is created
within the active project by taking the following steps.
1. Create the Conductor Types (TypCon) for phase and earth conductors:
• Navigate to the ’Equipment Type Library’ and select the New Object icon, or on the right-hand
side of the data manager right-click and select New → Others.
Note that the steps above could be conducted in an alternative order. For example, item 3 could be
completed before 1 and 2. Also, item 4 could be completed before items 1 and 2, and Conductor
Types and Towers could be created at the time the Line Couplings Element is created. However, the
recommended approach is to first define the Type data that is to be used in the Network Model, then to
create the Network Model with particular instances of the lines/towers as in the example.
Figure 9.3.4 illustrates the interrelationship between the elements and types used to define Line Cou-
plings (Tower Elements) in PowerFactory.
PowerFactory offers the user the option to explicitly represent the neutral connections and interconnec-
tions of the following widely used elements:
The interconnection of separate neutral wires is illustrated with the help of the Synchronous Generator.
A separate neutral connection can be activated by choosing the option N-Connection on the Zero
Sequence/Neutral Conductor tab on the basic data page of the element as shown in figure 9.4.1, the
graphical symbol of the object will change. An illustration for the Synchronous Generator element is
shown in figure 9.4.2. Please note, once the N-Connection via a separate terminal option is selected,
the Vector Groups layer can no longer be hidden in the single line diagram.
To connect the neutral of the Element to a neutral busbar, right click on the element and press Connect
Element. An example of a single line diagram with the interconnection of neutral wires is shown in figure
9.4.3. A Neutral terminal is configured by ensuring that the Phase Technology of the terminal is set to
N as shown in figure 9.4.4.
In the PowerFactory graphic windows, graphic objects associated with the active study case are dis-
played. Those graphics include single line diagrams, station diagrams, block diagrams and Virtual
Instruments. 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 the graphics, and calculation results
may be displayed and configured.
Many of the 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 them is to use the right mouse button to display a menu.
This menu is known as a ’Context Sensitive Menu’; 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 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.
1. Single Line Diagrams (network diagrams) for entering power grid definitions and for showing
calculation results.
2. Detailed graphics of substations or branches (similar to network diagrams) for showing busbar
(nodes) topologies and calculation results
3. Block Diagrams for designing logic (controller) circuits and relays.
4. Virtual Instrument Pages for designing (bar) graphs, e.g. for the results of a stability calculation,
bitmaps, value boxes, etc...
The icon Graphical Pages ( ) can be found inside the Data Manager. Grids, substations, branches,
and controller types (common and composite types in PowerFactory terminology) each have a graphical
page. In order to see the graphic on the screen, open a Data Manager and locate the graphic page
object you want to show, click on the icon next to it, right-click and select Show Graphic. The “Show
Graphic” option is also available directly from each object. So for example you can select a grid in the
data manager, right-click, and show the graphic. The graphic pages of grids and substations are to be
found in the subfolder Diagrams ( ) under the “Network Model” folder.
Note that it is also possible to store Diagrams within the Grid, although this is generally not recom-
mended.
The graphics that are displayed in an active project are determined by the active study case. 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 is much like the ’Summary Grid’ folder which is
also stored within the Study Case, and links active grids to the Study Case. Both the Graphics Board
and Summary Grid are automatically created and maintained and should generally not be edited by the
user.
Within a PowerFactory project, the Network Model folder contains a sub-folder called Diagrams. This
sub-folder should generally also not be edited by the user as it is automatically created and maintained.
It contains the objects that represent single line and substation graphics (IntGrfnet objects). More
than one graphic (single line or substation diagrams) may be created 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 ’Project’ that is shown in Figure 9.5.2. The active study case is called Study Case_1 and
the active grid has three single line graphics that have been created for it, Grid_1, Grid_2 and Grid_3.
The graphics board folder in the study case has a reference to only the Grid_1 graphic object and thus
only this graphic for the grid will be shown when the study case is activated.
In the case of single line graphics, 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 by right-clicking the grid and selecting
Show Graphic from the context sensitive menu. Graphics may be removed from the active study case
by right-clicking the tab at the bottom of the corresponding graphic page and selecting 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, such as Virtual Instrument Panels.
Figure 9.5.2: Relationship between the study case, graphics board and single line diagrams
In a simple network there may be a 1:1 relationship between data objects and their graphical repre-
sentations, i.e. every load, generator, terminal and line is represented once in the graphics. However,
PowerFactory provides additional flexibility in this regard. Data objects may be represented graphically
on more than one graphic, but only once per graphic. Thus a data object for one terminal can be
represented graphically on more than one graphic. All graphical representations contain the link to the
same data object.
Furthermore, graphical symbols may be moved without losing the link to the data object they represent.
Likewise, data objects may be moved without affecting the graphic.
The graphics themselves are saved in the database tree, by default in the Diagrams folder of the Network
Model. This simplifies finding the correct Single Line graphic representation of a particular grid, even in
the case where there are several graphic representations for one grid.
When the drawing tools are used to place a new component (i.e. a line, transformer, 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 are
associated with. This information may be determined by right-clicking the graphic → Graphic Options,
see Section 10.5 (Editing Data Objects in the Data Manager) 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 ). In this case 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 calculations.
When an element is deleted completely (right menu option → Delete Element) a warning message will
confirm the action. This warning may be switched off in the User Settings dialog, General page, “Always
confirm deletion of Grid Data”).
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 and selecting 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 dialog. 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 dialogs 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 Section 10.5 (Editing Data Objects in the Data
Manager).
Finding specific elements in a large project may be difficult if one had to look through the single line
diagram alone. PowerFactory includes the Mark in Graphic tool, to assist the user in finding elements
within the graphic. To use this tool the user has to first search for the desired object in the Data Manager
using any of the methods presented in Chapter 10 (Data Manager). Once a searched object/element
is identified, it may be right-clicked and the option Mark in Graphic selected. This action will mark the
selected object in the single line graphic where it appears. This can also be done pressing Crtl+M.
When performing this command ensure that the object itself is selected, as shown in Figure 9.5.3. The
menu will be different to that seen when selecting an individual field, as shown in Figure 9.5.4.
Note: The position of an object in the database tree can be found by:
-Opening the edit dialog. The full path is shown in the header of the dialog.
-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.
A new project may be created by selecting File → New on the main menu. This creates a new Project
folder and a dialog is displayed where the user can define a grid folder in the Project folder. Finally the
Graphic page in which the single line diagram will be displayed.
A new graphic window can be created using the New command dialog. This dialog may be opened
using one of the following methods:
The ComNew dialog must be configured to create the desired new object and the new object should
be named appropriately. Ensure that the correct target folder for the new object is selected. Graphical
objects that may be created using this dialog (DiaPagetyp) are:
Grid Creates a new grid folder and a new Single Line Graphic object in that folder. The (empty)
single line graphic will be displayed.
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 be displayed.
Virtual Instrument Panel Creates a new Virtual Instrument Page object. The (empty) Virtual
Instrument Page will be displayed.
Single Line Diagram Creates a Single Line Graphic in the target folder. Before the graphic is
inserted, the user is prompted to select the relevant grid.
The target folder will be set to the ∖User 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 icon on the graphics board toolbar. This will add the new graphics page
to the existing graphics board.
Further information about how to draw network components is given in the following sections.
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 are described other sections of the manual.
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 Ctrl key is pressed
during drag and drop. The icon copies a virtual instrument panel and inserts the copy alongside the
original panel.
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 icon 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 icon in the toolbar will do the same).
Each graphics window has a specific Drawing Tool Box. This toolbox has buttons for new network
symbols and for non-network symbols. See Figure 9.5.5 for two examples.
• Network or block diagram symbols, which are linked to a database object: terminals, busbars,
lines, transformers, switches, adders, multipliers, etc.
• Graphical add-on symbols: text, polygons, rectangles, circles, etc.
The toolboxes are only visible when the graphics freeze mode is off. The graphics freeze mode is turned
on and off with the icon (found at the main icon bar of the graphical window).
On the status bar of PowerFactory (Figure 9.5.6), the active grid folder is displayed on the left-most field,
indicating the target folder (grid) that will be modified when you make changes in the network diagram.
To change the active target folder, double-click this field and then select the desired target folder. This
can be useful if the user intends to place new elements on a single line diagram, but have the element
stored in a different grid folder in the data manager.
This section provides information about how to draw network components from existing 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, to first create objects in the database manager (either manually, or via import
from another program), and subsequently draw these objects 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 type 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).
The Draw Existing Net Elements tool may also be used to perform this action, as described in the next
sections.
Click on the button Drawing existing Net Elements ( ) and a window with a list of all the terminals
(busbars) in the network that are not visualised in the active diagram will appear.
Click on the symbol for busbars ( ) in the drawing toolbox. The symbol of the busbar (terminal) is now
attached to the cursor.
If the list is very large, press the button Adjacent Element Mode ( ), and then right-click an existing
node in the single line diagram and select ’Set as starting node’. This activates the selecting of distance
(number of elements) from elements in the active node. Select the Distance of 1 in order to reduce the
number of busbars (terminals) shown.
If the button Use drawn nodes as starting objects ( ) is also selected, the list will be filtered based on
all drawn nodes (not just a single starting node).
If Show elements part of drawn composite nodes ( ) is selected, elements internal to already drawn
composite nodes will be shown in the list. However, since they are already drawn as part of the
composite node, they should not be re-drawn.
The marked or selected element can now be visualised or drawn by clicking somewhere in the active
diagram. This element is drawn and disappears from the list.
Note that the number of elements in the list can increase or decreases depending on how many
elements are a distance away from the element lastly drawn. Scroll down the list, in case only certain
elements have to be visualised.
Close the window and press Esc to return the Cursor to normal. The drawn terminals (busbars) can be
moved, rotated or manipulated in various ways.
Similar to the busbars, elements like lines and transformers connecting the terminals in the substation
can be drawn.
Press the button Draw Existing Net Elements ( ). For lines select the line symbol ( ) from the drawing
toolbox, for transformers select the transformer symbol ( ), and so on.
Similar to terminals, a list of all the lines (or transformers, or elements which have been chosen) in the
network, that are not in the active diagram are listed. Reduce the list by pressing the button Elements
which can be completely connected ( ) at the top of the window with the list. A list of lines with both
terminals in the active diagram is pre-selected. If the list is empty, then there are no lines connecting
any two unconnected terminals in the active diagram.
For each selected line (or transformers...) a pair of terminals, to which the line is connected is marked
in the diagram. Click on the first terminal and then on the second. The selected line is drawn and is
removed from the list of lines.
Continue drawing all lines (or transformers...), until the list of lines is empty or all the lines to be drawn
have been drawn. If a branch cannot be completely drawn (for example, when the terminal at only one
end of a line is shown on the diagram), it is possible to double-click the diagram and arrows will appear
to indicate that the line connects to a terminal that is not shown. Figure 9.6.1 provides an illustration.
When a power system model is imported from DGS format that includes graphical information or GIS
data, single line diagram/s will automatically be created. However, if a model is imported from another
program it may only include network data (some data converters provided in PowerFactory do also
import graphics files). Even without a single line diagram, it is possible to perform load-flow and other
calculations, and new single line diagram can be created by drawing existing database elements.
This is done by first creating a new single line graphic object in the Diagrams folder of the Network
Model (right-click the Diagrams folder and select New → Graphic). This opens the single line graphic
dialog, where the ’Current Net Data’ pointer should be set to the respective grid folder. See Section 9.7
for more information.
As soon as the correct folder has been set, and OK has been pressed, the single line graphic object ( )
is created and a blank graphic page will be displayed. The Draw Existing Net Elements ( ) icon on the
graphics toolbar may now be pressed. This opens a database browser listing all elements considered
by the active study case (see Figure 9.6.2) 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
(Figure 9.6.2, red square) provided. Once a drawing tool is chosen, in this case the Terminal tool,
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 (in the browser, Figure 9.6.2) will be removed from the list
and placed onto the graphic, and the next terminal down will be highlighted, ready for placement.
After all busbars have been inserted into the single line graphic, branch elements may be selected in
the graphic toolbox. When one of the branch elements is selected in the browser, the corresponding two
busbars will be highlighted in the single line graphic. This is also why the nodes should first be placed
on the graphic. Branch elements are placed once the nodes are in position.
See also:
Note: Another useful approach to developing single line diagrams is to first define a feeder (say, at
the cubicle closest to the source node), then run a load-flow, navigate to the feeder in the data
manager, right-click and select Show → Schematic visualisation by Distance or Bus Index. See
Section 13.5 (Feeders) for further information on how to define feeders.
Note: Before placing elements onto the graphic users may find it useful to configure and display a
background layer. This will be an image 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 Section 9.7.4 for more information on layers.
In this section the commands, options and settings that are available in PowerFactory to configure and
use the graphic windows are introduced. The sub-sections of this chapter are divided as illustrated in
Figure 9.7.1. These commands are also available from the main menu under View.
Locks the diagram from graphical changes, no network elements can be added or deleted. Note that
the status of switches can still be modified when freeze mode is on.
9.7.1.2 Zoom In
Press the Zoom In icon to change the cursor to a magnifying glass. The mouse can then be clicked and
dragged to select a rectangular area to be zoomed. When the frame encompasses the area you wish
to zoom into release the mouse button. Alternatively, Ctrl+- and Ctrl++ keys can be used to zoom in
and out, or Ctrl and the mouse scroll wheel.
Note: The Acceleration Factor for zooming and panning can be changed on the Advanced tab of the
Graphic Window page in the User Settings dialog.
To zoom “back” press the Zoom Out button - this will step the zoom back to the last state.
Use the hand tool to pan the single line diagram (when not at the page extends). Alternatively, the
mouse scroll wheel can be used to scroll vertically, and Ctrl+Arrow keys used to scroll vertically
and horizontally. When zoomed to the extent of the page, the tool will automatically switch to either
’Rectangular Selection’ or ’Free-form Selection’.
Used to select a rectangular section of the single line diagram. Note that this icon is generally depressed
when using the mouse pointer for other tasks, such as selecting Menu items, however the ’Hand Tool’
or ’Free-form Selection’ may also be used.
This function marks (selects) all objects in the single line diagram. 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 Ctrl+A may also be used to perform
this action.
9.7.2.1 Print
This function will send the graphic to a printer. A printer dialog will first appear. Also accessed through:
The drawing area for single line diagrams, block diagrams and virtual instruments is modified in the
“Drawing Format” dialog. A predefined paper format can be selected as-is, edited, or a new format
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 Ctrl+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 across 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 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.
9.7.2.3 Rebuild
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.Also accessed through:
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 dialog to configure the new graphics object will appear first.
Note: The Page Tab menu is opened by right-clicking a page tab, shown just below the single line
diagram.
• Graphic folder object (IntGrfnet, single line network or substation diagrams) → opens the
selected graphic.
• Terminal (ElmTerm, ) opens the station graphic of the selected terminal (this may also be ac-
cessed 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.
Also accessed through:
Page Tab Menu: Insert Page → Open Existing Page
Other page commands accessed through the page tab are as follows:
Remove Page:
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:
This function can be used to change the name of the selected graphic.
Move/Copy Page(s):
This function can be used to move a page/s to modify the order of graphics. Also accessed through: