Chapter 29

Contingency Analysis

29.1 Introduction

In Chapter 21 (Load Flow Analysis) the general aspects of load flow analysis and its main areas of
application were presented. Additionally, two perspectives were discussed: that of planning and that of
system operation (see Figure 21.1.1). There it was made evident that regardless of the perspective, the
behaviour of the system must be analyzed under both normal and abnormal conditions.

When referring to contingency analysis, we are essentially referring to the analysis of abnormal system
conditions. In general, contingency analysis can be defined as: "the evaluation of the violations in
system operating states (if any) that certain contingencies can pose to the electrical power system";
or put in other words, contingency analysis is the execution and evaluation (loading and voltage-wise)
of post-fault load flows; each of which reflect the "outage" of a single or group of elements (such as
transformers, busbars, transmission lines, etc.).

Contingency analyses can be therefore used to determine power transfer margins or for detecting the
risk inherent in changed loading conditions. This chapter deals with deterministic contingency analysis.

29.2 Technical Background

The contingency analysis module available in PowerFactory offers two distinct contingency analysis
methods:

Single Time Phase Contingency Analysis:

The non-probabilistic (deterministic) assessment of failure effects under given contingencies,

within a single time period.

Multiple Time Phase Contingency Analysis:

The non-probabilistic (deterministic) assessment of failure effects under given contingencies,

performed over different time periods, each of which defines a time elapsed after the contingency
occurred. It allows the definition of user defined post-fault actions.

Figures 29.2.1 and 29.2.2 illustrate the general sequence of both methods. Here the results of both
pre- and post-fault load flows are compared to the specified loading and voltage limits; based on this
comparison contingency reports are generated.

In Figure 29.2.1 the term Single Time Phase is used because only one post-fault load flow is analyzed
per contingency case.

DIgSILENT PowerFactory 15, User Manual 653

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.2.2 illustrates the multiple time phases contingency analysis method. Here, more than one
post-fault load flow can be analyzed for the same contingency; hence the term Multiple Time Phase.
Furthermore, if required, each time phase can have its own post-fault actions defined. The defined
post-fault actions can be either a single event or a combination of the following events:

• Load shedding

• Generator re-dispatching
• Switching action (opening or closing)
• Tap changing

In PowerFactory , the term Fault Case (used in both Figures) is used to define a contingency.

Figure 29.2.1: Single Time Phase Contingency Analysis Method

654 DIgSILENT PowerFactory 15, User Manual

 29.2. TECHNICAL BACKGROUND

Figure 29.2.2: Multiple Time Phase Contingency Analysis Method

Before describing in detail the contingency analysis itself, it is necessary to introduce two basic concepts
which define the functionality of this tool:

• Contingencies: These are objects in PowerFactory of the class ComOutage ( ) which are used
to represent contingencies. They are defined by a set of events which represent the occurrence of
the originating fault(s) over time and the subsequent fault clearing and post-fault actions. It should
be noted that depending on the method selected and the value assigned to the Post Contingency
Time parameter (see Section 29.5.3: Multiple Time Phases), post-fault actions are carried out.
For further information on the definition and use of contingencies please refer to Section 29.5.7
(Defining Time Phases for Contingency Analyses).
• Time Phases: These represent points in time at which the steady-state operational point of
the network under analysis is calculated. Each time phase is defined via a user defined Post
Contingency Time (see the Multiple Time Phases page of the Contingency Analysis command).
The Post Contingency Time defines the end of a phase; that is, the point in time at which the
steady-state of the network is calculated. For further information regarding the definition of time
phases refer to Section 29.5.7 (Defining Time Phases for Contingency Analyses).

DIgSILENT PowerFactory 15, User Manual 655

CHAPTER 29. CONTINGENCY ANALYSIS

29.2.1 Single Time Phase Contingency Analysis

The single time phase contingency analysis function first performs a pre-fault (base) load flow calcula-
tion. Following this, for each contingency (stored inside the command itself) it performs a corresponding
post-contingency load flow (for a single time phase), which take one or more primary components out
of service. The command calculates the initial consequences of the contingencies, but does not regard
the operational measures taken to mitigate voltage band problems or supply interruptions.

It is important to mention here that if the contingency analysis command is set to consider Automatic Tap
Adjust of Transformers and Shunt Adjustment, they will only be considered if their time constants are
smaller than the current Post Contingency Time or if the Consider Specific Time Phase flag (Multiple
Time Phases page) is not enabled. Additionally, the operational thermal ratings of branch elements
during the contingency (if ’short term’ thermal ratings (12.3.7) have been defined) will depend on the
duration of the contingency i.e. the current Post Contingency Time.

The raw results of the single time phase contingency analysis correspond to the steady-state opera-
tional points of the network being studied, considering each one of the defined contingencies up to
the given Post Contingency Time (see Section 29.4: The Single Time Phase Contingency Analysis
Command for further information on this setting). The reporting facilities available in PowerFactory ’s
contingency analysis function allow the filtering of results of interest to the user, including maximum
loading of branch elements, exceeded voltage limits, etc. Refer to Section 29.4 (The Single Time
Phase Contingency Analysis Command) for further information on configuring the reporting settings,
and Chapter 11 Study Cases, Section 11.11 (Results Objects) for information on handling result objects
(ElmRes) in PowerFactory.

Note: If the Fault Case contains post-fault actions such as load shedding, generator re-dispatch, tap
changing and switching actions (closing), these are ignored in the Single Time Phase mode,
regardless of the specified Post Contingency Time.

29.2.2 Multiple Time Phases Contingency Analysis

As indicated previously, PowerFactory provides tools for the analysis of contingencies over multiple
time phases, allowing the definition of post-fault actions that can lead to the mitigation of voltage band
problems or supply interruptions which are caused by faults in the networks under analysis.

As in the single time phase contingency analysis, the multiple time phases contingency analysis function
first performs a pre-fault (base) load flow calculation. The major difference here is that for each
contingency (stored inside the command), it loops over the list of defined time phases (also stored
inside the command itself), calculating the corresponding post-contingency load flows. For each load
flow calculation, the events (faults and post-fault actions) whose time of occurrence are earlier than, or
equal to, the corresponding Post Contingency Time, are considered.

Similar to single time phase contingency analysis, the effect of transformer tap changers and switchable
shunts depends on these components’ corresponding time constants and the current Post Contingency
Time. Controllers are only considered if their time constants are smaller than the current Post Contin-
gency Time. Additionally, the operational thermal ratings of branch elements during the contingency (if
’short term’ thermal ratings (12.3.7) have been defined) will depend on the duration of the contingency
i.e. the current Post Contingency Time.

The raw results of the contingency analysis with multiple time phases correspond to the steady-state
operational point of the network being studied, at every Post Contingency Time for each of the de-
fined contingencies. The reporting features included in the function allows the filtering of problematic
contingencies, according to maximal loading of branch elements, exceeded voltage limits, etc.

656 DIgSILENT PowerFactory 15, User Manual

 29.3. EXECUTING CONTINGENCY ANALYSES

29.2.3 Time Sweep Option (Single Time Phase)

PowerFactory provides a special Calculate Time Sweep option for the Single Time Phase method, and
which can be found on the Time Sweep page of the contingency analysis command. When enabled,
the date and time of the active Study Case will be modified according to a list predefined by the user.
The application of this option is in situations where the calculation of contingencies is required for a
certain time span; for example, the automatic calculation of contingencies for every hour of the day.

