Effective December 6, 2006, this report has been made publicly available in

accordance with Section 734.3(b)(3) and published in accordance with

Section 734.7 of the U.S. Export Administration Regulations. As a result of
this publication, this report is subject to only copyright protection and does not
require any license agreement from EPRI. This notice supersedes the export
control restrictions and any proprietary licensed material notices embedded in
the document prior to publication.

Integration of Transmission Design

Tools and Software

2006 Progress Report

1012318
 Integration of Transmission Design
Tools and Software

2006 Progress Report

1012318

Technical Update, November 2006

EPRI Project Manager

J. Chan

ELECTRIC POWER RESEARCH INSTITUTE

3420 Hillview Avenue, Palo Alto, California 94304-1338▪ PO Box 10412, Palo Alto, California 94303-0813 ▪ USA
800.313.3774 ▪ 650.855.2121 ▪ [email protected] ▪ www.epri.com
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES
THIS DOCUMENT WAS PREPARED BY THE ORGANIZATION(S) NAMED BELOW AS AN ACCOUNT OF
WORK SPONSORED OR COSPONSORED BY THE ELECTRIC POWER RESEARCH INSTITUTE, INC. (EPRI).
NEITHER EPRI, ANY MEMBER OF EPRI, ANY COSPONSOR, THE ORGANIZATION(S) BELOW, NOR ANY
PERSON ACTING ON BEHALF OF ANY OF THEM:

(A) MAKES ANY WARRANTY OR REPRESENTATION WHATSOEVER, EXPRESS OR IMPLIED, (I) WITH
RESPECT TO THE USE OF ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM
DISCLOSED IN THIS DOCUMENT, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, OR (II) THAT SUCH USE DOES NOT INFRINGE ON OR INTERFERE WITH PRIVATELY OWNED
RIGHTS, INCLUDING ANY PARTY'S INTELLECTUAL PROPERTY, OR (III) THAT THIS DOCUMENT IS
SUITABLE TO ANY PARTICULAR USER'S CIRCUMSTANCE; OR

(B) ASSUMES RESPONSIBILITY FOR ANY DAMAGES OR OTHER LIABILITY WHATSOEVER (INCLUDING
ANY CONSEQUENTIAL DAMAGES, EVEN IF EPRI OR ANY EPRI REPRESENTATIVE HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES) RESULTING FROM YOUR SELECTION OR USE OF THIS
DOCUMENT OR ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM DISCLOSED IN
THIS DOCUMENT.

ORGANIZATION(S) THAT PREPARED THIS DOCUMENT

EPRI

This is an EPRI Technical Update report. A Technical Update report is intended as an informal report of
continuing research, a meeting, or a topical study. It is not a final EPRI technical report.

NOTE
For further information about EPRI, call the EPRI Customer Assistance Center at 800.313.3774 or
e-mail [email protected].

Electric Power Research Institute and EPRI are registered service marks of the Electric Power
Research Institute, Inc.

Copyright © 2006 Electric Power Research Institute, Inc. All rights reserved.
CITATIONS

This document was prepared by

EPRI
3420 Hillview Avenue
Palo Alto, CA 94304

Principal Investigator
J. Chan

EPRI
100 Research Drive
Haslet, TX 76052

Principal Investigator
I. Baskerville

This report describes research sponsored by the Electric Power Research Institute (EPRI).

The report is a corporate document that should be cited in the literature in the following manner:
Integration of Transmission Design Tools and Software. EPRI, Palo Alto, CA: 2006. 1012318.

iii
ABSTRACT

EPRI is updating the Transmission Line Design Tools by upgrading the design software package
TLWorkstation (TLW). TLW is a comprehensive software package contains a number of design
modules for transmission line designers. The modules for electrical designs were based on
information from EPRI Transmission Line Reference Book – 345 kV and Above, published in
1987 (the Red Book). A new version of the Red Book was published in 2004 along with a suite
of 50 small applets. To take advantage of the new information and the applets, the most
immediately step to upgrade the design tools is to integrate these applets into TLW.

The applets in the Red Book are targeted for the reader and were not developed as an integrated
design package. Thus separate data entry is required for each of these applets while TLW
provides a single, common database that manages and shares data among modules, and
incorporates industry standards, such as conductor and wire stress properties. The goal of the
integration is to avoid duplicating data entries and to provide friendly user interface.

In 2005, strategies and an implementation plan for achieving this integration were developed.
After detail review of the structure and software of the applets and TLW, the best way to
integrate the transmission design tools into one single package was identified. The most suitable
applets to be integrated into TLW were determined in 2006 and full integration was initiated.
The approach and selection were presented and discussed at the Overhead Transmission Design
Task Force meetings in Dallas, TX meeting on April 4-5 and in Atlanta, GA on September 18-19
as well as at the Webcasts on July 11 and October 24. Input was sought and feedbacks from
users were incorporated into the integration. The integration has reached the Alpha testing stage
the end of 2006. Integration will continue to Beta testing and then to completion the end of
2007.

Keywords
TLWorkstation
Transmission Line Design
Overhead Line Design
Line Design Tools
Line Design Software

v
CONTENTS

1 INTRODUCTION ....................................................................................................................1-1
Background ...........................................................................................................................1-1
Strategies ..............................................................................................................................1-1

2 TLWORKSTATION ................................................................................................................2-1
ACDCLINE ............................................................................................................................2-4
CORRIDOR...........................................................................................................................2-5
DYNAMP ...............................................................................................................................2-6
FAD .......................................................................................................................................2-7
MINIDES ...............................................................................................................................2-8
RNOISE ..............................................................................................................................2-11
TLOPGR .............................................................................................................................2-11
UPSTUDY ...........................................................................................................................2-12
WIRELDS ............................................................................................................................2-12

3 IMPLEMENTATION PLAN.....................................................................................................3-1
General .................................................................................................................................3-1
Current Applets – Development Environment .......................................................................3-3
Current Applets - Other Issues..............................................................................................3-4
Development Plan .................................................................................................................3-4
Activities in 2005 ...................................................................................................................3-5
Activities in 2006 ...................................................................................................................3-6
Work for 2007........................................................................................................................3-9
Future Work...........................................................................................................................3-9

4 SOFTWARE APPROVAL PROCESS ....................................................................................4-1

Product Requirements for All EPRI Software........................................................................4-1
Security Policy.......................................................................................................................4-4

vii
Contents

EPRI Software Development Process Requirements ...........................................................4-5

A APPENDIX ............................................................................................................................ A-1

B SOFTWARE REQUIREMENTS............................................................................................ B-1

C FUNCTIONAL SPECIFICATIONS ........................................................................................ C-1

viii
LIST OF FIGURES

Figure 2-1 Data Flow within TLWorkstation ...............................................................................2-2

ix
LIST OF TABLES

Table 3-1 Project Activities Schedule for 2006 ..........................................................................3-8

Table 4-1 EPRI Process Table and Planned Schedule .............................................................4-6
Table 4-2 Software Acceptance Form (SAF): Acceptance Testing, Publishing, and
Distribution Web and PC Applications ...............................................................................4-7

xi
1
INTRODUCTION

Background

Over the years, the Electric Power Research Institute (EPRI) has published a number of world-
renowned transmission line reference books and software, which are considered an industry
standard and are valued by many transmission companies and engineers. In addition, EPRI
issued the TLWorkstation (TLW) in the early 1990s, a comprehensive transmission line design
package that has a very strong set of users. In 2004, EPRI published the third edition of the
Transmission Line Reference Book – 200 kV and Above (the Red Book), along with a suite of
some 50 small software routines to help the reader employ the design theory within the book.
These software routines are targeted for the reader of the Red Book and were not developed as
an integrated design package. Thus separate data entry is required for each of these applets. The
software package in TLW contains a number of design modules, many of which were based on
the previous version of the Red Book. With changes in the Red Book, it is necessary to review
the present status of the TLW.

At the same time, new transmission line design packages have entered the market in recent years.
Consequently, a number of these tools, each with unique benefits could be integrated into the
TLW to form a more complete software package. For example, there are exceptional
commercial transmission line mechanical and 3-D graphical design packages. It would be ideal
to bring these design tools together, since the TLWorkstation is a leader in electrical design, with
a number of the existing modules in daily use by the global power delivery industry. This
combination would involve identifying the best of breed and then ensuring that the best EPRI
products work in an integrated fashion with the best commercial software.

Strategies

As a result of transmission expansion in some parts of the world such as South America, South
East Asia and Africa, and also the recent round of blackouts, it is clear that there is renewed
interest in building new transmission lines. The need to consider construction of high voltage
transmission lines is also captured in some of the recent US Government Department of Energy
documents. In the past there has been a slump in overhead line construction. Consequently, skill
levels within the industry have declined. Further, there are very powerful CAD and line layout
design software packages that are almost considered industry standards that have not been
interfaced with EPRI’s TLWorkstation. Combining with the new edition of the Red Book, it is
therefore crucial that TLW must be updated to address all these changes and challenges.

1-1
Introduction

In 2005, strategies for achieving integration of the Red Book applets were developed. The
general strategies were:

1. Identify one or more key line design packages, such as the PLSCAD and TLPRO that are
very strong on the graphical and structural aspects of line designs.

2. Develop a standard to move data between EPRI design modules and other design
software.

3. Focus on enhancing EPRI modules, ensuring that they are very robust and reflect the
latest thinking.

4. Look to market these modules as either stand alone or packages that can be loaded up
alongside the commercial software.

After detail review of the structure and software of the applets and TLW, the best way to
integrate the transmission design tools into one single package was identified in 2005.

This report provides an update of the integration since the first progress report on “Integration of
Transmission Design Tools and Software” was published in November 2005.

1-2
2
TLWORKSTATION

To comprehend fully the scope of work and activities involved in integrating the Red Book
applets into TLWorkstation (TLW), it is necessary to understand the structure and modules
inside TLW. This Chapter provides general description of the overall structure and different
modules of the existing TLW, their capability and features. Understanding the dynamics of
these application programs is essential in the development of the new TLWorkstation.

TLW is a comprehensive package of interactive computer programs for designing new

transmission lines and upgrading existing lines. TLW integrates a variety of software
applications that can be used separately or as one complete package to support the following:
Line analysis and optimization
Upgrade planning and design
Foundation analysis and design
Conductor/insulator analysis
Structural analysis and design

There are nine modules plus the EXECUTIVE control program. The modules are accessed and
integrated through this EXECUTIVE program which is displayed in the Program Manager. The
flow of data into, within and out of TLW is facilitated by the user interface, the executive control
program and the database management system and, is shown in Figure 2.1.

2-1
 User Interface

Executive Control Program

R
NE

Y
O

DS
P

ES

UD
Task Modules

ID

E
LI

PG

EL
IS
RR
DC

ID
NA

ST
O
D

IR
IN
CO

RN
DY

UP
AC

FA

TL

W
M
Database Management System
R
NE

Y
O

DS
P

ES

UD
Database
ID

E
LI

PG

EL
IS
RR
DC

ID
NA

ST
O
D

IR
IN
CO

RN
DY

UP
AC

FA

TL

W
M

Figure 2-1
Data Flow within TLWorkstation

2-2
The EXECUTIVE allows the user to customize the workstation environment to include only
those modules that the user needs. The user can add or remove task modules at any time without
affecting other workstations sharing the same machine. Complying with ODBC standards, the
EXECUTIVE features a relational database management system. This system provides an
efficient sharing of files and data among all modules and provides the capability of interfacing
with third-party software.

The latest TLW software is Version 3.0. TLW 3.0 has a full Windows environment that
provides a user-friendly graphical interface to increase the efficiency of producing and
modifying transmission designs. TLW features new and enhanced online Help documentation
that provides easy access to descriptions, hands-on tutorials and key engineering concepts.
Novice users have successfully used the design and analysis modules after only one or two hours
of training. Improved graphics capabilities include full-color two and three-dimensional plots
which make it easy for users to interpret the results of their design efforts.

TLW's unique structure enables the user to accomplish and record all related tasks within a larger
project or use individual programs to solve independent problems. Because the system maintains
a record of all past work, a new user can pick up where others left off. Besides helping utilities
complete larger projects much more quickly, TLW's integrated features can improve
communication between transmission line designers. Utility personnel with different functions
and specialties can more easily unify their efforts and maximize workgroup collaboration.

TLWorkstation 3.0 provides the following features:

Single, common database: Manages and shares data among modules, and incorporates industry
standards, such as conductor and wire stress properties.
Windows programming standard guidelines: Complies with Open Database Connectivity
(ODBC) standards.
Graphical user interface: Provides an easy-to-use Windows environment for input and output.
Fast conversion of existing databases: Loads and converts data from earlier versions of TLW
into the new common database.
Mixed units of measurement support: Allows the user to switch between English and SI units
within a project.
Illustrated online Help: Displays the entire user's manual as a Help file, and provides step-by-
step tutorials and reference information.
Full-color graphics plotting package: Creates two and three-dimensional plots and allows the
user to edit plot attributes.
Compatibility with various operating systems: Operates on Microsoft Windows 3.1, Windows
95 and Windows NT.

The nine modules are:

1. ACDCLINE: studies electric and magnetic phenomena of AC, DC and hybrid lines

2-3
TLWORKSTATION

2. CORRIDOR: solves problems related to shared use of right-of-way

3. DYNAMP: evaluates the dynamic ampacity of overhead conductors
4. FAD: performs foundation analysis and design
5. MINIDES: studies preliminary design of transmission line structures
6. RNOISE: calculates radio noise in fair and foul weather from high voltage lines
7. TLOPGR: displays the impacts of alternative line upgrades on design parameters
8. UPSTUDY: examines the feasibility and cost for upgrade alternatives
9. WIRELDS: generates loading trees for all types of structures

Detail descriptions of each module are given below.

ACDCLINE

This program provides the necessary tools for studying a range of electric and magnetic
phenomena associated with AC transmission lines, DC transmission lines, and AC/DC hybrid
lines.

ACDCLINE provides information on the following areas: conductor surface voltage gradients,
corona losses, audible noise, radio noise, ozone, electric field, ion density, ion current, human
sensation levels to electric fields, coupling to objects, shielding by objects, magnetic field, surge
performance of towers, and selection of insulators based on surface contamination. Graphics
options are also available for viewing the line geometry specified by the user and profiles of the
computed results.

ACDCLINE is composed of several individual sub-modules that are fully integrated. The
database contains common overhead conductors which simplify execution. ACDCLINE
automatically enters the physical constants of a conductor upon specifying the conductor code
name. It analyzes and designs AC lines, DC lines, multi-circuit lines, or hybrid AC/DC lines.
Solidly bonded, sectionalized and isolated ground wires can be specified, as well as different
span lengths for various circuits. For each project, ACDCLINE can perform calculations for:
Up to 12 phases for AC lines
Up to 24 AC and/or DC bundles (including energized and grounded bundles)
Up to 50 individual conductors
Regular and irregular bundle arrangements

The following are execution options in ACDCLINE for AC, DC or hybrid AC/DC lines:

1. Corona calculations (average height)

Surface gradient
Corona loss
Audible noise

2-4
 TLWORKSTATION

Ozone (only if DC bundles exist)

Radio noise

2. E-field and ion calculations (actual height)

Surface gradient
Electric field and ions without shielding objects
Sensation levels
Coupling to objects and shielding by objects

3. Magnetic field calculations (actual height)

Magnetic field

4. Insulation analysis
Switching surge performance
Insulator contamination

ACDCLINE uses various methods for calculating audible and radio noise. Human response
models to electric fields and field sensation levels are available. Coupling and shielding object
options allow for the calculation of voltages and currents coupled to nearby objects, as well as
the calculation of shielding effects of nearby objects. The magnetic field option calculates the
effects of induced ground wire currents, and the insulator contamination option includes the
selection of insulator number and type based on the contamination level.

CORRIDOR

This program solves complex right-of-way problems that include: power transmission lines,
multiple pipelines, other buried or above-ground conductors, railroad track circuits, and railroad
signal and communication lines. It provides the necessary tools for studying interference
conditions that may occur as a result of sharing a common corridor by these utilities.

CORRIDOR enables those with a minimum background in electromagnetic analysis to solve

complex rights-of-way problems. CORRIDOR calculates and provides as output the steady-state
or fault-induced voltage and current caused by adjacent electric power transmission lines at
locations of interest along pipelines, railroads, communications wires, shielded cables, or other
conductors. The analysis can include excitation of the passive conductors, by either magnetic or
electric fields that are produced by power lines.

CORRIDOR analyzes utility common corridors for which the passive conductors (non-power
line conductors) are nominally parallel. The program can model changes in the spacing between
passive conductors by dividing the corridor into nominally parallel segments. If the spacing
between passive conductors gradually changes, the region of change should be divided into
segments with stepwise constant effective separation. CORRIDOR allows the modeling of power
lines that are at an angle to the nominally parallel passive conductors. CORRIDOR makes it
easy to model several types of passive conductors that are typically encountered in common
utility corridors. The common passive conductors in CORRIDOR include:
Pipelines: Buried or above ground.

2-5
TLWORKSTATION

Rails or track: Specified to the program by customary railroad parameters.

Wires: Buried or above ground, and can be used to model such occurrences as fences, railroad
open wire communications or signal lines, mitigation wires, or de-energized power-line
conductors.
Shielded cables: Buried or above ground.

CORRIDOR calculates the voltage and current on the passive conductors that result from:
Current in power-line conductors: The effect on the passive conductors is by magnetic-field
coupling.
Voltage on power-line conductors: The power-conductor voltage results in a vertical component
of electric field near the earth that induces a voltage onto insulated passive conductors.
Voltage and current on the other passive conductors.
Discrete voltage sources that are connected to the passive conductors at user-selected locations to
simulate discrete signal sources.

The voltage and current induced onto passive conductors by the first two of the above types of
coupling can be calculated by the program either individually or together. Thus, the program
offers the user the opportunity to determine the relative importance of the two coupling
mechanisms for the modeled problem. Knowledge of which coupling mechanism is responsible
for the voltage or current on a conductor can be an important consideration in identifying
alternative methods to minimize interference to equipment or personnel safety risks.

The passive conductors (rails, pipelines, etc.) interact with each other. Thus, one passive
conductor can influence the resultant voltage and current on other passive conductors.
Therefore, the program allows the user to include all important passive conductors in the analysis
to accurately reflect resultant interactions. CORRIDOR can calculate induced voltage and
current due to the steady-state or faulted operation of the power line. The effects of the normal
small unbalance in the power-line-conductor currents can be readily assessed, if the unbalance is
known or is estimated. In addition, the program can be used to calculate other parameters or
voltages and currents of interest. This includes the shield factor of shielded cables, potential of
earth surface points, voltage and current associated with the impedance elements in the problem,
and current in power line overhead shield wires.

DYNAMP

This program appraises and reappraises the DYNamic AMPacity of overhead conductors. It
provides guidelines for producing either steady state, transient or predictive calculations for a
wide range of conductors and covers real-life examples of each type of calculation. Developed
at the Georgia Institute of Technology, DYNAMP's accuracy has been verified by comparing the
predicted conductor temperatures with values measured at Georgia Power Company's Research
Center and temperatures measured in a separate study sponsored by Kansas Electric Utilities
Research Program and implemented by Kansas Gas and Electric Company.

2-6
 TLWORKSTATION

DYNAMP includes common overhead conductors in the database to increase productivity. The
program automatically enters the conductor's five physical constants upon naming the conductor
code. Real-time calculations can be conducted. All real-time calculations are based upon
ambient weather. DYNAMP frequently updates these calculations so that real-time values of
wind speed and direction and the ambient temperature are used as input data. The program
incorporates the effects of the changing weather and conductor current into the thermal analysis
by accounting for the thermal capacity of the conductor.

The contribution of the sun, loading on the conductor temperature, is automatically considered in
a separate subroutine that calculates the clear sky incident solar energy at the specified location
of the conductor. DYNAMP predicts real-time temperatures for seven types of conductors. The
program uses composite conductors such as ACSR and those consisting of either all-aluminum
or all-copper strands.

The program provide diagnostics tools. DYNAMP conducts checks on internal calculations
performed within the program and inconsistencies in input data. If the program encounters
unusual values for calculated quantities or for input variables, DYNAMP displays a series of
diagnostic messages.

Four calculation types are available:

1. The steady state calculation type involves a steady state model that calculates a single value
of the conductor temperature for constant weather and a constant line current. The program
calculates ampacity for a given value of conductor limiting temperature. This type of model
has been traditionally referred to as the House and Tuttle method.
2. The transient calculation type consists of a transient model for real-time conductor operation.
It calculates instantaneous conductor temperatures when the conductor experiences varying
current levels and weather.
3. The time predictive calculation type provides predictive temperature calculations based on
emergency situations that can arise from a sudden current overload on the line.
4. The current predictive calculation type predicts the allowable overload current that can be
sustained for a given time and not exceeding the limiting temperature.

FAD

This program performs foundation analysis and design (FAD). FAD combines the capabilities
of modules CUFAD+ (Compression/Uplift Foundation Analysis and Design) and MFAD
(Moment Foundation Analysis and Design) into one module to analyze and design drilled shafts
(drilled piers and caissons), spread foundations, and direct embedded poles for axial, lateral and
moment loading. CUFAD+ was developed at Cornell University, and MFAD was developed by
GAI Consultants, Inc. They were included in earlier versions of TLW as separate modules.

CUFAD+ is an interactive program for analyzing and designing drilled shaft or spread
foundations for electrical transmission line structures. The program accommodates uplift and
compression loadings under both drained and un-drained soil conditions. Engineers can analyze
foundations to obtain the capacity and overall factor of safety under a set of loads. CUFAD+ also

2-7
TLWORKSTATION

enables engineers to design foundations of given widths or diameters to obtain the minimum
depth required.

MFAD analyzes and designs foundations that are subject to high overturning moment loading.
The program can be used for drilled shaft foundations and for direct embedment poles. MFAD
uses a nonlinear four-spring load deflection model and an ultimate capacity model in the
geotechnical analysis and design of laterally loaded drilled shafts.

FAD in TLW version 3.0 features the following:

Reliability based design
Structural design of drilled shafts
Design of rock sockets

An overview of geotechnical engineering concepts and geotechnical terms used in foundation

design are provided in the module’s User Manual. The terms included are found in Appendix A
of this report:

MINIDES

This program provides the necessary tools for studying the preliminary design of transmission
structures including estimates of component sizes, total structure weight, and foundation loads.
MINIDES can perform design sensitivity studies and cost estimates and provide data for design
optimization codes.

Input to MINIDES consists of very few data items. The MINIDES module automatically reads
design loads generated by the module WIRELDS, a TLW loading tree program. The sizes and
weights determined by MINIDES are approximate, but they are determined in a consistent
fashion and based on simplifying assumptions for each type of structure. The sizes and weights
determined by MINIDES normally lie within 10 percent of corresponding values obtained by a
detailed design. While a detailed structural design may require substantial engineering and
computing time, an approximate design requires only a few seconds.

MINIDES can compute weight regression coefficients for the TLOPGR module, an optimization
program within TLW. To produce these coefficients, MINIDES generates variations of the base
design from which linear regression coefficients are calculated automatically. The general
concepts are based on:

Geometry - Once a structure type has been selected, its overall geometry is defined through the
specification of a few key geometric parameters. MINIDES uses these parameters to develop a
model of the structure. The internal model developed by MINIDES may not be as detailed as the
model required for the final design of the structure, but it is appropriate for estimating sizes,
weights, and foundation loads.

Material - Self-supporting or guyed lattice structures consist of hot-rolled steel angle members
assumed pin connected at joints. Single or multi-pole structures can be made of wood, steel, or

2-8
 TLWORKSTATION

pre-stressed concrete. Wood poles are restricted to Douglas Fir, Western Red Cedar, or Southern
Pine. All steel poles use 12-sided cross sections made of plate thickness in increments of 1/16
inch. Pre-stressed concrete poles have circular cross sections with a constant taper.

Design Loads - The load file contains design loads for the MINIDES structure. Before running
MINIDES, the load file is normally generated from WIRELDS, a loading tree program in TLW.

Design Assumptions - The basic components of all the structures in MINIDES are:
Steel angle members
Guy cables
Poles of various types
Various braces and cross arms

Steel Angle Members - All members of lattice types SLi and GLi are single hot-rolled angles that
are efficient in carrying compression over large unbraced lengths. Therefore, in the design of
lattice structures, only a subset of all commercially available rolled angles is considered.

Member Tension Capacity: The tension capacity of a member with cross section area A and
yield stress fy is assumed equal to 0.85 A fy. The factor of 0.85 is an approximation to account for
the presence of bolt holes.

Member Compression Capacity: The compression capacity of an angle member is affected by its
physical dimensions (actual length L, cross section area A, radii of gyration, rx, ry, and rz), by its
end connections and its bracing (from redundant members). The compression capacity is
calculated by the procedures described in ASCE Manual 52.

Procedures involve calculating a slenderness ratio, kL/r, where the value of k is critical. In
MINIDES, the value of k is either assumed or calculated from an assumed number of
intermediate bracing points that subdivide the length L. Assumptions are based on average
values found in actual designs for typical members.

Guy Cables - MINIDES designs guys so that they are not used at more than 70 percent of their
ultimate strength.

Poles - MINIDES designs all pole shafts to resist the combined effect of axial load and bending
moments. The effects of shear and torsion are neglected.

Wood Poles: Wood poles are selected from available ANSI classes such that the following
equation is satisfied at all points along the pole:

fa + fb • fall = Φ MOR

where

fa = normal stress due to axial load, P/A

2-9
TLWORKSTATION

fb = normal compression stress due to bending, Mc/I (M is resultant of both transverse

and longitudinal moments)

fall = allowable stress described as fraction of wood MOR

Φ = strength factor

MOR = modulus of rupture

In the equation above, the strength factor must be compatible with the load factors selected for
the loading tree. For the NESC "District" load case of the National Electrical Safety Code, it is
recommended that all load factors be specified as one and the strength factor be specified as
0.25. This combination is equivalent to using load factors of four together with a strength factor
of one, as suggested by the NESC requirement that P-effects are based only on un-factored loads.

For load cases other than the NESC District case, values of larger than 0.25, but not greater than
one, can be used. Therefore, when wood poles are used, two separate values of should be
specified, one for the NESC District case and another one for all the other cases (including the
NESC extreme wind case). All wood poles are assumed directly embedded into the ground
following ANSI recommendations.

Steel poles: Steel pole shafts are assumed to be 12-sided polygons. A single plate thickness is
used over 20-foot lengths. Minimum plate thickness is 3/16 inches, and all other thicknesses are
multiples of 1/16 inches. Overall design assumptions follow the recommendations of ASCE
Manual. The shaft is sized so that the following equation is satisfied at all points along the pole:

fa + fb • fall

where

fa = normal stress due to axial load, P/A

fb = normal compression stress due to bending, Mc/I (M is resultant of both transverse and
longitudinal moments)

fall = allowable stress described in ASCE Manual and is based on the wall slenderness, w/t

All steel pole shafts are supported on top of reinforced concrete piers. They use 2-inch thick base
plates and no. 18 reinforcing bars for anchor bolts. Steel pole arms are assumed to be fabricated
of cylindrical tubes with a diameter to thickness ratio D/t of close to 40. In addition to the shaft
weight, the weights of the arms, base plate, and anchor bolts are calculated by MINIDES.

Pre-stressed Concrete Poles: It is assumed in MINIDES that:

1. A constant taper and a predetermined variation of thickness exists throughout the length of
the pole
2. Pre-stressing strands can be terminated at specified locations along the pole.

2-10
 TLWORKSTATION

RNOISE

This program calculates the electromagnetic interference or radio noise in fair and foul weather
from high voltage transmission lines. RNOISE computes lateral profiles of the radio noise from
electric power lines in the 500 KHz to 1.5 MHz frequency range. The predictions are based on
work at Washington State University. An overview of electromagnetic interference and radio
noise predictions and guidelines for selecting parameters is included in the user’s manual.

RNOISE predicts levels of electromagnetic interference (radio noise) between high voltage
transmission lines in corona and a standard receiver located near the line. Using a CISPR
standard receiver, the output corresponds to radio noise in either average fair or average stable
foul weather. The noise is calculated by measuring with a vertical rod antenna (E Field) and a
horizontal loop antenna (H Field). This result is an equivalent electric field by multiplying by
377 ohms (impedance of free space). This also demonstrates how the H field is presented as an
equivalent electric field. The H field is measured by standard receivers equipped with loop
antennas. For each project, RNOISE can perform calculations for:
Electric field at the surface of each bundle
Generation functions
Propagations of radio noise currents
Radio noise fields

TLOPGR

This program is a transmission line design program specifically oriented toward the upgrading of
existing lines. The program provides an interactive, "spreadsheet-like" output screen that
displays both editable input parameters and output values. The impact of changes in the input
data is seen almost instantaneously. This approach gives immediate feedback to the user,
speeding up the design process considerably.

TLOPGR calculates minimum vertical clearances to ground and horizontal clearances to edge of
right-of-way for each span, and the wind and ice loading on each structure with a digital
description of the terrain and structures along it. The program allows the user to identify problem
spans and structures, as well as investigate the effect of moving, raising or adding structures, and
changing conductor tension, maximum conductor temperature, or reconductoring.

The effect of these changes in structure and conductor on clearances and structure loading are
immediately visible to the user. TLOPGR can also be used to edit an output file from TLW
module TLOPWT, allowing the user to alter the optimum structure locations and heights as
given by TLOPWT. TLOPWT, or Transmission Line Optimization Program with Terrain,
examines a transmission line as a system of interdependent environmental, structural, insulation,
and economic design factors to determine the most cost-effective design.

2-11
TLWORKSTATION

UPSTUDY

This program provides the tools for conducting an upgrade analysis. Using a limited amount of
input data to describe the existing line, UPSTUDY provides a quick and easy way to examine the
feasibility and cost for many upgrade alternatives.

UPSTUDY provides a rapid and approximate estimate of environmental, mechanical and

economic effects for upgrading techniques such as increasing line voltage, re-conductoring, or
operating the existing conductor at a higher maximum temperature.

UPSTUDY can display the output results on an interactive spreadsheet that allows the creation of
"What If" scenarios by modifying various input parameters. The impact of these changes is
displayed instantaneously. This approach gives immediate feedback, speeding up the design
process considerably.

For each upgrading option, UPSTUDY calculates environmental parameters (electric field,
magnetic field, audible noise, and radio noise); clearance at high temperature in a typical span,
and line loading limits (thermal rating, voltage drop, and surge impedance loading). Vertical
clearance, "blowout," and structure transverse loading are calculated for a typical span. The
present worth of electrical losses and construction changes are determined for each alternative.

WIRELDS

This program provides the tools for studying loading trees. WIRELDS generates loading trees
for all types of structures and handles design procedures from classical methods, such as the
National Electric Safety Code (NESC), to new Reliability-Based techniques.

WIRELDS can be used as a stand-alone program or with other TLWorkstation (TLW) task
modules such as MINIDES (Mini-Design Loads for Transmission Structures) and POLDAR
(Pole Design, Analysis and Reliability). Load data files generated by WIRELDS are stored in
the TLW database.

WIRELDS is a general loading tree program that can be used for all line geometry with any type
of insulator. The program combines features normally found in sag/tension programs with other
geometric design considerations. WIRELDS uses the following methods to determine loading
trees:
1. Actual Geometry - Determines the actual loading tree for an existing structure.
2. Wind-Weight Spans - Determines loads for a structure where wind and weight spans are
specified.

WIRELDS utilizes a single, common database that manages and shares data among
TLWorkstation applications. Design loads generated by WIRELDS are saved in the database
where other TLW modules can access this information. For example, MINIDES, a mini-design
program for transmission structures, estimates the weight of an actual structure that supports
loads calculated by WIRELDS.

2-12
3
IMPLEMENTATION PLAN

The objective of the Transmission Line Design Tools project is to lower overall capital and
O&M costs for overhead lines by providing latest tools and information to make informed
decisions on the design of overhead lines.

General

For this particular project that extends from 2005 to 2007, the scope involves the integration of
selected applets from the new edition of the Red book and the immediate steps to be taken in the
overall plan include the following:
Replace software modules in TLW with new modules using algorithm in the 2004 edition of the
Red Book
Preserve and enhance modules in TLW where TLW is a clear market leader
Ensure TLW can integrate with other selected transmission line packages
Consider linking TLW, Red Book software, EPRI's TFLASH software and, other EPRI software
and applets
Ensure that associated handbooks and reports are available to complement the software packages

The ultimate goal of the Transmission Line Design Tools project is to develop TLWorkstation to
be the depository of all transmission line design programs covering different disciplines of
engineering. A tentative list of existing or new programs for each discipline is as follows:

Design Studies
Preliminary designs (MINIDES)
Probabilistic-based designs

Electrical
General designs (Red Book Applets)
Lightning (TFLASH program)
Current Rating (DYNAMP)
Shared ROW (CORRIDOR, EMC Book, ROW Guide)

Mechanical
General designs (Orange Book)

3-1
Implementation PLan

EPRI Vibration software

Wind/Ice Loading

Civil
Structure (WIRELDS)
o Pole
o Tower
Foundation (FAD)
Line Layout (PLSCADD, TLCADD)

Line Upgrades
Voltage Upgrades (Blue Book)
Current Upgrade (TLOPGR, UPSTUDY, HTC Matrix)

Programs outside of TLWorkstation can be integrated into the software by interfacing third party
software with TLW. Update of existing programs in TLW will be required as new information is
developed. Other than the Red Book, the following EPRI books and documents are being
updated or prepared:
Transmission Line Reference Book: Wind-induced Conductor Motion (Orange Book)
Transmission Line Reference Book: 115-138 kV Compact Line Design (Blue Book)
Power System and Railroad Electromagnetic Compatibility Handbook
Guide for the Engineering the Multiple Use of the Right-of-Way

Information from the new version of these documents can be applied to the programs.

Integrating programs into the TLS software will face a number of challenges. Some of the major
challenges are:
Software used in existing programs is outdated
Mapping data from different sources could be difficult. Even though the Red Book Applets were
developed by the same developer, data format and names varied with time.
The focus of different program could be quite different and thus data mapping produces little
benefit

To overcome some of these challenges, the project solicited aggressively user input. Some of the
initial input was that less emphasis should be put on data mapping and more attention should be
put on user interface. As a result, only the most commonly used data such as conductor
information and structure configuration will be mapped. Mapping and integrating of database
will be done cost effectively without sacrificing the overall outcome of the integration. Further
details on the challenges encountered and to be overcome are provided in the sections below on
Current Applets – Development Environment and Current Applets – Other Issues. The software
integration is being undertaken by EPRI staff up to the end of 2006.

3-2
 Implementation PLan

Current Applets – Development Environment

Development of the current Red Book Applets began in 1996. At that time, developers of
Windows Java applications (both Windows applications and Applets that would run from web
pages) could use Microsoft Visual J++ Version 1.1 or a number of other Java development tools.
So, the developers of these Applets chose to use Microsoft Visual J++ Version 1.1.

Java is a language that was originally developed by Sun Microsystems. The syntax for Java is a
subset of the syntax for C++. Java restricts the latitude given C++ programmers in order to
prevent the occurrence of runtime errors that plague many C++ applications such as the dreaded
‘Access Violation’. Hence, it is a good choice for the production of applications that are easy to
maintain and generally free of intractable errors.

The original version of Sun Microsystems’ Java was version 1.0, which was matched by
Microsoft Visual J++ Version 1.0. Later, Sun developed version 1.1 and Microsoft matched it
with their Visual J++ Version 1.1. Sun performed a major redesign of Java between the two
versions. They redesigned the Event handling model; i.e., the syntax of the code that handles
things like moving the mouse or clicking a mouse button. They also standardized the syntax of
function calls to the various screen controls [Clearly, when version 1.0 was developed, Sun
allowed the different programmers to use their own naming conventions. As a result, different
controls often use different function names to perform, what is essentially, the same function.]

In 1998, Microsoft began distributing Microsoft Visual J++ Version 6.0. This was the successor
to Version 1.1. Microsoft ‘jumped’ their version numbering to 6.0 in order to synchronize
version numbers with their other software development tools.

In 2001, Sun Microsystems won a lawsuit against Microsoft which required that Microsoft stop
distributing their version of Java. So, Microsoft stopped their Java development and began
scaling back their support of Visual J++. As a result, Microsoft no longer supports their old Java
products.

The current Applets have, in the course of the review, been recompiled in Microsoft Visual J++
version 6.0. Many of the Applets required some minor modifications to make them recompile.
Additionally, the compiler complained about the use of the Java 1.0 Event Model and function
names. A number of the Applets were modified to comply with the newer standards. This
examination suggests that, going forward, these modifications could be made at a rate of 2 to 3
Applets per day.

However, since Microsoft no longer supports Visual J++, there is the larger issue of what
development platform to use going forward. There are two basic options: stick with Java and
choose one of the various Java development tools, or, migrate the code to Microsoft’s
replacement for Java within their arsenal of tools, J# (J-sharp).

