Dispatcher Power Flow: Functional Description

ABB
Dispatcher Power Flow

Functional Description
Document Number: 1KSE000375 Revision Index: B
Date: 2009-08-18 Network Manager Release: NM4
ABB Inc. Copyright © 2005 - 2011

Blank_P_UT_NM_ABB_External_Word, 1KUS001186D0107, B
Dispatcher Power Flow Document Number: 1KSE000375
Function Description Date: 2009-08-18 Revision Index: A
DOCUMENT APPROVAL
Author/Modifier: Magnus Johansson Date:
Technical Review: Date:
Quality Review: Gale Keenan Date: 2009-03-10
ABB Manager: Mani Subramanian Date: 2009-08-18
Customer Approval
Date:
(where applicable):
1
REVISION HISTORY
Document Changes
Date Rev Author/Modifier Description of Changes
2005-06-07 A/0.0 SOM050464 New document. All contents from
3AST 001 648 moved to TTT-
template without any changes of the
TM
functions. Trade Mark SPIDER
replaced by Network Manager.
2008-06-23 A/5.0 Niklas Faber Document converted to NM 5
template. Spell-check.
2009-03-10 A00 Gale Keenan Quality reviewed the document format
and sent for technical review.
2009-04-30 A Mani Approval
Subramanian
2009-08-18 B00 Carina Mårlind Removed reference
2009-08-18 B Mani Approval
Subramanian
1
Disclaimer: An absence of signatures signifies that this document has not been approved by ABB Inc. and is not considered a 'final' document.
Page ii
Total pages in entire document (including front matter): 23 ABB Inc. © 2005 - 2011
Table of Contents
Document Approval ................................................................................................ ii