Here it is important to note that in order for the Time Sweep to activate the corresponding scenarios
automatically, a Scenario Scheduler (IntScensched) object needs to first be created and afterwards
activated. Once the execution of the contingency analysis has finished, the Study Case date and time
are restored to their original setting. For more information on the Scenario Scheduler please refer to
Chapter 14(Operation Scenarios).

In addition, the Time Sweep option can be used in combination with the Parallel Computing option
(Section 29.2.5).

29.2.4 Consideration of Predefined Switching Rules

In PowerFactory , the contingency analysis can be setup to consider predefined switching rules of
substations (refer to Chapter 9: Network Graphics (Single Line Diagrams), Section 9.2.6 for further
information). The Switching Rule defines switching actions for different fault locations (arranged in a
matrix) that can be reflected at a certain time. These switching actions will always be relative to the
current switch position of every breaker.

29.2.5 Parallel Computing Option (Single Time Phase)

The computation time required to perform a contingency analysis largely depends on two factors:

• The size of the power system; and

• The number of contingencies considered.

Depending on these factors, the computation time could take from a couple of seconds (or less) up to
several minutes.

With the development of multi-core machines and the existence of Ethernet network technology, the
calculation of contingencies in parallel is now an option in PowerFactory. This feature facilitates the
significant reduction of required computation time depending on the number of cores being used.

By default, the Parallel Computing option is enabled in each user account; however, the setting can be
modified when the user has logged on as an Administrator.

The following sections provide detailed information regarding the execution and settings of the contin-
gency analysis command in its single or multiple time phase configuration.

29.3 Executing Contingency Analyses

To access the various contingency analysis related functions within PowerFactory , click on the icon
Change Toolbox and select "Contingency Analysis".

Figure 29.3.1, shows the Contingency Analysis Toolbar, with all the related functions.

DIgSILENT PowerFactory 15, User Manual 657

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.3.1: Contingency Analysis Related Functions

Both the Single Time Phase and Multiple Time Phases contingency analysis are carried out using the
Contingency Analysis command (ComSimoutage, ). When configured and executed, it performs a
’base’ load flow calculation to determine the operational point of the network under no-fault conditions.
The command contains Contingency Cases (ComOutage objects) which define one or more elements
that are taken out of service simultaneously. Following the calculation of the base load flow, a contin-
gency load flow for each of these contingencies is calculated. This calculation considers the post-fault
thermal ratings of branch elements (see Chapter 12: Project Library, Section 12.3.7), transformer tap
changer controller time constants and automatic shunt compensators (for further information please
refer to Section 29.4: The Single Time Phase Contingency Analysis Command).

In PowerFactory , contingency cases can be generated by two primary means:

• Via the definition and use of Fault Cases and Fault Groups; and/or
• Using the Contingency Definition (ComNmink ) command, either via its toolbar icon ( ) or by
selecting component(s) in the single-line graphic, right-clicking and selecting Calculate → Contin-
gency Analysis. . .

In the first case, contingency cases can be created using references to user defined Fault Cases and
Fault Groups (introduced in Chapter 12: Project Library, Section 12.3.3) from the Operational Library.
By means of a topological search, PowerFactory determines which circuit breakers must be opened in
order to clear the faults, and generates the corresponding contingency cases. Each contingency case
is generated with its corresponding interrupted components for each fault case/group. Fault cases and
groups reside in the Operational Library folder, and can be reused. Hence there is no need to manually
redefine the same contingencies each time a contingency analysis is required. For further information
on creating contingencies from fault cases/groups, please refer to Section 29.6 (Creating Contingency
Cases Using Fault Cases and Groups).

In the second case, contingencies can be created using the Contingency Definition command. This
command is available either via the icon on the main toolbar, or by right-clicking on a selection of
elements in the single line diagram, and selecting the option Calculate → Contingency Analysis. . . .
Either an n-1 or an n-2 outage simulation for the selected elements can then be prepared. Additional to
these two options an n-k outage for mutually coupled lines/cables is available. The Contingency Defini-
tion command optionally allows all lines/cables, transformers, series reactors, series capacitors and/or
generators to be selected to create contingencies. For further information on creating contingencies
using the Contingency Definition command, please refer to Section 29.7 (Creating Contingency Cases
Using the Contingency Definition Command).

The following sections provide detailed information regarding the settings and features of the contin-
gency analysis command in its single time phase configuration.

658 DIgSILENT PowerFactory 15, User Manual

 29.4. THE SINGLE TIME PHASE CONTINGENCY ANALYSIS COMMAND

29.4 The Single Time Phase Contingency Analysis Command

The settings of the Basic Options page of the contingency analysis command (ComSimoutage ) are
illustrated in Figure 29.4.1.

Figure 29.4.1: Basic Options settings of the Contingency Analysis (ComSimoutage) Command

When executing a contingency analysis, the general sequence of operations performed is as follows:

• Execution of a ’base’ load flow in order to determine the initial operational point of the network.
This ’base’ (pre-fault) load flow is performed according to the settings stated in the load flow com-
mand and which is referenced on the Basic Options page of the contingency analysis command.

• Execution of the ’contingency’ load flows. That is, for each of the stored contingency cases, it
places the interrupted components (see Section 29.4.8: Representing Contingency Situations
- Contingency Cases) on outage and performs a contingency (post-fault) load flow. Here, the
settings of the post-fault load flows will depend on how the contingency command is configured.
That is, if specified by the user, the pre-fault and post-fault load flows can be executed with different
settings (only a difference in certain settings are allowed). For more information please refer to
Section 29.5.3 (Multiple Time Phases).

The contingency load flow is characterized by the Post Contingency Time parameter (available on the
Multiple Time Phases page of the Contingency Analysis command if either the option Allow different
settings has been enabled, or when the option Consider Specific Time Phase has been selected). This
parameter determines the duration of the interval between the occurrence of the fault(s) which define the
contingency, and the time when the load flow calculation of the network under the contingency situation

DIgSILENT PowerFactory 15, User Manual 659

CHAPTER 29. CONTINGENCY ANALYSIS

is performed. The Post Contingency Time is a key parameter of the single time phase contingency
analysis because:

1. The actions of transformer automatic tap changers and switchable shunt compensators on the
faulted network are only regarded if the time constants of their controllers are less than the defined
Post Contingency Time (meaning that the controllers are fast enough to operate during the time
phase); and
2. The operational thermal ratings of branch elements during the contingency (if ’short term’ thermal
ratings (see Section 12.3.7) have been defined) will depend on the duration of the contingency,
i.e. the Post Contingency Time.

Note: The ’base’ and the ’contingency’ load flow calculations by default use the same load flow com-
mand (ComLdf object). However, the user can define different load flow commands for these two
calculations by selecting the option ’Allow different settings’ on the Multiple Time Phases page
of the contingency analysis command (ComSimoutage). The actions of automatic tap changers
and switchable shunts are only possible if the corresponding options are selected in the ’Basic
Options’ page of the load flow command(s).

