You are on page 1of 47

DIgSILENT PowerFactory

Page 1 of 47

DIgSILENT PowerFactory

General Information
1: Welcome 2: DIgSILENT Contact and Support 3: About this Guide 4: PowerFactory Overview 5: Program Setting, Logging on and User Accounts 6: User Settings 7: The PowerFactory Data Model 8: General Information about Analyses in PowerFactory

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

Chapter 1 Welcome
The calculation program PowerFactory, as written by DIgSILENT, is a computer aided engineering tool for the analysis of industrial, utility, and commercial electrical power systems. It has been designed as an advanced integrated and interactive software package dedicated to electrical power system and control analysis in order to achieve the main objectives of planning and operation optimization. The name DIgSILENT stands for "DIgital SImuLation and Electrical NeTwork calculation program''. DIgSILENT Version 7 was the world's first power system analysis software with an integrated graphical one-line interface. That interactive one-line diagram included drawing functions, editing capabilities and all relevant static and dynamic calculation features. The PowerFactory package was designed and developed by qualified engineers and programmers with many years of experience in both electrical power system analysis and programming fields. The accuracy and validity of the results obtained with this package has been confirmed in a large number of implementations, by organizations involved in planning and operation of power systems. In order to meet today's power system analysis requirements, the DIgSILENT power system calculation package was designed as an integrated engineering tool which provides a complete 'walk-around' technique through all available functions, rather than a collection of different software modules. The following key-features are provided within one single executable program:
1. 2. 3. 4. 5. 6.

PowerFactory core functions: definition, modification and organization of cases; core numerical routines; output and documentation
functions Integrated interactive single line graphic and data case handling Power system element and base case database Integrated calculation functions (e.g. line and machine parameter calculation based on geometrical or nameplate information) Power system network configuration with interactive or on-line access to the SCADA system Generic interface for computer-based mapping systems

By using just a single database, containing all the required data for all equipment within a power system (e.g. line data, generator data, protection data, harmonic data, controller data), PowerFactory can easily execute any or all available functions, all within the same program environment. Some of these functions are load-flow, short-circuit calculation, harmonic analysis, protection coordination, stability calculation and modal analysis. DIgSILENT PowerFactory has originally been designed as a complete package for the high-end user. Consequently, there are no special 'lightweight' versions, no cut-outs of a 'heavy' version. This does not, however, mean that non high end users will find themselves at sea when using PowerFactory. The program is also friendly to the basic user. Users who are learning about power systems are able to easily and quickly perform load-flows and short-circuit calculations, without needing to immediately master the mathematical intricacies of the calculations. PowerFactory allows the user to learn primarily about power systems and not PC quirks- all that is required is a reasonable working knowledge of Windows applications such as Word and Excel. The program is shipped with all of the engines and algorithms that are required for high-end use. The functionality that has been bought by a user is configured in a matrix, where the licensed calculation functions, together with the maximum number of busses, are listed as coordinates. In addition, there are options available which will allow the configuration and fine-tuning of the software according to the user's needs, for some of the functions. In this manner, not every PowerFactory license contains all functionality described in this manual, but only those actually required, thereby reducing the complexity of the outset. As requirements dictate further functionality can be added to the license. The user thus does not have to learn a whole new interface for new functions, but merely uses new commands within the same environment. In addition, the original network data is used and only extra data, as may be required by the new calculation function, needs to be added.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 2 of 47

Chapter 2 DIgSILENT Contact and Support


For further information about the company DIgSILENT, our products and services please visit our web page www.digsilent.de or contact us at: DIgSILENT GmbH Heinrich-Hertz-Strae 9 72810 Gomaringen / Germany www.digsilent.de General Information: If you are looking 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: mail@digsilent.de Technical Support: If you need technical support concerning PowerFactory, DIgSILENT experts offer direct assistance to users with valid maintenance agreements via: Phone: +49-(0)7072-9168-50 E-mail: support@digsilent.de Adding your company affiliation and the build number of your PowerFactory version to your query will help us to answer your questions faster. The build number is in "Help -> About PowerFactory..." on the main menu. Here you also will find an abbreviation containing of three letters, which is helpful for us ("This Program is Licensed to XXX"). Additionally, if you send us an *.dz or *.pfd file concerning to your query, it is often easier for us to reproduce your reported items.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

Chapter 3 About this Guide


This chapter will give you information about how to use this documentation, the used conventions and information about additional documentations. The PowerFactory User's Manual Used Conventions The PowerFactory Help System

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

3.1 The PowerFactory User's Manual


This User's Manual is intended to be a reference for users of the DIgSILENT PowerFactory software. In the first part, the PowerFactory interface and the basic program settings are discussed. Then a data model approach is used to describe how to represent power systems in PowerFactory and how to manage studies over them. Following the discussion about the program handling, comes the presentation of the available calculation functions. Each chapter deals with a different calculation, presenting the most relevant theoretical aspects, the PowerFactory approach and the corresponding interface. Additional tools such as the DIgSILENT Programming Language (DPL), the reporting functions, and the communication interfaces with other programs are presented in the final part. The online version of this manual includes a especial section dedicated to the mathematical description of the models and their parameters. The section comprises a set of Technical Reference Papers, each one corresponding to a specific component of a power system. To facilitate its portability, visualization, and printing, the papers are attached to the online help as PDF documents. They are downloaded by clicking on the indicated links. References for the functions of the DIgSILENT Programming Language (DPL) and the DIgSILENT Simulation Language (DSL), are also included as appendixes of the online version. This Reference User's Manual is written for end users involved in the analysis of electrical power systems. It is assumed that the program has been installed and the user has a basic understanding of the PowerFactory work environment. Before starting with this guide, new users are recommended to read the information and complete the hands-on Tutorial from the Getting Started Manual.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

3.2 Used Conventions


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

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 3 of 47

Key As in "Press the left mouse key''. A key is either one of the mouse keys or a key on the keyboard. Mouse keys are sometimes called 'buttons', as in 'the mouse button.' Button As in "Press the OK button''. The word "button'' is used for screen areas which perform some action when clicked using the mouse. In other words, a 'virtual' button. Icons Icons are usually described by the popup name that you read when you hover the cursor over it. For example, press user settings dialogue. Icons are also shown as seen on screen, as in the press Right/Left clicking As in "Right click the browser''. Means pointing the cursor at the object described (the browser) and pressing the right/left mouse key. Double Clicking As in "Double click the button''. Means pointing the cursor at the object described and pressing the left mouse key twice within about half a second (the time interval is as set in the Windows operating system). Ctrl-B (key combination example) means that the user should press the combination of keys described. For example, "Press Ctrl-B to toggle between balanced/unbalanced case,'' means that the user should press and hold down the first keyboard key (the Control key on the keyboard in this example) and then press the second key (B) as well. Menu sequences When a user needs to select a command through cascaded menu options the sequence is shown by arrows that indicate what option to choose next, starting from the original menu button. For example, setting the drawing format can be done by pressing the Options button to access the options menu, then by choosing "Graphic" from the list offered, and finally "Drawing Format..." from the last list; this series of actions is all simply described by Options --> Graphic --> to open the

to open the user settings dialogue.

Drawing Format...
" " and ' ' 'These' quotes are used to indicate that the description is one that can be found within the program- one that is not user definable, for example, the balloon help description 'Calculate Load Flow' that you see when you hover your cursor over the Load Flow icon. "These" are used to indicate data that a user has entered or should enter. "These" quotes are also used to indicate a process or series of objects that have no discernible name, but which need to be described. For example, the "drawing tools panel", which is found on the right hand side of the drawing canvas. and [1] [2] [3], etc. Show a sequence of events that should be performed. Where they are numbered they will be associated with a graphic in which the numbers appear. left-clicking, right-clicking, clicking, double-clicking, etc. Wherever the instruction clicking or double-clicking appears it should be taken to mean clicking and double-clicking using the left mouse button. When the right mouse button is to be used it will be explicitly stated.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

3.3 The PowerFactory Help System


DIgSILENT PowerFactory is provided with a complete help package to support users at all levels of expertise. Documents with the basic information on the program and its functionality are combined with references to advanced simulation features, mathematical descriptions of the models and of course application examples. PowerFactory offers the following help resources:
Installation Manual: PowerFactory installation guide, describes the procedures followed to install and set the program. It is available in the PowerFactory installation CD and the DIgSILENT support site (PDF file). Licensed costumers receive a hard copy. Getting Started Manual: Basic Information for new users and hands-on tutorial. Access via Help menu (CHM file) of PowerFactory, and the DIgSILENT support site (PDF). Licensed users receive a Hard copy. User's Manual: This document. Access via Help menu (CHM file) of PowerFactory, and the DIgSILENT support site (PDF). Licensed users receive a Hard copy. 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 (chapters D Types Reference and C Elements Reference ). Additionally they can be downloaded from the DIgSILENT support site. Context Sensitive Online Help: Pressing the key F1 while working with PowerFactory will lead you directly to the related topic inside the User's Manual. Examples on the Demo account: The Demo account is a special user account set with every installation of the program. It contains several application examples of PowerFactory calculation functions. First Steps Document: Guide to use the calculation examples from the Demo version. Access via the installation CD and the DIgSILENT support site (PDF). FAQs: Users with a valid maintenance agreement can access the DIgSILENT support site and its FAQ section, which contains interesting questions and answers regarding specific applications of PowerFactory. Support: Users with a valid maintenance agreement will get individual support from DIgSILENT experts via: Phone: +49-(0)7072-9168-50 E-mail: support@digsilent.de DPL Manual: Reference manual for the DIgSILENT Programming Language, containing descriptions and examples of all the implemented functions. Available in the DIgSILENT support site (PDF). DSL Manual: Reference manual for the DIgSILENT Simulation Language, containing descriptions and examples of all the implemented functions. Available in the DIgSILENT support site (PDF).

All new versions and builds of the program include 'Release-Notes' documenting the implemented changes. Additional documents explaining the concept behind the program design and its applications are provided with the PowerFactory installation CD.

DIgSILENT GmbH www.digsilent.de

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 4 of 47

Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

Chapter 4 PowerFactory Overview


General Concept PowerFactory Simulation Functions General Design of PowerFactory Data Arrangement User Interface Getting Help

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.1 General Concept


The general concept behind the program design and application can be described by means of the three basic integration characteristics that contribute to make PowerFactory a unique power system analysis tool:
Functional Integration

DIgSILENT PowerFactory software is implemented as a single executable program, and is fully compatible with Windows
95/98/NT/2000/XP/Vista. The programming method employed allows for a fast 'walk around' the execution environment, and eliminates the need to reload modules and update or transfer results between different program applications. As an example, the power flow, fault analysis, and harmonic load flow analysis tools can be executed sequentially without resetting the program, enabling additional software modules and engines or reading external data files. Vertical Integration A special feature of the DIgSILENT PowerFactory software is the unique vertically integrated model concept. This allows models to be shared for all analysis functions and more importantly, for categories of analysis, such as "Generation", "Transmission", "Distribution" and "Industrial". No longer are separate software engines required to analyze separate aspects of the power system, as DIgSILENT PowerFactory can accommodate everything within one integrated frame and one integrated database. Database Integration

DIgSILENT PowerFactory provides optimal organization of data and definitions required to perform any type of calculation, memorization of settings or software operation options. There is no need in tedious organization of several files for defining the various analysis aspects. The PowerFactory database environment fully integrates all data required for defining cases, operation scenarios, single-line graphics, outputs, run conditions, calculation options, graphics, user-defined models, etc. There is no need to keep and organize hundreds of files on hard disc, every thing you require to model and simulate a power system is integrated in a single database!
Single Database Concepts: all data for standard and advanced functions are organized in a single, integrated database. This is applied also for graphics, study case definitions, outputs, run conditions, calculation options, fault sequences, monitoring messages as well as user defined models. Project Management: All the data that defines a power system model and allows its calculation is stored in so called 'Project' folders within the database. Inside a 'Project', folders called 'Study Cases' are used to define different studies of the system considering the complete network, only parts of it or variations on its current state. This 'project and study case' approach to define and manage power system studies is a unique application of the object-oriented software principle. Standard software packages often require the user to create a large number of similar saved cases, with multiple nested directories for large complex networks and studies. However, DIgSILENT PowerFactory has taken a totally new approach, and introduced a structure that is both easy to use while avoiding redundancy. Multi-User Operation: Multiple users each holding its own projects or working with data shared from other users are supported by a 'Multiuser' database operation. In this case the definition of access rights, user accounting and groups for data sharing are managed by a database administrator.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.2 PowerFactory Simulation Functions


PowerFactory incorporates an impressive and continuously growing list of simulation functions including:
Load Flow and Fault Analysis, allowing meshed and mixed 1-,2-, and 3-phase AC and/or DC networks. Low Voltage Network Analysis Distribution Network Optimization IEC Cable Sizing Dynamic Simulation EMT Simulation Eigenvalue Analysis

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 5 of 47

System Identification Protection Analysis Harmonic Analysis Reliability Analysis Voltage Stability Analysis Contingency Analysis Power Electronic Device Modeling Grounding A/D Interfacing Interface for SCADA/GIS/NIS Compatibility with other software systems such as PSS/E & PSS/U Multi-User Database and User Accounting Optimal Power Flow

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.3 General Design of PowerFactory


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

