PTW Userguide

Power*Tools®

for Windows

™

User's Guide

Electrical Engineering Analysis Software for Windows

Copyright © 2006, SKM Systems Analysis, Inc.

All Rights Reserved.

UG ii User's Guide

8/16/2006

Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, without the express written consent of SKM Systems Analysis, Inc. No patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this manual, the publisher and author assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of information contained herein. For information, address SKM Systems Analysis, Inc., PO Box 3376, Manhattan Beach, CA 90266-1376, USA.

©2006 SKM Systems Analysis, Inc. All rights reserved.

Power*Tools, CAPTOR and DAPPER are registered trademarks and HI_WAVE and I*SIM are trademarks of SKM Systems Analysis, Inc. Microsoft is a registered trademark and Windows is a trademark of Microsoft Corporation. Intel is a registered trademark and Pentium is a trademark of Intel Corporation. ACAD and AutoCAD are registered trademarks of AUTODESK, Inc. WordPerfect is a registered trademark of Novell, Inc. Lotus and 1-2-3 are registered trademarks of Lotus Development Corporation. Arial is a registered trademark of The Monotype Corporation, PLC. PIXymbols is a trademark of Page Studio Graphics ImageStream Graphics Filters is a registered trademark and ImageStream is a trademark of ImageMark Software Labs, Inc.

PIXymbols™ Extended Character Set. Copyright ©1995. Page Studio Graphics. All rights reserved. For information, address Page Studio Graphics, 3175 North Price Road, Suite 150, Chandler, AZ 85224. Phone/Fax: (602) 839-2763. ImageStream Graphics & Presentation Filters. Copyright ©1991-1995. ImageMark Software Labs, Inc. All rights reserved. Various definitions reprinted from IEEE Std 100-1992, IEEE Standard Dictionary of Electrical and Electronics Terms, copyright © 1992 by the Institute of Electrical and Electronics Engineers, Inc. The IEEE takes no responsibility or will assume no liability for the reader's misinterpretation of said information resulting from its placement and context in this publication. Information is reproduced with the permission of the IEEE. MathType™ math equation editing fonts are licensed from Design Science, Inc. ©1987-1996 by Design Science, Inc. All rights reserved.

Contents UG iii

SKM Power*Tools for Windows

Contents

Before You Begin..........................................................................................................xiii Keyboard Conventions...............................................................................................xiii Mouse Conventions....................................................................................................xiii Technical Support ...................................................................................................... xiv Power*Tools Seminars................................................................................................ xv Limitations .................................................................................................................. xv

1 INTRODUCTION............................................................................................................................ 1-1

1.1. Installing PTW ......................................................................................................1-2

1.1. UnInstalling PTW .................................................................................................1-2

1.2. Projects...................................................................................................................1-2 The One-Line Diagram ..........................................................................................1-3 The Component Editor ...........................................................................................1-4

1.3. Components and Attributes .................................................................................1-4 Components............................................................................................................1-5 Attributes................................................................................................................1-5

1.4. Queries ...................................................................................................................1-5

1.5. Libraries.................................................................................................................1-6

1.6. Studies ....................................................................................................................1-7

1.7. Reports, Datablocks and Crystal Report ............................................................1-7 1.7.1. Reports .............................................................................................................1-7 1.7.2. Datablocks........................................................................................................1-8 1.7.3. Crystal Reports ...............................................................................................1-10

1.8. Compatibility with Power*Tools for DOS ........................................................1-10

1.9. Sharing Data with Other Applications..............................................................1-10 1.9.1. Edit and Print Reports in Word Processors ....................................................1-11 1.9.2. Export One-Line Diagrams for Graphics and CAD Programs.......................1-11

1.10. On-Line Help .....................................................................................................1-12

UG iv User's Guide

8/16/2006

2 GETTING STARTED......................................................................................................................2-1

2.1. Starting PTW: Stand-Alone................................................................................ 2-2

2.2. Starting PTW: LAN Users.................................................................................. 2-2 2.2.1. Changing Permission Status During a PTW Session....................................... 2-3 2.2.2. Logging Out of PTW....................................................................................... 2-4

2.3. Global Options ...................................................................................................... 2-4 2.3.1. Setting Startup Options.................................................................................... 2-4

Opening the Most Recent Project Automatically .................................................. 2-4 Enabling the Pentium™ Warning.......................................................................... 2-4

2.3.2. Setting Application Options ............................................................................ 2-5 Setting the Display Standard.................................................................................. 2-5 Setting the System Frequency................................................................................ 2-5 Setting the Units of Measurement.......................................................................... 2-5 Setting Event Message Options ............................................................................. 2-5

2.4. Working with Projects ......................................................................................... 2-7 2.4.1. Creating a New Project .................................................................................... 2-7 2.4.2. Building the Electrical System in a Project ..................................................... 2-8 2.4.3. Opening an Existing Project ............................................................................ 2-8 2.4.4. Copying Projects.............................................................................................. 2-9 2.4.5. Closing Projects ............................................................................................. 2-10 2.4.6. Deleting Projects............................................................................................ 2-10 2.4.7. Getting Project Statistics................................................................................ 2-11 2.4.8. Backing Up Projects ...................................................................................... 2-11 2.4.9. Merging Projects............................................................................................ 2-12 2.4.10. Exporting Projects ....................................................................................... 2-12

Choosing Export Options .................................................................................... 2-13 2.4.11. Database Utility ........................................................................................... 2-14 2.4.12. Compress Library ........................................................................................ 2-14

2.5. Working with Menu Commands....................................................................... 2-15

2.6. Working with the Status Bar ............................................................................. 2-23

2.7. Working with Toolbars ...................................................................................... 2-23

3 ONE-LINE DIAGRAMS................................................................................................................ 3-1

3.1. What is a One-Line Diagram?............................................................................. 3-2

3.2. One-Line Diagrams and the Project Database................................................... 3-3 3.2.1. ‘Components’ vs. ‘Symbols’ ........................................................................... 3-3

Existing Components............................................................................................. 3-4 New Components................................................................................................... 3-4

3.2.2. Multiple One-Line Diagrams........................................................................... 3-5

3.3. Creating and Opening One-Line Diagrams ....................................................... 3-6 3.3.1. Creating a New One-Line Diagram................................................................. 3-6 3.3.2. Opening an Existing One-Line Diagram ......................................................... 3-6

Contents UG v


3.4. The One-Line Diagram Interface ........................................................................3-6 3.4.1. Database-Related Objects.................................................................................3-7

Symbol ...................................................................................................................3-7 Component Name and Datablock...........................................................................3-9 Connection .............................................................................................................3-9

3.4.2. User-Defined Objects.......................................................................................3-9 3.4.3. Mouse Pointers.................................................................................................3-9

3.5. Navigating the One-Line Diagram.....................................................................3-10 3.5.1. Scrolling a One-Line Diagram .......................................................................3-10 3.5.2. Magnifying a One-Line Diagram...................................................................3-11

Zooming In and Out .............................................................................................3-11 Zoom Area............................................................................................................3-12 Zoom All ..............................................................................................................3-12 Zoom Page............................................................................................................3-12 Find Component...................................................................................................3-13 Aerial View ..........................................................................................................3-13

3.6. Building the One-Line Diagram.........................................................................3-14 3.6.1. Adding a New Component .............................................................................3-14 3.6.2. Adding a Symbol for an Existing Component ...............................................3-15

Adding Symbols Individually ..............................................................................3-15 Adding Symbols Using the Expand Command....................................................3-16

3.6.3. Copy/Paste Components to New One-line .....................................................3-17 3.6.4. Cloning Components......................................................................................3-17 3.6.5. Connecting and Disconnecting Components..................................................3-18 3.6.6. Making valid connections ..............................................................................3-19 3.6.7. Bus versus Bus-Node .....................................................................................3-20 3.6.8. Auto-Bus Insert ..............................................................................................3-21 3.6.9. Renaming Components ..................................................................................3-22 3.6.10. Taking Components In and Out of Service ..................................................3-23 3.6.11. Removing Symbols Versus Destroying Components ..................................3-23

3.7. Selecting Objects .................................................................................................3-24 3.7.1. Selecting Individual Objects ..........................................................................3-25 3.7.2. Selecting a Group of Objects .........................................................................3-25 3.7.3. Selecting All Objects......................................................................................3-26 3.7.4. Running a Query to Select Objects ................................................................3-26

3.8. Moving and Sizing Objects.................................................................................3-28 3.8.1. Moving Objects ..............................................................................................3-28 3.8.2. Moving Connection Lines ..............................................................................3-28 3.8.3. Sizing Bus Symbols .......................................................................................3-29 3.8.4. Aligning and Distributing Objects .................................................................3-30

Aligning Objects ..................................................................................................3-30 Distributing Objects .............................................................................................3-30

3.9. Taking Components to the Component Editor ................................................3-31

3.10. Showing Project Data on a One-Line Diagram ..............................................3-31

UG vi User's Guide

8/16/2006

3.11. Customizing the One-Line Diagram ............................................................... 3-34 New Texblock...................................................................................................... 3-35 Component Color................................................................................................. 3-35 Datablocks ........................................................................................................... 3-35 Nametags ............................................................................................................. 3-35 Connection Points................................................................................................ 3-35 Annotation ........................................................................................................... 3-35 Annotation Line Style.......................................................................................... 3-35 Symbol Rotation .................................................................................................. 3-35 Convert to Bus Node ........................................................................................... 3-35 Convert to Bus ..................................................................................................... 3-35 Symbol Selection ................................................................................................. 3-35

3.12. Annotating the One-Line Diagram with Textblocks ..................................... 3-36 3.12.1. Working with Textblocks ............................................................................ 3-38

Moving a Textblock Leader................................................................................. 3-38 Sizing a Textblock ............................................................................................... 3-39

3.13. Exporting One-Line Diagrams ........................................................................ 3-39

3.14. Changing Colors and Fonts ............................................................................. 3-41

3.15. Creating Custom Symbols ............................................................................... 3-43 3.15.1. Starting the Symbol Generator .................................................................... 3-43 3.15.2. Creating Custom Symbols ........................................................................... 3-45 3.15.3. Using Custom Symbols on a One-Line ....................................................... 3-47

3.16. Using 1- and 2-Node Annotations.................................................................... 3-48 3.16.1. Adding annotations to the One-Line............................................................ 3-48

3.17. Symbol Rotation ............................................................................................... 3-50

4 COMPONENT EDITOR.................................................................................................................4-1

4.1. What is the Component Editor?.......................................................................... 4-2

4.2. Opening the Component Editor .......................................................................... 4-2

4.3. Using the Component Editor ............................................................................... 4-2 4.3.1. Components Box ............................................................................................. 4-3 4.3.2. Component Subviews Box .............................................................................. 4-4 4.3.3. Component Set Option Buttons ....................................................................... 4-4

4.4. Navigating the System .......................................................................................... 4-5

4.5. Building the System .............................................................................................. 4-6 4.5.1. Adding a New Component .............................................................................. 4-6 4.5.2. Cloning a Component ...................................................................................... 4-7 4.5.3. Connecting and Disconnecting Components ................................................... 4-7 4.5.4. Renaming Components.................................................................................... 4-8 4.5.5. Taking Components In and Out of Service ..................................................... 4-8 4.5.6. Destroying Components .................................................................................. 4-9

Contents UG vii


4.6. Entering Component Data....................................................................................4-9 4.6.1. Copy / Paste Data ...........................................................................................4-10 4.6.2. Save Data as Default ......................................................................................4-10

4.7. Running a Query to Limit the Component Set.................................................4-10

4.8. Showing System Data in the Datablock Subview .............................................4-12

4.9. Buses .....................................................................................................................4-13

4.10. Cables .................................................................................................................4-14

4.11. Two-Winding Transformers ............................................................................4-14

4.12. Three-Winding Transformers..........................................................................4-15

4.13. Pi Impedances....................................................................................................4-15

4.14. Transmission Lines ...........................................................................................4-15

4.15. Utilities ...............................................................................................................4-16

4.16. Generators .........................................................................................................4-16

4.17. Non-Motor Loads ..............................................................................................4-17

4.18. Induction Motors...............................................................................................4-17

4.19. Synchronous Motors .........................................................................................4-18

4.20. Protective Devices..............................................................................................4-18

4.21. Filters..................................................................................................................4-19

4.22. Load Schedules ..................................................................................................4-20 4.22.1. Schedule Subview ........................................................................................4-20 4.22.2. Panel, MCC, or Switchboard subview .........................................................4-21

Assigning Bus Loads and Sub-Feeds to the Schedule..........................................4-21 Adding Little Loads to Circuits............................................................................4-27

4.22.3. Load Schedule Reports.................................................................................4-28

5 DATABLOCKS.............................................................................................................................. 5-1

5.1. What is a Datablock? ............................................................................................5-2

5.2. Parts of a Datablock..............................................................................................5-4

5.3. Applying Datablock Formats ...............................................................................5-4

UG viii User's Guide

8/16/2006

5.4. Viewing Datablocks .............................................................................................. 5-6 5.4.1. Viewing Datablocks on a One-Line Diagram.................................................. 5-6 5.4.2. Viewing Datablocks with the Probe ................................................................ 5-6 5.4.3. Viewing Datablocks in the Component Editor ................................................ 5-7

5.5. Creating Datablock Formats ............................................................................... 5-8 5.5.1. Editing the Attribute Template ........................................................................ 5-9 5.5.2. Using the Show Zero Value/Blank Text check box ........................................ 5-9

5.6. Editing Datablock Formats................................................................................ 5-10

5.7. Copying and Deleting Datablock Formats ....................................................... 5-11

5.8. Creating and Printing Datablock Reports ....................................................... 5-11 5.8.1. Creating, Saving, and Printing Datablock Reports ........................................ 5-12 5.8.2. Formatting the Datablock Report .................................................................. 5-13 5.8.3. Choosing What Data will Appear.................................................................. 5-13 5.8.4. Choosing Components for Reporting ............................................................ 5-13

For the Component Editor ................................................................................... 5-13 For a One-Line Diagram...................................................................................... 5-13 For a TCC Drawing ............................................................................................. 5-14

5.9. Creating User-Defined Fields ............................................................................ 5-15 5.9.1. Text Fields versus Numeric Fields ................................................................ 5-19 5.9.2. Date, Time and Currency Fields .................................................................... 5-20 5.9.3. Changing data in a User-Defined Field ......................................................... 5-20 5.9.4. Querying with User-Defined Fields............................................................... 5-21 5.9.5. Displaying User-Defined Field data .............................................................. 5-22 5.9.6. Copying User-Defined Fields to Other Projects ............................................ 5-23

6 QUERIES........................................................................................................................................ 6-1

6.1. What is a Query? .................................................................................................. 6-2

6.2. Before Running a Query ...................................................................................... 6-2

6.3. Running a Query .................................................................................................. 6-3 6.3.1. Responding to Query Prompts......................................................................... 6-4

6.4. Query Results in the Component Editor vs. the One-Line Diagram ............... 6-5 6.4.1. Query Results in the Component Editor .......................................................... 6-5 6.4.2. Query Results in a One-Line Diagram............................................................. 6-6

6.5. Organizing Queries............................................................................................... 6-6

6.6. Copying and Deleting Queries............................................................................. 6-7

Contents UG ix


6.7. Custom Queries .....................................................................................................6-7 6.7.1. Query Building Blocks.....................................................................................6-7

Condition Line........................................................................................................6-8 Sample Condition lines ........................................................................................6-10

6.7.2. Adding Custom Queries .................................................................................6-11 6.7.3. Removing Condition Lines and Component Sets ..........................................6-12

6.8. Advanced Queries ...............................................................................................6-13 6.8.1. Adding Boolean Operators.............................................................................6-13 6.8.2. Changing Boolean Operator Precedence........................................................6-15

7 REPORTS ........................................................................................................................................ 7-1

7.1. What is a Report?..................................................................................................7-2

7.2. Creating and Opening Reports ............................................................................7-2 7.2.1. Creating Reports...............................................................................................7-2 7.2.2. Opening an Existing Report .............................................................................7-3

7.3. The Report Interface.............................................................................................7-3

7.4. Navigating the Report...........................................................................................7-4 7.4.1. Scrolling a Report.............................................................................................7-4 7.4.2. Moving to a Specific Line ................................................................................7-4

7.5. Working with Text ................................................................................................7-5 7.5.1. Copying, Pasting, and Deleting Text................................................................7-5 7.5.2. Finding and Replacing Text .............................................................................7-5

Finding Text ...........................................................................................................7-6 Replacing Text .......................................................................................................7-6

7.6. Setting Report Options .........................................................................................7-7

7.7. Opening Reports in Other Applications..............................................................7-8

7.8. Crystal Reports......................................................................................................7-9 7.8.1. Differences between PTW Reports and Crystal Reports .................................7-9 7.8.2. Opening a Crystal Report ...............................................................................7-10 7.8.3. Parts of a Crystal Report ................................................................................7-12 7.8.4. Exporting a Crystal Report.............................................................................7-12 7.8.5. Running a Crystal Query................................................................................7-13 7.8.6. Using the Crystal Query Editor ......................................................................7-14

And/Or Logic .......................................................................................................7-14 Choosing Subreports ............................................................................................7-16

7.8.7. Creating your own Crystal Reports ................................................................7-17 Connecting a Crystal Report to PTW through ODBC .........................................7-18 PTW’s Database Structure ...................................................................................7-19

8 LIBRARIES.................................................................................................................................... 8-1

8.1. What is a Library? ................................................................................................8-2

UG x User's Guide

8/16/2006

8.2. Managing Libraries .............................................................................................. 8-4 8.2.1. Creating a New Library ................................................................................... 8-4 8.2.2. Opening an Existing Library ........................................................................... 8-4 8.2.3. Copying and Renaming Libraries .................................................................... 8-5 8.2.4. Compressing PTW Library Files ..................................................................... 8-5 8.2.5. Library Backup ................................................................................................ 8-5 8.2.6. Copying Between Multiple Libraries............................................................... 8-5

8.3. Changing Project Library References ................................................................ 8-6 8.3.1. Changing Current Library References During a Project.................................. 8-7

8.4. Adding and Editing Library Entries................................................................... 8-8

8.5. Copying Library Entries...................................................................................... 8-8

8.6. Cable Library........................................................................................................ 8-9 8.6.1. Editing the Cable Library ................................................................................ 8-9 8.6.2. Viewing the Circular Mils for the Cable Library........................................... 8-12 8.6.3. Viewing the Derating Factors for the Cable Library ..................................... 8-12

8.7. Demand Load Library ....................................................................................... 8-13 8.7.1. Using the Demand Load Library ................................................................... 8-13

8.8. Motor Control Center Library.......................................................................... 8-14 8.8.1. Using the Motor Control Center Library ....................................................... 8-14 8.8.2. Viewing the Accessory Groups for the Motor Control Center Library ......... 8-15

8.9. Transformer Library.......................................................................................... 8-16 8.9.1. Using the Transformer Library ...................................................................... 8-16

8.10. CAPTOR Library............................................................................................. 8-17

8.11. TMS Library ..................................................................................................... 8-17

8.12. I*SIM Library................................................................................................... 8-18

8.13. HI_WAVE Library........................................................................................... 8-18

8.14. Standard Transmission Line Library ............................................................. 8-19 8.14.1. Technical Data ............................................................................................. 8-20

8.15. 3-Phase Transmission Line Library................................................................ 8-21

8.16. Bus Library ....................................................................................................... 8-21

8.17. Reliability Library ........................................................................................... 8-22

9 PRINTING...................................................................................................................................... 9-1

9.1. Before Printing...................................................................................................... 9-2 9.1.1. Selecting a Printer............................................................................................ 9-2 9.1.2. Printing ............................................................................................................ 9-2

Contents UG xi


9.2. Things to Consider when Printing a One-Line...................................................9-3 9.2.1. Previewing a One-Line Diagram......................................................................9-3 9.2.2. Layout Options.................................................................................................9-4

Working with Page Guides ....................................................................................9-5

9.3. What is a Form? ....................................................................................................9-6

9.4. Creating a New Form............................................................................................9-8 9.4.1. Assigning Paper Size and Border Coordinates for the Form ...........................9-8 9.4.2. Formatting Areas on the page ..........................................................................9-9

Formatting the One-Line Areas............................................................................9-11 Formatting the Report Areas ................................................................................9-12 Formatting the TCC Drawing Areas ....................................................................9-12 Formatting the Title Block Areas .........................................................................9-14 Formatting the Plot Areas.....................................................................................9-15 Formatting the Picture Areas................................................................................9-16

9.4.3. Setting the Project Options for the Title Block and Picture Areas.................9-17

9.5. Printing Using a Form ........................................................................................9-17 9.5.1. Previewing a Form Before Printing................................................................9-18 9.5.2. Printing a Group of Documents (Batch Printing)...........................................9-19

APPENIX A .............................................................................................................................................1

IMPORTING DOS PROJECTS ...........................................................................................................1

A.1 DAPPER Import ................................................................................................. 2 Schedules................................................................................................................... 2 Motors ....................................................................................................................... 3 2-Winding and 3-Winding Transformers .................................................................. 4

A.1.2 Converting Special Bus Loads ...................................................................... 6 Special Bus Load Conversion Values ....................................................................... 7

A.1.3 Converting End Use Loads............................................................................ 7 End Use Load Conversion Values............................................................................. 8

A.1.4 Merging Machines and Fault Contributions.................................................. 9 Methodology ........................................................................................................... 10

A.2 Notes on Importing............................................................................................ 10

A.3 Converting Older DOS Projects ...................................................................... 11

A.4 Running Import for CAPTOR Projects .......................................................... 13 A.4.1 Device Not Found message ......................................................................... 15

A.5 Running Import for CAPTOR Libraries ........................................................ 17

APPENIX B .............................................................................................................................................1

TROUBLE-SHOOTING GUIDE ...........................................................................................................1

UG xii User's Guide

8/16/2006

A.1 General Protection Fault on Start-up ................................................................2

A.2 General Protection Fault while running PTW Program..................................2

A.3 Important Project Files .......................................................................................3

A.4 Invalid Connections .............................................................................................4

A.5 Utility Fault Contribution Error ........................................................................4

Contents UG xiii


Before You Begin

Before you start reading this User’s Guide, you should understand some of the terms that will be used frequently.

Keyboard Conventions Key names are shown in small capitals, for example, "press the R key." Special keys are referenced according to their names on an extended keyboard. For instance, the Escape key is referenced as the ESC key.

Key Comments Shortcut Keys These are special key combinations or sequences

that perform many of the same functions as menu options and help to speed work. With shortcut keys, CTRL+L means to hold down the CTRL while pressing L. ALT, L means to press and release the ALT key then press and release the L key. For menu commands that have shortcuts, the equivalent shortcut keys are shown in parentheses after the menu item. For example: Choose Find from the Edit menu (CTRL+F).

TAB When working in dialog boxes (such as the Component Editor) you can use the tab key to advance the cursor to the next dialog box option, including buttons and list boxes. The cursor moves through the options from left to right and from top to bottom. To tab in reverse order, press SHIFT+TAB.

Numeric keypad keys If your keyboard has a keypad, you can type all numeric data entry with the keypad, provided that the NUM LOCK key is turned on. (Press the NUM LOCK key at the upper left corner of most keypads.)

Mouse Conventions The following table presents mouse terms that are used consistently throughout the documentation:

The term Means Mouse pointer or pointer The cursor controlled by the mouse (or certain

keys) and that allows the user to perform functions. Whenever possible, a graphic of the mouse pointer is included with the documentation instructions.

Point to Using the mouse, move the mouse pointer until the tip of the mouse pointer rests on the object you want to select.

Click Press and quickly release the left mouse button.

Right click Press and quickly release the right mouse button.

UG xiv User's Guide

8/16/2006

The term Means Double Click Click twice in rapid succession. Unless otherwise

indicated, double click always refers to the left mouse button.

Drag Point to an object, then press and hold the mouse key as you move the mouse.

Technical Support SKM provides technical support for installing and using PTW. This support is provided free of charge for one year from the data of purchase and entitles you to free product updates, if any updates are issued within that year. At the end of the first year, SKM will notify you by mail that your maintenance and support service is about to expire, at which time you have the option of renewing maintenance for a fee. If you would like a copy of the maintenance pricing schedule, call or fax SKM at the number below or visit SKM’s web site www.skm.com

System design or analysis is not included as part of the maintenance and support service. You can get design consultation support through consulting services available from many engineering firms. SKM cannot offer support pertaining to the use of AutoCAD or any other CAD software, except where it involves the SKM interface. Consult the CAD manual for technical support phone numbers.

To reach SKM technical support

• Call (310) 698-4700

• Fax (310) 698-4708

Monday - Thursday 7:00 AM to 5:00 PM Pacific Standard Time Friday 7:00 AM to 12:00 PM Pacific Standard Time

If we can’t resolve your problem by telephone, you can submit results for review. SKM requests that the Project Files, Library Files and the user's technical evaluation of the problem be submitted. SKM cannot evaluate the problem without this documentation.

Submit all such materials to:

SKM Systems Analysis, Inc. Attn: Technical Support P.O. Box 3376 Manhattan Beach, CA 90266 Or by email to [email protected]

Interpreting and applying Study results is the responsibility of the application engineer. SKM assumes no responsibility for direct, indirect damages or consequential damages incurred by use of the SKM software.

Contents UG xv


Power*Tools Seminars SKM offers instructional seminars on the entire line of Power*Tools products for Windows and DOS. The seminars lead users through the process of modeling network topologies, running Studies, interpreting results, and understanding the software methodology.

Seminars are held several times each year in Manhattan Beach, California. Enclosed in this PTW package you will find a schedule and an enrollment form detailing specific seminar dates for the current or upcoming calendar year. If you would like to attend a seminar, return the enrollment form to SKM.

If your company has a large number of Power*Tools users and would like to arrange an on-site class, please call SKM for further information at (310) 372-0088 or check our web site at www.skm.com.

Limitations Power*Tools for Windows has the following constraints:

PTW-Light 50 Bus, 150 total Components

PTW/50 50 Bus, Unlimited Components

PTW/100 100 Bus Unlimited Components




Demand Load Study Radial Systems Only

Note: While the Demand Load Study requires a radially-configured system, PTW automatically inspects for looped systems, temporarily opens the loops to perform the analysis, then closes the loops again. The entire process is invisible to the user.

Load Schedule Reporting Radial/Loop Systems

Sizing Study Radial/Loop Systems

Load Flow Study Radial/Loop Systems

Short Circuit Study Radial/Loop Systems

A maximum of ten independent power systems can be examined with all Studies, except for the Short Circuit Study, which can examine any number of independent power systems.

The Load Schedule Reporting limits the maximum number of connections to any one load center to 42. If more than 42 connections exist, it is recommended that two buses be created and named Section 1 and Section 2. The two sections can be connected by a low impedance cable, since there must be some impedance between two buses.

UG xvi User's Guide

8/16/2006

Contents UG xvii


This page left blank.


1 Introduction

We know you’re anxious to get started, and we are too. But before jumping into Power*Tools for Windows, we recommend that you take the time to read this chapter. It will familiarize you with some of the main Power*Tools for Windows (PTW) terms and concepts, show you main functions and environments, and help make your first experience more productive.

After reviewing this section, we recommend the tutorial as a great place to start. It takes you through a sample Project step by step, showing you all of the important stops along the way to completing your Studies and One-Line Diagrams.

IN

TH

IS

CH

AP

TE

R

1.1. Installing PTW.................................................................................................. 1-2 1.1. UnInstalling PTW............................................................................................. 1-2 1.2. Projects ............................................................................................................. 1-2 1.3. Components and Attributes .............................................................................. 1-4 1.4. Queries.............................................................................................................. 1-5 1.5. Libraries............................................................................................................ 1-6 1.6. Studies .............................................................................................................. 1-7 1.7. Reports, Datablocks and Crystal Report........................................................... 1-7 1.8. Compatibility with Power*Tools for DOS ..................................................... 1-11 1.9. Sharing Data with Other Applications............................................................ 1-11 1.10. On-Line Help ................................................................................................ 1-12

UG 1-2 User’s Guide

8/16/2006

1.1. Installing PTW

For installation instructions, please refer to the separate instruction sheet that came with PTW.

You should refer to the separate sheet that came with PTW because it contains information specific to the hardware or software key that came with the program.

The general procedure for standalone computers, though, involves these steps:

1. Run the Setup program from the CD.

2. Run the Key Utility program.

• You will be prompted at the end of the CD installation regarding whether you want to run the Key Utility program. You only need to run the Key Utility program for first time installation. The Key Utility program can also be accessed from Start>Programs>Power*Tools for Windows>Key Utility.

If you are installing PTW on a network and cannot find the separate instruction sheet, please contact SKM or retrieve it from the PTW CD.

1.1. UnInstalling PTW To uninstall PTW, just click Start>Programs>Power*Tools for Windows>Uninstall. Any Projects and Libraries that have been modified will not be deleted. Also, the font files installed by PTW (Fences, MT Symbol, MT Extra, PIXymbols Extended, and PIXymbols Extended Bold) will not be deleted.

1.2. Projects Whenever you work in PTW, you work on a Project. A Project is the total electrical system you create in PTW⎯the buses, cables, transformers, motors, transmission lines, and other electrical components. At times you might want to view only a portion of the electrical system (you might focus on a single branch of a One-Line Diagram, for example), or you might view the Project in one of PTW’s various formats⎯in Report form, in One-Line Diagram form, in list form via the Component Editor⎯but the Project itself never changes, for it always contains the complete electrical system. Thus, if you destroy a motor from the Project’s Component Editor, it will also be destroyed from the Project’s One-Line Diagram, since the One-Line Diagram accesses that same system.

The One-Line Diagram and the Component Editor represent the primary editing environments in PTW. In either of these environments, components can be added to, connected to, or deleted from the Project; the primary difference between the editing environments is the user interface. The One-Line Diagram works visually; with it, you can create electrical systems by moving component symbols onto a drawing area and

Introduction UG 1-3


connecting them to form your network topology. The Component Editor is tabular, displaying component data in a dialog box. As described above, both editors access the same Project and are therefore completely interactive. But what about consistency? What happens if you delete a motor from a Component Editor? Will it still be on your One-Line Diagrams? The really nice part about PTW is that the Component Editor and all One-Line Diagrams keep an active link to the Project Database, as shown in the following picture:

ProjectDatabase

Live Data Link

The One-Line Diagram The PTW One-Line Diagram is a visual design environment for building a classic one-line diagram, but is much more powerful. One-Line Diagrams are not simply drafting tools in PTW, but actual modeling tools that you can use to build your power system and analyze the results. You create a network topology by simply selecting component symbols from a toolbar, and moving them onto the drawing area. To connect components, drag lines between them. You can also expand and collapse portions of the one-line, which is particularly helpful when you’ve added components in the Component Editor and want to see them automatically displayed on the One-Line Diagram.

This method of building the network simultaneously creates a network one-line diagram, and establishes component records and connections in the Project. So when you add a component to a One-Line Diagram, that component is immediately available from the Component Editor.

. While working in the One-Line Diagram, you can switch to the Component Editor at any time. PTW’s accelerated link lets you switch to the Component Editor by simply double-clicking the component you want to edit.

To add a component to the One-Line Diagram, click it on the toolbar. . .

. . .and place it on the One-Line Diagram area.


8/16/2006

For a detailed description of the One-Line Diagram, refer to the “One-Line Diagrams” chapter.

The Component Editor The Component Editor is a dynamic dialog box used primarily for entering or changing the attributes of electrical components. For instance, if you’ve created a synchronous motor using the One-Line Diagram, you can enter detailed component data using the Component Editor.

In the Components box, you can select the component you want to look at, and the corresponding data appears on the right. Some components have more than one “page” of data, and each page of data is referred to as a subview. Above the list of components is a list of subviews available for that component type. To switch to a different subview, simply select the new subview from the list.

Components can be added to and deleted from the network using the Component Editor, and PTW simplifies this task by transferring data from connected components to the new component. For example, if you attach a new motor to an existing bus, that motor picks up the bus voltage automatically.

The Component Editor also controls the link to your library data. Simply select the cable or transformer key you want to use for that component, and PTW imports the data.

For a detailed description of the Component Editor, refer to the “Component Editor” chapter.

1.3. Components and Attributes The terms components and attribute refer to the data which you work with in the Project. A component is the smallest totally discrete unit of data that the Project holds. An attribute is a characteristic or property of the component.

Choose the subview you want to see from the available list...

...and detailed data for the selected components are shown on the right.

Components are displayed in the components box.

Introduction UG 1-5


Components The smallest discrete physical or theoretical unit of a Project is called a component. Components include such electrical devices as cables, transformers, motors, generators and transmission lines; and such theoretical entities as pi equivalent impedances, loads, and buses. One Project can contain hundreds or even thousands of components.

Attributes Each component contains certain characteristics such as length, rated voltage, and so on. The characteristics belonging to a component depend upon the component type. For example, cables have a length associated with them, but induction motors do not. All of these characteristics are called attributes, and attributes are stored with the component, so that each component can be thought of as a single object comprising a collection of attributes.

1.4. Queries If you’ve ever worked with a computer database, you are probably familiar with the term “query.” In its most fundamental sense, a query is a limiting function that compares all of the records in a database to a set of user-defined criteria, and displays only the records that meet those criteria. In a customer database, for example, you might a want list all clients who live in Texas, or who have a particular product. These data can be searched because of the way that the database organizes information.


8/16/2006

The PTW Project is no different. Each component in the Project represents a single object (and a component can be a literal component, like a motor, or a theoretical component, like a pi equivalent impedance). Each of these components has associated characteristics such as voltage, length, kVA, and so on. PTW provides a sophisticated query function that lets you search on any of these characteristics, limiting your component list to particular kinds of components, or even a particular voltage range. For example, using a query, you can look at all large motors, three winding transformers, cables longer than 1000 feet, or almost any component you want. Additionally, once a Study is completed, for example the short circuit Study, you can build a query to list all buses with a fault duty greater than a pre-selected value. In fact, any data item for any component type can be queried.

The query function is available from both editing environments in PTW: the Component Editor and One-Line Diagrams, and the way in which results are displayed depends upon which is active.

When you first access the query dialog box, you will find several pre-defined queries that search on the most common criteria. You can also create your own queries with just a few mouse clicks, all of which make queries an extremely powerful tool.

For more information on queries, see the “Queries” chapter. See also the “Component Editor” and “One-Line Diagrams” chapters for information on how query results vary according to the editing environment.

1.5. Libraries As its name implies, a library stores standard reference data for a particular component type. You can use libraries to speed up the process of entering data for network components. For example, you may have a power system that contains several Aluminum 600V, 250 kcmil cables. Instead of having to type in all of the impedance, raceway and ground wire size data for each cable, you can use the Component Editor to pick the cable library component you want, and PTW automatically fills in the rest of the data for you.

Select the query you want to run...

... and click the Run button.

You can also edit queries, or create custom ones.

Introduction UG 1-7


You can also edit any library data and add new components to meet the needs of your particular system. By customizing your libraries, the data more exactly models your system and provides consistent values for the best possible calculations.

You can also create multiple libraries for use within the same Project or different projects. For example, you may make changes to the library for each particular Project, to reflect international standards, or you may be working on a joint Project with a colleague sharing libraries. You can change your library and PTW updates your components so that your data is current and accurate at all times. By customizing and maintaining different libraries, you have tremendous power and flexibility to interchange the libraries within the same Project or between different projects.

For more information on libraries, see the “Libraries” chapter.

1.6. Studies Studies are the heart of PTW: they analyze and evaluate your network and generate report results for the load flow, voltage drop, demand loads, and so on. Since each has its own procedures, specific usage is discussed in the Reference Manual for that Study.

1.7. Reports, Datablocks and Crystal Report After you run Studies, you have access to a tremendous amount of information, and you can look at that information in different ways to meet specific needs.

PTW provides three principle methods of looking at your Study data: reports, datablocks and Crystal reports.

1.7.1. Reports Each Study type generates a pre-formatted ASCII text file report that presents an in-depth analysis of your entire system. PTW automatically generates a report for every Study you run. You decide what the reports are named and where they are stored. Note that reports


8/16/2006

are not linked interactively to the Project: each report represents a snapshot of your system at a moment in time, but will not change as you change system parameters.

Because reports are standard ASCII text files, you can open them in PTW’s built-in text editor, or in most popular word processing programs. Once opened, you can edit reports as you would any other text file.

Reports typically run to several pages in length, and can be used for presentations and system-wide troubleshooting. But they may not always be the best format for finding very specific data, or for analyzing the Study results on a particular component. For this reason, you can also see your input and output data in datablocks. For more information on reports, see the “Reports” chapter.

1.7.2. Datablocks Datablocks keep important Project data at your fingertips. Using datablocks, you can set up and view component attributes in a unique format for each component type, and save each named format in a datablock file. For instance, you can set up a datablock that displays the connected kVA and the connected power factor for cables. The datablock formats can consist of any component attributes you want to include. They may consist of input data, output data, or a combination of both.

You can create as many named datablock formats as you want, each of which can be very simple or extremely complex. One datablock format might include a few data for buses alone, whereas another might include several data items for each available component type.

For more information on formatting datablocks, see the “Datablocks” chapter.

Introduction UG 1-9


You can view datablock formats in the datablock subview of the Component Editor or on a One-Line Diagram. You have two options for viewing datablocks on a One-Line Diagram. First, by using the probe, you can click on any component and see its datablock in a temporary popup window. Second, you can view all datablocks on the surface of the One-Line Diagram, and move them as discrete objects.

Datablocks may also be printed in a special report called a Datablock Report. These provide extreme power and flexibility because you can include whatever data you want about each component.

Select the attribute you want to include in the datablock.

Datablocks on the One-Line Diagram ....

You can select the component type for which you want to create a datablock ...

... in the Component Editor ...

. . .and adjust the display format so that it’s just as you want it to appear on the screen.

... in the One-Line Diagram probe.


8/16/2006

Each of these datablock locations can be assigned different datablock formats: you can look at load flow data in your Component Editor, while looking at demand load data in the One-Line Diagram.

1.7.3. Crystal Reports Crystal Reports provide an alternative method for viewing input data and output results. A Crystal Report is similar to a Datablock report since it reads data from the project database, however the Crystal Reports can include sophisticated formatting for professional tabular output. The custom report formats can contain multiple fonts and bitmaps, page orientation specifications, query support and can be exported to a variety of popular formats.

Crystal Report Sample

For more information on Crystal Reports, see the “Crystal Reports” chapter.

... and in a Datablock report spreadsheet format

Introduction UG 1-11


1.8. Compatibility with Power*Tools for DOS Using Import, a separate program that comes with PTW, you can convert an existing Power*Tools for DOS projects and/or libraries into the PTW format in a matter of minutes. You don’t have to re-enter your data, or re-define connections; Import takes care of that for you. You are then ready to run Studies immediately. After you import your Project, you can use the Expand command in a One-Line Diagram to automatically generate your one-line branch by branch. See the “Import chapter” for more information about importing DOS Projects.

1.9. Sharing Data with Other Applications Throughout the life of a Project, you may want to show your Project data to a number of people in the forms that they can best understand, assimilate and use. And different colleagues will want to see your data from different perspectives, and for different reasons. To make all of these parties happy, you may need to manipulate your data using a variety different applications.

PTW puts a premium on connectivity and communication, giving you several different ways to use Project data, reports and One-Line Diagrams in other programs. PTW makes it easy to use your data in spreadsheets, word processors, databases, presentation packages and so on. Using these and other applications you can create charts, graphs, slides, and complete component lists based on your projects. PTW provides flexible import and export capabilities for project data.

Understanding the reporting and export options provides many new uses for your existing Project data: clarify your specification sheets with charts and graphics; make concise lists of all needed equipment, and quickly summarize total electrical power requirements.

1.9.1. Edit and Print Reports in Word Processors Reports are saved in an ASCII text format, and can be opened by virtually all word processors for editing, formatting, adding text or graphics and so on. This makes it easy to add report data to presentations, or handouts. We’ve even included a True Type font called PIXymbolsExtended, which provides special characters for printing lines and borders. This is the same font we use in the PTW Report Editor, and because it is True Type, it is available to all Windows applications. So what you see is what you get, even across applications.

Report

With PTW’s Reports and the PIXymbolsExtended True Type font, it’s easy to use report files in my favorite word processor. All I have to do is open up the file, change the font to the PIXymbolsExtended, and presto! instant PTW report, formatted and ready to go. From there, I can incorporate it into reports, presentations — any type of document I need.

Not only that, but the report itself is all native text, so if I want to cut a part out of the report, it’s no problem. Of course, I can use all the bells and whistles included with my word processor including word wrapping, tables, and other advanced layout functions.

I can now do things with my report data that I never

P


8/16/2006

1.9.2. Export One-Line Diagrams for Graphics and CAD Programs When you’re ready to make that big presentation, a picture says a thousand words. That’s why our One-Line Diagrams and TCC drawings can be exported either to the Windows Metafile (WMF) or the AutoCAD DXF file formats. If you have any experience with Windows graphics packages, you know how useful and flexible these formats are. Use them in presentation packages for slideshows, illustration packages, CAD programs, and word processors.

1.10. On-Line Help All of the information contained in the printed manuals can be accessed in electronic form from within the PTW program. This electronic documentation is referred to simply as Help (or On-Line Help to distinguish it from printed documentation). You can access Help in two ways: from the Help menu in PTW, or using a “context-sensitive” method.

Fast tips are available at all times in the PTW interface. Fast tips are small floating messages that show you helpful messages about the toolbar buttons. To get a fast tip on a button, point to it; after a moment, the tip appears in a small temporary window directly beneath the pointer.

To find out more about the parts of the PTW screen, you can click the Context-Sensitive Help button on the toolbar and then click the part of the screen you’re interested in. A related help topic window will appear. You can also browse the help system by choosing Index from the Help menu.

To see all the help topics, click the Help>Help Topics command and the on-line help appears. From there you can use the hyperlinks to browse through the available topics.

One-Line Diagrams can be imported into most graphics-based applications, like the presentation package shown here. Also place them in CAD programs, word processors, and illustration programs.

Introduction UG 1-13



SKM Power*Tools for Windows0

2 Getting Started

This chapter describes the main parts of PTW, using the on-line help system, and how to get started using the program.

This chapter discusses:

• Starting PTW: Stand-Alone.

• Starting PTW: LAN Users.

• Working with projects.

IN

TH

IS

CH

AP

TE

R

2.1. Starting PTW: Stand-Alone............................................................................. 2-2 2.2. Starting PTW: LAN Users............................................................................... 2-2 2.3. Global Options.................................................................................................. 2-4 2.4. Working with Projects ...................................................................................... 2-7 2.5. Working with Menu Commands..................................................................... 2-15 2.6. Working with the Status Bar........................................................................... 2-23 2.7. Working with Toolbars................................................................................... 2-23


8/16/2006

2.1. Starting PTW: Stand-Alone To run PTW, just click Start>Programs>Power*Tools for Windows>PTW32.

Tip: By default PTW automatically opens the most recently accessed Project on startup. If you prefer, you can instruct PTW not to open a Project. Refer to Section 2.3.1, “Setting Startup Options” for information and instructions.

2.2. Starting PTW: LAN Users If you are not using the Local Area Network (LAN) version of PTW, skip to section 2.3.

In a network environment, PTW is administered from the NetHASP Server and hardware key that your administrator installed on the file server. The NetHASP Server keeps track of the Studies that are available in your copy of PTW, and how many users are currently logged in to the software. This means that when you start PTW you will be required to log in.

As with the stand-alone version of PTW, log in by clicking Start>Programs>Power*Tools for Windows>PTW32.

PTW displays the PTW Network Login dialog box which you use to log in to PTW.

Click here to start PTW.

Click here to start PTW.

Getting Started UG 2-3


Using this dialog box, you can request login permissions for the Studies you need to run during your upcoming session. Logging in to PTW judiciously is very important, because Studies have to be shared among all of the users on the network. For example, your copy of PTW may be licensed to run three copies of DAPPER Studies and two copies of CAPTOR Studies. Every time a new user logs onto PTW, some of those permissions are used, and when all of the permissions have been used, no further copies of the program can be run. Therefore, you should request permission only for the Studies that you know you will need.

To log in to PTW

1. Under PTW Studies, select only the Studies you need to run during the current PTW session. These Studies vary according to the software license. If you do not select any of the Studies, you can still log on to PTW to examine One-Lines, network layout, and so on.

2. If you want to use the current settings for later logins without having to go through this dialog box each time you start PTW, select the bottom check box.

3. Click the OK button. This starts PTW and assigns the permissions you requested. If one or more of the Studies you requested are unavailable, PTW issues a message stating which Studies are not available.

After you log in, PTW processes the requests and sends them to the file server. If there is any problem with the network configuration or the NetHASP Server installation, PTW issues an error message. If there is an error, contact you network administrator.

2.2.1. Changing Permission Status During a PTW Session As you run PTW, you may find that you would like to run a Study that you did not request permission for when you logged in. Rather than having to close the program and log in again, PTW lets you change your permission status while you are running the program.

You can also use this procedure to free Studies that you no longer need so that other network users can have access to them.

Select this check box to use these settings for subsequent logins.

Select the Studies you want to use in your PTW session.


8/16/2006

To change the PTW Permission Status

1. Click the Project>Login command. PTW displays the PTW Network Login dialog box.

2. Select or clear the appropriate check boxes.

2.2.2. Logging Out of PTW To log out of PTW, simply close the application as you would in a regular standalone installation; the network software automatically frees the appropriate Studies and makes them available to other users.

2.3. Global Options Each time you start PTW, the program references global options for instructions on automation and technical standards. Global settings always apply to the active Project, so you should check these global options each time you begin a new Project.

2.3.1. Setting Startup Options Startup options control PTW’s level of automation during startup. These settings are not critical to operation, and you can set them according to preference.

Opening the Most Recent Project Automatically By default, PTW opens the most recently saved Project. You can leave the default the way it is, or instruct PTW to open no Project on startup.

To change the Project recall setting

1. Click the Project>Options command.

2. In the Option Groups box, select Startup.

3. Do one of the following:

• If you want to open the most recently saved Project on startup, select the Open Most Recent Project option button.

• If you do not want to a Project on startup, select the Do Not Open a Project option button.

Enabling the Pentium™ Warning By default, PTW enables a warning that notifies you if it finds a faulty Pentium processor in your computer. You can disable this warning at any time.

Early Intel® Pentium processors (manufactured through the beginning of 1995) contain an error in the floating-point division section of the chip that causes them to miscalculate certain mathematical computations. At startup, PTW sends a small computation known to cause such an error to your computer’s processor. If the processor returns the wrong answer, PTW alerts you that your computer has one of the faulty chips.

It is difficult to determine the impact of a faulty Pentium processor on your Project results. In many calculations, there may be no error. In cases where errors occur, some may be



negligible, while others may be magnified through the multiplication of arrays. Intel has since corrected the problem and if you get this error you should replace the faulty processor with a new one.

2.3.2. Setting Application Options Application options control the display standard (ANSI or IEC), the base system frequency, and the units or distance measurement (English or Metric) for data entry in the active Project. These settings are very important for proper operation of PTW. Typically, once you set them you won’t change them, but in some cases you may want to use alternative standards.

Setting the Display Standard PTW stores default symbols and setting for ANSI and IEC engineering standards. PTW also has the flexibility to be modified to work with almost any local or national standard. Storing two sets of defaults makes it easier to switch between standards.

Setting the System Frequency PTW allows you to specify 60 Hz, 50 Hz or any other custom frequency for the project. Impedance values referenced from the library are automatically adjusted for different operating frequencies.

Setting the Units of Measurement When you select an engineering standard, you should also select a unit of measurement. Typically, ANSI projects use English units and IEC projects use metric units. However, PTW does allow you to change the units independently of the engineering standard. Because the units of measurement are tied closely to engineering standard, PTW issues a warning if the standard and units are “mismatched” (that is, ANSI and metric or IEC and English). Note, however that this warning is issued only to make sure that you have not selected the combination by accident. There is nothing technically wrong with the selection.

Setting Event Message Options PTW informs you of various program events using written messages, color and sound. The events that PTW responds to are: “errors,” “warnings” and “success.” An error is defined as topology or Study error severe enough to prevent the program from continuing. For instance, failing to enter the length of a cable produces an error. Warnings are less severe problems that may or may not affect PTW’s proper operation in the future, and are flagged so that if they are unintentional, you can fix them. Success events happen after the successful completion of certain complicated tasks such as running Studies.

PTW uses sounds to indicate warnings, errors, and some completed operations. You can turn these beeps on and off as you choose.


8/16/2006

Select or clear the check box in this group

To enable or disable sound for this event

Error Errors: Fatal errors that prevents PTW from continuing.

Warning Warnings: Less severe errors that may or may not impact PTW functioning.

Success Successful operations: Studies completed, and so on.

The PTW events correspond to standard Windows events, meaning that you can assign custom sounds to them using the Windows Control Panel. Using this technique, you can play chimes at the completion of Studies, sound a buzzer at an error, and so on. Note that the following procedure affects not only PTW sounds, but all of the corresponding Windows sounds, so the sounds you choose will be consistent across all Windows applications.

In addition to sounds, PTW also posts written messages in the status bar at the bottom left of the screen. You can change the colors in which the error and warning messages are displayed. These messages appear in the status bar at the bottom of the PTW screen.

To set event message color options


2. In the Option Groups box, select Application.

3. Under Error or Warning, do one or more of the following:

Choose this button To set this color Background The background of the status bar message.

Foreground The foreground of the status bar message (that is, the text of the message).

4. In the Colors dialog box, choose the desired color.

5. Click the OK button to return to the Options Dialog Box.

6. Repeat steps 3 and 4 for other colors you want to set.

7. Click the OK button.



2.4. Working with Projects A Project is your most fundamental work environment; it identifies your network topology, data and One-Lines. After starting PTW, you will typically open or create a Project.

2.4.1. Creating a New Project You can create a new Project at any time. Before creating a new Project, be sure to close the active Project (if any). After you create a new Project, PTW opens the Component Editor and a creates a blank One-Line Diagram so you can start work immediately.

Since each Project represents a unique electrical system, each Project must be given its own Project name. PTW gives this Project file the extension .PRJ. If you name a Project FACTORY, for example, the resultant file will be called FACTORY.PRJ. You may open only one Project at a time in PTW, and each Project must be located in its own folder. PTW will facilitate this necessity by automatically creating the folder. For example, if you have all your Projects in a folder called WORK, and within the WORK folder you have saved three Projects called FACTORY, TEST, and MACHINE, there will actually be three folders within WORK: one called FACTORY, one called TEST, and one called MACHINE. Within each folder will be the Project itself, so that within WORK\FACTORY will be FACTORY.PRJ (the actual Project file), within WORK\TEST will be TEST.PRJ, and within WORK\MACHINE will be MACHINE.PRJ. All other files associated with that Project (such as Report files, and PTW’s internal data files) are saved in the Project’s folder. For example, a Load Schedule Report file (which might be entitled LS.RPT) run on the FACTORY Project would be located in the WORK\FACTORY folder.

Warning: Each Project must be located in its own folder. If you combine multiple projects in one folder, or if you move some of the files to another location, you will seriously corrupt your Project and you will lose data. If you want to move a Project using DOS or the File Manager, be sure to move the entire Project folder.

For further information on backing up projects, see Section 2.4.8, “Backing Up Projects.”

Type the name of the new Project.

PTW automatically adds a Project folder to the path you select. This folder has the same name as Project.


8/16/2006

To create a new Project

1. Click the Project>New command. The New Project dialog box appears.

2. In the Project Name box, type the name of the new Project.

3. In the box below Project Path, select the drive and path for the Project.

Notice that under Project Path, PTW shows the path to the new Project including the new folder that it will create, which has the same name that you typed in for the Project (step 2).

4. Click OK to create the Project folder and the new Project.

2.4.2. Building the Electrical System in a Project To build an electrical system in PTW, you first connect the topology using the One-Line Diagram, then enter data (such as bus voltage, rated size, cable length, and so on) using the Component Editor:

• The Component Editor is a dynamic dialog box in which you can create and edit components. Along with the One-Line Diagram, the Component Editor represents one of the primary network editing tools in PTW. You can open only a single instance of the Component Editor.

• A One-Line Diagram looks, feels and acts like any CAD-based one-line diagram, but it is in fact an interactive drawing with direct links to the Project database. You can build a network using a One-Line Diagram, or create interactive one-line diagrams for existing projects, complete with system and Study data.

See the Component Editor and One-Line Diagram chapters in the User’s Guide for more information on each.

2.4.3. Opening an Existing Project PTW keeps track of your most recently opened projects. You can open any of these projects by choosing it from the projects listed at the bottom of the Projects menu.

You can also use the Open command from the Project menu to open any existing Project.

To open one of the most recently accessed projects, choose the Project you want from the bottom of the Project menu.



When you open an existing Project, PTW opens an “All Components” Component Editor that contains all of the existing system components. All of your Project options are retained from the last time you saved the Project.

To open an existing Project

1. Click the Project>Open command. The Open Project dialog box appears.

2. In the Drives box, select the drive where the Project is located.

3. In the Directories box, select the directory where the Project is located.

4. In the Project Name box, type the name of the Project, or select the name of the Project from the list.

5. Click OK.

2.4.4. Copying Projects While working on a Project, you may want to save that Project at a particular stage of development, or create a slightly different Project to represent another operating condition. Using the Copy As command, you can copy the active Project, give it a new Project name, and save it to any location. As with new projects, each copied Project must be located in its own folder, and PTW automatically creates a folder for copied projects.

Except for location and name, the copied Project is in all ways identical to the original Project. It contains all of the same Project data and references the same libraries as the original.

Important: This command is intended to represent your system at a moment in time; it does not copy the libraries you need to recover the entire Project in the event of data loss or corruption, and should not be used as a backup function. For instructions on backing up projects, refer to Section 2.4.8, “Backing Up Projects.”

When you copy a Project, you continue to work with the original Project. This distinguishes the behavior of the Copy As command from a typical Save As command. For example, if you are working in a Project called Project 1, and make a copy called Project 2, after the copy is made you continue work in Project 1. Of course, you can switch to Project 2 at any time, only recognize that switching to the copied Project is not automatic.

Select the drive and directory where the Project is located.


8/16/2006

To copy a Project

1. Click the Project>Copy As command. The Copy As Project dialog box appears.

2. In the Project Name box, type the name of the Project copy.

3. Under Project Path, select the drive and path for the Project. Notice that under Project Path, PTW shows the path to the copy including the new folder that it will create, which has the same name that you typed in for the Project (step 2).

4. Click OK to create a folder, and save a copy of the active Project into it.

2.4.5. Closing Projects When you close the active Project, PTW automatically closes the Component Editor and any open One-Line Diagrams. If any of these One-Line Diagrams has not been saved, PTW asks you if you want to save changes before continuing. Component data are saved automatically, but changes to the one-line diagrams are saved only when instructed to do so.

Libraries and reports remain open because they are not interactively linked to the Project. You can continue to work in them and close them independently when you have finished.

To close the active Project

1. Click the Project>Close command.

2.4.6. Deleting Projects Projects can be large, and from time to time you may need to delete some older projects to free up space on your hard drive. Deleting projects permanently erases the Project directory from your hard drive including setup data, network topology data, One-Line Diagrams and any other files located in that directory. The libraries referenced by the Project are deleted if they are located in the Project directory, otherwise they remain intact for use by other projects. You must close the active Project before deleting a Project.

Before deleting a Project, we strongly recommend that you make a backup copy onto a floppy diskette or any archiving medium in case you need it in the future. For information on backing up projects, refer to Section 2.4.8 “Backing Up Projects” later in this chapter.

Type the name of the Project copy.

PTW automatically adds a Project folder to the path you select. This folder has the same name as the Project.



Warning: Deleting projects is permanent! Once your Project has been deleted, it is not recoverable. You should delete projects only after you have created a backup copy.

To delete a Project

1. Click the Project>Delete command.

2. In the File Name box, type or select the Project you want to delete.


2.4.7. Getting Project Statistics PTW keeps track of important Project statistics, and you can review them at any time. Information available in the Project Statistics dialog box includes the Project name, the data created and the data last edited, as well as component information such as the number of buses, branches and synchronous generators in the system. The Project statistics apply only to the active Project; the following procedure assumes that a Project is active.

To get Project statistics

1. Click the Project>Statistics command. The Project Statistics dialog box appears.

2. When you have reviewed the statistics, Click the OK button.

2.4.8. Backing Up Projects Hardware crashes of one kind or another are all too common in computer systems, and unless you prepare for them in advance they can represent a significant loss. To prevent costly data loss, you should periodically make complete Project backups. We also recommend that you keep a backup copy of older projects that you no longer want to store on your hard drive.

Tip: When working on a Project, especially one that is large or being edited heavily, you should make a backup copy of that Project daily or more frequently.

To make a complete Project backup, you need to copy all of the files necessary to restore the Project and reproduce the same results generated by the original; that means your Project and your libraries. You should not use the copy Project function as a backup function because it copies only the Project database, not the library files. If you want to make a copy of the Project rather than a complete Project backup, refer to Section 2.4.4 “Copying Projects” earlier in this chapter.

A complete Project backup includes:

• All of the files in the Project directory.

• All of the referenced libraries.

To back up a Project

1. Click the Project>Backup command.

2. Choose a location to back the project up to.


8/16/2006

2.4.9. Merging Projects The merge project function allows you to merge two projects in to one. The project merge does not allow duplicate component names. During the merge, if both projects contain a component with the same name, you will be prompted to rename or skip the duplicate component.

2.4.10. Exporting Projects With PTW’s export function, you can export your active Project to an ASCII text file. An ASCII file is a highly compatible data file that you can import into several different kinds of applications including spreadsheets, word processors, and databases. In fact, almost all applications that import data support ASCII files. Using other applications, you can use your PTW Project to create charts, graphs, presentations, complete component lists, and much more.

The ASCII file is divided up into sections according to component type: one section for cables, one for buses, and so on. After the ASCII file has been exported, you can edit and print it as you would any other text file.

To export a Project

1. Click the Project>Export command.

2. If you want the first row of data to include descriptive names, check the First Row Contains Field Names box.

3. Set the text and field delimiters you want. See “Choosing Export Options” later in this chapter for help with these options.


5. In the File Name box type the name of the ASCII file.


The ASCII file is created and saved to the directory you specified. When the file has been exported, you can edit it to suit your needs.

Tip: Each component type has its own, clearly marked section in the ASCII file. If you want, you can delete any sections you are not interested in. For example, if you only wanted information pertaining to cables, you could use a text editor to delete the other sections from the file.

Check here to have PTW write out field names at the top of each column.

Type or select your text and field delimiters.



Choosing Export Options The Export Project dialog box lets you pick settings for your ASCII file, each of which affects the file configuration. The key to determining how to adjust these settings is to determine requirements of the application into which you will import the Project (the target application). When in doubt, consult the target application’s documentation for specifics. The following paragraphs indicate how the settings are used.

• Field Names: Include field names to identify the data in the column beneath. For example, you may export a column of component names. If you check this option, PTW includes a field at the top of the column that says “Component Name.” If you do not check this option, the first row would start with the first component name, for example “Bus_0001.” The names that PTW uses are assigned by the program and cannot be modified. Of course once the ASCII file has been exported, you can use another application to change the column names.

• Text delimiter: The target application needs to know which fields contain text strings and which contain numerical data, because it treats these data types differently when it imports. If the application thinks that a field contains a number when it actually contains text, it may discard embedded spaces and special characters, or may not be able to import the file at all. Most applications require double quotation marks (“), but when in doubt, consult the destination application for instructions on setting this option.

• Field separator: Many applications require a particular character to separate the fields of data from each other. For example, if the destination application requires a “tab delimited” ASCII file, you would select {tab} in this box.


8/16/2006

PTW uses the settings to determine the configuration of the ASCII file.

=======Bus===== ComponentName InService New/Existing NomSysVoltage LFVoltage LFVoltageAngle ConstantKVALoad ConstantKVALoadPF ConstantZLoad ConstantZLoadPF ConstantCurrentLoad ConstantCurrentLoadPF ConnectedLoad DesignLoad DesignLoad Size Units¶ “001-GEN NO. 1” “In” “Existing” 480.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0¶

Tip: If you only need a small number of data fields for each component such as cable size, length and quantity/phase, create a datablock report rather than exporting the entire project. The datablock reports can be saved as Excel files and converted to other formats.

2.4.11. Database Utility The database utility option provides functions to re-index, and recover corrupted project or library database files. All project and library data files must be closed for the Database Utility option to be used.

2.4.12. Compress Library The compress library function removes empty space in the library database. When library components are deleted, they are removed from the list but the space is not freed until the library is compressed. This function may take several minutes.

Field Name — If this setting is checked, the entire first record is made up of descriptive names . Field Separator — In this case a tab

(displayed as an arrow in this sample).

Text Delimiter — In this case, double quotation marks.



2.5. Working with Menu Commands Following is a summary of the PTW menu commands.

Project Document Edit View Run Component One-Line Window Help

New... Open... Close Copy As... Backup Statistics... Delete... Export... Merge... Database Utility... Compress Library… Options... Ctrl+O Login... 1 C:\PTW32\...\PLANT\PLANT.PRJ Exit

This menu command Performs this function New... Creates a new Project.

Open... Opens an existing Project.

Close Closes the active Project.

Copy As... Creates a backup of the Project.

Backup... Makes a copy of all project and library files necessary for you or someone else to use the project files in the future.

Statistics... Lists the Project statistics.

Delete... Deletes a Project.

Export... Exports a Project to an ASCII text file.

Merge... Merges data from another project into the open project.

Database Utility... Re-indexes and may recover corrupted project files. This feature is only available when no projects are open in PTW.

Compress Library… Options...

Removes empty space from library database. This feature is only available when no project or library is open in PTW.

Changes PTW’s global options.

Login... Logs in or out of a Study. Applicable only when using the network version of PTW.

1, 2, 3, 4... Opens any of the last eight most recently accessed projects. Exit Closes PTW.


8/16/2006


Component Editor One-Line... Report... Library... CAPTOR TCC... Crystal Report Close Save Ctrl+SSave As... Export... Print Setup... Print Layout... Print... Ctrl+PPrint Preview Form Print Form Preview Ctrl+SForm Layout 1 C:\PTW32\...\MAINDRAW.DRW

This menu command Performs this function Component Editor Opens the Component Editor.

One-Line... Opens an existing One-Line Diagram or creates a new One-Line Diagram.

Report... Opens an existing Report or creates a new Report.

Library... Opens an existing Library or creates a new Library.

CAPTOR TCC... Opens or creates a Coordination Drawing.

Crystal Report Opens a Crystal Report template and displays selected project data.

Close Closes the active document window.

Save Saves the active document window.

Save As... Copies the active document window; renames the document; and/or saves it to a new location.

Print Setup... Sets printing options.

Print Layout... Sets printing layout. Active only when a One-Line Diagram is open. Reports use preset formatting.

Print... Prints the active window. Active only when a One-Line Diagram, TCC, or Report is open.

Print Preview Displays the window as it will actually appear when printed. Active only when a One-Line Diagram, TCC, or Report is open.

Form Print Prints single or multiple documents in custom formats. An example would be to print a TCC drawing with a small one-line, titleblock and Company logo.

Form Preview Displays the selected documents in the selected form on the screen prior to printing.

Form Layout Allows you to create and edit custom output formats used by the Form Print command.

1, 2, 3, 4... Opens any of the last eight most recently accessed One-Line Diagrams, Reports, TCCs, or Libraries).



This menu command Performs this function Project Document Edit View Run Component One-Line Window Help

Cut Ctrl+X Copy Ctrl+CPaste Ctrl+V Delete Text Del Select All Find... F5Find Next Shift+F3Replace... F6 Go to Line...

This menu command Performs this function Cut Cuts the selected data to the clipboard. Active only when a Report,

Library, or the Component Editor is open.

Copy Copies the selected data to the clipboard. Active only when a Report, Library, or the Component Editor is open..

Paste Copies clipboard text to the selected location. Active only when a Report, Library, or the Component Editor is open.

Delete Text Deletes the selected text. Available only when a Report is open.

Select All Selects all items. Available only when a Report or a One-Line Diagram is open.

Find... Finds specified text in a report and finds a specific component on a one-line.

Find Next Finds the next instance of the specified text. Available only when a Report is open.

Replace... Replaces text. Available only when a Report is open.

Go to Line... Moves to a specific numbered line. Available only when a Report is open.


8/16/2006


Toolbars... √ Status Bar Next Component Ctrl+Shift+N Previous Component Ctrl+Shift+P Next Subview Ctrl+Shift+X Previous Subview Ctrl+Shift+V √ TCC Device List √ Fixed Aspect Ratio √ Datablocks √ Probe √ Textblocks √ Protection Components Zoom In Ctrl+Z Zoom Out Ctrl+Shift+Z Zoom All Zoom Area Ctrl+Y Zoom Page Aerial Ctrl+Shift+A

This menu command Performs this function Toolbars... Displays or hides specific toolbars.

√ Status Bar Displays or hides the Status Bar.

Next Component Moves forward through the components in the Components box one at a time. Available only when a Library or the Component Editor is open.

Previous Component Moves backward through the components in the Components box one at a time. Available only when a Library or the Component Editor is open.

Next Subview Switches to the next subview. Available only when a Library or the Component Editor is open.

Previous Subview Switches to the previous subview. Available only when a Library or the Component Editor is open.

TCC Device List Displays or hides device list box on TCC setting page. The window size is smaller without the device list box. Available only when TCC drawing is active.

Fixed Aspect Ratio Forces the TCC drawing area to use square decades on log-log grid. Available only when TCC drawing is active.

√ Datablocks Displays or hides datablocks. Available only when a One-Line Diagram or TCC Drawing is open.

√ Probe Toggles the Probe mode on or off. Available only when a One-Line Diagram is open.

√ Textblocks Displays or hides textblocks. Available only when a One-Line Diagram or TCC Drawing is open.

√ Protection Components Displays or hides protective device symbols on the active one-line diagram. Available only when a One-Line Diagram is open.

Zoom In Enlarges the size of the One-Line Diagram. Available only when a One-Line Diagram is open.

Zoom Out Reduces the size of the One-Line Diagram. Available only when a One-Line Diagram is open.

Zoom All Shows the entire One-Line Diagram in the viewport. Available only h



This menu command Performs this function when a One-Line Diagram is open.

Zoom Area Magnifies a selected portion of the One-Line Diagram. Available only when a One-Line Diagram is open.

Zoom Page Magnifies the One-Line Diagram so that a single printer page fits within the viewport. Available only when a One-Line Diagram is open.

Aerial Shows a thumbnail representation of the One-Line Diagram. Available only when a One-Line Diagram is open.


Balanced System Studies... Ctrl+A Transient Motor Starting (TMS) Industrial Simulation (ISIM) Harmonic Analysis (HIWAVE) Unbalanced/Single-Phase Studies…Ctrl+U Reliability Analysis Equipment Evaluation Failed Input Evaluation Failed Equipment Evaluation Reset Color Query... Ctrl+Q Datablock Format... Ctrl+D Datablock Report...

This menu command Performs this function Balanced System Studies... Runs the standard suite of DAPPER balanced 3-phase study modules

Transient Motor Starting (TMS) Runs the transient motor starting simulation

Industrial Simulation (ISIM) Runs the ISIM transient stability simulation

Harmonic Analysis (HIWAVE) Runs the HIWAVE harmonic analysis calculations

Unbalanced/Single-Phase Studies Reliability Analysis

Equipment Evaluation

Failed Input Evaluation Failed Equipment Evaluation

Runs the Unbalanced 3-phase and Single-Phase Fault, load flow, sizing, load analysis and load schedule studies.

Runs the Reliability Analysis

Runs the System Evaluation comparing equipment ratings to study results

Performs a variety of input data checks including component connections, voltage continuity, and missing data and highlights failed devices on the one-lines and component editor.

Failed System Evaluation highlights components that failed the equipment evaluation study. The failed components are displayed in a different color on the one-line.

Reset Color

Query...

Resets the component colors after running the Failed Input or Equipment Evaluation.

Runs a Query.

Datablock Format Sets and applies a Datablock Format.

Datablock Report Creates a datablock report using the last applied datablock format.


8/16/2006


New Clone Copy Data Paste Data Destroy Remove Save As Default Select... Existing... Ctrl+I Expand Ctrl+E Collapse Ctrl+L Rename... Disconnect Ctrl+B In Service Out of Service

This menu command Performs this function New Adds a new component. Active only when a One-Line Diagram,

Library, or the Component Editor is open.

Clone Clones a component. Active only when a One-Line Diagram, Library, or the Component Editor is open.

Copy Data Copies data from a selected component to a temporary clipboard. Available only when a One-Line Diagram, TCC, or the Component Editor is open.

Paste Data Pastes data from the temporary clipboard to the selected components of the same type. Available only when a One-Line Diagram, TCC, or the Component Editor is open.

Destroy Destroys a component. Available only when a One-Line Diagram, Library, or the Component Editor is open.

Remove Removes a symbol from the One-Line Diagram. Available only when a One-Line Diagram is open.

Save As Default Select...

Saves the data from the selected component as the default data for new components.

Selects a specific component in the Library. Available only when a Library is open.

Existing... Adds a symbol for an existing component to the One-Line Diagram. Available only when a One-Line Diagram is open.

Expand Expands a component to display its connections. Available only when a One-Line Diagram or the Component Editor is open.

Collapse Collapses a component to hide its connections. Available only when a One-Line Diagram or the Component Editor is open.

Rename... Renames a component. Available only when a One-Line Diagram is open.

Disconnect Disconnects a component. Available only when a One-Line Diagram is open.

In Service Places a component in service. Available only when a One-Line Diagram is open.

Out of Service Takes a component out of service. Available only when a One-Line Diagram is open.




New Textblock... Textblock Attributes... Component Color Datablock Nametags Connection Points Annotation Annotation Line Style Symbol Rotation Convert to Bus Node Convert to Bus Symbol Selection Refresh Symbols from Library

This menu command Performs this function New Textblock... Creates a new textblock. Available only when a One-Line Diagram is

open.

Textblock Attributes... Edits a textblock. Available only when a One-Line Diagram is open.

Component Color Changes the color of selected components. Available only when a One-Line Diagram is open.

Datablock Turns the datablock display on and off for selected components. Available only when a One-Line Diagram is open.

Nametags Hides or displays the nametags for selected components. Available only when a One-Line Diagram is open.

Connection Points Hides or displays the connection point markers for selected components.. Available only when a One-Line Diagram is open.

Symbol Rotation Rotates selected symbols around connection point centroid. Available only when a One-Line Diagram is open.

Convert to Bus Node Converts selected Bus Symbols to Bus Node Symbols (a dot instead of a baar). The Bus Node also defaults to no nametag or datablock displayed.

Convert to Bus Converts selected Bus Node Symbols to Bus Symbols (bar instead of a dot).

Symbol Selection Replaces selected symbol with new symbol from the symbol library. Available only when a One-Line Diagram is open.

Refresh Symbols from Library Reads the symbol library and updates the symbols displayed on the one-line. Available only when a One-Line Diagram is open.


8/16/2006


New Window Close Cascade Tile Horizontally Tile Vertically Arrange Icons Close All Size Go To Component Editor Go To One-Line Go To TCC Drawing Go To TMS Go To ISIM Go To HIWAVE √ 1 Component Editor 2 INPUT.RPT

This menu command Performs this function New Window Opens a test copy of the Report or Library. Available only when a

Report or Library is open.

Close Closes the report window. Available only when a Report is open.

Cascade Arranges windows so they overlap.

Tile Horizontally Arranges windows horizontally so they do not overlap.

Tile Vertically Arranges windows vertically so they do not overlap.

Arrange Icons Arranges the minimized windows’ icons evenly across the bottom left of the workspace.

Close All Closes all windows.

Size Restores the Component Editor window to its standard dimensions. Available only when the Component Editor is open.

Go to Component Editor Opens the Component Editor and displays only the selected components. Active from One-Line Diagrams, TCC drawings, TMS, HI_WAVE and I*SIM study modules.

Go to One-Line

Opens the one-line associated with an open TCC drawing. Also returns to the one-line used to "go to Component Editor".

Go to I*SIM Transfers selected components to the I*SIM study interface. Used to graphically select machines, motors, cables and other components for dynamic representation, event specification or reporting in I*SIM.

Go to HIWAVE Transfers selected components to the HIWAVE study interface. Used to graphically select buses and branches for current and voltage distortion plots.

1, 2, 3, 4... Brings any of the open windows to the front; the check mark indicates which window is active.




Contents Using Help About PTW...

This menu command Performs this function Index Opens PTW’s Help Index. Under development.

Using Help Opens PTW’s How to Use Help Index. Under development.

About PTW... Displays version and copyright information about PTW.

2.6. Working with the Status Bar The Status Bar is located at the bottom of the PTW window. This Status Bar lists errors, such as “You must enter an integer between 0 and 1”; displays PTW’s progression, such as “Opening One-Line Diagram C:\PTW32\PROJECTS\PLANT\MAINDRAW.DRW”; and explains a button’s or command’s function, such as “Create a new induction motor.” You can display or hide the Status Bar like a toolbar.

To display or hide the Status Bar


• Click the View>Status Bar command (a check mark indicates the Status Bar is toggled on).

• Click a toolbar or the Status Bar with the right mouse button to display a checklist, and choose Status Bar to display or hide it. If neither the Status Bar nor any toolbars are visible, use the previous method.

2.7. Working with Toolbars PTW’s Toolbar is actually divided into various mini-toolbars, each consisting of a set of related buttons. You can customize your PTW workspace by displaying or hiding any toolbar, and moving any toolbar anywhere within the workspace.

A toolbar is considered “docked” when it is attached to a border of the application workspace, and “floating” when it resides in its own mini-frame window. By default, the toolbars are docked just below the menu bar.

Important: Once you move a toolbar from its default placement, you must manually return it; PTW does not return toolbars to the default placement.

To Do this Float a docked toolbar Point to a blank area on the toolbar and

hold the mouse button; drag the toolbar to a new location; and release the mouse button. Double-click the toolbar to return it to its


8/16/2006

To Do this previously docked location.

Dock a floating toolbar Point to the title bar and hold the mouse button; drag the toolbar to a border of the workspace; and release the mouse button. Double-click the toolbar to return it to its previously floating location.

Remember that a toolbar is not docked if you can see its title bar.

Each toolbar can also be displayed or hidden:

To display or hide a toolbar


• Click the View>Toolbars command and select or clear the check boxes next to the toolbars you want displayed or hidden.

• Click a toolbar with the right mouse button to display a checklist, and choose a toolbar to display or hide it. If no toolbars are visible, use the previous method.

Here are the toolbar buttons:

Button Function

Open the Component Editor.

Create or open a One-Line Diagram.

Create or open a Report.

Create or open a Report.

Create or open a Library.

Save changes to the component. This event is automatically triggered when you move among components.

Get context-sensitive help about any part of the screen.

Cut the selected data into the Windows Clipboard.

Copy the selected data into the Windows Clipboard.

Paste the contents of the Windows Clipboard to the selected location.

Print the active One-Line Diagram.

Preview the One-Line Diagram as it will be printed.

Run DAPPER Balanced 3-Phase Studies.

Run Single-Phase and Unbalanced 3-Phase Studies

Run Reliability Study

Run a Transient Motor Starting (TMS) Simulation.



Button Function

Run a Transient Stability Simulation using the I*SIM module.

Run a Harmonic Distortion and Scan Analysis using HI_WAVE.

Run the System Evaluation module.

Check the Input Data and Highlight Failed Components.

Highlight Failed Components from System Evaluation

Reset Colors after using the Failed Input or Failed Device Evaluation

Run a Query.

Apply and edit datablock formats.

Takes selected components from the One-Line, TCC, TMS setup, I*SIM setup or HI_WAVE setup and displays them in the Component Editor.

Opens the one-line associated with the active TCC drawing.

Displays selected components on a new or existing TCC drawing.

Add a new component. Can select any component type and any symbol from this option.

Add a new bus.

Add a new cable.

(or) Add a new two-winding transformer.

(or) Add a new three-winding transformer.

Add a new transmission line.

Add a new pi equivalent impedance.

Add a new utility.

Add a new generator.

Add a new non-motor load.

Add a new induction motor.

Add a new synchronous motor.

Add a new load schedule.

Add a new 1-node annotation symbol.

Add a new 2-node annotation symbol.

Add a new low-voltage breaker.

Add a new fuse.


8/16/2006

Button Function

Add a new motor overload.

Add a new motor circuit protector.

Add a new switch.

Add a new recloser.

Add a new relay.

Add a new high-voltage breaker.

Magnify the scale of the One-Line Diagram.

Reduce the scale of the One-Line Diagram.

Magnify a user-specified area on the One-Line Diagram.

Show the entire One-Line Diagram in the viewport.

Toggle datablocks on and off.

Switch to the Probe mode to get popup datablocks.

Annotate the One-Line Diagram with a customized textblock.

Expand the selected component(s) to show all connections.

Collapse the selected component(s) to hide all connections.

Rotate component left 90 degrees on one-line.

Rotate component right 90 degrees on one-line

Add new shunt resistor.

Add new shunt reactor.

Add new shunt capacitor.

Add new single-tuned filter.

Add new high-pass filter.

Modify TCC settings.

Modify selected device settings on TCC.

Select library entry for selected component.

Add measurement annotation to TCC drawing.

Re-draw selected device on TCC.





3 One-Line Diagrams

One-line diagrams are a fundamental tool of electrical engineering, and you probably have experience with them. PTW leverages that experience into its One-Line Diagram: it looks, feels and acts like a one-line diagram, but is actually a network building and editing tool that links directly to the project database. Using a One-Line Diagram you can change your network configuration: add components, change connections, take components in and out of service and more. One-Line Diagrams are so powerful, you can use them to build entire network topologies from the ground up. As you make changes to the One-Line Diagram, they are automatically reflected in the project.

The link to the database also lets you tap into other data, like Study data, and display them right on the One-Line Diagram. When you’re done, print your finished one-line to a wide variety of printers and paper sizes. This chapter discusses:

• Modeling power systems using a One-Line Diagram.

• Moving objects on a One-Line Diagram.

• Displaying system and Study data on the One-Line Diagram.

IN

TH

IS

CH

AP

TE

R

3.1. What is a One-Line Diagram? .......................................................................... 3-2 3.2. One-Line Diagrams and the Project Database .................................................. 3-3 3.3. Creating and Opening One-Line Diagrams ...................................................... 3-6 3.4. The One-Line Diagram Interface...................................................................... 3-6 3.5. Navigating the One-Line Diagram ................................................................. 3-11 3.6. Building the One-Line Diagram ..................................................................... 3-15 3.7. Selecting Objects ............................................................................................ 3-26 3.8. Moving and Sizing Objects ............................................................................ 3-29 3.9. Taking Components to the Component Editor ............................................... 3-32 3.10. Showing Project Data on a One-Line Diagram ............................................ 3-32 3.11. Customizing the One-Line Diagram............................................................. 3-35 3.12. Annotating the One-Line Diagram with Textblocks .................................... 3-37 3.13. Exporting One-Line Diagrams...................................................................... 3-40 3.14. Changing Colors and Fonts .......................................................................... 3-42 3.15. Creating Custom Symbols ............................................................................ 3-44 3.16. Using 1- and 2-Node Annotations ................................................................ 3-49 3.17. Symbol Rotation ........................................................................................... 3-51


8/16/2006

3.1. What is a One-Line Diagram? In many respects, a One-Line Diagram is very similar to a traditional one-line diagram: it contains symbols for network components, and shows how those components are connected together. But unlike a traditional one-line diagram, PTW’s One-Line Diagrams are interactive drawings that link directly to the project database, which means that by creating a One-Line Diagram, you can actually build a network model. When you add a component symbol to the One-Line Diagram, you also add it to the project database. PTW automatically updates any changes you make to the One-Line Diagram in the Component Editor and in the project database to guarantee consistency throughout the project. Using the One-Line Diagram you can add components, delete components, change connections, take components in and out of service, and much more. The One-Line Diagram also provides an accelerated link to the Component Editor that makes editing component data quick.

You can also create One-Line Diagrams for existing projects by expanding components to create complete one-line diagrams. And with PTW, you can create a one-line diagram for any portion of the project you choose.

Use datablocks in conjunction with a One-Line Diagram to access all of your study and topology data. Instantly display the percent voltage drop across cables, transformer rated sizes and more. In fact, any information kept in the database, including input data and study results, can be viewed right on the One-Line Diagram.

Here are some of the things that you can use a One-Line Diagram to do:

• Build an entire system model: Add components to the One-Line Diagram, and connect them visually to establish a system topology.

• Edit existing networks: Add components, change connections, take components in and out of service, delete components — all of this functionality is tied to the Component Editor and directly to the project database.

• Display additional One-Line Diagrams for selected processes or substations. The unique relationship between One-Line Diagrams and the project database makes this possible. Refer to expand and copy/paste functions form more details.

• Display network topology and study data: datablocks on the One-Line Diagram give you the information you need quickly. For further information, refer to Section 3.9, “Taking Components to the Component Editor.”

For more information on datablocks, see Section 3.10, “Showing Project Data on a One-Line Diagram” and the “Datablocks” chapter.

One-Line Diagrams UG 3-3


3.2. One-Line Diagrams and the Project Database

Important: Understanding the relationship between One-Line Diagrams and the project database is critical to using One-Line Diagrams effectively. Please take the time to read this section before creating a One-Line Diagram.

A One-Line Diagram can be used as a tool to edit the project and as a window to look in on the project database. However, it’s important to understand that a One-Line Diagram and the project database are not identical. In fact, One-Line Diagrams are not a required part of the project. For example, when you import a project from DOS, that project initially contains no One-Line Diagrams. Conversely, you may create an entire project topology using a One-Line Diagram. Think of the One-Line Diagram, then, as a tool much like the Component Editor. It provides an interface for looking at or working with the project, but does not necessarily represent the entire project. One-line diagrams are the most efficient way to enter component connections and should be used extensively.

3.2.1. ‘Components’ vs. ‘Symbols’ Because One-Line Diagrams are not required as part of a project, it follows that all of the components in a project can exist without being on a One-Line Diagram. A component is a discrete entity in the project database, and you can represent it graphically on a One-Line Diagram using a “symbol.”

A Symbol is a graphical object that is linked to, but is not identical with, the component it represents. When you place a symbol on a One-Line Diagram, PTW establishes a link between the graphical symbol and the component in the database. On a single One-Line Diagram, the link between a symbol and component is a one-to-one link, and cannot be broken. A symbol that represents a particular bus always represents that bus and only that bus.

Because of this strong one-to-one relationship between symbols and components, you can place a symbol for a given component on a One-Line Diagram only once: after the symbol for a particular bus has been placed on a One-Line Diagram, that bus has a unique name and cannot be placed on the same One-Line Diagram again. You can however add another bus to the drawing that has a new component name. You can also show one unique component on several different one-lines. The component exists only once in the project database but can be referenced on several One-Line diagrams and TCC drawings. This is one of the most important concepts: The project database owns the components, each One-line diagram and TCC drawing simply display some or all of the components that exist in the project database.


8/16/2006

CBL-0001CBL-0002CBL-0003CBL-0004CBL-0005

Project Database

Drawing

This unique relationship between symbols and components means that symbols can be added to and removed from a One-Line Diagram without necessarily changing the contents of the database. For example, if you no longer want to represent a particular bus on a given One-Line Diagram, you can remove the symbol from the One-Line Diagram without deleting the component from the database: all of the study results still include that bus, and the component still appears in the Component Editor.

When you add a symbol to the One-Line Diagram, PTW automatically displays the default symbol according to the type of component being represented. The symbols available for each component type can be changed using the One-Line>Symbol Selection option. Separate default symbols can be saved for ANSI or IEC project options. New symbols can be created using the Symbol Generator program.

Throughout this chapter, the term component refers to the object in the database, and term symbol refers to the graphical representation of that object on the One-Line Diagram. All work on the One-Line Diagram is conducted through symbols, but when an action affects the database object, the word component is used to signify both the symbol and the component. When an action affects only the symbol, the term symbol is used. The term symbol never refers to the object in the database.

Existing Components When you place a symbol for an existing component on a One-Line Diagram, it does not change the composition of the project database in any way. For example, say that you create a cable in the Component Editor, and now you want to include it on a One-Line Diagram. When you place the symbol for that cable onto the One-Line Diagram, you do not change the composition of the project; you are simply using the symbol as a link from the One-Line Diagram to the component, and as graphical representation of that component.

New Components When you add a new symbol to a One-Line Diagram, you are really doing two things at once: creating a component in the project database and placing an associated symbol on the One-Line Diagram to represent that new component. Now that the new component exists, it is a discrete object like any other component, meaning that the symbol can be removed from the One-Line Diagram without affecting the component as it is stored in the database.

For information on adding symbols and components, see Section 3.6.1 “Adding a New Component” and Section 3.6.2, “Adding a Symbol for an Existing Component.”

The symbol on the One-Line Diagram references the component in the project database, which exists independently of the symbol.



3.2.2. Multiple One-Line Diagrams For small projects, it’s easy to maintain one One-Line Diagram to represent the entire system. But what about very large projects? Or what if you are only interested representing a small portion of a project? Or breaking up your project into several different One-Line Diagrams according to process, area or substation? With PTW’s flexible One-Line Diagram architecture, you can create as many One-Line Diagrams as you want for a single project, and include any portion of the project you want on any of the One-Line Diagrams. Many choose to have one overall one-line that displays the entire power system and also have several smaller one-lines that display specific parts of the power system.

Let’s say that you have created a large project in the Component Editor, approximately 800 buses, and that project comprises five different industrial processes. Instead of having to create and maintain one large One-Line Diagram, you can create five smaller One-Line Diagrams, one for each of process. Or you can create a One-Line Diagram for one of the processes and not the others. As you build these One-Line Diagrams, change them, even delete them, the project database does not change, and any Study data you place on the One-Line Diagram will reflect values that take into account the entire system.

You can also display a single project component on two or more different One-Line Diagrams. For example, suppose two of the five industrial processes are serviced through Bus-0003, and you want to create a One-Line Diagram for each of the processes. Because symbols refer to components that are external to themselves, you can place a symbol for Bus-0003 on two One-Line Diagrams, and both symbols remain interactively linked to the same component. In the following illustration, One-Line Diagram 1 and One-Line Diagram 2 share symbols for all of the components from the utility through Bus-003, and then go on to represent two diverging processes.

BUS-0001BUS-0002BUS-0003BUS-0004BUS-0005

Drawing 1 Drawing 2

Project Database

Link several symbols from multiple One-Line Diagrams to a single component

Create several One-Line Diagrams for each project.


8/16/2006

3.3. Creating and Opening One-Line Diagrams One-Line Diagrams are project-specific, so in order to create or open a One-Line Diagram, you must open a project first.

3.3.1. Creating a New One-Line Diagram You can create a new One-Line Diagram at any time, and you can create as many One-Line Diagrams as you need: PTW imposes no upper limit on the number of One-Line Diagrams you can create per project. Each time you open a new One-Line Diagram, PTW assigns a default One-Line Diagram name. The first time you save the One-Line Diagram, you will have the opportunity to rename it.

To create a new One-Line Diagram

1. Either click the Document>One-Line command or click the One-Line Diagram toolbar button .

2. Click the New button.

3.3.2. Opening an Existing One-Line Diagram You can open as many One-Line Diagrams as you want concurrently.

To open an existing One-Line Diagram

1. Either click the Document>One-Line command or click the One-Line Diagram toolbar button .

2. Click the Open Button.

3.4. The One-Line Diagram Interface The One-Line Diagram interface works like most popular CAD systems. Its main feature is a central working area called the viewport that displays your One-Line Diagram. Think of the viewport as a window on the One-Line Diagram surface. At any given time, some or all of the One-Line Diagram is visible through the viewport. For information on navigating the One-Line Diagram, refer to Section 3.5, “Navigating the One-Line Diagram.”

Click the New button to create a new One-Line Diagram.



By default, objects are drawn in black, but you can change the color of objects, as well as special status colors.

3.4.1. Database-Related Objects The graphic elements of the one-line diagram are called objects, and there are two categories of objects: database-related objects and user-defined objects. Most of the objects that are on a One-Line Diagram are called database-related objects because they represent component attribute and connection information stored in the project. These database objects include the symbol, the datablock, the component name and the connection. Though all of the objects are related, they are, to a certain extent, discrete. This section explains the kinds of objects and their behaviors when you select and move them.

Symbol The symbol represents a component on the One-Line Diagram. The symbol is the most important object on the One-Line Diagram, and the other objects are to a certain extent subordinate to it. When you select a symbol, the component name and the datablock (if datablocks are visible) for that component are automatically selected as well. Likewise, when you move a symbol, the datablock and component name move as well, maintaining a constant relationship to the symbol. PTW allows you to specify two sets of default symbols for each component type, one set for the ANSI environment setting and another for the IEC environment setting. The default symbols are selected from the following toolbar:

The default symbols assigned to each component icon are specified in the Project>Options>Oneline option. The first icon allows you to select any component type and any symbol. The other icons select specific component types and display the default symbol.

Symbols show you the component type. Component Names show you

the name of the associated component.

Datablocks show you important component data.

Connections show you the power system layout.


8/16/2006

The default Symbol assignments are specified using the Default ANSI and Default IEC Symbol Assignment buttons. The assignment for the Cable symbol default is shown below. To change the default assignment, select one of the other cable symbols shown in the Graphic Symbol Select window. To add new symbols, refer to the section in the chapter titled "Creating Custom Symbols".



Component Name and Datablock Component names and datablocks provide information about the component, and cannot exist independently of a symbol. When you select either a component name or a datablock, the corresponding symbol is also selected. However, you can move the component names or datablock independently of the symbol.

The component name displays the name of the component in the project. The component name is a unique identifier that PTW uses to distinguish and sort components. The component name is always visible on the One-Line Diagram. To change the name of a component, see Section 0, “

Bus versus Bus-Node

A bus and a bus-node internally act the same but graphically have the the following differences:

• A Bus-Node is displayed as a Dot, whereas a bus is displayed as a sizeable bar.

• A Bus-Node defaults to not displaying the nametag or datablock, whereas the bus defaults to displaying the nametag and the datablock.

The following picture shows the difference between a Bus and a Bus-Node

Bus-Node SymbolBus SymbolBUS-2

TX-1 TX-2

C-1 C-2

BUS-1

U1 U2

BUS-3

M1 M2

3.4.2. Auto-Bus Insert Bus or Bus-node components can be added automatically by connecting two impedance components together.


8/16/2006

Bus-Nodes automatically created by connection

The Project-Options can be used to specify whether a Bus is automatically inserted or Bus-Nodes are automatically inserted.

Renaming Components.”

For information on changing the datablock format to show different data, and turning datablocks on and off, see Section 3.10, “Showing Project Data on a One-Line Diagram.”

Connection Connections appear as simple lines connecting two symbols, and represent the electrical connection defined in the project database. As such, the connection line is defined by the symbols: when you move a symbol, the connection redraws to maintain the simplest possible line between the connected symbols.



To change connections, see Section 3.6.5, “Connecting and Disconnecting Components.” To adjust connection lines vertically and horizontally without changing the connection status, see Section 3.8.2, “Moving Connection Lines.”

3.4.3. User-Defined Objects In addition to database objects, there are also user-defined objects called textblocks that you can use to annotate your One-Line Diagram, or to include other documentation such as a schedule report on your One-Line Diagram. Textblocks can include any text you want, and are not in any way interactively linked to the project.

For information on adding and editing textblock objects, refer to Section 3.12“Annotating the One-Line Diagram with Textblocks"

3.4.4. Mouse Pointers Notice that as you move the mouse pointer over various objects, it changes shape. The shape of the pointer indicates the kind of action you can take at that time. Refer to the following table:

When the pointer looks like this

You can do this Refer to

Select multiple objects. Section 3.7.2 “Selecting a Group

of Objects.”

Select single objects or move selected objects.

Section 3.7.1, “Selecting Individual Objects,” and Section 3.8.1, “Moving Objects.”

Size a bus symbol. Section 3.8.3, “Sizing Bus Symbols.”

Connect a component. Section 3.6.5, “Connecting and Disconnecting Components.”

Move a connection segment (horizontally).

Section 3.8.2, “Moving Connection Lines.”

Move a connection segment (vertically).

Section 3.8.2, “Moving Connection Lines.”

, , Size a textblock in the directions of the arrows.

“Sizing a Textblock.”

Move a textblock leader. “Moving a Textblock Leader.”

3.5. Navigating the One-Line Diagram One-Line Diagrams can be very large drawings, and being able to navigate them effectively is of great benefit when editing the network. In some cases, you may want to magnify one part One-Line Diagram, while at other times, you may want to see the entire


8/16/2006

One-Line Diagram at once. The One-Line Diagram offers several tools that you can use to navigate even very large One-Line Diagrams quickly.

3.5.1. Scrolling a One-Line Diagram You can use the scroll bars found along the bottom and right edges of the One-Line Diagram to move or “scroll” the One-Line Diagram in the viewport. The position of the scroll box in the scroll bar represents the position of the viewport relative to the boundaries One-Line Diagram: to move the viewport to the right, move the bottom scroll box to the right, and so on.

Scrolling a One-Line Diagram does not affect the level of magnification.

To scroll a One-Line Diagram

• Do one of the following:

To Do This Scroll slowly in any direction Click the arrow in the direction you want to

scroll: , , , .

Scroll quickly in any direction Click inside either scroll bar to move the scroll box in the direction of the mouse pointer.

Move to an approximate location on the One-Line Diagram

Drag either scroll box to the location you want. You can drag both the vertical and the horizontal scroll boxes.

Auto-Scroll Feature Drag the cursor or any component with the left mouse button depressed to an area just short of the one-line window edge. Holding your left mouse button depressed while the cursor is in this small "hit area" will automatically scroll the drawing area. This is particularly useful when dragging a component beyond the visible drawing area.

You may have noticed the grey-colored gridlines that crisscross the One-Line Diagram. These are page guides, and indicate where the page breaks will fall on the final printout in the "tiled" printing mode. Knowing where the page breaks are can help you group

Click any of the arrows to scroll through a One-Line Diagram.

Drag the scroll box to move to an approximate location in the One-Line Diagram.

Click in the scroll bar to move the scroll box quickly in the direction of the mouse pointer.



components on a single page, make sure that textblocks do not fall on a page break, and so on. Page guides appear as dashed lines in the viewport, indicating the location of page breaks. Page guides do not print, even when they are turned on; they are used strictly as guides to help you lay out the One-Line Diagram. The page guides have no affect on printing is the "shrink to fit" printing option is selected.

You can turn the Page Guide on or off, and control where they fall, using the Page Layout command. Doing this, though, only controls the grey-colored gridlines. It does not control your printer’s output (that is done using the Print Setup command). You must ensure that the Page Guide specifications match the paper size selected for your particular printer, or the lines are useless. For example, you can set the Page Guides to 5-inch by 5-inch, and the lines will appear onscreen with those dimensions, but if your printer’s output is set to 8.5-inch by 11-inch paper, the lines will give you erroneous information about where the page breaks will fall. In addition, if you choose Landscape as the paper orientation in the Print Setup dialog box, the Page Guide width and height specifications have to be manually reversed to accurately show onscreen where the page margins will fall. For example, if 8.5-inch by 11-inch paper is selected as Landscape- instead of Portrait-oriented, you need to manually type 11 in the Width box and 8.5 in the Height box (essentially reversing them) for the Page Guide lines to accurately represent Landscape-oriented paper.

3.5.2. Magnifying a One-Line Diagram You can use the One-Line Diagram’s zoom functions to magnify portions of the One-Line Diagram, and to move rapidly from place to place on large One-Line Diagrams.

Zooming In and Out To enlarge the size of the One-Line Diagram relative to the viewport, use the Zoom In command. Each time you use the Zoom In command, you enlarge the One-Line Diagram incrementally from the normal 100% zoom size. To use the Zoom In command, click the Zoom In button from the Toolbar , or choose Zoom In from the View Menu (CTRL+Z). You can repeat the Zoom In command until the One-Line Diagram reaches a maximum magnification of 300%.

By default zoom in magnifies the One-Line Diagram in 20% steps, relative to a zoom factor of 100% (that is, 100%, 120%, 140%, and so on). If you want, you can change this zoom step at any time using the following procedure. Note that the zoom step is a global variable that affects all projects.

To change the zoom step


2. In the Subviews box, choose One-Line Diagram.

3. In the Zoom Step box, type a value that represents the zoom step size, expressed in percent.

To reduce the size of the One-Line Diagram relative to the viewport, use the Zoom Out command. Each time you use the Zoom Out command, you reduce the One-Line Diagram incrementally from the normal 100% zoom size. To use the Zoom Out command, click the Zoom Out button from the toolbar or choose Zoom Out from the View Menu (CTRL+SHIFT+Z). You can repeat the Zoom Out command until the One-Line Diagram reaches a minimum magnification of 25%.


8/16/2006

Zoom Area To magnify a particular portion of the One-Line Diagram that is already visible in the viewport, use the Zoom Area command. With the Zoom Area command, you draw a box around any area, and that area enlarges to fill as much of the viewport as possible. You can only zoom in using the Zoom Area command; you cannot zoom out. To use the Zoom Area command, click the Zoom Area button from the Toolbar , or choose Zoom Area from the View Menu (CTRL+Y).

To magnify a portion of the One-Line Diagram

1. From the View menu, choose Zoom Area (CTRL+Y), or click the Zoom Area button on the Toolbar.

2. In the One-Line Diagram viewport, position the mouse pointer at one corner of the area you want to enlarge.

3. Press and hold the mouse button.

4. Drag the mouse pointer to the opposite corner of the area you want to enlarge.

5. Release the mouse button. The edges of the box you drew become the new boundary of the viewport.

Zoom All The Zoom All command shows you the entire One-Line Diagram in the viewport. The One-Line Diagram is shown as large as possible. To use the Zoom All command, choose Zoom All from the View Menu or click the Zoom All button on the Toolbar .

Zoom Page The Zoom Page command magnifies the One-Line Diagram so that a single printer page fits within the viewport. The page is shown as large as possible in the viewport. The dimensions of the printer page depend on the current printer settings. To use the Zoom Page command, choose Zoom Page from the View Menu.

Find Component Using the Edit>Find command displays a list of all components on the one-line. Selecting a component from the list selects the component on the one-line and automatically zooms-in around the component. This function is particularly useful for finding components on a large one-line.

Aerial View Using the Aerial View command you can move to a particular location on a large One-Line Diagram and set the level of zoom at the same time. The Aerial View dialog box shows you a thumbnail representation of the entire One-Line Diagram. An inverted box on the thumbnail, called the viewport box, represents the portion of the One-Line Diagram currently visible through the viewport.



You can draw a new viewport box around any portion of the thumbnail to see that portion of the One-Line Diagram in the viewport, or drag the existing viewport box to a new location. If you want to maintain the size of the viewport while moving it to a new area, hold the SHIFT key and drag the viewport to the new location.

To use the Aerial View command

1. Click the View>Aerial View command. The Aerial View dialog box shows a thumbnail sketch of the active One-Line Diagram. If the thumbnail sketch does not look like the active One-line Diagram, click the Refresh button to update the display.

2. Position the mouse pointer at one corner of the area you want to enlarge.

3. Press and hold the mouse button.

4. Drag the mouse pointer to the opposite corner of the area you want to enlarge.

5. Release the mouse button to draw the new viewport box on the thumbnail.

6. Click the OK button. This returns you to the One-Line Diagram where the edges of the box you drew become the new boundary of the viewport.

3.6. Building the One-Line Diagram The One-Line Diagram makes available several power system editing features. Using a One-Line Diagram, you can add new components, represent existing components, connect components, take components in and out of service, rename components, delete components and so on. In fact, you can edit your entire network using the One-Line Diagram as the main building tool.

After you have designed the network topology and are ready to edit component data you can use the accelerated link to the Component Editor. For information, see Section 3.9, “Taking Components to the Component Editor.”

3.6.1. Adding a New Component You can use the One-Line Diagram to create new components in the project. When you place a new component symbol on a One-Line Diagram, PTW automatically creates and adds the component to the project database. The new component has default data associated with it, and is not connected to any other component in the system. New components are named automatically according to an internal convention.

Drag or redraw the viewport box so that it covers the area you want to magnify.

Then Click the OK button to return to the One-Line Diagram and adjust the size of the viewport.


8/16/2006

Tip: When adding new components, leave plenty of room between components to display datablock information. It is much easier to remove extra space later than it is to add extra space.

To add a new component


• On the toolbar, click the type of component you want to add.

• Click the Component>New command. From the list, select the type of component you want to add. Click the OK button.

2. Move the pointer to One-Line Diagram viewport. A shadow image of the symbol follows the pointer.

3. Click the mouse button to place the symbol on the One-Line Diagram and save the new component in the project.

Tip: To add several components of the same type, use the process described above, but before doing Step 3, press and hold the SHIFT key. After that, each click on the One-Line Diagram adds a new component. When you are through adding the components, release the SHIFT key.

3.6.2. Adding a Symbol for an Existing Component If you are working in a project that is already defined, you can place symbols on the One-Line Diagram to represent any or all of the existing components. You can add symbols one at a time, or add several symbols at once using the expand command.

Adding Symbols Individually You can add a symbol that represents an existing component to the One-Line Diagram at any time. The only restriction that PTW imposes is that a component cannot be represented by more than one symbol on a single One-Line Diagram. You can represent the same component on more than one One-Line Diagram.

To add a component to the One-Line Diagram, click it on the toolbar ...

...and place it on the One-Line Diagram.



Adding a symbol to represent an existing component does not change the structure of the project; it simply represents that component on the One-Line Diagram. For a complete discussion about the differences between components and symbols, refer to Section 3.2.1 “‘Components’ vs. ‘Symbols’.”

When a symbol is placed on a One-Line Diagram, that symbol derives its characteristics from the component in the database. It reflects the component type, connection, in service status, etc.

To add a symbol for an existing component

1. Click the Components>Existing command.

2. In the Component box, select the component you want to represent on the One-Line Diagram.

Tip: If you are working with a large project, you can choose the query button to limit the size of the component list in the Existing Component dialog box. Refer to Section 3.7.4, “Running a Query to Select Objects” for information on running queries.


4. Move the pointer to One-Line Diagram viewport. A shadow image of the symbol follows the pointer.

5. Click the mouse button to place the symbol on the One-Line Diagram.

Adding Symbols Using the Expand Command Using the expand command, you can create a large One-Line Diagram based on an existing project quickly. The expand command automatically adds symbols to the One-Line Diagram for all of the components that are connected to the selected component(s), up to and including the surrounding level of buses. For example, suppose that you are

Select an existing component to add to the One-Line.

Choose the Query button to limit the contents of the component list.

Choose a component type to jump to the first matching component

Components already displayed on the active one-line appear in light grey.


8/16/2006

working on a One-Line Diagram and you want to add symbols for all of the components that are attached to Bus 5. To do that, you could select Bus 5, click the Expand button on the toolbar and all of the symbols would be added.

At least one symbol must be selected to use the expand function, and you can expand multiple symbols simultaneously. After you expand, all of the symbols that are added to the One-Line Diagram are automatically selected, so if you expand again, all of the new symbols are included.

To expand the One-Line Diagram

1. Select the symbol or symbols you want to expand.


• On the Toolbar, click the Expand button .

• Click the Component>Expand command.

Tip: If you want to represent only a part of a project on a given One-Line Diagram, you can use the expand feature to follow a particular path through a power system. For example, if a single process in a power system runs from Bus 1 through Buses 2, 8, 12 and 15, you can select Bus 1, expand, then select Bus 2, expand, select Bus 8, expand and so on until you reach the end of the process. Since expand does not know the position of other symbols on the one-line during the expand process, expand one component at a time to give yourself the opportunity to move the newly expanded items so they do not bump into or expand on top of other symbols on the one-line.

3.6.3. Copy/Paste Components to New One-line You can copy selected components from the active one-line and paste them to a new one-line using the Edit>Copy and Edit>Paste commands. You can copy components from any one-line but you can only paste components to a new, empty one-line. The copy/paste

When you select a symbol and use the expand command ...

...all of the symbols connected to the symbol, up to and including the next level of buses, are placed on the One-Line Diagram.



functions are similar to the Component>Existing and Expand functions in that they are displaying the same physical components on multiple one-lines. This capability is particularly useful when you have a large one-line and want to show a small section of the one-line with a coordination drawing or to highlight a specific area or process. Note the difference between "copying" a component for display on another one-line and "Cloning" a component to create a duplicate component with a new name.

3.6.4. Cloning Components The clone command duplicates a selected component or group of components on the One-Line Diagram and in the project database. Use this command to speed up the topology setup, particularly if your project contains several similar substations or processes. For example if your project has seven very similar substations, you can create the first substation, and then clone it six times.

Component clones are exact duplicates of the originals in all respects, except for their names and connections. Because each component must have a unique name to exist as an individual entity in the database, cloned components are automatically assigned the next available name according to the component naming convention.

External connections are not cloned. For instance, if you clone Motor 3, which is connected to Bus 2, the connection is not cloned. When you clone several components, any and all connections that are completely internal to the selected group are also cloned. For instance if you clone Motor 3 and Bus 2, the connection is cloned.

Note that cloning de-selects the original components and selects the cloned components.

To clone a component or components

1. Select the components you want to clone.

2. Click the Component>Clone command. The cloned components are placed below and to the right of the original symbols.

3.6.5. Connecting and Disconnecting Components You can use One-Line Diagram symbols to establish component connections throughout the power system. The One-Line Diagram gives you an advantage over the Component Editor when working with connections, because the connections are established visually: a connection is represented as a simple line between two symbols.

Each symbol has one or more connection points, called nodes. The number of nodes depends upon the component type: for example, loads have one node, cables have two, and three-winding transformers have three. A node can be connected to any bus on the system, but no two nodes on a single component can be connected to the same bus.

Connection line

Node


8/16/2006

The node’s appearance tells you its connection status, as follows:

An “o” node indicates that the terminal is not connected.

A straight line "invisible node connection" indicates that the connection point was turned-off or hidden. If the connection point is hidden, it looks the same whether it is connected, or not.

A crossed node indicates a connection to another symbol on the One-Line Diagram. A connection line always accompanies a crossed node.

An “x” node indicates a connection to a component that is not represented on the One-Line Diagram.

You can connect or disconnect components at any time. Note that in order to change a connection, you must disconnect the component first.

To connect a node

1. Using the mouse, point to the node you want to connect. The mouse pointer changes to open connection pointer. Note that if the mouse pointer changes to the closed connection pointer, that means the node is already connected.

2. Drag the node to the target bus symbol.

3. Release the mouse button. PTW draws the connection line between the two components, and the open “o” node changes to a crossed node to indicate that it is connected.

Tip: You can connect new components automatically by positioning the node on the target bus symbol as you place the new symbol on the One-Line Diagram.

You can disconnect components one at a time or in groups. When you disconnect a component in a One-Line Diagram, PTW automatically disconnects all nodes belonging to that component.

To disconnect a component or a group of components

1. Select the component or components you want to disconnect.

2. Click the Component menu>Disconnect command.

3.6.6. Making valid connections In order to make valid connections, there are some basic rules you need to follow:

• In PTW, buses are connection points between impedance devices which provide places for fault impedance. (They are not the same as busbar. To model busbar, you should use a cable component or other impedance component.) When you’re building a One-Line Diagram in PTW, you need to separate impedance devices by buses. You cannot place two impedance devices (when we refer to impedance

Open Connection pointer

Closed Connection pointer



devices, we mean cables, 2-winding and 3-winding transformers, transmission lines, and pi impedances) in series without an interconnecting bus.

Invalid Valid

• In order to connect any two buses, you must use at least one impedance device. This means that you cannot connect two buses with only a protective device (such as a fuse or circuit breaker). As the above rule attests, there must be at least one impedance device. Therefore, you must place some impedance device between the top or bottom bus and the protective device. Once you have an impedance device in the connection, though, you may insert multiple protective devices into the connection.

Invalid Valid Valid

• To simulate a tie breaker, you must use an impedance device such as a cable or a pi equivalent component. The pi equivalent usually works best:

• Parallel connections are not allowed, because a looped system results. However, you may simulate a parallel connection using an extra bus or two. Refer to these pictures:

Pi impedance


8/16/2006

Invalid Valid Valid

3.6.7. Bus versus Bus-Node A bus and a bus-node internally act the same but graphically have the the following differences:

• A Bus-Node is displayed as a Dot, whereas a bus is displayed as a sizeable bar.

• A Bus-Node defaults to not displaying the nametag or datablock, whereas the bus defaults to displaying the nametag and the datablock.

The following picture shows the difference between a Bus and a Bus-Node

Bus-Node SymbolBus SymbolBUS-2

TX-1 TX-2

C-1 C-2

BUS-1

U1 U2

BUS-3

M1 M2

3.6.8. Auto-Bus Insert Bus or Bus-node components can be added automatically by connecting two impedance components together.



Bus-Nodes automatically created by connection

The Project-Options can be used to specify whether a Bus is automatically inserted or Bus-Nodes are automatically inserted.

3.6.9. Renaming Components The name of each component is always displayed on the One-Line Diagram, and you can change the name at any time. PTW uses the component name to identify the component, so the component name you choose must be unique. PTW does not accept component names that already exist in the project database.

A component name can contain as many as 14 characters, including embedded spaces. A good rule is to keep the component names as consistent as possible within component types because the Component Editor sorts them alphanumerically; special characters or embedded spaces in a component name may cause it to fall out of the expected sequence. For example, “Transformer 14” appears before “Transformer-1” because of the embedded space.

Before Connections After


8/16/2006

Tip: If you are not sure which name belongs to which symbol, you can select the symbol, and the associated name changes to the selected color (which is blue by default). At any time, you can change the font and the font style for all component names.

To rename a component

1. Double click the component name you want to change.

2. In the New Name box, type in a new component name.


The name on the One-Line Diagram is updated immediately to reflect the change.

3.6.10. Taking Components In and Out of Service If you do not want to consider a component or a group of components when you run a study, you can take them outof service.

Note: Note that when you take a Protective Device out of service, the downstream branch will also be taken out of service. While the downstream branch will not change to the out of service color, it is indeed out of service.

The One-Line Diagrams offer you a very convenient way to take components in and out of service. Components can be taken in and out of service individually or in groups. When you take a component out of service, the symbol appears in the out of service color, which by default is gray.

In service. Out of service.

To take a component out of service

1. Select the component or components you want to take out of service.

2. From the Component menu, choose Out of Service.



To place a component in service

1. Select the component or components you want to place in service.

2. From the Component menu, choose In Service.

3.6.11. Removing Symbols Versus Destroying Components When you want to take a symbol off a One-Line Diagram, there are two ways to do it, and they are quite different. You can remove the symbol from the One-Line Diagram, hiding the symbol on the one-line without affecting the component in the database, or you can destroy the component, which deletes the component from the database and removes the symbol from all One-Line Diagrams where the component symbol is displayed.


Project Database

Drawing


Drawing

Project Database

Removing a symbol Destroying a component

Removing symbols does not affect the structure of the project in any way. It removes (hides) only the graphical representation of the symbol from the active One-Line Diagram. All attendant objects such as component names, connections, and datablocks are automatically removed with the symbol. Because the database component is still intact after you remove a symbol, you can replace that symbol at any time on the same or any other One-Line Diagram using the Component>Existing or Component>Expand functions.

To remove a symbol or a group of symbols from the One-Line Diagram

1. Select the symbol or symbols you want to remove.

2. Click the Component>Remove command.

Destroying components removes the symbol from all of the One-Line Diagrams and TCC's in the project and deletes the corresponding component from the project database.

Warning: Destroying components affects the structure of the power system. Destroying a component is permanent: once you destroy a component, it cannot be recovered.

To destroy a component or a group of components from the project

1. Select the symbol or symbols for the components you want to destroy.

2. Click the Component>Destroy command. PTW asks if you want to proceed.



8/16/2006

3.7. Selecting Objects Most actions that are performed on an individual object require you to select the object first. When an object is selected, it is referred to as active.

Selected components are drawn in the selected color, which is blue by default, and the selected status overrides any other color code that may be applied to the object. Let’s say, for instance, that MOTOR-0001 is out of service so that by default it appears gray. If you select it, the select status overrides the out of service status, and all of the objects associated with MOTOR-0001 turn blue. If you deselect it, the One-Line Diagram remembers that it is out of service and it turns gray again.

Many actions can apply to several objects simultaneously. You can select individual and groups of objects using different techniques, and you should experiment with all of them to find the technique that works best for you.

3.7.1. Selecting Individual Objects Click on objects to select them individually.

To select a single object

1. Point to the object you want to select. The mouse pointer becomes the select pointer

.

2. Click the object.

If you have already selected some objects, you can also add or remove single objects from/to the selected set. The selected set can contain as many objects as you want.

To add or remove a single object to a selected group

1. Press the SHIFT key.

2. Point to the object you want to add or remove. The mouse pointer becomes the select pointer.

3. Click the mouse button. The select status of the object will change.

4. Release the SHIFT key.

3.7.2. Selecting a Group of Objects To select multiple objects, draw a selection box around them. This saves a great deal of time when you want to select objects that are located in the same area of the One-Line Diagram — that is if they are grouped spatially.



To select a group of objects

1. Point to one corner of the selection area.

2. Press the mouse button.

3. Drag the mouse pointer to the opposite corner of the selection area. As you drag the mouse pointer, you will see the selection box being drawn.

4. Release the mouse button. All of the objects that are surrounded by the selection box are selected.

Note: The selection box must completely surround the object you want to select. Partially surrounded objects are not selected.

If you have already selected some objects, you can add or remove a group of objects. The selected group can contain as many objects as you want.

To add or remove a group of objects to a selected set

1. Press the SHIFT key.

2. Point to one corner of the selection box.


4. Drag the mouse pointer to the opposite corner of the selection box, which should contain all of the objects you want to add or remove to the group. As you drag the mouse pointer, you will see the selection box being drawn.

5. Release the mouse button. This changes the select status of all objects that are surrounded by the selection box.

3.7.3. Selecting All Objects To select all of the objects on the One-Line Diagram simultaneously, click the Edit>Select All command.

3.7.4. Running a Query to Select Objects Running a query is a very effective method of selecting components that are grouped by function (rather than by location). Using a query you can select components that share

Draw a selection box around the objects that you want to select.


8/16/2006

any attribute or group of attributes. For example, you can select all motors over 500 hp, or all three-winding transformers. Note that queries select symbols only (with the symbol names and datablocks), not connections.

Running a query on a One-Line Diagram de-selects any previous select, searches the active One-Line Diagram for components that meet the criteria of the query, and selects those components.

This section briefly summarizes the process of running a query on the One-Line Diagram, but is not intended as an in-depth discussion of queries, which are extremely powerful and flexible tools. For a more complete discussion of queries, refer to the “Queries” chapter.

To run a query

1. Do one of the Following:

• Click the Run>Query command.

• From the Toolbar, click the Query button .

2. Under Query Category, select the category from which you want to select your query.

3. Under Query Result Set, do one of the following:

• If you want to replace the results of the last query with the results of the new query, select the Replace option button.

• If you want to combine the result of the query with the results of a previous query or queries, select the Merge option button.


• In the list box, select the query you want to run, and choose the Run button.

• In the list box, double-click the query you want to run.

After you run the query, all of the devices on the One-Line Diagram that satisfy the conditions of the query appear in blue, indicating that they are selected.

Select the query you want to run.

Choose the Run button to run the selected query.

Replace previous query results, or merge several query results.



Tip: Use the Find Unconnected Components query to quickly locate any components

that you accidentally left unconnected.

3.8. Moving and Sizing Objects The One-Line Diagram is a powerful drafting tool that lets you change the layout of the one-line diagram to meet your needs. You may want to reposition expanded objects, move an entire substation to make room for a clone, size a bus bar, move a connection line, and so on. This section applies both to database-related and user-defined objects.

3.8.1. Moving Objects Using a single procedure, you can move objects across the One-Line Diagram either individually or in groups. If you move objects in groups, the relative position of the objects within the group remains constant. All connections within a group move with the objects even if the connections themselves are not selected.

Objects automatically snap to a grid that is superimposed on the One-Line Diagram, making it easy to align and space them evenly. For datablocks, textblocks, and component names you can disable the snap feature by holding down the CTRL key while you move the object.

Select the object (or objects) you want to move ...

and drag it to a new location. When the move is complete, connections redraw automatically.

This procedure cannot be used for connections, because the location of connections is defined by the objects they join. For information on adjusting connection lines, refer to Section 3.8.2, “Moving Connection Lines.”

To move objects

1. Select the object or objects you want to move.

2. Point to the selected object, or any one of the selected objects in the group. The mouse pointer becomes the select pointer.


4. Drag the object or objects to a new location.

5. Release the mouse button.


8/16/2006

3.8.2. Moving Connection Lines To accommodate the layout needs of a particular One-Line Diagram, you can move connection lines independently of symbols. You may want to move a connection line around a datablock, for example, straighten a connection, or make room for another connection on a bus symbol.

All connections can be moved horizontally along a bus. If the connection has a break in it, the horizontal portion of the line, called the connection elbow, can also be moved vertically between the component and the connected bus. When you move the vertical connection line, it move a as a single piece, unless you move it beyond the limits of the connected bus, in which case a horizontal connection elbow forms.

Move connection lines along a bus. Move connection line elbows vertically.

To move a connection line


• If you want to move a connection line horizontally (along a bus), point to the segment of the connection line closest to the bus symbol. The mouse pointer becomes the horizontal pointer.

• If you want to move a connection line elbow vertically, point to the horizontal segment of the connection line you want to move. The mouse pointer becomes the vertical pointer.


3. Drag the line segment to the new location.


3.8.3. Sizing Bus Symbols Bus symbol can be made longer or shorter to fit the number of components that are connected to it. A bus symbol that has eight connections has to be much longer than a bus bar that has only one. You size buses by dragging either end of the symbol to a new location.

Select either end of the bus symbol...

and drag it to a new location. The bus symbol redraws at a new length.

Horizontal pointer

Vertical pointer



Note that when you expand a One-Line Diagram, PTW sizes bus symbols automatically to accommodate any new connections. If you are building a network from scratch, you should size the bus symbol manually as necessary.

To size a bus symbol

1. Point to either end of the bus symbol you want to size. The mouse pointer becomes the Bus Sizing pointer.

2. Press and hold the left mouse button.

3. Drag the end of the bus symbol to the new location.


3.8.4. Aligning and Distributing Objects When you want to create neat, even rows of components on the One-Line Diagram, you can use two commands provided expressly to help you with One-Line Diagram layout: align and distribute. Use align to line up your One-Line Diagram objects, and distribute to space them evenly. Using these commands together makes it very easy to lay out One-Line Diagrams neatly.

Aligning Objects When you want to line up several objects relative to each other, use the Align command. You can align objects relative to the top-, bottom- right, or left-most edge of the current selection. Align takes into consideration all selected objects except connections, so datablocks and component names can be aligned as well as component symbols.

Select the objects you want to align Then select the direction in which you want to align them. In this case, the objects were aligned to the bottom-most selected object.

To align objects

1. Select the objects you want to align.

2. Click the One-Line>Align command.

3. From the new menu, choose the direction in which you want to align the objects: top, bottom, left or right.

Distributing Objects When you want to space several objects evenly, use the Distribute command. The Distribute command uses the two outer-most objects in the current selection as anchor points, and spaces all other selected objects as evenly as possible between them. You can distribute either from left to right, or from top to bottom.

To distribute objects

1. Select the objects you want to Distribute.

Bus Sizing pointer


8/16/2006

2. Click the One-Line>Distribute command.

3. From the new menu, choose the direction in which you want to distribute the objects: left to right or top to bottom.

3.9. Taking Components to the Component Editor While working in a One-Line Diagram, you can edit any component or group of components by “taking” them to the Component Editor using the Window>Go To Component Editor command. You can also click the Go To Component Editor toolbar button .

3.10. Showing Project Data on a One-Line Diagram Input data and study results can be displayed in One-Line Diagram objects called datablocks, and you can view datablocks through the One-Line Diagram interface in two ways: you can either place them on the One-Line Diagram as objects, or show them in temporary popup windows using the One-Line Diagram’s probe mode. This section does not explain datablocks completely, but summarizes applying and viewing datablocks. For a more thorough discussion of datablocks, see the “Datablocks” chapter.

Datablocks are small, semi-discrete objects that contain a few or several relevant pieces of data about each component. Datablocks are always related to a component, but can be moved independently for optimal placement. To show datablocks on the One-Line Diagram, you can apply any datablock format you want, and then turn the datablocks on or off. You can even print datablocks on the final one-line diagram.

When you take components to the Component Editor, only the components you select appear in the Components box. The Components Set shows that this component set came from the One-Line.



The probe is a way of looking at datablocks one at a time in a temporary popup window. Use probes on very intricate One-Line Diagrams where datablocks won’t fit, or to see a different datablock format quickly without redefining the format for your entire One-Line Diagram.

Datablocks are saved in named formats, so when you want to see Datablocks be sure that the correct datablock format is applied. Applying a datablock format is not the same as viewing a datablock. Applying a format means simply to select the datablock style you want. Then when you view datablocks, they conform to that style. You can apply different datablock formats to the One-Line Diagram and the probe at the same time, and you can change the formats at any time.

Each grouping of project data is a datablock. The datablocks are continuously updated from the project database.


8/16/2006

To apply a datablock format

1. Either click the Run>Datablock Format command or click the Datablock Format button on the toolbar .

2. Under Type select either Probe or One-Line.

3. In the Formats list box, select the datablock format you want.

4. Click the Apply button.

5. Repeat steps 1 through 4 for each type of datablock you want to define.

6. Click the Close button.

Note: If the datablock format you apply includes study data, be sure to run the corresponding study so current data are available. You can run studies at any time, even when the datablocks are visible, and the results are updated automatically.

When you have applied a datablock format, you can turn the Datablocks on to view them on the One-Line Diagram.

To show or hide datablocks on the One-Line Diagram

1. Either click the View>Datablocks command or click the click the Toggle Datablocks button .

To turn datablocks off, repeat this procedure.

The probe works a little differently. To use the probe, you enter the probe mode, which disables normal One-Line Diagram functions. When you click on any component while in the probe mode, its datablock appears in a popup window. The size of the popup window is constant, so the level of magnification has no effect on the size of the datablock.

To use the probe

1. Either click the View>Probe command or click the probe button .

The pointer becomes the probe pointer.

2. Click any component. The datablock for that component appears in a popup window.

3. Repeat step two for any component you want.

To exit the probe mode, repeat step 1 of this procedure.

To apply a datablock format, select the format you want, and then choose the Apply button. Be sure to assign to the choice to the proper type: either One-Line Diagram or Probe.



3.11. Customizing the One-Line Diagram Several features are available to help customize the one-line diagrams including custom annotation symbols, symbol rotation, connection lines, options to hide component names and connection points, etc. A sample one-line with symbol rotation, connection lines and custom annotation symbols follows:

A more detailed discussion about the one-line annotation and customization features on the One-Line menu follows:


8/16/2006

New Texblock Allows you to place custom text on the one-line. Review the following section for more details.

Component Color Allows you to change the color of selected components. We suggest keeping all components black so selected components and failed study components standout when highlighted. You may find it useful to keep multiple one-lines, some with user-defined colors and others with all black components.

Datablocks Allows you to hide or display datablocks for individual components. This control is at a works with the Run>Datablock Format option. Run>Datablock Format displays the selected datablock information for all components on the one-line except for those that are hidden by the Oneline>Datablock>Visible/Not Visible option.

Nametags Allows you to hide or display component names for individual components. This is particularly useful if you are displaying annotation components on the one-line.

Connection Points This option allows you to hide or display the visual connection points for individual components. This function is useful for removing open connection circles from floating annotation components and for hiding the + connection markers on final one-lines.

Annotation Allows you to draw annotation connection lines between two components. This is useful for connecting two relay circles, and for connecting annotation symbol such as a ground path to the body of a generator or transformer symbol.

Annotation Line Style Allows you to change the line style of the annotation line. Line style options include dotted, dashed, dot-dash, and solid.

Symbol Rotation Allows you to rotate symbols on the one-line to create riser diagrams or for better space useage.

Convert to Bus Node Changes the Bus symbol to a Bus Node symbol. The Bus Node symbol is a Dot rather than a sizable bar.

Convert to Bus Changes the Bus Node symbol to a Bus symbol. The Bus symbol is a sizable bar rather than a dot.

Symbol Selection Allows you to select a different symbol for the selected component, or group of components. If multiple components are selected, only the components that match the new symbol category will be changed.



3.12. Annotating the One-Line Diagram with Textblocks Use textblock to place a note on the One-Line Diagram, to draw attention to a particular area, or to include a part of a report on a One-Line Diagram.

You can even paste reports into textblocks, like the load schedule report shown here.

Textblock


8/16/2006

With textblocks, you can customize your display to meet your particular needs using a variety of design options including shadow effects, leaders, and borders. The picture below shows you all of the parts of a textblock.

You control the appearance of textblocks in the Textblock dialog box, in which you can control all of the display settings.

To create a textblock

1. Either click the One-Line>New Textblock command or click the Textblock button .

2. In the Text box, type the main body of the textblock. You can start a new line of text by pressing the ENTER key.

3. Under Shadow, select the shadow options you want

To Do This Turn the shadow on or off Select or clear the Visible check box.

To set the width of the shadow In the Width box, select the thickness of the shadow.

To set the direction in which the shadow extends from the text

In the direction box, select a direction.

Text

Border

Shadow Leader

Set the display options at the bottom of the dialog box.

Type the text of the textblock here.



4. Under Leader, select the leader options you want:

To Do This Turn the leader on or off Select or clear the Visible check box.

To set the location at which the leader attaches to the border

In the Width box, select one of the eight available attachment locations. Or, if you prefer PTW to determine the point of origin for you, select Automatic.

To add a pointer to the end of the leader line Select the style you want. Selecting None removes the pointer from the end of the leader line.

5. If you want to add a border around the text, select the Border check box.

6. If want to size the textblock to the longest line of text, select the Size to Text check box.


You can edit an existing textblock by changing the parameters in the Textblock dialog box. To access the Textblock dialog box, simply double click the textblock you want to edit.

To edit a textblock

1. Either select the textblock and click the One-Line>Textblock Attributes command, or double-click the textblock itself.

2. Edit any of the parameters, as described previously in this section.


3.12.1. Working with Textblocks Textblocks are discrete user-defined objects that can be moved freely across the surface of the One-Line Diagram. For the most part, textblocks behave like other One-Line Diagram Objects: you can select, move and remove them using the same procedures used for database objects. However, there are some additional features unique to textblocks, which are described in the following sections.

Moving a Textblock Leader Note that When you move a textblock, the end point of the leader is anchored in place, and the textblock moves relative to it. When you want to move the leader to a new location, drag it separately from the main body of the textblock. You can disable the snap feature by holding down the CTRL button while moving a textblock.

To move the textblock leader ... Drag it to another location

To move the textblock leader

1. Point to the end of the leader. The pointer becomes the leader pointer .

2. Press and hold the left mouse button.


8/16/2006

3. Drag the leader to a new location.


Note: When you move either the leader or the text, you may have to move the leader’s point of origin. If the point of origin for the textblock is set to automatic, PTW determines which point of origin is closest to the leader end point, and moves the leader to that point. Otherwise, you may have to change the point of origin yourself. For information and instructions on setting the point of origin, refer to the previous section, “Working with Textblocks.”

Sizing a Textblock You can change the shape of the textblock border in order to conform to the amount of text, or to the layout of the One-Line Diagram. You can size the text both vertically and horizontally, and PTW automatically wraps the text as needed to conform to the shape of the textblock.

To size a textblock, position the mouse pointer over an area of the textblock border, and drag the border to a new location. The active areas on the border include the four midpoints of each side, and the four corners.

To size a textblock

1. Point to the side or the corner of the border you want to move. The pointer becomes a sizing pointer .


3. Drag the border to a new location according to the following table:

If you point to this The pointer becomes Drag the border Any corner of the border or Diagonally.

Any side of the border or

Vertically or horizontally.


3.13. Exporting One-Line Diagrams PTW can export One-Line Diagrams into Windows Metafiles (WMF Files) or CAD format files (DXF Files), making them available to most Windows-based graphics programs: CAD programs, illustration programs, even word processors support either WMF files, DXF files or both. Many graphics applications even treat WMF files as native objects, letting you manipulate the layout even after you’ve exported. You can export the entire One-Line Diagram, or just the selected portion. You can also use the export function to copy the One-Line Diagram or portions of the One-Line Diagram into the Windows clipboard so that you can paste it directly into other applications.

Exporting is handled through the Export dialog box, which you can use to set the source data and the destination location for the exported One-Line Diagram.



To export a One-Line Diagram to a WMF or DXF File

1. If you want to export only a portion of the One-Line Diagram, select the objects in the portion you want to export.

2. Click the Document>Export command.

3. Under Source, do one of the following:

• If you want to export the entire One-Line Diagram, select the All One-Line Diagram option button.

• If you want to export only the portion of the One-Line Diagram you selected in Step 1, select the Selection option button.

4. Under Destination, do one of the Following:

• To export the One-Line Diagram to a Windows Metafile, select the Placeable Metafile option button.

• To export the One-Line Diagram to a DXF File, select the DXF File option button.

5. In the File Name box, type the filename for the exported metafile. The name of the One-Line Diagram is used as the default name. The metafile is saved in the project directory by default, but you can save it in any directory you choose by typing a valid path before the filename. You can also choosing the browse button to provide a path.

6. Click the OK button. To export a One-Line Diagram to the Windows clipboard

1. If you want to export only a portion of the One-Line Diagram, select the objects in the portion you want to export.

2. Click the Document>Export command.

3. Under Source, do one of the following:

• If you want to export the entire One-Line Diagram, select the All One-Line Diagram option button.

• If you want to export only the portion of the One-Line Diagram you selected in Step 1, select the Selection option button.

4. User Destination, select the Clipboard option button.


8/16/2006


3.14. Changing Colors and Fonts You can change colors for One-Line Diagrams on a global level, so they apply to all new One-Lines that you create, and on a particular level so they apply to a single One-Line.

To change a specific component’s color, select the component and click the One-Line>Component Color command, then pick a color, as shown following:

The available colors can be changed in the Project>Options>One-line>Current Application Settings.

Use the “Current Project Settings” and "Current Application Settings" subviews to establish settings for the One-Line Diagrams in the current project. To set the options for all new projects, use the “New Project Settings” and "New Application Settings" subviews.



The project settings include Font specification for component names, textblocks and datablocks, default bus and symbol rotation orientation, symbol spacing for expanding symbols, and printing thickness for buses and connection lines. More detailed descriptions for each option follows:

NewBus As. Allows you to control whether new bus symbols or new bus-node symbols are inserted when two impedance components are connected together.

Spacing. Often, you may want to add space between One-Line Diagram symbols to accommodate names, Textblocks, other symbols, and so on. Use these spacing options to set the amount of vertical and horizontal space PTW adds between symbols as you place them on the One-Line Diagram. “X” is the amount of space between symbols. Horizontal space is applied between symbols when you expand them from a common bus. The unit of measurement is the width of the symbol body, so to add the width of three symbol bodies between the expanded symbol, type a 3 in this box. “Y” is the amount of space between the symbol and its connection node(s). Vertical space is applied between the symbol body and each connection node. The unit of measurement is the height of the symbol body, so to add the height of three symbol bodies between the symbol and its connection nodes, type a 3 in this box.

New Symbol Orientation. Use the drop-down list box to select the default orientation for new bus and component symbols. The change will affect the orientation of new symbols added to the one-line, it will not change the orientation of symbols already displayed on the one-line. See One-Line>Symbol Rotation to change the orientation of symbols once they are displayed on the one-line.

Printed Thickness. Use the drop-down list box to select the thickness of the bus symbols and connection lines on printed output. Since line thickness varies with printer resolution, thicker lines may be required for high-resolution printers.

Default Symbol Assignment. Click the Assign button to assign new default symbols for each symbol icon. The bitmap image will not change on the symbol icon, but the symbol appearing on the one-line when the icon is selected will change to reflect your selection.

Zoom Step. Type a zooming increment for the One-Line Diagram’s zoom in and zoom out functions. This number represents a percent size of the One-Line Diagram, relative to a 100% factor.

Font Information. Use these options to set fonts for the component names, Datablocks, and Textblocks on the One-Line Diagram. You can even set font properties such as bold or italic. Changes you make to fonts are instantaneous, and they affect all One-Line Diagrams in all Projects.

The application setting subview controls the application colors and available symbol colors.


8/16/2006

Screen Colors. The One-Line Diagram uses color to identify not only objects, but also object status such as selected and out-of-service objects. You can change any of the above colors at any time by clicking the button next to the color scheme. “Background” is the background color of the One-Line Diagram against which symbols are shown. The background color is white by default. “Selected” sets the color of selected objects, and any associated text. The selected color is blue by default. “Out of Service” affects out of service components and any associated text. The Out of Service color is grey by default, but many people prefer to change the option to red.

Symbol Colors. The Default option sets the color which will be used for any new component you add to the One-Line Diagram. The rest of the 7 colors are those which appear under the Component Color command on the one-line. These colors can be used to change the color of symbols or groups of symbols on an existing one-line.

3.15. Creating Custom Symbols If you find that the standard symbols included with PTW don't meet your needs; you can use the Symbol Generator to change the existing symbols and create new symbols.

3.15.1. Starting the Symbol Generator The Symbol Generator program is a standalone utility that you run separate from PTW.

Important: Be sure to close PTW before you run the Symbol Generator program.



To start the Symbol Generator program

1. Select the Symbols Generator Icon from the PTW Program Group

--- or

To start the Symbol Generator program

1. Click Start>Run.

2. Click the Browse button.

3. Locate the symgen.exe program located in the c:\ptw32\bin folder.

4. Click the Open button.


The Symbol Generator program appears.

Each folder contains the symbols for that component type:


8/16/2006

3.15.2. Creating Custom Symbols The symbols used on PTW's One-Line Diagrams are stored in the Symbol Library. When you run the Symbol Generator program, it automatically opens this Symbol Library.

Technical Note: The Symbol Library is actually a separate file called symbols.ugs, which is located in the ptw32\lib folder. You can create new Symbol Libraries named <any name>.ugs and store symbols in these Libraries, but PTW always uses symbols.ugs when creating the One-Line Diagram. Therefore, it's usually best to add new symbols to symbols.ugs. You should never delete the original symbols.ugs Symbol Library; if you do, you'll have to re-create all the standard symbols. A better idea is to make a backup copy of the original symbols.ugs, then return to symbols.ugs to add and modify symbols.

To create a new symbol

1. Highlight the folder of the component type that you want to create a symbol for:

2. Click the Symbol>New command.

The folders contain the existing symbols for that

component type.



3. Type a name for the new symbol:

4. The Symbol Generator will reappear, showing the device you just created:


8/16/2006

• You can now use the drawing tools to add any combination of lines, arcs, ellipses, rectangles, and text to the symbol:

3.15.3. Using Custom Symbols on a One-Line One you have created a custom symbol, you can open PTW and use the custom symbol on a One-Line.

To use a custom symbol on the One-Line

1. Select a component on the One-Line:

These circles with numbers representthe connection nodes. You cannot

delete them--they are used for making connections on the One-Line. The

number of connection nodes dependson the component type: cables havetwo, motors have one, three-winding transformers have three, and so on.

This "Name" text indicates where the component's name will appear. You cannot delete it. Don't confuse this tag with the customizable text that you can add.

This is customizable text which we added by clicking the Text button. To modify its text, click the right-mouse button and select "Text Properties."

We added these rectangles and squares using the drawing tools.



2. Click the One-Line>Symbol Selection command. The Symbol Selection dialog box will appear:

3. Choose a symbol and click the OK button. The One-Line will now use the new

symbol you chose:

3.16. Using 1- and 2-Node Annotations Use one- and two-node annotations to add meters, sensors, group path symbols, and other components that are not directly required by the system study modules, but that you may wish to display on your one-lines. You can also create user-defined fields to store information about the annotation components. These annotations appear in the Component Editor but don't participate in Studies.

3.16.1. Adding annotations to the One-Line You can add one-node, two-node, and three-node annotations to the One-Line.

To add a 2-node, click the 2-node button:


8/16/2006

To add a 1-node, click the 1-node button:

To add a connection line, click the Connection Line command:



3.17. Symbol Rotation To rotate the symbols on the One-Line, use the One-Line>Symbol Rotation commands:


4 Component Editor

Together with One-Line Diagrams, the Component Editor represents one of the primary network editing tools in PTW. The Component Editor is a powerful dialog box that lets you navigate the network, display topology and Study data, and edit components. The Component Editor contains forms and text boxes containing all of the attributes for each component in the project. Note that this Chapter discusses many of the features of the Component Editor, but does not discuss the technical requirements of entering component data.


• What is the Component Editor?

• Opening the Component Editor.

• Adding components and editing components.

• Reviewing Study data in the Component Editor.

IN

TH

IS

CH

AP

TE

R

4.1. What is the Component Editor?........................................................................ 4-2 4.2. Opening the Component Editor ........................................................................ 4-2 4.3. Using the Component Editor ............................................................................ 4-2 4.4. Navigating the System...................................................................................... 4-5 4.5. Building the System.......................................................................................... 4-6 4.6. Entering Component Data ................................................................................ 4-9 4.7. Running a Query to Limit the Component Set ............................................... 4-10 4.8. Showing System Data in the Datablock Subview........................................... 4-12 4.9. Buses............................................................................................................... 4-13 4.10. Cables ........................................................................................................... 4-14 4.11. Two-Winding Transformers ......................................................................... 4-14 4.12. Three-Winding Transformers ....................................................................... 4-15 4.13. Pi Impedances............................................................................................... 4-15 4.14. Transmission Lines ....................................................................................... 4-15 4.15. Utilities ......................................................................................................... 4-16 4.16. Generators..................................................................................................... 4-16 4.17. Non-Motor Loads ......................................................................................... 4-17 4.18. Induction Motors .......................................................................................... 4-17 4.19. Synchronous Motors..................................................................................... 4-18 4.20. Protective Devices ........................................................................................ 4-18 4.21. Filters ............................................................................................................ 4-19 4.22. Load Schedules............................................................................................. 4-20


8/16/2006

4.1. What is the Component Editor? The Component Editor is a dialog box tied directly to the project database that you can use to complete any network editing task. The Component Editor displays a list of the components in the network, and shows you the data for the selected component.

Components are listed in the component list box which shows you the component name, type, and connections. When you select a component, its data are shown on the right side of the screen. You can view or edit these data at any time.

Each component type has one or more pages of data called subviews. Subviews are organized according to frequency of use: the most important information is always on the first subview so you can find it easily.

Here are some of the things that you can use the Component Editor to do:

• Build a network topology: Add new components to the network by clicking them on the toolbar.

• Edit all component data: Change attributes, change connections, take components in and out of service, delete components — all of this functionality is tied directly to the project database.

• Display and navigate the system: The Components list box can expand and collapse to display connections among devices, and can be use as a navigational tool to move throughout the components. See Section 4.3.1 “Components Box” and Section 4.4, “Navigating the System” for more information.

• Display Study results or input data: The Datablock subview quickly shows you any system or Study data for every component type. See Section 4.8, “Showing System Data in the Datablock Subview” for more information.

4.2. Opening the Component Editor The Component Editor is project-specific, so to open the Component Editor, you must first open a project. When you open the Component Editor, it shows you a list of all components in the project by default.

To open the Component Editor

1. Either click the Document>Component Editor command or click the Component

Editor toolbar button .

4.3. Using the Component Editor On the left side of the Component Editor, you pick the component you want to see, and its data are displayed on the right. You can see more pages of data by changing the subview.

Component Editor UG 4-3


4.3.1. Components Box

The components box displays a list of components referred to as the component set. You can display data for any component by selecting it in this box. When you select the component, all of its data appears in the subview portion of the Component Editor.

The component set being displayed at any given time corresponds to the Component Set option button that is currently selected (see “Component Set Option Buttons” later in this section). Components are sorted alphanumerically according to component type. For each component in the set, the component box displays an icon representing component type, and the component name. When you select a component in the components box, the data for that component appears in the subview on the right side of the screen.

You can also move through the components in the Components one at a time with the View>Next Component and View>Previous Component commands.

The Components box is arranged hierarchically, so you can use it to display connections and to navigate the power system. For more information refer to Section 4.4, “Navigating the System.”

Select the component data youwant to review.

Select the component you want to review or edit in the components box.

Review or edit all the component data in the component subviews.


8/16/2006

4.3.2. Component Subviews Box

Each component type has one or more pages of data associated with it, each of which is called a subview. The Component Subview dialog box displays the available subviews for the selected component. The subviews labels are descriptive of the contents for easy identification. For example, the conductor and raceway data for cables is located in the Conductor and Raceway subview.

Tip: All component types have a Datablock subview that you can use to see component data and Study results. For more information, see "Showing System Data in the Datablock Subview" on page 4-12.

4.3.3. Component Set Option Buttons

The Component Set option buttons control which components are currently listed in the components box. Each list of components is called a component set, and these component sets can come from other windows such as the One-Line Diagram, as shown:

If you select this button The components box displays All All components in the project.

From "Go To" The most recent group of components that you brought from another window (such as a One-Line Diagram or CAPTOR TCC Drawing) using the "Go To Component Editor" command.

Query The components that matched the criteria of the last-run Query. For information on running Queries, see Section 4.7, “Running a Query to Limit the Component Set.”

Error Components that are flagged by the Studies as containing input errors such as undefined data or invalid settings.

The Component Editor maintains all four component sets individually, so you can switch component sets at any time by selecting the option button corresponding to the component set you want to see. Switching component sets does not change the contents of the component sets: each component set remains intact until you close the Component Editor, or until you replace the set with another set. For instance, let’s suppose you run a Query on all synchronous generators in the system. The components box now contains all synchronous generators (the Query set), and the Query Component Set option button is selected. If you want to see the all set, you can choose the All option button without disturbing the contents of the Query set. To change the contents of the Query set, you have to run another Query. Changing the contents of one component set does not affect



the contents of the others, but closing the Component Editor deletes every component set except the All set.

Tip: If you have not run a Query in the Component Editor, you can use the Query option button as an accelerated link to the Query dialog box, where you can run a Query. Select the Query option button at any time, and the Query dialog box appears. After you run the first Query, selecting the Query option button displays the Query component set in the components box, as usual.

4.4. Navigating the System The Component box is not simply a list of components but also acts as the primary navigation tool in the Component Editor. To navigate the system using the Component box, you can click on components to “expand” them. When you expand a component a detailed connection hierarchy appears, displaying all of the components connected to the primary component, and the relationships among them.

Only one component can be expanded at a time, and PTW automatically collapses a component as you expand another.

All component types can be expanded. When expanded, components display the “From” bus(es) above and the “To” bus(es) below, giving you a quick visual representation of the system connections, like a miniature One-Line Diagram.

To display a component’s connections... click the symbol or double-click the name.

The direction of the hierarchy lines indicate the subordinate components’ relation to the expanded component. Those components shown adjacent to a right angle indicate they are directly connected to the expanded component; those shown adjacent to the diagonal line indicate they are intermediate connections.

To expand a component



8/16/2006

• In the components box, either click the symbol or double-click the name of the component you want to expand. All of the components electrically connected to that component appear in hierarchical relation to that component.

• Click the Component>Expand command.

The subordinate components that “appear” when you expand a component are interactive with the project, so you can expand any one of them as well. If you expand a subordinate component, PTW automatically moves to that component in the displayed component set, making it the primary component. If the subordinate component that is not a member of the active component set, PTW asks you if you want to add the component to the component set.

To collapse a component


• In the components box, click the symbol or double-click the name of the component you want to collapse. All of the component connections disappear, restoring the natural order of the component set.

• Click the Component>Collapse command.

4.5. Building the System All network editing capabilities are available through the Component Editor. Using the Component Editor, you can add new components, edit component data, connect components, take components in and out of service, rename components, delete components and so on.

Tip: Consider using a One-Line Diagram to connect components. In many cases, the One-Line Diagram gives you an advantage over the Component Editor when working with connections, because connections can be established visually using a convenient drag and drop method.

4.5.1. Adding a New Component You can create a new component in the project at any time. When you add a new component to the Component Editor, PTW automatically creates and adds the component to the project database. After you add a new component, that component appears in the components box regardless of the component set being displayed. New components have certain default data associated with them depending upon type, and that you may want to edit based on the needs of the project.

To add a new component


Add a new component to the project by clicking one of the component buttons.



• On the toolbar, click the type of component you want to add. If you don’t know which button represents the component you want to add, point to each component button and pause. The fast tip tells you what component type that button adds.

• Click the Component>New command and select the component you want to add.

4.5.2. Cloning a Component The clone command duplicates a selected component. Component clones are exact duplicates of the originals in all respects, except for their names and connections. Because each component must have a unique name to exist as an individual entity in the database, cloned components are automatically assigned the next available name according to the component naming convention. The cloned component is not connected to the system.

Note that cloning de-selects the original component and selects the cloned component.

To clone a component

1. Select the component you want to clone.

2. Click the Component>Clone command.

4.5.3. Connecting and Disconnecting Components Using the Connect Components dialog box available from the Component Editor, you can connect and disconnect component nodes.

Tip: Consider using a One-Line Diagram to connect components. In many cases, the One-Line Diagram gives you an advantage over the Component Editor when working with connections, because connections can be established visually using a convenient drag and drop method.

Each component has one or more connection points, called nodes. The number of nodes depends upon the component type. Loads have one node, cables have two, three-winding transformers have three, and so on. A node can be connected to any bus in the system, but no two nodes on a single component can be connected to the same bus. All nodes on a given component must be connected for the component to be connected. If you fail to connect one or more nodes of a given component, the Studies issue an error message to that effect.


8/16/2006

You can connect or disconnect components at any time. Note that in order to change a connection, you must disconnect the node first, and then reconnect it.

4.5.4. Renaming Components The name of each component is displayed in the Name dialog box which is always located on the first component subview. You can change the name at any time by typing a new name into the box. PTW uses the component name to identify the component, so it cannot accept component names that already exist in the project database.

To rename a component

1. In the components box, select the component you want to rename.

2. In the component "Name" field on the first subview, type in a new component name.


The name in the components box is updated immediately to reflect the change. You can also change component names by double-clicking the left mouse button on the one-line diagram with the cursor pointing at the component name you want to change.

4.5.5. Taking Components In and Out of Service If you do not want to consider a component or a group of components when you run a Study, you can take them out of service. While out of service components do not affect Study calculations, they do maintain an electrical connection, keeping the network topology intact. (Note that when you take a Protective Device out of service, the downstream branch will also be taken out of service. While the downstream branch will not change to the out of service color, it is indeed out of service.)

Tip: You might consider using One-Line Diagrams to take components in and out of service. One-Line Diagrams offer you a very convenient way to select multiple components and take them in or our of service with a single command. For more information, refer to the “One-Line Diagrams” chapter.

Select the node you want to connect.

Select the bus you want to connect to the selected node.

Click the connect button to make the connection.



When you take a component out of service, the name of the component in the components box changes to gray.

In service. Out of service.

To take a component in or out of service

1. In the components box, select the component you want to take in or out of service.

2. In the first Component Editor subview, do one of the following:

• To take a component out of service, clear the In Service check box.

• To take a component into service, select the In Service check box.

4.5.6. Destroying Components Destroying a component deletes the component from the database, and removes it from the components box. When a component is destroyed, all connections going to that component are broken.

Warning: Destroying components affects the structure of the power system. Destroying a component is permanent: once you destroy a component, it cannot be recovered.

To destroy a component

1. In the components box, select the component you want to destroy.

2. Click the Component>Destroy command. PTW asks if you want to proceed.


4.6. Entering Component Data When you create a component, you can use one of two methods to enter its attribute data: you can either type in the data yourself, or for some component types, link the component to a library model.

When you want to supply your own data for a component, you can type or select values in the Component Editor dialog box. If you type in your own data, it is your responsibility to fill in the proper values, and to know which values are needed for the type of Study (or Studies) you want to run. You can also type in data for one component and use the clone command to make exact duplicates of that component, which then have an existence of their own and can be edited as necessary. Refer to Section 4.5.2, “Cloning a Component” for further information.

In addition to typing in your own data, you can also use data that is stored in the library to define certain components. To do this, click the Library button and select a model from the Library. After clicking the library button, you can select the library category and the specific library entry you wish to reference to the component.


8/16/2006

To break the link with the library, click on the Deselect button. The data from the library will remain with the component, however when the library reference is deselected the data can be modified in the Component Editor.

4.6.1. Copy / Paste Data You can copy data from one component and paste the data into another component or group of components to minimize data entry. To copy data, select a single component and use the Device>Copy function. To paste the data to other components, select the components and use the Device>Paste function. The data will only be transferred to components in the selected group that match the component type of the copied data.

4.6.2. Save Data as Default Data entered for a component can be saved as default data for new components added to the project. To save the data as your default, select the component and use the Component>Save As Default function. Default data can be saved for each component type and can be updated at any time.

4.7. Running a Query to Limit the Component Set Running a Query is an effective method of filling the components box with a component set that is grouped by function. Using a Query you can select components that share any attribute or group of attributes. For example, you can look at all motors over 500 hp, or all three-winding transformers.



This section briefly summarizes the process of running a Query on the Component Editor, but is not intended as an in-depth discussion of Queries, which are extremely powerful and flexible tools. For a more complete discussion of Queries, refer to the “Queries” chapter.

To run a Query

1. Do one of the Following:

• Click the Run>Query command.

• Click the Query toolbar button .

2. Under Query Category, select the category from which you want to select your Query.


• If you want to replace the results of the last Query with the results of the new Query, select the Replace option button.

• If you want to combine the result of the Query with the results of a previous Query or Queries, select the Merge option button.


• In the list box, select the Query you want to run, and click the Run button.

• In the list box, double-click the Query you want to run.

After you run the Query, all of the components in the project that satisfy the conditions of the Query appear in the components box, and the Query option button is selected to indicate that the box contains the Query set. For more information on the Component Set option buttons, refer to Section 4.3.3, “Component Set Option Buttons.”

The Query set is not dynamically linked to the Query, so its contents do not change until you run another Query, regardless of any edits you make to the components. For

Select the Query you want to run.

Click the Run button to run the selected Query.

Replace previous Query results, or merge several Query results.


8/16/2006

example, if you generate a Query set including all motors over 500 kVA, and then change the size of one motor to 400 kVA, that motor does not “disappear” now that it is no longer satisfies the original Query criteria. If you rerun the Query, however, that motor does not appear in the Query set.

4.8. Showing System Data in the Datablock Subview Notice that all component types have one subview in common: the Datablock subview. You can use the Datablock subview to look at any datablock format. This section does not explain datablocks completely, but summarizes applying and viewing datablocks. For a more thorough discussion of datablocks, see the “Datablocks” chapter.

Datablocks are saved in named formats, so when you want to see a Datablock in the Datablock subview, you must first apply the datablock format you want.


1. Either click the Run>Datablock Format command or click the Datablock Format toolbar button .

2. Under Type, select Component Editor.

3. In the Formats For list box, select the datablock format you want.



Note: If the datablock format you apply includes Study data, be sure to run the corresponding Study so that current data are available. You can also re-run the Study at any time, even when the datablocks are visible, and the results will be updated automatically.

Select the Component Editor Option button.

Select the Datablock format you want.

Click the Apply button to apply the selected format to the Component Editor.



When you have applied a datablock format, you can then switch to the Datablock subview to see the datablock data. If the applied format does not include formatting for a particular component type, the Datablock subview is left blank for all members of that type.

To switch to the Datablock subview

1. In the components box, select the component whose datablock you want to see.

2. In the Component Subview box, select Datablock.

You can switch components at any time by selecting a new component in the components box. You can also switch between subviews without losing your applied datablock format.

4.9. Buses

A bus component is a nodal point that serves as a common connection for two or more impedance devices such as cables, transformers, and motors. The bus component is defined by its nominal system voltage, expressed in volts. (For example, express 13.8 kV as 13800 Volts). All per unit calculations are based on the nominal system voltage.

You enter data for the bus component using the Bus subview and view the applied datablocks in the Datablock subview.

A Bus can also be used to designate equipment such as MV Switchgear, MV E2 Starter, LV Panelboard, LV Switchgear, etc. Ratings can be assigned to the bus for comparison in the Equipment Evaluation module. Only buses that have assigned ratings will be evaluated by the Equipment Evaluation module.

A Bus can be displayed as a regular Bus or as a “Node Bus”. A node bus is just like a regular bus except for the following items:

1) Node Bus is displayed as a dot rather than a bar.

2) Node Bus default is to hide the bus name


8/16/2006

3) Node Bus default is to hide the datablock

4) Node Bus is not displayed in reports.

4.10. Cables

A cable component is a single or stranded conductor with or without insulation and other coverings (single-conductor cable), or a combination of conductors insulated from one another (multiple-conductor cable). A cable's Library-referenced name consists of four parts: the cable type (Al (Aluminum) or Cu (Copper)), the duct type (Magnetic, Non-Magnetic, Plastic, or Bus), the Insulation type (THWN, XLP, THHN, EPR, ****(non-insulated)), and the cable voltage. Cables are modeled in PTW as a series resistance-and-reactance value in ohms/1000 ft. (or meters, depending on the units of measurement chosen in the Application Options). Predefined Library models can be used to ease data entry for cable components. When referenced from the Library, the positive- and zero-sequence impedance values are displayed but not editable. When the cable is user-defined, you may enter positive- and zero-sequence values. Negative-sequence values are always equal to the positive-sequence values. The cable component can be resized, if you choose to do so, based on the results of the DAPPER Sizing Study.

You enter data for the cable component using the Cable subview, the Conductors and Raceway subview, and view the applied datablocks in the Datablock subview.

4.11. Two-Winding Transformers

(when Application Options are set to ANSI) (when Application Options are set to IEC)

A transformer component is a device which, when used, will raise or lower the voltage of alternating current of the original source. The two-winding transformer component has two nodes, or connection points. All transformers are modeled as three-phase devices--either three single-phase transformers or a single three-phase type. Note that kVA values are total three-phase values and the transformer rated-voltages are line-to-line voltages.

The two-winding transformer component can be resized, if you choose to do so, based on the results of the DAPPER Sizing Study. It may be resized based on the calculated demand load value or the calculated design load value. The transformer is always sized based on its full load kVA value. The transformer's full load kVA value equals the transformer nominal, or self-cooled, kVA rating times the transformer's capacity factor. The capacity factor is the ratio of a transformer's capacity to provide load when additional cooling elements or auxiliary devices such as forced-air fans are added to the transformer's nominal or self-cooled rating.

Predefined Library models may be used to ease data entry for two-winding transformer components. When referenced from the Library, the Library key is based on its cooling type. Each cooling type in the Library is defined with its associated capacity factor. Transformer positive- and zero-sequence resistance and reactance values, expressed in percent of the transformer's nominal kVA rating, are referenced from the Library when



you select the transformer's capacity factor and size. The transformer's negative-sequence impedance always equals its positive-sequence value. Transformer phase-shift must be defined by knowing the standard high-to-low voltage connection, which is usually a +30° phase-shift for a delta-wye transformer and 0° for a delta-delta transformer. Transformer zero-sequence modeling assumes a shell-type three-phase bank, wherein the wye-grounded, wye-grounded model is assumed to be a high-to-low voltage series impedance (no connection to the reference plane).

You enter data for the two-winding transformer component using the Two Winding Transformer subview and the Transformer Impedance subview and view the applied datablocks in the Datablock subview. If you have the single phase and unbalanced three-phase study modules, single phase and mid-tap transformers can be specified in any phase combination. Automatic Load Tap Changing (LTC) transformer parameters can also be specified for the unbalanced/single-phase studies.

4.12. Three-Winding Transformers

(when Application Options are set to ANSI) (when Application Options are set to IEC)

A transformer component is a device which, when used, will raise or lower the voltage of alternating current of the original source. The three-winding transformer component has three nodes, or connection points. PTW models the three-winding transformer as three two-winding transformers. This component cannot reference any predefined Library models. In addition, DAPPER's Sizing Study does not consider this component.

You enter data for the three-winding transformer component using the Three Winding Transformer subview and the Three Winding Transformer Impedance subview and view the applied datablocks in the Datablock subview.

4.13. Pi Impedances

A pi equivalent impedance component is a generic impedance model that may be used to represent a transmission line, tie-break, or other impedance element. Both series and shunt impedance (admittance) values may be entered. The pi equivalent impedance data may be modeled in actual units of ohms or Mhos (Siemens), or in per unit on any specified kVA and voltage base.

You enter data for the pi equivalent impedance component using the Pi Equivalent subview and view the applied datablocks in the Datablock subview.

4.14. Transmission Lines


8/16/2006

A transmission line component is used to model an impedance device with both series and shunt impedances. Transmission lines are modeled using the unit length in miles (or km, depending on the units of measurement chosen in the Application Options). Series compensation, expressed as a percent of the line series inductive impedance, as well as shunt reactors may be modeled.

You enter data for the transmission line component using the Transmission Line subview and view the applied datablocks in the Datablock subview.

4.15. Utilities

A utility component represents an electric power utility company or any primary power supply. Think of this component as a lumped equivalent of all the utility's generators. You specify the utility's voltage in per unit and relative voltage angle, and also define its capacity to produce short-circuit current. In PTW, utilities are automatically defined as swing buses.

You enter data for the utility component using the Utility subview and view the applied datablocks in the Datablock subview.

4.16. Generators

A synchronous generator component is a synchronous alternating-current machine which transforms mechanical work into electric power. (A synchronous machine is one in which the average speed of normal operation is exactly proportional to the frequency of the system to which it is connected). Besides specifying the machine's nameplate-rated power and average power factor, you must specify its initial operating conditions. The three choices depend on whether the generator is regulated (PV type), non-regulated (PQ type), or defined as the swing bus (V, angle type) generator.

Also, synchronous generators must be specified with an impedance. The positive-, negative-, and zero-sequence reactance and associated sequence X/R ratio must be specified. Usually those are the sub-transient reactance values, so as to capture the maximum short-circuit current. Generators are assumed to be solidly wye-grounded. Ungrounded generators may be modeled by typing a large value. Grounding impedances may be modeled.

You enter data for the synchronous generator component using the Synchronous Generator subview and the Synchronous Generator ANSI Contribution subview (or the Synchronous Generator IEC Contribution subview), and view the applied datablocks in the Datablock subview.



4.17. Non-Motor Loads

Electrical loads can be most generally divided into non-motor loads and motor loads. The primary difference between load types is that non-motor loads are non-rotating loads (such as lighting panels) which do not contribute fault current.

You can use non-motor loads to lump small loads together, but all of the loads should be of a non-rotating type. If you want to lump together a number of small rotating loads (motors), model them as a single large motor load.

You enter data for the non-motor load component using the General Load subview and the Load Diversity subview, and view the applied datablocks in the Datablock subview.

Predefined Library models can be used to categorize non-motor load components and assign global diversity or demand factors.

4.18. Induction Motors

Electrical loads can be most generally divided into non-motor loads and motor loads. The primary difference between the load types is that motor loads are rotating loads that store energy for fault current calculations. Non-rotating loads such as lighting panels, which do not affect faults, should be modeled as non-motor loads, not as motor loads.

You can use lump a number of small motor loads together as a single large motor load, but all of the loads should be of the same general size. If you want to lump together a number of small non-rotating loads, model them as a single large non-motor load.

An induction motor component is an ac motor in which a primary winding on one member (usually the stator) is connected to the power source, and a polyphase secondary winding or a squirrel-cage secondary winding on the other member (usually the rotor) carries induced current. Induction motors are modeled with delta-connected windings, and therefore have an infinite zero-sequence impedance.

You enter data for the induction motor component using the Induction Motor subview, the Motor Diversity subview, and the ANSI Contribution subview (or the IEC Contribution subview), and view the applied datablocks in the Datablock subview.

Motors can be referenced in a Motor Control Center Load Schedule and then linked to the Motor Control Library to ease data entry. If you do this, though, the motors assigned to an MCC are handled differently than motors not placed in an MCC. This is discussed more thoroughly in the Demand Load Study chapter of the DAPPER Reference Manual.


8/16/2006

4.19. Synchronous Motors

Electrical loads can be most generally divided into non-motor loads and motor loads. The primary difference between the load types is that motor loads are rotating loads that store energy for fault current calculations. Non-rotating loads such as lighting panels, which do not affect faults, should be modeled as non-motor loads, not as motor loads.

You can use lump a number of small motor loads together as a single large motor load, but all of the loads should be of the same type. If you want to lump together a number of small non-rotating loads, model them as a single large non-motor load.

A synchronous motor component is a synchronous machine which transforms electric power into mechanical work. (A synchronous machine is one in which the average speed of normal operation is exactly proportional to the frequency of the system to which it is connected). Synchronous motors are modeled with wye-grounded connected windings, and as such a zero-sequence impedance and associated grounding impedance may be modeled.

You enter data for the synchronous motor component using the Synchronous Motor subview, the Motor Diversity subview, and the ANSI Contribution subview (or the IEC Contribution subview), and view the applied datablocks in the Datablock subview.

Motors can be referenced in a Motor Control Center Load Schedule and then linked to the Motor Control Library to ease data entry. If you do this, though, the motors assigned to an MCC are handled differently than motors not placed in an MCC. This is discussed more thoroughly in the Demand Load Study chapter of the DAPPER Reference Manual.

4.20. Protective Devices

A protective device component is a bypass gap or other device which limits the voltage on the capacitor segment to a predetermined level when overcurrent flows through the series capacitor (that is, during system faults, system swings, or other abnormal events), and which is capable of carrying capacitor discharge, system fault, and load current for specified durations.

There are twelve different protective devices available in PTW:

1. Low-voltage breakers

2. Fuses

3. Motor Overloads

4. Motor Circuit Protectors

5. Switches

6. Reclosers

7. Relays



8. High-voltage breakers

The Component Editor does not differentiate between these twelve component types. Therefore, fuses, relays, high-voltage breakers, and so on all appear within the Components Box generically as "protective devices." This makes data entry easier for the protective devices, since they all use the same subviews. PTW distinguishes between the twelve protective devices on a One-Line Diagram, where each protective device has a unique symbol, and in the CAPTOR TCC Study, which applies unique information to each protective device.

You enter data for the protective device component using the Protective Device subview and view the applied datablocks in the Datablock subview.

Note that when you take a protective device out of service with the Out of Service command, you take the entire downstream branch out of service, too (that is, power does not flow through the downstream branch). While the downstream branch will not turn gray (or whatever color you have set as the out-of-service color), it is indeed out of service.

Predefined Library models can be used to ease data entry for protective device components.

4.21. Filters A filter is a device which is used to reduce the harmonics in a system (although filters can sometimes actually increase harmonics). There are four different filters available in PTW:

Resistor--Increases impedance in the system. Typically you pair a resistor with a reactor.

Reactor--Increases impedance in the system. Typically you pair a resistor with a reactor.

Single-Tuned Filter--Reduces impedance at a designated harmonic order in a rather narrow frequency band.

High-Pass Filter--Reduces impedance at the target harmonic order to a somewhat lesser degree, but is more effective in lowering impedance across the whole frequency spectrum.

The fifth "filter" is not really a filter at all but is a capacitor bank:

Capacitor Bank--Engineers typically add capacitor banks to a system to improve (increase) the power factor; as a byproduct, though, capacitor banks affect the harmonics of the system, sometimes reducing the harmonics but oftentimes increasing them.

The Component Editor does not differentiate between these five. Therefore, resistors, reactors, capacitor banks, single-tuned filters, and high-pass filters all appear within the Components Box generically as “filters.”


8/16/2006

The filter components are all shunt connected components. For series connected resistors, reactors and capacitors, use the PI impedance component.

4.22. Load Schedules

A load schedule is a formatted table of power system loads which are usually fed by panelboards, motor control centers, or switchboards. The loads are listed by circuit or cubicle number and include general load information, including size and description. It is useful to think of the schedule as a collection of loads attached to the load bus or fed from the load bus. There are three different schedule types available in PTW: Panels, Motor Control Centers (MCCs), and Switchboards.

In the Component Editor, there are three subviews for each schedule: (1) the Schedule Subview, which is the same for all three schedule types; (2) the Panel, MCC or Switchboard Subview, which changes to reflect what you selected in the Schedule Subview; and (3) and the Datablock Subview.

When you first create a schedule and switch to the Component Editor, in the Component Subviews box, select the Schedule Subview.

4.22.1. Schedule Subview The Schedule Subview, shown in the following figure, is the same for all three types of schedules. Select or type the data you want for the schedule in the Schedule Subview.

Tip: When you select the Schedule Category type (Panel, MCC, or Switchboard), the second subview in the Components Subviews box automatically changes to match the schedule type. Therefore, it is a good habit to always select the Schedule Category first. That way, you won’t inadvertently proceed to the incorrect second subview.

Each box and its available options are listed in the following table:

In this box Type or select this data Name: 14 character name; PTW-assigned name may be

used.

. . .corresponds to the schedule type you choose here.

This subview name. . .



In this box Type or select this data In Service: Checked for In Service, left unchecked for Out

of Service.

OC (Overcurrent) Device Type: Breaker, Fuse, MOL (Motor Overload), or your own description.

Mounting: Flush, Surface, Free Standing, or your own description.

Device Family: Bolt On, Plug In, Draw Out, Plug, Cartridge, or your own description.

Enclosure: NEMA 1, NEMA 3R, NEMA 4, NEMA 7, NEMA 9, NEMA 12, or your own description.

Continuous Current Rating, Busbar: Full-load current rating.

Withstand Rating, Bus SC: Maximum short circuit rating.

Schedule Specification: 3-Phase 3-Wire, 3-Phase 4-Wire, Single-Phase 3 Wire.

Schedule Category: Panel, Switchboard, MCC, or Single-Phase Panel.

Notes: Custom notes.

Mains: Reads breaker size of nearest upstream breaker in Fed From branch. Also allows user direct entry.

Fed From: Defines the upstream bus feeding the schedule. Options included the connected bus and all buses one away from the schedule bus.

Connections. . . Changes the component connections.

4.22.2. Panel, MCC, or Switchboard subview This subview changes slightly depending on the Schedule category chosen in the Schedule subview. All three are used to assign load descriptions to the schedule, but the Panel assigns them in the form of circuits, which display the separate phases A, B, and C for the circuit, while the MCC and Switchboard assign them in the form of cubicles, which do not show the separate phases. For example, let's say you assigned Transformer 1 to a schedule. If the schedule is a panel schedule, you will see the transformer at all 3 phases of the circuit, whereas if the schedule is an MCC or switchboard schedule, you will only see the transformer at the one cubicle:

Panels show all three phases of the circuits. MCCs and switchboards show the three phases

as one cubicle.

Assigning Bus Loads and Sub-Feeds to the Schedule To assign an existing load (induction motor, synchronous motor, or non-motor load) or sub-fed impedance device (cable, transformer, transmission line, or pi impedance) to a schedule, highlight the load or impedance device in the Available Loads at the Bus box.


8/16/2006

Next, highlight an available cubicle/circuit. Lastly, click the Connect to Circuit (or for MCCs and switchboards the Connect to Cubicle button).

For panels, highlight an available bus load, then highlight an available circuit, and click the Connect to Circuit button.

For MCCs and switchboards, highlight an available bus load, then highlight an available cubicle, and click the Connect to Cubicle button.

The load disappears from the Available Loads at the Bus box and appears next to the circuit, representing the connection. PTW assumes existing loads and impedance devices are three-phase and therefore they occupy all-three circuits in the schedule.

To break the connection, click the Remove button.

To add protective device data to an impedance device or non-motor load that is connected to a cubicle/circuit, highlight the cubicle/circuit, click the Modify button, and type an Overcurrent Protection size:

If you click the Ind Mtr button or the Synch Mtr button PTW actually creates a new motor (exactly as if you clicked the or button) and connects the motor to the schedule's bus. You will see the motor in the Component Editor, but you won't see the motor on the One-Line Diagram unless you add its symbol using the Component>Existing command.



Important: If you have a motor symbol on the One-Line Diagram which represents more than one motor, and you select that motor symbol from the Available Loads at the Bus box, the schedule treats it as only one motor. Therefore, if you want to model multiple motors in the schedule, it is best to assign only one motor to the motor symbol when you create the component. You can then Clone it as many times as you want, attaching each motor to the bus, so that you have the desired number of motors. You can then assign each motor to the schedule individually.

To assign additional data to a motor, click the Modify button, which displays the Motor Schedule Data dialog box. The Motor Schedule Data window has four different tabs: Motor Control, Impedance, Sizing, and Cable Key.

Motor Control Tab

The Motor Control tab, shown below, allows you to assign a motor name, size, and a library reference for overcurrent protection and starter information:

Each data field, and the available options, are listed in the following table:

In this box Type or select this data Name: 14 character name; PTW-assigned name may be

used.

Rating: Motor size in HP, kVA or kW (same as motor rating in Component Editor).

Motor Library Key: If set to <User Defined>, uses Rated Size; if a value is selected, references Motor Library to automatically assign overcurrent protection and starter information.

Rated Size: (only appears when Motor Library Key is set to <User Defined>)

Rated size as stored in the Motor Library.

— or —

Voltage Range/Starter: (only appears Required to complete the Motor Library Key.

Select the Motor Control subview by clicking on its tab.

Type or select data for the new motor.


8/16/2006

In this box Type or select this data when Motor Library Key has a value selected. Not shown in the preceding figure)

Voltage Range and Starter entries must be defined in the motor library to be displayed in this field.

Overcurrent Protection Not editable if a Motor Library component is selected. May be changed if Motor Library Key is set to <User Defined>. Text boxes include Type, Size and Poles.

Starter Not editable if a Motor Library component is selected. May be changed if Motor Library Key is set to <User Defined>. Text boxes include Type, Space, Size and Accessory Group.

Library FLA: Not editable if a Motor Library component is selected. May be changed if Motor Library Key is set to <User Defined>. Motor full load amperes as defined in the Motor Library. The Library FLA may reflect a standard NEC value and may not match the actual motor rating. The motor demand and design load values are calculated using the Library’s FLA value. If the FLA is zero, the Demand Load Study calculates this value based on the motor rated size. See the Demand Load Study chapter of the Reference Manual for further details and examples.

Impedance Tab

The Impedance tab, shown below, is linked to the Cable Library, and allows you to assign a cable size from a MCC schedule to the motor. The cable impedance is used to calculate the branch circuit voltage drop shown on the schedule input and output. The impedance is not used in the full system load flow and short circuit study modules:

Each data field, and the available options, are listed in the following table :

Select the Impedance subview by clicking on its tab.

Type or select Impedance data for the new motor.



In this box Type or select this data Cable Library Key: Selected size uses Cable Library’s impedance

value. If you do not want a Cable Library link, or if you want to edit impedance values after the initial Library link, Click the Library button followed by the Deselect button.

Cable Size: May be changed if Library Key is set to <User Defined>. Limited to standard library sizes when Cable Library Key is specified.

Length: Length in feet or meters (as selected in Project Options).

Impedance: Not editable for cables referenced from Cable Library. May be changed when Cable Library Key is set to <User Defined>. Units in Ohms per 1000 feet or meters (as selected in Project Options).

Conductors in Parallel/Phase: Number of parallel conductor per phase.

Per Unit Conv… Per unit conversion dialog box to assist with per unit conversions if Cable Library Key is set to <User Defined>.

Sizing Tab

The Sizing Tab, shown below, is also linked to the Cable Library and displays ground wire size, rated ampacity, neutral size, design ampacity, duct bank specification, temperature and raceway specifications. Most of the fields are not editable when a Cable Library Key value is selected in the Impedance Tab. All of the fields may be changed when the Cable Library Key is set to <User Defined>.


In this box Type or select this data Ground Size (No Parallel): Ground wire size for a single conductor.

Select the Sizing subview by clicking on its tab.

Type or select Sizing data for the new motor.


8/16/2006

In this box Type or select this data Rated Ampacity: Ampacity rating with no duct bank or

temperature derating.

Neutral Size: Neutral conductor size.

Ground Size (Parallel): Ground wire size for multiple parallel conductors. References the Cable Library’s Ground Wire Sizes for Number in Parallel Subview when a Cable Library Key value is selected in the Impedance Tab. See the “Libraries” chapter to view or edit the Cable Library Subview.

Duct Bank Detail: Ampacity based on pre-defined duct bank configurations. The library defaults use NEC detail drawings.

Design Ampacity: Cable ampacity adjusted for duct bank configuration.

Temperature: Temperature derating table.

Derating Factor: Temperature derating factor as defined for the specified temperature in the temperature derating table.

Number of Raceways: Number of raceways for the branch circuit, usually assumed to be one for each set of conductors.

Circuit Description: 3 Wire, 3 Wire+Grnd, 4 Wire, or 4 Wire+Grnd.

Type: User-defined description of raceway.

Size: User-defined size of raceway.

Cable Key Tab

The Cable Key Tab, shown below, is the last of the four tabs in the Motor Schedule Data dialog box. The Cable Key Tab is only used when the Cable Library key in the Impedance Tab is set to <User Defined>, and you want to assign a cable description:

Select the Cable Key subview by clicking on its tab.




In this box Type or select this data Voltage Rating: Maximum voltage rating of the cable.

Duct Material: Magnetic, Non-Magnetic, Bus, or Plastic.

Conductor Type: Copper or Aluminum.

Insul Type: Insulation (for example, THWN, THHN, XLP, EPR, etc.)

Adding Little Loads to Circuits "Little loads" are one-, two-, or three-pole loads (such as lighting) that you can assign to circuits or cubicles in a load schedule. The big difference between motor and non-motor loads and little loads is that motor and non-motor loads appear on the One-Line Diagram and can be searched for using Queries, whereas little loads do not appear on the One-Line Diagram (you only see them in the Panel, MCC, or Switchboard subview) and cannot be searched for using Queries. Little loads affect the system just as non-motor loads do, so they will affect the results of studies such as Demand Load and the Load Flow studies, and they will appear in the load schedule reports.

To add a new little load to the panel schedule, select an available circuit from the Circuit, Phase, and Description box and, under Load, click either the 1 Pole, 2 Pole or 3 Pole button. The Schedule Load dialog box, as shown below, appears:

Type or select Cable Key data for the new motor.


8/16/2006

Each data field and the available options are listed in the following table:

In this box Type or select this data Description: 14 character description; PTW-assigned

description may be used.

Rated Size: Load size in VA, kVA, kW, or Amps.

Quantity: Number of loads at the rated size.

Power Factor: Power factor in per unit (Unity), leading (Lead), or lagging (Lag).

Demand Category: Load category from Demand Load Library.

Notes: Personal notes.

Overcurrent Protection Size: Protective device size in amperes.

To copy existing circuit data to a blank circuit, select the circuit you want to copy from the Circuit, Phase, and Description box, and choose the Copy button; this copies the circuit to the clipboard. Then select a blank circuit from the Circuit, Phase, and Description box and choose the Paste button. The copied circuit is then pasted to the blank circuit. This lets you quickly create a complete schedule. (Only little loads can be Copied and Pasted. Use the Clone command in the One-Line Diagram to copy an load or impedance device.)

Note: While panel schedules let you model single-phase loads and report the load on each phase, the Demand Load and Load Flow Studies use the equivalent three-phase load.

4.22.3. Load Schedule Reports You can generate a Load Schedule Report the same way you run a Study, either by clicking the Run>Analysis command or clicking the Analysis button.

Note: In the Load Schedule Report, PTW uses the bus rated voltage to calculate the fault current, whereas in the Comprehensive Short Circuit Study PTW uses the pre-fault voltage. You probably won't notice the difference because the bus rated voltage and the pre-fault voltage are usually the same; the only time they'll be different is when you have modeled transformer tap values and turn on the "Model Transformer Taps" option in the Comprehensive Short Circuit Study.

Type or select data for the new load.



After running the Load Schedule Report, the Report may be viewed, printed, or copied to a textblock on the One-Line Diagram.

To copy a Load Schedule Report to a textblock

1. With the Report file open, select the Report data you want to copy and either click the Copy button on the Toolbar, choose Copy from the Edit menu, or press CTRL+C.

2. On the One-Line Diagram, either click the Textblock button on the Toolbar or choose New Textblock from the One-Line menu.

3. Paste the Report into the textblock by pressing the shortcut keys CTRL+V.

You can control the size of the font in the Options dialog box. Be sure that the font type is PIXymbols Extended or the gridlines will not be maintained.


8/16/2006



5 Datablocks

Your project contains thousands of individual pieces of data, but most of the time the information you need is very specific. For example, you may need to know the voltage drop through a particular cable. How do you get that information quickly and easily? You could generate a study report and look for it there, but it’s much nicer if you can take that bit of data and put it right on your One-Line Diagram or see it in Component Editor. That’s exactly what datablocks allow you to do. Using datablocks, you can create custom attribute formats for all component types, and have access to all of those formats as you work. It’s like having mini reports right at your fingertips.


• What is a datablock?

• Applying datablock formats.

• Creating and editing datablock formats.

• Viewing datablock formats.

• Working with user-defined fields.

• Creating and printing datablock reports.

IN

TH

IS

CH

AP

TE

R

5.1. What is a Datablock? ........................................................................................ 5-2 5.2. Parts of a Datablock.......................................................................................... 5-4 5.3. Applying Datablock Formats............................................................................ 5-4 5.4. Viewing Datablocks.......................................................................................... 5-6 5.5. Creating Datablock Formats ............................................................................. 5-8 5.6. Editing Datablock Formats ............................................................................. 5-10 5.7. Copying and Deleting Datablock Formats...................................................... 5-11 5.8. Creating and Printing Datablock Reports ....................................................... 5-11 5.9. Creating User-Defined Fields ......................................................................... 5-15


8/16/2006

5.1. What is a Datablock? A datablock is a small amount of important data about a component that you can place on a One-Line Diagram, TCC Drawing or look at in the Datablock subview of Component Editor. When you need just a few pieces of information very quickly, you can use a datablock in the place of a report. You define the component attributes you want to display and save your settings in a named datablock format that is available at any time, throughout the project. Both network topology data and study data can be placed into datablocks.

Each line of a datablock contains a customizable label, which tells you the component attribute, followed by a value for that attribute. Define one or several lines for each component type — you decide how much detail you want. The illustration below shows what a datablock looks like on a One-Line Diagram.

You can define datablocks for as many component types as you want, and save your settings in a named datablock format. Saving datablocks in formats makes it easy to view load flow data, fault data, and so on. Each project can have as many named formats as you want, and PTW comes with many ready-to-use datablock formats built into the program.

You can view datablocks in four environments:

• On a One-Line Diagram, datablocks are displayed for all of the component types that have defined datablock settings, and you can turn them on and off. Datablocks are treated as discrete objects that can be moved independently for optimal placement. You can also print your datablocks when you print the One-Line Diagram.

• In the One-Line Diagram probe, you can look at datablocks one at a time in a

temporary popup window. You can use probes on very intricate One-Line Diagrams where datablocks won’t fit, or to see a different datablock format quickly, without redefining the format for your entire One-Line Diagram.

The datablock shows you important information about your components — in this case load flow data for CBL-0001.

User’s Guide UG 5-3


• In the Datablock subview of the Component Editor you can see the applied datablock

for the active component.

• On the TCC drawing you can display datablocks for selected components.

Note that the size and relative position of the datablocks and textblocks on the TCC will vary with TCC aspect ratio and screen/printer resolution. Use a matching fixed aspect ratio on the screen and the printer form definition for best results.

Datablock display


8/16/2006

5.2. Parts of a Datablock Each line of a datablock contains as many as four distinct parts, each of which is described in this section. Knowing the parts of a datablock can help you read them, and define custom formats. For further information on defining custom datablock formats, refer to Section 5.5, “Creating Datablock Formats.”

Direction: If the attribute has a directional component, such as load flow current shown here, an arrow indicates the direction of flow. This is available only on One-Line Diagrams and in the probe.

Attribute label: Gives a descriptive name to the component attribute. This label is totally customizable.

Attribute Value (%1): Represents the actual numerical value for the current component attribute. The example above shows a 10.86 load flow current for the component (CBL-0001). This value comes directly from the project database, and uses the most current data available. You can exclude the attribute value from the datablock, if you choose. You can control the number of decimal places displayed in the datablock definition by adding .0, .1, .2, or .3 after the %1 value attribute place holder.

Attribute unit (%2): Represents the unit of measurement for the attribute. The above example displays an A for amperes. You can exclude the attribute unit from the datablock, if you choose.

5.3. Applying Datablock Formats Applying a datablock format means selecting the format you want to see on the active window. You can apply datablock formats from within either a Component Editor or a One-Line Diagram, but only to the active window. That is, from within a Component Editor, you can only apply a datablock format to the Component Editor. So before applying a datablock format, be sure that you have the correct window (One-Line or Component Editor) active. The probe is considered part of the One-Line Diagram, so if you want to apply a datablock format to the probe, be sure that a One-Line Diagram is active. After applying a datablock format, refer to Section 5.4, “Viewing Datablocks” for information on viewing the selected datablock format.



If none of the existing datablocks meets your present needs, you can design your own datablock format and all of the datablocks contained in it; refer to Section 5.5, “Creating Datablock Formats.”

Note: If the datablock format you want to apply includes study data, be sure to run the corresponding study so that current data are available. You can also re-run the study at any time, even when the datablocks are visible, and the results will be updated automatically.



2. In the Formats For list box, select the datablock format you want.



Each area can also be assigned a datablock format default which can be different from the applied format. The default datablock format is automatically applied for the Component Editor and all new One-Lines from that point on

To set a datablock format default


2. Under Type, choose the area for which you want to set the format.

3. In the Formats list box, select the datablock format you want to apply as the default.

4. Click the Set Default button. The default datablock format appears at the bottom of the dialog box. The default format is always displayed at this location.

5. Repeat steps 1 through 4 for each area to which you want to set the datablock format default.



8/16/2006

5.4. Viewing Datablocks You can view your datablocks in the One-Line Diagrams, TCC Drawings and from the Component Editor. This section summarizes how to view the datablocks that you have applied. All of the instructions contained in this section assume that you have already applied a datablock format to the area of the program you’re interested in. If you don’t know how to apply datablock formats, refer to Section 5.3, “Applying Datablock Formats.”

5.4.1. Viewing Datablocks on a One-Line Diagram Because you have already applied a datablock format, viewing datablocks in the One-Line Diagram is as simple as turning them on and off. When datablocks are on, you can see the datablocks and manipulate them on the One-Line Diagram or TCC. When datablocks are off, they removed from the One-Line Diagram or TCC Drawing completely; that is, you can neither see nor manipulate them.

Tip: With Datablocks turned on, you automatically include all datablocks for all component types. If you want to see datablock information for a single component or a small number of components, you can turn them groups of them on and off using Oneline>Datablocks>Not Visible or TCC>Settings>Selected Device Settings.

The following instructions assume that a One-Line Diagram is active.

To View Datablocks on a One-Line Diagram or TCC Drawing

• Either click the View>Datablocks command or click the click the Toggle Datablocks button .

5.4.2. Viewing Datablocks with the Probe You can also access probe mode from within One-Line Diagrams. Using the probe mode, you can click on individual One-Line Diagram symbols and see the datablock for that component in a temporary popup window. The window and remains visible until you select another component, or exit the probe mode.

You might find using the probe more convenient than One-Line Diagram datablocks in the following situations:

• Use the probe if you want to see different datablock formats quickly, without changing the format for the entire One-Line Diagram.

• Use the probe when the level of zoom on a One-Line Diagram, particularly on a large One-Line Diagram, makes the One-Line Diagram datablocks illegible. Unlike the datablocks on the One-Line Diagram, the size of the probe’s popup window is constant and is easily legible regardless of the level of zoom on the One-Line Diagram.



To use the probe

1. Apply a datablock format using the Run>Datablock format command. You will need to select the radial button for Probe before applying the selected datablock format.

2. Either click the View>Probe command or click the probe button .

The pointer becomes the probe pointer.

3. Click any component. The datablock for that component appears in a popup window.

4. Repeat step two for any component you want.

To exit the probe mode, repeat step 1 of this procedure.

5.4.3. Viewing Datablocks in the Component Editor The currently applied datablock is always available from the Component Editor. The datablock occupies its own subview, which is called Datablock for all component types. If the Datablock subview is blank, it means either that no datablock format has been applied, or that no datablock is defined for that component type in the applied format. For example, you may have a datablock format that contains datablocks for transformers only. In that case, the datablock subview for any other component type would be blank.

In probe mode, the pointer becomes a hand

When you click a component, the datablock appears in a popup window.


8/16/2006

5.5. Creating Datablock Formats If none of the pre-defined datablock formats meet your current needs, you can define a new datablock format. When you create new datablock formats, you decide which component types have datablocks, and which component attributes to include in the datablock. You can also create custom datablock labels which appear on the final datablock.

Datablock formats are maintained in two separate lists: one for the Component Editor and TCC Drawings, and one for the One-Line Diagram and probe. When you create a new datablock format, be sure to select the area you want so that the new format is saved into the correct list. You can create a new datablock format for any area you wish at any time. For example, even if a One-Line Diagram is active, you can still create a new datablock format for the Component Editor.

To create a datablock format


2. Under Type, choose the area for which you want to create the new format.

3. Click the New button.

4. In the Name box, type a name for the new datablock format. This name should be as descriptive as possible for quick identification.

5. In the Component box, select a component type to include in the datablock format.

6. In the Available Attributes, select a component attribute you want in the datablock.


If you want to Do this Add a component attribute to the bottom of the datablock.

Choose the Add button.

For each datablock in the format, select a component type. . .

Format the Attribute Template exactly how you want the attribute to appear in its final form. . .

and choose whether or not you want this component’s datablock to appear when its value is zero or non-

i t t

Select the attributes you want to include in the datablock. . .

Vector and Complex options are available for customizing unbalanced/Single-phase values.



If you want to Do this Insert a component attribute in the middle or at the top of the datablock.

In the displayed Data box, select the datablock line beneath location for the new line, and choose the Insert button.

8. In the Attribute Template box, edit the datablock label as it should appear on the final datablock. For further information, refer to the next section “Editing the Attribute Template.”

9. Repeat steps 6 through 8 for each component attribute you want to include in the datablock.

10. Add as many new component types as you want by making another selection in the Component Box. You can display information for different component types (buses, cables, motors, etc.) in the same datablock format.


When you have created a new format, you return to the Datablock Format dialog box, and the new format is added to the list of formats defined for that area. At this point, you can apply the format or set it as a default for the project.

5.5.1. Editing the Attribute Template This box controls how the attribute will be displayed. Typically you will see regular text followed by a numerical placeholder. For example, the Ampacity attribute’s template for cables appears like this: “CableAmpacity %1 %2.” The regular text (“CableAmpacity”) shows up in the datablock as it appears in the attribute template box—you can edit this text any way you like, or even delete it. The numerical placeholder (“%1 %2”) does not show up in the datablock; rather, PTW replaces it with the numerical value (if any) of the attribute (if there is no numerical value, nothing appears). This text can also be edited, but it is best not to because if you remove this placeholder PTW will not insert the value. The %1 represents the numeric value of the attribute and the %2 represents the unit in which the value is measured. In this example, if the cable’s ampacity is 100 A, the attribute will appear in the datablock like this: CableAmpacity 100A (the %1 is replaced by 100 and the %2 is replaced by A). You can also control the number of decimal places displayed in the datablock by adding a decimal place after the value placeholder. For example, %1.0 will display zero places after the decimal point and %1.2 will display 2 decimal places after the decimal point.

5.5.2. Using the Show Zero Value/Blank Text check box When checked, attributes will be shown even if they equal zero or are blank. When unchecked, only those attributes which report an amount will be displayed. The advantage to leaving this box unchecked is that your drawing won’t be cluttered with unneeded datablocks that merely show a zero value.

Note: When you change this option, you are only changing it for the active component type, not for the whole datablock format. For example, you could have this box checked for buses and generators but unchecked for motors and protective devices. If you want to check this box for all components, you need to select each component individually in the Component box and then check this box.


8/16/2006

5.6. Editing Datablock Formats At any time, you can change your datablock formats. You can add component types, delete component attributes, and change the sequence of lines in existing datablocks.

With all these steps, you must first open the datablock format box either by clicking the Run>Datablock Format command or clicking the Datablock Format toolbar button .

To add component types and attributes to a datablock format

1. In the Component box, select the component type you want to add to the datablock format.

2. In the Component Data box, select the component attribute you want to appear in the datablock format.


If you want to Do this Add a component attribute to the bottom of the datablock.

Choose the Add button.

Insert a component attribute in the middle or at the top of the datablock

In the displayed Data box, select the datablock line beneath location for the new line, and choose the Insert button..

8. In the Format box, edit the datablock label as it should appear on the final datablock.

9. Repeat steps 6 through 8 for each component attribute you want to include in the datablock.

10. Click the OK button. To remove component attributes from a datablock

1. In the Displayed Data box, select the component attribute you want to remove.

2. Click the Remove button.

To change the order of display in a datablock, you must remove an attribute and then replace it in a new location.

To resequence the lines of a datablock

1. In the Component box, select the component type you want to edit.

2. In the Displayed Data box, select the attribute you want to move.

3. Click the Remove button.

4. In the Device Data, select the attribute that you removed.

5. In the Displayed Data box, select the datablock line beneath the location for the attribute you removed.

6. Click the Insert button.

7. Repeat these steps for each attribute you want to move.




5.7. Copying and Deleting Datablock Formats You can copy or delete datablock formats at any time. You can delete datablock formats that are active or selected, but be aware that those formats will disappear from any open One-Lines.

To copy a datablock format


2. Under Type, choose the type of datablock you want to edit.

3. In the Formats box, select the format you want to copy.

4. Click the Edit button.

5. In the Name box, type a name for the datablock format copy.

6. Click the OK button. The copy is saved under the new name, and the original datablock format is not changed.

To delete a datablock format


2. Under Type, choose the type of datablock you want to edit.

3. In the Formats box, select the format you want to delete.

4. Click the Delete button.

5.8. Creating and Printing Datablock Reports Earlier in this chapter we demonstrated how to create custom datablocks. Their ease of use may have concealed their significance, but keep in mind these facts:

• Datablocks are a data-display tool.

• Datablocks are customizable.

• Datablocks let you display almost any piece of data about a component.

• Datablocks let you choose as many or as few pieces of data as you want.

• Datablocks let you choose different pieces of data for each component type.

In this section, we will add two more facts to this list:

• Datablocks may be printed in a spreadsheet-style report format.

• Datablock Reports may be created for whatever components you choose.

The ability to manipulate and print data in this way represents one of PTW’s most important and powerful features, and will reward your effort in learning how to use them.

Datablock reports are particularly useful for creating custom equipment lists such as cable lists, motor lists, load lists, etc. A sample datablock report for cable data follows. The lists can be printed directly or saved as an Excel spreadsheet file.


8/16/2006

5.8.1. Creating, Saving, and Printing Datablock Reports When you first create a Datablock Report, it appears in spreadsheet form:

To create a Datablock Report

1. Run the Datablock Format command (on the Run menu) to pick what data you want to show for each component type in the Datablock Report.

2. Click the Run>Datablock Report command.

You may save this spreadsheet either in PTW’s Report form or as a Microsoft Excel-compatible spreadsheet:

To save the Datablock Report

1. Click the Save button

2. Choose the Format as either *.RPT (PTW’s Report format) or *.XLS (Microsoft Excel-compatible format).

You may print the Datablock Report right from this spreadsheet (alternately, you may open the *.RPT in PTW or a word processing program and print it, or open the *.XLS file in Microsoft Excel and print it):

To print the Datablock Report

1. Click the Print button.

5.8.2. Formatting the Datablock Report You can use the Alignment and Font buttons to modify the spreadsheet. For more advanced formatting, open the *.RPT file in a word processing program, or the *.XLS file in Microsoft Excel.



5.8.3. Choosing What Data will Appear In regard to choosing what data will appear, the Datablock Report works just like Datablocks⎯it uses the Datablock Format you select. Put simply, the Report will display whatever data the Datablock Format tells it to display. Therefore, you should become familiar with customizing Datablock Formats. You can use the pre-defined Formats included with PTW, but the Report’s true flexibility comes when you can select the data you want to show. We recommend you review the procedures discussed in Section 5.5, “Creating Datablock Formats.” Once you can create custom Datablock Formats with ease, Datablock Reports will become your best tool for displaying data.

Important: For data to appear in the Datablock Report spreadsheet, a Datablock Format must have already been applied to that area using the Datablock Format command. As explained in Section 5.3, “Applying Datablock Formats,” Datablock Formats only apply to a specific are type. For example, if you want to view the Datablock Report spreadsheet for a TCC Drawing, even if you have applied a Datablock Format for the One-Line Diagram, no data will appear until you apply a Datablock Format for the TCC Drawing, too.

5.8.4. Choosing Components for Reporting A great feature of Datablock Reports is that they allow you to choose specific components for reporting. That way, you get the data for just the components you need. For example, say you only want to report the voltage drop for the five buses in a particular branch, not for all the buses in the project. Using a Datablock Report, there’s no need to sift through the hundreds of buses in the Load Flow/Voltage Drop Report. You just set up a Datablock Format that displays voltage drop for buses, choose those five buses, and create the Report.

For the Component Editor All the components appearing within the component set in the Component Editor will appear in the Datablock Report spreadsheet. If the Datablock Report spreadsheet appears empty when you run the Datablock Report command, either no Datablock Format has been applied for the Component Editor, or no attributes have been assigned to the component types presently shown in the Components Box.

Tip: Queries work quite well in the Component Editor to narrow the component list down to those you need for your Datablock Report. Even if you aren’t that familiar with Queries, try running basic ones, such as All Buses. You will find that queries add power to the Datablock Reports, since you can quickly narrow the component list to just the handful on which you need information.

For a One-Line Diagram If you have some components selected on the One-Line Diagram, only those components will appear in the Datablock Report spreadsheet; if you have no components selected, all the components on the One-Line Diagram will appear in the Datablock Report spreadsheet. If the Datablock Report spreadsheet appears empty when you run the Datablock Report command, either no Datablock Format has been applied for the One-Line, or no attributes have been assigned to the component types that have been selected.


8/16/2006

Tip: Since the Datablock Report only applies to the selected components, you can simply draw a box around a group of components and run the Datablock Report. This is especially effective if you only want to report on a specific branch. You can also run a Query to select specific components.

For a TCC Drawing All the components within the active TCC Drawing will appear in the Datablock Report spreadsheet. If the Datablock Report spreadsheet appears empty when you run the Datablock Report command, either no Datablock Format has been applied for the TCC Drawing, or no attributes have been assigned to the component types that are on the TCC Drawing.

Tip: If you only want to report on certain components in the TCC (for example, only the protective devices, not the cables or motors), copy the TCC then open the copy and remove the components you don't want to report using the Component>Remove command before running the Datablock Report. Once you have run the Datablock Report, you can delete the TCC copy.



5.9. Creating User-Defined Fields Throughout this chapter, you have probably come to understand the term component attributes to refer to those attributes included with PTW—attributes such as “AmbientTemperature” for cables or “RatedSize” for non-motor loads. We have shown how you can view these attributes in the Component Editor, One-Line Diagrams, TCC drawings and printed in a report. We will now show how you can create additional component attributes, or “user-defined fields,” and assign your own data to them.

2-Winding Transformer ComponentName Size (kVA) Location: TX A 20000.0 Wye-Ground Ground Floor Transmission Line Xpos Ohms (Ohm/mi) Xzero Ohms (Ohm/mi) Location: 0.4150 0.8300 Grid 75-A HV/MV Breakers Name/Type BusConnected Location: CB1 001-UTILITY CO 5th Floor, Room 8

Show user-defined fields in datablocks on the One-Line Diagram. Here we've used them to identify the physical locations of components.

Use the power of queries to retrieve component by the user-defined fields. Here we've retrieved all protective devices located on the 2nd floor, West Wing.

Display user-defined fields in Datablock Reports just like component attributes.


8/16/2006

These are just some of the many ways to use user-defined fields:

• track inventory;

• list power source;

• indicate component manufacturer;

• display purchase date and price of component;

• indicate physical location;

• list component’s subfeeds;

• assign employee to maintain component;

• show component’s serial number or inventory number;

• specify maintenance date and procedure;

• list vendor;

• and much more.

To create a new user-defined field

1. Click the Project>Options command and choose the User-Defined Fields option group, as shown in Fig. 1:

Fig. 1. The User-Defined Fields options.

Select a component type (we’ve selected the Component category in Fig. 1, which means the field will be created for all components—we’ll explain this concept in a moment) and click the New button. You can now create a text-based field or a



numeric field, as shown in

2. Fig. 2.

Fig. 2. Creating a new field.

3. Notice that the field we created now appears in the Attributes box, as shown in Fig. 3.

If you enter data here, be sure you really want to do so, because every component of the selected type will contain the data until you explicitly go to each component to modify it.


8/16/2006

Fig. 3. The field we created now appears in the “attributes” box.

Once you create a new field, it exists for all components of that type in the Project and will be created for all new components of that type. For example, in the above steps, we created a new field for the “Components” category, which means that every component in the Project will have the Location user-defined field we created. If we had instead selected a specific component, such as “cables,” the Location user-defined field would only exist for the cables in the Project. As Fig. 4 indicates, components belong to classifications, so when you create a user-defined field for a classification as opposed to a component type, you are really creating the user-defined field for all the component types in that classification. For example, let’s say you create a user-defined field called “Price” for the Impedance classification. By doing so, you are actually creating the “Price” user-defined field for cables, 2-winding transformers, 3-winding transformers, transmission lines, and pi impedances.

Source

Impedance

GeneralLoad

Protective Device

Bus

Schedule

Motors

Non-MotorLoad

Cable2-Winding Transformer3-Winding TransformerTransmission LinePi Equivalent Impedance

Synchronous MotorInduction Motor

Non-Motor Load

GeneratorUtility

Fig. 4. The classes of components in PTW.



5.9.1. Text Fields versus Numeric Fields At the time of creation you choose whether the user-defined field will be a text field or a numeric field:

For most uses, the text field provides more flexibility, because you can type text and numbers in them. Numeric fields, though, can perform range checking and Metric-to-Imperial conversions.

Use text fields if you want to:

• enter any text;

• enter dates;

• enter numbers that include text (for example, a part number such as “2E5A4”).

Use numeric fields if you want to:

• enter numbers only;

• ensure that any number entered falls within a specified range (called “Range Checking”);

• automatically perform Metric-to-Imperial conversions.

Selected as string-type.

Selected as numeric-type.

These boxes aren't used.

Use these boxes to establish the number of decimal places, whether to perform range checking and the range to check, and the units of measurement.


8/16/2006

Range checking occurs at the moment you type data in the user-defined field in the Component Editor, while Metric-to-Imperial conversions occur if you change the Engineering Standard (located under Project>Options>Application Options) from ANSI to IEC or vice versa.

5.9.2. Date, Time and Currency Fields Date, time and currency fields allow you to add user-defined fields in specific formats. Date fields can be used to store information about when equipment was purchased, installed, or when maintenance is scheduled or completed. Date and time fields can be combined to create complete maintenance schedules. Currency fields can be used to keep track of equipment costs, replacement costs, expansion cost estimates, etc.

5.9.3. Changing data in a User-Defined Field When you create a user-defined field for a component type (or for a component classification), every component of the selected type will now have the user-defined field in its User-Defined Fields subview of the Component Editor, as shown in Fig. 5. You use this subview to change the data for a component’s user-defined field.

Fig. 5. The user-defined field subview.

Note: When you create a user-defined field, you create it for all the components of that type in the Project. However, when you edit a specific component’s user-defined field, you only change it for that specific component.

For example, as the following pictures indicate, the Location attribute exists for all components—including the three we have shown, Cable 1, Cable 2, and Cable 3.

One of the following codes will be displayed next to each user-defined field:

S: String N: Numeric D: Date T: Time C0: Currency (no decimal) C2: Currency (2 decimal places)



Cable 1:

Cable 2:

Cable 3:

Now, suppose we enter the words “Basement Level A” in the user-defined field for Cable 1. The data is now different for Cable, 1, but it doesn’t change for Cables 2 and 3:

Cable 1:

Cable 2:

Cable 3:

Note: When entering fractions, if you want to enter a fraction with a leading integer (for example, 1 1/3) you can enter it directly. However, if there is no leading integer (for example, 2/3), be sure to precede the fraction by a zero and a space (as in 0 2/3).

5.9.4. Querying with User-Defined Fields You can search for components based on the data in their user-defined fields just as you search for data in component attributes.

The data we enter in one component's user-defined field does not change the data in that same user-defined field for any other components.


8/16/2006

To query based on a user-defined field

1. Click the Run>Query command and set up your query as discussed in the Queries chapter of this User’s Guide.

2. Select the user-defined field from the Attributes box, as shown in Fig. 6. As you can see, PTW treats the user-defined fields just like the component attributes included with PTW.

Fig. 6. The user-defined field appears along with the standard attributes in the Query dialog box.

5.9.5. Displaying User-Defined Field data Because PTW treats user-defined fields just like regular component attributes, you can include user-defined fields in One-Line Diagram datablocks and Datablock Reports.

To include a user-defined field in a datablock

1. Click the Run>Datablock Format command and set up your datablock format as discussed in the “Creating Datablock Formats” Section on page 5-8.

2. Select the user-defined field from the Attributes box, as shown in Fig. 6. As you can see, PTW treats the user-defined fields just like the component attributes included with PTW.



Fig. 7. The new field appears along with the standard attributes in the Datablock Format dialog box.

5.9.6. Copying User-Defined Fields to Other Projects If you want to copy any of these user-defined fields to another project, you do so by first copying them to the “New Project Set”, then opening the other project and copying them into that project from the “New Project Set.”

The “New Project Set” is a file which stores user-defined fields. By default, the file is named “desr.udf” and can be found in the ptw32\lib folder. When you create user-defined fields in a Project, you can copy the user-defined fields into this file so you can then copy them into other Projects at a later time. Similarly, you can create user-defined fields directly in this file, then copy them into the current Project.

To copy a user-defined field to the New Project Set, select the field in the Attributes box and click the Selected button. You can also click the All button to copy all the user-defined fields into the New Project Set.

To create user-defined fields directly in the “New Project Set,” first select the New Project Fields options subview and start creating fields. When you create user-defined fields in the New Project Set, you are not creating them in the current Project. Once you have created a user-defined field in the New Project Set, you can copy that user-defined field into your current project by selecting the user-defined field in the Attributes box and clicking the Selected button. You can also click the All button to copy all the user-defined fields from the New Project Set into the current Project (you must have a Project open, of course).

If you have created a user-defined field in the Current Project Fields subview and want to copy it to the New Project Set, switch to the Current Project Fields subview, then select the field in the Attributes box and click the Selected button to copy it to the New Project Set.


8/16/2006



6 Queries

Queries represent the most flexible and powerful means of selecting and retrieving components. Using queries, you can search through all of the components in your project or on your One-Line Diagram, and retrieve just the information you want. With queries you can set any criteria you want for a search, no matter how specialized: find your largest motors, cables with large voltage drops, largest motor loads, and much more.

This chapter includes:

• What is a query?

• Running queries.

• Query results in different windows.

• Designing custom queries.

• Designing complex queries.

IN

TH

IS

CH

AP

TE

R

6.1. What is a Query? .............................................................................................. 6-2 6.2. Before Running a Query................................................................................... 6-2 6.3. Running a Query............................................................................................... 6-3 6.4. Query Results in the Component Editor vs. the One-Line Diagram................. 6-5 6.5. Organizing Queries........................................................................................... 6-6 6.6. Copying and Deleting Queries.......................................................................... 6-7 6.7. Custom Queries ................................................................................................ 6-7 6.8. Advanced Queries........................................................................................... 6-13


8/16/2006

6.1. What is a Query?

A query is a filter that searches through your project and retrieves or selects just the components you want while filtering out the rest. You can run a query either from a One-Line Diagram or from the Component Editor.

PTW comes with may useful queries that are already defined, but you can also add your own queries using the powerful yet simple Query Editor. Custom queries can search on single or multiple component types and multiple component attributes. The specificity of the question is completely under your control: you choose which components and attributes to search on.

Here are just some of the things you can do with a query:

• Retrieve specific components: Retrieve a list of all motors that are larger than 100 horsepower, or all dry type transformers that are ∆/ΥG connected, and so on.

• Locate problem spots in a system: Retrieve a list of cables that have a voltage drop of greater than 3%.

• Manage your project: In very large projects limit your component list to a manageable group. If want to look at only induction motors over 800 hp, running a query can temporarily move substantial amounts of data out of your way.

• Quickly identify network distribution: Use a query in conjunction with a One-Line Diagram to determine where your largest loads or your largest generators are located.

Note: Queries never change the contents of your project; they simply limit the portion of the project displayed at a given time.

6.2. Before Running a Query Queries are specific to the active window (that is, a query run on the One-Line Diagram won’t affect the Component Editor). For this reason, it is important to have a clear idea of your goals before you run the query. Consider the following questions: What actions do

Run a query for 500 hp motors.

Queries UG 6-3


you want to perform after you run the query? What portion of the database do you want to search? The answers can help you determine where you want to run the query. Refer to the following guidelines:

• Scope: If you want to search on the entire project database, you should query from the Component Editor; One-Line Diagram queries search only the components that are represented on the active One-Line Diagram, which may not be the contents of the entire project.

• Goal: If you want to get a spatial idea of where your biggest generators are located in relationship to the rest of your system, run the query from a One-Line Diagram. One-Line Diagram queries are also useful if you want to perform simple tasks on the entire query set. For example, you can disconnect all of your queried components with one command. If on the other hand you want to edit the component data, run the query from the Component Editor.

6.3. Running a Query Queries populate the active window with a retrieved component list (query set), so in order to run a query either the Component Editor or a One-Line Diagram must be active. The effect of running a query is instantaneous, and applies only to the active window. If you are working in a One-Line Diagram, for example, running a query searches only the contents of that One-Line Diagram; neither the Component Editor nor any other open One-Line Diagrams are affected. Because queries are window-specific, you can open several One-Line Diagrams and display different query results in each one. For further information on viewing the results of your queries, see Section 6.4, “Query Results in the Component Editor vs. the One-Line Diagram.”

PTW comes with several pre-defined queries, but if none of these queries is appropriate for the type of search you want to perform, you can create a custom query easily using the Query Editor.

Select the query you want to run.

Click the Run button to run the selected query.

Replace previous query results, or merge query results with the current query set.


8/16/2006

To run a query

1. Click the Run>Query command.

2. Under Query Category, select the category from which you want to select your query.


• If you want to replace the results of the last query with the results of the new query, select the Replace option button.

• If you want to combine the result of the query with the results of a previous query or queries, select the Merge option button.


• In the list box, select the query you want to run, and choose the Run button.

• In the list box, double-click the query you want to run.

If the query has prompt values in it, the Query Prompt dialog box appears, in which you can specify attribute values. For further information, refer to the next section, “Responding to Query Prompts.”

6.3.1. Responding to Query Prompts You can design custom queries with internal prompts that ask you to supply one or more attribute values as you run the query. If the query you are running contains prompts, the Query Prompt dialog box appears at run time.

The Query Prompt dialog box requests a particular attribute value, and shows you the entire query definition so that you can see clearly how the prompt attribute relates to the entire query. In the example above, the condition line prompt is “SELECT Cable WHERE Ampacity >,” and your response would be a number such as 500 to search on all cables with an ampacity of 500 A or greater.

The condition line requests the value of a particular component attribute, in this case cable ampacity.

In the response box, type the attribute value.

The Query Definition shows you how this condition line relates to the whole query.

Queries UG 6-5


If there is more than one prompt in the query, PTW runs through the prompts sequentially, each time displaying the appropriate condition line above the text box, and highlighting that condition line in the query definition below. For information on creating prompt queries, refer to Section 6.7, “Custom Queries.”

6.4. Query Results in the Component Editor vs. the One-Line Diagram The results of a query in the Component Editor are much different from those in a One-Line Diagram, and the following sections explain query results in both.

For the purposes of comparison, let’s assume that you ran a query on all two-winding transformers from a One-Line Diagram and from the Component Editor. Let’s also assume that you chose to replace rather than merge the query set.

6.4.1. Query Results in the Component Editor After you run the query, the set of components in the component list box is replaced by the query set, in this case all two-winding transformers. A query on the component editor always searches the entire project database.

Notice that the Query option button is selected, meaning that the component set currently displayed is the result of one or more queries. To switch between the query set and another component set, select the option button that corresponds to the set you want. For example, to switch to the set of all components, select the All option button. When you switch to another set, PTW remembers the contents of your Query set, and you can restore that set at any time by selecting the Query option button.

The query set is not dynamically linked to the database, so its contents do not change until you run another query, regardless of any edits you make to the components. For example, if you generate a query set including all motors over 500 kVA, and then change the size of one motor to 400 kVA, that motor does not “disappear” now that it is no longer satisfies the original query criteria. If you rerun the query, however, that motor does not appear in the query set.

The active component set becomes the query set.


8/16/2006

6.4.2. Query Results in a One-Line Diagram After you run the query, the query set appears in the selected color, which is blue by default. Because all of the components in the query set are selected on the One-Line Diagram, any action you perform applies to all of them. You can disconnect them, delete them or take them out of service with a single command.

The status bar displays how many components in the project met the query’s criteria and how many of these components are on the active one-line:

You can deselect your query set at any time, either by using the mouse to select a new component or group of components on the One-Line Diagram, by running another query, or by clicking a blank portion of the One-Line Diagram.

If any components are selected when you run a query, the query automatically de-selects them.

Tip: If you want to edit data for the queried components, you can move the entire group into the Component Editor by clicking the Window>Go to Component Editor command.

6.5. Organizing Queries PTW sorts queries in any number of categories that you specify. You can make categories based on any criteria you want. For instance, you can create a category for load flow data queries, motor queries, impedance component queries and so on. Usually you assign a category when you create a query, as described in Section 6.7.2, “Adding Custom Queries.” If you don’t assign a category when you create the query, the query belongs only to the All Queries category. Having only one category is fine if your query list is relatively short, however as your query list grows you may find it necessary to assign your queries to more specific categories.

The advantage to categorizing queries is that it makes them easier to find. For instance, you can create a Motor Queries category for all queries that pertain to motors. Then,

Queried components appear in the selected color (blue by default).

Queries UG 6-7


rather than having to scroll through the All Queries category, you can select the Motor Queries category to limit the query list.

To change categories for an existing query


2. In the query list box, select the query you want to place into a query category.

3. Click the Edit Button. This opens the Query Editor.

4. In the Category box, do one of the following:

• If you want to create a new category for the query, type the name of the category you want to create.

• If you want to place the query into an existing category, select the category name from the list.

5. Click the OK button. This assigns the query category, and returns you to the Query dialog box.

6.6. Copying and Deleting Queries From the Query dialog box, you can copy and delete queries very quickly, and at any time.

To copy a query

1. In the Query list box, select the query you want to copy.

2. Click the Edit button.

3. In the Name box, type a unique name for the query copy. PTW does not accept duplicate query names.

4. Click the OK button. The copy appears in the query list box, and the original query is not changed.

To delete a query

1. In the Query list box, select the query you want to delete.

2. Click the Delete button.

6.7. Custom Queries Each project has specific needs, and PTW’s Query Editor lets you design your own queries to meet those needs. Designing queries gives you the power to retrieve just the components you want. When you design queries, you decide which components to include, which attributes to search on, and all of the search values.

6.7.1. Query Building Blocks In order to design effective custom queries, you need to know about the parts of queries, and how those parts work together to retrieve the query set.


8/16/2006

Queries are hierarchical structures, containing two main divisions:

• Component sets contain all of the search information pertaining to a single component type or component group (cables, motors, impedance components, and so on). Because you can search on several criteria, a component set can consist of several individual searches.

• Condition lines define a single search criterion for a given component set. A condition line is a complex structure consisting of search criteria and logical operators.

Each query can contain several component sets, and each component set can contain several condition lines.

Fault Duties

Buses

Induction Motors

Initial Symmetrical Fault Current >10,000 A

Horsepower => 500 hp

Query Name

ComponentSet

Condition Lines

This fault duty related query searches on all buses in the system with a calculated fault duty greater than 10,000 amps, and on induction motors rated equal to or larger than 500 hp.

Condition Line The smallest (and most complex) discrete building block of a query is called a condition line. Basically, a condition line asks a single question of your project, the question always compares a component attribute (such as synchronous generator power factor) to a known value (such as 0.85), and it retrieves those components for which the condition line is true.

You edit condition lines in the Component Editor Dialog box, shown below. For a step-by-step procedure for creating custom queries, refer to Section 6.7.2, “Adding Custom Queries.”

Queries UG 6-9


Each condition line comprises four distinct parts, each of which you assign: component set, attribute, operator, and value. In order to create a valid condition line, you have to define all four parts. The combination you choose determines which records are retrieved.

You can also combine several condition lines in a single component set to search on a more complex set of criteria. For example, you may want to search on motors that are larger than 500 hp, and that are out of service. When you combine condition lines, your query searches on components that satisfy all of the condition lines, by default. For more information on this default and overriding it, see Section 6.8.1, “Adding Boolean Operators.”

Component Set

A component set elects a component set for the condition line. This selection limits the search to a component type or group of component types.

A component set contains all the query information about one component type, or a group of components. For instance, a single component set might ask about three separate component attributes. For cables, you might be interested in searching on voltage, insulation type and length, for example. All three searches taken together compose the cable component set. A single query can contain several component sets: a query might contain one component set for two-winding transformers, one for induction motors and one for source components (generators and utilities).

The Component Set box contains groups of components that are arranged according to function allowing you to consolidate several component types into a single condition line. For example, you can query all of your impedance components simultaneously by selecting the Impedance Component group rather than creating condition lines for each component type individually.

Pick the component type or types.

Pick the component attribute.

Pick the logical operator.

Pick the target value.

When you are finished with the condition line, choose the Insert button to insert the condition line into the query definition.


8/16/2006

Attribute

An attribute tells the query which component attribute you are interested in. Because each component type has its own set of attributes, the selections available in this field will depend on the component type. For example, cables are associated with length, size, connected kVA, connected power factor, and so on. Each condition line can ask for information on only one attribute. To get information on more than one attribute for a given component type, you must combine two or more condition lines in the component set.

Operator

An operator represents the required relationship between the component attribute and a known value. PTW offers the following list of relational operators:

Operator Meaning < Less than

<= Less than or equal to

<> Not equal to

= Equal to

> Greater than

>= Greater than or Equal to

Note that for attributes defined as text — Component Name for example — only the equal to operator (=) is available.

Static Value

A value provides a static value as a target for the component attribute. The contents available in this field vary depending upon the component attribute. For example, if you choose “In/Out of Service” as the attribute, you will be able to choose either “In” or “Out” in this box. If you choose rated kVA as the attribute, you will be able to type a number.

If you anticipate changing this value frequently, you can choose the Prompt button which instructs PTW to prompt you for a value each time you run the query.

If the value field in your condition line requires a text value, you can use an asterisk or question mark (* or ?) as wildcard characters. Use the * in the target value to represent any string of characters, and the ? to represent for any single character. When mixed with alphanumeric characters, wildcards can be very powerful. For instance, you can search on all values that begin with the letter C by typing C* in this field. You can also use the wildcard characters between alphanumeric characters: S*N retrieves all values that begin in S and end in N regardless of the number of characters in between (for example, Saturn, satin, sun). S??N retrieves all four-letter values that begin in S and end in N (for example, stun, swan, scan).

Sample Condition lines When all of the pieces of a condition line are assembled, they form a query syntax that PTW automatically converts into a text-based query definition. Refer to the table below for a sampling of possible condition lines and the component list that each lines retrieves.

Component Set Attribute Operator Value Query Retrieves ... Induction Motor Rated kVA < 500 All induction motors that have a

rated kVA of 499 or lower

Queries UG 6-11


Component Set Attribute Operator Value Query Retrieves ... rated kVA of 499 or lower.

Cable Size >= Prompt All cables that have a size equal to or greater than a number you specify at run time.

Motor Component In/Out of Service

= Out All synchronous and induction motors that are out of service.

6.7.2. Adding Custom Queries If your group of pre-defined queries does not meet your needs, you can add a custom query to the list at any time.

To add a custom query, you should be familiar with the parts of a query and their functions. If you are not familiar with the parts of a query, refer to Section 6.7.1, “Query Building Blocks” for a detailed description of each part.

If the query you want to design is particularly complicated, refer to this section and to Section 6.8, “Advanced Queries” for further instructions on editing the query definition directly.

To add a custom query


2. Press the New button. The Query Editor Appears.

3. In the Name box, type a name for the new query. This name should be as descriptive as possible for quick identification. The only restriction in naming is that you can’t start the query name with an asterisk (*), because those names are reserved by PTW.

4. Optional: In the Category box, do one of the following:

• If you want to create a new category for the query, type the name of the category you want to create.

• If you want to place the query into an existing category, select the category name from the list.

5. In the Component Set box, select the component set to search on. Note that the component set can be a single component type such as cables, or a component group such as impedance components.

6. In the Attribute box, select the component attribute to search on.

7. In the Op box, select a comparative operator. Depending upon the component and attribute selected, you may or may not have access to all of the comparative operators.

8. Under Value, do one of the following:

• If you want to assign a comparison value that never changes, type in a value in the text box.

• If you want to assign a comparison value that changes from query to query, choose the Prompt button. With Prompt selected, PTW asks you to type in this value each time you run the query.

9. Click the Insert Button.


8/16/2006

If no condition line is selected, or if the selected query line belongs to a different component set, a new component set is added to the query definition. If the selected condition line belongs to the same component set, then the condition line is inserted into the current component set, just above the selected line.

10. Repeat these steps for each condition line.

11. Optional: For complex queries, you can insert Boolean operators and change Boolean operator precedence after the query lines are defined. See Section 6.8, “Advanced Queries” for instructions.


As you add condition lines to the query, notice that PTW updates the query definition displayed near the bottom of the dialog box to incorporate all of the component sets and condition lines.

After designing a query, run it on a sample case to make sure that it retrieves the components you expect. If it doesn’t, you can edit and replace condition lines, as described in Section 6.7.3, “Removing Condition Lines.”

6.7.3. Removing Condition Lines and Component Sets If the needs of a particular query change slightly, you can edit an existing query to meet those new needs. For example, your definition of a large motor might change from 300 to 500 hp. In order to maintain a relatively short query list, you should edit an existing query whenever possible. To edit a condition line, you need must first remove the existing condition line, and then replace it with the one you want. You can replace single condition lines or entire component sets.

To remove a condition line


2. In the queries list box, select the query you want to edit.

3. Click the Edit button. The Query Editor appears showing the selected query.

4. In the query definition box, select the condition line you want to replace.

5. Click the Clear Line button.

6. Optional: Create a new condition line to replace the deleted line, using the process outlined in Section 6.7.2, “Adding Custom Queries.”

7. Repeat these steps for all of the condition lines you want to change.

8. Click the OK button. To remove a component set


2. In the queries list box, select the query you want to edit.

3. Click the Edit button. The Query Editor appears showing the selected query.

4. In the query definition box, select the first line of the component set you want to replace. The first line of a component set always takes the form of SELECT [component] ... WHERE).

5. Click the Clear Set button.

Queries UG 6-13


6.8. Advanced Queries With advanced querying techniques, you can control the relationships among the parts of the query to make them more complex than otherwise possible. These techniques are particularly helpful for large projects, when you want the retrieved list to be as specific as possible. A sample advanced query might search on induction motors that are smaller than 50 hp or induction motors that are out of service, but not both. When queries get this complex, you need to set your own query parameters by editing the query definition text shown in the Query Editor.

The query definition is a text-based form of your query with a grammar and a syntax that tells PTW how to perform your query. PTW automatically writes and maintains the query definition as you edit the query. There are two types of changes that you can make to the query definition to customize a query:

• Boolean Operators: These control the relationships among the divisions of the query, and determine the inclusiveness of your search (that is, how many of the criteria must be satisfied to include a component in the retrieved list). In the syntax of a query definition, the Boolean operator works like a conjunction (AND, OR, and so on).

• Boolean Operator Precedence: This determines the sequence in which the Boolean operators are resolved.

6.8.1. Adding Boolean Operators Condition lines have to express a relationship in order for a query to work, and that is the role of the Boolean operator. By default, condition lines are bound together with the AND Boolean operator which searches on components that satisfy both condition lines. In some cases, however, you may want to search on one condition line or another, or one condition line and not another. In such cases, you can use the Query Editor to add a Boolean operator between two condition lines.

As you work, the Query Editor maintains the query definition in this box.


8/16/2006

You can choose from among four different Boolean operators, which gives you a great deal of control over the inclusiveness of your search. Review the following table carefully for a thorough understanding of the available Boolean operators and their functions:

Boolean Operator Sample Expression Results AND Line 1

AND Line 2

Retrieves components that satisfy both Line 1 and Line 2.

OR Line 1 OR Line 2

Retrieves components that satisfy either Line 1 or Line 2 or both.

XOR (Exclusive or) Line 1 XOR Line 2

Retrieves components that satisfy either Line 1 or Line 2, but not both.

NOT Line 1 NOT Line 2

Retrieves components that satisfy Line 1 but not Line 2.

Note: The default Boolean operator between component sets (OR) cannot be edited because components and component groups are always mutually exclusive.

As an illustration, say that you want to retrieve a list of DT or OAFA transformer. If you create two query lines without a Boolean operator, the query definition looks like this:

SELECT 2-Winding Transformer WHERE { Key = DT Key = ONAF }

Component Set

To add a Boolean operator ...

Condition Lines

Choose one of the Boolean operator buttons.

Queries UG 6-15


While the condition lines in this query are correct, they are bound by the default AND Boolean operator, as follows:

Query

Key = ONAF

Key = DT

ANDANDAND

Two-Winding Transformers

A quick survey of the graph tells you that this query will not work because the AND Boolean operator tries to make the query set satisfy mutually exclusive attributes — a single transformer cannot be both a DT and an ONAF type. To correct the problem, you can add the OR Boolean operator between the condition lines.

SELECT 2-Winding Transformer WHERE { Key = DT OR Key = ONAF }

6.8.2. Changing Boolean Operator Precedence If condition lines are connected with only one type of Boolean operator, the query proceeds sequentially though the component set, resolving each Boolean operator before continuing to the next. For instance, if a component set contains condition lines 1 AND 2 AND 3, PTW resolves the first AND first, and then the second. For Boolean operators of a common type, this sequence makes no difference. However, when you combine different types of Boolean operators in the same component set, PTW must prioritize them. By default PTW resolves AND Boolean operators before OR Boolean operators. This sequence of priority is referred to as Boolean operator precedence: the AND Boolean operator takes precedence over the OR Boolean operator.

You can change the default Boolean precedence by grouping condition lines together using parentheses in the query definition. This imposes an internal structure on a component set, telling PTW how to resolve the query. Changing the Boolean operator precedence can dramatically affect the retrieved component list.


8/16/2006

To get an understanding of how changing precedence can affect the results of a query, look at the following equations:

3+2×5 = 13 (3+2)×5 = 25 Notice that while the number to the left of the equal sign remains constant, the sequence in which the operations are performed has been changed by grouping operations in parentheses, yielding significantly different results. Queries resolve themselves just like equations: they resolve the innermost set of parentheses first, and work their way to the outermost set. Let’s rewrite the equations above in terms of a query:

1 OR 2 AND 3 (1 OR 2) AND 3

In these queries, 1, 2 and 3 are condition lines. Because there is no differentiation in the first query, PTW follows the precedence default and resolves the AND Boolean operator first. Thus it retrieves all components that have both 2 AND 3, OR all components that have 1. In the second equation, the parentheses reverse the default precedence order, and the query retrieves all components that have 1 OR 2 AND all components that have 3.

Note: To create a valid group, you must be sure to insert parentheses in pairs. That is, for each open parenthesis “(” you must include a close parenthesis “)”. Each close parenthesis closes the nearest available open parenthesis. You can also nest parentheses, creating several levels of Boolean operations.

To change Boolean operator precedence

1. Define or edit a query that includes all of the condition lines you want, with the proper Boolean operators.

2. In the query definition box, select the condition line above which you want to insert the open parenthesis.

3. Click the “(” button. An open parenthesis appears above the selected condition line.

To change Boolean operator precedence, use the parentheses buttons.

Queries UG 6-17


4. In the query definition box, select the condition line above which you want to insert the close parenthesis.

5. Click the “)” button. A close parenthesis appears below the selected condition line.

As an illustration, say that you want to retrieve a list of DT or OAFA two-winding transformers with a nominal kVA between 50 and 100. If you create the query with all the proper Boolean operators, the query definition looks like this:

SELECT 2-Winding Transformer WHERE ( Key = ONAF OR Key = DT AND NomSize >= 50 AND NomSize <= 100 )

In this query, the AND Boolean operators take precedence by default so PTW resolves the first AND, proceeds to the second AND, and then finishes with the OR. As a result, this query retrieves all ONAF two-winding transformers and all DT two-winding transformers with a nominal kVA between 50 and 100. To correct the problem, the condition lines have to be grouped as follows:

SELECT 2-Winding Transformer WHERE ( ( Key = ONAF OR Key = DT ) AND ( NomSize >= 50 AND NomSize <= 100 ) )

The query now resolves the Boolean operators within the parentheses first, which determines the transformer type and the nominal size. Only then does it resolve the AND Boolean operator between the parentheses, giving us the results we want.

By default, the only group in the query definition encloses the entire component set.

Adding parentheses establishes the proper Boolean operator precedence.


8/16/2006



7 Reports

Reports are ASCII text files that can contain a variety of information such as Study results, input data, schedule documentation, or your own notes about a project. You can use PTW’s Report Editor to view, edit and print existing Reports, or to create blank Reports for your own notes. Using advanced features of the Report Viewer, you can cut and paste text among Reports, change the font size, search and replace text, and much more. Use the Reports to store numerous Study scenarios, to create presentation or proposal prototypes, or just to keep your thoughts and comments on the computer in a form that you can retrieve easily.

Studies automatically generate Reports every time you run them, based on the Report file name you provide. For information on running Studies, refer to the Reference Manual for that Study.


• What is a Report?

• Creating and opening Reports.

• Editing Reports.

• Changing Report options such as color, word-wrap, and font size.

• Opening Reports in other applications.

IN

TH

IS

CH

AP

TE

R

7.1. What is a Report? ............................................................................................. 7-2 7.2. Creating and Opening Reports.......................................................................... 7-2 7.3. The Report Interface ......................................................................................... 7-3 7.4. Navigating the Report....................................................................................... 7-4 7.5. Working with Text............................................................................................ 7-5 7.6. Setting Report Options ..................................................................................... 7-7 7.7. Opening Reports in Other Applications............................................................ 7-8 7.8. Crystal Reports ................................................................................................. 7-9


8/16/2006

7.1. What is a Report? A Report is a text file that holds Study data, notes about a project, or any text you want. Most often, you will use Reports to review Study data; Studies automatically create Reports when they are run. You can save different Study scenarios to different Reports, and then open one or more of them at the same time to compare results.

In addition to Study results, Reports can hold any of your own text, including notes or comments about a given project. To do this, create a new Report and type in the text you want. You can also paste selected Study results and include them with your notes. Using this method, you can generate the prototype of a formal Report or presentation.

The Report Editor integrates Report management into PTW, so you never have to leave the application to look at Study results. The Report Editor is similar to many word processors or text editors available in Windows. You can use the Report Editor to create, view, edit or print Reports. You can also use specialized functions in the Report Editor to search for text, replace text, copy and paste text, change font size and much more.

For full-featured word processing, you can open Report files in word processing program such as Microsoft Word. Reports are saved in the highly generic ASCII file format, which any application can interpret. Use one of these word processors to add advanced formatting, add headers, vary fonts, and so on. In this way, you can take Study results directly from PTW and incorporate them into a final Report without ever having to retype them. For information on opening Report files in another applications, refer to Section 7.7, “Opening Reports in Other Applications.”

7.2. Creating and Opening Reports Reports are independent ASCII files that represent a snapshot of the project database at a given moment in time, but are not otherwise linked to a project. Therefore, you can open or create a Report at any time, even when a project is not open.

7.2.1. Creating Reports There are two ways to create reports: running Studies, and creating a report file manually. Most often, you will want to use reports to show your Study results. To do this, simply

Reports UG 7-3


run the Studies you want. When you run Studies, PTW automatically saves the results in report files that you can open and review.

You can also create a new Report manually when you want to start a blank Report for holding your notes pertaining to a project, portions of Study results, or any other miscellaneous text. You can create a new Report at any time, and you can create as many Reports as you need: PTW imposes no upper limit on the number of Reports you can create. Each time you open a new Report, PTW assigns a default Report name. The first time you save the Report, you will have the opportunity to rename it.

To create a new Report

1. Either click the Document>Report command or click the Report toolbar button .

2. Click the New button

7.2.2. Opening an Existing Report Existing Reports might contain Study data, or your own notes and comments about a particular project. You can open an existing Report at any time.

To open an existing Report

1. Either click the Document>Report command or click the Report toolbar button .

2. In the Report Name box type or select the name of the Report you want to open.

3. Click the Open Button.

7.3. The Report Interface The Report interface works like a word processing program: its main interface feature is a central working area called the viewport, which displays your Report. The following picture shows you the parts of the Report interface.


8/16/2006

The viewport acts as a window on the Report text. At any given time, some or all of the Report may be visible through the viewport. You can use the Report interface to view or edit Reports as needed. For information on navigating the Report to find the information you need, refer to Section 7.4, “Navigating the Report.”

7.4. Navigating the Report A Report may be several pages in length, and the pages of a Report scroll vertically, as though on one continuous sheet of paper. Using the vertical scroll bar, you can scroll through the length of the Report. You can also use the Go to Line command to move to a specific line in the Report, which can be very useful when you are comparing two different Reports. The following sections discuss the navigation options for Reports.

7.4.1. Scrolling a Report You can use the scroll bars found along the bottom and right edges of the Report to move or “scroll” the Report in the viewport. The position of the scroll box in the scroll bar represents the position of the viewport relative to the boundaries Report: to move the viewport to the right, move the bottom scroll box to the right, and so on. The pages of a Report scroll vertically, so you will usually use the vertical scrollbar.

Scrolling a Report does not affect the level of magnification.

7.4.2. Moving to a Specific Line Use the Edit>Go to Line command to move to a specific numbered line in the Report. The Line box in the status bar at the bottom of the screen always displays line number of

Click the arrows to move up or down.

The text of the Report is shown in the Viewport.

Drag the scroll box to move to an approximate location in the Report.

Reports UG 7-5


the present cursor location, where 1 represents the top line of the Report. The example below shows that the cursor is located at line 193.

To move to a specific line, type the line number in the Go To Line dialog box.

This method of navigating is very convenient if you are comparing values in two long Reports. For example, if you have two Load Flow Study Reports on two different scenarios of the same project, and want to compare voltage drop across a particular branch, position the cursor on the same line as the voltage drop data, and look up the line number in the status bar at the bottom of the screen. Then, open the second Report and use the Go To Line command to move to the same line number.

7.5. Working with Text The Report Editor offers you several advanced word processing features to help you find and edit text including a powerful search function, a replace function, and cutting and pasting capabilities. Refer to the following sections for information and instructions on these capabilities.

7.5.1. Copying, Pasting, and Deleting Text When you want to copy text from one part of the Report into the other, the easiest way to do that is to copy the text into the clipboard, and then paste it into the new location. To do

this, use the Cut , Copy , and Paste buttons. To delete text, highlight it and click the DELETE key.

7.5.2. Finding and Replacing Text When you want to find a specific sequence, or string, of characters, the Report Editor offers you two different commands. You can use the find command to locate the string, or the find and replace command to locate the string and replace it with another string.

The find and replace functions move from the cursor location towards either the beginning or the end of the file, and then stops. For that reason, before using these commands, it’s a good idea to position the cursor at one end of the file. To do this quickly, press CTRL+HOME to move to the beginning of the file, or CTRL+END to move to the end of the file.

Type a line number, and then click the OK button to go to that line.


8/16/2006

Finding Text Use the Edit>Find command to search for any sequence of characters you want. The search string can contain any alphanumeric characters, special characters such as ampersands, and embedded spaces. The Find command finds the first instance of the text string you want to find.

By default, find is case-sensitive, meaning that it finds the text exactly typed. So if you search for the string “text,” you will not find “Text.” This option can be changed before running find.

Replacing Text Replace works similarly to find, but with it you can search for one sequence of characters and replace it with another. For example, you can search for the string “bus” and replace it with “Bus.” Use the Edit>Replace command to do this. You can replace any text string with any other text string.

Reports UG 7-7


7.6. Setting Report Options The Report Editor incorporates a number of options that operate at a global level, which means that they apply to all of Reports in all projects. You set options in the Reports subview of the Options Dialog box. The option categories include editing options, font options and colors, each of which is described in the following sections.

The text editing options that you can set in PTW are very generalized. For more flexibility in viewing, editing and printing Reports, consider opening your Report in a word processing application. For further information, see Section 7.7, “Opening Reports in Other Applications.”

Font Size. Type the size of the Report font in points (1 point = 1/72 inch).

Tab Stops. Type the number of spaces (columns) between tab stops. The column count for tab stops always begins at 1, so if the you type a 3 in the Tab Stop box, the first tab stop will be located at column 4 (1 +3), the second at column 7 (4 +3) and so on.

Display using the OEM Character Set. Displays the OEM character set as the screen font for Reports. The OEM character set is a system font that resides on your computer, and that varies from system to system. If you want to view this font in the Report Editor, select the OEM Character Set check box. The advantage of viewing the OEM character set is that it is configured specifically for your machine. If you want to view the font that comes with PTW rather than the OEM font, clear this check box. You should experiment to see which font looks better on your screen. This setting does not affect the print font, which cannot be changed from within PTW. If you want to change the print font, you can open the report in another text editor.

Wordwrap. Wordwrap tells the Report to begin a new line when the text reaches the column number you assign to the right margin. Wordwrap is on by default; to turn wordwrap off, clear the Wordwrap check box.

Enable. Turns wordwrap on.


8/16/2006

Right Margin. Type a column number at which you want text to wrap to the next line. This option is available only if the Enable check box is selected.

Indent. Sets the left margin for printed Reports by indenting the specified number of spaces. The indention does not appear in the Report viewport, but will appear in print preview. Font size dictates how large these spaces are, but a 14-space indention sets a standard one-inch margin (assuming a 10-pt. font size).

Screen Colors. Use these options to set the Report foreground (text) and background colors. The default colors for Reports is black text on a white background, but you can change both of these colors to any that you prefer. You change colors using the Color dialog box.

Foreground. Set the color of the Report text. Choosing this brings up the Color dialog box. The current foreground color is displayed in the square to the right of this button.

Background. Set the color of the Report background. Choosing this brings up the Color dialog box. The current background color is displayed in the square to the right of this button.

7.7. Opening Reports in Other Applications Reports can be opened in a variety of word processing applications. In fact, the file format used in Reports is the ASCII text format which is extremely generic and almost universally accepted among text editing packages.

When you open a Report in another application it may not look as it does in the Report Editor because the new application may have substituted a proportional font for PTW’s native font, PIXymbolsExtended. Proportional fonts allocate different widths for different characters: for example an “I” is much narrower than an “M.” The effect of proportional fonts in Reports is to shift columns so that they no longer line up properly. Non-proportional fonts, on the other hand, allocate the same width for every character ( “I” is the same width as “M”) keeping all columns neatly aligned . For this reason, you should always use non-proportional fonts for the entire Report. PTW automatically installs the PIXymbolsExtended font onto your machine when you load it, and you can find it by scrolling through the fonts box of your application. We recommend that you use this font for your Reports.

========================================================================== ITEM DESCRIPTION * CONNECTED LOAD * DEMAND LOAD * DESIGN LOAD * % KVA AMPS KVA AMPS KVA AMPS P F ========================================================================== END USE LOADS LARGEST KVA MTR 7100.0 297.0 7100.0 297.0 8875.0 371.3 100.00 BRANCH LOADS 004-TX B P 853.5 35.7 853.5 35.7 1020.4 42.7 83.42 005-TXD PR .0 .0 .0 .0 WARNING: LOAD IS ZERO 006-TX3 PR 7963.3 333.2 7963.3 333.2 9003.7 376.7 82.41 007-TX E P 2860.1 119.7 2860.1 119.7 2942.7 123.1 80.71 ==========================================================================

Proportional fonts like Arial shift the Report text so that columns no longer align.

Non-proportional fonts like PIXymbolsExtended keep the columns neatly aligned.

If for some reason you don’t want to use the PIXymbolsExtended font, you can also use another non-proportional font such as Courier, provided that the Report does not use extended characters.

Reports UG 7-9


7.8. Crystal Reports PTW also includes a set of Crystal Reports that you can use to view project data. Crystal Reports is a reporting tool that allows for greater formatting and the ability to run queries to retrieve particular data. The Crystal Reports are not meant to replace the existing PTW reports, but rather to enhance them by providing an alternate way to view data.

7.8.1. Differences between PTW Reports and Crystal Reports There is a fundamental difference between PTW Reports and Crystal Reports:

• PTW Reports are text files.

• Crystal Reports are templates.

When you view a PTW Report, you’re viewing the actual text in the file. You can copy the text, delete the text, and so on. By contrast, when you view a Crystal Report, you’re viewing a representation of the data in the Project Database at that moment. Whenever you open a Crystal Report, it reaches into Project Database, gets the data, and shows the data.

Tip: Crystal Reports are more similar to Datablocks than to PTW Reports―both Crystal Reports and Datablocks use a template to determine what data to show. Once you export data from Crystal Reports (using the Export button) and Datablocks (using the Run>Datablock Report command), that exported data is what resembles the PTW Reports.


8/16/2006

7.8.2. Opening a Crystal Report As with the PTW Reports, you can open a Crystal Report without having a Project open. However, unlike the PTW Reports, you do have to specify which Project you want to open the Crystal Report for. Remember, Crystal Reports are merely templates, so they need to be based on a specific Project.

To open a Crystal Report

1. Click the Document>Crystal Report command. This opens the Crystal Report Manager:

2. Click the symbol next to PTW Report Generator:

3. If you already have a project open, then you’ll see the Project name and Library name appear in the parentheses, as shown in Figure 1; this means you can skip to step 5. However, if you don’t have a Project open, you’ll see the captions “No Project Selected” and “No Library Selected,” as shown in Figure 2; this means you have to proceed to step 4.

Figure 1 Figure 2

4. Since you need to select a Project and a Library for the Crystal Report to report on, click the right-mouse button and use the “Select Library” and “Select Project” commands to choose the Project and Library that you want to report on, as shown in Figure 3 and Figure 4.

Figure 3 Figure 4

5. Now that you have the Project and the Library that you want to report on, you can open a Crystal Report. To see the list of Crystal Reports, click the symbol next to PTW Project Report (you can also open a PTW Library Report by clicking the symbol next to PTW Library Report), then select a category:

Reports UG 7-11


Click a category... ...and you see the Crystal Reports.

6. To open a Crystal Report, double-click on it and it will open in the Crystal Viewer:

The Crystal Report Viewer


8/16/2006

7.8.3. Parts of a Crystal Report The Crystal Report Viewer displays the Crystal Report that you have opened:

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Number Function 1 Closes the Crystal Report.

2 Moves to the first page.

3 Moves one page back.

4 Indicates the page number.

5 Moves one page forward.

6 Moves to the last page.

7 Stops processing records.

8 Prints the Crystal Report.

9 Sets up the printer.

10 Refreshes the data from the database.

11 Exports the Crystal Report to a text file, Excel spreadsheet, or other file.

12 Shows or hides the tree view that appears in the left half of the window.

13 Sets the level of zoom.

14 Searches the Crystal Report to find the text you typed.

7.8.4. Exporting a Crystal Report As we mentioned in Section 7.8.1, "Differences between PTW Reports and Crystal Reports," unlike the PTW Reports the Crystal Reports are not an actual text file that you can manipulate. However, you can export the data in a Crystal Report to a text file, spreadsheet, or other file type. To do so, just click the Export button and select the file type you want to export to.

This half of the window shows each component in the report; not all reports will display data

here.

This half of the window shows the report itself.

Reports UG 7-13


To export a Crystal Report

1. Click the Export button:

2. In the Export dialog box, select the format and the destination:

3. The data in the Crystal Report will now be exported to the format you select.

7.8.5. Running a Crystal Query Sometimes you might want to filter a Crystal Report for records that meet certain criteria. With our special Crystal Query feature, you can filter a report with just a few mouse clicks.

Note: Not all the Crystal Report included with PTW have Crystal Query functionality built in; if you try to query a report that doesn’t allow querying, you’ll receive a message saying so. Also, for those reports that allow querying, some fields are not queryable (for example, you cannot filter for device name―our Crystal Query feature only works on numeric fields). If you're an advanced user who knows how to write SQL and work with relational databases, you can write your own queries to search for any criteria you want. You will need to read Section 7.8.7, "Creating your own Crystal Reports," to learn some crucial aspects of writing your own queries.


8/16/2006

To create a new Crystal Query

1. Click the right-mouse button and choose "Query":

This opens the Crystal Query dialog box.

2. Click the New button. This opens the Crystal Query Editor:

7.8.6. Using the Crystal Query Editor The Crystal Query Editor works much like the standard PTW Query Editor. You choose the field you want to query (such as "Bus Voltage"), the operator (such as "="), and the criteria (such as "480"). Together these make up a query criteria, such as "Bus Voltage=480":

Click here to remove the applied query and show all data.

Click here to apply the selected query.

Click here to create a new query.

Reports UG 7-15


Select a field, operator, and criteria, then click Insert...

...and the query condition line appears in the Query Conditions list.

And/Or Logic If you want to query more than one field, you must keep in mind the following restriction:

You may create any combination of "AND/OR" Boolean operators on the same field, but you may only use the "AND" Boolean operator between fields.

This is necessary because of the way the Crystal Query works. Refer to Figure 5 for an example:

Figure 5

Here is how the precedence works in Figure 5:

( (Bus Voltage = 480.00) OR (Bus Voltage < 5000.00 AND Bus Voltage > 4000.00) ) AND (V THD <> 0.00) AND (V RMS <> 0.00) Within the field Bus Voltage, you may create both ANDs and ORs. Note that the ANDs take precedence, which means they group together within parentheses. Between the fields Bus Voltage, V THD, and V RMS, you may only use ANDs.

You may use any combination of ORs and ANDs within the same field.

You may only use ANDs between fields.

When you create multiple conditionlines for a field (in this case, the Bus Voltage field), the condition

lines always group together.


8/16/2006

Choosing Subreports Depending on the report you've opened, you may have to choose the Sub-Report to query on. This isn't as tricky as it sounds; basically, each Sub-Report is really just a Crystal Report, except that we've put them together so you they all reside in a single Crystal Report.

For example, the HI_WAVE report (shown in Figure 6) has seven sections, or subreports: Buses, Branches, Filters, Motors, Non-Motor Loads, Sources, and Harmonic Sources.

HI_WAVE Report

Buses Bus Name Bus Voltage V THD V RMS V TIF 001-UTILITY CO 69,000 0.69 68,737.97 13.94

Branches Component Name

Type From Bus To Bus

Bus Volt.

I_THD I_RMS I_T I_K LF Amps

LF Angle

C1 Cable 003-HV SWGR 004-TX B PRI

13,800 32.97 13.76 3,065.39 4.14 13.06 -24.58

Filters Filter Name Bus Name Bus Voltage I_THD I_RMS I_T I_K LF

Amps LFAngle�

Cap-Bus13 013-DS SWG2 4,160 139.58 807.29 261,401.50 19.20 470.17 81.24

Motors Motor Name Type Bus Name Bus Volt. I_THD I_RMS I_T I_K LF�A

mps LF Angle

M 28 # 1&2 Ind Mtr 028-MTR 28 A 480 40.61 672.60 180,069 5.55 623.18 -45.04

Non-Motor Loads Load Name Bus Name Bus Voltage I_THD� I_RMS

� I_T� I_K� LF

Amps LF Angle

L1 013-DS SWG2 4,160 0.00 0.00 0.00 0.00 27.24 -8.80

Sources Source Name�

Type Bus Name Bus Voltage I_THD�

I_RMS�

I_T� I_K� LF Amps�

LF Angle�

G1 Gen. 008-DS SWG1 4,160 12.38 89.89 7,798.23 1.49 89.21 38.66

Harmonic Sources Source Name�Bus Connected To

Lib. Source Name Component Type

Bus Voltage Rated kVA

I_THD I_RMS I_T I_K LF Amps

LF Angle

M 28 # 1&2 SKM Six Pulse 480 40.61 672.60 180,069. 5.55 623.18 -45.04 028-MTR 28 A Ind Mtr 250.00 M25 SKM Six Pulse 4,160 40.61 299.56 80,199.6 5.55 277.55 -44.95 025-MTR 25 Ind Mtr 1,956.46

Figure 6

When you create a query for this report, you simply choose the subreport that you want to query on. As shown in Figure 7, the list of subreports corresponds to the sections of the report shown in Figure 6

Reports UG 7-17


Figure 7

Not every report has subreports. Those reports that don't contain subreports will simply list "Main Report," as shown following:

This report contains subreports. This report doesn't contain subreports.

7.8.7. Creating your own Crystal Reports

Important: To make your own reports, you must purchase Seagate Crystal Reports. PTW only includes the Report Viewer, not the Report Designer.

Before taking on this venture, you must be aware of the complications involved in making your own reports. You must, of course, purchase the full version of Crystal Reports, since you need the Crystal Report Designer to create reports (PTW only includes the Report Viewer, not the Report Designer). In addition, you must understand SQL (a querying language) and relational database technology. We will provide instructions on making the Reports, and enough information about the Project Database structure to know what you’re looking for, but you must know SQL and database usage quite well to do so. We don’t say this to discourage you from creating your own reports (quite the contrary!), just to let you know what is needed for making your own Crystal Reports for PTW.

Tip: If you’re new to SQL, but want to learn, this provides an excellent learning opportunity, because you can learn a lot about SQL and relational databases by experimenting with Crystal Reports that extract data from a PTW Project Database. Read all the following pages, then try making one or two Reports. It will be difficult at first, but if you keep practicing with Crystal Reports and read an introductory tutorial to SQL in a book or on the Internet, you’ll become proficient surprisingly quickly.


8/16/2006

Connecting a Crystal Report to PTW through ODBC The following steps describe how to use Crystal Reports to open a PTW project:

1. Start PTW.

2. Open the Project which you want to open in Crystal Reports (you have to open the Project in PTW first so the Data Source Name, or DSN, will point to this Project―this will make sense in a moment).

3. Close PTW.

4. Start the 32-bit Crystal Report Designer.

5. Click File>New. This opens the Report Gallery:

6. Click the Standard button. This opens the Standard Report Expert:

7. Click SQL/ODBC. This opens the Log On Server box:

Reports UG 7-19


8. Select "ODBC - PTW_PRJ" and click OK. (This is the Data Source Name, or DSN, which you set back in step 2 to point to the PTW Project you want to open; whenever you work in PTW, this DSN is automatically updated to point to the project you currently have open.)

9. You will now see a list of all the tables in the PTW Project. Since there are literally hundreds of them, you should not choose all of them, but just those tables that contain the data you want to show (for example, to see Load Flow Voltage, you would choose the BusOutput table). For a list of all the tables in the PTW Project and their relations to one another, see the following section, "PTW’s Database Structure."

PTW’s Database Structure As you can see from the previous section, it's not enough to just connect Crystal Reports to a PTW Project; you need to know where to find the field you want, too. Since it's difficult to manually search for the field you want (there are hundreds of tables, each with an average of 10 fields, resulting in thousands of fields), you need to know something about PTW's database structure and some experimentation will be required. If you can not locate the desired data field, contact SKM for additional database information.


8 Libraries

Libraries are data containers that you can use to dramatically speed up system modeling. Libraries contain frequently used component attributes that you can copy into your project components as needed. This greatly reduces your data entry, because instead of having to type in component attributes over and over, you can simply select the library model you want, and PTW copies the component attributes into the Component Editor. Not only does this make your work easier and faster, but it also minimizes data entry errors.

Libraries are fully customizable: you can enter manufacturer’s data into new libraries to model your equipment according to exact specifications. This chapter introduces libraries and library concepts, and details the procedure of working with the library data in your projects.


• What is a library?

• Managing libraries.

• The library interface.

• Reviewing and editing library data.

IN

TH

IS

CH

AP

TE

R

8.1. What is a Library? ............................................................................................ 8-2 8.2. Managing Libraries........................................................................................... 8-4 8.3. Changing Project Library References............................................................... 8-6 8.4. Adding and Editing Library Entries.................................................................. 8-8 8.5. Copying Library Entries ................................................................................... 8-8 8.6. Cable Library .................................................................................................... 8-9 8.7. Demand Load Library..................................................................................... 8-13 8.8. Motor Control Center Library......................................................................... 8-14 8.9. Transformer Library ....................................................................................... 8-16 8.10. CAPTOR Library.......................................................................................... 8-17 8.11. TMS Library ................................................................................................. 8-17 8.12. I*SIM Library............................................................................................... 8-18 8.13. HI_WAVE Library ....................................................................................... 8-18 8.14. Standard Transmission Line Library ............................................................ 8-19 8.15. 3-Phase Transmission Line Library.............................................................. 8-21 8.16. Bus Library ................................................................................................... 8-21 8.17. Reliability Library........................................................................................ 8-22


8/16/2006

8.1. What is a Library? As the name suggests, a library is a file that hold detailed component data that you can copy into your project over and over again very quickly.1 The benefit of using library data is that it can substantially speed up your network modeling task: you can model a specific component once, and then copy that model several times in your project without having to repeat the data entry process. For example, say that your project uses 100 cables that are exactly the same. Instead of having to create each of those cables individually, you can create a single model in the Cable Library, and then select the library reference for any cable as needed. You can use the libraries in combination with component cloning to build projects very quickly. For information on cloning, see the “Component Editor” and “One-Line Diagrams” chapters.

You can also use libraries to make global changes to the project. For example, if you need to change the positive sequence impedance for all of the cables of a given size, you can change the library component once, and all of the cables referencing that library component are updated interactively.

There is one main library in PTW and the default name is PTW.LIB. The library database has 11 main categories and several sub-categories as shown:

1 The data used in the default libraries is derived from the IEEE Std 141-1993 (Red Book). New York: Institute of Electrical and Electronics Engineers, Inc., 1993, and from the Electrical Transmission and Distribution Book. Fourth Edition. East Pittsburgh, PA: Westinghouse Electric Corporation, 1964 (1950).

Libraries UG 8-3


Library category Function CAPTOR TMS ISIM HIWAVE Transmission Line Transformer Standard Cable Single Core – Pipe Type Cable Motor Control Center Bus Reliability

Contains protective device information including trip curves for coordination and device ratings for system evaluation. Contains motor and load models used for dynamic motor starting simulations. Contains machine and control models used in transient stability simulations. Contains harmonic spectrum models used in harmonic analysis calculations. Contains transmission line samples and a calculator for generating custom transmission line data for use in all studies. Contains standard transformer information used for studies and documentation. Contains standard cable information used for studies and documentation. Contains cable information generated by the built-in cable parameter calculator. Contains information on motor circuit protective devices, cable and conduit sizes and unique motor starter data. Contains bus rating information for System Evaluation. Contains individual component reliability and cost information used for system reliability calculations.

There is a separate Demand Load library file that contains demand and design load factors used in the Demand Load Study. Loads entered in the project can reference load categories in the Demand Load library to account for diversity and continuous operating conditions for sizing cables and transformers.


8/16/2006

8.2. Managing Libraries Libraries are not specific to projects, so you can create and open them regardless of whether a project is open or not.

8.2.1. Creating a New Library To open a Library, click the Document>Library command or the Library icon .

Select the library type PTW Library or Demand Load Library and click OK to continue.

Enter a File name and Click the New button to create the new Library.

8.2.2. Opening an Existing Library To open a Library, click the Document>Library command or the Library icon .

Select the Library type and click the OK button to continue.

Libraries UG 8-5


Select the library file and click the Open button to open the library.

8.2.3. Copying and Renaming Libraries It is a good idea to copy or rename the original libraries after they are installed. By renaming the library files, you can expand and modify the libraries without fear of over-writing your changes when new versions of the PTW program are installed. For example, you could rename PTW.LIB to MYLIB.LIB. After changing the name, the projects will need to be directed to use the MYLIB.LIB library file as described in the following section.

8.2.4. Compressing PTW Library Files After copying and deleting library entries, the PTW library file may contain empty data markers that continue to use space. The library file can be compressed using the Project>Compress Library function. You must close all PTW project files before the Project>Compress Library menu choice is accessible.

8.2.5. Library Backup In many cases it is useful to keep a small library with each project. The Project>Backup function automatically creates a backup library that contains only the library entries used in the active project. The backup library file is automatically stored with the project files created with the backup function.

8.2.6. Copying Between Multiple Libraries You can copy and paste library entries between two different libraries. The general process is to open both libraries in PTW (Document>Library>Open). With both libraries open, select the library entries you wish to copy and use the Device>Copy function. Keeping both libraries open, switch to the destination library, select any entry in the matching category of the target library and use the Device>Paste function.


8/16/2006

8.3. Changing Project Library References When you create a project, PTW establishes a library reference between the project and the default library file located in the library directory (C:\PTW\LIB if you followed the default setup options). PTW uses the referenced libraries for the active project. As you work with PTW, you may want to use a different library that you have tailored to fit your needs. You can do this by first creating the library file (or by copying and editing the library files included with PTW), and then changing the library reference to point to the new library. If you edit the library that is already referenced in the active project, you do not need to change the file reference; PTW automatically detects the change and asks you if you want to copy the changes into the project when you save the library.

You should set current project library reference at the beginning of each new project so that PTW has access to all of the correct data from the start. If you have to change a library reference midway through the project, refer to Section 8.3.1, “Changing Current Library References During a Project” for special information and instructions.

Library current project library references pertain to the active project only; changing the library reference in one project does not affect the references in another project.

Each project must reference a library file. If PTW cannot find the referenced library file, it issues an error message to that effect on startup.

To change current project library references


2. In the Option Groups box, select Library.

3. In the Option Subviews, select Current Project Libraries.

4. In the Library box, do one of the following:

• Type the full path and filename of the new library.

• Use the Browse button to browse the file and directory structure for the new library file.

The current library references are displayed in the library box. To change the library references, either type the name of a different library, or use the Browse button to locate a different library file.

Libraries UG 8-7


5. Click the OK button. If you are changing the files reference of the library that is currently being used in the project, PTW will ask you to confirm the change.

You can also set the default library reference for new projects. Setting this reference tells PTW which library to use for projects you create in the future. Note that changing new project library references does not affect the library reference for the current project.

To change the “new project library reference”


2. In the Option Groups box, select Library.

3. In the Option Subviews, select New Project Libraries.

4. In the library box, do one of the following:

• Type the full path and filename of the new library.

• Use the Browse button to browse the file and directory structure for the new library file.

Click the OK button. If you are changing the file reference of a library that is currently being used in the project, PTW will ask you to confirm the change.

8.3.1. Changing Current Library References During a Project While it’s best to set the current library reference before you begin work on a project, you may find that you need to change the library reference in the middle of a project. You can do this using the procedure described above, and after making the change, PTW asks you if you want to update all of the components in the project that reference that library type. Choosing the Yes button copies all of the new library data into the components that reference the library, overwriting the attribute data from the old library. Choosing the No button leaves all project values unchanged. If you choose the No button, PTW maintains the link between the component and the referenced library entry so that you can update the project component at a later time if you choose.

Important: If you change a library reference in the middle of a project, we highly recommend updating the reference for all components.

If a project component references a library entry that does not exist in the new library, PTW breaks the link between that component and the library, leaving all of the attribute data intact. For example, say that one of your transformers references an OAFA entry in the library, and then you change the library reference to a file that does not contain an OAFA entry. PTW breaks the link between that component and the library, but leaves all other attributes as they were before the library reference change. The Transformer key box keeps the OAFA selection, but because it cannot find a proper control attribute, PTW posts the warning message, “Transformer Key Not Found in Current Library.”

After changing a library reference in the middle of a project, you should check all of the project components to update or confirm library references.


8/16/2006

8.4. Adding and Editing Library Entries To edit a library entry, open the library as described in Section 8.2.2 Opening an Existing Library. Select the entry to wish to edit by expanding the library category and double-clicking on the specific device entry. To add a new library entry, select any device in the desired library category, and pick the Device>New menu function. Some specific information regarding some of the library categories follows:

8.5. Copying Library Entries Library entries can utilize the standard Cut/Copy/Paste features of windows. Select the individual library entry on the right side of the window and click the Right Mouse Button to display the Cut/Copy/Paste menu options. Alternatively you can use the Component>Copy / Component>Paste menu functions. To copy entries between two different libraries, both libraries must be open in PTW. The right half of the library window must be the active window for the Cut/Copy/Paste functions to be active.

Libraries UG 8-9


8.6. Cable Library The cable library has two categories, standard cable data and pipe type cable models. The standard cable is from manufacturers published data and from related standards. The pipe type cable uses a built-in cable parameter calculation program.

8.6.1. Editing the Cable Library Cable types are defined by Manufacture, Description, Conductor Material, Duct Material, Insulation Type, Insulation Class, Voltage Rating, Installation and Description. The Description field can be used to identify a specific cable manufacturer, data source, etc. Additional fields for Frequency, Application and Temperature ratings are provided. The base frequency is used to convert library data to the system frequency. Circular Mils equivalents are accessed through the buttons at the bottom of the General Cable tab.

Conductor sizes and impedances are entered on the Impedance Data tab for each cable type. The number of parallel conductors allowed can be specified so that the sizing program does not parallel small conductors and you can control internal design standards. Raceway sizes and Installation ampacities can also be entered. The first column of the Ampacity tab is reserved for defining the rated ampacity.


8/16/2006

Raceway sizes can be referenced for each cable size. The raceway specifications are for reporting purposes only and do not affect any calculations directly.

Ground wire sizes can be specified for each parallel combination of cable sizes. To increase the number of parallel conductors allowed for a given size, click on the Heading button and enter the maximum number of parallel conductors. For this example, parallel conductors are not allowed for sizes below 1/0, and the maximum number of parallel circuits allowed for sizes 1/0 and above is 12.

Libraries UG 8-11


Ampacity entries can be defined for any installation. Installation descriptions are added, changed or removed by clicking on the Headings button on the Ampacity tab. Any user-defined installation description can be specified for the ampacity entries. When a cable is selected from the library, the optional installation description can be selected to reference the base ampacity for the configuration. Additional ampacity de-rating can be specified by selecting different ambient temperatures.


8/16/2006

8.6.2. Viewing the Circular Mils for the Cable Library This supplemental table lists each cable’s size in equivalent circular mils, which are a unit

of measurement. A circular mil is a unit of area equal to π4

of a square mil (0.7854

square mil). The cross-sectional area of a circle in circular mils is therefore equal to the square of its diameter in mils. A circular inch is equal to one million circular mils. (A mil is one-thousandth part of an inch. There are 1974 circular mils in a square millimeter). The default table includes standard sizes for both AWG and mm2 .

To open this spreadsheet, click on the Circular Mils button at the bottom of the General cable library tab.

8.6.3. Viewing the Derating Factors for the Cable Library This supplemental spreadsheet lists derating factors for the different temperature ratings for each installation specified in the Library. These derating factors appear in the Derating Factor box in the Conductors and Raceway subview for cable components.

To open this spreadsheet, click the Temperature Correction tab in the cable library. New temperature columns can be added by clicking on the Temperature button. Ampacity

Libraries UG 8-13


de-rating factors can be assigned for each installation at any temperature. The temperature de-rating factors are combined with the Installation descriptions and ampacities.

8.7. Demand Load Library While in the Component Editor, you may want to specify a demand load category rather than an individual load factor for each load. The demand load library assigns diversity factors to loads based on the type and quantity of the load. The demand load library data is used by the Demand Load analysis when reporting Connected Load, Demand Load and Design load values. Many of the other PTW studies can use the calculated demand loads.

8.7.1. Using the Demand Load Library The Demand Load Library includes a Load Model Description, Load Type, 3-Levels of Demand Factors, and a Long Continuous Load (LCL) Factor. Up to 20 load categories can be specified.


8/16/2006

To edit one of the 20 load models, click on the field you wish to change and type the new name or value. The Load Type can be defined as Constant Impedance, Constant kVA, or Constant Current. The 3 demand levels are used by the demand load analysis and assign global diversity based on cumulative quantity. For example, it is common to count the first 10 kVA of receptacle load at 100% and additional receptacle load at only 50%.

To change the entry so that all receptacle load is counted at 100%, you would check the All kVA box above the 1st Level entry data. To change the entry so that all receptacle load is counted at 80%, check the All kVA box and change the 1st Level % Demand value to 80. If the All kVA box is checked, the 3 Phase kVA limit is ignored.

8.8. Motor Control Center Library When a motor (either synchronous or induction) is referenced in an MCC or Switchboard Load Schedule, you can access preset starter information by linking the motor to this Library. To do this, you must first reference the motor in an MCC or Switchboard Load Schedule. Once the motor is referenced in the MCC or Switchboard Load Schedule, choose the Modify button in the MCC or Switchboard subview. This opens the Motor Schedule Data dialog box, where you will find the Motor Library Key that can be linked to this Library.

For each motor hp size and voltage/starter type, you can reference key wiring specification data based on national codes and standards. When motors are specified by this data, the motor demand and design loads are based on the Library full load amperes, not on the calculated amperes based on motor rated size. None of the library data except the FLA values are used by the studies. The information is for documentation purposes only. The library FLA values can be used by the Demand Load Analysis, in place of the FLA calculated from the motor rated size, power factor and efficiency specified.

8.8.1. Using the Motor Control Center Library To add a new entry in the MCC library, click your right mouse button on the library window, or use the Device>New menu item. MCC library data is specified with a Description, Motor Size, Voltage Range, FLA, Feeder/Raceway Description, Overcurrent Protection, and Starter information.

Libraries UG 8-15


8.8.2. Viewing the Accessory Groups for the Motor Control Center Library This supplemental spreadsheet lists the descriptions for various motor starter accessory groups. You assign a specific starter accessory group to a motor by typing the group’s name (usually a single letter, such as “B”) in the Starter Accessory column in the Motor Control Center Library. Select or clear the appropriate check boxes within an accessory group that correspond to its contents.

For example, suppose you want to create a new accessory group, called “D,” that has an automatic switch and a panic button in it: first, open the demand load library, then select the View>Accessory Groups menu followed by the Edit>Descriptions command. Assign the name D to an empty column; select the check boxes in column D that lie in the Panic Button and Auto Switch rows; and Click the OK button. If you need to add a new option row to the accessory group table, use the Edit>New Row menu item. To assign the new Accessory Group "D" to a Library motor, make the Motor Control Center Library the active window and type the letter “D” in the specific motor’s row in the Starter Accessory column.


8/16/2006

8.9. Transformer Library While in the Component Editor, you may want to select a two-winding transformer from the library rather than enter the impedance and Full Load kVA data manually. To do this, you link the two-winding transformer component to the Transformer Library by selecting the Transformer Library component from the Component Editor Key box.

8.9.1. Using the Transformer Library Transformer library entries consist of a Manufacturer description, Type, Capacity Factor, Frequency Base and Description entries. For consistency with the old libraries, typical data is entered with the Manufacturer Description set to NONE. The capacity factor represents the Full Load kVA capabilities compared to the Nominal kVA rating.

To add a new transformer entry in the library, click your right mouse button in the library window or select the Component>New menu item. To edit or delete a library entry, double click on the library entry you wish to edit. Only the Manufacturer description field is selectable.

Libraries UG 8-17


8.10. CAPTOR Library This Library contains data for the protective devices including trip curves for CAPTOR and rating information for Device Evaluation.

For more detailed information on using the Library with regard to the Device Evaluation or Protective Coordination Studies see the individual Study module.

8.11. TMS Library The Transient Motor Starting (TMS) library contains motor and load information used by the TMS study module. The motor data includes Speed versus Torque, Current and Power factor curves. The Load data includes Speed versus Torque curves, Wk2, and frequency. The base torque and speed are also defined in the library.


8/16/2006

8.12. I*SIM Library The I*SIM library includes generator, governor, exciter, motor, load and relay models used in the I*SIM transient stability analysis module. For more details, see the I*SIM reference manual.

8.13. HI_WAVE Library The HI_WAVE Library contains non-linear load data used for harmonic analysis. For more detailed descriptions, see the HI_WAVE Reference Manual.

Libraries UG 8-19


8.14. Standard Transmission Line Library The transmission line library model determines the transmission line positive-sequence resistance per mile, zero-sequence resistance per mile, reactance per mile, and charging per meter based on the earth's resistivity, circuit resistance, system frequency and phase and ground wire configuration. PTW allows any spacing configuration up to two conductors per phase and up to two ground wires.

The model consists of three phases (A1/A2, B1/B2, C1/C2), and two grounds (G1 and G2). A1 & A2 together refer to a single-phase bundle, as do B1 & B2 and C1 & C2; don't perceive A1 & A2 as separate phases (this would mean that the model represents a 6-phase transmission line).

Earth Resistivity. Enter earth resistivity in ohms per cubic meter.

X & Y. Enter x and y coordinates in feet on the same arbitrary coordinate system for all conductors and ground wires.

D. Diameter of each conductor and ground wire in inches.

GMR. Geometric configuration variable of a single conductor (don't mistake it for the geometric mean radius). The value varies with the number of strands and conductor shape, and is available from the Electrical Transmission and Distribution Reference Book or from the conductor manufacturer.

r/mi. Resistance per mile in ohms for each conductor and ground wire.

Think of this diagram as a cross-section of a real transmission line. The red dots represent the lines themselves (as seen from head on). There are three phases, as represented by bundles A1/A2, B1/B2, and C1/C2. Each line is not a phase, but rather each bundle (consisting of two lines) is a phase--just as the six lines seen in the transmission line to the left embody only three phases.


8/16/2006

8.14.1. Technical Data In his article "Transmission-Line Parameters by Digital Computer,"2 M. H. Hesse describes Carson's solution for the earth-return problem results in an infinite series of Bessel functions. PTW uses a first-order correction wherein only the first term in each series is employed. This first order correction is the one most commonly used, and is generally satisfactory for single tower configurations.

The positive and zero sequence charging is determined using Potential Coefficients. The matrix equations are formulated, then the equations for the sub-conductors and ground wires are reduced to the three phases quantities. The Potential Coefficients are then inverted to obtain capacitance, and transposed to obtain the sequence quantities. Since only the diagonal elements of the sequence matrix are retained for further modeling, the transmission lines are assumed to be transposed.

Ground

A

B

C

Ground

A B C 11 1

Simple tower R + jX modeling for transmission lines

Fig. 8-1. Transmission line modeling.

2 IEEE Transactions on Power Apparatus and Systems, no. 66, June 1963.

Libraries UG 8-21


8.15. 3-Phase Transmission Line Library The 3-phase Transmission Line Library is similar to the Standard Transmission Line library except that it accounts for multiple independent circuits, circuit bundles, transposition, and line sag. The standard transmission line model reports sequence values, whereas the 3-phase Transmission Line model reports phase and sequence values.

8.16. Bus Library The bus library stores bus rating information for use with the system evaluation module. The bus information includes a Bus Type Description, Maximum Application Voltage, Continuous Current Rating, Momentary Fault Rating, Test X/R, and a Description Note field.


8/16/2006

8.17. Reliability Library The Reliability Library stores cost-based functions for power outages. The library entries can be assigned to motors and loads in the system model and represent processes in a plant or customers of a Utility.

There is also a user-defined library for component reliability data.

Libraries UG 8-23


The reliability information includes failure rate, down time, and age adjustment factors.


8/16/2006



9 Printing

PTW provides powerful printing options. In addition to printing documents such as One-Line Diagrams and TMS Plots, you may combine them on a single page and print them using a Form.


• Printing documents

• Print using a Form

• Using Forms.

• Creating New Forms.

IN

TH

IS

CH

AP

TE

R

12.2 Printing a One-Line Diagram ........................................................................... 9-3 12.3 What is a Form? ............................................................................................... 9-6 12.4 Creating a New Form ....................................................................................... 9-8 12.5 Printing Using a Form .................................................................................... 9-18


8/16/2006

9.1. Before Printing In PTW, you can print to any Windows printer or plotter set up on your computer. In order to print a document, you must first select the printer you want to print to, and then send the document to the printer.

9.1.1. Selecting a Printer You can send the document to any printer that has been set up in the Windows Control Panel. If you want to print to the default printer, you do not have to change the printer setting; PTW automatically prints to the default device. If you want to print to another printer on your system, you must first select it in the printer Setup dialog box.

To select a printer

1. Click the Document>Print Setup command.

9.1.2. Printing After you have selected a printer, you can print the document.

To print a document

1. Click the Document>Print command.

Printing UG 9-3


9.2. Things to Consider when Printing a One-Line PTW automatically prints the active One-Line Diagram to the selected printer, and includes the selected printing options. If you want to print on a printer other than the default printer, you must first select the printer you want.

9.2.1. Previewing a One-Line Diagram Before printing a One-Line Diagram, it’s a good idea to preview it first. When you preview the One-Line Diagram, PTW shows it on the screen exactly as it will appear on paper. All of the printer settings are applied to the preview automatically.

The print preview mode is a view-only mode; you cannot edit the One-Line Diagram from within this mode. To make any corrections or edits to the One-Line Diagram, you must return to the editing mode.

To preview a One-Line Diagram

1. From the Document>Print Preview command or click the Print Preview toolbar

button .

The preview mode is a display-only mode, and it is controlled exclusively by the buttons on the print preview toolbar. Refer to the following table:

Press this button To do this Print Print the One-Line Diagram. See Section 9.2,

“Things to Consider when Printing a One-Line .” for further information.

Next Page Preview the next page of the One-Line Diagram. This command is for multi-page One-Line Diagrams only.

Prev Page Preview the previous page of the One-Line Diagram. This command is for multi-page One-Line Diagrams only.

Preview displays the One-Line Diagram as it will appear on paper. You can preview one page, as shown here, or two pages.

Click toolbar buttons to perform actions.


8/16/2006

Press this button To do this One Page/Two Pages Switch between previewing one or two pages of

the One-Line Diagram.

Zoom In Magnify the One-Line Diagram preview by ten percent.

Zoom Out Reduce the One-Line Diagram preview by ten percent.

Close Exit the preview mode and return to the One-Line Diagram.

Notice that in preview mode, the mouse pointer is replaced by the Zoom Preview pointer . You can use the mouse to zoom in instead of the Zoom In button. To zoom in using

the mouse, point to the location on the preview you want to magnify and, click the mouse button.

9.2.2. Layout Options While some document types have standard formatting that PTW applies when you print, the One-Line Diagrams are much more customizable, and you can change layout options to suit your specific needs. Using the Print Layout options, you can set margins, print borders, magnify the printout, and control pagination. Layout options affect only the active One-Line Diagram. All layout options are controlled by the Diagram Layout dialog box.

These settings are not the same as the printer setup, which applies to all printing tasks and depends on the configuration of the selected printer. These settings apply exclusively to One-Line Diagrams, and do not affect the printing of any other document type. Before you print One-Line Diagrams, you should check both the print setup and the layout options. After changing print layout options, you can see the results of the changes by previewing the printed One-Line Diagram on the screen. See Section 9.2.1, “Previewing a One-Line Diagram.”

Turn grey-colored page guides on or off.

Set the distance from the edge of the paper to the One-Line Diagram.

Printing UG 9-5


Margins control the distance between the One-Line Diagram and the edge of the paper. You can set all four margins individually by typing the distance in inches from the One-Line Diagram to the edge of the page. Margins apply to all of the pages in the active One-Line Diagram.

Note: Most printers cannot print to the edge of the page. You should check the

minimum printer margin in your printer’s documentation before adjusting the One-Line Diagram margins. If you set the One-Line Diagram margins smaller than the printer margins, parts of your One-Line Diagram may not print.

If the One-Line Diagram is too large to fit on a single page of the selected printer, you can instruct PTW either to tile the One-Line Diagram over several pages (at standard size), or shrink the One-Line Diagram to fit on a single page. Note that if your One-Line Diagram does not exceed the size of a single printer page, PTW ignores this setting.

If you shrink the One-Line Diagram to fit on a single page, PTW prints the One-Line Diagram as large as possible within the confines of the page and margin settings.

If you tile the One-Line Diagram across two or more pages, it tiles along the page guides visible in the One-Line Diagram viewport.

When you tile the pages, PTW automatically assigns page numbers in rows from top to bottom and left to right. For example, if the One-Line Diagram tiles to 4 pages, the page numbers are as follows:

1 2

3 4

While these numbers do not print on the final One-Line Diagram, you can use them to print a single page or a range of pages, as described in Section 9.2, “Things to Consider when Printing a One-Line .”

Working with Page Guides When you are working on a One-Line Diagram that spans several pages, it is often convenient for you to be able to see where the page breaks will fall on the final printout. Knowing where the page breaks are can help you group components on a single page, make sure that textblocks do not fall on a page break, and so on. Page guides appear as dashed lines in the viewport, indicating the location of page breaks. Page guides do not print, even when they are turned on; they are used strictly as guides to help you lay out the One-Line Diagram.


8/16/2006

You can turn the Page Guide on or off, and control where they fall, using the Page Layout command. Doing this, though, only controls the grey-colored gridlines. It does not control your printer’s output (that is done using the Print Setup command). You must ensure that the Page Guide specifications match the paper size selected for your particular printer, or the lines are useless. For example, you can set the Page Guides to 5-inch by 5-inch, and the lines will appear onscreen with those dimensions, but if your printer’s output is set to 8.5-inch by 11-inch paper, the lines will give you erroneous information about where the page breaks will fall. In addition, if you choose Landscape as the paper orientation in the Print Setup dialog box, the Page Guide width and height specifications have to be manually reversed to accurately show onscreen where the page margins will fall. For example, if 8.5-inch by 11-inch paper is selected as Landscape- instead of Portrait-oriented, you need to manually type 11 in the Width box and 8.5 in the Height box (essentially reversing them) for the Page Guide lines to accurately represent Landscape-oriented paper.

Page guides appear as dotted lines in the viewport as you work on your One-Line Diagram.

You can turn the page guides off at any time.

PTW automatically calculates where the page guides appear based on the page size you select for the page guides, and on the margin settings. You can turn the page guides on and off at any time.

You can also change the size of the page guides independently of the selected printer. For example, the selected printer may be set for 11” × 17”, but you may want to see page guides for 8½” × 11” paper. You can use standard paper sizes, or type in your own height and width values for custom paper. You can change the dimensions of the page guides at any time.

You can print a single border around the entire one-line diagram area. The diagram area is defined as the page margins minus the title block (if the title block is printed). If you tile your One-Line Diagram over several pages, PTW prints a border on each page.

9.3. What is a Form? Now that you have created One-Line Diagrams, Reports, TCC Drawings, and TMS Plots, you may wish to incorporate them into a single, professional-quality printed report. With PTW’s Forms, doing so is surprisingly easy, and can be accomplished without ever leaving PTW. Whether producing inserts for contract plans and specifications, or providing a specialized relay settings report, Forms make your job vastly easier.

Printing UG 9-7


Sample Form Output for TCC, One-line, Titleblock and Logo

A Form is a printing template (that is, a set of instructions to your printer) which designates certain Areas on a page to include these types of documents and files:

• One-Line Diagrams

• Reports

• TCC Drawings

• TMS Plots

• I*SIM Plots

• HI_WAVE Plots

• user-definable Title Blocks (for including date, time and heading text)

• Bitmaps (for including company logos or other graphics)

When you print using a Form, the Form automatically inserts the correct document into the correct Area, so that the paper comes from your printer just as you formatted it. Once you have created a Form, you may save it and use it again; also, you may create many Forms, each with its own format. Your printer treats the entire Form as a single page, and prints it without any excess appearing on a second page.

The key to Forms is the designated Areas. When you set up a Form, you allocate rectangular Areas of the page for one of the documents or files listed above. When you are ready to print using a Form, you choose the Form to use and select which specific documents to insert into the Areas and print. Specify the primary area first to automate the group printing function. When printing a TCC drawing and a One-line on the same page, specify the TCC area first since TCC drawings can store the name of the associated one-line.

TCC Area

Titleblock Area

One-line Area

Logo Area


8/16/2006

For example, you might print using Form portfolio, which you have set to place a Report aside a One-Line Diagram. When PTW asks you to specify which Report and which One-Line Diagram (within the active Project) to insert into those two Areas, you might select ls.rpt and draw1.drw. The next time you use Form portfolio, you might specify Report sc.rpt and One-Line Diagram bldg5.drw. The Form is only a blueprint for the page’s layout⎯it does not keep a specific document in an Area, but asks you each time you print using that Form which document of that Area’s type to insert.

9.4. Creating a New Form When you create a Form, you specify information about the page, including its size and whether or not to draw a border, and the Area designations.

Note: All printers will print with a certain degree of inaccuracy. Laser printers, for example, may be off by as much as 1/8-inch depending on the paper stock, how the paper was inserted, and the printer’s age. Plotters, too, may deviate from their intended print zone because they slip frequently. Therefore, Areas will seldom print in the exact location you designate them; a good rule-of-thumb is to expect a deviation of 1/16-inch in any direction.

9.4.1. Assigning Paper Size and Border Coordinates for the Form The first step in the creation of a Form is to set the Form’s paper size so it matches your printer, and to choose whether you want to print a border on the page.

Click the Document>Form Layout command. The Forms Edit dialog box will appear.

On the Forms tab page, choose the New button and type a name for the Form. If you wish, type some descriptive notes in the Description box about the Form.

Switch to the Page tab page.

Printing UG 9-9


Select or clear the Landscape orientation check box; when cleared, the Portrait Format is used.

Select a page size. Note that the thumbnail representation of the paper changes with the page size. Size availability corresponds directly to your printer driver; therefore, any paper size you select should be manageable by your printer. You do not have to worry that you are creating an unprintable Form.

If you want a border to appear, select the Enable Form Border check box and enter its coordinates. Coordinate (0,0) is the upper left. For example, for a border appearing 1/2 inch around an 8/12 by 11-inch paper size (Portrait-oriented), you would enter the top-left X coordinate as 0.5, the top-left Y coordinate as 0.5, the bottom-right X coordinate as 8.0, and the bottom-right Y coordinate as 10.5. After you have entered the last coordinate, you must place the cursor into another coordinate box so the last coordinate will register and allow the thumbnail representation to draw the border. Note that plotters may automatically create a margin and treat 0,0 as a point indented from the top and left side. Also, some plotters treat 0,0 as the lower-right corner, in which case the thumbnail representation of the paper will actually be, in effect, upside down.

9.4.2. Formatting Areas on the page Areas act as “containers” for each document type. In choosing where to put each Area, you must consider the finished product (that is, how the Form will look when printed). For example, it would not make sense to print a TCC Drawing in an Area that is 5” high and only 1” wide, because the TCC Drawing would squish down into a illegible mass; you’d be better off printing the TCC Drawing in an Area measuring 7” wide and 8” high. By the same token, a Title Block consisting of two lines of text would look odd in an Area measuring 7” wide and 9” high—it’d be better suited for the 5” wide by 1” high Area.

Naturally, you can demarcate the Areas anywhere you want, and we do recommend that you experiment, especially if you want to achieve a different look than that available from the predefined Forms; however, the predefined Forms do provide good examples, since each Area’s dimensions have been optimized for its document type.

To create new Areas, switch to the Areas tab page.


8/16/2006

Click the New button to create a new Area. The New Area dialog box will appear.

Choose the Area’s data type and type a name for the Area, then click the OK button. Note that the name you type only acts as a name for the Area—it does NOT determine what document or file will be inserted. The document or file that the Area will contain is determined by which option button you select. Therefore, to avoid confusion be sure to type a name for the Area that matches the document or file it will contain (for example, you wouldn't select the TCC Drawing area and name the Area “TMS Plot”).

The order that the area types are specified can be important since the documents are arranged based on the first area specified. If you are printing TCC and one-lines on the same form, specify the TCC area first, since the TCC drawings store the name of an associated one-line to automate document selection.

Specify the Area’s coordinates using the X and Y coordinate boxes. Coordinate (0,0) is the upper left. For example, for an Area spanning the entire page on an 8/12 by 11-inch

Printing UG 9-11


paper size (Portrait-oriented), you would enter the top-left X coordinate as 0.5, the top-left Y coordinate as 0.5, the bottom-right X coordinate as 8.0, and the bottom-right Y coordinate as 10.5. After you have entered the last coordinate, you must place the cursor into another coordinate box so the last coordinate will register and allow the thumbnail representation to draw the border. Note that plotters may automatically create a margin and treat 0,0 as a point indented from the top and left side. Also, some plotters treat 0,0 as the lower-right corner, in which case the thumbnail representation of the paper will actually be, in effect, upside down.

If you want a border to appear, select the Print with Border check box.

Repeat the above steps for all the Areas that you want to create. Areas may overlap, and even lie within, other Areas (this produces a nice effect with a TCC Drawing and its associated One-Line Diagram, as you can place the One-Line in the lower-left corner of the TCC Drawing; see any of the “TCC & One-Line” predefined Forms for an example this).

Once you have defined the dimensions for all of the Areas, you need to provide formatting information that is specific for each Area type. To do this, switch to each tab page which has an Area of that type. For example, in the following picture,

there are three Area types: TCC, One-Line, and Title Block. Therefore, in order to provide formatting information for each of these three, we need to switch to three of the remaining six tabs: TCC, One-Line, and Title Block. We won’t have to use the Report, Plot, or Picture tabs because we have no Areas of those types (and in fact, if we did switch to any of these other tabs, all the options would be grayed out because there would be no Areas to format).

Formatting the One-Line Areas


8/16/2006

For each One-Line Area, you need to select or clear the transparent background check box. When selected, documents such as TCC Drawings lying underneath the One-Line Area will be visible; when cleared, the One-Line Diagram area will print with a blank background. This selection is irrelevant if you do not have Areas overlapping or lying atop one another, or if you are using a plotter (which cannot print transparent backgrounds).

Datablocks can be turned-off at the form level or selected to display the last datablock applied to each one-line or the default datablock assigned to the project.

Formatting the Report Areas

For each Report Area, you need to select a font type. If your Report is a Load Schedule, we recommend that you maintain the PIXymbolsExtended font. Keep in mind that Reports will not shrink to fit; they maintain the point size assigned to them. Therefore, these should be reduced to very concise information, so they will fit into an Area. If the right edge of the Area is not far enough from the left, the right half of the Report will be clipped.

Printing UG 9-13


Formatting the TCC Drawing Areas

For each TCC Area, you need to select a Grid Density. This determines whether or not the TCC grid will appear, and if so, how densely. (The highest density actually prints with the density of K&E log-log paper, with quite nice results on higher resolution printers.) If you are printing with a grid, you also need to set the Grid color and the Line Width for the grid. The Grid Label Density determines the number of labels for each decade, which can be less than or equal to the number of grid lines per decade.

Note: Some printer drivers map light colors to white and dark colors to black. If you pick a light grey color for grid lines, they may actually print as white lines (invisible).

Datablocks can be turned-off at the form level or selected to display the last datablock applied to each TCC or the default datablock assigned to the project.

For each TCC Area, you can select or clear the Colors to Black and White check box. This determines whether or not colors will be printed. The selection is irrelevant if you are using a black-and-white printer, although since the curve patterns may print slightly differently; you should test each, as printer output varies.

For each TCC Area, you can select or clear the Maintain Aspect Ratio check box. If you choose a TCC Drawing to maintain fixed aspect ratio, the Drawing will become as large as it can to fit into the Area while still maintaining the ratio of width to height. Therefore, unless the Area matches exactly the dimensions of the TCC Drawing, there will be extra space across the top and bottom, or along the left and right. Without fixed aspect ratio, the Drawing will stretch either its left and right sides or its top and bottom sides so it fits the Area.

For each TCC Area, you can set the Device font, which controls the font of the pointer labels.

For each TCC Area, you can select or clear the Print Grid Area Only check box. When selected only the grid area will be printed. When cleared the entire TCC Drawing, including the Amperes and Seconds labels surrounding the grid, will print. When this


8/16/2006

option is cleared, which means the labels will print, you need to set the Background font. (The Device font option sets the font for the pointer labels on the TCC.)

For each TCC Area, you can select or clear the Print Default Title Block check box. (Be sure that the Print Grid Area Only option is not selected, or this Default Title Block won’t print even when selected.) When selected the line of information that appears at the bottom of a TCC will be printed. The line gives the TCC name, Current Scale, and Reference Voltage, and usually reads something like this:

“TCC1.TCC Ref. Voltage 480 Current Scale X 10^1”

This line is merely part of the TCC Drawing and should not be confused with the Title Block Area, which is a separate Area that has its own coordinates. Of the two, the Title Block Area provides superior flexibility and formatting, but you can print this Default Title Block and print a Title Block in the Title Block Area if you want, since they aren’t connected with one another.

Lastly, for each TCC Area you can set the Border Margin Factors. These settings determine the margin between the Area’s border and the TCC Drawing itself.

Formatting the Title Block Areas

This is the text that will appear in the Title Block. The text that appears between < and > are formatting fields, which are not printed but rather contain instructions for specific items. (If you have used the HTML programming language, which is used to create Internet web pages, the concept will be familiar.) The fields that you see in the list box are fields that will insert the listed information. For example, the <Current Date> field will insert the date when you print the form, so that the end result will not be “<Current Date>” but “March 18, 1998.” To insert one of these fields into the Title Block, simply highlight it and click the Insert button.

This field Inserts this information <TCC Name (TCC)> The file name of the TCC Drawing

<TCC Ref Voltage (TCC)> The reference voltage of the TCC Drawing

Printing UG 9-15


This field Inserts this information <TCC Scale (TCC)> The current scale of the TCC Drawing

<One-Line Name (Oneline)>

The file name of the One-Line Diagram

<Project Title> The title specified under Project>Options>Print Using Form option group (see Section 9.4.3, “Setting the Project Options for the Title Block and Picture Areas”)

<Current Date> The date that you are printing

<Current Time> The time that you are printing

You may also format the text in each line as left-aligned, centered, or right-aligned. Each line may have all three types of formatting, but only one of each per line. For example, you may have a line which has left-aligned and centered, but you may not have a line which has two left-aligned lines.

The alignment codes look like this: <!L> <!C> <!R>, which are left-aligned, centered, and right-aligned.

You put the code before the line that needs to be formatted. For example, the following lines,

<!L>George Washington <!C>John Quincy Adams

<!R>Woodrow Wilson

will be formatted like this when printed:

George Washington John Quincy Adams.

Woodrow Wilson

To insert a left-aligned, centered, or right-aligned code, simply click the appropriate option button.


8/16/2006

Formatting the Plot Areas

For each Plot Area, you need to set the Image Size. This determines how big the graph portion will be in relation to the axes and labels.

For each Plot Area, you need to set the Viewing Style. If you are printing to a black-and-white printer, you should use one of the Monochrome options for best results.

Lastly, for each Plot Area, you need to set the Font and Font Size for the axes and labels surrounding the graph portion of the Plot.

Formatting the Picture Areas

Picture Areas will insert a bitmap (BMP) or enhanced metafile (EMF) when printed. These Areas are useful for inserting, for example, company logos.

For each Picture Area, you need to choose its Scale, which determines how the picture will be inserted.

Printing UG 9-17


• The Best Fit option will stretch the picture’s height and/or width to fit the Area.

• The Fit to Height option will resize the picture while still maintaining the ratio of width to height so it will fill the Area from top to bottom; the left or right will be cropped if necessary.

• The Fit to Width option will resize the picture while still maintaining the ratio of width to height so it will fill the Area from left to right; the top or bottom will be cropped if necessary.

• The Actual Size option will place the picture in the center of the Area. It will not be resized, but it will be cropped if the Area is smaller than the picture.

• The 25%, 50%, and 75% options will reduce the size of the picture to the percentage shown and place the picture in the center of the Area. It will be cropped if the Area is smaller than the picture.

For each Picture Area, you need to set the Margin. These settings determine the margin between the Area’s border and the picture itself.

If you want a default picture which will always be inserted into this Area (as opposed to choosing the picture file at print time), use the Browse button to select a picture file. If you click the Project Logo button, the picture that you have designated under Project>Options>Print Using Forms option group as the Project Logo will be used (unless no Project Logo has been designated). See Section 9.4.3, “Setting the Project Options for the Title Block and Picture Areas” for information on choosing a picture file as the Project Logo.

9.4.3. Setting the Project Options for the Title Block and Picture Areas Because they are less likely to be changed frequently, the Title Block and Picture Areas allow you to configure them in the Project options: for the Title Block Area you can specify title text that you always want the Title Block Area to use, and for the Picture Area you can specify a picture file that you always want the Picture Area to use. The advantage of this feature is that when you print using a Form you won’t need to type the title text or pick the picture file if these two aspects will never change.


8/16/2006

To set these two Project Options, click the Project>Options command and select the Print Using Forms option group:

The text that you type in Project Title will be used in any Title Block Area which includes the <Project Title> field.

Similarly, the picture file that you pick for Project Logo will be used in any Picture Area in which you have clicked the Project Logo button.

9.5. Printing Using a Form To print a Form, you may either use one of the predefined Forms or use one that you have created. (You may want to first try printing with the predefined Forms that were included with PTW before trying to create a new one. The predefined Forms will most likely cover your typical needs, and they have been optimized for their paper size.)

To print using a Form

1. Click the Document>Form Print command. The Print Using Form dialog box will appear.

Printing UG 9-19


2. Select or clear the Show Printer Page Size Forms Only check box. When selected, only the Forms that match the current printer page size will be displayed. For example, if your printer is currently set to print 8.5x11 paper, none of the 11x17 Forms will appear, since they cannot be printed with that printer setup.

3. Highlight the Form that you want to print. Note that the Areas on that Form appear below it. The square icons will indicate which are Forms and which are Areas. This is a Form: This is an Area:

4. Below the Form’s name, select an Area. Note that the Select Data button below the box now becomes active.

5. Choose the Select Data button. Documents of the Area’s type will appear.

6. Choose the One-Line, Report, TCC Drawing, TMS Plot, or picture file that you want to insert into the Area (Title Block Areas do not require any file to be selected because they take their information from the Form’s layout.)

7. Repeat steps 4-6 until every Area that you want to use has a document assigned to it. (You don’t have to put a document in every Area; if you want an Area to print blank, just don’t select a file for it.)

8. Choose the Print button.

9.5.1. Previewing a Form Before Printing To verify that the Form will appear as you expect it to, you may preview it as it will actually be printed.

To preview a Form before printing

1. Click the Document>Form Preview command.

2. Follow the steps for printing using a Form, above. The only difference is that the Print button will instead be labeled “Preview,” and when you click it, a Preview will be displayed.

9.5.2. Printing a Group of Documents (Batch Printing) To open the Group Print feature, click the Group Print button in the Print Using Form dialog box.

This feature allows you to use a single Form to automatically print a number of documents. Printing a number of documents with a single function bypasses having to pick a single document to print, wait for the printer to print, then repeat the process for each document. Keep in mind that when you use the Group Print function, the “blueprint” for the page does not change—just the documents that are inserted into the Areas. Each row on the spreadsheet represents one print “run” of the Form, so that the documents that you have chosen for each Area will be printed on each run. (One “run” of the Form simply means the printing of one sheet of paper.) Note this example:

three Areas on the Form.


8/16/2006

In this example, the first run will print mainprot.tcc in the TCC Area, mainprot.drw in the One-Line Area, and the Title Block (whose information comes from the Form) in the Title Block Area. The second run will not be printed because it has not been checked in the Print column. The third run will print mtr28.tcc in the TCC Area, mtr28.drw in the One-Line Area, and the Title Block in the Title Block Area.

All documents matching the primary document type defined in the form will automatically be displayed in the Group Print window. To pick individual documents to print, you can add rows to Group Print window using the. Add Row button. Similarly, to delete a row, click the Delete Row button. To remove the data from an Area so that no data will print in that Area for that run of the Form, highlight the Area and click the Clear Cell button (when you remove an Area’s data, the words “<empty>” will appear in the cell). Since Picture Areas and Title Block Areas get their data from the Form’s Layout, the Clear Cell button will not be active if you highlight them.

To choose a different document than that listed for a particular Area (or to add a document to an empty Area), highlight the cell and click the Select Data button.

To quickly check all the runs of the Form, click the Check All button; to uncheck all runs, click the Uncheck All button. Lastly, to print the selected runs of the Form, click the Print Selected button (you must have at least one check in the Print column for anything to be printed).

Other points to consider:

• When the Group Print dialog box first opens, the number of rows that will appear is determined by the number of Documents you have in the Project that match the first document type in the Form definition. For the previous example, the first document type in the Form definition is a TCC drawing. If you have not created any TCC Documents, no rows will initially appear. (You can still add rows using the Add Row button.)

• When the Group Print dialog box first opens, only the TCC Reports in the Project will appear, not the entire list of Reports in the Project. You can still choose a different report for that Area by selecting the cell and clicking the Select Data button.

Printing UG 9-21


• The order that the columns appear is based on the order that the Areas appear in the Form’s Layout. The order of the columns does not affect their printing.

• Since Title Block Areas and Picture Areas get their data from the Form’s layout, you do not need to select any data for them.


Appenix A

Importing DOS Projects

If you have an existing project in a Power*Tools for DOS product that you want to analyze using PTW, you can quickly import that project into the PTW project format. PTW comes with a standalone application called Import which can import DAPPER for DOS Projects and Libraries, and CAPTOR for DOS Projects and Libraries.

IN

TH

IS

CH

AP

TE

R

A.1 DAPPER Import ....................................................................................................... 2 A.2 Notes on Importing ................................................................................................. 10 A.3 Converting Older DOS Projects ............................................................................. 11 A.4 Running Import for CAPTOR Projects................................................................... 13 A.5 Running Import for CAPTOR Libraries ................................................................. 17

UG 2 User’s Guide

8/16/2006

A.1 DAPPER Import Before beginning any Import procedures, you should close PTW

Import is a standalone Windows application included with the PTW package that converts Power*Tools for DOS projects, libraries, or both, into the PTW format. Release 1.0 of Import works with the following DOS products:

• DAPPER and DAPPER-IEC for DOS Versions 3.5 and 4.5

• DAPPER-LAN Version 4.0

• HI_WAVE for DOS Version 3.5 as a DAPPER project.

• I*SIM for DOS Version 3.5 as a DAPPER project.

Note: Import does not convert harmonic data from HI_WAVE or dynamic simulation data from I*SIM in this release, but it can import these projects for use with currently existing PTW studies such as the Demand Load Study, Short Circuit Study, and so on.

Many of the components in DAPPER for DOS will be imported with little or no change to their data. However, you should understand how Import translates the DOS components into PTW components so you won’t be surprised by the results.

Schedules Since the PTW schedule has more “fields,” or places to enter data, than the DOS Schedule, those fields that were not available in DOS will be set to default values or left blank for you to fill in. For example, if a motor in DOS has an FLA of zero, it will import with a rated size of zero.

A blank line circuit in the DOS schedule will import as a blank circuit.

Loads which have a Demand Code of 1 through 8 in the DOS Schedule will be imported as “little loads” and placed in the PTW Schedule. These “little loads” are the same loads which you add to a schedule using the 1-Pole, 2-Pole, and 3-Pole buttons located on the Panel/MCC/Switchboard subview of the Component Editor, and which do not appear on the One-Line Diagram and are not searched during Queries.

For Panel Schedules, if data has been entered in the Unit Load and the Unit Quantity fields, Import uses this formula to calculate little load rated size:

Little Load Rated Size Unit Load Load Quantity= ×

Otherwise, if one of those two fields was left blank, Import uses this formula:

Little Load Rated Size Total VA Load=

For MCC Schedules, Import uses this formula (0.8 is the default efficiency value, which was not editable in DOS but may be changed in PTW):

Little Load Rated Size(HP Size) 0.746

PF Size=

b gb gb g10.

Appenix A

Importing DOS Projects UG 3


For Switchboard Schedules, Import uses this formula:

Little Load Rated Size connected kVA=

Loads which have a Demand Code of 9 or 10 in the DOS Schedule will be imported as induction motors and placed in the PTW Schedule. Also, they will be attached to the bus to which the Schedule is attached. Each induction motor will be named “MTR XXXX-YY,” where XXXX is the bus number and YY is the circuit number. Import determines the rated size of the induction motor using the appropriate formula:

For Panel Schedules, if data has been entered in the Unit Load and the Unit Quantity fields, Import uses this formula to calculate induction motor rated size:

Induction Motor Rated Size (Unit Load Load Quantity)1000

=×

Otherwise, if one of those two fields was left blank, Import uses this formula:

Induction Motor Rated Size (Total VA Load)1000

=

For MCC Schedules, Import uses this formula (0.8 is the default efficiency value, which was not editable in DOS but may be changed in PTW):

Induction Motor Rated Size(FLA) Bus Voltage

1000 =

b ge jb gb g

3

0 8.

For Switchboard Schedules, Import uses this formula:

Induction Motor Rated Size connected kVA=

Motors When importing a motor contribution where the value in the DAPPER for DOS base kVA field is different from the value in the kW or hp field, PTW determines that multiple motors exist at the bus. For example, if the DOS base kVA is 1000 kVA and the kW or hp field is 250 hp, then PTW assumes that there were four 250 hp motors at the bus. The Base kVA for the total group is 1000 kVA, and the subtransient reactance for the group is

calculated as four times that of the Xd″ value imported from DOS. During the

calculations for the fault current, this subtransient reactance value is divided by the number of motors indicated on the first subview. A numerical example follows.

Consider the case in DOS, where the Base kVA is 1000 kVA and the kW or hp field is 250 hp. The DOS subtransient reactance is .25 pu on the kVA base. Running a fault study in DAPPER for this 4 kV motor results in a three phase fault current contribution of 577 amperes from the four 250 hp motors at the bus. In PTW, the kVA base is 1000 kVA,

but the imported Xd″ is 1 pu. This value is divided by the number of motors (four each)

to determine the equivalent circuit impedance for the four machines on the bus. Thus, in PTW, the motor fault duty contribution is:

UG 4 User’s Guide

8/16/2006

I kVA.25 kV

ASC3Φ = =1000

3 4 0577b ge jb g.

2-Winding and 3-Winding Transformers The phase shift angle is determined using the connection and neutral impedance placed in the first winding that has a Wye-Ground connection. Two winding transformer impedance is from the transformer library, if not user-defined.

Feeders

Feeders in the DOS Projects are imported as cable components, which take part of their data from the Cable Library. Feeders that are specified as impedance data, per unit impedance data, or transmission lines are imported as Pi equivalent components.

You can also import DAPPER V3.0-V3.4 files by first converting them to V3.5 files using a DOS utility called MF2PF, which is also included with PTW. Refer to Section A.3, “Converting Older DOS Projects” for information and instructions.

To Start Import

1. Click Start>Programs>Power*Tools for Windows>DOS Dapper Captor Project Import.

The interface for Import is easy to use, consisting mainly of the Import dialog box, which lets you specify the paths to your projects and libraries.

As it builds the PTW project, Import implements some basic conversion methods that affect certain component types. For an understanding of these methods, refer to Section

Select the directories where your DOS project and libraries are stored.

Select a path for the new PTW project.

Appenix A



“Methodology.” After importing a project or libraries, you should always compare the PTW project and study results to the original to verify consistency.

Note that Import actually creates a new PTW project using the DOS files; it does not change the format of the DOS files directly. This means that all your DOS Project and Library Files are left intact and unchanged in their original locations.

Library files are automatically stored in the same directory as your project, and have the same name as the project but with various file extensions according to type. So if your project is named plant, the transformer library for that project would be named plant.xfr.

Important: In order to import a Project, you must have all the files that make up the Project or the Import program will create an incomplete Project. For example, if you want to import the Plant project included with DOS-DAPPER, you would need these files:

Project files Library files plant.pf1 daplib0.lb plant.pf2 daplib1.lb ... ... plant.pf8 daplib7.lb As you can see, you must include the whole series of Project and Library files, not just one of each. Note also that the files must all be grouped together (that is, the Project files must be in the same folder, such as Projects, and the Library files must be in the same folder, such as Library). The Import program only asks for the Project and Library file locations once, and assumes the rest of the Project files will be in the same project folder and the rest of the Library files will be in the same library folder.

To import a DOS Project and Libraries

1. Under From DOS products, do both of the following:

• In the Project box, type the path to the DOS project you want to import. You can also select the path using the Browse button.

• In the Library Path box, type the path to the libraries you want to import. You can also select the path using the Browse button.

2. Under To Power*Tools for Windows, type path to a new project, or to an existing project including the project filename. You can also use the Browse button to select a path. If you select an existing project, that project will be replaced with the imported project. If you type a path that does not exist, Import creates it for you.

3. Click the OK button. Import begins converting your project.

As Import proceeds, it may bring up additional dialog boxes asking you to:

• Convert Special Bus Loads

• Convert End Use Loads

• Merge machine load values and associated fault contributions

UG 6 User’s Guide

8/16/2006

You may or may not need to perform all of these tasks, depending on the configuration of the project. If a particular dialog box does not appear, Import has determined that it is not necessary for importing your project.

For information and instructions on all of these procedures, refer to the following sections up to “Merging Machines and Fault Contributions.”

A.1.2 Converting Special Bus Loads In Power*Tools for DOS products, miscellaneous loads on the bus are modeled as special bus loads, which do not “exist” as an entity apart from the load bus. In PTW, on the other hand, special bus loads must be converted into motors or non-motor loads, which are discrete components connected to the bus. Import automatically converts many of your special bus loads based on the following criteria:

Load Type in DOS Converted as Constant current or constant impedance loads

Non-motor loads. By definition, motors cannot be defined as constant current or constant impedance loads, so when PTW finds these loads, it assumes a non-motor load type.

If Import finds special bus loads in your DOS project specified as constant kVA loads, it will ask you how to import those loads. You can import each constant kVA special bus load as a non-motor load, synchronous motor or induction motor. After you specify the load as a particular type, import creates an appropriate component and connects it to the load bus.

For information on the methods Import uses to convert each of the load types, refer to “Special Bus Load Conversion Values” later in this chapter.

To convert special bus loads

1. In the Constant kVA Loads box, do one of the following:

• To convert loads one at a time, select a single load.

• To Convert several loads at once, select all of the loads you want to convert to a common load type. To make a consecutive multiple selection, hold down the

Select the Special bus load.

Select the type of load you want the special bus load to be converted into in PTW.

Appenix A



SHIFT key while selecting. To add individual loads to the selected list, hold down the CTRL key while selecting.

2. Under Import as a new Load Type, choose the button that corresponds to the new load type you want. The selected load or loads will be converted into a load component of that type and connected to the corresponding load bus.

3. Repeat Steps 1 and 2 for all of the constant kVA loads you want to convert. Any remaining loads are imported as non-motor loads.


Special Bus Load Conversion Values Import converts special bus loads into PTW load types using the following formulas:

Component Variable Value Rated Size

kW kVAR2 2+

Rated Units kVA

Power Factor cos arctan kVAR

kWFHG

IKJ

Power Factor Units Lagging if kVAR > 0 Leading if kVAR < 0

Rated Voltage Bus Voltage

Demand Category / Energy Audit Energy Audit

Energy Audit Factor 1.0

Induction Motor Efficiency 1.0

A.1.3 Converting End Use Loads In Power*Tools for DOS, end use loads are specified as part of the bus record, and do not exist as an entity apart from the load bus. On the other hand, in PTW end use loads must be converted into motors or non-motor loads, which are unique components connected to the load bus. Import automatically converts many of your end use loads based on the following criteria:

Load Type in DOS Converted as Constant current or constant impedance loads Non-motor loads.

Demand Load Library classifications 9 and 10 Induction Motors. The Demand Load Library reserves these classifications for induction motors.

If Import finds end use loads in your DOS project other than the types listed above, it will ask you how to import those loads. You can import each end use load as either a non-motor load, synchronous motor or induction motor. After you specify the load as a particular type, import creates an appropriate component and connects it to the load bus. Note that for buses with schedules, the resulting end use loads from the schedule are imported, but not a detailed definition of the schedule itself.

UG 8 User’s Guide

8/16/2006

For information on the methods Import uses to convert each of the load types, refer to “End Use Load Conversion Values” later in this chapter.

To convert end use loads

1. In the Bus List box, do one of the following:

• To convert loads singly, select a single load bus.

• To convert several loads at once, select all of the buses whose loads you want to convert to a common load type. To make a multiple selection, hold down the SHIFT key while selecting. To add individual loads to the selected list, hold down the CTRL key while selecting.

2. In the Load Category box, do one of the following:

• If converting loads singly, select a load category for the selected bus.

• If converting several loads at once, select all of the loads categories you want to convert into a single load type.

3. Under Import as a New Load Type, choose the button that corresponds to the new load type you want. The selected load or loads will be converted into a load component for that type for all selected buses. Each load component is automatically connected to the corresponding load bus.

4. Repeat Steps 1 through 3 for all of the end use loads you want to convert. Any remaining loads are imported as non-motor loads.


End Use Load Conversion Values Import converts end use loads into PTW load types using the following values. These values are the same for non-motor loads, induction motors and synchronous motors:

Component Variable Value Rated Size End use load size, if the load size is in VA, convert to kVA

Rated Units kVA or Amps

Power Factor From the Demand Load Library

Select the bus and the end use load.

Select the type of load you want for the end use load.

Appenix A



Component Variable Value Power Factor Units From the Demand Load Library

Rated Voltage Bus Voltage

Demand Category / Energy Audit Demand Category

Demand Category The Demand Category for the end use load

Energy Audit Factor 1.0

A.1.4 Merging Machines and Fault Contributions In Power*Tools for DOS products, each fault contribution is modeled in various locations throughout the program: the contribution itself is modeled as a branch record connected to a bus, while the motors/generators associated with the contribution are modeled as properties of the bus record itself. In PTW, fault contributions are modeled as a property of a separate machine (generator or motor) component connected to the bus component.

If Import finds a contribution branch record and a machine that express a clear one-to-one relationship, it merges the fault contribution data with the machine load data into a single component. For example, if Bus 15 has one induction motor and one induction motor contribution record, Import assumes that these data items are related and merges them into a single induction motor component.

If the relationship between your contributions and machines on a given bus is ambiguous, Import will ask you how to merge the data.

The Merge Machines and Contributions dialog box takes its machine data both from your DOS project, and from any motors you created while converting end use and special bus loads earlier in the import process.

To merge machines and contributions

1. In the Bus List box, select the bus associated with the machine.

2. In the Machines box, select the machine you want to merge.

3. In the Contributions box, select the contribution you want to merge.

For each bus ...

...match the machine to the proper contribution ...

... and choose the Merge button.

UG 10 User’s Guide

8/16/2006

4. Click the Merge Button.

5. Repeat Steps 1 and 2 for all of the machines and contributions you want to merge. If you do not merge all of the machines or contributions, each remaining machines is imported as an individual motor or generator with no contribution data, or with the rated size defaulted to zero.


Methodology When importing a motor contribution where the value in the DAPPER for DOS base kVA field is different from the value in the kW or hp field, PTW determines that multiple motors exist at the bus. For example, if the DOS base kVA is 1000 kVA and the kW or hp field is 250 hp, then PTW assumes that there were four 250 hp motors at the bus. The Base kVA for the total group is 1000 kVA, and the subtransient reactance for the group is

calculated as four times that of the Xd″ value imported from DOS. During the

calculations for the fault current, this subtransient reactance value is divided by the number of motors indicated on the first subview. A numerical example follows.

Consider the case in DOS, where the Base kVA is 1000 kVA and the kW or hp field is 250 hp. The DOS subtransient reactance is .25 pu on the kVA base. Running a fault study in DAPPER for this 4 kV motor results in a three phase fault current contribution of 577 amps from the four 250 hp motors at the bus. In PTW, the kVA base is 1000 kVA,

but the imported Xd″ is 1 pu. This value is divided by the number of motors (four each)

to determine the equivalent circuit impedance for the four machines on the bus. Thus, in PTW, the motor fault duty contribution is:

Isc3 577φ = =1000kVA

14 3 4.0kV

Ae je jb g

A.2 Notes on Importing Most component types are imported directly from Power*Tools for DOS programs into PTW. In some cases, however, Import has to consolidate data from various locations in the DOS product to build a single component. For components other than loads, this process is automatic and invisible.

PTW thinks of components as single “objects” that have several attributes associated with them. For example, transformers have connection data, impedance data, and so on. All of these individual data attributes do not “exist” apart from the component. In certain cases, the DOS programs store data for single components in different places. As Import builds the PTW database, it merges or calculates data for the following component types:

Component type Conversion Cables Feeders in the DOS projects are imported as cable components,

which take part of their data from the Cable Library. Feeders that are specified as impedance data, per unit impedance data, or transmission lines are imported as Pi equivalent components.

Two and three winding transformers

The phase shift angle is determined using the connection and neutral impedance placed in the first winding that has a Wye-Ground

ti T i di t f i d i f th

Appenix A



Component type Conversion connection. Two winding transformer impedance is from the transformer library, if not user-defined.

A.3 Converting Older DOS Projects Importing DAPPER V3.0 to V3.4 projects into PTW is a two step process. First, use MF2PF, a DOS utility included with PTW, to convert the files from the pre-3.5 file format to the V3.5 format. Next, use Import to import the V3.5 files into PTW. The Library files used with early versions of DAPPER can be imported directly into PTW.

Note: This procedure is not required for any version of DAPPER-IEC or HI_WAVE.

If you don’t know whether of not you need to run MF2PF on your DAPPER files, use the Windows Explorer to check the project’s file extension. To do this, switch to the Windows Explorer, go to your DAPPER project directory and use the search function to find files that have an MF* extension. All versions of DAPPER prior to V3.5 use MF* project files, whereas later versions use PF* files. If you find an .MF* file (for example PLANT.MF1, PLANT.MF2, and so on.) in your project directory, you need to run MF2PF on your project before you can import it into PTW.

After converting the MF files to the V3.5 format, you can use Import to convert them into the PTW format.

To run MF2PF

1. Click Start>Programs>MS-DOS (called the Command Prompt in Windows NT).

2. Type cd\ptw32\bin, and press the ENTER key. This command switches you to the directory that contains MF2PF.

3. Type MF2PF and Press the ENTER key. This command starts MF2PF.

Note: The MS-DOS icon runs DOS under Windows. You should be able to run MF2PF under Windows’ DOS shell, but if you experience any problems, contact PTW.

MF2PF uses a single screen that handles the entire conversion process.


8/16/2006

To convert DAPPER V3.0-V3.4 files into DAPPER V3.5 files

1. In the Path to PF Files box, type the path for the DAPPER V3.5 files. This path must point to an existing directory. MF2PF cannot create a new directory.

2. In the Enter Project File Name box, type a valid DOS filename for the new project.

3. In the Path to MF Files box, type a path to the older DAPPER project. This path must contain the project files for the project.

4. In the Select Action Box, select Convert to PF* File — Retain Original Bus Numbers. This option converts your MF files to PF files and retains the original bus numbering scheme.

5. Press the F1 key to convert the project. MF2PF will tell you when it has finished converting the project.

6. Press the F10 key to exit MF2PF and return to DOS. MF2PF converts your old project into the V3.5 format, and saves it in the specified directory.

To return to Windows from the DOS shell, type exit at the DOS prompt and press the ENTER key. You can import your project into PTW from this point.

Type a path for the V3.5 project files.

Type a path to the older project files. Select conversion options here.

Appenix A



A.4 Running Import for CAPTOR Projects This program will import your CAPTOR for DOS Projects into the Power*Tools for Windows format.

Important: If you have the original CAPTOR for DOS Library files, you can import them into a CAPTOR for Windows Library file. This is the recommended procedure, because there will be less possibility of devices not being found. To do so, see Section A.5, “Running Import for CAPTOR Libraries” before continuing. If you do not have the original CAPTOR for DOS Library files, continue reading.

Based on your choice, Import will either create a new PTW Project or merge the CAPTOR for DOS Project into an existing PTW Project; it does not change the format of the DOS files directly. This means that all your DOS Project and Library Files are left intact and unchanged in their original locations.

Before running Import, you should be aware of the following:

• In addition to Device Not Found messages (discussed in Section A.4.1, “Device Not Found message,” cable damage curves may not show up because insufficient data exists in the DOS format to convert them into the Windows format.

• If you merge a CAPTOR for DOS project with an existing PTW Project, the protective devices will not be connected to the electrical system. They will maintain their proper bus voltages, of course (until you connect them, at which point they will reference their bus voltages from the connected bus), but you will need to manually connect them.

• If you merge a CAPTOR for DOS project with an existing PTW Project, components from the DOS Project will replace any same-named components in the PTW Project. For example, if “Fuse 1” exists in both the CAPTOR for DOS Project and the PTW Project, the “Fuse 1” coming from the CAPTOR for DOS Project will replace the “Fuse 1” in the PTW Project.


8/16/2006

To import a CAPTOR Project

1. (Be sure PTW is closed.) Under From DOS CAPTOR Project, type the path to, or use the Browse button to find, the CAPTOR Project you want to import.

2. Set the option button either to New Project or to Merge Project.

• If set to New Project, use the Browse button to find a location for the new Project to be created. Be sure to type a Project Name. Note that a new folder and a new Project file will be created. For example, if you type FACTORY in the Project Name box, and you have set the Project Path to X:\PTW32\PROJECTS, a new folder, called X:\PTW32\PROJECTS\FACTORY, will be created, and within that folder will be the new PTW Project file, called FACTORY.PRJ

• If set to Merge Project, type the path to, or use the Browse button to find, the PTW Project with which you want to merge the CAPTOR Project.

3. If you have already imported your CAPTOR for DOS Libraries into a CAPTOR for Windows Library using the DOS CAPTOR Library Import program, proceed to step 4. If you have not yet imported your CAPTOR for DOS Libraries, but you have them available, see Section A.5, “Running Import for CAPTOR Libraries.” If you have not imported your CAPTOR for DOS Libraries because they are not available, skip to step 5.

4. In the Library Path box, type the path to, or use the Browse button to find, the CAPTOR for Windows Library that you created by importing your CAPTOR for DOS Libraries. (The CAPTOR for Windows Library will have an *.LIB extension.) The Import Program needs this Library because it extracts data from it during the import process. Skip to step 6.

5. In the Library Path box, type the path to, or use the Browse button to find, the CAPTOR for Windows Library supplied with PTW and located in the X:\PTW32\LIB folder. (The CAPTOR for Windows Library will have an *.lib extension.) The Import Program needs this Library because it extracts data from it during the import process. Proceed to step 6.

6. Click the OK button. Import begins converting your Project.

Find the CAPTOR Project you want to Import.

Set to New or Merge Project.

Locate the existing Project or pick a location for the new Project.

Locate the Library you imported ( if it wasn’t available, locate the Library included with PTW).

Appenix A



7. When you are ready to open the Project, keep in mind that if you had your CAPTOR for DOS Library available and used it in step 4, you need to set the Library Reference (available under Project>Options>Library) to point to the new Library you created.

When Import runs, you may receive one or more warnings telling you “Device Not Found.” See Section A.4.1, “Device Not Found message.”

A.4.1 Device Not Found message When Import runs, you may receive one or more warnings telling you “Device Not Found.” These warnings also appear in a text-format log file called <project>.log, where project is the name of the project you are importing. (To view the log file, open it in a text editor such as NotePad, which comes with Windows. You can find the log file in the same folder as the imported project.) If you prefer not to see this message repeatedly, you can check the “Don’t show this message again” checkbox (the log file will still be created).

The “Device Not Found” message signifies that a protective device in the CAPTOR Project being imported uses a Library item that cannot be found in the CAPTOR for Windows Library. This means that Import cannot find the Library item under its three identifying elements:

• Manufacturer (for example, “Square D”)

• Description (for example, “100-800 A”)

• Type (for example, “ME LI B”)

Unless the Manufacturer, Description, and Type of the device in your CAPTOR Project match exactly a device in the Library under the proper device category, Import will not find the device (and CAPTOR for Windows will not be able to plot the curve). Either a) the device does not exist in the Library, b) the device exists somewhere in the Library but under a difference device category, or c) the device was not imported by the DOS CAPTOR Library Import program (see Section A.5, “Running Import for CAPTOR Libraries”).

So how do you find the missing data? Depending on the device’s origin, this may or may not be easy. Refer to the following notes:

• You will have less unfound devices if you have access to the original CAPTOR for DOS Library files with which the CAPTOR Project was created, especially if the stock Libraries were customized at all. Even though the CAPTOR for Windows Library includes all of the devices from the stock CAPTOR for DOS Libraries (except for Ground Fault and Motor Overload Devices—see following), it will not include any devices added or customized by the user.

• If you have the original CAPTOR for DOS Libraries with which the CAPTOR Project was created, and a device is still not found, the Libraries may have been altered after the CAPTOR Project was created, so that you have a later version of the Libraries that do not accurately reflect the devices in the CAPTOR Project.

• If you are using the Library supplied with PTW (because you do not have the original CAPTOR for DOS Libraries), and the unfound device is a Westinghouse, it probably


8/16/2006

results from a spelling revision which changed “Westnhouse” (in the DOS version) to “Westinghouse” (in the Windows version). If this is the case, relinking the device will be easy. Once Import finishes, you can open the CAPTOR TCC Drawing, click the Library button, and find the Westinghouse device in the Library. Using the newly-found data, CAPTOR for Windows will plot the curve.

• Ground Fault and Motor Overload devices will not be found, regardless of whether you have the original CAPTOR for DOS Libraries. This is because the format for these devices is much more sophisticated in CAPTOR for Windows, and insufficient data in the DOS Libraries prevents them from being imported. Therefore, you will have to remodel the Ground Fault or Motor Overload device.

Appenix A



A.5 Running Import for CAPTOR Libraries Unlike CAPTOR for DOS, which uses multiple Library files for its different protective device types, CAPTOR for Windows combines all its protective devices into a single Library file. This streamlines the PTW program, making Library usage easier.

Because the format has been changed, however, a separate program must be used to convert the set of CAPTOR for DOS Libraries into the single CAPTOR for Windows Library. The DOS CAPTOR Library Import program will accomplish this procedure for you. Once the Libraries have been converted, you may use the Import program to convert your CAPTOR for DOS Projects into CAPTOR for Windows Projects. (If you do not have the original CAPTOR for DOS Libraries, you cannot use DOS CAPTOR Library Import. Return to Section A.4, “Running Import for CAPTOR Projects.”) You only need to run the DOS CAPTOR Library Import program once for each set of CAPTOR for DOS Libraries, even if that set of Libraries is used by many different CAPTOR for DOS Projects.

Note that DOS CAPTOR Library Import actually creates a new PTW Library using the DOS files; it does not change the format of the DOS files directly. This means that all your DOS Library Files are left intact and unchanged in their original locations.

Before running DOS CAPTOR Library Import, you should be aware of the following:

• The secondary current for relays will be set to PTW’s preset values (5.0 Amperes for standard relays, 1.0 Amperes for IEC relays) by DOS CAPTOR Library Import. If you had different values set, after DOS CAPTOR Library Import finishes you can edit the Library to change these secondary current values back to their original values.

• Ground Fault devices will not be imported.

• Adjustable and non-adjustable molded case circuit breakers will both be imported as thermal magnetic molded case circuit breakers.

• Fuses with a device voltage less than or equal to 600 V will be imported as low-voltage fuses.

• Fuses with a device voltage greater than 600 V will be imported as high-voltage fuses.

• Generalized relay by equation devices in CAPTOR for DOS will be imported as electro-mechanical relays.

• Overcurrent/instantaneous relays set to U.S. type (in the DOS Library) will be imported as electro-mechanical relays, whereas overcurrent/instantaneous relays set to European type will be imported as IEC-type relays.

• Generalized relay by segment devices will be imported as electronic relays.

• Each unconnected curve in a specialty device will import as a separate segment. (CAPTOR for DOS allowed you to model multiple unconnected curves for a single


8/16/2006

specialty device, whereas PTW will connect every point given for a specialty device segment; therefore, each curve in a specialty device imports as a distinct segment.)

DOS CAPTOR Library Import allows you to convert existing CAPTOR for DOS Protective Device Libraries into the CAPTOR for PTW format. Once completed, you may access the Protective Device Libraries using CAPTOR for PTW.

To start DOS CAPTOR Library Import

1. (Be sure that PTW is not running). Click Start>Programs>Power*Tools for Windows>DOS Captor Library Import.

2. Use the Browse button to locate the CAPTOR for DOS Protective Device Library that you want to import (this will have the extension *.lb).

3. Select those check boxes next to the devices you want to import. If you want to import the entire Library, choose the All button. (Ground Fault devices cannot be imported because there is insufficient data in the DOS format.)


5. Select a location and file name for the CAPTOR for PTW Protective Device Library that will be created (this will have the extension *.lib). You may have multiple Libraries within a single folder.

6. Click the OK button. The Library will now be imported.

7. Repeat step 3 for each Library that you want to import.

Once you have imported the Protective Device Libraries, you may copy devices from one Protective Device Library to another to consolidate them in one Library.

Select the DOS Library that you will import.

Click the All button to select all devices for import, or select specific devices to import.

Appenix A



You may change a new or existing Project’s references to use the newly-imported Library. See “Changing Library References” in the “Libraries” chapter for more information.


Appenix B

Trouble-Shooting Guide

This section describes error messages, trouble-shooting procedures and frequently asked questions.

IN

TH

IS

CH

AP

TE

R

Appenix B 1 Trouble-Shooting Guide 1

A.1 General Protection Fault on Start-up 2 A.2 General Protection Fault while running PTW Program 2 A.3 Important Project Files 3

UG 2 User’s Guide

8/16/2006

A.1 General Protection Fault on Start-up Symptom: General Protection Fault or Dr. Watson Error on Start-up. The PTW program terminates with a system level error before reaching the main PTW application window.

Solution: Delete the PTW32 Registry Entry using the RegDel.EXE utility program.

Background: During start-up, PTW reads the Registry entries to recover the state of PTW when it was last closed. The state includes the tool bar positions, default symbol assignments, project windows open and a variety of other settings. If the Registry settings become corrupted or stores invalid startup information, it can cause PTW to fail during start-up. The error is generally either a General Protection Fault or a Dr. Watson error, depending on the operating system in use.

A.2 General Protection Fault while running PTW Program Symptom: A general protection fault or Dr. Watson error occurs while performing a combination of operations in the PTW program. A general protection fault is an abnormal unexpected program termination.

Solution: Help Isolate the cause through an organized process of elimination. The following background discussion provides a general procedure:

Background: A general protection fault can be caused by any of the following conditions:

• Corrupted Project File

• Corrupted Program File Installation

• Hardware or Memory Problems

• Corrupted Operating System Files, or Software Virus

• Un-handled Data Error Passed to PTW Program

Use the following procedures to identify and correct the problem:

• Corrupted Project File: Make sure that the error can be re-produced consistently. Try the same procedure in a different project file and if the error occurs in both projects it's probably not a corrupted project. Another common symptom is If the error occurs in one project only, close the project and run the Project>Database Utility program:

Trouble-Shooting UG 3


If the error persists after running the Database Utility program on the corrupted project file, forward the project file to SKM for review.

• Corrupted Program File Installation: This should be a repeatable problem. If the problem occurs in multiple projects, re-install the PTW Program Files.

• Hardware or Memory Problems: Install the PTW program on a different computer and try to re-create the problem

• Corrupted Operating System Files or Software Virus is similar to Hardware and Memory Problems. The first step is to see if the problem occurs on other computers. If not, run virus detection software and re-install the Operating System files.

• Un-handled Data Error Passed to PTW Program. These types of errors should be reproduceable. Once you can consistently reproduced the problem, report the error to SKM and provide a list of steps required to produce the error. If necessary, forward the project file to SKM for review. We strive to prevent data errors through extensive error checking, however we're only human and sometimes miss some.

A.3 Important Project Files The PTW Projects are made up of many different files and it is important to know the importance of each file for backup, trouble-shooting, and for sharing files with others. A list of the primary files follows:

Project Files - Stored together in a separate folder for each project

Objects.DAT (project data - must stay with matching Objects.IDX index file)

Objects.IDX (project index file - must stay with matching Objects.DAT file)

Poet.CFG (database configuration file)

Yourproject.PRJ (stores project preferences and options)

Youroneline.DRW (one-line diagram files for specific project)

There are several other project output files such as reports and plots, however they can be re-generated with the primary project files listed above.

Miscellaneous Files - Stored in the folder specified for Miscellaneous Files

Compedit.FMT (stores datablock formats used in Component Editor and TCC's)

DRAW.FMT (stores datablock formats used in One-line diagrams)

PTWforms.FRM (stores form definitions used in Form-Print)

UG 4 User’s Guide

8/16/2006

Query.ARC (stores query definitions)

Symbols.UGS (stores one-line symbols)

Library Files - Stored in the folder specified for Libraries

Ansi/Iec.DLD - ANSI/IEC Demand Load Analysis Library

Ansi/Iec.MCC - ANSI/IEC Motor Control Center Library

Ansi/Iec.XFR - ANSI/IEC Transformer Library

Ansi/Iec.CBL - ANSI/IEC Cable Library

Ptw.LIB - All other PTW libraries including Protective Devices, Transient Motor Starting models, Transient Stability models, Harmonic Source Spectrum models, and Transmission Line Configuration models.

The library files can be renamed provided the extensions (.DLD, .MCC, etc.) are not changed. It is recommended that you change the library names so you can distinguish them from the default libraries supplied with PTW in future upgrades.

A.4 Invalid Connections Symptoms: An "Invalid Connection" error message appears when trying to connect two components on the One-line.

Solution: Add a bus or impedance device as appropriate. Refer to the following background discussion.

Background: Unlike a CAD program, PTW is building an electrical model. The model forms an impedance network for system calculations. The industry terminology uses the term "bus" to signify a specific location in the power system and "branch" to signify impedance between two buses. The connection rules in PTW follow these basic power system impedance network assumptions. Therefore you must place a bus between two impedance components and must have one impedance component between two buses. You can hide buses and replace impedance components with straight-line symbols for aesthetic purposes but must follow the impedance network rules when building the one-line.

A.5 Utility Fault Contribution Error Symptoms: "The calculated zero sequence impedance is negative" error message appears when trying to save the Utility fault contribution.

Solution: Divide the zero sequence impedance MVA entry by 3.

Background: PTW uses the three-phase fault data and the single-line-to-ground fault data to calculate the positive, negative- and zero-sequence impedances from the following per unit equations:

Trouble-Shooting UG 5


Z Z

Z 1.0I

I3 1.0

Z Z Z

Z 3I

Z Z

1 2

1f

f1 2 0

0f

1 2

3

slg

slg

=

=

=×

+ +

= − −

Φ

b gb g

Utilities often report available single-line-to-ground fault duties on an equivalent three-phase rating apparent power basis, using the equation:

kVA 3 I kVfslg= × ×

However, the actual apparent power of a single-line-to-ground fault is:

kVA = I kV3fslg

×

where

kV line-to-line voltage.

You cannot use the three-phase equivalent rating of a single-line-to-ground short circuit contribution. If you do, PTW may attempt to calculate the zero-sequence impedance as a negative value. The actual apparent power to be entered into PTW is the utility equivalent single-line-to-ground duty divided by 3. Enter the single-line-to-ground fault current X/R ratio, not the zero sequence impedance X/R ratio.

Index

A Accessory Groups, 8-15 Advanced Queries, 6-13 Attributes

about, 1-5 AutoCAD, 1-11

B Boolean Operators. See Queries Bus, 4-13 Bus-Node, 3-20

C Cable, 4-14 CAD, 1-11 Carson's Solution, 8-20 Circular Mils, 8-12 Cloning components, 4-7 Comparative Operators, 6-10 Component Editor

opening, 4-2 Component Editor

adding components, 4-6 cloning components, 4-7 component set option buttons, 4-4 component subviews box, 4-4 components box, 4-3 connecting components, 4-7 datablock subview, 4-12 destroying components, 4-9, 4-10 entering data, 4-9 introduction, 1-4 navigating, 4-5 query results in, 4-10, 6-5 renaming components, 4-8

Component Sets queries

adding, 6-9 Components

about, 1-5 searching. See Queries

Condition Lines, 6-8 Connections - Invalid, 4 Connections-Automatic, 3-21 Creating Datablock Formats, 5-8 Crystal Reports, 7-9

about, 1-10

D Datablock Report command, 5-11 Datablocks

about, 1-8, 5-2 copying datablock formats, 5-11 creating datablock formats, 5-8 editing datablock formats, 5-10 in the Component Editor, 5-7 on a One-Line Diagram, 3-31 parts of, 5-4 probe, 5-6 snap, 3-28 viewing, 5-6

Derating Factors, 8-12 DOS Projects, Importing, 2 DXF files, 3-39

E Exporting

One-Line Diagrams, 1-11

F Fault Contribution Error, 4 Filters, 4-19 Finding Components. See Queries Forms

creating, 9-8 introduction to, 9-6 previewing before printing, 9-18 printing with, 9-17

G General Protection Fault - Running, 2 General Protection Fault - Startup, 2 Generator, 4-16

H Help, on-line, 1-12

I In Service, 4-9 In Service Components, 3-23 Induction Motor, 4-17 Installing PTW, 1-2

I-2 User’s Guide

8/16/2006

L Libraries

about, 1-6, 8-2 copy and rename, 8-5 creating, 8-4 opening, 8-4 references

changing in the middle of a project, 8-7 references:, 8-6 types, 8-3

Load Schedule, 4-20 Reports, 4-28

N Non-Motor Load, 4-17

O One-Line Diagram

Datablocks:, 5-6 One-Line Diagram Objects

moving, 3-28 snap, 3-28

One-Line Diagrams adding existing components, 3-15 aligning objects, 3-30 and the Project Database, 3-3 building the project, 3-14 cloning components, 3-17 components vs. symbols, 3-3 connecting and disconnecting components, 3-18 copy/paste components to new One-line, 3-17 creating, 3-6 datablocks, 3-31 destroying components, 3-23 distributing objects, 3-30 existing components, 3-4 Expand command, 3-16 exporting, 1-11 exporting to WMF and DXF, 3-39 in service and out of service, 3-23 interface, 3-6 introduction, 1-3 mouse pointers, 3-9 multiple, 3-5 navigating, 3-10 new components, 3-4 objects, 3-7 opening, 3-6 page guides, 9-5 print layout, 9-4 print preview, 9-3 printing, 9-3 probe, 3-33 query results in, 6-6 removing symbols, 3-23 renaming components, 3-22 scrolling, 3-10

selecting objects, 3-24 selecting objects using a query, 3-26 sizing bus symbols, 3-28 textblocks, 3-36 zooming, 3-11

On-Line Help, 1-12 Operators, 6-10 Organizing Queries, 6-6 Out of Service Components, 3-23 Out of Service, 4-9

P Page Guides, 9-5 Pentium Warning, 2-4 Pi Impedance, 4-15 PIXymbolsExtended Font, 7-8 Print Layout, 9-4 Print Preview, 9-3 Printing

about, 9-2 Printing

One-Line Diagram, 9-3 Project Database

and One-Line Diagrams, 3-3 Project Files - Important, 3 Project Options, 2-4 Projects

backing up, 2-11, 2-12, 2-14 closing, 2-10 copying, 2-9 creating, 2-7 deleting, 2-10 exporting, 2-12 opening, 2-8 statistics, 2-11 working with, 2-7

Projects Introduction, 1-2

Protective Device, 4-18

Q Queries

about, 1-5, 6-2 adding, 6-11 advanced, 6-13

adding boolean operators, 6-13 attributes, 6-9 before running, 6-2 component sets, 6-9 condition lines, 6-8 copying, 6-7 customizing, 6-7 deleting, 6-7 operators, 6-10 organizing, 6-6 results in Component Editor, 6-5 results in One-Line Diagrams, 6-6 running, 6-3

from a One-Line Diagram, 3-26

Index I-3


from the Component Editor, 4-10 Query Prompt, 6-10

R Renaming Components, 4-8 Reports

about, 1-7, 7-2 creating, 7-2 exporting, 1-11 go to line, 7-4 interface, 7-3 opening, 7-3 opening in other applications, 7-8 PIXymbolsExtended Font, 7-8 searching for text, 7-6

S Searching Components. See Queries Snap Feature, 3-28 Starting PTW, 2-2 Status Bar, 2-23

Studies about, 1-7

Synchronous Motor, 4-18

T Textblocks, 3-36 Three-Winding Transformer, 4-15 Toolbars, 2-23 Transmission Line, 4-15 Transmission Line Model, 8-17, 8-18, 8-19, 8-21, 8-22 Two-Winding Transformer, 4-14

U Utility, 4-16

W Windows Metafiles, 3-39 WMF, 3-39

I-4 User’s Guide

8/16/2006