The contingency analysis uses a result file object (ElmRes, see Chapter 11 Study Cases, Section 11.11
(Results Objects)) to store the voltages at terminals and the loading of certain branch element classes
(lines, transformers, series capacitors and series reactors). Recording the loadings for all branches and
the voltages for all terminals for every contingency may lead to excessive data storage. Therefore, in or-
der to minimize data storage, only significant results are recorded. In contingency analysis, a calculated
parameter is considered to be significant if the threshold (Limits for Recording) of the corresponding
component are out of the threshold. Limits can be set individually for each terminal and branch element
(in the Load Flow page of the element’s dialogue) or globally in the Limits for Recording field of the
contingency analysis command. A calculated result is stored in the result file whenever one of the
constraints (individual or global) is violated.

The settings of the contingency analysis command are entered using the dialogue shown in Fig-
ure 29.4.1. The following subsections explain each of the available options.

29.4.1 Basic Options

Calculation Method

AC Load Flow Calculation The contingency analysis uses an iterative AC load flow method to
calculate the power flow and voltages per contingency case.

DC Load Flow Calculation The contingency analysis uses a linear DC load flow method to
calculate the active power flow per contingency case.

DC Load Flow + AC Load Flow for Critical Cases The contingency analysis will perform two
runs (if required). First it will use a linear DC load flow method to calculate the active power flow
per contingency case; if for certain contingencies loadings are detected to be outside a certain
threshold, then for these cases the contingency analysis will recalculate the post-fault load flow
using the iterative AC load flow method. The criteria (threshold) used for the AC recalculation of
critical DC cases is stated on the Advanced Options page.

Limits for Recording

The parameters in this section set the global threshold used to determine whether a calculated result is
recorded in the Results object (object pointed to by the Results for AC or Results for DC field located in
the bottom section of the Basic Options page). Whenever one of the defined constraints is violated, the
calculated result (for the corresponding contingency case and network component) is recorded.

660 DIgSILENT PowerFactory 15, User Manual

 29.4. THE SINGLE TIME PHASE CONTINGENCY ANALYSIS COMMAND

Max. thermal loading of components (%) Maximum thermal loading in percent. Loadings
exceeding this value will be recorded in the result file for the corresponding component.

Lower limit of allowed voltage (p.u.) Minimum admissible voltage in per unit. Voltages lower
than this value will be recorded in the result file for the corresponding terminal.

Upper limit of allowed voltage (p.u.) Maximum admissible voltage in per unit. Voltages higher
than this value will be recorded in the result file for the corresponding terminal.

Maximum voltage step change (p.u.) Maximum (+/-) admissible voltage change in per unit.
Larger voltage changes (pre-fault vs. post-fault) will be recorded in the result file for the corre-
sponding terminal.

Contingencies

The Contingencies section of the Basic Data tab, as shown in Figure 29.4.2, allows the display, creation
and removal of contingencies. These are the contingencies that will be analyzed by the contingency
analysis command.

Figure 29.4.2: Contingencies Section of Contingency Analysis Dialogue

Show Displays a list of all defined contingencies.

Add Cases/Groups This button is used to create the contingency cases (ComOutage objects)
based on fault cases and/or fault groups. A fault case contains events: one for the fault location,
and (optionally) others specifying post-fault actions. Fault groups contain a set of references to
fault cases. In order to use the Add Cases/Groups option, the fault cases and/or groups must
have been previously defined in the Operational Library. If these have been defined, when the
Add Cases/Groups button is pressed, a data browser listing the available fault cases/groups
pops up. The user can then select the desired fault cases/groups from this browser and press
Ok. The corresponding contingencies are then created automatically by PowerFactory. One
contingency is created for each selected fault case, and one contingency is created for each fault
case referred to within each selected fault group. For further information on creating contingen-
cies from fault cases/groups, please refer to Section 29.6 (Creating Contingency Cases Using
Fault Cases and Groups).

Remove All Removes all contingency cases (ComOutage objects) stored in the contingency
analysis command.

Results for AC/DC

Depending on the calculation method selected, the reference to the corresponding result file object
(ElmRes) is defined. If, for example, the calculation method DC Load Flow + AC Load Flow for Critical
Cases is selected, two result file objects will be referenced (one for AC calculations and another for DC
calculations). The results stored in this file are filtered according to the global threshold set in the Limits
for Recording section of the Basic Data tab, and also according to the individual limits defined within
each component’s respective dialogue (such as on the Load Flow page of the element’s own dialogue).
For further information on result objects, please refer to Chapter 11 Study Cases, Section 11.11 (Results
Objects).

DIgSILENT PowerFactory 15, User Manual 661

CHAPTER 29. CONTINGENCY ANALYSIS

29.4.2 Effectiveness

The Effectiveness page of the contingency analysis command (Figure 29.4.3), allows the display,
addition and removal of quad boosters and generators in order to calculate their effectiveness.

Figure 29.4.3: Effectiveness Options Settings of the Contingency Analysis Command

Calculate Quad Booster Effectiveness

Show QBs Shows a list of the transformers for which the effectiveness should be calculated.

Add QBs Adds references to transformers for which the effectiveness should be calculated. Only
transformers where the additional voltage per tap is different to 0 and multiples of 180 degrees
will be listed (Load Flow page of the transformer type (TypTr2) Phase of du parameter).

Remove All Removes all references to transformers for which the effectiveness is currently
calculated.

Calculate Generator Effectiveness

Show Gen. Shows a list of the generators for which the effectiveness should be calculated.

Add Gen. Adds references to transformers for which the effectiveness should be calculated.

Remove All Removes all references to generators for which the effectiveness is currently calcu-
lated.

29.4.3 Multiple Time Phases

The Multiple Time Phases tab, as shown in Figure 29.4.4, allows the selection of the contingency
method to be performed as well as the corresponding settings.

662 DIgSILENT PowerFactory 15, User Manual

 29.4. THE SINGLE TIME PHASE CONTINGENCY ANALYSIS COMMAND

Figure 29.4.4: Multiple Time Phases Option Settings of the Contingency Analysis Command

Method

Single Time Phase Performs the contingency analysis for a single time phase.

Multiple Time Phase Performs the contingency analysis for multiple time phases, allowing the
definition of post-fault actions.

Base Case versus Contingency Load Flow

Use same settings Uses the settings from the base case load flow for the contingency case load
flow.

Allow different settings Allows different settings for the base case load flow and the contingency
case load flow.

Calculation Settings

Base Case Load Flow Only available when option Allow different settings is selected in the Base
Case versus Contingency Load Flow section of the Multiple Time Phases tab. This is a reference
to the load flow command used to calculate the network operational point before the simulation of
contingencies. The settings of this load flow command can be edited by pressing the button.

Contingency Load Flow Only available when option Allow different settings is selected in the
Base Case versus Contingency Load Flow section of the Advanced Options tab. This is a
reference to the load flow command used to assess the network in contingency situations. It
is characterized by the Post Contingency Time, which is defined in the Post Contingency Time
field, also located in the Calculation Settings section of the dialogue. The contingency load flow
command referred to by the Contingency Load Flow is always stored inside the contingency
analysis command itself. The settings of this load flow command can be edited by pressing the
button. The Contingency Load Flow command settings can be set to those of the currently
used by the Base Case Load Flow command by pressing the button.

Note: If no ’Contingency Load Flow’ command is defined, the ’Base Case Load Flow’ command is
used to asses the network under contingency situations. In this case the action of automatic
transformer tap changers and switchable shunt compensators is directly considered (provided
that the corresponding options are selected in the ’Basic Options’ page of the assigned load flow

DIgSILENT PowerFactory 15, User Manual 663

CHAPTER 29. CONTINGENCY ANALYSIS

command).