PowerFactory is intended to be initially used and operated in a graphical environment. That is, data entry is accomplished by drawing the network under study and then by editing the objects on the drawing canvas to assign data to them.
Figure 4.1 shows how PowerFactory looks like when a project is active. It shows the Graphic window (up) and the Output window (below).

Fig. 4.1: Main PowerFactory windows

As users progress and become more adept with the program, data will be manipulated by using a data viewer called the Data Manager. The two means of accessing the data are thus via the graphics page/s and via the Data Manager. Data is accessed from the graphics page by double-clicking on an object. An input dialogue pops up and the user may then edit the data for that object. All of the data that is entered for such objects is hierarchically structured in folders to allow the user to navigate through it. To view the data and its organization, a "Data Manager" is used. Figure 4.2 shows the Data Manager Window. The data manager is similar in appearance and working to a Windows Explorer. As mentioned, data pertaining to a study is organized into several folders. Before examining this structure we should understand the philosophy behind this arrangement.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 6 of 47

Fig. 4.2: PowerFactory Data Manager window

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.4 Data Arrangement


Firstly, it is clear that, for the study of any system, there are two distinct sets of information that can be defined:
Data that pertains directly to the system under study, that is, electrical data. Study management data, for example, which graphics should be displayed, what options have been chosen for a load flow, which 'areas' of the network should be considered for calculation, etc.

The electrical data itself can also be further divided into logical sets. When we construct a power system we make use of standardized materials or components - a roll of cable for example. In simple terms we can describe the cable electrically by its impedance per km length whilst it is still on the cable drum; in other words, generic information about this cable, is called "Type" data. When we cut a length of the cable for installation the type data is retained in a modified way, as follows: 600m of cable that has a Type impedance of 'Y' Ohms/ km will now have an impedance of '0.6*Y' Ohms. We can thus see that the length of the cable, 0.6 km, can be seen as a separate set of information. This set will contain all of that information particular to the specific installation or application of the piece of cable we are considering. Information such as the derating factor of the installed cable, its local name, the nodes that it is connected to at either end; in other words, all information that is non-generic, will fall into this information set. In PowerFactory we call this "Element Data". Within the element data, there is information related to the operational point of a devise but not to the devise itself i.e. the tap position on a transformer or the active power dispatch of a generator. These kind of data, which is subject to frequent changes during a study and may be used to simulate different operation scenarios of the same network, is further grouped inside the element data set in a subset called "Operational Data". This means that there are now four distinct sets that we need to arrange the data into. In 'data base' terms this means four folders, which, in PowerFactory, we call:
''Network Data'' folder: Holds all the element data. ''Operation Scenario'' folder: Holds the operational data defining a certain operational point. ''Equipment Type'' folder: Holds all the type data ''Study Case'' folder: Holds all the study management data.

For an optimal advantage of the flexibility offered by this data arrangement approach, the aforementioned folders should be hierarchically organized within a higher directory. In PowerFactory this higher directory is called ''Project''. Besides the described data sets, a project stores all the additional database ''objects'' required to model, simulate, analyze and visualize a particular power system. The PowerFactory database supports multiple users (as mentioned in 4.1) and each user can manage several 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.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 7 of 47

Fig. 4.3: Structure of a PowerFactory project in the Data Manager

Figure 4.3 shows a snapshot from a database as seen by the user in a data manager window.The folders listed contain the following type of data:
User Folder Three user accounts (Demo, Manual and Peter) containing different projects are shown. Project In this case named Simple Power System. This folder is the frame for all project subfolders. Equipment Types Holds all the type data. Network Model Holds the Network Data folder containing the element data. The Network Model folder also contains the graphical objects folders (Diagrams), storing network diagrams and the network modifications folders (Variations) storing expansions or topological changes to be applied in the original networks. Operation Scenarios Holds sets of operational data. Study Cases Contains the study Management Data - the 'tools' and 'tool settings' that are used to perform the calculations and the visualization of the results.

All the aspects related to the use and management of the project folder, including the subfolders listed above is given in chapters: For information about user accounts please refer to Chapter 5 Program Setting, Logging on and User Accounts .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.5 User Interface


The PowerFactory windows are the users interface to the program and the means to enter or manipulate data and/or graphics. DIgSILENT PowerFactory uses several kinds of windows some of which have been shown previously. To follow the explanation, please see Figure 4.4:
The main PowerFactory window is described in the title bar- "DIgSILENT PowerFactory 14.0" 1. The main menu bar contains the drop down menu selections 2. The Graphical Editor 3 displays single line diagrams, block diagrams and/or simulation plots of the current project. Studied networks and simulation models can be directly modified from the graphical editor by placing and connecting elements. The "Data Manager" 4 is the direct interface with the database. It is similar in appearance and working to a Windows Explorer. 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. When an object is right clicked (in the graphical editor or in the data manager) a context sensitive menu with several possible actions appears 5. When an object is double clicked its edit dialogue pops up 6. The edit dialogue is the interface between an object and the user. The parameters defining the object are accessed trough this edit dialogue. Normally an edit dialogue is composed of several 'pages' (also called tabs). Each tab groups parameters that are relevant to a certain function. In the example of Figure 4.4 the 'Load Flow' tab of a generator is shown, therefore only the generator parameters relevant to a load flow calculation are available. At the bottom of the PowerFactory window, an output window 7 with its own toolbar is shown.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 8 of 47

Fig. 4.4: PowerFactory initial appearance

The data manager sub-window (this window is created by pressing the icon, which is the first icon on the left of the main toolbar) is always floating and more than one can be active at the same time. The database manager itself has several appearances: it may only show the database tree for selecting a database folder, or it may be the full version with the database tree, the data browser, and all editing capabilities. One of the major tasks for the data manager is to provide access to the power system components. The power system components shown in the data manager can be 'gang-edited' (or 'group-edited') within the data manager itself, where the data is presented in a tabular format, for all the selected objects. Alternatively each object may also be individually edited by double clicking on an object (or right click -> "Edit"). The output window, at the bottom of the screen, is always there; it cannot be closed although it can be minimized. The output window can be "docked'', that is: fixed to a location on the bottom of the main window. The docked state is the default, as shown in the Figure 4.4. When clicking the right mouse button, when the cursor is in the output window area, the context sensitive menu of the output window appears. The output window can then be undocked by deselecting the "Docking View" (by clicking the mouse onto "Docking View" to 'untick' it. The undocked output window is still confined to the main window, but now as a free floating window. This sometimes occurs 'accidentally' when the user left clicks the tool bar for the output window and drags the mouse (keeping the mouse button down) to somewhere outside of the output window boundaries. To rectify this simply left click in the title bar of the undocked window and drag it down to the bottom of the screen where it will dock once more (if you have right clicked 'unticked' "Docking View" to right click and select "Docking View" once more. The undocked state is not a normal situation for the output window. Because the output messages that appear in this window are important at any stage while using the program, the docked state is the best place because it will be visible then and easy to locate. The edge of the output window shows a splitter bar [a] which is used to change the size of the output window. The 'drag' cursor, as shown at [a], appears automatically when the cursor is placed on the splitter bar. The left mouse button can be pressed when the 'drag' cursor is visible. This will turn the splitter bar to grey and the output window can now be resized by holding down the mouse button and moving the mouse up or down. The icon "Maximize Output Window'' ( ) on the main toolbar will enlarge the output window to almost full-screen. Left click the button again to switch back to the small output window. On the right of the title bar of any window or sub-window there are three buttons that are used to "Minimize", "Maximize"/"Restore Down" or "Close" the window.
The button minimizes the window to a small object, somewhere on the screen (usually in the lower left corner- this is the default position) in the case of a sub-window, or to the task bar for your computer- at the bottom of the screen. The button 'opens' the minimized window to full screen size.

The button reduces the window to a smaller size on the screen; initially there is a default size for this window but the user may resize it as desired. The button will close the sub-window or end the program if this button is clicked on the main window.

Sub-windows can be re-sized as follows: place the cursor over the lower right corner of the window and left click and hold the

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 9 of 47

button down- now drag the window to the size you require. You will find that each corner can be sized like this, as well as each edge.

Re-sizing sub-windowsThe following sections provide further information about the PowerFactory windows and their tool bars. Because the Graphical Editor and the Data Manager are main interfaces and their use is fundamental in the definition and analysis of power systems with PowerFactory, they are explained in separate chapters (11 The Data Manager and 10 The Graphics Editor ). Menu Bar Main Toolbar The Output Window

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.5.1 Menu Bar


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

Fig. 4.5: The help menu on the Menubar Press Alt-H to open the help menu. Use your keyboard to select the Getting Started Tutorial. Press return to open the Tutorial. The on-line Getting Started Tutorial is exactly the same as the printed version. Close the Getting Started Tutorial help (Use the on the main bar). You will return to the main PowerFactory program window. Left click the Help menu. Left click the option Users Manual. This opens the on-line User's Manual.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.5.2 Main Toolbar


The main toolbar (see Figure 4.6) shows the main PowerFactory command buttons/icons. Buttons that appear in grey only become active when appropriate.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 10 of 47

Fig. 4.6: The main toolbar

All command icons are equipped with balloon help text which pop up when the cursor is held still at the icon for a moment, and no key is pressed.
Find the icon for User Settings by using the balloon help. Do not use the mouse keys: just point at the icons, hold still, and a balloon text will pop up. Scan all icons until you find the right one.

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

When PowerFactory has just been started, the toolbar shows only the general command icons. The 'toolbar select' icon ( be clicked to select additional command icons.
Main Toolbar Definitions

) can

The main PowerFactory toolbar provides the user with quick access to the main commands available in the program. This section provides a brief explanation of the purpose of the icons found on this toolbar. More detailed explanations for each of the functions that the icons command are provided in the other sections of the manual. The main toolbar is depicted in two parts in Figure 4.7 and Figure 4.8. The icons from the lower part of figures 4.7 and 4.8 correspond to the options of the Graphic Window and are presented in Section 10.6.1.

Fig. 4.7: Main Toolbar, left part

Fig. 4.8: Main Toolbar, right part New Database Manager Opens a new database manager. When the option "Use Multiple Data Manager" (see under User Settings >General) is enabled in the user settings menu the user will be able to open as many data manager windows as required. If "Use Multiple Data Manager" is disabled in the user settings menu, the user will be able to open only one data manager window. For more information please refer to Chapter 11. Edit Relevant Objects for Calculation Provides a list of elements (colored in green) or types (colored in red) that are considered for calculation: e.g. transformer types, line elements, composite models, etc. The study case determines which objects are considered for calculation (for more information about study cases refer to Chapter 13: Study Cases). These objects are grouped by 'Class' (see the Chapter: Glossary for an explanation of 'Class' in the PowerFactory context). If, for instance, no relay objects are used, then the relay-button will not be shown. All objects from the selected class(es) will be shown in a browser. For more information please refer to Section 8.2. Date/Time of Calculation Case Displays the date and time for the calculation case. This option is useful when parameter characteristics of specific elements (e.g. active and reactive power of loads) are set to change according to a certain time scale. Modifying the date/time in this dialogue adjusts those Parameters that have time based triggers/scales accordantly. Edit Trigger Displays a list of all triggers that are in current use by the active study case. These triggers can be edited in order to change the values for which one or more characteristics are defined. These values will be modified with reference to the new trigger value. All triggers for all relevant characteristics are automatically listed. If required, new triggers will be created in the study case. For more information, see 7.7 Parameter Characteristics and Parametric Studies . Calculate Load-Flow Activates the load-flow command dialogue. For more information about the specific settings, please refer to Chapter 22 Load Flow Analysis . Calculate Optimal Power Flow Activates the optimal power flow command dialogue. Calculate Short-Circuit Activates the short-circuit calculation command dialogue. For more information, please refer to Chapter 23 Short-Circuit Analysis . Edit Short-Circuits Edits Short-Circuit events. Events are used when a calculation requires more than one action or considers more than one object for the calculation. Multiple fault analysis is an example of this. If, for instance, the user multi selects two busbars (using the cursor) and then clicks the right mouse button Calculate > Multiple Faults a Short-circuit event list will be created with these two busbars in it. Execute DPL Scripts

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 11 of 47