Microsoft’s J# uses syntax similar to that of Java, but does not run on the Java VM platform; it
runs on Microsoft’s ‘.NET Framework’. In all likelihood, J# will diverge from Java as future
versions (of J#) are developed. So, taking this path would restrict future versions of the Applets
to running on Microsoft Windows machines.

3-3
Implementation PLan

Maintaining the Applets in a Java-compliant development platform would allow the flexibility of
running the Applets on any operating system that supports the Java VM.

Current Applets - Other Issues

The choice of writing the Applets as Applets and the extent of the period over which they were
written has resulted in other coding issues. Each Applet is made up of the main Java class that is
executed from the web page, and supporting classes that are called by that main Applet class.
All these classes must be contained within the directory or subdirectories of the main [Applet]
class. This has led to many versions of classes that perform the same function.

For instance, all of the Applets that deal with conductor bundles contain a java code module (and
resulting class) called ‘Bundle.java’. This code defines an object that encapsulates a list of
conductors and their configuration for each bundle under consideration. The first Applet in the
list is ‘AN1’ which calculates the audible noise caused by corona from transmission lines. It has
the first version of the Bundle object in the directory for the AN1 Applet. When AN4 (that
calculates the audible hum at twice the power frequency caused by corona) was coded,
‘Bundle.java’ (and other modules) was copied to that directory to be used to build that Applet.
During the development and debugging of these separate Applets, the code in each version of
‘Bundle.java’ was modified separately and has diverged.

Development Plan

The following procedure describes the approach for the integration of the applets into TLW.
1. Identify data that is common to multiple Applets.
a. Conductor Information
b. Bundle Configuration
2. Re-code objects to encapsulate all data and functionality relating to those objects.
a. For instance, some Applets require specification of conductor Sag while others do
not.
3. Redesign the dialogs currently used to maintain those objects to include all information
required for all the Applets, and to allow for more robust editing of the data.
a. The current Applets allow for add and delete, but not modify. So, if a user makes
a mistake when specifying a bundle, they have to delete the old bundle and enter
all the bundle data again.
4. Design a database, based on the tables in TLWorkstation, in which to store the data
required by the application.
a. For the current applets, this involves the ACDCLINE tables and Conductor
Lookup tables.
5. Build an Application framework to encapsulate the current Applets into one application.
a. This will be done in the new development platform.

3-4
 Implementation PLan

6. Convert the Applets to functions executed from within the new Application framework.
a. Converting Java Applets to run from within an application is trivial.
b. The Load/Save buttons will be changed to Load and Save the data through the
new dialogs from and to the database tables instead of disk.
c. All the Applets screen forms must be converted to the new development platform.

Activities in 2005

This project “Transmission Line Design Tools’ with three other projects forms Project Set 35C
“Overhead Transmission Design for Optimized Life Cycle”. The objective of this Project Set is
to provide clients with tools to make informed decisions when designing and constructing new
transmission lines or when upgrading existing transmission lines. Tools include research results,
techniques, equations, methodologies, guides and software. These tools will help clients achieve
the goals of producing reliable and safe design, enabling the selection of the lowest life cycle
cost, decreasing design times, reducing labor costs and lowering capital cost by at least 5% for
overhead transmission lines.

The other projects under this Project Set are:

Compaction of Overhead Lines
Engineering the Multiple Use of the Right-of-Way
Vibration Management of Overhead Transmission Lines

A task force, TF3, was formed for Project Set 35C in 2005. The purpose of the task force is to
review progress and direction of this group of projects and to ensure that each project achieves
its objective. Two task force meetings were held, one on March 21 - 22 in Palo Alto, CA and
one on November 3 - 4 in Charlotte, NC. In addition, two Webcasts were held on June 20 and
August 22. At these task force meetings and Webcasts, this project was reviewed and discussed.
Input was sought from the advisors. The implementation plan was heavily influenced by the
advisors.

The Portfolio provides the following description of tasks to be conducted in 2005:

Establish a strategy to update EPRI TLWorkstation
Develop a plan to integrate EPRI software such as applets from the new Red Book and, third
party software into TLWorkstation

The following summarizes the achievements for the year:

The architecture of the existing TLW software was reviewed in order to develop an architecture
that would minimize duplication of data entries and that would link different calculation
modules, applets and 3rd party software effectively.
The existing TLW was evaluated by volunteers for improvements.
The existing TLW was evaluated internally by EPRI staff for improvements.
The architecture of 50+ applets from the Red Book was examined.

3-5
Implementation PLan

Integrating the Red Book applets into the TLW began.

The deliverable for the year was a technical update on “Integration of Transmission Design
Tools & Software – 2005 Progress Report” published in November, 2005 under Product ID
1010238.

Activities in 2006

In 2006, suitable applets to be integrated into TLW were evaluated. The selection were
presented and discussed at the Overhead Transmission Design Task Force meetings in Dallas,
TX meeting on April 4-5 and in Atlanta, GA on September 18-19 as well as at the Webcasts on
July 11 and October 24. Input was sought and feedbacks from users were incorporated into the
integration. It was determined that certain Red Book applets will be used to replace the
ACDCLine and RNoise modules in TLWorkstation.
The primary objective of the integration is to create an application that will replace the
ACDCLine and RNoise modules in TLWorkstation as the first step in maintaining the viability
of EPRI’s TLWorkstation software.

Additional objectives are:

• Include updated algorithms, specifically 3-D calculations

• Improve Import, Export and Save As functionality
• Improve Data Input Forms, with graphical feedback
• Improve maintainability by using up-to-date development platforms
• Provide architecture that can be linked to other software packages.

The final list of selected applets is:

3-6
 Implementation PLan

Applet Description
AN-1 Audible Noise of Transmission Lines
AN-2 Audible Noise of Transmission Line (3-D)
AN-3 Bundle Geometry for Minimum Audible Noise
AN-4 Audible Noise, Hum
AN-6 Audible Noise vs. Rain Rate
CC-1 Conductor Surface Gradient (2-D)
CC-2 Conductor Surface Gradient (3-D)
CC-3 Surface Gradient on Toroidal Corona Shields
CC-4 Conductor Tables
CC-5 Transmission Line Parameters (Single Circuit)
CL-1 Transmission Line Corona Loss
CL-3 Ozone Concentration near Transmission Lines
EMF-2 Electric Field of Transmission Lines in 2-D
EMF-4 Electric Field of Transmission Lines in 3-D
EMF-5 Electric Field Shielding by Grids of Wires - 2D
EMF-6 Magnetic Field from Sets of Current Carrying Conductors (2-D)
EMF-7 Magnetic Field (3-D)
EMF-8 Magnetic Induction in Wires Parallel to Transmission Lines
EMF-9 Distant Magnetic Field Equations for Transmission Lines
EMF-10 Electric Field Induction on Objects
EMF-11 Magnetic Field Reduction Using Cancellation Loops (3-D)
EMF-12 Magnetic Field Reduction Using 4th-Wire Scheme
RN-1 Electromagnetic Interference up to 30 MHz
RN-2 EMI Calculation Using Empirical Methods
RN-4 Traditional Radio Noise Calculation Method
S-1 Switching Surge Flashover Model

The Applets that are not implemented consist of those calculations that are implemented
elsewhere, or are purely training modules.
After the selection, full integration was initiated. Project activities with a planned completion
date for 2006 was prepared last year and are shown in Table 3-1 on the next page. The Table
lists in detail the software development from the Concept Development to Test & Integration.
According to the original plan, Beta Testing of the new software would begin the end of this
year. Due to staff workload and departure of software staff from the Haslet Engineering Center
that was closed this September, the project is about 3 months behind schedule. For continuity,
development of the TLW software is being contracted to the former EPRI staff who worked on
the software. He will dedicate most of his time on this project to meet the 2007 completion date.

The integration has reached the Alpha testing stage the end of 2006. As part of software
approval process, appropriate documentation was prepared. A list of these documents can be
found in the next Chapter under Document for the Project.

3-7
Implementation PLan

Table 3-1
Project Activities Schedule for 2006

Key: X = primary responsibility; R = review; A = approval required

EPRI EPRI Software User Planned
Project Corporate Developer Completion
Manager Software
Quality

Step 1: Concept Development

Determine User Requirements X R Completed
Software Contract Package X RA Completed
Developer Qualifications Review RA RA X N/A - EPRI Staff
Step 2: Defining Requirements
Software Requirements Document & Review RA RA X R This Document
Functional Specification & Review RA RA X R This Document
Software Development Project Plan & RA RA X This Document
Review
Step 3: Design and Implementation
Identify data common to multiple Applets X 10/15/2005
Re-design objects to encapsulate X 11/1/2005
functionality
Re-design Dialogs to maintain data X 12/9/2005
Design database for data storage and retrieval X 12/16/2005
Design new Application Framework X 12/31/2005
Detailed Design Document RA RA X 12/31/2005
Create Test Cases RA R X 12/31/2005
Build new application prototype X 3/29/2006
Software Prototype & Review RA X R 3/31/2006
Implement Change Requests and Unit Tests X 6/30/2006
Step 4: Test & Integration
Alpha Test RA RA X 7/14/2006
Draft Documentation RA R X 7/14/2006
Beta Review by EPRI RA RA X 9/17/2006
Beta Test RA X R 12/31/2006
Implement Change Requests and Unit Tests X
Submit Final Software RA X
Step 5: Acceptance
Prescreen & Begin EPRI Acceptance Testing RA X
Complete Software & Documentation X
Software Release XRA
Step 6: Distribution & Maintenance
Set up Software Distribution X
Support & Maintenance Releases RA RA X

3-8
Work for 2007

After Alpha testing of the prototype software, it will be developed further for the Beta Test.
Additional documentation will be required and will be filed with the Software Evaluation Team
(SET) of EPRI prior to the Test. Volunteers will be sought for Beta Test evaluations. Often this
request is made at Task Force meetings and Webcasts. Additional improvements as requested by
the Beta testers will be implemented. The revised software is then submitted to SET testing.
Anomalies detected by the SET must be corrected before the software is approved for release.
This process is vigorous and could take a few iterations.

Along with the other projects in Project Set 35C, two task force meetings are scheduled for 2007
on March 27 - 28 in Palo Alto, CA and September 18 - 19 in Washington, DC. Webcasts will be
held on May 30 and November 6.

Integration of the listed applets will be completed by the end of 2007. The new modules will
have the most recent algorithms and data from the Red Book. In some cases, 3-D model is
available instead of the 2-D model in the existing module. Only one single input is required for
all these calculations instead of one for each applet.

In addition to the integration, the feasibility of interfacing TLW with transmission line layout
software packages such as PLSCADD and TLPRO will be explored. In consultation with Task
Force advisors, the direction of the TLW will be discussed and determined for future work.

Future Work

Many questions remain as to the full scope of the project beyond 2007. Upon completion of the
first phase of integration, future activities can be established. An immediate activity for 2008 is
to bring FAD 4.0, the upgraded version of FAD, into TLW. Another option is to improve and
update the TLW user interface. The ultimate goal is to develop TLWorkstation to be the
depository of all transmission line design programs covering different disciplines of engineering.

3-9
4
SOFTWARE APPROVAL PROCESS

EPRI software generally did not receive high marks from the users in the past. Quality was
inconsistent and problems were often encountered. Experience in using application software
developed by EPRI could be frustrating and unpleasant. On the other hand, lack of
documentation from software developers had made improvements of older software expensive
and extremely difficult.

In response to all these concerns, EPRI has in recent years established a software approval
process to assure that all software from EPRI is of high quality. The process not only
guarantees a certain standard for the software but also saves software development cost in the
long run. The procedure applies to both software developed internally by EPRI staff and that
developed externally by contractors. Thus, integration of the Red Book applets into TLW and
future modifications of TLW must be subjected to this process.

Before starting the development of the software, the qualifications of the software developer
along with a development & quality assurance plan must be submitted to EPRI for review and
approval. The software is then developed according to the pre-approved plan. When the
developer completes its software and prior to its release for Beta testing, the software must first
be reviewed by EPRI Software Evaluation Team (SET) to ensure no major problem will be
encountered and that the software can be installed properly. The software is then released to the
users. Upon completion of Beta-testing, feedbacks from Beta-testers are documented for
consideration of improvements by the software developer. Following the changes, the software
is put under vigorous testing conducted by the Software Evaluation Team. The software could
goes through a number of cycles of testing until all anomalies have been fixed.

There are two types of requirements for EPRI software:

Product Requirements
Development Process Requirements.

The following provides detail descriptions of these requirements.

Product Requirements for All EPRI Software

The requirements in this section apply to both new software and upgrades of existing software.
Additional requirements for new software appear in the following section.

4-1
Software Approval Process

Developers must validate and verify that the calculations and other operations performed by the
software yield correct results. EPRI Software Acceptance Testing concentrates upon ensuring
that the software is reliable and easy to use.

The items in this section are formally evaluated during Software Acceptance Testing. Acceptable
quality levels must be reached before an "A" is issued, approving software for distribution.
The EPRI Copyright, Ordering Information, and Disclaimer Notice elements for software appear
as required by EPRI legal staff.
The User Manual and any handouts for users that will accompany the software will be
distributed in electronic form, on the same CD with the software. The User Manual, in the form
of a Microsoft Word document, must be submitted for acceptance testing in a separate directory
on the CD (directly off the CD root directory) called Manuals. Any other documentation or
handouts for users must also be placed in the Manuals directory. Be sure to discuss any
exceptions with EPRI Corporate Software Quality.
Any media duplicated outside of EPRI must include the new Product ID number for the release
on the label. This number is obtained by the EPRI Project Manager from the Apollo system
Product Master.
Installation is straightforward
Graphical user interface (GUI) is easy to use. A GUI supported by the Microsoft Windows
operating system is required unless an exception has been approved by EPRI Software Quality.
User documentation and on-line help are complete and easy to use
Error messages must be clear and direct the user to a solution
System response time meets industry performance standards
Software coexists with other products on the platform
The user documentation must include solved example problems (also called test cases), with
active user input and interaction. The examples will show users how to use the main features of
the application, and will help them verify that the software is working correctly. A self-guiding
tutorial can be used to meet this requirement.
Outputs from solved example problems or tutorial must match user documentation when
specified inputs are entered
An uninstall procedure is present.
The opening screen of the software (also called the launch screen or "splash screen," seen each
time the program is used) prominently displays the EPRI copyright and EPRI wordmark.
Applications must support copying and pasting of relevant data to Microsoft Office applications.
The exact nature of copying and pasting required by each application is dependent on the
application's functionality and features. The goal is to enable users to easily manipulate data,
store the data back in the application, and create customized reports. Single text field copying
and pasting is not sufficient to meet this requirement. For tabular data, a standard tab- or comma-
delimited export function is also required to avoid dependence upon a specific release of Excel.

4-2
 Software Approval Process

Software must be designed for the Windows 32-bit platform (is coded using 32-bit internal
architecture, not 16-bit). Exceptions must be documented and approved by the EPRI software
quality manager.
A Windows-based (not DOS-based) graphical user interface (GUI) is required. New software
must implement a GUI using Windows GUI system calls. Software must support, at a minimum,
Microsoft Windows 2000 and XP platforms. Exceptions must be documented and approved by
the EPRI software quality manager.
Internationalization: End users for all software will be able to choose, by changing the regional
settings of their operating system, to the country of their choosing and the application will pick
up the proper units of measure, currencies, date formats, and number formats. If data has been
already entered into the application or stored in a file or database, then the users needs to be told
what will happen to the data already entered or stored.

The options are:

o Convert the data already entered to the new units or format. This would have to be
done by the application conversion program
o Use the original data and format type for data already entered or stored and the
new format for new data. The application program would have to make this
happen correctly
o The application program could clear the fields of the application where data was
already entered

The user manual should document the expected results and the user interface should provide
information or warning indicating what changes will occur when a user changes the regional
settings. Exceptions must be documented and approved by EPRI Corporate Software Quality in
the development plan.

Where numbers are used with scientific units the ability to use both US English and Metric (or
SI) units is required.

The specific units to be converted, and the types of conversions, will be determined for each
software project, based upon user requirements. There is no single definition to be followed.

Localization: Localization is generally the issue of providing the application in the local
language, or supporting multiple languages. It is optional, but useful, for international users to
have all GUI screen text information and error messages in a file that can be easily translated and
loaded into the program on initiation. Some special domain projects may have specific
Localization requirements defined in advance. For all applications the Localization plan will be
documented in the lifecycle plan and requirements documents.

Maintenance & Local Language Support: All messages, such as error messages and on-line help,
must be placed into a single table, file, or other central location. This will ease software
maintenance as well as the implementation of future local language support.

4-3
Software Approval Process

Security Policy

As a minimum, the following requirements will be met:

Security issues and security plan for the software will be covered and described in the planning
documents (e.g., Functional Specifications, Software Requirements Document, etc.) and in the
User Manual.
Software is free from viruses.
No passwords are viewable in plain text nor are passwords kept in an open-access file or
database in plain text. Plain text may be used in databases or files that can otherwise be secured
from general users.
There is no "backdoor" method to enter the software.
There are no "Trojan horses" or similar detrimental coding in the software.
Software is written in a manner that promotes the highest security state applicable for this
software.
Software uses Authentication and Access control as appropriate.
Software must offer ability to use Windows Authentication as well as proprietary Authentication
when both are available (i.e., using Windows Authentication and MS SQL Authentication).
Software is delivered in the maximum security state as stated in the design documents (e.g., the
documentation has warnings and clear directions to set up the security states; software that uses
passwords and administrative functions have them enabled).

4-4
 Software Approval Process

EPRI Software Development Process Requirements

Table 4.1 on the next page provides detail steps that a software developer must take in the
development of the software, starting from concept development, software design,
implementation, testing to distribution & maintenance. The functions and responsibility of each
party including the EPRI project manager, EPRI software quality team, the software developer as
well as the user at each step are clearly defined.

Both of EPRI’s product requirement and development process requirement combined to assure
only high quality software packages are produced. A copy of the Software Acceptance Form
forming part of the product requirement is shown in Table 4.2. The SAF provides some insight
into the stringent requirements demanded from all EPRI software.

Documents for the Project

As part of the software approval process, the following documents have been prepared for the
new TLWorkstation in order that it may be evaluated by users in the Alpha testing.

1. Software Acceptance Form

2. Software Life Cycle Management

3. Software Requirements

4. Functional Specifications

5. Software Quality Assurance Plan

Documents 3 and 4, which contain information relevant to the users, are attached with the report
under Appendix B and C respectively for references to the reader.

4-5
Software Approval Process

Table 4-1
EPRI Process Table and Planned Schedule
Software Name___________________________________ Version ____________ Date: _____________
(Up to 20 characters can be inserted in the right hand column of this table. The other parts of the table cannot be
modified.)
Key: X = primary responsibility; R = review; A = approval required
EPRI EPRI Software User Schedule (fill
Project Corporate Developer in your
Manager Software dates)
Quality
Step 1: Concept Development
Determine User Requirements X R
Software Contract Package X RA
Developer Qualifications Review RA RA X
Step 2: Defining Requirements
Software Requirements Document & Review RA RA X R
Functional Specification & Review RA RA X R
Software Development Project Plan & Review RA RA X
Step 3: Design
Software Prototype & Review (optional) RA X R
Detailed Design Document (optional) RA RA X
Step 4: Implementation
Project Plan Status Review(s) RA R X
Create Test Cases RA R X
Unit Tests X
Step 5: Test & Integration
Alpha Test RA RA X
Draft Documentation RA R X
Beta Review by EPRI RA RA X
Beta Test RA X R
Submit Final Software RA X
Step 6: Acceptance
Prescreen & Begin EPRI Acceptance Testing RA X
Complete Software & Documentation X
Software Release XRA
Step 7: Distribution & Maintenance
Set up Software Distribution X
Support & Maintenance Releases RA RA X

4-6
 Software Approval Process

Table 4-2
Software Acceptance Form (SAF):
Acceptance Testing, Publishing, and Distribution Web and PC Applications

Process Stage: Alpha Beta Prescreen Final Acceptance Test

INSTRUCTIONS: Submit this Word document as an email attachment. Software at all process stages
must be tested before being sent to the customer. The EPRI Project Manager completes Parts 1, 2, 3
and 5. The Software Developer completes Part 4.

Alpha, Beta and Prescreen: Complete Part 1. If some items do not apply, please enter “NA”. Be sure to
include contact information for EPRI Project Manager and Developer, and a Work Order Number.
Final Acceptance: Complete all sections. Missing information will delay software approval. If some items
do not apply, please enter “NA”.

4-7
Software Approval Process

Today’s Date: Work Order No.: EPRI Sector:

PART 1: GENERAL INFORMATION

A. Contact Information

EPRI Project Manager: Phone(s):

Administrative Assistant Name: Phone(s):

ESI Project Mgr. Name (if applicable):

ESI Work Order Number:

Developer:

Company Name: Phone(s): Fax:

Address: City: State: Zip:

Software Programmer
Phone(s): Email:
Contact:

Software Support: Please refer all support inquiries about this software to:

Developer Other - support contact information is:

Company Name: Phone(s): Fax:

Address: City: State: Zip:

4-8
 Software Approval Process

Support Contact: Phone(s): Email:

B. Product Information

Blue Chip: Yes No

Planned Completion Date
(PCD): If Yes: Corporate Sector
Business

Software Product ID #:

Note: Please work with your Apollo Product Master representative to obtain ID#.

Software Acronym:
Version or release number:

Full name of software:

Part of a multi-code group or workstation? No Yes, (Name)

Software Type: PC Software Other (describe)

Web Application - Who have you contacted in IT Apps

If not already submitted, please fill out and submit the Web application form
at: http://insideepri/epri%5Fcom/webapplicationchecklistform.htm

Is this software data only? No Yes, If Yes: Database

Spreadsheet

s this a: New Application Modification of Existing Application,

(Name) Other (describe)

4-9
Software Approval Process

For this modification or upgrade, a list of enhancements made is attached. Yes

No

PART 2: TECHNICAL BACKGROUND

A. Final Acceptance Testing Checklist

PC Applications and Web Applications:

User Documentation is included: (indicate type provided)

A User Guide or other accompanying documentation is provided in

electronic form

On-line help substitutes for a User Manual

Other types of User Documentation: (describe)

Hard copy of each user documentation item is included.

User guide and other accompanying documentation is provided in MS Word

format, using the EPRI Technical Publishing template, on the same CD with
software, in a separate directory off the root directory called Manuals

The User Documentation (User Guide or on-line help) contains solved example
problems or a tutorial showing users how to use the main features of the
application. These examples also help users to check that the software installed
properly and is working correctly.

Additional items submitted to testing: (describe):

Web Applications and Web Sites Only:

4-10
 Software Approval Process

URL for testing: This Web App has a User Manual Yes
No

PC Applications Only:

Specify media (preferred media is CD-Rom) that is provided for testing and how
many are provided.

Executable software application:

Source code

Security/Unlock Code (If required):

Software Life Cycle Management Document

http://www.epri.com/eprisoftware/processguide/swurr.html#LifeCycleManagement
Yes No If no, please explain:

B. System Requirements & Development Data

Ensure that these match the user documentation.

System requirements needed for standard, typical use:

Database requirements (Oracle, etc.): Third-party software required – note

release IDs:

Software key, password, or hardware key required? No Yes,

(describe)

Other installation dependencies, such as hardware or software the user must

install besides this software application:

Programming Third party What installation software

4-11
Software Approval Process

language(s) used: development tools was used? (InstallShield,

used: WISE, etc)

PC Applications Only:

Is this software designed to install on a server, with multiple users? Yes

No

If yes, can the software also be installed and used on a non-networked computer?
Yes No

C. Results of Beta Testing

At least 3 beta test users outside of EPRI are required, who exercise the software
utilizing their own data. Below are the summarized results of testing the software
functions, ease of use, installation instructions, and documentation. It is highly
recommended to name the beta testers (with their permission) in the
Acknowledgments section of the User Manual.

Is a copy of the beta test evaluation forms and test plan submitted? Yes
No If no, please explain:

Number of beta testers: planned: Number of beta test bugs reported:

Number of beta test bugs unresolved:

Number who provided feedback:

Number of unresolved bugs at each severity level: Critical Severe

Minor

Number of enhancements suggested during beta testing that were not incorporated
in this version:

4-12
 Software Approval Process

PART 3: PUBLISHING & DISTRIBUTION INFORMATION

A. Distribution

Note that the software is zipped with the user documentation and made
downloadable from epri.com when released for distribution. If you have user
groups where not all members are EPRI funders, establishing a Casper list will
enable them to download this software.

The software will be distributed by:

EPSC (EPSC distribution is expected) Other distributor (provide details):

Web site on epri.com (provide URL): Other web site (provide name
and URL)

Prior software products:

Remove previous release from distribution? Yes No

B. Software Description

Software will not be made active until the Project Manager has approved the
Product Description with Technical Publishing (Tech Pubs). Items 1-4 below are
required for the Software Description. View example Software Description at:
http://inside/marketingcr/marketing/TechnicalPublishing/docs/SoftwareDescription
Sample.pdf

1. A single sentence describing the overall technical capability that the

software provides (e.g. “The ABC software version xx enables users to
analyze…..”):

2. One paragraph (4 or 5 sentences) providing a summary description of the

software. Also note if customers will incur additional expenses to utilize the

4-13
Software Approval Process

software such as customization, training, purchasing a supporting program, user

group fees, license fees, etc:

3. Bullet points (2 or 3) highlighting the Benefits and Value provided by the

software:

4. Keywords (6 or less):

5. One screen shot showing key features of the software (optional) One way
to do this is to press ALT + PrintScreen; then select Edit>Paste to save a .BMP file
in Windows Paint.

Screen shot is attached: Yes No Please see complete

instructions at
http://inside.epri.com/marketingcr/marketing/templates.htm#techpubstemp

Additional Descriptive Information

Special additional actions needed by Customers to use the software (e.g. extra
license payments or fees required, joining user groups, installation services,
mandatory customization, training, unusual equipment):

Is software encryption (e.g., keys, database keys, data transfer, etc.) used or
required? Yes No

If yes, please provide specific information about the encryption: . If not

yet filled out, please complete the Encryption Document (link below) and submit
it to York Huang ("cc" your Software Quality Manager).
http://www.epri.com/eprisoftware/processguide/docs/Encryption.doc

Does this software support international/SI units of measure?

Yes No

If yes, please explain which units are used, and when conversions are available
(e.g. at start of program, at any time): .

4-14
 Software Approval Process

C. User Manual

An electronic copy of the user documentation will automatically be included on the

distribution CD-ROM.

Manual will ONLY be provided together with the software

If manual will be available separately from the software, please see the
following link:
http://inside/marketingcr/marketing/TechnicalPublishing/docs/pubform.doc

D. License & Copyright

For appropriate legal protection, EPRI's Intellectual Property staff has advised that
EPRI software needs to use Executable Licenses. EPRI members' Master
Agreements provide this license automatically. Other purchasers of EPRI software
will be contacted after an order is placed, so that they can sign the needed license.

Copyright alone is used when software is intended for free and universal public
use. (Please note that "shrinkwrap license" is no longer an option for EPRI
software, as it does not provide legal protection to EPRI.)

Encryption greater than 64 bit may require a special license which may take 90
days to process.

For legal advice, please contact EPRI’s Intellectual Property staff

Corporate Owner & License Category:

EPRI Copyright EPRI Executable

EPRIsolutions, Inc. Copyright EPRIsolutions, Inc. Executable

EPRIsolutions, Inc. Private A EPRIsolutions, Inc. Private B

4-15
Software Approval Process

Other: Describe any special licensing requirements (e.g. third-party software

restrictions):

Copyright Owner(s): EPRI (501) EPRI Solutions, Inc. (ESI)

Other (Legal Name):

E. Initial Distribution

The EPRI Project Manager will receive 1 copy of the product.

EPRI Project Manager wishes the software developer to receive a copy of the
final product.

PART 4. DEVELOPER’S REQUIREMENTS

A. Software Documentation

Copies of these documents have been submitted to the Software Engineering Team
(SET):

Software Development Project Plan

http://www.epri.com/eprisoftware/processguide/sdp.html

Yes No If no, please explain:

Software Requirements Document

http://www.epri.com/eprisoftware/processguide/srd.html

Yes No If no, please explain:

Functional Specification
http://www.epri.com/eprisoftware/processguide/funcspec.html

4-16
 Software Approval Process

Yes No If no, please explain:

Source Code Transmittal Letter

http://www.epri.com/eprisoftware/processguide/docs/exsctl.doc

Yes No If no, please explain:

Developer’s Quality Assurance Plan

http://www.epri.com/eprisoftware/processguide/csqap.html

Yes No If no, please explain:

If contract was executed BEFORE June 1, 2005, a Developer’s Submittal Report is

required, not a Certificate of Conformance.

Developer’s Submittal Report

http://www.epri.com/eprisoftware/processguide/docs/DSReport.doc

Yes No If no, please explain:

If contract was executed AFTER June 1, 2005, a Certificate of Conformance is

required, not a Developer’s Submittal Report.

Certificate of Conformance
http://www.epri.com/eprisoftware/processguide/swurr.html#ConformanceStatement

Yes No If no, please explain:

B. Developer’s Signature

By signing below, the developer certifies that the software meets all requirements
in the developer’s corporate quality plan, EPRI’s software development
requirements, security policies, requirements of the contract to develop the

4-17
Software Approval Process

software, and the developer’s submittal report.

Signature: ________________________ Date: _____________ _

Printed Name: _____________________________Title: ________________________

PART 5. AUTHORIZATIONS:

Release to Testing (Project Manager)

Signature (may be replaced by email message): _____________ Date:_________

Software Testing Approval for Distribution

This section for use by Software Testing

“A” Acceptance Release:

EPRI Software Quality Manager Authorized Signature: ___________Date:_________

Software ID for Distribution Master Media: SQA ID # ___________________

4-18
A
APPENDIX

Terms found in manual for FAD 3.0:

Adhesion Factor
Atterberg Limits
Backfill Density for Spread Foundation
Belled Shaft
Chemical Alteration of Soils
Clay Sample
Coefficient of Horizontal Soil Stress (Ko)
Coefficient of Permeability
Cohesion Intercept
Concrete Types
Cone Penetration Test (CPT)
Consistency of Cohesive Soils
Construction of Shaft
Deep Soft Silt
Density
Desiccation
Dilatometer Test (DMT)
Direct Embedment
Drained and Undrained Conditions
Drilled Shaft
Eccentricity
Effective Stress
Elastic Behavior of Soils
Erosion of Overlying Soil
Excavation
Fall Cone Test
Friction Angle
Friction Angle Laboratory Tests
Geologic History
H-Frame Structure
In-Situ Coefficient of Horizontal Stress (Ko)
In-Situ Test Methods
Interface Friction Angle
Large Boulders
Lattice Towers
Liquid Limit
Lowering or Raising of the Ground Water Table
Material Index (ID)

A-1
Appendix

Oedometer Test
Operative/In-Situ Coefficient of Horizontal Stress
Overconsolidation Ratio (OCR)
P-delta
Particle Size and Distribution
Pile Foundation
Plastic Limit
Plasticity Index
Pocket Penetrometer
Poisson's Ratio
Pressuremeter Test (PMT)
Relative Density of Cohesionless Soils
Rock
Sand Sample
Single Pole or Guyed Structure
Site Access
Soil Characteristic
Soil Types
Spread Foundation
Standard Penetration Test (SPT)
Stiff Crust
Substation Structure
Time-Dependent Deformability of Soils
Tip Suction Stress
Torvane
Triaxial Compression Test
Tube Sample
Unconfined Compression Test
Undrained Shear Strength
Unit Weight/Density
Vane Shear Test (VST)
Walls of Foundation Holes
Young's Modulus

A-2
B
SOFTWARE REQUIREMENTS

B-1
 Software Requirements
For
TL Workstation Design Tools

Prepared By: Ian C. Baskerville Date: 9/8/2006

Reviewed By: Date:

Approved By: Date:

B-3
Software Requirements TL Workstation Design Tools Rev. 0

Record of Revision

Date: Revision: Section: Description:

09/08/2006 00 All Original Release

B-4
Software Requirements TL Workstation Design Tools Rev. 0

Table of Contents

RECORD OF REVISION.......................................................................................................... B-4

TABLE OF CONTENTS ........................................................................................................... B-5

INTRODUCTION ..................................................................................................................... B-7

Purpose.................................................................................................................................. B-7
Background............................................................................................................................ B-7
Strategy ................................................................................................................................. B-7

BUSINESS REQUIREMENTS .................................................................................................. B-8

Current Tools ......................................................................................................................... B-8
Objectives .............................................................................................................................. B-9

FUNCTIONAL REQUIREMENTS ......................................................................................... B-10

Primary Requirements........................................................................................................... B-10
User Interface....................................................................................................................... B-10
Hardware Interfaces .............................................................................................................. B-11
Software Interfaces ............................................................................................................... B-11
Communications Interfaces.................................................................................................... B-11
Memory Constraints.............................................................................................................. B-11
Design Constraints................................................................................................................ B-12
Installation ........................................................................................................................... B-12
Assumptions......................................................................................................................... B-12

NON-FUNCTIONAL REQUIREMENTS ................................................................................ B-13

Performance Issues ............................................................................................................... B-13
Security ............................................................................................................................... B-13
Configuration, Compatibility and Usability ............................................................................. B-13

USER INTERFACE REQUIREMENTS .................................................................................. B-14

Sample Forms ...................................................................................................................... B-15
Data Source Connection Dialog......................................................................................... B-15
Application Main (MDI) Form .......................................................................................... B-16
Open Project Dialog ......................................................................................................... B-16

B-5
Software Requirements TL Workstation Design Tools Rev. 0

Child Form ...................................................................................................................... B-17

B-6
Software Requirements TL Workstation Design Tools Rev. 0

Introduction

Purpose

Integrate the Applets, from the third edition of the Transmission Line Reference Book – 200
kV and Above (the Red Book), into a desktop application. This application will replace the
ACDCLine and RNoise Applications that were part of the TLWorkstation version 3.0. It will
apply the updated algorithms used in the Applets, and update the User Interface to comply
with modern programming standards, using the latest software technology.

Background

Over the years, the Electric Power Research Institute (EPRI) has published a number of
world-renowned transmission line reference books and software, which are considered an
industry standard and are valued by many transmission companies and engineers. In addition,
EPRI issued the TLWorkstation (TLW) in the early 1990s, a comprehensive transmission
line design package that has a very strong set of users. In 2004, EPRI published the third
edition of the Transmission Line Reference Book – 200 kV and Above (the Red Book), along
with a suite of some 50 small software routines to help the reader employ the design theory
within the book. These software routines are targeted for the reader of the Red Book and
were not developed as an integrated design package. The software package in TLW contains
a number of design modules, many of which were based on the previous version of the Red
Book. With changes in the Red Book, it is necessary to review the present status of the TLW.

At the same time, new transmission line design packages have entered the market in recent
years. Consequently, a number of these tools, each with unique benefits could be integrated
into the TLW to form a more complete software package. For example, there are exceptional
commercial transmission line mechanical and 3-D graphical design packages. It would be
ideal to bring these design tools together, since the TLWorkstation is a leader in electrical
design, with a number of the existing modules in daily use by the global power delivery
industry. This combination would involve identifying the best of breed and then ensuring that
the best EPRI products work in an integrated fashion with the best commercial software.

Strategy

As a result of transmission expansion in some parts of the world such as South America,
South East Asia and Africa, and also the recent round of blackouts, it is clear that there is
renewed interest in building new transmission lines. The need to consider construction of
high voltage transmission lines is also captured in some of the recent US Government
Department of Energy documents. In the past there has been a slump in overhead line

B-7
Software Requirements TL Workstation Design Tools Rev. 0

construction. Consequently, skill levels within the industry have declined. Further, there are
very powerful CAD and line layout design software packages that are almost considered
industry standards that have not been interfaced with EPRI’s TLWorkstation. Combining
with the new edition of the Red Book, it is therefore crucial that TLW must be updated to
address all these changes and challenges.

The general strategies are as follows:

Identify one or more key line design packages, such as the PLSCAD and TLCADD, that
are very strong on the graphical and structural aspects of line designs
3. Develop a standard to move data between EPRI design modules and other design
software
4. Focus on enhancing EPRI modules, ensuring that they are very robust and reflect the
latest thinking
5. Look to market these modules as either stand alone or packages that can be loaded up
alongside the commercial software.

Business Requirements

Current Tools

Currently, there are a limited number of tools available to designers to analyze Electric,
Magnetic and Noise characteristics of existing and planned Transmission Lines. One of
those applications in general use is the ACDCLine and RNoise applications that are a part of
EPRI’s TLWorkstation version 3.0, released in 1997.

Unfortunately, these TLWorkstation modules have not been upgraded since their release.
Additionally, with regards their underlying architecture,
• They are written using Microsoft Visual C++ version 1.5, which was the last version
capable of creating 16-bit Windows applications that would execute under Windows
3.1.
• They use the WATCOM SQL database as the underlying database. This was a 16-bit
database, which has not been supported in over 5 years.
• It uses an old version of EasyPlot to display graphs of the analysis results. Many of
these graphs would only work if the application was executing under Windows 3.1.
While these modules still install and execute on current Windows 32-bit operating systems,
there is no promise that Microsoft will ensure that future Windows operating systems will be
backward compatible to the 16-bit realm. (In fact, I have been unable to install it under
Windows XP Professional 64-bit.)

The Red Book Applets were created as a companion to the Transmission Line Reference
Book – 200 kV and Above 3rd ed. Though the work well as a way to demonstrate individual
aspects of Transmission Lines, they are generally individual and independent modules:
• Each Applet saves and loads user entered data in their own individual and
inconsistent format.

B-8
Software Requirements TL Workstation Design Tools Rev. 0

• The data is stored in individual disk files, in arbitrary directories.

• The circuit configurations entered into one Applet has to be re-entered in another for
analysis in that Applet.
• The information entered cannot generally be edited. Any information entered
incorrectly, must be deleted and the corrected item re-entered.
As far as the underlying architecture is concerned, the Applets were written, starting in 1996,
with Microsoft Visual J++ version 1.1 (although the code conforms to the earlier Java
version 1.0 event and object model). Unfortunately, due to the age of that development
platform and the fact that Sun Microsystems won a lawsuit against Microsoft in 2000
ordering them to cease Java development and support by 2002; there is no support from
Microsoft for applications written in Visual J++. Also, there is no support from any other
Java development environments for conversion of Visual J++ code to other platforms. So, all
conversion of User Interface code written with Visual J++ must be done manually
(Completely Rewritten.).
What the Red Book Applets provide are the implementations of updated algorithms,
including support for field calculations in 3 dimensions.

Objectives

The primary objective of this project is to create an application that will replace the
ACDCLine and RNoise modules in TLWorkstation as the first step in maintaining the
viability of EPRI’s TLWorkstation software.

Additional objectives are:

• Include updated algorithms, specifically 3-D calculations;

• Improved Import, Export and SaveAs functionality;
• Improved Data Input Forms, with graphical feedback;
• Improved maintainability by using up-to-date development platforms;
• Provide architecture that can be linked to other software packages.

B-9
Software Requirements TL Workstation Design Tools Rev. 0

Functional Requirements

Primary Requirements

This program will replace the ACDCLine and RNoise modules in TLWorkstation by
implementing the following Red Book Applets:

Applet Description
AN-1 Audible Noise of Transmission Lines
AN-2 Audible Noise of Transmission Line (3-D)
AN-3 Bundle Geometry for Minimum Audible Noise
AN-4 Audible Noise, Hum
AN-6 Audible Noise vs. Rain Rate
CC-1 Conductor Surface Gradient (2-D)
CC-2 Conductor Surface Gradient (3-D)
CC-3 Surface Gradient on Toroidal Corona Shields
CC-4 Conductor Tables
CC-5 Transmission Line Parameters (Single Circuit)
CL-1 Transmission Line Corona Loss
CL-3 Ozone Concentration near Transmission Lines
EMF-2 Electric Field of Transmission Lines in 2-D
EMF-4 Electric Field of Transmission Lines in 3-D
EMF-5 Electric Field Shielding by Grids of Wires - 2D
EMF-6 Magnetic Field from Sets of Current Carrying Conductors (2-D)
EMF-7 Magnetic Field (3-D)
EMF-8 Magnetic Induction in Wires Parallel to Transmission Lines
EMF-9 Distant Magnetic Field Equations for Transmission Lines
EMF-10 Electric Field Induction on Objects
EMF-11 Magnetic Field Reduction Using Cancellation Loops (3-D)
EMF-12 Magnetic Field Reduction Using 4th-Wire Scheme
RN-1 Electromagnetic Interference up to 30 MHz
RN-2 EMI Calculation Using Empirical Methods
RN-4 Traditional Radio Noise Calculation Method
S-1 Switching Surge Flashover Model

The Applets that are not implemented consist of those calculations that are implemented
elsewhere, or are purely training modules.

User Interface

This application will be an MDI Application based on a Project/Detail data format. (The original
TLWorkstation modules were SDI applications based on the same Project/Detail underlying data format.)

Each Detail constitutes a unit of work that includes the information related to an example Right-of-Way or
Circuit configuration. Each open configuration is managed with one MDI Child window.

B-10
Software Requirements TL Workstation Design Tools Rev. 0

Multiple child windows can be opened at a time, so that the user can directly contrast and compare multiple line
configurations.

All analysis and reporting functions are accessed from the Menu of the MDI Parent window.
Analysis and Reporting functions should operate on the active Child form, all Child forms or the open project as
a whole.

The results are presented to the user in application dialog windows, or optionally exported as Microsoft Word or
Excel documents.

The results are presented as text and graphs, as well as 3-D, navigable models.

Hardware Interfaces

This software will be written in Microsoft C#, which runs under the Microsoft .NET Frameworks implemented
on Windows OS. New versions of Windows are distributed with the .NET Frameworks. The earliest Windows
OS version that will support the .NET Frameworks version 2.0 is Windows 2000 Service Pack 3.

Software Interfaces

This application will have the ability to export the results of calculations to Microsoft Word
or Excel documents if available.

Output forms will provide the Clipboard Copy functionality to allow for the copy and pasting
results into other applications.

Import and Export functions will be provided. These will ostensibly for transferring data
between different TLWorkstation databases. However, the data will be XML compliant so
that it can be viewed and/or processed using standard XML tools.

An Import function will be provided to import data from PLS-CADD.

Communications Interfaces

No direct internet communication methods to transfer data will be implemented.

Memory Constraints

The application will be tested to ensure it will execute reasonably well on 1GHz Windows
2000 systems with 256MB.

All graphical output will be optimized to use the minimum necessary memory.

Testing will include examination of the calculation limits. Some of the 3-D calculations,
based on the circuit configuration involved and the level of detail and precision requested by

B-11
Software Requirements TL Workstation Design Tools Rev. 0

the user can result in the use of very large matricies. These situations will have to be
examined in the test plan.

Design Constraints

No design constraints other than those described in the Hardware and Software configuration
sections.

Installation

Installation programs will be provided in the form of conventional Setup executable

(Setup.exe) and a Windows Installer (*.msi) module. The installation will include Microsoft
.NET Frameworks version 2 installer, in case it does not exist on the target system.

Assumptions

All prospective customers for this application will be using Windows 2000 or later.

B-12
Software Requirements TL Workstation Design Tools Rev. 0

Non-Functional Requirements

Performance Issues

Some of the 3-D Applet calculations may take some time to complete, depending on user
selected parameters for those calculations. The Test Plan will be designed to test the
performance of these calculations. Reasonable limits will be imposed by the system, based
on this testing. However, those limits will be generous. The help and documentation will
include discussion and guidance regarding the parameter selection, so that the user can be
prepared for the wait.

Security

The default data source, supplied with this application will not have security implemented.
Data Source Security will be assumed the responsibility of the Data Source, where a different
data source may be used.

Configuration, Compatibility and Usability

This application will comply with the latest Windows Design standards using .NET 2.0
Windows Forms. It will take advantage of the components provided as part of that platform
to ensure consistency with respect to other future Windows applications. Except for
graphical display output, all components will use the Windows System Colors determined by
the user selected Windows Theme to ensure consistency between this application and other
applications on the user’s desktop. And, as a result, no issues should be encountered where
the clarity and appearance of this application on the desktop would be inferior to that of other
applications. In the graphical display output, or where different colors and fonts (other than
default system values) may be used, the user will be provided the capability of changing
those colors or fonts.

B-13
Software Requirements TL Workstation Design Tools Rev. 0

User Interface Requirements

The user interface will be designed such that it could execute on systems with a minimum
monitor size of 1024 by 768, though it will be designed such that it can take advantage of
systems with larger monitors (or where the user would be willing to devote more screen
space to this application).

Most forms will be designed to use Windows System Colors for text and backgrounds in
order to ensure for maximum clarity and consistency. Exceptions will be noted.

Most text will be displayed with an 8.25 pt Tahoma Font. (Windows applications
traditionally used Microsoft Sans Serif Font; but the new standard is Tahoma, which better
distinguishes characters like a lowercase ‘L’ and an uppercase ‘I’).

The application will be an MDI Application based on a Project/Detail data format. Each Detail constitutes a
unit of work that includes the information related to an example Right-of-Way or Circuit configuration. On
entry, the user opens a project, and creates or selects individual configurations with which to work. Each open
configuration is managed with one MDI Child window. Multiple child windows can be opened at a time, but
only one at a time is the active window. All analysis and reporting functions are accessed from the Menu of the
MDI Parent window. Those functions generally only operate on the configuration maintained by the active child
window. However, additional menu options will be provided to allow the user to run analyses and reports on all
open details or the open project as a whole.

The results are presented to the user in application dialog windows, or optionally exported as Microsoft Word or
Excel documents, which will automatically be loaded as separate desktop windows (not under direct control
from this application). The results are presented as text and graphs, as well as 3-D, navigable models.

Except for results windows, which will be modeless forms; all forms will be modal forms.

All data entry for a given configuration will be accomplished through one MDI Child
window instead of a sequence of dialogs (as in the old TLWorkstation). The Child window
utilizes a Tabbed Page Control to divide the data entry into groups of related data. That is, all
Circuit/Bundle data will be entered on one tab (unlike the 3 dialogs in TLWorkstation 3.0).
Other objects that appear in the Right-Of-Way and/or interact with the Circuit configuration
are entered on another tab, etc.

All changes to the data will be stored in the application. The information will not be saved to
the database unless the user selects to do so. The user will be asked if any unsaved changes
are to be saved whenever the user closes a child form or the application.

Windows Forms provides better support than previous development platforms for reporting
errors. Generally, on data entry, the application will perform validation each time the user
leaves a field (or row in the case of Data Grids) and display an icon next to the erroneous
field. The user will be able to see the text of the error by clicking on the error icon. This
means that the user won’t have to keep clicking on OK buttons to close error dialog boxes. It
provides all the information needed by a novice to resolve the error, but, at the same time,

B-14
Software Requirements TL Workstation Design Tools Rev. 0

does not overly slow data entry for simple or obvious keying errors. (The experienced user
would be expected to figure out what is wrong with a given data field by just looking at it.)

Some validation will be done at the keystroke level where the application can detect a
keystroke error immediately. (E.g. numeric characters only in a numeric only field.)

Sample Forms

Data Source Connection Dialog

A database is installed with the application for desktop use. But, in general, the
application is designed to allow access to different sources of data. Some of those data
sources may require the user to log in with a userid and password. So, when the
application starts, and the currently configured data source (from the Registry) requires
a userid and password, the user is requested to either enter the userid and password, or
change to connect to a different data source.

B-15
Software Requirements TL Workstation Design Tools Rev. 0

Application Main (MDI Parent) Form

Open Project Dialog

B-16
Software Requirements TL Workstation Design Tools Rev. 0

Child Form

This is an example Child form showing the Primary tab the user would use to enter the Circuit, Bundle and
Conductor configuration.

B-17
Software Requirements TL Workstation Design Tools Rev. 0

B-18
C
FUNCTIONAL SPECIFICATIONS

C-1
 Functional Specifications
For
TL Workstation Design Tools

Prepared By: Ian C. Baskerville Date: 9/8/2006

Reviewed By: Date:

Approved By: Date:

C-3
Software Requirements TL Workstation Design Tools Rev. 0

Record of Revision

Date: Revision: Section: Description:

09/08/2006 00 All Original Release

C-4
Functional Specifications TL Workstation Design Tools Rev. 0

Table of Contents

RECORD OF REVISION.......................................................................................................... C-4

TABLE OF CONTENTS ........................................................................................................... C-5

INTRODUCTION ..................................................................................................................... C-9

Purpose.................................................................................................................................. C-9
Objectives .............................................................................................................................. C-9

ARCHITECTURE................................................................................................................... C-10
Overview ............................................................................................................................. C-10
User Interface....................................................................................................................... C-10
Data Source.......................................................................................................................... C-12

HIGH-LEVEL DESIGN .......................................................................................................... C-13

Entity Relationship Diagram .................................................................................................. C-13
Data Source Interface ............................................................................................................ C-14
Support Modules .................................................................................................................. C-14
Jama Module ................................................................................................................... C-15
AppletCommon Module ................................................................................................... C-15
Electric Circuit Components Module ................................................................................. C-15
OpenGL 3-D Model Display Modules................................................................................ C-15
Graphing Module ............................................................................................................. C-16
Individual Applets ................................................................................................................ C-16
AN-1 .............................................................................................................................. C-16
AN-2 .............................................................................................................................. C-16
AN-3 .............................................................................................................................. C-17
AN-4 .............................................................................................................................. C-17
AN-6 .............................................................................................................................. C-18
CC-1............................................................................................................................... C-18
CC-3............................................................................................................................... C-18
CC-4............................................................................................................................... C-19
CC-5............................................................................................................................... C-19
CL-1 ............................................................................................................................... C-19

C-5
Software Requirements TL Workstation Design Tools Rev. 0

CL-3 ............................................................................................................................... C-20

EMF-2 ............................................................................................................................ C-21
EMF-4 ............................................................................................................................ C-21
EMF-5 ............................................................................................................................ C-22
EMF-6 ............................................................................................................................ C-22
EMF-7 ............................................................................................................................ C-22
EMF-8 ............................................................................................................................ C-23
EMF-9 ............................................................................................................................ C-23
EMF-10 .......................................................................................................................... C-24
EMF-11 .......................................................................................................................... C-24
EMF-12 .......................................................................................................................... C-24
RN-1............................................................................................................................... C-24
RN-2............................................................................................................................... C-25
RN-4............................................................................................................................... C-25
S-1.................................................................................................................................. C-26
File Menu ............................................................................................................................ C-26
Segments Menu .................................................................................................................... C-26
Analysis Menu ..................................................................................................................... C-27
Reports Menu....................................................................................................................... C-28
View Menu .......................................................................................................................... C-28
Windows Menu .................................................................................................................... C-28
Help Menu ........................................................................................................................... C-28

LOW-LEVEL DESIGN ........................................................................................................... C-30

Data Diagrams...................................................................................................................... C-30
Project Header ................................................................................................................. C-30
Circuit Configuration........................................................................................................ C-31
Miscellaneous Right-Of-Way Objects ................................................................................ C-32
Support Modules .................................................................................................................. C-32
Jama Module ................................................................................................................... C-32
AppletCommon Module ................................................................................................... C-33
Electric Circuit Components Module ................................................................................. C-34
OpenGL 3-D Model Display Modules................................................................................ C-36
Graphing Module ............................................................................................................. C-36
Individual Applets’ Code....................................................................................................... C-37

C-6
Functional Specifications TL Workstation Design Tools Rev. 0

AN-1 .............................................................................................................................. C-37

AN-2 .............................................................................................................................. C-37
AN-3 .............................................................................................................................. C-37
AN-4 .............................................................................................................................. C-38
AN-6 .............................................................................................................................. C-38
CC-1............................................................................................................................... C-38
CC-4............................................................................................................................... C-38
CC-5............................................................................................................................... C-39
CL-1 ............................................................................................................................... C-39
CL-3 ............................................................................................................................... C-39
EMF-2/EMF-5................................................................................................................. C-40
EMF-4 ............................................................................................................................ C-40
EMF-6 ............................................................................................................................ C-40
EMF-7 ............................................................................................................................ C-40
EMF-8 ............................................................................................................................ C-40
EMF-9 ............................................................................................................................ C-40
EMF-10 .......................................................................................................................... C-40
EMF-11 .......................................................................................................................... C-41
EMF-12 .......................................................................................................................... C-41
RN-1............................................................................................................................... C-41
RN-2............................................................................................................................... C-41
RN-4............................................................................................................................... C-41
S-1.................................................................................................................................. C-41
Starting Application .............................................................................................................. C-41
Disclaimer Form .............................................................................................................. C-41
Data Source Connection Dialog......................................................................................... C-42
Application Main (MDI Parent) Form ................................................................................ C-43
Menu Functions.................................................................................................................... C-43
File Menu........................................................................................................................ C-43
Segments Menu ............................................................................................................... C-45
Analysis Menu................................................................................................................. C-47
Reports Menu .................................................................................................................. C-47
View Menu ..................................................................................................................... C-48
Help Menu ...................................................................................................................... C-49

C-7
Software Requirements TL Workstation Design Tools Rev. 0

Child Form........................................................................................................................... C-50

Circuit/Bundle/Conductor Configuration Tab ..................................................................... C-50
Miscellaneous Objects Tab ............................................................................................... C-51
Location/Profile Specifications Tab ................................................................................... C-52

C-8
Functional Specifications TL Workstation Design Tools Rev. 0

Introduction

Purpose

Integrate the Applets, from the third edition of the Transmission Line Reference Book – 200
kV and Above (the Red Book), into a desktop application. This application will replace the
ACDCLine and RNoise Applications that were part of the TLWorkstation version 3.0. It will
apply the updated algorithms used in the Applets, and update the User Interface to comply
with modern programming standards, using the latest software technology.

Objectives

The primary objective of this project is to create an application that will replace the
ACDCLine and RNoise modules in TLWorkstation as the first step in maintaining the
viability of EPRI’s TLWorkstation software.

Additional objectives are:

• Include updated algorithms, specifically 3-D calculations;

• Improved Import, Export and Save As functionality;
• Improved Data Input Forms, with graphical feedback;
• Improved maintainability by using up-to-date development platforms;
• Provide architecture that can be linked to other software packages.

C-9
Software Requirements TL Workstation Design Tools Rev. 0

Architecture

Overview

This program will replace the ACDCLine and RNoise modules in TLWorkstation by
implementing the following Red Book Applets:

Applet Description
AN-1 Audible Noise of Transmission Lines
AN-2 Audible Noise of Transmission Line (3-D)
AN-3 Bundle Geometry for Minimum Audible Noise
AN-4 Audible Noise, Hum
AN-6 Audible Noise vs. Rain Rate
CC-1 Conductor Surface Gradient (2-D)
CC-2 Conductor Surface Gradient (3-D)
CC-3 Surface Gradient on Toroidal Corona Shields
CC-4 Conductor Tables
CC-5 Transmission Line Parameters (Single Circuit)
CL-1 Transmission Line Corona Loss
CL-3 Ozone Concentration near Transmission Lines
EMF-2 Electric Field of Transmission Lines in 2-D
EMF-4 Electric Field of Transmission Lines in 3-D
EMF-5 Electric Field Shielding by Grids of Wires - 2D
EMF-6 Magnetic Field from Sets of Current Carrying Conductors (2-D)
EMF-7 Magnetic Field (3-D)
EMF-8 Magnetic Induction in Wires Parallel to Transmission Lines
EMF-9 Distant Magnetic Field Equations for Transmission Lines
EMF-10 Electric Field Induction on Objects
EMF-11 Magnetic Field Reduction Using Cancellation Loops (3-D)
EMF-12 Magnetic Field Reduction Using 4th-Wire Scheme
RN-1 Electromagnetic Interference up to 30 MHz
RN-2 EMI Calculation Using Empirical Methods
RN-4 Traditional Radio Noise Calculation Method
S-1 Switching Surge Flashover Model

User Interface

This application will be an MDI Application based on a Project/Detail data format.

One Project is open at a time.

Each Detail corresponds to one Right-Of-Way or Circuit configuration. And, each open configuration is
managed with one MDI Child window.

C-10
Functional Specifications TL Workstation Design Tools Rev. 0

Multiple child windows can be opened at a time, so that the user can directly contrast and compare multiple line
configurations.

All analysis and reporting functions are accessed from the Menu of the MDI Parent window.
Analysis and Reporting functions should operate on the active Child form, all Child forms or the open project as
a whole.

The Application Main Form (MDI Parent):

Since only one project is open at a time, the File menu options are used to access and manage projects.

The Segments menu (may be renamed) allow access to and management of individual Details. As such, the
options on that menu allow for the user to open and close Child forms.

The Analysis menu provides options allowing users to run selected analyses on the configuration specified in
the active Child form, all Child forms or all Segments in the open Project.

The Reports menu provides options allowing the user to specify how the output is to be displayed, or displays
the results of previously run analyses.

C-11
Software Requirements TL Workstation Design Tools Rev. 0

The View menu allows the user to configure how the data is displayed.

The Windows menu provides the options standard to the Windows menus in Windows applications.

The Help menu provides the options standard to the Help menus in Windows applications.

Data Source

The default database, supplied with the installation, is an Access database. It provides all information required
to execute all aspects of the application.

The required information can be broken down into two types:

• Right-Of-Way or Circuit Configuration, which consist of:
o Circuit/Bundle/Conductor Configuration,
o Right-Of-Way Objects
o Local Geography and Climate
• Reference data.
o Conductor Wire Types Parameters
o General calculation Parameters

The Right-Of-Way or Circuit Configuration information could be imported from some other source, such as
PLS-CADD.

C-12
Functional Specifications TL Workstation Design Tools Rev. 0

High-Level Design

Entity Relationship Diagram

A generalized Circuit entity relationship could be defined as follows:

Circuit Entity Diagram

TransmissionLine
ROW
-LineID

1 -LineID 0..1 -CiruitID

1 -ROW
Circuit
0..*
1

1..* -SegmentID
-CircuitID * -Segment
Segment 1
ROWSegment
-End1
-SegmentID

* 1
-RowSegmentID-End3 -End2
* -RowSegmentID
1
LineCircuitSegment ShieldingObjects
*

1 -LCSID

-End4
*
* * -StructureID
* -SpanID -SpanID
1 1 CoupledObjects
Span TLStructure
1 1
-SpanID -BOLStructure

-SpanID -AOLStructure
1 -SpanID 1 -StructureID

* -BundleID 1..* -InsulatorNo

Bundle -BundleNo -InsulatorNo Insulator

1 1..*

1 -BundleID

1..* -ConductorNo

Conductor

C-13
Software Requirements TL Workstation Design Tools Rev. 0

In this application, at this time, the Circuit entities represented consist only of: Span,
Circuit, Bundle, Conductor and Structure. The Span is referred to in the following as
‘Segment’. This may change, pending user review. All objects are treated as one group.

Data Source Interface

Project level interface Objects encapsulate the routines to load and save projects from and to the data source…

Segment Level interface Objects encapsulate the routines to load and save individual Segments (Cases) from and to
the data source…

IDisposable

Abstract Class

RedbookCaseDa… TLW30CaseData…
Class Class
BaseCaseDataModule BaseCaseDataModule

Note: there is no encapsulation of the PLS-CADD Segments because PLS-CADD information will only be imported
to the primary data source.

Support Modules

C-14
Functional Specifications TL Workstation Design Tools Rev. 0

Jama Module

This module contains the Jama calculation routines for matricies as used by the original Applets.
It has been enhanced to provide additional math objects and functions. These routines are used in this application to
simplify the appearance of the calculations, making them easier to validate for correctness. Additional structures and
classes have been added to support geometric calculations and 3-D results displays.

AppletCommon Module

This module contains all miscellaneous classes from the original Applets, plus new classes used by all integrated
Applets.

Most data entry fields in the application involve numeric data that have specific unit dimensions. These data fields
allow the user to enter unit text when entering these numbers in order to override the default units used in the
interface. For example, a given field may require a number with the units of Length and the display is in feet. In this
application, in such a field, if the user enters just a number, then it is assumed to be in the display units of feet.
However, this application allows the user to enter ‘6 in’; the application will automatically convert it to ‘0.5’ (ft).

Additional miscellaneous Enumerated Types, Exception Types have been added to this module to simplify the code
of all converted Applets.

Electric Circuit Components Module

The original Applets defined Circuit, Bundle and Conductor (named Cylinder) classes to encapsulate the data
pertaining to those individual real-world objects. With this integration, that data is properly encapsulated as
Properties. Also, the field names in these classes have been modified to be more descriptive, and to contain the units.
For example, the diameter of the conductor was named ‘dblD’. In this application, the field, as a property, has been
renamed to ‘DiameterInCm’, i.e. diameter in centimeters. This should greatly facilitate code validation during
testing. In addition, the conductor wire name and type are further refactored to encapsulate those parameters and
further simplify the code, eliminating duplication.

Various Applets used either 2-D or 3-D Electric field calculations. The class and naming of the corresponding
routines varied. All the calculation modules have been reconciled and refactored into two basic classes that will be
used by all Applets in the new application.

OpenGL 3-D Model Display Modules

Separate modules have been included, which interface .NET Managed Code to Windows native OpenGL dlls. These
include:
1. csgl.native, which is creates the dll that encapsulate the interface to the OpenGL.org Windows dlls:
opengl.dll. Glu.dll and glut.dll.
2. CsGL, which provide wrappers for all the basic OpenGL types; and,
3. CsGLBasecode, which provides high-level wrappers encapsulating a Windows Control, ‘View’, that
provides the display canvas control that appear on a Form; and one that encapsulates the displayed 3-D
objects ’Model’.

This application encapsulates extended functionality by extending the above wrappers in CsGLBasecode with
‘RedbookGLControl’ and ‘RedbookModel’ respectively. These controls are provided by the ‘RedbookGL’ module.

C-15
Software Requirements TL Workstation Design Tools Rev. 0

In addition, the routines for rendering Conductors and Miscellaneous Objects are encapsulated in another set of
classes. These are also included the ‘RedbookGL’ module.

Graphing Module

Displaying Graphs is accomplished with another tool called Zedgraph.

However, the components in Zedgraph are encapsulated in wrappers in the AppletCommon. This is done to
simplify the development of the graphs and to ensure consistency.

Individual Applets

AN-1

This applet calculates the audible noise caused by corona on high voltage transmission lines at different distances
from the line. The audible noise is calculated as the L50 value in rain, i.e. the value exceeded for 50% of the periods
during which there is measurable rain. The results are given for both the EPRI and the BPA calculation methods
described in the Reference Book. For most lines the two methods give similar results. The difference between the
two sets of values can be used to indicate variations that can be expected between different climates, or different
conductor surface conditions (aging). In addition to L50 rain, the L5 rain and the range of possible fair weather
values also are given. These are values obtained using the EPRI method. According to the BPA method the L5 rain
is obtained by adding 3.5 dB to the L50 rain and the L50 fair weather value is obtained by subtracting 25 dB from
the L50 rain value. The fair weather values calculated in this applet are the lower and the upper expected values of
the fair weather noise, which is very dependent on season, climate, and particles that may be present in the air.

The applet also calculates the generated acoustic power of individual bundles. This gives the user information on
which bundle is most responsible for the noise.

The applet calculates the noise for any type of bundles, including irregular bundles, i.e. bundles for which the
conductors are not placed on the vertices of a regular polygon.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

AN-2

This applet calculates the audible noise caused by corona on high voltage transmission lines at different distances
from the line. The problem is solved in 3-D. Conductive objects are simulated by sets of cylindrical segments above
a conductive flat ground plane.

This applet is ideal for conductors that have sags (such as transmission line conductors), are not parallel to each
other (transposition spans), or are at an angle with respect to each other (substation buses). This applet is also ideal
to find out the effect of the presence of lattice towers, steel poles, guy wires and other objects at ground potential
that may be well represented by sets of cylindrical segments (see Appendix 7.6 of the Reference Book)).