Consider Specific Time Phase Only available when option Use same settings is selected in the
Base Case versus Contingency Load Flow section. This option must be enabled to define a post
contingency time.

Post Contingency Time (End of Time Phase) This value defines the time phase of the contin-
gencies. This means that all switch-open events with an event time less than or equal to this are
considered in the contingency.

29.4.4 Time Sweep

The Time Sweep settings shown in Figure 29.4.5 allow the automatic modification of the date and time
of the active Study Case according to a list predefined by the user. The advantage of this option is
in situations where the contingency analysis needs to be automatically performed taking into account
different system conditions such as considering several load and generation profiles (according to the
hour of the day).

Figure 29.4.5: Time Sweep Option Setting of the Contingency Analysis Command

Note: When enabled, the Time Sweep will automatically change the Date and Time of the active Study
Case. However, in order for the Study Case to activate the corresponding scenario automatically,
a Scenario Scheduler (IntScensched) object needs to first be created and afterwards activated.
Once the execution of the contingency analysis has finished, the Study Case date and time is
restored to its original setting. For more information on the Scenario Scheduler please refer to
Chapter 14(Operation Scenarios)

To add study times to the list, first enable the Calculate Time Sweep option, then right-click anywhere in
the table and select Insert Rows (alternatively select Append Rows or Append n Rows). To modify the
date and time, double-click on the corresponding Study Time cell. Additionally, the user has the option

664 DIgSILENT PowerFactory 15, User Manual

 29.4. THE SINGLE TIME PHASE CONTINGENCY ANALYSIS COMMAND

to ignore previously defined Study Times by enabling the Ignore flag. This ensures that the contingency
analysis will not take into account the ignored Study Times in the calculation.

29.4.5 Advanced Options

Handling of busbar fault

Open both local and remote breakers For a bus fault, not only all local breakers which are
directly connected to this bus, but also relevant remote breakers will be opened to isolate this bus
and isolate the connected branches. Open local breakers only Only the local breakers, which
are directly connected to this bus will be opened to isolate this fault..

Restricted Recording of Contingencies Results

Do not record contingency result if base case is above. . . If in the pre-fault load flow elements
have loadings above this value, then they are not recorded in the results.

Output per Contingency Case

Short Displays only the number of iterations required for each contingency case.

Detailed Displays the full load flow output per contingency case.

Consider Predefined Switching Rules of Substations If this option is selected, predefined

switching rules which describe switching actions for different fault locations will be considered.
For more information on Switching Rules, please refer to Chapter 9, Section 9.2.6.

Criteria for AC Recalculation of Critical DC Cases If the calculation method DC Load Flow +
AC Load Flow for Critical Cases is selected, the recalculation of critical DC cases using the AC
load flow method is performed whenever:

1. The maximum loading of a component is greater than or equal to the first value specified; for
example 100% (parameter name: maxLoadAbs); or
2. The maximum loading of a component is greater than or equal to the second value specified;
for example 80% (parameter name: maxLoad) and the maximum relative change of loading
compared to the base case is equal to or greater than the value specified; for example 5%
(parameter name: stepLoad).

In addition to these settings, if required, the user can define a set of components to be ignored
in the AC recalculation or to ignore components if they are already overloaded in the base case.
This set of components is assigned via the Components to be ignored field.

DIgSILENT PowerFactory 15, User Manual 665

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.4.6: Advanced Options Settings of the Contingency Analysis Command

29.4.6 Parallel Computing

There are two types of settings associated with the Parallel Computing option. The first and more
general group of settings are the ones related to the management of the parallel computation function
(computing method and the assignments of slaves). To access and modify these settings; log-on first as
an administrator and afterwards open a Data Manager window. Locate and edit the Parallel Computing
Manager (\System\Configuration \Parallel Computation \) as indicated in Figure 29.4.7.

The users can however define their own settings by creating a system folder (with key "Parallel") under
the folder "\\Configuration" and then creating the setting object ComParalman. This can only be carried
out when logged on as administrator.

The available options are:

Master Host Name or IP Refers to the machine name or IP address of the master host. If a local
multi-core machine is used, the name "localhost" can be used.

Parallel Computing Method

1. Local Machine with Multi Cores/Processors: All the slaves will be started in the local machine.
2. Local Machine Plus Remote Machines: The slaves will be started in both the local and remote
machines.

Number of Slaves Defines the number of slaves that will be started in the local machine. This
number should not be greater than the number of cores available in the local machine.

666 DIgSILENT PowerFactory 15, User Manual

 29.4. THE SINGLE TIME PHASE CONTINGENCY ANALYSIS COMMAND

Computer Group Specifies the link to a computer group (number of remote machines) which will
be used for parallel computing.

Figure 29.4.7: Parallel Computing Manager

The second group of settings are the ones related to the execution of the contingency analysis; and
which are located in the Parallel Computing page of the contingency analysis command (Figure 29.4.8).

Enable Parallel Contingency Analysis for AC, DC or Time Sweep If the corresponding option
is enabled, the contingencies will be calculated in parallel; otherwise the contingency analysis is
executed in its default mode (i.e. sequential calculation).

Minimum Number of Contingencies The parallel contingency analysis will be started only if the
number of contingencies is greater than this setting.

Package Size for Optimized Method and Package Size for Standard Method The master
distributes the contingencies to slaves per package. The package size indicates how many
contingencies will be calculated by a slave each time. The contingencies can be calculated
using either optimized method or standard method. As the standard method is much slower than
optimized method, the package size of the standard method should be smaller than that used for
the optimized method to balance the calculation.

DIgSILENT PowerFactory 15, User Manual 667

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.4.8: Parallel Computing Settings of the Contingency Analysis Command

29.4.7 Calculating an Individual Contingency

To calculate an individual contingency, click on the Show button in the contingency analysis command
dialogue (see Figure 29.4.2) to open the list of contingencies included in the analysis. From here the
user can right-click on a contingency of interest, and select Execute from the context sensitive menu.
Additionally, the corresponding element can be marked in the single line graphic by right-clicking on the
contingency object in the list and selecting Mark in Graphic from the context sensitive menu.

29.4.8 Representing Contingency Situations

Contingency Cases

Contingency cases (ComOutage objects) are objects used in PowerFactory to define contingency sit-
uations within the analyzed networks. A contingency case determines which components are put on
outage. When a contingency analysis (ComSimoutage) is executed, the contingency analysis command
considers each of the contingency cases stored inside it, taking the corresponding components out of
service and performing a contingency load flow.

As mentioned previously, the contingency cases used by a specific contingency analysis command are
stored inside the command itself. Contingency cases are created either by using Fault Cases and/or
Fault Groups (see Section 29.6), or via the Contingency Definition command ( , see Section 29.7).
Once the contingencies have been defined in the contingency command, the cases can be viewed
by using the Show button available in the dialogue (see Figure 29.4.2). Additionally, the contingency
cases within the active study case’s contingency analysis command may be viewed by clicking on
the Show Contingencies icon ( ), located on the main toolbar (only available when the Contingency
Analysis toolbar is selected). In both cases a new data browser showing the defined contingencies
is opened, with the contingencies listed inside. By double-clicking on a contingency from the list, the
corresponding dialogue for that particular contingency is opened (as illustrated in Figure 29.4.9). The
dialogue displayed in Figure 29.4.9 shows the following fields:

Name Name of the contingency case.

Not Analyzed If enabled, the case is not considered by the contingency analysis command.