Displays a list of DPL scripts that are available. For more information about DPL scripts, please refer to Chapter G The DIgSILENT Programming Language - DPL . Output Calculation Analysis Presents calculation results in various formats. The output is printed to the output window and can be then used in external reports, or may be of assistance to interpret calculation results. Several different reports, depending on the actual calculation, can be created. For more information about the output of results please refer to Section 20.2.5 Output of Results . Documentation of Device Data Presents a listing of device data (a device is the model of any physical object that has been entered into the project for study). This output may be used in reports, or may be of use in checking data that has been entered. Depending on the element chosen for report, the user has two possibilities: to generate a short listing, or a detailed report. For more information please refer to Section 20.2.5 Output of Results Comparing of Results On/Off Compares the differences between two or more calculation results, for example, where certain settings or designs options of a power system have been changed from one calculation to the next. For more information please refer to 8.4 Comparisons Between Calculations . Edit Comparing of Results Enables the user to select the cases/ calculation results that are to be compared to one another, or to set the coloring mode for the difference reporting. For more information please refer to 8.4 Comparisons Between Calculations . Update database Utilizes the current calculations results (i.e. the calculation 'output' data) to change input parameters (i.e. that data that the user has entered). An example is the transformer tap positions, where these have been calculated by the load-flow command option "Automatic Tap Adjust of Tap Changers." For more information please refer to Section 8.4 Comparisons Between Calculations . Break Stops a transient simulation or DPL script that is running. Reset Calculation Resets any calculation performed previously. This icon is only enabled after a calculation has been carried out. User Settings User options for many global features of PowerFactory may be set from the dialogue accessed by this icon. For more information please refer to Chapter 6 User Settings . Maximize Graphic Window Maximizes the graphic window. Pressing this icon again will return the graphic window to its original state. Maximize Output Window Maximizes the output window. Pressing this icon again will return the output window to its original state. Current Study Case This drop down window displays the name of the study case that is currently activate. The user may also 'toggle' between study cases in the project by selecting them from this drop down list. Select ToolBar Drops down when pressed to present sets of icons (to the right of it) for various calculation commands: e.g. Stability, Reliability, Harmonics, Optimal Capacitor Placement and Data Acquisition.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.5.3 The Output Window


All textual output of DIgSILENT PowerFactory will be written to the output window. This includes all error messages or warnings, command messages, device documentation, result of calculations, generated reports, etc. The output window, at the bottom of the screen, is always there; it cannot be closed although it can be minimized. The output window can be "docked'', that is: fixed to a location on the bottom of the main window. The docked state is the default, as shown in Figure 4.9.

Fig. 4.9: The PowerFactory output window

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 12 of 47

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

The undocked state is not a normal situation for the output window. Because the output messages that appear in this window are important at any stage while using the program, the docked state is the best place because it will be visible then and easy to locate. The upper edge of the output window shows a splitter bar which is used to change the size of the output window. The 'drag' cursor, appears automatically when the cursor is placed on the splitter bar. The left mouse button can be pressed when the 'drag' cursor is visible. This will turn the splitter bar to grey and the output window can now be resized by holding down the mouse button and moving the mouse up or down. The output window may be moved and resized by:
Dragging the splitter bar as shown in Figure 4.9, when the output window is in the 'docking' mode Double-clicking the frame of the output window to dock/undock it from the main window. Pressing the Pressing the on the main toolbar, which enlarges the graphics board by hiding the output window. icons on the main toolbar, which enlarges the output window

The contents of the output window may be stored, edited, redirected, etc., using the following icons:
Opens an editor and pastes any selected or complete text from the output window Opens a different output file Either saves the selected text to an ASCII file, or the complete contents of the output window if no selection was made Copies the selected text to the Windows Clipboard for use in other programs Clears the output window by deleting all messages Searches the text in the output window for the occurrences of a given text. A "?'' wild cart may be used Changes the font used in the output window Redirects everything to a file on disk. The output window will stop displaying messages while this icon is down Acts like "redirect to disk", but all messages will now be printed directly Pre-sets the option for the print dialogue. Either chooses printing of the selected text or all buffered text if no selection was made

Using the Output Window Context Sensitive Menu inside the Output Window Output Window Legend Copying from the output window
Using the Output Window

The output window is more than just a dumb message viewer. It is an interactive tool, which helps in preparing your data for calculations and it improves any search for errors or bugs in your projects. Every line in the output window with a full folder and object name can be double-clicked with the left mouse button. This will open the appropriate edit dialogue for the shown object. See the example in Figure 4.10.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 13 of 47

Fig. 4.10: The interactive output window

In this example, a calculation function reported an error because a transformer element has not been assigned a transformer type. Double-clicking the error message opens the edit dialogue of the transformer.
Context Sensitive Menu inside the Output Window

It is also possible to press the right mouse button while pointing at the object name. The context sensitive menu will pop-up and show entries to easily find and edit objects, if the printed object name was found to be an existing object in the database tree. These option are
Edit Object will open the edit dialogue of the printed object, which is i.e. the reason for the error message Edit and Browse Object will open the data manager and show the element and its parameters there. Mark in Graphic will mark the clicked element in the single line diagram and zoom into the region of its place. The interactive feature of the output window is extremely convenient when 'debugging' a new or changed power system design. Faulty elements don't have to be searched for in order to correct their parameters. Output Window Legend

The output window uses colors and other formatting to distinguish between different types of messages or for specials like bar diagrams. Text messages formats:
DIgSI/err - ... Error messages. Format: red colored. DIgSI/info - .... Information messages. Format: green colored. DIgSI/wrng - ... Warning message. Format: brown colored. DIgSI/pcl - ...' Protocol message. Format: blue colored. Text only Output text. Format: black colored.

Reports of calculation results may contain bar graph information. The "voltage profiles'' report after a load-flow command, for instance, produces bar graphs of the per-unit voltages of busbars. These bars will be colored blue, green or red if the "Verification'' option in the load-flow command dialogue has been enabled. They will be hatch-crossed if the bars are too large to display. An part of a bar graph output is shown in Figure 4.11. The following formatting is visible:

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 14 of 47

Fig. 4.11: Output window bar diagram Green Solid Bar Used when the value is in the tolerated range. Blue Solid Bar Used when the value is too low. Red Solid Bar Used when the value is too high Hatch-crossed Bar Used when the value is out of reach and cannot be displayed correctly. Copying from the output window

The contents of the output window, or parts of its contents, may be copied to the build-in editor of PowerFactory or to any other program. Normally, not all selected lines will be copied and the format of the copied text may undergo changes. The latter is caused by the fact that the PowerFactory output window uses special formatting 'escape sequences'. Other programs may not be capable of dealing with these formatting commands.

Fig. 4.12: The output window Info Message

Which lines will be copied is determined by the output window settings. See Section 6.4 for more information. When text from the output window is about to be copied, an info message will pop up, informing the user about the current settings. See Figure 4.12. A button is supplied which brings the user directly to the user settings dialogue. The info message may be disabled, in which case it will never show up again.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

4.6 Getting Help


The PowerFactory software comes with a number of help facilities:
1. 2. 3. 4. The licensed version comes with a printed hard copy of the Users Manual and the Getting Started Tutorial. An on-line version of the Users Manual and the Getting Started Tutorial, which can be opened from the Help option on the main menu (see Figure 4.5). A context sensitive help which will directly jump to the right page of the on-line Users Manual when the F1 key is pressed. Balloon help which will give the names of command icons, or input parameters, if the cursor is positioned over these items and held still for about half a second. The graphical elements for which balloon help is provided are:

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 15 of 47

5. 6.

1. Buttons/icons (available for all command icons). Class-icons. Parameter fields.

Command buttons/icons are sometimes referenced by their name, instead of by their image. For large buttons, this is normally the case. The name of a button is either the name on the button itself (OK, Cancel), or the name that appears in the balloon help (e. g. = User Settings).

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

Chapter 5 Program Setting, Logging on and User Accounts


This chapter provides reference information on how to configure the program, how to log on and how to create and manage user Accounts. More Detailed descriptions of the process introduced here can be found in the PowerFactory Installation Manual.
Program Configurations and Settings The Log-on Dialogue User Accounts and User Groups

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.1 Program Configurations and Settings


In general there are 3 main questions to be answered before installing the software, the answers to these questions will determine the installation settings:
License: Where should the license key(s) reside? Installation: Where should PowerFactory be installed? Database: Where should the database reside?

Once PF has been set up in a computer, the installation setting is carried out by means of a 'Log-on' dialogue. This dialogue pops up automatically when the program is opened for the first time. Through the Licence, Network and Database tabs of the Log-on dialogue, the answers to the questions above are provided and the program installation is configured. A detailed description of the installation procedure and the program configuration alternatives is given in the PowerFactory Installation Manual. The next section provides reference information about the Log-on dialog.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.2 The Log-on Dialogue


The application of PowerFactory is carried out within a user session. Since an account system is used, it is necessary to log on when starting a session. Immediately after opening the program a 'Log-on' dialogue is presented, there the user must specify his/her credentials. As indicated in Section 5.1 the Log-on dialogue also serves as interface to the program settings. To start a session, the user must always provide the corresponding name and password (credentials). Unless they have changed, the installations settings do not need to be update every time a session starts. In the next subsections a description of the fields presented in the log-on dialogue is given.
Note: A user account is the working space of a specific user (the account owner) within the DB. It is the object where the user stores his projects and settings. To access a specific account the corresponding user name and password must be given. Information on the account management system and how to share information with other users is given in Chapter 21 Data Management . The description on how data is arranged within PF is given in Chapter 7 The PowerFactory Data Model .

Log On Configuration License Settings Network Settings Database Configuration Advanced Settings Appearance Settings

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 16 of 47

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.2.1 Log On Configuration

Fig. 5.1: The Log-on Dialogue, User Credentials

Once the PF installation had been set, a name and a password must be given in order to access an account and start to use the program. Two special accounts are created when installing PF, the Demo and the Administrator. The Demo account is used to access and run the examples provided with the program. The administrator (database administrator) account is used to create and manage user's accounts in a multi-user environment (see Section 5.3). To log on as Demo, just select the corresponding option on the users name drop down menu (Figure 5.1), no password is required. To log on as administrator, select the Administrator name from the menu and use the assigned password. By default the administrator account password is Administrator. Users other than the Administrator and the Demo, require their own name and password to log on. If you are using a stand alone installation, you can create a new user account by typing in a new name and a password of your choice (an empty password is also accepted). After creating the new account the 'Do you really want to create a new user account' message will pop up, click Ok to continue. In a multi-user installation (see Section 5.3) new accounts and passwords are created by the administrator. For further information about the roll of the database administrator please refer to Section 5.3.2. Further information about the Demo account is given in Section 5.3.5.
Note To run the prepared examples please log on as Demo user. This user requires no password and you have the possibility to use the demo projects with the full functionality of PowerFactory.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.2.2 License Settings

Fig. 5.2: Log-on Dialogue License Settings

In order to run the program, users require access to a license key (also known as dongle or hardlock). By means of the interface described below (License tab of the Log-on dialogue), this access is defined.
License Key

In the License Key field, the installed license key setting must be selected. PowerFactory offers four choices to install the license key:
not available (Demo) No local key is installed, only Demo version of PowerFactory can be run. on local port A valid PowerFactory license key ('hardlock') must be connected to a USB or parallel port.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 17 of 47

in network (file based communication) A connection to a network computer, which has the PowerFactory network license service running must be available. The communication between the user and the license server is done trough shared directories. in network (protocol based communication) A connection to a network computer, which has the PowerFactory network license service running must be available. The communication between the user and the license server is done trough a protocol.

A detailed description of the different license key settings is given in the PowerFactory Installation Manual. Demo users (those without licence) should select 'not available (Demo)'.
Serial Number

Your serial number must be provided in the 'Serial Number' field. It can be found on the page 2 of the license agreement.
License Server

If the you are using a network key with file based communication, the path to the PowerFactory working directory of license server must be provided. This path is usually mapped on the client machine. If you are working with a protocol based communication key, you are required to specify the computer name or the IP network address (as in Figure 5.2) of the license server.
Advanced RPC-Settings

If a network license key with protocol based communication is used, the 'Advanced RPC-Settings' must be given. To reach these fields, press the arrow button ( ) on the first page of the License tab.

The 'RPC' settings must be the ones specified in the license server. For detailed information consult your network management or see Section 3.2.3 of the PowerFactory Installation Manual.
NOTE: If you are not sure about your license key setting please refer to your network administrator. File based communication is only recommended for old versions of PowerFactory that don't support protocol based. For further information on the license key configuration refer to the Installation Manual.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.2.3 Network Settings


The PowerFactory installation directory contains the application's binaries; the working directory contains some temporary data, an error log file and the local database. In the 'Network' tab of the Log-on dialogue, the location of the PowerFactory installation and working directories is defined. Depending on that location three installation types are available:
on local machine Locally installed on individual computers. on file server Only the working directory of each client resides on the local hard disk. on an application server (e.g. Terminal Server) The installation and working directories reside on a server.

A detailed description of the different installation methods is given in the PowerFactory Installation Manual.
Note: If you are not sure about your installation type please refer to your network administrator. For detailed information about the installation types see the installation manual Chapter 5.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.2.4 Database Configuration


In this tab it is specified how the database is going to be used. You can select among:
A single-user database which resides locally on each computer. A multi-user database which resides on an remote server. Here all users have access to the same data simultaneously. In this case user accounts are created and administrated exclusively by the Administrator.

DIgSILENT PowerFactory provides drivers for the following multi-user database systems:
Oracle. Microsoft SQL Server.

For further information about the database configuration please refer to the PowerFactory Installation Manual.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 18 of 47

Fax: +49 (0)7072 9168-88 support@digsilent.de

5.2.5 Advanced Settings


The advanced program settings should only be changed under the guidance of the DIgSILENT PowerFactory support at support@digsilent.de.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.2.6 Appearance Settings


The appearance settings influence the way in which the toolbar buttons are displayed and the way in which dialogues will open, close or move scroll bars and other objects. These settings may be changed to suit the users personal taste.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.3 User Accounts and User Groups


The user account philosophy of PowerFactory basically works in the same way as is usual for larger computer systems. The first objectives of the user account managing system are:
To protect the 'system' parts of the database from changes by normal users. To protect the part of the databases which belongs to user ''A'' from being changed by user ''B''. To allow users to share data.