The audible noise is calculated as the L50 and L5 values in rain (i.e. the values exceeded for 50% and 5% of the
periods during which there is measurable rain) and the upper limit of expected fair weather values,. The noise is

C-16
Functional Specifications TL Workstation Design Tools Rev. 0

calculated using the EPRI calculation method. The applet divides the conductors into a large number of short
segments, calculates the surface gradient on each segment using a 3-D electric field program (Applet CC-2),
calculates the generated acoustic power for each segment, and finally the noise produced by all segments together at
each measuring point.

The applet calculates the noise for regular bundles, i.e. bundles for which the conductors are placed on the vertices
of a regular polygon.

The audible noise is calculated along a line specified by the user.

AN-3

This applet calculates the optimum bundle geometry corresponding to the minimum audible noise. Only three-phase
transmission lines are considered. The bundles of the three phases are all equal. For a given number of sub-
conductors, sub-conductor diameter, and bundle diameter, there is an optimum arrangement of the individual sub-
conductors on the bundle circumference that produces the lowest audible noise for well-aged conductors in rain. The
value calculated is the L50 value in rain, i.e. the value exceeded for 50% of the periods during which there is a
measurable rain. The calculations are based on the EPRI method to calculate the L50 Rain value and on the method
for bundle geometry optimization described in Section 10.7.2 of the Red Book. The experimental data needed to
execute the calculations are those described in (Comber and Zaffanella 1973). The curves in that paper were
digitized for use by this applet. The optimum bundle geometry is given for different bundle diameters. There is a
bundle diameter and an optimum sub-conductor arrangement for which the audible noise reaches an absolute
minimum. The applet calculates the audible noise value (at 15 meters from the outer phase and 1.5-m height) for
regular and optimum bundles and calculates the sub-conductor location for the optimum bundles.

AN-4

This applet calculates the audible hum at twice the power frequency caused by corona on high voltage transmission
lines at different distances from the line. The hum is a mixture of pure tones, the most significant of which occurs at
twice the power frequency. The algorithms for the calculations are described in Chapter 10 of the Reference Book.
The hum is calculated as the L50 and the L5 values in rain, i.e. the values exceeded for 50% and 5%, respectively, of
the periods during which there is measurable rain. The rain intensity selected for the L50 value is 0.75 mm/h and the
rain intensity selected for the L5 value is 6.5 mm/h. The hum in fair weather is negligible and is not calculated. The
hum is calculated for an altitude of 100 m or less above sea level. There is no experimental or other research data to
support estimates of the effect of altitude.

The applet calculates also the generated acoustic hum power of individual bundles. This gives the user information
on which bundle is most responsible for the hum.

The applet calculates the hum only for single conductors and regular bundles, i.e. bundles for which the conductors
are placed on the vertices of a regular polygon. There is no experimental or other research data to support estimates
of the effect of bundle irregularities.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

The hum is calculated at different lateral distances from the center of the line (lateral profile) at a constant height
above ground that can be set by the user (default value is 1.5 m).

C-17
Software Requirements TL Workstation Design Tools Rev. 0

AN-6

This applet calculates the audible noise caused by corona on high voltage transmission lines at a specified distance
from the line and the noise caused by the rain itself for different rain rates. The calculation of audible noise due to
corona versus rain rate is based on the algorithms in Section 10.4.6 of the Reference Book. The calculation of the
noise of rain is based on the algorithms in Appendix 10.2.

The applet is useful to determine at which distance from the line and at which rain intensity the noise of rain may
mask the noise of the line.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

The audible noise is calculated at a height of 1.5 m above ground. The altitude must be between 0 and 300 m.

CC-1

This applet calculates the electric field at the surface of conductors (conductor surface gradient) of high voltage
transmission lines. The problem is solved in two dimensions, i.e. the conductors are considered straight, infinitely
long, and parallel to each other and to the flat surface of a conductive earth. If the conductors are catenaries, the
height of the conductors above ground should be specified as the average height above ground. It is recommended to
use the minimum height plus one third of the sag. The user may input data regarding single conductors, or bundles,
or three-phase circuits, or any combination of these elements. When three-phase transmission circuits are
considered, their voltages are assumed symmetric—i.e. the three phase-to-ground voltages are equal in magnitude
and their phase angles differ by 120º. The applet can be applied to any number of circuits in a transmission-line
corridor.

For each conductor the average surface gradient and the maximum surface gradients are calculated. In the case of a
bundle of conductors, the maximum surface gradient is defined as the average of the maximum surface gradients of
the individual conductors.
The applet calculates also the surface gradient at any point on the surface of a specified conductor.

The applet calculates the surface gradient for any type of bundles, including irregular bundles, i.e. bundles for which
the conductors are not placed on the vertices of a regular polygon.

The electric field is calculated only on the surface of the conductors. Calculations do not apply to the electric field
away from the conductor surface. To calculate the electric field or the space potential away from the conductor
surfaces, use Applet EMF-2.

The 2-D Surface Gradient calculation from this Applet will be reconciled with the Surface Gradient calculations in
the other Applets, and refactored into a common module.

CC-3

This applet calculates the highest electric field on the surface (maximum surface gradient) of toroids. Toroids are
often used to terminate the high voltage conductors toward a dead end structure or near the line end of insulator
strings to reduce the voltage gradient along the insulators. If the dimensions or the position of the toroid are not
appropriate, the electric field may reach unacceptably high values and create a strong corona source. The problem of
calculating the surface gradient is solved in 3-D. All conductive objects present (conductors, bundles, tower
elements, objects at ground potential) are simulated by sets of cylindrical segments above a conductive flat ground
plane. Each toroid is also simulated with a set of cylinders. The number of cylinders in which a toroid is divided is

C-18
Functional Specifications TL Workstation Design Tools Rev. 0

108, which provides a very good simulation. The other conductive objects that can be simulated include single or
bundled conductors either straight segments or catenaries and flat plates. The user can build other objects and store
them for future use.

The maximum surface gradient is calculated only on toroids. A maximum of two toroids is allowed. There is no
limitation on other objects. However, if the number of cylindrical segments simulating the conductive objects
(excluding the toroids) exceeds 100, the computation time may be very long.

CC-4

This applet may be used for the following purposes;

1. Given the name of a conductor, list its properties and show the drawing of its cross-section.
2. Select a conductor with a desired property and look up its other parameters. For instance, the user may
want a list of conductors ordered by outside diameter, or by resistance, or by strength and choose a
conductor from that list. After selecting the conductor the user may see the list of its parameters.
3. The user may calculate quantities that are not normally found in a conductor table, such as the resistance at
different temperatures and/or different frequencies.
All units are both in metric and British units. The applet incorporates tables of common North American Aluminum
Conductors Steel Reinforced (ACSR), common British ACSR, ACSR/TW (the aluminum strands are trapezoidal),
ACSR-IEC, Single-Layer High-Strength Aluminum Conductors Steel Reinforced (ACSR-EHS), Aluminum
Conductors Steel Supported (ACSS), All-Aluminum Conductors (ACC), All-Aluminum-Alloy Conductors
(AAAC), Aluminum Conductors Alloy Reinforced (ACAR), Aluminum-Clad Steel Conductors (ALUMOWELD),
High-Strength Utility-Grade Steel Conductors (HS), and Extra-High-Strength Utility-Grade Steel Conductors (EHS)
(see Chapter 2).

CC-5

This applet calculates:

• the series impedance matrix, either full or after ground wire reduction,
• the shunt admittance matrix,
• the sequence impedance matrix,
• The surge impedance and the surge impedance loading,
• The series voltage drop, and
• The capacitive currents.

This applet provides also a tool to pass from phase to sequence quantities and vice versa.
The algorithms presented in the Reference Book are used and expanded in this applet.

The calculations are performed for a single 3-phase circuit with 0, 1, or 3 ground wires. The frequency can have any
value from power frequency to 100 kHz. The user can input the resistance and the GMR of a conductor directly or
input known characteristics of the conductor and let the applet calculate resistance and GMR.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors
form catenaries, the height of the conductors above ground should be taken as the minimum height plus one third of
the sag.

CL-1

C-19
Software Requirements TL Workstation Design Tools Rev. 0

This applet calculates, for a given transmission line, corona losses under fair weather and under heavy rain. The loss
is calculated for each phase and for the entire line. The values are in W/m. The applet also calculates the mean
annual and maximum corona loss of the line. Accuracy of empirical formulas for corona effects is generally
evaluated by comparing them with good measured data obtained on operating high voltage transmission lines.
Unlike electromagnetic interference and audible noise, however, sufficient measured data are not available for
corona losses from operating lines and, therefore, it is not possible to make a realistic evaluation of the accuracy of
corona loss empirical formulas. Different results are obtained using calculation methods developed by different
researchers. The difference may be caused by different surface conditions of the conductors tested (particularly the
degree of aging), different climates, different rain rates, measurement errors, and approximation in deriving
empirical equations. Calculation results are given for different methods. By comparing the different results the user
may gather an appreciation for the variability of the phenomenon and the reliability of the data. The methods are
described in Chapter 11 of the Third Edition of EPRI’s Red Book, i.e.:
1. Fair weather loss according to Peterson’s equation, which is applicable only for single conductors.
2. Fair weather loss according to Gary and Moreau (EdF). This method is applicable to any regular
bundle and gives a range of possible fair weather losses.
3. Fair weather loss according to a BPA formula.
4. Heavy rain loss according to a BPA formula.
5. Heavy rain loss according to a method developed by Trinh and Maruvada (IREQ).
6. Heavy rain loss according to Clade’ and Gary (EdF).
7. Heavy rain loss according to Comber and Zaffanella (EPRI Red Book, second edition)
8. Heavy rain loss according to Project EHV (GE). This method is applicable for bundles with voltage to
ground between 220kV and 470 kV.

Each of this method is described in the Red Book. Essentially, all methods start with the calculation of the electric
field at the surface of the conductors of each phase. The problem is solved in 2-D, i.e. the conductors are considered
straight, infinitely long, and parallel to each other and to the flat surface of a conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.
For each bundle (or single conductor if there is only one conductor per phase) the average surface gradient and the
maximum surface gradients are calculated. In the case of a bundle of conductors, the maximum surface gradient is
defined as the average of the maximum surface gradients of the individual conductors. Each method uses
empirically derived equations giving the corona loss as a function of some of the following variables: sub-conductor
diameter, number of sub-conductors, bundle diameter, rain rate, frequency, and altitude. When a method did not
formalize the dependence of corona loss on some of these variables, the best available algorithm derived from other
methods was used. For example, for all methods the dependence of corona loss, P (W/m), on frequency, f (Hz), and
altitude above sea level, A (m), was determined using equation:
f
P = P0 ⋅ ⋅ 10( A / 300 ) / 10
f0 ,
where P0 is the loss at the frequency f0 and at the altitude A=0.

CL-3