Number An identification number given to the contingency and which is stored in the results.
This number can be used for reporting purposes.

668 DIgSILENT PowerFactory 15, User Manual

 29.4. THE SINGLE TIME PHASE CONTINGENCY ANALYSIS COMMAND

Fault Case Reference to the fault case (if any) from where the contingency case originated.

Fault Group Reference to the fault group (if any) from where the contingency case originated.
This field is only available if the contingency case has an associated fault group.

Events Used for this Contingency (Multiple Time Phase only) As showed in figure 29.4.10,
the user can specify wether to generate the events based on the fault case definition (automati-
cally), or to use locally defined events. If the user chooses to use locally defined events, then the
ComOutage object which defines the contingency (located in contingency command of the study
case) can be modified independently.

Interrupted Components This is a table showing the components put on outage by the contin-
gency case. The table, which is read-only, is automatically generated when the contingency case
is created.

Fault Type Displays the fault type and the contingency order. See Figure 29.6.1.

Contingency Analysis Reference to the contingency analysis command where the contingency
case is stored.

The Mark in Graphic button highlights the interrupted components in the single line diagram.

Figure 29.4.9: Contingency Cases (ComOutage objects)

DIgSILENT PowerFactory 15, User Manual 669

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.4.10: Contingency Cases (ComOutage objects for Multiple Time Phase)

Normally, contingency cases (ComOutage objects) are analyzed by the contingency analysis command
(ComSimoutage) in which they are stored. However, each contingency case provides the functionality
of a command itself, and can be executed individually using the Execute button at the top right of the
ComOutage dialogue. In this case the actions taken by the circuit breakers, which must switch to clear
the fault, are shown in the single line graphic (only if the contingency case was created using fault
cases/groups).

Note: The ’Interrupted Components’ table is updated by the program each time the contingency anal-
ysis is executed.

For further information on contingency cases generated using fault cases and/or fault groups, please
refer to Section 29.6 (Creating Contingency Cases Using Fault Cases and Groups). For information
on contingency cases created using the Contingency Definition (ComNmink ) command, please refer to
Section 29.7 (Creating Contingency Cases Using the Contingency Definition Command).

29.5 The Multiple Time Phases Contingency Analysis Command

As explained in Section 29.3 (Executing Contingency Analyses), the multiple time phases contingency
analysis is executed with the same contingency analysis command (ComSimoutage) as that used for
the single time phases contingency analysis. In the multiple time phases configuration it determines the
initial operational condition of the system via a ’base’ load flow calculation. Following this, it loops over
the defined time phases for each stored contingency (ComOutage object). Load flow calculations are
performed which consider the contingency events whose time of occurrence is earlier than, or equal to,
the Post Contingency Time, which is set in the corresponding load flow command.

As a result of the execution of the Contingency Analysis command, the steady-state operational point
of the network at the Post Contingency Time, for every contingency, is obtained. The calculated results

670 DIgSILENT PowerFactory 15, User Manual

 29.5. THE MULTIPLE TIME PHASES CONTINGENCY ANALYSIS COMMAND

are filtered according to user defined criteria and recorded in the Results (ElmRes) object referred to by
the Contingency Analysis command.

When configured to perform contingency analysis with multiple time phases, the Contingency Analysis
command stores the contingencies to be analyzed within the command itself. If different settings for
the contingency load flow are stated, a folder (named Time Phases) is also stored within the command;
this folder contains the load flow commands that define the time phases. The user may define as many
contingencies and time phases as required, following the procedures explained in this section.

The Contingency Analysis command can be accessed via the main toolbar by clicking on the icon
(provided that the Contingency Analysis toolbar has already been selected). The following subsections
present the options available in the dialogue provided that the user has selected the Multiple Time
Phases method in the contingency command (Multiple Time Phases tab).

29.5.1 Basic Options

Calculation Method

This setting is configured as described for Single Time Phase operation. Please refer to Section 29.4.1
(Basic Options). Only AC Load Flow Calculation and DC Load Flow Calculation methods are available
(no DC Load Flow + AC Load Flow for Critical Cases).

Limits for Recording

This setting is configured as described for Single Time Phase operation. Please refer to Section 29.4.1
(Basic Options).

Contingencies

This setting is configured as described for Single Time Phase operation. Please refer to Section 29.4.1
(Basic Options).

Results for AC/DC

This setting is configured as described for Single Time Phase operation. Please refer to Section 29.4.1
(Basic Options).

29.5.2 Effectiveness

These options are only available for the Single Time Phase calculation. Please refer to Section 29.4.2
(Effectiveness).

29.5.3 Multiple Time Phases

The Multiple Time Phases tab, as shown in Figure 29.5.1, allows the selection of the contingency
method as well as its corresponding settings. Although most of the setting descriptions are similar to
those given for the Single Time Phase method, they are reviewed here.

DIgSILENT PowerFactory 15, User Manual 671

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.5.1: Multiple Time Phases Option Settings of the Contingency Analysis Command (Multiple
Time Phases Method)

Method

Single Time Phase Performs the contingency analysis for a single time phase.

Multiple Time Phase Performs the contingency analysis for a multiple time phases, allowing the
definition of post-fault actions.

Base Case versus Contingency Load Flow

Use same settings Uses the settings from the base case load flow for the contingency case load
flow.

Allow different settings Allows different settings for the base case load flow and the contingency
case load flow.

Calculation Settings

Load Flow Only available when option Use same settings is selected in the Base Case versus
Contingency Load Flow section of the Advanced Options tab. This is a reference to the load
flow command used to calculate both the network operational point before the simulation of
contingencies, and the contingency load flow(s). The settings of this load flow command can
be edited by pressing the button.

Allow different settings Only available when option Allow different settings is selected in the
Base Case versus Contingency Load Flow section of the Advanced Options tab. This is a
reference to the load flow command used to calculate the network operational point before the
simulation of contingencies. The settings of this load flow command can be edited by pressing
the button.

Time Phase n

Lists the defined time phase(s). The button next to each time phase can be used to remove the
corresponding time phase. If the option Allow different settings has been selected on the Advanced
Options tab, the Time Phase will have its corresponding load flow accessible by pressing the button
next to the defined time phase.

672 DIgSILENT PowerFactory 15, User Manual

 29.5. THE MULTIPLE TIME PHASES CONTINGENCY ANALYSIS COMMAND

Add Time Phase Opens an input dialogue to define the new time phase by entering its Post
Contingency Time. If the option Allow different settings has been selected on the Advanced
Options tab, the previous load flow settings (i.e. those with the preceding occurrence in time) will
be used for the new time phase. In the case that there is no previous time phase load flow, the
base case settings will be used for the new time phase.

Use Base Case Settings for All Copies the settings from the base case load flow to all time
phase load flows.

Post contingency time for order identification

The order of the contingencies stored inside the command is calculated according to the time defined in
this field. Only the events (actions) taking place before this point in time are considered when calculating
the contingency order.

Note: In PowerFactory a region is defined as a set of topologically connected components. A region is

interrupted if it is energized (topologically connected to a network reference bus) before a fault and
de-energized afterwards. The order of a contingency corresponds to the number of interrupted
regions at the time of its calculation (i.e. the ’Post contingency time for order identification’).

29.5.4 Time Sweep

This option is only available for the Single Time Phase calculation. Please refer to Section 29.4.4 (Time
Sweep).

29.5.5 Advanced Options