The user account managing system provides each user with his/her 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 some of his/her 'private' data. The user account managing system manages this whilst using only one single database in the background, which allows for simple backup and management of the overall database. PowerFactory Database Overview The Database Administrator Creating and Managing User Accounts Creating User Groups The Demo Account

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.3.1 PowerFactory Database Overview


A brief introduction to the top level structure of the PowerFactory database is convenient before presenting 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 customizing for user groups, user default settings, project templates and class templates for objects 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 the project folders and all other folders in which the normal user defines her/his power systems and all accompanying objects and settings. Project folders are the housing for the data model that allows the definition and analysis of a power system: Chapter 7 The PowerFactory Data Model is dedicated to them.

The top level structure described above can be seen in the Data Manager's screen shot from Figure 5.3.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 19 of 47

Fig. 5.3: Basic database structure

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.3.2 The Database Administrator


A database administrator account is created with the PowerFactory installation. The main functions of the administrator are:
Creation and management of user accounts. System database maintenance under the guidance of the DIgSILENT customer support.

Under a multiuser database environment, the administrator is the only user with the rigth to:
Add and delete users. Define users groups. Set individual user rights. Restrict or allow calculation functions. Set/reset user passwords.

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 rigth to perform any calculation. To log on as administrator, select the 'Administrator' user from the drop down menu of the 'Log on' page from the Log-on dialogue and write the corresponding password. By default the administrator password is Administrator. For further information about the administrator roll, please refer to the PowerFactory Installation Manual (Chapter 6).

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.3.3 Creating and Managing User Accounts


In the case of an installation with a local database, the simplest way to create a new user account is to enter an unknown account name and an arbitrary password in the Log-on dialogue (see Section 5.2.1). In this case the program will automatically create and activate the new account, without administrator intervention. 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. To create a new user:
Log on as administrator. In the left pane of the Data Manager click on Configuration folder to display its contents. Double click on the User Manager icon ( , rigth pane) and press the Add User... button.

The User edit dialogue will pop up:


In the 'General' tab, 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 dialogue will pop up.

Any user can edit her/his own account by means of the User edit dialogue. 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).

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 20 of 47

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.3.4 Creating User Groups