This applet calculates the incremental concentration of ozone caused by corona on high voltage transmission lines at
different distances from the line. The amount of ozone is expressed in ppb (parts per billion in terms of weight
relative to air; 1 ppb = 1.23 μg/m3). The algorithms for the calculations are described in Chapter 11 of the Reference
Book. Ozone concentration is calculated for fair weather and for rain. In both cases the most conservative estimates
are made. In the case of fair weather, the worst fair weather conditions conducive to corona are assumed. In the case
of rain an intensity of 10 mm/h (heavy rain) is assumed.

The generation of ozone is expressed in μg/(m·s). The generation is based on corona loss. For corona loss
calculations in fair weather the upper bound values obtained using the EdF method are used. For corona loss
calculation in heavy rain the EPRI method, which is generally the most conservative, is used. Corona loss is
calculated accounting for frequency and for altitude above sea level. Other than their effect on corona loss, these two
variables are assumed not to affect ozone concentration.

C-20
Functional Specifications TL Workstation Design Tools Rev. 0

If the user prefers to calculate the corona loss using other methods, calculations should be made separately (for
instance using Applet CL-1) and the user should choose the option of entering the corona loss values for each bundle
directly.

The following assumptions are made:

1. Ozone generation rate in fair weather: 0.5 g/kWh (grams of ozone per kWh of corona loss)
2. Ozone generation rate in rain: 4.5 g/kWh
3. Time to half value in fair weather: 1 hour
4. Time to half value in rain: 5 minutes.
5. Spreading coefficients for both stable and unstable winds are those given in Chapter 11 of the Reference
Book.

The applet calculates the lateral profile of ozone concentration and also the ozone generated by individual phases.
The user must specify the interval of distances from the line, the number of segments in which this interval is
divided, and the height above ground at which ozone concentration is measured. The user must also specify wind
speed and direction (parallel or perpendicular to the line), and wind type (stable or unstable).

In the case of wind parallel to the line, the contributions from 500 2-m sections of line are added (total line length is
1000 m).

The applet calculates corona loss (and from it ozone concentration) for single conductors or regular bundles, i.e.
bundles for which the conductors are placed on the vertices of a regular polygon. There is no experimental or other
research data to support estimates of the effect of bundle irregularities.

The conductors are treated as if they were infinitely long and parallel to a flat earth. If the conductors are catenaries,
the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

EMF-2

This applet calculates the electric field and the space potential at power frequency at any point at the ground or in
space caused by high-voltage transmission lines or by any set of conductors to which a known voltage may be
applied. The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the
conductors form catenaries, the sag is neglected, and the height of the conductors above ground should be that at the
location where the field is calculated. When three-phase transmission circuits are considered, their voltages are
assumed symmetric—i.e., the three phase-to-ground voltages are equal in magnitude and their phase angles differ by
120º. The applet can be applied to any number of circuits in a transmission-line corridor.

The electric field and the space potential are calculated along a specified line. The space potential may also be
calculated on a vertical plane orthogonal to the conductors, and the space potential contour lines may be provided.
Calculations, however, do not apply to the field on the conductor surface (surface gradient) or in the immediate
vicinity of conductors.

EMF-5 is really the same as EMF-2, with the addition of miscellaneous objects in the field.

EMF-4

This applet calculates the electric field and the potential in space caused by high-voltage transmission lines or any
set of conductors to which a voltage may be applied. Conductive objects are simulated by sets of cylindrical
segments above a conductive flat ground plane.
This applet is ideal for conductors that have sags (such as transmission-line conductors), are not parallel to each
other (transposition spans), or are at an angle with respect to each other (substation buses). This applet is also ideal
to find out the effect of the presence of lattice towers, steel poles, guy wires and other objects at ground potential

C-21
Software Requirements TL Workstation Design Tools Rev. 0

that may be well represented by sets of cylindrical segments. The algorithms on which this applet is based are
described in Appendix 7.6 of Chapter 7 of the Reference Book.
The electric field and space potential can be calculated along a specified line and displayed in both tabular and
graphical formats. The electric field and space potential may also be calculated individually on a designated plane
orthogonal to the conductors (X-Y, X-Z, or Y-Z planes), and contour line maps can be constructed.

EMF-5

This applet calculates the electric field and space potential caused by high-voltage transmission lines (or any set of
conductors to which a voltage may be applied) in the presence of a grid of grounded wires that act as a shield. Both
energized and grounded conductors are treated as if they were infinitely long and parallel to a flat conductive earth.
If the conductors form catenaries, the height of the conductors above ground should be specified at the location
where the field is calculated. Conductor sag is not considered in this calculation. Grounded conductor shielding
grids are defined by location and density, and can be either horizontal or vertical grids.

The electric field and space potential can be calculated along a specified line, creating a lateral profile plot. Space
potential can also be calculated within a rectangular calculation grid in a vertical plane orthogonal to the conductors,
with space potential contour lines provided.

EMF-6

This applet calculates the magnetic field at power frequency at any point caused by high-voltage transmission lines
or by any set of conductors in which known currents flow. The conductors are treated as if they were infinitely long
and parallel to a flat nonmagnetic, nonconductive earth. For the calculation of magnetic field, the current is assumed
to be concentrated at the center of each conductor (or conductor bundle). The image currents in the earth are
neglected, which is a good approximation for calculation of power frequency magnetic field in proximity to power
lines. If the conductors form catenaries, the sag is neglected, and the height of the conductors above ground should
be that at the location where the field is calculated. When conductor bundles are considered, they are treated as
single conductors with the current concentrated at the center of the bundle. When three-phase transmission circuits
are considered, the data for each phase must be entered one at a time. If the transmission line has shield wires for
lightning protection, their current must be calculated before exercising this applet. Shield wire currents or currents in
any other grounded wires may be calculated using Applet EMF-8.

The magnetic field is calculated at points along a specified line or at points of a grid in a vertical plane orthogonal to
the conductors, in which case magnetic field contour lines are provided. Calculations, however, do not apply to the
field on the conductor surface. If the field in the immediate vicinity of a bundle is desired, the data for each sub-
conductor must be entered separately. If the bundle is asymmetric, the current subdivision among the sub-conductors
may be calculated using Applet CC-1.

EMF-7

This applet calculates the magnetic field at power frequency at any desired point in space produced by conductors
that can be simulated by sets of segments of known starting and ending points and that carry known currents. In
addition to conductor segments, the user can enter catenaries just by defining attachment points, sag, and number of
segments. This applet is ideal for conductors that have sags (transmission-line conductors), are not parallel to each
other (transformation spans), and are at an angle with each other (substation buses). This applet is also ideal for any
three-dimensional arrangement of conductors. The earth is assumed nonconductive and, therefore, the image
currents in the earth are neglected, which is a good approximation for calculation of power frequency magnetic field
in proximity to power lines. No conductive (other than the specified conductor segments, catenaries, buses, or coils)
or magnetic objects that may modify the magnetic field are assumed to be present.

C-22
Functional Specifications TL Workstation Design Tools Rev. 0

The magnetic field and space potential can be calculated along a specified line and displayed in both tabular and
graphical formats. The magnetic field may also be calculated on a designated plane orthogonal to the conductors (X-
Y, X-Z, or Y-Z planes), and contour line maps can be constructed.

EMF-8

This applet calculates:

• Currents induced in the shield wires when the shield wires are grounded at every tower. The
calculations assume that the line is infinitely long in both directions from the point of calculations and that
the ground resistance is the same for all towers. In these conditions the current flowing from shield wires to
ground at each tower is zero.
• Voltages induced between the end of a shield wire section and a tower when the shield wires are
sectionalized to avoid current flow. The wires are grounded at one tower and insulated from all the other
towers to which the shield wire section is attached. A voltage will exist at the end of the shield wire section
between each shield wire and the tower.
• Currents induced in shield wires that are grounded at every other tower and isolated and transposed at
intermediate towers. A voltage will exist between ground wires ant tower at the transposition tower. The
calculations assume that the line is infinitely long in both directions from the point of calculations and that
the ground resistance is the same for all towers. In these conditions the current flowing from shield wires to
ground at each tower is zero.
• Voltage induced between ground and the end of a wire strung in the general direction of the
transmission line and grounded at the other end.

The user must choose which of the above calculations are desired. Calculations are made for the power frequency
(50 Hz or 60 Hz). Calculations can be made for any type of line (one or more circuits) in the transmission corridor.
Calculations assume all the conductors parallel to each other and to a conductive earth. The earth resistivity must be
specified.

EMF-9

This applet calculates the magnitude of the basic elements to which a set of current carrying conductors can be
reduced for the purpose of assessing the magnetic field produced. Appendix 2 of Chapter 7 of the Reference Book
discusses definitions, properties, and methods of calculations of the basic elements: monopole, dipole, and
quadrupole. The field produced by each of the basic elements has a different law of decays. For instance a monopole
produces a magnetic field inversely proportional to the distance, equal to BM = 2M/R, where BM is the magnetic field
(mG), M is the magnitude of the monopole (A), and R is the distance from the center of the set of wires to the
measuring point (m). A dipole produces a field that decays much faster, being inversely proportional to the square of
the distance. The dipole field is BD = 2D/R2, where D is the magnitude of the dipole (A·m). A quadrupole field
decays even faster, the field being equal to BQ = 4Q/R3, where Q is the magnitude of the quadrupole (A·m2). These
calculations are useful to determine which basic element has the largest effect at a given distance from the line, so
that an appropriate field reduction method may be applied. Calculations can be made for any set of parallel current-
carrying conductors with a known current (magnitude and phase angle) and location in space.

The total magnetic field produced by the set of line currents is equal to the vectorial sum of the field produced by the
basic elements (monopole, dipole, and quadrupole). However, the total field is not calculated by the applet, since it
depends not only on the distance but also on the direction of the line connecting the point of measurements with the
center of the set of line currents. This direction does not affect the magnitudes of the basic elements but affects their
relative phase angle and direction in space. The best estimate of the total field is the square root of the sum of the
squares of the magnitudes of the fields produced by the basic elements.

C-23
Software Requirements TL Workstation Design Tools Rev. 0

EMF-10

This applet calculates the short–circuit current and the capacitance to ground of conductive objects placed in a
transmission line environment. These issues are discussed in Section 7.8 of the Reference Book. The short-circuit
current is the current that would flow in a zero-resistance connection between object and ground. The capacitance of
the object to ground is calculated as if the object were perfectly insulated from ground.

The objects may be located in an electric field created by high voltage conductors. In this case the geometry and
voltage of these conductors must be specified. The objects may also be placed in an unperturbed (before the
introduction of the objects) uniform electric field w/o the need to specify the geometry and voltage of the source of
the field. If the electric field is created by energized objects, the short circuit currents and the capacitances to ground
will be calculated for all the objects at ground potential (V = 0). If the user specifies a uniform electric field,
calculations will be performed considering all the objects at ground potential (including those to which a voltage is
assigned).

The calculations are performed by using algorithms described in Appendix 7 of Chapter 7 of the Reference Book.
Objects are simulated by sets of cylindrical segments at the same potential and the 3-D electric field problem is
solved. The charges on each object are calculated and from them short-circuit currents are capacitances. This applet
is ideal for 3-D objects, for high voltage conductors that have sags (transmission line conductors), or have an
irregular geometry (line angles, crossing lines), and when there are other shielding objects present.
The most challenging task for the user is the simulation of complex 3-D objects using cylindrical segments. This
issue is discussed in Section 7.3 of the Reference Book. Building an object may be a laborious task.

EMF-11

This applet calculates the magnetic field at desired locations before and after the application of conductors arranged
to form loops where currents will be induced by field sources such as transmission lines. The induced currents may
have the effect of producing a magnetic field that tends to cancel the source field, hence the name “cancellation
loop”.

The source of the field may be one or more transmission lines, or any current carrying conductor, or substation
buses, or coils. The cancellation loops are formed by conductor segments that form the so-called “passive network”.

This applet accepts not only straight conductors, but also conductors that have sags (transmission line conductors),
are not parallel to each other (transposition spans), and are at an angle with each other (substation buses).

The magnetic field is calculated along a straight segment or on a plane grid, both with and without the passive
network

EMF-12

This applet calculates the magnetic field reduction that can be achieved by adding a fourth wire connected to one of
the phases of a thee-phase line. This method of field reduction is discussed in Section 7.17.7 of the Reference Book.
Examples of possible geometries for this scheme are shown in the figure of the applet window. The phases are
designated as A, B, and C. The fourth wire is connected in parallel to phase A. The applet applies to the field inside
a calculation area adjacent to the line. The problem is treated as a 2-D problem. The phase currents are assumed
balanced and symmetric.

RN-1

C-24
Functional Specifications TL Workstation Design Tools Rev. 0