This setting is configured as described for Single Time Phase operation. Please refer to Section 29.4.5
(Advanced Options).

29.5.6 Parallel Computing

This option is only available for the Single Time Phase calculation. Please refer to Section 29.4.6
(Parallel Computing).

29.5.7 Defining Time Phases for Contingency Analyses

The time phases of a contingency analysis are defined in the Calculation Settings section of the Multiple
Time Phases page of the Contingency Analysis command, by specifying a Post Contingency Time for
each defined time phase. A specified Post Contingency Time defines the end of a time phase and is
used to determine which events (actions) from the analyzed contingency are considered. If the time of
occurrence of an event from a contingency occurs earlier than or equal to the Post Contingency Time,
the event will be considered in the corresponding load flow calculation.

Each defined time phase uses a corresponding load flow calculation, and by default, this is the same
load flow calculation as that used for the base case load flow. If the option Allow different settings in
the Base Case versus Contingency Load Flow section of the Multiple Time Phases page is selected,
the user can define individual load flow commands for each time phase, as illustrated in Figure 29.5.2.
Access to each load flow command and its settings is via the button.

DIgSILENT PowerFactory 15, User Manual 673

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.5.2: Different Settings for Base Case and Contingency Load Flows

Note: Transformer tap changer controllers and switchable shunts are only considered by a time phase
if their time constants are smaller than the current Post Contingency Time. The operational
thermal ratings of branch elements during a contingency (if ’short term’ thermal ratings (see
Section 12.3.7) have been defined) will also depend on the duration of the contingency (i.e. the
current Post Contingency Time).

The Contingency Analysis time phases (which are essentially just load flow commands) are stored
within a folder inside the ComSimoutage command and can be accessed in several ways. One way is
by clicking on the button next to each defined time phase in the Calculation Settings section of the
Multiple Time Phases tab; by doing so, the edit dialogue of the corresponding load flow command pops
up.

Another way is through the Data Manager. After performing a contingency analysis, a contingency
command object (ComSimoutage) is created inside the current active Study Case. If the contingency
analysis was performed using the Multiple Time Phases method (with different load flow settings), then
a Time Phases folder with the corresponding time phase load flow commands will be created inside the
contingency analysis, as illustrated in Figure 29.5.3.

Figure 29.5.3: Location of the Time Phases Folder

New time phases can be defined in the data browser by clicking on the Add Time Phase button. Existing
time phases can be deleted using the button. Note that after several time phases have been defined,

674 DIgSILENT PowerFactory 15, User Manual

 29.5. THE MULTIPLE TIME PHASES CONTINGENCY ANALYSIS COMMAND

this list is then scrollable using the up/down arrow buttons ( ) available in the dialogue.

29.5.8 Representing Contingency Situations with Post - Fault Actions

Contingency situations which include post-fault actions are represented in PowerFactory via objects
called ’contingencies’ (ComOutage, ). The contingencies are defined by a set of events which
represent:

• Faults on the selected components;

• The switching actions carried out to isolate the faulty components; and
• The post contingency actions taken in order to mitigate the subsequent voltage band problems
and/or supply interruptions.

Contingencies are created based on fault cases defined in the Operational Library. These fault cases
define the location of the fault events, and may also define post contingency actions taken to isolate
the fault and mitigate the effects of the outage of the component(s). Whenever a new contingency is
created, a link from the ComOutage object to the fault case is set. New contingencies can be created
in a Contingency Analysis command by clicking on the Add Cases/Groups button in the Configuration
section of the Basic Data page (see Section 29.4.1: Basic Options).

Besides the events which are transferred from the linked fault case during calculation of the contingency
case, the user has the possibility of defining additional post contingency actions in the contingency by
manually creating new events.

The contingencies calculated in a Contingency Analysis, are stored inside the command itself and
can be accessed using the Show button (see Figure 29.4.2). Alternatively, the contingencies in the
Contingency Analysis command contained in the active study case can be viewed by clicking on the
Show Contingencies icon ( ) on the main toolbar. In both cases a new data browser listing the defined
contingencies is shown. By double-clicking on a selected item from the list, the edit dialogue of the
corresponding contingency (Figure 29.4.9) pops up.

Normally, contingency cases are analyzed by the Contingency Analysis command in which they are
stored. However, each case provides the functionality of a command and can be executed individually
using the Execute button at the top right of the ComOutage dialogue (see Figure 29.4.9). In this case,
all of the time phases are executed for the selected contingency considering its associated events. The
results observed in the single line graphic correspond to those from the last time phase, including the
final states of the network switches.

The events that define a contingency can be displayed in a list format in a new data browser by pressing
the Events button in the fault case (IntEvt) dialogue (as shown in Figure 29.6.3). This data browser
can be used to edit and/or delete the listed events. New events can be created by using the New
icon at the top of the opened browser window. Only four different types of events are allowed in the
contingency analysis as post-fault actions, which are:

• Load Event (EvtLod)

• Dispatch Event (EvtGen)
• Switch Event (EvtSwitch)

• Tap Event (EvtTap)

It should be noted that events created locally in the contingency object are only considered if the
ComOutage option Use locally defined events (User defined) is selected in the Events Used for this
Contingency field.

DIgSILENT PowerFactory 15, User Manual 675

CHAPTER 29. CONTINGENCY ANALYSIS

The Start Trace button ( ) (available on the main toolbar) can be used to follow the behaviour of
the system over time. When this button is pressed, a dialogue opens allowing the user to select a
contingency. Following the selection of a contingency by the user and pressing OK, the contingency
dialogue is closed and the base case load flow is executed. The execution of the first event(s) and all
subsequent event(s) is initiated by pressing the Next Time Step button ( ) on the main toolbar. At each
time step the load flow calculation results and the state of the network circuit breakers are displayed
in the single line graphic. It should be noted that the Next Time Step evaluates events according
to their time of occurrence, and not according to the time phases defined in the Contingency Analysis
command. After the last time event(s) have been executed, the Next Time Step button becomes inactive.
The Stop Trace button ( ) can be pressed to clear the calculation. Alternatively, the Trace button in
each ComOutage dialogue can be used to initiate the Trace for that particular contingency.

Note: The ’Trace’ functionality can be started directly from the main toolbar by pressing the Start Trace
button ( ). In this case a data browser listing all available contingencies (i.e. those stored inside
the ’Contingency Analysis’ command of the active study case) is displayed. After the user selects
the desired contingency by double-clicking on it, the ’Base Case’ load flow is executed. The
subsequent event(s) are then calculated using the Next Time Step button.

29.6 Creating Contingency Cases Using Fault

Cases and Groups

Contingency cases created from fault cases can be regarded as contingency situations produced in
a network as a consequence of the clearing of a fault. Fault cases without switching events (created
following the procedure described in Chapter 12: Project Library, Section 12.3.3: Fault Cases and Fault
Groups) are used to automatically generate contingency cases in the contingency analysis command,
by pressing the Add Cases button and selecting the desired objects from the data browser that pops
up.

For every selected fault case, the calculation automatically detects which circuit breakers must open
in order to clear the defined fault(s). All components which lose their connection to the network
reference bus following the switching actions that clear the fault(s), are regarded as ’interrupted’ and
are subsequently added to the Interrupted Components table of the corresponding contingency case.
In other words, these components are put on outage by the contingency case. Depending on the fault
defined in the fault case that generates a contingency, the Fault Type field in the contingency case
dialogue (Figure 29.6.1) is set to:

• Busbar fault:
If the contingency originates from a fault on a busbar
• n-k fault:
With contingency order equal to k (where k >= 0). k corresponds to the number of network
regions (sets of topologically connected components) which are disconnected during a fault, by the
switching actions performed. It should be noted that the switching actions which are considered
depend on the post contingency time used by the update (this time differs between single- and
multiple time phase analyses).

Figure 29.6.1: Fault Type Field in the Contingency Case (ComOutage) Dialogue

676 DIgSILENT PowerFactory 15, User Manual

 29.6. CREATING CONTINGENCY CASES USING FAULT
CASES AND GROUPS

Note: In PowerFactory an interrupted component is a network primary element that is energized before
a fault and de-energized afterwards. A component is considered to be energized if it is topologi-
cally connected to a network reference bus. A region is defined as a set of topologically connected
components. Like components, regions can have energized, de-energized and interrupted states,
depending on their connection to a network reference bus.

Contingency cases can be created from fault cases/groups, which reside in the Operational Library, by
pressing the Add Cases/Groups button in the contingency analysis command (see Section 29.4.1 (Ba-
sic Options) and Figure 29.4.2). In the case of creating contingencies from fault group(s), a contingency
case will be generated for each fault case referred to in the selected fault group(s).

Note: The ’topological search’ algorithm used by the program to set contingency cases from fault cases
requires the explicit definition of at least one reference bus in the analyzed system. A bus is
explicitly set as a reference if it has connected to it either a synchronous generator (ElmSym), or an
external grid (ElmXnet) with the option ’Reference Machine’ enabled (available on the element’s
’Load Flow’ tab).

29.6.1 Browsing Fault Cases and Fault Groups

There are two types of subfolder inside the Faults folder in the Operational Library : Fault Cases and
Fault Groups.

Figure 29.6.2: Contents of the Faults folder in the Operational Library

In order to make a new folder of either of these types, left-click on the Faults folder icon ( ) and then
press the New Object button ( ) on the Data Manager toolbar. In the drop-down list, select whether a
new Fault Cases or Fault Groups folder should be created.

The Fault Cases folder holds every contingency (n-1, n-2, or simultaneous) defined for the system, as
described in Section 29.6.2 (Defining a Fault Case). Alternatively, several fault cases can be selected
and stored in a Fault Group, as described in Section 29.6.3 (Defining a Fault Group).

29.6.2 Defining a Fault Case

To define a fault case for an element in the grid, select it in the single-line diagram. Then right-click and
choose one of: Define. . . → Fault Case→ Single Fault Case or Define. . . → Fault Case→ Multiple Fault

DIgSILENT PowerFactory 15, User Manual 677

CHAPTER 29. CONTINGENCY ANALYSIS

Cases, n-1 (or Multiple Fault Cases, n-2) or Define. . . → Fault Case→ Mutually Coupled Lines/Cables,
n-k.

If Multiple Fault Cases, n-2 is selected, fault cases will be created for the simultaneous outage of every
unique combination of two elements in the selection. If the user selects Single Fault Case, a fault case
will be created for the simultaneous outage of all elements in the selection.

If Mutually Coupled Lines/Cables, n-k is selected, then fault cases will be created for the simultaneous
outage of each coupled line in the selection.

Alternatively, a filter can be used. This can be done (for example) with the help of the Edit Relevant
Objects for Calculation button ( ), to list all elements for which outages are to be defined. These
elements can then be highlighted and the user can then right-click on the highlighted selection and
choose (for example) Define. . . → Fault Case. . . . The Simulation Events/Fault dialogue opens, as
shown in Figure 29.6.3, where the user can enter the desired name of the fault case in the Name field.

On the Advanced tab of the Basic Data page of the same dialogue, the user can create the correspond-
ing switch events, by clicking on the Create Switch Events button.

Figure 29.6.3: Creation of Fault Case (IntEvt)

Fault cases can also be defined by the Contingency Definition command, as explained in Section 29.7
(Creating Contingency Cases Using the Contingency Definition Command).

For further background on fault cases, please refer to Chapter 12: Project Library, Section 12.3.3 (Fault
Cases and Fault Groups).

29.6.3 Defining a Fault Group

To define a fault group, left-click on the Fault Groups folder. Then click on the New Object button ( ).
A Fault Group dialogue pops up as shown in Figure 29.6.4. In this dialogue the user can specify the
name of the fault group in the Name field, and add fault cases to this new group using the Add Cases
button. Click the Cases button to view existing cases (if any) in the fault group.

Figure 29.6.4: Creation of Fault Group (IntFaultgrp)

678 DIgSILENT PowerFactory 15, User Manual

 29.7. CREATING CONTINGENCY CASES USING THE
CONTINGENCY DEFINITION COMMAND

Note: When a fault group is defined and fault cases are added to it, a reference is created to each of
these fault cases. The fault case itself resides in the Fault Cases subfolder. This means that if an
item in the fault group is deleted, only the reference to the fault case is deleted. The fault case
itself is not deleted from the Fault Cases subfolder.

29.7 Creating Contingency Cases Using the

Contingency Definition Command

The Contingency Definition command (ComNmink ) is used to automatically generate contingency cases
based on selected components. It is accessible via the Contingency Analysis toolbar ( ) but using the
button. The Contingency Definition command can be used to automatically generate contingency
cases for either (i) a user-defined selection of elements; or (ii) pre-defined sets of elements. These two
approaches are now described.

To generate contingency cases for a user-defined selection of elements:

• Select the components to be put on outage either by multi-selecting them in the single line graphic
or the Data Manager.
• Right click on the selection and choose Calculate → Contingency Analysis. . . from the context
sensitive menu. This command will create a list with references to the selected objects inside the
Contingency Definition command (ComNmink ). The command dialogue shown in Figure 29.7.1
will pop up.
• Select the required outage level.
• Select the Creation of Contingencies option according to how the contingencies should be handled
(see explanation of options below) and click on Execute.

To generate contingency cases for either the complete system or from pre-defined sets of elements:

• Click on the icon on the main toolbar to open the command;

• Select the option Whole System in the Create Cases for field;

• Select the required pre-defined set of elements (for example transformers and lines);
• Select the Creation of Contingencies option according to how the contingencies should be handled
(see explanation of options below) and click on Execute.

DIgSILENT PowerFactory 15, User Manual 679

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.7.1: Contingency Definition Dialogue (option: Generate Contingencies for Analysis)

Once the Contingency Definition command is executed, it generates the corresponding contingency
cases according to the options and elements selected. The Contingency Analysis command, which is
automatically created inside the current active Study Case is then automatically opened. The created
contingencies can be analyzed by executing this already-opened Contingency Analysis command. Note
that when a new list of contingencies is created using the Contingency Definition command, the previous
content of the contingency analysis command is overwritten.

It is also possible to open the Contingency Definition command directly from the Contingency Analysis
toolbar, without any previous selection, by clicking on the icon. In this case, contingencies for all
elements within the network (selected according to their class, as described below), can be created.

The Contingency Definition command offers the following options to generate contingency cases from
the selected objects:

Creation of Contingencies

Generate Fault Cases for Library Generates fault cases which are stored in the Operational
Library, in a folder named Faults.

Alarm Generates contingencies which are stored in the contingency analysis command, and
then opens the contingency analysis command (ComSimoutage) dialogue.