Any project or folder in a user account may be shared. This action can 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( In the User manager dialogue that pops up press Add Group..... Enter the name of the new group, optionally a description and press Ok. 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 dialogue (rigth clicking on it and selecting Edit from the context sensitive menu). Via the context sensitive menu, groups can also be deleted. The administrator can add users to a group by:
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.

The last action is carried out by: Right-clicking the user group and selecting Paste Shortcut from the context sensitive menu. Users are taken out of a group by deleting their shortcut from the corresponding group. For information about sharing projects please refer to Chapter 21 Data Management .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

5.3.5 The Demo Account


The demo account is special user account for demonstration or testing purposes. Like the administrator account it is automatically created with the program installation. The demo account folder is filled with numerous demonstration projects. These projects are accompanied by demonstration command scripts which can automatically activate a demo project and perform commands such as load-flow, short-circuit or transient analysis. Execution of these command scripts is started by selecting a demonstration from the main menu option File > Examples. This menu option has several sub-menus from which a demonstration may be selected. Selecting a demonstration will start the appropriate command script.
Note: The menu option File > Examples is only available when one is logged into the Demo account.

The ''Demo'' projects may also be activated and observed in the manner normally employed by PowerFactory. To learn how this is achieved it is best to work through the on-line tutorial that is provided. A demo user has read and write permissions for all demonstration projects. However, calculations will only be permitted for the demonstration networks as long as they have not been changed in a topological sense. This means that adding or deleting lines, transformers, loads, machines, etc., will lead to error messages. Licensed users may log on as demo users, change the demonstration projects in any way, and still be able to start a calculation (as long as their hardlock is available to PowerFactory). However licensed users are recommended to copy and paste into their own account the ''Demo'' projects of their interest. As long as a user does not make any topological changes, these demonstration projects may be used to experiment with PowerFactory. Such experimentation may include:
Changing and executing commands such as load-flow, short-circuit or transient analysis. Changing power system elements such as selecting other line types, changing generator settings, etc. Creating new calculation cases Changing the appearance of the single line graphics except for adding or deleting power system elements. Creating or changing virtual instruments panels such as defining graphs or changing bar diagrams.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

Chapter 6 User Settings


The User Settings dialogue, shown in Figure 6.1, offers options for many global features of PowerFactory. This chapter is dedicated to describe this options. The User settings dialogue may be opened either by clicking the User Settings icon ( ) on

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 21 of 47

the main tool bar, or by selecting the Options > User Settings... menu item from the main menu.
General Settings Graphic Windows Settings Data Manager Settings Output Window Settings Functions Settings Directories Editor

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

6.1 General Settings

Fig. 6.1: User Settings dialogue

The general settings include (Figure 6.1):


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

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

6.2 Graphic Windows Settings

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 22 of 47

The graphic windows has the following settings. Cursor settings General Options Coordinate Output at statusbar in mm Update Hidden pages always Exclude Feeder Colors Update Graphic while Simulation is running Use own background color for single line graphics Allow Resizing of branch objects Edit Mode Cursor Set Mark Objects in Region Show balloon Help
Cursor settings Defines the cursor shape: Arrow A normal, arrow shaped cursor. Crosshair A large, full screen cross. Tracking cross A small cross. General Options

Valid for all graphs:


Show Grid only if stepsize will be least Grid points smaller than the selected size will not be shown. Show Text only if height will be least Text smaller than the selected size will not be shown. No. of columns in graphics floater Specifies the width of the graphics toolbar when this is a floating window. No. of columns in graphics docker Specifies the width of the graphics toolbar when it is docked on the right side of the drawing space. Line factor when printing The width of all lines in the graphics will be multiplied by the specified percentage when printing. Coordinate Output at statusbar in mm

Specifies that the status bar will display the cursor position in millimeters.
Update Hidden pages always

Results in all graphical pages on a graphics board being updated, even when they are not visible. Note that this can slow the processing speed considerably. The advantage is that no updating is required when a different graphics page is selected.
Exclude Feeder Colors

May be used to exclude colors, by number code, which are to be used for feeder definitions. This is used to prevent the use of colors which are already used for other purposes. Ranges of color numbers are entered as '2-9'. Multiple ranges of colors must separated by commas, as in '2-9;16-23'.
Update Graphic while Simulation is running Use own background color for single line graphics

If the option is enabled, the user can define the background color of the single line graphics by using the pop up menu and then pressing OK.
By pressing the ( )button more graphic setting options are available:

Allow Resizing of branch objects

If the option is enabled, the user can left click a branch element within the single line graphic and then resize it.
Edit Mode Cursor Set

Allows the selection of the mouse pointer shape.


Mark Objects in Region

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. Show balloon Help

Enables or disables the balloon help dialogues. For information about the Graphic Window refer to Chapter 10 The Graphics Editor .

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 23 of 47

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

6.3 Data Manager Settings


The data manager tab specifies which object types will be displayed or hidden in the tree representation, and whether confirmation prompts will appear when objects or data is changed in the data manager itself. Show in Treelist Browser Operation Scenario Export/Import Data Folders for Global Library
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

Configures the export and import of PowerFactory 'DZ'-files, as follows:


Binary Data Saves 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. Folders for Global Library

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 Power Factory Database Manager refer to Chapter 11 The Data Manager .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

6.4 Output Window Settings


The output window settings control the way in which messages selected by the user, in the output window are to be copied for pasting into other programs. Whichever options are checked will determine what will be copied. The text in the output window itself will not be influenced. Escape sequences are special hidden codes which are used for coloring 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.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

6.5 Functions Settings


The functions settings page provides check boxes for the function modules that are accessible from the data manager or from the object edit dialogues. The user may choose to see only certain modules in order to ''unclutter'' dialogues. This may also be used to protect data by allowing only certain calculation functionality to be seen by certain users. This is particularly useful in a multi-user environment or in when inexperienced users utilize PowerFactory.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 24 of 47

support@digsilent.de

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

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

6.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 Tabs Language coloring ShortCuts
Options Enable Virtual Space Allows the cursor to move into empty areas. Enable Auto Indent Automatically indents the next line. Enable Backspace at Start of Line Will not stop the backspace at the left-most position, but will continue at the end of the previous line. View blanks and tabs Shows these spaces. Show Selection Margin Provides a column on the left side where bookmarks and other markings are shown. Show line Numbers Shows line numbers. Tab Size Defines the width of a single tab. Tabs

Toggles between the use of standard tabs, or to insert spaces when the tab-key is used.
Language coloring

Defines the syntax-highlighting used when the type of text is not known.
ShortCuts

Opens the short-cut definition dialogue.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

6.8 Station Ware


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.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 25 of 47

Chapter 7 The PowerFactory Data Model


Up to this point, information regarding the general structure of the database, the user interfaces and the administration of users' accounts has been given. Now it is time to describe how the data is organized to model and analyze a power system. The set of folders and objects hierarchically organized to model and perform calculations on a power system will be referred to here as the data model.
Database, Objects and Classes PowerFactory Project Structure The Network Model The Equipment Type Library The Operational Library The Templates Library Parameter Characteristics and Parametric Studies DIgSILENT Programming Language (DPL) Scripts

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.1 Database, Objects and Classes


As explained in Chapter 4 PowerFactory Overview , PowerFactory uses a hierarchical, object-oriented database. All the data, which represents power system elements, single line diagrams, study cases, system operation scenarios, calculation commands, program settings etc., are stored as objects inside a hierarchical set of folders. The folders are arranged in order to facilitate the definition of the studies and optimize the use of the tools provided by the program. The objects are grouped according to the kind of element that they represent. These groups are known as classes within the PowerFactory environment. For example, an object that represents a synchronous generator in a power system belongs to the class defined for synchronous machines (called ElmSym in PowerFactory); whereas an object storing the settings for a load flow calculation belongs to a class defined to set and execute load flows (called ComLdf), and so on. Analogous to Windows, classes may be seen as the file extensions of the objects. Each object belongs to a class and each class has a specific set of parameters that defines the objects which it represents. As explained in Section 4.5 User Interface , the edit dialogues are the interfaces between the user and an object; the parameters defining the object are accessed through this dialogue. This means that there is an edit dialogue for each class of objects. This information may seem somewhat academic to the user at first, as PowerFactory will assign objects automatically. However it is useful for the reader to have some understanding of this arrangement before the data model and its management tools are described. The PowerFactory database philosophy can thus be summarized by one 'golden' rule:

'Everything is an object, all the objects belong to a class and are stored according to a hierarchical arrangement in the database tree'
The following sections describe the arrangement of folders in the database and the objects that are used to represent and analyze power systems with PowerFactory.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.2 PowerFactory Project Structure


Projects are used in PowerFactory to manage the studies of power systems. They include all of the networks for analysis with their corresponding variations and graphics, the definitions of the calculations performed, the results, etc. When defining and studying a system, the user always works on an active project, creating/modifying networks, performing calculations or analyzing results. From a database point of view, a project is a directory which stores:
All the objects that collectively define a power system and its changes over time. Objects that the define the graphical representations of the system. Objects that define the calculations performed on the system. Objects that contain the results of the calculations.

The objects mentioned above are stored in folders according to their functionality. These folders are hierarchically arranged within the project in order to facilitate the definition of the studies and optimize the use of the tools provided by the program. To understand the structure of the 'project folder' it is useful to examine which kind of information is represented by the data and what it is used for. This will lead us to PowerFactory's data model, which is organized in folders as illustrated in Figure 7.1. In PowerFactory Version 14, all changes in the projects are tracked: the date (day and time) of each change and the user who made the change are stored inside the database.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 26 of 47

Fig. 7.1: Data Arrangement Inside a Project (Default Structure of a Project Folder)

The default project structure (the data model described above) is shown in Figure 7.1. The remaining sections of this chapter deal with the description of the objects/folders shown above. For information on how to create and configure a new project please refer to Section 9.1 Defining and Configuring a Project .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.2.1 The Library


The library contains the equipment types (as in older versions of PowerFactory), special operational information, DPL scripts, templates and user-defined models. To make the library simple to navigate, PowerFactory Version 14 stores equipment types in a special subfolder called Equipment Type Library.
Equipment Type Library It is convenient to store all manufacturer-specific data in the same location and organize it in such a way that it can be easily accessed when defining power system elements. Within the data model this information corresponds to the above mentioned type data and is stored inside the Equipment Type Library folder. An equipment type object holds the essential electrical information for each class of network component. This information is usually provided in manufacturers' data sheets. Within the project structure, the type objects are stored inside the Equipment Type Library. Type objects may be sorted by class using library subfolders, i.e. a subfolder for generator types, a subfolder for line types etc. Operational Library It is often desired to change the operation point of a network in order to analyze the effects of different loading levels, changed maintenance schedules or operational limits. An Operational Library folder, which contains sorted operational alternatives, is part of the approach used by PowerFactory to manage this task.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 27 of 47

Fig. 7.2: The Operational Library To create a new element in one of these folders, first select the folder by clicking once on it. Then press the `New Object' button ( select the desired element. ), and

The network may need to be analyzed at different times of the day, week or year, where changed load conditions and different component ratings are considered. As described above, Operational Library objects and Operation Scenarios facilitate this analysis by allowing the definition of different operational data. The Parameter Characteristics tool is designed to extend this flexibility of analysis via the use of characteristics. Characteristics are defined by a range of values, as opposed to a single fixed value, which are assigned to the parameters of selected power systems elements. Within this range, the selection of the appropriate value for the parameter is carried out according to a user-defined trigger. For example, the active power demand of a load can be modeled by means of a characteristic with 12 values, each one corresponding to a month of the year. If the trigger is set to January (triggers are user-defined), then the value used by the program to perform the calculations will be the first value of the characteristic; if the trigger is set to December, the last value of the characteristic will be used. Additional objects which support the calculations and the modeling of the system are also stored inside the Library folder. These objects include: automation commands developed with the DIgSILENT Programming Language (DPL) and user-defined templates for composite network elements.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.2.2 The Network Model


It would be convenient to have simultaneous access to all electrical and graphical data relating to the network to be analyzed (i.e. all objects that define the analyzed system and its graphical representation). This is achieved by storing all network data in the Network Model folder. The Network Model contains the electrical and graphical information for the grid. To further enhance manageability, this information is split into two subfolders: Diagrams and Network Data. An additional subfolder, Variations, contains all expansion stages for planning purposes. Together with Operation Scenarios (see Section 7.2.3) the concept of Variations takes place of the earlier system stage concept in PowerFactory.
Network Data The electrical data may be sorted according to logical, organizational and/or geographical areas; therefore within any project, one or more Grid objects may be defined. All Grids are by default contained within the Network Data folder. Diagrams When drawing a grid, all graphic information is automatically stored in this folder. Variations In order to plan or assess the network under different topological configurations, it is useful to be able to create variations of the current network. These variations are linked to the original network data, so that changes made to the original network are automatically transferred to the variation. Additionally, these variations should be placed in a time frame, in order to allow scheduled expansion plans. PowerFactory uses objects called Expansion Stages to model these time-dependant variations. Expansion stages are stored inside Variation objects. Variations can be seen as expansion plans composed of different expansion stages, which are chronologically activated. Variations, like all other network data, are stored inside the Network Model folder. Expansion Stages (of an active Variation) are activated automatically by PowerFactory, if you set the date and time of the calculation case to a value, which is equal to or higher than the Activation Time of the expansion stage. The concepts of Variations and Expansion Stages are complemented by Operation Scenarios, which are stored on the same hierarchical level as the network model, because these scenarios don't model the grid itself, only its operation.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.2.3 Operation Scenarios


Storing recurrent operation points and being able to activate or deactivate them when required, accelerates the analyses of the network under different operative conditions, e.g. different dispatch programs, low or high load periods, etc. PowerFactory can store complete operation points in objects called operation scenarios. This kind of data, which is subject to frequent changes during a study and may be used to simulate different operation scenarios of the same network, is further grouped into subsets. Within the project folder, operation scenarios are stored inside the Operation Scenarios folder.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 28 of 47

Fig. 7.3: Operation Scenarios

We may need to analyze the network at different times during the day, week or year, where changed loading conditions and different component ratings are considered. As described above, Operational Library objects and Operation Scenarios facilitate this feature by allowing the definition of different operation points. Scenarios facilitate this analysis by allowing the definition of different operational data. The Parameter Characteristics tool is designed to extend this flexibility of analysis via the use of characteristics. Characteristics are defined by a range of values, as opposed to a single fixed value, which are assigned to the parameters of selected power systems elements. Within this range, the selection of the appropriate value for the parameter is carried out according to a user-defined trigger. For example, the active power demand of a load can be modeled by means of a characteristic with 12 values, each one corresponding to a month of the year. If the trigger is set to January (triggers are userdefined), then the value used by the program to perform the calculations will be the first value of the characteristic; if the trigger is set to December, the last value of the characteristic will be used.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.2.4 Study Cases


Once the network data has been entered and configured, users may wish to perform network studies, including load-flow, various short-circuits, time-dependant simulations, etc. It would be useful if the results of these studies could also be stored for review or repeated later. The concept of the Study Case is the same as it was in previous versions of PowerFactory. In PowerFactory Version 14 all study cases are stored inside a folder called Study Cases.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.2.5 Changed Settings


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

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.3 The Network Model


As introduced in Section 7.2.2, the Network Model folder contains the all graphical and electrical data which defines the networks and the single line diagrams of the power system under study. This set of data is referred as the network data model. The following folders are defined inside the Network Model folder:
Network Diagrams ( ) Contains all objects pertaining to graphical information (single line diagrams) from the networks defined in the project. Network Data ( ) Contains all network components of the power system: generators, busbars, transformers, lines, switches, controller models, etc. These network components are stored in this folder, in accordance with PowerFactory's handling of network topologies (7.3.2 Network Topology Handling ) ) This folder, as introduced in Section 7.2.2, contains the objects which represent variations of the defined networks, such as topological changes, installation or retirement of network components, etc. Time stamps of these variations can be set in order to make the variations time-dependant.

Variations (

The following subsections describe how the network data model is organized in these folders. Before any explanation of the Network Data folder is given, a subsection explaining PowerFactory's handling of network topology is presented. For an improved understanding of the following subsections, the key concepts related to the modeling of electric power systems with PowerFactory are recapped:
Data model: The hierarchical set of objects from the database which are used to model and analyze a power system. All objects which comprise the data model are stored in the project folder.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 29 of 47

Network data model: The hierarchical subset of objects, within the data model, which are used to represent and model the electrical networks of the power system under analysis. Most objects from the network data model correspond to: electrical network components; graphical representations of the electrical components and sets of electrical components, grouped for analysis purposes. The objects comprising the network data model are stored inside the Network Model folder, within the Project folder. Network topology handling: The approach used by the data model to represent and connect the nodes and branches of real networks. This is achieved using by single electrical network components and sets of them. Electrical network components (or simply network components or elements): Are the objects used to represent real network elements, i.e. generators, switches, lines, etc. Each of these objects contains a model that DIgSILENT has developed to reproduce the static and dynamic behavior of the represented element. The theoretical information about the models and the relation among their parameters are given in the corresponding technical reference documents, which are attached to the sections of Appendix C and D. Like all objects in PowerFactory, components can be identified by their class, for example ElmLod (for loads), ElmLne (for transmission lines), etc. Each element class has a symbol that helps to distinguish it within the database, for example the symbol used to represent a load is ( ), and that used to represent a transmission line is ( ).

Network Diagrams Network Topology Handling Network Data Variations and Expansion Stages

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.3.1 Network Diagrams


Single line diagrams 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 (see database tree in Figure 7.4). Single line diagrams are composed of graphical objects, which represent components of the networks under study. Each graphical object is related (by means of a reference) to the network component that it is representing; additionally it uses a reference to a symbol object (IntSym, Appendix E), which defines its graphical appearance. Figure 7.4 illustrates the information given above. It shows the Network Diagrams folder of a project, containing two single line graphics: North Grid and South Grid. The content of North Grid (graphical objects related to network components) is displayed in the right pane of the Data Manager.

Fig. 7.4: Network Diagrams

The relation between graphical objects and network components allows the definition and modification of the studied networks directly from the single line diagrams. In addition to this, the network components can be represented by more than one graphical object (manyIntGrf objects can refer to the same network component). Therefore, one component can appear in several diagrams. Thanks to the relation described above, several diagrams for one network can be defined. Diagrams displaying components from different networks are also possible. 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, every time the study case is activated, the diagram is automatically opened. As with any other object, diagrams can be added/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 that s/he wants to display. References to the selected diagrams are then automatically created in the corresponding Graphics Board. Chapter 10 The Graphics Editor , explains how to define and work with single line graphics. Additional information about the relation between graphical objects and network components is given below in Section 7.3.2 Network Topology Handling . For further information about symbols and the appearance of graphical objects, please refer to Appendix E Reference to the use of Symbols in PowerFactory . Single Line Graphics and Data Objects
Single Line Graphics and Data Objects

In a simple network there may be a 1:1 relationship between data objects and their graphical representations, i.e. every load, generator, terminal and line is represented once in the graphic. However, in this regard, PowerFactory provides additional flexibility Data objects may be represented graphically on more than one graphic, but only once per individual graphic. Thus a data

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 30 of 47

object for a single terminal can be represented graphically on two or more graphics. Both graphical representations contain the link to the same network component (i.e. the terminal element). Furthermore, graphical symbols may be moved without losing the link to the data object (network component) that they represent. Likewise, data objects may be moved without affecting the graphic. The graphics themselves are saved in the database tree. This makes finding the correct single line graphic representation of a particular grid easy, even in the case where there are several graphical representations of one grid. When PowerFactory's drawing tools are used to place a new component (i.e. a line, transformer, bar graph, etc.) a new data object is also created in the database tree (in a target Grid folder). A Single Line Graphic object therefore has a reference to a target Grid folder. The new data objects are stored in the 'target' folders that the graphics page is associated with. Since data objects may have more than one graphical 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 (context sensitive 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 calculation. This is indeed what will occur, when this kind of graphical deletion is performed. When an element is deleted completely (context sensitive menu --> Delete Element) a warning message will request confirmation of the deletion. This warning may be switched off - see User Settings on the main menu, General tab, and untick Always confirm deletion of Grid Data).
Note: A graphical object represents an electrical element from the database but is not the element itself. PowerFactory allows the generation of single line graphics containing any of the defined graphical objects. Therefore single line graphics containing objects not necessarily stored in the same grid or substation can be created.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.3.2 Network Topology Handling


Network components can be classified as node elements or branch elements. Branch elements can be further separated single connection elements (generators, motors, loads, etc.), two connections elements (transmission lines, transformers, etc.) and three connections elements (three winding transformers, AC/DC converters with two DC terminals, etc.). Simple networks are easily modeled in PowerFactory by defining and connecting nodes and branch elements. For larger networks, in order to achieve a more realistic representation and facilitate their analysis, basic components may need to be grouped into higher-level hierarchical objects to represent electrical substations and composite branches (for example). Furthermore, substations, branches and any other network component can be grouped within Site objects to represent geographical areas of a system. The following subsections provide further information regarding the PowerFactory representation of network topological components. Nodes Branch Elements Substations Branches Sites
Nodes

In circuit theory, the junction points connecting lines, generators, loads, etc. to the network are generally termed `nodes'. In PowerFactory, nodes are modeled by means of objects called 'terminals' (ElmTerm). Depending on their usage within the power system, terminals can represent busbars, junctions or simply internal nodes (their usage is defined by a drop down menu found in the Basic Data tab of the terminal dialogue). According to the selected usage, different calculation functions are enabled; for example the short-circuit calculation can be performed only for busbars or for busbars and internal nodes, and so on. When any branch element is directly connected to a terminal, PowerFactory uses a 'cubicle' (StaCubic) to define the connection. Cubicles may be visualized as the panels on a switchgear board, or bays in a high voltage yard, to which the branch elements are connected. Normally a cubicle is created automatically when an element is connected to a node. In this case the switch configuration of the new cubicles has been previously defined by the user and is carried out using simple switches of class StaSwitch (for further information about defining cubicles refer to Section 11.2: Defining Network Models with the Data Manager).

PowerFactory also offers the possibility to create more detailed cubicle connections (in order to model complex busbar-substation configurations) by using switches of class ElmCoup, whose usage can be set to circuit breaker, disconnector, switch disconnector or load switch. In this case the branch elements are connected to the terminals (busbars) through ElmCoup objects. The connection of an ElmCoup to a terminal is carried out by means of automatically generated cubicles without any additional switch (StaSwitch) object.
For further information regarding how to connect nodes with branch elements using circuit breakers (ElmCoup objects) please refer to Section 11.2 Defining Network Models with the Data Manager .
Note: The use of ElmCoup objects also allows the representation of complex busbar systems by connecting several terminals together. Additionally they allow the application of running arrangements (7.5.6: Running Arrangements).
Branch Elements

As explained earlier, branch elements are connected to nodes via cubicles. A connection between two nodes is made by two-port elements like transformers, switches or lines. Three-port elements require a connection to three different nodes.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 31 of 47

Generally, branch elements are single components whose connection to the network is automatically set when selecting the connected terminals. From the data model point of view, the case of transmission lines (and cables) is interesting, because they can be defined as a one-to-one connection between two nodes, or as folders containing line sections that together connect two nodes. The purpose of sectionalizing the line into parts is so that different line types may be used for the different sections (such as when a cable connecting two nodes uses different types in different sections, or when a line uses two or more different tower types, or when manual transpositions should be modeled - since the Transposed option in the type object is a perfect, balanced, transposition). For information about how to define transmission lines (and cables) and sections please refer to Section 10.1 Defining Network Models with the Graphical Editor . For technical information about the transmission line and cable model, please refer to Appendix C.10 Line (ElmLne) .
Substations

Detailed representations of electrical substations can be achieved in PowerFactory by connecting and storing terminals and switches together, under one 'Substation' object (ElmSubstat ). Substations can also be used to model composite busbar systems, by storing terminal and switch arrangements under the same object. Separate single line diagrams of individual substations can be created. Substation objects allow the use of running arrangements to store/set a certain status of the station circuit breakers (ElmCoup objects) (see 7.5.6: Running Arrangements). For information about how to define substations please refer to Section 10.1 Defining Network Models with the Graphical Editor and 11.2 Defining Network Models with the Data Manager .
Branches

Similar to substations, PowerFactory allows nodes and branch elements to be stored under the same object (the branch object, ElmBranch ) in order to represent branched-off connections between two terminals or substations. Branches are 'composite' two-port elements that may be connected at each end to a node. One typical application is a distribution line with branched-off loads along the connection: transmission lines, loads and the corresponding terminals can be stored together under the same branch, and the two ends of the line correspond to the branch connections with the grid. As in the case of substations, separate single line graphics for branches can be created with the graphical editor. For information about how to define branches please refer to Section 10.1 Defining Network Models with the Graphical Editor and 11.2 Defining Network Models with the Data Manager .
Sites

Substations, branches and any other network component can be stored together under the same 'Site' object in order to represent and analyze a network according to its geographical (topological) regions. Sites are high-level hierarchical objects that can store any defined component within a network. For information about how to define sites please refer to Section 11.2 Defining Network Models with the Data Manager .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.3.3 Network Data


The Network Data folder contains all components which make up the electrical networks of the power system being analyzed. As introduced in Section 7.2, the electrical data may be sorted according to logical or organizational and/or geographical areas. Consequently different networks may arise. These networks are made up of electrical components which conform to the PowerFactory topology handling approach (explained in the previous section). In PowerFactory, electrical networks (as defined above) are 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. An example of this approach is the Tutorial project provided with the Getting Started Manual. In this project, a distribution network and a transmission network are created and analyzed separately. At a later stage both networks are connected and the analysis of the complete system is carried out. Figure 7.5 shows a network model with two grids: North and South. Both networks are active (red-colored icons). The left pane in the Data Manager shows the hierarchical organization of the components in the North grid (only objects containing other elements are shown). The right pane shows the contents of highest hierarchical level of the North Grid.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 32 of 47

Fig. 7.5: Network Data - Grid folders

Additionally to grids, the Network Data folder contains a set of special objects that allow the further grouping of network components. This additional grouping of elements is carried out in order to allow further analysis and calculations of the power system. By default, when a new project is created, new empty folders to store these special objects are created inside the Network Model folder. The left pane shown in Figure 7.6 illustrates the complete structure of the Network Data folder from the example shown in Figure 7.5. Besides the two defined grids (North and South), folders to store the grouping objects are created. The user can define any of the corresponding grouping objects inside each of these folders. The right pane shown in Figure 7.6 shows the contents of the 'Feeders' subfolder, which contains a 'Feeder' object named F1.

Fig. 7.6: The Network Data folder

Descriptions of the above mentioned grouping objects and a component's parameter characteristics is given in the following subsections. The user can define any of these additional grouping objects via the use of references to relevant network components stored in the grid folders. For information about defining grids please refer to Section 9.2 Creating New Grids .
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. An active object can be distinguished in the data manager because of the red color seen on its icon.

Areas Virtual Power Plants Boundaries Circuits Feeders Operators Owners Paths Routes Zones
Areas

To facilitate the visualization and analysis of a power system, elements may be allocated into areas (ElmArea ). The single line graphics can then be colored according to these areas and special reports after load flow calculations ('Area summary report' and 'Area interchange report') can be generated. Area objects are stored inside the Areas folder ( ) in the Network Data directory. For information about defining an Area please refer to Chapter 12 Grouping Objects . For information concerning the visualization of areas within the single line Graphic please refer to 10.6.3 Commands and Settings for Single Line Graphics . For information about reporting Area results please refer to Chapter 20 Reporting Results in PowerFactory .
Virtual Power Plants

Virtual Power Plants are used to group generators in the network, in such a way that the total dispatched active power is set to a target value. The dispatch of each generator (the Active Power field available in the Dispatch section of the Load Flow tab in the generator element dialogue) is scaled according to the Virtual Power Plant rules (must run, merit of order, etc.), in order to achieve the total target value. Virtual Power Plant objects (ElmBmu Data directory. ) are stored inside the Virtual Power Plants folder ( ) within the Network

For information regarding how to define a Virtual Power Plant, please refer to Chapter 12 Grouping Objects .
Boundaries

Boundaries are objects used in the definition of network reductions and in summation reports after a load flow calculation (to report the active and reactive power flow along the boundary). Boundary objects (ElmBoundary ) may define topological regions by

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 33 of 47

specifying a topological cut through the network. New boundaries are created by specifying the cubicles that define the cut through the network. An interior region, corresponding to the boundary cut, is defined by specifying a direction for each cubicle. Interior regions and boundaries can be colored in the single line graphic. New boundaries are stored in the Boundaries folder within the Network Data folder. For information on the definition and functionality of boundaries please refer to Chapter 12 Grouping Objects . For information on coloring options for boundaries and interior points please refer to Section 10.6.3 Commands and Settings for Single Line Graphics .
Circuits

Circuits are objects of class ElmCircuit ( ), and are used to group branches in order to clarify which branches are connected galvanically. Each branch (ElmBranch) can have a reference to any defined circuit object. This feature allows branches to be sorted according to the circuit to which they belong. For information regarding the definition of circuits and the assignment of branches to a circuit, please refer to Chapter 12 Grouping Objects .
Feeders

When analyzing a system it is often useful to know where the various elements are receiving their power supply from. In PowerFactory this is achieved using Feeder Definitions (ElmFeeder ). A feeder is defined at a line or transformer end, and then the feeder definition algorithm searches the system from the definition point to determine the extent of the feeder. The feeder ends when:
An open breaker is encountered; or The end of a line of supply is encountered; or `Terminate feeder at this point' is enabled in a cubicle (optional); or A higher voltage is encountered (optional).

Once a feeder has been defined it may be used to scale the loads connected along it according to a measured current or power, to create voltage profile plots or to select particular branches and connected objects in the network. Following load flow calculations, special reports can be created for the defined feeders. To distinguish the different feeder definitions, they can be colored uniquely in the single line graphic. All feeder objects are stored in the Feeders folder ( ) in the Network Data folder. For information regarding the definition of feeders and load scaling please refer to Chapter 12 Grouping Objects . For information about coloring the single line graphic according to feeder definitions please refer to Section 10.6.3 Commands and Settings for Single Line Graphics . For information about voltage profile plots, please refer to Chapter 20 Reporting Results in PowerFactory .
Operators

For descriptive purposes, it is useful to sort network components according to their operators. Additionally, system operators may find it advantageous to generate summary reports of the losses, generation, load, etc. according to their designated region(s). PowerFactory allows the definition of operators, the assignment of network components to these operators, and the identification of operators on single line diagrams by means of Operator objects. The Operator objects (ElmOperator, ) are stored in the Operators folder ( ) in the Network Model directory.

Further information about the definition and functionality of Operator objects is given in Chapter 12 Grouping Objects .
Owners

For descriptive purposes it is useful to sort network components according to their owners. Additionally, for network owners it may prove advantageous to generate summary reports of the losses, generation, load, etc. for their region(s). Similar to Operators, PowerFactory allows the definition of network owners, and the assignment of network components to them, by means of Owner objects. The Owner objects (ElmOwner, ) are stored in the 'Owners' folder ( ) in the Network Model directory.

Further information regarding the definition and functionality of Owner objects is given in Chapter 12 Grouping Objects .
Paths

A path (SetPath, ) is a set of two or more terminals and their interconnected objects. This is used primarily by the protection module to analyze the operation of protection devices within a network. The defined paths can be colored in a single line graphic using the coloring function. New paths are stored inside the Paths folder ( ) in the Network Data directory. For information regarding how to define a path please refer to Chapter 12 Grouping Objects . For information about the coloring function please refer to Section 10.6.3 Commands and Settings for Single Line Graphics . For information about the use of the path definitions for the analysis of the protective devices, please refer to Chapter 32 Protection .
Routes

Routes are objects which are used to group line couplings (tower elements). Each coupling (ElmTow) can have a reference to any defined route (ElmRoute, ). Each route has a color that can be used to identify it in single line diagrams, when the corresponding coloring function is enabled. For information regarding line couplings please refer to the technical reference for the transmission line model (Appendix C.10 Line (ElmLne) ); for information about the definition of routes and the assignment of couplings to a route, please refer to Chapter 12 Grouping Objects . For information about coloring functions in single line diagrams, please refer to Section 10.6.3 Commands and Settings for Single Line Graphics .
Zones

Components of a network may be allocated to a zone object (ElmZone, ) in order to represent geographical regions of the system. Each zone has a color which can be used to identify the elements belonging to it in the single line graphic. These elements can be listed in a browser format for group editing; additionally all loads belonging to the zone can be quickly scaled from the zone edit dialogue. Reports for the defined zones can be generated following calculations.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 34 of 47

Upon being defined, zones are by default stored inside the Zones folder ( ) in the Network Data folder. For information regarding the definition of a zone and its functionality, please refer to Chapter 12 Grouping Objects .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.3.4 Variations and Expansion Stages


During the planning and assessment of a power system it is necessary to analyze different variations and expansion alternatives of the original networks. In PowerFactory these variations are modeled by means of 'Variations', which are objects that can store and implement the changes which are expected on a network without affecting the original model. The use of variations allows the user to conduct studies under different network configurations in an organized and simple way. The user only needs to define (by means of Variations) the changes that s/he wants to implement and then activate or deactivate them according to her/his studies. Different variations can be independently applied (activated) at the same time to the same network, which further facilitates the user. The changes can also be implemented gradually according to the study time in order to allow the representation of scheduled expansion plans. Variations objects (IntScheme, ) are stored inside the Variations folder ( ) which resides in the Network Model folder. As introduced in Section 7.2, 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. 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. The changes contained in an expansion stage can be classified as:
Changed parameters of network components; Additions; i.e. objects added to the network. Deletions; i.e. objects removed from the network.

The example shown in Figure 7.7 illustrates the concept of variations and expansion stages. Variation 1 is composed of expansion stages: Stage 1, Stage 2 and Stage 3. Assume that the activation time of each of the expansion stages is t1, t2 and t3, respectively. With Variation 1 active and a study time between t1 and t2, the changes stored in Stage 1 apply to the original network. For a study time between t2 and t3, the changes from Stage 1 and Stage 2 apply. Similarly, for a study time greater than t3, changes from Stage 1 to Stage 3 apply. In this case, the red coloring of Variation 1 indicates that it is activated and that the changes included in its expansion stages are considered. The dark red color on Stage 1 means that the stored changes were already applied (the study time precedes t1). The red color on Stage 2 means that this is the current stage (the study time is between t2 and t3). The changes inside it have been applied and modifications carried out on the network will be stored inside this stage. The black color on Stage 3 means that the study time precedes t3; therefore the included changes have not yet been applied.

Fig. 7.7: Variations and expansion stages

Within an active variation, all changes applied to the actual network (i.e original network plus changes of preceding expansion stages) are recorded in the current expansion stage. Therefore, it is important to note that the current expansion stage is also the "recording" expansion stage. It may be possible to have two (or more) active variations and therefore two (or more) current expansion stages; only one of them can be set as the recording expansion stage (changes can only be stored in one of the actual expansion stages). In such cases the user must set one of the current expansion stages as the recording stage. In the example shown in Figure 7.7, if it assumed that Variation 1 is the only active variation: the recording expansion stage for a study time between t1 and t2 is Stage 1; for a study time between t2 and t3 it is Stage 2 (as illustrated in the figure); for a study time greater than t3 it is Stage 3. The study time may be changed to store modifications in a different expansion stage. It is also possible (and recommended) to directly set the desired stage as the recording expansion stage. This last action will automatically change the study time. Variations and expansion stages are not only used to record time-dependant modifications to the network model. Time dependencies of operational objects can also be modeled by means of them, in this case they are known as 'Variations'. For information about defining, setting, activating and working with Variations and Expansion Stages, please refer to Chapter 17

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 35 of 47

Network Variations and Expansion Stages . For information about Study Cases and the Study Time please refer to Section 13.3 Study Time .
Note: Operational parameters can only be changed if there is no active operation scenario.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.4 The Equipment Type Library


A type object holds the essential electrical information for each class of network component. This information is usually provided in manufacture's data sheets. Within the project structure the type objects are stored inside the Equipment Type Library. Type objects may be sorted by class using library subfolders ( ). Figure 7.8 shows the equipment library of a project containing generator, load and transformer types, all sorted using library subfolders.

Fig. 7.8: The Equipment Library

Unlike the Global Library (Section 5.3: User Accounts and User Groups), which is accessible to all users, the local Equipment Type Library can only be used by the project owner and those with which the project is shared. It is used to define types that are going to be used in the specific project. When defining a new network component, the user is asked for a type object. There s/he can choose among a 'Global Type' (from the Global Library), a 'Project Type' (from the project Equipment Library) or a New Project Type (Figure 7.9). If the latter option is selected, a new type will be defined and automatically stored in the local Equipment Type Library.
Notice: The local Equipment Type Library is generated automatically with a project. By default the equipment libraries include the 'Scales' folder (IntScales), which is used to store time scales (for further information please refer to Chapter 18: Parameter Characteristics).

Fig. 7.9: Defining the type for a generator element

Inside the equipment libraries, the user can define new suitable types for her/his project or simply copy types from the Global Library or other folders. If the types inside the Equipment Type Library are to be sorted according to their class, the user must create new folders for each class. For information regarding how to set the equipment library please refer to Chapter 14 The Equipment Type Library . For an explanation about type data please refer to Section 4.4 Data Arrangement .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5 The Operational Library


Network components use references to type objects in order to set parameters related to the equipment itself and avoid data redundancy. For example, two generators defined in a network model (let's call them G1 and G2) may refer to the same generator type (let's call it `G 190M-18kV') to set their manufacturer equipment related data, i.e. nominal voltage, nominal power, impedances, etc. G1 and G2 will have the same equipment data but may be operated at different points or may be connected to ground in a different way. That is, they may have the same type data, but different operational and element data. As mentioned, certain parameters of network components do not depend on the equipment itself but on the operational point. These parameters are grouped under the operational data set of the element. In the previous example considering synchronous generators, the active power dispatch or the reactive power limits are part of this operational data. In order to analyze a network under different operational points, operational data may change frequently during a study.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 36 of 47

Considering that different network components may have identical operational parameters (for example 2 generators with the same MVAr limits or various circuit breakers with the same ratings for short-circuit currents); references to objects storing operational data would facilitate the definition of different network operational points. Similar to types, the use of objects containing operational data avoids redundancy. The Operational Library is the folder where objects containing operational data are stored. The description of these objects and their hierarchical organization within the Operational Library is the subject of the following subsections. Figure 7.10 shows how the Operational Library looks from its uppermost hierarchical level.

Fig. 7.10: Operational Library

Note: Please note that fault conditions of network components are also considered part of the operational data.

Circuit Breaker Ratings Demand Transfer Faults Capability Curves for Generators Outages Running Arrangements Thermal Ratings

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5.1 Circuit Breaker Ratings


Circuit Breaker Rating objects (IntCbrating ) contain information that defines the rated short-circuit currents for circuit breakers (objects of class ElmCoup). They are stored inside the CB-Rating folder ( ) in the Operational Library. Any circuit breaker (ElmCoup) defined in the Network Model can use a reference to a Circuit Breaker Rating object in order to change its current ratings. Originally these ratings are defined in the type of the circuit breaker element. The right side of Figure 7.11 shows the edit dialogue of the IntCbrating object. The left side shows the edit dialogue of a circuit breaker where a reference to an IntCbrating object called Rating 1 is created.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 37 of 47

Fig. 7.11: CB-Rating

As shown in Figure 7.11, the parameters defined by a circuit breaker rating are:
Three phase initial peak short circuit current Single phase initial peak short circuit current Three phase peak break short circuit current Single phase peak break short circuit current Three phase RMS break short circuit current Single phase RMS break short circuit current DC time constant

For information about how to define new circuit breaker ratings please refer to Section 15.1 Circuit Breaker Ratings .
Note: Circuit breaker elements (ElmCoup) must be distinguished from Switch objects (StaSwitch); the latter are automatically created inside cubicles when connecting a branch element (which differs to a circuit breaker) to a terminal. StaSwitch object employ references to Circuit Breaker Rating objects.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5.2 Demand Transfer


The active and reactive power demand defined for loads and feeders in the network model can be transferred to another load (or feeder) within the same system by means of Load Demand Transfers (objects of the class IntOutage). This transfer only takes place if it is applied during a validity period defined by the user (i.e. if the current study time lies within the validity period). Figure 7.12 shows the edit dialogue of a Load Demand Transfer. In this case the user will transfer 13 MW from a load called Load A to a load called Load B (the active power demand of Load of A will be reduced by 13 MW, which will be added to the demand of Load B).

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 38 of 47

Fig. 7.12: Load Demand Transfer

The demand transfer can be defined with absolute values (MW and MVA) or with relative (percent) values. For information regarding how to define and how to apply Load Demand Transfers, please refer to Section 15.2 Demand Transfers .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5.3 Faults
The calculation commands provided by the reliability assessment function of PowerFactory use objects called Contingencies (ComContingency and ComOutage) to simulate the outage (and subsequent recovery) of one or more system elements. In order to facilitate the definition of these Contingencies and to avoid data redundancy, objects called Fault Cases (class IntEvt) are defined in the Operational Library. Whenever it is required, the user can create new Contingencies based on the defined fault cases. Fault cases can be considered to be fault scenarios that determine the outage of one or more system elements. They are comprised of a collection of events (i.e. short-circuits, switching) that define how the elements are taken out of service. Fault cases are stored inside the Faults folder within the Operational Library. Besides fault cases, other objects which facilitate the management of fault scenarios and the creation of contingencies are stored in the Faults folder. This section focusses on the data structure of the Faults folder and the objects that comprise it. The actual functionality of these objects will be presented in Chapter 29 Reliability Assessment . The 'Faults' folder (
1. 2.

) can store two kinds subfolders:


): stores objects that represent fault scenarios (fault cases IntEvt ): stores objects called Fault Groups (IntFaultgrp )