This applet calculates the electromagnetic interference (EMI) produced by corona on high voltage transmission
lines. The wideband method of EMI calculation is used. This method does not incorporate the approximations used
by the traditional method of radio noise calculations: quasi-TEM modes of propagation, quasi-static methods of field
calculations. Therefore, the results are valid in the entire MF and HF frequency ranges from 300 kHz to 30 MHz.
The results consist in the median EMI during measurable rain (L50 rain). The EMI is calculated as an electric field
(dB above 1 μV/m) read either by a rod or a loop antenna. The location of the measuring point is not confined to
points close to the ground (as in the traditional radio noise calculation method, but can be also above the conductors.
The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. Any number of
circuits may be considered, and the voltages do not have to be symmetric. Each phase may have a different bundle,
whose geometry must be specified. The conductors are assumed to be ACSR. Ground wires are considered in the
calculation of the surface gradient of phase conductors, but are otherwise neglected in the EMI calculation. The
applet calculates the excitation function of each phase based on the bundle geometry, the maximum surface gradient,
and the altitude above sea level. The excitation function is then used to calculate the EMI accounting for line
geometry, measuring frequency, earth resistivity, and earth dielectric constant. The EMI lateral profile is calculated
along a specified line orthogonal to the line.

RN-2

This applet calculates the electromagnetic interference (EMI) caused by corona on high voltage transmission lines at
different distances from the line. The EMI is calculated in terms of electric field expressed in decibels above 1
μV/m. The algorithms for the calculations are described in Section 9.5.3 (for frequencies up to 30 MHz) and Section
9.6.3 (for frequencies above 30 MHz) of the Reference Book. EMI is calculated for fair weather and for rain. In both
cases average values are given.

The applet calculates the lateral profile of EMI and also the EMI generated by individual bundles in the reference
condition (1MHz, 15 m laterally, quasi-peak detector, 9 kHz bandwidth) so that the bundle that most contributes to
the EMI could be assessed. The user must specify the interval of distances from the line, the number of segments in
which this interval is divided, and the height above ground at which the antenna measuring EMI is located. The user
must also specify the altitude, the ground resistivity, the type of detector (quasi-peak, peak, rms, or average) and its
bandwidth. However, for QP only the single bandwidth of 9 kHz is allowed for frequencies from 150 kHz to 30
MHz. From 30 MHz to 1 GHz the QP bandwidth is 120 kHz. These fixed bandwidths are according to CISPR
specifications as shown in Table 9.4-1 of the Red Book. Any bandwidth can be specified for average, rms and peak
detector calculations.

The applet calculates EMI only for single conductors or regular bundles, i.e. bundles for which the conductors are
placed on the vertices of a regular polygon. The conductors are treated as if they were infinitely long and parallel to
a flat earth. If the conductors are catenaries, the height of the conductors above ground should be specified as the
average height above ground. It is recommended to use the minimum height plus one third of the sag.

RN-4

This applet calculates the radio noise produced by corona on high voltage transmission lines using the traditional
method that has evolved over a period of several decades with contributions and refinements by several researchers.
This method incorporates approximations (quasi-TEM modes of propagation, quasi-static methods of field
calculations) that limit its application to frequencies less than 1.6 MHz, to distances from the line not much greater
than a quarter of the wavelength, and to points near ground level. The method is described in the second edition of
the Transmission Line Reference Book. All the algorithms used for this applet are described in details in the
Appendix at the end of this Help document. In order to overcome the limitations of the traditional method, Dr.
Robert Olsen has developed the wideband method of EMI calculations, which is the basis for Applet RN-1.

The results of this applet consist in the median Radio Noise during measurable rain (L50 rain). The Radio Noise is
calculated as an electric field (dB above 1 μV/m) read either by a rod or a loop antenna with a CISPR quasi-peak

C-25
Software Requirements TL Workstation Design Tools Rev. 0

detector with a 9 kHz bandwidth. The conductors are treated as if they were infinitely long and parallel to a flat
conductive earth. Any number of circuits may be considered, and the voltages do not have to be symmetric. Each
phase may have a different bundle, whose geometry must be specified. The conductors are assumed to be ACSR.
Ground wires are considered for the calculation of the surface gradient of phase conductors and for the propagation
of radio noise currents and voltages along the line. The applet calculates the excitation function of each phase based
on bundle geometry, surface gradient, frequency, and altitude above sea level. The excitation function is given for a
CISPR quasi-peak detector with a 9 kHz bandwidth. The excitation function is then used to calculate the Radio
Noise accounting for line geometry, measuring frequency, earth resistivity, and earth dielectric constant. The Radio
Noise profile is calculated along a specified horizontal line perpendicular to the transmission line.

S-1

This applet calculates the 50% flashover voltage, V50, of air gaps of complex geometry when stressed with switching
impulses of positive polarity and critical time to crest. Chapter 5 of the Reference Book reports V50 data for several
gaps with simple geometry (rod-plane, rod-rod, conductor-plane, conductor-tower truss, etc). This applet extends the
calculations to any type of air gap using a flashover model generically described in Chapter 5, Appendix 2 of the
Reference Book.

File Menu

The File Menu provides options to manage the available projects in the selected Data Source to which the
application is connected. Those options are:
• New Project
o Allows user to create a new, empty project.
• Open Project
o Allows user to select an existing project to open.
• Close Project
o Allows user to close the open project.
• Save Project
o Allows user to save any current changes to the open project.
• Save Project As…
o Allows user to duplicate the open project, requiring the user to provide a different name for the
new project. It closes the old project, making the new project the open project.
• Delete Project
o Allows user to delete the current open project.
• Import Project
o Allows user to import a project that had either been previously exported from the currently
connected data source or exported from some other data source. The file will be an XML
formatted file. (Will allow users to share project data amongst data sources.)
• Export Project and
o Allows user to export the current open project. The export file will be an XML formatted file.
• Project Properties
o Allow user to change the default project properties, including the name and description.

The menu also provides a Change Data Source option that will allow the user to close the current data source and
open a different data source without having to exit the application.

Segments Menu

The Segments Menu provides options to manage the individual Right-Of-Way/Circuit Configurations (Segments)
within the open project. Those options are:

C-26
Functional Specifications TL Workstation Design Tools Rev. 0

• New Segment
o Allows user to create a new, empty segment. User will be required to a unique name and
description for the new segment. Once the application determines the name to be valid, it opens a
new Child Window to provide the user the ability to enter the data describing the segment.
• Open Segment
o Allows user to select another segment from within the currently open project to open. It opens a
new Child Window to allow editing of the data for that Segment.
• Open All Segments
o Allows user to open for editing, all remaining Segments in the open project. It opens one Child
window for each Segment in the project. For a large project, this could be a lot.
• Close Segment
o Allows user to close the currently active Child window, and correspondingly, the Segment that
window manages. If there are any outstanding changes, the user will be asked if they wish to save
those changes before closing.
• Close All Segments
o Allows user to close all Child windows. As with Close Segment, the user will be asked if they
wish to save any changes. They will also be provided the options of Yes to All and No to All.
• Save Segment
o Allows user to save the Segment in the currently active Child window.
• Save As Segment…
o Allows user to duplicate the Segment in the currently active Child window, creating a new
Segment within the currently open project. The user will be required to change the name of the
Segment to ensure uniqueness.
• Save All Segments
o Allows user to save all currently open Segments.
• Delete Segment
o Allows user to delete the Segment in the currently active Child window.
• Import Segment
o Allows user to import a Segment that had either been previously exported from the current project
or exported from some other project or data source. The file will be an XML formatted file. (Will
allow users to share Segment data amongst data sources and projects.)
• Export Segment
o Allows user to export the Segment in the currently active Child window. The export file will be an
XML formatted file.
• Segment Properties
o Allow user to change the default Segment properties, including the name and description.

Analysis Menu

The Analysis Menu provides option to run the Applet calculations against the Project/Segment data. It will allow the
user to run the analysis on the entire project, the currently active Segment (Child window) or to run specific Applet
calculations. This is subject to change pending review by the Task Force. At this time (9/8/2006), the options are:
• Run Segment Analysis
• Run Project Analysis
• Audible Noise [applets sub-menu]
• Surface Gradients [applets sub-menu]
• Corona/Ozone [applets sub-menu]
• Electric and Magnetic Fields [applets sub-menu]
• Radio Noise [applets sub-menu] and
• Switching [applets sub-menu]

C-27
Software Requirements TL Workstation Design Tools Rev. 0

Reports Menu

The Reports Menu allows the user to specify how the results are to be presented, or to display the results of a
previously executed analysis for the currently active Child window (Segment). The options are:
• Report
• Plot
• Excel
• Word
• Default Report Type [sub-menu]
o Allows user to specify the default type of file to which to write the analysis output (e.g. Word,
Excel or internal report dialog).
• Output Directory
o This allows the user to specify the directory to which report files (e.g. Word document) should be
written.

View Menu

The View Menu allows the user to configure the user interface. For now, the configuration options are limited to:
• System of Units [sub-menu]
o This allows the user to specify the units to use when displaying dimensioned data. The options are:
ƒ By Project
ƒ English
ƒ SI
• Angle Units [sub-menu]
o This allows the user to specify the units to use to display angles. The options are:
ƒ By Project
ƒ Degrees
ƒ Radians
ƒ Milliradians
ƒ Grads

In addition, any available dialogs to display or manage underlying reference data, are listed in this menu. For now,
the only dialog is Conductor Names, which allows for management of the Conductor Wire types (from Applet CC-
4).

Windows Menu

This menu contains the standard MDI Parent Windows Menu options of: Cascade, Tile Horizontally, Tile Vertically,
Minimize All, and Arrange All. It will also contain a list of all Child Forms and other open non-modal application
forms.

Help Menu

C-28
Functional Specifications TL Workstation Design Tools Rev. 0

This menu contains the standard Help Menu options of: Help Contents, Help Index, Using Help and About. It will
also contain a sub-menu of any Demonstration Applets the Task Force may choose to include in the application.

C-29
Software Requirements TL Workstation Design Tools Rev. 0

Low-Level Design

Data Diagrams

Project Header

The Project Header Tables are retained from TLWorkstation version 3 for the initial
database. However, the key field sizes are increased to allow for the use of more
descriptive names.

TL Workstation Project/Segment/Tower Header

Project ProjectApplication

PK stProjectName PK stProgramName
PK,FK1 stProjectName
stAuthorName
stAppCreatedBy stAuthorName
dtStart dtModified
dtLastChange chUnitsOfMeas
stDesc1
stDesc2
stDesc3
stDesc4

ProjectDescription

PK,FK1 stProgramName
PK,FK1 stProjectName

dtStart
stDesc1
stDesc2
stDesc3
stDesc4

ProjectSegment
PK,FK1 stProjectName
PK stSegmentName ProjectDetails

stDesc1 PK,FK1 stSegmentName

stDesc2 PK stTowerName
stDesc3 PK,FK2 stProgramName
stDesc4 PK,FK2 stProjectName
dLatitude
dLongitude chUnitsOfMeas
dLineLength dtStart
iLineLengthUnit dtModified
sKeraunic stAuthorName
sTimeZone stDesc1
dAltitude stDesc2
iAltitudeUnit stDesc3
dRightOfWay stDesc4
iRightOfWayUnit

C-30
Functional Specifications TL Workstation Design Tools Rev. 0

Circuit Configuration

Similarly, the Circuit configuration tables are retained from TL Workstation version 3.0:

C-31
Software Requirements TL Workstation Design Tools Rev. 0

Miscellaneous Right-Of-Way Objects

The Objects Tables have been revised to allow for additional information required by the
algorithms used by the Applets.

TL Workstation Design Tools ACDCLine

Miscellaneous Right-Of-Way Objects

AcdcMiscObject AcdcMiscObjectPoint
PK stProjectName PK,FK1 stProjectName
PK stSegmentName PK,FK1 stSegmentName
PK stTowerName PK,FK1 stTowerName
PK nMiscObjectNo PK,FK1 nMiscObjectNo
PK PointNo
stMiscObjectType
VoltageInKV XInM
PhaseInDeg YInM
CurrentInAmp ZInM
DiameterInM
InnerDiameterInM
Turns
CurrMultFactor
GMDInM
ResistanceInOhm
CapacitanceInFarad
SagMidHeightInM

Support Modules

Jama Module

This module contains the Jama calculation routines for matricies as used by the original Applets…

This module has been enhanced to provide additional math objects and functions. These routines are used in this
application to simplify the appearance of the calculations, making them easier to validate for correctness…

C-32
Functional Specifications TL Workstation Design Tools Rev. 0

Maths
Class

Methods
ACosh
ASinh
ATanh
DegToRad (+ 1 overload)
Distance (+ 3 overloads)
RadToDeg (+ 1 overload)
Resultant (+ 3 overloads)
SinCos (+ 1 overload)

Additional structures and classes added to support geometric calculations and 3-D results displays...

Vector2D Point2D Bounds3D

Class Class Class

GLRotation3D
Class

Vector3D Point3D
Class Class
Vector2D Point2D RCatenaryParms
Struct

RCatenaryPoint
Struct

Vector4D Point4D
Class Class
Vector3D Point3D

AppletCommon Module

This module contains all miscellaneous classes from the original Applets, plus new classes used by all integrated
Applets.

Classes from the original Applets…

C-33
Software Requirements TL Workstation Design Tools Rev. 0

Most data entry fields in the application involve numeric data that have specific unit dimensions. These data fields
allow the user to enter unit text when entering these numbers in order to override the default units used in the
interface. For example, a given field may require a number with the units of Length and the display is in feet. In this
application, in such a field, if the user enters just a number, then it is assumed to be in the display units of feet.
However, this application allows the user to enter ‘6 in’; the application will automatically convert it to ‘0.5’ (ft).
To support this, these field validations/unit conversions are encapsulated in classes, a few of which are illustrated
below.

Additional miscellaneous Enumerated Types, Exception Types have been added to this module to simplify the code
of all converted Applets.

Electric Circuit Components Module

The original Applets defined Circuit, Bundle and Conductor (named Cylinder) classes to encapsulate the data
pertaining to those individual real-world objects. With this integration, that data is properly encapsulated as
Properties. Also, the field names in these classes have been modified to be more descriptive, and to contain the units.
For example, the diameter of the conductor was named ‘dblD’. In this application, the field, as a property, has been
renamed to ‘DiameterInCm’, i.e. diameter in centimeters. This should greatly facilitate code validation during
testing. In addition, the conductor wire name and type are further refactored to encapsulate those parameters and
further simplify the code, eliminating duplication.

C-34
Functional Specifications TL Workstation Design Tools Rev. 0

Abstract Class

Circuit IEditableObject
Class
Asset ConductorType
Class
Asset

IEditableObject IEditableObject

Bundle ConductorName
Class Class
Asset Asset

ICloneable
IEditableObject

Conductor
Class
Asset

Various Applets used either 2-D or 3-D Electric field calculations. The class and naming of the corresponding
routines varied. All the calculation modules have been reconciled and refactored into two basic classes that will be
used by all Applets in the new application…

C-35
Software Requirements TL Workstation Design Tools Rev. 0

Abstract Class
Asset

BoxObject FlatPlateObject
Class Abstract Class Class
MiscObject MiscObject MiscObject

ToroidObject WireObject
Class Class
MiscCylindricalObject MiscCylindricalObject

CatenaryObject CylinderObject
Class Class
MiscCylindricalObject MiscCylindricalObject

SphereObject CoilObject RodObject

Class Class Class
MiscCylindricalObject MiscCylindricalObject MiscCylindricalObject

OpenGL 3-D Model Display Modules

Separate modules have been included, which interface .NET Managed Code to Windows native OpenGL dlls. These
include:
4. csgl.native, which is creates the dll that encapsulate the interface to the OpenGL.org Windows dlls:
opengl.dll. Glu.dll and glut.dll.
5. CsGL, which provide wrappers for all the basic OpenGL types; and,
6. CsGLBasecode, which provides high-level wrappers encapsulating a Windows Control, ‘View’, that
provides the display canvas control that appear on a Form; and one that encapsulates the displayed 3-D
objects ’Model’.

This application encapsulates extended functionality by extending the above wrappers in CsGLBasecode with
‘RedbookGLControl’ and ‘RedbookModel’ respectively. These controls are provided by the ‘RedbookGL’ module.

In addition, the routines for rendering Conductors and Miscellaneous Objects are encapsulated in another set of
classes. These are also included the ‘RedbookGL’ module.

Graphing Module

C-36
Functional Specifications TL Workstation Design Tools Rev. 0

Displaying Graphs is accomplished with another tool called Zedgraph.

However, the components in Zedgraph are encapsulated in wrappers in the AppletCommon. This is done to
simplify the development of the graphs and to ensure consistency…

IPointList

GraphMultiPoint…
Class Abstract Class

MultiCalculation…
Class Abstract Class
GraphMultiPointList GraphData

Individual Applets’ Code

AN-1

AN-2

AN-3

C-37
Software Requirements TL Workstation Design Tools Rev. 0

AN-4

Detailed Design remains to be done.

AN-6

Detailed Design remains to be done.

CC-1

The 2-D Surface Gradient calculation from this Applet has been reconciled with the Surface Gradient calculations in
the other Applets, and refactored into the ElectricField2D module listed in the Electric Circuits Component Modules
above.

CC-4

This Applet is converted and reformatted as shown below.

C-38
Functional Specifications TL Workstation Design Tools Rev. 0

CC-5

Detailed Design remains to be done.

CL-1

Detailed Design remains to be done.

CL-3

C-39
Software Requirements TL Workstation Design Tools Rev. 0

Detailed Design remains to be done.

EMF-2/EMF-5

EMF-5 is really the same as EMF-2, with the addition of miscellaneous objects in the field.

EMF-4

EMF-6

Detailed Design remains to be done.

EMF-7

Detailed Design remains to be done.

EMF-8

Detailed Design remains to be done.

EMF-9

Detailed Design remains to be done.

EMF-10

C-40
Functional Specifications TL Workstation Design Tools Rev. 0

EMF-11

Detailed Design remains to be done.

EMF-12

Detailed Design remains to be done.

RN-1

Detailed Design remains to be done.

RN-2

Detailed Design remains to be done.

RN-4

Detailed Design remains to be done.

S-1

Detailed Design remains to be done.

Starting Application

On executing the application, the application initializes with the following steps:
1. Displays the EPRI Disclaimer dialog. This dialog displays the Disclaimer and OK and Cancel buttons. If
the user clicks the Cancel button, then the application terminates. If the user clicks the OK button, then the
application proceeds to…
2. Display the Data Source Connection dialog. This dialog provides:
a. UserID field for the userid with which to connect to the Data Source,
b. Password field for the Password for the entered UserID and Data Source,
c. A Change Connection button to allow user to configure a different Data Source,
d. An OK button, which the user clicks to proceed and
e. A Cancel button, which the user clicks to terminate the application.
3. Displays the application main form.

Disclaimer Form

C-41
Software Requirements TL Workstation Design Tools Rev. 0

Data Source Connection Dialog

A database is installed with the application for desktop use. But, in general, the
application is designed to allow access to different sources of data. Some of those data
sources may require the user to log in with a userid and password. So, when the
application starts, and the currently configured data source (from the Registry) requires
a userid and password, the user is requested to either enter the userid and password, or
change to connect to a different data source.

C-42
Functional Specifications TL Workstation Design Tools Rev. 0

Application Main (MDI Parent) Form

Menu Functions

File Menu

The File Menu provides options to manage the available projects in the selected Data Source to which the
application is connected.

New Project

This option allows user to create a new, empty project.

Open Project

C-43
Software Requirements TL Workstation Design Tools Rev. 0

This option allows user to select an existing project to open.

Open Project Dialog

Close Project

This option allows user to close the open project.

Save Project

This option allows user to save any current changes to the open project.

Save Project As…

This option allows user to duplicate the open project.

Delete Project

This option allows user to delete the current open project.

Import Project

This option allows user to import a project

C-44
Functional Specifications TL Workstation Design Tools Rev. 0

Export Project

This option allows user to export the current open project.

Project Properties

This option allow user to change the default project properties.

Change Data Source

This option allow the user to switch data source.

Segments Menu

The Segments Menu provides options to manage the individual Right-Of-Way/Circuit Configurations (Segments)
within the open project.

New Segment

This option allows user to create a new, empty segment. User will be required to a unique name and
description for the new segment. Once the application determines the name to be valid, it opens a new
Child Window to provide the user the ability to enter the data describing the segment.

Open Segment

This option allows user to select another segment from within the currently open project to open. It opens a
new Child Window to allow editing of the data for that Segment.

Open All Segments

This option allows user to open for editing, all remaining Segments in the open project. It opens one Child
window for each Segment in the project. For a large project, this could be a lot.

Close Segment

C-45
Software Requirements TL Workstation Design Tools Rev. 0

This option allows user to close the currently active Child window, and correspondingly, the Segment that
window manages. If there are any outstanding changes, the user will be asked if they wish to save those
changes before closing.

Close All Segments

This option allows user to close all Child windows. As with Close Segment, the user will be asked if they
wish to save any changes. They will also be provided the options of Yes to All and No to All.

Save Segment

This option allows user to save the Segment in the currently active Child window.

Save As Segment…

This option allows user to duplicate the Segment in the currently active Child window, creating a new
Segment within the currently open project. The user will be required to change the name of the Segment to
ensure uniqueness.

Save All Segments

This option allows user to save all currently open Segments.

Delete Segment

This option allows user to delete the Segment in the currently active Child window.

Import Segment

This option allows user to import a Segment that had either been previously exported from the current
project or exported from some other project or data source. The file will be an XML formatted file. (Will
allow users to share Segment data amongst data sources and projects.)

Export Segment

This option allows user to export the Segment in the currently active Child window. The export file will be
an XML formatted file.

C-46
Functional Specifications TL Workstation Design Tools Rev. 0

Segment Properties

This option allow user to change the default Segment properties, including the name and description.

Analysis Menu

The Analysis Menu provides option to run the Applet calculations against the Project/Segment data. It will allow the
user to run the analysis on the entire project, the currently active Segment (Child window) or to run specific Applet
calculations. This is subject to change pending review by the Task Force

Run Segment Analysis

Run Project Analysis

Audible Noise [applets sub-menu]

Surface Gradients [applets sub-menu]

Corona/Ozone [applets sub-menu]

Electric and Magnetic Fields [applets sub-menu]

Radio Noise [applets sub-menu] and

Switching [applets sub-menu]

Reports Menu

The Reports Menu allows the user to specify how the results are to be presented, or to display the results of a
previously executed analysis for the currently active Child window (Segment).

Report

C-47
Software Requirements TL Workstation Design Tools Rev. 0

Plot

Excel

Word

Default Report Type [sub-menu]

Allows user to specify the default type of file to which to write the analysis output (e.g. Word, Excel or
internal report dialog).

Output Directory

This allows the user to specify the directory to which report files (e.g. Word document) should be written.

View Menu

The View Menu allows the user to configure the user interface.

System of Units [sub-menu]

This allows the user to specify the units to use when displaying dimensioned data. The options are:
By Project
English
SI

Angle Units [sub-menu]

This allows the user to specify the units to use to display angles. The options are:
By Project
Degrees
Radians
Milliradians

C-48
Functional Specifications TL Workstation Design Tools Rev. 0

Grads

Conductor Names

Display Conductor Wire types dialog (from Applet CC-4).

Help Menu

This menu contains the standard Help Menu options

Help Contents

Help Index

Using Help

About.

Demonstration Applets [sub-menu]

C-49
Software Requirements TL Workstation Design Tools Rev. 0

Child Form

Circuit/Bundle/Conductor Configuration Tab

This is an example Child form showing the Primary tab the user would use to enter the Circuit, Bundle and
Conductor configuration.

C-50
Functional Specifications TL Workstation Design Tools Rev. 0

Miscellaneous Objects Tab

The second tab [currently] allows the user to specify the miscellaneous object in the Right-Of-Way.

C-51
Software Requirements TL Workstation Design Tools Rev. 0

Location/Profile Specifications Tab

The third tab [currently] allows the user to specify the calculation parameters.

C-52
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES
THIS DOCUMENT WAS PREPARED BY THE ORGANIZATION(S) NAMED BELOW AS AN ACCOUNT OF
WORK SPONSORED OR COSPONSORED BY THE ELECTRIC POWER RESEARCH INSTITUTE, INC. (EPRI).
NEITHER EPRI, ANY MEMBER OF EPRI, ANY COSPONSOR, THE ORGANIZATION(S) BELOW, NOR ANY
PERSON ACTING ON BEHALF OF ANY OF THEM:

(A) MAKES ANY WARRANTY OR REPRESENTATION WHATSOEVER, EXPRESS OR IMPLIED, (I) WITH
RESPECT TO THE USE OF ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM
DISCLOSED IN THIS DOCUMENT, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, OR (II) THAT SUCH USE DOES NOT INFRINGE ON OR INTERFERE WITH PRIVATELY OWNED
RIGHTS, INCLUDING ANY PARTY'S INTELLECTUAL PROPERTY, OR (III) THAT THIS DOCUMENT IS
SUITABLE TO ANY PARTICULAR USER'S CIRCUMSTANCE; OR

(B) ASSUMES RESPONSIBILITY FOR ANY DAMAGES OR OTHER LIABILITY WHATSOEVER (INCLUDING
ANY CONSEQUENTIAL DAMAGES, EVEN IF EPRI OR ANY EPRI REPRESENTATIVE HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES) RESULTING FROM YOUR SELECTION OR USE OF THIS
DOCUMENT OR ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM DISCLOSED IN
THIS DOCUMENT.

ORGANIZATION(S) THAT PREPARED THIS DOCUMENT

EPRI

This is an EPRI Technical Update report. A Technical Update report is intended as an informal report of
continuing research, a meeting, or a topical study. It is not a final EPRI technical report.

NOTE
For further information about EPRI, call the EPRI Customer Assistance Center at 800.313.3774 or
e-mail [email protected].

Electric Power Research Institute and EPRI are registered service marks of the Electric Power
Research Institute, Inc.

Copyright © 2006 Electric Power Research Institute, Inc. All rights reserved.
CITATIONS

This document was prepared by

EPRI
3420 Hillview Avenue
Palo Alto, CA 94304

Principal Investigator
J. Chan

EPRI
100 Research Drive
Haslet, TX 76052

Principal Investigator
I. Baskerville

This report describes research sponsored by the Electric Power Research Institute (EPRI).

The report is a corporate document that should be cited in the literature in the following manner:
Integration of Transmission Design Tools and Software. EPRI, Palo Alto, CA: 2006. 1012318.

iii
ABSTRACT

EPRI is updating the Transmission Line Design Tools by upgrading the design software package
TLWorkstation (TLW). TLW is a comprehensive software package contains a number of design
modules for transmission line designers. The modules for electrical designs were based on
information from EPRI Transmission Line Reference Book – 345 kV and Above, published in
1987 (the Red Book). A new version of the Red Book was published in 2004 along with a suite
of 50 small applets. To take advantage of the new information and the applets, the most
immediately step to upgrade the design tools is to integrate these applets into TLW.

The applets in the Red Book are targeted for the reader and were not developed as an integrated
design package. Thus separate data entry is required for each of these applets while TLW
provides a single, common database that manages and shares data among modules, and
incorporates industry standards, such as conductor and wire stress properties. The goal of the
integration is to avoid duplicating data entries and to provide friendly user interface.

In 2005, strategies and an implementation plan for achieving this integration were developed.
After detail review of the structure and software of the applets and TLW, the best way to
integrate the transmission design tools into one single package was identified. The most suitable
applets to be integrated into TLW were determined in 2006 and full integration was initiated.
The approach and selection were presented and discussed at the Overhead Transmission Design
Task Force meetings in Dallas, TX meeting on April 4-5 and in Atlanta, GA on September 18-19
as well as at the Webcasts on July 11 and October 24. Input was sought and feedbacks from
users were incorporated into the integration. The integration has reached the Alpha testing stage
the end of 2006. Integration will continue to Beta testing and then to completion the end of
2007.

Keywords
TLWorkstation
Transmission Line Design
Overhead Line Design
Line Design Tools
Line Design Software

v
CONTENTS

1 INTRODUCTION ....................................................................................................................1-1
Background ...........................................................................................................................1-1
Strategies ..............................................................................................................................1-1

2 TLWORKSTATION ................................................................................................................2-1
ACDCLINE ............................................................................................................................2-4
CORRIDOR...........................................................................................................................2-5
DYNAMP ...............................................................................................................................2-6
FAD .......................................................................................................................................2-7
MINIDES ...............................................................................................................................2-8
RNOISE ..............................................................................................................................2-11
TLOPGR .............................................................................................................................2-11
UPSTUDY ...........................................................................................................................2-12
WIRELDS ............................................................................................................................2-12

3 IMPLEMENTATION PLAN.....................................................................................................3-1
General .................................................................................................................................3-1
Current Applets – Development Environment .......................................................................3-3
Current Applets - Other Issues..............................................................................................3-4
Development Plan .................................................................................................................3-4
Activities in 2005 ...................................................................................................................3-5
Activities in 2006 ...................................................................................................................3-6
Work for 2007........................................................................................................................3-9
Future Work...........................................................................................................................3-9

4 SOFTWARE APPROVAL PROCESS ....................................................................................4-1

Product Requirements for All EPRI Software........................................................................4-1
Security Policy.......................................................................................................................4-4

vii
Contents

EPRI Software Development Process Requirements ...........................................................4-5

A APPENDIX ............................................................................................................................ A-1

B SOFTWARE REQUIREMENTS............................................................................................ B-1

C FUNCTIONAL SPECIFICATIONS ........................................................................................ C-1

viii
LIST OF FIGURES

Figure 2-1 Data Flow within TLWorkstation ...............................................................................2-2

ix
LIST OF TABLES

Table 3-1 Project Activities Schedule for 2006 ..........................................................................3-8

Table 4-1 EPRI Process Table and Planned Schedule .............................................................4-6
Table 4-2 Software Acceptance Form (SAF): Acceptance Testing, Publishing, and
Distribution Web and PC Applications ...............................................................................4-7

xi
1
INTRODUCTION

Background

Over the years, the Electric Power Research Institute (EPRI) has published a number of world-
renowned transmission line reference books and software, which are considered an industry
standard and are valued by many transmission companies and engineers. In addition, EPRI
issued the TLWorkstation (TLW) in the early 1990s, a comprehensive transmission line design
package that has a very strong set of users. In 2004, EPRI published the third edition of the
Transmission Line Reference Book – 200 kV and Above (the Red Book), along with a suite of
some 50 small software routines to help the reader employ the design theory within the book.
These software routines are targeted for the reader of the Red Book and were not developed as
an integrated design package. Thus separate data entry is required for each of these applets. The
software package in TLW contains a number of design modules, many of which were based on
the previous version of the Red Book. With changes in the Red Book, it is necessary to review
the present status of the TLW.

At the same time, new transmission line design packages have entered the market in recent years.
Consequently, a number of these tools, each with unique benefits could be integrated into the
TLW to form a more complete software package. For example, there are exceptional
commercial transmission line mechanical and 3-D graphical design packages. It would be ideal
to bring these design tools together, since the TLWorkstation is a leader in electrical design, with
a number of the existing modules in daily use by the global power delivery industry. This
combination would involve identifying the best of breed and then ensuring that the best EPRI
products work in an integrated fashion with the best commercial software.

Strategies

As a result of transmission expansion in some parts of the world such as South America, South
East Asia and Africa, and also the recent round of blackouts, it is clear that there is renewed
interest in building new transmission lines. The need to consider construction of high voltage
transmission lines is also captured in some of the recent US Government Department of Energy
documents. In the past there has been a slump in overhead line construction. Consequently, skill
levels within the industry have declined. Further, there are very powerful CAD and line layout
design software packages that are almost considered industry standards that have not been
interfaced with EPRI’s TLWorkstation. Combining with the new edition of the Red Book, it is
therefore crucial that TLW must be updated to address all these changes and challenges.

1-1
Introduction

In 2005, strategies for achieving integration of the Red Book applets were developed. The
general strategies were:

1. Identify one or more key line design packages, such as the PLSCAD and TLPRO that are
very strong on the graphical and structural aspects of line designs.

2. Develop a standard to move data between EPRI design modules and other design
software.

3. Focus on enhancing EPRI modules, ensuring that they are very robust and reflect the
latest thinking.

4. Look to market these modules as either stand alone or packages that can be loaded up
alongside the commercial software.

After detail review of the structure and software of the applets and TLW, the best way to
integrate the transmission design tools into one single package was identified in 2005.

This report provides an update of the integration since the first progress report on “Integration of
Transmission Design Tools and Software” was published in November 2005.

1-2
2
TLWORKSTATION

To comprehend fully the scope of work and activities involved in integrating the Red Book
applets into TLWorkstation (TLW), it is necessary to understand the structure and modules
inside TLW. This Chapter provides general description of the overall structure and different
modules of the existing TLW, their capability and features. Understanding the dynamics of
these application programs is essential in the development of the new TLWorkstation.

TLW is a comprehensive package of interactive computer programs for designing new

transmission lines and upgrading existing lines. TLW integrates a variety of software
applications that can be used separately or as one complete package to support the following:
Line analysis and optimization
Upgrade planning and design
Foundation analysis and design
Conductor/insulator analysis
Structural analysis and design

There are nine modules plus the EXECUTIVE control program. The modules are accessed and
integrated through this EXECUTIVE program which is displayed in the Program Manager. The
flow of data into, within and out of TLW is facilitated by the user interface, the executive control
program and the database management system and, is shown in Figure 2.1.

2-1
 User Interface

Executive Control Program

R
NE

Y
O

DS
P

ES

UD
Task Modules

ID

E
LI

PG

EL
IS
RR
DC

ID
NA

ST
O
D

IR
IN
CO

RN
DY

UP
AC

FA

TL

W
M
Database Management System
R
NE

Y
O

DS
P

ES

UD
Database
ID

E
LI

PG

EL
IS
RR
DC

ID
NA

ST
O
D

IR
IN
CO

RN
DY

UP
AC

FA

TL

W
M

Figure 2-1
Data Flow within TLWorkstation

2-2
The EXECUTIVE allows the user to customize the workstation environment to include only
those modules that the user needs. The user can add or remove task modules at any time without
affecting other workstations sharing the same machine. Complying with ODBC standards, the
EXECUTIVE features a relational database management system. This system provides an
efficient sharing of files and data among all modules and provides the capability of interfacing
with third-party software.

The latest TLW software is Version 3.0. TLW 3.0 has a full Windows environment that
provides a user-friendly graphical interface to increase the efficiency of producing and
modifying transmission designs. TLW features new and enhanced online Help documentation
that provides easy access to descriptions, hands-on tutorials and key engineering concepts.
Novice users have successfully used the design and analysis modules after only one or two hours
of training. Improved graphics capabilities include full-color two and three-dimensional plots
which make it easy for users to interpret the results of their design efforts.

TLW's unique structure enables the user to accomplish and record all related tasks within a larger
project or use individual programs to solve independent problems. Because the system maintains
a record of all past work, a new user can pick up where others left off. Besides helping utilities
complete larger projects much more quickly, TLW's integrated features can improve
communication between transmission line designers. Utility personnel with different functions
and specialties can more easily unify their efforts and maximize workgroup collaboration.

TLWorkstation 3.0 provides the following features:

Single, common database: Manages and shares data among modules, and incorporates industry
standards, such as conductor and wire stress properties.
Windows programming standard guidelines: Complies with Open Database Connectivity
(ODBC) standards.
Graphical user interface: Provides an easy-to-use Windows environment for input and output.
Fast conversion of existing databases: Loads and converts data from earlier versions of TLW
into the new common database.
Mixed units of measurement support: Allows the user to switch between English and SI units
within a project.
Illustrated online Help: Displays the entire user's manual as a Help file, and provides step-by-
step tutorials and reference information.
Full-color graphics plotting package: Creates two and three-dimensional plots and allows the
user to edit plot attributes.
Compatibility with various operating systems: Operates on Microsoft Windows 3.1, Windows
95 and Windows NT.

The nine modules are:

1. ACDCLINE: studies electric and magnetic phenomena of AC, DC and hybrid lines

2-3
TLWORKSTATION

2. CORRIDOR: solves problems related to shared use of right-of-way

3. DYNAMP: evaluates the dynamic ampacity of overhead conductors
4. FAD: performs foundation analysis and design
5. MINIDES: studies preliminary design of transmission line structures
6. RNOISE: calculates radio noise in fair and foul weather from high voltage lines
7. TLOPGR: displays the impacts of alternative line upgrades on design parameters
8. UPSTUDY: examines the feasibility and cost for upgrade alternatives
9. WIRELDS: generates loading trees for all types of structures

Detail descriptions of each module are given below.

ACDCLINE

This program provides the necessary tools for studying a range of electric and magnetic
phenomena associated with AC transmission lines, DC transmission lines, and AC/DC hybrid
lines.

ACDCLINE provides information on the following areas: conductor surface voltage gradients,
corona losses, audible noise, radio noise, ozone, electric field, ion density, ion current, human
sensation levels to electric fields, coupling to objects, shielding by objects, magnetic field, surge
performance of towers, and selection of insulators based on surface contamination. Graphics
options are also available for viewing the line geometry specified by the user and profiles of the
computed results.

ACDCLINE is composed of several individual sub-modules that are fully integrated. The
database contains common overhead conductors which simplify execution. ACDCLINE
automatically enters the physical constants of a conductor upon specifying the conductor code
name. It analyzes and designs AC lines, DC lines, multi-circuit lines, or hybrid AC/DC lines.
Solidly bonded, sectionalized and isolated ground wires can be specified, as well as different
span lengths for various circuits. For each project, ACDCLINE can perform calculations for:
Up to 12 phases for AC lines
Up to 24 AC and/or DC bundles (including energized and grounded bundles)
Up to 50 individual conductors
Regular and irregular bundle arrangements

The following are execution options in ACDCLINE for AC, DC or hybrid AC/DC lines:

1. Corona calculations (average height)

Surface gradient
Corona loss
Audible noise

2-4
 TLWORKSTATION

Ozone (only if DC bundles exist)

Radio noise

2. E-field and ion calculations (actual height)

Surface gradient
Electric field and ions without shielding objects
Sensation levels
Coupling to objects and shielding by objects

3. Magnetic field calculations (actual height)

Magnetic field

4. Insulation analysis
Switching surge performance
Insulator contamination

ACDCLINE uses various methods for calculating audible and radio noise. Human response
models to electric fields and field sensation levels are available. Coupling and shielding object
options allow for the calculation of voltages and currents coupled to nearby objects, as well as
the calculation of shielding effects of nearby objects. The magnetic field option calculates the
effects of induced ground wire currents, and the insulator contamination option includes the
selection of insulator number and type based on the contamination level.

CORRIDOR

This program solves complex right-of-way problems that include: power transmission lines,
multiple pipelines, other buried or above-ground conductors, railroad track circuits, and railroad
signal and communication lines. It provides the necessary tools for studying interference
conditions that may occur as a result of sharing a common corridor by these utilities.

CORRIDOR enables those with a minimum background in electromagnetic analysis to solve

complex rights-of-way problems. CORRIDOR calculates and provides as output the steady-state
or fault-induced voltage and current caused by adjacent electric power transmission lines at
locations of interest along pipelines, railroads, communications wires, shielded cables, or other
conductors. The analysis can include excitation of the passive conductors, by either magnetic or
electric fields that are produced by power lines.

CORRIDOR analyzes utility common corridors for which the passive conductors (non-power
line conductors) are nominally parallel. The program can model changes in the spacing between
passive conductors by dividing the corridor into nominally parallel segments. If the spacing
between passive conductors gradually changes, the region of change should be divided into
segments with stepwise constant effective separation. CORRIDOR allows the modeling of power
lines that are at an angle to the nominally parallel passive conductors. CORRIDOR makes it
easy to model several types of passive conductors that are typically encountered in common
utility corridors. The common passive conductors in CORRIDOR include:
Pipelines: Buried or above ground.

2-5
TLWORKSTATION

Rails or track: Specified to the program by customary railroad parameters.

Wires: Buried or above ground, and can be used to model such occurrences as fences, railroad
open wire communications or signal lines, mitigation wires, or de-energized power-line
conductors.
Shielded cables: Buried or above ground.

CORRIDOR calculates the voltage and current on the passive conductors that result from:
Current in power-line conductors: The effect on the passive conductors is by magnetic-field
coupling.
Voltage on power-line conductors: The power-conductor voltage results in a vertical component
of electric field near the earth that induces a voltage onto insulated passive conductors.
Voltage and current on the other passive conductors.
Discrete voltage sources that are connected to the passive conductors at user-selected locations to
simulate discrete signal sources.

The voltage and current induced onto passive conductors by the first two of the above types of
coupling can be calculated by the program either individually or together. Thus, the program
offers the user the opportunity to determine the relative importance of the two coupling
mechanisms for the modeled problem. Knowledge of which coupling mechanism is responsible
for the voltage or current on a conductor can be an important consideration in identifying
alternative methods to minimize interference to equipment or personnel safety risks.

The passive conductors (rails, pipelines, etc.) interact with each other. Thus, one passive
conductor can influence the resultant voltage and current on other passive conductors.
Therefore, the program allows the user to include all important passive conductors in the analysis
to accurately reflect resultant interactions. CORRIDOR can calculate induced voltage and
current due to the steady-state or faulted operation of the power line. The effects of the normal
small unbalance in the power-line-conductor currents can be readily assessed, if the unbalance is
known or is estimated. In addition, the program can be used to calculate other parameters or
voltages and currents of interest. This includes the shield factor of shielded cables, potential of
earth surface points, voltage and current associated with the impedance elements in the problem,
and current in power line overhead shield wires.

DYNAMP

This program appraises and reappraises the DYNamic AMPacity of overhead conductors. It
provides guidelines for producing either steady state, transient or predictive calculations for a
wide range of conductors and covers real-life examples of each type of calculation. Developed
at the Georgia Institute of Technology, DYNAMP's accuracy has been verified by comparing the
predicted conductor temperatures with values measured at Georgia Power Company's Research
Center and temperatures measured in a separate study sponsored by Kansas Electric Utilities
Research Program and implemented by Kansas Gas and Electric Company.

2-6
 TLWORKSTATION

DYNAMP includes common overhead conductors in the database to increase productivity. The
program automatically enters the conductor's five physical constants upon naming the conductor
code. Real-time calculations can be conducted. All real-time calculations are based upon
ambient weather. DYNAMP frequently updates these calculations so that real-time values of
wind speed and direction and the ambient temperature are used as input data. The program
incorporates the effects of the changing weather and conductor current into the thermal analysis
by accounting for the thermal capacity of the conductor.

The contribution of the sun, loading on the conductor temperature, is automatically considered in
a separate subroutine that calculates the clear sky incident solar energy at the specified location
of the conductor. DYNAMP predicts real-time temperatures for seven types of conductors. The
program uses composite conductors such as ACSR and those consisting of either all-aluminum
or all-copper strands.

The program provide diagnostics tools. DYNAMP conducts checks on internal calculations
performed within the program and inconsistencies in input data. If the program encounters
unusual values for calculated quantities or for input variables, DYNAMP displays a series of
diagnostic messages.

Four calculation types are available:

1. The steady state calculation type involves a steady state model that calculates a single value
of the conductor temperature for constant weather and a constant line current. The program
calculates ampacity for a given value of conductor limiting temperature. This type of model
has been traditionally referred to as the House and Tuttle method.
2. The transient calculation type consists of a transient model for real-time conductor operation.
It calculates instantaneous conductor temperatures when the conductor experiences varying
current levels and weather.
3. The time predictive calculation type provides predictive temperature calculations based on
emergency situations that can arise from a sudden current overload on the line.
4. The current predictive calculation type predicts the allowable overload current that can be
sustained for a given time and not exceeding the limiting temperature.

FAD

This program performs foundation analysis and design (FAD). FAD combines the capabilities
of modules CUFAD+ (Compression/Uplift Foundation Analysis and Design) and MFAD
(Moment Foundation Analysis and Design) into one module to analyze and design drilled shafts
(drilled piers and caissons), spread foundations, and direct embedded poles for axial, lateral and
moment loading. CUFAD+ was developed at Cornell University, and MFAD was developed by
GAI Consultants, Inc. They were included in earlier versions of TLW as separate modules.

CUFAD+ is an interactive program for analyzing and designing drilled shaft or spread
foundations for electrical transmission line structures. The program accommodates uplift and
compression loadings under both drained and un-drained soil conditions. Engineers can analyze
foundations to obtain the capacity and overall factor of safety under a set of loads. CUFAD+ also

2-7
TLWORKSTATION

enables engineers to design foundations of given widths or diameters to obtain the minimum
depth required.

MFAD analyzes and designs foundations that are subject to high overturning moment loading.
The program can be used for drilled shaft foundations and for direct embedment poles. MFAD
uses a nonlinear four-spring load deflection model and an ultimate capacity model in the
geotechnical analysis and design of laterally loaded drilled shafts.

FAD in TLW version 3.0 features the following:

Reliability based design
Structural design of drilled shafts
Design of rock sockets

An overview of geotechnical engineering concepts and geotechnical terms used in foundation

design are provided in the module’s User Manual. The terms included are found in Appendix A
of this report:

MINIDES

This program provides the necessary tools for studying the preliminary design of transmission
structures including estimates of component sizes, total structure weight, and foundation loads.
MINIDES can perform design sensitivity studies and cost estimates and provide data for design
optimization codes.

Input to MINIDES consists of very few data items. The MINIDES module automatically reads
design loads generated by the module WIRELDS, a TLW loading tree program. The sizes and
weights determined by MINIDES are approximate, but they are determined in a consistent
fashion and based on simplifying assumptions for each type of structure. The sizes and weights
determined by MINIDES normally lie within 10 percent of corresponding values obtained by a
detailed design. While a detailed structural design may require substantial engineering and
computing time, an approximate design requires only a few seconds.

MINIDES can compute weight regression coefficients for the TLOPGR module, an optimization
program within TLW. To produce these coefficients, MINIDES generates variations of the base
design from which linear regression coefficients are calculated automatically. The general
concepts are based on:

Geometry - Once a structure type has been selected, its overall geometry is defined through the
specification of a few key geometric parameters. MINIDES uses these parameters to develop a
model of the structure. The internal model developed by MINIDES may not be as detailed as the
model required for the final design of the structure, but it is appropriate for estimating sizes,
weights, and foundation loads.

Material - Self-supporting or guyed lattice structures consist of hot-rolled steel angle members
assumed pin connected at joints. Single or multi-pole structures can be made of wood, steel, or

2-8
 TLWORKSTATION

pre-stressed concrete. Wood poles are restricted to Douglas Fir, Western Red Cedar, or Southern
Pine. All steel poles use 12-sided cross sections made of plate thickness in increments of 1/16
inch. Pre-stressed concrete poles have circular cross sections with a constant taper.

Design Loads - The load file contains design loads for the MINIDES structure. Before running
MINIDES, the load file is normally generated from WIRELDS, a loading tree program in TLW.

Design Assumptions - The basic components of all the structures in MINIDES are:
Steel angle members
Guy cables
Poles of various types
Various braces and cross arms

Steel Angle Members - All members of lattice types SLi and GLi are single hot-rolled angles that
are efficient in carrying compression over large unbraced lengths. Therefore, in the design of
lattice structures, only a subset of all commercially available rolled angles is considered.

Member Tension Capacity: The tension capacity of a member with cross section area A and
yield stress fy is assumed equal to 0.85 A fy. The factor of 0.85 is an approximation to account for
the presence of bolt holes.

Member Compression Capacity: The compression capacity of an angle member is affected by its
physical dimensions (actual length L, cross section area A, radii of gyration, rx, ry, and rz), by its
end connections and its bracing (from redundant members). The compression capacity is
calculated by the procedures described in ASCE Manual 52.

Procedures involve calculating a slenderness ratio, kL/r, where the value of k is critical. In
MINIDES, the value of k is either assumed or calculated from an assumed number of
intermediate bracing points that subdivide the length L. Assumptions are based on average
values found in actual designs for typical members.

Guy Cables - MINIDES designs guys so that they are not used at more than 70 percent of their
ultimate strength.

Poles - MINIDES designs all pole shafts to resist the combined effect of axial load and bending
moments. The effects of shear and torsion are neglected.

Wood Poles: Wood poles are selected from available ANSI classes such that the following
equation is satisfied at all points along the pole:

fa + fb • fall = Φ MOR

where

fa = normal stress due to axial load, P/A

2-9
TLWORKSTATION

fb = normal compression stress due to bending, Mc/I (M is resultant of both transverse

and longitudinal moments)

fall = allowable stress described as fraction of wood MOR

Φ = strength factor

MOR = modulus of rupture

In the equation above, the strength factor must be compatible with the load factors selected for
the loading tree. For the NESC "District" load case of the National Electrical Safety Code, it is
recommended that all load factors be specified as one and the strength factor be specified as
0.25. This combination is equivalent to using load factors of four together with a strength factor
of one, as suggested by the NESC requirement that P-effects are based only on un-factored loads.

For load cases other than the NESC District case, values of larger than 0.25, but not greater than
one, can be used. Therefore, when wood poles are used, two separate values of should be
specified, one for the NESC District case and another one for all the other cases (including the
NESC extreme wind case). All wood poles are assumed directly embedded into the ground
following ANSI recommendations.

Steel poles: Steel pole shafts are assumed to be 12-sided polygons. A single plate thickness is
used over 20-foot lengths. Minimum plate thickness is 3/16 inches, and all other thicknesses are
multiples of 1/16 inches. Overall design assumptions follow the recommendations of ASCE
Manual. The shaft is sized so that the following equation is satisfied at all points along the pole:

fa + fb • fall

where

fa = normal stress due to axial load, P/A

fb = normal compression stress due to bending, Mc/I (M is resultant of both transverse and
longitudinal moments)

fall = allowable stress described in ASCE Manual and is based on the wall slenderness, w/t

All steel pole shafts are supported on top of reinforced concrete piers. They use 2-inch thick base
plates and no. 18 reinforcing bars for anchor bolts. Steel pole arms are assumed to be fabricated
of cylindrical tubes with a diameter to thickness ratio D/t of close to 40. In addition to the shaft
weight, the weights of the arms, base plate, and anchor bolts are calculated by MINIDES.

Pre-stressed Concrete Poles: It is assumed in MINIDES that:

1. A constant taper and a predetermined variation of thickness exists throughout the length of
the pole
2. Pre-stressing strands can be terminated at specified locations along the pole.

2-10
 TLWORKSTATION

RNOISE

This program calculates the electromagnetic interference or radio noise in fair and foul weather
from high voltage transmission lines. RNOISE computes lateral profiles of the radio noise from
electric power lines in the 500 KHz to 1.5 MHz frequency range. The predictions are based on
work at Washington State University. An overview of electromagnetic interference and radio
noise predictions and guidelines for selecting parameters is included in the user’s manual.

RNOISE predicts levels of electromagnetic interference (radio noise) between high voltage
transmission lines in corona and a standard receiver located near the line. Using a CISPR
standard receiver, the output corresponds to radio noise in either average fair or average stable
foul weather. The noise is calculated by measuring with a vertical rod antenna (E Field) and a
horizontal loop antenna (H Field). This result is an equivalent electric field by multiplying by
377 ohms (impedance of free space). This also demonstrates how the H field is presented as an
equivalent electric field. The H field is measured by standard receivers equipped with loop
antennas. For each project, RNOISE can perform calculations for:
Electric field at the surface of each bundle
Generation functions
Propagations of radio noise currents
Radio noise fields

TLOPGR

This program is a transmission line design program specifically oriented toward the upgrading of
existing lines. The program provides an interactive, "spreadsheet-like" output screen that
displays both editable input parameters and output values. The impact of changes in the input
data is seen almost instantaneously. This approach gives immediate feedback to the user,
speeding up the design process considerably.

TLOPGR calculates minimum vertical clearances to ground and horizontal clearances to edge of
right-of-way for each span, and the wind and ice loading on each structure with a digital
description of the terrain and structures along it. The program allows the user to identify problem
spans and structures, as well as investigate the effect of moving, raising or adding structures, and
changing conductor tension, maximum conductor temperature, or reconductoring.

The effect of these changes in structure and conductor on clearances and structure loading are
immediately visible to the user. TLOPGR can also be used to edit an output file from TLW
module TLOPWT, allowing the user to alter the optimum structure locations and heights as
given by TLOPWT. TLOPWT, or Transmission Line Optimization Program with Terrain,
examines a transmission line as a system of interdependent environmental, structural, insulation,
and economic design factors to determine the most cost-effective design.

2-11
TLWORKSTATION

UPSTUDY

This program provides the tools for conducting an upgrade analysis. Using a limited amount of
input data to describe the existing line, UPSTUDY provides a quick and easy way to examine the
feasibility and cost for many upgrade alternatives.

UPSTUDY provides a rapid and approximate estimate of environmental, mechanical and

economic effects for upgrading techniques such as increasing line voltage, re-conductoring, or
operating the existing conductor at a higher maximum temperature.

UPSTUDY can display the output results on an interactive spreadsheet that allows the creation of
"What If" scenarios by modifying various input parameters. The impact of these changes is
displayed instantaneously. This approach gives immediate feedback, speeding up the design
process considerably.

For each upgrading option, UPSTUDY calculates environmental parameters (electric field,
magnetic field, audible noise, and radio noise); clearance at high temperature in a typical span,
and line loading limits (thermal rating, voltage drop, and surge impedance loading). Vertical
clearance, "blowout," and structure transverse loading are calculated for a typical span. The
present worth of electrical losses and construction changes are determined for each alternative.

WIRELDS

This program provides the tools for studying loading trees. WIRELDS generates loading trees
for all types of structures and handles design procedures from classical methods, such as the
National Electric Safety Code (NESC), to new Reliability-Based techniques.

WIRELDS can be used as a stand-alone program or with other TLWorkstation (TLW) task
modules such as MINIDES (Mini-Design Loads for Transmission Structures) and POLDAR
(Pole Design, Analysis and Reliability). Load data files generated by WIRELDS are stored in
the TLW database.

WIRELDS is a general loading tree program that can be used for all line geometry with any type
of insulator. The program combines features normally found in sag/tension programs with other
geometric design considerations. WIRELDS uses the following methods to determine loading
trees:
1. Actual Geometry - Determines the actual loading tree for an existing structure.
2. Wind-Weight Spans - Determines loads for a structure where wind and weight spans are
specified.

WIRELDS utilizes a single, common database that manages and shares data among
TLWorkstation applications. Design loads generated by WIRELDS are saved in the database
where other TLW modules can access this information. For example, MINIDES, a mini-design
program for transmission structures, estimates the weight of an actual structure that supports
loads calculated by WIRELDS.

2-12
TLWORKSTATION

2-13
3
IMPLEMENTATION PLAN

The objective of the Transmission Line Design Tools project is to lower overall capital and
O&M costs for overhead lines by providing latest tools and information to make informed
decisions on the design of overhead lines.

General

For this particular project that extends from 2005 to 2007, the scope involves the integration of
selected applets from the new edition of the Red book and the immediate steps to be taken in the
overall plan include the following:
Replace software modules in TLW with new modules using algorithm in the 2004 edition of the
Red Book
Preserve and enhance modules in TLW where TLW is a clear market leader
Ensure TLW can integrate with other selected transmission line packages
Consider linking TLW, Red Book software, EPRI's TFLASH software and, other EPRI software
and applets
Ensure that associated handbooks and reports are available to complement the software packages

The ultimate goal of the Transmission Line Design Tools project is to develop TLWorkstation to
be the depository of all transmission line design programs covering different disciplines of
engineering. A tentative list of existing or new programs for each discipline is as follows:

Design Studies
Preliminary designs (MINIDES)
Probabilistic-based designs

Electrical
General designs (Red Book Applets)
Lightning (TFLASH program)
Current Rating (DYNAMP)
Shared ROW (CORRIDOR, EMC Book, ROW Guide)

Mechanical
General designs (Orange Book)

3-1
Implementation PLan

EPRI Vibration software

Wind/Ice Loading

Civil
Structure (WIRELDS)
o Pole
o Tower
Foundation (FAD)
Line Layout (PLSCADD, TLCADD)

Line Upgrades
Voltage Upgrades (Blue Book)
Current Upgrade (TLOPGR, UPSTUDY, HTC Matrix)

Programs outside of TLWorkstation can be integrated into the software by interfacing third party
software with TLW. Update of existing programs in TLW will be required as new information is
developed. Other than the Red Book, the following EPRI books and documents are being
updated or prepared:
Transmission Line Reference Book: Wind-induced Conductor Motion (Orange Book)
Transmission Line Reference Book: 115-138 kV Compact Line Design (Blue Book)
Power System and Railroad Electromagnetic Compatibility Handbook
Guide for the Engineering the Multiple Use of the Right-of-Way

Information from the new version of these documents can be applied to the programs.

Integrating programs into the TLS software will face a number of challenges. Some of the major
challenges are:
Software used in existing programs is outdated
Mapping data from different sources could be difficult. Even though the Red Book Applets were
developed by the same developer, data format and names varied with time.
The focus of different program could be quite different and thus data mapping produces little
benefit

To overcome some of these challenges, the project solicited aggressively user input. Some of the
initial input was that less emphasis should be put on data mapping and more attention should be
put on user interface. As a result, only the most commonly used data such as conductor
information and structure configuration will be mapped. Mapping and integrating of database
will be done cost effectively without sacrificing the overall outcome of the integration. Further
details on the challenges encountered and to be overcome are provided in the sections below on
Current Applets – Development Environment and Current Applets – Other Issues. The software
integration is being undertaken by EPRI staff up to the end of 2006.

3-2
 Implementation PLan

Current Applets – Development Environment

Development of the current Red Book Applets began in 1996. At that time, developers of
Windows Java applications (both Windows applications and Applets that would run from web
pages) could use Microsoft Visual J++ Version 1.1 or a number of other Java development tools.
So, the developers of these Applets chose to use Microsoft Visual J++ Version 1.1.

Java is a language that was originally developed by Sun Microsystems. The syntax for Java is a
subset of the syntax for C++. Java restricts the latitude given C++ programmers in order to
prevent the occurrence of runtime errors that plague many C++ applications such as the dreaded
‘Access Violation’. Hence, it is a good choice for the production of applications that are easy to
maintain and generally free of intractable errors.

The original version of Sun Microsystems’ Java was version 1.0, which was matched by
Microsoft Visual J++ Version 1.0. Later, Sun developed version 1.1 and Microsoft matched it
with their Visual J++ Version 1.1. Sun performed a major redesign of Java between the two
versions. They redesigned the Event handling model; i.e., the syntax of the code that handles
things like moving the mouse or clicking a mouse button. They also standardized the syntax of
function calls to the various screen controls [Clearly, when version 1.0 was developed, Sun
allowed the different programmers to use their own naming conventions. As a result, different
controls often use different function names to perform, what is essentially, the same function.]

In 1998, Microsoft began distributing Microsoft Visual J++ Version 6.0. This was the successor
to Version 1.1. Microsoft ‘jumped’ their version numbering to 6.0 in order to synchronize
version numbers with their other software development tools.

In 2001, Sun Microsystems won a lawsuit against Microsoft which required that Microsoft stop
distributing their version of Java. So, Microsoft stopped their Java development and began
scaling back their support of Visual J++. As a result, Microsoft no longer supports their old Java
products.

The current Applets have, in the course of the review, been recompiled in Microsoft Visual J++
version 6.0. Many of the Applets required some minor modifications to make them recompile.
Additionally, the compiler complained about the use of the Java 1.0 Event Model and function
names. A number of the Applets were modified to comply with the newer standards. This
examination suggests that, going forward, these modifications could be made at a rate of 2 to 3
Applets per day.

However, since Microsoft no longer supports Visual J++, there is the larger issue of what
development platform to use going forward. There are two basic options: stick with Java and
choose one of the various Java development tools, or, migrate the code to Microsoft’s
replacement for Java within their arsenal of tools, J# (J-sharp).

Microsoft’s J# uses syntax similar to that of Java, but does not run on the Java VM platform; it
runs on Microsoft’s ‘.NET Framework’. In all likelihood, J# will diverge from Java as future
versions (of J#) are developed. So, taking this path would restrict future versions of the Applets
to running on Microsoft Windows machines.

3-3
Implementation PLan

Maintaining the Applets in a Java-compliant development platform would allow the flexibility of
running the Applets on any operating system that supports the Java VM.

Current Applets - Other Issues

The choice of writing the Applets as Applets and the extent of the period over which they were
written has resulted in other coding issues. Each Applet is made up of the main Java class that is
executed from the web page, and supporting classes that are called by that main Applet class.
All these classes must be contained within the directory or subdirectories of the main [Applet]
class. This has led to many versions of classes that perform the same function.

For instance, all of the Applets that deal with conductor bundles contain a java code module (and
resulting class) called ‘Bundle.java’. This code defines an object that encapsulates a list of
conductors and their configuration for each bundle under consideration. The first Applet in the
list is ‘AN1’ which calculates the audible noise caused by corona from transmission lines. It has
the first version of the Bundle object in the directory for the AN1 Applet. When AN4 (that
calculates the audible hum at twice the power frequency caused by corona) was coded,
‘Bundle.java’ (and other modules) was copied to that directory to be used to build that Applet.
During the development and debugging of these separate Applets, the code in each version of
‘Bundle.java’ was modified separately and has diverged.

Development Plan

The following procedure describes the approach for the integration of the applets into TLW.
1. Identify data that is common to multiple Applets.
a. Conductor Information
b. Bundle Configuration
2. Re-code objects to encapsulate all data and functionality relating to those objects.
a. For instance, some Applets require specification of conductor Sag while others do
not.
3. Redesign the dialogs currently used to maintain those objects to include all information
required for all the Applets, and to allow for more robust editing of the data.
a. The current Applets allow for add and delete, but not modify. So, if a user makes
a mistake when specifying a bundle, they have to delete the old bundle and enter
all the bundle data again.
4. Design a database, based on the tables in TLWorkstation, in which to store the data
required by the application.
a. For the current applets, this involves the ACDCLINE tables and Conductor
Lookup tables.
5. Build an Application framework to encapsulate the current Applets into one application.
a. This will be done in the new development platform.

3-4
 Implementation PLan

6. Convert the Applets to functions executed from within the new Application framework.
a. Converting Java Applets to run from within an application is trivial.
b. The Load/Save buttons will be changed to Load and Save the data through the
new dialogs from and to the database tables instead of disk.
c. All the Applets screen forms must be converted to the new development platform.

Activities in 2005

This project “Transmission Line Design Tools’ with three other projects forms Project Set 35C
“Overhead Transmission Design for Optimized Life Cycle”. The objective of this Project Set is
to provide clients with tools to make informed decisions when designing and constructing new
transmission lines or when upgrading existing transmission lines. Tools include research results,
techniques, equations, methodologies, guides and software. These tools will help clients achieve
the goals of producing reliable and safe design, enabling the selection of the lowest life cycle
cost, decreasing design times, reducing labor costs and lowering capital cost by at least 5% for
overhead transmission lines.

The other projects under this Project Set are:

Compaction of Overhead Lines
Engineering the Multiple Use of the Right-of-Way
Vibration Management of Overhead Transmission Lines

A task force, TF3, was formed for Project Set 35C in 2005. The purpose of the task force is to
review progress and direction of this group of projects and to ensure that each project achieves
its objective. Two task force meetings were held, one on March 21 - 22 in Palo Alto, CA and
one on November 3 - 4 in Charlotte, NC. In addition, two Webcasts were held on June 20 and
August 22. At these task force meetings and Webcasts, this project was reviewed and discussed.
Input was sought from the advisors. The implementation plan was heavily influenced by the
advisors.

The Portfolio provides the following description of tasks to be conducted in 2005:

Establish a strategy to update EPRI TLWorkstation
Develop a plan to integrate EPRI software such as applets from the new Red Book and, third
party software into TLWorkstation

The following summarizes the achievements for the year:

The architecture of the existing TLW software was reviewed in order to develop an architecture
that would minimize duplication of data entries and that would link different calculation
modules, applets and 3rd party software effectively.
The existing TLW was evaluated by volunteers for improvements.
The existing TLW was evaluated internally by EPRI staff for improvements.
The architecture of 50+ applets from the Red Book was examined.

3-5
Implementation PLan

Integrating the Red Book applets into the TLW began.

The deliverable for the year was a technical update on “Integration of Transmission Design
Tools & Software – 2005 Progress Report” published in November, 2005 under Product ID
1010238.

Activities in 2006

In 2006, suitable applets to be integrated into TLW were evaluated. The selection were
presented and discussed at the Overhead Transmission Design Task Force meetings in Dallas,
TX meeting on April 4-5 and in Atlanta, GA on September 18-19 as well as at the Webcasts on
July 11 and October 24. Input was sought and feedbacks from users were incorporated into the
integration. It was determined that certain Red Book applets will be used to replace the
ACDCLine and RNoise modules in TLWorkstation.
The primary objective of the integration is to create an application that will replace the
ACDCLine and RNoise modules in TLWorkstation as the first step in maintaining the viability
of EPRI’s TLWorkstation software.

Additional objectives are:

• Include updated algorithms, specifically 3-D calculations

• Improve Import, Export and Save As functionality
• Improve Data Input Forms, with graphical feedback
• Improve maintainability by using up-to-date development platforms
• Provide architecture that can be linked to other software packages.

The final list of selected applets is:

3-6
 Implementation PLan

Applet Description
AN-1 Audible Noise of Transmission Lines
AN-2 Audible Noise of Transmission Line (3-D)
AN-3 Bundle Geometry for Minimum Audible Noise
AN-4 Audible Noise, Hum
AN-6 Audible Noise vs. Rain Rate
CC-1 Conductor Surface Gradient (2-D)
CC-2 Conductor Surface Gradient (3-D)
CC-3 Surface Gradient on Toroidal Corona Shields
CC-4 Conductor Tables
CC-5 Transmission Line Parameters (Single Circuit)
CL-1 Transmission Line Corona Loss
CL-3 Ozone Concentration near Transmission Lines
EMF-2 Electric Field of Transmission Lines in 2-D
EMF-4 Electric Field of Transmission Lines in 3-D
EMF-5 Electric Field Shielding by Grids of Wires - 2D
EMF-6 Magnetic Field from Sets of Current Carrying Conductors (2-D)
EMF-7 Magnetic Field (3-D)
EMF-8 Magnetic Induction in Wires Parallel to Transmission Lines
EMF-9 Distant Magnetic Field Equations for Transmission Lines
EMF-10 Electric Field Induction on Objects
EMF-11 Magnetic Field Reduction Using Cancellation Loops (3-D)
EMF-12 Magnetic Field Reduction Using 4th-Wire Scheme
RN-1 Electromagnetic Interference up to 30 MHz
RN-2 EMI Calculation Using Empirical Methods
RN-4 Traditional Radio Noise Calculation Method
S-1 Switching Surge Flashover Model

The Applets that are not implemented consist of those calculations that are implemented
elsewhere, or are purely training modules.
After the selection, full integration was initiated. Project activities with a planned completion
date for 2006 was prepared last year and are shown in Table 3-1 on the next page. The Table
lists in detail the software development from the Concept Development to Test & Integration.
According to the original plan, Beta Testing of the new software would begin the end of this
year. Due to staff workload and departure of software staff from the Haslet Engineering Center
that was closed this September, the project is about 3 months behind schedule. For continuity,
development of the TLW software is being contracted to the former EPRI staff who worked on
the software. He will dedicate most of his time on this project to meet the 2007 completion date.

The integration has reached the Alpha testing stage the end of 2006. As part of software
approval process, appropriate documentation was prepared. A list of these documents can be
found in the next Chapter under Document for the Project.

3-7
Implementation PLan

Table 3-1
Project Activities Schedule for 2006

Key: X = primary responsibility; R = review; A = approval required

EPRI EPRI Software User Planned
Project Corporate Developer Completion
Manager Software
Quality

Step 1: Concept Development

Determine User Requirements X R Completed
Software Contract Package X RA Completed
Developer Qualifications Review RA RA X N/A - EPRI Staff
Step 2: Defining Requirements
Software Requirements Document & Review RA RA X R This Document
Functional Specification & Review RA RA X R This Document
Software Development Project Plan & RA RA X This Document
Review
Step 3: Design and Implementation
Identify data common to multiple Applets X 10/15/2005
Re-design objects to encapsulate X 11/1/2005
functionality
Re-design Dialogs to maintain data X 12/9/2005
Design database for data storage and retrieval X 12/16/2005
Design new Application Framework X 12/31/2005
Detailed Design Document RA RA X 12/31/2005
Create Test Cases RA R X 12/31/2005
Build new application prototype X 3/29/2006
Software Prototype & Review RA X R 3/31/2006
Implement Change Requests and Unit Tests X 6/30/2006
Step 4: Test & Integration
Alpha Test RA RA X 7/14/2006
Draft Documentation RA R X 7/14/2006
Beta Review by EPRI RA RA X 9/17/2006
Beta Test RA X R 12/31/2006
Implement Change Requests and Unit Tests X
Submit Final Software RA X
Step 5: Acceptance
Prescreen & Begin EPRI Acceptance Testing RA X
Complete Software & Documentation X
Software Release XRA
Step 6: Distribution & Maintenance
Set up Software Distribution X
Support & Maintenance Releases RA RA X

3-8
Work for 2007

After Alpha testing of the prototype software, it will be developed further for the Beta Test.
Additional documentation will be required and will be filed with the Software Evaluation Team
(SET) of EPRI prior to the Test. Volunteers will be sought for Beta Test evaluations. Often this
request is made at Task Force meetings and Webcasts. Additional improvements as requested by
the Beta testers will be implemented. The revised software is then submitted to SET testing.
Anomalies detected by the SET must be corrected before the software is approved for release.
This process is vigorous and could take a few iterations.

Along with the other projects in Project Set 35C, two task force meetings are scheduled for 2007
on March 27 - 28 in Palo Alto, CA and September 18 - 19 in Washington, DC. Webcasts will be
held on May 30 and November 6.

Integration of the listed applets will be completed by the end of 2007. The new modules will
have the most recent algorithms and data from the Red Book. In some cases, 3-D model is
available instead of the 2-D model in the existing module. Only one single input is required for
all these calculations instead of one for each applet.

In addition to the integration, the feasibility of interfacing TLW with transmission line layout
software packages such as PLSCADD and TLPRO will be explored. In consultation with Task
Force advisors, the direction of the TLW will be discussed and determined for future work.

Future Work

Many questions remain as to the full scope of the project beyond 2007. Upon completion of the
first phase of integration, future activities can be established. An immediate activity for 2008 is
to bring FAD 4.0, the upgraded version of FAD, into TLW. Another option is to improve and
update the TLW user interface. The ultimate goal is to develop TLWorkstation to be the
depository of all transmission line design programs covering different disciplines of engineering.

3-9
4
SOFTWARE APPROVAL PROCESS

EPRI software generally did not receive high marks from the users in the past. Quality was
inconsistent and problems were often encountered. Experience in using application software
developed by EPRI could be frustrating and unpleasant. On the other hand, lack of
documentation from software developers had made improvements of older software expensive
and extremely difficult.

In response to all these concerns, EPRI has in recent years established a software approval
process to assure that all software from EPRI is of high quality. The process not only
guarantees a certain standard for the software but also saves software development cost in the
long run. The procedure applies to both software developed internally by EPRI staff and that
developed externally by contractors. Thus, integration of the Red Book applets into TLW and
future modifications of TLW must be subjected to this process.

Before starting the development of the software, the qualifications of the software developer
along with a development & quality assurance plan must be submitted to EPRI for review and
approval. The software is then developed according to the pre-approved plan. When the
developer completes its software and prior to its release for Beta testing, the software must first
be reviewed by EPRI Software Evaluation Team (SET) to ensure no major problem will be
encountered and that the software can be installed properly. The software is then released to the
users. Upon completion of Beta-testing, feedbacks from Beta-testers are documented for
consideration of improvements by the software developer. Following the changes, the software
is put under vigorous testing conducted by the Software Evaluation Team. The software could
goes through a number of cycles of testing until all anomalies have been fixed.

There are two types of requirements for EPRI software:

Product Requirements
Development Process Requirements.

The following provides detail descriptions of these requirements.

Product Requirements for All EPRI Software

The requirements in this section apply to both new software and upgrades of existing software.
Additional requirements for new software appear in the following section.

4-1
Software Approval Process

Developers must validate and verify that the calculations and other operations performed by the
software yield correct results. EPRI Software Acceptance Testing concentrates upon ensuring
that the software is reliable and easy to use.

The items in this section are formally evaluated during Software Acceptance Testing. Acceptable
quality levels must be reached before an "A" is issued, approving software for distribution.
The EPRI Copyright, Ordering Information, and Disclaimer Notice elements for software appear
as required by EPRI legal staff.
The User Manual and any handouts for users that will accompany the software will be
distributed in electronic form, on the same CD with the software. The User Manual, in the form
of a Microsoft Word document, must be submitted for acceptance testing in a separate directory
on the CD (directly off the CD root directory) called Manuals. Any other documentation or
handouts for users must also be placed in the Manuals directory. Be sure to discuss any
exceptions with EPRI Corporate Software Quality.
Any media duplicated outside of EPRI must include the new Product ID number for the release
on the label. This number is obtained by the EPRI Project Manager from the Apollo system
Product Master.
Installation is straightforward
Graphical user interface (GUI) is easy to use. A GUI supported by the Microsoft Windows
operating system is required unless an exception has been approved by EPRI Software Quality.
User documentation and on-line help are complete and easy to use
Error messages must be clear and direct the user to a solution
System response time meets industry performance standards
Software coexists with other products on the platform
The user documentation must include solved example problems (also called test cases), with
active user input and interaction. The examples will show users how to use the main features of
the application, and will help them verify that the software is working correctly. A self-guiding
tutorial can be used to meet this requirement.
Outputs from solved example problems or tutorial must match user documentation when
specified inputs are entered
An uninstall procedure is present.
The opening screen of the software (also called the launch screen or "splash screen," seen each
time the program is used) prominently displays the EPRI copyright and EPRI wordmark.
Applications must support copying and pasting of relevant data to Microsoft Office applications.
The exact nature of copying and pasting required by each application is dependent on the
application's functionality and features. The goal is to enable users to easily manipulate data,
store the data back in the application, and create customized reports. Single text field copying
and pasting is not sufficient to meet this requirement. For tabular data, a standard tab- or comma-
delimited export function is also required to avoid dependence upon a specific release of Excel.

4-2
 Software Approval Process

Software must be designed for the Windows 32-bit platform (is coded using 32-bit internal
architecture, not 16-bit). Exceptions must be documented and approved by the EPRI software
quality manager.
A Windows-based (not DOS-based) graphical user interface (GUI) is required. New software
must implement a GUI using Windows GUI system calls. Software must support, at a minimum,
Microsoft Windows 2000 and XP platforms. Exceptions must be documented and approved by
the EPRI software quality manager.
Internationalization: End users for all software will be able to choose, by changing the regional
settings of their operating system, to the country of their choosing and the application will pick
up the proper units of measure, currencies, date formats, and number formats. If data has been
already entered into the application or stored in a file or database, then the users needs to be told
what will happen to the data already entered or stored.

The options are:

o Convert the data already entered to the new units or format. This would have to be
done by the application conversion program
o Use the original data and format type for data already entered or stored and the
new format for new data. The application program would have to make this
happen correctly
o The application program could clear the fields of the application where data was
already entered

The user manual should document the expected results and the user interface should provide
information or warning indicating what changes will occur when a user changes the regional
settings. Exceptions must be documented and approved by EPRI Corporate Software Quality in
the development plan.

Where numbers are used with scientific units the ability to use both US English and Metric (or
SI) units is required.

The specific units to be converted, and the types of conversions, will be determined for each
software project, based upon user requirements. There is no single definition to be followed.

Localization: Localization is generally the issue of providing the application in the local
language, or supporting multiple languages. It is optional, but useful, for international users to
have all GUI screen text information and error messages in a file that can be easily translated and
loaded into the program on initiation. Some special domain projects may have specific
Localization requirements defined in advance. For all applications the Localization plan will be
documented in the lifecycle plan and requirements documents.

Maintenance & Local Language Support: All messages, such as error messages and on-line help,
must be placed into a single table, file, or other central location. This will ease software
maintenance as well as the implementation of future local language support.

4-3
Software Approval Process

Security Policy

As a minimum, the following requirements will be met:

Security issues and security plan for the software will be covered and described in the planning
documents (e.g., Functional Specifications, Software Requirements Document, etc.) and in the
User Manual.
Software is free from viruses.
No passwords are viewable in plain text nor are passwords kept in an open-access file or
database in plain text. Plain text may be used in databases or files that can otherwise be secured
from general users.
There is no "backdoor" method to enter the software.
There are no "Trojan horses" or similar detrimental coding in the software.
Software is written in a manner that promotes the highest security state applicable for this
software.
Software uses Authentication and Access control as appropriate.
Software must offer ability to use Windows Authentication as well as proprietary Authentication
when both are available (i.e., using Windows Authentication and MS SQL Authentication).
Software is delivered in the maximum security state as stated in the design documents (e.g., the
documentation has warnings and clear directions to set up the security states; software that uses
passwords and administrative functions have them enabled).

4-4
 Software Approval Process

EPRI Software Development Process Requirements

Table 4.1 on the next page provides detail steps that a software developer must take in the
development of the software, starting from concept development, software design,
implementation, testing to distribution & maintenance. The functions and responsibility of each
party including the EPRI project manager, EPRI software quality team, the software developer as
well as the user at each step are clearly defined.

Both of EPRI’s product requirement and development process requirement combined to assure
only high quality software packages are produced. A copy of the Software Acceptance Form
forming part of the product requirement is shown in Table 4.2. The SAF provides some insight
into the stringent requirements demanded from all EPRI software.

Documents for the Project

As part of the software approval process, the following documents have been prepared for the
new TLWorkstation in order that it may be evaluated by users in the Alpha testing.

1. Software Acceptance Form

2. Software Life Cycle Management

3. Software Requirements

4. Functional Specifications

5. Software Quality Assurance Plan

Documents 3 and 4, which contain information relevant to the users, are attached with the report
under Appendix B and C respectively for references to the reader.

4-5
Software Approval Process

Table 4-1
EPRI Process Table and Planned Schedule
Software Name___________________________________ Version ____________ Date: _____________
(Up to 20 characters can be inserted in the right hand column of this table. The other parts of the table cannot be
modified.)
Key: X = primary responsibility; R = review; A = approval required
EPRI EPRI Software User Schedule (fill
Project Corporate Developer in your
Manager Software dates)
Quality
Step 1: Concept Development
Determine User Requirements X R
Software Contract Package X RA
Developer Qualifications Review RA RA X
Step 2: Defining Requirements
Software Requirements Document & Review RA RA X R
Functional Specification & Review RA RA X R
Software Development Project Plan & Review RA RA X
Step 3: Design
Software Prototype & Review (optional) RA X R
Detailed Design Document (optional) RA RA X
Step 4: Implementation
Project Plan Status Review(s) RA R X
Create Test Cases RA R X
Unit Tests X
Step 5: Test & Integration
Alpha Test RA RA X
Draft Documentation RA R X
Beta Review by EPRI RA RA X
Beta Test RA X R
Submit Final Software RA X
Step 6: Acceptance
Prescreen & Begin EPRI Acceptance Testing RA X
Complete Software & Documentation X
Software Release XRA
Step 7: Distribution & Maintenance
Set up Software Distribution X
Support & Maintenance Releases RA RA X

4-6
 Software Approval Process

Table 4-2
Software Acceptance Form (SAF):
Acceptance Testing, Publishing, and Distribution Web and PC Applications

Process Stage: Alpha Beta Prescreen Final Acceptance Test

INSTRUCTIONS: Submit this Word document as an email attachment. Software at all process stages
must be tested before being sent to the customer. The EPRI Project Manager completes Parts 1, 2, 3
and 5. The Software Developer completes Part 4.

Alpha, Beta and Prescreen: Complete Part 1. If some items do not apply, please enter “NA”. Be sure to
include contact information for EPRI Project Manager and Developer, and a Work Order Number.
Final Acceptance: Complete all sections. Missing information will delay software approval. If some items
do not apply, please enter “NA”.

4-7
Software Approval Process

Today’s Date: Work Order No.: EPRI Sector:

PART 1: GENERAL INFORMATION

A. Contact Information

EPRI Project Manager: Phone(s):

Administrative Assistant Name: Phone(s):

ESI Project Mgr. Name (if applicable):

ESI Work Order Number:

Developer:

Company Name: Phone(s): Fax:

Address: City: State: Zip:

Software Programmer
Phone(s): Email:
Contact:

Software Support: Please refer all support inquiries about this software to:

Developer Other - support contact information is:

Company Name: Phone(s): Fax:

Address: City: State: Zip:

4-8
 Software Approval Process

Support Contact: Phone(s): Email:

B. Product Information

Blue Chip: Yes No

Planned Completion Date
(PCD): If Yes: Corporate Sector
Business

Software Product ID #:

Note: Please work with your Apollo Product Master representative to obtain ID#.

Software Acronym:
Version or release number:

Full name of software:

Part of a multi-code group or workstation? No Yes, (Name)

Software Type: PC Software Other (describe)

Web Application - Who have you contacted in IT Apps

If not already submitted, please fill out and submit the Web application form
at: http://insideepri/epri%5Fcom/webapplicationchecklistform.htm

Is this software data only? No Yes, If Yes: Database

Spreadsheet

s this a: New Application Modification of Existing Application,

(Name) Other (describe)

4-9
Software Approval Process

For this modification or upgrade, a list of enhancements made is attached. Yes

No

PART 2: TECHNICAL BACKGROUND

A. Final Acceptance Testing Checklist

PC Applications and Web Applications:

User Documentation is included: (indicate type provided)

A User Guide or other accompanying documentation is provided in

electronic form

On-line help substitutes for a User Manual

Other types of User Documentation: (describe)

Hard copy of each user documentation item is included.

User guide and other accompanying documentation is provided in MS Word

format, using the EPRI Technical Publishing template, on the same CD with
software, in a separate directory off the root directory called Manuals

The User Documentation (User Guide or on-line help) contains solved example
problems or a tutorial showing users how to use the main features of the
application. These examples also help users to check that the software installed
properly and is working correctly.

Additional items submitted to testing: (describe):

Web Applications and Web Sites Only:

4-10
 Software Approval Process

URL for testing: This Web App has a User Manual Yes
No

PC Applications Only:

Specify media (preferred media is CD-Rom) that is provided for testing and how
many are provided.

Executable software application:

Source code

Security/Unlock Code (If required):

Software Life Cycle Management Document

http://www.epri.com/eprisoftware/processguide/swurr.html#LifeCycleManagement
Yes No If no, please explain:

B. System Requirements & Development Data

Ensure that these match the user documentation.

System requirements needed for standard, typical use:

Database requirements (Oracle, etc.): Third-party software required – note

release IDs:

Software key, password, or hardware key required? No Yes,

(describe)

Other installation dependencies, such as hardware or software the user must

install besides this software application:

Programming Third party What installation software

4-11
Software Approval Process

language(s) used: development tools was used? (InstallShield,

used: WISE, etc)

PC Applications Only:

Is this software designed to install on a server, with multiple users? Yes

No

If yes, can the software also be installed and used on a non-networked computer?
Yes No

C. Results of Beta Testing

At least 3 beta test users outside of EPRI are required, who exercise the software
utilizing their own data. Below are the summarized results of testing the software
functions, ease of use, installation instructions, and documentation. It is highly
recommended to name the beta testers (with their permission) in the
Acknowledgments section of the User Manual.

Is a copy of the beta test evaluation forms and test plan submitted? Yes
No If no, please explain:

Number of beta testers: planned: Number of beta test bugs reported:

Number of beta test bugs unresolved:

Number who provided feedback:

Number of unresolved bugs at each severity level: Critical Severe

Minor

Number of enhancements suggested during beta testing that were not incorporated
in this version:

4-12
 Software Approval Process

PART 3: PUBLISHING & DISTRIBUTION INFORMATION

A. Distribution

Note that the software is zipped with the user documentation and made
downloadable from epri.com when released for distribution. If you have user
groups where not all members are EPRI funders, establishing a Casper list will
enable them to download this software.

The software will be distributed by:

EPSC (EPSC distribution is expected) Other distributor (provide details):

Web site on epri.com (provide URL): Other web site (provide name
and URL)

Prior software products:

Remove previous release from distribution? Yes No

B. Software Description

Software will not be made active until the Project Manager has approved the
Product Description with Technical Publishing (Tech Pubs). Items 1-4 below are
required for the Software Description. View example Software Description at:
http://inside/marketingcr/marketing/TechnicalPublishing/docs/SoftwareDescription
Sample.pdf

1. A single sentence describing the overall technical capability that the

software provides (e.g. “The ABC software version xx enables users to
analyze…..”):

2. One paragraph (4 or 5 sentences) providing a summary description of the

software. Also note if customers will incur additional expenses to utilize the

4-13
Software Approval Process

software such as customization, training, purchasing a supporting program, user

group fees, license fees, etc:

3. Bullet points (2 or 3) highlighting the Benefits and Value provided by the

software:

4. Keywords (6 or less):

5. One screen shot showing key features of the software (optional) One way
to do this is to press ALT + PrintScreen; then select Edit>Paste to save a .BMP file
in Windows Paint.

Screen shot is attached: Yes No Please see complete

instructions at
http://inside.epri.com/marketingcr/marketing/templates.htm#techpubstemp

Additional Descriptive Information

Special additional actions needed by Customers to use the software (e.g. extra
license payments or fees required, joining user groups, installation services,
mandatory customization, training, unusual equipment):

Is software encryption (e.g., keys, database keys, data transfer, etc.) used or
required? Yes No

If yes, please provide specific information about the encryption: . If not

yet filled out, please complete the Encryption Document (link below) and submit
it to York Huang ("cc" your Software Quality Manager).
http://www.epri.com/eprisoftware/processguide/docs/Encryption.doc

Does this software support international/SI units of measure?

Yes No

If yes, please explain which units are used, and when conversions are available
(e.g. at start of program, at any time): .

4-14
 Software Approval Process

C. User Manual

An electronic copy of the user documentation will automatically be included on the

distribution CD-ROM.

Manual will ONLY be provided together with the software

If manual will be available separately from the software, please see the
following link:
http://inside/marketingcr/marketing/TechnicalPublishing/docs/pubform.doc

D. License & Copyright

For appropriate legal protection, EPRI's Intellectual Property staff has advised that
EPRI software needs to use Executable Licenses. EPRI members' Master
Agreements provide this license automatically. Other purchasers of EPRI software
will be contacted after an order is placed, so that they can sign the needed license.

Copyright alone is used when software is intended for free and universal public
use. (Please note that "shrinkwrap license" is no longer an option for EPRI
software, as it does not provide legal protection to EPRI.)

Encryption greater than 64 bit may require a special license which may take 90
days to process.

For legal advice, please contact EPRI’s Intellectual Property staff

Corporate Owner & License Category:

EPRI Copyright EPRI Executable

EPRIsolutions, Inc. Copyright EPRIsolutions, Inc. Executable

EPRIsolutions, Inc. Private A EPRIsolutions, Inc. Private B

4-15
Software Approval Process

Other: Describe any special licensing requirements (e.g. third-party software

restrictions):

Copyright Owner(s): EPRI (501) EPRI Solutions, Inc. (ESI)

Other (Legal Name):

E. Initial Distribution

The EPRI Project Manager will receive 1 copy of the product.

EPRI Project Manager wishes the software developer to receive a copy of the
final product.

PART 4. DEVELOPER’S REQUIREMENTS

A. Software Documentation

Copies of these documents have been submitted to the Software Engineering Team
(SET):

Software Development Project Plan

http://www.epri.com/eprisoftware/processguide/sdp.html

Yes No If no, please explain:

Software Requirements Document

http://www.epri.com/eprisoftware/processguide/srd.html

Yes No If no, please explain:

Functional Specification
http://www.epri.com/eprisoftware/processguide/funcspec.html

4-16
 Software Approval Process

Yes No If no, please explain:

Source Code Transmittal Letter

http://www.epri.com/eprisoftware/processguide/docs/exsctl.doc

Yes No If no, please explain:

Developer’s Quality Assurance Plan

http://www.epri.com/eprisoftware/processguide/csqap.html

Yes No If no, please explain:

If contract was executed BEFORE June 1, 2005, a Developer’s Submittal Report is

required, not a Certificate of Conformance.

Developer’s Submittal Report

http://www.epri.com/eprisoftware/processguide/docs/DSReport.doc

Yes No If no, please explain:

If contract was executed AFTER June 1, 2005, a Certificate of Conformance is

required, not a Developer’s Submittal Report.

Certificate of Conformance
http://www.epri.com/eprisoftware/processguide/swurr.html#ConformanceStatement

Yes No If no, please explain:

B. Developer’s Signature

By signing below, the developer certifies that the software meets all requirements
in the developer’s corporate quality plan, EPRI’s software development
requirements, security policies, requirements of the contract to develop the

4-17
Software Approval Process

software, and the developer’s submittal report.

Signature: ________________________ Date: _____________ _

Printed Name: _____________________________Title: ________________________

PART 5. AUTHORIZATIONS:

Release to Testing (Project Manager)

Signature (may be replaced by email message): _____________ Date:_________

Software Testing Approval for Distribution

This section for use by Software Testing

“A” Acceptance Release:

EPRI Software Quality Manager Authorized Signature: ___________Date:_________

Software ID for Distribution Master Media: SQA ID # ___________________

4-18
A
APPENDIX

Terms found in manual for FAD 3.0:

Adhesion Factor
Atterberg Limits
Backfill Density for Spread Foundation
Belled Shaft
Chemical Alteration of Soils
Clay Sample
Coefficient of Horizontal Soil Stress (Ko)
Coefficient of Permeability
Cohesion Intercept
Concrete Types
Cone Penetration Test (CPT)
Consistency of Cohesive Soils
Construction of Shaft
Deep Soft Silt
Density
Desiccation
Dilatometer Test (DMT)
Direct Embedment
Drained and Undrained Conditions
Drilled Shaft
Eccentricity
Effective Stress
Elastic Behavior of Soils
Erosion of Overlying Soil
Excavation
Fall Cone Test
Friction Angle
Friction Angle Laboratory Tests
Geologic History
H-Frame Structure
In-Situ Coefficient of Horizontal Stress (Ko)
In-Situ Test Methods
Interface Friction Angle
Large Boulders
Lattice Towers
Liquid Limit
Lowering or Raising of the Ground Water Table
Material Index (ID)

A-1
Appendix

Oedometer Test
Operative/In-Situ Coefficient of Horizontal Stress
Overconsolidation Ratio (OCR)
P-delta
Particle Size and Distribution
Pile Foundation
Plastic Limit
Plasticity Index
Pocket Penetrometer
Poisson's Ratio
Pressuremeter Test (PMT)
Relative Density of Cohesionless Soils
Rock
Sand Sample
Single Pole or Guyed Structure
Site Access
Soil Characteristic
Soil Types
Spread Foundation
Standard Penetration Test (SPT)
Stiff Crust
Substation Structure
Time-Dependent Deformability of Soils
Tip Suction Stress
Torvane
Triaxial Compression Test
Tube Sample
Unconfined Compression Test
Undrained Shear Strength
Unit Weight/Density
Vane Shear Test (VST)
Walls of Foundation Holes
Young's Modulus

A-2
B
SOFTWARE REQUIREMENTS

B-1
 Software Requirements
For
TL Workstation Design Tools

Prepared By: Ian C. Baskerville Date: 9/8/2006

Reviewed By: Date:

Approved By: Date:

B-3
Software Requirements TL Workstation Design Tools Rev. 0

Record of Revision

Date: Revision: Section: Description:

09/08/2006 00 All Original Release

B-4
Software Requirements TL Workstation Design Tools Rev. 0

Table of Contents

RECORD OF REVISION.......................................................................................................... B-4

TABLE OF CONTENTS ........................................................................................................... B-5

INTRODUCTION ..................................................................................................................... B-7

Purpose.................................................................................................................................. B-7
Background............................................................................................................................ B-7
Strategy ................................................................................................................................. B-7

BUSINESS REQUIREMENTS .................................................................................................. B-8

Current Tools ......................................................................................................................... B-8
Objectives .............................................................................................................................. B-9

FUNCTIONAL REQUIREMENTS ......................................................................................... B-10

Primary Requirements........................................................................................................... B-10
User Interface....................................................................................................................... B-10
Hardware Interfaces .............................................................................................................. B-11
Software Interfaces ............................................................................................................... B-11
Communications Interfaces.................................................................................................... B-11
Memory Constraints.............................................................................................................. B-11
Design Constraints................................................................................................................ B-12
Installation ........................................................................................................................... B-12
Assumptions......................................................................................................................... B-12

NON-FUNCTIONAL REQUIREMENTS ................................................................................ B-13

Performance Issues ............................................................................................................... B-13
Security ............................................................................................................................... B-13
Configuration, Compatibility and Usability ............................................................................. B-13

USER INTERFACE REQUIREMENTS .................................................................................. B-14

Sample Forms ...................................................................................................................... B-15
Data Source Connection Dialog......................................................................................... B-15
Application Main (MDI) Form .......................................................................................... B-16
Open Project Dialog ......................................................................................................... B-16

B-5
Software Requirements TL Workstation Design Tools Rev. 0

Child Form ...................................................................................................................... B-17

B-6
Software Requirements TL Workstation Design Tools Rev. 0

Introduction

Purpose

Integrate the Applets, from the third edition of the Transmission Line Reference Book – 200
kV and Above (the Red Book), into a desktop application. This application will replace the
ACDCLine and RNoise Applications that were part of the TLWorkstation version 3.0. It will
apply the updated algorithms used in the Applets, and update the User Interface to comply
with modern programming standards, using the latest software technology.

Background

Over the years, the Electric Power Research Institute (EPRI) has published a number of
world-renowned transmission line reference books and software, which are considered an
industry standard and are valued by many transmission companies and engineers. In addition,
EPRI issued the TLWorkstation (TLW) in the early 1990s, a comprehensive transmission
line design package that has a very strong set of users. In 2004, EPRI published the third
edition of the Transmission Line Reference Book – 200 kV and Above (the Red Book), along
with a suite of some 50 small software routines to help the reader employ the design theory
within the book. These software routines are targeted for the reader of the Red Book and
were not developed as an integrated design package. The software package in TLW contains
a number of design modules, many of which were based on the previous version of the Red
Book. With changes in the Red Book, it is necessary to review the present status of the TLW.

At the same time, new transmission line design packages have entered the market in recent
years. Consequently, a number of these tools, each with unique benefits could be integrated
into the TLW to form a more complete software package. For example, there are exceptional
commercial transmission line mechanical and 3-D graphical design packages. It would be
ideal to bring these design tools together, since the TLWorkstation is a leader in electrical
design, with a number of the existing modules in daily use by the global power delivery
industry. This combination would involve identifying the best of breed and then ensuring that
the best EPRI products work in an integrated fashion with the best commercial software.

Strategy

As a result of transmission expansion in some parts of the world such as South America,
South East Asia and Africa, and also the recent round of blackouts, it is clear that there is
renewed interest in building new transmission lines. The need to consider construction of
high voltage transmission lines is also captured in some of the recent US Government
Department of Energy documents. In the past there has been a slump in overhead line

B-7
Software Requirements TL Workstation Design Tools Rev. 0

construction. Consequently, skill levels within the industry have declined. Further, there are
very powerful CAD and line layout design software packages that are almost considered
industry standards that have not been interfaced with EPRI’s TLWorkstation. Combining
with the new edition of the Red Book, it is therefore crucial that TLW must be updated to
address all these changes and challenges.

The general strategies are as follows:

Identify one or more key line design packages, such as the PLSCAD and TLCADD, that
are very strong on the graphical and structural aspects of line designs
3. Develop a standard to move data between EPRI design modules and other design
software
4. Focus on enhancing EPRI modules, ensuring that they are very robust and reflect the
latest thinking
5. Look to market these modules as either stand alone or packages that can be loaded up
alongside the commercial software.

Business Requirements

Current Tools

Currently, there are a limited number of tools available to designers to analyze Electric,
Magnetic and Noise characteristics of existing and planned Transmission Lines. One of
those applications in general use is the ACDCLine and RNoise applications that are a part of
EPRI’s TLWorkstation version 3.0, released in 1997.

Unfortunately, these TLWorkstation modules have not been upgraded since their release.
Additionally, with regards their underlying architecture,
• They are written using Microsoft Visual C++ version 1.5, which was the last version
capable of creating 16-bit Windows applications that would execute under Windows
3.1.
• They use the WATCOM SQL database as the underlying database. This was a 16-bit
database, which has not been supported in over 5 years.
• It uses an old version of EasyPlot to display graphs of the analysis results. Many of
these graphs would only work if the application was executing under Windows 3.1.
While these modules still install and execute on current Windows 32-bit operating systems,
there is no promise that Microsoft will ensure that future Windows operating systems will be
backward compatible to the 16-bit realm. (In fact, I have been unable to install it under
Windows XP Professional 64-bit.)

The Red Book Applets were created as a companion to the Transmission Line Reference
Book – 200 kV and Above 3rd ed. Though the work well as a way to demonstrate individual
aspects of Transmission Lines, they are generally individual and independent modules:
• Each Applet saves and loads user entered data in their own individual and
inconsistent format.

B-8
Software Requirements TL Workstation Design Tools Rev. 0

• The data is stored in individual disk files, in arbitrary directories.

• The circuit configurations entered into one Applet has to be re-entered in another for
analysis in that Applet.
• The information entered cannot generally be edited. Any information entered
incorrectly, must be deleted and the corrected item re-entered.
As far as the underlying architecture is concerned, the Applets were written, starting in 1996,
with Microsoft Visual J++ version 1.1 (although the code conforms to the earlier Java
version 1.0 event and object model). Unfortunately, due to the age of that development
platform and the fact that Sun Microsystems won a lawsuit against Microsoft in 2000
ordering them to cease Java development and support by 2002; there is no support from
Microsoft for applications written in Visual J++. Also, there is no support from any other
Java development environments for conversion of Visual J++ code to other platforms. So, all
conversion of User Interface code written with Visual J++ must be done manually
(Completely Rewritten.).
What the Red Book Applets provide are the implementations of updated algorithms,
including support for field calculations in 3 dimensions.

Objectives

The primary objective of this project is to create an application that will replace the
ACDCLine and RNoise modules in TLWorkstation as the first step in maintaining the
viability of EPRI’s TLWorkstation software.

Additional objectives are:

• Include updated algorithms, specifically 3-D calculations;

• Improved Import, Export and SaveAs functionality;
• Improved Data Input Forms, with graphical feedback;
• Improved maintainability by using up-to-date development platforms;
• Provide architecture that can be linked to other software packages.

B-9
Software Requirements TL Workstation Design Tools Rev. 0

Functional Requirements

Primary Requirements

This program will replace the ACDCLine and RNoise modules in TLWorkstation by
implementing the following Red Book Applets:

Applet Description
AN-1 Audible Noise of Transmission Lines
AN-2 Audible Noise of Transmission Line (3-D)
AN-3 Bundle Geometry for Minimum Audible Noise
AN-4 Audible Noise, Hum
AN-6 Audible Noise vs. Rain Rate
CC-1 Conductor Surface Gradient (2-D)
CC-2 Conductor Surface Gradient (3-D)
CC-3 Surface Gradient on Toroidal Corona Shields
CC-4 Conductor Tables
CC-5 Transmission Line Parameters (Single Circuit)
CL-1 Transmission Line Corona Loss
CL-3 Ozone Concentration near Transmission Lines
EMF-2 Electric Field of Transmission Lines in 2-D
EMF-4 Electric Field of Transmission Lines in 3-D
EMF-5 Electric Field Shielding by Grids of Wires - 2D
EMF-6 Magnetic Field from Sets of Current Carrying Conductors (2-D)
EMF-7 Magnetic Field (3-D)
EMF-8 Magnetic Induction in Wires Parallel to Transmission Lines
EMF-9 Distant Magnetic Field Equations for Transmission Lines
EMF-10 Electric Field Induction on Objects
EMF-11 Magnetic Field Reduction Using Cancellation Loops (3-D)
EMF-12 Magnetic Field Reduction Using 4th-Wire Scheme
RN-1 Electromagnetic Interference up to 30 MHz
RN-2 EMI Calculation Using Empirical Methods
RN-4 Traditional Radio Noise Calculation Method
S-1 Switching Surge Flashover Model

The Applets that are not implemented consist of those calculations that are implemented
elsewhere, or are purely training modules.

User Interface

This application will be an MDI Application based on a Project/Detail data format. (The original
TLWorkstation modules were SDI applications based on the same Project/Detail underlying data format.)

Each Detail constitutes a unit of work that includes the information related to an example Right-of-Way or
Circuit configuration. Each open configuration is managed with one MDI Child window.

B-10
Software Requirements TL Workstation Design Tools Rev. 0

Multiple child windows can be opened at a time, so that the user can directly contrast and compare multiple line
configurations.

All analysis and reporting functions are accessed from the Menu of the MDI Parent window.
Analysis and Reporting functions should operate on the active Child form, all Child forms or the open project as
a whole.

The results are presented to the user in application dialog windows, or optionally exported as Microsoft Word or
Excel documents.

The results are presented as text and graphs, as well as 3-D, navigable models.

Hardware Interfaces

This software will be written in Microsoft C#, which runs under the Microsoft .NET Frameworks implemented
on Windows OS. New versions of Windows are distributed with the .NET Frameworks. The earliest Windows
OS version that will support the .NET Frameworks version 2.0 is Windows 2000 Service Pack 3.

Software Interfaces

This application will have the ability to export the results of calculations to Microsoft Word
or Excel documents if available.

Output forms will provide the Clipboard Copy functionality to allow for the copy and pasting
results into other applications.

Import and Export functions will be provided. These will ostensibly for transferring data
between different TLWorkstation databases. However, the data will be XML compliant so
that it can be viewed and/or processed using standard XML tools.

An Import function will be provided to import data from PLS-CADD.

Communications Interfaces

No direct internet communication methods to transfer data will be implemented.

Memory Constraints

The application will be tested to ensure it will execute reasonably well on 1GHz Windows
2000 systems with 256MB.

All graphical output will be optimized to use the minimum necessary memory.

Testing will include examination of the calculation limits. Some of the 3-D calculations,
based on the circuit configuration involved and the level of detail and precision requested by

B-11
Software Requirements TL Workstation Design Tools Rev. 0

the user can result in the use of very large matricies. These situations will have to be
examined in the test plan.

Design Constraints

No design constraints other than those described in the Hardware and Software configuration
sections.

Installation

Installation programs will be provided in the form of conventional Setup executable

(Setup.exe) and a Windows Installer (*.msi) module. The installation will include Microsoft
.NET Frameworks version 2 installer, in case it does not exist on the target system.

Assumptions

All prospective customers for this application will be using Windows 2000 or later.

B-12
Software Requirements TL Workstation Design Tools Rev. 0

Non-Functional Requirements

Performance Issues

Some of the 3-D Applet calculations may take some time to complete, depending on user
selected parameters for those calculations. The Test Plan will be designed to test the
performance of these calculations. Reasonable limits will be imposed by the system, based
on this testing. However, those limits will be generous. The help and documentation will
include discussion and guidance regarding the parameter selection, so that the user can be
prepared for the wait.

Security

The default data source, supplied with this application will not have security implemented.
Data Source Security will be assumed the responsibility of the Data Source, where a different
data source may be used.

Configuration, Compatibility and Usability

This application will comply with the latest Windows Design standards using .NET 2.0
Windows Forms. It will take advantage of the components provided as part of that platform
to ensure consistency with respect to other future Windows applications. Except for
graphical display output, all components will use the Windows System Colors determined by
the user selected Windows Theme to ensure consistency between this application and other
applications on the user’s desktop. And, as a result, no issues should be encountered where
the clarity and appearance of this application on the desktop would be inferior to that of other
applications. In the graphical display output, or where different colors and fonts (other than
default system values) may be used, the user will be provided the capability of changing
those colors or fonts.

B-13
Software Requirements TL Workstation Design Tools Rev. 0

User Interface Requirements

The user interface will be designed such that it could execute on systems with a minimum
monitor size of 1024 by 768, though it will be designed such that it can take advantage of
systems with larger monitors (or where the user would be willing to devote more screen
space to this application).

Most forms will be designed to use Windows System Colors for text and backgrounds in
order to ensure for maximum clarity and consistency. Exceptions will be noted.

Most text will be displayed with an 8.25 pt Tahoma Font. (Windows applications
traditionally used Microsoft Sans Serif Font; but the new standard is Tahoma, which better
distinguishes characters like a lowercase ‘L’ and an uppercase ‘I’).

The application will be an MDI Application based on a Project/Detail data format. Each Detail constitutes a
unit of work that includes the information related to an example Right-of-Way or Circuit configuration. On
entry, the user opens a project, and creates or selects individual configurations with which to work. Each open
configuration is managed with one MDI Child window. Multiple child windows can be opened at a time, but
only one at a time is the active window. All analysis and reporting functions are accessed from the Menu of the
MDI Parent window. Those functions generally only operate on the configuration maintained by the active child
window. However, additional menu options will be provided to allow the user to run analyses and reports on all
open details or the open project as a whole.

The results are presented to the user in application dialog windows, or optionally exported as Microsoft Word or
Excel documents, which will automatically be loaded as separate desktop windows (not under direct control
from this application). The results are presented as text and graphs, as well as 3-D, navigable models.

Except for results windows, which will be modeless forms; all forms will be modal forms.

All data entry for a given configuration will be accomplished through one MDI Child
window instead of a sequence of dialogs (as in the old TLWorkstation). The Child window
utilizes a Tabbed Page Control to divide the data entry into groups of related data. That is, all
Circuit/Bundle data will be entered on one tab (unlike the 3 dialogs in TLWorkstation 3.0).
Other objects that appear in the Right-Of-Way and/or interact with the Circuit configuration
are entered on another tab, etc.

All changes to the data will be stored in the application. The information will not be saved to
the database unless the user selects to do so. The user will be asked if any unsaved changes
are to be saved whenever the user closes a child form or the application.

Windows Forms provides better support than previous development platforms for reporting
errors. Generally, on data entry, the application will perform validation each time the user
leaves a field (or row in the case of Data Grids) and display an icon next to the erroneous
field. The user will be able to see the text of the error by clicking on the error icon. This
means that the user won’t have to keep clicking on OK buttons to close error dialog boxes. It
provides all the information needed by a novice to resolve the error, but, at the same time,

B-14
Software Requirements TL Workstation Design Tools Rev. 0

does not overly slow data entry for simple or obvious keying errors. (The experienced user
would be expected to figure out what is wrong with a given data field by just looking at it.)

Some validation will be done at the keystroke level where the application can detect a
keystroke error immediately. (E.g. numeric characters only in a numeric only field.)

Sample Forms

Data Source Connection Dialog

A database is installed with the application for desktop use. But, in general, the
application is designed to allow access to different sources of data. Some of those data
sources may require the user to log in with a userid and password. So, when the
application starts, and the currently configured data source (from the Registry) requires
a userid and password, the user is requested to either enter the userid and password, or
change to connect to a different data source.

B-15
Software Requirements TL Workstation Design Tools Rev. 0

Application Main (MDI Parent) Form

Open Project Dialog

B-16
Software Requirements TL Workstation Design Tools Rev. 0

Child Form

This is an example Child form showing the Primary tab the user would use to enter the Circuit, Bundle and
Conductor configuration.

B-17
Software Requirements TL Workstation Design Tools Rev. 0

B-18
C
FUNCTIONAL SPECIFICATIONS

C-1
 Functional Specifications
For
TL Workstation Design Tools

Prepared By: Ian C. Baskerville Date: 9/8/2006

Reviewed By: Date:

Approved By: Date:

C-3
Software Requirements TL Workstation Design Tools Rev. 0

Record of Revision

Date: Revision: Section: Description:

09/08/2006 00 All Original Release

C-4
Functional Specifications TL Workstation Design Tools Rev. 0

Table of Contents

RECORD OF REVISION.......................................................................................................... C-4

TABLE OF CONTENTS ........................................................................................................... C-5

INTRODUCTION ..................................................................................................................... C-9

Purpose.................................................................................................................................. C-9
Objectives .............................................................................................................................. C-9

ARCHITECTURE................................................................................................................... C-10
Overview ............................................................................................................................. C-10
User Interface....................................................................................................................... C-10
Data Source.......................................................................................................................... C-12

HIGH-LEVEL DESIGN .......................................................................................................... C-13

Entity Relationship Diagram .................................................................................................. C-13
Data Source Interface ............................................................................................................ C-14
Support Modules .................................................................................................................. C-14
Jama Module ................................................................................................................... C-15
AppletCommon Module ................................................................................................... C-15
Electric Circuit Components Module ................................................................................. C-15
OpenGL 3-D Model Display Modules................................................................................ C-15
Graphing Module ............................................................................................................. C-16
Individual Applets ................................................................................................................ C-16
AN-1 .............................................................................................................................. C-16
AN-2 .............................................................................................................................. C-16
AN-3 .............................................................................................................................. C-17
AN-4 .............................................................................................................................. C-17
AN-6 .............................................................................................................................. C-18
CC-1............................................................................................................................... C-18
CC-3............................................................................................................................... C-18
CC-4............................................................................................................................... C-19
CC-5............................................................................................................................... C-19
CL-1 ............................................................................................................................... C-19

C-5
Software Requirements TL Workstation Design Tools Rev. 0

CL-3 ............................................................................................................................... C-20

EMF-2 ............................................................................................................................ C-21
EMF-4 ............................................................................................................................ C-21
EMF-5 ............................................................................................................................ C-22
EMF-6 ............................................................................................................................ C-22
EMF-7 ............................................................................................................................ C-22
EMF-8 ............................................................................................................................ C-23
EMF-9 ............................................................................................................................ C-23
EMF-10 .......................................................................................................................... C-24
EMF-11 .......................................................................................................................... C-24
EMF-12 .......................................................................................................................... C-24
RN-1............................................................................................................................... C-24
RN-2............................................................................................................................... C-25
RN-4............................................................................................................................... C-25
S-1.................................................................................................................................. C-26
File Menu ............................................................................................................................ C-26
Segments Menu .................................................................................................................... C-26
Analysis Menu ..................................................................................................................... C-27
Reports Menu....................................................................................................................... C-28
View Menu .......................................................................................................................... C-28
Windows Menu .................................................................................................................... C-28
Help Menu ........................................................................................................................... C-28

LOW-LEVEL DESIGN ........................................................................................................... C-30

Data Diagrams...................................................................................................................... C-30
Project Header ................................................................................................................. C-30
Circuit Configuration........................................................................................................ C-31
Miscellaneous Right-Of-Way Objects ................................................................................ C-32
Support Modules .................................................................................................................. C-32
Jama Module ................................................................................................................... C-32
AppletCommon Module ................................................................................................... C-33
Electric Circuit Components Module ................................................................................. C-34
OpenGL 3-D Model Display Modules................................................................................ C-36
Graphing Module ............................................................................................................. C-36
Individual Applets’ Code....................................................................................................... C-37

C-6
Functional Specifications TL Workstation Design Tools Rev. 0

AN-1 .............................................................................................................................. C-37

AN-2 .............................................................................................................................. C-37
AN-3 .............................................................................................................................. C-37
AN-4 .............................................................................................................................. C-38
AN-6 .............................................................................................................................. C-38
CC-1............................................................................................................................... C-38
CC-4............................................................................................................................... C-38
CC-5............................................................................................................................... C-39
CL-1 ............................................................................................................................... C-39
CL-3 ............................................................................................................................... C-39
EMF-2/EMF-5................................................................................................................. C-40
EMF-4 ............................................................................................................................ C-40
EMF-6 ............................................................................................................................ C-40
EMF-7 ............................................................................................................................ C-40
EMF-8 ............................................................................................................................ C-40
EMF-9 ............................................................................................................................ C-40
EMF-10 .......................................................................................................................... C-40
EMF-11 .......................................................................................................................... C-41
EMF-12 .......................................................................................................................... C-41
RN-1............................................................................................................................... C-41
RN-2............................................................................................................................... C-41
RN-4............................................................................................................................... C-41
S-1.................................................................................................................................. C-41
Starting Application .............................................................................................................. C-41
Disclaimer Form .............................................................................................................. C-41
Data Source Connection Dialog......................................................................................... C-42
Application Main (MDI Parent) Form ................................................................................ C-43
Menu Functions.................................................................................................................... C-43
File Menu........................................................................................................................ C-43
Segments Menu ............................................................................................................... C-45
Analysis Menu................................................................................................................. C-47
Reports Menu .................................................................................................................. C-47
View Menu ..................................................................................................................... C-48
Help Menu ...................................................................................................................... C-49

C-7
Software Requirements TL Workstation Design Tools Rev. 0

Child Form........................................................................................................................... C-50

Circuit/Bundle/Conductor Configuration Tab ..................................................................... C-50
Miscellaneous Objects Tab ............................................................................................... C-51
Location/Profile Specifications Tab ................................................................................... C-52

C-8
Functional Specifications TL Workstation Design Tools Rev. 0

Introduction

Purpose

Integrate the Applets, from the third edition of the Transmission Line Reference Book – 200
kV and Above (the Red Book), into a desktop application. This application will replace the
ACDCLine and RNoise Applications that were part of the TLWorkstation version 3.0. It will
apply the updated algorithms used in the Applets, and update the User Interface to comply
with modern programming standards, using the latest software technology.

Objectives

The primary objective of this project is to create an application that will replace the
ACDCLine and RNoise modules in TLWorkstation as the first step in maintaining the
viability of EPRI’s TLWorkstation software.

Additional objectives are:

• Include updated algorithms, specifically 3-D calculations;

• Improved Import, Export and Save As functionality;
• Improved Data Input Forms, with graphical feedback;
• Improved maintainability by using up-to-date development platforms;
• Provide architecture that can be linked to other software packages.

C-9
Software Requirements TL Workstation Design Tools Rev. 0

Architecture

Overview

This program will replace the ACDCLine and RNoise modules in TLWorkstation by
implementing the following Red Book Applets:

Applet Description
AN-1 Audible Noise of Transmission Lines
AN-2 Audible Noise of Transmission Line (3-D)
AN-3 Bundle Geometry for Minimum Audible Noise
AN-4 Audible Noise, Hum
AN-6 Audible Noise vs. Rain Rate
CC-1 Conductor Surface Gradient (2-D)
CC-2 Conductor Surface Gradient (3-D)
CC-3 Surface Gradient on Toroidal Corona Shields
CC-4 Conductor Tables
CC-5 Transmission Line Parameters (Single Circuit)
CL-1 Transmission Line Corona Loss
CL-3 Ozone Concentration near Transmission Lines
EMF-2 Electric Field of Transmission Lines in 2-D
EMF-4 Electric Field of Transmission Lines in 3-D
EMF-5 Electric Field Shielding by Grids of Wires - 2D
EMF-6 Magnetic Field from Sets of Current Carrying Conductors (2-D)
EMF-7 Magnetic Field (3-D)
EMF-8 Magnetic Induction in Wires Parallel to Transmission Lines
EMF-9 Distant Magnetic Field Equations for Transmission Lines
EMF-10 Electric Field Induction on Objects
EMF-11 Magnetic Field Reduction Using Cancellation Loops (3-D)
EMF-12 Magnetic Field Reduction Using 4th-Wire Scheme
RN-1 Electromagnetic Interference up to 30 MHz
RN-2 EMI Calculation Using Empirical Methods
RN-4 Traditional Radio Noise Calculation Method
S-1 Switching Surge Flashover Model

User Interface

This application will be an MDI Application based on a Project/Detail data format.

One Project is open at a time.

Each Detail corresponds to one Right-Of-Way or Circuit configuration. And, each open configuration is
managed with one MDI Child window.

C-10
Functional Specifications TL Workstation Design Tools Rev. 0

Multiple child windows can be opened at a time, so that the user can directly contrast and compare multiple line
configurations.

All analysis and reporting functions are accessed from the Menu of the MDI Parent window.
Analysis and Reporting functions should operate on the active Child form, all Child forms or the open project as
a whole.

The Application Main Form (MDI Parent):

Since only one project is open at a time, the File menu options are used to access and manage projects.

The Segments menu (may be renamed) allow access to and management of individual Details. As such, the
options on that menu allow for the user to open and close Child forms.

The Analysis menu provides options allowing users to run selected analyses on the configuration specified in
the active Child form, all Child forms or all Segments in the open Project.

The Reports menu provides options allowing the user to specify how the output is to be displayed, or displays
the results of previously run analyses.

C-11
Software Requirements TL Workstation Design Tools Rev. 0

The View menu allows the user to configure how the data is displayed.

The Windows menu provides the options standard to the Windows menus in Windows applications.

The Help menu provides the options standard to the Help menus in Windows applications.

Data Source

The default database, supplied with the installation, is an Access database. It provides all information required
to execute all aspects of the application.

The required information can be broken down into two types:

• Right-Of-Way or Circuit Configuration, which consist of:
o Circuit/Bundle/Conductor Configuration,
o Right-Of-Way Objects
o Local Geography and Climate
• Reference data.
o Conductor Wire Types Parameters
o General calculation Parameters

The Right-Of-Way or Circuit Configuration information could be imported from some other source, such as
PLS-CADD.

C-12
Functional Specifications TL Workstation Design Tools Rev. 0

High-Level Design

Entity Relationship Diagram

A generalized Circuit entity relationship could be defined as follows:

Circuit Entity Diagram

TransmissionLine
ROW
-LineID

1 -LineID 0..1 -CiruitID

1 -ROW
Circuit
0..*
1

1..* -SegmentID
-CircuitID * -Segment
Segment 1
ROWSegment
-End1
-SegmentID

* 1
-RowSegmentID-End3 -End2
* -RowSegmentID
1
LineCircuitSegment ShieldingObjects
*

1 -LCSID

-End4
*
* * -StructureID
* -SpanID -SpanID
1 1 CoupledObjects
Span TLStructure
1 1
-SpanID -BOLStructure

-SpanID -AOLStructure
1 -SpanID 1 -StructureID

* -BundleID 1..* -InsulatorNo

Bundle -BundleNo -InsulatorNo Insulator

1 1..*

1 -BundleID

1..* -ConductorNo

Conductor

C-13
Software Requirements TL Workstation Design Tools Rev. 0

In this application, at this time, the Circuit entities represented consist only of: Span,
Circuit, Bundle, Conductor and Structure. The Span is referred to in the following as
‘Segment’. This may change, pending user review. All objects are treated as one group.

Data Source Interface

Project level interface Objects encapsulate the routines to load and save projects from and to the data source…

Segment Level interface Objects encapsulate the routines to load and save individual Segments (Cases) from and to
the data source…

IDisposable

Abstract Class

RedbookCaseDa… TLW30CaseData…
Class Class
BaseCaseDataModule BaseCaseDataModule

Note: there is no encapsulation of the PLS-CADD Segments because PLS-CADD information will only be imported
to the primary data source.

Support Modules

C-14
Functional Specifications TL Workstation Design Tools Rev. 0

Jama Module

This module contains the Jama calculation routines for matricies as used by the original Applets.
It has been enhanced to provide additional math objects and functions. These routines are used in this application to
simplify the appearance of the calculations, making them easier to validate for correctness. Additional structures and
classes have been added to support geometric calculations and 3-D results displays.

AppletCommon Module

This module contains all miscellaneous classes from the original Applets, plus new classes used by all integrated
Applets.

Most data entry fields in the application involve numeric data that have specific unit dimensions. These data fields
allow the user to enter unit text when entering these numbers in order to override the default units used in the
interface. For example, a given field may require a number with the units of Length and the display is in feet. In this
application, in such a field, if the user enters just a number, then it is assumed to be in the display units of feet.
However, this application allows the user to enter ‘6 in’; the application will automatically convert it to ‘0.5’ (ft).

Additional miscellaneous Enumerated Types, Exception Types have been added to this module to simplify the code
of all converted Applets.

Electric Circuit Components Module

The original Applets defined Circuit, Bundle and Conductor (named Cylinder) classes to encapsulate the data
pertaining to those individual real-world objects. With this integration, that data is properly encapsulated as
Properties. Also, the field names in these classes have been modified to be more descriptive, and to contain the units.
For example, the diameter of the conductor was named ‘dblD’. In this application, the field, as a property, has been
renamed to ‘DiameterInCm’, i.e. diameter in centimeters. This should greatly facilitate code validation during
testing. In addition, the conductor wire name and type are further refactored to encapsulate those parameters and
further simplify the code, eliminating duplication.

Various Applets used either 2-D or 3-D Electric field calculations. The class and naming of the corresponding
routines varied. All the calculation modules have been reconciled and refactored into two basic classes that will be
used by all Applets in the new application.

OpenGL 3-D Model Display Modules

Separate modules have been included, which interface .NET Managed Code to Windows native OpenGL dlls. These
include:
1. csgl.native, which is creates the dll that encapsulate the interface to the OpenGL.org Windows dlls:
opengl.dll. Glu.dll and glut.dll.
2. CsGL, which provide wrappers for all the basic OpenGL types; and,
3. CsGLBasecode, which provides high-level wrappers encapsulating a Windows Control, ‘View’, that
provides the display canvas control that appear on a Form; and one that encapsulates the displayed 3-D
objects ’Model’.

This application encapsulates extended functionality by extending the above wrappers in CsGLBasecode with
‘RedbookGLControl’ and ‘RedbookModel’ respectively. These controls are provided by the ‘RedbookGL’ module.

C-15
Software Requirements TL Workstation Design Tools Rev. 0

In addition, the routines for rendering Conductors and Miscellaneous Objects are encapsulated in another set of
classes. These are also included the ‘RedbookGL’ module.

Graphing Module

Displaying Graphs is accomplished with another tool called Zedgraph.

However, the components in Zedgraph are encapsulated in wrappers in the AppletCommon. This is done to
simplify the development of the graphs and to ensure consistency.

Individual Applets

AN-1

This applet calculates the audible noise caused by corona on high voltage transmission lines at different distances
from the line. The audible noise is calculated as the L50 value in rain, i.e. the value exceeded for 50% of the periods
during which there is measurable rain. The results are given for both the EPRI and the BPA calculation methods
described in the Reference Book. For most lines the two methods give similar results. The difference between the
two sets of values can be used to indicate variations that can be expected between different climates, or different
conductor surface conditions (aging). In addition to L50 rain, the L5 rain and the range of possible fair weather
values also are given. These are values obtained using the EPRI method. According to the BPA method the L5 rain
is obtained by adding 3.5 dB to the L50 rain and the L50 fair weather value is obtained by subtracting 25 dB from
the L50 rain value. The fair weather values calculated in this applet are the lower and the upper expected values of
the fair weather noise, which is very dependent on season, climate, and particles that may be present in the air.

The applet also calculates the generated acoustic power of individual bundles. This gives the user information on
which bundle is most responsible for the noise.

The applet calculates the noise for any type of bundles, including irregular bundles, i.e. bundles for which the
conductors are not placed on the vertices of a regular polygon.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

AN-2

This applet calculates the audible noise caused by corona on high voltage transmission lines at different distances
from the line. The problem is solved in 3-D. Conductive objects are simulated by sets of cylindrical segments above
a conductive flat ground plane.

This applet is ideal for conductors that have sags (such as transmission line conductors), are not parallel to each
other (transposition spans), or are at an angle with respect to each other (substation buses). This applet is also ideal
to find out the effect of the presence of lattice towers, steel poles, guy wires and other objects at ground potential
that may be well represented by sets of cylindrical segments (see Appendix 7.6 of the Reference Book)).

The audible noise is calculated as the L50 and L5 values in rain (i.e. the values exceeded for 50% and 5% of the
periods during which there is measurable rain) and the upper limit of expected fair weather values,. The noise is

C-16
Functional Specifications TL Workstation Design Tools Rev. 0

calculated using the EPRI calculation method. The applet divides the conductors into a large number of short
segments, calculates the surface gradient on each segment using a 3-D electric field program (Applet CC-2),
calculates the generated acoustic power for each segment, and finally the noise produced by all segments together at
each measuring point.

The applet calculates the noise for regular bundles, i.e. bundles for which the conductors are placed on the vertices
of a regular polygon.

The audible noise is calculated along a line specified by the user.

AN-3

This applet calculates the optimum bundle geometry corresponding to the minimum audible noise. Only three-phase
transmission lines are considered. The bundles of the three phases are all equal. For a given number of sub-
conductors, sub-conductor diameter, and bundle diameter, there is an optimum arrangement of the individual sub-
conductors on the bundle circumference that produces the lowest audible noise for well-aged conductors in rain. The
value calculated is the L50 value in rain, i.e. the value exceeded for 50% of the periods during which there is a
measurable rain. The calculations are based on the EPRI method to calculate the L50 Rain value and on the method
for bundle geometry optimization described in Section 10.7.2 of the Red Book. The experimental data needed to
execute the calculations are those described in (Comber and Zaffanella 1973). The curves in that paper were
digitized for use by this applet. The optimum bundle geometry is given for different bundle diameters. There is a
bundle diameter and an optimum sub-conductor arrangement for which the audible noise reaches an absolute
minimum. The applet calculates the audible noise value (at 15 meters from the outer phase and 1.5-m height) for
regular and optimum bundles and calculates the sub-conductor location for the optimum bundles.

AN-4

This applet calculates the audible hum at twice the power frequency caused by corona on high voltage transmission
lines at different distances from the line. The hum is a mixture of pure tones, the most significant of which occurs at
twice the power frequency. The algorithms for the calculations are described in Chapter 10 of the Reference Book.
The hum is calculated as the L50 and the L5 values in rain, i.e. the values exceeded for 50% and 5%, respectively, of
the periods during which there is measurable rain. The rain intensity selected for the L50 value is 0.75 mm/h and the
rain intensity selected for the L5 value is 6.5 mm/h. The hum in fair weather is negligible and is not calculated. The
hum is calculated for an altitude of 100 m or less above sea level. There is no experimental or other research data to
support estimates of the effect of altitude.

The applet calculates also the generated acoustic hum power of individual bundles. This gives the user information
on which bundle is most responsible for the hum.

The applet calculates the hum only for single conductors and regular bundles, i.e. bundles for which the conductors
are placed on the vertices of a regular polygon. There is no experimental or other research data to support estimates
of the effect of bundle irregularities.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

The hum is calculated at different lateral distances from the center of the line (lateral profile) at a constant height
above ground that can be set by the user (default value is 1.5 m).

C-17
Software Requirements TL Workstation Design Tools Rev. 0

AN-6

This applet calculates the audible noise caused by corona on high voltage transmission lines at a specified distance
from the line and the noise caused by the rain itself for different rain rates. The calculation of audible noise due to
corona versus rain rate is based on the algorithms in Section 10.4.6 of the Reference Book. The calculation of the
noise of rain is based on the algorithms in Appendix 10.2.

The applet is useful to determine at which distance from the line and at which rain intensity the noise of rain may
mask the noise of the line.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

The audible noise is calculated at a height of 1.5 m above ground. The altitude must be between 0 and 300 m.

CC-1

This applet calculates the electric field at the surface of conductors (conductor surface gradient) of high voltage
transmission lines. The problem is solved in two dimensions, i.e. the conductors are considered straight, infinitely
long, and parallel to each other and to the flat surface of a conductive earth. If the conductors are catenaries, the
height of the conductors above ground should be specified as the average height above ground. It is recommended to
use the minimum height plus one third of the sag. The user may input data regarding single conductors, or bundles,
or three-phase circuits, or any combination of these elements. When three-phase transmission circuits are
considered, their voltages are assumed symmetric—i.e. the three phase-to-ground voltages are equal in magnitude
and their phase angles differ by 120º. The applet can be applied to any number of circuits in a transmission-line
corridor.

For each conductor the average surface gradient and the maximum surface gradients are calculated. In the case of a
bundle of conductors, the maximum surface gradient is defined as the average of the maximum surface gradients of
the individual conductors.
The applet calculates also the surface gradient at any point on the surface of a specified conductor.

The applet calculates the surface gradient for any type of bundles, including irregular bundles, i.e. bundles for which
the conductors are not placed on the vertices of a regular polygon.

The electric field is calculated only on the surface of the conductors. Calculations do not apply to the electric field
away from the conductor surface. To calculate the electric field or the space potential away from the conductor
surfaces, use Applet EMF-2.

The 2-D Surface Gradient calculation from this Applet will be reconciled with the Surface Gradient calculations in
the other Applets, and refactored into a common module.

CC-3

This applet calculates the highest electric field on the surface (maximum surface gradient) of toroids. Toroids are
often used to terminate the high voltage conductors toward a dead end structure or near the line end of insulator
strings to reduce the voltage gradient along the insulators. If the dimensions or the position of the toroid are not
appropriate, the electric field may reach unacceptably high values and create a strong corona source. The problem of
calculating the surface gradient is solved in 3-D. All conductive objects present (conductors, bundles, tower
elements, objects at ground potential) are simulated by sets of cylindrical segments above a conductive flat ground
plane. Each toroid is also simulated with a set of cylinders. The number of cylinders in which a toroid is divided is

C-18
Functional Specifications TL Workstation Design Tools Rev. 0

108, which provides a very good simulation. The other conductive objects that can be simulated include single or
bundled conductors either straight segments or catenaries and flat plates. The user can build other objects and store
them for future use.

The maximum surface gradient is calculated only on toroids. A maximum of two toroids is allowed. There is no
limitation on other objects. However, if the number of cylindrical segments simulating the conductive objects
(excluding the toroids) exceeds 100, the computation time may be very long.

CC-4

This applet may be used for the following purposes;

1. Given the name of a conductor, list its properties and show the drawing of its cross-section.
2. Select a conductor with a desired property and look up its other parameters. For instance, the user may
want a list of conductors ordered by outside diameter, or by resistance, or by strength and choose a
conductor from that list. After selecting the conductor the user may see the list of its parameters.
3. The user may calculate quantities that are not normally found in a conductor table, such as the resistance at
different temperatures and/or different frequencies.
All units are both in metric and British units. The applet incorporates tables of common North American Aluminum
Conductors Steel Reinforced (ACSR), common British ACSR, ACSR/TW (the aluminum strands are trapezoidal),
ACSR-IEC, Single-Layer High-Strength Aluminum Conductors Steel Reinforced (ACSR-EHS), Aluminum
Conductors Steel Supported (ACSS), All-Aluminum Conductors (ACC), All-Aluminum-Alloy Conductors
(AAAC), Aluminum Conductors Alloy Reinforced (ACAR), Aluminum-Clad Steel Conductors (ALUMOWELD),
High-Strength Utility-Grade Steel Conductors (HS), and Extra-High-Strength Utility-Grade Steel Conductors (EHS)
(see Chapter 2).

CC-5

This applet calculates:

• the series impedance matrix, either full or after ground wire reduction,
• the shunt admittance matrix,
• the sequence impedance matrix,
• The surge impedance and the surge impedance loading,
• The series voltage drop, and
• The capacitive currents.

This applet provides also a tool to pass from phase to sequence quantities and vice versa.
The algorithms presented in the Reference Book are used and expanded in this applet.

The calculations are performed for a single 3-phase circuit with 0, 1, or 3 ground wires. The frequency can have any
value from power frequency to 100 kHz. The user can input the resistance and the GMR of a conductor directly or
input known characteristics of the conductor and let the applet calculate resistance and GMR.

The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the conductors
form catenaries, the height of the conductors above ground should be taken as the minimum height plus one third of
the sag.

CL-1

C-19
Software Requirements TL Workstation Design Tools Rev. 0

This applet calculates, for a given transmission line, corona losses under fair weather and under heavy rain. The loss
is calculated for each phase and for the entire line. The values are in W/m. The applet also calculates the mean
annual and maximum corona loss of the line. Accuracy of empirical formulas for corona effects is generally
evaluated by comparing them with good measured data obtained on operating high voltage transmission lines.
Unlike electromagnetic interference and audible noise, however, sufficient measured data are not available for
corona losses from operating lines and, therefore, it is not possible to make a realistic evaluation of the accuracy of
corona loss empirical formulas. Different results are obtained using calculation methods developed by different
researchers. The difference may be caused by different surface conditions of the conductors tested (particularly the
degree of aging), different climates, different rain rates, measurement errors, and approximation in deriving
empirical equations. Calculation results are given for different methods. By comparing the different results the user
may gather an appreciation for the variability of the phenomenon and the reliability of the data. The methods are
described in Chapter 11 of the Third Edition of EPRI’s Red Book, i.e.:
1. Fair weather loss according to Peterson’s equation, which is applicable only for single conductors.
2. Fair weather loss according to Gary and Moreau (EdF). This method is applicable to any regular
bundle and gives a range of possible fair weather losses.
3. Fair weather loss according to a BPA formula.
4. Heavy rain loss according to a BPA formula.
5. Heavy rain loss according to a method developed by Trinh and Maruvada (IREQ).
6. Heavy rain loss according to Clade’ and Gary (EdF).
7. Heavy rain loss according to Comber and Zaffanella (EPRI Red Book, second edition)
8. Heavy rain loss according to Project EHV (GE). This method is applicable for bundles with voltage to
ground between 220kV and 470 kV.

Each of this method is described in the Red Book. Essentially, all methods start with the calculation of the electric
field at the surface of the conductors of each phase. The problem is solved in 2-D, i.e. the conductors are considered
straight, infinitely long, and parallel to each other and to the flat surface of a conductive earth. If the conductors are
catenaries, the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.
For each bundle (or single conductor if there is only one conductor per phase) the average surface gradient and the
maximum surface gradients are calculated. In the case of a bundle of conductors, the maximum surface gradient is
defined as the average of the maximum surface gradients of the individual conductors. Each method uses
empirically derived equations giving the corona loss as a function of some of the following variables: sub-conductor
diameter, number of sub-conductors, bundle diameter, rain rate, frequency, and altitude. When a method did not
formalize the dependence of corona loss on some of these variables, the best available algorithm derived from other
methods was used. For example, for all methods the dependence of corona loss, P (W/m), on frequency, f (Hz), and
altitude above sea level, A (m), was determined using equation:
f
P = P0 ⋅ ⋅ 10( A / 300 ) / 10
f0 ,
where P0 is the loss at the frequency f0 and at the altitude A=0.

CL-3

This applet calculates the incremental concentration of ozone caused by corona on high voltage transmission lines at
different distances from the line. The amount of ozone is expressed in ppb (parts per billion in terms of weight
relative to air; 1 ppb = 1.23 μg/m3). The algorithms for the calculations are described in Chapter 11 of the Reference
Book. Ozone concentration is calculated for fair weather and for rain. In both cases the most conservative estimates
are made. In the case of fair weather, the worst fair weather conditions conducive to corona are assumed. In the case
of rain an intensity of 10 mm/h (heavy rain) is assumed.

The generation of ozone is expressed in μg/(m·s). The generation is based on corona loss. For corona loss
calculations in fair weather the upper bound values obtained using the EdF method are used. For corona loss
calculation in heavy rain the EPRI method, which is generally the most conservative, is used. Corona loss is
calculated accounting for frequency and for altitude above sea level. Other than their effect on corona loss, these two
variables are assumed not to affect ozone concentration.

C-20
Functional Specifications TL Workstation Design Tools Rev. 0

If the user prefers to calculate the corona loss using other methods, calculations should be made separately (for
instance using Applet CL-1) and the user should choose the option of entering the corona loss values for each bundle
directly.

The following assumptions are made:

1. Ozone generation rate in fair weather: 0.5 g/kWh (grams of ozone per kWh of corona loss)
2. Ozone generation rate in rain: 4.5 g/kWh
3. Time to half value in fair weather: 1 hour
4. Time to half value in rain: 5 minutes.
5. Spreading coefficients for both stable and unstable winds are those given in Chapter 11 of the Reference
Book.

The applet calculates the lateral profile of ozone concentration and also the ozone generated by individual phases.
The user must specify the interval of distances from the line, the number of segments in which this interval is
divided, and the height above ground at which ozone concentration is measured. The user must also specify wind
speed and direction (parallel or perpendicular to the line), and wind type (stable or unstable).

In the case of wind parallel to the line, the contributions from 500 2-m sections of line are added (total line length is
1000 m).

The applet calculates corona loss (and from it ozone concentration) for single conductors or regular bundles, i.e.
bundles for which the conductors are placed on the vertices of a regular polygon. There is no experimental or other
research data to support estimates of the effect of bundle irregularities.

The conductors are treated as if they were infinitely long and parallel to a flat earth. If the conductors are catenaries,
the height of the conductors above ground should be specified as the average height above ground. It is
recommended to use the minimum height plus one third of the sag.

EMF-2

This applet calculates the electric field and the space potential at power frequency at any point at the ground or in
space caused by high-voltage transmission lines or by any set of conductors to which a known voltage may be
applied. The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. If the
conductors form catenaries, the sag is neglected, and the height of the conductors above ground should be that at the
location where the field is calculated. When three-phase transmission circuits are considered, their voltages are
assumed symmetric—i.e., the three phase-to-ground voltages are equal in magnitude and their phase angles differ by
120º. The applet can be applied to any number of circuits in a transmission-line corridor.

The electric field and the space potential are calculated along a specified line. The space potential may also be
calculated on a vertical plane orthogonal to the conductors, and the space potential contour lines may be provided.
Calculations, however, do not apply to the field on the conductor surface (surface gradient) or in the immediate
vicinity of conductors.

EMF-5 is really the same as EMF-2, with the addition of miscellaneous objects in the field.

EMF-4

This applet calculates the electric field and the potential in space caused by high-voltage transmission lines or any
set of conductors to which a voltage may be applied. Conductive objects are simulated by sets of cylindrical
segments above a conductive flat ground plane.
This applet is ideal for conductors that have sags (such as transmission-line conductors), are not parallel to each
other (transposition spans), or are at an angle with respect to each other (substation buses). This applet is also ideal
to find out the effect of the presence of lattice towers, steel poles, guy wires and other objects at ground potential

C-21
Software Requirements TL Workstation Design Tools Rev. 0

that may be well represented by sets of cylindrical segments. The algorithms on which this applet is based are
described in Appendix 7.6 of Chapter 7 of the Reference Book.
The electric field and space potential can be calculated along a specified line and displayed in both tabular and
graphical formats. The electric field and space potential may also be calculated individually on a designated plane
orthogonal to the conductors (X-Y, X-Z, or Y-Z planes), and contour line maps can be constructed.

EMF-5

This applet calculates the electric field and space potential caused by high-voltage transmission lines (or any set of
conductors to which a voltage may be applied) in the presence of a grid of grounded wires that act as a shield. Both
energized and grounded conductors are treated as if they were infinitely long and parallel to a flat conductive earth.
If the conductors form catenaries, the height of the conductors above ground should be specified at the location
where the field is calculated. Conductor sag is not considered in this calculation. Grounded conductor shielding
grids are defined by location and density, and can be either horizontal or vertical grids.

The electric field and space potential can be calculated along a specified line, creating a lateral profile plot. Space
potential can also be calculated within a rectangular calculation grid in a vertical plane orthogonal to the conductors,
with space potential contour lines provided.

EMF-6

This applet calculates the magnetic field at power frequency at any point caused by high-voltage transmission lines
or by any set of conductors in which known currents flow. The conductors are treated as if they were infinitely long
and parallel to a flat nonmagnetic, nonconductive earth. For the calculation of magnetic field, the current is assumed
to be concentrated at the center of each conductor (or conductor bundle). The image currents in the earth are
neglected, which is a good approximation for calculation of power frequency magnetic field in proximity to power
lines. If the conductors form catenaries, the sag is neglected, and the height of the conductors above ground should
be that at the location where the field is calculated. When conductor bundles are considered, they are treated as
single conductors with the current concentrated at the center of the bundle. When three-phase transmission circuits
are considered, the data for each phase must be entered one at a time. If the transmission line has shield wires for
lightning protection, their current must be calculated before exercising this applet. Shield wire currents or currents in
any other grounded wires may be calculated using Applet EMF-8.

The magnetic field is calculated at points along a specified line or at points of a grid in a vertical plane orthogonal to
the conductors, in which case magnetic field contour lines are provided. Calculations, however, do not apply to the
field on the conductor surface. If the field in the immediate vicinity of a bundle is desired, the data for each sub-
conductor must be entered separately. If the bundle is asymmetric, the current subdivision among the sub-conductors
may be calculated using Applet CC-1.

EMF-7

This applet calculates the magnetic field at power frequency at any desired point in space produced by conductors
that can be simulated by sets of segments of known starting and ending points and that carry known currents. In
addition to conductor segments, the user can enter catenaries just by defining attachment points, sag, and number of
segments. This applet is ideal for conductors that have sags (transmission-line conductors), are not parallel to each
other (transformation spans), and are at an angle with each other (substation buses). This applet is also ideal for any
three-dimensional arrangement of conductors. The earth is assumed nonconductive and, therefore, the image
currents in the earth are neglected, which is a good approximation for calculation of power frequency magnetic field
in proximity to power lines. No conductive (other than the specified conductor segments, catenaries, buses, or coils)
or magnetic objects that may modify the magnetic field are assumed to be present.

C-22
Functional Specifications TL Workstation Design Tools Rev. 0

The magnetic field and space potential can be calculated along a specified line and displayed in both tabular and
graphical formats. The magnetic field may also be calculated on a designated plane orthogonal to the conductors (X-
Y, X-Z, or Y-Z planes), and contour line maps can be constructed.

EMF-8

This applet calculates:

• Currents induced in the shield wires when the shield wires are grounded at every tower. The
calculations assume that the line is infinitely long in both directions from the point of calculations and that
the ground resistance is the same for all towers. In these conditions the current flowing from shield wires to
ground at each tower is zero.
• Voltages induced between the end of a shield wire section and a tower when the shield wires are
sectionalized to avoid current flow. The wires are grounded at one tower and insulated from all the other
towers to which the shield wire section is attached. A voltage will exist at the end of the shield wire section
between each shield wire and the tower.
• Currents induced in shield wires that are grounded at every other tower and isolated and transposed at
intermediate towers. A voltage will exist between ground wires ant tower at the transposition tower. The
calculations assume that the line is infinitely long in both directions from the point of calculations and that
the ground resistance is the same for all towers. In these conditions the current flowing from shield wires to
ground at each tower is zero.
• Voltage induced between ground and the end of a wire strung in the general direction of the
transmission line and grounded at the other end.

The user must choose which of the above calculations are desired. Calculations are made for the power frequency
(50 Hz or 60 Hz). Calculations can be made for any type of line (one or more circuits) in the transmission corridor.
Calculations assume all the conductors parallel to each other and to a conductive earth. The earth resistivity must be
specified.

EMF-9

This applet calculates the magnitude of the basic elements to which a set of current carrying conductors can be
reduced for the purpose of assessing the magnetic field produced. Appendix 2 of Chapter 7 of the Reference Book
discusses definitions, properties, and methods of calculations of the basic elements: monopole, dipole, and
quadrupole. The field produced by each of the basic elements has a different law of decays. For instance a monopole
produces a magnetic field inversely proportional to the distance, equal to BM = 2M/R, where BM is the magnetic field
(mG), M is the magnitude of the monopole (A), and R is the distance from the center of the set of wires to the
measuring point (m). A dipole produces a field that decays much faster, being inversely proportional to the square of
the distance. The dipole field is BD = 2D/R2, where D is the magnitude of the dipole (A·m). A quadrupole field
decays even faster, the field being equal to BQ = 4Q/R3, where Q is the magnitude of the quadrupole (A·m2). These
calculations are useful to determine which basic element has the largest effect at a given distance from the line, so
that an appropriate field reduction method may be applied. Calculations can be made for any set of parallel current-
carrying conductors with a known current (magnitude and phase angle) and location in space.

The total magnetic field produced by the set of line currents is equal to the vectorial sum of the field produced by the
basic elements (monopole, dipole, and quadrupole). However, the total field is not calculated by the applet, since it
depends not only on the distance but also on the direction of the line connecting the point of measurements with the
center of the set of line currents. This direction does not affect the magnitudes of the basic elements but affects their
relative phase angle and direction in space. The best estimate of the total field is the square root of the sum of the
squares of the magnitudes of the fields produced by the basic elements.

C-23
Software Requirements TL Workstation Design Tools Rev. 0

EMF-10

This applet calculates the short–circuit current and the capacitance to ground of conductive objects placed in a
transmission line environment. These issues are discussed in Section 7.8 of the Reference Book. The short-circuit
current is the current that would flow in a zero-resistance connection between object and ground. The capacitance of
the object to ground is calculated as if the object were perfectly insulated from ground.

The objects may be located in an electric field created by high voltage conductors. In this case the geometry and
voltage of these conductors must be specified. The objects may also be placed in an unperturbed (before the
introduction of the objects) uniform electric field w/o the need to specify the geometry and voltage of the source of
the field. If the electric field is created by energized objects, the short circuit currents and the capacitances to ground
will be calculated for all the objects at ground potential (V = 0). If the user specifies a uniform electric field,
calculations will be performed considering all the objects at ground potential (including those to which a voltage is
assigned).

The calculations are performed by using algorithms described in Appendix 7 of Chapter 7 of the Reference Book.
Objects are simulated by sets of cylindrical segments at the same potential and the 3-D electric field problem is
solved. The charges on each object are calculated and from them short-circuit currents are capacitances. This applet
is ideal for 3-D objects, for high voltage conductors that have sags (transmission line conductors), or have an
irregular geometry (line angles, crossing lines), and when there are other shielding objects present.
The most challenging task for the user is the simulation of complex 3-D objects using cylindrical segments. This
issue is discussed in Section 7.3 of the Reference Book. Building an object may be a laborious task.

EMF-11

This applet calculates the magnetic field at desired locations before and after the application of conductors arranged
to form loops where currents will be induced by field sources such as transmission lines. The induced currents may
have the effect of producing a magnetic field that tends to cancel the source field, hence the name “cancellation
loop”.

The source of the field may be one or more transmission lines, or any current carrying conductor, or substation
buses, or coils. The cancellation loops are formed by conductor segments that form the so-called “passive network”.

This applet accepts not only straight conductors, but also conductors that have sags (transmission line conductors),
are not parallel to each other (transposition spans), and are at an angle with each other (substation buses).

The magnetic field is calculated along a straight segment or on a plane grid, both with and without the passive
network

EMF-12

This applet calculates the magnetic field reduction that can be achieved by adding a fourth wire connected to one of
the phases of a thee-phase line. This method of field reduction is discussed in Section 7.17.7 of the Reference Book.
Examples of possible geometries for this scheme are shown in the figure of the applet window. The phases are
designated as A, B, and C. The fourth wire is connected in parallel to phase A. The applet applies to the field inside
a calculation area adjacent to the line. The problem is treated as a 2-D problem. The phase currents are assumed
balanced and symmetric.

RN-1

C-24
Functional Specifications TL Workstation Design Tools Rev. 0

This applet calculates the electromagnetic interference (EMI) produced by corona on high voltage transmission
lines. The wideband method of EMI calculation is used. This method does not incorporate the approximations used
by the traditional method of radio noise calculations: quasi-TEM modes of propagation, quasi-static methods of field
calculations. Therefore, the results are valid in the entire MF and HF frequency ranges from 300 kHz to 30 MHz.
The results consist in the median EMI during measurable rain (L50 rain). The EMI is calculated as an electric field
(dB above 1 μV/m) read either by a rod or a loop antenna. The location of the measuring point is not confined to
points close to the ground (as in the traditional radio noise calculation method, but can be also above the conductors.
The conductors are treated as if they were infinitely long and parallel to a flat conductive earth. Any number of
circuits may be considered, and the voltages do not have to be symmetric. Each phase may have a different bundle,
whose geometry must be specified. The conductors are assumed to be ACSR. Ground wires are considered in the
calculation of the surface gradient of phase conductors, but are otherwise neglected in the EMI calculation. The
applet calculates the excitation function of each phase based on the bundle geometry, the maximum surface gradient,
and the altitude above sea level. The excitation function is then used to calculate the EMI accounting for line
geometry, measuring frequency, earth resistivity, and earth dielectric constant. The EMI lateral profile is calculated
along a specified line orthogonal to the line.

RN-2

This applet calculates the electromagnetic interference (EMI) caused by corona on high voltage transmission lines at
different distances from the line. The EMI is calculated in terms of electric field expressed in decibels above 1
μV/m. The algorithms for the calculations are described in Section 9.5.3 (for frequencies up to 30 MHz) and Section
9.6.3 (for frequencies above 30 MHz) of the Reference Book. EMI is calculated for fair weather and for rain. In both
cases average values are given.

The applet calculates the lateral profile of EMI and also the EMI generated by individual bundles in the reference
condition (1MHz, 15 m laterally, quasi-peak detector, 9 kHz bandwidth) so that the bundle that most contributes to
the EMI could be assessed. The user must specify the interval of distances from the line, the number of segments in
which this interval is divided, and the height above ground at which the antenna measuring EMI is located. The user
must also specify the altitude, the ground resistivity, the type of detector (quasi-peak, peak, rms, or average) and its
bandwidth. However, for QP only the single bandwidth of 9 kHz is allowed for frequencies from 150 kHz to 30
MHz. From 30 MHz to 1 GHz the QP bandwidth is 120 kHz. These fixed bandwidths are according to CISPR
specifications as shown in Table 9.4-1 of the Red Book. Any bandwidth can be specified for average, rms and peak
detector calculations.

The applet calculates EMI only for single conductors or regular bundles, i.e. bundles for which the conductors are
placed on the vertices of a regular polygon. The conductors are treated as if they were infinitely long and parallel to
a flat earth. If the conductors are catenaries, the height of the conductors above ground should be specified as the
average height above ground. It is recommended to use the minimum height plus one third of the sag.

RN-4

This applet calculates the radio noise produced by corona on high voltage transmission lines using the traditional
method that has evolved over a period of several decades with contributions and refinements by several researchers.
This method incorporates approximations (quasi-TEM modes of propagation, quasi-static methods of field
calculations) that limit its application to frequencies less than 1.6 MHz, to distances from the line not much greater
than a quarter of the wavelength, and to points near ground level. The method is described in the second edition of
the Transmission Line Reference Book. All the algorithms used for this applet are described in details in the
Appendix at the end of this Help document. In order to overcome the limitations of the traditional method, Dr.
Robert Olsen has developed the wideband method of EMI calculations, which is the basis for Applet RN-1.

The results of this applet consist in the median Radio Noise during measurable rain (L50 rain). The Radio Noise is
calculated as an electric field (dB above 1 μV/m) read either by a rod or a loop antenna with a CISPR quasi-peak

C-25
Software Requirements TL Workstation Design Tools Rev. 0

detector with a 9 kHz bandwidth. The conductors are treated as if they were infinitely long and parallel to a flat
conductive earth. Any number of circuits may be considered, and the voltages do not have to be symmetric. Each
phase may have a different bundle, whose geometry must be specified. The conductors are assumed to be ACSR.
Ground wires are considered for the calculation of the surface gradient of phase conductors and for the propagation
of radio noise currents and voltages along the line. The applet calculates the excitation function of each phase based
on bundle geometry, surface gradient, frequency, and altitude above sea level. The excitation function is given for a
CISPR quasi-peak detector with a 9 kHz bandwidth. The excitation function is then used to calculate the Radio
Noise accounting for line geometry, measuring frequency, earth resistivity, and earth dielectric constant. The Radio
Noise profile is calculated along a specified horizontal line perpendicular to the transmission line.

S-1

This applet calculates the 50% flashover voltage, V50, of air gaps of complex geometry when stressed with switching
impulses of positive polarity and critical time to crest. Chapter 5 of the Reference Book reports V50 data for several
gaps with simple geometry (rod-plane, rod-rod, conductor-plane, conductor-tower truss, etc). This applet extends the
calculations to any type of air gap using a flashover model generically described in Chapter 5, Appendix 2 of the
Reference Book.

File Menu

The File Menu provides options to manage the available projects in the selected Data Source to which the
application is connected. Those options are:
• New Project
o Allows user to create a new, empty project.
• Open Project
o Allows user to select an existing project to open.
• Close Project
o Allows user to close the open project.
• Save Project
o Allows user to save any current changes to the open project.
• Save Project As…
o Allows user to duplicate the open project, requiring the user to provide a different name for the
new project. It closes the old project, making the new project the open project.
• Delete Project
o Allows user to delete the current open project.
• Import Project
o Allows user to import a project that had either been previously exported from the currently
connected data source or exported from some other data source. The file will be an XML
formatted file. (Will allow users to share project data amongst data sources.)
• Export Project and
o Allows user to export the current open project. The export file will be an XML formatted file.
• Project Properties
o Allow user to change the default project properties, including the name and description.

The menu also provides a Change Data Source option that will allow the user to close the current data source and
open a different data source without having to exit the application.

Segments Menu

The Segments Menu provides options to manage the individual Right-Of-Way/Circuit Configurations (Segments)
within the open project. Those options are:

C-26
Functional Specifications TL Workstation Design Tools Rev. 0

• New Segment
o Allows user to create a new, empty segment. User will be required to a unique name and
description for the new segment. Once the application determines the name to be valid, it opens a
new Child Window to provide the user the ability to enter the data describing the segment.
• Open Segment
o Allows user to select another segment from within the currently open project to open. It opens a
new Child Window to allow editing of the data for that Segment.
• Open All Segments
o Allows user to open for editing, all remaining Segments in the open project. It opens one Child
window for each Segment in the project. For a large project, this could be a lot.
• Close Segment
o Allows user to close the currently active Child window, and correspondingly, the Segment that
window manages. If there are any outstanding changes, the user will be asked if they wish to save
those changes before closing.
• Close All Segments
o Allows user to close all Child windows. As with Close Segment, the user will be asked if they
wish to save any changes. They will also be provided the options of Yes to All and No to All.
• Save Segment
o Allows user to save the Segment in the currently active Child window.
• Save As Segment…
o Allows user to duplicate the Segment in the currently active Child window, creating a new
Segment within the currently open project. The user will be required to change the name of the
Segment to ensure uniqueness.
• Save All Segments
o Allows user to save all currently open Segments.
• Delete Segment
o Allows user to delete the Segment in the currently active Child window.
• Import Segment
o Allows user to import a Segment that had either been previously exported from the current project
or exported from some other project or data source. The file will be an XML formatted file. (Will
allow users to share Segment data amongst data sources and projects.)
• Export Segment
o Allows user to export the Segment in the currently active Child window. The export file will be an
XML formatted file.
• Segment Properties
o Allow user to change the default Segment properties, including the name and description.

Analysis Menu

The Analysis Menu provides option to run the Applet calculations against the Project/Segment data. It will allow the
user to run the analysis on the entire project, the currently active Segment (Child window) or to run specific Applet
calculations. This is subject to change pending review by the Task Force. At this time (9/8/2006), the options are:
• Run Segment Analysis
• Run Project Analysis
• Audible Noise [applets sub-menu]
• Surface Gradients [applets sub-menu]
• Corona/Ozone [applets sub-menu]
• Electric and Magnetic Fields [applets sub-menu]
• Radio Noise [applets sub-menu] and
• Switching [applets sub-menu]

C-27
Software Requirements TL Workstation Design Tools Rev. 0

Reports Menu

The Reports Menu allows the user to specify how the results are to be presented, or to display the results of a
previously executed analysis for the currently active Child window (Segment). The options are:
• Report
• Plot
• Excel
• Word
• Default Report Type [sub-menu]
o Allows user to specify the default type of file to which to write the analysis output (e.g. Word,
Excel or internal report dialog).
• Output Directory
o This allows the user to specify the directory to which report files (e.g. Word document) should be
written.

View Menu

The View Menu allows the user to configure the user interface. For now, the configuration options are limited to:
• System of Units [sub-menu]
o This allows the user to specify the units to use when displaying dimensioned data. The options are:
ƒ By Project
ƒ English
ƒ SI
• Angle Units [sub-menu]
o This allows the user to specify the units to use to display angles. The options are:
ƒ By Project
ƒ Degrees
ƒ Radians
ƒ Milliradians
ƒ Grads

In addition, any available dialogs to display or manage underlying reference data, are listed in this menu. For now,
the only dialog is Conductor Names, which allows for management of the Conductor Wire types (from Applet CC-
4).

Windows Menu

This menu contains the standard MDI Parent Windows Menu options of: Cascade, Tile Horizontally, Tile Vertically,
Minimize All, and Arrange All. It will also contain a list of all Child Forms and other open non-modal application
forms.

Help Menu

C-28
Functional Specifications TL Workstation Design Tools Rev. 0

This menu contains the standard Help Menu options of: Help Contents, Help Index, Using Help and About. It will
also contain a sub-menu of any Demonstration Applets the Task Force may choose to include in the application.

C-29
Software Requirements TL Workstation Design Tools Rev. 0

Low-Level Design

Data Diagrams

Project Header

The Project Header Tables are retained from TLWorkstation version 3 for the initial
database. However, the key field sizes are increased to allow for the use of more
descriptive names.

TL Workstation Project/Segment/Tower Header

Project ProjectApplication

PK stProjectName PK stProgramName
PK,FK1 stProjectName
stAuthorName
stAppCreatedBy stAuthorName
dtStart dtModified
dtLastChange chUnitsOfMeas
stDesc1
stDesc2
stDesc3
stDesc4

ProjectDescription

PK,FK1 stProgramName
PK,FK1 stProjectName

dtStart
stDesc1
stDesc2
stDesc3
stDesc4

ProjectSegment
PK,FK1 stProjectName
PK stSegmentName ProjectDetails

stDesc1 PK,FK1 stSegmentName

stDesc2 PK stTowerName
stDesc3 PK,FK2 stProgramName
stDesc4 PK,FK2 stProjectName
dLatitude
dLongitude chUnitsOfMeas
dLineLength dtStart
iLineLengthUnit dtModified
sKeraunic stAuthorName
sTimeZone stDesc1
dAltitude stDesc2
iAltitudeUnit stDesc3
dRightOfWay stDesc4
iRightOfWayUnit

C-30
Functional Specifications TL Workstation Design Tools Rev. 0

Circuit Configuration

Similarly, the Circuit configuration tables are retained from TL Workstation version 3.0:

C-31
Software Requirements TL Workstation Design Tools Rev. 0

Miscellaneous Right-Of-Way Objects

The Objects Tables have been revised to allow for additional information required by the
algorithms used by the Applets.

TL Workstation Design Tools ACDCLine

Miscellaneous Right-Of-Way Objects

AcdcMiscObject AcdcMiscObjectPoint
PK stProjectName PK,FK1 stProjectName
PK stSegmentName PK,FK1 stSegmentName
PK stTowerName PK,FK1 stTowerName
PK nMiscObjectNo PK,FK1 nMiscObjectNo
PK PointNo
stMiscObjectType
VoltageInKV XInM
PhaseInDeg YInM
CurrentInAmp ZInM
DiameterInM
InnerDiameterInM
Turns
CurrMultFactor
GMDInM
ResistanceInOhm
CapacitanceInFarad
SagMidHeightInM

Support Modules

Jama Module

This module contains the Jama calculation routines for matricies as used by the original Applets…

This module has been enhanced to provide additional math objects and functions. These routines are used in this
application to simplify the appearance of the calculations, making them easier to validate for correctness…

C-32
Functional Specifications TL Workstation Design Tools Rev. 0

Maths
Class

Methods
ACosh
ASinh
ATanh
DegToRad (+ 1 overload)
Distance (+ 3 overloads)
RadToDeg (+ 1 overload)
Resultant (+ 3 overloads)
SinCos (+ 1 overload)

Additional structures and classes added to support geometric calculations and 3-D results displays...

Vector2D Point2D Bounds3D

Class Class Class

GLRotation3D
Class

Vector3D Point3D
Class Class
Vector2D Point2D RCatenaryParms
Struct

RCatenaryPoint
Struct

Vector4D Point4D
Class Class
Vector3D Point3D

AppletCommon Module

This module contains all miscellaneous classes from the original Applets, plus new classes used by all integrated
Applets.

Classes from the original Applets…

C-33
Software Requirements TL Workstation Design Tools Rev. 0

Most data entry fields in the application involve numeric data that have specific unit dimensions. These data fields
allow the user to enter unit text when entering these numbers in order to override the default units used in the
interface. For example, a given field may require a number with the units of Length and the display is in feet. In this
application, in such a field, if the user enters just a number, then it is assumed to be in the display units of feet.
However, this application allows the user to enter ‘6 in’; the application will automatically convert it to ‘0.5’ (ft).
To support this, these field validations/unit conversions are encapsulated in classes, a few of which are illustrated
below.

Additional miscellaneous Enumerated Types, Exception Types have been added to this module to simplify the code
of all converted Applets.

Electric Circuit Components Module

The original Applets defined Circuit, Bundle and Conductor (named Cylinder) classes to encapsulate the data
pertaining to those individual real-world objects. With this integration, that data is properly encapsulated as
Properties. Also, the field names in these classes have been modified to be more descriptive, and to contain the units.
For example, the diameter of the conductor was named ‘dblD’. In this application, the field, as a property, has been
renamed to ‘DiameterInCm’, i.e. diameter in centimeters. This should greatly facilitate code validation during
testing. In addition, the conductor wire name and type are further refactored to encapsulate those parameters and
further simplify the code, eliminating duplication.

C-34
Functional Specifications TL Workstation Design Tools Rev. 0

Abstract Class

Circuit IEditableObject
Class
Asset ConductorType
Class
Asset

IEditableObject IEditableObject

Bundle ConductorName
Class Class
Asset Asset

ICloneable
IEditableObject

Conductor
Class
Asset

Various Applets used either 2-D or 3-D Electric field calculations. The class and naming of the corresponding
routines varied. All the calculation modules have been reconciled and refactored into two basic classes that will be
used by all Applets in the new application…

C-35
Software Requirements TL Workstation Design Tools Rev. 0

Abstract Class
Asset

BoxObject FlatPlateObject
Class Abstract Class Class
MiscObject MiscObject MiscObject

ToroidObject WireObject
Class Class
MiscCylindricalObject MiscCylindricalObject

CatenaryObject CylinderObject
Class Class
MiscCylindricalObject MiscCylindricalObject

SphereObject CoilObject RodObject

Class Class Class
MiscCylindricalObject MiscCylindricalObject MiscCylindricalObject

OpenGL 3-D Model Display Modules

Separate modules have been included, which interface .NET Managed Code to Windows native OpenGL dlls. These
include:
4. csgl.native, which is creates the dll that encapsulate the interface to the OpenGL.org Windows dlls:
opengl.dll. Glu.dll and glut.dll.
5. CsGL, which provide wrappers for all the basic OpenGL types; and,
6. CsGLBasecode, which provides high-level wrappers encapsulating a Windows Control, ‘View’, that
provides the display canvas control that appear on a Form; and one that encapsulates the displayed 3-D
objects ’Model’.

This application encapsulates extended functionality by extending the above wrappers in CsGLBasecode with
‘RedbookGLControl’ and ‘RedbookModel’ respectively. These controls are provided by the ‘RedbookGL’ module.

In addition, the routines for rendering Conductors and Miscellaneous Objects are encapsulated in another set of
classes. These are also included the ‘RedbookGL’ module.

Graphing Module

C-36
Functional Specifications TL Workstation Design Tools Rev. 0

Displaying Graphs is accomplished with another tool called Zedgraph.

However, the components in Zedgraph are encapsulated in wrappers in the AppletCommon. This is done to
simplify the development of the graphs and to ensure consistency…

IPointList

GraphMultiPoint…
Class Abstract Class

MultiCalculation…
Class Abstract Class
GraphMultiPointList GraphData

Individual Applets’ Code

AN-1

AN-2

AN-3

C-37
Software Requirements TL Workstation Design Tools Rev. 0

AN-4

Detailed Design remains to be done.

AN-6

Detailed Design remains to be done.

CC-1

The 2-D Surface Gradient calculation from this Applet has been reconciled with the Surface Gradient calculations in
the other Applets, and refactored into the ElectricField2D module listed in the Electric Circuits Component Modules
above.

CC-4

This Applet is converted and reformatted as shown below.

C-38
Functional Specifications TL Workstation Design Tools Rev. 0

CC-5

Detailed Design remains to be done.

CL-1

Detailed Design remains to be done.

CL-3

C-39
Software Requirements TL Workstation Design Tools Rev. 0

Detailed Design remains to be done.

EMF-2/EMF-5

EMF-5 is really the same as EMF-2, with the addition of miscellaneous objects in the field.

EMF-4

EMF-6

Detailed Design remains to be done.

EMF-7

Detailed Design remains to be done.

EMF-8

Detailed Design remains to be done.

EMF-9

Detailed Design remains to be done.

EMF-10

C-40
Functional Specifications TL Workstation Design Tools Rev. 0

EMF-11

Detailed Design remains to be done.

EMF-12

Detailed Design remains to be done.

RN-1

Detailed Design remains to be done.

RN-2

Detailed Design remains to be done.

RN-4

Detailed Design remains to be done.

S-1

Detailed Design remains to be done.

Starting Application

On executing the application, the application initializes with the following steps:
1. Displays the EPRI Disclaimer dialog. This dialog displays the Disclaimer and OK and Cancel buttons. If
the user clicks the Cancel button, then the application terminates. If the user clicks the OK button, then the
application proceeds to…
2. Display the Data Source Connection dialog. This dialog provides:
a. UserID field for the userid with which to connect to the Data Source,
b. Password field for the Password for the entered UserID and Data Source,
c. A Change Connection button to allow user to configure a different Data Source,
d. An OK button, which the user clicks to proceed and
e. A Cancel button, which the user clicks to terminate the application.
3. Displays the application main form.

Disclaimer Form

C-41
Software Requirements TL Workstation Design Tools Rev. 0

Data Source Connection Dialog

A database is installed with the application for desktop use. But, in general, the
application is designed to allow access to different sources of data. Some of those data
sources may require the user to log in with a userid and password. So, when the
application starts, and the currently configured data source (from the Registry) requires
a userid and password, the user is requested to either enter the userid and password, or
change to connect to a different data source.

C-42
Functional Specifications TL Workstation Design Tools Rev. 0

Application Main (MDI Parent) Form

Menu Functions

File Menu

The File Menu provides options to manage the available projects in the selected Data Source to which the
application is connected.

New Project

This option allows user to create a new, empty project.

Open Project

C-43
Software Requirements TL Workstation Design Tools Rev. 0

This option allows user to select an existing project to open.

Open Project Dialog

Close Project

This option allows user to close the open project.

Save Project

This option allows user to save any current changes to the open project.

Save Project As…

This option allows user to duplicate the open project.

Delete Project

This option allows user to delete the current open project.

Import Project

This option allows user to import a project

C-44
Functional Specifications TL Workstation Design Tools Rev. 0

Export Project

This option allows user to export the current open project.

Project Properties

This option allow user to change the default project properties.

Change Data Source

This option allow the user to switch data source.

Segments Menu

The Segments Menu provides options to manage the individual Right-Of-Way/Circuit Configurations (Segments)
within the open project.

New Segment

This option allows user to create a new, empty segment. User will be required to a unique name and
description for the new segment. Once the application determines the name to be valid, it opens a new
Child Window to provide the user the ability to enter the data describing the segment.

Open Segment

This option allows user to select another segment from within the currently open project to open. It opens a
new Child Window to allow editing of the data for that Segment.

Open All Segments

This option allows user to open for editing, all remaining Segments in the open project. It opens one Child
window for each Segment in the project. For a large project, this could be a lot.

Close Segment

C-45
Software Requirements TL Workstation Design Tools Rev. 0

This option allows user to close the currently active Child window, and correspondingly, the Segment that
window manages. If there are any outstanding changes, the user will be asked if they wish to save those
changes before closing.

Close All Segments

This option allows user to close all Child windows. As with Close Segment, the user will be asked if they
wish to save any changes. They will also be provided the options of Yes to All and No to All.

Save Segment

This option allows user to save the Segment in the currently active Child window.

Save As Segment…

This option allows user to duplicate the Segment in the currently active Child window, creating a new
Segment within the currently open project. The user will be required to change the name of the Segment to
ensure uniqueness.

Save All Segments

This option allows user to save all currently open Segments.

Delete Segment

This option allows user to delete the Segment in the currently active Child window.

Import Segment

This option allows user to import a Segment that had either been previously exported from the current
project or exported from some other project or data source. The file will be an XML formatted file. (Will
allow users to share Segment data amongst data sources and projects.)

Export Segment

This option allows user to export the Segment in the currently active Child window. The export file will be
an XML formatted file.

C-46
Functional Specifications TL Workstation Design Tools Rev. 0

Segment Properties

This option allow user to change the default Segment properties, including the name and description.

Analysis Menu

The Analysis Menu provides option to run the Applet calculations against the Project/Segment data. It will allow the
user to run the analysis on the entire project, the currently active Segment (Child window) or to run specific Applet
calculations. This is subject to change pending review by the Task Force

Run Segment Analysis

Run Project Analysis

Audible Noise [applets sub-menu]

Surface Gradients [applets sub-menu]

Corona/Ozone [applets sub-menu]

Electric and Magnetic Fields [applets sub-menu]

Radio Noise [applets sub-menu] and

Switching [applets sub-menu]

Reports Menu

The Reports Menu allows the user to specify how the results are to be presented, or to display the results of a
previously executed analysis for the currently active Child window (Segment).

Report

C-47
Software Requirements TL Workstation Design Tools Rev. 0

Plot

Excel

Word

Default Report Type [sub-menu]

Allows user to specify the default type of file to which to write the analysis output (e.g. Word, Excel or
internal report dialog).

Output Directory

This allows the user to specify the directory to which report files (e.g. Word document) should be written.

View Menu

The View Menu allows the user to configure the user interface.

System of Units [sub-menu]

This allows the user to specify the units to use when displaying dimensioned data. The options are:
By Project
English
SI

Angle Units [sub-menu]

This allows the user to specify the units to use to display angles. The options are:
By Project
Degrees
Radians
Milliradians

C-48
Functional Specifications TL Workstation Design Tools Rev. 0

Grads

Conductor Names

Display Conductor Wire types dialog (from Applet CC-4).

Help Menu

This menu contains the standard Help Menu options

Help Contents

Help Index

Using Help

About.

Demonstration Applets [sub-menu]

C-49
Software Requirements TL Workstation Design Tools Rev. 0

Child Form

Circuit/Bundle/Conductor Configuration Tab

This is an example Child form showing the Primary tab the user would use to enter the Circuit, Bundle and
Conductor configuration.

C-50
Functional Specifications TL Workstation Design Tools Rev. 0

Miscellaneous Objects Tab

The second tab [currently] allows the user to specify the miscellaneous object in the Right-Of-Way.

C-51
Software Requirements TL Workstation Design Tools Rev. 0

Location/Profile Specifications Tab

The third tab [currently] allows the user to specify the calculation parameters.

C-52
Export Control Restrictions The Electric Power Research Institute (EPRI)
Access to and use of EPRI Intellectual Property is The Electric Power Research Institute (EPRI), with
granted with the specific understanding and major locations in Palo Alto, California, and Charlotte,
requirement that responsibility for ensuring full North Carolina, was established in 1973 as an
compliance with all applicable U.S. and foreign export independent, nonprofit center for public interest energy
laws and regulations is being undertaken by you and and environmental research. EPRI brings together
your company. This includes an obligation to ensure members, participants, the Institute’s scientists and
that any individual receiving access hereunder who is engineers, and other leading experts to work
not a U.S. citizen or permanent U.S. resident is collaboratively on solutions to the challenges of electric
permitted access under applicable U.S. and foreign power. These solutions span nearly every area of
export laws and regulations. In the event you are electricity generation, delivery, and use, including
uncertain whether you or your company may lawfully health, safety, and environment. EPRI’s members
obtain access to this EPRI Intellectual Property, you represent over 90% of the electricity generated in the
acknowledge that it is your obligation to consult with United States. International participation represents
your company’s legal counsel to determine whether nearly 15% of EPRI’s total research, development, and
this access is lawful. Although EPRI may make demonstration program.
available on a case-by-case basis an informal
assessment of the applicable U.S. export classification Together…Shaping the Future of Electricity
for specific EPRI Intellectual Property, you and your
company acknowledge that this assessment is solely
for informational purposes and not for reliance
purposes. You and your company acknowledge that it
is still the obligation of you and your company to make
your own assessment of the applicable U.S. export
classification and ensure compliance accordingly. You
and your company understand and acknowledge your
obligations to make a prompt report to EPRI and the
appropriate authorities regarding any access to or use
of EPRI Intellectual Property hereunder that may be in
violation of applicable U.S. or foreign export laws or
regulations.

© 2006 Electric Power Research Institute (EPRI), Inc. All rights

reserved. Electric Power Research Institute and EPRI are registered
service marks of the Electric Power Research Institute, Inc.

Printed on recycled paper in the United States of America 1012318

ELECTRIC POWER RESEARCH INSTITUTE

3420 Hillview Avenue, Palo Alto, California 94304-1338 • PO Box 10412, Palo Alto, California 94303-0813 • USA
800.313.3774 • 650.855.2121 • [email protected] • www.epri.com