Outage Level

n-1 Creates single contingency cases for each of the selected components.

n-2 Creates contingency cases for every unique combination of two selected components.

n-k cases of mutually coupled lines/cables Creates contingency cases for every set of mutu-
ally coupled lines/cables. If for example, three lines are modelled as having a mutual coupling,
by selecting this option a fault case is created considering the simultaneous outage of the three
coupled lines.

Lines/cables

Contingency cases according to the selected outage level will be generated for all lines and cables

680 DIgSILENT PowerFactory 15, User Manual

 29.8. COMPARING CONTINGENCY RESULTS

(ElmLne objects) in the system.

Transformers

Contingency cases according to the selected outage level will be generated for all transformers (ElmTr2,
ElmTr3 objects) in the system.

Generators

Contingency cases according to the selected outage level will be generated for all synchronous gener-
ators (ElmSym objects) in the system.

Series Capacitors

Contingency cases according to the selected outage level will be generated for all series capacitors
(ElmScap objects) in the system.

Series Reactors

Contingency cases according to the selected outage level will be generated for all series reactors
(ElmSind objects) in the system.

The selection of elements to outage in the Contingency Definition command can also be created by the
use of DPL scripts. Please refer to the ComNmink methods in the appendix DPL Reference.

Note: It is important to note the difference between contingency cases created from fault cases and
contingency cases created with the Contingency Definition command. In the former, the cases
are regarded as the outage of certain network components as a consequence of fault clearing
switching actions, with the fault(s) being defined by the fault case and the switching actions
automatically calculated by the program. In the latter, the cases are regarded as contingency
situations generated by the outage of a selected group of components.

29.8 Comparing Contingency Results

In order to compare contingencies in a fast and easy way, PowerFactory provides a Contingency Com-
parison function ( ). The Contingency Comparison function is only enabled if the user has previously
defined the contingency cases in the Contingency Analysis command, as explained in Sections 29.6
(Creating Contingency Cases Using Fault Cases and Groups) and 29.7 (Creating Contingency Cases
Using the Contingency Definition Command). The general handling of the Contingency Comparison
function is as follows:

1. Define the contingency cases in the Contingency Analysis command (see Sections 29.6: Creating
Contingency Cases Using Fault Cases and Groups and 29.7: Creating Contingency Cases Using
the Contingency Definition Command).
2. Click on the Contingency Comparison button ( ). A window will pop up allowing the user to select
the required contingency cases (Figure 29.8.1). The selection can correspond to one, several, or
all contingency cases.

DIgSILENT PowerFactory 15, User Manual 681

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.8.1: Selection of Contingency Cases for Comparison

3. By clicking on the OK button, the Comparing of Results On/Off button (Figure 29.8.2) is enabled
and the selected contingency cases are automatically executed.

Figure 29.8.2: Comparing of Results Button

4. The single line graphic result boxes will display the results, based on the comparison mode and
the two compared cases. By default, the comparison is made between the Base Case and the
last selected contingency case in the list.

5. To change the comparison mode and/or the cases to be compared, click on the Edit Comparing of
Results button (Figure 29.8.2). The Compare dialogue will pop up displaying the current settings.
To change the cases to be compared, click on the black arrow pointing down ( ) and select a
different case (Figure 29.8.3).

682 DIgSILENT PowerFactory 15, User Manual

 29.9. RESULT ANALYSIS

Figure 29.8.3: Selection of other Cases for Comparison

6. If the contingency analysis is defined with time phases, the compare dialogue will have the option
of selecting the time phase.
7. Once the calculation is reset (for example by either making changes in the model or by clicking on
the Reset Calculation button), the comparison mode will be disabled.

29.9 Result Analysis

29.9.1 Predefined Report Formats (Tabular and ASCII Reports)

In PowerFactory the Contingency Analysis function has a special set of predefined report formats
that can be launched by clicking on the Report Contingency Analysis Results button ( ), which is
illustrated in Figure 29.8.2. The Report Contingency Analysis Results button will only be enabled if
the user has previously executed the Contingency Analysis command, as explained in Section 29.3
(Executing Contingency Analyses). Once the reporting of results has been launched, the dialogue
window illustrated in Figure 29.9.1 will be displayed.

DIgSILENT PowerFactory 15, User Manual 683

CHAPTER 29. CONTINGENCY ANALYSIS

Figure 29.9.1: Contingency Analysis Reports Dialogue

The following types of report can be selected:

• Maximum Loadings:
Only the maximum loaded component (according to the specified loading limit) for each contin-
gency is displayed in a single list.

• Loading Violations:
All overloaded components (according to the specified loading limit) for each contingency are
displayed in a single list.
• Voltage Steps:
All voltage deviations of terminals (between the base case and the contingency case) for each
contingency are displayed in a single list. Reports the highest voltage deviation of terminals
(between the base case and the contingency case) considering all contingencies. Any such
terminal is reported only once. Only terminals with the highest voltage deviation greater than
the specified maximum voltage step are reported.
• Maximum Voltages:
Reports the greatest voltage violation of a terminal (greater than or equal to the specified voltage
limit) considering all contingencies. Any such terminal is reported only once (i.e. it is reported for
the contingency causing this violation).
• Minimum Voltages:
Reports the greatest voltage violation of a terminal (less than or equal to the specified voltage
limit) considering all contingencies. Any such terminal is reported only once (i.e. it is reported for
the contingency causing this violation).
• Maximum Voltage Violations:
Reports all voltage violations of a terminal (greater than or equal to the specified upper voltage
limit) considering all contingencies.

• Minimum Voltage Violations:

Reports all voltage violations of a terminal (less than or equal to the specified lower voltage limit)
considering all contingencies.

684 DIgSILENT PowerFactory 15, User Manual

 29.9. RESULT ANALYSIS

• Loading Violations per Case:

All overloaded components (according to the specified loading limit) for each contingency are
displayed in separate lists (i.e. one list per contingency case).

• Voltage Violations per Case:

All busbars with exceeding voltage (maximum or minimum) are displayed in separate lists.
• Generator Effectiveness:
Generators having an effectiveness greater than or equal to the specified value (%) are displayed
in a single list.

• Quad-Booster Effectiveness:
Quad-booster transformers having an effectiveness greater than or equal to the specified value
(MW/Tap) are displayed in a single list.
• Non-convergent Cases:
The non-convergent cases of the contingency analysis are displayed in a list.

Figure 29.9.2: Tabular Report of Loading Violations

The tabular format (Figure 29.9.2) for reporting has the following sections:

• Header:
Identifies the report and its data.
• Filter:
Represented as drop-down lists, allowing the selection of one item at a time or as "Custom".

• Table:
Matrix of rows and columns containing cells that can refer to an object and provide actions such as
"Edit", "Edit and Browse" and "Mark in Graphic". It also supports copy and paste, scroll features,
page up and down keys as well as Ctrl+Pos1, Ctrl+End and HTML view.

DIgSILENT PowerFactory 15, User Manual 685

CHAPTER 29. CONTINGENCY ANALYSIS

After being executed, the Tabular Report can be exported as HTML format or exported directly to Excel,
by using the Select icon ( ).

Although the tabular reports are already predefined, the user can modify them if required (by going to
the second page of the Report Contingency Analysis Results dialogue and clicking on the blue arrow
pointing to the right of the Used Format definition).

686 DIgSILENT PowerFactory 15, User Manual