Fault Cases folders (IntFltcases Fault Groups folders (IntFltgroups, to fault cases.

), which in-turn store references

The user can define as many subfolders (fault cases-IntFltcases and fault groups-IntFltgroups) and objects (fault cases-IntEvt and fault groups-IntFaultgrp) as s/he needs. The uppermost window in Figure 7.13 shows the Faults folder in a project. Two Fault Cases subfolders (Cases North and Cases South) have been defined; and a Fault Groups subfolder, called Grouping Faults is also contained. The middle window in Figure 7.13 shows the content of Cases South, which stores three fault cases: namely Bus 1, G1 and T1. In the bottom window of Figure 7.13, a fault group called Fault Group has been defined inside Grouping Faults which contains references to the fault case Line2-Line5 (defined in the Cases North).

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 39 of 47

Fig. 7.13: The Faults Folder

In the following subsections more detailed descriptions of the fault case object and the fault group object are given. For information on how to define new objects in the Faults folder, please refer to Section 15.3 Fault Cases and Fault Groups .
Fault Cases

Fault cases are objects of class IntEvt (in PowerFactory terminology IntEvt objects are called Simulation Events/Faults) which are used to model fault scenarios as explained in the previous section. They are comprised of objects called Events, which represent the specific events taking place on the network and leading to the unintended outage of the elements. A fault case can of course represent a fault in more than one component; in this case more than one event would be defined. The fault case Line 2-Line 5 shown in Figure 7.13, represents a short-circuit fault in transmission lines Line2 and Line 5 of the sample network. Line 2-Line 5 is therefore made of short-circuit events for the two corresponding components. There are two types of Fault Cases:
1. Fault cases without switch events (Type 1): Independent of the current topology and only stores the fault locations. The corresponding switch events are automatically generated by the contingency analysis tools. For further information please refer to Chapter 29 Reliability Assessment . Fault Case with at least one switch event (Type 2): A Fault Case of Type 2 predefines the switch events that will be used to clear the fault. No automatic generation of switch events will take place. For further information please refer to Chapter 29 Reliability Assessment .

2.

Note: Event objects can generate more than short-circuits. PowerFactory offers several kinds of events for contingency analysis and time-domain simulations, a detailed description of each event class is given in Section 13.8 Events . In the case of fault representations in the Operational Library by means of fault cases, only short-circuit and switching events are relevant.

For information on how to define fault cases and how the events of the defined faults are created please refer to Section 15.3 Fault Cases and Fault Groups .
Fault Cases and The Contingency Analysis Tool

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 40 of 47

The main purpose of defining fault cases in the Operational Library is to facilitate the definition of reliability analyses on complex networks. From the contingency analysis command (ComSimoutage), the user makes references to the desired fault cases and the program automatically generates the contingencies for the corresponding components. There is no need to redefine the same contingencies each time a contingency analysis of the network (regardless of its operational point or current configuration) is required. This is demonstrated by performing a contingency analysis of the critical components T1, G1 and Bus 1 in the network South in Figure 7.13. Once the fault cases G1, T1 and Bus 1 have been created, the user can call them from the contingency analysis command every time s/he needs to analyze the network, considering the contingencies of these components. For further information regarding the use of fault cases to create outages for PowerFactory's contingency analysis tools please refer to Chapter 29 Reliability Assessment .
Note: The use of IntEvt objects extends beyond PowerFactory's reliability analysis functions. Time domain simulations (EMT/RMS) make reference to IntEvt objects, in order to include simulation events which take place during runtime. In this case the execution time sequence of the events must be defined by the user.
Fault Groups

A fault group object (IntFaultgrp) as introduced in 7.5.3 can store references to different fault cases; therefore they may be considered as 'sets' of faults. Like fault cases, fault groups can be referred to by the contingency analysis command (ComSimoutage); in this case all the faults contained in the set will be considered. For the use of fault cases to create outages for the contingency analysis tools please refer to Chapter 29 Reliability Assessment .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5.4 Capability Curves for Generators


The Capability Curve objects (IntQlim, ) allow the consideration of distinct minimum /maximum values of the reactive power, ) in the at different levels of active power injection. Capability curves are stored inside the Mvar Limit Curves folder ( Operational Library. Synchronous generators (ElmSym) and static generators (ElmGenstat) defined in the Network Model can use a pointer to a Capability Curve object from the Load Flow tab of their edit dialogue. When a capability curve is used, the dispatch of the generator always stays within its minimum and maximum range. For information regarding how to define new capability curves for generators, please refer to Section 15.4 Capability Curves (MVAr Limit Curves) for Generators . For information about the dispatch of synchronous generators, please refer to the corresponding technical reference (C.28: Synchronous Machine (ElmSym)). For information about Load Flow calculations and reactive power limits please refer to Chapter 22 Load Flow Analysis .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5.5 Outages
Outages are objects which are used to check and/or apply programmed actions (programmed outages or generator deratings) over a set of network components. An outage object requires the definition of the outage period (start and end time), the actions that are taken during that period (outage type), and the network components affected by these actions. The outages (objects of class IntOutage) are stored in the Outages folder inside the Operational Library. According to the actions performed on the selected elements, the outages can be of two different types: Outage of an Element or Generator Derating. Outage of Element Generator Derating
Outage of Element

Outages of elements are used to intentionally take certain network components out of service according to programmed actions (i.e. because of maintenance). In this case, references to network components which should be out of service during the defined period, are stored inside the outage object. If the Check button of the outage dialogue is pressed, the program looks for the current state of the referred-to elements. If, according to the current study time (and the outage period), a referred-to component is out of service but still energized, a warning message is shown in the output window. The fulfillment of programmed outages can also be checked using the single line graphic coloring functions. If the Apply button is pressed, the program automatically executes the outage (which can also be manually carried out by the user) of the referred-to element(s), as long as the study time lies within the outage period. The outage of an element consists of the disconnection (deenergizing) and the earthing of the target component. Figure 7.14 (front) shows the edit dialogue of the outage object called Planned Outage. The Outage Type selected is `Outage of Element'. The outage period starts on 01.01.2007 and ends on 01.10.2007. The outage contains references to the network components G2 and Line 3 (back, right pane of Data Manager window). If the current study time lies between the start and the end of the outage, both G2 and Line 3 must be out of service during this period. This condition may be checked by pressing the Check button or by setting the coloring mode of the single line graphic to `Outage Check'.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 41 of 47

Fig. 7.14: Outage of an Element

For information on defining Outages please refer to Section 15.5 Element Outages and Generator Deratings . For information regarding the single line graphic coloring function please refer to Section 10.6.3 Commands and Settings for Single Line Graphics .
Generator Derating

In this case, a reference to the generator which is to be derated and the amount of MW reduction is given. Similar to Outage of Element, the fulfillment of the derated condition, according to the outage period and the current study time, can be known via the Check button or by setting the coloring function of the single line graphic. The Apply button automatically executes the derating of the generator (according to the outage period). For information on defining Outages please refer to Section 15.5 Element Outages and Generator Deratings . For information regarding the single line graphic coloring function please refer to Section 10.6.3 Commands and Settings for Single Line Graphics .
Load Demand Transfer

Please refer to Section 7.5.2 Demand Transfer .


Note: If a Planned Outage object is defined in the Outages folder of the Operational Library, only the outage types Outage of Element and Generator Derating are enabled. Similarly if outage objects are defined in the Demand transfer folder, only the outage type Demand Transfer is enabled.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5.6 Running Arrangements


Running Arrangements (IntRunarrange ) are operational data objects that store statuses of switches (open or closed) of one substation. As shown in Figure 7.15, a running arrangement uses a reference to the substation object (ElmSubstat) whose switch statuses are stored. An application period (start and end time) is used to discriminate the use of a running arrangement, according to the study time. Running arrangements are stored in the Running Arrangements folder in the Operational Library ( ).

Fig. 7.15: RA object dialogue

Different configurations of the same substation can be defined by storing the corresponding switch statuses in running arrangements. During the study, the user can apply any of the stored statuses simply by selecting the corresponding running arrangement. If a running arrangement is selected for a substation, the status of the switches cannot be modified (i.e. they become read-only). If there is no setting for a switch in a running arrangement (i.e. the running arrangement is incomplete), the switch will remain unchanged but its status will also be set to read-only. If the current running arrangement is deselected, the switches recover the status that they had before the running arrangement was selected (and therefore resume their write access status).

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 42 of 47

Running arrangements can be defined and selected in the substation object dialogue (Figure 7.16). For information regarding defining, selecting and working with running arrangements please refer to Section 15.6 Running Arrangements .

Fig. 7.16: Definition of a running arrangement via the station object dialogue

Note: Running arrangements store only the status of switches of class ElmCoup. The status of switches which are automatically created in a cubicle following the connection of a branch element (StaSwitch objects) are not considered in a running arrangement.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.5.7 Thermal Ratings


Thermal Ratings objects (IntThrating, ) allow the definition of post-fault operational ratings for certain branch elements, depending on the fault duration and the loading before the fault. IntThrating objects are stored in the Thermal Rating folder in the Operational Library ( ). Basically they are two-dimensional matrices whose cells contain the ''short time'' post-fault ratings (in MVA), according to the pre-fault loading (defined in the first column) and the duration of the fault/overloading (defined in the first row). The components in the Network Model that can use references to thermal ratings are: transmission lines (ElmLne), 2- and 3winding transformers (ElmTr2 and ElmTr3), series reactors (ElmSind) and series capacitors (ElmScap). Please note that the rating table given on the Ratings tab of the Thermal Rating object (when option Consider short term ratings is enabled) is used solely the contingency analysis command in PowerFactory. In this calculation, the pre-fault loading conditions of the network components are determined after a base load flow calculation. The contingency analysis is then performed using a load flow command, where the post-contingency duration is specified. For information on how to define thermal rating objects, please refer to Section 15.7 Thermal Ratings . For information about the contingency analysis command in PowerFactory please refer to Chapter 29 Reliability Assessment .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.6 The Templates Library


Templates of existing network components (or groups of components) can be defined in PowerFactory in order to facilitate the further construction of network models. Once a template has been defined, the user can create new components (or groups of components) based on this template. The result is a new component (or group of components) with the same parameters and configuration as the original one. Components from templates are created using the graphical editor. Four kinds of templates are supported in PowerFactory:
1. 2. 3. 4. Element template for single network elements: New single network elements with the same parameters as the original element are created. Group template for non-composite graphic objects: New groups of objects (including graphical attributes) are created. Substation template (composite node): New substations with the same configuration as the original substation (including its diagram). Branch template (composite branch): New branches with the same configuration as the original branch (including its diagram).

Templates are normally stored in the Templates folder ( ), in the Library. When a template for a single network element is defined, a copy of the original element is automatically created in the Templates folder. New templates of substations and branches will copy the objects together with all of their contents (including the diagram) to the Templates folder. New templates for groups of objects will copy the corresponding objects, together with their graphical information to a subfolder for groups of class IntTemplate ( ) within the Templates Library.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 43 of 47

For further information about working with templates, please refer to Section 10.1 Defining Network Models with the Graphical Editor .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.7 Parameter Characteristics and Parametric Studies


In PowerFactory any parameter may be assigned a range of values that will be selectable by date and time, or by a user-defined trigger (Section 13.11: Triggers). Examples include ambient temperature, temporary overload limit, etc. These kinds of ranges of values are known as characteristics. The range of values may be in the form of a one-dimensional vector or a two-dimensional matrix. The assignment of a characteristic may be made either individually to a parameter or to a number of parameters. If the characteristic is to be applied to parameters across multiple objects (i.e. active power of all loads), then a reference characteristic is used. Studies which utilize characteristics are known as parametric studies. The parametric techniques available in PowerFactory use the flexible, generic 'characteristic vector' (ChaVec, ) or the generic 'characteristic matrix' (ChaMat, ). Both of these characteristics use some sort of scale with which the target parameter is varied. Four types of parameter scale are available:
1. 2. 3. 4. Continuous Scale: A continuous function, such as a temperature scale from 0 to 45 degrees. Discrete Scale: A discrete 'case' function, such as 'Temporary Overload' and `Emergency Overload'. Continuous Time Scale: A continuous time-dependent function. Discrete Frequency Scale: A continuous frequency-dependent function.

When the scale is created, a means to 'set' the scale, and thereby to set the parameter to the corresponding value, is required. This ). New scales are normally defined in the Scales folder of the Equipment Type Library. is called a trigger (SetTrigger, After a new scale has been defined, a trigger is automatically created in the active study case folder (see also Section 13.11: Triggers). When a trigger is edited and a 'current' value is set (the triggers are accessed by pressing the set and the parameter value is changed. in the main toolbar) the scale is

When a different study case is activated, or a new study case is created, and a load-flow is performed, all relevant triggers are copied into the study case folder and may be used in the new study case. For information about the different kinds of scales and characteristics and how are they defined, please refer to Chapter 18 Parameter Characteristics .

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

7.8 DIgSILENT Programming Language (DPL) Scripts


The DIgSILENT Programming Language DPL offers an interface to the user for the automation of tasks in PowerFactory. By means of a simple programming language, the user can define her/his own automation commands (or `scripts') to perform iterative or repetitive calculations on target networks, and post-process the results. Such user-defined scripts can be used in all areas of power system analysis, such as:
Network optimization Cable-sizing Protection coordination Stability analysis Parametric sweep analysis Contingency analysis

DPL scripts may include any/all of the following:


Program flow commands such as 'if-else and 'do-while' PowerFactory commands (i.e. load-flow or short-circuit commands: ComLdf, ComShc) Input and output routines Mathematical expressions PowerFactory object procedure calls Subroutine calls

DPL command objects (ComDpl, ) contain the DPL script itself (amongst other things). 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 subroutines, and may then output results. This process takes place following the execution of the object's corresponding DPL script. DPL scripts are written by the user utilizing the DPL editor which resides inside the DPL command object. DPL commands are stored inside the Scripts folder ( ) in the project directory. For further information about DPL commands and how to write and execute DPL scripts please refer to Chapter G The DIgSILENT Programming Language - DPL and Appendix H DPL Reference (only available in the online help).

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 44 of 47

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

Chapter 8 General Information about Analyses in PowerFactory


This chapter gives an introduction to the calculation commands used in PowerFactory, additionally it presents the tools that facilitate the visualization and comparison of the calculated results. Chapters, exclusively dedicated to the tools presented here, are available in the subsequent volumes of this manual. Calculation Commands in PowerFactory Edit relevant Objects for Calculation Results Comparisons Between Calculations

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

8.1 Calculation Commands in PowerFactory


PowerFactory offers a wide variety of calculation commands, of which the
Load-flow calculations, Short-circuit calculations, Transient simulations,

are the most important. Calculations are performed using data as defined by the active study case (see Section 13.1 Creating and Using Study Cases for more information on study cases). Therefore a study case, having at least one grid or system stage, should be activated prior to starting any calculation function. See the Chapter 13 Study Cases for more information. The main menu calculation icons will be enabled as soon as a correct study case is active. These icons will pop up the default calculation command dialogues which are used to configure and execute a calculation. The default calculation command objects are stored in the active study case. The main toolbar shows the following calculation icons.
Calculate Load-Flow (Chapter 22: Load Flow Analysis) Calculate Optimal Power Flow (OPF, Chapter 30: Optimal Power Flow) Calculate Short-Circuit (Chapter 23: Short-Circuit Analysis) Break Reset Calculation Undo (to reverse the last changings)

Other command icons are grouped together in sub-toolbars which are selected by the toolbar selection list. If you press the 'Select Toolbar' button ( ), the options for the different toolbars are depicted by their icons. If you have selected a toolbar different from the 'Stability' toolbar, the icon for the 'Select Toolbar' button changes.

Fig. 8.1: Available additional toolbars in the main icon bar The toolbar selection icon (this icon differs in dependence of the selected toolbar). Stability analysis commands (Chapter 25: Stability and EMT Simulations) Modal analysis commands (Chapter 26: Modal Analysis / Eigenvalue Calculation) Contingency analysis commands (Chapter 28: Contingency Analysis)

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 45 of 47

Reliability analysis commands (Chapter 29: Reliability Assessment) Harmonics analysis commands (Chapter 24: Harmonics Analysis) Protection tools (Chapter 32: Protection) Additional tools (sensitivity analysis, network reduction, cable reinforcement optimization etc.) Optimal capacitor placement commands (Chapter 31.1: Optimal Capacitor Placement) User defined tools

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

8.2 Edit relevant Objects for Calculation


The icon is used to gather and show all objects considered by the study case, and which are of a certain class, in a browser in order to inspect their data or to edit them. Pressing the icon will present a menu listing the icons of all classes of objects currently used for the calculations, as depicted in Figure 8.2. Pressing a class icon will pop up an object filter browser, filled with all the objects of the selected class, which are considered by the calculation. Pressing the line icon, for instance, will open a filter browser which contains a list of all lines. Pressing the transformer icon gives the list of all transformers, etc. The filter browser can be used to inspect, select or edit selected objects. Normally, the filter browser is closed after performing any of these actions. It is possible to open more filter browser at the same time, by repeatedly pressing the icon.

Fig. 8.2: Selecting calculation relevant objects

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

8.3 Results
Following calculations some messages are printed to the output window. These generally consist of errors, warnings or information that may be useful when interpreting the calculated data. The load-flow calculation function, for example, will provide the following message when the power system under analysis is has 2 separated areas:
DIgSI/wrng - 1 area(s) are unsupplied. DIgSI/info - Grid splitted into 2 isolated areas

More extensive output is given in the output window, for example, by the (N-1) outage calculation, which is an option in the loadflow command dialogue. The output given by that calculation is a list of load-flow calculations that were performed, each with a table in which the element on outage and all overloaded elements are provided. The usual place, however, to visualize load-flow or short-circuit calculation results is in the single line graphics, or the data manager and object filter (when tabulated results are required). The results on view may configured using the highly flexible, user-definable, variable sets. These are accessed from the results boxes or flexible data tab. See Chapter 19 Defining Variable Sets for more information. Some calculations offer additional results in the form of bar-graphs, vector diagrams or other graphical output. All such outputs are presented by so-called virtual instruments, which are placed on a virtual instruments page in the current graphics board.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

8.4 Comparisons Between Calculations


At many stages in the development of a power system design, the differences between certain settings or design options become of interest. For a single calculation, the 'absolute' results are shown in the single line graphics. The variables that are shown may be specified by the user by altering the result-box definitions. When comparing two cases, the results of the first calculation are 'frozen'. All subsequent calculations will then show their results as deviations from the first calculation made. The subsequent calculation results are stored together with the first result. This allows the user to re-arrange the comparisons as desired by pressing the icon (see the next Section).

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 46 of 47

The differences between cases are colored according to the severity of the deviation, making it possible to recognize the differences between calculation cases very easily. The coloring and severity ranges may be set in the Edit Comparing of Results... menu option, found by pressing (see the next section).

A comparison between cases is made as follows:


Calculate the first case by activating a certain calculation case and, for example, calculating a load-flow. Press the icon on the main toolbar. This will store the base case results and prepares to store the results of forthcoming calculations. If relative results are also required for a particular calculation report, in a formatted report, that report has to be generated for the first case by pressing the icon on the main toolbar and selecting the required report. This step is necessary to let the comparison manager know which parameters are to be compared. Change the power system or a calculation setting to create the next case. Permitted alterations include opening/closing switches, altering load settings or any other component parameter, changing calculation cases, adding or deleting elements, etc. Repeat the calculations as performed for the first case. The result boxes in the single line graphic will now show the percentage change as compared to the first case. If the calculation report, as generated for the first case, is generated again, it will also show relative results. Make and calculate the other cases. After each calculation, the comparison to the first case is shown.

Editing a Set Of Comparison Cases Update Database

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

8.4.1 Editing a Set Of Comparison Cases


The set of calculated comparisons may be edited to select the cases which are to be compared to each other or to set the coloring mode. When the icon on the main toolbar is pressed, the Compare dialogue will open. See Figure 8.3.

Fig. 8.3: The Compare dialogue

With the Compare dialogue, the two cases which are to be compared can be selected. Furthermore, a list of colors may be set which is then used to color the results displayed in the result boxes, according to certain levels of percentage change.

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

8.4.2 Update Database


In PowerFactory input (data that has been entered by the user) and output (parameters that have been calculated) data is kept separate and output data, such as the new tap positions following an automatic tap adjustment calculation, does not overwrite the settings that the user originally entered, unless the user specifically commands this, using the icon on the main toolbar.

Note The corresponding input parameters of the database will be overwritten by the calculated values.

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

DIgSILENT PowerFactory

Page 47 of 47

Updating the database may be performed for:


Scaling factor of loads Transformer taps Capacitive Steps of Shunts/Filter P,Q of Loads P,Q of asynchronous machines Example:

A load-flow is calculated with the options "Automatic Tap Adjust of Transformers" and "Automatic Shunt Adjustment" enabled. The calculated tap and shunt positions may be seen in the single line diagram, but it will be noticed that the input data parameter in the element data dialogue is as originally entered. The icon calculated values found on the single line diagram. is clicked, and the input parameters are now overwritten by the

DIgSILENT GmbH www.digsilent.de Tel: +49 (0)7072 9168-50 Fax: +49 (0)7072 9168-88 support@digsilent.de

file://C:\Documents and Settings\sesa157733\Configuracin local\Temp\~hhA846.htm

07/10/2011

You might also like