DIgSILENT

PowerFactory 2016

User Manual

I N T E G R AT E D P O W E R S Y S T E M A N A LY S I S S O F T W A R E F O R
TRANSMISSION / DISTRIBUTION / INDUSTRY / G E N E R AT I O N / I N T E G R AT I O N O F R E N E W A B L E S
DIgSILENT PowerFactory
Version 2016

User Manual

Online Edition

DIgSILENT GmbH

Gomaringen, Germany

March 2016
 Publisher:
DIgSILENT GmbH
Heinrich-Hertz-Straße 9
72810 Gomaringen / Germany
Tel.: +49 (0) 7072-9168-0
Fax: +49 (0) 7072-9168-88

Please visit our homepage at:

http://www.digsilent.de

Copyright DIgSILENT GmbH

All rights reserved. No part of this
publication may be reproduced or
distributed in any form without written
permission of the publisher.

March 2016
r2648
Contents

I General Information 1

1 About this Guide 3

1.1 Contents of the User Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 Used Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Contact 5

2.1 Direct Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Documentation and Help System 7

4 PowerFactory Overview 9

4.1 General Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.2 Database, Objects, and Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.3 PowerFactory Simulation Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.4 General Design of PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.5 Type and Element Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.6 Data Arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.6.1 Global Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.6.2 User Defined Global Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.6.3 Project Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.6.4 Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.6.5 Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.6.6 Operation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.6.7 Study Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.6.8 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

DIgSILENT PowerFactory 2016, User Manual i

CONTENTS

4.7 Project Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.7.1 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.7.2 Branches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.7.3 Cubicles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.7.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.7.5 Substations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.7.6 Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.7.7 Branch Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.8 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.8.2 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.8.3 Main Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.8.4 The Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.9 Scripting in PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.9.1 DIgSILENT Programming Language (DPL) Scripts . . . . . . . . . . . . . . . . . 30

4.9.2 Python Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

II Administration 33

5 Program Administration 35

5.1 Program Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.2 PowerFactory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.3 Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.4 External Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.5 Map Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2.6 Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.3 Licence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.3.1 Select Licence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.3.2 Activate / Update / Deactivate Licence . . . . . . . . . . . . . . . . . . . . . . . . 38

5.4 Workspace Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.4.1 Show Workspace Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

ii DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

5.4.2 Import and Export Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.4.3 Show Default Export Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.4.4 Import Workspace from 14.X or 15.0. . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.5 Offline Mode User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.5.1 Functionality in Offline Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.5.2 Functionality in Online mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.5.3 Terminate Offline session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.6 Housekeeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.6.2 Configuring Permanently Logged-On Users . . . . . . . . . . . . . . . . . . . . . 44

5.6.3 Configuring Housekeeping Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

5.6.4 Project Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.6.5 Configuring Deletion of Old Projects . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.6.6 Configuring Purging of Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.6.7 Configuring Emptying of Recycle Bins . . . . . . . . . . . . . . . . . . . . . . . . 48

5.6.8 Monitoring Housekeeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.6.9 Summary of Housekeeping Deployment . . . . . . . . . . . . . . . . . . . . . . . 48

6 User Accounts, User Groups, and Profiles 49

6.1 PowerFactory Database Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

6.2 The Database Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6.3 Creating and Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

6.4 Creating User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

6.5 Creating Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

6.5.1 Tool Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6.5.2 Configuration of Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.5.3 Configuration of Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

6.5.4 Configuration of Dialog Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

6.5.5 Configuration of Dialog Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6.5.6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7 User Settings 59

7.1 Data/Network Model Manager Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

DIgSILENT PowerFactory 2016, User Manual iii

CONTENTS

7.2 Graphic Windows Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

7.2.1 General tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

7.2.2 Advanced tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.3 Output Window Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.4 Functions Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.5 Editor Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.6 StationWare Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

7.7 Miscellaneous Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

III Handling 65

8 Basic Project Definition 67

8.1 Defining and Configuring a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

8.1.1 Project Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

8.1.2 Project Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

8.1.3 Project Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8.1.4 Activating and Deactivating Projects . . . . . . . . . . . . . . . . . . . . . . . . . 72

8.1.5 Exporting and Importing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

8.1.6 External References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

8.2 Creating New Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

9 Network Graphics (Single Line Diagrams) 77

9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

9.2 Defining Network Models with the Graphical Editor . . . . . . . . . . . . . . . . . . . . . . 77

9.2.1 Adding New Power System Elements . . . . . . . . . . . . . . . . . . . . . . . . . 77

9.2.2 Drawing Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

9.2.3 Drawing Branch Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

9.2.4 Marking and Editing Power System Elements . . . . . . . . . . . . . . . . . . . . 80

9.2.5 Interconnecting Power Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . 81

9.2.6 Working with Substations in the Graphical Editor . . . . . . . . . . . . . . . . . . 83

9.2.7 Working with Composite Branches in the Graphical Editor . . . . . . . . . . . . . 86

9.2.8 Working with Single and Two Phase Elements . . . . . . . . . . . . . . . . . . . . 86

9.3 Defining and Working with Lines and Cables . . . . . . . . . . . . . . . . . . . . . . . . . 87

iv DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

9.3.1 Defining a Line (ElmLne) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

9.3.2 Defining Line Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

9.3.3 Example Cable System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

9.3.4 Example Line Couplings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

9.4 Neutral winding connection in network diagrams . . . . . . . . . . . . . . . . . . . . . . . 93

9.5 Graphic Windows and Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

9.5.1 Network Diagrams and Graphical Pages . . . . . . . . . . . . . . . . . . . . . . . 96

9.5.2 Active Graphics, Graphics Board and Study Cases . . . . . . . . . . . . . . . . . 97

9.5.3 Single Line Graphics and Data Objects . . . . . . . . . . . . . . . . . . . . . . . . 98

9.5.4 Editing and Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

9.5.5 Creating a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

9.5.6 Creating New Graphic Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

9.5.7 Basic Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

9.5.8 Page Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

9.5.9 Drawing Toolboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

9.5.10 Active Grid Folder (Target Folder) . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

9.6 Graphic Commands, Options, and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 103

9.6.1 Freeze Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

9.6.2 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

9.6.3 View commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

9.6.4 Select commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

9.6.5 Graphic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

9.6.6 Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

9.6.7 Colouring Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

9.6.8 Graphic Legends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

9.6.9 Element Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

9.6.10 Node Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

9.6.11 Page and Print Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

9.6.12 Diagram Layout Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

9.6.13 Insert New Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

9.7 Drawing Diagrams with Existing Network Elements . . . . . . . . . . . . . . . . . . . . . 123

9.7.1 Generate complete diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

DIgSILENT PowerFactory 2016, User Manual v

CONTENTS

9.7.2 Expand k-neighbourhood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

9.7.3 Insert Missing graphical branches . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

9.7.4 Draw manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

9.7.5 Automatic Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

9.7.6 Draw existing elements using Drag & Drop . . . . . . . . . . . . . . . . . . . . . . 126

9.8 Editing and Changing Symbols of Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 126

9.9 Result Boxes, Text Boxes and Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

9.9.1 Result Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

9.9.2 Text Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

9.9.3 Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

9.9.4 Free Text Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

9.10 Annotation Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

9.11 Annotation of Protection Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

9.12 Navigation Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

9.13 Geographical Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

9.13.1 Using an External Map Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

9.13.2 Using Local Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

10 Data Manager 139

10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

10.2 Using the Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

10.2.1 Navigating the Database Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

10.2.2 Adding New Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

10.2.3 Deleting an Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

10.2.4 Cut, Copy, Paste and Move Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 144

10.2.5 The Data Manager Message Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

10.2.6 Additional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

10.3 Defining Network Models with the Data Manager . . . . . . . . . . . . . . . . . . . . . . . 146

10.3.1 Defining New Network Components in the Data Manager . . . . . . . . . . . . . 146

10.3.2 Connecting Network Components in the Data Manager . . . . . . . . . . . . . . . 146

10.3.3 Defining Substations in the Data Manager . . . . . . . . . . . . . . . . . . . . . . 146

10.3.4 Defining Composite Branches in the Data Manager . . . . . . . . . . . . . . . . . 147

10.3.5 Defining Sites in the Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 148

vi DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

10.3.6 Editing Network Components using the Data Manager . . . . . . . . . . . . . . . 148

10.4 Searching for Objects in the Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 149

10.4.1 Sorting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

10.4.2 Searching by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

10.4.3 Using Filters for Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

10.5 Auto-Filter functions in Data Manager and browser windows . . . . . . . . . . . . . . . . 151

10.6 Editing Data Objects in the Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

10.6.1 Editing in Object Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

10.6.2 Editing in “Detail” Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

10.6.3 Copy and Paste while Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

10.7 The Flexible Data Page Tab in the Data Manager . . . . . . . . . . . . . . . . . . . . . . 155

10.7.1 Customising the Flexible Data Page . . . . . . . . . . . . . . . . . . . . . . . . . 156

10.8 The Input Window in the Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

10.8.1 Input Window Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

10.9 Save and Restore Parts of the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

10.9.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

10.10Spreadsheet Format Data Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

10.10.1 Export to Spreadsheet Programs (e. g. MS EXCEL) . . . . . . . . . . . . . . . . 160

10.10.2 Import from Spreadsheet Programs (e. g. MS EXCEL) . . . . . . . . . . . . . . . 162

11 Study Cases 167

11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

11.2 Creating and Using Study Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

11.2.1 The Study Case Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

11.3 Summary Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

11.4 Study Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

11.5 The Study Case Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

11.6 Variation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

11.7 Operation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

11.8 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

11.9 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

11.9.1 Dispatch Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

11.9.2 External Measurement Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

DIgSILENT PowerFactory 2016, User Manual vii

CONTENTS

11.9.3 Inter-Circuit Fault Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

11.9.4 Events of Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

11.9.5 Message Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

11.9.6 Outage of Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

11.9.7 Parameter Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

11.9.8 Save Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

11.9.9 Short-Circuit Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

11.9.10 Stop Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

11.9.11 Switch Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

11.9.12 Synchronous Machine Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

11.9.13 Tap Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

11.10Simulation Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

11.11Results Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

11.12Variable Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

11.13Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

11.14Graphic Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

12 Network Model Manager 181

12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

12.2 Using the Network Model Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

13 Project Library 185

13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

13.2 Equipment Type Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

13.3 Operational Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

13.3.1 Circuit Breaker Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

13.3.2 Demand Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

13.3.3 Fault Cases and Fault Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

13.3.4 Capability Curves (Mvar Limit Curves) for Generators . . . . . . . . . . . . . . . . 193

13.3.5 Planned Outages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

13.3.6 Running Arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

13.3.7 Thermal Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

13.4 Templates Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

viii DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

13.4.1 General Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

13.4.2 Substation Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

13.4.3 Busbar Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

13.4.4 Composite Branch Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

13.4.5 Example Power Plant Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

13.4.6 Wind Turbine Templates according to IEC 61400-27-1 . . . . . . . . . . . . . . . 202

13.4.7 Example Busbar Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

14 Grouping Objects 205

14.1 Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

14.2 Virtual Power Plants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

14.2.1 Defining and Editing a New Virtual Power Plant . . . . . . . . . . . . . . . . . . . 206

14.2.2 Applying a Virtual Power Plant . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

14.2.3 Inserting a Generator into a Virtual Power Plant and Defining its Virtual Power
Plant Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

14.3 Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

14.3.1 Boundary Definition Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

14.3.2 Element Boundary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

14.4 Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

14.5 Feeders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

14.5.1 Feeder Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

14.6 Meteo Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

14.7 Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

14.8 Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

14.9 Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

14.10Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

14.11Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

15 Operation Scenarios 221

15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

15.2 Operation Scenarios Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

15.3 How to use Operation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

15.3.1 How to create an Operation Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 223

15.3.2 How to save an Operation Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . 223

DIgSILENT PowerFactory 2016, User Manual ix

CONTENTS

15.3.3 How to activate an existing Operation Scenario . . . . . . . . . . . . . . . . . . . 225

15.3.4 How to deactivate an Operation Scenario . . . . . . . . . . . . . . . . . . . . . . 225

15.3.5 How to identify operational data parameters . . . . . . . . . . . . . . . . . . . . . 226

15.4 Administering Operation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

15.4.1 How to view objects missing from the Operation Scenario data . . . . . . . . . . 226

15.4.2 How to compare the data in two operation scenarios . . . . . . . . . . . . . . . . 227

15.4.3 How to view the non-default Running Arrangements . . . . . . . . . . . . . . . . 227

15.4.4 How to transfer data from one Operation Scenario to another . . . . . . . . . . . 227

15.4.5 How to update the default data with operation scenario data . . . . . . . . . . . . 228

15.4.6 How exclude a grid from the Operation Scenario data . . . . . . . . . . . . . . . 228

15.4.7 How to create a time based Operation Scenario . . . . . . . . . . . . . . . . . . . 229

15.5 Advanced Configuration of Operation Scenarios . . . . . . . . . . . . . . . . . . . . . . . 230

15.5.1 How to change the automatic save settings for Operation Scenarios . . . . . . . 231

15.5.2 How to modify the data stored in Operation Scenarios . . . . . . . . . . . . . . . 231

16 Network Variations and Expansion Stages 233

16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

16.2 Variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

16.3 Expansion Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

16.4 The Study Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

16.5 The Recording Expansion Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

16.6 The Variation Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

16.7 Variation and Expansion Stage Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

16.8 Variation and Expansion Stage Housekeeping . . . . . . . . . . . . . . . . . . . . . . . . 238

16.8.1 Applying Changes from Expansion Stages . . . . . . . . . . . . . . . . . . . . . . 238

16.8.2 Consolidating Variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

16.8.3 Splitting Expansion Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

16.8.4 Comparing Variations and Expansion Stages . . . . . . . . . . . . . . . . . . . . 239

16.8.5 Colouring Variations the Single Line Graphic . . . . . . . . . . . . . . . . . . . . . 240

16.8.6 Variation Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

16.8.7 Error Correction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

16.9 Compatibility with Previous PowerFactory

Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

x DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

16.9.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

16.9.2 Converting System Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

17 Parameter Characteristics,
Load States, and Tariffs 247

17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

17.2 Parameter Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

17.2.1 Time Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

17.2.2 Profile Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

17.2.3 Scaling Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

17.2.4 Linear Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

17.2.5 Vector Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

17.2.6 Matrix Parameter Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

17.2.7 Parameter Characteristics from Files . . . . . . . . . . . . . . . . . . . . . . . . . 255

17.2.8 Characteristic References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

17.2.9 Edit Characteristic Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

17.2.10 Browser in ’Scales’ mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

17.2.11 Example Application of Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 257

17.3 Load States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

17.3.1 Creating Load States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

17.3.2 Viewing Existing Load States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

17.3.3 Load State Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

17.3.4 Example Load States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

17.4 Load Distribution States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

17.4.1 Creating Load Distribution States . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

17.4.2 Viewing Existing Load Distribution States . . . . . . . . . . . . . . . . . . . . . . 264

17.4.3 Load Distribution State Object Properties . . . . . . . . . . . . . . . . . . . . . . 264

17.4.4 Example Load Distribution States . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

17.5 Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

17.5.1 Defining Time Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

17.5.2 Defining Energy Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

18 Reporting and Visualising Results 269

18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

DIgSILENT PowerFactory 2016, User Manual xi

CONTENTS

18.2 Results, Graphs and Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

18.2.1 Editing Result Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

18.2.2 Output of Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

18.2.3 Output of Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

18.2.4 Result Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

18.3 Comparisons Between Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

18.3.1 Editing a Set Of Comparison Cases . . . . . . . . . . . . . . . . . . . . . . . . . 276

18.3.2 Update Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

18.4 Variable Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

18.4.1 The Variable Selection Monitor Dialog . . . . . . . . . . . . . . . . . . . . . . . . 278

18.4.2 Searching the Variables to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 279

18.4.3 Examples of Variable Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

18.4.4 Selecting the Bus to be Monitored . . . . . . . . . . . . . . . . . . . . . . . . . . 285

18.5 Virtual Instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

18.5.1 Virtual Instrument Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

18.5.2 Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

18.5.3 Calculated Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

18.5.4 Digital Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

18.5.5 Fault Recorder View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

18.5.6 The Vector Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

18.5.7 The Voltage Profile Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

18.5.8 Schematic Visualisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

18.5.9 The Waveform Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

18.5.10 The Curve-Input Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

18.5.11 Embedded Graphic Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

18.5.12 Tools for Virtual Instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

18.5.13 User-Defined Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

19 Data Management 329

19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

19.2 Project Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

19.2.1 What is a Version? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

19.2.2 How to Create a Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

xii DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

19.2.3 How to Rollback a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

19.2.4 How to Check if a Version is the Base for a Derived Project . . . . . . . . . . . . 331

19.2.5 How to Delete a Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

19.3 Derived Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

19.3.1 Derived Projects Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

19.3.2 How to Create a Derived Project . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

19.4 Comparing and Merging Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

19.4.1 Compare and Merge Tool Background . . . . . . . . . . . . . . . . . . . . . . . . 335

19.4.2 How to Merge or Compare Two Projects Using the Compare and Merge Tool . . 335

19.4.3 How to Merge or Compare Three Projects Using the Compare and Merge Tool . 336

19.4.4 Compare and Merge Tool Advanced Options . . . . . . . . . . . . . . . . . . . . 338

19.4.5 Compare and Merge Tool ’diff browser’ . . . . . . . . . . . . . . . . . . . . . . . . 338

19.5 How to Update a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

19.5.1 Updating a Derived Project from a new Version . . . . . . . . . . . . . . . . . . . 344

19.5.2 Updating a Base Project from a Derived Project . . . . . . . . . . . . . . . . . . . 345

19.5.3 Tips for Working with the Compare and Merge Tool . . . . . . . . . . . . . . . . . 345

19.6 Sharing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

19.7 Database Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

20 Task Automation 349

20.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

20.2 Configuration of Task Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

20.2.1 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

20.2.2 Parallel Computing Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

20.2.3 Output Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

20.3 Task Automation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

20.4 Parallel Computing Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

20.4.1 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

20.4.2 Communication page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

21 Scripting 357

21.1 The DIgSILENT Programming Language - DPL . . . . . . . . . . . . . . . . . . . . . . . 357

21.1.1 The Principle Structure of a DPL Command . . . . . . . . . . . . . . . . . . . . . 358

DIgSILENT PowerFactory 2016, User Manual xiii

CONTENTS

21.1.2 The DPL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

21.1.3 The DPL Script Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

21.1.4 The DPL Script Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

21.1.5 Access to Other Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

21.1.6 Access to Locally Stored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

21.1.7 Accessing the General Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

21.1.8 Accessing External Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

21.1.9 Remote Scripts and DPL Command Libraries . . . . . . . . . . . . . . . . . . . . 369

21.1.10 DPL Functions and Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

21.2 Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

21.2.1 Installation of a Python Interpreter . . . . . . . . . . . . . . . . . . . . . . . . . . 373

21.2.2 The Python PowerFactory Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

21.2.3 The Python Command (ComPython) . . . . . . . . . . . . . . . . . . . . . . . . . 375

21.2.4 Running PowerFactory in Unattended Mode . . . . . . . . . . . . . . . . . . . . . 378

21.2.5 Debugging Python Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

21.2.6 Example of a Python Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

22 Interfaces 381

22.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

22.2 DGS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

22.2.1 DGS Interface Typical Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 382

22.2.2 DGS Structure (Database Schemas and File Formats) . . . . . . . . . . . . . . . 383

22.2.3 DGS Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

22.2.4 DGS Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

22.3 PSS/E File Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

22.3.1 Importing PSS/E Steady-State Data . . . . . . . . . . . . . . . . . . . . . . . . . 387

22.3.2 Import of PSS/E file (Dynamic Data) . . . . . . . . . . . . . . . . . . . . . . . . . 389

22.3.3 Exporting a project to a PSS/E file . . . . . . . . . . . . . . . . . . . . . . . . . . 391

22.4 ELEKTRA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

22.4.1 Import of Elektra Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

22.4.2 General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

22.4.3 Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

22.4.4 Importing Elektra Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

xiv DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

22.4.5 Importing Elektra Type Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

22.4.6 Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

22.5 NEPLAN Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

22.5.1 Importing NEPLAN Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

22.6 INTEGRAL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

22.6.1 Importing Integral Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

22.6.2 Export Integral Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

22.7 UCTE-DEF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

22.7.1 Importing UCTE-DEF Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

22.7.2 Exporting UCTE-DEF Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

22.8 CIM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

22.8.1 Importing CIM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

22.8.2 General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

22.8.3 Exporting CIM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

22.9 CGMES Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

22.9.1 CIM Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

22.9.2 CIM Data Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

22.9.3 CIM to Grid Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

22.9.4 Grid to CIM Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

22.9.5 Conversion to Bus-Branch Models . . . . . . . . . . . . . . . . . . . . . . . . . . 403

22.9.6 CIM Data Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

22.10MATLAB Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

22.11OPC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

22.11.1 OPC Interface Typical Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 405

22.12StationWare Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

22.12.1 About StationWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

22.12.2 Component Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

22.12.3 Fundamental Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

22.12.4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

22.12.5 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

22.12.6 DPL Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

22.12.7 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

DIgSILENT PowerFactory 2016, User Manual xv

CONTENTS

22.13API (Application Programming Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

IV Power System Analysis Functions 433

23 Load Flow Analysis 435

23.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

23.2 Technical Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

23.2.1 Network Representation and Calculation Methods . . . . . . . . . . . . . . . . . 439

23.3 Executing Load Flow Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

23.3.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

23.3.2 Active Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

23.3.3 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

23.3.4 Iteration Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

23.3.5 Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

23.3.6 Load/Generation Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

23.3.7 Low Voltage Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452

23.3.8 Advanced Simulation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

23.4 Detailed Description of Load Flow Calculation Options . . . . . . . . . . . . . . . . . . . . 453

23.4.1 Active and Reactive Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . 453

23.4.2 Advanced Load Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

23.4.3 Temperature Dependency of Lines and Cables . . . . . . . . . . . . . . . . . . . 462

23.5 Result Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

23.5.1 Viewing Results in the Single Line Diagram . . . . . . . . . . . . . . . . . . . . . 463

23.5.2 Flexible Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

23.5.3 Predefined Report Formats (ASCII Reports) . . . . . . . . . . . . . . . . . . . . . 464

23.5.4 Diagram Colouring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

23.5.5 Load Flow Sign Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

23.5.6 Results for Unbalanced Load Flow Calculations . . . . . . . . . . . . . . . . . . . 466

23.6 Troubleshooting Load Flow Calculation Problems . . . . . . . . . . . . . . . . . . . . . . 466

23.6.1 General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

23.6.2 Data Model Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469

23.6.3 Some Load Flow Calculation Messages . . . . . . . . . . . . . . . . . . . . . . . 469

23.6.4 Too many Inner Loop Iterations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

xvi DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

23.6.5 Too Many Outer Loop Iterations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

23.7 Load Flow Sensitivities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

23.7.1 Load Flow Sensitivities Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

23.7.2 Load Flow Sensitivities Execution and Results . . . . . . . . . . . . . . . . . . . . 475

23.7.3 Technical Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

24 Short-Circuit Analysis 479

24.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

24.2 Technical Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

24.2.1 The IEC 60909/VDE 0102 Method . . . . . . . . . . . . . . . . . . . . . . . . . . 483

24.2.2 The ANSI Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

24.2.3 The Complete Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

24.2.4 The IEC 61363 Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490

24.2.5 The IEC 61660 (DC) Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

24.2.6 The ANSI/IEEE 946 (DC) Method . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

24.3 Executing Short-Circuit Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

24.3.1 Toolbar/Main Menu Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

24.3.2 Context-Sensitive Menu Execution . . . . . . . . . . . . . . . . . . . . . . . . . . 494

24.3.3 Faults on Busbars/Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

24.3.4 Faults on Lines and Branches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

24.3.5 Multiple Faults Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

24.4 Short-Circuit Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

24.4.1 Basic Options (All Methods) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

24.4.2 Verification (Except for IEC 61363, IEC 61660 and ANSI/IEEE 946) . . . . . . . . 500

24.4.3 Basic Options (IEC 60909/VDE 0102 Method) . . . . . . . . . . . . . . . . . . . . 500

24.4.4 Advanced Options (IEC 60909/VDE 0102 Method) . . . . . . . . . . . . . . . . . 501

24.4.5 Basic Options (ANSI C37 Method) . . . . . . . . . . . . . . . . . . . . . . . . . . 503

24.4.6 Advanced Options (ANSI C37 Method) . . . . . . . . . . . . . . . . . . . . . . . . 504

24.4.7 Basic Options (Complete Method) . . . . . . . . . . . . . . . . . . . . . . . . . . 505

24.4.8 Advanced Options (Complete Method) . . . . . . . . . . . . . . . . . . . . . . . . 505

24.4.9 Basic Options (IEC 61363) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

24.4.10 Advanced Options (IEC 61363) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507

24.4.11 Basic Options (IEC 61660 Method) . . . . . . . . . . . . . . . . . . . . . . . . . . 507

DIgSILENT PowerFactory 2016, User Manual xvii

CONTENTS

24.4.12 Advanced Options (IEC 61660 Method) . . . . . . . . . . . . . . . . . . . . . . . 508

24.4.13 Basic Options (ANSI/IEEE 946 Method) . . . . . . . . . . . . . . . . . . . . . . . 508

24.4.14 Advanced Options (ANSI/IEEE 946 Method) . . . . . . . . . . . . . . . . . . . . . 509

24.5 Result Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

24.5.1 Viewing Results in the Single Line Diagram . . . . . . . . . . . . . . . . . . . . . 509

24.5.2 Flexible Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510

24.5.3 Predefined Report Formats (ASCII Reports) . . . . . . . . . . . . . . . . . . . . . 510

24.5.4 Diagram Colouring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

24.6 Capacitive Earth-Fault Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

25 Power Quality and Harmonics Analysis 513

25.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

25.2 Harmonic Load Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514

25.2.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514

25.2.2 IEC 61000-3-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

25.2.3 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

25.3 Frequency Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

25.3.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

25.3.2 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518

25.4 Filter Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518

25.5 Modelling Harmonic Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

25.5.1 Definition of Harmonic Injections . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

25.5.2 Assignment of Harmonic Injections . . . . . . . . . . . . . . . . . . . . . . . . . . 525

25.5.3 Harmonics Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

25.5.4 Frequency Dependent Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 528

25.5.5 Waveform Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

25.6 Flicker Analysis (IEC 61400-21) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

25.6.1 Continuous Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

25.6.2 Switching Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

25.6.3 Flicker Contribution of Wind Turbine Generator Models . . . . . . . . . . . . . . . 532

25.6.4 Definition of Flicker Coefficients . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

25.6.5 Assignment of Flicker Coefficients . . . . . . . . . . . . . . . . . . . . . . . . . . 533

25.6.6 Flicker Result Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534

xviii DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

25.7 Short-Circuit Power Sk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534

25.7.1 Balanced Harmonic Load Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

25.7.2 Unbalanced Harmonic Load Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

25.7.3 Sk Result Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

25.7.4 Short-Circuit Power of the External Grid . . . . . . . . . . . . . . . . . . . . . . . 536

25.8 Connection Request Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536

25.8.1 Connection Request Assessment: D-A-CH-CZ . . . . . . . . . . . . . . . . . . . 536

25.8.2 Connection Request Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

25.8.3 Connection Request Assessment Report . . . . . . . . . . . . . . . . . . . . . . 540

25.9 Definition of Result Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

25.9.1 Definition of Variable Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

25.9.2 Selection of Result Variables within a Variable Set . . . . . . . . . . . . . . . . . 542

26 Flickermeter 545

26.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

26.2 Flickermeter (IEC 61000-4-15) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

26.2.1 Calculation of Short-Term Flicker . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

26.2.2 Calculation of Long-Term Flicker . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

26.3 Flickermeter Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

26.3.1 Flickermeter Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

26.3.2 Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

26.3.3 Signal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

26.3.4 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548

26.3.5 Input File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549

27 Quasi-Dynamic Simulation 553

27.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

27.2 Technical background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554

27.3 How to complete a

Quasi-Dynamic Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

27.3.1 Defining the variables for monitoring in the Quasi dynamic simulation . . . . . . . 555

27.3.2 Running the Quasi dynamic simulation . . . . . . . . . . . . . . . . . . . . . . . . 556

27.3.3 Considering maintenance outages . . . . . . . . . . . . . . . . . . . . . . . . . . 557

27.3.4 Configuring the Quasi Dynamic Simulation for parallel computation . . . . . . . . 557

DIgSILENT PowerFactory 2016, User Manual xix

CONTENTS

27.4 Analysing the Quasi-dynamic

simulation results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

27.4.1 Plotting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

27.4.2 Quasi-Dynamic simulation reports . . . . . . . . . . . . . . . . . . . . . . . . . . 558

27.4.3 Statistical summary of monitored variables . . . . . . . . . . . . . . . . . . . . . . 559

28 Stability and EMT Simulations 561

28.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561

28.2 Calculation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

28.2.1 Balanced RMS Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

28.2.2 Three-Phase RMS Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

28.2.3 Three-Phase EMT Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564

28.3 Setting Up a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564

28.3.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

28.3.2 Step Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

28.3.3 Solver Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567

28.3.4 Noise Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570

28.3.5 Advanced Simulation Options - Load Flow . . . . . . . . . . . . . . . . . . . . . . 570

28.4 Result Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

28.4.1 Saving Results from Previous Simulations . . . . . . . . . . . . . . . . . . . . . . 573

28.5 Simulation Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

28.5.1 Frequency Scan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

28.5.2 Synchronous Machine Speed Scan Module . . . . . . . . . . . . . . . . . . . . . 574

28.5.3 Loss of Synchronism Scan Module . . . . . . . . . . . . . . . . . . . . . . . . . . 574

28.5.4 Variable Scan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

28.5.5 Voltage Scan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

28.5.6 Simulation scan example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575

28.6 Events (IntEvt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

28.7 Running a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

28.8 Frequency Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580

28.8.1 Prony Analysis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580

28.8.2 Basic Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

28.8.3 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

xx DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

28.8.4 FFT Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584

28.8.5 Prony Analysis Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586

28.8.6 Recalculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

28.8.7 Output Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

28.8.8 Output Result Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

28.8.9 General Recommendations on the Use of Prony Analysis . . . . . . . . . . . . . 590

28.8.10 Quick Overview of Used Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . 593

28.9 Models for Stability Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

28.10System Modelling Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

28.10.1 The Composite Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600

28.10.2 The Composite Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

28.10.3 The Common Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

28.11The Composite Block Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

28.11.1 Drawing Composite Block Diagrams and Composite Frames . . . . . . . . . . . 612

28.12User Defined (DSL) Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

28.12.1 Modelling and Simulation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

28.12.2 DSL Implementation: an Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 620

28.12.3 Defining DSL Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624

28.12.4 Encrypting a DSL Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

28.13The DIgSILENT Simulation Language (DSL) . . . . . . . . . . . . . . . . . . . . . . . . . 627

28.13.1 Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

28.13.2 General DSL Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

28.13.3 DSL Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

28.13.4 DSL Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

28.13.5 Definition Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

28.13.6 Initial Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

28.13.7 Equation Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633

28.13.8 Equation Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633

28.13.9 DSL Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

28.13.10Events and Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

28.13.11DSL Modelling Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637

28.13.12Example of a Complete DSL Model . . . . . . . . . . . . . . . . . . . . . . . . . 638

DIgSILENT PowerFactory 2016, User Manual xxi

CONTENTS

28.14DSL Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

28.14.1 DSL Standard Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

28.14.2 DSL Special Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

28.15C Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

28.15.1 C Interface Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

28.16MATLAB Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

28.16.1 Example Implementation of Voltage Controller . . . . . . . . . . . . . . . . . . . 648

28.16.2 Additional notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

29 Modal Analysis / Eigenvalue Calculation 657

29.1 Theory of Modal Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

29.2 How to Complete a Modal Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660

29.2.1 Completing a Modal Analysis with the Default Options . . . . . . . . . . . . . . . 660

29.2.2 Modal Analysis command - Basic Options . . . . . . . . . . . . . . . . . . . . . . 660

29.2.3 Modal Analysis command - Advanced Options . . . . . . . . . . . . . . . . . . . 662

29.2.4 Modal Analysis command - Output . . . . . . . . . . . . . . . . . . . . . . . . . . 663

29.3 Viewing Modal Analysis Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663

29.3.1 Viewing Modal Analysis Reports in the Output Window . . . . . . . . . . . . . . . 664

29.3.2 Viewing Modal Analysis Results using the built-in Plots . . . . . . . . . . . . . . . 666

29.3.3 Viewing Modal Analysis Results using the Modal Data Browser . . . . . . . . . . 670

29.3.4 Viewing Results in the Data Manager Window . . . . . . . . . . . . . . . . . . . . 672

29.4 Troubleshooting Modal Analysis Calculation Problems . . . . . . . . . . . . . . . . . . . . 674

29.4.1 The Arnoldi/Lanczos Method is slow . . . . . . . . . . . . . . . . . . . . . . . . . 674

30 Model Parameter Identification 675

30.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

30.2 Target Functions and Composite Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . 676

30.2.1 The Measurement File Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677

30.2.2 Power System Element Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677

30.2.3 Comparison Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677

30.3 Creating The Composite Identification Model . . . . . . . . . . . . . . . . . . . . . . . . . 678

30.3.1 The Comparison Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679

30.4 Performing a Parameter Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680

xxii DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

30.5 Identifying Primary Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

31 Contingency Analysis 685

31.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685

31.2 Technical Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685

31.2.1 Single Time Phase Contingency Analysis . . . . . . . . . . . . . . . . . . . . . . 688

31.2.2 Multiple Time Phases Contingency Analysis . . . . . . . . . . . . . . . . . . . . . 688

31.2.3 Time Sweep Option (Single Time Phase) . . . . . . . . . . . . . . . . . . . . . . 689

31.2.4 Consideration of Predefined Switching Rules . . . . . . . . . . . . . . . . . . . . 689

31.2.5 Parallel Computing Option (Single Time Phase) . . . . . . . . . . . . . . . . . . . 689

31.3 Executing Contingency Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

31.4 The Single Time Phase Contingency Analysis Command . . . . . . . . . . . . . . . . . . 691

31.4.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692

31.4.2 Effectiveness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693

31.4.3 Multiple Time Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694

31.4.4 Time Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

31.4.5 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

31.4.6 Parallel Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696

31.4.7 Calculating an Individual Contingency . . . . . . . . . . . . . . . . . . . . . . . . 697

31.4.8 Representing Contingency Situations

Contingency Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697

31.5 The Multiple Time Phases Contingency Analysis Command . . . . . . . . . . . . . . . . 699

31.5.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

31.5.2 Effectiveness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

31.5.3 Multiple Time Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

31.5.4 Time Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701

31.5.5 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702

31.5.6 Parallel Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702

31.5.7 Defining Time Phases for Contingency Analysis . . . . . . . . . . . . . . . . . . . 702

31.5.8 Representing Contingency Situations with Post - Fault Actions . . . . . . . . . . . 703

31.6 Creating Contingency Cases Using Fault

Cases and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704

31.6.1 Browsing Fault Cases and Fault Groups . . . . . . . . . . . . . . . . . . . . . . . 705

DIgSILENT PowerFactory 2016, User Manual xxiii

CONTENTS

31.6.2 Defining a Fault Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

31.6.3 Defining a Fault Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

31.7 Creating Contingency Cases Using the

Contingency Definition Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707

31.8 Comparing Contingency Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

31.9 Result Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711

31.9.1 Predefined Report Formats (Tabular and ASCII Reports) . . . . . . . . . . . . . . 711

32 Reliability Assessment 715

32.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715

32.2 Probabilistic Reliability Assessment

Technical Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

32.2.1 Reliability Assessment Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 718

32.2.2 Stochastic Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719

32.2.3 Calculated Results for Reliability Assessment . . . . . . . . . . . . . . . . . . . . 720

32.2.4 System State Enumeration in Reliability Assessment . . . . . . . . . . . . . . . . 725

32.3 Setting up the Network Model for Reliability Assessment . . . . . . . . . . . . . . . . . . 726

32.3.1 How to Define Stochastic Failure and Repair models . . . . . . . . . . . . . . . . 727

32.3.2 How to Create Feeders for Reliability Calculation . . . . . . . . . . . . . . . . . . 732

32.3.3 Configuring Switches for the Reliability Calculation . . . . . . . . . . . . . . . . . 733

32.3.4 Load Modelling for Reliability Assessment . . . . . . . . . . . . . . . . . . . . . . 734

32.3.5 Modelling Load Interruption Costs . . . . . . . . . . . . . . . . . . . . . . . . . . 736

32.3.6 System Demand and Load States (ComLoadstate) . . . . . . . . . . . . . . . . . 736

32.3.7 Fault Clearance Based on Protection Device Location . . . . . . . . . . . . . . . 736

32.3.8 How to Consider Planned Maintenance . . . . . . . . . . . . . . . . . . . . . . . 736

32.3.9 Specifying Individual Component Constraints . . . . . . . . . . . . . . . . . . . . 737

32.4 Running The Reliability Assessment Calculation . . . . . . . . . . . . . . . . . . . . . . . 737

32.4.1 How to run the Reliability Assessment . . . . . . . . . . . . . . . . . . . . . . . . 737

32.5 Results of the Reliability Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

32.5.1 Contribution to Reliability Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

32.5.2 Viewing Results in the Single Line Diagram . . . . . . . . . . . . . . . . . . . . . 745

32.5.3 Viewing Results in the Data Browser . . . . . . . . . . . . . . . . . . . . . . . . . 747

32.5.4 Reliability Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

xxiv DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

33 Optimal Power Restoration 749

33.1 Failure Effect Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749

33.2 Animated Tracing of Individual Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754

33.3 Optimal RCS Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754

33.3.1 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755

33.3.2 Output Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

33.3.3 Advanced Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

33.3.4 Example Optimal RCS Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . 756

33.4 Optimal Manual Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

33.4.1 OMR Calculation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758

33.4.2 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758

33.4.3 Advanced Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759

33.4.4 Definition of the objective function . . . . . . . . . . . . . . . . . . . . . . . . . . . 760

33.4.5 Example of an Optimal Manual Restoration Calculation . . . . . . . . . . . . . . . 761

34 Generation Adequacy Analysis 763

34.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

34.2 Technical Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

34.3 Database Objects and Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

34.3.1 Stochastic Model for Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

34.3.2 Power Curve Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

34.3.3 Meteorological station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

34.4 Assignment of Stochastic Model for Generation . . . . . . . . . . . . . . . . . . . . . . . 768

34.4.1 Definition of a Stochastic Multi-State Model . . . . . . . . . . . . . . . . . . . . . 768

34.4.2 Stochastic Wind Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769

34.4.3 Time Series Characteristic for Wind Generation . . . . . . . . . . . . . . . . . . . 769

34.4.4 Demand definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

34.5 Generation Adequacy Analysis toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772

34.5.1 Generation Adequacy Initialisation command . . . . . . . . . . . . . . . . . . . . 772

34.5.2 Run Generation Adequacy command . . . . . . . . . . . . . . . . . . . . . . . . . 774

34.6 Generation Adequacy results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

34.6.1 Distribution (Cumulative Probability) Plots . . . . . . . . . . . . . . . . . . . . . . 775

34.6.2 Monte-Carlo Draws (Iterations) Plots . . . . . . . . . . . . . . . . . . . . . . . . . 777

DIgSILENT PowerFactory 2016, User Manual xxv

CONTENTS

34.6.3 Convergence Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778

34.6.4 Summary of variables calculated during the Generation Adequacy Analysis . . . 780

35 Optimal Power Flow 781

35.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781

35.2 AC Optimisation (Interior Point Method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781

35.2.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781

35.2.2 Initialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794

35.2.3 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794

35.2.4 Iteration Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794

35.2.5 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796

35.3 DC Optimisation (Linear Programming) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797

35.3.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798

35.3.2 Initialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802

35.3.3 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803

35.3.4 Iteration Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803

35.4 Contingency Constrained DC Optimisation (LP Method) . . . . . . . . . . . . . . . . . . . 804

35.4.1 Basic Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805

35.4.2 Initialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808

35.4.3 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809

35.4.4 Iteration Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809

35.4.5 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809

36 Transmission Network Tools 811

36.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811

36.2 PV Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812

36.2.1 PV Curves Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813

36.2.2 PV Curves Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814

36.2.3 Outputs and Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815

36.3 QV Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816

36.3.1 QV Curves Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817

36.3.2 QV Curves Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818

36.4 Power Transfer Distribution Factors (PTDF) . . . . . . . . . . . . . . . . . . . . . . . . . . 819

xxvi DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

36.4.1 Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819

36.5 Transfer Capacity Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

36.5.1 Basic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

36.5.2 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

36.5.3 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822

36.5.4 Iteration Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822

36.5.5 Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822

37 Techno-Economical Calculation 825

37.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825

37.2 Requirements for Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826

37.3 Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826

37.3.1 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826

37.3.2 Costs Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

37.3.3 Output Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

37.3.4 Parallel Computing Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

37.4 Example Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

38 Distribution Network Tools 833

38.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833

38.2 Voltage Sag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833

38.2.1 Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834

38.2.2 How to Perform a Voltage Sag Table Assessment . . . . . . . . . . . . . . . . . . 834

38.2.3 Voltage Sag Table Assessment Results . . . . . . . . . . . . . . . . . . . . . . . 835

38.3 Voltage Profile Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837

38.3.1 Optimisation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837

38.3.2 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840

38.3.3 Output Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841

38.3.4 Advanced Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841

38.3.5 Results of Voltage Profile Optimisation . . . . . . . . . . . . . . . . . . . . . . . . 841

38.4 Tie Open Point Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842

38.4.1 Tie Open Point Optimisation Background . . . . . . . . . . . . . . . . . . . . . . . 842

38.4.2 How to run a Tie Open Point Optimisation . . . . . . . . . . . . . . . . . . . . . . 843

DIgSILENT PowerFactory 2016, User Manual xxvii

CONTENTS

38.5 Backbone Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846

38.5.1 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

38.5.2 Scoring Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848

38.5.3 Tracing Backbones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849

38.5.4 Example Backbone Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849

38.6 Optimal Capacitor Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850

38.6.1 OCP Objective Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851

38.6.2 OCP Optimisation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853

38.6.3 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853

38.6.4 Available Capacitors Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854

38.6.5 Load Characteristics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855

38.6.6 Advanced Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855

38.6.7 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856

38.7 Phase Balance Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857

38.7.1 Objective functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858

38.7.2 Optimisation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858

38.7.3 Considered elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859

38.7.4 Representation of solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859

38.7.5 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860

39 Cable Analysis 861

39.1 Cable Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861

39.2 Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862

39.2.1 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862

39.2.2 Constraints Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863

39.2.3 Output Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864

39.2.4 Advanced Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866

39.2.5 Type Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867

39.3 Cable Ampacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868

39.3.1 Cable Ampacity calculation options . . . . . . . . . . . . . . . . . . . . . . . . . . 868

39.4 Cable Analysis: Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869

39.4.1 Cable Analysis: Line Type Parameters . . . . . . . . . . . . . . . . . . . . . . . . 869

39.4.2 Cable Analysis: Line Element Parameters . . . . . . . . . . . . . . . . . . . . . . 870

xxviii DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

39.4.3 Cable Analysis: Cable System Parameters . . . . . . . . . . . . . . . . . . . . . . 870

39.4.4 Cable Analysis: Single Core Cable Parameters . . . . . . . . . . . . . . . . . . . 870

39.5 Reporting command (ComCablereport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871

40 Motor Starting 873

40.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873

40.2 How to define a motor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873

40.2.1 How to define a motor Type and starting methodology . . . . . . . . . . . . . . . 873

40.2.2 How to define a motor driven machine . . . . . . . . . . . . . . . . . . . . . . . . 875

40.3 How to run a Motor Starting simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876

40.3.1 Basic Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876

40.3.2 Output Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878

40.3.3 Motor Starting simulation results . . . . . . . . . . . . . . . . . . . . . . . . . . . 879

40.3.4 Motor Starting Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880

41 Arc-Flash Hazard Analysis 883

41.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883

41.2 Arc-Flash Hazard Analysis Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883

41.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883

41.2.2 Data Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884

41.3 Arc-Flash Hazard Analysis Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . 885

41.3.1 Arc-Flash Hazard Analysis Basic Options Page . . . . . . . . . . . . . . . . . . . 885

41.3.2 Arc-Flash Hazard Analysis Advanced Options Page . . . . . . . . . . . . . . . . 886

41.4 Arc-Flash Hazard Analysis Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887

41.4.1 Viewing Results in the Single Line Graphic . . . . . . . . . . . . . . . . . . . . . . 887

41.4.2 Arc-Flash Reports Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887

41.4.3 Arc-Flash Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888

41.5 Example Arc-Flash Hazard Analysis Calculation . . . . . . . . . . . . . . . . . . . . . . . 888

42 Protection 891

42.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891

42.1.1 The modelling structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891

42.1.2 The relay frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892

42.1.3 The relay type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893

DIgSILENT PowerFactory 2016, User Manual xxix

CONTENTS

42.1.4 The relay element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894

42.2 How to define a protection

scheme in PowerFactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895

42.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895

42.2.2 Adding protective devices to the network model . . . . . . . . . . . . . . . . . . . 895

42.2.3 Protection single line diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899

42.2.4 Locating protection devices within

the network model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901

42.3 Setup of an overcurrent

protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902

42.3.1 Overcurrent relay model setup - basic data page . . . . . . . . . . . . . . . . . . 902

42.3.2 Overcurrent relay model setup - max/min fault

currents tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904

42.3.3 Configuring the current transformer . . . . . . . . . . . . . . . . . . . . . . . . . . 904

42.3.4 Configuring the voltage transformer . . . . . . . . . . . . . . . . . . . . . . . . . . 906

42.3.5 How to add a fuse to the network model . . . . . . . . . . . . . . . . . . . . . . . 908

42.3.6 Basic relay blocks for overcurrent relays . . . . . . . . . . . . . . . . . . . . . . . 910

42.4 The time-overcurrent plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914

42.4.1 How to create a time-overcurrent plot . . . . . . . . . . . . . . . . . . . . . . . . . 915

42.4.2 Understanding the time-overcurrent plot . . . . . . . . . . . . . . . . . . . . . . . 916

42.4.3 Showing the calculation results on the time-overcurrent plot . . . . . . . . . . . . 916

42.4.4 Displaying the grading margins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917

42.4.5 Adding a user defined permanent current line to the time-overcurrent plot . . . . 918

42.4.6 Configuring the auto generated protection diagram . . . . . . . . . . . . . . . . . 918

42.4.7 Overcurrent plot options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918

42.4.8 Altering protection device characteristic settings from the time-overcurrent plot . 920

42.4.9 How to split the relay/fuse characteristic . . . . . . . . . . . . . . . . . . . . . . . 921

42.4.10 Equipment damage curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924

42.5 Setup and analysis of a distance

protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937

42.5.1 Distance relay model setup - basic data page . . . . . . . . . . . . . . . . . . . . 937

42.5.2 Primary or secondary Ohm selection for distance relay parameters . . . . . . . . 937

42.5.3 Basic relay blocks used for distance protection . . . . . . . . . . . . . . . . . . . 938

42.6 The impedance plot (R-X diagram) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945

xxx DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

42.6.1 How to create an R-X diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945

42.6.2 Understanding the R-X diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946

42.6.3 Configuring the R-X plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947

42.6.4 Modifying the relay settings and branch elements from the R-X plot . . . . . . . . 951

42.7 The time-distance plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951

42.8 Setup of the differential protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . 955

42.8.1 Differential relay model setup-basic data page . . . . . . . . . . . . . . . . . . . . 955

42.8.2 Basic relay blocks used for differential protection . . . . . . . . . . . . . . . . . . 956

42.9 Differential Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956

42.9.1 Magnitude biased differential diagram (.VisMagndiffplt) . . . . . . . . . . . . . . . 957

42.9.2 Phase comparison differential diagram (.VisPcompdiffplt) . . . . . . . . . . . . . 958

42.10Distance protection coordination assistant . . . . . . . . . . . . . . . . . . . . . . . . . . 958

42.10.1 Distance protection coordination assistant - technical background . . . . . . . . . 958

42.10.2 Worked example of the distance protection coordination assistant . . . . . . . . . 962

42.10.3 Prerequisites for using the distance protection coordination tool . . . . . . . . . . 964

42.10.4 How to run the distance protection coordination calculation . . . . . . . . . . . . 964

42.10.5 Distance protection coordination options . . . . . . . . . . . . . . . . . . . . . . . 965

42.10.6 How to output results from the protection coordination assistant . . . . . . . . . . 966

42.11Accessing results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968

42.11.1 Quick access to protection plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969

42.11.2 Tabular protection setting report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970

42.11.3 Results in single line graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972

42.12Short circuit trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973

42.12.1 Short Circuit Trace Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974

42.13Building a basic overcurrent relay model . . . . . . . . . . . . . . . . . . . . . . . . . . . 975

42.14Appendix - other commonly used relay blocks . . . . . . . . . . . . . . . . . . . . . . . . 983

42.14.1 The frequency measurement block . . . . . . . . . . . . . . . . . . . . . . . . . . 983

42.14.2 The frequency block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983

42.14.3 The under-/overvoltage block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984

43 Network Reduction 985

43.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985

43.2 Technical Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985

DIgSILENT PowerFactory 2016, User Manual xxxi

CONTENTS

43.2.1 Network Reduction for Load Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . 986

43.2.2 Network Reduction for Short-Circuit (Ward Equivalent only) . . . . . . . . . . . . 986

43.2.3 Network Reduction using REI Method . . . . . . . . . . . . . . . . . . . . . . . . 986

43.3 How to Complete a Network Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986

43.3.1 How to Backup the Project (optional) . . . . . . . . . . . . . . . . . . . . . . . . . 987

43.3.2 How to run the Network Reduction tool . . . . . . . . . . . . . . . . . . . . . . . . 987

43.3.3 Expected Output of the Network Reduction . . . . . . . . . . . . . . . . . . . . . 988

43.4 Network Reduction Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990

43.4.1 Basic Options (Selection of Method) . . . . . . . . . . . . . . . . . . . . . . . . . 990

43.4.2 Basic Options (Ward Equivalent Method) . . . . . . . . . . . . . . . . . . . . . . . 990

43.4.3 Basic Options (REI Method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991

43.4.4 Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992

43.4.5 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993

43.4.6 Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993

43.5 Network Reduction Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994

43.6 Tips for using the Network Reduction Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 995

43.6.1 Station Controller Busbar is Reduced . . . . . . . . . . . . . . . . . . . . . . . . . 995

43.6.2 Network Reduction doesn’t Reduce Isolated Areas . . . . . . . . . . . . . . . . . 996

43.6.3 The Reference Machine is not Reduced . . . . . . . . . . . . . . . . . . . . . . . 996

44 State Estimation 999

44.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999

44.2 Objective Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000

44.3 Components of the PowerFactory State Estimation . . . . . . . . . . . . . . . . . . . . . . 1000

44.3.1 Plausibility Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001

44.3.2 Observability Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002

44.3.3 State Estimation (Non-Linear Optimisation) . . . . . . . . . . . . . . . . . . . . . 1003

44.4 State Estimation Data Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003

44.4.1 Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004

44.4.2 Editing the Element Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008

44.5 Running SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009

44.5.1 Basic Setup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009

44.5.2 Advanced Setup Options for the Plausibility Check . . . . . . . . . . . . . . . . . 1012

xxxii DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

44.5.3 Advanced Setup Options for the Observability Check . . . . . . . . . . . . . . . . 1012

44.5.4 Advanced Setup Options for Bad Data Detection . . . . . . . . . . . . . . . . . . 1012

44.5.5 Advanced Setup Options for Iteration Control . . . . . . . . . . . . . . . . . . . . 1013

44.6 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014

44.6.1 Output Window Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015

44.6.2 External Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015

44.6.3 Estimated States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017

44.6.4 Colour Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018

V Appendix 1021

A Hotkeys Reference 1023

A.1 Calculation Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023

A.2 Graphic Windows Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023

A.3 Data Manager Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025

A.4 Dialog Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027

A.5 Output Window Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027

A.6 Editor Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029

B Technical References of Models 1033

B.1 Branch Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035

B.1.1 2-Winding Transformer (ElmTr2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035

B.1.2 3-Winding Transformer (ElmTr3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035

B.1.3 Autotransformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035

B.1.4 Booster Transformer (ElmTrb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035

B.1.5 Overhead Line Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035

B.1.6 Cable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038

B.1.7 Series Capacitor (ElmScap) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038

B.1.8 Series Reactor (ElmSind) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038

B.1.9 Series RLC-Filter (ElmSfilt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038

B.1.10 Common Impedance (ElmZpu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039

B.2 Generators and Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039

B.2.1 Asynchronous Machine (ElmAsm) . . . . . . . . . . . . . . . . . . . . . . . . . . 1039

DIgSILENT PowerFactory 2016, User Manual xxxiii

CONTENTS

B.2.2 Doubly Fed Induction Machine (ElmAsmsc) . . . . . . . . . . . . . . . . . . . . . 1039

B.2.3 Static Generator (ElmGenstat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039

B.2.4 PV System (ElmPvsys) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

B.2.5 Synchronous Machine (ElmSym) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

B.2.6 Loads (ElmLod) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

B.2.7 Low Voltage Load (ElmLodlv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

B.2.8 Medium Voltage Load (ElmLodmv) . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

B.2.9 Partial Loads (ElmLodlvp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

B.2.10 Motor Driven Machine (ElmMdm__X) . . . . . . . . . . . . . . . . . . . . . . . . . 1041

B.2.11 DC Machine (ElmDcm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041

B.2.12 External Grid (ElmXnet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041

B.3 Power Electronic Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041

B.3.1 PWM AC/DC Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041

B.3.2 Rectifier/Inverter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

B.3.3 Soft Starter (ElmVar) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

B.3.4 DC/DC Converter (ElmDcdc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

B.4 Reactive Power Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

B.4.1 Shunt/Filter Element (ElmShnt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

B.4.2 Static Var System (ElmSvs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

B.5 Load Flow Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

B.5.1 Station Controller (ElmStactrl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

B.5.2 Power Frequency Control (ElmSecctrl) . . . . . . . . . . . . . . . . . . . . . . . . 1043

B.6 Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

B.6.1 AC Voltage Source (ElmVac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

B.6.2 AC Voltage Source/two terminals (ElmVacbi) . . . . . . . . . . . . . . . . . . . . 1043

B.6.3 DC Voltage Source (ElmVdc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

B.6.4 AC Current Source (ElmIac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043

B.6.5 AC Current Source/two terminals (ElmIacbi) . . . . . . . . . . . . . . . . . . . . . 1043

B.6.6 DC Current Source (ElmDci) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

B.6.7 Impulse Source (ElmImpulse) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

B.6.8 DC Battery (ElmBattery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

B.6.9 Fourier Source (ElmFsrc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

xxxiv DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

B.7 Measurement Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

B.7.1 Current Measurement (StaImea) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

B.7.2 Power Measurement (StaPqmea) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

B.7.3 Voltage Measurement (StaVmea) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045

B.7.4 Current Transformer (StaCt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045

B.7.5 Voltage Transformer (StaVt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045

B.7.6 Phase Measurement Device (Phase Locked Loop, ElmPhi__pll) . . . . . . . . . . 1045

B.7.7 Measurement File (ElmFile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045

B.8 Digital Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045

B.8.1 Digital Clock (ElmClock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045

B.8.2 Digital Register (ElmReg) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045

B.8.3 Sample and Hold Model (ElmSamp) . . . . . . . . . . . . . . . . . . . . . . . . . 1046

B.8.4 Trigger Model (ElmTrigger) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046

B.9 Protection Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046

B.9.1 Current Time Characteristic (TypChatoc) . . . . . . . . . . . . . . . . . . . . . . . 1046

B.9.2 Directional Block (RelDir, TypDir) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046

B.9.3 Logic/DIP (RelLogdip, TypLogdip) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046

B.9.4 Recloser Block (RelRecloser, TypRecloser) . . . . . . . . . . . . . . . . . . . . . 1046

B.9.5 Differential Protection (RelBiasidiff) . . . . . . . . . . . . . . . . . . . . . . . . . . 1046

B.9.6 Distance mho (RelDismho, TypDismho) . . . . . . . . . . . . . . . . . . . . . . . 1046

B.9.7 Distance Polygon (RelDispoly, TypDispoly) . . . . . . . . . . . . . . . . . . . . . . 1047

B.9.8 Power Swing (RelDispspoly, TypDispspoly) . . . . . . . . . . . . . . . . . . . . . 1047

B.9.9 ABB starting element (RelFdetabb) . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

B.9.10 Starting/Fault Detector (RelFdetect) . . . . . . . . . . . . . . . . . . . . . . . . . 1047

B.9.11 Siemens starting element (RelFdetsie) . . . . . . . . . . . . . . . . . . . . . . . . 1047

B.9.12 Instantaneous Overcurrent (RelIoc, TypIoc) . . . . . . . . . . . . . . . . . . . . . 1047

B.9.13 Logic Block (RelLogic, TypLogic) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

B.9.14 Measurement Block (RelMeasure, TypMeasure) . . . . . . . . . . . . . . . . . . . 1047

B.9.15 Time Overcurrent (RelToc, TypToc) . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

B.10 Analysis Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048

B.10.1 Fast Fourier Transform (ElmFft) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048

B.11 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048

DIgSILENT PowerFactory 2016, User Manual xxxv

CONTENTS

B.11.1 Neutral Earthing Element (ElmNec) . . . . . . . . . . . . . . . . . . . . . . . . . . 1048

B.11.2 Surge Arrester (StaSua) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048

B.12 Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048

B.12.1 Wind Turbine Templates according to IEC 61400-27-1 . . . . . . . . . . . . . . . 1048

B.12.2 WECC Wind Turbine Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048

B.12.3 Generic Doubly Fed Induction Generator . . . . . . . . . . . . . . . . . . . . . . . 1048

B.12.4 Generic Fully Rated Wind Turbine Generator . . . . . . . . . . . . . . . . . . . . 1049

B.12.5 Generic Photovoltaic System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049

B.12.6 Generic Battery Energy Storage System . . . . . . . . . . . . . . . . . . . . . . . 1049

B.12.7 Generic Variable Speed Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049

C Standard Models in PowerFactory 1051

C.1 AVR Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051

C.2 Turbine-Governor Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060

C.3 PSS Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065

C.4 Excitation Limiter Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067

C.5 Static Compensator Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068

C.6 Frames for Dynamic Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070

C.7 Typical Arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071

D The DIgSILENT Output Language 1073

D.1 Format string, Variable names and text Lines . . . . . . . . . . . . . . . . . . . . . . . . . 1074

D.2 Placeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074

D.3 Variables, Units and Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075

D.4 Colour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077

D.5 Advanced Syntax Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077

D.6 Line Types and Page Breaks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078

D.7 Predefined Text Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078

D.8 Object Iterations, Loops, Filters and Includes . . . . . . . . . . . . . . . . . . . . . . . . . 1079

E Element Symbol Definition 1081

E.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081

E.2 General Symbol Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081

E.3 Geometrical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082

xxxvi DIgSILENT PowerFactory 2016, User Manual

 CONTENTS

E.4 Including Graphic Files as Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084

F Standard Functions DPL and DSL 1085

Bibliography 1087

Glossary 1089

Index 1093

DIgSILENT PowerFactory 2016, User Manual xxxvii

CONTENTS

xxxviii DIgSILENT PowerFactory 2016, User Manual

 Part I

General Information
Chapter 1

About this Guide

This User Manual is intended to be a reference for users of the DIgSILENT PowerFactory software. This
chapter provides general information about the contents and the used conventions of this documenta-
tion.

1.1 Contents of the User Manual

The first section of the User Manual provides General Information, including an overview of PowerFac-
tory software, a description of the basic program settings, and a description of the PowerFactory data
model.

The next sections describe PowerFactory administration, handling, and power system analysis func-
tions. In the Power System Analysis Functions section, each chapter deals with a different calculation,
presenting the most relevant theoretical aspects, the PowerFactory approach, and the corresponding
interface.

The online version of this manual includes additional sections dedicated to the mathematical description
of models and their parameters, referred to as Technical References. To facilitate their portability,
visualisation, and printing, the papers are attached to the online help as PDF documents. They are
opened by clicking on the indicated links within the manual. References for DIgSILENT Programming
Language functions are also included as appendices of the online manual.

It is recommended that new users commence by reading Chapter 4 (PowerFactory Overview), and
completing the PowerFactory Tutorials.

1.2 Used Conventions

Conventions to describe user actions are as follows:

Buttons and Keys Dialog buttons and keyboard keys are referred to with bold and underline text
formatting. For example, press the OK button in the PowerFactory dialog, or press CTRL+B on
the keyboard.
Menus and Icons Menus and icons are usually referenced using Italics. For example, press the User
Settings icon , or select Tools → User Settings. . .
Other Items “Speech marks” are used to indicate data to be entered by the user, and also to refer to
an item defined by the author. For example, consider a parameter “x”.

DIgSILENT PowerFactory 2016, User Manual 3

CHAPTER 1. ABOUT THIS GUIDE

4 DIgSILENT PowerFactory 2016, User Manual

Chapter 2

Contact

For further information about the company DIgSILENT , our products and services please visit our web
site, or contact us at:

DIgSILENT GmbH

Heinrich-Hertz-Str. 9

72810 Gomaringen / Germany

www.digsilent.de

2.1 Direct Technical Support

DIgSILENT experts offer direct assistance to PowerFactory users with valid maintenance agreements
via telephone or online via support queries raised on the customer portal.

To register for the on-line portal, select Help → Register. . . or go to directly to the registration page (link
below). Log-in details will be provided by email shortly thereafter.

To log-in to the portal, enter the email (or Login) and Password provided. When raising a new support
query, please include the PowerFactory version and build number in your submission, which can be
found by selecting Help → About PowerFactory. . . from the main menu. Note that including relevant
*.dz or *.pfd file(s) may assist with our investigation into your query. The customer portal is shown in
Figure 2.1.1.

Phone: +49-(0)7072-9168-50 (German)

+49-(0)7072-9168-51 (English)
Portal log-in and Registration: http://www.digsilent.de/index.php/support.html

DIgSILENT PowerFactory 2016, User Manual 5

CHAPTER 2. CONTACT

Figure 2.1.1: DIgSILENT customer portal

2.2 General Information

For general information about DIgSILENT or your PowerFactory licence, please contact us via:

Phone: +49-(0)7072-9168-0

Fax: +49-(0)7072-9168-88
E-mail: [email protected]

6 DIgSILENT PowerFactory 2016, User Manual

Chapter 3

Documentation and Help System

DIgSILENT PowerFactory is provided with a complete help package to support users at all levels of
expertise. Documents with the basic information of the program and its functionality are combined with
references to advanced simulation features, mathematical descriptions of the models and of course
application examples.

PowerFactory offers the following help resources:

• Getting Started: a document describing the first steps to follow after receiving the installation DVD
or downloading the software from the DIgSILENT download area. The Getting Started document
covers the basic installation options.
• Advanced Installation and Configuration Manual: in this document, advanced installation
options e.g. multi-user database, installation on an application server, and the Offline mode
installation, are covered. The Offline mode guide is available in Section 5.5: Offline Mode User
Guide.

• Tutorial: basic information for new users and hands-on tutorial. Access via Help menu of Power-
Factory, and for registered users in the DIgSILENT download area:
http://www.digsilent.de/index.php/downloads.html
• User Manual: this document. Access via Help menu of PowerFactory. Current and previous
manuals (PDF files) can also be found on the in the DIgSILENT download area.

• Technical References: description of the models implemented in PowerFactory for the different
power systems components. The technical reference documents are attached to the online help
(Appendix B: Technical References of Models).
• Additional Packages: additional information and/or examples about specific PowerFactory func-
tions are available on the menu Help → Additional Packages. The additional packages are:
– Programming Interface (API)
– DGS Data Exchange Format
– C++ DPL Extensions
– OPC Interface
– DSL models C-Interface
– DSL functions C-Interface
– External C Interface for dynamic models
• Context Sensitive Help: pressing the key F1 while working with PowerFactory will lead directly
to the related topic inside the User Manual.

DIgSILENT PowerFactory 2016, User Manual 7

CHAPTER 3. DOCUMENTATION AND HELP SYSTEM

• PowerFactory Examples: the window PowerFactory Examples provides a list of application ex-
amples of PowerFactory calculation functions. Every example comes with an explanatory docu-
ment that can be opened by clicking on the Show Documentation button ( ). Additionally, videos
demonstrating the software handling and its functionalities are available.
The PowerFactory Examples window will “pop up” automatically every time the software is open,
this could be deactivated by unchecking the Show at Startup checkbox. PowerFactory Examples
are also accessible on the main menu, by selecting File → Examples. . . .
• Release Notes: for all new versions and updates of the program Release Notes are provided,
which document the implemented changes. They are available from the DIgSILENT download
area.
• Knowledge base: all PowerFactory users can access the Knowledge base section, on the DIgSI-
LENT Support area: http://www.digsilent.de/index.php/support.html. The knowledge base con-
tains interesting questions and answers regarding specific applications of PowerFactory.
• Technical Support: See Chapter 2: Contact

• Portal log-in and Registration: http://www.digsilent.de/index.php/support.html

• Website: www.digsilent.de

8 DIgSILENT PowerFactory 2016, User Manual

Chapter 4

PowerFactory Overview

The calculation program DIgSILENT PowerFactory , is a computer-aided engineering tool for the anal-
ysis of transmission, distribution, and industrial electrical power systems. It has been designed as an
advanced integrated and interactive software package dedicated to electrical power system and control
analysis in order to achieve the main objectives of planning and operation optimisation.

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

PowerFactory was designed and developed by qualified engineers and programmers with many years
of experience in both electrical power system analysis and computer programming. The accuracy and
validity of results obtained with PowerFactory has been confirmed in a large number of implementations,
by organisations involved in the planning and operation of power systems throughout the world.

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

1. PowerFactory core functions: definition, modification and organisation of cases; core numerical
routines; output and documentation functions.
2. Integrated interactive single line graphic and data case handling.

3. Power system element and base case database.

4. Integrated calculation functions (e.g. line and machine parameter calculation based on geometri-
cal or nameplate information).
5. Power system network configuration with interactive or on-line SCADA access.

6. Generic interface for computer-based mapping systems.

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

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

DIgSILENT PowerFactory 2016, User Manual 9

CHAPTER 4. POWERFACTORY OVERVIEW

The functionality purchased by a user is configured in a matrix-like format, where the licensed calcu-
lation functions, together with the maximum number of buses, are listed as coordinates. The user can
then, as required, configure the interface and functions according to their requirements.

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

4.1 General Concept

The general PowerFactory program design concept is summarised as follows:

Functional Integration

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

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

Vertical Integration

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

Database Integration

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

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

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

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

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

10 DIgSILENT PowerFactory 2016, User Manual

 4.2. DATABASE, OBJECTS, AND CLASSES

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

Customisation

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

• Customise the element dialog pages that are displayed.

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

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

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

4.2 Database, Objects, and Classes

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

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

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

DIgSILENT PowerFactory 2016, User Manual 11

CHAPTER 4. POWERFACTORY OVERVIEW

4.3 PowerFactory Simulation Functions

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

of the manual, including the following:

• Load Flow Analysis, allowing meshed and mixed 1-,2-, and 3-phase AC and/or DC networks
(Chapter 23: Load Flow Analysis).
• Low Voltage Network Analysis (Section 23.4.2: Advanced Load Options).
• Short-Circuit Analysis, for meshed and mixed 1-,2-, and 3-phase AC networks (Chapter 24: Short-
Circuit Analysis).

• Power Quality and Harmonics Analysis (Chapter 25: Power Quality and Harmonics Analysis.
• Quasi-Dynamic simulation, which allows to perform several load flow calculations in a period of
time (Chapter 27:Quasi-Dynamic Simulation).
• RMS Simulation (time-domain simulation for stability analysis, Chapter 28: Stability and EMT
Simulations).
• EMT Simulation (time-domain simulation of electromagnetic transients, Chapter 28: Stability and
EMT Simulations).
• Eigenvalue Analysis (Chapter 29: Modal Analysis / Eigenvalue Calculation).

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

• Contingency Analysis (Chapter 31: Contingency Analysis).
• Reliability Analysis (Chapter 32: Reliability Assessment).
• Optimal Power Restoration, including manual restorations (Chapter 33: Optimal Power Restora-
tion).
• Generation Adequacy Analysis (Chapter 34: Generation Adequacy Analysis).
• Optimal Power Flow (Chapter 35: Optimal Power Flow).
• Transmission Network Tools (Chapter 36: Transmission Network Tools).

• Distribution Network Optimisation (Chapter 38: Distribution Network Tools).

• Protection Analysis (Chapter 42: Protection).
• Network Reduction (Chapter 43: Network Reduction).

• State Estimation (Chapter 44: State Estimation).

4.4 General Design of PowerFactory

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

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

12 DIgSILENT PowerFactory 2016, User Manual

 4.4. GENERAL DESIGN OF POWERFACTORY

Figure 4.4.1: PowerFactory Main Window

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

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

1. Data that pertains directly to the system under study, that is, electrical data.
2. Study management data, for example, which graphics should be displayed, what options have
been chosen for a Load Flow, which Areas of the network should be considered for calculation,
etc.

DIgSILENT PowerFactory 2016, User Manual 13

CHAPTER 4. POWERFACTORY OVERVIEW

Figure 4.4.2: PowerFactory Data Manager

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

4.5 Type and Element Data

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

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

Consider the following example:

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

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

14 DIgSILENT PowerFactory 2016, User Manual

 4.6. DATA ARRANGEMENT

4.6 Data Arrangement

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

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

4.6.1 Global Library

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

• Type data for standard components such as conductors, motors, generators, and transformers.
• Standard control system frames, models, and macros (i.e. transfer functions and logic blocks,
etc).

DIgSILENT PowerFactory 2016, User Manual 15

CHAPTER 4. POWERFACTORY OVERVIEW

• Standard CT, VT, fuse, and relay models.

• Pre-defined model templates, including:

– Battery System with frequency control (10 kV, 30 MVA).

– Double Fed Induction Wind Turbine Generator (0.69 kV, 2 MW).
– Fully Rated Converter Wind Turbine Generator (0.4 kV, 2 MW).
– Variable Rotor Resistance Wind Turbine Generator (0.69 kV, 0.66 MW).
– Photovoltaic System (0.4 kV, 0.5 MVA)

• Standard DPL scripts, including scripts to:

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

Documentation about the various elements and types in the global library can be found directly in the
description page of the elements, in the appendix B.12 and C of the manual and in additional documents
(linked in the corresponding appendix parts).

4.6.2 User Defined Global Library

Sometimes it is useful to share a Library with another PowerFactory user in a Global Library. This re-
quires the creation of a Library folder, which can be done by the Administrator as shown in Figure 4.6.2.
To do this, the Administrator must proceed as follows:

• Right-click on the “Database”

• Click on New → Folder
• Chose a library name and select “Library” as Folder Type

• Click OK

The new Library is now created at the same level of the hierarchy as the Global Library. Every user of
this database has full read access, however the Types within this Library must be created and edited by
the Administrator.

16 DIgSILENT PowerFactory 2016, User Manual

 4.6. DATA ARRANGEMENT

Figure 4.6.2: Creation of a user-defined Global Library

Note: The user-defined Library should not be named “Library”, as this name is reserved for the standard
Global Library. Furthermore, the data within the standard Global Library should not be changed
by the User, as this folder will be overwritten when installing a new PowerFactory version. This
also applies to the Library folder within the standard Global Library.

4.6.3 Project Library

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

4.6.4 Diagrams

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

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

These diagrams are managed by the active Study Case, and specifically by an object called the
Graphics Board. If a reference to a network diagram is stored in a Study Case’s Graphics Board,

DIgSILENT PowerFactory 2016, User Manual 17

CHAPTER 4. POWERFACTORY OVERVIEW

when the Study Case is activated, the diagram is automatically opened. Diagrams can be easily added
and deleted from the Graphics Boards.

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

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

4.6.5 Network Data

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

Grids

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

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

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

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

Variations

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

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

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

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

18 DIgSILENT PowerFactory 2016, User Manual

 4.7. PROJECT STRUCTURE

• Modifications to network components.

• Components added to the network.

• Components deleted from the network.

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

Grouping Objects

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

4.6.6 Operation Scenarios

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

4.6.7 Study Cases

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

4.6.8 Settings

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

4.7 Project Structure

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

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

DIgSILENT PowerFactory 2016, User Manual 19

CHAPTER 4. POWERFACTORY OVERVIEW

Figure 4.7.1: Example Project Structure

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

4.7.1 Nodes

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

4.7.2 Branches

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

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

4.7.3 Cubicles

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

4.7.4 Switches

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

20 DIgSILENT PowerFactory 2016, User Manual

 4.8. USER INTERFACE

4.7.5 Substations

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

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

4.7.6 Sites

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

4.7.7 Branch Elements

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

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

4.8 User Interface

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

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

• Chapter 9(Network Graphics (Single Line Diagrams)).

• Chapter 10 (Data Manager).

4.8.1 Overview

The main PowerFactory window is shown in Figure 4.8.1

DIgSILENT PowerFactory 2016, User Manual 21

CHAPTER 4. POWERFACTORY OVERVIEW

Figure 4.8.1: PowerFactory user interface

Key features of the main window are as follows:

1. The main window includes a description of the PowerFactory version, and standard icons to
Minimise, Maximise/Restore, Resize, and Close the window.
2. The main menu bar includes drop-down menu selections. The main menu is discussed further in
Section 4.8.2 (Menu Bar).
3. The Main Toolbar includes commands and other icons. The Main Toolbar is discussed in further
detail in Section 4.8.3 (Main Toolbar).
4. The Graphical Editor displays single line diagrams, block diagrams and/or simulation plots of the
active project. Studied networks and simulation models can be directly modified from the graphical
editor by placing and connecting elements.
5. When an object is right clicked (in the graphical editor or in the Data Manager) a context sensitive
menu with several possible actions appears.
6. When an object is double clicked its edit dialog will be displayed. The edit dialog is the interface
between an object and the user. The parameters defining the object are accessed through this edit
dialog. Normally an edit dialog is composed of several “pages”. Each page groups parameters
that are relevant to a certain function. In Figure 4.8.1 the Load Flow page of a generator is shown,
where only generator parameters relevant to load flow calculations are shown.
7. The “Data Manager” is the direct interface with the database. It is similar in appearance and
functionality to a Windows Explorer window. The left pane displays a symbolic tree representation
of the complete database. The right pane is a data browser that shows the content of the currently
selected folder. The Data Manager can be accessed by pressing the Data Manager icon ( )
on the left of the main toolbar. It is always ’floating’, and more than one can be active at a
time. Depending on how the user navigates to the Database Manager, it may only show the
database tree for selecting a database folder, or it may show the full database tree. The primary

22 DIgSILENT PowerFactory 2016, User Manual

 4.8. USER INTERFACE

functionality of the Data Manager is to provide access to power system components/objects. The
Data Manager can be used to edit a group of selected objects within the Data Manager in tabular
format. Alternatively, objects may be individually edited by double clicking on an object (or right-
click → Edit).
8. The output window is shown at the bottom of the PowerFactory window. The output window cannot
be closed, but can be minimised. The output window is discussed in further detail in Section 4.8.4
(The Output Window).
9. The “Project Overview” window is displayed by default on the left side of the main application
window between the main toolbar and the output window. It displays an overview of the project
allowing the user to assess the state of the project at a glance and facilitating easy interaction with
the project data.

4.8.2 Menu Bar

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

Figure 4.8.2: The help menu on the Menu bar

For example as show in Figure 4.8.2:

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

DIgSILENT PowerFactory 2016, User Manual 23

CHAPTER 4. POWERFACTORY OVERVIEW

4.8.3 Main Toolbar

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

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

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

Open Data Manager

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

Open Network Model Manager

Opens the Network Model Manager, which is a browser for all calculation relevant objects. It
provides a list of all elements (coloured in green) and types (coloured in red) that are in an active
Grid: e.g. transformer types, line elements, composite models, etc. For more information, see
Chapter 12 (Network Model Manager).

Date/Time of Calculation Case (SetTime)

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

Edit Trigger

Displays a list of all Triggers that are in the active Study Case. These Triggers can be edited in
order to change the values for which one or more characteristics are defined. These values will
be modified with reference to the new Trigger value. All Triggers for all relevant characteristics
are automatically listed. If required, new Triggers will be created in the Study Case. For more
information, see Chapter 17: Parameter Characteristics, Load States, and Tariffs. Section 17.2
(Parameter Characteristics).

Network Data Assessment (ComCheck)

Activates the Network Data Assessment command dialog to generate selected reports on net-
work data or to perform model data verification. For more information see Section 24.6 (Capaci-
tive Earth-Fault Current) or Section 23.6 (Troubleshooting Load Flow Calculation Problems).

Calculate Load Flow (ComLdf)

Activates the Load Flow Calculation command dialog. For more information about the specific
settings, refer to Chapter 23 (Load Flow Analysis).

Calculate Short-Circuit (ComShc)

24 DIgSILENT PowerFactory 2016, User Manual

 4.8. USER INTERFACE

Activates the short-circuit calculation command dialog. For more information, refer to Chapter 24
(Short-Circuit Analysis).

Edit Short-Circuits

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

Execute Scripts

Displays a list of scripts that are available. See Section 4.9.1 for a general description of DPL
scripts, and Chapter 21(Scripting) for detailed information.

Output Calculation Analysis (ComSh)

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

Documentation of Device Data (ComDocu)

Presents a listing of device data (a device is the model of any physical object that has been
entered into the project for study). This output may be used in reports, and for checking data that
has been entered. Depending on the element chosen for the report, the user has two options;
generate a short listing, or a detailed report. For more information refer to Chapter 18:Reporting
and Visualising Results, Section 18.2.3 (Output of Results).

Comparing of Results On/Off

Turns on/off comparing of calculation results. Used to compare results where certain settings or
designs options of a power system have been changed from one calculation to the next. For more
information refer to Chapter 18:Reporting and Visualising Results, Section 18.3 (Comparisons
Between Calculations).

Edit Comparing of Results (CommDiff)

Enables the user to select the cases/ calculation results that are to be compared to one another,
or to set the colouring mode for the difference reporting. For more information refer to Chap-
ter 18:Reporting and Visualising Results, Section 18.3 (Comparisons Between Calculations).

Update Database

Utilises the current calculations results (i.e. the calculation ’output’ data) to change input param-
eters (i.e. data the user has entered). An example is the transformer tap positions, where these
have been calculated by the Load Flow command option “Automatic Tap Adjust of Tap Chang-
ers.” For more information refer to Chapter 18:Reporting and Visualising Results, Section 18.3
(Comparisons Between Calculations).

Save Operation Scenario

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

Break

Stops a transient simulation or DPL script that is running.

DIgSILENT PowerFactory 2016, User Manual 25

CHAPTER 4. POWERFACTORY OVERVIEW

Reset Calculation

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

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

User Settings (SetUser)

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

Maximise Graphic Window

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

Maximise Output Window

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

Change Toolbox

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

26 DIgSILENT PowerFactory 2016, User Manual

 4.8. USER INTERFACE

Figure 4.8.3: Change Toolbox selection

4.8.4 The Output Window

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

Sizing and Positioning the Output Window

The default location of the Output Window is “docked” (fixed) at the bottom of the main window, as
shown in Figure 4.8.1 It can be minimised, but not closed. When right-clicking the mouse button with the
cursor in the output windows area, the context sensitive menu of the output window appears. The output
window can then be undocked by deselecting the Dock Output Window. The undocked output window
is still confined to the main window, but now as a free floating window. This can occur unintentionally
when the user left clicks the tool bar for the output window and drags the mouse (keeping the mouse
button down) to somewhere outside of the output window boundaries. To rectify this simply left-click in
the title bar of the undocked window and drag it down to the bottom of the screen where it will dock once
more (if you have right-clicked and unticked “Docking View” then right click and select “Docking View”
once more).

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

The output window may be moved and resized by:

DIgSILENT PowerFactory 2016, User Manual 27

CHAPTER 4. POWERFACTORY OVERVIEW

• Dragging the splitter bar (grey bar at the upper edge of the output window) when the output window
is in “docking mode”.
• Double-clicking the frame of the output window to dock/undock it from the main window.

• Pressing the Maximise Graphic Window icon ( ) on the main toolbar to enlarge the graphics
board by hiding the output window.

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

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

Opens a previously saved output file.

Saves the selected text to an ASCII file, or the complete contents of the output window if no selection
was made.
Copies the selected text to the Windows Clipboard. Text may then be pasted in other programs.

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

Searches the text in the output window for the occurrences of a given text.

Changes the font used in the output window.

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

Redirects the output window to be printed directly.

Redirects the output window to be printed directly.

Using the Output Window

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

Figure 4.8.4: Output Window Context Sensitive Menu

28 DIgSILENT PowerFactory 2016, User Manual

 4.8. USER INTERFACE

Output Window Context Sensitive Menu

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

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

• Edit and Browse Object: Opens a Data Manager and displays the Element and its parameters.
• Mark in Graphic: Marks the selected element in the Single Line Graphic and zooms into the region
it is placed.

Output Window Legend

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

DIgSI/err - ... Error messages. Format: red coloured.

DIgSI/info - .... Information messages. Format: green coloured.
DIgSI/wrng - ... Warning message. Format: brown coloured.
DIgSI/pcl - ...’ Protocol message. Format: blue coloured.
Text only Output text. Format: black coloured.

Output Window Graphical Results

Reports of calculation results may contain bar graphical information. The “voltage profiles” report after
a Load Flow command, for instance, produces bar graphs of the per-unit voltages of busbars. These
bars will be coloured blue, green or red if the “Verification” option in the Load Flow command dialog has
been enabled. They will be hatch-crossed if the bars are too large to display.

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

Figure 4.8.5: Output window bar diagram

• Green Solid Bar: Used when the value is in the tolerated range.
• Blue Solid Bar: Used when the value is below a limit.

DIgSILENT PowerFactory 2016, User Manual 29

CHAPTER 4. POWERFACTORY OVERVIEW

• Red Solid Bar: Used when the value is above a limit.

• Hatch-crossed Bar: Used when the value is outside the range.

Copying from the Output Window

The contents of the Output Window, or parts of its contents, may be copied to the built-in editor of
PowerFactory , or to other programs. Normally, not all selected lines will be copied and the format of the
copied text may undergo changes. The latter is caused by the fact that the PowerFactory output window
uses special formatting “escape sequences”, which other programs may not support.

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

Figure 4.8.6: The output window Info Message

4.9 Scripting in PowerFactory

4.9.1 DIgSILENT Programming Language (DPL) Scripts

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

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

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

• Network optimisation.
• Cable-sizing.
• Protection coordination.

30 DIgSILENT PowerFactory 2016, User Manual

 4.9. SCRIPTING IN POWERFACTORY

• Stability analysis.
• Parametric sweep analysis.

• Contingency analysis.

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

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

Figure 4.9.1: Example DPL Script

DIgSILENT PowerFactory 2016, User Manual 31

CHAPTER 4. POWERFACTORY OVERVIEW

For further information about DPL commands and how to write and execute DPL scripts refer to Chap-
ter 21 (Scripting), and the DPL Reference.

4.9.2 Python Scripts

Additionally to DPL it is also possible to use the Python language to write scripts to be executed in
PowerFactory .

Pythons scripts should be written in an external editor and linked to the Python command (ComPython)
inside PowerFactory .

For further information about the python command and how to write and execute Python scripts refer to
Chapter 21 (Scripting), and the Python Reference.

32 DIgSILENT PowerFactory 2016, User Manual

 Part II

Administration
Chapter 5

Program Administration

This chapter provides information on how to configure PowerFactory , and how to log on. More de-
tailed descriptions of the installation, database settings and additional information can be found in the
PowerFactory Advanced Installation and Configuration Manual.

5.1 Program Installation and Configuration

In general there are 3 primary questions to consider before installing PowerFactory software, which will
determine the installation settings:

• Licence: Where should the licence key(s) reside?

• Installation: Where should PowerFactory be installed?
• Database: Where should the database reside?

Once PowerFactory has been installed, it can be started by clicking either on the Desktop or by selecting
PowerFactory in the Windows Start menu. PowerFactory will then start and create a user account upon
the initial user log-in. If the user is working in a single-user-database environment, PowerFactory will
take the username from Windows by default. In the case that several user accounts have been created,
a log-on dialog will pop up allowing the user to select their username. The user will be asked to enter a
password if one has been defined for that particular account.

In a multi-user-database installation (see Chapter 6: User Accounts, User Groups, and Profiles) new
accounts and passwords are created by the administrator. The ’Administrator’ account is created when
installing PowerFactory and is used to create and manage users’ accounts in a multi-user environment
(see Chapter 6: User Accounts, User Groups, and Profiles). To log on as Administrator, the shortcut
from the Windows Start Menu can be used. By default the administrator account password is Adminis-
trator. When already running a PowerFactory session, the user can select Tools → Switch User in the
main menu to log-on as Administrator.

For further information about the roll of the database administrator refer to Section 6.2: The Database
Administrator.

Changes to the default installation settings can be made using the PowerFactory Configuration dialog.
Once PowerFactory is started, the Configuration dialog can be accessed via Tools → Configuration in
PowerFactory ’s main menu. The Database and Licence tabs of the Configuration dialog provide options
to determine how the program installation should be configured. Administrator rights are necessary to
perform changes to these settings.

DIgSILENT PowerFactory 2016, User Manual 35

CHAPTER 5. PROGRAM ADMINISTRATION

A detailed description of the installation procedure and the program configuration alternatives is pro-
vided in the PowerFactory Advanced Installation and Configuration Manual.

5.2 PowerFactory Configuration

The Configuration (SetConfig) dialog is used to apply changes to the configuration settings. Windows
Administration rights are required.

5.2.1 General

On this page the user can select the application language for the session.

5.2.2 Database

This page allows the selection of how the database will be used. The options are:

• A single-user database which resides locally on each computer

• A multi-user database which resides on a 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 regarding the database configuration refer to the PowerFactory Advanced Instal-
lation and Configuration Manual.

5.2.3 Workspace

The Workspace page allows the user to set the workspace directory and the workspace backup direc-
tory. The workspace is used to store the local database, result files and log files. For further information
regarding options for configuring and using the workspace, refer to Chapter 5.4.

5.2.4 External Application

The External Applications page is used to set the Python editor path. This setting is used by Python.

5.2.5 Map Server

On the Map Server page, the default settings for background maps can be changed. The following
parameters can be set:

36 DIgSILENT PowerFactory 2016, User Manual

 5.3. LICENCE

• Directory: Map cache directory where downloaded map tiles are stored (default: workspace
directory). A custom directory can be specified if the cache should be shared across different
PowerFactory installations.

• Preferred tile size [pixels]: Pixel dimensions of map tiles.

• Max server connections: Maximum number of map tiles that are downloaded simultaneously.
• Download time-out: Timespan after which a non-finished tile download is cancelled. This value
may need to be increased for slow/unstable internet connections.

• HTTP proxy: Needs to be specified in the case the user’s computer connects to the internet via a
proxy server. Format: host:port , e.g.: “myproxy:1234”

If Google Maps©should be used as the map provider, the “Google Maps for Business account” data
must be set on this page as well. To acquire a licence, please contact Google sales: (http://www.
google.com/enterprise/mapsearth).

5.2.6 Advanced

Settings on the Advanced page should only be changed under the guidance of the DIgSILENT Power-
Factory support (see Chapter 2 Contact).

5.3 Licence

5.3.1 Select Licence

In order to run PowerFactory , the user is required to define licence settings in the DIgSILENT Power-
Factory Licence Manager, its dialog can be accessed via Tools → Licence→ Select Licence. . .

Note: The DIgSILENT PowerFactory Licence Manager can be started externally using the correspond-
ing shortcut in the main installation folder of PowerFactory.

The Licence Access defines the type of licence, which can be a local licence (either a licence file or a
USB dongle) or a network licence.

Automatic search

This option searches automatically local and network licences via a broadcast and chooses the first one
found without further input.

Local licence file / USB dongle

If the local licence is chosen, the Local Licence Settings require the selection of a Licence Container.
The locally found containers are available in the drop-down-list.

Network licence

If the network licence is chosen, the server name has to be entered in the Network Licence Settings.
By pressing , a connection to the server will be established. If the check-box auto-select licence
container on this server is activated, one of the available licence containers provided by the server is
chosen. Else the Licence container can be chosen manually from a drop-down-list.

Selected Licence:

DIgSILENT PowerFactory 2016, User Manual 37

CHAPTER 5. PROGRAM ADMINISTRATION

The field on the right side of the dialog shows various information about the selected licence. It contains,
amongst others, the order ID (useful for any contact with the sales department), the customer ID (useful
for contact with technical support), the number of possible users for a multi user environment and a list
of the licensed additional modules.

If problems with the licence occur, the button Create Licence Support Package creates a zipped file with
the needed information for the support to identify the cause of the problems.

5.3.2 Activate / Update / Deactivate Licence

These options are relevant for local licences, where the user has to manage the licence. In a network
licence environment, this is done by the network administrator.

For the activation, the update and the deactivation process the licence related Activation Key has to be
entered into the upcoming dialog.

More information regarding licence types and their management is available in the PowerFactory
Advanced Installation and Configuration Manual.

5.4 Workspace Options

By selecting Tools → Workspace from the main menu, the options described below are available.

5.4.1 Show Workspace Directory

The workspace directory can be seen by clicking Tools → Workspace→ Show workspace directory.

5.4.2 Import and Export Workspace

To import the workspace, select Tools → Workspace→ Import Workspace. . . . This is a convenient
way to import the entire workspace after a new installation. To export the workspace, select Tools →
Workspace→ Export Workspace. . . . The package will be saved as a .zip file.

5.4.3 Show Default Export Directory

The selection Tools → Workspace→ Show Default Export Directory from the main menu shows the
user the directory that is used for the export.

5.4.4 Import Workspace from 14.X or 15.0. . .

This option allows the migration of the database from an older PowerFactory version (e.g 14.X, 15.0. . . )
to the newest version.

This can be selected from the main menu, under Tools → Workspace→ Import Workspace from 14.x
or 15.0. . . . After “Import Workspace from 14.x or 15.0. . . ” has been selected, the user can choose the
working directory. The database that is saved in selected working directory will be migrated.

Depending on the database size, a migration may take several hours. Figure 5.4.1 shows the two
different migration types available.

38 DIgSILENT PowerFactory 2016, User Manual

 5.5. OFFLINE MODE USER GUIDE

Figure 5.4.1: Database migration settings

Migration Types

Complete: the database structure and all projects will be altered and migrated immediately upon
pressing the OK button.
Minimal: the database structure will be altered immediately, but the project migration will occur upon
activation.

Minimal migration is recommended for the migration of large databases.

5.5 Offline Mode User Guide

This section describes working in offline mode. Installation of the offline Mode is described in the
Advanced Installation and Configuration Manual.

5.5.1 Functionality in Offline Mode

5.5.1.1 Start Offline Session

Preconditions:

• A PowerFactory user account must already exist in the online database. The PowerFactory “Ad-
ministrator” user is able to create user accounts.
• The user must not be logged-on to an online session. In the example in Figure 5.5.1, User 2 and
User 3 are able to start an offline session, but User 1 is not, as s/he is already logged-on to an
online session.

Figure 5.5.1: Offline and online sessions

Note: the Administrator user is only allowed to work in online mode (not in offline mode).

DIgSILENT PowerFactory 2016, User Manual 39

CHAPTER 5. PROGRAM ADMINISTRATION

To create an offline session, follow these steps:

• Start PowerFactory . In the Log-on dialog enter the user name and password.

• On the Database page, enter the Offline Proxy Server settings (see Figure 5.5.2)

Figure 5.5.2: Log-on dialog, Database page

• Press OK
• An info message is shown. (fig. 5.5.3)

Figure 5.5.3: Info message

• Press OK
• Following initialisation, the usual PowerFactory application window is shown.

5.5.1.2 Release Offline Session

• From the main menu, select File → Offline→ Terminate Offline session
• A warning message is shown to confirm the synchronisation

40 DIgSILENT PowerFactory 2016, User Manual

 5.5. OFFLINE MODE USER GUIDE

• Press Yes
• All unsynchronised local changes will then be transferred to the server and the local offline
database is removed.

5.5.1.3 Synchronise All

Synchronises global data (new users, projects added, projects removed, projects moved) and all sub-
scribed projects.

• Open the main menu File → Offline→ Synchronise all

5.5.1.4 Subscribe Project for Reading Only

• Open the Data Manager and navigate to the project.

• Right-click on the project stub. A context menu is shown.

• Select Subscribe project in offline mode for reading only.

The project will then be retrieved from the Offline Proxy Server and stored in the local Offline DB cache.

5.5.1.5 Subscribe Project for Reading and Writing

Write access to the project is required.

• Open the Data Manager and navigate to the project.

• Right-click on the project stub. A context menu is shown.

• Select Subscribe project in Offline mode for reading and writing.

5.5.1.6 Unsubscribe Project

• Open the Data Manager and navigate to the project.

• Right-click on the project. A context menu is shown.
• Select Unsubscribe project in Offline mode.

5.5.1.7 Add a New Project

A new project is created in offline mode. It is available only in this offline session. Later this project
should be published to other users and synchronised to the online database.

• Create a new project or import a PFD project file.

• Open the Data Manager and navigate to the project.

• Right-click on the project stub. A context menu is shown.
• Select Subscribe project in Offline mode for reading and writing.

DIgSILENT PowerFactory 2016, User Manual 41

CHAPTER 5. PROGRAM ADMINISTRATION

5.5.1.8 Synchronise Project

Synchronises a subscribed project. If the project is subscribed for reading only, the local project will be
updated from the online database. If the project is subscribed for reading and writing, the changes from
the local offline database will be transferred to the online database.

• Open the Data Manager and navigate to the project

• Right-click on the project stub. A context menu is shown.

• Select Synchronise

5.5.2 Functionality in Online mode

5.5.2.1 Show Current Online/Offline Sessions

The session status for each user is shown in the Data Manager.

Figure 5.5.4: Online and offline users

In Figure 5.5.4:

• User 1 and Administrator are logged on to an online session. They are indicated by the
green ONLINE icon.
• User 2 has started an offline session. It is indicated by the red OFFLINE icon.
• Public, Demo, and User 3 are not logged on.

5.5.3 Terminate Offline session

There may occasionally be cases which require that an offline session be terminated by the Adminis-
trator; e.g. if the computer on which the offline session was initialised has been damaged and can no
longer be used, and the user wants to start a new offline session on a different computer.

The Administrator is able terminate a session as follows:

• Right-click on the user; the context menu is shown.

• Select Terminate session (see Figure 5.5.5)

42 DIgSILENT PowerFactory 2016, User Manual

 5.6. HOUSEKEEPING

Figure 5.5.5: Terminate offline session

• A warning message is shown to confirm the synchronisation.

• Press Yes

As shown in Figure 5.5.6, User 2 no longer has an active session:

Figure 5.5.6: Online users

5.6 Housekeeping

5.6.1 Introduction

Housekeeping automates the administration of certain aspects of the database; in particular purging
projects, emptying user recycle bins and the deletion of old projects. Housekeeping is triggered by the
execution of a Windows Scheduled Task; this can be set up to run at night, thus improving performance
during the day by moving regular data processing to off-peak times. An additional benefit to housekeep-
ing is that users will need to spend less time purging projects and emptying recycle bins, something that
can slow down the process of exiting PowerFactory .

Housekeeping is only available for multi-user databases (e.g. Oracle, SQL Server). For details on
scheduling housekeeping, see the PowerFactory Advanced Installation and Configuration Manual.

DIgSILENT PowerFactory 2016, User Manual 43

CHAPTER 5. PROGRAM ADMINISTRATION

5.6.2 Configuring Permanently Logged-On Users

Normally, housekeeping will not process data belonging to logged-on users; however, some user
accounts (e.g. those for a control room) may be connected to PowerFactory permanently. These users
can be configured to allow housekeeping to process their data while they are logged-on. This is done
from the User Settings dialog (see Figure 5.6.1). Regardless of this setting, housekeeping will not
operate on a user’s active project.

Figure 5.6.1: The User Settings dialog: housekeeping for connected users

5.6.3 Configuring Housekeeping Tasks

The Housekeeping command (SetHousekeeping) is used to control which housekeeping tasks are
enabled (see Figure 5.6.2). It is recommended that the user move this object from Database \Sys-
tem\Configuration\Housekeeping to Database∖Configuration∖Housekeeping, in order to preserve the
user’s configuration throughout database upgrades.

The following sections discuss the different housekeeping tasks available in the Housekeeping dialog.

44 DIgSILENT PowerFactory 2016, User Manual

 5.6. HOUSEKEEPING

Figure 5.6.2: Housekeeping dialog

5.6.4 Project Archiving

Project archiving provides the following options:

• Disable: Archiving is not used.

• Immediate archiving by the user: by selecting “Archive” from the context menu, the project will
be immediately archived and placed in the vault directory.
• Deferred archiving by Housekeeping job: by selecting “Archive” from the context menu, the
project will be immediately archived, but not placed in the vault directory. This will happen
automatically depending on the Housekeeping settings.

Important: The vault directory can be defined under “Tools\Configuration\Database \Vault Directory”

A project cannot be archived unless it is deactivated. By right-clicking on the project a context menu
will appear. By selecting “Archive”, the project will be moved to the Archived Projects folder of the user
(IntUser ). If specified in the Housekeeping archiving options, the project will be immediately placed in
the vault directory.

Conversely, archived projects may also be restored. To restore an archived project, the user must select
“Restore” from the context menu which appears after right-clicking on a deactivated project.

5.6.5 Configuring Deletion of Old Projects

If the option Remove projects based on last activation date has been selected in the Housekeeping
dialog, when the Housekeeping is executed, for each user, each project will be handled according to
the selected Action.

The Action options are:

• Delete project: deletes the project

DIgSILENT PowerFactory 2016, User Manual 45

CHAPTER 5. PROGRAM ADMINISTRATION

• Archive project: archives the project

The project properties determine whether a project can be automatically deleted or archived, as shown
in Figure 5.6.3. The default setting for “Housekeeping project deletion” is disabled. When enabled, the
default retention period is 60 days. These defaults can be changed for new projects by using a template
project (under Configuration/Default in the Data Manager tree).

Figure 5.6.3: Project properties

The settings for multiple projects may be selected using the tabular pane of the Data Manager window
(select the relevant column, right-click and select Modify Values). A value of ’1’ is equivalent to the
Housekeeping option Delete project being selected (see Figure 5.6.4). Many projects can be changed
via the tabular window which appears following a Find operation, though it should be noted that execut-
ing a Find is potentially a lengthy operation.

46 DIgSILENT PowerFactory 2016, User Manual

 5.6. HOUSEKEEPING

Figure 5.6.4: Setting parameters for multiple projects

A project will be deleted/archived by the housekeeping task if it meets the following criteria:

1. The project is configured for automatic deletion/archiving on the Storage page of the project
properties.
2. The last activation of the project is older than the retention setting on the project.
3. It is not a base project with existing derived projects.

4. It is not a special project (e.g. User Settings, or anything under the System or Configuration trees).
5. The project is not locked (e.g. active).
6. The owner of the project is not connected, unless that user is configured to allow concurrent
housekeeping (see Section 5.6.2).

5.6.6 Configuring Purging of Projects

If Purge projects has been ticked in the Housekeeping dialog, when the Housekeeping is executed,
each project will be considered for purging. A project that is already locked (e.g. an active project) will
not be purged.

The criteria used by Housekeeping to purge a project are:

• If the project has been activated since its last purge.

• If it is now more than a day past the object retention period since last activation, and the project
has not been purged since then.
• If the project is considered to have invalid metadata (e.g. is a pre-14.0 legacy project, or a PFD
import without undo information).

DIgSILENT PowerFactory 2016, User Manual 47

CHAPTER 5. PROGRAM ADMINISTRATION

Once housekeeping has been configured to purge projects, the automatic purging of projects on acti-
vation may be disabled by the user, thus preventing the confirmation dialog popping up. To do this, the
option Automatic Purging should be to Off on the Storage page in the Project Properties dialog. This
parameter can also be set to Off for multiple projects (see Section 5.6.5 for details).

5.6.7 Configuring Emptying of Recycle Bins

If Delete recycle bin objects is set in the Housekeeping dialog, when Housekeeping is executed, each
user’s recycle bin will be examined. Entries older than the number of days specified in the Housekeeping
dialog (as shown in Figure 5.6.2) will be deleted.

5.6.8 Monitoring Housekeeping

In order to ensure that housekeeping is working correctly, it should be regularly verified by an adminis-
trator. This is done by inspecting the HOUSEKEEPING_LOG table via SQL or the data browsing tools of
the multi-user database. For each run, housekeeping will insert a new row to this table showing the start
and end date/time and the completion status (success or failure). Other statistics such as the number
of deleted projects are kept. Note that absence of a row in this table for a given scheduled day indicates
that the task failed before it could connect to the database. In addition to the HOUSEKEEPING_LOG
table, a detailed log of each housekeeping run is stored in the log file of the housekeeping user.

5.6.9 Summary of Housekeeping Deployment

The basic steps to implement housekeeping are:

1. Set up a Windows Scheduled Task, as described in the PowerFactory Advanced Installation and
Configuration Manual.

2. Configure those users expected to be active during housekeeping, as described in Section 5.6.2.
3. Configure the Housekeeping dialog as described in Section 5.6.3.
4. If using the project deletion/archiving task, configure automatic deletion/archiving properties for
new projects, as described in Section 5.6.5.

5. If using the project deletion/archiving task, configure automatic deletion/archiving properties for
existing projects, as described in Section 5.6.5.
6. Regularly monitor the HOUSEKEEPING_LOG table to verify the status of housekeeping runs, as
described in Section 5.6.8.

48 DIgSILENT PowerFactory 2016, User Manual

Chapter 6

User Accounts, User Groups, and

Profiles

This chapter provides details of how to create and manage user accounts, user groups, and profiles.
Key objectives of the user account managing system are to:

• Protect the ’system’ parts of the database from changes by normal (non-Administrator) users.
• Protect parts of the databases belonging to user “A” from changes by user “B”.
• Facilitate sharing of user data.

The user account managing system provides each user with their own “private” database space. The
user is nevertheless able to use shared data, either from the common system database or from other
users, and may enable other users to use data from their private database.

The user account managing system manages this whilst using only one single database in the back-
ground, which allows for simple backup and management of the overall database.

The default name for a PowerFactory user is the Windows user name, which is automatically created
when PowerFactory is started for the first time.

6.1 PowerFactory Database Overview

A brief introduction to the top level structure of the PowerFactory database is convenient before present-
ing the user accounts and their functionality.

The data in PowerFactory is stored inside a set of hierarchical directories. The top level structure is
constituted by the following folders:

The Configuration folder Contains company specific customising for user groups, user default set-
tings, project templates and class templates for objects. Configuration folder is read only for
normal users.
The main Library folder Contains all standard types and models provided with PowerFactory. The
main library folder is read only for normal users.
The System folder Contains all objects that are used internally by PowerFactory. The system folder is
read only for all normal users. Changes are only permitted when logged on as the Administrator,
and should be conducted under the guidance of DIgSILENT customer support.

DIgSILENT PowerFactory 2016, User Manual 49

CHAPTER 6. USER ACCOUNTS, USER GROUPS, AND PROFILES

User account folders Contain user project folders and associated objects and settings.

The structure described above is illustrated in Figure 6.1.1

Figure 6.1.1: Basic database structure

6.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 permissions to:

• Add and delete users.

• Define users groups.
• Set individual user rights.
• Restrict or allow calculation functions.
• Set/reset user passwords.
• Create and edit Profiles (see Section 6.4 for details).

The administrator is also the only user that can modify the main library and the system folders. Although
the administrator has access to all the projects of all the users, it does not have the right to perform any
calculation.

To log on as administrator, there are two options:

• Select the Shortcut in the Windows Start Menu PowerFactory 2016 (Administrator).
• Log into PowerFactory as a normal User and select via the Main menu Tools → Switch User. Se-
lect Administrator and enter the corresponding password. By default the administrator password
is Administrator.

For further information about the administrator roll, refer to the PowerFactory Advanced Installation
and Configuration Manual.

50 DIgSILENT PowerFactory 2016, User Manual

 6.3. CREATING AND MANAGING USER ACCOUNTS

6.3 Creating and Managing User Accounts

In the case of an installation with a local database, the default name for a PowerFactory user is the
Windows user name, which is automatically created when PowerFactory is started for the first time. (see
Chapter 5: Program Administration). In this case the program will automatically create and activate the
new account, without administrator intervention. In order to create other PowerFactory users if required,
the ’User Manager’ object can be used as described below:

In multi-user database installations, the administrator creates new user accounts by means of a tool
called the ’User Manager’, which is found in the Configuration folder.

To create a new user:

• Log on as Administrator. You can do so by starting the PowerFactory Administrator shortcut in the
Windows Start menu or by switching the user via Tools → Switch User in the main tool bar.
• In the left pane of the Data Manager click on Configuration folder to display its contents.

• Double click on the User Manager icon ( , right pane) and press the Add User. . . button.

The User edit dialog will be displayed:

• In the General page, enter the new user name and password.

• If a licensed version with a restricted number of functions is used (i.e. you may have 4 licences
with basic functionality, but only 2 stability licences), the Licence tab may be used to define the
functions that a user can access. The Multi User Database option (bottom of the tab) should be
checked for all users that will access the multi user database.

The administrator can edit any user account to change the user name, set new calculation rights or
change the password. To edit an existing user account:

• Right-click on the desired user and select Edit from the context sensitive menu. The User edit
dialog will be displayed.

Any user can edit her/his own account by means of the User edit dialog. In this case only the full name
and the password can be changed.

Note: The Administrator is the only one who may delete a user account. Although users can delete
all projects inside their account folder, they cannot delete the account folder itself or the standard
folders that belong to it (i.e. the Recycle Bin or the Settings folder).

6.4 Creating User Groups

Any project or folder in a user account may be shared. This action can be performed selectively by
sharing only with certain user groups. User groups are created by the administrator via the User
Manager. To create a new user group:

• Log on as Administrator.
• In the Data Manager open the Configuration folder and double click on the User Manager icon( ).

DIgSILENT PowerFactory 2016, User Manual 51

CHAPTER 6. USER ACCOUNTS, USER GROUPS, AND PROFILES

• In the User Manager dialog that appears 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 dialog
(right 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 (right-click the user group and select Paste
Shortcut from the context sensitive menu).

Users are taken out of a group by deleting their shortcut from the corresponding group.

The Administrator can also set the Groups Available Profiles on the Profile tab of the Group dialog.

For information about sharing projects, refer to Section 19.6 (Sharing Projects).

6.5 Creating Profiles

Profiles can be used to configure toolbars, menus, dialog pages, and dialog parameters. By default,
PowerFactory includes “Base Package” and “Standard” profiles, selectable from the main menu under
Tools → Profiles. Selecting the “Base Package” profile limits icons shown on the Main Toolbar to those
that are used with the Base Package of the software. The “Standard” profile includes all available
PowerFactory icons.

Profiles are created in the Configuration → Profiles folder by selecting the New Object icon and then
Others → Settings→ Profile. An Administrator can create and customise profiles, and control User/User
Group selection of profiles from the Profile tab of each group.

Figure 6.5.1 shows the Profile dialog for a new profile, CustomProfile, and Figure 6.5.2 illustrates
aspects of the GUI that may be customised using this profile. This section describes the customisation
procedure.

52 DIgSILENT PowerFactory 2016, User Manual

 6.5. CREATING PROFILES

Figure 6.5.1: Profile dialog

Figure 6.5.2: GUI Customisation using Profiles

6.5.1 Tool Configuration

Definition of Icons

Icons can be defined in the Configuration → Icons folder by selecting the New Object icon and then
Others → Other Elements→ Icon (IntIcon). From the Icon dialog, icon images can be imported and
exported. Icons should be 19 pixels by 19 pixels in Bitmap format (recommended to be 24-bit format).

Command Configuration

• Command: This is the selected DPL script (which should generally be located in the Configuration
→ DPL commands folder), or selected Com* object.

DIgSILENT PowerFactory 2016, User Manual 53

CHAPTER 6. USER ACCOUNTS, USER GROUPS, AND PROFILES

• Edit: If selected, the DPL command dialog will appear when a Command is executed. If de-
selected, the DPL command dialog will not appear when a Command is executed.
• Icon: Previously created icons can be selected, which will be shown on the menu where the
command is placed. If no icon is selected, a default icon will appear (a Hammer, DPL symbol, or
default Com* icon, depending on the Class type).

Template Configuration:

• Template The name of the template. The name may be for a unique template, or include wildcards
(such as *.ElmLne) for selection of a group of templates. Templates should be in ’System/Li-
brary/Busbar Systems’ folder, or in the ’Templates’ folder of the active project.
• Drawing modeThe drawing mode can be set where there are multiple diagrammatic representa-
tions for a template (such as for a substation). Three options are available:
– Blank will place the default (detailed) graphic of the template.
– Simplified will place the simplified graphic of the template.
– Composite will place a composite representation of the template.

• Symbol name Sets the representation of templates with a composite drawing mode (e.g. Gener-
alCompCirc or GeneralCompRect).
• Icon Previously created icons can be selected, which will be shown on the menu where the
template is placed. If no icon is selected, a default icon will appear (a Template symbol or custom
icon).

• Description This description will be displayed when a user hovers the mouse pointer over the
icon. If left blank, the template name will be displayed.

6.5.2 Configuration of Toolbars

The Main Toolbar and Drawing Toolbars can be customised using the Toolbar Configuration. The field
Toolboxes may either refer to a Toolbox Configuration (SetTboxconfig) or a Toolbox Group Configuration
(SetTboxgrconfig), which may in-turn refer to one or more Toolbox Configurations.

Figure 6.5.3 shows an example where there is a main toolbox, and a toolbox group. The toolbox group
adds a Change Toolbox icon to the menu, which allows selection of Basic Commands and Custom
Commands groups of commands.

54 DIgSILENT PowerFactory 2016, User Manual

 6.5. CREATING PROFILES

Figure 6.5.3: Toolbar Configuration

Each toolbox can be customised to display the desired icons, such as illustrated in Figure 6.5.4

Figure 6.5.4: Toolbox Configuration

DIgSILENT PowerFactory 2016, User Manual 55

CHAPTER 6. USER ACCOUNTS, USER GROUPS, AND PROFILES

Prior to customising the displayed buttons and menu items etc, the user should first define any required
custom Commands and Templates. A Tool Configuration object can be created in the Configuration →
Profiles folder, or within a user-defined Profile, by selecting the New Object icon and then Others →
Settings→ Tool Configuration. If created in the Profiles folder, the commands will be available from the
“Standard” profile. Conversely, if the Tool Configuration object is created within a profile (SetProfile) the
commands and templates will only be available for use in this profile. If there is a Tool Configuration
within a user-defined profile, as well as in the Profiles folder, the Tool Configuration in the user-defined
profile will take precedence. Optionally, customised icons can be associated with the Commands and
Templates.

6.5.3 Configuration of Menus

The Main Menu, Data Manager, Graphic, Virtual Instruments, and Output Window menus can be
customised from the Menu Configuration dialog. The Change to Configuration View button of the Profile
dialog is used to display description identifiers for configurable items, such as illustrated in the context-
sensitive menu shown in Figure 6.5.5. The Menu Configuration includes a list of entries to be removed
from the specified menu. Note that a Profile may include multiple menu configurations (e.g. one for
each type of menu to be customised).

Figure 6.5.5: Menu Configuration

6.5.4 Configuration of Dialog Pages

The Dialog Page Configuration may be used to specify the Available and Unavailable dialog pages
shown when editing elements, such as illustrated in Figure 6.5.6. Note that Users can further customise
the displayed dialog pages from the Functions tab of their User Settings.

Figure 6.5.6: Dialog Page Configuration

56 DIgSILENT PowerFactory 2016, User Manual

 6.5. CREATING PROFILES

6.5.5 Configuration of Dialog Parameters

The Dialog Configuration may be used to customise element dialog pages, such as illustrated for a
Synchronous Machine element in Figure 6.5.7. “Hidden Parameters” are removed from the element
dialog page, whereas “Disabled Parameters” are shown but cannot be modified by the user. A Profile
may include multiple dialog configurations (e.g. one for each class to be customised).

Note that if a there is a Dialog Configuration for say, Elm* (or similarly for ElmLne,ElmLod), as well as
a dialog Configuration for ElmLne (for example), the configuration settings will be merged.

Figure 6.5.7: Dialog Configuration

Note: Configuration of Dialog parameters is an advanced feature of PowerFactory , and the user should
be cautious not to hide or disable dependent parameters. Seek assistance from DIgSILENT
support if required.

6.5.6 References

Profiles can also contain references to configurations. This allows several profiles to use the same
configurations. These referenced configurations can either be stored in another profile or in a subfolder
of the “Profiles” folder (e.g. a user-defined profile can use configurations from a pre-defined profile).

DIgSILENT PowerFactory 2016, User Manual 57

CHAPTER 6. USER ACCOUNTS, USER GROUPS, AND PROFILES

58 DIgSILENT PowerFactory 2016, User Manual

Chapter 7

User Settings

The User Settings dialog, offers options for many global features of PowerFactory. This chapter is
dedicated to describe this options. The User settings dialog may be opened either by clicking the User
Settings button ( ) on the main tool bar, or by selecting the Tools → User Settings. . . menu item from
the main menu.

7.1 Data/Network Model Manager Settings

The Data/Network Model Manager settings include:

Browser

• Save Data Automatically. The Data Manager and the Network Model Manager will not ask for
confirmation every time a value is changed in the data browser when this option is selected.
• Confirm Delete Activity. Pops up a confirmation dialog whenever something is about to be
deleted.

Data Manager

• Sort Automatically. Specifies that objects are automatically sorted (by name) in the data browser.
• Remember last selected object. The last selected object will be remember when a new Data
Manager window is opened.
• Use Multiple Data Manager. When enabled, more than one Data Manager dialog can be opened
at a time. When disabled only one Data Manager may be opened at a time and pressing the New
Data Manager button will pop up the minimised Data Manager.
• Use custom font. When enabled, a customised font can be defined.

Operation Scenario

If Save active Operation Scenario automatically is enabled, the period for automatic saving must
be defined.

Export/Import Data (DZ)

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.

DIgSILENT PowerFactory 2016, User Manual 59

CHAPTER 7. USER SETTINGS

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

Folders for Global Library

The default global type folder is the Database/Library/Types folder. This default folder contains
many predefined object types, but objects within this folder may not be changed by the user (read-
only access). This option allows the user to specify a different “Global Type Folder”, possibly a
company specific and defined type library.

For information about the PowerFactory Data Manager refer to Chapter 10.

7.2 Graphic Windows Settings

7.2.1 General tab

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.

Mark in Graphic

The colour used when the objects are marked in the graphics can be defined in the option Colour.

Drawing Toolbar

• No. of Columns in Drawing Tools Floater. Specifies the width of the graphics toolbar when this
is a floating window.
• No. of Columns in Drawing Tools Docker. Specifies the width of the graphics toolbar when it is
docked on the right side of the drawing space.

General Options

• Show Grid only if stepsize will be least. Grid points smaller than the selected size will not be
shown.

• Show Text only if height will be least. Text smaller than the selected size will not be shown.
• Line Width Factor when Printing. The width of all lines in the graphics will be multiplied by the
specified percentage when printing.

Update Graphic while Simulation is running

The graphic will be updated during the simulation.

Use own background colour for single line graphics

If the option is enabled, the user can define the background colour of the single line graphics by
using the pop up menu.

60 DIgSILENT PowerFactory 2016, User Manual

 7.3. OUTPUT WINDOW SETTINGS

7.2.2 Advanced tab

Cursor

Defines the cursor shape:

• Arrow. A normal, arrow shaped cursor.

• Tracking Cross. A small cross.

Default Font for New Graphic

When the Use custom font. is enabled, a customised font can be defined.

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.

7.3 Output Window Settings

The output window settings control the way in which messages selected by the user, in the output
window are to be copied for pasting into other programs.

Whichever options are checked will determine what will be copied. The text in the output window itself
will not be influenced.

Escape sequences are special hidden codes which are used for colouring the text, or other formatting
commands. Some text processing programs are not capable of using the PowerFactory escape codes.
The Text Only option should be set in such cases. The text in the output window itself will not be
influenced by the options chosen here.

The number of lines displayed in the output window may also be limited.

7.4 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 dialogs. The user may choose to see only certain modules in
order to “unclutter” dialogs.

This may also be used to protect data by allowing only certain calculation functionality to be seen by
certain users. This is particularly useful in a multi-user environment or in when inexperienced users
utilise PowerFactory .

7.5 Editor Settings

The editor which is used to enter large pieces of text (such as DPL scripts, objects descriptions, etc.)
can be configured on this page.

Options

• Enable Virtual Space Allows the cursor to move into empty areas.

DIgSILENT PowerFactory 2016, User Manual 61

CHAPTER 7. USER SETTINGS

• 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 colouring

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

ShortCuts

Opens the short-cut definition dialog.

7.6 StationWare Settings

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.

7.7 Miscellaneous Settings

Localisation

• Decimal Symbol. Selects the symbol selected to be used for the decimal point.

62 DIgSILENT PowerFactory 2016, User Manual

 7.7. MISCELLANEOUS SETTINGS

• Use operating system Format for Date and Time. The operating system date and time settings
are used when this is checked.

Retention of results after network change

When the option Show last results is selected, modifications to network data or switch status etc.
will retained the results, these will be shown on the single line diagram and on flexible data pages
in grey until the user reset the results (e.g. by selecting Reset Calculation, or conducting a new
calculation).

DIgSILENT PowerFactory 2016, User Manual 63

CHAPTER 7. USER SETTINGS

64 DIgSILENT PowerFactory 2016, User Manual

 Part III

Handling
Chapter 8

Basic Project Definition

The basic database structure in PowerFactory and the data model used to define and study a power
system is explained in Chapter 4 (PowerFactory Overview). It is recommended that users become
familiar with this chapter before commencing project definition and analysis in PowerFactory . This
chapter describes how to define and configure projects, and how to create grids.

8.1 Defining and Configuring a Project

There are three methods to create a new project. Two of them employ the Data Manager window and
the third employs the main menu. Whichever method is used the end result will be the same: a new
project in the database.

Method 1: Using the main menu:

• On the main menu choose File → New→ Project.

• Enter the name of the project. Make sure that the Target Folder is set to the folder in which the
project should be created. By default it is set to the active user account folder.
• Press Execute.

Method 2: Using the element selection dialog from the Data Manager:

• In the Data Manager click the New Object button ( )

• In the field at the bottom of the New Object window (IntPrj) (after selecting option Others in the
Elements field). Note that names in PowerFactory are case-sensitive.
• Press Ok. The project folder dialog will then open. Press Ok.

Method 3: Directly via the Data Manager:

• Locate the active user in the left-hand pane of the Data Manager.
• Place the cursor on the active user’s icon or a folder within the active user account and right-click.

• From the context-sensitive menu choose New → Project. Press Ok. The project folder dialog will
then open. Press Ok.

DIgSILENT PowerFactory 2016, User Manual 67

CHAPTER 8. BASIC PROJECT DEFINITION

Note: The ComNew command is used to create objects of several classes. To create a new project it
must be ensured that the Project option is selected.

In order to define and analyse a power system, a project must contain at least one grid and one
study case. After the new project is created (by any of the methods described), a new study case
is automatically created and activated. A dialog used to specify the name and nominal frequency of a
new, automatically-created grid pops up. When the button OK is pressed in the grid dialog:

• The new grid folder is created in the newly-created project folder.

• An empty single line diagram associated with the grid is opened.

The newly-created project has the default folder structure shown in Figure 8.1.1. Although a grid folder
and a study case are enough to define a system and perform calculations, the new project may be
expanded by creating library folders, extra grids, Variations, Operation Scenarios, Operational Data
objects, extra study cases, graphic windows, etc.

Projects can be deleted by right-clicking on the project name in the Data Manager and selecting Delete
from the context-sensitive menu. Only inactive projects can be deleted.

Note: The default structure of the project folder is arranged to take advantage of the data model
structure and the user is therefore advised to adhere to it. Experienced users may prefer to
create, within certain limits, their own project structure for specific advanced studies.

Figure 8.1.1: Default project structure

68 DIgSILENT PowerFactory 2016, User Manual

 8.1. DEFINING AND CONFIGURING A PROJECT

8.1.1 Project Dialog

The project (IntPrj) dialog can be accessed by selecting Edit → Project. . . on the main menu or by
right-clicking the project folder in the Data Manager and selecting Edit from the context-sensitive menu.

The Basic Data page contains basic project settings and allows the creation of new study cases and
grids:

• Pressing the button in the Project Settings field opens a dialog where the validity period of
the project, the input units to be used within the project (i.e. units and the decimal prefixes for
input dialogs) and the calculation settings (i.e. base apparent power and the minimal value of the
resistances and conductances in p.u) are defined.
• Pressing the New Grid button will create a new grid and will open the grid edit dialog. A second
dialog will ask for the study case to which the new grid folder should be added. For additional
information about creating a new grid refer to Section 8.2(Creating New Grids).

• The New Study Case button will create a new study case and will open its dialog. The new study
case will not be activated automatically. For further information about creating study cases refer
to Chapter 11: Study Cases, Section 11.2 (Creating and Using Study Cases).
• When a project is created, its settings (i.e. result box definitions, report definitions, flexible page
selectors, etc.) are defined by the default settings from the system library. If these settings are
changed, the changes are stored in the project’s Settings folder. The settings from another project
or the original (default) ones can be taken by using the buttons Take from existing project or
Set to default in the Changed Settings field of the dialog. The settings can only be changed
when a project is inactive.
• The name of the active study case is shown in the lower part of the dialog window under Active
Study Case. Its dialog can be opened by pressing the button.

• Pressing the Contents button on the dialog will open a new data browser displaying all the folders
included in the current project directory.

The Sharing page of the dialog allows the definition of the project sharing rules. These rules are
particularly useful when working in a multi-user database environment. Further information is given in
Chapter 19 (Data Management).

The Derived Project page provides information if the project is derived from a master project.

The Storage page provides information about the data stored inside the project. By default all changes
within the last 7 days will be stored. This is called the retention period and can be changed on this page.

The Description page is used to add user comments and the approval status.

8.1.2 Project Overview

The Project Overview is illustrated in Figure 8.1.2. It is a dockable window, displayed by default on the
left side of the main application window between the main toolbar and the output window. It displays
an overview of the project allowing the user to assess the state of the project at a glance and facilitates
easy interaction with the project data. The window is docked by default, but can be undocked by the user
and displayed as a floating window that can be placed both inside and outside of the main application
window. If required, the window can be closed by the user. To close or reopen the window, toggle the
option Window → Project Overview from the main menu.

DIgSILENT PowerFactory 2016, User Manual 69

CHAPTER 8. BASIC PROJECT DEFINITION

Figure 8.1.2: Project overview

The following objects and information can be accessed via the Project Overview.

• Study Cases
– Active Study Case
– Inactive Study Cases
– Current Study Time
• Operation Scenarios
– Active Scenario Schedulers
– Active Scenarios
– Inactive Scenarios
• Variations
– Recording Expansion Stage
– List of active Variations with active and inactive Expansion Stages as children
– List of inactive Variations with inactive Expansion Stages as children
• Grid/System Stages
– List of active Grids or System Stages
– List of inactive Grids or System Stages

70 DIgSILENT PowerFactory 2016, User Manual

 8.1. DEFINING AND CONFIGURING A PROJECT

• Trigger
– Active triggers

Entries for active objects are displayed with bold text, entries for inactive objects are displayed as
disabled/grey.

A context-sensitive menu can be accessed by right-clicking on each of the tree entries. The following
actions are available for each of the entries:

• Change active item(s): Activate, Deactivate, change active

• Show all available items
• Edit (open dialog)

• Edit and Browse

• Delete
• Save (for Operation Scenario only)

8.1.3 Project Settings

In the project settings, the validity period of the project can be defined, as can the method used for
calculation of symmetrical components for untransposed lines, amongst other settings.

Validity Period of the Project

PowerFactory 15 extends the idea of a model into the dimension of time. The project may span a period
of months or even years considering network expansions, planned outages and other system events.
The period of validity of a project specifies the time span the network model is valid for.

The validity period is defined by the Start Time and End Time of the project. The study case has study
time, which must fall inside the validity period of the project.

To specify the validity period of the Project:

• Open the Data Manager and browse to the project folder (IntPrj).
• Right-click on it and select Edit from the context-sensitive menu.

• On the Basic Data tab press the project settings button ( ). The project settings dialog will open.

• On the Validity Period page adjust the Start Time and End Time of the project.
• Press OK to accept the changes and close the window.

Advanced Calculation Parameters

• Auto slack assignment

This option only influences the automatic slack assignment (e.g. if no machine is marked as
“Reference Machine”)
– Method 1: all synchronous machines can be selected as slack (reference machine);
– Method 2: a synchronous machine is not automatically selected as slack if, for that machine,
the option on its Load Flow page: Spinning if circuit-breaker is open is disabled.

DIgSILENT PowerFactory 2016, User Manual 71

CHAPTER 8. BASIC PROJECT DEFINITION

– Off: auto slack assignment is switched off; the grid will be considered as de-energised if no
reference machine is defined.
• Calculation of symmetrical components for untransposed lines
The selection of one of these methods defines how the sequence components of lines in Power-
Factory will be calculated:
– Method 1: apply the 012-transformation (irrespective of line transposition). This is the
standard method used;
– Method 2: first calculate a symmetrical transposition for untransposed lines, and then apply
the 012-transformation.

8.1.4 Activating and Deactivating Projects

To activate a project use the option File → Activate Project from the main menu. This shows a tree with
all the projects in the current user’s account. Select the project that should be activated. Alternatively,
a project may be activated by right-clicking on it in the Data Manager and using the context-sensitive
menu.

The last 5 active projects are listed under File in the main menu. The currently active project is the first
entry in this list. To deactivate the currently active project, select it in the list. Alternatively, you may
choose the option File → Deactivate Project from the main menu. To activate another project, select it
in the list of the 5 last active projects.

Note: Only one project can be activated at a time.

8.1.5 Exporting and Importing Projects

Projects (or any folder in the database) can be exported using the *.dz or the *.pfd (PowerFactory Data)
file format. It is recommended to use the new PFD format (*.pfd) whenever possible. This format is
ideal for handling even very large projects. The performance of the import/export using the *.pfd has
been optimised and the consumption of memory resources is significantly lower than with the old file
format (*.dz). All new functions available in the PowerFactory database, e.g. time stamps and versions,
are fully-supported by the new PFD file format.

8.1.5.1 Exporting a Project

To export a project, select File → Export. . . → Data. . . from the main menu or click on the icon of the
Data Manager. Alternatively projects can be exported by selecting the option Export. . . on the project
context-sensitive menu (only available for inactive projects). The dialog is shown in Figure 8.1.3.

• Objects to export: This table shows all objects that will be exported within the *.pfd file.
• Export current state: This option is visible if the project (or, object in the Objects to export
table) has Versions defined. If enabled (default), the current state of the project will be exported.
Otherwise, only the state of the selected Version/s will be exported.
• Versions to export: This table shows all Versions of the Objects to export, if any are available. By
disabling the checkbox for specific Versions, the user can define which Version should or should
not be exported. For master projects, the corresponding Version for the derived project must be
selected. See Section 19.3.1 for further details.
• Export data in retention period: If enabled, data changes from within the retention period will
be exported. See Section 8.1.1 for further details.

72 DIgSILENT PowerFactory 2016, User Manual

 8.1. DEFINING AND CONFIGURING A PROJECT

• Export external data files (e.g. result files): If enabled, calculation results (i.e. result files, plot
data, etc.) will be exported. Otherwise, the calculation must be repeated after importing.
• Export derived project as regular project (only available for derived projects, see Section 19.3.1):
If enabled, a derived project will be exported as an ’adequate’ project. In this case no master
project is required. It should be noted that this project can no longer be reused as a derived
project.
• Export to former PowerFactory version: If the project is intended to be imported into a former
PowerFactory version, this flag must be activated and the version specified.
• PFD file: The path where the *.pfd file will be saved.

Figure 8.1.3: Export dialog

DIgSILENT PowerFactory 2016, User Manual 73

CHAPTER 8. BASIC PROJECT DEFINITION

8.1.5.2 Importing a Project

Projects can be imported by selecting File → Import. . . → Data. . . from the main menu or by clicking
on the icon in the Data Manager. The user can select the type of file to import from the Files of type
field in the Open dialog which pops up. Alternatively, projects can be imported by selecting Import. . .
on the project context-sensitive menu (only available for inactive projects).

Additionally, several import/export filters are available for other data formats.

8.1.6 External References

In order to avoid problems when exporting/importing projects, it is recommended to check for external
references before exporting the project. This can be done by selecting the option Check for external
References via the project context-sensitive menu.

If external references are found, these can be packed before exporting by selecting the option Pack
external References in the project context-sensitive menu.

The user can define the source of the External References (i.e. Global Library, Configuration folder,
etc). A new folder, called “External” containing all external references will be created inside the project.

8.2 Creating New Grids

Electrical networks can be defined in PowerFactory using the graphical editor or the Data Manager.
The graphical method is simple; it consists of selecting the desired network components from the
drawing toolbox and placing them at the desired location on the single line graphic. In this case,
PowerFactory automatically creates the network components represented by the graphical objects in
the active grids/expansion stages. The connections and the corresponding cubicles are automatically
created as the new component is placed (and connected). Using the Data Manager requires the manual
definition of the cubicles within the terminals and the selection of the specific cubicle where a branch
element is to be connected. This manual definition is more suitable for large networks whose graphical
representation becomes complicated. Advanced users may combine both graphical and Data Manager
methods to define and modify their network models more efficiently.

In addition to describing the basic methods used to define and edit network models, this section is
intended to explain practical aspects related to the creation and management of network grouping
objects. The procedures used to create and manage additional network diagrams are also presented
here. Information about defining and working with Variations and Expansion Stages is provided in a
separate section. To begin, a description of the network model definition, and how new grid folders are
created, is required.

Note: Experienced users may define networks combining the Data Manager and the graphical editor.
Good practice is to create and connect the network components in the single line graphic and
multi-edit them in the Data Manager.

To add a grid folder to the current network model, various methods may be employed:

1. Select Edit → Project on the main menu. This will open the dialog of the currently-active project.
Press the New Grid button.

2. Select Insert → Grid . . . on the main menu.

3. Right-click the project folder in the Data Manager and select Edit. Press the New Grid button.

74 DIgSILENT PowerFactory 2016, User Manual

 8.2. CREATING NEW GRIDS

4. Right-click the Network Data folder (in the active project) in a Data Manager window and select
New → Grid from the context-sensitive menu.

The dialog to create a new grid will then pop up. There the grid name, the nominal frequency and a grid
owner (optional) may be specified. A second dialog will appear after the Ok button has been pressed.
In this dialog the study case that the grid will be linked to must be selected. Three options are given:

1. add this Grid/System Stage to active Study Case: Only available when a study case is active.

2. activate a new Study Case and add this Grid/System Stage: Creates and activates a new study
case for the new grid.
3. activate an existing Study Case and add this Grid/System Stage: Add the new grid folder to
an existing, but not yet active study case.

After the Ok button in the second dialog has been pressed, the new grid is created in the Network Model
folder and a reference in the Summary Grid object of the selected study case is created. Normally,
the second option (from the list above) is preferred because this creates a new study case which is
dedicated to the new grid only. This means that the new grid may be tested separately using a load flow
or other calculation. To analyse the combination of two or more grids, new study cases may be created
later, or the existing ones may be altered.

As indicated in Chapter 11(Study Cases), grids can be later added or removed from the active study
case by right-clicking and selecting Add/Remove from Active study case.

DIgSILENT PowerFactory 2016, User Manual 75

CHAPTER 8. BASIC PROJECT DEFINITION

76 DIgSILENT PowerFactory 2016, User Manual

Chapter 9

Network Graphics (Single Line

Diagrams)

9.1 Introduction

PowerFactory works with three different classes of graphics which constitute the main tools used to
design new power systems, controller block diagrams and displays of results:

• Single Line Diagrams (described in this chapter)

• Block Diagrams (described in Section 28.9: Models for Stability Analysis)

• Virtual Instruments (described in Section 18.5: Virtual Instruments)

Diagrams are organised in Graphic Boards for visualisation (see Section 9.5.2 for more information).

9.2 Defining Network Models with the Graphical Editor

In this section it is explained how the tools of the Graphical Editor are used to define and work with
network models.

9.2.1 Adding New Power System Elements

Drawing power system elements is a simple matter of choosing the required element representation in
the Drawing Toolbox located in the right hand pane of the PowerFactory GUI. Input parameters of the
element are edited through the element and type dialog. Complete information about the element and
type parameters are given in the Appendix B Technical References of Models.

To create a new power system element, select the corresponding button in the Drawing Toolbox. This
toolbar is only visible to the user when a project and study case is active and the open graphic is
unfrozen by deselecting the Freeze Mode button ( ). As the cursor is positioned over the drawing
surface, it will have a symbol of the selected tool ’attached’ to it, showing that the cursor is, for example,
in ’Terminal’ drawing mode (to reset the mode either press the one of the cursor icons (rectangular or
free-form selection) or press ESC or right-click with the mouse).

Power system elements are placed and connected in the single line graphic by left clicking on empty

DIgSILENT PowerFactory 2016, User Manual 77

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

places on the drawing surface (places a symbol), and by left clicking nodes (makes a connection). If
wishing to stop the drawing and connecting process press the Escape key or right click at the mouse.

There are basically three ways of positioning and connecting new power system elements:

1. By left clicking on one or more nodes to connect and position the element directly. Single port
elements (loads, machines) will be positioned directly beneath the nodes at a default distance
(the symbol can later be moved if required). Double or triple port objects (transformers) will be
centred between the first two terminal connections automatically.

2. By first left clicking on an empty place to position the symbol and then left clicking a node to make
the connections.
3. By first left clicking on an empty place, consequently clicking on the drawing surface to define a
non-straight connection line and finally clicking on a terminal to make the connection.

Note: Nodes for connecting branches are usually defined before placing them on the single line dia-
gram. However, it is possible to place ’connection free’ branch element on the single line diagram
by pressing the Tab key once for each required connection (e.g. twice for a line, three times for a
three winding transformer)

Figure 9.2.1 shows an example of a generator placed according to the first method (left generator),
one placed according to the second method (middle generator), and one placed according to the third
method (right generator with long connection).

Figure 9.2.1: Illustration of graphical connection methods

If a load or machine is connected to a terminal using the first method (single left click on busbar), but a
cubicle already exists at that position on the busbar, the load or machine symbol will be automatically
positioned on the other side of the terminal, if possible.

Note: By default all power system elements are positioned “bottom down”. However, if the Ctrl key
is pressed when the graphic symbol is positioned onto the drawing surface, it will be positioned
either turned 90 degrees (terminals) or 180 degrees (edge elements). If the element has already
been placed and the user wishes to flip it to the other side of the terminal, it can be done by
selecting the element and the right-click → Flip At Busbar.

Once drawn, an element can be rotated by right-click and selecting from the Rotate commands. Fig-
ure 9.2.2 shows an example of rotated and flipped power system elements.

78 DIgSILENT PowerFactory 2016, User Manual

 9.2. DEFINING NETWORK MODELS WITH THE GRAPHICAL EDITOR

Figure 9.2.2: Flipped and rotated power system elements

The connection between edge elements and terminals is carried out by means of cubicles. When work-
ing with the graphical editor, the cubicles are automatically generated in the corresponding terminal.

Note: When connections to terminals are defined with switch elements of the class ElmCoup (circuit
breakers), cubicles without any additional switches (StaSwitch) are generated.

9.2.2 Drawing Nodes

When commencing a single line diagram, it is common to first place the required nodes / terminals
(ElmTerm) on the graphic. There are several symbol representations available for busbar type terminals,
from the drawing toolbox on the right-hand pane of the PowerFactory GUI.

Busbar This is the most common representation of a node.

Busbar (Short) Looks the same as a Busbar but is shorter and the results box and name is
placed on the “Invisible Objects” layer by default. Typically used to save space or to unclutter the
graphic.

Junction / Internal Node Typically used to represent a junction point, say between an overhead
line and cable. The results box and name is placed on the “Invisible Objects” layer by default.

Busbar (rectangular) Typically used for reticulation and / or distribution networks.

Busbar (circular) Typically used for reticulation and / or distribution networks.

Busbar (polygonal) Typically used for reticulation and / or distribution networks.

Busbars (terminals) should be placed in position and then, once the cursor is reset, dragged, rotated
and sized as required. Re-positioning is performed by first left clicking on the terminal to mark it, and
then click once more so that the cursor changes to . Hold the mouse button down and drag the
terminal to a new position. Re-sizing is performed by first left clicking on the terminal to mark it. Sizing
handles appear at the ends.

9.2.3 Drawing Branch Elements

Single port elements (loads, machines, etc.) can be positioned in two ways. The simplest method is
to select the symbol from the toolbar and then left click the busbar where the element is to be placed.

DIgSILENT PowerFactory 2016, User Manual 79

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

This will draw the element at a default distance under the busbar. In case of multi busbar systems, only
one of the busbars need be left-clicked. The switch-over connections to the other busbars will be drawn
automatically.

The ’free-hand’ method first places the element symbol wherever desired, that is, first click wherever
you wish to place the symbol. The cursor now has a ’rubber band’ connected to the element (i.e. a
dashed line), left-clicking on another node will connect it to that node. To create corners in the joining
line left click on the graphic. The line will snap to grid, be drawn orthogonally, as determined by the
“Graphic Options” that have been set.

Double port elements (lines, transformers, etc.) are positioned in a similar manner to single port
symbols. By left-clicking the first busbar, the first connection is made. The second connection line
is now held by the cursor. Again, left-clicking the drawing area will create corners. Double-clicking the
drawing area will position the symbol (if not a line or cable - e.g. a transformer). The second connection
is made when a node is left clicked.

Triple port elements (e.g. three-winding transformers) are positioned in the same manner as two port
symbols. Clicking the first, and directly thereafter the second node, will place the symbol centred
between the two nodes, which may be inconvenient. Better positioning will result from left clicking
the first busbar, double-clicking the drawing space to position the element, and then making the second
and third connection.

The ’free-hand’ method for two and triple port elements works the same as for one port elements.

Note: Pressing the Tab key after connecting one side will leave the second leg unconnected, or jump to
the third leg in the case of three port elements (press Tab again to leave the third leg unconnected).
Pressing Esc or right-click will stop the drawing and remove all connections. If the element being
drawn seems as if it will be positioned incorrectly or untidily there is no need to escape the drawing
process, make the required connections and then right-click the element and Redraw the element
whilst retaining the data connectivity.

Annotations are created by clicking one of the annotation drawing tools. Tools are available for drawing
lines, squares, circles, pies, polygons, etc. To draw these symbols left click at on an empty space on
the single line diagram and release the mouse at another location (e.g. circles, lines, rectangles). Other
symbols require that you first set the vertices by clicking at different positions and finishing the input
mode by double-clicking at the last position.

For further information on defining lines, see Section 9.3 (Defining and Working with Lines and Cables).

9.2.4 Marking and Editing Power System Elements

To mark (select) a power system element click on it with the cursor. The element is then highlighted
and becomes the “focus” of the next action or command. For branch elements, the parts near their
connection to nodes are treated differently and show specific context sensitive menu options regarding
the marked side of the element (e.g. to insert a new device at the line end or to disconnect the line). To
get all the menu options anyway, hold down the Ctrl-key while clicking the right mouse button.
The element can be un-marked or de-selected by clicking on another element or by clicking onto some
free space in the graphic.

There are different ways to mark several objects at once:

• To mark all graphical elements, press the All button ( ). The keyboard short cut Ctrl+A may also
be used.
• To mark a set of elements at the same time click on a free spot in the drawing area, hold down
the mouse key and move the cursor to another place where you release the mouse button. All

80 DIgSILENT PowerFactory 2016, User Manual

 9.2. DEFINING NETWORK MODELS WITH THE GRAPHICAL EDITOR

elements in the so defined rectangle will now be marked. A setting, found in the User Settings
dialog under the ’Graphic Windows’ page, on the Advanced tab, can alter the manner in which
objects are marked using this marking method, as either ’Partial’ or ’Complete’. ’Complete’ means
that the whole object marked must lie inside the rectangle.
• To mark more than one object, hold down the Ctrl key whilst marking the object.
• Holding down the Alt-key while clicking on the same object again marks all the adjacent objects.
Doing this several times marks more and more connected objects.

• In PowerFactory it is possible to place a terminal on an existing line in the single line diagram by
placing the terminal on the line itself. Moving the terminal to a different location on the single line
diagram may move line sections in an undesirable manner. By holding the Ctrl+Alt keys whilst
moving the terminal, the line sections will not be moved. However, note that this does not change
the actual location of the terminal along the line.

The data of any element (its edit dialog) may be viewed and edited by either double-clicking the graphic
symbol under consideration, or by right-clicking it and selecting Edit Data.

When multiple objects are selected, their data can be viewed and edited trough a data browser by
right-clicking the selection and choosing Edit Data from the context sensitive menu.

9.2.5 Interconnecting Power Subsystems

Interconnections between two different graphics can be achieved using two methods:

1. Representing a node in additional different graphics by copying and pasting the graphic only and
then by connecting branch and edge elements to the graphical object in the additional graphic.
This is performed by copying the desired node (right-click → Copy ) and then clicking on the other
graphic in which it should be represented and right-click → Paste Graphic Only. Only a graphical
object is pasted into the second graphic and no new data element is created.
2. Ensure that there is a node to connect to in the graphics that are to be interconnected. Then
connect an edge element between the two graphics.

Example

In this example a line will be used to interconnect two regions according to the second method.

1. Select a line drawing tool from the toolbar and create the first connection as normal by left clicking
a node (see Figure 9.2.3).

2. Double-click to place the symbol. Your cursor is now attached to the line by a ’rubber band’.
Move the cursor to the bottom of the drawing page and click on the tab of the graphic that the
interconnection is to be made to (see Figure 9.2.4).
3. Once in the second graphic left click to place the line symbol (see Figure 9.2.5) and then left click
on the second node.

The interconnected leg is shown by an symbol. Right-clicking on the element presents a Jump to
next page option.

DIgSILENT PowerFactory 2016, User Manual 81

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Figure 9.2.3: First step to interconnecting

Figure 9.2.4: Second step to interconnecting

Figure 9.2.5: Third step to interconnecting

Note: The first method of interconnection, that of representing a node in two, or more, different graphics,
may lead to confusion at a later point as the ’inflow’ and ’outflow’ to the node will not appear correct

82 DIgSILENT PowerFactory 2016, User Manual

 9.2. DEFINING NETWORK MODELS WITH THE GRAPHICAL EDITOR

when just one graphic is viewed - especially if a user is not familiar with the system. The node
may be right-clicked to show all connections in what is known as the ’Station Graphic’ (menu
option Show station graphic). Thus, the second method may be preferred. To check for nodes that
have connections on other graphics the “Missing graphical connections” diagram colouring may
be employed.

9.2.6 Working with Substations in the Graphical Editor

Substations and Secondary Substations from existing templates are created using the network dia-
grams. The substations are represented in these diagrams by means of composite node symbols.

9.2.6.1 Creating a New Substation in an Overview Diagram

Overview diagrams are single line diagrams without detailed graphical information of the substations.
Substations and Secondary Substations are illustrated as “Composite Nodes”, which can be coloured
to show the connectivity of the connected elements (“Beach Ball”). Substations and Secondary Sub-
stations from pre-defined templates (or templates previously defined by the user) are created using the
network diagrams. The substations are represented in these diagrams by means of composite node
symbols.

To draw a substation from an existing template in an overview diagram:

• Click on the symbol of the composite node ( or ) for Substations or ( ) for Secondary
Substations listed among the symbols on the right-hand drawing pane.
• Select the desired substation template from the list.
• Click on the overview single line diagram to place the symbol. The substation is automatically
created in the active grid folder.
• Right click the substation, select Edit Substation, and rename the substation appropriately.
• Close the window with the templates.
• Press Esc or right click on the mouse to get the cursor back.
• Resize the substation symbol in the overview diagram to the desired size.

A diagram of the newly created substation can be opened by double clicking at the composite node
symbol. In the new diagram it is possible to rearrange the substation configuration and to connect the
desired components to the grid.

To resize a composite node:

• Click once on the composite node you want to resize.

• When it is highlighted, place the cursor on one of the black squares at the corners and hold down
the left mouse button.
• A double-arrow symbol appears and you can resize the figure by moving the mouse. For a
rectangular composite node you can also resize the shape by placing the cursor on one of the
sides.

For further information on templates refer to Chapter 13: Project Library, Section 13.4 (Templates
Library).

To show the connectivity inside a composite node:

DIgSILENT PowerFactory 2016, User Manual 83

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Press the button to open the colouring dialog. Select the ’Function’ for which the colouring mode is
relevant (for example, select the ’Basic Data’ page). Under ’Other’ select ’Topology’, and then ’Station
Connectivity’.

There are two ways to open the graphic page of a substation. The first is to double-click on the
corresponding composite node in the overview diagram. The second is to go to the graphic object
of the substation in the Data Manager, right-click and select Show Graphic.

Details of how to define templates are provided in Chapter 13 (Project Library).

9.2.6.2 Substation Switching Rules

Switching Rules ( ) (IntSwitching) store switching actions for a selected group of switches that are
defined inside a substation. The different switching actions (no change, open or close) are defined by
the user considering different fault locations that can occur inside a substation. By default, the number
of fault locations depends on the number of busbars and bay-ends contained inside the substation;
although the user is allowed to add (and remove) specific fault locations and switches belonging to the
substation. The switch actions will always be relative to the current switch positions of the breakers.

The selection of a Switching Rule for a substation is independent of the selection of a Running Arrange-
ment and if required, the reference to the switching rule in a substation can be stated to be operational
data; provided the user uses the Scenario Configuration object. For more information on the scenario
configuration refer to Chapter 15 (Operation Scenarios).

A typical application of Switching Rules is in contingency analysis studies, where there is a need to
evaluate the contingency results considering the “actual” switch positions in a substation and compare
them to the results considering a different substation configuration (for the same contingency).

To create a switching rule

To create a new Switching Rule:

• Edit a Substation, either by right-clicking on the substation busbar from the single line graphic,
and from the context-sensitive menu choosing Edit a Substation, or by clicking on an empty place
in the substation graphic, and from the context-sensitive menu choosing Edit Substation. This will
open the substation dialog.

• Press the Select button ( ) in the Switching Rule section and select New. . .
• The new Switching Rule dialog pops up, where a name and the switching actions can be specified.
The switching actions are arranged in a matrix where the rows represent the switches and the
columns the fault locations. By default the fault locations (columns) correspond to the number of
busbars and bay-ends contained inside the substation, while the switches correspond only to the
circuit breakers. The user can nevertheless add/remove fault locations and/or switches from the
Configuration page. The switch action of every defined breaker in the matrix can be changed by
double clicking on the corresponding cell, as illustrated in Figure 9.2.6. Press afterwards Ok.

• The new switching rule is automatically stored inside the substation element.

84 DIgSILENT PowerFactory 2016, User Manual

 9.2. DEFINING NETWORK MODELS WITH THE GRAPHICAL EDITOR

Figure 9.2.6: Switching Rule Dialog

To select a Switching Rule

A Switching Rule can be selected in the Basic Data page of a substation dialog (ElmSubstat) by:

• Opening the substation dialog.

• Pressing the Select button ( ) in the Switching Rule section. A list of all Switching Rules for the
current substation is displayed.
• Selecting the desired Switching Action.

To apply a Switching Rule

A Switching Rule can be applied to the corresponding substation by pressing the Apply button from
within the switching rule dialog. This will prompt the user to select the corresponding fault locations
(busbars) in order to copy the statuses stored in the switching rule directly in the substation switches.
Here, the user has the option to select either a single fault location, a group or all of them.

The following functional aspects must be regarded when working with switching rules:

• A switching rule can be selected for each substation. By default the selection of a switching rule
in a substation is not recorded in the operation scenario. However, this information can defined
as part of an operational scenario by using the Scenario Configuration object (see Chapter 15:
Operation Scenarios).
• If a variation is active the selection of the Switching Rule is stored in the recording expansion
stage; that is considering that the Scenario Configuration object hasn’t been properly set.

To assign a Switching Rule

The Assign button contained in the switching rule dialog allows to set it as the one currently selected
for the corresponding substation. This action is also available in the context-sensitive menu in the Data
Manager (when right-clicking on a switching rule inside the Data Manager).

To preview a Switching Rule

The Preview button contained in the switching rule dialog allows to display in a separate window the
different switch actions for the different fault locations of the corresponding substation.

DIgSILENT PowerFactory 2016, User Manual 85

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.2.7 Working with Composite Branches in the Graphical Editor

New composite branches can be created in the Data Manager using the procedure described in Chap-
ter 10, Section 10.3.4 (Defining Composite Branches in the Data Manager). The definition and con-
nection of the branch components can then be carried out in the relevant single line diagram, which is
automatically generated after the creation of the new branch.

Branches from previously defined templates are created using the single line diagram. The branches
are represented in these diagrams by means of the Composite Branch symbol ( ). To create a new
branch from a template:

• Click on the Composite Branch button ( ) listed among the symbols on the right-hand drawing
pane. A list of available templates (from the Templates library) for branches will appear. If only
one Branch template exists, no list is shown.
• From this list choose the template that you want to create the branch from.
• If the branch is to be connected with terminals of the same single line graphic, simply click once
on each terminal.
• If the branch is to be connected with a terminal from another single line diagram, you have to
’Paste graphically’ one of the terminals on the diagram where you want to represent the branch,
or connect across pages as discussed in Section 9.2.5 (Interconnecting Power Subsystems).

• If the branch is to be connected with terminals from a substation, click once on each composite
node to which the branch is to be connected. You will be automatically taken inside each of those
composite nodes to make the connections. In the substation graphic click once on an empty spot
near the terminal where you want to connect the branch end, and then on the terminal itself.

A diagram of the newly created branch can be opened by double clicking at the composite branch
symbol. In the new diagram it is possible to rearrange the branch configuration and to change the
branch connections.

Details of how to define templates are provided in Chapter 13 (Project Library).

9.2.8 Working with Single and Two Phase Elements

It is possible to define the phase technology of elements such as terminals, lines, and loads. In
instances where the number of phases of a connecting element (e.g. a circuit breaker or line) is equal
to the number of phases of the terminal to which it connects, PowerFactory will automatically assign
the connections. However, when connecting single-phase elements to a terminal with greater than one
phase, or two-phase elements to terminals with greater than three phases, it is sometimes necessary to
adjust the phase connectivity of the element to achieve the desired connections. The phase connectivity
can be modified as follows:

• Open the dialog window of the element (by double-clicking on the element).

• Press the Figure >> button to display a figure of the elements with its connections on the bottom
of the dialog window.
• Double-click on the dark-red names for the connections inside this figure.
• Specify the desired phase connection/s.

Alternatively, click the right arrow ( ) next to the Terminal entry and specify the desired phase connec-
tion/s.

86 DIgSILENT PowerFactory 2016, User Manual

 9.3. DEFINING AND WORKING WITH LINES AND CABLES

Note: It is possible to colour the grid according to the phases (System Type AC/DC and Phases). For
more information about the colouring refer to Section 9.6.7.1 (Diagram Colouring).

9.3 Defining and Working with Lines and Cables

This section describes specific features and aspects of line and cable data models used in PowerFactory
. Detailed technical descriptions of the models are provided in Appendix B (Technical References of
Models).

In PowerFactory , lines and cables are treated alike, they are both instances of the generalised line
element ElmLne. A line may be modelled simply as a point-to-point connection between two nodes and
will refer to a line (TypLne), tower (TypTow), a tower geometry (TypGeo), a line coupling (ElmTow), or a
cable system coupling (ElmCabsys) type. Alternatively, lines may be subdivided into sections referring
to different types.

Note: Anywhere that ’line’ is written in this section, ’lines and/or cables’ may be read, unless otherwise
specified.

The two basic line configurations are depicted in Figure 9.3.1:

1. Top line: the simplest line is a single line object (ElmLne).

2. Bottom line: such a single line may be subdivided into line section objects (ElmLnesec) at any
time/location. No terminals are allowed between two sections, but the sections may have different
line types.

Figure 9.3.1: Basic line configurations

The purpose of separating lines into sections is to obtain different line parts, with different types (such as
when a line uses two or more different tower types, or when manual transpositions should be modelled
- since the “Transposed” option in the type object is a perfect, balanced, transposition).

9.3.1 Defining a Line (ElmLne)

The simplest line model is a point-to-point connection between two nodes. This is normally done in the
single line graphic by selecting the ( ) icon and by left clicking the first terminal, possibly clicking on
the drawing surface to draw a corner in the line and ending the line at the second terminal by left clicking
it. This will create an ElmLne object in the database. When this object is edited, the following dialog will
appear.

DIgSILENT PowerFactory 2016, User Manual 87

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Figure 9.3.2: Editing a transmission line

The dialog shows the two cubicles to which the transmission line is connected (’terminal i’ and ’terminal
j’). The example in Figure 9.3.2 shows a line which is connected between the nodes called ’Line End
Terminal’ and ’Line Feeder Bus’ from a grid called ’ North’. The line edit dialog shows the name of the
node (in red) in addition to the name of the cubicle (in blue). The actual connection point to the node
is the cubicle and this may be edited by pressing the edit button ( ). The cubicle may be edited to
change the name of the cubicle, add/remove the breaker, or change phase connectivity as discussed in
Section 9.2.8 (Working with Single and Two Phase Elements).

The type of the line is selected by pressing the ( ) next to the type field. Line types for a line/ line route
are:

• The TypLne object type, where electrical parameters are directly written (the user can select if the
type is defined for an overhead line or a cable).
• Tower types (TypTow and TypGeo), where geometrical coordinates and conductor parameters are
specified, and the electrical parameters are calculated from this data. Selection of the tower type
will depend on the user’s requirement to link conductor type data to the line element as in TypGeo
(for re-use of the one tower geometry with different conductors), or to link conductor type data to
the tower type as in TypTow (for re-use of one tower geometry with the same conductors).

Once the lines (or cables) have been created it is possible to define couplings between the circuits that
they are representing by means of line coupling elements ElmTow (for overhead lines) and cable system
coupling elements ElmCabsys (for cables).

88 DIgSILENT PowerFactory 2016, User Manual

 9.3. DEFINING AND WORKING WITH LINES AND CABLES

Details of how to create Line Sections, Cable Systems, and Line Couplings are provided in the fol-
lowing sections, and further information about line/cable modelling is given in the respective Technical
References.

9.3.2 Defining Line Sections

To divide a line into sections:

• Press the Sections/Line Loads button in the line dialog. This will open a data browser showing
the existing line sections (if the line has not been sectioned, it will be empty).

• Click on the new object icon ( ) and select the element Line Sub-Section (ElmLnesec).
• The edit dialog of the new line section will pop up. There it is possible to define the type and length
of the new section.

9.3.3 Example Cable System

Consider a three-phase underground cable comprised of three single-core cables with sheaths. The
cable system is created within the active project by taking the following steps.

1. Create a Single Core Cable Type (TypCab) and Cable Definition Type (TypCabsys):
• Navigate to the ’Equipment Type Library’ and select the New Object icon, or on the right-hand
side of the Data Manager right-click and select New → Others.
• Select ’Special Types’, ’Single Core Cable Type’, and then Ok.
• Enter the Type parameters and select Ok. (Note that in this example, a Sheath is also
selected, and therefore a separate line will later be defined in the Network Model to represent
the sheath.)
• Again select the New Object icon, or on the right hand side of the Data Manager right-click
and select New → Others.
• Select ’Special Types’, ’Cable Definition’, and then Ok.
• Enter type parameters including ’Earth Resistivity’, and ’Coordinates of Line Circuits’ (note
that positive values indicate the depth below the surface). Select the Single Core Cable Type
defined in the previous steps and press Ok.
2. Create the Network Model:

• Add four terminals in the single line diagram at the same voltage defined in the Single Core
Cable Type.
• Connect a Line Element between two of the terminals to represent the phase conductors,
and enter the element parameters.
• Connect another Line Element between the other two terminals to represent the sheath,
and enter the element parameters. (Add connections from the sheath terminals to earth as
required.)
3. Create a Cable System Element (ElmCabsys):
• Create a Cable System by selecting the two lines drawn in the single line diagram (hold down
Ctrl and left-click each line). Then right-click one of the lines and select Define → Cable
System from the context sensitive menu. Alternatively, define the cable system in the Data
Manager by creating a New Object and selecting Other → Net Elements→ Cable System,
and then select the required Cable Definition and Line Elements to represent the Conductor
and Sheath circuits.

DIgSILENT PowerFactory 2016, User Manual 89

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

• Select the Cable Definition defined in step 1 and press Ok twice.

Note that the steps above could be conducted in an alternative order. For example, item 2 could be
completed before 1. Also, item 3 could be completed before item 1, and Cable Types could be created
at the time the Cable System Element is created. However, the recommended approach is to first define
the Type data that is to be used in the Network Model, then to create the Network Model with particular
instances of the cable as in the example.

Figure 9.3.3 illustrates the interrelationship between the elements and types used to define cable
systems inPowerFactory. Note that by right-clicking the line that represents the sheath and selecting
’Edit Graphic Object’ the Line Style can be modified to indicate graphically that this line represents the
sheath.

90 DIgSILENT PowerFactory 2016, User Manual

 9.3. DEFINING AND WORKING WITH LINES AND CABLES

Figure 9.3.3: Example Cable System

DIgSILENT PowerFactory 2016, User Manual 91

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.3.4 Example Line Couplings

Consider an example where there are two parallel transmission lines, each with a three-phase HV (132
kV) circuit, three-phase MV (66 kV) circuit, and two earth conductors. The tower element is created
within the active project by taking the following steps.

1. Create the Conductor Types (TypCon) for phase and earth conductors:
• Navigate to the ’Equipment Type Library’ and select the New Object icon, or on the right-hand
side of the Data Manager right-click and select New → Others.
• Select ’Special Types’, ’Conductor Type’, and then Ok.
• Enter the Type parameters and select Ok. In this example, conductors are defined for HV,
MV, and earth conductors.
2. Create a Tower Geometry Type (TypeGeo):
• Again select the New Object icon, or on the right hand side of the Data Manager right-click
and select New → Others.
• Select ’Special Types’, ’Tower Geometry Type’, and then Ok.
• Enter type parameters for the number of Earth Wires and Line Circuits (in this example, two
earth wires and two line circuits), and the coordinates of the conductors.
3. Create the Network Model:

• Add two HV and two MV terminals in the single line diagram (at voltages consistent with the
previously defined conductor types).
• Connect two Line Elements between the HV terminals, connect two Line Elements between
the MV terminals, and enter element parameters.

4. Create a Line Couplings Element (ElmTow):

• Create a Line Coupling by selecting the four lines drawn in the single line diagram (hold
down Ctrl and left-click each line). Then right-click one of the lines and select Define →
Line Couplings from the context sensitive menu. Alternatively, define the Line Coupling in
the Data Manager by creating a New Object and selecting Other → Net Elements→ Line
Couplings.
• Enter the Number of Overhead Line Systems (in this case, two) select the previously defined
tower Geometries, Earth Wires, Circuits, and Types, and enter element parameters such as
the Distance between the Towers.
• Optionally define a Route so that the single line diagram may be coloured based on the
defined Line Couplings and press Ok.

Note that the steps above could be conducted in an alternative order. For example, item 3 could be
completed before 1 and 2. Also, item 4 could be completed before items 1 and 2, and Conductor
Types and Towers could be created at the time the Line Couplings Element is created. However, the
recommended approach is to first define the Type data that is to be used in the Network Model, then to
create the Network Model with particular instances of the lines/towers as in the example.

Figure 9.3.4 illustrates the interrelationship between the elements and types used to define Line Cou-
plings (Tower Elements) in PowerFactory.

92 DIgSILENT PowerFactory 2016, User Manual

 9.4. NEUTRAL WINDING CONNECTION IN NETWORK DIAGRAMS

Figure 9.3.4: Example Tower

9.4 Neutral winding connection in network diagrams

PowerFactory offers the user the option to explicitly represent the neutral connections and interconnec-
tions of the following widely used elements:

DIgSILENT PowerFactory 2016, User Manual 93

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

• Power transformers (ElmTr2 and ElmTr3)

• Shunt elements (ElmShunt)

• External grids (ElmXnet)

• Synchronous (ElmSym) and asynchronous machines (ElmAsm)
• Static generators (ElmGenstat)
• PV systems (ElmPvsys)

• Neutral earthing elements (ElmNec)

The interconnection of separate neutral wires is illustrated with the help of the Synchronous Generator.

A separate neutral connection can be activated by choosing the option N-Connection on the Zero
Sequence/Neutral Conductor tab on the basic data page of the element as shown in figure 9.4.1, the
graphical symbol of the object will change. An illustration for the Synchronous Generator element is
shown in figure 9.4.2. Please note, once the N-Connection via a separate terminal option is selected,
the Vector Groups layer can no longer be hidden in the single line diagram.

Figure 9.4.1: Zero Sequence/Neutral Connection Tap

Figure 9.4.2: Generator with N-Connection via separate terminal

To connect the neutral of the Element to a neutral busbar, right click on the element and press Connect
Element. An example of a single line diagram with the interconnection of neutral wires is shown in figure
9.4.3. A Neutral terminal is configured by ensuring that the Phase Technology of the terminal is set to
N as shown in figure 9.4.4.

94 DIgSILENT PowerFactory 2016, User Manual

 9.4. NEUTRAL WINDING CONNECTION IN NETWORK DIAGRAMS

Figure 9.4.3: Grid with neutral winding connection

Figure 9.4.4: Set neutral Terminal

DIgSILENT PowerFactory 2016, User Manual 95

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.5 Graphic Windows and Database Objects

In the PowerFactory graphic windows, graphic objects associated with the active study case are dis-
played. Those graphics include single line diagrams, station diagrams, block diagrams and Virtual
Instruments. Many commands and tools are available to edit and manipulate symbols in the graphics.
The underlying data objects may also be accessed and edited from the graphics, and calculation results
may be displayed and configured.

Many of the tools and commands are found in the drop down menus or as buttons in the toolbars, but by
far the most convenient manner of accessing them is to use the right mouse button to display a menu.
This menu is known as a ’Context Sensitive Menu’; PowerFactory evaluates where the tip of your cursor
is, and then presents a menu that is appropriate to the cursor location. Thus cursor position is important
when selecting various menu options. It is important to keep the cursor in place when right-clicking, as
the menu presented is determined from cursor position primarily, and not from the selected or marked
object.

9.5.1 Network Diagrams and Graphical Pages

Four types of graphical pages are used in PowerFactory :

1. Single Line Diagrams (network diagrams) for entering power grid definitions and for showing
calculation results.

2. Detailed graphics of substations or branches (similar to network diagrams) for showing busbar
(nodes) topologies and calculation results
3. Block Diagrams for designing logic (controller) circuits and relays.

4. Virtual Instrument Pages for designing (bar) graphs, e.g. for the results of a stability calculation,
bitmaps, value boxes, etc...

The icon Graphical Pages ( ) can be found inside the Data Manager. Grids, substations, branches,
and controller types (common and composite types in PowerFactory terminology) each have a graphical
page. In order to see the graphic on the screen, open a Data Manager and locate the graphic page
object you want to show, click on the icon next to it, right-click and select Show Graphic. The “Show
Graphic” option is also available directly from each object. So for example you can select a grid in the
Data Manager, right-click, and show the graphic. The graphic pages of grids and substations are to be
found in the subfolder Diagrams ( ) under the “Network Model” folder.

Note that it is also possible to store Diagrams within the Grid, although this is generally not recom-
mended.

96 DIgSILENT PowerFactory 2016, User Manual

 9.5. GRAPHIC WINDOWS AND DATABASE OBJECTS

Figure 9.5.1: The Diagrams folder inside the Data Manager

9.5.2 Active Graphics, Graphics Board and Study Cases

The graphics that are displayed in an active project are determined by the active study case. The study
case folder contains a folder called the ’Graphics Board’ folder (SetDesktop) in which references to the
graphics to be displayed are contained. This folder is much like the ’Summary Grid’ folder which is
also stored within the Study Case, and links active grids to the Study Case. Both the Graphics Board
and Summary Grid are automatically created and maintained and should generally not be edited by the
user.

Within a PowerFactory project, the Network Model folder contains a sub-folder called Diagrams. This
sub-folder should generally also not be edited by the user as it is automatically created and maintained.
It contains the objects that represent single line and substation graphics (IntGrfnet objects). More
than one graphic (single line or substation diagrams) may be created for a grid, either to display the
different grid elements over several pages, or to display the same grid elements in different graphical
arrangements.

Consider the ’Project’ that is shown in Figure 9.5.2. The active study case is called Study Case_1 and
the active grid has three single line graphics that have been created for it, Grid_1, Grid_2 and Grid_3.
The graphics board folder in the study case has a reference to only the Grid_1 graphic object and thus
only this graphic for the grid will be shown when the study case is activated.

In the case of single line graphics, the references in the graphics board folder are created when the
user adds a grid to a study case. PowerFactory will ask the user which graphics of the grid should be
displayed. At any time later the user may display other graphics by right-clicking the grid and selecting
Show Graphic from the context sensitive menu. Graphics may be removed from the active study case
by right-clicking the tab at the bottom of the corresponding graphic page and selecting Remove Page(s).

The study case and graphics board folder will also contain references to any other graphics that have
been created when the study case is active, such as Virtual Instrument Panels.

DIgSILENT PowerFactory 2016, User Manual 97

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Figure 9.5.2: Relationship between the study case, graphics board and single line diagrams

9.5.3 Single Line Graphics and Data Objects

In a simple network there may be a 1:1 relationship between data objects and their graphical repre-
sentations, i.e. every load, generator, terminal and line is represented once in the graphics. However,
PowerFactory provides additional flexibility in this regard. Data objects may be represented graphically
on more than one graphic, but only once per graphic. Thus a data object for one terminal can be
represented graphically on more than one graphic. All graphical representations contain the link to the
same data object.

Furthermore, graphical symbols may be moved without losing the link to the data object they represent.
Likewise, data objects may be moved without affecting the graphic.

The graphics themselves are saved in the database tree, by default in the Diagrams folder of the Network
Model. This simplifies finding the correct Single Line graphic representation of a particular grid, even in
the case where there are several graphic representations for one grid.

When the drawing tools are used to place a new component (i.e. a line, transformer, etc.) a new data
object is also created in the database tree. A Single Line Graphic object therefore has a reference
to a grid folder. The new data objects are stored into the ’target’ folders that the graphics page are
associated with. This information may be determined by right-clicking the graphic → Graphic Options,
see Section 10.6 (Editing Data Objects in the Data Manager) for more information.

Since data objects may have more than one graphic representation the deletion of a graphic object
should not mean that the data object will also be deleted. Hence the user may choose to delete only the
graphical object (right-click menu → Delete Graphical Object only ). In this case the user is warned that
the data object will not be deleted. This suggests that a user may delete all graphical objects related to
a data object, with the data object still residing in the database and being considered for calculations.

When an element is deleted completely (right menu option → Delete Element) a warning message will
confirm the action. This warning may be switched off in the User Settings dialog, General page, “Always
confirm deletion of Grid Data”).

98 DIgSILENT PowerFactory 2016, User Manual

 9.5. GRAPHIC WINDOWS AND DATABASE OBJECTS

9.5.4 Editing and Selecting Objects

Once elements have been drawn on the graphic the data for the element may be viewed and edited by
either double-clicking the graphic symbol under consideration, or by right-clicking it and selecting Edit
Data.

The option Edit and Browse Data will show the element in a Data Manager environment. The object
itself will be selected (highlighted) in the Data Manager and can be double-clicked to open the edit
dialog. A new Data Manager will be opened if no Data Manager is presently active. If more than one
symbol was selected when the edit data option was selected, a data browser will pop up listing the
selected objects. The edit dialogs for each element may be opened from this data browser one by
one, or the selected objects can be edited in the data browser directly, see Section 10.6 (Editing Data
Objects in the Data Manager).

Finding specific elements in a large project may be difficult if one had to look through the single line
diagram alone. PowerFactory includes the Mark in Graphic tool, to assist the user in finding elements
within the graphic. To use this tool the user has to first search for the desired object in the Data Manager
using any of the methods presented in Chapter 10 (Data Manager). Once a searched object/element
is identified, it may be right-clicked and the option Mark in Graphic selected. This action will mark the
selected object in the single line graphic where it appears. This can also be done pressing Crtl+M.

When performing this command ensure that the object itself is selected, as shown in Figure 9.5.3. The
menu will be different to that seen when selecting an individual field, as shown in Figure 9.5.4.

Figure 9.5.3: Selecting an object correctly to Mark in Graphic

DIgSILENT PowerFactory 2016, User Manual 99

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Figure 9.5.4: Selecting an object incorrectly to Mark in Graphic

Note: The position of an object in the database tree can be found by:
• Opening the edit dialog. The full path is shown in the header of the dialog.
• Using the keyboard shortcut Ctrl+E, which opens the Data Manager with the element marked
in the folder hierarchy.
• Right-clicking the object and selecting Edit and Browse. This will open a new database
browser when required, and will focus on the selected object.

9.5.5 Creating a New Project

A new project may be created by selecting File → New on the main menu. This creates a new Project
folder and a dialog is displayed where the user can define a grid folder in the Project folder. Finally the
Graphic page in which the single line diagram will be displayed.

9.5.6 Creating New Graphic Windows

A new graphic window can be created using the New command dialog. This dialog may be opened
using one of the following methods:

• By pressing the icon.

• By pressing the keyboard shortcut Ctrl+N.

• By selecting from the Insert menu on the main menu.

100 DIgSILENT PowerFactory 2016, User Manual

 9.5. GRAPHIC WINDOWS AND DATABASE OBJECTS

The ComNew dialog must be configured to create the desired new object and the new object should
be named appropriately. Ensure that the correct target folder for the new object is selected. Graphical
objects that may be created using this dialog (DiaPagetyp) are:

Grid Creates a new grid folder and a new Single Line Graphic object in that folder. The (empty)
single line graphic will be displayed.

Block Diagram Creates a new Block Diagram folder in the selected folder and a new Block
Diagram Graphic object. The (empty) block diagram graphic will be displayed.

Virtual Instrument Panel Creates a new Virtual Instrument Page object. The (empty) Virtual
Instrument Page will be displayed.

Single Line Diagram Creates a Single Line Graphic in the target folder. Before the graphic is
inserted, the user is prompted to select the relevant grid.

The target folder will be set to the ∖User folder by default, but may be changed to any folder in the
database tree. The new grid, Block Diagram or Virtual Instruments folder will be created in the target
folder.

In all cases, a new graphics board object is also created, because graphic pages can only be shown
as a page in a graphics board. An exception is the creation of a new page, while in a graphics board.
This can be done by pressing the icon on the graphics board toolbar. This will add the new graphics
page to the existing graphics board.

Further information about how to draw network components is given in the following sections.

9.5.7 Basic Functionality

Each of the four graphic window types are edited and used in much the same way. This section gives
a description of what is common to all graphic windows. Specific behaviour and functionality of the
graphic windows themselves are described in other sections of the manual.

9.5.8 Page Tab

The page tab of the graphic window displays the name of the graphics in the graphics board. The
sequence of the graphics in the graphics board may be changed by the user. A page tab is clicked and
moved by dragging and dropping. An arrow marks the insert position during drag and drop. Another way
to change the order of the graphics is to select the option Move/Copy Page(s) of the context sensitive
menu. In addition virtual instrument panels can be copied very easily. To do so the Ctrl key is pressed
during drag and drop. The icon copies a virtual instrument panel and inserts the copy alongside the
original panel.

The page tab menu is accessed by a right-click on the page tab of the graphic windows. The following
commands are found:

• Insert Page → Create New Page creates a new page (the icon in the toolbar will do the same).
• Insert Page → Open Existing Page opens a page or graphic that has already been created but
which is not yet displayed.

• Rename Page presents a dialog to change the name of the graphic.

• Move/Copy Page(s) displays a dialog to move or copy the selected page. Copy is only available
for virtual instrument panels.

DIgSILENT PowerFactory 2016, User Manual 101

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.5.9 Drawing Toolboxes

Each graphics window has a specific Drawing Tool Box. This toolbox has buttons for new network
symbols and for non-network symbols. See Figure 9.5.5 for three examples.

(a) Single Line Diagrams (b) Block Diagrams (c) Geographic Diagrams

Figure 9.5.5: Drawing Toolbox examples

The toolboxes have:

• Network or block diagram symbols, which are linked to a database object: terminals, busbars,
lines, transformers, switches, adders, multipliers, etc.
• Graphical add-on symbols: text, polygons, rectangles, circles, etc.

The toolboxes are only visible when the graphics freeze mode is off. The graphics freeze mode is turned
on and off with the icon (found at the main icon bar of the graphical window).

9.5.10 Active Grid Folder (Target Folder)

On the status bar of PowerFactory (Figure 9.5.6), the active grid folder is displayed on the left-most field,
indicating the target folder (grid) that will be modified when you make changes in the network diagram.
To change the active target folder, double-click this field and then select the desired target folder. This
can be useful if the user intends to place new elements on a single line diagram, but have the element
stored in a different grid folder in the Data Manager.

Figure 9.5.6: The Status Bar

102 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

9.6 Graphic Commands, Options, and Settings

In this section the commands, options and settings that are available in PowerFactory to configure and
use the graphic windows are introduced. The sub-sections of this chapter are divided as illustrated in
Figure 9.6.1. These commands are also available from the main menu under View.

Figure 9.6.1: Categories of graphic commands, options, and settings

9.6.1 Freeze Mode

locks the diagram from graphical changes, no network elements can be added or deleted. Note that
the status of switches can still be modified when freeze mode is on.

9.6.2 Rebuild

The drawing may not be updated correctly under some circumstances. The rebuild function updates
the currently visible page by updating the drawing from the database. Also accessed through:

• Main Menu: Edit → Rebuild

• Right-Click: Drawing → Rebuild

9.6.3 View commands

9.6.3.1 Zoom In

Press the Zoom In to change the cursor to a magnifying glass. The mouse can then be clicked and
dragged to select a rectangular area to be zoomed. When the frame encompasses the area you wish
to zoom into release the mouse button.
Alternatively, by pressing Ctrl and using the mouse scroll wheel it can be zoomed in and out with the
mouse cursor as reference point. Using the Ctrl+- and Ctrl++ keys, zooming is also possible referenced
to the centre of the visible area. If in addition Shift is pressed, the reference changes to the mouse
cursor.

Note: The Acceleration Factor for zooming and panning can be changed on the Advanced tab of the
Graphic Window page in the User Settings dialog.

9.6.3.2 Zoom Back

To return to the previous zoom scale, press the Zoom Back button .

DIgSILENT PowerFactory 2016, User Manual 103

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.6.3.3 Zoom All

zooms to the page extends.

9.6.3.4 Zoom Level

Zooms to a custom or pre-defined level.

9.6.3.5 Hand Tool

Use the hand tool to pan the single line diagram (when not at the page extends). The hand tool is
activated with pressed middle mouse button, too. Alternatively, the mouse scroll wheel can be used to
scroll vertically, and Ctrl+→ / ↑ / ← / ↓ used to scroll vertically and horizontally.

9.6.3.6 View Bookmarks

The View Bookmarks allow to save the current view and restore that view at a later date. The
bookmarks may be used with different network diagrams (single line, geographic, detailed substation
graphic) of the same or different grids. In big networks this feature allows to switch very fast between
diagram details to check e.g. the impact of operational changes in loads/feed-in at different places in
the network.
By clicking View Bookmarks → Add Bookmark... the name will be asked, under which the current view
is stored and displayed in the list of the View Bookmarks. To edit, delete already existing or even create
manually new bookmarks, click on View Bookmarks → Manage Bookmarks.... An object browser with all
existing bookmarks appears. They can directly be changed using the object browser or by opening the
Edit-dialog for single bookmarks. The IntViewBookmark -objects contain the reference to the diagram,
the position and size of the View Area. To further accelerate the workflow Hotkeys are set automatically
for the bookmarks, which can be changed, too. If the current view should be assigned to the opened
bookmark, the button « From View may be pressed.

9.6.4 Select commands

9.6.4.1 Rectangular Selection

is used to select a rectangular section of the diagram. Note that this icon is generally depressed
when using the mouse pointer for other tasks, such as selecting Menu items, however the Hand Tool or
Free-form Selection may also be used.

9.6.4.2 Free-form Selection

is used to select a custom area of the diagram.

9.6.4.3 Mark All Elements

marks (selects) all objects in the current diagram. This is helpful for moving the whole drawing to
another place or copying the whole drawing into the clipboard. In block diagrams the surrounding block
will not be marked. The keyboard short cut Ctrl+A may also be used to perform this action.

104 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

Note: To select and/or move network and annotation elements at once, select first the network ele-
ments, unlock then the annotation layers with and with pressed Ctrl-key mark the annotation
objects. The whole selection can then be moved together.

9.6.5 Graphic Options

Each graphic window has its own settings, which may be changed using the Graphic Options . The
available settings of the dialog are described in the following sections.

9.6.5.1 Basic Attributes page

The General-tab offers the following settings:

Name: The name of the graphic

Target Folder for Network Elements: The reference to the database folder in which new power sys-
tem elements created in this graphic will be stored.
Write protected: if enabled, the single line graphic can not be modified. The drawing toolboxes are not
displayed and the freeze icon becomes inactive.
Drawing Tools :

• Snap: Snaps the mouse onto the drawing raster.

• Grid: Shows the drawing raster using small points.
• Ortho-Type: Defines if and how non-orthogonal lines are permitted:
– Ortho Off: Connections will be drawn exactly as their line points were set.
– Ortho: Allows only right-angle connections between objects.
– Semi Ortho: The first segment of a connection that leads away from a busbar or terminal
will always be drawn orthogonally.
Line Style for Cables: Is used to select a line style for all cables.
Line Style for Overhead Lines: Is used to select a line style for all overhead lines.

Offset Factor for Branch Symbols: Defines the length of a connection when a branch symbol is drawn
by clicking on the busbar/terminal. This is the default distance from the busbar/terminal in grid
points.
Offset Factor for semi-orthogonal Branch Symbols: Like previous, but for branches, which are drawn
with semi-orthogonal settings.
Node width factor: The width of points and lines for nodes and busbars.
Simplified view substations: scale factor of connection circles: In single line diagrams multiple bus-
bar substations are only represented by their main busbars. Connected elements may be con-
nected to each of the busbars by changing the state of the internal switches. The currently active
connection is shown in the diagram by a filled circle, the not connected ones by hollow circles.
The width of the circles is defined in this field.
Allow Individual Line Style: Permits the line style to be set for individual lines. The individual style
may be set for any line in the graphic by right-clicking the line → Set Individual Line Style. This
may also be performed for a group of selected lines/cables in one action, by first multi selecting
the elements.

DIgSILENT PowerFactory 2016, User Manual 105

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Allow Individual Line Width: As for the individual line style, but may be used in combination with the
“Line Style for Cables/Overhead Lines” option. The individual width is defined by selecting the
corresponding option in the right mouse menu (may also be performed for a group of selected
lines/cables in one action).
Diagram Colouring: By default, changes of the active Colouring Scheme take effect on every diagram
(Default). By setting the option to Colouring Scheme, the scheme of the current diagram can
be configured separately. Press Manage... to open an object browser with a list of the available
Colouring Scheme settings. Copy the existing or create a new one and alter it to the wished
Scheme. Close the object browser and choose the new Colouring Scheme out of the drop down
list.

The Advanced-tab offers the following settings:

Allow Navigation Pane: If checked, the Navigation Pane can be activated by Window → Navigation
Pane or the context sensitive menu in the diagram Navigation Pane.
Animated Load Flow: If the graphic layer ’Direction Arrows’ is set to visible, the power flows after a
Load Flow Calculation may be animated using the context sensitive menu item Show Animation
in the network diagram.

9.6.5.2 Text Boxes page

Boxes of Object Names :

• Show frame for nodes/branches: The text boxes of the according elements will show a
frame.
• Background: specifies the transparency of object names boxes:
– Opaque: means that objects behind the results box cannot be seen through the results
box.
– Transparent: means that objects behind the results box can be seen through the results
box.
Result Boxes :

• Show frame for nodes/branches: The result boxes of the according elements will show a
frame.
• Background: Specifies the transparency of result boxes (as boxes of object names)
• Always show result boxes of detailed couplers: Self-explanatory.
• Space saving representation of result boxes on connection lines: Self-explanatory.
Show line from General Textboxes to referenced objects: May be disabled to unclutter the graphic.
Reset textboxes completely: Textboxes and result boxes have reference points (the point on the box
at which the box will ’attach’ to its element) that may be changed by the user. If this option is:

• Enabled: The default reference will be used.

• Disabled: The user defined reference will be used.
Show Tooltip on Network Elements: enables or disables the balloon help dialogs.

106 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

9.6.5.3 Switches page

Switch state symbol at connection end: selects the switch representation (see Figure 9.6.2):

• Permanent Box: shows a solid black square for a closed and an frame line for an open
switch (left picture).
• Old Style Switch: shows the switches as the more conventional switch symbol (right picture).

Figure 9.6.2: Cubicle representations

Display Frame around Switches: Draws a frame around the switch itself (Breakers, Disconnectors,
etc.). This only applies to user-drawn breakers and disconnectors.
Create switches when connecting to terminal: Self-explanatory.

Show connected busbars as small dots in simplified substation representation: Defines how the
connection points on busbars are represented in busbar systems.

9.6.5.4 Substation Types

The settings in this page are related to the graphical representation of substations in geographic
diagrams. The dialog offers the possibility to distinguish graphically different types of substations and
improve the clearness of the diagram by adding additional data through the substation symbol. A
possible use of this feature can be seen in the geographic diagram ’Overview Diagram’ of the Application
Example ’MV Distribution Network’ (File → Examples...).
The column ’Substation Type’ of the Assignment Table is the list, of which one element may be chosen
in the drop down list Type in the Description-page of the Substation-dialog, opened by right-clicking on
a graphical substation element and choosing Edit Substation. The list contains the Substation Types
defined in the according page of the Project Settings dialog.
The column ’Symbol’ is storing the name of the symbol, which is searched by default in the subfolder
Database/System/Library/Graphic/Symbols/SGL/Composites. As additional source, the project’s sub-
folder Settings/Additional Symbols is taken into account.

9.6.5.5 Geographic Diagram

The settings of this page define the appearance of the graphical representation of network elements in
the geographic diagrams.

Size Factors for: Defines the size of the symbols in the diagram for Substations, Terminals, Text, Line
Loads and Section Transitions, Line End Symbols and the Line Width.

DIgSILENT PowerFactory 2016, User Manual 107

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Scale level when: In extent networks with a high scale level, switch state boxes at line ends, text
labels and annotation objects are hidden at a specified scale level to improve the clearness of the
diagram.

Margin at full zoom: Since in geographic diagrams, there is no border, this value defines the margin
shown in the case Zoom All is pressed.
Show Coordinates in Latitude/Longitude: Shows the coordinates of the current cursor position in
latitude and longitude in the Status Bar. Else the position is displayed as X/Y values representing
UTM-coordinates. The border values of the area represented by the diagram are listed in the page
’Coordinates’ of the Graphic Options dialog.
Prefer Branch Coordinates: This option affects elements, which are grouped to branches (ElmBranch).
If the branch itself has geographic coordinates, they will be used in the geographic diagram, else
the coordinates of the elements contained in the branch are taken into account.
Show Scale: Shows or hides the scale in the diagram.
GPS projection: Defines the projection used in the geographic diagram.

9.6.5.6 Other pages

Additional Attributes and Coordinates pages should generally only be configured with the assistance
of DIgSILENT support staff. Note that if Use Scaling Factor for Computation of Distances is selected
on the Coordinates page, it is possible to calculate the length of lines on the Single Line Graphic by
right-clicking and selecting Measure Length of Lines. In geographic diagrams, this option is activated
by default.

Also accessed through:

Right-click: Graphic Options

Note: The settings for the cursor type for the graphic windows (arrow or tracking cross) may be set in
the User Settings dialog, see section 7.2 (Graphic Windows Settings). This is because the cursor
shape is a global setting, valid for all graphic windows, while all graphic settings described above
are specific for each graphic window.

9.6.6 Layers

The single line, geographic and block diagrams use transparent layers of drawing sheets on which the
graphical symbols are placed. Each of these layers may be set to be visible or not. The names of
objects that have been drawn, for example, are on a layer called ’Object Names’ and may be made
visible or invisible to the user.

Which layers are visible and exactly what is shown on a layer is defined in the Graphical Layers dialog,
accessed through the graphic toolbar ( ), by right-clicking on an empty spot of the graphic area →
Show Layer, or selecting View → Layers from the main menu. The layers dialog has a ’Visibility’ page
to determine which layers will be visible, and a ’Configuration’ page to define various attributes for the
layers. See Figure 9.6.3.

In the Visibility page, the layers are divided into two tabs, one for the Network Element and one for
the Annotation Layers. In Figure 9.6.3, the layers in the left pane (Base Level, Object Names, Results,
etc.) are visible in the graphical window. The layers in the right pane are invisible. Layers can be
made visible by multi selecting them (hold the Ctrl key down whilst selecting) and pressing the
button (alternatively, double-click a layer name and it will jump to the other pane). A layer can be made
invisible again by selecting it in the left pane and pressing the button or by double-clicking it. It is
also possible to define user-specific layers, by pressing the New button. The selection of visible layers

108 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

is saved individually for every diagram. Pressing the button Apply to all graphics overwrites the layer
selection of all diagrams with the one of the open dialog.

Figure 9.6.3: Graphical layers dialog (SetLevelvis)

Each graphic symbol in a single line, geographic or block diagram is assigned by default to the corre-
sponding layer at first. All busbar symbols, for example, are drawn on the ’Base Level’ layer by default,
their name boxes on the layer ’Object Names’. Graphic symbols may be shifted onto other layers by
right-clicking them in the single line graphic and selecting the option Shift to Layer from the context
sensitive menu. This option will show a second menu with all layers. Selecting a layer will move all
selected symbols to that layer. Moving symbols from one layer to another is normally needed when
only a few symbols from a certain group should be made visible (for instance the result boxes of one or
two specific junction nodes), or when user defined layers are used. This allows to hide some elements
or text boxes to improve the clarity of the diagram, or to show additional information for e.g. printing
purposes.

Note: Certain names and result boxes are, by default, assigned to the ’Invisible Objects’ layer. An
example are the names and result boxes for point terminals. This is done to unclutter the graphic.
Should the user wish to display names and/or result boxes for certain Junction / Internal nodes
simply make the ’Invisible Objects’ layer visible and re-assign the names and result boxes required
to another layer, such as the ’Object Names’ or ’Results’ layers - then make the ’Invisible Objects’
layer invisible once more.

The list of the Annotation Layers is empty until the first Annotation object is inserted. It will be assigned to
the automatically created and visible ’Default Layer’. Clicking on Edit Layers... opens a object browser
to manage the Annotation Layers. New ones can be created or existing ones may be changed or
deleted. The Edit-dialog shows in addition to the Visible-flag also the option Zoom invariant. If the box
is checked, the annotation objects assigned to the layer won’t change size or position in the diagram
regardless of any zoom or move operation. This zoom invariant layers are useful, when e.g. additional
information or customised legends were created and which should always appear in the current view
of the diagram at the same position to achieve a unified appearance of diagram exports or prints for

DIgSILENT PowerFactory 2016, User Manual 109

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

documentation purposes. Best practise is to select all annotation objects, which form a unity (like a
legend) and group them using right-click → Group to one Object.
If multiple annotation layers exist, the annotation objects can easily be shifted from one to another by
right clicking on them and select the destination layer from the list of Move to Annotation Layer.

The ’Configuration’ page has a drop down list showing all layers that may be configured by the user.
Considering the ’Object Names’ layer as shown in Figure 9.6.4, it may be seen that a target (or focus)
may be set. The selected target will be the focus of the performed configuration command. Various
actions or settings may be performed, such as e.g. changing the font using the Change Font button.
The configuration page may also be used to mark (select/ highlight) the target objects in the graphic
using the Mark button.

The options available to configure a layer depend on the type of Layer. Table 9.6.1 shows for each layer
in which way its content can be changed in format.

Figure 9.6.4: Graphical layers configuration page

As an example, suppose that a part of the single line graphics is to be changed, for instance, to allow
longer busbar names. To change the settings, the correct graphical layer is first selected. In this
example, it will be the ’Object Names’ layer. In this layer, only the busbar names are to be changed,
and the target must therefore be set to ’All Nodes’. When the layer and the target has been selected,
the width for object names may be set in the Settings area. The number of columns may be set using
the Visibility/Frame/Width button. Alternatively, the Adapt Width will adapt all of the object name
placeholders to the length of the name for each object.

Changing a setting for all nodes or all branches at once will overwrite the present settings. The
predefined layers existing in PowerFactory are described in Table 9.6.1.

Note: Should an object disappear when it has been re-assigned to a layer, that layer may be invisible.
Layer visibility should be inspected and changed if required.

110 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

Diagram Type:
SL Single
Configuration
Layer Content Line, GEO
Options
Geographic, B
Block
Symbols for the elements Text/Box For-
Base Level SL/GEO/B
of the grid mat
Boxes with names and
Object Text/Box For-
additional data descrip- SL/GEO/B
Names mat
tion, if configured
Boxes with calculation re- Text/Box For-
Results SL/GEO/B
sults mat
Additional Text explana-
Text/Box For-
Device Data tion given in the device SL/GEO/B
mat
symbol
Dots at the connections
Connection between edges and bus- Text/Box For-
SL/GEO/B
Points es/terminals and signal mat
connections to blocks
Layer containing the sym-
Invisible Text/Box For-
bols of elements hidden SL/GEO/B
Objects mat
by default
Graphic used as the back- Name of file
ground (“wallpaper”) to al- with graphics
low easier drawing of the (WMF, DXF,
Background SL/B
diagram or to show ad- BMP, JPEG,
ditional information (map PNG, GIF,
information) TIF)
Map Provider
Geographical map used (see section
as the background to al- 9.13), map
Background GEO
low easier drawing of the type and
diagram graphic
settings
Numbers of
Number of lines for each Text/Box For-
Connection SL/GEO
connection mat
Lines
Symbols at lines consist-
Sections
ing of sections and/or Text/Box For-
and Line SL/GEO
where line loads are con- mat
Loads
nected
Double-Arrow at connec-
Connection tions where the end point Text/Box For-
SL/GEO
Arrows is not represented in the mat
current diagram.
Tap Positions of taps for Text/Box For-
SL/GEO
Positions shunts and transformers mat
Vector group for rotating
Vector Text/Box For-
machines and transform- SL/GEO
Groups mat
ers

DIgSILENT PowerFactory 2016, User Manual 111

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Diagram Type:
SL Single
Configuration
Layer Content Line, GEO
Options
Geographic, B
Block
Active/Reactive
Arrows that can be config- Power
Direction ured for active and reac- for direct/
SL/GEO
Arrows tive power flow represen- inverse/
tation homopolar
system
Number of phases of a
Text/Box For-
Phases line/cable, shown as par- SL/GEO
mat
allel lines
Connection Index of each possible Text/Box For-
B
Numbers block connection point mat
Connection Name of each unused Text/Box For-
B
Names connection of a block mat
Name of the signal trans- Text/Box For-
Signals B
mitted mat
Block Defi- Definition each block is Text/Box For-
B
nition based on mat
Remote
Controlled Remote Controlled Sub-
Colour SL/GEO
Substa- stations
tions
Additional text labels for Text/Box For-
Text Labels SL/GEO
elements mat
Graphically represented Text/Box For-
Relays SL/GEO
relays mat
Contains the drawn cur-
CTs and Text/Box For-
rent and voltage trans- SL/GEO
VTs mat
formers
Virtual In- Virtual instruments Text/Box For-
SL/GEO/B
struments placed in the diagrams mat
Selection
Load/ Gen- Shows circles for load and
of S, P or
eration Dis- generation around sub- GEO
Q, colour-
tribution stations
settings
Table 9.6.1: Predefined Diagram Layers of PowerFactory

9.6.7 Colouring Options

9.6.7.1 Diagram Colouring

The single line and geographic diagrams have an automatic colour representation mode. The Diagram
Colouring icon on the local toolbar will open the diagram colouring representation dialog (alterna-
tively, select View → Diagram Colouring on the main menu). This dialog is used to select different
colouring modes and is dependent if a calculation has been performed or not. If a specific calculation
is valid, then the selected colouring for that calculation is displayed.

112 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

The Diagram Colouring has a 3-priority level colouring scheme implemented, allowing colouring ele-
ments according to the following criteria: 1𝑠𝑡 Energising status, 2𝑛𝑑 Alarm and 3𝑟𝑑 “Normal” (Other)
colouring.

Energising Status: If this check box is enabled “De-energised” or “Out of Calculation” elements
are coloured according to the settings in the “Project Colour Settings”. The settings of the “De-
energised” or “Out of Calculation” mode can be edited by clicking on the Colour Settings button.

Alarm: If this check box is enabled a drop down list containing alarm modes will be available. It
is important to note here that only alarm modes available for the current calculation page will be
listed. If an alarm mode is selected, elements “exceeding” the corresponding limit are coloured.
Limits and colours can be defined by clicking on the Colour Settings button.

“Normal” (Other) Colouring: Here, two lists are displayed. The first list contains all available
colouring modes. The second list contains all sub modes of the selected colouring mode. The
settings of the different colouring modes can be edited by clicking on the Colour Settings button.

Every element can be coloured by one of the three previous criteria. Also, every criterion is optional
and will be skipped if disabled. Regarding the priority, if the user enables all three criteria, the hierarchy
taken into account will be the following:

• “Energising Status” overrules the “Alarm” and “Normal Colouring” mode. The “Alarm” mode
overrules the “Normal Colouring” mode.

The graphic can be coloured according to the following list. Availability of some options will depend on
the function that is selected (e.g. ’Voltage Violations’ does not appear when the ’Basic Data’ page is
selected, but does when the ’Load Flow’ page is selected) and on the licence (e.g. Connection Request
is only available if the advanced function Connection Request Assessment is part of the licence).

Energising Status:

• De-energised
• Out of Calculation

Alarm:

• Feeder Radiality Check (Only if “Feeder is supposed to be operated radially” is selected).

• Outages
• Overloading of Thermal/Peak Short Circuit Current
• Voltage Violations/Overloadings

“Normal” (Other) Colouring:

• Results
– Connection Request: Approval Status
– Contribution to EIC
– Contribution to ENS
– Contribution to SAIDI
– Contribution to SAIFI
– Fault Clearing Times
– Incident Energy

DIgSILENT PowerFactory 2016, User Manual 113

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

– Loading of Thermal / Peak Short-Circuit Current

– Loads: Average Interruption Duration
– Loads: Load Point Energy Not Supplied
– Loads: Yearly interruption frequency
– Loads: Yearly interruption time
– Optimal Manual Restoration
– PPE-Category
– State Estimation
– Voltage Angle (colouring according to absolute or relative voltage angles and angle dif-
ferences along branch elements; relative voltage angles do not reflect transformer vector
groups, while absolute voltage angles include the angle shift caused by transformer vector
groups)
– Voltages / Loading
• Topology
– Boundaries (Definition)
– Boundaries (Interior Region)
– Connected Components
– Connected Components, Voltage Level
– Connected Grid Components
– Energising Status
– Feeders
– Missing graphical connections
– Outage Check
– Station Connectivity
– Station Connectivity (Beach Balls only)
– Supplied by Secondary Substation
– Supplied by Substation
– System Type AC/DC and Phases
– Voltage Levels
• Primary Equipment

– Cross Section
– Forced Outage Duration
– Forced Outage Rate
– Year of Construction

• Secondary Equipment
– Measurement Locations
– Power Restoration
– Relays, Fuses, Current and Voltage Transformers
– Switches, Type of Usage
• Groupings (Grids, Zones, Areas...)
– Areas
– Grids
– Meteo Stations

114 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

– Operators
– Owners
– Paths
– Routes
– Zones
• Variations / System Stages
– Modifications in Recording Expansion Stage
– Modifications in Variations / System Stages
– Original Locations
• User-defined
– Individual

The list ’User-defined’ may be used to define own colouring schemes. Pressing Manage Filters...
opens an object browser with the list of all available user-defined filters, found in the subfolder Settings/-
Colouring/Colouring Scheme. New filter sets (IntFiltset) can be created, containing several General
Filter objects (SetFilt) with an assigned colour and the conditions, under which an element is coloured.
This allows to implement very specific filters to identify graphically elements in the diagram with certain
properties or results.

An illustration of diagram colouring options is shown in Figure 9.6.5. In this case, the Voltage Colouring
Mode is set to ’Voltage Drop and Rise’, under ’Colour Settings’. Also, the ’Colouring scheme for voltages
and loading’ is set to ’Continuous’ on the Advanced tab.

Figure 9.6.5: Illustration of diagram colouring

DIgSILENT PowerFactory 2016, User Manual 115

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.6.7.2 Heatmaps

In PowerFactory , Heatmaps can be used to illustrate the state of a grid by colouring the area around
network elements. The colour definition is carried out as described in section 9.6.7.1.

To use the colour definition for Heatmaps, click on the Heatmap button . On the General page of the
dialog, the basic settings for the creation of the heatmap can be selected. The colour settings dialog
(explained in section 9.6.7.1) is accessible from this page. The Mode shows which type of colouring is
used.

The resolution of the Heatmap can be:

• Low
• Medium
• High

• User-defined (in pixels)

Note: The amount of time required to generate each Heatmap increases with the specified resolution.
Since the optimal settings for Heatmaps vary for each grid, the process of finding this optimum
might take a few iterations. Therefore it is advised to start with a small or medium resolution.

A background colour for the Heatmap may additionally be set.

The General page defines the general settings for the Heatmap and the Advanced page defines
specifics regarding the colouring. Five different parameters can be set; the first two being:

• Number of closest influence points: defines the number of reference points taken into account
when colouring a certain point of the Heatmap.
• Contour sharpness: defines the smoothness of the transition between differently coloured areas.

The other three parameters define the Fading Area, i.e. the orthogonal transition from the element
colouring to the background colour:

Begin: defines how far away from the centre of the element on the lateral axis the colouring begins to
fade to the background colour.
Extent: defines how far away from the centre of the element on the lateral axis the colouring ends to
fade to the background colour.
Fading exponent: defines how fast the colour between Begin and Extent will fade to the background
colour.

Figure 9.6.6 shows an example of a Heatmap, which is coloured according to loading, over- and under-
voltage.

116 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

Figure 9.6.6: Example of a Heatmap coloured according to loading, over- and under-voltage

9.6.8 Graphic Legends

9.6.8.1 Show Title Block

The title block can be turned on and off from the single line diagram toolbar ( ) or the View menu. The
title block is placed in the lower right corner of the drawing area by default.

The contents and size of the title mask can be changed by right-clicking the title block and selecting the
Edit Data option from the context sensitive menu. The Select Title dialog that pops up is used to scale
the size of the title block by setting the size of the block in percent of the default size. The font used will
be scaled accordingly. To edit the text in the title block press the edit button ( ) for the ’Title Text’ field.

All text fields have a fixed format in the title block. The data and time fields may be chosen as automatic
or user defined. Most text fields are limited to a certain number of characters. When opening a new
graphic the title will appear by default.

9.6.8.2 Show Legend Block

The legend block can be turned on and off from the single line diagram toolbar ( ), or from the ’View’
menu. The legend block describes the contents of result boxes (for information about result boxes
see 9.9).

Because more than one type of result box is normally used in the Single line graphic, for instance, one
for node results and another one for branch results, the legend box normally shows more than one

DIgSILENT PowerFactory 2016, User Manual 117

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

column of legends. After changing the result box definitions, it may be required to manually resize the
legend box in order to show all result box legends.

The Legend Box definition dialog is opened by right-clicking the legend block and selecting Edit Data
from the context sensitive menu. The font and format shown may be configured. When opening a new
graphic the legend will appear by default.

9.6.8.3 Colour Legend Block

The colour legend block can be turned on and off from the single line diagram toolbar ( ), or from the
’View’ menu. The legend updates automatically based on the colouring options selected.

9.6.9 Element Options

9.6.9.1 Edit and Browse Data

This option lets the user edit the device data of all marked objects in the drawing. If only one object is
marked, then this object will be selected in its project folder within the list of the other objects. When
more than one object is marked, the Data Manager window will show only the list of marked objects.
As with a normal Data Manager, these objects can be double-clicked to open their edit dialogs. See
chapter 10 (Data Manager) for more information.

Note: Changes made in the device data of objects are not registered by the graphical Undo Function.
Undoing these changes is therefore not possible.

Also accessed through:

Right-click: Edit and Browse Data

Note: To edit data for a single element, double-click the element, or select the element and press
Alt+Return.

9.6.9.2 Delete Element

This function deletes all marked objects in the diagram. The database objects for the graphical object
will also be deleted (a warning message will pop up first - this may be switched off in the “User Settings”
dialog; see section 7.2 (Graphic Windows Settings)).

Also accessed through:

Right-click: Delete
Keyboard: Del

Note: To delete graphical objects only, right click the selected element/s and select Delete Graphical
Object only.

9.6.9.3 Cut

This function cuts the marked objects in the diagram. Objects can then later be pasted as discussed
below.

118 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

Also accessed through:

Right-click: Cut
Keyboard: Ctrl+X

9.6.9.4 Copy

Copies all marked objects from the current drawing and puts them into the clipboard.

Also accessed through:

Right-click: Copy
Keyboard: Crtl+C

9.6.9.5 Paste

Copies all objects from the clipboard and pastes them into the current drawing. The objects are pasted
at the current graphical mouse position. Objects that are copied and pasted create completely new
graphic and data objects in the graphic that they are pasted into.

Also accessed through:

Right-click: Paste
Keyboard: Crtl+V

Note: If you wish to copy and paste just the graphic, then choose Paste Graphic Only from the right-
click menu. Similar results are obtained when using the “Draw Existing Net Elements” tool (see
Section 9.7: Drawing Diagrams with Existing Network Elements).

Note: The undo command undoes the last graphic action and restores deleted elements, or deletes
created elements. The undo command is accessed through the undo icon ( ), by right-clicking
and selecting ’Undo’, or by pressing Ctrl+Z.

9.6.9.6 Other Commands

The following commands are accessed via the context sensitive menu of the elements pressing the right
mouse button.

Rotate:
Right-click selection and Rotate to rotate symbols clockwise, counter-clockwise, or 180 degrees. It is
generally preferable to disconnect an element before rotating it.

Disconnect:
Right-click and select Disconnect Element to disconnect the selected element/s. When right-clicking at
the end of a connection element a different/reduced menu is shown which allows disconnecting just the
selected side (Disconnect Side)

Connect:
Right-click and select Connect Element to connect an element.

Reconnect:
Right-click and select Reconnect Element to disconnect the selected elements and then re-connect
them. The branch to be connected will be ’glued’ to the cursor. Left clicking a bar or terminal will

DIgSILENT PowerFactory 2016, User Manual 119

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

connect the element. When right-clicking at the end of a connection element a different/reduced menu
is shown which allows reconnecting just the selected side (Reconnect Side)

Redraw:
Right-click and select Redraw Element to redraw a selected element.

Move:
Marked objects can be moved by left clicking them and holding down the mouse button. The objects
can be moved when the cursor changes to an arrowed cross ( ). Hold down the mouse button and
drag the marked objects to their new position. Connections from the moved part of the drawing to other
objects will be adjusted.

Edit Line Points:

Right-click and select Edit Line Points will show the black squares (’line points’) that define the shape
of the connection. Each of these squares can be moved by left clicking and dragging them to a new
position (see Figure 9.6.7). New squares can be inserted by left clicking the connection in between
squares. Line points are deleted by right-clicking them and selecting the Delete Vertex option from the
case sensitive menu. This menu also presents the option to stop (end) the line point editing, which can
also be done by left clicking somewhere outside the selected lines.

Figure 9.6.7: Editing line points

9.6.10 Node Default Options

Figure 9.6.8 shows the commands available for setting node default options. These are discussed in
further detail in this section.

120 DIgSILENT PowerFactory 2016, User Manual

 9.6. GRAPHIC COMMANDS, OPTIONS, AND SETTINGS

Figure 9.6.8: Node default options

Default Voltage Levels for Terminals and Busbars:

The default voltage level for terminals can be set in this field. New terminals placed on the single line
diagram will have this voltage (e.g. 110 kV, 0.4 kV).

Default Phase Technologies for Terminals:

The default phase technology for terminals can be set in this field. New terminals placed on the single
line diagram will be of this type (e.g. three-phase ABC, single-phase, DC, etc.).

9.6.11 Page and Print Options

9.6.11.1 Print

This function is accessed via the button, the menu File → Print or via the hotkey Ctrl+P. It opens
the Print Preview, showing the first page of the diagram, which will be printed after pressing the Print
button. If the drawing size of the diagram doesn’t fit the printers paper size, the diagram is split up into
more pages, its previews can be browsed using the buttons , , and . To edit the Print Setup,
press the button . By default, the whole active diagram will be selected. If only the current view
should be printed, the option Selection in the Print range of the Print Setup has to be selected. The
button in the Print Preview opens the Page Setup dialog, where the margins can be customised.

9.6.11.2 Define Print Area

The Print Area enhances the print functionality by predefining a selected area of the diagram to print.
By pressing the Define Print Area button , a red bounded rectangle, the Print Area, will be shown,
which covers by default the whole active view. Its proportion fits the one of the printer settings. The size
and position of the Print Area can be scaled and moved to cover only the desired part of the diagram.
With the Print Area still active, the Print command opens the Print Preview with exactly the area of the
network covered by the Print Area.
Once defined, the Print Area can be shown and hidden using the -button. For every network diagram
a separate Print Area can be defined, which is saved over the whole session (no more available after
de- and reactivating the project or using the rebuild command for the according diagram).

9.6.11.3 Drawing Format

The drawing area for single line diagrams, block diagrams and virtual instruments is modified in the
Drawing Format dialog, accessed using the button. A predefined paper format can be selected
as-is, edited, or a new format can be defined. The selected paper format has ’Landscape’ orientation
by default and can be rotated by 90 degrees by selecting ’Portrait’. The format definitions, which are
shown when an existing format is edited or when a new format is defined, also show the landscape
dimensions for the paper format.

It is not possible to draw outside the selected drawing area. If a drawing no longer fits to the selected

DIgSILENT PowerFactory 2016, User Manual 121

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

drawing size, then a larger format should be selected. The existing graphs or diagrams are repositioned
on the new format (use Ctrl+A to mark all objects and then grab and move the entire graphic by left
clicking and holding the mouse key down on one of the marked objects; drag the graphic to a new
position if desired).

If no ’Subsize for Printing’ format has been selected, then, at printing time, the drawing area will be
scaled to fit the paper size of the printer. If, for instance, the drawing area is A3 and the selected paper
in the printer is A4, then the graphs/diagrams will be printed at 70% of their original size.

By selecting a subsize for printing, the scaling of the drawing at printing time can be controlled. The
dimensions of the sub-sized printing pages are shown in the graphic page. If, for instance, the drawing
size has been selected as A3 landscape, and the printing size as A4 portrait, then a vertical grey line
will divide the drawing area in two halves. The drawing area will be accordingly partitioned at printing
time and will be printed across two A4 pages.

Make sure that the selected subsize used for printing is available at the printer. The printed pages are
scaled to the available physical paper if this is not the case.

For instance:

• The drawing area has been selected as A2 landscape.

• The subsize for printing has been selected as A3 portrait. The A2 drawing is thus to be printed
across two pages.
• Suppose that the selected printer only has A4 paper. The original A2 drawing is then scaled down
to 70% and printed on two A4 sheets of paper.

Also accessed through:

Main Menu: File → Page Setup

9.6.12 Diagram Layout Tool

The Diagram Layout Tool is a powerful feature to create graphical representations of network
topologies. The tool offers a manual, semi- and fully automatic creation of nodes and branch elements,
which are not yet graphically represented in the current Network Diagram. The options and the dialog
are described in detail in section 9.7.

9.6.13 Insert New Graphic

Pressing the button inserts a new graphic object into the Graphic Board folder of the active study
case and presents a blank graphics page to the user. A dialog to configure the new graphics object will
appear first.

Also accessed through:

Page Tab Menu: Insert Page → Create New Page

Note: The Page Tab menu is opened by right-clicking a page tab, shown just below the single line
diagram.

Note: Existing graphics can be opened by selecting Show Graphic of the context sensitive menu of
the graphic object in the subfolder Network Model/Diagrams or by choosing it from the list, which
opens after selecting Insert Page → Open Existing Page from the context sensitive menu of the
page tab.

122 DIgSILENT PowerFactory 2016, User Manual

 9.7. DRAWING DIAGRAMS WITH EXISTING NETWORK ELEMENTS

9.6.13.1 Other Page Commands

Other page commands accessed through the page tab are as follows:

Remove Page:

This function will remove the selected graphic from the Graphics Board. The graphic itself will not be
deleted and can be re-inserted to the current or any other Graphics Board at any time.

Rename Page:

This function can be used to change the name of the selected graphic.

Move/Copy Page(s):

This function can be used to move a page/s to modify the order of graphics. Also accessed through:

• Mouse Click: Left-click and select a single page (optionally press control and select multiple
pages) and drag the page/s to change the order graphics are displayed.
• Data Manager: (Advanced) Modify the order field of Graphics Pages listed within the Study
Case Graphics Board. To reflect the changes, the study case should be deactivated and then
re-activated.

9.7 Drawing Diagrams with Existing Network Elements

This section provides information about how to draw network components from existing objects. Power-
Factory separates strictly the electrical (and therefore for calculations relevant) data of network elements
from their graphical representation in the diagrams. Calculations of networks without any graphical
representation is possible.

Designing new (extensions to) power system grids, is preferably done graphically. This means that the
new power system objects may be created in a graphical environment. After the new components are
added to the design, they can be edited, either from the graphical environment itself (by double-clicking
the objects), or by opening a Data Manager and using its editing facilities.

It is however possible, to first create objects in the Data Manager (either manually, or via data import
using e.g. the DGS format), and subsequently draw these objects in one or more single line diagrams.
If the imported data contains geographical coordinates, a geographical diagram can be created auto-
matically by right clicking on the Grid in the Project Overview window and choosing Show Graphic →
Geographic Diagram.

If no geographic coordinates are given or if a single line diagram should be created, PowerFactory
provides the Diagram Layout Tool to do that. In a first step, a new single line diagram has to be
created. This can be done out of the main menu using Insert → Single Line Diagram... or by right
clicking on the tab of the currently active diagram and choosing Insert Page → Create New Page. In
both cases a grid has to be chosen from the network data folder, which should be represented by the
new diagram.

The following sections describe the options and possibilities of the Diagram Layout Tool , located in
the graphic icon bar. It replaces the Draw Existing Net Elements tool of previous versions and enhances
its functionality by a semi- and fully automated creation of network diagrams.

DIgSILENT PowerFactory 2016, User Manual 123

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.7.1 Generate complete diagram

This action is only available in new network diagrams, where no element is graphically represented
yet. The tool creates for every element a graphical representation considering the Automatic Layout
settings. It’s a fast possibility to get a graphical overview of a network, which offers all the advantages
of visualisation for e.g. results or the topology (colouring schemes for feeders, zones, etc.).

9.7.2 Expand k-neighbourhood

This action creates graphical elements starting from a selection of already in the diagram graphically
represented elements. A selection of elements is therefore necessary. If some or all graphic elements
are selected before opening the Diagram Layout Tool, these elements are automatically inserted into
the Start elements selection. Alternatively the Start elements can be selected directly from the dialog
using Select... or Add Element... in the Neighbourhood Expansion settings.
Starting from every selected element, the connected and not yet graphically represented neighbours
are created and subsequently also their neighbours. The depth of this recursive algorithm is defined by
the K-factor, which can be configured in the Neighbourhood Expansion settings.
This approach offers a step-by-step creation of a diagram, where an intervention after each step is
possible to adapt the final appearance of the network diagram. Alternatively this action may be used in
combination with the following actions.

9.7.3 Insert Missing graphical branches

This action completes automatically the current diagram with the branch elements, which are not yet
graphically represented. It is only available for diagrams with already some existing graphical node
elements in it.

9.7.4 Draw manually

This action replaces the formerly known Drawing existing Net Elements tool. By its execution, a window
will appear, listing all the elements, which are not yet graphically represented in the diagram.

9.7.4.1 Drawing Existing Busbars

Click on the symbol for busbars ( ) in the drawing toolbox. The symbol of the busbar (terminal) is now
attached to the cursor.

If the list is very large, press the button Adjacent Element Mode ( ). This activates the selecting of
distance (number of elements) from elements in the selection of the ’Neighbourhood Expansion’. Select
the Distance of 1 in order to reduce the number of busbars (terminals) shown.

If the button Use drawn nodes as starting objects ( ) is also selected, the list will be filtered based on
all drawn nodes (not just a single starting node).

If Show elements part of drawn composite nodes ( ) is selected, elements internal to already drawn
composite nodes will be shown in the list. However, since they are already drawn as part of the
composite node, they should not be re-drawn.

The marked or selected element can now be visualised or drawn by clicking somewhere in the active
diagram. This element is drawn and disappears from the list.

Note that the number of elements in the list can increase or decreases depending on how many

124 DIgSILENT PowerFactory 2016, User Manual

 9.7. DRAWING DIAGRAMS WITH EXISTING NETWORK ELEMENTS

elements are a distance away from the element lastly drawn. Scroll down the list, in case only certain
elements have to be visualised.

Close the window and press Esc to return the Cursor to normal. The drawn terminals (busbars) can be
moved, rotated or manipulated in various ways.

9.7.4.2 Drawing Existing Lines, Switches, and Transformers

Similar to the busbars, elements like lines and transformers connecting the terminals in the substation
can be drawn.

Execute the Draw manually action of the Diagram Layout Tool. For lines select the line symbol ( )
from the drawing toolbox, for transformers select the transformer symbol ( ), and so on.

Similar to terminals, a list of all the lines (or transformers, or elements which have been chosen) in the
network, that are not in the active diagram, is shown.

For each selected line (or transformers...) a pair of terminals, to which the line is connected, are marked
in the diagram. Click on the first terminal and then on the second. The selected line is drawn and
removed from the list of lines.

Continue drawing all lines (or transformers...), until the list of lines is empty or all the lines to be drawn
have been drawn. If a branch cannot be completely drawn (for example, when the terminal at only one
end of a line is shown on the diagram), it is possible to draw a first line section, then press Tab or double
click on the diagram and arrows will appear to indicate that the line connects to a terminal that is not
shown. Figure 9.7.1 provides an illustration.

Figure 9.7.1: Illustration of single line diagram connectivity

Note: Another useful approach to developing single line diagrams is to first define a feeder (say, at
the cubicle closest to the source node), then run a load-flow, navigate to the feeder in the Data
Manager, right-click and select Show → Schematic visualisation by Distance or Bus Index. See
Section 14.5 (Feeders) for further information on how to define feeders.

Note: Before placing elements onto the graphic users may find it useful to configure and display a
background layer. This will be an image of an existing single line diagram of the system. It may be
used to ’trace’ over so that the PowerFactory network looks the same as current paper depictions;
see Section 9.6.6 for more information on layers.

9.7.5 Automatic Layout

The settings regarding the Automatic Layout take effect on the actions Generate complete diagram and
Expand k-neighbourhood.

• Node Dispersion: This option defines the distance between the newly created nodes in the
diagram and can be chosen between low, medium or high.

DIgSILENT PowerFactory 2016, User Manual 125

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

• Consider composite elements: This check box shows only an impact, if the corresponding grid
contains composite elements (e.g. ElmSubstat, ElmTrfstat), which graphically combine substa-
tions with a lot of internal nodes, switches, transformers, etc. If checked, the graphical represen-
tation of the composite elements are created, else all of the internal elements of the composite
elements are created separately in the diagram.
• Consider physical line length: With this option checked, the length of the graphical representa-
tion is based on the corresponding line length. The graphic object length doesn’t follow a linear
dependence from the electrical line length, but gives a good overview about long or short lines in
the network diagram.
• Adjust diagram size: The size of the diagram, defined in the Drawing Format is ignored and
overwritten by the algorithm, which uses so much space as needed. To get clearer outputs, this
option should be set. The new drawing size is saved and can be reused in other diagrams, too. To
print the diagram, the new drawing size can be scaled to other sizes (Subsize for Printing in the
Drawing Format dialog ).
• Insert graphical branches: If not checked, the Diagram Layout Tool creates only graphical
representations of nodes (or composite elements, if the option is checked).
• Ortho Type: If set to Ortho, all the inserted branch elements will consist of only vertical or
horizontal sections. The contrary option is Ortho Off, where the branch elements show a direct
point-to-point connection between the according start and end nodes. With the option set to Semi-
Ortho, the branches have a orthogonal part near the start and end node and in between a direct
connection.

9.7.6 Draw existing elements using Drag & Drop

An additional possibility to create graphical objects of existing data elements is offered by the Drag &
Drop functionality of PowerFactory , following these steps:

1. Enable the Drag & Drop feature in a Data Manager window by double-clicking the Drag & Drop
message in the message bar.
2. Select the data object in the Data Manager by left clicking on its icon.
3. Hold down the left mouse button and move the mouse to the graphic drawing area (drag it).
4. Position the graphical symbol and release the mouse button to drop the object.

5. A new graphical symbol is created, which is representing the selected element in the diagram. No
new data object is created.

This approach may lead to problems and should therefore be used carefully.

9.8 Editing and Changing Symbols of Elements

You can edit or change the symbols, which are used to represent the elements in the single line graphic.
Right click with on a symbol of an element in the single line graphic, and select Change Symbol from
the context sensitive menu in order to use a different symbol for the element.

PowerFactory supports user-defined symbols as Windows-Metafile (* .wmf) and Bitmap (* .bmp) files.

For additional information refer to Appendix E (Element Symbol Definition).

126 DIgSILENT PowerFactory 2016, User Manual

 9.9. RESULT BOXES, TEXT BOXES AND LABELS

9.9 Result Boxes, Text Boxes and Labels

PowerFactory uses result boxes, text boxes, and labels in the Single Line Diagram to display calculation
results and other useful information. Figure 9.9.1 illustrates how these can be shown in the Single Line
Diagram.

Figure 9.9.1: Results boxes, text boxes, and labels available in PowerFactory

9.9.1 Result Boxes

General:

Result boxes are generally set up so that there are a series of different formats for each calculation
function, with variables appropriate to that function. In addition, the format differs for the objects class
and/or for individual objects. For example, following a load-flow, branch and edge elements will have
different formats compared to nodes, and an external grid will have an individual, different, format as
compared to the branch and edge elements.

The result box itself is actually a small output report, based on a form definition. This form definition,
and the PowerFactory output language that is used to define it, allows for the display of a wide range of
calculated values, object parameters, and even for colouring or user defined text.

Although the result boxes in the single line graphic are a very versatile and powerful way for displaying
calculation results, it is often not possible to display a large (part of a) power system without making
the result boxes too small to be read. PowerFactory solves this problem by offering balloon help on the
result boxes. Positioning the mouse over a result box will pop up a yellow text balloon with the text
displayed in a fixed size font. This is depicted in Figure 9.9.1. The result box balloon always states the
name of the variable, and may thus also be used as a legend.

Reference points:

A result box is connected to the graphical object for which it displays the results by a ’reference point’.
Figure 9.9.1 shows the default reference points for the result box of a terminal. A reference point is a
connection between a point on the result box (which has 9 optional points), and one of the ’docking’
points of the graphical object. The terminal has three docking points: on the left, in the middle and on
the right. The reference point can be changed by:

• Right-clicking the result box with the graphics cursor (freeze mode off), and selecting Change

DIgSILENT PowerFactory 2016, User Manual 127

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Reference Points.
• The reference points are shown: docking points in green, reference points in red. Select one of
the reference points by left-clicking it.

• Left-click the selected reference point, and drag it to a red docking point and drop it.
• An error message will result if you drop a reference point somewhere else than on a docking point.

Result boxes can be freely moved around the diagram. They will remain attached to the docking point,
and will move along with the docking point. A result box can be positioned back to its docking point by
right-clicking it and selecting Reset Settings from the menu.

If the option “Reset textboxes completely” is set in the graphical settings, then the default reference
and docking points will be selected again, and the result box is moved back to the default position
accordingly.

Editing Result Boxes:

PowerFactory uses separate result boxes for different groups of power system objects, such as node
objects (i.e. busbars, terminals) or edge objects (i.e. lines, loads). For each type of result box, a different
result box definition is used.

A newly installed version of PowerFactory has pre-defined result box formats for all object groups. These
default formats cannot be changed, however the user may define other formats and save these for use.
For the edge objects, for example, the default box shows P and Q without units.

A number of these predefined formats are available for display; they may be selected by right-clicking a
results box to get the Format for Edge Elements (in this example) option, which then presents a number
of formats that may be selected. The active format is ticked ( ) and applies for all the visualised edge
elements.

It is also possible to select predefined formats for a specific element class. If the edge element is for
example an asynchronous machine, in the context sensitive menu it will be also possible to get the
option Format for Asynchronous Machine, which shows the predefined formats for the element class
Asynchronous Machine (ElmAsm). The selected format will in this case apply only to the visualised
asynchronous machines.

If the user wants to create a specific format that is different from the pre-defined ones, the Edit Format
for Edge Elements (or Node Elements) option should be used. Note that the new format will be applied
to the entire group of objects (edge or node objects).

If a created format is expected to be used for just one specific element, then the Create Textbox option
should be used. An additional results box/ textbox will be created, using the current format for the object.
This may then be edited. Information about text boxes is given in 9.9.2.

When the Edit Format option has been selected, the user can modify the variables and how are they
showed as described Chapter 18: Reporting and Visualising Results, Section 18.2.1: Editing Result
Boxes.

128 DIgSILENT PowerFactory 2016, User Manual

 9.9. RESULT BOXES, TEXT BOXES AND LABELS

Formatting Result Boxes:

Result boxes can be formatted by means of the context sensitive menu (right-clicking the desired result
box). The available options include:

• Shift to layer (see 9.6.6).

• Rotate the result box
• Hide the result box

• Change the font type and size of the text

• Change the width
• Change colour

• Set the text alignment

• Adapt width
• Change reference points
• Set the default format (Reset Settings, only available after changes have been made).

Resetting Calculation Results:

When pressed, the Reset Calculation icon ( ) will clear the results shown on the Single Line Diagram.
By default, PowerFactory will also clear the calculation results when there is a change to network data
or network configuration (such as opening a switch). However, if ’Retention of results after network
change’ is set to ’Show last results’ in the User Settings (see Section 7.1: General Settings), results will
appear in grey on the Single Line Diagram and on the Flexible Data tab until the calculation is reset,
or a new calculation performed. ’Reset Calculation’ can also be accessed from the main menu under
’Calculation’.

9.9.2 Text Boxes

As mentioned before, text boxes are used to display user defined variables from a specific referenced
object within the single line graphic. To create a text box, right-click on the desired object (one end of
the object when it is a branch element) and select Create Textbox. By default a text box with the same
format of the corresponding result box will be generated.

The created text box can be edited, to display the desired variables, following the same procedure
described in 9.9.1. In this case after right-clicking the text box, the option Edit Format should be
selected. By default the text boxes are graphically connected to the referred object by means of a
line. This ”connection line” can be made invisible if the option show line from General Textboxes.... from
the Result Boxes page of the Graphic Option dialog (9.6.5) is disabled.

9.9.3 Labels

In the general case, a label showing the name of an element within the single line graphic is automat-
ically created with the graphical objects (see Figure 9.9.1). The label can be visualised as a text box
showing only the variable corresponding to the name of the object. As for text boxes, the format of
labels can be set using the context sensitive menu.

DIgSILENT PowerFactory 2016, User Manual 129

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.9.4 Free Text Labels

Free Text Labels (see Figure 9.9.1) can be anchored to an element on the single line diagram, and used
to display custom text. The are created by right-click and selecting ’Create Free Text Label’.

9.10 Annotation Layer

The Annotation Layer function offers the user the opportunity to include additional graphical information
in one or more configurable layers in the single line, geographic or block diagrams. Examples include:

• Built in graphical annotation elements

• Text
• Icons (bitmap files)
• Plots

To draw the Elements in the single line diagram the user has to deactivate the Freeze Annotation Layer
mode in the upper right corner (marked in figure 9.10.1).

Figure 9.10.1: Geographical diagram example

The activation of the annotation layer deactivates the selection of power system elements and activates
the selection of annotation elements. By selecting an annotation element, the user can place it in the
diagram. The annotation elements are as follows:

• Graphical annotation

– Line:
– Polyline:
– Arrow:

130 DIgSILENT PowerFactory 2016, User Manual

 9.10. ANNOTATION LAYER

– Polyline with arrow:

– Polygon:
– Rectangle:
– Circle:
– Pie:
– Arc:

• Text:

• Icons (bitmap files):

• Plots:

Except the icons and plots, all the annotation elements can be drawn directly in the diagram. Before
placing an icon in the diagram, an available icon-object has to be selected or if not yet existing, created.
To insert a plot into the diagram, an already existing virtual instrument can be selected from the list in
the object browser, which opens after pressing the button.

It is possible to create multiple annotation layers. To do this, the user should click on the button and
then select the Annotation Layer tab from the Visibility page (see figure 9.10.2). Alternatively, this dialog
can be accessed by right clicking on the single line diagram and select Layers.... A new layer can be
created by pressing the edit layers button as illustrated in figure 9.10.2 and then by pressing the icon
( ). The new layer should be given an appropriate name.

DIgSILENT PowerFactory 2016, User Manual 131

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

Figure 9.10.2: Layer overview

The newly created layers can be made visible or invisible by clicking or in the dialog shown
in figure 9.10.2. The Network Elements layer can not be hidden, since it contains the fundamental
Elements of the diagram which are to be annotated.
To edit a particular layer the layer has to be selected in the drop-down menu shown in the Layer Edit
Modes section of the dialog. Additional information about layers can be found in section 9.6.6.

Drawing sequence of Layers

If annotation layers are drawn on top of each other the sequence in which the layers are drawn becomes
important. The sequence of the layers can be changed by dragging them to a higher or lower position
in the Visibility/Order list shown in figure 9.10.2. The first entry in the list will be displayed as the upper
layer of the diagram. Layers can be given a higher entry in the list than the Network Elements layer and
this will be reflected in the graphic.

Export graphical layer

To export a graphical layer the user should press the Edit Layers Button as shown in figure 9.10.2. In
the following Window a list of all the available layers is shown. The user can export the layer as an *.svg
file as shown in figure 9.10.3.

Import graphical layer

132 DIgSILENT PowerFactory 2016, User Manual

 9.11. ANNOTATION OF PROTECTION DEVICE

To import a graphical layer, the user should select the Edit Layers button. By creating a new layer with
( ), it is possible to Import an existing layer as shown in (figure 9.10.4).

Figure 9.10.3: Layer overview

Figure 9.10.4: New Layer

9.11 Annotation of Protection Device

Adding a protection device into the single line diagram is described in Section 42.2.2.

DIgSILENT PowerFactory 2016, User Manual 133

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.12 Navigation Pane

The navigation pane provides the user an overview of the whole network in a small window. It is
available for all graphics but Virtual Instruments (described in Section 18.5: Virtual Instruments). When
zooming-in on a part of the grid, the navigation pane provides an overview of the whole network and
highlights the part of the network that is currently being shown in the diagram. This is illustrated in
Figure 9.12.1.

In addition, the navigation pane supports the relocation of the zoomed area, while maintaining the zoom
level. This is achieved by either moving the red frame inside the navigation pane to the desired location,
or by double-clicking on another location within the navigation pane. By resizing the red frame in the
navigation pane, the zoom level used in the single line diagram can be changed accordingly.

Figure 9.12.1: Navigation pane

The navigation pane is enabled for every diagram by default, but can be disabled for specific diagrams.
Disabling the navigation pane is done by first clicking on the Graphic Options icon ( ). In the dialog,
go to the Advanced tab within the Basic Attributes and disable the option “Allow Navigation Pane”.

To close the navigation pane, either click on the X in the top right-hand corner, or go to the main menu,
under Window → Navigation Pane. It can be reactivated by clicking on Window → Navigation Pane
again.

9.13 Geographical Diagrams

In PowerFactory it is possible to specify terminal GPS coordinates, and automatically generate geo-
graphical diagrams. GPS coordinates (latitude and longitude) are entered on the Description page of
terminals and lines, on the Geographical Coordinates tab. One geographical diagram can be created
per project by either:

• Opening the Data Manager, right-clicking on the active project or active grid and selecting Show
Geographical Diagram.

134 DIgSILENT PowerFactory 2016, User Manual

 9.13. GEOGRAPHICAL DIAGRAMS

• On the main menu, under Insert → Geographical Diagram.

The geographical diagram provides a visual representation of the network and includes all terminals
and lines for which GPS coordinates have been entered.

An additional layer called “Load / Generation Distribution” is available for GPS coordinates to illustrate
the magnitude of network load and generation (apparent power), as illustrated in Figure 9.13.1. Note
that the displayed size of circles does not change as the user zooms in and out of the diagram.
Colour and ’Scaling Factor’ settings can be modified on the Configuration page of Layers ( ), see
Section 9.6.6 (Layers).

Figure 9.13.1: Geographical diagram example

Maps can be used as background images and can be specified on the Configuration page of Layers
( ). Maps from the following providers are supported:

• IGN Géoportail, including road maps, satellite and special maps

• OpenStreetMap (OSM), featuring free-of-charge mapnik-style maps

• Esri ArcGIS©, including road maps, satellite, and hybrid maps
• Google Maps©1 , including road maps, satellite/aerial, hybrid, and topographic maps

• Bing Maps, including road and satellite maps

• Local map files, stored in plain text-files

To use the map data of some providers, special licence keys are necessary, which can be stored in the
Geographic Maps page of the configuration dialog accessed via Tools → Configuration.
1 requires Google Maps for Business account: http://www.google.com/enterprise/mapsearth

DIgSILENT PowerFactory 2016, User Manual 135

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

9.13.1 Using an External Map Provider

If an external map provider from the internet is used, the Map type can be chosen from (depending on
what types of maps the provider offers):

• Roadmap
• Satellite/Aerial

• Hybrid
• Topographic

The following parameters are available:

• Saturation adjustment
• Brightness adjustment

These parameters are valid in the range -100 % and +100 % and can be used to highlight either the
map or the network elements.

Figures 9.13.2 and 9.13.3 illustrate small distribution grids where OpenStreetMap, and Esri ArcGIS©
satellite maps, respectively, are used as the background image providers.

Figure 9.13.2: Network example with OpenStreetMap data

136 DIgSILENT PowerFactory 2016, User Manual

 9.13. GEOGRAPHICAL DIAGRAMS

Figure 9.13.3: Network example with satellite background map (ESRI ArcGIS©)

9.13.2 Using Local Maps

To display background images (e.g. maps) on the geographical diagram, the map provider must be
selected as Local map files. A File for reading background images must be selected. This facilitates
’tiling’ of multiple images in the background of the GPS graphic if required.

The File is simply a text file with semicolon delimited entries, as follows:

Image_filename; X1; Y1; X2; Y2

Where:

• Image_filename is the name of the image file. If it is not in the same directory as the File, it should
include the file path.
• X is the latitude and Y is the longitude.
• (X1,Y1) are the bottom-left coordinates of the image.

• (X2,Y2) are the top-right coordinates of the image.

• The # symbol can be used to comment-out entries.

DIgSILENT PowerFactory 2016, User Manual 137

CHAPTER 9. NETWORK GRAPHICS (SINGLE LINE DIAGRAMS)

138 DIgSILENT PowerFactory 2016, User Manual

Chapter 10

Data Manager

10.1 Introduction

To manage/ browse the data in PowerFactory , a Data Manager is provided. The objective of this
chapter is to provide detailed information on how this Data Management tool. Before starting, users
should ensure that they are familiar with Chapter 4 (PowerFactory Overview).

10.2 Using the Data Manager

The Data Manager provides the user with all the features required to manage and maintain all the data
from the projects. It gives both an overview over the complete data base as well as detailed information
about the parameters of single power system elements or other objects. New case studies can be
defined, new elements can be added, system stages can be created, activated or deleted, parameters
can be changed, copied, etc. All of these actions can be instituted and controlled from a single data
base window.

The Data Manager uses a tree representation of the whole database, in combination with a versatile
data browser.To initially open a Data Manager window press the icon from the main toolbar. The
settings of this window can be edited using the ’User Settings’ dialog (Section 10.2.5: Data Manager
Settings).

The Data Manager window has the following parts (see Figure 10.2.1):

• The title bar, which shows the name and path of the of the folder currently selected in the database
[1].

• The Data Manager local tool bar [2].

• In the left upper area the database window, which shows a symbolic tree representation of the
complete database [3].
• In the left lower area the input window. It may be used by more experienced users to enter
commands directly, instead of using the interactive command buttons/dialogs. By default it is not
shown. For further information see Section 10.8 (The Input Window in the Data Manager) [4].
The input window is opened and closed by the clicking on the Input Window button ( ).
• On the right side is the database browser that shows the contents of the currently selected folder
[5].

DIgSILENT PowerFactory 2016, User Manual 139

CHAPTER 10. DATA MANAGER

• Below the database browser and the input window is the message bar, which shows the current
status and settings of the Data Manager (for further information see Section 10.2.5).

There are some special features of the database browser which can be accessed at any time when the
content of a folder is shown:

• Balloon text: this is not only available for the buttons in the tool bar and the active parts of the
message bar or the browser window, but also for the data fields [a].

• Active Title buttons of each column; click on any title button to sort the items in the column; first
click- items are sorted in ascending order; second click - items are sorted in descending order [b].
• Object buttons showing the object standard icon in the first column of the database browser: each
object is represented by a button (here a line object is shown). One click selects the object and a
double-click presents the edit dialog for the object [c].

Figure 10.2.1: The Data Manager window

PowerFactory makes extensive use of the right mouse button. Each object or folder may be ’right-clicked’
to pop up a context sensitive menu. For the same object the menu presented will differ depending on
whether the object is selected in the left or right hand side of the Data Manager (this is known as a
’context sensitive’ menu). Generally, the left hand side of the Data Manager will show object folders
only. That is, objects that contain other objects inside them. The right hand side of the Data Manager
shows object folders as well as individual objects.

140 DIgSILENT PowerFactory 2016, User Manual

 10.2. USING THE DATA MANAGER

Figure 10.2.2: Context sensitive menus in the Data Manager

Using the right mouse button to access menus is usually the most effective means of accessing features
or commands. Figure 10.2.2 shows an Illustration of a context-sensitive right mouse button menu.

The symbolic tree representation of the complete database shown in the database window may not
show all parts of the database. The user settings offer options for displaying hidden folders, or for
displaying parts that represent complete stations. Set these options as required (Section 10.2.5: Data
Manager Settings).

Note: It is useful to keep in mind that object folders, such as the grid ( ) folder are merely common
folders , that have been designated to contain particular classes of objects.

10.2.1 Navigating the Database Tree

There are several ways to “walk” up and down the database tree:

• Use the mouse: all folders that have a “+” sign next to them may be expanded by double-clicking
on the folder, or by single clicking the “+” sign.
• Use the keyboard: the arrow keys are used to walk up and down the tree and to open or close
folders (left and right arrows). The Page Up and Page Down keys jump up and down the tree in
big steps and the “-” and “+” keys may also be used to open or close folders.

• Use the toolbar in combination with the browser window. Double-click objects (see “c” in Fig-
ure 10.2.1) in the browser to open the corresponding object. This could result in opening a folder,
in the case of a common or case folder, or editing the object dialog for an object. Once again, the
action resulting from your input depends on where the input has occurred (left or right side of the
Data Manager).

DIgSILENT PowerFactory 2016, User Manual 141

CHAPTER 10. DATA MANAGER

• The buttons Up Level ( ) and Down Level ( ) on the Data Manager tool bar can be used to
move up and down the database tree.

10.2.2 Adding New Items

Generally, new network components are added to the database via the graphical user interface (see
Section 9.2: Defining Network Models with the Graphical Editor), such as when a line is drawn between
two nodes creating, not only the graphical object on the graphics board, but also the corresponding
element data in the relevant grid folder. However, users may also create new objects “manually” in the
database, from the Data Manager.

Certain new folders and objects may be created by right-clicking on folders in the Data Manager. A
context sensitive menu is presented, offering a choice of objects to be created that will “fit” the selected
folder. For example, right-clicking a grid folder will allow the creation (under the New menu) of a Graphic,
a Branch, a Substation, a Site or a Folder object. The new object will be created in the folder that was
selected prior to the new object button being pressed. This folder is said to have the ’focus’ for the
commanded action. This means that some objects may not be possible to create since the focused
folder may not be suited to hold that object.

For instance: A synchronous machine should not go into a line folder. A line folder should contain
only line routes, line sections and cubicles. The cubicles in their turn should contain only switches or
protection elements.

To access the whole range of objects that may be created, the icon must be pressed (new object
icon). This is found the Data Manager toolbar and presents the dialog shown in Figure 10.2.3.

To simplify the selection of the new objects, a filter is used to sort the object list. This filter determines
what sort of list will appear in the drop-down list of the ’Element’ field. If “Branch Net Elements” is first
selected, the selection of, for instance, a 2-winding transformer is accomplished by then scrolling down
the element list.

The Element field is a normal edit field. It is therefore possible to type the identity name of the new
element, like ElmTr3 for a three-winding transformer, or TypLne for a line type directly into the field.

The possible list of new objects is therefore context sensitive and depends on the type or class of the
originally selected folder.

142 DIgSILENT PowerFactory 2016, User Manual

 10.2. USING THE DATA MANAGER

Figure 10.2.3: The element selection dialog

After the selection for a new object has been confirmed, the “Element Selection” dialog will close, the
new object will be inserted into the database and the edit dialog for the new object will pop up. If this
dialog is closed by pressing the Cancel button, the whole action of inserting the new object will be
cancelled: the newly created object will be deleted from the active folder. The dialog for the new object
may now be edited and the OK button pressed to save the object to the database.

As any other object, folders can be created either by using the context sensitive menu or by using the
icon. Common folders (IntFolder objects) may have an owner name entered, for documentation or
organisational purposes. In this way it should be clear who has created the data. Descriptions may also
be added. An existing folder may be edited by using the Edit icon on the toolbar or by using the right
mouse button.

Each folder may be set to be read-only, or to be a PowerFactory system folder. The folder may be a
“Common” or “Library” folder. These attributes can be changed in the edit-folder dialog. These settings
have the following meaning:

• Common folders are used for storing non-type objects: electric elements, command objects,
settings, projects, etc.
• Type folders are used as ’libraries’ for type objects.
• System folders, which are read only folders

The use of read-only folders is clear: they protect the data. In addition, folders containing data that is

DIgSILENT PowerFactory 2016, User Manual 143

CHAPTER 10. DATA MANAGER

not normally accessed may be hidden. Selecting the kind of folders that the user/administrator wants to
be hidden is done in the user settings dialog see Chapter 7 (User Settings).

10.2.3 Deleting an Item

A folder or object which is selected may be deleted by pressing the Delete key on the keyboard, or by
clicking the icon on the toolbar of the Data Manager.

When deleting an object on the Data Manager or in the Single Line diagram, this object will be deleted
immediately from the database. Only the Undo button or Crlt-Z can restore the element and its
references to the original location.

Because most power system objects that are stored in the database are interconnected through a
network topology or through type-element relationships, deleting objects often causes anomalies in the
database consistency. Of course, PowerFactory knows at any moment which objects are used by which
others and could prevent the user from creating an inconsistency by refusing to delete an object that is
used by others.

10.2.4 Cut, Copy, Paste and Move Objects

Cut, Copy and Paste

Cutting, copying and pasting may be achieved in four different manners:

1. By using the Data Manager tool bar buttons.

2. By using the normal ’MS Windows’ shortcuts:

• Ctrl-X will cut a selection,
• Ctrl-C will copy it,
• Ctrl-V will paste the selection to the active folder.

Cutting a selection will colour the item-icons gray. The cut objects will remain in their current folder
until they are pasted. A cut-and-paste is exactly the same as moving the object, using the context
sensitive menu. All references to objects that are being moved will be updated. Cancelling a
cut-and-paste operation is performed by pressing the Ctrl-C key after the Ctrl-X key has been
pressed.

3. By using the context sensitive menu. This menu offers a Cut, a Copy and a Move item. The move
item will pop up a small second database tree in which the target folder can be selected. When
the selected objects have been Cut or Copied, the context sensitive menu will then show a Paste,
Paste Shortcut and a Paste Data item.
• Paste will paste the selection to the focused folder.
• Paste Shortcut will not paste the copied objects, but will create shortcuts to these objects. A
shortcut object acts like a normal object. Changes made to the shortcut object will change the
original object. All other shortcuts to this original object will reflect these changes immediately
• Paste Data is only be available when just one object is copied, and when the selected target
object is the same kind of object as the copied one. In that case, Paste Data will paste all
data from the copied object into the target object. This will make the two objects identical,
except for the name and the connections.
4. By dragging selected objects to another folder. The ’Drag & Drop’ option must be enabled first
by double-clicking the ’Drag & Drop: off’ message on the Data Manager’s message bar. When
the Drag & Drop option is on, it is possible to copy or move single objects by selecting them and
dragging them to another folder. Dragging is done by holding down the left mouse button after an

144 DIgSILENT PowerFactory 2016, User Manual

 10.2. USING THE DATA MANAGER

object has been selected and keeping it down while moving the cursor to the target/destination
folder, either in the database tree or in the database browser window.

Note: When dragging and dropping a COPY of the object will be made (instead of moving it) if the Ctrl
key is held down when releasing the mouse button at the destination folder. To enable the ’Drag &
Drop’ option double click the ’Drag & Drop’ message at the bottom of the Data Manager window.

10.2.5 The Data Manager Message Bar

The message bar shows the current status and settings of the Data Manager. Some of the messages
are in fact buttons which may be clicked to change the settings.

The message bar contains the following messages.

• “Pause: on/off” (only in case of an opened input window) shows the status of the message queue
in the input window. With pause on, the command interpreter is waiting which makes it possible
to create a command queue. The message is a button: double-clicking it will toggle the setting.

• “N object(s) of M” shows the number of elements shown in the browser window and the total
number of elements in the current folder.
• “N object(s) Selected:” shows the number of currently selected objects.
• “Drag & Drop: on/off” shows the current drag & drop mode. Double clicking this message will
toggle the setting.

10.2.6 Additional Features

Most of the Data Manager functionality is available through the context sensitive menus (right mouse
button).

The following items can also be found in the context sensitive menus:

Show Reference List (Output. . . → Reference List) Produces the list of objects that have links, or
references (plus the location of the linked object), to the selected object. The list is printed to the
output window. In this manner for example, a list of elements that all use the same type can be
produced. The listed object names can be double- or right-clicked in the output window to open
their edit dialog.
Select All Selects all objects in the database browser.
Mark in Graphic Marks the highlighted object(s) in the single line graphic. This feature can be used to
identify an object.
Show → Station Opens a detailed graphic (displaying all the connections and switches) of the terminal
to which the selected component is connected. If the component, is connected to more than one
terminal, as might be in the case of lines or other objects, a list of possible terminals is shown first.

Goto Busbar Opens the folder in the database browser that holds the busbar to which the currently
selected element is connected. If the element is connected to more than one busbar, a list of
possible busbars is shown first.
Goto Connected Element Opens the folder in the database browser that holds the element that is
connected to the currently selected element. In the case of more than one connected element,
which is normally the case for busbars, a list of connected elements is shown first.

DIgSILENT PowerFactory 2016, User Manual 145

CHAPTER 10. DATA MANAGER

Calculate Opens a second menu with several calculations which can be started, based on the currently
selected objects. A short-circuit calculation, for example, will be performed with faults positioned
at the selected objects, if possible. If more than one possible fault location exists for the currently
selected object, which is normally the case for station folders, a short-circuit calculation for all
possible fault locations is made.

Other useful features:

• Relevant objects for calculations are tagged with a check-mark sign (this will only be shown
following a calculation). Editing one of these objects will reset the calculation results.

10.3 Defining Network Models with the Data Manager

In this section it is explained how the tools of Data Manager are used to define network models.

10.3.1 Defining New Network Components in the Data Manager

New network components can be directly created in the Data Manager. To do this you have to click
on the target grid/expansion stage (right pane) to display its contents in the browser (left pane). Then
you have to click on the New Object icon and select the kind of object to create. Alternatively you can
directly enter the class name of the new component.

10.3.2 Connecting Network Components in the Data Manager

To connect newly created branch elements to a node, a free cubicle must exist in the target terminal. In
the ’Terminal’ field (Terminal I and Terminal j for two port elements, etc.) of the edge element you have
to click on the ( ) arrow to select (in the data browser that pops up) the cubicle where the connection
is going to take place.

To create a new cubicle in a terminal you have to open its edit dialog (double click) and press the
Cubicles button (located at the right of the dialog). A new browser with the existing cubicles will pop up,
press the New Object icon and in the ’Element’ field select Cubicle (StaCubic). The edit dialog of
the new cubicle will pop up; by default no internal switches will be generated. If you want a connection
between the edge element and the terminal trough a circuit breaker, you have to press the Add Breaker
button. After pressing the Ok button the new cubicle will be available to connect new branch elements.

Note: New users are recommended to create and connect elements directly from the single line graph-
ics. The procedures described above are intended for advanced users.

10.3.3 Defining Substations in the Data Manager

The concept and the application context of substations is presented in Section 4.7 (Project Structure). A
description of the procedure used to define new substations with the Data Manager is given as follows.
For information about working with substations in the graphical editor refer to Section 9.2 (Defining
Network Models with the Graphical Editor).

To define a new substation from the Data Manager do the following:

• Display the content of the grid where you want to create the new substation.

146 DIgSILENT PowerFactory 2016, User Manual

 10.3. DEFINING NETWORK MODELS WITH THE DATA MANAGER

• Right click on the right pane of the Data Manager and select New → Substation from the context
sensitive menu.
• The new substation edit dialog will pop up. There you can change the name, assign running
arrangements and visualise/edit the content of the substation (directly after creation it is empty).
• After pressing Ok the new substation and an associated diagram (with the same name of the
substation) will be created.

The components of the new substation can be created and connected using the associated single line
diagram or using the Data Manager, the first option is recommended. For the second option, a data
browser with the content of the substation will pop up after pressing the Contents button; there you can
use the New Object icon to create the new components.

Components of a substation can of course be connected with components of the corresponding grid or
even with components of other networks. The connection in the Data Manager is carried out following
the same procedure discussed in the previous section.

For information about working with substations in the graphical editor refer to Section 9.2 (Defining Net-
work Models with the Graphical Editor). For information about the definition of Running Arrangements
refer to Section 13.3.6 (Running Arrangements).

10.3.4 Defining Composite Branches in the Data Manager

The concept and the application context of composite branches is discussed in Section 4.7 (Project
Structure), and a description of how to define branches from within the diagram is provided in Sec-
tion 9.2 (Defining Network Models with the Graphical Editor). This section provides a description of the
procedure used to define new branches from within the Data Manager.

Branches can be defined in the Data Manager as follows:

1. To create a Branch template, navigate to the Library → Templates folder in the Data Manager.

2. Right-click on the right pane of the Data Manager and select New → Branch from the context
sensitive menu.
3. In the branch edit dialog, define the name of the branch and press Ok.
4. Now navigate back to the branch edit dialog (right-click and ’edit’, or double click), and select
Contents to add terminal and line elements etc. to the template as required. The internal
elements can be connected as discussed in Section 10.3.2.
5. Use the fields ’Connection 1’ and ’Connection 2’ to define how the branch is to be connected to
external elements.
6. To create an instance of the Branch from the created Branch template, either:

• Select the Composite Branch icon and connect the branch to existing terminals on the
Single Line Diagram.
• Select the Composite Branch icon and place the branch on the single line diagram, press
Tab twice to place the branch without making any connections. Then connect the branch to
external elements by right-clicking and selecting ’Connect’, or double-clicking the branch and
selecting external connections for the relevant internal elements (e.g. lines). Select Update
on in the Branch dialog to update the external connections.

Alternatively, for a single Branch (i.e. not using Templates) the branch can be defined in the grid folder.

DIgSILENT PowerFactory 2016, User Manual 147

CHAPTER 10. DATA MANAGER

10.3.5 Defining Sites in the Data Manager

The concept and the application context of sites are presented in the Section 4.7 (Project Structure).
Next a description of the procedure used to define new sites is given.

To define a new site from the Data Manager do the following:

• Display the content of the grid where you want to create the new site.
• Right click on the right pane of the Data Manager and select New → Site from the context sensitive
menu.
• The new Site edit dialog will pop up.
• After pressing Ok the new site will be created.

Note: Advanced users would notice that it is possible to move objects from a grid to a Substation,
Branch, Site, etc. and vice versa.

10.3.6 Editing Network Components using the Data Manager

Each component can be individually edited by double clicking on it to open the corresponding dialog.
The class dialog is composed of several tabs each corresponding to a calculation function of PowerFac-
tory. The parameters required by a determined calculation are always available on the corresponding
tab. The description of the network component’s models, explaining the relations among the input
parameters is given in the technical reference papers attached to the Appendix B (Technical References
of Models).

It is possible to simultaneously edit components of the same class using the Data Manager. To do this
you have to select a component of the class that you want to edit (left click on the component icon) and
click on the Detail Mode icon at the upper part of the Data Manager.

In ’detail’ mode, the browser shows all data fields for the selected calculation function data set, which
can be selected by clicking on a tab shown at the bottom of the table view. If a page tab is out of reach,
then the page tab scrollers will bring it within the browser window again.

The list of objects may be sorted by any column by pressing the title field button. The widths of the data
fields can be adjusted by pointing the mouse on the separation line between two title fields and dragging
the field border by holding a mouse button down. The data fields can be edited by double-clicking them.
As with any Spread Sheet, you can copy and paste individual or multiple cells with Crtl_C and Crtl_V or
with right click ’ Copy/Paste.

It is also possible to change a parameter field for more than one object simultaneously. The parameter
fields which are going to be changed have to be multi-selected first, then you have to right-click the
selection and select the option Modify Value(s) from the context sensitive menu. This will open the
SetValue dialog. This dialog can be used to:

• Increase or decrease them by multiplication with a scale factor (“Relative”).

• Increase or decrease them by multiplication with a scale factor with respect to the sum of values
selected (“Relative to Sum”).
• Set all the selected parameter fields to a new fixed (“absolute”) value.

Note: It is not possible to simultaneously alter parameter fields from more than one column, i.e. to
change nominal currents and nominal frequencies simultaneous, even if they would happen to
take the same value or would have to be raised with the same percentage.

148 DIgSILENT PowerFactory 2016, User Manual

 10.4. SEARCHING FOR OBJECTS IN THE DATA MANAGER

For further information refer to 10.6 (Editing Data Objects in the Data Manager).

10.4 Searching for Objects in the Data Manager

There are three main methods of searching for objects in the data base: Sorting, searching by name
and filtering.

10.4.1 Sorting Objects

Objects can be sorted according to various criteria, such as object class, name, rated voltage,..., etc.
Sorting according to object class is done using the Open Network Model Manager. . . icon on the toolbar
( ). A browser window will open, in which the user may select a particular class of calculation-relevant
object (e.g. synchronous machine, terminal, general load, but not graphics, user settings etc.).

Further sorting can be done according to the data listed in a table- either in the Data Manager or in a
browser obtained using the procedure described above. This is done by clicking on the column title. For
example, clicking on the column title ’Name’ in a data browser sorts the data alphanumerically (A-Z and
1-9). Pressing it again sorts the data Z-A, and 9-1.

Tabulated data can be sorted by multiple criteria. This is done by clicking on various column titles in a
sequence. For example, terminals can be sorted alphanumerically first by name, then by rated voltage
and finally by actual voltage by pressing on the titles corresponding to these properties in reverse-
sequence (actual voltageĚrated voltageĚname). A more detailed example follows:

Suppose that you have executed a load flow calculation and that, for each rated voltage level in the
network, you want to find the terminal with the highest voltage. These terminals could be identified
easily in a table of terminals, sorted first by rated voltage and then by calculated voltage. Proceed as
follows:

• Perform the load flow calculation.

• Select the ElmTerm class in the Network Model Manager .
• Include, in the Flexible Data page tab, the terminal voltage and nominal voltage (see 10.7).
• In the table (Flexible Data page tab), click on the title ’u, Magnitude p.u’ to sort all terminals from
highest to lowest calculated voltage.
• Then click on the title ’Nom.L-L Volt kV’ to sort by nominal voltage level.
• Now you will have all terminals first sorted by voltage level and then by rated terminal voltage.

10.4.2 Searching by Name

Searching for an object by name is done either in the right-hand pane of the Data Manager or in a data
browser. To understand the procedure below, notice that the first column contains the symbols of the
objects in the table. Clicking on such a symbol selects all columns of that row, i.e. for that object. The
procedure is as follows:

• Select an object in the table by clicking on any object symbol in the table (if one object was already
selected then select a different one).
• Now start typing the object name, which is case sensitive. Notice how the selection jumps as you
type, For example, typing ’T’ moves the selection to the first object whose name starts with T, etc.
• Continue typing until the selection matches the object that you are looking for

DIgSILENT PowerFactory 2016, User Manual 149

CHAPTER 10. DATA MANAGER

10.4.3 Using Filters for Search

Advanced filtering capability is provided with the Find function . A filter is normally defined to find a
group of objects, rather than individual objects (although the latter is also possible). Advanced search
criteria can be defined, e.g. transmission lines with a length in the range 1 km to 2.2 km, or synchronous
machines with a rating greater than 500 MW etc.

The function is available in both the Data Manager and a data browser. Clicking on the Find ( ) in the
Data Manager allows the user to apply a predefined filter or to define a new filter, called ’General filter’.
If a new filter is defined, the database folder that will be searched can be defined.

General Filters defined by the user are objects stored in the Changed Settings ∖ Filters folder.

The options in the General Filter dialog window are now explained:

Name: Name of filter.

Object filter: This field defines either the complete or a part of the search criteria, and is optional.
Examples are as follows:
• *.ElmSym: Include element objects of the class synchronous machines.
• *.TypSym: Include type objects of the class synchronous machines.
• Lahney.*: Include all objects with the name Lahney.
• Lahney.Elm*: Include all element objects with the name Lahney.
• D*.ElmLod: Include all load element objects whose names start with D.
• A drop down list providing various object classes can be accessed with .
Look in: This field is available if a filter id defined within the Data Manager. It allows the user to specify
the folder in the database that will be searched.
Check boxes:

• Include Subfolders will search the root folder specified as well as the subfolders in the root
folder. The search can be stopped at the matching folder.
• Relevant Objects for Calculation will include only those objects considered by the active
study case (if no study case is active the search is meaningless and no search results will be
returned).
• Area Interconnecting Branches will search for branch elements that interconnect grids.

The OK button will close the search dialog, but save the filter object to the Changed Settings∖Filters
folder. This makes it available for further use. The Cancel button will close the dialog without saving
the changes. This button is useful if a search criterion (filter) will only be used once.The Apply button
starts the actual search. It will scan the relevant folders and will build a list of all objects that match the
search criteria.

Once the search is complete a list of results is returned in the form of a new data browser window. From
this browser, the returned objects can be marked, changed, deleted, copied, moved, etc. . . .

Advanced search options allow more sophisticated expressions as search criteria. These are specified
in the Advanced page of the General Filter dialog (Figure 10.4.1). The filter criterion is defined in terms
of a logical expression, making use of parameter names. Objects will be included in the data browser if,
for their parameters, the logical expression is determined to be true. An example of a logical expression
is 𝑑𝑙𝑖𝑛𝑒 > 0.7. The variable dline refers to the length of a transmission line, and the effect of such a
filter criterion is to limit the data in the browser to transmission lines having a length exceeding 0.7 km.
The logical expressions can be expanded to include other relations (e.g. >=), standard functions (e.g.
sin()), and logical operators (e.g. .and.).

150 DIgSILENT PowerFactory 2016, User Manual

 10.5. AUTO-FILTER FUNCTIONS IN DATA MANAGER AND BROWSER WINDOWS

Note: Parameter names can be object properties or results. The parameter names for object properties
are found, for example, by letting the mouse pointer hover over an input field in an object’s dialog
window. Parameter names for result variables are found from variable sets, which are described
in Section 18.4 (Variable Sets).

Figure 10.4.1: Filter dialog - Advanced page

Search Literally is used to search for user defined strings ’inside’ parameter fields. The user can
specify if the search is done in a specific parameter, if the field in Parameter is left blank, all parameter
fields will be searched for this string.

As stated before, the objects matching the filter criteria are displayed in a data browser. They may also
be highlighted in the graphic using the ’Colour representation’ function described in Chapter 9: Network
Graphics (Single Line Diagrams). The colour to be used in this case can be specified under the page
Graphic of the General Filter dialog.

Note: New filters are saved to the Project∖Changed Settings∖Filters folder in the project and are
available for use directly, using the right mouse menu. If a search is to be performed in a particular
grid simply proceed as follows: right-click the grid folder → Find→ Local Filters→ Filter Name
(e.g. Lines longer than 700 m). Remember to press the Apply button to perform the search. If
you unchecked the Show Filter Settings before Application box under User Settings → General
then the filter will be applied as soon as it is selected from the menu. This is useful when you have
already defined several filters for regular use.

10.5 Auto-Filter functions in Data Manager and browser windows

Columns within the Data Manager, browser windows or the Network Model Manager can be filtered. To
add a filter for a column proceed as follows:

• Click on the down arrow in the column header of the table. A window will open.
• A list of all entries that differ from each other within that column, will be shown.
• Option: Selection

DIgSILENT PowerFactory 2016, User Manual 151

CHAPTER 10. DATA MANAGER

– Select/deselect desired/undesired entries from that list. Only objects, which contain marked
entries will later be shown in the table. All other ones will be hidden.
– Sometimes the list of entries can be very long. To reduce this list, the user may enter a text
into the search field. The list will be filtered with every typed character.
• Option: Custom...
– In addition to the possibility of selecting existing entries, also custom filters can be used by
choosing the radio button Custom... and confirming with OK.
– A new window will open, in which up to two filter can be combined via an AND or an OR
relation. For each of both filters one of the following criterions has to be chosen:
* None
* Equals
* Is not equal to
* Contains
* Does not contain
* Starts with
* Does not start with
* Ends with
* Does not end with
* Special
– After one criterion has been selected (except: None), a drop-down box will appear, from
which one of the entries may be chosen or an own text may be entered.

Filtered columns are indicated by a blue column heading and a filter symbol in the lower right corner of
the column header. By holding the mouse cursor still over the heading of a filtered column, a balloon
help appears and shows the applied filter settings.

The auto filters in the Data Manager and browser windows are temporary. They will be lost, if for
example another path is chosen.

10.6 Editing Data Objects in the Data Manager

The Data Manager offers several ways to edit power system components and other objects stored in
the database, regardless they appear graphically or not.

The basic method is to double-click the object icons in the database browser. This will open the same
edit dialog window obtained, when double clicking the graphical representation of an element in the
graphic window.

An open edit dialog will disable the Data Manager window from which it was opened. The edit dialog
has to be closed first in order to open another edit dialog.

However, it is possible to activate more than one Data Manager (by pressing the icon on the main
toolbar) and to open an edit dialog from each of these Data Managers. This can be useful for comparing
objects and parameters.

Using the edit dialogs has one major drawback: it separates the edited object from the rest of the
database, making it impossible to copy data from one object to the other, or to look at other object
parameter values while editing.

PowerFactory brings the big picture back in sight by offering full scale editing capabilities in the Data
Managers browser window itself. The browser window in fact acts like a spreadsheet, where the user
can edit and browse the data at the same time. The browser window has two modes in which objects
can be edited,

152 DIgSILENT PowerFactory 2016, User Manual

 10.6. EDITING DATA OBJECTS IN THE DATA MANAGER

• Object mode
• Detail Mode

which are described in the following sections.

10.6.1 Editing in Object Mode

In the general case the icon, the name, the type and the modification date (with its author) of the objects
are shown in the ’object’ mode. Certain objects, for example network components, show additional
fields like the “Out of Service” field.

The title buttons are used to sort the entries in the browser. The visible data fields can be double-clicked
to edit their contents, or the F2 button can be pressed. The object will show a triangle in its icon when
it is being edited.

After the data field has been changed, move to the other fields of the same object using the arrow-keys
or by clicking on these data fields, and alter them too.

The new contents of a data field are confirmed by pressing the Return key, or by moving to another
field within the same object. The triangle in the icon will change to a small star to show that the object
has been altered. The object itself however has not been updated. Updating the changes is done by
pressing Return again, or by moving to another object in the browser. By default, PowerFactory will
ask to confirm the changes. See Section 10.2.5 (Data Manager Settings) to disable these conformation
messages.

10.6.2 Editing in “Detail” Mode

If the icon on the browse window of the Data Manager is pressed, the browser changes to ’detail’
mode. It will display only the objects from the same class as the one which was selected when the
button was pressed.

In ’detail’ mode, the browser shows all data fields for the selected calculation function data set, which
can be selected by clicking on a tab shown at the bottom of the table view.If a page tab is out of reach,
then the page tab scrollers will bring it within the browser window again.

The list of objects may be sorted by any column by pressing the title field button. The widths of the
data fields can be adjusted by pointing the mouse on the separation line between two title fields and
dragging the field border by holding a mouse button down.

As with the browser in ’object’ mode, the data fields can be edited by double-clicking them. In the
example the active power settings are being edited, but from the star in the object icon it is clear
that another field of the same object has been edited too, but not confirmed, because this star would
otherwise be a triangle.

It is possible to change a parameter field for more than one object simultaneously. This is, for instance,
useful to raise a certain limit for a range of objects, in order to get a better load-flow result i.e. by
alleviating line overloads. An example is shown in Figure 10.6.1 where the nominal current for a range
of lines is changed at once.

DIgSILENT PowerFactory 2016, User Manual 153

CHAPTER 10. DATA MANAGER

Figure 10.6.1: Modify values dialog

Figure 10.6.2: Modify values dialog

The parameter fields which have to be changed have to be multi-selected first. Right-clicking the
selection will pop up a case sensitive menu from which the Modify Value(s) option opens the SetValue
dialog, see Figure 10.6.2.

This dialog can be used to:

• increase or decrease them by multiplication with a scale factor (“Relative”).

• increase or decrease them by multiplication with a scale factor with respect to the sum of values
selected (“Relative to Sum”).
• Set all the selected parameter fields to a new fixed (“absolute”) value.

It is not possible to simultaneously alter parameter fields from more than one column, i.e. to change
nominal currents and nominal frequencies simultaneous, even if they would happen to take the same
value or would have to be raised with the same percentage.

154 DIgSILENT PowerFactory 2016, User Manual

 10.7. THE FLEXIBLE DATA PAGE TAB IN THE DATA MANAGER

10.6.3 Copy and Paste while Editing

One of the great advantages of editing data fields in the Data Manager’s browser window is the possi-
bility to copy data from one object to another. This is done by selecting one or more objects or object
fields, copying this selection to the clipboard, and pasting the data back in another place.

To copy one or more objects,

1. Open the Data Manager and select the grid folder where you find the objects to be copied.
2. Select the objects.

3. Press Ctrl-C to copy or use the icon on the Data Manager toolbox.

4. Press Ctrl-V to paste or use the icon on the Data Manager toolbox. The objects will be copied
with all the data. Their names will automatically be altered to unique names.

Copying data fields from one object to another is done just like for any spreadsheet software you may
be familiar with. To copy one or more data fields,

1. Select them by clicking them once. Select more data fields by holding down the Ctrl key.

2. Copy the fields to the clipboard by pressing Ctrl-C or the icon.

3. Select one or more target objects data fields. If more than one field was copied, make sure that
the target field is the same as the first copied data field.

4. Press Ctrl-V or the icon. The contents of the data fields will be copied to the target objects.

10.7 The Flexible Data Page Tab in the Data Manager

The data browser (this will be seen in the Data Manager when the ’Detail Mode’ has been engaged)
has page tabs for all calculation functions. These tabs are used to view or edit object parameters which
are categorised according to a calculation function and have a fixed format.

The ’Flexible Data’ tab, normally used to display calculation results, allows the user to define a custom
set of data to be displayed.

The default format for the calculation results displayed in the flexible page depends on the calculation
performed: Following a load-flow calculation, the default variables for terminals are line-to-line voltage,
per unit voltage and voltage angle. Following a short-circuit calculation the default variables are initial
short-circuit current, initial short-circuit power, peak current etc. Figure 10.7.1 shows an example of the
flexible data page tab.

DIgSILENT PowerFactory 2016, User Manual 155

CHAPTER 10. DATA MANAGER

Figure 10.7.1: The Flexible Data page tab

10.7.1 Customising the Flexible Data Page

The displayed variables are organised in ’Variables Sets’ that are, in turn, organised according to the
calculation functions. For example, an object class ElmTr2 (two-winding transformer) has a variable set
for symmetrical load flow calculation, a variable set for short-circuit calculation etc. There may also be
more than one variable set for any calculation function. For example, the object ElmTr2 may have two
variable sets for symmetrical load flow calculation.

The Flexible Page Selector allows the user to specify the variable set to use, or to define new variable
sets. Furthermore, the Flexible Page Selector allows the user to access and edit the variable sets, i.e.
to specify which variables to display in the Flexible Data page.

The ’Flexible Page Selector’ dialog is shown in Figure 10.7.2. This dialog is opened by pressing the
( ) icon on the Data Manager toolbar. The Flexible Page Selector has a menu with all the different
calculation functions. It opens in the page corresponding to the most recent calculation.

The selection of variables within Variable Sets is presented in detail in Section 18.4 (Variable Sets).

156 DIgSILENT PowerFactory 2016, User Manual

 10.7. THE FLEXIBLE DATA PAGE TAB IN THE DATA MANAGER

Figure 10.7.2: The Flexible Page Selector

The Format/Header tab (Figure 10.7.3) allows the user to customise the header of the Flexible Data
page.

Figure 10.7.3: The Flexible Page Selector

Note: Variable Sets are objects of class IntMon, within PowerFactory they have multiple uses. This
section only presents their use in conjunction with Flexible Data. For further information refer to
Section 18.4 (Variable Sets).

DIgSILENT PowerFactory 2016, User Manual 157

CHAPTER 10. DATA MANAGER

The number format per column in the Flexible Data Page can also be modified by right clicking on the
column header of the variable and selecting Edit Number Format . . . . A new window will appear and
the user may define the number representation.

The order of the columns (except: Name, In Folder and Grid) on the Flexible Data page can be changed.
Therefor, the header of a column has to be clicked and while holding the left mouse button pressed, the
column can be moved to the desired position. To illustrate, where the column will be placed, when the
mouse button is released, an arrow between the actual and the possible new position of the column is
shown during this process.

10.8 The Input Window in the Data Manager

The input window is for the more experienced users of DIgSILENT PowerFactory . It is closed by default.
Almost all commands that are available in PowerFactory through the menu bars, pop-up menus, icons,
buttons, etc., may also be entered directly into the input window, using the PowerFactory commands.

The contents of the input window can be saved to file, and commands can be read back into the window
for execution.

PowerFactory also has special command objects which carry one single command line and which are
normally used to execute commands. In this way, complex commands can be saved in the same folder
as the power system for which they were configured.

10.8.1 Input Window Commands

In principle, everything that can be done in DIgSILENT PowerFactory , can be done from the command
line in the input window. This includes creating objects, setting parameters, performing load-flow or
short-circuit calculations.

Some commands that are available are typically meant for command line use or for batch commands.
These commands are rarely used in another context and are therefore listed here as “command line
commands”, although they do not principally differ from any other command.

Cd Command Moves around in the database tree by opening another folder at a relative position
from the currently open folder.
Example:
cd...∖gridB∖Load1

Cl Command Stops the redirection of the output window to either a file or to a printer. All following
messages will again be shown only in the output window.

cl/out stops redirection to a file cl/prn stops redirection to a printer

Cls Command Clears the output or input window.

cls/out clears output window

cls/inp clears input window completely
cls/inp/done clears only previously executed commands
.../y asks for confirmation

Dir Command Displays the contents of a folder.

Example:
dir Study Case

158 DIgSILENT PowerFactory 2016, User Manual

 10.9. SAVE AND RESTORE PARTS OF THE DATABASE

Ed Command Pops up the dialog of a default command, i.e. “ldf”, “shc”, etc.
Example:
ed ldf

Exit Command Queries or sets a variable.

Example:
man/set obj=Load_1.elmlod variable=plini value=0.2

Op CommandC Redirects output to either a file or a printer.

Example:
op/out f=train3.out

Pause Command Interrupts the execution of the command pipe until a next pause command is
executed.

Pr Command Prints either the contents of the output window or the currently active graphics
window.

Rd Command Opens and reads a file.

Stop Command Stops the running calculation.

Wr Command Writes to a file.

10.9 Save and Restore Parts of the Database

A selected part of the database can be written to a “DZ” Import/Export file with the button Export Data. . .
. This will bring a ’File Save’ dialog where a filename must be specified.

Alternatively, the folder or object that is to be exported can be right-clicked in the database tree, after
which the option Export. . . is selected.

The exported part of the database may be a complete project, a library, or a specific object in the
browser window. Exporting a folder (i.e a project, grid, library, etc.) will export the complete content of
that folder, inclusive subfolders, models, settings, single line graphics, etc.

It is even possible to export a complete user account. However, only the administrator is able to import
an user-account. Exporting the user-account on a regular basis is a practical way to backup your data.

It is even possible to export data from another user account, or even to export another user-account
completely. However, only the shared, visible, data will be exported.

The exported data file can be imported into the database again in any desired folder by pressing the
Import Data. . . button. This will bring a ’File Open’ dialog where the “DZ” data-file can be selected.

The “DZ”-file will be analysed and error messages will be displayed when the file is not a genuine
PowerFactory data file, or if it is corrupted. If the file format has been found to be correct, a dialog will
appear which shows the data and version of the file. The default target folder is shown also, which is the
original folder of the saved data. If this is not desired, another target folder can be selected by pressing
the Drop Down button. This button will bring a small version of the database tree. A new target folder
can be selected from this tree.

10.9.1 Notes

By exporting a folder from the database, only the information in that folder and all its subfolders will be
stored. If the exported objects use information (e.g. power system types like line or transformer types)

DIgSILENT PowerFactory 2016, User Manual 159

CHAPTER 10. DATA MANAGER

that is saved somewhere else, then that information will not be stored. Make sure that the used power
system types and all other referenced information is exported too.

When importing a file that contains objects which use data outside the import-file, a search for that data
is started.

For instance, assume a project is exported. One of the line-models uses a type from a library outside
the project. When exporting, the path and name of this type is written in the export-file, but the type
itself is not exported, as is does not reside in the exported project.

At importing, the stored path and name of the ’external’ type is used to find the type again and to
restore the link. However, if the ’external’ type is not found, then it will be created, using the stored
path and name. Of course, the created object has default data, as the original data was not exported.
Additionally, an error message is written to the output window.

Suppose that you are working with a large library, which is stored in a special user-account to make it
read-only. The library is made accessible by sharing it to all users.

When export the projects, the objects from the external library are not exported. However, a colleague
which has access to the same library may still import your projects without problems. The external
objects used in your projects will be found in the same location, and the links to these objects will be
correctly restored.

10.10 Spreadsheet Format Data Import/Export

The PowerFactory data browser in the Data Manager’s window looks and acts like a spreadsheet
program as far as creating and editing power system objects is concerned. To enable and simplify the
use of power system element data which is stored in spreadsheet programs such as the Microsoft Excel
or the Lotus 123 programs, the data browser offers ’Spreadsheet Format’ import and export facilities.

10.10.1 Export to Spreadsheet Programs (e. g. MS EXCEL)

All data visible in the data browser may be exported as it is. The export format is such that most
common spreadsheet programs can read in the data directly (space separated ASCII). Exporting data
is performed as follows.

• Select a range of data in the data browser. Such a range may contain more than one column and
more than one row.
• Right-click the selected range.
• Now you have different options:
– If you want to copy the content of the marked cells only, simply select Copy from the context-
sensitive menu.
– If you want to copy the content of the marked cells together with a description header, select
the Spread Sheet Format option. This opens a second menu which offers the choice between
writing the Spreadsheet export to a file (Write to File), or to put it on the Windows Clipboard
(Copy (with column headers)). See Figure 10.10.1.
• The exported data can now be imported into a Spreadsheet program. When the Clipboard was
used, using the Paste option of the spreadsheet program or pressing Ctrl-V will Paste the data
into the spreadsheet.
• The imported data may now be edited, or additional calculations may be made. The PowerFactory
data is imported as numbers and descriptions. The example in Figure 10.10.2 calculates a mean
value from a range of line loading percentages.

160 DIgSILENT PowerFactory 2016, User Manual

 10.10. SPREADSHEET FORMAT DATA IMPORT/EXPORT

Figure 10.10.1: Exporting a range of data

Figure 10.10.2: Imported data in a spreadsheet program

DIgSILENT PowerFactory 2016, User Manual 161

CHAPTER 10. DATA MANAGER

10.10.2 Import from Spreadsheet Programs (e. g. MS EXCEL)

There are two methods available for importing data from a spreadsheet program. The first method uses
a direct import of ’anonymous’ numerical data, i. e. of the values stored in the cells of the table. This
method is used to change parameter of existing objects by importing columns of parameter values.

The second method can be used to create new objects (or replace whole objects) by importing all the
data from a spreadsheet.

Any range of parameter values can be copied from a spreadsheet program and imported into the Data
Manager. The import is performed by overwriting existing parameter values by ’anonymous’ values.
The term ’anonymous’ expresses the fact that the imported data has no parameter description. The
size of the imported value range and the required data are tested. Importing invalid values (i.e. a power
factor of 1.56) will result in an error message.

Spreadsheet Import of Values

The import of values (anonymous variables), i. e. cells of a table, is explained by the following example.

In Figure 10.10.3, a range of active and reactive power values is copied in a spreadsheet program. In
Figure 10.10.4, this range is pasted to the corresponding fields of 6 load objects by right-clicking the
upper left most field which is to be overwritten. The result of this action is shown in Figure 10.10.5.

In contrast to the import of whole objects, the anonymous import of data does not need a parameter
description. This would complicate the import of complete objects, as the user would have to enter all
parameters in the correct order.

Figure 10.10.3: Copying a range of spreadsheet data

162 DIgSILENT PowerFactory 2016, User Manual

 10.10. SPREADSHEET FORMAT DATA IMPORT/EXPORT

Figure 10.10.4: Pasting spreadsheet data from clipboard

Figure 10.10.5: Database browser with imported data

Spreadsheet Import of Objects and Parameters

With this kind of import, it is possible to import whole objects (in contrast to the import of pure values,
which is described above). The object import uses a header line with the parameter names (which is
necessary in addition to the cells with the pure values). This header must have the following structure:

• The first header must be the class name of the listed objects.
• The following headers must state a correct parameter name.

This is shown in Figure 10.10.6.

Figure 10.10.6: Excel required format

Figure 10.10.7 shows an example of valid spreadsheet data of some line types and some 2-winding
transformer types.

DIgSILENT PowerFactory 2016, User Manual 163

CHAPTER 10. DATA MANAGER

Figure 10.10.7: Example of valid spreadsheet data

The import of the spreadsheet data into PowerFactory is performed as follows.

• Select the header line and one or more objects lines.

• Copy the selection. See Figure 10.10.8 for example.
• Right-click the folder browser in the Data Manager to which the objects are to be imported. Select
Spread Sheet Format → Import Objects from Clipboard. See Figure 10.10.9 for example.

Figure 10.10.8: Selecting object data in spreadsheet

164 DIgSILENT PowerFactory 2016, User Manual

 10.10. SPREADSHEET FORMAT DATA IMPORT/EXPORT

Figure 10.10.9: Importing objects from clipboard

The result of the object import depend on whether or not objects of the imported class and with the
imported names already exist or not in the database folder. In the example of Figure 10.10.10, none
of the imported objects existed in the database an all were created new therefore. The example shows
the database in detail mode.

Figure 10.10.10: Result of spreadsheet object import

Note: New objects are created in the PowerFactory database folder only when no object of the imported
class and with the imported name is found in that folder. If such an object is found then its data
will be overwritten by the imported data

Because new objects are only created when they do not exist already, and only the imported parameters
are overwritten when the object did exists already, the import is always a save action.

Remarks
Object Names

DIgSILENT PowerFactory 2016, User Manual 165

CHAPTER 10. DATA MANAGER

Object names may not contain any of the characters

*
?=",∖∼|

Default Data
When an imported object is created newly, the imported data is used to overwrite the correspond-
ing default data. All parameters that are not imported will keep their default value.

Units
The spreadsheet values are imported without units. No conversion from MW to kW, for example,
will be possible. All spreadsheet values therefore have to be in the same units as used by
PowerFactory.

166 DIgSILENT PowerFactory 2016, User Manual

Chapter 11

Study Cases

11.1 Introduction

The concept of study cases was introduced in Chapter 4 (PowerFactory Overview). Study cases (Int-
Case, ) define the studies to be performed on the system being modelled. They store everything
created by the user to perform calculations, allowing the easy reproduction of results even after deacti-
vation/reactivation of the project. By means of the objects stored inside them, the program recognises:

• Parts of the network model (grids and expansion stages) to be considered for calculation;
• Calculations (and their settings) to be performed on selected parts of the network;
• Study time;
• Active variations;
• Active operation scenario;
• Calculation results to be stored for reporting;
• Graphics to be displayed during the study.

A study case with a reference to at least one grid or expansion stage has to be activated in order to
enable calculations. A project that contains more than one grid, which has several expansion stages for
design alternatives, or which uses different Operation Scenarios to model the various conditions under
which the system should operate, requires multiple study cases. All of the study cases in a project are
stored inside the study cases folder ( ) in the project directory.

Note: Only one study case can be active at a given time. When activating a study case, all the grids,
Variations and Operation Scenarios that it refers to will also become active.

Without study cases, it would be necessary to manually activate the relevant grid and/or expansion
stage multiple times in order to analyse the resulting power system configuration. Similarly, it would
be necessary to define over and over again the same calculation command setup used to analyse the
behaviour of the selected network.

In addition to storing the objects that define a network study, study cases set the units used for the
output of calculation results, and allow the definition of specific options for the calculation algorithms.

The following sections describe the main objects stored inside study cases. For further information
regarding the definition and use of study cases, refer to Section 11.2 (Creating and Using Study Cases).

DIgSILENT PowerFactory 2016, User Manual 167

CHAPTER 11. STUDY CASES

11.2 Creating and Using Study Cases

When a new project is created, an empty study case is automatically created and activated. This new
study case has default settings. The user can later modify these settings using the study case dialog.

The user may define several study cases to facilitate the analysis of projects containing more than one
grid, several Expansion Stages, different Operation Scenarios or simply different calculation options. To
create a new study case:

• Open the Data Manager and go to the study cases folder. Right-click on the folder and select
New → Study Case from the context-sensitive menu. Enter the name of the new study case in
the dialog that pops up and (if desired) modify the default settings.

Only one study case can be active at any given time. To activate or deactivate a study case:

• Open the Data Manager. The active study case and the folder(s) where it is stored are highlighted.
Right-click on the active study case and choose Deactivate from the context-sensitive menu. To
activate an inactive study case place the cursor on its name, right-click and choose Activate. Study
cases may also be activated via the Project Overview Window (see Figure 11.2.1).

Figure 11.2.1: Activating a study case from the Project Overview Window

A study case can have more than one grid. Only the objects in the active grids will be considered by the
calculations. To add an existing grid to the active study case:

• Open the Data Manager and go to the Network Data folder. Right-click the desired grid to add
to the calculation and select Add to study case from the context-sensitive menu. The grid will
be activated and any relevant graphics will be opened (following a user selection). To remove an
active grid, select Remove from study case.

Variations are considered by a study case when they are activated. The Expansion Stages are applied
according to the study case time, which is set by the time trigger stored inside the study case folder.
More than one variation can be active for a given study case. However there can be only one recording
stage. For further information, refer to Chapter 16 (Network Variations and Expansion Stages). To add
(activate) a Variation to the active study case:

• Right-click on the Variation and select Activate from the context-sensitive menu. The Variation will
be activated and stages will be highlighted depending on the study time.

An Operation Scenario can be activated or deactivated via the context-sensitive menu, or by using
the option File → Activate Operation Scenario/Deactivate Operation Scenario from the main menu.
Upon activation, a completeness check is performed (i.e. a check that operational data is available

168 DIgSILENT PowerFactory 2016, User Manual

 11.2. CREATING AND USING STUDY CASES

for all components). This is reported in the PowerFactory output window. If an Operation Scenario
is active, all operational data attributes in property sheets or in the Data Manager are highlighted in
blue. This indicates that changes to these values will not modify the base component (or Variation)
but are recorded by the active Operation Scenario. Upon deactivation, previous operational data is
restored. If the Operation Scenario was modified, user confirmation is requested regarding the saving
of changes. For further information about working with Operation Scenarios, refer to Chapter 15
(Operation Scenarios).

Note: Only one study case can be activated at a time. Although network components and diagrams
can be edited without an active study case, calculations cannot be performed. Variations and
Operation Scenarios used by a study case are automatically activated upon activation of the
corresponding study case.

11.2.1 The Study Case Overview

The Study Case Overview is an enhancement of the Project Overview described in Chapter 8: Basic
Project Definition, Section 8.1.2, and simplifies the management of study cases. It provides an overview
of all existing study cases with all active Operation scenarios, Variations, Grids and Triggers. In
this representation, study cases are arranged in the columns of the chart, and their components are
visualised row-wise. The Study Case Overview can be accessed by clicking on the arrow symbol
(“Open Study Case Overview”) in the upper right corner of the Project overview window, as shown in
Figure 11.2.2 or from Window → Study Case Overview in the main menu. Upon opening the Study
Case Manager the active study case will be deactivated. This study case will be reactivated when
closing the Study Case Overview. By clicking on the arrow symbol “Close Study Case Overview” in the
upper-right corner of the Study Case Overview, it is possible to return to the Project Overview.

This overview can be used to manage the setup of individual study cases, as it allows the activation/de-
activation of:

• Operation Scenarios

• Variations
• Grids
• Triggers

simply by double-clicking on the cell entries - without the need to activate the study cases themselves.
Since the time of the active study case defines which Expansion Stage is active, it is only possible to
activate or deactivate Variations, but not Expansion Stages. Depending on the study time, the recording
Expansion Stage will be marked in bold.

Note: When folders are used to store study cases, only the study cases within the selected folder will
be shown.

DIgSILENT PowerFactory 2016, User Manual 169

CHAPTER 11. STUDY CASES

Figure 11.2.2: Study Case Overview

11.3 Summary Grid

The primary task of a study case is to activate and deactivate a calculation target, which is a combination
of grids and optionally expansion stages from the network model. The Summary Grid object holds
references to the grids which are considered in the calculation (i.e. the active grids). Grids may be added
to or removed from the currently active study case by right-clicking on them in the database tree or the
project overview window and Activate or Deactivate them. A reference to the activated/deactivated grid
is automatically generated in or deleted from the Summary Grid.

A grid cannot be activated without an active study case. With no study case active, the Activate action
from the context-sensitive menu of a grid will show a dialog, where a new study case can be created or
an existing one can be chosen in order to activate the grid.

11.4 Study Time

PowerFactory Version 14 extended the idea of a model to incorporate time. Therefore, study cases have
a study time which defines the point in time the user wishes to analyse.

The study time must be inside the Validity Period of the project, which specifies the time span for
which the project is valid (see Chapter 8: Basic Project Definition, Section 8.1.3 (Project Settings)).
PowerFactory will use the study time in conjunction with time-dependent network expansions (see
Chapter 16: Network Variations and Expansion Stages) to determine which network data is applicable
at that point in time. The study time may be changed in order to analyse a different point in time. The
Expansion Stages will be activated/deactivated in accordance with the study time.

The status bar at the bottom of the PowerFactory program window shows the currently-set study time.

170 DIgSILENT PowerFactory 2016, User Manual

 11.5. THE STUDY CASE DIALOG

The simplest way to change the study time is:

• Double-click on the Study Time shown in the status bar of PowerFactory.

• Enter the date and time or press the Date and Time buttons in order to set the study time to the
current time of the computer on which PowerFactory is being run.
• Press OK and close the window.

There are several alternative ways to edit the study time.

Alternative 1: Edit the study time like a trigger:

• Press the button Date/Time of Calculation Case in the main toolbar of PowerFactory.
• Enter the date and time or press the Date and Time buttons in order to set the study time to the
current time of the computer on which PowerFactory is being run.
• Press OK to accept the changes and close the window.

Alternative 2: Edit the study case from within the study case dialog:

• Activate the project and browse for the study case in the Data Manager.
• Right-click on the study case and select Edit from the context-sensitive menu.
• On the Basic Data page press the button with the three dots beneath the entry for the study time.
• Set the study time.
• Press OK and close the window.

11.5 The Study Case Dialog

To edit the settings of a study case, select Edit → Study Case from the main menu, or right-click the
study case in the Data Manager and select Edit from the context-sensitive menu. A dialog will appear.
On the Basic Data page, the user can define the name and an owner of the study case. The output
units of the calculated variables are defined in the Output Variables field. The grids that are linked to a
study case may be viewed by pressing the Grids/System Stages button. The study time can be edited
by pressing the button; this will open the dialog of the study case time trigger (see Section 16.4:
Study Time). Please note that the study time can also change if the recording expansion stage is set
explicitly (see Chapter 16: Network Variations and Expansion Stages).

The Calculation Options page is used to configure the basic algorithm for the study case calculations.
The following options are available:

• The Breaker reduction mode determines the internal calculation topology of the grid. In particular,
electrically equivalent areas of a detailed substation are identified and merged for an efficient
internal treatment. If the check box Calculate results for all breakers is ticked, results of reduced
elements may then be post-calculated.
• The solution of linear equation systems is an intrinsic part of most calculations in PowerFactory,
such as load flow, short-circuit or the RMS/EMT simulation. Since version 15.2, these equation
systems can either be solved by a direct factorisation method or an iterative method. The latter
method has been developed to meet the increasing demands of modern applications where
interconnected, large-scale networks must be analysed. In contrast to traditional direct methods,
the implemented iterative solver is able to solve even very large systems with controlled precision.

DIgSILENT PowerFactory 2016, User Manual 171

CHAPTER 11. STUDY CASES

• The tabs Calculation matrices and Advanced offer access to additional calculation options which
tune performance and robustness of the linear system solver.
• The button Set all calculation options to default will restore all default options on the Calcula-
tion Options tab.

Please note that alteration of default options is only recommended under the supervision of the DIgSI-
LENT support experts.

The Description page is used for user comments.

Note: To edit the study time one can alternatively press on the “Date/Time of Calculation Case” button
. This will open the study case time trigger window. In addition, the time of the simulation case
is displayed in the lower-right corner of the program window. Double-clicking on this field provides
access to the same window.

11.6 Variation Configuration

Similar to the Summary Grid, the Variation Configuration object (IntAcscheme ) contains references
to the active variations.

11.7 Operation Scenarios

A reference to the active Operation Scenario (if any) is always stored in the study case. Similar to
Variation Configurations and Summary Grids, when a study case is activated, the Operation Scenario (if
any) whose reference is contained, will be automatically activated. The reference to the active Operation
Scenario will be automatically updated by the program.

11.8 Commands

In PowerFactory a calculation (i.e load flow , short-circuit , initial conditions of a time-domain

simulation , etc.) is performed via ’Calculation Commands’, which are the objects that store the
calculation settings defined by the user. Each study case stores its own calculation commands, holding
the most recent settings. This ensures consistency between results and calculation commands and
enables the user to easily reproduce the same results at a later date. When a calculation is performed
in a study case for the first time, a calculation command is automatically created inside the active study
case. Different calculation commands of the same class (i.e different load flow calculation commands:
objects of the class ComLdf or different short-circuit calculation commands: objects of the class
ComShc ) can be stored in the same study case. This allows the user to repeat any calculation with
identical settings (such as fault location, type, fault impedance, etc.) as last performed in the study case.
The calculations are only performed on active grids (expansion stages).

Figure 11.8.1 shows a study case, ’Study 1’ which contains two load flow calculation commands ( ,
’Ldf 1’ and ’Ldf 2’), one command for an OPF calculation , one command for the calculation of
initial conditions , and one transient simulation . The dialog of each of calculation command in
PowerFactory is described in the chapter corresponding to that calculation function.

172 DIgSILENT PowerFactory 2016, User Manual

 11.9. EVENTS

Figure 11.8.1: Calculation commands in a study case

Actions such as generating a report of the actual calculation results or the state of the defined network
components are carried out via commands (in this case ComSh and ComDocu, respectively). For
information about reporting commands refer to Chapter 18 (Reporting and Visualising Results).

Note: As with any other object, calculation commands can be copied, pasted, renamed and edited.

11.9 Events

Simulation Event objects are used to define simulation events. For time-domain simulations, events
are stored within the Study Case → Simulation Events/Fault folder (see Chapter 28: Stability and EMT
Simulations, Section 28.6 for a general description). For short-circuit studies, they are stored in the
Study Case → Short Circuits folder. For other steady-state calculations that utilise Simulation Events,
they are stored within the Operational Library → Faults folder. PowerFactory offers several kinds of
events:

• Dispatch Event (EvtGen)

• External Measurement Event (EvtExtmea)
• Intercircuit Fault Events (EvtShcll)
• Events of Loads (EvtLod)
• Message Event (EvtMessage)
• Outage of Element (EvtOutage)
• Parameter Events (EvtParam)
• Save Results (EvtTrigger )
• Short-Circuit Events (EvtShc)
• Stop Events (EvtStop)
• Switch Events (EvtSwitch)
• Synchronous Machine Event (EvtSym)
• Tap Event (EvtTap)

DIgSILENT PowerFactory 2016, User Manual 173

CHAPTER 11. STUDY CASES

11.9.1 Dispatch Event

The user specifies the point in time in the simulation for the event to occur, and a generation element
(ElmSym, ElmXnet or ElmGenstat). The incremental change of the generator can then be altered using
the dispatch event.

11.9.2 External Measurement Event

External measurement events can be used to set and reset values and statuses of external measure-
ments.

11.9.3 Inter-Circuit Fault Events

This type of event is similar to the short-circuit event described in Section 11.9.9 (Short-Circuit Events
(EvtShc)). Two different elements and their respective phases are chosen, between which the fault
occurs. As for the short-circuit event, four different elements can be chosen:

• Busbar (StaBar )
• Terminal (ElmTerm)
• Overhead line or cable (ElmLne)

11.9.4 Events of Loads

The user specifies the point in time in the simulation for the event to occur, and a load or set of load
element(s) (ElmLod, ElmLodlv, ElmLodmv or ElmLodlvp). Optionally a set of loads SetSelect can be
also selected. The value of the load (s) can then be altered using the load event. The power of the
selected load(s) can be changed as follows:

• Step Changes the current value of the power (positive or negative) by the given value (in % of the
nominal power of the load) at the time of the event.
• Ramp Changes the current value of the power by the given value (in % of the nominal power of
the load), over the time specified by the Ramp Duration (in seconds). The load ramping starts at
the time of the event.

11.9.5 Message Event

A message will be printed to the output window at the specified time in the simulation.

11.9.6 Outage of Element

The Outage of Element event can be used to take an element out of service at a specified point in
time. It is intended for use in steady-state calculations e.g. short-circuit calculations and reliability
assessment.

It may also be used to take elements out of service in time-domain simulations, however it is not possible
to bring an outaged element back into service using this event during a transient simulation. This is only
possible in steady-state calculations. The following message will be displayed if the user attempts to
bring a previously-outaged element back into service using Outage of Element:

174 DIgSILENT PowerFactory 2016, User Manual

 11.9. EVENTS

DIgSI/err (t=000:000 ms) - Outage Event in Simulation

not available.
Use Switch-Event instead!

11.9.7 Parameter Events

With this type of event, an input parameter of any element or DSL model can be set or changed. First,
a time specifying when the event will occur is specified. An element or set of elements SetSelect must
then be specified/selected using the down-arrow button .Choose Select. . . from the context-sensitive
menu, and insert the name and the new value of the element parameter. In case a selection is used all
elements within the selection have to share the same element parameter.

11.9.8 Save Results

This event is only used for PowerFactory Monitor applications. It cannot be used during time-domain
simulations.

11.9.9 Short-Circuit Events

This event applies a short-circuit on a busbar, terminal or specified point on a line. The fault type (three-
phase, two-phase or single-phase fault) can be specified, as can the fault resistance and reactance and
the phases which are affected. The duration of the fault cannot be defined. Instead, to clear the fault,
another short-circuit event has to be defined, which will clear the fault at the same location.

11.9.10 Stop Events

Stops the simulation at the specified time within the simulation time frame.

11.9.11 Switch Events

Switch events are only used in transient simulations. To create a new switch event, press the icon
on the main menu (if this icon is available), which will open a browser containing all defined simulation
events. Click on the icon in the browser, which will show the Element Selection dialog (IntNewobj as
shown in Figure 11.9.1). This dialog can be used to create a new switching event.

DIgSILENT PowerFactory 2016, User Manual 175

CHAPTER 11. STUDY CASES

Figure 11.9.1: Creation of a new switch event (IntNewobj)

After pressing OK, the reference to the switch (labelled Breaker or Element) must be manually set. Any
switch in the power system may be selected, thus enabling the switching of lines, generators, motors,
loads, etc. The user is free to select the switches/breakers for all phases or only those for one or two
phases.

It should be noted that more than one switching event must be created if, for instance, a line has to be
opened at both ends. These switch events should then have the same execution times.

11.9.12 Synchronous Machine Event

The Synchronous Machine Event is used to change the mechanical torque of a synchronous machine
(ElmSym) in a simple manner. The user specifies the point in time in the simulation for the event to
occur, and an active synchronous machine. The user can then define the additional mechanical torque
supplied to the generator. The torque can be positive or negative and is entered in per-unit values.

11.9.13 Tap Event

The user specifies the point in time in the simulation for the tap event to occur, and a shunt or transformer
element (ElmShnt, ElmTr2, etc). The Tap Action can then be specified.

11.10 Simulation Scan

For details of Simulation Scan modules, refer to Chapter 28 Section 28.5.

11.11 Results Objects

The results object (ElmRes ) is used to store tables with the results obtained after the execution of
a command in PowerFactory. The typical use of a results object is to write specific variables during a
transient simulation, or during a data acquisition measurement. The results obtained can later be used
to generate plots, or in DPL scripts.

176 DIgSILENT PowerFactory 2016, User Manual

 11.12. VARIABLE SETS

The results dialog has the following fields:

Name The name of the result object.

Database ID The database ID and the date; date of last modification.
Default for Default use (i.e. for Harmonics; for OPF; etc).
Info Information regarding the stored data, i.e. the time interval, step sizes, number of variables, etc.
Trigger-Times Trigger times (in case of a triggered default use).

The information pertaining to the stored data shows the following:

• Time interval;
• Average time step;
• Number of points in time;
• Number of variables;
• Size of the database result file.

The Clear Data button will clear all result data (only available if calculation results are stored).

Note: Clearing the data will delete the result file and will reset the database ID. This will destroy all
calculated or measured data in the result file. It is not possible to restore the data.

The contents of a result object (that is, the variables whose results are stored) is determined by sets
of selected variables called Monitor Variable Sets (IntMon ). Each Monitor Variable Set stores the
results of the selected variables for one network component. These monitor objects can be edited by
pressing the Variables button. A list of monitor sets currently in use by the result object will then be
displayed.

Note: Selecting a set of result variables through the use of Monitor Variable Sets is necessary because
otherwise all available variables would have to be stored, which would be impractical.

When the Export button is pressed, all events that happened during the simulation can be exported in
different formats. For information about exporting results, refer to Chapter 18: Reporting and Visualising
Results, Section 18.2.4 (Result Objects).

11.12 Variable Sets

The result object combines one or more Monitor Variable Sets (IntMon ), allowing a very flexible and
highly transparent result definition. In fact, by using Monitor Variable Sets, just about every parameter
used in the PowerFactory program can be made available as a calculation result, including with a
description and a unit.

The variables selected via the Monitor Variable Sets dialog in the result object are available to the
subplot objects in virtual instrument panels. In these plots, one or more result objects can be selected.
From the selected result object/s, a power system element and one of its variables can then be chosen
(if that element and that variable were previously selected in one of the IntMon objects). The subplot
will then show the plot of that variable.

DIgSILENT PowerFactory 2016, User Manual 177

CHAPTER 11. STUDY CASES

Variable sets always have a reference to a network component, whose selected variables are going
to be recorded (Figure 11.12.1 red circle, in this case a transformer called EBT1). To facilitate the
selection of the variables, monitor variable sets are organised according to PowerFactory calculation
functions and by the type of data. For example, if the results of a harmonics calculation are to be
recorded, the user should go to the Harmonics/Power Quality page (Figure 11.12.1, green circle). If
the voltage or the power of the element referred to is to be stored, the selected Variable Set should be
Currents, Voltages and Powers (Figure 11.12.1 blue circle).

Figure 11.12.1: Monitor Variable Set dialog

For further information on the definition of Monitor Variable Sets refer to Chapter 18: Reporting and
Visualising Results, Section 18.4 (Variable Sets).

11.13 Triggers

As described in Chapter 17 (Parameter Characteristics, Load States, and Tariffs), parameter charac-
teristics are used to define parameters as ranges of values instead of fixed amounts. The parameter
characteristics are set over user defined scales. The current value of the parameter is at the end
determined by a trigger object (SetTrigger, ), which sets a current value on the corresponding
scale. For example if the value of a certain parameter depends on the temperature, a characteristic
over a temperature scale is set. The current value of the temperature is defined by the trigger. The
current value of the temperature determines the current value of the parameter, according to the defined
characteristic.

Once a parameter characteristic and its corresponding scale are set, a trigger pointing to the scale is
automatically created in the active study case. The user can access the trigger and change its value as
required.

PowerFactory offers different types of characteristics and scales, and each scale points to a trigger from
the active study case. By default, scales are stored in the Scales folder in the Equipment Type Library.
Information regarding the use and definition of characteristics, scales and triggers is given in Chapter 17
(Parameter Characteristics, Load States, and Tariffs).

178 DIgSILENT PowerFactory 2016, User Manual

 11.14. GRAPHIC BOARD

11.14 Graphic Board

The study case folder contains a folder called the Graphics Board folder (SetDesktop, ). This folder
contains references to the graphics which are to be displayed. This folder, similar to the Summary Grid
folder, is automatically created and maintained and should generally not be edited by the user.

The references in the graphics board folder are created when the user adds a grid to a study case.
PowerFactory will ask the user which graphics pertaining to the grid should be displayed. At any time,
the user may display other graphics in the grid by right-clicking the grid and selecting Show Graphic.
Graphics may be removed by right-clicking the tab at the bottom of the page and selecting Remove
Page(s).

The study case and graphics board folder also contain references to any other graphics that were
created when the study case was active.

DIgSILENT PowerFactory 2016, User Manual 179

CHAPTER 11. STUDY CASES

180 DIgSILENT PowerFactory 2016, User Manual

Chapter 12

Network Model Manager

12.1 Introduction

The Network Model Manager is a browser for all calculation relevant objects. The objective of this
chapter is to provide detailed information about this Management tool. Before starting, users should
ensure that they are familiar with Chapter 4 (PowerFactory Overview).

12.2 Using the Network Model Manager

The Network Model Manager contains all relevant objects for the calculation. It can be accessed by
clicking the button Open Network Model Manager. . . in the main icon bar.

On the left hand side of the Network Model Manager window the classes of all calculation relevant
objects are displayed with their names and their symbols. To obtain a better overview, they are sorted
into groups, like e.g. Substations/Terminals/Switches or Network Components. Undesired groups can
be collapsed to hide their contents. If one of the classes is selected, all calculation relevant objects
will be listed in the table on the right side of the browser window. Thereby, the Detail Mode is
automatically activated. This provides the possibility to easily edit all parameters of an object, without
opening the dialog of this element.
Figure 12.2.1 shows the Network Model Manager window, where some of the groups are collapsed and
the class *.ElmTerm is selected.

DIgSILENT PowerFactory 2016, User Manual 181

CHAPTER 12. NETWORK MODEL MANAGER

Figure 12.2.1: The Network Model Manager window

Figure 12.2.2: Icon bar of the Network Model Manager

Following, the functions of the buttons of the icon bar of the Network Model Manager shown in Fig-
ure 12.2.2 are described:

1. The Refresh button can be used to update the Network Model Manager. For example this is
necessary, when objects are deleted in the Data Manager or the Single line diagram while the
Network Model Manager is still opened. In this case the objects in the Network Model Manager
are still displayed until the refresh button is pressed.

2. A mouse click on the Edit Object button will open the dialog window of the object selected in
the table on the right. A selected object is indicated by a marked row and an arrowhead next to
the object symbol. Another possibility to open the edit dialog of an object is to double click on the
corresponding symbol of the desired object.
3. One or more objects can be deleted by marking the objects to be removed and then pushing the
Delete Object button. A query window will appear, which requests to confirm the deletion.

4. The button Copy (with column headers) copies the data of a selection with the corresponding

182 DIgSILENT PowerFactory 2016, User Manual

 12.2. USING THE NETWORK MODEL MANAGER

column header(s) into the Windows Clipboard. The content can then be pasted into e.g. a
spreadsheet program.

5. The Detail Mode can be activated and deactivated. If it is activated (button is pressed), the
table on the right will display all the object parameters of the class (e.g. Busbars, as shown in
Figure 12.2.1). With the tabs on the button of the table, all pages, which are also available in the
dialog window of the object, can be easily accessed and the parameters can be changed via the
table.
If the Detail Mode is deactivated, a table will appear, in which columns with predefined parameters
are shown. This table and the Flexible Data page (available in Detail Mode) can be extended, by
pressing the Variable Selection button.

6. By clicking on Variable Selection , variables/parameters can be chosen, which shall be dis-

played in the table. For more information about how to handle the selection dialog refer to
Section 18.4 (Variable Selection).
7. Objects, which are Out-of-Service or non-relevant for the calculation, can be hidden by clicking
the button Hide Out-of-Service-Objects and Objects non-relevant for Calculation .

8. The Network Model Manager provides the following filter functions, which are available when at
least one column is filtered. How to filter columns is described in section 10.5 (Auto-Filter functions
in Data Manager and browser windows).

• If one or more columns are filtered, the button Edit Filter will become accessible. After
the button has been pressed, an edit dialog will open, in which a filter name can be entered.
Furthermore the filters for each parameter can be modified by double clicking the relevant
cell in the Filter column.
• The Current Working Filter is temporary. That means, if the Network Model Manager window
is closed, the applied filters will all be discarded. However, one or more column filters can be
consolidated to one common filter, which can then be saved under any name to reuse it, by
clicking the Save Filter button. A window will pop-up, in which the user can insert a name
for that filter.
• Undesired filters can also be deleted from the list of saved filters again, by selecting a Filter
from the drop-down list in the icon bar and clicking on the Delete Filter button.

DIgSILENT PowerFactory 2016, User Manual 183

CHAPTER 12. NETWORK MODEL MANAGER

184 DIgSILENT PowerFactory 2016, User Manual

Chapter 13

Project Library

13.1 Introduction

The project library stores the following categories of data:

• Equipment Types (Section 13.2: Equipment Type Library)

• Operational Data (Section 13.3: Operational Library)
• Scripts (See Chapter 21: Scripting)
• Table Reports (See section Table Report Methods of the DPL Reference)
• Templates (Section 13.4: Templates Library).
• User Defined Models (See Section 28.12: User Defined (DSL) Models)

This chapter is describes the Equipment Type Library, Operational Library, and Templates library. Note
that in addition to the project Library, the global Library includes a range of pre-defined types, models,
templates, and scripts (refer to Chapter 4: PowerFactory Overview, Section 4.6: Data Arrangement for
details).

13.2 Equipment Type Library

The Equipment Type Library is used to store and organise Type data for each class of network com-
ponent. Once a new project is created, an Equipment Type Library is automatically set by the program
within the Library folder. It also includes a subfolder for storing Scales.

To create or edit a folder in the Equipment Type Library :

1. On the Equipment Type Library folder in the left pane of the Data Manager right-click and select
New → Project Folder from the context sensitive menu (or to edit an existing folder, right-click the
folder and select Edit). The project folder edit dialog is displayed.
2. In the Name field, enter the name of the new folder.
3. In the Folder Type field, select Generic.
4. In the Class Filter field, write the name of the type class(es) to be allowed in the folder (case
sensitive). If more than one class is to be allowed, write the class names separated by commas.
An asterisk character (* ) can be used to allow all classes.

DIgSILENT PowerFactory 2016, User Manual 185

CHAPTER 13. PROJECT LIBRARY

5. In the Icon field, select Library.

To create new type objects in these folders select the New Object icon and select the appropriate
type class. Alternatively, types can be copied from other projects or the global library. If the type class
does not match the folder filter, an error message is displayed.

Within the Equipment Type Library, the Scale folder is used to store the Scales used by the parameter
characteristics. Refer to Chapter 17 (Parameter Characteristics, Load States, and Tariffs) for details.

Note: By default new block definitions (used by dynamic models) created from block diagrams are
also stored in the Equipment Types Library. Chapter 28 (Stability and EMT Simulations) provides
details related to dynamic modelling and block definitions.

Figure 13.2.1 shows the equipment library of a project containing generator, load, and transformer
types, sorted using library sub-folders.

Figure 13.2.1: The Equipment Library

Unlike the “Global Library”, which is accessible to all users, the local Equipment Type Library is used
to define types that are to be used in the specific project. It can only be used by the project owner, and
users with which the project is shared.

There are three options available for defining Type data for network components, as illustrated in
(Figure 13.2.2):

1. Select Global Type from the Global Library. The Data Manager is launched in the “Global Library”.
2. Select Project Type. The Data Manager is launched in the local Equipment Type Library.
3. New Project Type. A new type will be defined and automatically stored in the local Equipment
Type Library.

Note that Global Types and Project Types buttons can be used to quickly switch between the global
and local libraries (Figure 13.2.2).

186 DIgSILENT PowerFactory 2016, User Manual

 13.3. OPERATIONAL LIBRARY

Figure 13.2.2: Selecting a Synchronous Machine Type

13.3 Operational Library

The Operational Library is used to store and organise operational data for application to a number of
elements, without the need to duplicate operational information.

To illustrate, consider an example where there are two generators, “G1” and “G2”. The units have slightly
different Type data, and thus unique Type models, “G 190M-18kV Ver-1” and “G 190M-18kV Ver-2”. The
Capability Curves for these units are identical, and so the user wishes to create only a single instance
of the capability curve. By defining a Capability Curve in the Operational Library, a single Capability
Curve can be linked to both generators.

Similarly, various circuit breakers may refer to the same short-circuit current ratings. A Circuit Breaker
Rating object can be defined in the Operational Library and linked to relevant circuit breakers

This section describes the definition and application of operational data objects.

13.3.1 Circuit Breaker Ratings

Circuit Breaker Ratings objects (IntCbrating) contain information that define the rated short-circuit
currents of 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.

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.

DIgSILENT PowerFactory 2016, User Manual 187

CHAPTER 13. PROJECT LIBRARY

• Three phase RMS break short circuit current.

• Single phase RMS break short circuit current.

• DC time constant.

To create a new circuit breaker rating in the operational library:

• In the Data Manager open the CB Ratings folder.

• Click on the New Object icon .

• In the Element Selection dialog select Circuit Breaker Rating (IntCbrating) and press Ok.
• The new circuit breaker rating dialog will then be displayed. Set the corresponding parameters
and press Ok.

To assign a circuit breaker rating to a circuit breaker (ElmCoup object) from the network model:

1. Go to the Complete Short-Circuit page of the element’s dialog.

2. In the Ratings field click on the button to select the desired rating from the CB Ratings folder.

The parameters defined in the circuit breaker ratings can be made to be time-dependant by means of
variations and expansion stages stored inside the CB Ratings folder.

For information regarding short-circuit calculations, refer to Chapter 24 (Short-Circuit Analysis). For
further information about variations and expansion stages, refer to Chapter 16(Network Variations and
Expansion Stages).

Note: Variations in the CB Ratings folder act ’locally’, they will only affect the circuit breaker ratings
stored within the folder. Similarly, the variations of the Network Model will only affect the network
components from the grids.

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. Ratings can also be entered in the StaSwitch Type object.

Example Time-Dependent Circuit Breaker Rating

Consider an example where a substation circuit breaker “CB” operates with different ratings depending
on the time of the year. From 1st January to 1st June it operates according to the ratings defined in a
set of parameters called “CBR1”. From 1st June to 31st December it operates with the ratings defined
in a set of parameters called “CBR2”.

This operational procedure can be modelled by defining a circuit breaker rating “CBR” in the CB Ratings
folder, and a variation “CB_Sem_Ratings” containing two expansion stages. The first expansion stage
should activate on the 1st January and the second on the 1st June. The first task is the definition of the
time-dependant circuit breaker rating “CBR”. To set the parameters of “CBR” for the first period:

1. Set a study time before the 1st June to activate the first expansion stage (the Variation “CB_Sem_-
Ratings” must be active).
2. Edit the parameters of “CBR” (previously defined) according to the values defined in “CBR1”. The
new parameters will be stored in the active expansion stage.

188 DIgSILENT PowerFactory 2016, User Manual

 13.3. OPERATIONAL LIBRARY

3. To set the parameters of “CBR” for the second period:

4. Set a study time after the 1st June to activate the second expansion stage;

5. Edit “CBR” according to the values of “CBR2”. The new parameters will be stored in the active
expansion stage.

Once the ratings for the two expansion stages have been set, and the circuit breaker rating “CBR” has
been assigned to the circuit breaker “CB”, the study time can be changed from one period to the other
to apply the relevant ratings for “CB” (note that the variation must be active).

13.3.2 Demand Transfers

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 a Demand Transfer (objects
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).

To create a new load demand transfer:

1. In the Data Manager, open the Demand Transfer folder.

2. Click on the New Object icon .

3. In the Element Selection dialog select Planned Outage (IntOutage) and press Ok.
4. Set the validity time, the source and target loads/feeders and the power transfer.

Note: If there is a demand transfer, which transfers load between two loads (ElmLod) belonging to
different feeders (ElmFeeder ), then the same MW and Mvar value is transferred from one feeder
to the other.

A demand transfer is only possible if an active operation scenario (to record the changes) is available.
The Apply all button will automatically apply all transfers that are stored in the current folder and which
fit into the current study time. Before execution, the user is asked if the current network state should
be saved in a new operation scenario. The same demand transfers can be applied as many times as
desired during the validity period.

If a non-zero power transfer has been executed and the source’s power is less than zero, a warning is
printed to the output window indicating that the power limit has been exceeded. The applied transfers
can be reverted by using the Reset all button.

When the current operation scenario is deactivated, all load transfers executed while the operation
scenario was active will be reverted.

For information about operation scenarios refer to Chapter 15 (Operation Scenarios).

13.3.3 Fault Cases and Fault Groups

This section discusses the data structure of the Faults folder, and the objects contained within it. The
functionality of Event objects is described in Section 28.6: Events (IntEvt).

The Faults folder stores two types of subfolders:

DIgSILENT PowerFactory 2016, User Manual 189

CHAPTER 13. PROJECT LIBRARY

1. Fault Cases folders which in turn store objects that represent Simulation Events . Simulation
Events may contain a number of individual Events (Evt* ), e.g. short-circuits events, switching
events.

2. Fault Groups folders store Fault Groups (IntFaultgrp) objects, which in-turn reference fault
Cases (Simulation Events or individual Events).

The uppermost window in Figure 13.3.1 show an example project Faults folder. Two Fault Cases
subfolders (“Cases North” and “Cases South”), and a Fault Groups subfolder Grouping Faults have
been defined.

The centre window in Figure 13.3.1 shows the content of “Cases South”, which stores three fault cases,
“Bus 1”, “G1”, and “T1”. In the lower window of Figure 13.3.1, a Fault Group named Fault Group has
been defined inside the Grouping Faults folder, and contains a reference to the fault case “Line2-Line5”
(which has previously been defined in the folder “Cases North”).

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 a time-domain simulation. In this case the execution time sequence
of the events must be defined. In the case of fault representations in the Operational Library by
means of fault cases, only short-circuit and switching events are relevant.

190 DIgSILENT PowerFactory 2016, User Manual

 13.3. OPERATIONAL LIBRARY

Figure 13.3.1: The Faults Folder

Note that the calculation commands provided by the reliability assessment function of PowerFactory use
Contingencies objects (ComContingency and ComOutage) to simulate the outage (and subsequent
recovery) of one or more system elements. To avoid duplication of data, these objects can refer to
previously defined Simulation Events (IntEvt). For information regarding the functionality of fault cases
and fault groups in contingency analysis tools refer to Chapter 31 (Contingency Analysis). For the
use of fault cases to create outages for the contingency analysis tools refer to Chapter 32 (Reliability
Assessment).

The following sections provide a details of how to define Fault Cases and Fault Groups.

DIgSILENT PowerFactory 2016, User Manual 191

CHAPTER 13. PROJECT LIBRARY

Fault Cases

A fault case can represent a fault in more than one component, with more than one event defined.
For example, the fault case “Line 2-Line 5” shown in Figure 13.3.1 represents a short-circuit fault in
transmission lines Line2 and Line5, i.e. the fault case “Line 2-Line 5” consists of short-circuit events for
both 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 refer to Chapter 32 (Reliability Assessment).
2. 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 refer to Chapter 32 (Reliability Assessment).

To create new Fault Cases or new Fault Groups folders, open the Faults project folder from the Oper-
ational Library and use the New Object icon (select Fault Cases(IntFltcases) or Fault Groups (IntFlt-
groups) respectively).

To create new fault case (object of class IntEvt):

1. Multi-select the target components on a single line diagram.

2. Right-click and select Define → Fault Cases from the context-sensitive menu.
3. Select from the following options:
• Single Fault Case: This creates a single simultaneous fault case including all selected
elements. A dialog box containing the created fault case is opened to allow the user to
specify a name for the fault case. Press Ok to close the dialog and saves the new fault case.
• Multi fault Cases, n-1: This creates an n-1 fault case for each selected component. There-
fore the number of fault cases created is equal to the number of components selected.
This menu entry is only active if more than one component is selected. The fault case is
automatically created in the database after selection.
• Multi fault Cases, n-2: This creates an n-2 fault case for each unique pair among the
selected components. Therefore the number of fault cases is (𝑏 · (𝑏 − 1)/2) where ”b” is
equal to the number of selected components. This menu entry is only active if more than one
component is selected. If only one component is selected, then no fault case will be created.
The fault case is automatically created in the database after selection.
• Mutually Coupled Lines/Cables, n-k : This creates fault cases considering the simultane-
ous outage of each coupled line in the selection.

The fault cases created will consist of short-circuit events applied to the selected components. All
breakers (except for circuit breakers, which are used to model a circuit breaker failure) will be ignored.

• If only breakers are included in the selection, an error message will be issued.
• If a simple switch (not a circuit breaker) is included in the selection, a warning message will be
issued that this switch will be ignored.
• If a circuit breaker is contained in the selection, then an Info message will be issued, that the CB
will be used for modelling a CB failure and will not be handled as a fault location.

Note: In the case that a branch is selected, the short-circuit event is generated for a (non-switch device
with more than one connection) component of the branch. The component used in the event
is: “Connection 1” if suitable, otherwise “Connection 2” if suitable, otherwise a suitable random
component of the branch (line, transformer . . . ).

192 DIgSILENT PowerFactory 2016, User Manual

 13.3. OPERATIONAL LIBRARY

Fault Groups

New Fault Groups are created in the Data Manager as follows:

1. Open the target Fault Groups folder and select the New Object icon .
2. In the edit dialog, specify the name of the Fault Group, and Add Cases (IntEvt) to the Fault Group.

13.3.4 Capability Curves (Mvar Limit Curves) for Generators

Reactive Power operating limits can be specified in PowerFactory through definition of Capability Curves
(IntQlim). They are stored in Operational Library, within the Mvar Limit Curves folder . Syn-
chronous generators (ElmSym) and static generators (ElmGenstat) defined in the Network Model can
use a pointer to a Capability Curve object from the Load Flow page of their edit dialog. When executing
a Load Flow (with Consider Reactive Power Limits selected on the Basic Options page) generator
Reactive Power dispatch will be limited to within the extends of the defined capability curve. For
information about the dispatch of synchronous generators, refer to the synchronous machine technical
reference in the appendix B (Synchronous Machine (ElmSym)). For information about Load Flow
calculations and reactive power limits, refer to Chapter 23 (Load Flow Analysis).

Note: If ’Consider Active Power Limits’ is selected on the Active Power Control page of the Load Flow
command, Active power is limited to the lesser of the Max. Operational Limit and the Max. Active
Power Rating specified on the Synchronous Machine Load Flow page.

Defining Capability Curves

To define a new generator Capability Curve:

1. Open the folder Mvar Limit Curves from the Operational Library.

2. Click on the New Object icon and select Capability Curve. The new capability curve dialog will
be displayed.
3. Enter data points to define the generation limits, and Append Rows to add the required number of
rows to the table.

4. To apply a Capability Curve to a generator:

• Locate the Reactive Power Limit section on the Load Flow page of the synchronous ma-
chine’s or static generator’s dialog.
• Press next to Capability Curve.
• Choose Select and then select the required curve in the Mvar Limit Curves folder of the
Operational Library (the required curve can also be created at this step by selecting the New
Object icon .
5. Select a capability curve and press OK.

Capability curves are included in operation scenario subsets; meaning that if a capability curve is
selected/reset from a generator when an operation scenario is active, the change will be stored in
the operation scenario. Once the operation scenario is deactivated, the assignment/reset of the curve
is reverted. For information on working with operation scenarios, refer to Chapter 15 (Operation Sce-
narios).

To enter a capability curve for information purposes only (i.e. a capability curve which is not to be
considered by the calculation), enter it on the Advanced tab of the Load Flow page. Then select User

DIgSILENT PowerFactory 2016, User Manual 193

CHAPTER 13. PROJECT LIBRARY

defined Capability Curve and enter the curve as a series of points in the table. Right-click on the rows
to append, delete or insert new rows.

Defining a Variation of a Capability Curve

Similar to circuit breaker ratings (see Section 13.3.1 (Circuit Breaker Ratings), Capability Curves can
become time-dependant by means of variations and expansion stages stored inside the Mvar Limit
Curves folder.

To create a time-dependent variation for a Capability Curve, navigate to theMvar Limit Curves folder in
the left pane of a Data Manager window. Right-click on the folder and select New → Variation. Name
the variation, press OK, name the Expansion Stage, and press OK. Changes to Capability Curves are
recorded in the active expansion stage.

To activate a variation of a Capability Curve, open the Data Manager. Right-click the Variation object
in the Mvar Limit Curves folder and select Activate.

For general information about variations and expansion stages refer to Chapter 16(Network Variations
and Expansion Stages).

13.3.5 Planned Outages

A Planned Outage is an object used to check and/or apply an Outage of Element or Generator Derating
over a specified time period. Planned Outages are stored within the Operational Library in the Outages
folder.

• For the Outage of Element type, PowerFactory automatically isolates the referenced components.
The switches connecting the target elements with the other network components are open and the
terminals connected to the elements are earthed (if the Earthed option in the terminal (ElmTerm)
dialog is checked). Note that the target element can only be earthed if it is directly connected
(without switches in the cubicle) to terminals, which are then connected through switches to the
network terminals.
• For a Generator Derating, a reference to the generator which is to be derated and the magnitude
of the MW reductions is specified. For the Generator Derating, the maximum active power that
can be dispatched (defined on the Load Flow page of the generator element dialog, in the section
Operational Limits) is recalculated as the difference between the maximum active power (section
Active Power: Ratings) and the MW reductions.

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.

Defining Outages and Deratings

To create a new Element Outage or Generator Derating:

1. In the Data Manager, open the Outages folder.

2. Click on the New Object icon , select Planned Outage and press Ok.
3. The Planned Outage dialog will be displayed. In the Outage Type frame of the dialog, the options
Outage of an Element and Generator Derating will be enabled. Set the desired Outage Type,
Start Time and End Time.
4. The definition of a Planned Outage requires reference(s) to relevant network components. To
create a reference:

194 DIgSILENT PowerFactory 2016, User Manual

 13.3. OPERATIONAL LIBRARY

• Press the Contents button of the outage object.

• In the data browser that is displayed, create a reference to the target element by selecting
the New Object icon (IntRef ).
• Press the button in the Reference field to select the target element.
• Press Ok to add the reference.
5. (Generator Derating only) Specify the MW Reduction (see previous section for details) for the
generator derating.

6. To apply the Planned Outage, press the Apply button (the Apply button is only available if the
study time lies within the outage period, and an Operation Scenario is active).

Applied outages and generator deratings can be reset using the Reset button.

Checking Outages and Deratings

The Check All button in the Planned Outage dialog is used to verify if the actions defined for the
target element(s) have been performed (right-click a Planned Outage and select Check to perform an
individual check). Only the outages within a valid period are considered. Outages marked as Out of
Service are not regarded (even if the study time lies within the outage period).

For an Outage of Element, the energising state is always determined by a connectivity analysis. Any
component that is connected to an External Grid or a reference Generator is considered to be energised.
All other components are considered to be deenergised (if circuit breakers are open). A deenergised
component is earthed if a topological connection to a grounding switch or an earthed terminal exists
(terminal with the Earthed option checked).

Note: If the outaged element is a branch element (ElmBranch), all contained elements are checked.
If any of these elements is not correctly outaged, the whole branch is reported as not correctly
outaged.

The fulfilment of programmed outages can also be checked via the use of the colour representation
function available within the single line graphic by setting the Colouring option to Outage Check from
the colour representation dialog . The following states are coloured, according to user preferences:

• Components that are energised, but should be outaged.

• Components that are deenergised and not earthed, but should be outaged.
• Components that are deenergised and earthed, but should NOT be outaged.
• Components that are deenergised, not earthed and should be outaged.

• Generators that are not derated, but should be outaged.

• Generators that are derated, but should NOT be outaged.

13.3.6 Running Arrangements

Running Arrangement objects store operational data (switch status) for a single substation. As
shown in Figure 13.3.2, a Running Arrangement uses a reference to the substation object (ElmSubstat)
whose switch statuses are stored. A Start Time and End Time is used to specify the validity period of
the Running Arrangement. Running arrangements are stored in the Running Arrangements folder in
the Operational Library .

DIgSILENT PowerFactory 2016, User Manual 195

CHAPTER 13. PROJECT LIBRARY

Figure 13.3.2: RA object dialog

Different configurations of the same substation can be defined by storing the corresponding switch
statuses in Running Arrangements. Different Running Arrangements can then be easily selected during
a study. If a running arrangement is selected for a substation, the status of the substation 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, switch status
will be reverted to the status prior to application of the Running Arrangement, and write-access will be
re-enabled. Running arrangements are defined and selected in the substation object dialog Basic Data
page.

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.

Further details of how to create, select, apply, and assign Running Arrangements are provided in the
following sections.

Creating a Running Arrangement

To store the current status of the switches in a substation, a Running Arrangement object must be
created. To create and save a new Running Arrangement (RA):

1. Click on an empty place in the substation graphic, and from the context-sensitive menu choose
Edit Substation. Open the substation dialog.
2. Click Save as (see Figure 13.3.3) to store the switch settings of the substation as a new RA. This
button is only available if there is currently no RA selection active.
3. In the new RA dialog is displayed, specify a name and time period, and press Ok. The new RA is
automatically stored in the Running Arrangements folder in the Operational Library.

An Overwrite button is available in the substation dialog (if no RA is selected), to store current switch
statuses to an existing RA.

196 DIgSILENT PowerFactory 2016, User Manual

 13.3. OPERATIONAL LIBRARY

Figure 13.3.3: Running Arrangement in a Substation dialog

Selecting a Running Arrangement

A Running Arrangement (RA) can be selected in the Basic Data page of a substation dialog (see
Figure 13.3.3):

1. Open the substation dialog.

2. In the Running Arrangement frame of the Substation dialog, select from a list of previously
defined RA’s.
3. Select the desired RA. This selection is immediately reflected in the substation graphic.

While an RA is selected, the switch statuses of a substation are determined by this RA and cannot be
changed by the user (i.e. they are read-only).

If there is no setting for a switch in an RA (i.e. the RA is incomplete), such a switch will remain
unchanged but its status is also set to read-only.

Furthermore, there is a button Select by Study Time (also available via the context-sensitive menu
when right-clicking on the Data Manager), which selects a valid RA automatically according to the study
time. If there are multiple RAs valid for the current study time, or if there is no valid one, a warning is
printed to PowerFactory ’s output window (nothing is selected in this case).

Applying and Resetting a Running Arrangement

DIgSILENT PowerFactory 2016, User Manual 197

CHAPTER 13. PROJECT LIBRARY

An active Running Arrangement (RA) can be applied to a substation by pressing the Apply and Reset
button from within the substation dialog. This action copies the statuses stored in the RA directly in the
substation switches. It is only available only if an RA is selected. The RA will be deselected afterwards.
An RA can be directly set as the substation’s selected RA, using the Assign button (from within the RA
dialog).

The following functional aspects must be regarded when working with running arrangements:

• An RA can be selected for each substation. If an operation scenario is active, the selection of
an RA in a substation is recorded in the operation scenario (i.e. the RA selection is part of the
operational data included in the operation scenario subset).
• If a variation is active (and there is no active operation scenario), the selection of the RA is stored
in the recording expansion stage.

• While an RA is selected, the switch statuses of the corresponding substation are determined by
the RA and can not be modified. Any attempt to change such a switch status will be rejected
and a warning message will be printed to the output window. The switch statuses preceding the
activation of an RA remain unchanged and are restored when deselecting the RA.
• The switch statuses stored in the RA could be incomplete due to the activation of a variation or a
modification made to the network model. For example, if an RA was defined and then deactivated,
and then later new switches were added to a substation. In this case if the RA is re-activated, a
warning would be printed to the output window and the current switch statuses, which depend on
the base network, active variations and active operation scenario, remain unchanged. Missing
switch statuses will be added only when performing the Save as or Overwrite functions (available
in the substation dialog).

• Switch statuses stored in the RA, and which are currently not required (depending on expansion
stages) are ignored and remain unchanged. In this case a summary warning is printed during the
RA activation.
• It is not possible to add a new switch to a substation while a running arrangement is selected.
Additionally, it is not possible to delete an existing switch from this substation. In both cases the
action is blocked and an error message is issued.

For information regarding operation scenarios and their application refer to Chapter 15 (Operation
Scenarios).

Assigning a Running Arrangement

The Assign button contained in the Running Arrangement (RA) dialog facilitates the selection of the
RA as the one currently selected for the corresponding substation. This action is also available in the
context-sensitive menu in the Data Manager (when right-clicking on an RA inside the Data Manager). It
should be noted that assignment is executed immediately and cannot be undone by pressing the cancel
button of the dialog.

Figure 13.3.4: Running Arrangement Dialog

198 DIgSILENT PowerFactory 2016, User Manual

 13.3. OPERATIONAL LIBRARY

13.3.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 prior to the fault. Thermal Ratings ob-
jects are stored in the Thermal Ratings folder in the Operational Library . They are two-dimensional
matrices, with cells that 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).

References to Thermal Ratings are defined on the Basic Data page of the dialog of the target branch
elements. Elements that can use references to Thermal Ratings are:

• Transmission lines (ElmLne).

• 2- and 3-winding transformers (ElmTr2) and (ElmTr3).

• Series reactors (ElmSind).

• Series capacitors (ElmScap).

Note that the rating table given on the Ratings page of the Thermal Rating object (when option Consider
short term ratings is enabled) is used solely for 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.

To create a new Thermal Ratings object:

1. Open the folder Thermal Ratings from the Operational Library.

2. Click on the New Object icon and select Thermal Ratings.

3. The new object dialog is displayed. To configure the table for the short-term ratings (only visible if
the option Consider short term ratings is checked), go to the Configuration page and:
• Introduce the increasing values for the pre-fault loading axis (Prefault %). By default, values
between 0% and 80%, with increments of 5%, up to 84% are set.
• Introduce the fault duration in minutes. Default values are: 360min, 20min, 10min, 5min, 3
min).

The pre-fault continuous rating (used as the base to calculate the loading before the fault) and the post-
fault continuous rating (assumed as the branch element post-fault rating if the fault duration is larger
than the largest duration time defined in the table) are defined on the Ratings page.

The values of a thermal rating object can be edited at any time by double-clicking on it to open the
Thermal Ratings dialog. Similar to Circuit Breaker Ratings and Capability Curves, Thermal Ratings
objects can be made to be time-dependant by means of variations and expansion stages stored inside
the Thermal Ratings folder (refer to the Circuit Breaker Ratings section for an explanation on how to
define time-dependant operational objects).

When a contingency analysis (ComSimoutage) is configured, the user can define a post-contingency
time. According to the pre-fault loading found by the load flow used to calculate the base case,
and the post-contingency time (if specified), the ratings to be used in the contingency load flow are
determined (based on the referred Thermal Ratings object). The loading of the branch elements after
the contingency load flow are calculated with respect to the new ratings.

For information about contingency analysis refer to Chapter 31 (Contingency Analysis).

DIgSILENT PowerFactory 2016, User Manual 199

CHAPTER 13. PROJECT LIBRARY

13.4 Templates Library

The Templates folder is used to store and organise templates of network components (or groups of
components) for re-use in a power system model. Components from templates are created using the
graphical editor. Five kinds of templates are supported in PowerFactory :

1. Element template for single network elements: New single network elements with the same
parameters as the original element are created.
2. Group template for non-composite graphic objects: New groups of objects (including graphical
attributes) are created.
3. Substation template (composite node): New substations with the same configuration as the origi-
nal substation (including its diagram).
4. Secondary Substation template: New secondary substations.
5. 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.

For further information about working with templates, refer to Section 9.2 (Defining Network Models with
the Graphical Editor).

Substation (composite node) templates ( or ), secondary substation ( ), busbar templates ( ),

branch templates ( ), and general templates ( ) can be selected from the Drawing Toolbox on the
right-hand pane of the PowerFactory GUI. To apply an element template:

• Select the symbol for a substation, secondary substation, busbar, branch, or general template as
required.
• Select the required template.
• Insert the new element in the single line graphic.

Note: The use of Substation templates is recommended for diagrams of networks, where components
are grouped in branches and substations. In this case the composite nodes can be graphically
connected with the composite branch, forming an overview diagram of the complete network.

This section explains how to create and use templates.

13.4.1 General Templates

Any kind of single network component (lines, transformers, terminals, etc.) can be used to define
an “Element” template; this is done by right clicking the desired element on a single line graphic and
selecting Define Template from the context sensitive menu, a dialog where the name of the new template
is to be written pops up. After the name is given and the Ok button is pressed, a copy of the selected
element is stored in the templates folder. Similarly, a group of network components can be used to
define a “Group” template, which will create a ’template’ folder ( ) storing the objects from the group
together with their graphical information. If a group of elements containing substation and branches has
been selected the elements outside the substation will not be added to the template.

200 DIgSILENT PowerFactory 2016, User Manual

 13.4. TEMPLATES LIBRARY

13.4.2 Substation Templates

Existing substations can be used as “models” to define templates, which may be used later to create new
substations. A new substation template is created by right clicking on one of the busbars of the detailed
substation single line diagram and selecting Define substation template from the context sensitive menu.
This action will copy the substation together with all of its contents (including its diagram even if it is not
stored within this substation) in the Templates folder.

Note: In case of creating templates which contain graphical information the default settings of the
names and result boxes defining their graphical representation (font, frame, size,...) are copied
into the template diagram so that they appear as in the source object(s).

13.4.3 Busbar Templates

Similar to creating substation templates, existing busbars can be used as a “models” to create user-
defined templates, which may be used later to create new busbars. A new busbar template is created
by right clicking on the detailed single line diagram or simplified diagram of busbar and selecting ’Define
substation template’ from the context sensitive menu. This action will copy the busbar together with all
of its contents (including detailed and simplified diagrams) in the Templates folder. If the detailed busbar
configuration has been modified, it is possible to right-click the (existing) simplified representation in the
main single line diagram and select ’Update representation’.

Busbars that have been created by the user in this way can be added to the single line diagram by
selecting the ’General Busbar System’ icon ( ). Note that for a busbar to be accessible from this icon,
both detailed and simplified diagrams must be included within the busbar template, as in the previously
described method.

13.4.4 Composite Branch Templates

Composite Branch templates can be defined as follow

1. To create a Branch template, navigate to the Library → Templates folder in the Data Manager.
2. Right-click on the right pane of the Data Manager and select New → Branch from the context
sensitive menu.
3. In the branch edit dialog, define the name of the branch and press Ok.

4. A new (empty) single line diagram will be displayed. Draw the required elements (for example, a
terminal with two lines connected, with each line connected at one end only).
5. To create an instance of the Branch from the newly created Branch template, navigate back to the
main grid diagram, then select the Composite Branch ( ) icon and connect the branch to existing
terminals on the Single Line Diagram.

Alternatively, composite branches can be defined in the Data Manager as described in Chapter 10:
Data Manager, Section 10.3.4 (Defining Composite Branches in the Data Manager).

13.4.5 Example Power Plant Template

Consider the following example, where there is a power station with multiple transformers, generators,
and control systems of the same type. The model can be created using templates as follows:

DIgSILENT PowerFactory 2016, User Manual 201

CHAPTER 13. PROJECT LIBRARY

1. Firstly, define type data for the transformer, generator, and control system.
2. Add a single instance of the generating unit (including generator transformer) to the network
model.

3. Define a Template by selecting the generator, generator bus, and transformer, then right-click and
select Define Template. Optionally include the control system model with the template.

4. To create another instance of the newly created template, select the General Templates icon ( )
and place it on the single line graphic.

13.4.6 Wind Turbine Templates according to IEC 61400-27-1

There are predefined Templates for Wind turbine models according to IEC 61400-27-1 in the Templates
Library of PowerFactory . More information is available in Section B.12.1

13.4.7 Example Busbar Template

Consider the following example where there is network with multiple instances of a Double Busbar
System. However, the Double Busbar System required for this particular model is a variant on the
standard Double Busbar System, which requires two switches. To simplify the task of developing the
model, a Template may be defined as follows:

1. Place a standard Double Busbar System on the single line graphic.

2. Right-click and select Show Detailed Graphic of Substation.

3. Extend the busbar length, and then copy and duplicate the switches connecting “BB1” to “BB2”
(see Figure 13.4.1).

Figure 13.4.1: Detailed Busbar Layout

4. On the main Grid single line graphic, select Draw Existing Net Elements, press the Logical Switch
icon ( ) and draw the second switch connecting “BB1” to “BB2”.
5. Right-click either busbar in the overview diagram and select Define Substation Template (see
Figure 13.4.2), then name the Template.

202 DIgSILENT PowerFactory 2016, User Manual

 13.4. TEMPLATES LIBRARY

Figure 13.4.2: Example Busbar Template

6. Use the General Busbar System icon ( ) to place additional instances of the busbar system in
the power system model.

DIgSILENT PowerFactory 2016, User Manual 203

CHAPTER 13. PROJECT LIBRARY

204 DIgSILENT PowerFactory 2016, User Manual

Chapter 14

Grouping Objects

This chapter describes the management and functionality of the objects used to group network compo-
nents.

14.1 Areas

To facilitate the visualisation and analysis of a power system, elements may be allocated into areas (El-
mArea ). The single line graphics can then be coloured 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.

To define a new area:

• Multi select the components belonging to the new area (in the Data Manager or in a single line
diagram).

• Right click on the selection and select Define → Area from the context sensitive menu.
• After the area has been defined, terminals can be added to it by selecting Add to. . . → Area. . . in
their context sensitive menu.

In the edit dialog of the new area you must select a colour to represent the area in the single line
diagrams. Using the Edit Elements button you can have access to all the element belonging to that
area in a data browser, then you can edit them. The Mark in Graphic button may be used to locate the
components of an Area in a single line diagram.

Note: Areas that are created/deleted when a recording expansion stage is active; become available/not
available only if the corresponding variation is active and the expansion stage activation time is
earlier than the current study time.

For information concerning the visualisation of areas within the single line Graphic refer to Chapter 9:
Network Graphics, section 9.6.5.1 (Basic Attributes). For information about reporting Area results refer
to Chapter 18 (Reporting and Visualising Results).

DIgSILENT PowerFactory 2016, User Manual 205

CHAPTER 14. GROUPING OBJECTS

14.2 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 page in the generator element dialog) 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 ) are stored inside the Virtual Power Plants folder ( ) within
the Network Data directory.

14.2.1 Defining and Editing a New Virtual Power Plant

A new Virtual Power Plant is created by:

• Multi selecting in a single line diagram or in a data browser an initial set of generators to be
included in the Virtual Power Plant;
• Then pressing the right mouse button and selecting Define → Virtual Power Plant from the context
sensitive menu.

Figure 14.2.1: Defining a Virtual Power Plant

Alternatively you can create a new empty Virtual Power Plant by using the Data Manager:

• Open a Data Manager.

• Find the Virtual Power Plant folder ( ) and click on it.

• Press the icon for defining new objects ( ).

206 DIgSILENT PowerFactory 2016, User Manual

 14.3. BOUNDARIES

• select Others.
• Then select Virtual Power Plant (ElmBmu) in the list box.
• Assign a suitable name to the Virtual Power Plant.
• Press OK.

The rules which determine the dispatch of the selected generators are set in the Virtual Power Plant
dialog. The total active power to be dispatched is set in the field ’Active Power’. The dispatch of the
belonging generators (variable “pgini” from the Load Flow tab of the generator) is set by pressing the
Apply button. If the ’Maximal active power sum’ of the included generators (sum of the maximal active
power operational limit of the generators) is smaller than the active power to be dispatched, an error
message pops up. Otherwise the dispatch is set according the user defined ’Distribution Mode’:

According to merit order Distribution of the dispatched active power is done according to the
priorities given to each generator in the Merit Order column of the ’Machines’ table (this value can
also be set in the Optimisation tab of the generators dialog). Lower values have higher priority.
Generators with the option ’Must Run’ checked are dispatched even if they have low priority (high
value). It is assumed that the merit of order of all generators in the Virtual Power Plant is different.
If not an error message appears after the ’Apply’ button is pressed.

According to script The rules for the dispatch are set in user defined DPL scripts, which are
stored inside Virtual Power Plant object. To create new scripts or to edit the existing ones you
must open a data browser with the ’Scripts’ button.

Note: The Virtual Power Plant active power is part of the operation scenario subsets and therefore
is stored in the active operation scenario (if available). The active power is stored in the active
expansion stage (if available) if no active operation scenario is active. Virtual Power Plants that
are created/deleted when a recording expansion stage is active; become available/non available
only if the corresponding variation is active and the expansion stage activation time is earlier than
the current study time.

14.2.2 Applying a Virtual Power Plant

Check that the active power set for the Virtual Power Plant is less than or equal to the maximum power.
Press the Apply button.

14.2.3 Inserting a Generator into a Virtual Power Plant and Defining its Virtual
Power Plant Properties

Generators are added to an existing Virtual Power Plant by adding a reference in the ’Optimisation’ tab
of their edit dialog. Notice that a generator can belong to at most one Virtual Power Plant. Define the
Merit Order and must run properties as required.

You also can add a generator to a Virtual Power Plant by clicking with the right mouse button on the
element in the network graphic and choose Add to. . . → Virtual Power Plant. . . from the context
sensitive menu.

14.3 Boundaries

Boundaries are used in the definition of network reductions and to report the interchange of active and
reactive power after a load flow calculation. Boundary objects (ElmBoundary ) may define topological
regions by specifying a topological cut through the network.

DIgSILENT PowerFactory 2016, User Manual 207

CHAPTER 14. GROUPING OBJECTS

Boundaries are defined by the cubicles that determine the cut through the network, these cubicles
together with the orientations define the corresponding “Interior Region”. Topologically, the interior
region is found searching through the network starting at each selected cubicles towards the given
direction. The topological search continues until either an open switch or a cubicle that is part of the
boundary list is found. Any open switch that is found by this search is considered to be part of the
interior region.

Boundaries can be defined using the Boundary Definition Tool or directly on the branch elements by
right clicking on them and selecting Define → Boundary. . . .

The Boundaries are stored in the project folder Boundaries ( ) within the Network Data.

Note: Boundaries that are created or deleted when a recording expansion stage is active; become
available/not available only if the corresponding variation is active and the expansion stage acti-
vation time is earlier than the current study time.

14.3.1 Boundary Definition Tool

The Boundary Definition Tool ( ) is located within the Additional Tools toolbox as shown in Fig-
ure 14.5.3.

Figure 14.3.1: Additional Tools toolbox

The following options are available when using the Boundary Definition Tool command:

Based on regional elements

Zones, areas, grids and even existing boundaries can be used to define a boundary. The selection
supports multiple elements of the same type.

When regional elements are used, some additional options are available for the user:

• One common boundary: single boundary containing all the interior elements of the composing
regions.
• Separate boundary for each region: a number of boundaries corresponding to the number of
regions will be defined with corresponding interior elements.

208 DIgSILENT PowerFactory 2016, User Manual

 14.3. BOUNDARIES

• All boundaries between neighbouring regions: each combination between selected regions is
considered and corresponding boundary is defined.

Based of branch elements

Branch elements (e.g. lines, transformers) can be used to define a boundary, PowerFactory will perform
a topological search to define the interior elements. To finishing defining the interior region, the user
can check the Assign selected branch elements to interior region checkbox on the Basic Data page of
the command dialog.

In addition the Boundary Definition Tool offers the possibility to define the boundary only if it splits the
network into two separated regions.

14.3.2 Element Boundary

The element boundary ElmBoundary edit dialog is accessible by double clicking on the boundary
element, using either the Data Manager or the Network Model Manager.

To add cubicles to an existing Boundary:

• In the Boundary dialog, right click on the table (on the number of a row) that lists the included
cubicles.

• Select Insert rows, Append rows or Append n rows from the context sensitive menu.
• Double click on the Boundary Points cell of the new line.
• Select the target cubicle using the data browser that pops up.

After selecting the desired cubicle, the terminal and the branch element connected to it are added to
the Busbar and Branch cells on the table. By default the Orientation (direction used to determine the
interior region) is set to the branch; you can change it in order to direct the definition of the internal
region to the connected terminal.

Cubicles can be retired from a boundary by selecting Delete rows from the context sensitive menu of
the table in the element dialog.

The selected colour at the bottom of the dialog is used to represent the boundary in the single line
diagrams ( ). Each element in the graphic is coloured according to the following criteria:

• If it uniquely belongs to one interior region of a boundary to be drawn, its colour will be assigned
to that specific boundary colour.

• If it belongs to exactly two of the interior regions of the boundaries to be drawn, its will be
represented with dashed lines in the specific boundary colours.
• If it belongs to exactly more than two of the interior regions of the boundaries to be drawn, its will
be represented with dashed lines in black and the colour selected for multiple intersections.

The Edit Interior Elements button can be used to list in a data browser all the components included in
the internal region. The Mark Interior Region button marks all the components of the interior region in
the selected network diagram.

Topological changes in the network that affect the defined interior regions are automatically detected by
the program.

DIgSILENT PowerFactory 2016, User Manual 209

CHAPTER 14. GROUPING OBJECTS

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

To create a new Circuit:

• In the Data Manager open the Circuits folder from the Network Model.
• Click on the New Object icon.
• The edit dialog of the new Circuit pops up. Give a name to the new object and press Ok.

Branches are added to a circuit using the pointer from the ’Circuit’ field of the branch dialog. The button
Branches in the Circuit dialog opens a data browser listing the branches that refer to that circuit.

Note: Circuits that are created or deleted when a recording expansion stage is active; become avail-
able/not available only if the corresponding variation is active and the expansion stage activation
time is earlier than the current study time.

14.5 Feeders

When analysing 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 coloured uniquely in the single line
graphic. All feeder objects are stored in the Feeders folder ( ) in the Network Data folder.

A new feeder is created by right-clicking on a cubicle (that is, when the cursor is held just above the
breaker in the single line diagram) and selecting Define → Feeder. . . . Once the option Feeder has been
selected, the Feeder dialog pops up. There you can define the desired options for the new object. After
pressing Ok, the new Feeder is stored in the Feeders folder of the Network Model.

Any existing Feeder can be edited using its dialog (double click the target Feeder on a data browser).
The Feeder dialog presents the following fields:

Name
Cubicle Is a reference to the cubicle where the Feeder was created. It is automatically set by the
program once the Feeder is created.

210 DIgSILENT PowerFactory 2016, User Manual

 14.5. FEEDERS

Zone Reference to the Zone (if any) to which the feeder belongs. A Feeder is assigned to the zone of
the local busbar/terminal.
Colour Sets the colour be used when the Feeder Definitions colouring mode ( ) is engaged in the
single line diagram.
Terminate feeder when. . . A feeder will, by default, terminate when a higher voltage level is encoun-
tered, however, this may not always be desirous. This may be prevented by un-checking this
option. The feeder will now continue ’past’ a higher voltage level and may be terminated at
a user defined cubicle if desired. To manually terminate a feeder right-click a branch element
above the breaker (to select the desired cubicle where the feeder is going to end) and select Edit
Cubicle. The cubicle dialog will be presented, and the ’Terminate feeder at this point’ option may
be checked.
Orientation The user may select the direction towards the feeder is defined. ’Branch’ means that
the feeder starts at the cubicle and continues in the direction of the connected branch element.
’Busbar’ means that the Feeder is defined in the direction of the connected Terminal.
Load Scaling In any system some loads values may be accurately known whilst others are estimated.
It is likely that measurement points exist for feeders in the system as well, and thus the power
that is drawn through this feeder is also known. The load scaling tool assists the user in adjusting
these estimated load values by scaling them to match a known feeder power or current that has
been measured in the real system. More information about the use of the Load Scaling Function
is given below.
Elements The Mark in Graphic button may be used to select all the elements of a Feeder in the
desired single line diagram. The Edit button is used to list all the elements belonging to a Feeder
in a data browser.

To use the Load Scaling tool first define which loads may be scaled by enabling the ’Adjusted by Load
Scaling’ option on the Load-Flow tab of the load dialog. All of the loads in a feeder may also be quickly
viewed by editing the feeder from the feeders folder. Load scaling is now performed by the load-flow
calculation function when:

• At least one feeder is defined with load scaling according to a current or power.
• The option ’Feeder Load Scaling’ is enabled in the load-flow command dialog (basic options).
• At least one load exists in the feeder area for which
– A change in operating point affects the load-flow at the feeder position
– The option ’Adjusted by Load Scaling’ has been enabled.

The load-flow calculation will then adjust the scaling of all adjustable loads in the feeder areas in such
a way that the load-flow at the feeder equals the current or power set-point.

The feeder setpoint is influenced by the zone scaling. This means that the current or power flow as
calculated by the load-flow could differ from the setpoint in the feeder dialog when the busbar where the
feeder is defined is part of a zone.

For instance, a feeder has a set-point of 1.22 MVA. The busbar is in a zone and the zone-scale is set to
0.50. The flow at the feeder position will thus be 0.61 MVA.

For information about colouring the single line graphic according to feeder definitions refer to Chapter 9:
Network Graphics. For information about voltage profile plots, refer to Chapter 18 (Reporting and
Visualising Results).

Defining Feeders from a Terminal Element

Often it is useful to be able to quickly setup a feeder or many feeders from a ’source’ bus within the
system. There is a specific methodology within PowerFactory for this purpose. The procedure is as
follows:

DIgSILENT PowerFactory 2016, User Manual 211

CHAPTER 14. GROUPING OBJECTS

1. Right-click the target terminal where the feeder/s should be defined from.
2. Choose the option Define → Feeder. . . from the context sensitive menu that appears. This step
is illustrated in Figure 14.5.1.

3. PowerFactory will automatically create Feeder objects for each of the connected two terminal
elements, for example lines and transformers. The list of created feeders is displayed in a pop-up
window. The default name for each feeder is the concatenation of the terminal name and the
connected object.

4. Adjust the feeder colours and definitions as required and remove any unwanted feeders.

Figure 14.5.1: Definition of Feeders from a terminal by right-clicking the terminal

Note: The Load Scaling options are part of the operation scenario subsets; therefore they are stored
in the active operation scenario (if available). The Load Scaling options are stored in the active
expansion stage (if available) if no active operation scenario is active. feeders that are created
or deleted when a recording expansion stage is active; become available/not available only if the
corresponding Variation is active and the expansion stage activation time is earlier than the current
study time.

14.5.1 Feeder Tools

Feeder Tools is a set of three tools that can be used only in radial systems to change voltage, technology
from a particular point downwards.

Note: Additional functions for feeders like Backbone Calculation or Phase Balance Optimisation are
available in the module Distribution Network Tools, described in chapter 38

14.5.1.1 Voltage Change Tool

The Voltage Change Tool automatically changes type data (for transformers, lines, loads and motors)
and element data such that the primary voltage can be changed to a specified voltage value. The tool

212 DIgSILENT PowerFactory 2016, User Manual

 14.5. FEEDERS

will change the voltage from a particular point downwards but is limited to the HV side. This will enable
the voltage level of a network to be changed for planning studies, taking into account all downstream
equipment.

14.5.1.2 Technology Change Tool

The Technology Change Tool automatically changes type data (for transformers, lines, loads, motors)
and element data such that the primary number of phases or neutrals (commonly referred to as ’tech-
nology’) can be changed to a specific number of phases/neutrals. The tool will change the technology
from a particular point downwards but is limited to the HV side.

Note: If a device such as a transformer or shunt device is no longer compatible (number of phases
and/or phasing is not supported) then the device is set out of service and is reported to the user.

14.5.1.3 Feeder Tool Command

Feeder Tools is a built-in command (ComFeedertool) in PowerFactory and can be started via the right-
mouse context-sensitive menu, by clicking on an element of a feeder as shown in Figure 14.5.2. A radial
feeder must be defined prior to using the command.

Figure 14.5.2: Feeder Tool

DIgSILENT PowerFactory 2016, User Manual 213

CHAPTER 14. GROUPING OBJECTS

The voltage, technology and balancing tools are all related and are integrated in PowerFactory as one
command having different options for enabling/disabling each individual tool. Any combination of the
three tools can be used. For example, a user may want to evaluate the alternative where an existing
19 kV SWER line is to be changed to a 22 kV three-phase line. In this case, the line type voltage, phasing
and technology will all need to change. The transformers should then be changed to equivalent single-
or dual-phase transformers (depending on their original secondary technology) with 22 kV phase-to-
phase conn