Revision History ...................................................................................................... ii
List of Figures .......................................................................................................... iii
Preface ...................................................................................................................... v
Conventions ............................................................................................................. v
1 Overview .................................................................................................. 1
1.1 Introduction................................................................................................ 1
1.2 Interfaces................................................................................................... 2
1.3 Data Overview ........................................................................................... 4
1.4 Overview Diagram ..................................................................................... 5
2 Functional Description ........................................................................... 6
2.1 Dispatcher Power Flow (DPF)................................................................... 6
2.1.1 Functional Components ....................................................................... 6
2.1.2 Modeling Features ............................................................................... 7
2.1.3 Output Features ................................................................................... 8
2.1.4 Support................................................................................................. 8
3 User Interface .......................................................................................... 10
3.1 Index Displays ........................................................................................... 10
3.1.1 DPF Input Index (DPFIIDX) ................................................................. 10
3.1.2 DPF Output Index (DPFOIDX) ............................................................. 12
3.2 Execution Control Displays ....................................................................... 12
3.2.1 DPF Execution Display (DPFEXEC) .................................................... 12
4 Special Considerations .......................................................................... 15
4.1 Start-up/Switch Over Considerations ........................................................ 15
4.2 Data Engineering ...................................................................................... 15
5 Project Definition .................................................................................... 16
6 Design ...................................................................................................... 17
List of Figures
Figure 1 - Overview Diagram..................................................................................... 5
Page iii
Figure 2 - DPF Input Index (DPFIIDX) ...................................................................... 11
Figure 3 - DPF Output Index (DPFOIDX) .................................................................. 12
Figure 4 - DPF Execution (DPFEXEC) ...................................................................... 14
Page iv
PREFACE
Purpose
This specification describes the functionality of the Dispatcher Power Flow function.
Associated Documents
1KSE000377, Functional Description, State Estimator (WAA
1KSE000374, Functional Description, Security Analysis (WAA
1KSE000787, Detailed Description, Dispatcher Power Flow (WAB216)
1KSE000423, Operator's Manual, Dispatcher Power Flow (WAG121)
Conventions
The following text conventions are used in this document to distinguish between different
types of text. Refer to this section when clarification is needed to determine the proper
convention to use.
Item Convention Example

Buttons on screens First Letter uppercase, Save button
bold
Command lines, options Lowercase, 9 pt., Courier copy command
and parameters New /a option
Database table names All capitals, regular CUST_ORG
Icon and Tab names Initial capitals, italic Click the Microsoft Excel
icon.
Key names, key All uppercase CTRL, TAB,
combinations, and key CTRL+ALT+DEL, SHIFT+F7
sequences.
Menu commands Initial capitals, separated Select File > Save.
by >, bold. Select Format > Font >
Arial.
Menu names Bold, initial capitals Insert menu
Program code Lowercase, 9 pt., bold $ set def clc$cin
User input Usually lowercase Type -p password
depending on use. Also
bold or italic depending
on use.
Page v
Notes, Cautions, Warnings, and Tips

Notes, Cautions, Warnings, and Tips are used throughout this document to call attention to
information of special importance. The different circumstance where each of these is used is
described below.
A Note is used to indicate neutral or positive information that emphasizes or supplements

important points of the main text, to supply information that may apply only in special cases.
A Caution is used when system performance may be affected and of potential damage to
the equipment, data, or software.
A Warning is used to advise you when there is a potential for irreversible damage to the
data, hardware, or operating system or when taking or avoiding a specific action could result
in physical harm to you or the equipment.
A Tip helps apply the techniques and procedures described in the text to their specific
needs. A tip suggests alternative methods that may not be obvious and helps the user
understand the benefits and capabilities of the application.
Page vi
1 Overview
1.1 Introduction
The Dispatcher Power Flow subsystem performs Dispatcher Power Flow and
Off-Line Power Flow Interface functions.
• Dispatcher Power Flow (DPF)

The Dispatcher Power Flow executes the power flow studies, including: loss of
line(s), changes of generation(s), or bus load(s), and; changes of system or
area loads, for both analyzing the results as for provides a base case solution
for other applications. This subsystem can be initiated from any of the
Dispatcher Power Flow, State Estimator, or Security Analysis saved cases, a
flat start, or the solution of the most recent State Estimator execution. Two
power flow methods are provided: the Fast Decoupled method and the full
Newton-Raphson method. Logic is incorporated into both methods for
handling the common load flow adjustments.
Solutions can be performed with all the adjustments enforced, with none, or
with a subset of them. The one-line displays allow the entry of the circuit
breaker statuses and the tabular displays allow all other types of data entry,
such as transformer taps, unit related data, etc. The results can be seen
directly in the one-line displays, and tabular displays also present summarized
results of the power flow in a clear and simple format.
• Power Flow IEEE Common Format (PFIEEE)

This program will convert the power flow solution into the IEEE common
format.
• Tabular Output
This program will build the tabular output for DPF solution results for any
specified company and zone.
The function can be executed in the real-time database environment under the
control of the Application Monitor, within the following two sequences.
• Study Power Flow sequence (STPF)
• Real-Time Power Flow sequence (RTPF)

It can also be executed in the study database environment within the Study
Power Flow sequence.
Page 1
1.2 Interfaces
The Dispatcher Power Flow subsystem interfaces with the following EMS
subsystems.
• Application Monitor (NAC)
The Network Application Monitor controls the execution of all the above
subsystems. In the real-time database environment, DPF is executed both
as part of the real-time power flow (RTPF) and study power flow (STPF)
sequences. In the study database environment, DPF is executed as part
of the study power flow sequence. The input data is set up via this
function, which controls all the data retrieval and scheduling tasks.
• Schedule and Limit Retrieval (SSKD)
The Schedule and Limit Retrieval subsystem merges manually entered

data (required to prepare the Power Flow case) with time dependent data
retrieved from other subsystems (for a time/date selected by the user).
This time dependent data includes: adapted breaker status’s; load

distribution parameters; interchange and regulating voltages fetched from
the Network Parameter Update (NPU) subsystem; and overload and
voltage limits fetched from the Limit Manager subsystem. Schedule and
Limit Retrieval (SSKD) is executed within the study sequence.
• Telemetry Snapshot (SNP) and Status and Analog Retrieval (SAR)
Telemetry Snapshot (SNP) takes a snapshot of the current telemetry.
The Status and Analog Retrieval (SAR) subsystem coordinates various

power system data required by the Network Model Builder (NMB)
subsystem and the Dispatcher Power Flow (DPF) subsystem. SAR is the
counter part of SSKD in the real time sequence. Basically, SAR merges
the real-time measurements, real-time unit characteristics, the current
active set of limits and some of the user specified data. These values are
entered via MMI displays belonging to the NMB and DPF subsystems.
• Network Model Builder (NMB)
The Network Model Builder subsystem performs the Network Topology

function. It determines the current topology (bus model) of the network,
given the circuit breaker status data. NMB also identifies the electrical
networks in the power system. Efficient graph algorithms provide the
means of transforming the node-breaker-branch base data description
into the bus-branch description of the network. Dispatcher Power Flow
(DPF) uses the Network Topology model as input.
• Bus Scheduler (BSK)
The Bus Scheduler determines the load, regulation schedule, and unit
generation as input to DPF. It consists of the following components
Page 2
• Load Scheduler (LSKD)
The Load Scheduler distributes the system load into individual load values
based on the load distribution parameters. The system load can either be
entered by the user, or obtained from the main company net load forecast
fetched from the System Load Forecasting subsystem. Before execution
of the Load Scheduler, the user is free to override any of the distribution
coefficients using the displays. This component is the same as the one
described in the Network Model Functional Description.
• Regulation Scheduler (RSKD)
The Regulation Scheduler maintains the consistency of the desired bus

voltages. The company net interchange for all companies is also balanced
to zero.
• Unit Scheduler (USKD)
The Unit Scheduler performs an economic dispatch to obtain initial

conditions for the generator units. The unit scheduler obtains a realistic
generation pattern, based on the system load, specified interchange
requirements and estimated losses. This component is the same as the
one described in the Network Model Functional Description document.
• Security Analysis (SA)
The DPF subsystem provides the base case solution to the Security
Analysis subsystem in the both the real-time database and study
database environment.
• Optimal Power Flow (OPF)
The DPF subsystem provides the base case solution to the Optimal
Power Flow (OPF) subsystem in the real-time database and study
database environment.
• System Load Forecasting (SLF)
The System Load Forecasting subsystem provides the main company

load from schedules updated by the Network Parameter Update (NPU)
function. Retrieving the main company load from the Short-term Load
Forecast is optional.
• Outage Scheduler (OS)
The Outage Scheduler subsystem provides the list of out aged equipment.
• Saved Case Subsystem (SAV)
The Saved Case subsystem handles the saved case management

capabilities for DPF.
Page 3
1.3 Data Overview
The following list presents a brief description of the data components used by
the Dispatcher Power Flow subsystem.
• DPF Input/Output Files - Contains:
− all the input to run a base case power flow;
− any item that the user desires to change;
− the output generated by the run.

• Base Data - Contains nominal values of the Dispatcher
Power Flow Applications static input.
• Save Case Files - The save case file is used to initialize
the various parameters needed by these functions.
Page 4
1.4 Overview Diagram
Figure 1 gives an overview diagram of the Dispatcher Power Flow subsystem

within the study power flow sequence. The execution of Schedule and Limit
Retrieval (SSKD) is replaced by Telemetry Snapshot (SNP), followed by
Status and Analog Retrieval (SAR) for the real time power flow sequence. The
overview diagram for the real time sequence is not given here, as it is similar
to the one for the study sequence. The major functions and data flows are
described in the above sections.
STUDY POWER FLOW SEQUENCE

NPU
SSKD
LIM time
dependent
parameters
NMB
SLF LSKD
RSKD
MMI
USKD
SAV
Save Cases
DPF
Solved
Case
PFIEEE
Figure 1 - Overview Diagram
Page 5
2 Functional Description
2.1 Dispatcher Power Flow (DPF)
2.1.1 Functional Components
Dispatcher Power Flow Solution

The Dispatcher Power Flow is used to study the steady-state operation of a
power system under real-time or simulated conditions, and to provide a base
case solution for the other network application functions. The algorithm used
in the DPF is capable of processing network islands. In order to assure that all
practical systems can be solved, two methods are provided: the Fast
Decoupled method and the Newton’s method. The Fast Decoupled Load flow
requires less computer memory and far less execution time than the Newton’s
method for most problems. It may occasionally encounter problems of
convergence in the presence of high R/X line ratios. In such cases the
Newton’s method is more suitable. Logic is incorporated into both methods in
order to handle common load flow adjustments.
The available adjustments are listed below:
• Distributed Slack Power: The system slack active power is distributed

among the system generators, respecting generator MW limits and
islanding conditions. Conventional single system slack will be used if this
adjustment is not activated. Slack area to be used is specified within the
base data.
• Area Interchange Control: Net interchanges for each area or a group of

areas are controlled to meet their specified schedules. All generators in
each controlled area will be adjusted proportionally to allocate the area
interchange error.
• Transformer MW flow Control: Transformers with angle/out-phase tap can

be designated to control MW flows.
• Generator Q-limit Control: The MVAR limits of the controllable generators

are respected in the power flow solution process.
• Remote Voltage Control: Generators and synchronous condensers can be

specified to control the voltage of a remote bus.
• Transformer Tap Control: Transformers with voltage/in-phase tap can be

designated to control the local or remote bus voltage.
• Capacitor/Reactor Voltage Control: Regulating capacitors/reactors can be

used to maintain the voltage at the controlled bus within a range.
Page 6
• Static VAR Compensator (SVC) Control: The MVAR output of SVC is

proportional to the different between the referenced and the actual voltage
of the regulated local or remote bus.
Input Sources
The schedulers and the real time measurement retrieval, described in the
earlier sections, all help in the setting up of the initial conditions for the various
parameters needed in solving the power flow: Telemetry Snapshot (SNP) and
Status and Analog Retrieval (SAR) for Real Time Power Flow sequence, or
Schedule and Limit Retrieval (SSKD) for Study Power Flow sequence;
Network Model Builder (NMB), Load Scheduler (LSKD), Regulation Scheduler
(RSKD); and Unit Scheduler (USKD).
2.1.2 Modeling Features
Automatic Adjustments
The adjustments handled by the Dispatcher Power Flow include: transformer
angle/out-phase tap MW flow control; area interchange control; distributed
slack power; generator/synchronous condenser remote voltage control;
capacitor/reactor voltage control; SVC voltage control; transformer tap voltage
control; and the enforcements of Q-limits at generator buses.
The adjustment of transformer voltage tap control, transformer angle tap
control, SVC voltage control and generator remote voltage control are
achieved by introducing additional state variables into the power flow solution
process. Specifically, these state variables are: the tap ratio for transformer
voltage control; tap angle for transformer MW flow control; and MVAR
generation for SVC and generator remote voltage control.
Corresponding to these state variables, explicit mismatch equations for the
controlled MW flow and controlled bus voltage are included in the network
matrix equations. The generator bus Q-limiting and back off is handled by
switching between the deactivation and activation for the corresponding
explicit voltage mismatch equation together with the use of efficient partial
refactorization.
The error-feedback approach is used for all other control adjustments.
Adjustments are further characterized as either sensitivity-based or injection-
based. For the sensitivity-based adjustments, a set of computed or empirical
sensitivities is required to estimate the control parameter variations. The
capacitor/reactor voltage control belongs to this category. The injection-based
adjustments involve the modification of bus injections to meet the control
objective (i.e. area interchange).
Bus mismatch, rather than the conventional iteration number, is used as the
criterion for starting the adjustments. The bus mismatches are particularly
Page 7
suited for this purpose, because they provide a measure of the solution
accuracy and allow for the coordinated control of the adjustments. The
possible "hunting" between different adjustments can be circumvented by
activating them in a selective manner, depending on the solution accuracy and
type of adjustment. In general, the sensitivity-based adjustments are started in
the early stages of the solution, and the injection-based adjustments are
started only when the solution is moderately converged. Practical default
values are supplied for the starting mismatches of all adjustments. The user
can override any of them, if needed.
All the adjustments can be inhibited or activated based on individual
equipment, company, or the entire system.
Transformer Variable Impedance and Step Size Model
DPF supports variable impedance for voltage regulating transformers, where
the impedance is modeled as a nominal value plus a variational term. The
variational term is defined using impedance versus tap position table. DPF
also supports variable step size for the transformer tap. It is also defined as a
function of tap position.
2.1.3 Output Features
Power Flow Output

The power flow output includes the branch flows, the unit generations, loads,
bus voltages, transformer and phase shifter taps, etc. It also calculates the
variable voltage limits for buses with TCUL and the phase shifter transformers
connected to them. It is used as the base case solution by other applications
in the power flow sequence. The output can also be converted into the IEEE
common card image format.
Displays
The input/output displays of this subsystem are listed in Chapter 3 (Human
Machine Interface).
2.1.4 Support
DPF Case Initialization

This task is executed on demand when a base case is being built from
scratch. It initializes the static data in the DPF input categories from the Base
Data. The default execution parameters such as the maximum number of
iterations, control options, etc., are also initialized here.
Tabular Output Formatting
This task is executed on demand and allows the user to build the detailed
tabular output of the solution results for any specified company and zone.
Power Flow IEEE output
Page 8
This task converts the DPF output into the IEEE common card image format
and stores the output into a disk file.
Page 9
3 User Interface
This chapter describes important displays in the Dispatcher Power Flow and
related subsystems.
For the figures in this guide, poke points, which initiate an execution, are
identified by a shadowed symbol, and poke points that call up another display
are identified by a regular symbol. Entry fields are delineated by pointed
brackets, "<" and ">". Sample data is also used where appropriate. Some
examples use numbers to denote numeric data, and the letter "A" to denote
alphanumeric data. Displays are arranged into Index, Execution, Input/Output,
and Support sections.
The Dispatcher Power Flow Applications have a large number of displays that
provide the dispatcher with the ability to monitor the status of the control
system and the variables being controlled.
The figures in this chapter represent the current or projected versions of the
various displays.
3.1 Index Displays
There are two displays in this section.
3.1.1 DPF Input Index (DPFIIDX)
The DPF Input Index Display, shown in Figure 2, provides poke points to call
up all the DPF input displays.
Page 10
Figure 2 - DPF Input Index (DPFIIDX)
Page 11
3.1.2 DPF Output Index (DPFOIDX)
The DPF Output Index Display, shown in Figure 3, provides poke points to call
up all the DPF output displays.
Figure 3 - DPF Output Index (DPFOIDX)
3.2 Execution Control Displays
There is one display in this section.
3.2.1 DPF Execution Display (DPFEXEC)
The DPF Execution Control Display, shown in Figure 4, serves as the central
mechanism for the user to enter the execution options, to execute the power
flow supporting tasks.
The display is structured into the following sections:
Page 12
• Select Solution Technique - This entry field allows the user to select the
power flow solution technique. Either the Fast Decoupled solution
(default) or the full Newton-Raphson technique can be selected.
• Select Solution Options - This entry field allows the user to modify the
different controls during the power flow solution. The option whether the
power flow should begin from a flat start or not is provided by the entry
"FLAT START" Default value is "YES".
• Active Power Adjustment - The Active Power Adjustment controls can be

specified in the entries: "COMPANY INTERCHANGE CONTROL",
"DISTRIBUTED SLACK", " ANGLE/OUT-PHASE TAPS CONTROL " and
IGNORE PHASE SHIFTER ANGLE LIMITS. All options, except the last
one, have the default value “YES”. The Company Interchange Control and
Distributed Slack options cannot be activated simultaneously. If both are
activated, Distributed Slack is ignored.
• Reactive Power Adjustment - The Reactive Power Adjustment control can

be specified in the entries: "UNIT MVAR LIMIT ENFORCEMENT",
"TRANSFORMER TAP CONTROL", "CAPACITOR/REACTOR
SWITCHING" and “SVC IMPEDANCE LIMIT CONTROL”. All options have
the default value "YES".
• Tabular Output Generation -The poke point "BUILD TABULAR OUTPUT"

allows the user to build the tabular output for a specified company and
zone. If the company field is left blank, tabular output for the whole system
will be built. If the company is specified and the zone field is left blank, all
the zones in that company are included.
Page 13
Figure 4 - DPF Execution (DPFEXEC)
Page 14
4 Special Considerations
4.1 Start-up/Switch Over Considerations
4.2 Data Engineering
There are no Dispatcher Power Flow specific Data Engineering activities.
Page 15
5 Project Definition
The Dispatcher Power Flow subsystem uses the same power system model
that is used by all the other power system applications.
There are no significant Dispatcher Power Flow specific parameters.
Page 16
6 Design
This chapter describes the unusual aspects of the design. The Dispatcher
Power Flow subsystem (DPF) executes under the control of the Network
Application Monitor (NAC). In the real time database environment, DPF is
executed as part of the two power flow sequences, the real time one and the
study one. In the study database DPF can also be executed within study
database environment as part of the study power flow sequence.
The application monitor triggers the execution of the power flow sequence
periodically or when a SCADA event occurs. The sequence may also be
triggered manually.
Page 17

Dispatcher Power Flow: Functional Description

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dispatcher Power Flow: Functional Description

Uploaded by

Copyright:

Available Formats

ABB

Dispatcher Power Flow

Document Number: 1KSE000375 Revision Index: B

Date: 2009-08-18 Network Manager Release: NM4

ABB Inc. Copyright © 2005 - 2011

Document Approval ................................................................................................ ii

Figure 2 - DPF Input Index (DPFIIDX) ...................................................................... 11

Figure 3 - DPF Output Index (DPFOIDX) .................................................................. 12

Figure 4 - DPF Execution (DPFEXEC) ...................................................................... 14

Item Convention Example

Notes, Cautions, Warnings, and Tips

A Note is used to indicate neutral or positive information that emphasizes or supplements

• Dispatcher Power Flow (DPF)

• Power Flow IEEE Common Format (PFIEEE)

• Study Power Flow sequence (STPF)

• Real-Time Power Flow sequence (RTPF)

• Application Monitor (NAC)

The Schedule and Limit Retrieval subsystem merges manually entered

This time dependent data includes: adapted breaker status’s; load

• Telemetry Snapshot (SNP) and Status and Analog Retrieval (SAR)

Telemetry Snapshot (SNP) takes a snapshot of the current telemetry.

The Status and Analog Retrieval (SAR) subsystem coordinates various

The Network Model Builder subsystem performs the Network Topology

• Load Scheduler (LSKD)

• Regulation Scheduler (RSKD)

The Regulation Scheduler maintains the consistency of the desired bus

• Unit Scheduler (USKD)

The Unit Scheduler performs an economic dispatch to obtain initial

The System Load Forecasting subsystem provides the main company

The Saved Case subsystem handles the saved case management

1.3 Data Overview

• DPF Input/Output Files - Contains:

− all the input to run a base case power flow;

− any item that the user desires to change;

− the output generated by the run.

1.4 Overview Diagram

Figure 1 gives an overview diagram of the Dispatcher Power Flow subsystem

STUDY POWER FLOW SEQUENCE

Figure 1 - Overview Diagram

2.1 Dispatcher Power Flow (DPF)

2.1.1 Functional Components

Dispatcher Power Flow Solution

• Distributed Slack Power: The system slack active power is distributed

• Area Interchange Control: Net interchanges for each area or a group of

• Transformer MW flow Control: Transformers with angle/out-phase tap can

• Generator Q-limit Control: The MVAR limits of the controllable generators

• Remote Voltage Control: Generators and synchronous condensers can be

• Transformer Tap Control: Transformers with voltage/in-phase tap can be

• Capacitor/Reactor Voltage Control: Regulating capacitors/reactors can be

• Static VAR Compensator (SVC) Control: The MVAR output of SVC is

2.1.2 Modeling Features

2.1.3 Output Features

Power Flow Output

DPF Case Initialization

3.1 Index Displays

There are two displays in this section.

3.1.1 DPF Input Index (DPFIIDX)

Figure 2 - DPF Input Index (DPFIIDX)

3.1.2 DPF Output Index (DPFOIDX)

Figure 3 - DPF Output Index (DPFOIDX)

3.2 Execution Control Displays

There is one display in this section.

3.2.1 DPF Execution Display (DPFEXEC)