EERWAY

EE Raceway Modeling Reference Guide Document Number Version Date Pages DPDS3-PB-200005B PDS 7.2 February 2003 1-594 DPDS3-PB-200005C PDS 7.2 February 2003 595-643

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, orimplied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties.

The information and the software discussed in this document are subject to change without notice and should not be consideredcommitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for any error that may appear in this document.

The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of thislicense.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or itsaffiliated companies.

Trademarks

Intergraph, and RIS are registered trademarks of Intergraph Corporation. ACE, DBACCESS, DIALOG, DMRS, EE CMS, EE Power, EERaceway, EE Schematic, EE Wiring Diagram, IGDS, and SEE are trademarks of Intergraph Corporation. All other brands and productnames are trademarks of their respective owners.

Copyright

1984-2003 Intergraph CorporationAll Rights Reserved

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; containsconfidential and proprietary information of Intergraph and/or third parties which is protected by copyright and trade secret law and may notbe provided or otherwise made available without proper authorization.

RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of The Rights in TechnicalData and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of Commercial ComputerSoftware — Restricted Rights at 48 CFR 52.227-19, as applicable.

Unpublished — rights reserved under the copyright laws of the United States.

Intergraph Corporation

Huntsville, Alabama 35894-0001

Table of Contents________________

Table of Contents

If You Need Assistance ........................................................................................................ 17Intergraph Directory ............................................................................................................. 17

Preface ................................................................................................................................................. 19

Document Purpose ................................................................................................................ 19Document Prerequisites / Audience ...................................................................................... 19Related Documents/Products ................................................................................................ 19About this Document ............................................................................................................ 19Ordering Information ............................................................................................................ 20Additional Information ......................................................................................................... 20

General Conventions .................................................................................................................... 21

Keyboard Conventions ......................................................................................................... 22Terminology ......................................................................................................................... 23

1. Introduction .................................................................................................................................. 25

About the Reference Guide .......................................................................................................... 25Basic Workstation Skills .............................................................................................................. 26

2. Installation Instructions ................................................................................................................ 27

Assumptions ......................................................................................................................... 27Overview ............................................................................................................................... 27

Upgrading the Workstation .......................................................................................................... 28Installation Procedure .................................................................................................................. 29Databases ..................................................................................................................................... 33

3. Electrical Engineer (EE) Environment ......................................................................................... 35

Using the Electrical Engineer Menus ........................................................................................... 36Create ........................................................................................................................................... 39Enter ............................................................................................................................................. 40Product Menu ............................................................................................................................... 42Copy ............................................................................................................................................. 43Delete ........................................................................................................................................... 44Archive ......................................................................................................................................... 46Restore ......................................................................................................................................... 48Database Utilities ......................................................................................................................... 50

RIS schema utilities .............................................................................................................. 51Update Project Schema ......................................................................................................... 52

3

________________

Update Reference Schema .................................................................................................... 55

4. Electrical Engineer (EE) Raceway Environment ......................................................................... 59

Create ........................................................................................................................................... 61Design .......................................................................................................................................... 63Process ......................................................................................................................................... 64

Overview ............................................................................................................................... 64Operating Modes .................................................................................................................. 65

EDEN ........................................................................................................................................... 67

Operating Modes .................................................................................................................. 68Entering Time in Batch Mode .............................................................................................. 69

Report ........................................................................................................................................... 70

Overview ............................................................................................................................... 70A Special Note for Bill of Materials by Volume .................................................................. 72

Rule Checks ................................................................................................................................. 73

Overview ............................................................................................................................... 73

Utilities ......................................................................................................................................... 75

Copy ...................................................................................................................................... 78Delete .................................................................................................................................... 79Undelete ................................................................................................................................ 80Purge ..................................................................................................................................... 81Rename ................................................................................................................................. 82Send ...................................................................................................................................... 83Receive ................................................................................................................................. 84Archive ................................................................................................................................. 86Restore .................................................................................................................................. 87Output ................................................................................................................................... 89

5. EE Graphics Interface Elements .................................................................................................. 91

Start-up Sequence ........................................................................................................................ 92Screen Display ............................................................................................................................. 93EERWAY Command Menu Bar .................................................................................................. 96Palettes in the EE Raceway Graphics Environment .................................................................... 97Identifying Elements .................................................................................................................... 103Working Units and Precision Key-ins ......................................................................................... 104

Working Units in MU:SU:PU .............................................................................................. 104Precision Key-ins .................................................................................................................. 105

4

Table of Contents________________ 6. Workflow and Procedures ............................................................................................................ 107

The Drawing Process ................................................................................................................... 108

System Manager Setup ......................................................................................................... 109Drawing Setup ...................................................................................................................... 110Define Systems and Set Active Systems .............................................................................. 110Define One-Line Type and Set Active One-Line Type ........................................................ 110Set Symbology ...................................................................................................................... 110Set Active Parameters ........................................................................................................... 111Set Propagation Parameters .................................................................................................. 111Place One-Line ..................................................................................................................... 112Propagation ........................................................................................................................... 113Sketch and Eden Modes ........................................................................................................ 113Manual Fitting Placement ..................................................................................................... 113Seamless Tubing Representations ........................................................................................ 114

Databases ..................................................................................................................................... 115

Reference Database ............................................................................................................... 115Project Database ................................................................................................................... 115

Reports ......................................................................................................................................... 117Interference Detection .................................................................................................................. 118

7. Precision Input Form .................................................................................................................... 119

View ...................................................................................................................................... 120Maximize/Minimize ............................................................................................................. 120Cancel ................................................................................................................................... 120Reject .................................................................................................................................... 120Accept ................................................................................................................................... 120Move/Move To Toggle ......................................................................................................... 121Display Fields ....................................................................................................................... 121Active Point Coordinates Display ........................................................................................ 121Justification Point ................................................................................................................. 122Height and Width .................................................................................................................. 122

Construct Point ............................................................................................................................ 123Midpoint/Any Point on Segment ................................................................................................. 123Extend/Reduce Run ..................................................................................................................... 125Distance and Direction ................................................................................................................. 126Runtime Setup .............................................................................................................................. 127

8. Design Commands ....................................................................................................................... 129

Commands ............................................................................................................................ 129

Using the Design Commands ....................................................................................................... 131

5

________________

When to Use These Commands ............................................................................................ 131Before Using These Commands ........................................................................................... 131Group Workflow ................................................................................................................... 131Operating Information .......................................................................................................... 131

Place One-Line ............................................................................................................................. 132

Steps ...................................................................................................................................... 134

Route Around Vessel ................................................................................................................... 135

Steps ...................................................................................................................................... 136

Insert RCP .................................................................................................................................... 138

Steps ...................................................................................................................................... 138

Rotate Cross Section .................................................................................................................... 140

Steps ...................................................................................................................................... 140

Place Drop Point .......................................................................................................................... 142

Steps ...................................................................................................................................... 142

Place Equipment Pointer .............................................................................................................. 144

Steps ...................................................................................................................................... 144

Define Active Point ...................................................................................................................... 145

Steps ...................................................................................................................................... 145

Set Active Parameters .................................................................................................................. 146

Steps ...................................................................................................................................... 146

Place Manual Fitting .................................................................................................................... 147Conduit Sizing ............................................................................................................................. 155

Field Descriptions ........................................................................................... 156

Insert One-Line Vertex ................................................................................................................ 160Place Field Routed Raceway ....................................................................................................... 161Define Duct Cross Section ........................................................................................................... 164Place Stub Up ............................................................................................................................... 167

Steps ................................................................................................................ 169

6

Table of Contents________________ 9. Modify Commands ...................................................................................................................... 173

Using the Modify Commands ...................................................................................................... 174


Modify Element Commands ........................................................................................................ 175

Using the Modify Element Commands ................................................................................ 177When to Use These Commands ............................................................................................ 177Before Using These Commands ........................................................................................... 177Group Workflow ................................................................................................................... 177Operating Information .......................................................................................................... 177Annotate Element ................................................................................................................. 178Field Descriptions ................................................................................................................. 179Copy Element ....................................................................................................................... 184

Steps ................................................................................................................ 185

Move Element ....................................................................................................................... 186

Steps ................................................................................................................ 187

Clone Element ...................................................................................................................... 188

Steps ................................................................................................................ 189

Move One-Line Segment ...................................................................................................... 190

Steps ................................................................................................................ 191

Move One-Line Vertex ......................................................................................................... 192Propagate Element ................................................................................................................ 194Edit/Insert Manual Fitting ..................................................................................................... 198Modify One-Line .................................................................................................................. 204Place Fitting by Rule ............................................................................................................ 207Combine Coincident RCPs ................................................................................................... 209Delete Duplicate One-Lines .................................................................................................. 211Delete Element ...................................................................................................................... 212Remove RCP ........................................................................................................................ 214Delete Fitting ........................................................................................................................ 216Remove One-Line Vertex ..................................................................................................... 217Minimize Joints .................................................................................................................... 219

Steps ................................................................................................................ 220

7

________________

Change System Parameters ................................................................................................... 221

Modify Group Commands ........................................................................................................... 223

Topics ................................................................................................................................... 223Using the Modify Group Commands ................................................................................... 225When to Use These Commands ............................................................................................ 225Before Using These Commands ........................................................................................... 225Group Workflow ................................................................................................................... 225Operating Information .......................................................................................................... 225Define Group ........................................................................................................................ 226

Steps ................................................................................................................ 230

Copy Element by Group ....................................................................................................... 231Annotate Element by Group ................................................................................................. 233Clone Element by Group ...................................................................................................... 239Propagate by Group .............................................................................................................. 241Place Fitting by Rule by Group ............................................................................................ 243

Steps ................................................................................................................ 244

Add Systems Group .............................................................................................................. 245Replace Systems by Group ................................................................................................... 246Minimize Joints by Group .................................................................................................... 248Delete Element by Group ..................................................................................................... 251

10. Setup Commands ....................................................................................................................... 253

Using the Setup Commands ......................................................................................................... 255


Set Raceway Defaults .................................................................................................................. 256Define System .............................................................................................................................. 258Define One-Line Type ................................................................................................................. 260Set Symbology Control ................................................................................................................ 262

Steps ................................................................................................................ 263

Symbology Control ...................................................................................................................... 264Set Text Defaults .......................................................................................................................... 266Set Conduit Sizing Attributes ...................................................................................................... 268Create Cell Commands ................................................................................................................ 269

Using the Create Cell Commands ......................................................................................... 270When to Use These Commands ............................................................................................ 270

8


Before Using These Commands ........................................................................................... 270Group Workflow ................................................................................................................... 270Operating Information .......................................................................................................... 270Create Model Cell ................................................................................................................. 271Create Equipment Pointer Cell ............................................................................................. 274Create Drop Point Cell .......................................................................................................... 277

Model Commands ........................................................................................................................ 280

Using the Model Commands ................................................................................................ 281When to Use These Commands ............................................................................................ 281Before Using These Commands ........................................................................................... 281Group Workflow ................................................................................................................... 281Operating Information .......................................................................................................... 281Lock Model ........................................................................................................................... 282Move Model Annotation ....................................................................................................... 283Unlock Model ....................................................................................................................... 284Annotate Model .................................................................................................................... 285

11. Runtime Setup Commands ......................................................................................................... 287

Using the Runtime Setup Commands .......................................................................................... 288


Set Active One-Line Type Parameters ......................................................................................... 289Set Active One-Line Type ........................................................................................................... 294Set Active System ........................................................................................................................ 295Propagation Setup ........................................................................................................................ 297Set Active Levels ......................................................................................................................... 299Display Element Information ....................................................................................................... 301

12. Utilities Commands .................................................................................................................... 303

Using the Utilities Commands ..................................................................................................... 305


Toggle Construction Display On/Off ........................................................................................... 306Highlight Element by Sector/Word ............................................................................................. 307

Highlight Sector/Word With Filename ................................................................................. 307

9

________________

Highlight Element by ASID ID ................................................................................................... 309

Highlight ASID ID With Filename ....................................................................................... 309

Highlight Element by Link .......................................................................................................... 312

Highlight Link With Filename .............................................................................................. 312

Highlight Propagation Errors ....................................................................................................... 314Display Sector/Word Value ......................................................................................................... 315Display Element Type and ASID ID ........................................................................................... 316Display Link ................................................................................................................................. 317Display System and One-Line Type ............................................................................................ 318Active Coordinate System ........................................................................................................... 320

13. Database Commands .................................................................................................................. 321

Using the Database Commands ................................................................................................... 322


Load Database .............................................................................................................................. 323

Steps ................................................................................................................ 325

Report ........................................................................................................................................... 326

A Special Note for Bill of Materials by Volume .................................................................. 327

Rule Checks ................................................................................................................................. 329

14. Raceway Processes ..................................................................................................................... 331

Load Database .............................................................................................................................. 332

Batch File Option ............................................................................................ 335

Unload Design ............................................................................................................................. 336Unload Sheet ................................................................................................................................ 338Cleanup Database ......................................................................................................................... 340Create Interference Envelope (default name) .............................................................................. 342Create Interference Envelope (given name) ................................................................................. 344

15. Eden Processes ........................................................................................................................... 347

Compile EDEN Symbol ............................................................................................................... 349Delete EDEN Symbol .................................................................................................................. 351

10


Steps ................................................................................................................ 352

List EDEN Symbol Library ......................................................................................................... 353

Steps ................................................................................................................ 354

List EDEN User Functions .......................................................................................................... 355Merge EDEN Symbol Libraries ................................................................................................... 357Compress EDEN Symbol Library ............................................................................................... 359Extract EDEN Symbol From Library .......................................................................................... 361

Steps ................................................................................................................ 362

Extract EDEN User Function From Library ................................................................................ 363Edit EDEN Symbol File .............................................................................................................. 366

Steps ................................................................................................................ 367

16. Integrated Commands ................................................................................................................ 369

Using the Integrated Commands .................................................................................................. 370


16.1 Review PDS Attributes ............................................................................................................ 371

Parameters ............................................................................................................................. 371

16.2 Reference PDS Model .............................................................................................................. 372

Parameters ............................................................................................................................. 372

16.3 Window to Named PDS Item ................................................................................................... 374

Options .................................................................................................................................. 374

16.4 Review PDS Clash ................................................................................................................... 375

Parameters ............................................................................................................................. 375

Appendix A: Error Messages ........................................................................................................... 377

Appendix B: System/Application Manager Information ................................................................. 415

Customizing ................................................................................................................................. 417EE Environment Variables .......................................................................................................... 422

11

________________ Appendix C: EE Databases .............................................................................................................. 425

Relational Interface System (RIS) ............................................................................................... 426Database and RIS Procedures ...................................................................................................... 427

For New Users ...................................................................................................................... 427

Update Schema (create_db) Process ............................................................................................ 428Reference Schema - General Description .................................................................................... 430

Default Attributes ................................................................................................................. 430Keys ...................................................................................................................................... 430Codelists ............................................................................................................................... 432Approval Status Codelist Table ............................................................................................ 432Cardinal Codelist Table ........................................................................................................ 433Drawing Type Codelist Table ............................................................................................... 433Manual Fitting Part Codelist Table ....................................................................................... 433One-Line Type Codelist Table ............................................................................................. 434RCP Type Codelist Table ..................................................................................................... 435System Codelist Table .......................................................................................................... 435Three-Line Type Codelist Table ........................................................................................... 436Three_Line Subtype Codelist Table ..................................................................................... 437Three-Line Qualifier Codelist Table ..................................................................................... 437Units Codelist Table ............................................................................................................. 438Vendor Codelist Table .......................................................................................................... 438Wire/Cable Code Codelist Table .......................................................................................... 439Wire/Cable Configuration Codelist Table ............................................................................ 440Wire/Cable Size Codelist Table ............................................................................................ 440Wire/Cable Color Codelist Table ......................................................................................... 441Wire/Cable Voltage Codelist Table ...................................................................................... 443Wire/Cable Insulation Type Codelist Table ......................................................................... 444Yes-No Codelist Table ......................................................................................................... 445Fitting Environment Rules .................................................................................................... 446

Project Schema - General Description ......................................................................................... 448Updating Schemas ....................................................................................................................... 449

Updating a Project Schema ................................................................................................... 449Updating Reference Schemas ............................................................................................... 449Schema Names ...................................................................................................................... 450

Modifying the Reference Schema ................................................................................................ 451EE Raceway Reference Database Schema Description ............................................................... 454

approv_status ........................................................................................................................ 454away_part .............................................................................................................................. 454away_spec ............................................................................................................................. 455cardinal ................................................................................................................................. 456cond_body ............................................................................................................................. 457cond_fill_calc ....................................................................................................................... 458

12


cond_part .............................................................................................................................. 459cond_spec ............................................................................................................................. 460drawing ................................................................................................................................. 461drawing_type ........................................................................................................................ 461drop_point ............................................................................................................................. 462duct_spec .............................................................................................................................. 462ee_cond_x_area .................................................................................................................... 463ee_graphic_only .................................................................................................................... 463ee_pcbl_code ........................................................................................................................ 464ee_pcbl_color ........................................................................................................................ 464ee_pcbl_config ...................................................................................................................... 464ee_pcbl_insul ........................................................................................................................ 465ee_pcbl_size .......................................................................................................................... 465ee_pcbl_volt .......................................................................................................................... 465ee_pseudo_cable ................................................................................................................... 466ee_system .............................................................................................................................. 466ee_units ................................................................................................................................. 467ee_unique .............................................................................................................................. 467ee_yes_no ............................................................................................................................. 467envelope ................................................................................................................................ 468light_fixture .......................................................................................................................... 469manual_part .......................................................................................................................... 471mscatalog .............................................................................................................................. 471mscodelist ............................................................................................................................. 472mscolumns ............................................................................................................................ 473ol_type .................................................................................................................................. 474one_line ................................................................................................................................. 475panel ...................................................................................................................................... 475project ................................................................................................................................... 476pullbox .................................................................................................................................. 477rcp ......................................................................................................................................... 478rcp_type ................................................................................................................................ 478tl_fit_env ............................................................................................................................... 479tl_qual ................................................................................................................................... 480tl_subtype .............................................................................................................................. 480tl_type ................................................................................................................................... 480to_equip ................................................................................................................................ 481to_support ............................................................................................................................. 481tray_part ................................................................................................................................ 482tray_spec ............................................................................................................................... 483vendor ................................................................................................................................... 484wway_part ............................................................................................................................. 484wway_spec ............................................................................................................................ 485

EE Raceway Project Database Schema Description .................................................................... 487

cabsch_spec .......................................................................................................................... 487cndsch_spec .......................................................................................................................... 489drawing ................................................................................................................................. 491drop_point ............................................................................................................................. 491

13

________________

duct_fill ................................................................................................................................. 492ee_pseudo_cable ................................................................................................................... 492ee_system .............................................................................................................................. 493envelope ................................................................................................................................ 493fitting ..................................................................................................................................... 494fit_to_sys ............................................................................................................................... 495mscatalog .............................................................................................................................. 496mscolumns ............................................................................................................................ 497ol_to_sys ............................................................................................................................... 498one_line ................................................................................................................................. 498panel ...................................................................................................................................... 500project ................................................................................................................................... 500panel_to_drw ........................................................................................................................ 501rcp ......................................................................................................................................... 501rcp_to_drw ............................................................................................................................ 502rcp_to_sys ............................................................................................................................. 502straight .................................................................................................................................. 503str_to_sys .............................................................................................................................. 504sys_to_drw ............................................................................................................................ 505to_support ............................................................................................................................. 505

Appendix D: Specification ............................................................................................................... 507

Preparing the Specifications ........................................................................................................ 507

Sample .unl Files .................................................................................................... 509

Update Reference Schema ........................................................................................................... 510

Available Fittings .................................................................................................................. 512

Appendix E: Eden Symbol Generation ............................................................................................ 513

Symbol Processor File .......................................................................................................... 513

Appendix F: EE File Structure ......................................................................................................... 519

EE Nucleus File Structure ............................................................................................................ 520EE Raceway File Structure .......................................................................................................... 524

Appendix G: Customizing Environment Files ................................................................................. 531

eden.dat ........................................................................................................................................ 531process.dat .................................................................................................................................... 533report.dat ...................................................................................................................................... 534rule_chk.dat .................................................................................................................................. 535print.dat ........................................................................................................................................ 536manager.dat .................................................................................................................................. 537

14

Table of Contents________________ Appendix H: alias.cmd file .............................................................................................................. 539

Appendix I: rway.cmd ...................................................................................................................... 543

Appendix J: Reports ......................................................................................................................... 545

RIS Report Processing .......................................................................................................... 545

Project Drawing List (drwlst) ...................................................................................................... 547

Information Output: .............................................................................................................. 547Sorted by (Highest to lowest priority) .................................................................................. 547Associated Software/Files .................................................................................................... 547

Material Takeoff Report (mto_rpt) .............................................................................................. 548

Information Output: .............................................................................................................. 548Associated Software/Files .................................................................................................... 548

Raceway Bill of Materials Report (rway_bom) ........................................................................... 549


Raceway Bill of Materials by Volume Report (rway_bom_vol) ................................................. 550

A Special Note for Bill of Materials by Volume .................................................................. 550Information Output: .............................................................................................................. 551Associated Software/Files .................................................................................................... 551

Raceway Blank Part IDs (blank_ids) ........................................................................................... 552


Appendix K: RIS Schema Manager ................................................................................................. 553

Schema Information Form ........................................................................................................... 554Create Schema Form .................................................................................................................... 555Drop Schema Form ...................................................................................................................... 556Alter Schema Form ...................................................................................................................... 556Data Definition Form ................................................................................................................... 557

Table Information Form ....................................................................................................... 557Create Table Form ................................................................................................................ 558Drop Table Form .................................................................................................................. 559Alter Table Form .................................................................................................................. 559

Schema File Form ........................................................................................................................ 560Set Form ....................................................................................................................................... 560

15

________________ Appendix L: RIS Schema Definition File ........................................................................................ 561

Appendix M: EE Manager ............................................................................................................... 565

In this Appendix ................................................................................................................... 566

Database Edit Functions .............................................................................................................. 567

Appendix N: EE Configure .............................................................................................................. 571

Glossary ............................................................................................................................................... 573

Index .................................................................................................................................................... 581

16


If You Need Assistance

Intergraph Online

Our web site brings you fast, convenient, up-to-the-minute information about Intergraph’sproducts, services, and direction. Our web address is: http://www.intergraph.com.

Support

For the lasest Support Services information, use a World Wide Web browser to connect tohttp://www.intergraph.com/ppo/services/support.asp.

If you are outside of the United States, please call your local Intergraph office. The most up-to-date list of international offices and distributors is available on the web athttp://www.intergraph.com.

Intergraph Directory

The following numbers are only valid in the United States unless otherwise indicated. If youare outside the United States, please call your local Intergraph office.

Intergraph General Information

All countries — 1-256-730-2000

Training Registration

1-800-766-7701 (U.S. Only)

1-256-730-5400 (Outside the U.S.)

Mailing Address

Intergraph Process, Power & Offshore300 Intergraph WayMadison, Alabama 35758U.S.A.

You can also reach us by electronic mail at [email protected].

17

________________

Documentation Contacts

We are constantly working on updates and improvements to the documents and othereducational media. If you have any suggestions on where we can improve the documentationor where you think more information is needed, let us know. You can reach us by:

Mail Intergraph Process, Power & OffshoreDocumentation Manager300 Intergraph WayMadison, AL 35758

18

Preface________________

Preface

Document Purpose

This document is a reference guide for Intergraph Corporation’s Electrical Engineer (EE) Raceway Modeling tm

software package. EE Raceway is a MicroStation graphics based software and lets you design, modify, andmodel electrical raceway systems in a three-dimensional environment.

This document is designed as a reference; it is organized around the structure of the product rather thanpresenting a typical work flow. Use this guide when you need to look up a specific EE Raceway function. It isrecommended that you work through the EE Raceway Modeling Course Guide to learn the basic concepts of theproduct.

Document Prerequisites / Audience

This document is intended for designers who have a working knowledge of the standard interactive graphicssystem. Knowledge of 3-D design systems is helpful but not necessary. Also, you should be familiar with atext editor, such as vi or EMACS.

Related Documents/Products

MicroStation software is required to operate EE Raceway. Information about MicroStation capabilities canbe found in the following documents:

MicroStation Reference Guide

MicroStation User’s Guide

Intergraph Corporation’s Relational Interface System (RIS)TM is required to operate EE Raceway, along with arelational database management system (RDBMS) supported by RIS. Currently, these include Informix,Oracle, and Ingres. Information about RIS capabilities can be found in the following documents:

Relational Interface System (RIS) Reference Manual

Relational Interface System (RIS) Operator Training Guide

About this Document

This document contains front matter, numbered sections, appendices, a glossary, and an index. Because thedesign process is controlled by executing commands, much of this document is devoted to a description of thosecommands, grouped according to function.

19

EE Raceway Modeling Reference Guide - February 2003________________ Section 1 Provides an overview of the product and the document.

Section 2 Provides installation instructions.

Sections 3 & 4 Describe the product environment. This includes information on accessing the productand creating and manipulating product files.

Section 5 Describes the graphics environment for the product. This includes information on thescreen display, menus, forms, and on-line Help.

Section 6 Describes the typical workflow using EE Raceway.

Sections 7-16 Describe the command groups and operating sequences of each command within thecommand groups.

Ordering Information

To order documents:

Within the United States, contact your Customer Engineer or Sales Account Representative.

For international locations, contact the Intergraph subsidiary or distributor from whom you purchasedyour workstation.

Additional Information

The following informational files are delivered with the EE Raceway software in the win32app\ingr\eerwaydirectory.

File Name Contents

readme.txt Describes changes and additions to the product since the last version. Lists the namesand dates of the files in the current release. For a fixes release, the files which have beenmodified are appended to the top of the initial file to provide a history of all changes tothe product. Includes Comments and Trouble Report numbers which describe whatproblems have been fixed. Provides special notices to the customer. Lists any exceptionsmade to the certification.

20

Preface________________

General Conventions

This document contains many visual cues to help you understand the meaning of certainwords or phrases. The use of different fonts for different types of information allows you toscan the document for key concepts or commands. Symbols help abbreviate and identifycommonly used words, phrases, or groups of related information.

Typefaces

Italic Indicates a system response, which is an explanation of what the software isdoing. For example,

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. Commandpaths are shown using an arrow between command names. For example,

Choose File > Open to load a new file.

Sans serif Indicates a system prompt or message, which requires an action be taken bythe user. For example,

Select first segment of alignment

Bold TypewriterIndicates what you should literally type in. For example,

Key in original.dat to load the ASCII file.

Normal TypewriterIndicates an actual file or directory name. For example,

The ASCII report is stored in the layout.rpt file.

21

EE Raceway Modeling Reference Guide - February 2003________________

Symbols

This document uses the following symbols to represent mouse buttons and to identify specialinformation:

<C> Command button<D> Data button (usually the left mouse button)<R> Reset/reject button (usually the right mouse button)<T> Tentative button (usually the center mouse button)

Note — Important supplemental information.

Warning — Critical information that could cause the loss of data if not followed.

Technical tip or information — provides information on what the software isdoing or how it processes information.

Map or path — shows you how to get to a specific command or form.

More information — indicates there is additional or related information.

Need a hint — used with activities and labs, provides a tip or hint for doing theexercises.

Keyboard Conventions

The following list outlines the abbreviations this document uses for keyboard keys anddescribes how to use them in combination. You can make some menu selections through theuse of keyboard accelerators, which map menu selections to key combinations.

ALT Alternate keyCTRL Control keyDEL Delete keyENTER Enter keyESC Escape key

CTRL+z To hold down the Control key and press Z.ESC,k To press the Escape key, then K.

22

Preface________________

Terminology

Click To use a mouse or key combination to pick an item that begins anaction. For example,

Click Apply to save the changes.

Select To mark an item by highlighting it with key combinations or by pickingit with your cursor. Selecting does not initiate an action. Afterselecting an item, you click the action you want to affect the item. Forexample,

Select the file original.dat from the list box, then click Delete toremove it from the directory.

In addition, you would select items to define parameters, such asselecting toggle buttons. This also applies to selecting graphicelements from the design file. For example,

Select the line string to define the graphic template.

Tentative-select To place a tentative point on an existing graphic element in a designfile. If you are using the Windows NT operating system, youtentative-select by pressing a left-button, right-button chord.

Double-click To select and execute a command by clicking the mouse or hand-heldcursor button twice in rapid succession. This term implies that you areclicking the data button (<D>) as part of a menu or dialog box action.For example,

Double-click on the file original.dat to load it into the new surface.

Drag To press and hold the data button (<D>) while moving the mouse orhand-held cursor.

Type To key a character string into a text box.

Key in To type in data and press ENTER to enter the data and execute thedefault action.

In a dialog box, pressing TAB after keying in data willenter the data and move the cursor to the next field.

23


24

1. Intro

du

ction

Introduction________________

1. Introduction

EE Raceway allows you to design, modify, and model electrical raceway systems in a three-dimensional environment.

EE Raceway serves a variety of general purposes, including:

Model building – Uses either a centerline or a three-line component graphic to build athree-dimensional raceway model.

Interference detection – Creates the raceway component interference envelope files forinput to the PDS interference detection task.

Material takeoff – Extracts a list of material required to construct a raceway model.

You can also use EE Raceway models as background drawings for designs created in otherPDS facility design disciplines.

About the Reference Guide

This document, the EE Raceway Modeling Reference Guide, provides descriptions of EERaceway commands and processes. It describes the basic workflow for creating an electricalraceway model. Separate sections outline the preparation and responsibilities for the systemand/or application manager.

25


Basic Workstation Skills

The following basic workstation drafting skills are necessary to use the EE RacewayModeling product. These and other skills can be learned in Microstation Training materials:

Fit view

Window area

Zoom in & out

File design

Compress

Update

Toggle between virtual screens

Turn views on & off

26

2. D

ow

nlo

ad/In

stall

Installation Instructions________________

2. Installation Instructions

This section is an instruction sheet both for initial installation and for updating theworkstation software. The software covered includes baseline and application software,Electrical Engineer (EE) Nucleus software, and EE Raceway Modeling.

Assumptions

The following assumptions have been made in the writing of this section.

You must be familiar with the PDS Loader.

You must be familiar with a text editor, such as vi, EMACS, or Notepad.

If you are updating, all projects have been archived.

Products will be used with any one of the following databases: Standard Engine (SE)Informix, On-line Informix, Oracle, or Ingres. You will need to consult individualdocumentation for these products for detailed information.

Overview

This chapter covers the following topics pertaining to installation/upgrading:

Upgrading the Workstation

Installation Procedure

Databases

27


Upgrading the Workstation

This section describes the loading procedure and details the software you will need to operateyour system. Additionally, it describes the applications software necessary for each of threepossible configurations: the stand-alone workstation, the workstation as server, and theserver-client workstation.

The chapter also outlines the basic workflow for database setup and refers you to appropriatedatabase documentation.

There are several things you must do before loading any software to your workstation. First,you must select the Relational Database Management System (RDBMS) you plan to use anddecide where to locate it on your system. A database can reside locally on each workstation,or remotely on a server. Based on these two setups, you have three options:

— Placing both project and reference databases locally on each workstation.

— Placing both project and reference databases remotely on a server.

— Placing the project database locally on each workstation and the reference databaseremotely on a server.

You must also know before beginning to download products that the order in which you loadthem is very important. For the purposes of this installation, you should load system nucleussoftware, followed by system application software (including EE Nucleus), followed by theEE application products.

28

2. D

ow

nlo

ad/In

stall

Installation Procedure________________

Installation Procedure

This section’s examples assume that you are running the loader delivered with PDS; theloader delivered to stand-alone EE Raceway sites may vary slightly.

Once you know what application software you need, based on your system configuration,follow these steps to download all of the desired products to a Windows NT/2000/XP system.

1. First, connect to the drive on which the distribution software resides. This may be anetworked drive, or it may be on your local system.

2. Double-click on setup.exe to invoke the Intergraph PDS Component Loader.

3. Select Continue to invoke the Intergraph Registration Data form. This form expectsyour user name, company, and serial number (as delivered). Pressing Enter will haveno effect until all fields have been entered, including a valid serial number. TheContinue button will remain inactive until a valid serial number has been keyed in.

4. Select Continue when the button is no longer inactive. This will invoke the productselection form.

29


5. Place an X next to the software you wish to install. This will invoke the installationdata form for each selection. Among other installation options that vary according toproduct, you will be asked to select the Installation Type (local, client, or server).

If local is selected, you must key in the path to the location to which you want toinstall the software. (Note that the icon path changes as you edit the install path.)

If client is selected, you must provide the name of the server which will behosting the session, as well as path to the software on the server, and a local pathto the icon associated with the software.

If server is selected, you must provide the installation path. (Note that the iconpath changes as you edit the install path.)

When all information has been provided, select OK. This will return control to theIntergraph PDS Component Loader. When all software to be loaded has been selected,select Load Components. A message box will appear.

30

2. D

ow

nlo

ad/In

stall

Installation Procedure________________

Select Yes to continue, otherwise select No. A message box will display that tells youwhich products are being loaded.

When the software has successfully loaded, the EENUC (Common) program groupwill be created. This program group contains the EE Manager, EE Configure, EEReadme.txt, EE Help, and EE Nucleus icons.

6. Before executing the software, you must set the environment variables in your ee.cfgfile.

Copy the ee.cfg file found in the win32app/ingr/eenuc directory into another directorynot in the EE or PDS structure. (Your login directory will be fine; you will modify thiscopied file, and it needs to be placed somewhere that it will not be over-written whenyou next update the software.)

7. Double-click on the EE Configure icon to display the Configure EE Environmentform.

8. Use the browse command to locate and open the new ee.cfg file that you copied in theearlier step.

The Reset command should always be used at this point to ensure thatthe environment variables in the display window are those that belong tothe file you just selected, and not to a previously-selected file.

9. Set your user environment variables. Before you can enter the EE environment, youwill need to set at least the following variables:

31

EE Raceway Modeling Reference Guide - February 2003________________ PROJECT_LOCATION

EE_SCHEMA

EE_REFDB

DB_TYPE

Select the variable to be set. This displays the current value and description for thatvariable. To modify the value of that variable, key the desired value into the Valuefield, then select Set.

After all variables have been set properly for your environment, and no more changesare needed, select OK to save the modifications to the ee.cfg file.

This will close the EE Configure utility.

32

2. D

ow

nlo

ad/In

stall

Databases________________

Databases

This section provides an overview of the workflow involved in creating a database andschemas. What follows is a very basic outline, and you should consult your individualRDBMS and RIS documentation for detailed instructions on database setup.

1. Select and install the RDBMS you will use.

— Decide where on the system to locate your databases.

— Refer to the Software Requirements section for information on database locationoptions. Also, see your individual RDBMS documentation for installationinstructions and general information about the product.

2. Download your RDBMS product and the Relational Interface System (RIS) software.

— See the section of this guide entitled Software Requirements for information aboutthe RIS products. Also, see the Relational Interface System (RIS) ReferenceManual.

3. Create new databases/upgrade existing databases.

In order for the EE Raceway project to integrate to PDS there must betwo entries in pdtable_102 corresponding to type_of_rdb_data: 200 forproject schema, and 202 for reference schema. Only after these entriesare in the table will the user be able to update the project and referencedatabase for use with PDS.

— Informix users must create all databases in ANSI mode with this release. See theRIS Reference Manual for information about this process or look in theRISNOTES*.* file in the /usr#/informix/release directory for details aboutcreating databases in ANSI mode.

— For detailed information about creating and updating databases, see Appendix C ofthis reference guide or refer to your individual RDBMS documentation.

4. Create empty RIS schemas.

— You will do this through the EE Environment and the RIS Schema Managerproduct.

— For information about accessing RIS Schema Manager, see the section entitledDatabase Utilities in this reference guide.

— For information about using the RIS Schema Manager product, see the appendixentitled RIS Schema Manager in this reference guide or refer to the RelationalInterface System (RIS) Reference Manual.

33


5. Update your project and reference schemas.

— You will use the Database Utilities option in the EE Environment to accomplishthis.

— See the Database Utilities section in this reference guide. The Database Utilitiessection contains instructions for updating both project and reference schemas.

34

3. EE

E

nviro

nm

ent

Electrical Engineer (EE) Environment________________

3. Electrical Engineer (EE)Environment

Electrical Engineer (EE) products are accessed through the Electrical Engineer (EE) form. Toenter the Electrical Engineer form, click Electrical Raceway Environment on the mainPD_Shell form. When you key in EE, the Project Menu displays:

A project is a group of related electrical drawings and their associated database which youcreate. All EE drawings are organized by project. The Project Menu and other EEEnvironment menus provide easy access to all the product functions.

35


Using the Electrical Engineer Menus

The following areas make up the Electrical Engineer form:

Menu Icons - control the EE form.

Listing Area - lists available project and design files

Input/Output Area - for keying in or displaying data about a project.

Message Area - displays messages from the software.

Options List - a list of options which require additional input or other selections beforeyou can continue. These options can display additional forms or menus.

The basic procedure for using EE menus is first to select an option from the options list, andthen to select, or key in, the necessary information in the input fields in the input/output area.

To turn off an active option, select another option. To edit information you key in to inputfields, use standard EMACS commands.

For some options you will need to know net addresses for the input data boxes.If you do not know the appropriate addresses, check with your systemmanager.

36

3. EE

E

nviro

nm

ent

Using the Electrical Engineer Menus________________

Scrolling Through Listings

The listing area in the EE form provides you access to the projects and design files you willmanage using the available menu options. When a particular option is active, the item youselect from the listing area will display in the appropriate input field.

When listings fill more than one page, you can scroll up and down the list using the scrollbar. The bar above the arrows indicates where you are in the listing. If the bar fills the spaceabove the arrows, all of the available listings are currently displayed.

Icons

There are three icons that can display on EE forms, in any combination:

Confirm (√) accepts the current form settings, and executes the active process.

Reset returns you to the previous form and cancels the current form settings.

Cancel (X) exits the EE application entirely.

The menus will not allow you to perform illegal operations. For example, youare not allowed to print a design file from the Drawing Utility form.

Message Area

Once you have selected and confirmed a option, operating or error messages will display inthe message area at the bottom of the form. You can monitor lengthy processes by reviewingthe message area.

Summary

The best way to familiarize yourself with the environment form and their functions is simplyto practice using the available features. Remember that the basic procedure for executing agiven process is to select a form option, provide the necessary input, and then select Confirm(√).

37


Project Menu Options

The individual Project Menu options are discussed in the following sections:

Create — Creates new EE projects.

Enter — Accesses available EE applications and enters existing EE projects.

— EE Product Menu — Displays (and allows you to select from) those EEapplications that are loaded on the workstation, if there are more than one.

Copy — Copies existing project files to new projects.

Delete — Deletes EE project files.

Archive — Archives EE project files to a floppy disk or network nodes.

Restore — Restores archived EE project files from a floppy disk or network nodes.

Database Utilities — Accesses EE Update Schema utilities and RIS SchemaManager.

38

3. EE

E

nviro

nm

ent

Create________________

Create

This option creates a project in which your design file(s) reside. Multiple files can existwithin a single project, which itself can span multiple products.

Field Descriptions

Project name — This field allows you to enter the project name in uppercase orlowercase letters, though uppercase letters are automatically converted to lowercase.Your project name should have eight or fewer characters. A .prj extension isautomatically appended to the project file name when you select Confirm (√), so youare not required to key in this extension.

Steps

1. Select Create from the Project Menu option list.

The Project name field displays below the scrolling area.

2. Select the Project name field, and key in the new project name.

3. Select Confirm (√) to create the project.

You may also want to create a new project schema when you create aproject. For information about creating a project schema, see RISSchema Manager, page 553 .

— OR —

Select another option to ignore your input and cancel the Create process.

39


Enter

This option accesses a specified project, and is the first step in entering the Electrical Engineerenvironment. You will need to input the names of the project, the project and referenceschemas, and the schema passwords, if they exist.

Field Descriptions

Project name — This field reflects the project name that is selected in the projectlisting area. You may also key project names into this field.

Project schema — This field is automatically updated with the project schema nameassociated with the selected project name. You can override the default selection bykeying in another schema name.

This field may also be defined by the environment variableEE_SCHEMA. Refer to the section about EE Environment Variablesin Appendix B of this document for more information on environmentvariables.

Reference schema — This field is automatically updated with the reference schemaname associated with the selected project name. You can override the default selectionby keying in the desired schema name.

This field may also be defined by the environment variable EE_REFDB.Refer to the section about EE Environment Variables in Appendix Bof this document for more information on environment variables.

Schema password — This field accepts a password for entering the respective schema,if one has been defined. This field may or may not display the password once it hasbeen entered, depending on the setting of the appropriate Password Echo toggle.

40

3. EE

E

nviro

nm

ent

Enter________________ Password Echo — This toggle controls whether or not the password is displayed in therespective password fields.

Steps

1. Select Enter from the Project Menu option list.

The project listing displays.

2. Select a project from the listing area.

— OR —

Select the Project name field, and key in a project name.

The project schema (defaults to project name) and the current reference schema displayautomatically.

You can make modifications to these fields, if needed.

3. Enter schema passwords if they were created for either schema. Identify the appropriateSchema password field, and key in the password. If no password was defined for theschemas, leave these fields blank.

For information about schema passwords, see RIS Schema Manager,page 553 .

4. Select Confirm (√).

The EE Product Menu displays.

If only one EE product exists on your workstation, the environmentbypasses the Product Menu and goes directly into the Drawing Menu.

41


Product Menu

The Product Menu form displays all of the available EE products on your workstation. Inthis example, only the EE Raceway product is on menu, available for use. If only one EEproduct exists on your workstation, then the environment bypasses the Product Menu andgoes directly into the selected product’s Design Menu.

Only the EE products you actually have installed on your workstation will bedisplayed on this menu.

Steps

1. Select the desired EE application from the Product Menu form.

The Design Menu displays. (See the chapter entitled EE Raceway Environment for moreinformation about the Design Menu.)

42

3. EE

E

nviro

nm

ent

Copy________________

Copy

This option copies all the files within an existing project to a new project.

Field Descriptions

Copy project from — Key in the source project name (or select it from the list).

Copy project to — Key in the destination project name; this cannot be the name of aproject that already exists.

Steps

1. Select Copy from the Project Menu option list.

2. Select a project to be copied from the listing area.

— OR —

Select the Copy project from input field, and key in a project to be copied.

3. Select the Copy project to input field, and key in the new project name.

You cannot key in the name of an existing project in the Copy projectto field.

4. Select Confirm (√) to copy the project.

— OR —

Select another option to ignore your input and cancel the Copy process.

43


Delete

This option completely deletes all the files and databases within an existing project.

Field Descriptions

Project name — Key in (or select from the list) the project to be deleted.

Steps

1. Select Delete from the Project Menu option list.

2. Select the project name from the listing area.

— OR —

Select the Project name field, and key in the project name.


If a database exists in the project directory, a warning displays indicating that youshould drop the schema corresponding to the database contained within the project.

44

3. EE

E

nviro

nm

ent

Delete________________

Selecting Accept on the warning form deletes the project and its database, whileselecting Cancel cancels the Delete function.

For information about dropping a schema, see RIS Schema Manager,page 553 .

If a database does not exist in the project directory, a warning displays indicating thatyou are about to delete an entire project.

Selecting Accept on the warning form deletes the project, while selecting Cancelcancels the Delete function.

— OR —

Select another option to ignore your input and cancel the Delete process.

45


Archive

This option stores an entire project and associated database on a network host or on a floppydisk.

Field Descriptions

Remote node name/address — This field accepts the node name or address of thesystem to receive the project.

TCP/XNS — This toggle allows you to choose between TCP and XNS networkprotocols. A password is required if you are using the TCP option.

Remote path/directory — This field accepts a key-in for the destination node of theproject. The project name is appended to this path. The path must exist on the remotenode.

Password Echo — This toggle allows you to display the user password you enter in thePassword field.

Username on remote node — This field accepts the user name for the destinationnode.

Password — This field accepts the password (if one exists) for the destination node. Apassword is required if you are using the TCP option.

46

3. EE

E

nviro

nm

ent

Archive________________

Steps

1. Select Archive from the Project Menu option list.

2. Select the Project name from the scrolling area.

— OR —

Select the Project name field, and key in a project name.

3. Select the storage facility for your project files.

Network is the default setting on the Network/Floppy toggle. Toggling to Floppychanges the displayed form information.

Default values for the remote node name, user name, and remote directory may beassigned in the user’s .EErc file, using the global symbols EE_NODENAME,EE_USERNAME, and EE_REMDIR. (If you need more information about the .EErcfile, contact your system administrator.)

When archiving using a floppy disk, you must have a formatted floppydisk placed in the disk drive.

4. Select Confirm (√) to begin archiving.

— OR —

Select another option to ignore your input and cancel the Archive process.

47


Restore

This option retrieves an entire project and any associated database from a network or a floppydisk.

When restoring from a network, you cannot restore a project that is currentlylisted in the listing area. You must delete or rename the current project tocomplete the restore process.

When restoring from a floppy, you can restore a project that is currently listed in yourlisting area. The project on the floppy will overwrite the project in your directory. Besure to verify that archived project will not overwrite existing projects with the samename.

Field Descriptions

Remote node name/address — This field accepts the node name or address of thesystem from which to receive the project.

TCP/XNS — This toggle allows you to choose between TCP and XNS networkprotocols. A password is required if you use the TCP option.

Remote path/directory — This field accepts a key-in for the project’s node of origin.)

Password Echo — This toggle allows you to display the user password you enter in thePassword field.

Username on remote node — This field accepts the user name for the node of origin.

Password — This field accepts the password (if one exists) for the node of origin. Apassword is required if you are using the TCP option.

48

3. EE

E

nviro

nm

ent

Restore________________

Steps

1. Select Restore from the Project Menu.

2. Select the Project name field, and key in a project name.

3. Indicate the storage location for your project.

Network is the default setting on the Network/Floppy toggle. Toggling to Floppychanges the displayed form information.

When restoring from a floppy disk, you must have the disk in the diskdrive.

4. Select Confirm (√) to begin restoring.

— OR —

Select another option to ignore your input and cancel the Restore process.

49


Database Utilities

This option accesses the RIS Schema Manager environment and the EE schema updatingprocesses.

The Database Utilities options are described in detail in the following sections.

RIS schema utilities

Update Project Schema

Update Reference Schema

50

3. EE

E

nviro

nm

ent

RIS schema utilities________________

RIS schema utilities

This option accesses the RIS Schema Manager form. With this utility you can create, drop,and maintain project and reference database schemas.

Before using this utility, you must have an existing database and user name. Consult yourrelational database management system (RDBMS) documentation for specific informationabout database installation. RIS Schema Manager, page 553 supplies examples of CreateSchema input for several RDBMSs.

Normally this is a procedure for a system or application manager.

Steps

1. To access the RIS Schema Manager form, select the RIS schema utilities option fromthe Database Utilities menu.

2. Proceed through the necessary RIS Schema Manager processes. For moreinformation, see RIS Schema Manager, page 553 .

51


Update Project Schema

This option allows you to modify the structure and data of an existing project schema. Youcan use individual or multiple EE applications to update the schema.

For additional information about updating schemas, seeEE Databases, page 425 .

Field Descriptions

Output file — Defines the processing message file name.

Error file — Defines the error processing message file name.

Schema name — Defines the project database’s schema name. To enter the schemaname, select the field and key in the name of an existing project schema.

Schema password — Defines the schema password, if one exists. To enter thepassword, select the field and key in the name of the password corresponding to theschema name you entered.

Password Echo/No echo — This toggle defines if you want to display the schemapassword input. To display the schema password input, set the toggle to Echo.

Application checkboxes – These boxes allow you to select the EE application(s) withwhich you are updating the schema. Only those products loaded on your workstationwill display as options. You can update the schema with multiple products, thoughdoing so will slow processing time.

52

3. EE

E

nviro

nm

ent

Update Project Schema________________ You can also update the schema with your own data by selecting the User Definedcheckbox.

Sql and Cmd file — These fields display the command and SQL files associated witheach application. The delivered default files are defined in thewin32app\eenuc\bin\.EErc file. You can redefine the defaults by editing this .EErc fileor by redefining the variables in your $HOME\.EErc file.

To change the displayed default files, select the field, and key in the desired filenames.To specify command and SQL files for usr-defined data, select the fields next to theUser Defined checkbox, and key in the full pathname for those files, or exportEE_CUSTOM_SQL and EE_CUSTOM_CMD for the customized SQL and commandfiles.

Processing toggle — This toggle indicates the operating mode for the update process.You can set the toggle to Foreground (default), Background, or Batch. For moreinformation about operating modes, seeProcess, page 64 .

Steps

1. Select the Update project schema option from the Database Utilities form.

The Update project schema form displays:

2. Set up the form to meet your specifications.

3. Select Confirm (√) to update the project schema.

The update process displays the message Processing ...

— OR —

Select Reset to return to the Database Utilities form without retaining your input.Return to step 1.

4. When Update project schema finishes processing, it will display one of two messagefiles to the screen:

— If the schema is updated without errors, the system displays a processing messagefile (create_db.msg).

53


— OR —

— If errors occur during the update process, the system displays an error message file(create_db.err).

You can also access these message files, located in the currentproject’s /tmp directory, using the Output option on the Utilitiesform. For more information, seeOutput, page 89 .

5. Select Reset on the message file form to return to the Update project schema form.

6. Select Reset again to exit the process and return to the Database Utilities form.

54

3. EE

E

nviro

nm

ent

Update Reference Schema________________


This option allows you to modify the structure and data of an existing reference schema. Youcan use individual or multiple EE applications to update the schema.

For additional information about updating schemas, seeEE Databases, page 425 .

Field Descriptions

Output file — Defines the processing message file name.

Error file — Defines the error processing message file name.

Schema name — Defines the reference database’s schema name. To enter information,select the field, and key in the name of an existing reference schema.

Schema password — Define the schema password, if one exists. To enter information,select the field, and key in the name of the password corresponding to the schema nameyou entered.

Password Echo/No echo — This toggles define if you want to display the schemapassword. To display the schema password input, set the toggle to Echo.

Application checkboxes — These boxes allow you to select the EE application(s) withwhich you are updating the schema. Only those products loaded on your workstationwill display as options. You can update the schema with multiple products, thoughdoing so will slow processing time.

You can also update the schema with your own data by selecting the User Definedcheckbox.

Sql and Cmd File — These fields display the command and SQL files associated witheach application. The delivered default files are defined in thewin32app\eenuc\bin\.EErc file. You can redefine the defaults by editing this .EErc fileor by redefining the variables in your $HOME\.EErc file.

To change the displayed default files, select the field, and key in the desired filenames.To specify command and SQL files for usr-defined data, select the fields next to theUser Defined checkbox, and key in the full pathname for those files, or exportEE_CUSTOM_REFSQL and EE_CUSTOM_REFCMD for the customized SQL andcommand files.

Processing mode — This toggle indicates the operating mode for the update process.You can set the toggle to Foreground (default), Background, or Batch. For moreinformation about operating modes, see Process, page 64 .

55


Steps

1. Select the Update reference schema option from the Database Utilities form.

The Update reference schema form displays.

2. Set up the form to meet your specifications.

3. Select Confirm (√) to update the reference schema.

The update process displays the message Processing ...

— OR —

Select Reset to return to the Database Utilities form without retaining the formparameters. Return to step 1.

4. When Update reference schema finishes processing, it will display one of twomessage files.

— If the schema is updated without errors, the system displays a processing messagefile (create_db.msg).

— OR —

— If errors occur during the update process, the system displays an error message file(create_db.err).

56

3. EE

E

nviro

nm

ent

Update Reference Schema________________

You can also access these message files, located in the currentproject’s /tmp directory, using the Output option on the Utilitiesform. For more information, seeOutput, page 89 .

5. Select Reset on the message file form to return to the Update reference schema form.

6. Select Reset again to exit the process and return to the Database Utilities form.

57


58

4. EE

RW

AY

E

nviro

nm

ent

Electrical Engineer (EE) Raceway Environment________________

4. Electrical Engineer (EE)Raceway Environment

When you select the Enter option from the Project Menu, one of two menus display:

The EE Environment Product Menu, if you have multiple EE products installed on theworkstation (seeProduct Menu, page 42 for more information).

— OR —

The EE Raceway Design Menu.

The rest of this chapter describes all the options on this menu. If you are anew user, you may want to skip all but the Create and Design options.

Commands

The following sections describe each option in detail and show the menu as it displays wheneach option is selected.

Create — Allows you to create a design file.

59

EE Raceway Modeling Reference Guide - February 2003________________ Design — Allows you to enter a design file and attaches the EE menus.

Process — Allows you to list and select EE Raceway processes. It also processeswork on design files and/or databases.

EDEN — Allows you to design your own symbols for raceway elements.

Report — Displays the information in an EE Raceway database.

Rule — Displays the design rule errors occurring in the design process.

Utilities — Allows you to access functions needed to manipulate EE Raceway design,rule, report, and message files.

60

4. EE

RW

AY

E

nviro

nm

ent

Create________________

Create

This option creates design files, based on a specified seed file.

When you create a drawing, you are actually copying a seed file (a template). The seed filecontains basic information that EE Raceway uses. A seed file can also contain customizedinformation like company borders and logos.

EE Raceway is delivered with both a metric (mseed.dgn) and English seed file (seed.dgn).You can also use seed files that were generated in a Plant Design (PDS) environment. EERaceway will convert PDS seed files to raceway design files the first time you enter the EERaceway graphics environment.

Steps

1. Select Create from the Design Menu.

If there is only one seed file, it is displayed as the default. If there is more than oneseed file available, the listing area displays all these files.

By default, the seed file subdirectory is win32app\ingr\eerway\dgn\seed.You can change this directory by redefining the EERWAY_SEEDsymbol in the directory or in your login directory.

2. Select the seed file.

Choose a seed file either by accepting the default (this happens automatically when youselect Confirm (√)) or by selecting a seed file from the scrolling area.

3. Select the drawing name input box and key in a drawing name and, optionally, a fileextension.

61

EE Raceway Modeling Reference Guide - February 2003________________ A file extension of .dgn is automatically appended to the drawing name if you do notenter your own file extension.


The drawing name and its file extension become the filename of the drawing. Thedrawing is added to the active project.

— OR —

Select another option from the Design Menu to ignore your input and cancel theCreate process.

62

4. EE

RW

AY

E

nviro

nm

ent

Design________________

Design

This option accesses the graphics environment, taking you into a specified existing designfile.

Steps

1. Select Design from the Design Menu.

2. Select the drawing name from the listing area.


The system invokes the graphics environment.

— OR —

Select another option from the Design Menu to ignore your input and cancel theDesign process.

63


Process

This option accesses all available EERWAY processes. These processes allow you tomanipulate drawings and the project database.

Overview

This section provides general information about running all processes. See RacewayProcesses, page 331 for more information about individual processes.

The screen above lists the processes currently delivered with the product. Thesystem manager can add or delete processes from the list by modifying theprocess.dat file in win32app\eerway\data.

64

4. EE

RW

AY

E

nviro

nm

ent

Process________________ When you enter a specific process, an input screen displays.

You must key in any information not already shown as defaults. You can override defaultvalues by keying in your own information. All drawings are displayed on the screen scrollingarea. An asterisk (*), when placed in the Enter Drawing Name input field, is a wild cardcharacter which can be used to list a subset of your drawings. For example, if you enter a*,all drawings beginning with the letter "a" will be displayed. The ? character can also be usedas a wild card for a single character. Once you have entered all necessary information, selectConfirm (√) to execute the process.

Operating Modes

The Processing toggle allows you to select the operating mode for a process. The defaultmode is Foreground, but you can toggle between that option and the Background and Batchoptions.

A process in Foreground runs immediately, and you do not regain control until theprocess is finished. In other words, you cannot perform other functions within the samewindow in which you are running the process.

A process in Background runs immediately, and you regain control immediately.

A process in Batch does not run until the time you specify. You must key in a timeand/or date when you want the process to start. After providing this information, youregain control immediately.

65


Entering Time in Batch Mode

If you select Batch mode, an input box displays, allowing you to enter the time and date whenyou want the process to run.

The time can be entered as 1, 2 or 4 digits. One- and two-digit numbers are taken to be hours,four digits to be hours and minutes. The time can also be specified as two numbers separatedby a colon (hour:minute). The suffix AM or PM may be appended; otherwise, a 24-hourclock (military time) is understood. The system also recognizes the names NOON,MIDNIGHT, NOW and NEXT.

Optionally, you can specify a date using either a month name followed by a day number or aday of the week (fully spelled or abbreviated to three characters). The system recognizes thewords TODAY and TOMORROW. If you input no date, the system assumes it should run thejob TODAY if the specified hour is greater than the current hour, and TOMORROW if thespecified hour is less than the current hour.

Legitimate commands include:

0815am Jan 248:15am Jan 24Now + 1 day5pm Friday

Steps

1. Select Process from the Design Menu.

2. Select a process from the listing area.

3. Select Confirm to invoke the input form for the specified process.

— OR —

Select another option from the Design Menu to ignore your input and cancel theProcess option.

66

4. EE

RW

AY

E

nviro

nm

ent

EDEN________________

EDEN

Eden is a high-level symbol definition language (modeled after the FORTRAN programminglanguage) that allows you to design your own symbols for straights, fittings, and special parts.

The following screen displays the Eden options delivered with this version of EE Raceway.The system manager can add or delete displayed options by modifying the eden.dat file.

This section provides general information about running all Eden programoptions. For detailed information about individual Eden options, see EdenProcesses, page 347 .

67

EE Raceway Modeling Reference Guide - February 2003________________ When you select an option from the Eden menu (and confirm the selection using Confirm(√)), an input screen displays.

You must key in all information not displayed as defaults. If necessary, you can override thedefault values that already display, and key in your own information.

Once you have entered all necessary information, select Confirm (√) to begin the optionprocess.

Operating Modes

A box on the right side of the menu allows you to select the operating mode for the selectedoption. The default mode is foreground. The circular arrow on the right indicates that thisbox leads to other selections. These selections are the three methods of running an option:foreground, background, and batch.

An option in foreground mode runs immediately, and you cannot regain control untilthe process is finished. In other words, you cannot perform other functions within thewindow in which the option is running.

An option in background mode runs immediately, and you regain control immediately.

A process in batch does not run until the time you specify. You must key in a timeand/or date when you want the process to start. After providing this information, youregain control immediately.

68

4. EE

RW

AY

E

nviro

nm

ent

EDEN________________

Entering Time in Batch Mode

If you select batch mode, an input box displays, allowing you to enter the time and date whenyou want the option to begin processing.

The time can be entered as 1, 2 or 4 digits. One- and two-digit numbers are taken to be hours,four digits to be hours and minutes. The time can also be specified as two numbers separatedby a colon (hour:minute). The suffix AM or PM may be appended; otherwise, a 24-hourclock (military time) is understood. The special names NOON, MIDNIGHT, NOW andNEXT are also recognized.

You can specify an optional date in the form of either a month name followed by a daynumber or a day of the week (spelled in its entirety or abbreviated to three characters). Thesystem accepts the words TODAY and TOMORROW. If you input no date, the systemassumes that if the specified hour is greater than the current hour, it will run the job TODAY,and if the specified hour is less than the current hour, it will run the job TOMORROW.

Legitimate commands include:

0815am Jan 248:15am Jan 24Now + 1 day5pm Friday

69


Report

This option accesses the standard EERWAY reports. These reports report on the project andreference databases. You must load the project database before running any reports.

Overview

This section contains general information about running all EE Raceway reports. SeeReports, page 545 for more detailed information about individual reports.

The system manager can change the names of the reports that display in thelisting area and can add additional reports by editing the report.dat file(win32app\eerway\data).

70

4. EE

RW

AY

E

nviro

nm

ent

Report________________ When you process a report, an input screen displays, allowing you to enter all input necessaryto run the report.

Key in any information that is not supplied by default. You can change the name of theoutput file or error file. To change the output filename, select the output file box and key in anew name. (No file extension is automatically appended to the name you key in.)

If you want to save reports throughout a project, you should name the output filesyourself. If a new output file has the same name as an existing file, the new filewill overwrite that file. You should give each report you want to save a uniquename.

Steps

1. Select Report from the Design Menu.

2. Select a report from the listing area.

3. Select Confirm (√) to invoke the input form for the specified process.

— OR —

Select another option from the Design Menu to ignore your input and cancel theReport option.

71


A Special Note for Bill of Materials by Volume

When running a Bill of Materials by Volume report, you are required to define a low and highrange in PDS coordinates. These low and high ranges define a cubic volume from which thereport is pulled.

Any Raceway component extending outside the clipping volume defined by the High andLow Range Coordinates will not be included in the report output.

You can find the coordinates you want to use by using the active point coordinate display onthe precision input form. The coordinate values need to be in subunits and entered in the formfield with a space between the coordinates: easting northing elevation For example, 234532 34

It should be understood that westing and southing coordinates must be thenegative of their opposite directional coordinate. For instance, a westingcoordinate of 100 should be keyed in as a value of -100 in the eastingdirection, and a southing coordinate of 3000 should be keyed in as a value of-3000 in the northing direction.

72

4. EE

RW

AY

E

nviro

nm

ent

Rule Checks________________

Rule Checks

This option accesses the standard EERWAY Rule Checks. These rule checks are reports thatidentify violations of certain design rules by working on the project database. You must loadthe project database before running any rule checks.

Overview

This section contains general information about running all EERWAY rule checks. For moredetailed information about each rule check, see Reports, page 545 .

The system manager can change the names of the reports or add new reports tothe listing area by editing the rule_chk.dat file in win32app\eerway\data.

73

EE Raceway Modeling Reference Guide - February 2003________________ When you process a rule check, an input screen displays.

The name of the rule check report displays at the top. Accept the default information thatdisplays in the input fields, or change that information according to your specifications.

If you want to save reports throughout a project, you should name the output filesyourself. If a new output file has the same name as another file created previously,the new file will destroy the previously created file. You should give each reportthat you want to save a unique name.

Steps

1. Select Rule from the Design Menu.

2. Select a rule check report from the listing area.


— OR —

Select another option from the Design Menu to ignore your input and cancel the Ruleoption.

74

4. EE

RW

AY

E

nviro

nm

ent

Utilities________________

Utilities

This option manipulates files within a project. All manipulations are performed on those filesresiding in the current project’s directories.

When you select Utilities from the Design Menu, the Drawing Utility Menu displays.

Files in the current project sub-directories will be listed in four columns. Each column will lista different subdirectory.

75

EE Raceway Modeling Reference Guide - February 2003________________ Drawing (.dgn) - All drawings. (<project_name>/eerway/dgn)

Report (.rpt) - All report files generated by standard reports.(<project_name>/eerway/rpt)

Rule (.chk) - All report files generated by rule checks reports.(<project_name>/eerway/chk)

Message (.tmp) - All files output by Raceway processes, and error files generated bystandard reports and rule check reports. (<project_name>/eerway/tmp)

Utilities options will operate on all of the above file types.

Commands

The commands on the Drawing Utility Menu are described in their respective sections laterin this chapter.

Copy — Copies a file.

Delete — Deletes a file (mark for purging).

Undelete — Undeletes a file (unmark for purging).

Purge — Purges (permanently deletes) a file.

Rename — Renames a file.

Send — Sends a file to a network node.

Receive — Receives a file from a network node.

Archive — Archives a file to a network node or floppy disk.

Restore — Restores an archived file from a network node or floppy disk.

Output — Outputs a file to a printer, screen, or plotter.

Steps

1. Select Utilities from the Design Menu.

2. Select the desired option from the Drawing Utility Menu, and then select the file(s) onwhich to perform that option.

3. Enter necessary form information for the active option.

76

4. EE

RW

AY

E

nviro

nm

ent

Utilities________________

4. Select Confirm (√) to accept the settings and execute the active option.

— OR —

Select another option to ignore your input and cancel the active option.

77


Copy

This option copies an existing file to another file. You must specify a unique filename for thedestination file. Copy DOES NOT automatically append a file extension (.dgn, .rpt, and soforth) to the new file.

Field Descriptions

Copy file from — This field displays the name of the file to be copied; elect a file fromthe list, or key in the name of the file to be copied.

Copy file to — This field displays the name that the copy (destination) file will becalled; key in a unique destination file name into this field.

78

4. EE

RW

AY

E

nviro

nm

ent

Delete________________

Delete

This option removes your access to a specified file. To physically remove the file from theworkstation, you must select the Purge option. Note that files you delete with this option takeup storage space, but can be undeleted (that is, have access returned to them) until youactively Purge them.

79


Undelete

This option returns your access to a file that you removed using Delete. Once you haveremoved files using Purge, you cannot undelete them with this option.

80

4. EE

RW

AY

E

nviro

nm

ent

Purge________________

Purge

This option permanently removes all the files you marked for deletion using the Deleteoption. Once you Purge a file, you cannot recover it.

Field Descriptions

Purge Files toggle — This toggle allows you to choose between purging ALL files thathave been deleted, selected files that have been deleted, or no files at all.

When the toggle is set to Select files to purge, you can select specific files from the listby placing a data point on them. To de-select a selected file, place a data point on it.

81


Rename

This option changes the name of an existing file. It does not automatically append a fileextension (.dgn, .rpt, and so forth) to the new filename.

Field Descriptions

Rename file from — This field displays the current filename. You can select the filefrom the list, or key the name into this field.

Rename file to — Key in the name that you desire to rename the current file.

82

4. EE

RW

AY

E

nviro

nm

ent

Send________________

Send

This option copies a file to a network node. Be sure to include the entire filename includingthe extension (for example, test1.dgn). If you are sending a design file to a VAX, turn on theIGDS toggle. Doing so will store the file in contiguous blocks on the VAX.

Field Descriptions

Password Echo toggle — The setting of this toggle determines whether the passwordof the remote machine is visible or hidden upon keyin to the password field.

TCP/XNS Protocol toggle — The setting of this toggle determines whether the transferuses the TCP or XNS protocol to communicate between machines.

IGDS/No IGDS toggle — This toggle should be set to the IGDS setting when sendingto a VAX system. Otherwise, the setting should be No IGDS.

File name — This field reflects the name of the file to be sent. You can either selectthe desired file from the list, or key in the appropriate name.

Remote node name/address — This field expects the node name or address of themachine to which you want to send the file.

Remote path directory — This field expects the path on the remote machine to whichyou want to send the file.

Username on remote node — This field expects the username on the receivingmachine.

Password — This field expects the password that corresponds with given username onthe receiving machine. The password may or may not be visible in the field, dependingon the setting of the Password Echo toggle.

83


Receive

This option copies a file from a network node. Be sure to specify the complete filename,including its extension. Also, specify the local path to the file; otherwise the file will beplaced in the <project_name>/eerway directory.

Receive will overwrite any file having the same name as the file you are receiving.

Field Descriptions

Password Echo toggle — The setting of this toggle determines whether the passwordof the sending machine is visible or hidden upon keyin to the password field.

TCP/XNS Protocol toggle — The setting of this toggle determines whether the transferuses the TCP or XNS protocol to communicate between machines.

File name — This field reflects the name of the file to be received. You can eitherselect the desired file from the list, or key in the appropriate name.

Remote node name/address — This field expects the node name or address of themachine from which you want to receive the file.

Remote path directory — This field expects the path on the remote machine fromwhich you want to receive the file.

Username on remote node — This field expects the username on the sending machine.

Password — This field expects the password that corresponds with given username onthe sending machine. The password may or may not be visible in the field, dependingon the setting of the Password Echo toggle.

84

4. EE

RW

AY

E

nviro

nm

ent

Receive________________ Local path (dgn, rpt, chk, tmp) — This field expects the path to the desired locationof the file being received.

85


Archive

This option creates a backup copy of a file to a network node or to a floppy disk. Togglebetween Network and Floppy by selecting the toggle button. For more information about thefields that display on the form when Network is active, see the description of Archive inArchive, page 46 .

Field Descriptions

Password Echo toggle — The setting of this toggle determines whether the passwordof the archiving machine is visible or hidden upon keyin to the password field.

TCP/XNS Protocol toggle — The setting of this toggle determines whether thecommunication between machines uses the TCP or XNS protocol.

Network/Floppy toggle — The setting of this toggle determines if the file will bearchived over a network or to a floppy disk.

Archive file name — This field expects you to key in the desired name of the archivefile.

Remote node name/address — This field expects the node name or address of themachine to which you want to archive the file.

Remote path directory — This field expects the path on the remote machine to whichyou want to archive the file.

Username on remote node — This field expects the username on the receivingmachine.

Password — This field expects the password that corresponds with given username onthe remote machine. The password may or may not be visible in the field, dependingon the setting of the Password Echo toggle.

86

4. EE

RW

AY

E

nviro

nm

ent

Restore________________

Restore

This option copies a backup file from a network node or floppy disk. Use theNetwork/Floppy toggle to select between the two options. For more information about thefields that display on the form when Network is active, see the description of Restore inRestore, page 48 .

This option will overwrite any file having the same name as the file you arerestoring.

Field Descriptions

Password Echo toggle — The setting of this toggle determines whether the passwordof the archiving machine is visible or hidden upon keyin to the password field.

TCP/XNS Protocol toggle — The setting of this toggle determines whether thecommunication between machines uses the TCP or XNS protocol.

Network/Floppy toggle — The setting of this toggle determines if the file will bearchived over a network or to a floppy disk.

Archive file name — This field expects you to key in the name of the archive file to berestored.

Remote node name/address — This field expects the node name or address of themachine from which you want to restore the archive file.

Remote path directory — This field expects the path on the remote machine fromwhich you want to restore the archive file.

87

EE Raceway Modeling Reference Guide - February 2003________________ Username on remote node — This field expects the username on the remote machine.

Password — This field expects the password that corresponds with given username onthe remote machine. The password may or may not be visible in the field, dependingon the setting of the Password Echo toggle.

88

4. EE

RW

AY

E

nviro

nm

ent

Output________________

Output

This option sends files to the printer, screen, plotter, or laser printer. Invalid operations –sending a drawing to the printer, for example – are not allowed. If you do not specify anoutput destination, the selection displayed at the top of the list is the default selection.

An external data file delivered with the environment (win32app\eenuc\data\print.dat) controlsthe available output options. The system manager may modify this file to add desired options.Local commands, NQS options, IPLOT commands, or user programs may be added to supportspecific output requirements.

Field Descriptions

File name — Key in the name of the file to be submitted to the output process, or selectit from the list.

Output Destination List — Select the appropriate output device.

89


90

5. EE

RW

AY

G

raph

ics

EE Graphics Interface Elements________________

5. EE Graphics Interface Elements

This chapter describes the graphics environment you will encounter while working in a designfile. It also documents the on-line Help system and provides other general information neededto work in a design file. This chapter contains the following sections:

Start-Up Sequence

Screen Display

EERWAY Command Menu Bar

Palettes in the EERWAY Graphics Environment

Identifying Elements

Working Units and Precision Key-ins

All of the EERWAY graphics commands are menu-driven. You will use the panel menus andthe bar menu to select the commands. By default, the panel menu is located on the right sideof your screen and the bar menu is at the top. You can also invoke commands by keying inthe command name and pressing <Return>. This chapter contains more detailed informationabout using menus.

If you are not familiar with the following terms: command button <C>, data button <D>, orreset button <R> in reference to the cursor or mouse, see Document Conventions in thePreface to this document.

91


Start-up Sequence

When you enter an EERWAY design file (seeDesign, page 63 ), the system goes through the following processes:

Displays all active design file views.

Displays a command window at the bottom of the screen.

Initializes RIS with the reference schema.

92

5. EE

RW

AY

G

raph

ics

Screen Display________________

Screen Display

The screen display you will see when you enter a design file is described below.

If you have modified the default application menu configuration file, asdescribed in the previous section, your screen display may be different. (Checkwith your system manager if you have a customized rway.cmds file.)

1. MicroStation Command Window - contains the following six fields that displaysystem messages and your inputs from the keyboard:

— Window Menu Button - displays a list of window actions. Only the Lower andSink actions are available from the command window. To select an action, pressand hold the data button and move the cursor through the list. When the correctitem highlights, release the data button.

93


— Sink Box - moves the command window below views and other windows of itsown type.

— Command Status Field - displays startup file information and product name.

— Current Command Field - displays the name of the current active command.

— Key-In Field - displays alphanumeric values you enter from the keyboard.

— System Prompt Field - displays a system prompt that directs you through acommand.

2. Command Menu Bar - contains the primary types of commands used in the EERWAYgraphic environment. Select the type of command you want to use with a data point tosee the pull-down menu of available commands or command palettes.

3. Working Area - displays elements as you place them. All your design work occurs inthe screen working area.

4. Windows - provide ways for you to change the way you look at your design. Thenumber and name of each view appears in the window title area.

94

5. EE

RW

AY

G

raph

ics

Screen Display________________ Window Manipulation Buttons - provide ways to manipulate windows.

Window Menu Button - displays a list of window actions. Double-clicking on thisbutton deletes the window. To select an action from the menu, press and hold the databutton and move the cursor through the list. When the correct item highlights, releasethe data button.

Restore - restores a minimized or maximized window to the previous size andlocation.

Move - moves a window around the workspace.

Size - changes the height and width of the window in the direction indicated bythe pointer.

Minimize - collapses a window.

Maximize - enlarges a window to its maximum size. If you select this entry on awindow that is already at its maximum size, the window is restored to itsprevious size and location.

Lower - moves a window to the bottom of the window hierarchy.

Close - deletes a window.

Minimize Button - collapses a window.

Maximize Button - enlarges a window to its maximum size. If you select themaximize button on a window that is already at its maximum size, the window isrestored to its previous size and location.

Resize Borders - provide ways to move and resize windows.

Move Arrows - appear when the cursor is placed over the window border. Press andhold the data button to move the window.

Vertical Arrows - appear when the cursor is placed at the top or bottom border. Pressand hold the data button to change the height of the window as you move the cursor.

Horizontal Arrows - appear when the cursor is placed at the left or right border. Pressand hold the data button to change the width of the window as you move the cursor.

Diagonal Arrows - appear when the cursor is placed at the border corners. Press andhold the data button to change both the height and width of the window withoutchanging the position of the opposite corner.

95


EERWAY Command Menu Bar

The EERWAY command menu bar appears near the top of the MicroStation commandwindow. Each keyword on the command menu bar allows access to a menu of optionsrelating to that keyword.

Using the Command Menu Bar

The command menu bar is a logical menu. Each keyword leads to a pull-down menu thatcontains commands for various EERWAY tasks; you can also access command palettes fromthese pull-down menus, when applicable.

To select a keyword, place the cursor over the button and press <D>.

For instance, selecting File initializes the File pull-down menu, which allows access to thefollowing commands:

EERWAY Palette - Invokes the EERWAY command palette.

Bar Commands - Invokes the Bar Commands palette, which allows access to the mostfrequently-used MicroStation commands.

Remove Palettes - Removes all palettes that have been invoked.

Compress Design - Invokes MicroStation’s Compress Design command.

Exit - Executes the File Design command, and exits the graphics environment to returncontrol to the EE Raceway menu interface.

Integrated Commands - Invokes the Integrated Commands menu.

96

5. EE

RW

AY

G

raph

ics

Palettes in the EE Raceway Graphics Environment________________

Palettes in the EE Raceway GraphicsEnvironment

This section presents the palettes that are used in the EE Raceway graphics environment.Palettes are groups of commands that are accessible from the EERWAY command menu baron the MicroStation command window. This section presents the palettes in the order thatthey are accessible if you look at each menu going from left to right across the EERWAYcommand menu bar on the MicroStation command window.

Next to each icon is the name of the form or command it represents. You should becomefamiliar with the name and functionality of each command on each palette. Each command isdescribed in full in later sections of this text.

EERWAY

This palette is activated by selecting File from the MicroStation command window, thenselecting EERWAY from the resulting menu.

Integrated Commands

This palette is activated by selecting File from the MicroStation command window, thenselecting Integrated Commands > Palette from the resulting menu.

97


Bar Commands

This palette is activated by selecting File from the MicroStation command window, thenselecting Bar Commands from the resulting menu. This palette contains the MicroStationcommands as discussed in the MicroStation documentation.

Modify Element

This palette is activated by selecting Modify Element from the EERWAY palette, or it canbe activated by selecting Modify Element from the Modify palette as shown later in thissection.

This palette can also be activated by selecting Modify from the MicroStation commandwindow, then selecting Modify Element Commands from Modify menu, then selectingPalette.

98

5. EE

RW

AY

G

raph

ics


Design

This palette is activated by selecting Design from the MicroStation command window, thenselecting Palette from the resulting menu.

Modify

This palette is activated by selecting Design from the MicroStation command window, thenselecting Modify from the resulting menu.

99


Modify Group

This palette is activated by selecting Modify Group from the Modify Palette. You can alsoactivate this palette by selecting Modify from the MicroStation command window, thenselecting Modify Group Commands, then selecting Palette.

Setup Commands

This palette is activated by selecting Setup from the MicroStation command window, thenselecting Palette.

100

5. EE

RW

AY

G

raph

ics


Model Commands

This palette is activated by selecting Model Commands from the Setup Commands palette.

Runtime Setup

This palette is activated by selecting Runtime from the MicroStation command window, thenselecting Palette.

101


Utilities

This palette is activated by selecting Utilities from the MicroStation command window, thenselecting Palette.

Database

This palette is activated by selecting Database from the MicroStation command window, thenselecting Palette.

102

5. EE

RW

AY

G

raph

ics

Identifying Elements________________

Identifying Elements

Any structure, line, or shape you place is called an element. In many commands, you mustidentify an element to perform certain manipulations.

To identify an element, place a data point on it. The system highlights the element. If thecorrect element highlights, press <D> again to accept the element. If there is more than oneelement in the location you want to identify, the wrong element may highlight. If the wrongelement highlights, press <R> to reject that element. The system then highlights anotherelement.

When you are moving an element, one data point can serve more than one function in thesame command. For example, the point you place to accept the element becomes the pointfrom which the element is moved. Several of the command descriptions include steps wherethe accepting data point also serves as the placement point.

103


Working Units and Precision Key-ins

When you place elements or manipulate them, you can often use data points, but placing datapoints does not always provide the accuracy you need. Therefore, EERWAY lets you key invalues (called precision key-ins) as well as place data points.

Precision key-ins let you accurately place elements by using a working units system based onMaster Units, Subunits, and Positional Units, also known as MU:SU:PU. You mustunderstand the MU:SU:PU system before you can use precision key-ins.

Working Units in MU:SU:PU

For Intergraph electrical designs, the working units of measurement, called MU:SU:PU, areestablished based on the project type (metric or English).

Working units are coordinate units corresponding to the position and definition of a point inthe design file. The working unit dictates the degree of accuracy for placement of elements ina drawing and determines the scale relationship of elements in the design. The followingexplains the format of MU:SU:PU.

MU — Master (main) Unit of measurement (for example, 1 foot)

SU — Subunit, a division of a master unit (1 inch)

PU — Positional Unit, the smallest degree of accuracy that is possible in the design file(a fraction of an inch)

In EERWAY, predetermined values for working units in imperial and metric projects wereused to create the delivered cell library. If using this cell library, we recommend that you usethese default settings:

Unit Imperial Metric

1 Master Unit 1 foot = 12 subunits 1 meter = 1000 subunits

1 Subunit 1 inch = 8000 positional units 1 millimeter = 10 positional units

1 Positional Unit 1/8000 inch 1/10 millimeter

While these are the suggested working units for delivered cell libraries, you arenot limited to using only them. You may set your working units to any desiredvalue, if a user-created cell library is being used. (See your system manager formore information about the working units settings used at your location.)

104

5. EE

RW

AY

G

raph

ics

Working Units and Precision Key-ins________________ Below are some examples of values and how to key them in:

1/2 foot

= :6 (6 subunits)

= .5 (1/2 master unit)

1/2 inch

= :.5 (1/2 subunit)

= :1/2 (1/2 subunit)

= :0:4000 (4000 positional units)

18 inches

= 1.5 (1-1/2 master units)

= 1:6 (1 master unit and 6 subunits)

Precision Key-ins

Precision key-ins let you place points accurately to create elements and shapes with exactlengths and areas. You specify a distance and an angle from the last point placed, or you canspecify the delta values in X and Y to place another point. Key-ins are entered through thealphanumeric keyboard.

There are several ways to key in precision points, as described below:

DI=(distance, direction) To place a precision point, key in the distance in MU:SU:PUworking units and the direction in degrees that you want the point to be placed. Thenew point is placed relative to the previous point. For example, if you want to place apoint 10 inches directly to the right, key in DI=0:10,0.

DL= (delta coordinates) To place a precision point, key in the delta x and delta y inMU:SU:PU that you want the point to be placed. The new point is placed relative to theprevious point. For example, if you want to place a point 18 inches over and 18 inchesup, key in DX=1:6,1:6.

XY= (absolute coordinates) To place a precision point, key in its absolute x and ycoordinates.

105


106

6. Wo

rkflow

Workflow and Procedures________________

6. Workflow and Procedures

This section describes the overall workflow of EE Raceway Modeling software, as an operatorwould typically use it. This includes setting up the design file, creating a raceway model, andrunning reports and processes on the file. Preparation for the application or system manageris described in System/Application Manager Information, page 415 .

This section covers the following topics:

The drawing process

EE Databases

Reports

Interference detection

Because the steps of the workflow are covered in detail elsewhere in thedocument, this section will refer you to other documentation whereverpossible.

107


The Drawing Process

Before outlining a typical workflow for drawing a raceway, it is important to describe basicraceway concepts.

Typically you begin drawing raceways with one-line elements (one-lines). These one-linedrawings are the centerlines of raceways and through propagation become the three-dimensional shapes (three-lines) that occupy the volume of the raceways. EE RacewayModeling software allows you to place one-lines and then propagate them into three-lines orraceways.

The figure below displays one-line elements on the left. On the right are the same elementsafter propagation.

This section is divided into individual descriptions of the steps involved in the drawingprocess. In general, you should perform these steps in the order in which they are described.The following steps comprise the drawing process and this section:

System manager setup

Drawing setup

Place one-lines

Propagation

108

6. Wo

rkflow

System Manager Setup________________

System Manager Setup

Before you begin an individual drawing, the system/application manager should determine thedefaults and parameters that will affect your project and drawing (tray sizes, for example).The system manager must also add vendor catalogs (parts, specifications, and vendor names)and the desired systems and one-line types to the reference database (seeSpecification, page 507 for information about adding specifications to the database).

You can review the default and parameters settings while in the design file, using the SetRaceway Defaults command (see the section entitled Setup Commands for information aboutthis command). Your system manager should also tell you the project name and designfilename.

For additional system manager information, see the appendix entitled System/ApplicationManager Information and the section entitled Installation Instructions.

109


Drawing Setup

Define Systems and Set Active Systems

Every one-line type is part of a system that reflects the purpose of the raceway. You musthave at least one raceway system defined and active in the design file.

Use the Define System command to define your system(s) for the design file from thereference database. The command displays all systems available in the reference database. Ifyou need systems not available to you, ask the system manager to add them to referencedatabase. See Define System, page 258 for more information.

Then, use the Set Active System command to specify the system you want active as you aredrawing raceways. You can change the active system throughout the design session. SeeSet Active System, page 295 for more information.

Define One-Line Type and Set Active One-Line Type

Just as you must define systems from the reference database in the design file and set anactive system, you must have at least one one-line type defined and active in order to drawraceways.

Use the Define One-Line Type command to define one-line types for the design file from thereference database. The command displays all one-line types available in the referencedatabase. If you need one-line types that are not available to you, ask the system manager toadd them to the reference database. SeeDefine One-Line Type, page 260 for more information.

Then, use the Set Active One-Line Type command to specify the one-line type you wantactive as you are drawing raceways. You can change the active one-line type throughout yourdrawing session. See Set Active One-Line Type, page 294 for more information.

Set Symbology

Once you have defined your systems and one-line types, you can change the defaultsymbology settings for them. Doing so involves two commands: Set Symbology Controland Symbology Control.

Use the Set Symbology Control command to define the matrix of systems and one-line typesfor the design’s symbology control. See Set Symbology Control, page 262 for moreinformation.

Use the Symbology Control command to review and modify the symbology settings forthose systems and one-line types you selected with the Set Symbology Control command.You can also review and modify the default symbology settings with this command. SeeSymbology Control, page 264 for more information.

110

6. Wo

rkflow

Drawing Setup________________

Set Active Parameters

Each one-line type has its own set of parameters or catalogs. As you place one-line segments,you are also placing the data associated with that one-line type in the reference database intothe design file for loading later into the project database. To review and modify this data youwill use the Set Active One-Line Parameters command. See Set Active One-Line TypeParameters, page 289 for more information.

Set Propagation Parameters

Before you propagate one-lines in your model, you should review the active propagationparameters. These parameters determine how the system defines fittings, what one-lines willbe propagated, and whether or not certain commands will automatically propagate one-lines.To review and modify these parameters you will use the Propagation Setup command. SeePropagation Setup, page 297 for more information.

111


Place One-Line

You will place all one-lines, regardless of type, using the Place One-Line or Place ManualFitting commands, and the Precision Input form. SeePlace One-Line, page 132 ; Place Manual Fitting, page 147 ; andPrecision Input Form, page 119 for more information on these commands. To draw araceway, first place one-line segments (centerlines) in connected groups called runs. A run isa group of connected segments that do not branch or change specification. initially inphantom mode, placing tentative segments, until you accept them with the Accept option onthe Precision Input form. If not accepted, a phantom run disappears.

When you accept the run, it becomes a permanent part of the design file (unless you laterchoose to delete it). An accepted run has a Raceway Connect Point (RCP) attached to eachend of the run. Each run has a cross section on each end depicting the type of raceway and itsorientation (for trays and wireways).

The following figure displays the parts of a run.

Once you place and accept a run, you can continue placing one-lines. See DesignCommands, page 129 for a description of the Place One-Line command.

112

6. Wo

rkflow

Propagation________________

Propagation

A one-dimensional raceway is composed of one-line segments. To convert this one-dimensional view of the raceway to a three-dimensional view, use the Propagate command,see Propagate Element, page 194 for more information.

When you propagate a one-line segment into a three-line element, the three-line element’sshape is determined by the one-line type (tray, for example). The length of each three-linesegment is determined by the length of the one-line, and the width and height (or diameter) ofa segment are determined by the active parameters when you placed the one-line. The defaultfitting radius determines the radius of any bends between raceway segments. This radius isused to propagate fittings between straight segments.

Sketch and Eden Modes

There are two modes of propagation in EE Raceway: Sketch and Eden.

Sketch: In sketch mode, one-lines are propagated into three-lines based on the cross sectionand the radius, extension, and transition information stored for the one-lines and RCPs.Sketch is the quicker mode of propagation for two reasons. First, all information necessaryfor sketching the three-line is stored in the design file, so reference database access is notrequired. Second, the three-dimensional elements are drawn in-line without accessing theEden symbol library.

Sketch propagation places the sketched fittings based on the environment in which the one-lines come together. For example, where two tray sections come together at a 90 degreeangle, propagation will automatically sketch a 90 degree elbow.

Eden: In Eden mode, one-lines are propagated into three-lines based on the specificationinformation. The system analyzes the environment in which the one-lines meet whendetermining the type of fitting to place. It then searches the database for the appropriate partfor the proper specification. Once found, the specification dimensions and part informationare sent to the Eden symbol library where the symbol is generated.

While this mode of propagation is considerably slower than sketch, it allows you to define theshape of your fittings. For example, EE Raceway provides rounded tray elbows. If yourequire mitred elbows for production, you can define the fitting through Eden. Edenpropagation allows you greater detail and accuracy in three-dimensional fitting design. Thismay be particularly useful for later interference detection.

Manual Fitting Placement

You can place fittings manually in the design file using the Place Manual Fitting command,see Place Manual Fitting, page 147for more information. You can use manual placement in situations where placing a sparsemodel will not be sufficient or is not possible. For example, you may need to place fittingsmanually when dealing with tight spaces, unusual angles, or fitting-to-fitting placement. Allspecial fittings (conduit bodies, pullboxes, and light fixtures) must be placed manually.

113

EE Raceway Modeling Reference Guide - February 2003________________ Fittings placed through the manual placement command are Eden symbols. Anyrepropagation of such fittings will yield the same Eden symbols as well, regardless of theactive propagation mode. This ensures that fittings will always be repropagated with the sameorientation, definition, and specification.

After propagation (whether performed in sketch or Eden mode), the one-line elements remainin the design file. You can turn off the one-line levels for display and plotting purposes.

To highlight errors that occur during propagation, select the Highlight Propagation Errorscommand, seeHighlight Propagation Errors, page 314 . For a detailed description of these error messages,seeError Messages, page 377 .

Seamless Tubing Representations

In the following three-line representation of a bent conduit, the corners that do not have anRCP display circles that make the bent conduit look like an elbow. You have the option ofhiding these circles by turning off level 63, thus displaying a more realistic graphicalrepresentation of seamless tubing. In order for the circles to be placed on level 63, thepropagation mode must be set to sketch.

114

6. Wo

rkflow

Databases________________

Databases

A basic understanding of EE Raceway databases is necessary for efficient use of the software.For the purposes of this discussion, a database is a collection of information about racewaymodels. There are two databases that can be associated with your drawing: the referencedatabase and the project database.

Reference Database

A large amount of annotation is used in raceway models. Much of this annotation isrepetitious and not unique to any element in the drawing. The EE Raceway referencedatabase provides a simple method for generating this repetitious annotation. The referencedatabase automatically supplies default annotation values for the project database. (Thesystem manager may customize these values.) You can also add this information to thisdrawing using the Annotate Element command.

The default annotation can be associated with RCPs, one-lines, three-lines, and title blocks.For title blocks, the default can be unique for each title block cell. The Raceway parameterinformation is supplied from the vendor catalog in the reference database, using theannotation forms.

Override Keys

EE Raceway supports EE reference database override keys. The override key gives you theability to add to and/or modify default database information for RCPs, one-lines, three-lines,and title blocks. The override key acts as a pointer to a row of data in the EE referencedatabase. The default annotation information, supplied by the reference database, can now beoverridden by specifying another valid database key.

The Annotate Element command is used to place and modify the override key linkages. Theform that displays with this command contains the reference database key value in a separatefield below the annotation input area (see Annotate Element, page 178 ). You can both key inoverride values and display different annotation information.

Project Database

The project database contains information about all the particular elements (RCPs, one-lines,three-lines, title blocks) in each drawing in a project. The project database is normally createdwhen the project is created. (The project database can be created any time before the LoadDatabase process is run.) It will contain information about a particular drawing only after theLoad Database process has been run on that drawing. Once the project database is loaded,you can report on this information using the reports available through the EE RacewayDrawing Menu.

115

EE Raceway Modeling Reference Guide - February 2003________________ With the addition of RIS to the EE Raceway product, a distinction is now made betweenschema and database. The database is the file where the non-graphic drawing data (one-lines, three-lines, etc.) are stored. A schema is a RIS-specific file that contains a descriptionof the columns and tables of the database, and also identifies which users will be allowed touse the database.

116

6. Wo

rkflow

Reports________________

Reports

Currently, there are several reports delivered with the EE Raceway Modeling software: fourstandard reports and a rule check report. You can access these reports from the EE RacewayDrawing Menu by selecting the Report option. These reports run on the project and referencedatabases.

See Electrical Engineer (EE) Raceway Environment, page 59 for general information aboutrunning reports. For more detailed information about the individual reports, see Reports,page 545 .

117


Interference Detection

Interference detection is processed through Plant Design software. However, the EERaceway Modeling product creates an envelope file for input to the Plant Design interferencedetection task.

You will use the Interference Detection Envelope File Creation process to create theenvelope file needed for interference detection. This process reads the design file and thencreates a data file that contains envelopes (spaces in which valid raceway shapes reside).

See Create Interference Envelope (default name), page 342 for more information about theInterference Detection process.

118

7. Precisio

n

Inp

ut

Precision Input Form________________

7. Precision Input Form

This chapter describes all the options available on the precision input form and how to usethem. Since you will use the form with a number of commands, refer to the individualcommand sections for a description of operating sequences. For each command, the formdisplays the active command name as its title.

The precision input form is used to:

Accept/reject/cancel in response to the active prompt.

Identify an absolute point

Specify a delta coordinate to move.

Specify an absolute coordinate to move.

Specify a series of coordinate changes to move.

When you select a command from the menu, a precision input form displays and remains inview as long as you are working in the command. This section describes each button andfield available on the precision input form.

Several designs of the precision input form are delivered with EE Raceway.See System/Application Manager Information, page 415 for instructionsabout changing the form design.

119


View

This field displays the active working view. The displayed view determines the orientation ofthe elements you are placing in the design. The orientation of elements is most visible whenplacing annotation.

Pressing <D> in a view for the placement of points simultaneously overridesthe active view setting.

To change the displayed working view, select the field, and scroll through the available viewsuntil the appropriate view displays.

Maximize/Minimize

Enlarges the form to its maximum size or reduces the form to its normal size.

Cancel

Terminates the active command, while collapsing the precision input form. You can exit acommand at any point by selecting Cancel.

Reject

Enters a negative response to an active prompt. It can also reset a current command action byone step. In most cases, Reject performs the same actions as pressing <R>.

Accept

Enters an affirmative response to an active prompt. It also accepts any information you haveentered through the form, and prompts the system to continue to the next step. In most cases,Accept performs the same actions as pressing <D>.

120

7. Precisio

n

Inp

ut

Precision Input Form________________

Move/Move To Toggle

Used to specify a delta distance or absolute coordinates, and direction. Aset of directional buttons accompanies each option. Both options acceptkey-in for distance, while only Move To accepts a data point for input.

The Move (delta move) toggle allows you to specify the distance anddirection to place an active point. Using Move, you will select a directionalbutton and key in a distance to place a point. For example, by selectingNorth and keying in 20, you move to a point that is 20 master units northof the original active point.

The Move To (absolute move) toggle allows you to place an active point atan exact coordinate. Using Move To, you will select a directional buttonand key in an absolute coordinate. For example, by selecting North andkeying in 20, you move to a point that is at coordinate 20 (in master units)in the north direction.

Display Fields

Displays some of your active parameters and general messages. The top field displays theactive system and one-line type. The middle field displays the active one-line typespecification description. The bottom field displays various precision input messages.

Active Point Coordinates Display

The Active Point Coordinates display shows the coordinates of the active segment point.The coordinates display in the following order:

East/WestNorth/SouthElevation

The following two options are only available when placing ductbanks.

121


Justification Point

The justification point defines the location of the three-line duct bank graphic in relation tothe one-line graphic. Three justification points are available: lower left, lower center, andlower right.

By using the justification point and the height and width option described below, you canbuild duct bank elements similar to the one shown below.

Height and Width

These fields are used to define a ductbank element’s dimensions during placement.

122

7. Precisio

n

Inp

ut

Construct Point________________

Construct Point

This command specifies a series of movement options before accepting the shortest distanceto the displayed location. In Construct Point mode, you can route segments non-orthogonally. You may place as many points as you want in this mode, but they are onlytentative until you select the Accept button. If you do select Accept, only the coordinates ofthe last point you placed are accepted by the command. Selecting the Reject buttondiscontinues the command and returns you to the last point you placed before enteringConstruct Point mode.

Midpoint/Any Point on Segment

This command identifies a midpoint or any point on a segment at which to place an activepoint. When you select the command, a toggle displays with the following options:

The Midpoint option finds the midpoint of a specified one-line.When you identify a one-line, the option calculates and then entersits midpoint.

The Any Point option allows you to identify either end of a segmentand then specify a distance along that segment at which to place apoint. The operating sequence for the Any Point option is:

1. Activate the Any Point option.

Select the Midpoint/Any Point command on the precisioninput form, and set the toggle to Any Point if it is not alreadyactive.

2. Identify Raceway One-Line Segment

Identify the one-line segment on which you intend to place apoint.

The command highlights the identified segment.

3. Raceway one lineAccept/reject

Press <D> to accept the one-line segment.

The command highlights one of the segment’s endpoints.

— OR —

Press <R> to reject the segment, and return to the previousstep to identify another one-line.

123


4. Accept/reject end point

Press <D> to accept the highlighted endpoint as your referencepoint.

— OR —

Press <R> to highlight the other segment endpoint, and thenpress <D> to accept it as the reference point.

5. Specify Distance

Key in the distance from the reference point to the point youwant to enter, and select Accept.

The command calculates the distance from the endpoint andthen enters the point on the segment. If the specified distanceexceeds the length of the one-line, the command stillcalculates the point from the endpoint, moving in the directionof the segment.

— OR —

Select Accept to enter the active endpoint.

— OR —

Press <R> to return to Step 2.

124

7. Precisio

n

Inp

ut

Extend/Reduce Run________________

Extend/Reduce Run

The Extend/Reduce Run command allows you to extend or reduce the length of anupcoming run by the value you specify. The command accepts as values the height and widthof the active one-line type (as defined in its specification), or any distance you key in.

You cannot use this command to place a first point. You must already have defined an activepoint to establish the active direction before using Extend/Reduce Run.

When you select the command, the following toggles display:

The Extend Run toggle allows you to increase the length of anupcoming run by the value you specify.

When you select the Height or Width buttons, the Full/Half toggledisplays. Using the toggle, you can enter the full height/width of theactive one-line type, or half the height/width of the active one-linetype as the distance by which to extend the run. The distancedisplays at the bottom of the form. Only after you select Accept willthe system extend the upcoming run by the displayed distance.

When you select the Distance button, you must key in a value bywhich to extend the run. The distance you key in displays at thebottom of the form. Only after you select Accept will the systemextend the run by the displayed distance.

The Reduce Run toggle allows you to reduce the length of anupcoming segment by the value you specify.

When you select the Height or Width buttons, the Full/Half toggledisplays. Using the toggle, you can enter the full height/width of theactive one-line type, or half the height/width of the active one-linetype as the distance by which to reduce the run. The distancedisplays at the bottom of the form. Only after you select Accept willthe system reduce the upcoming run by the displayed distance.

When you select the Distance button, you must key in a value bywhich to reduce the run. The distance you key in displays in masterunits at the bottom of the form. Only after you select Accept willthe system reduce the run by the displayed distance.

125


Distance and Direction

The Distance and Direction command specifies the distance and direction from an activepoint to place a point or vertex. You can define distance with this command using the MoveTo and Move toggles or by specifying the true length from an active point. You can definedirection by keying in values for horizontal and vertical angles.

Steps

1. Select the Distance and Direction command from the main precision input form.

The Distance and Direction form displays. The coordinates of the active point and theangles of the active direction are displayed on the form.

2. Specify Distance/Direction

You can define the distance in one of three ways:

Distance - Define the true length from the active point in the direction to bedefined.

Move to - These options define the absolute coordinate for the point in thedirection to be defined. Select the direction and key in the absolute coordinate orsnap to an element to retrieve its corresponding coordinate.

Move - These options define the change in the selected coordinate for the point inthe direction entered.

3. You can define the direction from the active point one of two ways:

Active Direction - The direction is defined by the active horizontal and verticalangles initially displayed.

Angles - Key in the horizontal angle and the vertical angle in decimal degrees.Negative values are acceptable.

126

7. Precisio

n

Inp

ut

Distance and Direction________________

The direction is always determined by both the horizontal and thevertical angles.

The horizontal angle can be measured clockwise or counterclockwise. If clockwise, thehorizontal angle starts at the North coordinate (zero degrees). If counterclockwise, thehorizontal angle starts at the east coordinate (zero degrees). This option is set in thePDS product. The default setting is clockwise.

The vertical angle is measured up or down from the horizontal plane of the active point.

4. Accept/Reject Distance and Direction

Select the Process button to accept the displayed distance and direction and return tothe main Precision Input form.

— OR —

Select the Reset button or press <R> to reject the distance and direction option andreturn to the main Precision Input form.

— OR —

Select the Cancel button to terminate the active command.

Runtime Setup

The Runtime Setup command is used to define, modify, and review the active drawingparameters in your design file. SeeRuntime Setup Commands, page 287 for more information on the available commands.

127


128

8. Desig

n

Design Commands________________

8. Design Commands

The Design palette is activated by selecting Design from the EERWAY Command Menu Bar,then selecting Palette from the resulting pull-down menu.

The commands on this palette place raceway elements – one-lines, manual fittings, racewayconnect points (RCPs), drop points, and equipment pointer symbols – in the design file. Youcan also use these commands to enter an active point, change the active design parameters,rotate cross sections, and size conduit and duct banks. There are also commands available forrouting one-lines around vessels and for inserting vertices in an existing one-line.

Commands

Place One-Line — Places the centerlines of raceway elements.

Route Around Vessel — Routes elements parallel to an arc, circle, and right cylinder.

Insert RCP — Places a raceway connect point (RCP) in your raceway model.

Rotate Cross Section — Rotates a cross section at the current cross section angle.

Place Drop Point — Places a drop point symbol in the design file.

Place Equipment Pointer — Places an equipment pointer symbol in the design file.

Define Active Point — Places an active point in the design file.

Set Active Parameters — Sets the active parameters in the design file based on anidentified one-line or RCP.

Place Manual Fitting — Places a manual fitting in the design file at the specifiedorientation and location.

129


Conduit Sizing — Sizes conduit by "placing" cables in the conduit to determine the percentfill.

Insert One-Line Vertex — Places a vertex in an existing one-line.

Place Field Routed Raceway — Places short raceway sections from the raceway model toequipment. These sections represent raceway components that are field routed by theinstaller.

Define Duct Cross Section — Defines the cross section configuration of the containedconduit for an underground conduit duct bank.

Place Stub Up — Places conduit stub ups from an underground ductbank.

130

8. Desig

n

Using the Design Commands________________

Using the Design Commands

When to Use These Commands

Once you have performed the necessary setups, you can use these commands throughout thedesign session.

Before Using These Commands

These commands require that you have an active system and one-line type defined in thedesign file. See Setup Commands, page 253 andRuntime Setup Commands, page 287 for instructions about setting up your systems and one-line types.

You must have conduit one-lines placed in the design file before you can use the ConduitSizing command. Likewise, you must have ductbank one-lines placed before you can use theDefine Duct Cross Section command.

You must be familiar with precision input and its functions before using any of the Designcommands, because it is through the Precision Input form that you will enter values for theplacement of points and for the location of raceway elements. For detailed information aboutprecision input, seePrecision Input Form, page 119 .

Group Workflow

There is no required or suggested sequence for using the commands in this group.

Operating Information

During the operating sequence for any of these commands, you can exit the command sessionby pressing <Esc> or by selecting Cancel (X) on the precision input form. Pressing <R> orselecting Reject on the precision input form will either reset the active command by one stepor reject a highlighted element in the design file.

131


Place One-Line

This command places the centerlines of raceway elements based on points you give it. Theactive one-line type determines the type of one-line you place (tray, conduit, and so forth),while the active system determines the system to which the one-line belongs. Active racewayparameters supply the default data associated with each one-line segment as you sketch.

One-line routes begin and terminate with a raceway connect point (RCP). RCPs are requiredwhen you are changing the system, one-line type, or specifications of a one-line, or when youplace a fitting. Whenever you begin or terminate a one-line segment, you will have at leastone of five possible routing options. The following list describes each routing option indetail:

New RCP — If you do not identify a one-line or RCP for the beginning and/ortermination point, the system places a new RCP and routes the one-line from/to theRCP. Any one-line segment you are placing in space, unattached to another element, isnew.

Break One-Line — If you identify a one-line for the beginning and/or terminationpoint, the system places a new RCP and breaks the existing one-line into two one-linesegments. These two segments will retain the systems, one-line type, racewayparameters, and annotation of the original one-line.

Continue One-Line — If you identify an RCP for the beginning and/or terminationpoint, you can resume routing an existing one-line. You can also combine two existingone-line segments using Continue.

Attach to RCP — If you identify an RCP for the beginning and/or termination point,you can attach to an existing RCP. This allows you to use the existing RCP as abeginning and/or termination point.

Connect to One-Line — If you identify either a one-line or an RCP for the beginningand/or termination point, you can connect to an existing one-line. Connect will place adrop point cell on the identified one-line at the point of identification. Drop pointsestablish connectivity between one-lines and RCPs where they are of different one-linetypes.

Valid connections to one-lines are determined by the priority level assigned to eachone-line type in the database. The values are defined by the ee_priority_levelcolumn in the ol_type table. One-line types with lower priority can only connect toone-line types with higher priority. If the priority levels are equal between one-linetypes, then connect will not be an option.

The chart below illustrates the parameters that are assigned to one-lines as you place ormodify them, based on every possible combination of routing options.

132

8. Desig

n

Place One-Line________________

In the above chart:

Active — Indicates that the one-line you are placing is assigned the active racewayparameters.

Last — Indicates that the one-line you are placing is assigned the parameters of the lastone-line you identified.

First — Indicates that the one-line you are placing is assigned the parameters of thefirst one-line you identified.

You should keep the following points in mind when using the Place One-Line command:

If an RCP on the end of a one-line belongs to a manual fitting, the command will notallow the continue option.

You can attach to or continue manually placed straights.

If you reject all routing options for the beginning and/or termination points of a one-line, then the command places a new RCP by default. This allows RCPs to be placedon top of one another without establishing connectivity, though it is not a recommendedpractice.

If the beginning or termination action is break, attach, or continue, then the identifiedone-line or RCP must have at least one system in common with the active systems.

If the beginning and termination actions are continue, then the two identified one-linesmust have all systems in common.

If the beginning or termination action is break, attach, or continue, then the identifiedone-line must be of the same one-line type as the active one-line type.

133


Before Using This Command

You can enter all values for the placement of points through a precision input form. Using theform, you can locate elements, route one-lines, accept input, reject input, reset a commandaction, and exit a command. You must be familiar with precision input and its functionsbefore using this command. For detailed information about precision input, see PrecisionInput Form, page 119.

At any point during this operating sequence, you can exit the command session either bypressing <Esc> or by selecting Cancel (X) on the precision input form. To reset a commandaction by one step or to reject a highlighted element, press <R> or select Reject on theprecision input form. You must set an active one-line type and system in the design file. SeeSet Active One-Line Type and Set Active System in Runtime Setup Commands, page 287 .In addition, you should be familiar with the Set Raceway Defaults command (see SetRaceway Defaults, page 256 ).

Steps

1. Select the Place One-Line command.

The Place One-Line precision input form displays.

2. Begin entering points to sketch the one-lines. Refer to the description of routingoptions at the beginning of this section to determine proper routing.

3. Complete the routing.

The system places cross sections and RCPs (if they do not already exist) on the ends ofthe one-line.

4. Data Point Accepts, Reset Rotates

Press <D> to accept the cross section rotation, and return to step 2.

The system saves the rotation and returns to the beginning of the command, promptingyou to Enter first data point.

— OR —

Press <R> to rotate the cross section by the rotation angle defined in RacewayDefaults.

The system rotates the cross section and prompts you again to accept or continuerotating it.

134

8. Desig

n

Route Around Vessel________________

Route Around Vessel

This command routes the active one-line type around a vessel (represented by an arc, circle, orright cylinder) selected in either the active or reference design file. The arc, circle, or rightcylinder element can be a single MicroStation element, or part of a cell.

The route is attached to two terminating RCPs which may or may not have a fitting on them.If the RCP has a fitting on it, the fitting angle will be used when routing off the RCP andaround the vessel. If the RCP does not have a fitting, the route will come off the RCP at a 90degree angle to the one-line.

A fitting on the RCP can only have two attach points, such as an elbow. Wyeand tee fittings cannot be used.



At any point during this operating sequence, you can exit the command session either bypressing <Esc> or by selecting Cancel (X) on the precision input form. To reset a commandaction by one step or to reject a highlighted element, press <R> or select Reject on theprecision input form.

135


Steps

1. Select the Route Around Vessel command.

The precision input form displays.

2. Identify first RCP

Select the RCP where you want the route to begin and press <D> to accept it.

— OR —

Press <R> to exit the command.

3. Identify second RCP

Select the RCP on the other side of the vessel where you want the route to end and press<D> to accept it.

— OR —

Press <R> to back up one step and respecify the first RCP.

4. Identify vessel to route around

Select the vessel (the arc, circle, or right cylinder element) between the RCPs, whichyou want to route around and press <D> to accept it.

— OR —

Press <R> to back up one step and respecify the second RCP.

5. Key in minimum distance from vessel

Key in the minimum distance, the closest, the route can be placed to the vessel. Youcannot key in a negative value.

The route is not placed at the minimum distance from the vessel all theway around. The minimum distance key-in defines the closest the routecan come to the vessel.

If you want the route to maintain the minimum distance all the wayaround the vessel, be sure that the distance from the RCPs to the vesselis the same as the minimum distance you key in.

— OR —

Press <R> to back up one step and respecify the vessel to route around.

136

8. Desig

n

Route Around Vessel________________

6. Key in the number of one-line segments

Key in the number of one-line segments to use when routing around the vessel. Thenumber of segments must be greater than one (two segments or more).

The route is calculated and the elements display on one side of the vessel.

— OR —

Press <R> to back up one step and key in a new minimum distance from vessel value.

7. Accept/reject

Press <D> to accept that the elements should be placed on that side of the vessel.

— OR —

Press <R> to place the elements on the other side of the vessel.

— OR —

Press <R> twice to back up one step and key in a new number of one-line segments.

137


Insert RCP

This command breaks an identified one-line in the design file and inserts a raceway connectpoint (RCP).




Steps

1. Select the Insert RCP command from the menu.

The Insert RCP precision input form displays.

2. Identify Raceway One-Line

Identify a one-line in the design file.

The system highlights a valid one-line. If you do not locate an acceptable one-lineelement, the system displays the message Element not found. The messagedisappears when you identify a valid element.

138

8. Desig

n

Insert RCP________________


Accept or reject the highlighted one-line.

If you accept the one-line, the command inserts the RCP as specified.

— OR —

If you reject the one-line, the system prompts you to identify another. Go to Step 2.

4. Continue inserting RCPs. Go to Step 2.

— OR —

Exit the command.

139


Rotate Cross Section

This command rotates a cross section using the current cross section rotation angle. For ductbank cross sections, this command does not rotate duct bank’s cross section, but changes theduct bank justification location.

You can change the rotation angle in the EE Raceway Defaults form, see Set RacewayDefaults, page 256 for more information.




Steps

1. Select the Rotate Cross Section command.

The Rotate Cross Section precision input form displays.

2. Identify Cross Section

Identify a cross section and accept it with a <D>. If you identified a duct bank crosssection, go to step 4. Otherwise continue to step 3.

140

8. Desig

n

Rotate Cross Section________________ The system highlights a valid cross section. If you do not locate an acceptable element,the system displays the message Element not found. The message disappears whenyou identify a valid cross section.

— OR —

Exit the command.


Press <D> to accept the current cross section orientation and exit the command.

If Automatic Propagation is on, the elements will repropagate at the new orientationangle.

— OR —

Press <R> to rotate the cross section.

The system rotates the cross section by the defined rotation angle. See Set RacewayDefaults, page 256 for information about changing the angle of rotation.

Repeat this step.

4. Select New Cross Section Justification

Select a new justification point from the precision input form and accept it.

The duct bank justification changes and the command exits.

141


Place Drop Point

This command places a drop point symbol in the design file. Drop points establishconnectivity between a RCP and a one-line. You can place drop points between RCPs andone-lines of the same and/or different one-line type.

Valid connections to one-lines are determined by the priority level assigned to each one-linetype in the database. You can, for instance, establish connectivity between a piece of conduitand a tray at the point where the cables drop out of the tray into the conduit. You can alsoestablish connectivity between two one-lines where graphic coincidence does not occur.

The values which determine priority status are defined in theee_priority_level column in the ol_type table; a higher numberindicates a lesser priority. For example, 10 is of lesser priority than 5.

The point on the one-line where you place the drop point symbol defines the drop-out point.If the drop point symbol is not on the one-line, the drop-out point will be calculated bydetermining the closest point on the one-line to the drop point symbol.




Steps

1. Select the Place Drop Point command.

The Place Drop Point precision input form displays.

2. Identify Raceway RCP

Identify an RCP in the design file.

The system highlights a valid RCP. If you do not locate an acceptable element, thesystem displays the message Element not found. The message disappears when youidentify a valid RCP.

142

8. Desig

n

Place Drop Point________________

3. Raceway connect pointAccept/reject

Accept the highlighted RCP.

— OR —

Reject the highlighted RCP.

The system prompts you to identify another RCP. Go to step 2.


Identify a one-line in the design file. The identification point is the point at which thesystem will place the drop point.

The system highlights the identified one-line.

— OR —

Press <R> or Reject to identify a different RCP. Go to step 2.


Accept the one-line.

The system places the drop point as specified, and returns you to the previous prompt.

— OR —

Reject the one-line.

The system prompts you to identify another one-line.

Go to step 4.

143


Place Equipment Pointer

This command places an equipment pointer symbol in the design file. An equipment pointersymbol serves as a tag that identifies a particular piece of equipment. The equipment pointershould match the corresponding symbol in the PDS Equipment Modeling product.




Steps

1. Select the Place Equipment Pointer command.


Identify an RCP in the design file and accept it.

The system highlights a valid RCP. If you do not locate an acceptable element, thesystem displays the message Element not found. The message disappears when youidentify a valid RCP.

— OR —


3. Enter data point to place

Place a data point at the desired location for the equipment pointer symbol.

The system places the equipment pointer symbol as specified.

Continue placing equipment pointer symbols in the design.

— OR —

Press <R> to select another RCP.

144

8. Desig

n

Define Active Point________________

Define Active Point

This command defines a new active point in your design file.




Steps

1. Select the Define Active Point command.

The Enter Active Point precision input form displays.

2. Enter active point

Specify a data point in the design file where you want the active point to be.

The command makes the specified data point the active point, and exits the command.

145


Set Active Parameters

This command sets the active parameters; active systems, one-line type, and racewayparameters; to those of a one-line or RCP you identify.




Steps

1. Select the Set Active Parameters command.

The Set Active Parameters precision input form displays.

2. Identify Raceway One-Line or RCP

Select a one-line or RCP to use to set the active parameters.

The system highlights the identified element.

— OR —


3. Accept/reject

Press <D> to accept the element as the one to use.

The system sets the active one-line type, system, and one-line type parameters based onthe highlighted element. The command exits automatically.

— OR —

Press <R> to reject the highlighted element. Return to step 2.

146

8. Desig

n

Place Manual Fitting________________

Place Manual Fitting

This command identifies a unique part from the reference database and places it in the designfile at whatever orientation and location you specify.

You will use manual placement in situations where placing a sparse model will not besufficient or is not possible. For example, you may need to place fittings manually whendealing with tight spaces, unusual angles, or fitting-to-fitting placement. You can placespecial fittings (conduit bodies, pullboxes, and light fixtures) as well as spec driven fittings(horizontal elbows, vertical tees, and so forth) using this command.

During placement, the location of a manual fitting is determined by the location of the activepoint. If the active point lies in the vicinity of a fitting, the system locates the closestattachment point on that fitting. If the new fitting and the existing one do not share the samesystem and one-line type, then the system places the new fitting by itself. Such a fitting isplaced with its own RCP. When placing a straight section, or placing a fitting on the end of astraight section, the system extends the one-line for that straight to terminate on the RCP ofthe fitting. Otherwise, the new fitting is attached to the existing fitting and a one-line isautomatically placed.

When attaching a manual fitting to the placement point of another fitting (or a straight), thesystem derives the default orientation for placing the new fitting from the placement point.

147


Commands

Define Active Point — Defines the active point in the design file for the placement offittings. If manual placement cannot locate a fitting, the previous orientation will be retained.Otherwise, the command derives the orientation from the place point. See Define ActivePoint, page 145 .

Set Active System — Displays the current active system and allows you to select a newactive system. See Set Active System, page 295 .

Set Active One-Line Type — Displays the current active one-line type and allows you toselect a new active one-line type. Selecting a new active one-line type updates the partinformation elsewhere on the form. See Set Active One-Line Type, page 294 .

Set Active Parameters — Defines the active system, one-line type, and active one-line typeparameters in the design. Changing the active parameters updates the part informationelsewhere on the form. See Set Active Parameters, page 146 .

Field Descriptions

Type — Displays the active three-line type for the current specification. The listcontains all available three-line types (elbow, straight, wye, etc.) for that specification.To change the displayed three-line type, select a value from the list. Modifying thevalue in the Part field may also change the active and available Type values.

Subtype — Displays the active subtype for the displayed Type value. The list containsall available subtypes (vertical, horizontal, inside vertical, etc.) for the active type andsubtype in the current specification. To change the displayed subtype, select a valuefrom the list. Modifying the value for Type also may change the active and availablesubtypes.

Qualifier — Displays the active qualifier for the displayed Type and Subtype. The listcontains all available qualifiers (adjustable, rigid, etc.) for the active type and subtype inthe current specification. To change the displayed qualifier, select a value from the list.Modifying Type or Subtype values may change the available qualifiers.

148

8. Desig

n

Place Manual Fitting________________ Symbol — Displays the name of the Eden symbol you are placing. You can onlyreview the values in this field.

Angle — Displays the active angle associated with the Type, Subtype, and Qualifierfor the current specification. The list contains available angles. To change thedisplayed angle, select an angle from the list or select the field, and key in the newvalue.

When placing a fitting (such as a vertical tee), if the placepoints andRCPs do not line up correctly, key in a negative angle, (-90 degrees) toshift the RCPs and placepoints to the correct location.

Length — Displays the length by which to project a straight. If straight is not youractive Type, the Length field does not display on the form. To change the displayedlength, select the field, and key in the new value.

Part — Displays the active part. The list contains all available parts for the currentspecification. To change the displayed part, select a value from the list.

— OR —

Change any of the values for Type, Subtype, Qualifier, Spec1, (if applicable) Spec2,or Angle (if applicable).

Spec1 — Displays the active specification for the displayed Type, Subtype, andQualifier. The list contains all available specifications. To change the displayedspecification, select a value from the list.

To display the specification itself, select the corresponding Display button. Doing sodisplays a specification form.

149

EE Raceway Modeling Reference Guide - February 2003________________ Column name - Displays the aliases of those columns in the database that areassociated with the specified type. You can only review the information in this column.

Column value - Displays the column name values currently associated with thespecified type. You can review and modify the values in this column. To change avalue, select the Override button. Then select the field, and key in a new value.

List - Indicates whether or not a column value has an associated codelist. If an *displays in the List column, then the column value has an associated codelist. Todisplay the codelist, select the *.

Select - Retrieves the row(s) from the specification table that meet the select criteriadefined in the form. If only one row matches this criteria, then the Column values fillin with the matching row’s values. If more than one row matches the criteria, then asecond form, containing all matching rows, displays.

You can use certain relational operators as search criteria. For a list ofvalid operators, see Annotate Element, page 178 .

Clear - Clears the Column values from the lower portion of the form, and thenautomatically depresses the Override button so that you can select a different row(s)from the specification.

Override - Allows you to override those columns whose access is Read Only (R). Youcan activate the Override button by selecting it directly or by selecting the Clearbutton, which automatically activates it.

Spec2 — Displays the active secondary specification, if any, for the given Spec1,Type, Subtype, and Qualifier. The list contains all available secondary specificationsfor the current settings. Secondary specifications are generally used with reducers.

You can display the current specification itself by selecting the Display button. Doingso displays a specification form. See Spec1 for a description of the form.

Overrides from the secondary specification are not passed to the Edensymbol.

Placepoint — Defines the point of attachment for the fitting you are currently placing.To change the active placepoint, select the slide bar, and drag it along the scale until itreaches the appropriate value.

Cutback Mode — Defines whether a straight section is to be cutback when placing amanual fitting. If Cutback Mode is on, the existing RCP location is fixed. If CutbackMode is off, the RCP will be moved accordingly.

150

8. Desig

n

Place Manual Fitting________________ Automatic Size — Automatically selects the correct size fitting. You must specify themanual fitting type before using the button.

The fitting size is determined by comparing the spec table nominal size of all one-linesat the RCP and selecting the largest nominal size among them. That nominal size isthen compared to the fitting table nominal sizes. If in the fitting table there is a nominalsize the same as the largest one-line nominal size, then that fitting is used. If there is nofitting of that nominal size, then the first fitting that is of greater nominal size than theone-line nominal size is used. If there is no nominal size fitting larger than the one-linenominal size, then the largest fitting available is used.

Automatic Fit — Re-orients the fitting in reference to the one-line it is associated with.

Rotate Orientation — Defines the active orientation matrix.

Angle - Defines the angle by which to rotate the orientation tee. To change thedisplayed angle, select the field, and key in a new value.

About - Defines the axis about which to rotate the orientation tee. To change thedisplayed axis, select the field, and toggle between the three axes (Primary,Secondary, Normal) until the appropriate axis displays.

— OR —

Identify the appropriate axis name (text) on the orientation matrix diagram (to the rightof the Angle and About fields.)

I Button — Reorients the orientation tee along the identity matrix. It realigns thePrimary axis with the positive X axis, the Secondary axis with the positive Y axis, andthe Normal axis with the positive Z axis.

If you set the Driven By Spec/Table toggle to Table, the Place Manual Fitting formdisplays.

151


Field Descriptions

Table — Displays the active special part table from the database. The list contains theavailable special part tables from the database. To change the active special part table,select a table name from the list.

Attribute — The next four display lists on the form are the first four Part Keyattributes from the active table and will change depending on which Table is active.The attribute display lists are used to interactively query the database for the desiredPart Key.

For example, you set the active Table to cond_body. size, type, material, and vendordisplay as the active attributes. Each attribute displays only those values that havecorresponding matching values for the other three attributes in the database. In otherwords, if you set material to feraloy, vendor to 3, and size to 1/2 inch, then only thosetypes that are 1/2 inch in size from vendor 3 and made of feraloy will be displayed inthe types list. Similarly, if you set type to form 7c, material to feraloy, and vendor to3, then only the sizes the form 7c comes in, made of feraloy from vendor 3, will bedisplayed in the size list.

Select/All toggles — Overrides the interactive queries of the attribute fields. When setto All, all available values for that attribute are displayed in the list, regardless of theother attribute settings.

Part Key — Displays the current part for the displayed Table that matches the attributevalues. Modifying the Table value also changes the active and available Part values.

You can display the current table information for the part by selecting the Displaybutton.

See the description of the Spec1 field earlier in this section for detailed informationabout the form parameters.

For information about the Placepoint and Rotate Orientation fields aswell as the form commands, see the descriptions earlier in this section.These fields and the commands operate identically in either Driven BySpec or Driven By Table modes.

152

8. Desig

n

Place Manual Fitting________________


You should be familiar with precision input and its functions. For more information, seePrecision Input Form, page 119 .

When deciding whether your fitting information will come from a specification or from atable in the database, you should first consider a few points. Specification-driven fittings relyon the specification information (width, height, radius, etc.) to construct the three-linesymbols. All parts of a given specification will inherit the attributes of that specification. Onthe other hand, some fittings derive their information from their own database tables becausethey are not so easily classified into a common group of parts. Such fittings are called specialparts. The following table indicates fittings that are specification-driven and those that arespecial parts:

Specification-Driven Fittings Special Parts

straight pullboxelbow conduit bodywye light fixturecrossdropout

Steps

1. Select the Place Manual Fitting command.

The Place Manual Fitting form displays.

2. Set the Driven By Spec/Table toggle to meet your requirements.

To derive fitting attributes from a specification in the database, set the toggle to DrivenBy Spec.

— OR —

To derive fitting attributes from a special part table in the database, set the toggle toDriven By Table. Go to step 4.

3. Change fitting descriptions, orientations, and location until the desired fitting is seen indynamics (phantom mode) in the design file.

4. Select Accept to accept the fitting with the current settings, orientation, and location.

The system accepts the fitting at the specified location and orientation.

153


5. Continue placing manual fittings.

— OR —

Exit the command.

154

8. Desig

n

Conduit Sizing________________

Conduit Sizing

This command places cables (wires) in a conduit to determine the correct conduit size basedon the conduit’s percent fill calculation.

155


Field Descriptions

Column Alias — Displays the column aliases for each column in the database table.

Value — Select and key in values to use as search criteria to find corresponding cablesin the database. This command also accepts certain relational operators as searchcriteria. You should be familiar with the following operators:

Symbol Name DataType

Description

= equal to numeric This is the default operator. If you do not enter anotheroperator, the system assumes =.

> greater than numeric This operator indicates that the queried values shouldbe greater than the given value.

< less than numeric This operator indicates that the queried values shouldbe less than the given value.

>= greater thanor equal to

numeric This operator indicates that the queried values shouldbe greater than or equal to the given value.

<= less than orequal to

numeric This operator indicates that the queried values shouldbe less than or equal to the given value.

!= not equal to numeric This operator indicates that the queried values shouldNOT be equal to the given value.

% wild card CHAR This operator is a wild card, representing zero or morecharacters. The queried values must have everycharacter aside from the % in common with the givenvalue.

_ underline CHAR This operator is a wild card, representing a singlecharacter. The queried values must have everycharacter aside from the underline in common with thegiven value.

Code List — Indicates whether a Value has an associated code list. A code list is a listof valid database values for that Column Alias. If an * displays in the column, then theValue has an associated code list. To display the code list, select the *.

156

8. Desig

n

Field Descriptions________________ Initialize Query — Clears all entries in the Value fields.

Process Query — Queries the database to find cables matching the search criteriadefined in the Value fields. If only one cable is found that matches the criteria, it isadded to the conduit. If more than one cable matches the search criteria, the Pseudo-Cable form displays, from which you can select a cable or cables to route in theconduit.

Increase Size ONLY / Increase/Decrease size — Defines how the conduit should besized. There are two methods to choose from:

— Increase Size ONLY - When a conduit is calculated to be full, the next size largerconduit in the spec table is used until an adequately sized conduit is found.

— Increase/Decrease size - The smallest conduit available in the spec that meets thepercent fill criteria is used.

Percent Fill — Displays how full the conduit is as a percentage. The field displays inred and the message Warning: Percent Fill exceeds maximum allowed displayswhen the conduit has reached its capacity as defined by the electrical code you areusing. The Percent Fill calculation is based on the conduit’s cross-sectional areadivided by the summation of all of that conduit’s cables’ cross-sectional areas.

Conduit Size — Displays the size of the conduit in spec units.

Selected Cables — Displays information on all cables that have been selected to go inthe active conduit.

Select Conduit — Displays the Conduit Sizing precision input form. Using this formyou can select another conduit in which to route cables without having to exit thecommand.

Copy Contents — Copies cables from a selected conduit into the active conduit. Anycables in the active conduit before the copy are removed.

Append Contents — Adds cables from a selected conduit into the active conduitleaving any cables in the active conduit there.

Add Cable — Mode for adding cables to a conduit.

157

EE Raceway Modeling Reference Guide - February 2003________________ Remove Cable — Mode for removing cables from a conduit.

Delete All Cables — Deletes all cables in the active conduit. This option is availableonly when Remove Cable is selected.

Quantity — Defines the number of cables of that type. This field can be edited to takepositive integers other than zero (zero and blank are invalid entries).




You must use the Set Conduit Sizing Attributes command to define how the conduit sizeswill be selected. See Set Conduit Sizing Attributes, page 268 for more information.

Steps

1. Select the Conduit Sizing command.

The Conduit Sizing precision input form displays.

2. Identify CONDUIT

Identify the conduit to size and accept it with <D>

The Conduit Sizing form displays.

3. Define the cables for the conduit. You can query the database and select them from theform or copy them from a conduit that has "cable" in it.

4. Set the Increase size ONLY / Increase/Decrease size toggle to the sizing method youwant.

158

8. Desig

n

Field Descriptions________________

5. Select Accept to calculate and size the conduit.

If the largest size conduit available does not satisfy the percent fill calculation, awarning message displays.

— OR —

Select Cancel to exit the command and ignore any changes you have made.

159


Insert One-Line Vertex

This command places a vertex in an existing one-line. To move an inserted vertex, use theMove One-Line Vertex command, see Move One-Line Vertex, page 192 for moreinformation.




Steps

1. Select the Insert One-Line Vertex command.

The Insert One-line Vertex precision input form displays.

2. Identify Raceway One-line

Select the one-line to which to add the vertex.

The point that identifies the one-line in this step is the point where thevertex is inserted.

The selected one-line highlights.

3. Accept/reject

Press <D> to accept the one-line.

The vertex is inserted. If Automatic Propagation is on, the one-line will repropagateand the vertex will display with its cross-section.

— OR —

Press <R> to reject the one-line.

160

8. Desig

n

Place Field Routed Raceway________________

Place Field Routed Raceway

The Place Field Routed Raceway command places short raceway sections from the racewaymodel to equipment. These sections represent raceway components that are field routed bythe installer. For example, conduit less than a particular size is typically not modeled in theplant model but is installed in the field by the installer. Similarly, there are instances wherethe raceway does not terminate at equipment and cables must be routed through airways(space) by the installer from the raceway to the equipment. Field routed raceway sections areneeded to get appropriate material takeoff (MTO) reports and to facilitate cable routing. Thiscommand is intended primarily to support field routed conduit and airways, but can also beused for other raceway types that are field routed.

Field Descriptions

Column name — Displays the aliases for the columns (attributes) in the referenceschema that unique identify equipment. The column names reside in the ee_uniquetable in the reference schema. This field is informational only.

Column value — Defines a value for the corresponding equipment identifying attributein the Column name field. To change the value, select the field and key in the newvalue.

Display — Enables or disables the annotation of the Column value. When on, thevalue is displayed in the design. You are prompted to position the annotation after theequipment pointer is placed in the design.

Keyin/Calculate — Defines the method for entering the distance from the beginning ofthe placed one-line to the equipment (that is, field route length.)

When set to Keyin, you must key in the length in the Distance to equipment field.

The Distance to equipment specifies the field routed length (in subunits) of the placedone-line. This length represents the estimated length of raceway to the equipment fromthe beginning point of the placed one-line. To change the displayed length, select thefield and key in a new length.

161

EE Raceway Modeling Reference Guide - February 2003________________ When the Keyin/Calculate toggle is set to Calculate, you are prompted to identify thelocation of the equipment. The software calculates the orthogonal distance (that is, sumof the x, y, z deltas) from the beginning of the placed one-line to the identifiedequipment location. The calculated distance is stored with the one-line as field routedlength.

First Point & Orientation/Beginning & Ending Point — Defines the method forentering the plant coordinates of the one-line element. When placing the one-lineelement using the First Point & Orientation method the Rotate Orientation gadgetsdisplay.

After specifying the orientation and the length of the one-line, you are prompted for thefirst point (that is, placement point) of the one-line element.

When placing the one-line element using the Beginning & Ending Point method, youare prompted for the beginning and ending plant coordinates of the one-line.

Angle — Defines the angle by which to rotate the orientation tee. To change thedisplayed angle, select the field, and key in a new value.

About — Defines the axis about which to rotate the orientation tee. To change thedisplayed axis, select the field, and toggle between the three axis (Primary, Secondary,Normal) until the appropriate axis displays. Or you can identify the appropriate axisname (text) on the orientation matrix diagram (to the right of the Angle and Aboutfields.)


Length of Placed Raceway Field — Displays the length by which to project the one-line along the orientation tee from the first point. To change the displayed length, selectthe field, and key in a new value.




162

8. Desig

n

Place Field Routed Raceway________________

Operator Sequence

1. Select the Place Field Routed Raceway command.



Identify a one-line element to which you want to connect the field routed racewaysection and accept it when it highlights.

The Place Field Routed Raceway form displays.

— OR —

Exit the command.

3. Define the form parameters to meet your specifications.

163


Define Duct Cross Section

This command defines the cross section configuration of the contained conduit or cable forunderground duct banks. The duct bank will automatically resize after configuration toaccommodate the defined conduit or cable.

Field Descriptions

Button Matrix — Each button represents an area in the duct bank’s cross section thatextends the size of the duct bank. By assigning a conduit, cable or gap to a button, youassign that area in the duct bank. All assigned buttons (areas) are then used to calculatethe duct bank’s cross section. Unassigned or unused buttons in the matrix are not usedin calculating the ductbank’s cross sectional size unless they are in the middle ofassigned buttons.

Copy section layout from — Copies an existing duct cross section layout from aspecified duct into the active duct.

164

8. Desig

n

Define Duct Cross Section________________ Add — Assigns a conduit, cable or gap to a matrix button. A form displays allavailable conduit/cables in the project database for the defined control number. Theconduit/cable identification will appear on the button after assignment.

Delete — Removes a conduit/cable or gap from a matrix button.

Move — Moves a conduit/cable or gap from one matrix button to another.

Modify — Removes an existing button assignment and replaces it with newassignment.

Control Number — Displays the control number to use for retrieving the conduit/cableinformation from the project database. You can define any control number that isloaded to the project database.

You define whether you are routing conduit or cables by setting the Duct toggle in theEE Raceway Defaults form. See Set Raceway Defaults, page 256 for moreinformation.

If conduit routing is selected, this information is retrieved from the drawing_numbcolumn of the cndsch_spec table. If cable routing is selected, this information isretrieved from the drawing_numb column of the cabsch_spec table. These tables arethe cable/conduit schedule listings used for this project. The cable schedule is not thesame table as the cable table in the EE Wiring Diagram and Panel Design software.

Horizontal spacing — Defines the horizontal spacing between each button (area).

Vertical spacing — Defines the vertical spacing between each button (area).

Gap Distance — Defines a gap between two conduit/cables in the matrix. The gap ismeasured from the center of the left conduit/cable to the center of the rightconduit/cable and can only be defined on the top row of buttons. The gap distance willappear on the button after assignment.

165





Define whether you are placing conduit or cables in the duct bank by setting the Duct togglein the EE Raceway Defaults form. Likewise, you can define a margin width, a spacebetween the button matrix and the outside of the ductbank in the EE Raceway Defaults form.SeeSet Raceway Defaults, page 256 for more information.

Steps

1. Select the Define Duct Cross Section command.


2. Identify duct element

Select the duct bank element for which to define the cross section layout and accept itwith <D>.

The Duct Cross Section Layout form displays.

3. Define cross section layout using the various commands.

4. Select Confirm (√) to exit the form and save your changes.

The duct bank section layout, all conduit/cable information, is assigned to the ductone-line. The duct bank size is checked and resized as necessary, both width andheight. If Automatic Propagation is on, the duct bank will automatically repropagate.

— OR —

Select Cancel to exit the form without saving any changes.

If you select Cancel after having modified the ductbank’s layout, a warningform displays confirming that you want to exit without saving changes. Ifyou select Confirm (√) on the warning form, any changes you made will beignored. If you select Cancel on the warning form, you cancel your "exitwithout saving" and are returned to the command.

166

8. Desig

n

Place Stub Up________________

Place Stub Up

This command manipulates conduit stub ups. Stub ups are pieces of conduit associated with aconduit or cable contained in an underground duct bank and are placed in the raceway modelfor making above ground conduit connections. The stub up is connected to the correspondingunderground duct bank section by means of a drop point.

Before Using this Command

You must define conduit as an available one-line type using the Define One-Line Typecommand. See Define One-Line Type, page 260 .

You must define conduit as the active one-line type using the Set Active One-Line Typecommand. See Set Active One-Line Type, page 294 .

You must define the conduit sizing attributes using the Set Conduit Sizing Attributescommand. See Set Conduit Sizing Attributes, page 268 .

You must define the duct cross section layout using the Define Duct Cross Sectioncommand. See Define Duct Cross Section, page 164 .

You must select the a conduit specification using the Set Active One-Line Type Parameterscommand. See Set Active One-Line Type Parameters, page 289 .

The conduit specification and the conduit sizing attributes (for example,vendor, units, material) are used to determine the conduit stub up sizesavailable.

167


Field Descriptions

Button Matrix — Each button represents an area in the duct bank’s cross section thathas or has not been assigned during the Define Duct Cross Section command. Thismatrix is used in the Change Association and Place Stub Up options to identify whichcross section (that is, conduit/cable) to manipulate.

Select Duct Segment — Selects an existing duct segment in the raceway model as theactive duct segment.

Delete Stub Up — Deletes a conduit stub up.

Change Association — Changes the association of a conduit stub up from the currentlyassociated conduit/cable to another conduit/cable in the active duct segment.

Place Stub Up — Places a conduit stub up in the raceway model associated with aconduit/cable in the active duct segment.

Stub Up Size — After selecting the Place Stub Up button and selecting aconduit/cable from the active duct segment, this field displays the associated conduitstub up size. You can optionly override the displyed value by selecting a conduit stubup size from the available sizes as determined by matching the conduit sizing attributesto the active conduit specification.

If underground conduit routing is selected for this model, the size of stub up will beretrieved from the conduit schedule table in project schema based upon conduit numberthat user selected from matrix.

If underground cable routing is selected for this model or the conduit size is not definedfor the conduit number, you are required to select the desired size from the availablesizes. The displayed value is simply the value from the previous place stub upselection.

Stub Up Length — Displays the conduit stub up length as measured in the modelmaster units (feet, meters) The user can optionally override the displayed value.

168

8. Desig

n

Steps________________

Steps

1. Select the Place Stub Up command.

The Place Stub Up form displays.

2. Select Option

Select the Select Duct Segment option.

— OR —

Select the Delete Stub Up option. Go to Step 6.

— OR —

Select the Change Association option. Go to Step 9.

— OR —

Select the Place Stub Up option. Go to Step 14.

— OR —

Select Cancel (X) to exit the command.

3. Select the Select Duct Segment option.


4. Identify duct element

Identify a duct one-line in the design file.

The identified element highlights.

— OR —

Exit the option. Go to Step 2.


Accept the highlighted element. Go to Step 2.

The identified duct one-line’s cross section layout displays in the Button Matrix.

— OR —

Reject the highlighted element. Go to Step 4.

169


6. Select the Delete Stub Up option.


7. Identify stub up element

Identify a stub up one-line in the design file.


— OR —



Accept the highlighted element. It also deletes all cross sections, propagated elements,annotation, and RCP’s that are associated with the selected one-line. Go to Step 7.

— OR —


9. Select the Change Association option.

Select stub up for modification. is displays in the form message field. The precisioninput form displays.

10. Identify stub up element

Identify a stub up one-line in the design file.


— OR —



Accept the highlighted element.

— OR —


12. Conduit/Cable Number = [conduit/cable number]Select another cable/conduit to modify existing stub up.

170

8. Desig

n

Steps________________ Select a button from the Button Matrix.

13. Stub up spec. has been changed.

Go to Step 2.

14. Select the Place Stub Up option.

15. Select cable/conduit to connect stub up.

Select cable/conduit to connect stub up. displays in the message field.

Select a button from the Button Matrix.

— OR —

Select a option button. Go to Step 2.

16. Select a button from the Button Matrix.


17. Select location to place stub up.

Select location to place stub up. displays in the message field.

Place a data point at the desired location for the top of the conduit stub up. The systemplaces the stub up and connects it to the duct bank by means of a drop point located onthe duct bank one-line closest to the bottom of the conduit stub up.

The stub up is placed down from the given data point.

Go to Step 14.

— OR —

Override the stub up size or length. Go to Step 17.

— OR —

Exit the placement of the selected conduit/cable. Go to Step 2.

171


172

9. Mo

dify

Modify Commands________________

9. Modify Commands

The Modify commands manipulate elements, such as RCPs, one-lines, and three-lines, withinthe design file. Available element manipulations include copying, moving, deleting,annotating, and propagation. You can elect to manipulate either single elements or thoseelements belonging to an active group.

Do not use MicroStation commands to manipulate or modify EE Raceway elements(one-line, three-lines, annotation, and so forth). Doing so will cause seriousproblems and/or destroy the EE Raceway model. Use only these EE Racewaymodify commands to manipulate EE Raceway elements.

The Modify palette is activated by selecting Modify from the EERWAY Command MenuBar, then selecting Palette.

Commands

The commands on the Modify palette both activate other command palettes. These palettesand their commands will be described in this chapter.

Modify Element Commands — Manipulate single elements within the design file.

Modify Group Commands — Define elements for inclusion in a group andmanipulate elements belonging to the active group.

173


Using the Modify Commands


Once you have performed the necessary setups, you can use these commands throughout thedesign session. For reliable results, you should use these commands, not MicroStationmanipulation commands, any time you are modifying raceway elements.


These commands require that you have existing raceway elements in your design file (see theDesign Commands, page 129 for information about placing elements in the model). Youmust also have an active system and one-line type defined in the design file. SeeSetup Commands, page 253 and Runtime Setup Commands, page 287 for instructions aboutsetting up your systems and one-line types.

You must be familiar with precision input and its functions before using any of the Modifycommands, because it is through the Precision Input form that you will enter values for theplacement of points and for the location of raceway elements. For detailed information aboutprecision input, seePrecision Input Form, page 119 .

Group Workflow

There is no required or suggested sequence for the commands in this group.



174

9. Mo

dify

Modify Element Commands________________

Modify Element Commands

The Modify Element palette is activated by selecting the Modify Element command from theModify palette, or by selecting Modify from the EERWAY Command Menu Bar, then selectingModify Element Commands, then selecting Palette.

The Modify Element commands manipulate individual elements, including RCPs, one-lines, andthree-lines, within the design file. You can use individual commands to move, copy, and deletespecified elements, to review or edit element annotation, and to check for duplicate one-lines andcoincident RCPs in the design file. Modify Element commands also allow you to propagate one-lines in your raceway model.

Do not use MicroStation commands to manipulate or modify EE Raceway elements (one-line, three-lines, annotation, and so forth). Doing so will cause serious problems and/ordestroy the EE Raceway model. Use only these EE Raceway modify commands tomanipulate EE Raceway elements.

Commands

Annotate Element — Places, reviews, and edits intelligent annotation for raceway elements.

Copy Element — Copies an element as specified within the design file.

Move Element — Moves an element to a specified location in the design file.

Clone Element — Copies an element multiple times in the same direction.

Move One-Line Segment — Moves a one-line segment while maintaining connectivity to existingelements.

Move One-Line Vertex — Moves an internal one-line vertex.

Propagate Element — Expands one-line elements into three-dimensional elements.

175


Edit/Insert Manual Fitting — Modifies fittings that were manually placed in the model.

Modify One-Line — Modifies the route of an existing one-line element.

Place Fitting by Rule — Places a non-standard fitting at an RCP using a set of rules defined in thereference database.

Check Coincident RCPs — Checks for coincident RCPs in the design file.

Check Duplicate One-lines — Checks for duplicate or overlapping one-lines in the design file.

Delete Element — Removes a valid raceway element, and elements associated with it, from thedesign file.

Remove RCP — Deletes a specified RCP (raceway connect point) from the design file.

Delete Fitting — Removes fittings from the design file.

Remove One-Line Vertex — Deletes an internal vertex from an existing one-line.

Minimize Joints — Reduces the number of vertices in an identified one-line to a minimum.

Change System Parameters — Changes the system percentage and the project rule for a selectedelement.

176

9. Mo

dify

Using the Modify Element Commands________________

Using the Modify Element Commands




These commands require that you have existing raceway elements in your design file (seeDesign Commands, page 129 for information about placing elements in the model). Youmust also have an active system and one-line type defined in the design file. SeeSetup Commands, page 253 andRuntime Setup Commands, page 287 for instructions about setting up your systems and one-line types.

You must be familiar with precision input and its functions before using any of the ModifyElement commands, because it is through the Precision Input form that you will enter valuesfor the placement of points and for the location of raceway elements. For detailed informationabout precision input, seePrecision Input Form, page 119 .

Group Workflow





177


Annotate Element

This command places, reviews, and edits intelligent annotation for individual racewayelements. By definition, intelligent annotation is recognized by the EE Raceway product andcan be added to an EE database. You can also add cosmetic text to a raceway model fordisplay purposes, though the product does not recognize such annotation nor can the productadd it to an EE database.

The Annotate Element command recognizes one-lines, three-lines, Raceway Connect Points(RCP), straights, and fittings. For straights and fittings, you are allowed only to review theannotation.

Using this command, you can change the specifications or sizes of raceway components.

The following graphic shows the Annotate Element form for an RCP.

The following graphic shows the Annotate Element form for a one-line.

178

9. Mo

dify


Field Descriptions

Column name — Displays the aliases for those columns in the database that areassociated with the specified element. The displayed columns reside in the mscolumnstable in the database. You can only review the Column name column information.

Column value — Displays the current value for the column whose alias displays in theColumn name field. You can review and modify the values in this field. To changethe values associated with the element, select the field, and key in the new value. Youcan enter blank spaces into the design, using your keyboard space bar. Empty<Return>s, however, enter nothing into the design. Entering a space or a text value foran attribute will override that value in the reference database. To delete an override ona reference database attribute, select the Column value field and delete the blankcharacter. Once you have deleted the override, a value will display in the field only ifthe value can be retrieved from the reference database. Otherwise, the field remainsnull.

If blanks exist for a field, the cursor will jump to the end of the blankswhen the field is tagged beyond value.

Source — Displays the source of the corresponding column value. If Ref displays inthe column, then the value derives from the reference database. If Dgn displays in thecolumn, then the value derives from the design file. If you change a column value, thecolumn displays New until you select Confirm (√) to save your changes. The next timeyou enter the annotation form, the Source column will display either Ref or Dgn, whereNew had displayed. Where UD displays in the column, the corresponding columnvalue comes from user data. When modified, the value is saved back to user data.

List — Indicates whether or not a column value has an associated codelist. If an *displays in the List column, then the column value has a corresponding codelist. Todisplay the codelist, select the *.

Access — Indicates whether or not you can manipulate a particular column value. Ifyou can view and modify (read and write) the column value, the Access columndisplays a R/W. If you can only view (read) the column value, then it will display anR. You can only review the information in this column.

Display On/Off — Enables or disables the graphic display for each column value.Where the toggle is On, the value will display in the design where you place it. Youwill be prompted to place displayed values when placing one-lines in the drawing.

Reference Database Key — This field allows you to insert an override key into thereference database.

When you enter a new value in the EE Reference Database Key field, it becomes anoverride key to the reference database.

The key field is updated, and corresponding database values are retrieved and displayedon the annotation form. If the specified key does not exist in the reference database, anerror message displays and the annotation form returns to the previous values. Anyannotation you placed in the drawing will override the reference database defaults onthe form.

179

EE Raceway Modeling Reference Guide - February 2003________________ If you delete the value in this field, a value will automatically redisplay if it can beretrieved from the reference database. Otherwise, the field remains null.

If an override linkage is not present on a device or a title block, then the cell name orthe Default key will be used to locate default data. If the linkage is not present on aconnect point or one-line, the key specified in the user element is used. If no key existsin the user element, the Default key is used. Once you place an override key on anelement, you can modify it, but cannot delete it.

To change the displayed value, select the field, and key in a new value.

Key Description — Displays the description from the reference database of the currentEE Reference Database Key. You can only review the information in this field.

The lower portion of the Active [One_Line Type] Parameters form displays aspecification table. The EE spec key field on the upper portion of the form is used asthe key for the Column name values on the lower portion of the form.

Select — Retrieves the row(s) from the specification table that meet the select criteriadefined in the form. The select criteria are those values that display in the Columnvalue column on the lower portion of the annotation form. You can use relationaloperators when keying in your own select criteria. Available operators are describedlater in this section.

If only one row matches the select criteria you provide, then the Column values fill inwith the matching row’s values. If more than one row matches the criteria, then asecond form containing all matching rows displays.

From this form you can select the row(s) containing the desired values. To add valuesfrom the displayed specification table rows, select the row you want, and then selectConfirm (√). If you select Cancel (X), the system cancels the form and retrieves thevalues from the EE spec key field on the original form.

Clear — Clears the Column values from the lower portion of the form, and thenautomatically depresses the Override button to select a different row(s) from thespecification table. Clearing the column values allows you to key in new select criteria.

Override — This button allows you to override those columns whose access is ReadOnly (R). You can activate the Override button by selecting it directly or by selectingthe Clear button, which automatically activates it.

180

9. Mo

dify

Field Descriptions________________ This command accepts certain relational operators as search criteria. You should be familiarwith the following operators:


Description

= equal to numeric This is the default operator. If you do not enter anotheroperator, the system assumes =.

> greater than numeric This operator indicates that the queried values should begreater than the given value.

< less than numeric This operator indicates that the queried values should beless than the given value.


numeric This operator indicates that the queried values should begreater than or equal to the given value.


numeric This operator indicates that the queried values should beless than or equal to the given value.


% wild card CHAR This operator is a wild card, representing zero or morecharacters. The queried values must have everycharacter aside from the % in common with the givenvalue.

_ underline CHAR This operator is a wild card, representing a singlecharacter. The queried values must have every characteraside from the underline in common with the givenvalue.




181


Steps

1. Select the Annotate Element command.

The Annotate Element precision input form displays.

2. Identify Raceway element

Identify the element to annotate (one-line, three-line, drop point, equipment pointer, orRCP).

The system highlights the specified element. If you do not locate an acceptable element,the system displays the message Element not found. The message disappears whenyou identify a valid element.

— OR —

Exit the command.

3. Accept/Reject

Press <D> to accept the highlighted element.

The annotation form displays when you accept the element. The form displays all thecurrent values associated with the element. It also identifies all the possible values(column values) associated with this element.

— OR —

Press <R> to reject the highlighted element. Return to step 2.

4. Set up the form parameters to meet your specifications.

5. Select Confirm (√) to save your changes and exit the annotation form.

— OR —

Select Cancel (X) to exit the annotation form without saving your changes. Return toStep 2.

6. Placing [column alias]Data point <D> to place, reset <R> to skip.

The prompt indicates the column alias being placed. The column value displays in dragmode attached to the cursor.

Position the column value, and place a data point.

The new value displays in the design file. This step repeats for each new value. Whenthere are no more values to place, return to Step 2.

182

9. Mo

dify


Any value placed with the Annotate Element command will be enteredinto the drawing and, optionally, displayed. When you load the projectdatabase, these values are loaded into the project database.

When you annotate any raceway element, if you see graphics extendinginto the next raceway element, repropagate all of the connected racewayelements.

183


Copy Element

This command copies raceway elements to specified locations within the design file. You canuse this command to copy one-lines and their associated elements. This command will copy asingle RCP provided that no one-lines are attached.

Equipment pointers and drop points cannot be copied using this command.




184

9. Mo

dify

Steps________________

Steps

1. Select the Copy Element command.

The Copy Element precision input form displays.


Identify the one-line or RCP element you intend to copy and accept it with <D>.


3. Enter placement point

Specify a location for the copied element.

The system copies the element to the specified location in the design file.

Repeat this step.

— OR —

Press <R> to select another element to copy. Return to Step 2.

185


Move Element

This command moves individual raceway elements as specified within the design file. Youcan use this command to move one-lines, RCPs, drop points, equipment pointers, andannotation. If an RCP is moved, all attached one-lines will be rerouted to the new position ofthe RCP. All associated annotation, three-line fittings, and equipment pointers will also bemoved.

If a one-line is moved, all attached RCPs will be moved and all attached one-lines will be re-routed to the new one-line position. All associated annotation, three-line fittings, andequipment pointers will also be moved.




186

9. Mo

dify

Steps________________

Steps

1. Select the Move Element command.

The Move Element precision input form displays.


Identify the element you intend to move and accept it with <D>.


— OR —



Specify the new location for the element.

The system moves the element to the specified location.

Repeat this step.

— OR —

Press <R> to select another element to move. Return to Step 2.

187


Clone Element

This command copies raceway elements multiple times to specified locations within thedesign file. You can use this command to copy one-lines and their associated elements. Thiscommand will copy a single RCP provided that no one-lines are attached.

Equipment pointers and drop points cannot be copied using this command.




188

9. Mo

dify

Steps________________

Steps

1. Select the Clone Element command.


Identify the element you want to clone (copy) and accept it with <D>. The point youidentify the element with becomes the origin of the copy.

The element highlights.

— OR —


3. Key in number of clones

Key in the number of times to clone the identified element.

A warning box displays verifying the number of times you want to clone the identifiedelement.

4. Confirm (√) the number of times to clone the element.

— OR —

Cancel the form and reenter the number of clones.


Identify the location of the first copy. If you are placing more than one clone, eachsuccessive clone is placed the same distance and direction from the previous clone asthe first clone is from the original element.

The clone elements are placed in the design file.

Return to step 2.

189


Move One-Line Segment

This command moves one-line segments. Segments attached to the moved one-line segmentwill stretch or shrink to maintain connections with the moved one-line segment. If the first orlast segment of a one-line is moved, the attached RCP will also move. Any one-lines attachedto the RCP will stretch or shrink to maintain connections with the moved one-line segment.Also, any RCPs that are associated with a segment by a drop point will move only if the RCPand the drop point are coincident.




190

9. Mo

dify

Steps________________

Steps

1. Select the Move One-Line Segment command.

2. Identify Raceway One-Line Segment

Select the one-line segment you want to move and accept it with <D>.

The point that identifies the one-line segment in this step will bereference point used when placing the one-line segment at the newlocation.

The selected one-line segment highlights.

— OR —



Identify the new location of the one-line segment. Repeat this step.

The system moves the segment to the specified location.

— OR —

Press <R> to select another one-line segment to move.

If you have the Automatic Propagation toggle set to on, the one-line willautomatically repropagate after the move. SeePropagation Setup, page 297 for more information on this toggle.

191


Move One-Line Vertex

This command moves a one-line vertex. Any segments attached to a moved vertex willstretch or shrink to maintain connection. If a one-line end vertex is moved, the attached RCP,along with any annotation, equipment pointers, and equipment pointer annotation that isassociated with the RCP, also move with the vertex.




Steps

1. Select the Move One-Line Vertex command.

2. Identify Raceway One-Line Vertex

Select the vertex of the one-line you want to move and accept it with <D>.

The one-line vertex closest to the point where you identify the one-lineis automatically selected.

The selected vertex highlights.

— OR —


192

9. Mo

dify

Move One-Line Vertex________________


Identify the new location of the vertex. Repeat this step.

— OR —

Press <R> to select another one-line vertex.

If you have the Automatic Propagation toggle set to on, the one-linewill automatically repropagate after the move. SeePropagation Setup, page 297 for more information on this toggle.

193


Propagate Element

This command expands one-line segments and RCPs into three-dimensional elements (aprocess called propagation). Manually placed or edited fittings will propagate exactly asplaced. All other element will propagate depending on the specific situation of the element.

To view errors that occur during propagation, select the Highlight Propagation Errorscommand, seeHighlight Propagation Errors, page 314 . This command displays to the screen the pro.errfile, which resides in the <current_project>/rway/tmp directory.

The Propagate Element command automatically adds propagated (three-dimensional)fittings between non-straight raceway segments with a common RCP. A description of someof the delivered fittings follows the operating sequence in this section.




You can set active parameters for propagation through the Propagation Setup form. Forinformation about the form, see Propagation Setup, page 297 .

194

9. Mo

dify

Propagate Element________________

Steps

1. Select the Propagate Element command.

The Project Run precision input form displays.


Identify a raceway one-line or RCP.

The system highlights the specified element. If you do not locate an acceptable one-lineor RCP, the system displays the message Element not found. The message disappearswhen you identify a valid element.

— OR —

Exit the command. Go to step 1.

3. Accept/reject


The system propagates the identified one-line and returns you to step 2 to continueidentifying elements for propagation.

— OR —

Reject the highlighted element. Go to step 2.

Fittings

This section describes some of the fittings available with the delivered raceway one-linetypes. The attributes associated with each fitting are contained in the tray_part table in thereference database. For information about this table, seeSpecification, page 507 .

Fittings are produced through propagation and can be divided into the following categories:

Straights: fittings produced by propagating a one-line segment.

Elbows: fittings produced by propagating two intersecting one-line segments.

Wyes: fittings produced by propagating three intersecting one-line segments.

Crosses: fittings produced by propagating four intersecting one-line segments.

Reducers: fittings produced by propagating two or three intersecting one-linesegments which have different raceway parameters.

195

EE Raceway Modeling Reference Guide - February 2003________________ The following illustrations detail some of the fittings available for each raceway one-line type:

Tray Fittings

Wireway Fittings

196

9. Mo

dify

Propagate Element________________

Conduit Fittings

197


Edit/Insert Manual Fitting

This command is used to edit fittings that have been manually placed in the design file.

Options

Remove RCP — Deletes an RCP from the design file. See Remove RCP, page 214 .

Field Descriptions

Type — Displays the active three-line type for the current specification. The listcontains all available three-line types (elbow, straight, wye, etc.) for that specification.To change the displayed three-line type, select a value from the list. Modifying thevalue in the Part field may also change the active and available Type values.

Subtype — Displays the active subtype for the displayed Type value. The list containsall available subtypes (vertical, horizontal, inside vertical, etc.) for the active type andsubtype in the current specification. To change the displayed subtype, select a valuefrom the list. Modifying the value for Type also changes the active and availablesubtypes.

Qualifier — Displays the active qualifier for the displayed Type and Subtype. The listcontains all available qualifiers (adjustable, rigid, etc.) for the active type and subtype inthe current specification. To change the displayed qualifier, select a value from the list.Modifying Type or Subtype values may change the available qualifiers.

Symbol — Displays the name of the Eden symbol you are placing. You can onlyreview the values in this field.

Angle — Displays the active angle associated with the Type, Subtype, and Qualifierfor the current specification. The list contains available angles. To change thedisplayed angle, select an angle from the list or select the field, and key in the newvalue.

198

9. Mo

dify

Edit/Insert Manual Fitting________________

When placing a fitting (such as a vertical tee), if the placepoints and RCPs donot line up correctly, key in a negative angle, (-90 degrees) to shift the RCPsand placepoints to the correct location.

Length — Displays the length by which to project a straight. If straight is not youractive Type, the Length field does not display on the form. To change the displayedlength, select the field, and key in the new value.

Part — Displays the active part. The list contains all available parts for the currentspecification. To change the displayed part, select a value from the list. You can alsochange any of the values for Type, Subtype, Qualifier, Spec1, and (if applicable)Spec2.

Spec1 — Displays the active specification for the displayed Type, Subtype, andQualifier. The list contains all available specifications.

To change the displayed specification, select a value from the list.

To display the specification itself, select the corresponding Display button.

The specification form has these parameters:

— Column name - Displays the aliases of those columns in the database that areassociated with the specified type. You can only review the information in thiscolumn.

— Column value - Displays the column name values currently associated with thespecified type. You can review and modify the values in this column. To change avalue, select the Override button. Then select the field, and key in a new value.

199


— List - Indicates whether or not a column value has an associated codelist. If an *displays in the List column, then the column value has an associated codelist. Todisplay the codelist, select the *.

— Select - Retrieves the row(s) from the specification table that meet the select criteriadefined in the form. If only one row matches this criteria, then the Column valuesfill in with the matching row’s values. If more than one row matches the criteria,then a second form containing all matching rows displays.

You can use certain relational operators as search criteria. For a list of validoperators, see Annotate Element, page 178 .

— Clear - Clears the Column values from the lower portion of the form, and thenautomatically depresses the Override button so that you can select a differentrow(s) from the specification.

— Override - Allows you to override those columns whose access is Read Only (R).

You can activate the Override button by selecting it directly or by selecting theClear button, which automatically activates it.

Spec2 — Displays the active secondary specification, if any, for the given Spec1,Type, Subtype, and Qualifier. The list contains all available secondary specificationsfor the current settings. Secondary specifications are generally used with reducers.

You can display the current specification itself by selecting the Display button. Doingso displays a specification form. See Spec1 for a description of the form.

Overrides from the secondary specification are not passed to the Eden symbol.

Placepoint — Defines the point of attachment for the fitting you are currently placing.To change the active placepoint, select the slide bar, and drag it along the scale until itreaches the appropriate value.

Automatic Size — Automatically selects the appropriate size fitting base on the one-lines connected to the fitting.

The fitting size is determined by comparing the spec table nominal size of all one-linesat the RCP and selecting the largest nominal size among them. That nominal size isthen compared to the fitting table nominal sizes. If in the fitting table there is a nominalsize the same as the largest one-line nominal size, then that fitting is used. If there is nofitting of that nominal size, then the first fitting that is of greater nominal size than theone-line nominal size is used. If there is no nominal size fitting larger than the one-linenominal size, then the largest fitting available is used.

Automatic Fit — Correctly orients the fitting to the one-lines.

Rotate Orientation — These fields define the orientation matrix:

200

9. Mo

dify


— Angle - Defines the angle by which to rotate the orientation tee. To change thedisplayed angle, select the field, and key in a new value.

— About - Defines the axis about which to rotate the orientation tee. To change thedisplayed axis, select the field, and toggle between the three axes (Primary,Secondary, Normal) until the appropriate axis displays.

OR

Identify the appropriate axis name (text) on the orientation matrix diagram (to theright of the Angle and About fields.)


If you set the Driven By Spec/Table toggle to Table, the form changes.

Field Descriptions

Table — Displays the active special part table from the database. The list contains theavailable special part tables from the database. To change the active special part table,select a table name from the list.

Attribute — The next four display lists on the form are the first four Part Keyattributes from the active table and will change depending on which Table is active.The attribute display lists are used to interactively query the database for the desiredPart Key.

For example, you set the active Table to cond_body. size, type, material, and vendordisplay as the active attributes. Each attribute displays only those values that havecorresponding matching values for the other three attributes in the database. In otherwords, if you set material to feraloy, vendor to 3, and size to 1/2 inch, then only thosetypes that are 1/2 inch in size from vendor 3 and made of feraloy will be displayed inthe types list. Similarly, if you set type to form 7c, material to feraloy, and vendor to3, then only the sizes the form 7c comes in, made of feraloy from vendor 3, will bedisplayed in the size list.

201

EE Raceway Modeling Reference Guide - February 2003________________ Select/All toggles — Overrides the interactive queries of the attribute fields. When setto All, all available values for that attribute are displayed in the list, regardless of theother attribute settings.

Part Key — Displays the current part for the displayed Table. The list contains allavailable parts from the table. To change the active part, select a part from the list.Modifying the Table value also changes the active and available Part values.

You can display the current table information for the part by selecting the Displaybutton.

See the description of the Spec1 field earlier in this section for detailed informationabout the form parameters.

For information about the Placepoint and Rotate Orientation fields as well asthe form commands, see the descriptions earlier in this section. These fieldsand the commands operate identically in either Driven By Spec or Driven ByTable modes.


You should be familiar with precision input and its functions. For more information, seePrecision Input Form, page 119 .

When deciding whether your fitting information will come from a specification or from atable in the database, you should first consider a few points. Specification-driven fittings relyon the specification information (width, height, radius, etc.) to construct the three-linesymbols. All parts of a given specification will inherit the attributes of that specification. Onthe other hand, some fittings derive their information from their own database tables becausethey are not so easily classified into a common group of parts. Such fittings are called specialparts. The following table indicates fittings that are specification-driven and those that arespecial parts.

Specification-Driven Fittings Special Parts

straight pullboxelbow conduit bodywye light fixturecrossdropout

202

9. Mo

dify


Steps

1. Select the Edit/Insert Manual Fitting command.

2. Identify Raceway Fitting or RCP

Select the fitting or RCP you want to edit and accept it with <D>.

The Edit/Insert Manual Fitting form displays.

— OR —


3. Set the Driven By Spec/Table toggle to meet your requirements.

To derive fitting attributes from a specification in the database, set the toggle to DrivenBy Spec.

— OR —

To derive fitting attributes from a special part table in the database, set the toggle toDriven By Table. Go to step 4.

4. Edit the fitting as needed. Select Confirm when finished.

— OR —

Select Cancel to exit the form without editing the fitting or RCP.

203


Modify One-Line

This command modifies the route of an existing one-line. You cannot modify the terminationpoints of a one-line.

You will identify the one-line to be modified at the point where modification should begin.When identified, one segment of the one-line will display as a solid line with increased lineweight; the other segment appears as a dashed line. The dashed segment will then bemodified. You can reverse the segment to be modified by pressing <R>.




Steps

1. Select the Modify One-Line command.

The Modify One-Line precision input form displays.


Identify a one-line in the design.

The system highlights a valid one-line. If you do not locate an acceptable element, thesystem displays the message Element not found. The message will disappear whenyou identify a valid element.

204

9. Mo

dify

Modify One-Line________________

3. Raceway one-lineAccept/reject

Accept the highlighted element. Accepting the element identifies the one-line formodification.

The one-line highlights. Part of the one-line displays with an increased line weight,while the part to be modified displays as a dashed line.

— OR —

Reject the element.

The command prompts you to identify another one-line. Go to step 2.

4. Accept/reject

Accept the one-line element as displayed.

— OR —

Reject the one-line element as displayed.

— Pressing <R> (or Reject) once reverses the segments to be modified. Repeat thisstep.

— Pressing <R> (or Reject) a second time rejects the one-line. Go to step 2.

5. Enter next point

Enter points to draw new one-line routes. You can press <R> (or Reject) to reject thelast segment drawn. To terminate the new routes, place a data point on the originalone-line, or at the RCP containing the end of the one-line you are modifying.

The command reroutes the one-line according to your specifications.

— OR —

Reset to return to the previous step.


Accept the cross section, and return to step 2.

The system saves the rotation and returns to the beginning of the command, promptingyou to Identify Raceway One-Line.

— OR —

Rotate the cross section by the rotation angle defined in Raceway Defaults.

205

EE Raceway Modeling Reference Guide - February 2003________________ The system rotates the cross section and prompts you again to accept or continuerotating it.

7. Accept the rotation and return to step 2.

— OR —

Continue rotating the cross section.

206

9. Mo

dify

Place Fitting by Rule________________

Place Fitting by Rule

This command places a non-standard fitting at an RCP using a set of rules defined in thereference database. For example, one rule might define that at a 90 degree intersection of twoconduits, a LB fitting be placed. You can add to or replace the delivered rule set by editingthe tl_fit_env table in the database.

The fitting size is determined by comparing the spec table nominal size of all one-lines at theRCP and selecting the largest nominal size among them. That nominal size is then comparedto the fitting table nominal sizes. If in the fitting table there is a nominal size the same as thelargest one-line nominal size, then that fitting is used. If there is no fitting of that nominalsize, then the first fitting that is of greater nominal size than the one-line nominal size is used.If there is no nominal size fitting larger than the one-line nominal size, then the largest fittingavailable is used.

The spec table and the fitting table are defined in the rule.



At any point during this operating sequence, you can exit the command session either bypressing <Esc> or by selecting Cancel (X) on the precision input form. To reset a commandaction by one step or to reject a highlighted element, press <R> or select Reject on theprecision input form. You must define the rules in the reference database. SeeEE Databases, page 425 for a list of the delivered default rules.

207


Steps

1. Select the Place Fitting by Rule command.


Select the RCP on which you want to place the fitting.

If no rule is defined for the selected RCP’s situation, then the message Unable to finda rule that applies. displays. Otherwise the correct fitting as defined by the rule isplaced on the RCP.

— OR —


208

9. Mo

dify

Combine Coincident RCPs________________

Combine Coincident RCPs

This command is used to check for coincident RCPs in the design file. If coincident RCPs arefound and can be combined, you are given a choice of which RCP to keep. RCPs can becombined if the following criteria are true:

No more than four (4) RCPs are coincident.

All coincident RCPs must be of the same one-line type.

All RCPs must have a system in common.

Connectivity is re-established for the attached one-lines after RCPs have been combined.

Steps

1. Select the Combine Coincident RCPs command.

If no coincident RCPs are found, the message No coincident RCPs found displaysand the command exits.

— OR —

If coincident RCPs are found, the Combine Coincident RCPs form displays listing thecoincident RCP information.

Each set of coincident RCPs is listed in the form separated by the horizontal dotted line.

Combine — Merges the coincident RCPs into one RCP.

One-Line Type — Displays which one-line type each RCP belongs to.

Systems — Displays which system each RCP belongs to.

Status — Defines if the RCPs can be merged. If Combinable, then the RCPscan be merged. If Invalid, then you need to fix the coincident RCPs in yourmodel.

209


2. For each set of coincident RCPs, select the RCP information on the form to highlightthe associated elements in the model.

3. Choose which RCP in the set of RCPs you want to keep and leave that line highlighted.

4. Select the Combine button to merge that set of coincident RCPs.

The RCPs are combined, and the Status of the remaining RCP, the one you selected,changes to Kept. The status of the removed RCP changes to Combined.

You can not combine RCPs that have an Invalid status.

210

9. Mo

dify

Delete Duplicate One-Lines________________

Delete Duplicate One-Lines

This command is used to check for and correct duplicate one-lines (having only two vertices)that occupy the same geographical space and terminate on the same RCPs.

Steps

1. Select the Delete Duplicate One-Lines command.

If no duplicate one-lines are found, then the message No duplicate one-lines founddisplays and the command exits.

— OR —

If duplicate one-lines are found, then the Delete Duplicate One-Lines form displays.

Each set of duplicate one-lines is listed in the form separated by a dotted horizontal line.

2. For each set of duplicate one-lines in the form, select the one-line information on theform to highlight that one-line in the model.

3. Choose which one-line out of each set you want to keep. The Status of the one-lineyou chose changes to Save.

4. Select the Delete button to delete the other one-line(s).

The one-line is deleted and its Status changes to Deleted. The Status of the one-lineyou wanted to keep changes to Kept.

5. Continue to select the one-line to keep and deleting the other. Select Cancel whenfinished.

211


Delete Element

This command removes elements from the design file. You can use this command to deleteone-lines, RCPs (only if no one-lines are attached), cosmetic graphics, drop points, equipmentpointers, and annotation.




Steps

1. Select the Delete Element command from the menu.

The Delete Element precision input form displays.


Identify an element for deletion.


212

9. Mo

dify

Delete Element________________

— OR —


3. Raceway [element]Accept/reject

Press <D> to accept the element for deletion.

If you accept the highlighted element, the system deletes it. It also deletes all crosssections, propagated fittings, annotation, and RCPs (unless shared by another one-line)that are associated with the selected element.

Return to step 2.

— OR —

Press <R> to reject the highlighted element. Return to Step 2.

213


Remove RCP

This command removes a raceway connect point (RCP) from the design file. You cannot usethe Delete Element commands to remove an RCP, unless the RCP has no one-lines attached.

The command will remove an identified RCP only if all of the following conditions are true:

— Two one-lines are attached to the RCP.

— The two attached one-lines are of the same one-line type.

— The two attached one-lines belong to identical systems.

Once such an RCP is removed, the two one-lines form a single one-line element. If both one-lines are annotated, the annotation for the second one-line is deleted.




214

9. Mo

dify

Remove RCP________________

Steps

1. Select the Remove RCP command.

The Remove RCP precision input form displays.


Identify an RCP to remove.

The system highlights the specified element. If you do not locate an acceptable RCP,the system displays the message Element not found. The message disappears whenyou identify a valid RCP.

— OR —


3. Raceway connect pointAccept/reject

Press <D> to accept the highlighted RCP for deletion. Return to step 2.

If you accept the RCP, the command deletes it or displays an error message to thescreen.

— OR —

Press <R> to reject the highlighted RCP for deletion.

If you reject the RCP, the system prompts you to identify another. Go to Step 2.

215


Delete Fitting

This command deletes the raceway fitting from a selected RCP, useful for removing manuallyplaced special fittings (like pullboxes and conduit bodies) and replacing them with bends.This command does not remove the RCP.

Steps

1. Select the Delete Fitting command.


Select the fitting, or the fitting’s RCP, to delete.

— OR —


3. Accept/Reject

Press <D> to accept the highlighted fitting and delete it. Return to step 2.

— OR —

Press <R> to reject the highlighted fitting and return to step 2.

216

9. Mo

dify

Remove One-Line Vertex________________

Remove One-Line Vertex

This command deletes an internal one-line vertex.

You can not delete the end points of the one-line using this command.




Steps

1. Select the Remove One-Line Vertex command.

2. Identify Raceway One-Line Vertex

Select the vertex of the one-line you want to remove.

The one-line vertex closest to the point where you identify the one-lineis automatically selected.

The selected vertex highlights.

— OR —


217


3. Accept/reject

Press <D> to accept the highlighted vertex as the one to remove. Return to step 2.

The vertex is removed. If Automatic Propagation is on, the one-line repropagates.

— OR —

Press <R> to reject the highlighted vertex and choose another one. Return to step 2.

218

9. Mo

dify

Minimize Joints________________

Minimize Joints

This command reduces to a minimum the number of vertices in an identified one-line, whileretaining the original geometry of the one-line. If automatic propagation is toggled on, thecommand will repropagate the one-line. (See Propagation Setup, page 297 for informationabout the Automatic Propagation toggle.)

The following example demonstrates the effect of the Minimize Joints command on a one-line. (Automatic propagation is on to show the resulting seamless representation.)

Automatic propagation must be toggled on in order for the results of thiscommand to be visible.




219


Steps

1. Select the Minimize Joints command from the menu.

The Minimize Joints precision input form displays.

2. Identify Raceway one line

Identify a one-line in the design.

The system highlights a valid one-line. If you do not locate an acceptable element, thesystem displays the message Element not found. The message will disappear whenyou identify a valid element.


Accept the highlighted one-line to minimize the number of its vertices.

The command reduces the number of vertices comprising the one-line to a minimum(while retaining the original geometry). Go to step 2.

— OR —

Reject the element.

The command prompts you to identify another one-line. Go to step 2.

220

9. Mo

dify

Change System Parameters________________

Change System Parameters

This command changes the system parameters, the system Percent and the Project Rule, forthe systems associated with a single raceway element.

Field Descriptions

Primary System — Displays the primary system. The primary system determines thesymbology of the elements.

Project Rule Set — Displays the Project Electrical Code from the your projectschema’s project table. This is defined in EEmgr with the EE CMS Project Definitionprocess. The Project Rule Set determines which rules can be assigned to the activesystems. If the Project Rule Set is not defined, Project Rules cannot be assigned.

Systems — Displays all the systems associated with the selected element.

Percent — Specifies the current Percent space allocation assigned to each of theselected systems. The total Percent space allocation cannot exceed 100 percent. Thetotal of the system Percents is displayed in the field at the bottom of the Percentcolumn. All the selected systems percentages are summed to calculate the totalpercentage. The Percent represents the portion of the raceway’s width assigned to thatsystem. This Percent is used when calculating the cable fill of the raceway section inthe EECMS product.

Project Rule — Displays the Project Rule assigned to each of the selected systems forcalculating raceway fill. When a row is selected, a list of available rules for the ProjectRule Set defined with the EE CMS Project Definition process is displayed for reviewand selection. To clear the Project Rule, select the row and select the Cancel (X) on thelist of Rules.

List — Indicates whether or not a Project Rule can be assigned. If an * displays in theList column, then the Project Rule can be assigned. To display a list of available rulesfor the Project Rule Set defined with the EE CMS Project Definition process, select the*.

221





Steps

1. Select the Change System Parameters command.



Identify an element in the design file.


— OR —

Exit the command.




5. Select Confirm (√) to save your changes and exit the command.

The selected element is changed to reflect you selections.

— OR —

Select Cancel (X) to exit the command without making any changes to the selectedelement.

222

9. Mo

dify

Modify Group Commands________________

Modify Group Commands

The Modify Group commands define and manipulate groups within a design file. Groupsare temporary associations of Raceway and other elements in your model. The ModifyGroup commands allow you first to define a group of elements and then to manipulate thegroup in part or as a whole.

The Modify Group palette is activated by selecting the Modify Group command from theModify palette, or by selecting Modify from the EERWAY Command Menu Bar, thenselecting Modify Group Commands, then selecting Palette.

You can use individual Modify Group commands to move, copy, and delete elements ofspecified groups, and to review or edit element annotation. You can also propagate one-linesin a particular group using these commands.


Topics

Define Group — Identifies raceway elements for inclusion in a particular group.

Copy Element by Group — Copies within the design file some or all elements of aspecified group.

Annotate Element by Group — Places, reviews, and edits intelligent annotation forraceway elements within a specified group.

Clone Group — Copies a group multiple times in the same direction.

Propagate Element by Group — Expands some or all one-line elements of a specifiedgroup into three-dimensional elements.

223


Place Fitting by Rule Group — Places non-standard fittings using a set of rules defined inthe reference database.

Add Systems Group — Defines multiple systems for a single one-line.

Replace Systems Group — Changes the defined active system type of a one-line.

Minimize Joints by Group — Reduces to a minimum the number of vertices of some or allone-lines in a specified group.

Delete Element by Group — Removes from the design file some or all elements of aspecified group.

224

9. Mo

dify

Using the Modify Group Commands________________

Using the Modify Group Commands




These commands require that you have existing raceway elements in your design file (seeDesign Commands, page 129 for information about placing elements in the model). Youmust also have an active system and one-line type defined in the design file. SeeSetup Commands, page 253 andRuntime Setup Commands, page 287 for instructions about setting up your systems and one-line types.

You must be familiar with precision input and its functions before using any of the ModifyGroup commands, because it is through the Precision Input form that you will enter valuesfor the placement of points and for the location of raceway elements. For detailed informationabout precision input, seePrecision Input Form, page 119 .

Group Workflow

You must use the Define Group command to create and activate an element group beforeusing other Modify Group commands.




225


Define Group

This command compiles a group from elements you specify. A group is a temporaryassociation of Raceway elements in your model. Once you have defined a group of Racewayelements using this command, you can manipulate the group as a whole or in part.

Identifying the contents of an existing group can be done graphically, using the Hilite option.In general, however, you should assign your groups meaningful names that reflect theircontents.

All groups you create using this command are dropped when you exit the EE Raceway designsession.

Single Element/Entire Group — Determines how Modify Group commands will actupon existing groups. If the toggle is set to Single Element, then a command willprompt you to accept/reject every element within a specified group before performingthe command action. If the toggle is set to Entire Group, then a command will promptyou once to accept/reject the specified group as a whole before performing thecommand action.

Use caution when you are manipulating groups in Entire Group mode. Thesystem prompts you just once to accept/reject a group for manipulation.

Available Groups — Lists the groups you have already created. The active group ishighlighted in the list. The key-in field above the list accepts input for group namewhen you are defining a new group. To change the active group, select a group fromthe list. To enter a group name, select the group name key-in field, and key in a name.

Create — Creates a group containing the elements you specify in the EE ElementTypes list. The system adds the elements using the selection method you specified inthe Graphic Method list.

226

9. Mo

dify

Define Group________________ To initiate the Create operation, select the button, key in a group name, and selectAccept. The system then compiles a group according to your specifications. Whenprocessing is complete, review the form Message Area for information about thenumber of elements the new group contains.

Drop — Removes the active group (the highlighted group in the Available Groupslist).

To initiate the Drop operation, select a group from the Available Groups list, selectDrop, and then select Accept.

Copy — Copies the specified contents of one group to a new group.

To initiate the Copy action, select an existing group from the Available Groups list,select Copy, and key in a new group name.

Add to — Adds elements you specify from the EE Element Types list to an existinggroup. The system compiles the elements using the selection method you specified inthe Graphic Method list.

To initiate the Add to operation, select an existing group from the Available Groupslist, select Add to, and then select Accept. The system compiles the elements using theselection method you specified in the Graphic Method list. When processing iscomplete, review the form Message Area for information about the number of elementsadded to the group.

Drop from — Removes elements you specify in the EE Element Types list from anexisting group. If you remove all elements from a group, the system automaticallydrops the entire group.

To initiate the Drop from action, select an existing group from the Available Groupslist, select Drop from, and then select Accept. The system drops the elements usingthe selection method you specified in the Graphic Method list. When processing iscomplete, review the form message display for information about the number ofelements dropped from the group.

Hilite — Highlights in the design file the entire contents of an existing group.

To initiate the Hilite action, select an existing group from the Available Groups list,and select Hilite. It is not necessary to select Accept. The system automaticallyhighlights the group contents in the drawing.

Clear Hilite — Clears all highlighting placed in the design when you use the Hilitecommand.

EE Element Types — Displays all available element types available for inclusion in ordeletion from a group. Types include one-lines, three-lines, RCPs, drop points, toequipment, and all annotation. You must choose at least one element type whencreating, adding elements to, or dropping elements from a group.

227

EE Raceway Modeling Reference Guide - February 2003________________ Select All — Selects every element type from the EE Element Types list.

Clear All — Clears all selected element types from the EE Element Types list.

EE Method — This list displays optional restrictions for the items selected in the EEElement Types list. You can use the three options in this list to restrict the elements inyour group to those belonging to particular one-line types or systems.

– One-Line Type - Displays a list of available one-line types.

When you select a one-line type from this list, only those element types (RCPs, one-lines, three-lines, and so forth) belonging to that one-line type will be included in yourgroup.

You can select individual one-line types from this list, or you can select all displayedone-line types (using Select All). Clear All cancels the selections you have made fromthe list.

Once you have displayed the One-Line Type list, you must Cancel (X) or Confirm(√) your selections before selecting the Accept button on the main form.

– System - Displays a list of available systems.

When you select a system from this list, only those element types (RCPs, one-lines,three-lines, and so forth) belonging to that system will be included in your group.

You can select individual systems from this list, or you can select all displayed systems(using Select All). Clear All cancels the selections you have made from the list.

Once you have displayed the System list, you must Cancel (X) or Confirm (√) yourselections before you can select the Accept button on the main form.

– Attributes - Displays a list of available element types from which you can defineselection attributes.

228

9. Mo

dify

Define Group________________ When you select an element type from this list, an attribute list form displays for thatelement type in which you can specify the attributes to include in the groupidentification.

Once you have defined the attributes, select the Accept button on the main form. Toreset out of the attribute list form and disregard the attributes, select the Cancel (X)button on the attribute form.

Graphic Method — Displays the available methods for selecting group elements. Youwill use these methods to identify elements for group creation, insertion into groups, ordeletion from groups. These methods can serve to further restrict the element types youare including in your group.

For example, if you identified one-line trays for insertion into a group, and select FenceBlock from this list, the system inserts into the group only those one-line trayscontained within the fence you place.

– Selection - Prompts you to identify specified element types in the design file to dropfrom or include in a group.

– Fence Block - Drops from or includes in a group those specified element typescontained within a fence block you place in the design.

– Fence Shape - Drops from or includes in a group those specified element typescontained within a fence shape you place in the design.

– View - Drops from or includes in a group those specified elements types contained ina view you identify.

– All Elements - Drops from or includes in a group all specified element types in thedesign.

229


Steps

1. Select the Define Group command.

The Groups form displays.

2. Create a group of elements:

— Key in a name for the group in the field provided.

— Select the Create button under Group Operations.

— Use the EE Element Types, EE Method, and Graphic Method lists to definewhich elements to place in the group and how you want to select them in the designfile.

— Select the Process button at the top of the form.

— Using the Graphic Method you defined, select your elements for the group.

The group is created. The number of elements added to the group displays at thebottom of the form.

— OR —

Select one of the available group from the list

3. Set the Entire Group/Single Element and Hilite On/Hilite Off toggles the way youwant.

4. Select one of the group modification commands.

230

9. Mo

dify

Copy Element by Group________________

Copy Element by Group

This command copies all or selected valid elements in the active group.

Equipment pointers and drop points are not copied even if they are part of thedefined group.




You must define a temporary group of elements, using the Define Group command, seeDefine Group, page 226. Placing a fence around elements in the design also constitutes agroup for the purposes of this command. A fence group overrides the active group.

Steps

1. Select the Copy Element by Group command from the menu.

The Copy by Group precision input form displays. If you have not defined a group,the message No active group defined displays.

— If you have a fence in the design, go to step 2.

— If Single Element is the active toggle on the Define Group form, go to step 3.

— If Entire Group is the active toggle on the Define Group form, go to step 4.

2. Accept/reject fence contents

Accept the contents of the fence to define them as a group.

Go on to step 3 if Single Element is the active toggle on the Define Group form.

Go to step 5 if Entire Group is the active toggle on the Define Group form.

231




— OR —

Reject the highlighted element.

The system highlights another group element if any elements remain uncopied. Repeatthis step. Otherwise, the command exits automatically.

4. Accept/reject Group [group name]

Accept the active group.

— OR —

Reject the active group.

The command exits automatically.

5. Define origin

Enter a point to use as a base for the group copy.

Elements within the active group highlight.


Enter a point for the location of the element you are copying.

The system copies the element as specified. If there are group elements that remainuncopied, you are returned to step 3. Otherwise, the command exits automatically.

— OR —

Reject the element you are copying.

The system returns you to step 3 if there are group elements that remain uncopied.Otherwise, the command exits automatically.

232

9. Mo

dify

Annotate Element by Group________________

Annotate Element by Group

This command places, reviews, and edits intelligent annotation for some or all racewayelements associated with a specified group. Intelligent annotation is recognized by the EERaceway product and can be added to an EE database. You can also add cosmetic text to araceway model for display purposes, though the product does not recognize such annotationnor can the product add it to an EE database.

The Annotate Element command recognizes one-lines, three-lines, Raceway Connect Points(RCP), straights, and fittings. For straights and fittings, you are allowed only to review theannotation (read only access).

Using this command, you can change the specifications or sizes of raceway components.

Field Descriptions

Column name — Displays the aliases for those columns in the database that areassociated with the specified element. The displayed columns reside in the mscolumnstable in the database. You can only review the Column name column information.

Column value — Displays the current value for the column whose alias displays in theColumn name field. You can review and modify the values in this field.

To change the values associated with the element, select the field, and key in the newvalue. You can enter blank spaces into the design, using your keyboard space bar.Empty <Return>s, however, enter nothing into the design. Entering a space or a textvalue for an attribute will override that value in the reference database. To delete anoverride on a reference database attribute, select the column value field and delete theblank character. Once you have deleted the override, a value will display in the fieldonly if the value can be retrieved from the reference database. Otherwise, the fieldremains null.

233


If blanks exist for a field, the cursor will jump to the end of the blanks whenthe field is tagged beyond value.

Source — Dislays the source of the corresponding column value. If Ref displays in thecolumn, then the value derives from the reference database. If Dgn displays in thecolumn, then the value has been defined from the design file. If you change a columnvalue, the column displays New until you select Confirm (√) to save your changes.The next time you enter the annotation form, the Source column will display either Refor Dgn, where New had displayed. Where UD displays in the column, thecorresponding column value comes from user data. When modified, the value is savedback to user data.

List column — Indicates whether or not a column value has an associated codelist. Ifan * displays in the List column, then the column value has a corresponding codelist.To display the codelist, select the *.

Access column — Indicates whether or not you can manipulate a particular columnvalue. If you can view and modify (read and write) the column value, the Accesscolumn displays a R/W. If you can only view (read) the column value, then it willdisplay an R. You can only review the information in this column.

Display On/Off — This toggle enables or disables the design display for each columnvalue. Where the toggle is On, the value will display in the design where you place it.You will be prompted to place displayed values when placing one-lines in the drawing.

Reference Database Key — This field allows you to insert an override key into thereference database. When you enter a new value in the EE Reference Database Keyfield, it becomes an override key to the reference database.

The key field is updated, and corresponding database values are retrieved and displayedon the annotation form. If the specified key does not exist in the reference database, anerror message displays and the annotation form returns to the previous values. Anyannotation you placed in the drawing will override the reference database defaults onthe form.

If you delete the value in this field, a value will automatically redisplay if it can beretrieved from the reference database. Otherwise, the field remains null.

If an override linkage is not present on a device or a title block, then the cell name orthe Default key will be used to locate default data. If the linkage is not present on aconnect point or one-line, the key specified in the user element is used. If no key existsin the user element, the Default key is used. Once you place an override key on anelement, you can modify it, but cannot delete it.

To change the displayed value, select the field, and key in a new value.

Key Description — Displays the description from the reference database of the currentEE Reference Database Key. You can only review the information in this field.

234

9. Mo

dify

Annotate Element by Group________________ Global/Single — Determines whether or not the annotation modifications you aremaking to the specified element will be applied to all identical element types within thegroup. For example, setting the toggle to Global while annotating an RCP will changethe annotation for all RCPs within the group when you select Confirm (√). If thetoggle is set to Single for the same RCP annotation, the system will modify annotationonly for that RCP when you select Confirm (√).


Select — Retrieves the row(s) from the specification table that meet the select criteriadefined in the form. The select criteria are those values that display in the Columnvalue column on the lower portion of the annotation form. You can use relationaloperators when keying in your own select criteria. Available operators are describedlater in this section.

If only one row matches the select criteria you provide, then the Column values fill inwith the matching row’s values. If more than one row matches the criteria, then asecond form containing all matching rows displays.

From this form you will select the row(s) containing the desired values. To add valuesfrom the displayed specification table rows, select the row you want, and then selectConfirm (√). If you select Cancel (X), the system cancels the form and retrieves thevalues from the EE spec key field on the original form.

Clear — Clears the Column values from the lower portion of the form, and thenautomatically depresses the Override button to select a different row(s) from thespecification table. Clearing the column values allows you to key in new select criteria.

Override — This button allows you to override those columns whose access is ReadOnly (R). You can activate the Override button by selecting it directly or by selectingthe Clear button, which automatically activates it.

235

EE Raceway Modeling Reference Guide - February 2003________________ This command accepts certain relational operators as search criteria. You should be familiarwith the following operators:

Symbol Name DataTypes

Description

= equal to numeric This is the default operator. If you do not enteranother operator, the system assumes =.








% wild card CHAR This operator is a wild card, representing zero ormore characters. The queried values must have everycharacter aside from the % in common with the givenvalue.

_ underline CHAR This operator is a wild card, representing a singlecharacter. The queried values must have everycharacter aside from the underline in common withthe given value.



At any point during this operating sequence, you can exit the command session either bypressing <Esc> or by selecting Cancel (X) on the precision input form. To reset a commandaction by one step or to reject a highlighted element, press <R> or select Reject on theprecision input form. You must define a temporary group of elements, using the DefineGroup command. (For information about the command, see Define Group, page 226 .)Placing a fence around elements in the design also constitutes a group for the purposes of thiscommand. A fence group overrides the active group.

236

9. Mo

dify

Annotate Element by Group________________

Steps

1. Select the Annotate Element by Group command from the menu.

The Annotate by Group precision input form displays.


— If there is not a fence in the design, go to step 3.



The system highlights the group contents.

— OR —

Reject the contents of the fence.

The command exits automatically. Go to step 1.


Accept the highlighted group element.

The system displays the Annotate Element form for the identified element.

— OR —

Reject the highlighted group element.

The system highlights another group element. Repeat this step. If no group elementsremain, the command exits.


5. Select Confirm (√) to save your changes and exit the annotation form.

— OR —

Select Cancel (X) to exit the annotation form without saving your changes. Go to Step3.

6. Placing [column alias]Data point <D> to place, reset <R> to skip.

The prompt indicates the column alias you are placing. The column value displays indrag mode attached to the cursor.

237

EE Raceway Modeling Reference Guide - February 2003________________ Position the column value, and place a data point.

The new value displays in the design file. The system places all new displayedannotation for the specified element.

If you set the toggle to Global, the system places the same annotation for all identicalelement types in the group. When there are no more values to place for the elementtype, the system prompts you to annotate other element types within the group. Go tostep 3.

— OR —

If you set the toggle to Single, the system returns you to step 3 to annotate otherelements within the group. Go to step 3.

Any value placed with the Annotate Element by Group command willbe entered into the drawing and, optionally, displayed. When you loadthe project database, these values are loaded into the project database.

238

9. Mo

dify

Clone Element by Group________________

Clone Element by Group

This command copies the active group multiple times, useful when the same elements are tobe placed at regular intervals.

Equipment pointers and drop points are not copied even if they are part of thedefined group.





Steps

1. Select the Clone Group command.

The Clone Group precision input form displays. If you have not defined a group, themessage No active group defined displays.








239



Accept the highlighted element. Go to step 6.

— OR —





— OR —



5. Define origin

Identify a point in the group to use as the origin for the copies.

6. Key in number of clones

Key in the number of times to clone the identified group.

A warning box displays verifying the number of times you want to clone the identifiedgroup.

7. Confirm (√) the number of time to clone the group.

— OR —

Cancel the form and reenter the number of clones.


Identify the location of the first copy. If you are placing more than one clone, eachsuccessive clone is placed the same distance and direction from the previous clone asthe first clone is from the original group.

The clone elements are placed in the design file.

Return to step 2.

240

9. Mo

dify

Propagate by Group________________

Propagate by Group

This command expands into three-dimensional elements all or selected valid one-linesegments and RCPs from the active group.

The Propagate by Group command automatically adds propagated (three-dimensional)fittings between non-straight raceway segments with a common RCP. For a description ofsome of the delivered fittings, see Propagate Element, page 194 .

To view errors that occur during propagation, select the Highlight Propagation Errorscommand. This command displays to the screen the pro.err file, which resides in the<current_project>/rway/tmp directory). For information about using this command, seeHighlight Propagation Errors, page 314 .





You can set active parameters for propagation through the Propagation Setup form. Forinformation about the form, see Propagation Setup, page 297 .

Steps

1. Select the Propagate by Group command from the menu.

The Project by Group precision input form displays.




241



Accept the contents of the fence to manipulate them as a group.

— If Entire Group is the active toggle on the Define Group form, the commandpropagates all valid elements within the fence, and exits automatically. Go to step1.


— OR —





The system propagates the element, and then highlights another group element forpropagation. If no group elements remain, the command exits automatically.

Repeat this step until you have processed all elements within the group, or until youexit the command.

— OR —


The system highlights another group element for propagation. If no group elementsremain for propagation, the command exits automatically.

Repeat this step until you have processed all elements within the group, or until youexit the command.



The system propagates every element belonging to the group.

— OR —


242

9. Mo

dify

Place Fitting by Rule by Group________________

Place Fitting by Rule by Group

This command places a non-standard fitting at an RCP using a set of rules defined in thereference database. For example, one rule might define that a CLB fitting be placed at a 90degree intersection of two conduits. You can add to or replace the delivered rule set byediting the tl_fit_env table in the database.

The fitting size is determined by comparing the spec table nominal size of all one-lines at theRCP and selecting the largest nominal size among them. That nominal size is then comparedto the fitting table nominal sizes. If in the fitting table there is a nominal size the same as thelargest one-line nominal size, then that fitting is used. If there is no fitting of that nominalsize, then the first fitting that is of greater nominal size than the one-line nominal size is used.If there is no nominal size fitting larger than the one-line nominal size, then the largest fittingavailable is used.

The spec table and the fitting table are defined in the rule.




You must define a temporary group of elements, using the Define Group command, seeDefine Group, page 226. Placing a fence around elements in the design also constitutes agroup for the purposes of this command. A fence group overrides the active group. You mustdefine the rules in the reference database. SeeEE Databases, page 425 for a list of the delivered default rules.

243


Steps

1. Select the Place Fitting by Rule by Group command.

The Group Place Fitting by Rule precision input form displays. If you have notdefined a group, the message No active group defined displays.










— OR —





If no rule is defined for the selected RCP’s situation, then the message Unable to finda rule that applies. displays. Otherwise the correct fitting as defined by the rule isplaced on the RCP.

— OR —



244

9. Mo

dify

Add Systems Group________________

Add Systems Group

This command defines multiple systems for a single one-line. This command will not changethe master system, the system defined at placement. It will only append systems to theelement. For example, using this command you can add an alarm and control system to anexisting element with a communication system.

If you try to add a system that already exists on the element, it will not be duplicated.


You must define a temporary group of elements using the Define Group command and thegroup mode must be set to Entire Group, see Define Group, page 226 . Placing a fencearound elements in the design also constitutes a group for this command. A fenced group willoverride the active temporary group.

Steps

1. Select the Add Systems Group command.

The group that the systems will be added to highlights.

2. Press <D> to accept the group as the one to add systems to.

The Add Systems form displays.

— OR —

Press <R> to reject the group and exit the command.

3. Select the system or systems you want to add and select Confirm (√).

The system(s) is added.

— OR —

Select Cancel to exit the form and command.

245


Replace Systems by Group

This command changes the defined active system(s) for a group. For example, use thiscommand when you want to change an existing high voltage tray to a low voltage tray. Thiscommand performs a total replacement of all systems; that is, all defined systems for thegroup are removed and replaced by the new systems.

Changing the active system will cause the graphic symbology to change to thesymbology define for the new system.

Field Descriptions

Systems — This button allows the selection of the active system. When a new activesystem is selected, the subsystem are all unselected. The active system is automaticallyincluded as a subsystem. The active system determines the symbology of the raceway.

Subsystem — This button allows the selection of subsystems. While this button isdepressed, the Percent and Project Rule can be defined for each subsystem.

Project Rule Set — Displays the Project Electrical Code from the your projectschema’s "project" table. This is defined in EEmgr with the EE CMS ProjectDefinition process. The Project Rule Set determines which rules can be assigned to theactive systems. If the Project Rule Set is not defined, Project Rules cannot be assigned.

Systems — Displays all the available systems. Selecting a row in this field defines theActive System or Subsystems.

Percent — Displays the current Percent space allocation assigned to each of theselected systems. The total Percent space allocation cannot exceed 100 percent. Thetotal of the system Percents is displayed in the field at the bottom of the Percentcolumn. All the selected systems percentages are summed to calculate the totalpercentage. The Percent represents the portion of the raceway’s width assigned to thatsystem. This Percent is used when calculating the cable fill of the raceway section inthe EECMS product.

246

9. Mo

dify

Replace Systems by Group________________ Project Rule — Displays the Project Rule assigned to each of the selected systems forcalculating raceway fill. When a row is selected, a list of available rules for the ProjectRule Set defined with the EE CMS Project Definition process is displayed for reviewand selection. To clear the Project Rule, select the row and select the Cancel (X) on thelist of Rules.

List — Indicates whether or not a Project Rule can be assigned. If an * displays in theList column, then the Project Rule can be assigned. To display a list of available rulesfor the Project Rule Set defined with the EE CMS Project Definition process, select the*.


You must define a temporary group of elements using the Define Group command and thegroup mode must be set to Entire Group, see Define Group, page 226 . Placing a fencearound elements in the design also constitutes a group for this command. A fenced group willoverride the active temporary group.

When defining the group for this command, you must define a group that containsall elements that have connectivity. You can not replace a system on just oneelement in a network of elements that have connectivity. A network may bethought of as all RCPs, drop points, one-lines, and so forth that are associatedthrough a series of graphically connected one-lines.

Steps

1. Select the Replace Systems by Group command.

The active group to be changed highlights.

2. Press <D> to accept the group.

The Replace Systems form displays.

— OR —

Press <R> to reject the group and exit the command.

3. Select the new system type from the form and select Confirm (√).

The active group is changed to the new system type.

— OR —

Select Cancel to exit the form and the command.

247


Minimize Joints by Group

This command reduces to a minimum the number of vertices in valid one-line(s) within theactive group, while retaining the original geometry of the one-line(s). If automaticpropagation is toggled on, the command will repropagate each affected one-line. (SeePropagation Setup, page 297 for information about the Automatic Propagation toggle.)

The following example demonstrates the effect of the Minimize Joints command on a one-line. (Automatic propagation is on to show the resulting seamless representation.)

Automatic propagation must be toggled on in order for the results of thiscommand to be visible.





248

9. Mo

dify

Minimize Joints by Group________________

Steps

1. Select the Minimize Joints by Group command from the menu.

The Minimize Joints Group precision input form displays.






— If Entire Group is the active toggle on the Define Group form, the vertices of allone-lines within the fence are reduced to a minimum number, and the commandexits automatically.

— If Single Element is the active toggle on the Define Group form, the systemprompts you to minimize the number of vertices for each one-line within the fence.Go to step 3.

— OR —




Accept the highlighted one-line.

The system minimizes the number of vertices comprising the one-line, and thenidentifies another valid one-line within the group (if any remain). Repeat this step. Ifthere are no valid one-lines remaining in the group, the command exits automatically.

— OR —

Reject the highlighted one-line.

The system then identifies another valid one-line in the group, if any remain. Repeatthis step. If there are no valid one-lines remaining in the group, the command exitsautomatically.

4. Accept/reject Group ([group name])

249

EE Raceway Modeling Reference Guide - February 2003________________ Accept the active group.

The system minimizes the number of vertices for all valid one-line elements within thegroup. The command exits automatically.

— OR —



250

9. Mo

dify

Delete Element by Group________________

Delete Element by Group

This command deletes all or selected valid elements in an active group from the design file.





Steps

1. Select the Delete Element by Group command from the menu.

The Delete by Group precision input form displays. If you have not defined a group,the message No active group defined displays.






— If Entire Group is the active toggle on the Define Group form, the contents of thegroup are deleted, and the command exits automatically.

— If Single Element is the active toggle on the Define Group form, the systemprompts you to delete each element within the fence. Go to step 3.

— OR —


251

EE Raceway Modeling Reference Guide - February 2003________________ The command exits automatically.



The system deletes the element, and prompts you to delete another group element.Repeat this step. If there are no remaining group elements for deletion, the commandexits automatically.

— OR —


The system prompts you to delete another group element if any remain for deletion. Ifthere are no remaining group elements for deletion, the command exits automatically.



The system deletes all valid elements within the group. The command exitsautomatically.

— OR —



252

10. Setu

p

Setup Commands________________

10. Setup Commands

The Setup commands allow you to define, review, and modify the default parameters, systems,one-line types, and symbology settings for your design file. The Setup palette is activated byselecting Setup from the EERWAY Command Menu Bar, then selecting Palette from theresulting pulldown menu.

In a new design file, you must use the Setup commands before using any other command group.Your system/application manager should ensure that the reference database contains the necessarysystems and one-line types before you use these commands.

Commands

Set Raceway Defaults — Defines, reviews, and modifies the raceway default parameters forsymbols, working view, model annotation, RCPs, report IDs, and cross sections.

Define System — Selects any or all systems from those available in the reference database foruse in the design file.

Define One-Line Type — Selects any or all available one-line types from those available in thereference database for use in the design file.

Set Symbology Control — Selects the standard graphic symbology control for all systems andone-line types in a design file.

Symbology Control — Defines, reviews, and modifies the graphic symbology control for thoseone-line types you specified using the Set Symbology Control command.

Set Text Defaults — Defines, reviews, and modifies the default parameters for text, text nodes,and engineering units.

Set Conduit Sizing Attributes — Defines which conduit attributes will be used selecting thecorrect size conduit in the Conduit Sizing command.

Cell Creation Commands — Create various types of raceway cells necessary for creating EERaceway models.

253


Model Commands — Place and manipulate a model information in the design file.

254

10. Setu

p

Using the Setup Commands________________

Using the Setup Commands


You will typically use Setup commands when you enter a design file for the first time. Someof the setups performed by this group of commands are required for later design work anddatabase operations.


You must have a valid reference database attached to your design file before using the Setupcommands. For individual command prerequisites, see the appropriate commanddescriptions.

Group Workflow

Before using the symbology commands in this group (Set Symbology Control andSymbology Control), you must have defined at least one system and one-line type from thedatabase using the Define System and Define One-Line Type commands.


See individual command descriptions for specific operating information.

255


Set Raceway Defaults

This command defines, reviews, and modifies raceway defaults, including cross sectionparameters, symbol defaults, and Raceway Connect Point (RCP) parameters. It also allowsyou to view the reference database contents for RCP. You will enter all raceway defaultvalues through the EE Raceway Defaults form.

Parameters — Displays the EE Raceway default digitizing parameters, such as Coloror Active Angle. You can review, define, and/or modify any of the values in thesefields. To change a displayed value, select the field, and key in a new value. Use thesefields to set the default symbology for different systems in a design file.

Changes in these fields do not affect existing systems. Use the SetSymbology Control to make changes to individual, existing systems.Default settings are applied to new systems created in or added to adesign file.

Duct — Specifies whether to use conduit or cable when using the Define Duct CrossSection command, seeDefine Duct Cross Section, page 164 for more information.

Margin Width — Defines the distance, in sub-units, between the routed cable/conduit,represented by the matrix buttons, and the shell of the duct bank when using the DefineDuct Cross Section command, see Define Duct Cross Section, page 164 for moreinformation.

Global Symbology — Displays the default symbology settings for Model Annotation.The system uses these settings when annotating the model either during cell creation orafter you have placed one in the design file. You can review, define, and/or modify thesettings. To change a displayed value, select the field, and key in a new value.

Cross Section — Displays the default Scale Factor and Rotation Angle for crosssections. You can review, define, and/or modify the values in these fields. To change adisplayed value, select the field, and key in a new value.

256

10. Setu

p

Set Raceway Defaults________________ Working view — Displays the current working view for the design file. The workingview determines the orientation of text and cells you place through precision input.Additionally, precision input uses the working view to place and locates points in thedesign. To change the current working view, select the slide bar, and drag it along thescale until the desired view number displays. The scale includes views 1 through 8.

Symbols — Displays the names of the cells that represent equipment pointers and droppoints. To change a displayed value, select the field, and key in a new value.

RCP — Displays the Default Weight for RCPs. You can review, define, and/ormodify the value in this field. This value will also become the default RCP weight onthe Symbology Control form. To change the displayed value, select the field, and keyin a new value.

Default Key — Displays the current default keys for RCP (raceway connect point),equipment pointer, and drop point annotation. You can review, define, and/or modifythis key. To display the current default data from the database for a particular element(RCP, equipment pointer, or drop point), select first the key field and then the Displaybutton. The information will display in the scrollable list in the lower right corner ofthe form. You can only view this data.

Steps

1. Select the Set Raceway Defaults command.

The EE Raceway Defaults form displays.

2. Set up the form parameters to meet your requirements.


— OR —

Select Cancel (X) to exit without saving your changes.

257


Define System

This command allows you to select any or all available systems from the reference databasefor use in the design file. The System Definition form displays those systems available forselection from the reference database, as well as those already selected for the current designfile.

If you need systems not available to you, you should ask the system/application manager toadd them to the reference database. Caution should be used when adding these to thedatabase, so as to avoid duplication of elements.

In order to place one-lines, you must have at least one system defined in thedesign file.

Steps

1. Select the Define System command.

The System Definition form displays.

2. Select the systems in the From Database column that you want to define in the presentdesign file. To define ALL systems from the reference database in the present designfile, select the Select All button.

The systems you select display in the To Design column and will be defined in thedesign file once you select the Confirm button (√).

— OR —

Select those systems listed in the To Design column that you no longer want definedfor the design file. To remove ALL systems from definition in the design file, select theClear All button.

258

10. Setu

p

Define System________________ The systems you select are deleted from the To Design column and will no longer bedefined in the design file.


— OR —

Select Cancel (X) to exit the command without saving your changes.

259


Define One-Line Type

This command allows you to select any or all available one-line types from the referencedatabase for use in the design file. The One Line Type Definition form displays those one-line types available in the database, as well as those already selected for the current designfile.

If you need one-line types not available to you, you should ask the system/applicationmanager to add them to the reference database. Caution should be used when adding these tothe database, so as to avoid duplication of elements.

You must define one-line types for the design file before you can use relatedcommands, such as Set Active One-Line Type and Place One-Line Type.

Steps

1. Select the Define One-Line Type command.

The One Line Type Definition form displays.

2. Select the one-line types in the From Database column that you want to define in thepresent design file. To define ALL one-line types from the reference database in thedesign file, select the Select All button.

The one-line types you select display in the To Design column and will be defined inthe design file once you select the Confirm button (√).

— OR —

Select those one-line types listed in the To Design column that you no longer wantdefined for the design file. To remove ALL one-line types from definition in the designfile, select the Clear All button.

260

10. Setu

p

Define One-Line Type________________ The one-line types you select are deleted from the To Design column and will no longerbe defined in the design file.


— OR —


261


Set Symbology Control

This command defines the standard graphic symbology for all systems and one-line types in adesign file. The Set Graphic Symbology Control form displays a matrix of systems andone-line types and the standard graphic symbology assigned to each system (all one-line typeswithin a system are originally assigned the same symbology).

When you enter a new design file, all symbology is taken from the system defaults.Therefore, to make any changes in symbology, you must first use the Set Symbology Controlcommand to specify the systems and one-line types that can be changed. You can specify theone-line types for which to change the standard symbology by setting them to override mode.

In cases where you do not specify overrides for the one-line types within a system, those one-line types will use a system default. The Symbology Control command allows you to set upthe symbology details for all the override cases within a system. You can also modify thesystem default symbology details if necessary. For more information, seeSymbology Control, page 264 .


You must have defined at least one system and one-line type in the design file. For moreinformation, see Define System, page 258 andDefine One-Line Type, page 260 .

262

10. Setu

p

Steps________________

Steps

1. Select the Set Symbology Control command.

The Set Graphic Symbology Control form displays.

2. Using your cursor, select the individual area that matches a system and one-line type to"turn on" an override for that case.

— OR —

Toggle the Available button in each field to None to change the defaults symbology forall one-line types within a system. Each one-line type within the system will then haveits own symbology defined, so default symbology is not necessary for that system.

— OR —

Select a one-line type from the list to "turn on" the override for that type in all systems.

The Override setting displays in the appropriate field(s).

— OR —

Select the individual Override settings you wish to "turn off" (return to default status).To turn off ALL selected Override settings, select the No Overrides button.

The Override settings you selected are deleted from the Override field and the defaultsettings restored.


— OR —


263


Symbology Control

This command defines, reviews, and modifies the graphic symbology for those one-line typesyou specified using the Set Symbology Control command (see Set Symbology Control, page262 for more information about this command).

The Symbology Control form displays the current symbology settings for all systems andcorresponding one-line types.

You must have at least one system and one-line type defined for the design filein order to use this command.

System — Displays the system for which you can currently change the symbologysettings. The display list contains a list of available systems. To change the displayedsystem, select another system from the list, or select the field, and key in a systemname.

One Line Type Overrides — Displays the one-line type within the displayed systemfor which you can change the symbology settings. The display list contains a list ofavailable one-line types within the currently displayed system.

If you have not set overrides for all one-line types within a system,System Default will display in the One-Line Type display list.

To change the displayed one-line type (or system default), select another one-line typefrom the list, or select the field, and key in the new value.

Symbology — Displays the symbology settings for the selected system and one-linetype. You can review and edit these settings. To change a value in the list, select thefield, and key in a new value.

264

10. Setu

p

Symbology Control________________

Steps

1. Select the Symbology Control command.

The Symbology Control form displays.



— OR —


265


Set Text Defaults

This command defines, reviews, and modifies the MicroStation default parameters for text,text nodes, and engineering units. You will enter all values using the Text form.

Field Descriptions

Font — Displays the default font style number.

Height — Displays the default text height in a ratio of master units to sub units (#:#).

Width — Displays the default text width in a ratio of master units to sub units (#:#).

Line spacing — Displays the default vertical spacing between lines of text in a ratio ofmaster units to sub units (#:#).

Line length — Displays the default length for lines of text in a ratio of master units tosub units (#:#).

Text String — These buttons and the associated display list display the currentjustification for text strings in the design file. You can modify the justification usingeither the buttons or the list. To change the current text string justification, select thebutton that graphically represents the desired justification, or select a value from thelist.

Text Nodes — These buttons and the associated display list display the currentjustification for text nodes in the design file. You can modify the justification usingeither the buttons or the list. To change the current text node justification, select thebutton that graphically represents the desired justification, or select a value from thelist.

266

10. Setu

p

Set Text Defaults________________ Engineering Units — These fields (Master units, Sub units, and Positional units)display the current PDS engineering units. You can only review the displayed settings.

Steps

1. Select the Set Text Defaults command.

The Text form displays.



— OR —


267


Set Conduit Sizing Attributes

This command defines which conduit attributes will be used in selecting the correct sizeconduit in the Conduit Sizing command.

Steps

1. Select the Set Conduit Sizing Attributes command.

The Set Conduit Sizing Attributes form displays.

2. Define which attributes to use.

— THEN —

Select Confirm (√) to save your changes and exit the form.

— OR —

Select Cancel (X) to exit the form without saving any changes.

268

10. Setu

p

Create Cell Commands________________

Create Cell Commands

The Create Cell commands create various types of raceway cells necessary for creating EERaceway models. The cells you create using this command are stored, along with all existingcells, in your cell library.

You must have a cell library attached to the design file in order to activate the Create Cellcommands. EE Raceway is delivered with a sample cell library, rway.cel, which resides inwin32app\eerway\dgn. If you want to modify the delivered library, copy it to a non-production directory, and modify the copied version. You must have write access to thelibrary before modifying it.

This section contains detailed descriptions of the following commands:

Create Model Cell — Creates or recreates a model cell to carry the sheet name of adrawing.

Create Equipment Pointer Cell — Creates an equipment pointer symbol for laterplacement in the design file.

Create Drop Point Cell — Creates a drop point symbol for later placement in thedesign file.

269


Using the Create Cell Commands




You must have a cell library with read/write privileges attached to the design file. To displaya list of available cell libraries, key in rc= in the MicroStation Command Window.

You should be familiar with precision input and its functions before using any of the CreateCell commands, because it is through the Precision Input form that you will enter values forthe placement of points and for the location of raceway elements. For detailed informationabout precision input, seePrecision Input Form, page 119 .

Group Workflow

There is no required or suggested sequence for using the Create Cell commands.



270

10. Setu

p

Create Model Cell________________

Create Model Cell

This command allows you to create a model cell and to store that cell permanently in your celllibrary.

Make sure you have a cell library attached to the design file before using thiscommand and be sure the library is not read only. To display a list ofavailable cell libraries, key in rc=.

Steps

1. Select the Create Cell command.

The Select cell type form displays.

2. Select the Model button from the form.

3. Enter first fence point

If no fence is defined, place the first data point of a fence block diagonal. Include allthe graphic elements of the component. Be sure to include any existing annotation thatyou want as part of the cell. Make enough room within the fence to include all textelements within the fence. Do not include any elements within the fence that you donot want as part of the cell.

— OR —


4. Enter second fence point

Place the second data point of a fence block diagonal. Include all the graphic elementsof the component. Be sure to make room to include any text elements within the fence.

5. Accept/reject fence

(This is the first prompt if a fence is already established when you start the command.)

Press <D> to Accept the fence.

— OR —

Press <R> to reject the fence. Go to step 2.

271


6. When you accept the fence, a form displays prompting you to Close or Annotate.

If you select Annotate, go to step 7.

If you select Close, go to step 10.

7. The Annotate Element form displays, allowing you to add annotation to the cell anddisplaying those values already in the cell.

8. To enter a value, select the Column value field, key in the value, and press <Return>.To make a change or correction, select the field again and key in the new value. Turnthe Display toggle on for any text attribute you want displayed in the cell. For detailedinformation about the annotation form, see Annotate Element, page 178 .

When complete, save your modifications by selecting Confirm (√).

— OR —

Select Cancel (X) to exit the command without saving the changes. Return to step 7.

9. Placing sheet, etc.Data point <D> to place, reset <R> to skip

For all new displayed text attributes, you are prompted to place any new values. Anyvalues (including empty enter data fields) already present in the cell are editedautomatically. The prompt tells you which value you are placing.

Underlines (for empty enter data fields) will not be displayed on thescreen cursor like other new values. However, they will be placed in thecell (and visible) when you press <D>.

272

10. Setu

p

Create Model Cell________________ Move the text to the desired position in the drawing and press <D>.

The value is placed in the cell as you indicated. This step repeats for each enter datafield. When complete, you are returned to step 7. All new non-displayed text attributesare placed at the center of the active fence.

10. If you try to close with the fence around invalid elements, various error messages willdisplay. Refer toError Messages, page 377 for descriptions of these messages.

When you select Close, the Close cell parameters form displays.

11. To enter a value, select the input box, key in the value, and press <Return>. To make achange or correction, select the input box again and key in the new value. You mustenter a cell name. The description is optional. When complete, confirm your entriesby selecting Confirm (√).

12. Identify cell origin

Place a data point to define the cell origin. This point must be within the graphic extentof the fenced elements.

The cell is created and placed into the attached cell library. The messageAccept/reject Successful Completion displays as long as the fence is still active.

— OR —

Press <R> to reject the cell. Return to step 11.

273


Create Equipment Pointer Cell

This command allows you to create a equipment pointer symbol and to store that cellpermanently in your cell library.


Steps

1. Select the Create Cell command from the command menu.


2. Select the To Equipment button from the form.



— OR —






Press <D> to accept the fence.

— OR —

Press <R> to reject the fence. Go to step 2.

274

10. Setu

p

Create Equipment Pointer Cell________________







— OR —


9. Placing equipment tag, etc.Data point <D> to place, reset <R> to skip



275

EE Raceway Modeling Reference Guide - February 2003________________ Move the text to the desired position in the drawing and press <D>.








— OR —


276

10. Setu

p

Create Drop Point Cell________________

Create Drop Point Cell

This command allows you to create a drop point symbol and to store that cell permanently inyour cell library. Your cell library must contain a drop point cell for the placement of one-lines in the design file (the drop point establishes connectivity between an RCP and a one-linewhere the two are of a different one-line type).


Steps

1. Select the Create Cell command from the command menu.


2. Select the Drop Point button from the form.



— OR —






Press <D> to accept the fence.

— OR —

Press <R> to reject the fence. Go to step 2.277








— OR —


9. Placing drop point tag, etc.Data point <D> to place, reset <R> to skip



278

10. Setu

p

Create Drop Point Cell________________ Move the text to the desired position in the drawing and press <D>.








— OR —


279


Model Commands

These commands are used to place and manipulate model information in your design file.

Commands

Lock Model — Locks the symbology control parameters, the defined systems, and thedefined one-line types.

Move Model Annotation — Moves the model annotation within the design file.

Unlock Model — Unlocks the model.

Annotate Model — Adds, changes, or reviews the sheet name in a model.

280

10. Setu

p

Using the Model Commands________________

Using the Model Commands


You may want to use the Lock Model command after performing basic design setups to lockthe symbology control parameters and the defined systems and one-line types. However, youcan use these commands throughout the design session.

You must lock the model in order to load the drawing into the project database.


You should complete the symbology and basic design file setups before locking the model.

You should be familiar with precision input and its functions before using any of the Modelcommands, because it is through the Precision Input form that you will enter values for theplacement of points and for the location of raceway elements. For detailed information aboutprecision input, seePrecision Input Form, page 119 .

Group Workflow

Before you can annotate or move annotation in the model, you must have locked the modelusing the Lock Model command.



281


Lock Model

This command locks the model. The locking of the model locks the symbology controlparameters and the defined systems and one-line types. Therefore, you should lock yourmodel after setup, but before placing graphics in a file in order to protect your parameters.

You must lock the model in order to load the drawing into the project database.

Steps

1. Select the Lock Model command.

The model is locked. If the model was locked when you selected this command, themessage Model is already locked displays.

282

10. Setu

p

Move Model Annotation________________

Move Model Annotation

This command moves the model annotation within a design.




Steps

1. Select the Move Model Annotation command.

The Move Model Annotation precision input form displays. The command checks thedesign file for the existing model annotation and places it in drag mode.


Move the annotation to the desired location, and place it.

— OR —

Exit the command.

283


Unlock Model

This command unlocks the model. If you want to change the symbology control or add newsystems and one-line types to a model that has been locked, you must first unlock the modelusing this command.

Steps

1. Select the Unlock Model command.

2. A warning form displays.

3. Select Confirm (√) to unlock the model.

— OR —

Select Cancel (X) to exit the command without unlocking the model.

284

10. Setu

p

Annotate Model________________

Annotate Model

This command adds or changes the annotation for the model. This command cannot preventthe duplication of sheet numbers within a project. The Load Database process, however, willprevent such duplication. The sheet number should be unique for each drawing.

Steps

1. Select the Annotate Model command.

The Annotate Element form displays.

2. Select the Column value field for sheet on the form and key in a new sheet number.

If you want to display the annotation in the model, toggle the Display fields in the formto On.

3. Select Confirm (√) to accept the new annotation.

— OR —


4. If you toggled Display to On, you are prompted to place the annotation in the model.

285


286

11. Ru

ntim

e

Runtime Setup Commands________________

11. Runtime Setup Commands

The Runtime Setup commands allow you to define, modify, and review the active drawingparameters in your design file.

The Runtime Setup palette is activated by selecting Setup from the EE Raceway CommandMenu Bar, then selecting Palette from the resulting pull-down menu.

Commands

Set Active One-Line Parameters — Displays the active one-line parameters, based on thecurrent active one-line type, and allows you to set new active parameters.

Set Active One-Line Type — Displays the current active one-line type and allows you toselect a new active one-line type.

Set Active System — Displays the current active system and allows you to set a new activesystem.

Propagation Setup — Sets the active parameters for propagation in the design file.

Set Active Levels — Displays the current active level(s) and allows you to turn Offdisplayed levels and to turn On new level displays.

Display Element Information — Displays characteristics of selected elements.

287


Using the Runtime Setup Commands




You must have at least one system and one-line type defined in the design file in order to usethese commands. SeeSetup Commands, page 253 for more information about defining systems and one-line types.

Group Workflow




288

11. Ru

ntim

e

Set Active One-Line Type Parameters________________

Set Active One-Line Type Parameters

This command displays the active one-line parameters based on the current active one-linetype you set using the Set Active One-Line Type command (see Set Active One-Line Type,page 294 ).

The Set Active One-Line Type Parameters command allows you to enter values through theappropriate form, which is based on the current active one-line type. For example, if youdefined tray as your active one-line type, then the Active TRAY Parameters form willdisplay when you use this command.

Column name — Displays the aliases for those columns in the database that areassociated with the specified one-line type. You can only review the information in thisfield.

Column value — Displays the current value for the column whose alias displays in theColumn name field. You can review and modify the values in this field.

To change the values associated with a one-line type, select this field, and key in thenew value. You can enter blank spaces into the design, but empty <Return>s enternothing into the design. Entering a space or a text value for an attribute will overridethat value in the reference database. To delete an override on a reference databaseattribute, select the column value field and delete the blank character. Once you havedeleted the override, a value will display in the field only if the value can be retrievedfrom the reference database. Otherwise, the field remains null.

If blanks exist for a field, the cursor will jump to the end of the blanks whenthe field is tagged beyond value.

Save to Memory (M) — Temporarily saves your overrides and specification changes.When you change the active one-line type or end your design session, you lose theoverrides and specifications you saved to memory. The previous set of specificationsbecomes active again.

289

EE Raceway Modeling Reference Guide - February 2003________________ List — Indicates whether or not a column value has an associated codelist. If an *displays in the List column, then the column value has a corresponding codelist. Todisplay the codelist, select the *.

Access — Indicates whether or not you can manipulate a particular column value. Ifyou can view and modify (read and write) the column value, the Access columndisplays a R/W. If you can only view (read) the column value, then it will display anR. You can only review the information in this column.

Display On/Off — Enables or disables the design display for each column value.Where the toggle is On, the value will display in the design where you place it. Youwill be prompted to place displayed values when placing one-lines in the drawing.

EE Reference Database Key — This field allows you to insert an override key in thereference database. When you enter a new value in the EE Reference Database Keyfield, it becomes an override key to the reference database. The key field is updated,and corresponding database values are retrieved and displayed on the annotation form.If the specified key does not exist in the reference database, an error message displaysand the annotation form returns to the previous values. Any annotation you placed inthe drawing will override the reference database defaults on the form.

If you delete the value in this field, a value will automatically redisplay if it can beretrieved from the reference database. Otherwise, the field remains null.

If an override linkage is not present on a device or a title block, then the cell name orthe Default key will be used to locate default data. If the linkage is not present on aconnect point or one-line, the key specified in the user element is used. If no key existsin the user element, the Default key is used. Once you place an override key on anelement, you can modify it, but cannot delete it. To change the displayed value, selectthe field, and key in a new value.

Key Description — This field displays the description from the reference database ofthe current EE Reference Database Key. You can only review the information in thisfield.


Select — Retrieves the row(s) from the specification table that meet the select criteriadefined in the form. The select criteria are those values that display in the Columnvalue column on the lower portion of the annotation form. You can use relationaloperators when keying in your own select criteria.

290

11. Ru

ntim

e

Set Active One-Line Type Parameters________________ If only one row matches the select criteria you provide, then the Column values fill inwith the matching row’s values. If more than one row matches the criteria, then asecond form containing all matching rows displays.

From this form you will select the row(s) containing the desired values. To add valuesfrom the displayed specification table rows, select the row you want, and then selectConfirm (√). If you select Cancel (X), the system cancels the form and retrieves thevalues from the EE spec key field on the original form.

Clear button — This button clears the Column values from the lower portion of theform, and then automatically depresses the Override button to select a different row(s)from the specification table.

Override button — This button allows you to override those columns whose access isRead Only (R). You can activate the Override button by selecting it directly or byselecting the Clear button, which automatically activates it.

291

EE Raceway Modeling Reference Guide - February 2003________________ This command accepts certain relational operators as search criteria. You should be familiarwith the following operators:


Description

= equal to numeric This is the default operator. If you do not enteranother operator, the system assumes =.








% wild card CHAR This operator is a wild card, representing zero ormore characters. The queried values must have everycharacter aside from the % in common with the givenvalue.

_ underline CHAR This operator is a wild card, representing a singlecharacter. The queried values must have everycharacter aside from the underline in common withthe given value.

Steps

1. Select the Set Active One-Line Type Parameters command.

An Active One-Line Type Parameters form displays.



— OR —


292

11. Ru

ntim

e

Set Active One-Line Type Parameters________________

Any value you place with the Set Active One-line Parameterscommand will be entered into the drawing and, optionally, displayed.When you load the project database, these values are loaded into theproject database.

293


Set Active One-Line Type

This command displays all one-line types available in the design file, based on your selectionsfrom the reference database using the Define One-Line Type command (seeDefine One-Line Type, page 260 ). The command also highlights the current active one-linetype and allows you to select a new one from the set of those available.

You must set an active one-line type in order to use the Place One-Line Typecommand.

Steps

1. Select the Set Active One-Line Type command.

The Active One Line Type form displays.

2. From the list, select the one-line type you want to make active.

The one-line type you selected highlights.


— OR —


294

11. Ru

ntim

e

Set Active System________________

Set Active System

This command displays the current active system and all available systems, based on thoseyou selected from the reference database using the Define System command (seeDefine System, page 258 ). Using the Set Active System form, you can select a new activesystem from the set of those available.

You can have multiple systems defined for a single one-line type as a way of defining splittrays or elements. This is done by specifying a system and one or more subsystems. Theactive system is automatically included as a subsystem. The active system determines thesymbology of the one-line type, whereas subsystems do not.

You can have no more than six systems active for each one-line type.

Field Descriptions

Systems — Selects the active system. When a new active system is selected, thesubsystems are all unselected. The active system is automatically included as asubsystem. The active system determines the symbology of the raceway.

Subsystem — Selects the subsystems. While this button is depressed, the Percent andProject Rule can be defined for each subsystem.

Active System — Displays the active system which determines the symbology of theraceway.

Project Rule Set — Displays the Project Electrical Code from the your projectschema’s project table. This is defined in EEmgr with the EE CMS Project Definitionprocess. The Project Rule Set determines which rules can be assigned to the activesystems. If the Project Rule Set is not defined, Project Rules cannot be assigned.

Systems Column — Displays all the available systems. Selecting a row in this fielddefines the Active System or Subsystems.

295

EE Raceway Modeling Reference Guide - February 2003________________ Percent — Displays the current percent space allocation assigned to each of theselected systems. The total space allocation cannot exceed 100 percent. The total ofthe system percents is displayed in the field at the bottom of the Percent column. Allthe selected systems percentages are summed to calculate the total percentage. ThePercent represents the portion of the raceway’s width assigned to that system. ThisPercent is used when calculating the cable fill of the raceway section in the EECMSproduct.

Project Rule — Displays the Project Rule assigned to each of the selected systems forcalculating raceway fill. When a row is selected, a list of available rules for the ProjectRule Set defined with the EE CMS Project Definition process is displayed for reviewand selection. To clear the Project Rule, select the row and select the Cancel (X) on thelist of Rules.

List — Indicates whether or not a Project Rule can be assigned. If an * displays, then aProject Rule can be assigned. To display a list of available rules for the Project RuleSet defined with the EE CMS Project Definition process, select the *.

Steps

1. Select the Set Active System command.

The Active System form displays.

2. Select the system and subsystem(s) you want to make active. To access the list ofsubsystems, press the Subsystem button.

3. Define the percentages and the project rules you want to use.


— OR —


296

11. Ru

ntim

e

Propagation Setup________________

Propagation Setup

This command sets the active parameters for propagating one-line elements in the design file.For additional information about propagation, see The Drawing Process, page 108 .

Field Descriptions

Propagation Style — Defines the active style of propagation.

Smooth - Propagates straight sections and fittings.

Rough - Propagates straight sections only.

Cutback - Propagates straight sections, cutting them back to leave room for fittings.

Propagation Mode — Defines the active propagation mode.

Sketch - Sketches standard straights and fittings, using the dimensions of the crosssections and the transition, radius, and extension on the one-lines and RCPs. Sketchpropagation is considerably faster than Eden propagation, but lacks the detail that Edenpropagation provides.

Eden - Retrieves one-line type and RCP dimensions from specifications in the databaseand from overrides. Propagation sends these dimensions to the Eden symbol.

All fittings you place manually are propagated with Eden, regardless ofthe settings on this form.

Part Verification — Enables or disables part verification. Set the toggle to On toverify that an element exists in the database before you propagate it. Set the toggle toOff to skip part verification before propagation.

297


If Eden is the active propagation mode, part verification will beperformed, regardless of the status of this toggle.

Automatic Propagation — Enables or disables the automatic propagation of elements.

If you set the toggle to On, elements are automatically propagated when placed. Also,any changes you make to an element, like editing the size, that affect the graphicaldisplay of the propagation, will cause the propagation to be deleted and redrawn toreflect the change.

When the toggle is set to Off, automatic propagation is disabled.

Steps

1. Select the Propagation Setup command.

The Propagation Setup form displays.

2. Define the form parameters to meet your specifications.

3. Select Confirm (√) to save your changes and to exit the command.

— OR —

Select Cancel (X) to exit the command without saving any changes to the form.

298

11. Ru

ntim

e

Set Active Levels________________

Set Active Levels

This command displays the current active level(s) and allows you both to turn off any activelevels and to activate new levels.

View — Displays the active view. All level display settings on the form are valid forwhatever view is active. To change the active view, select a value from the list, orselect the field, and key in a new value.

Levels — Indicate what levels display in the design. They also allow you to turn off oron the display of some or all available levels.

1 - 63 indicate whether or not each available level displays in the design. When a levelhas its display turned on, the button appears to be depressed. To turn on or off thedisplay of a particular level, select the appropriate level number.

All On — Turns on the display of all levels in the design.

All Off — Turns off the display of all levels in the design.

Restore — Returns the display of levels in the selected view to its state prior toentering the Set Active Levels command.

Turn Levels On/Off — This toggle enables or disables the display for the levelsassociated with the one-line types in your design file.

To turn on or off the display of a particular level, select the Turn Levels On/Offtoggle, and then select the desired level number displayed in the Systems/One Line list.

Systems/One Line — Displays the available systems, their corresponding one-linetypes, and the levels on which they display. You can only review the system and one-line information in these fields, but can select the level numbers (in combination withthe Turn Levels On/Off toggle).

299

EE Raceway Modeling Reference Guide - February 2003________________ Graphics — Displays the level display for title block annotation in the design file.

Steps

1. Select the Set Active Levels command.

The Levels form displays.


3. Select Confirm (√) to save your changes and to exit the command.

— OR —


300

11. Ru

ntim

e

Display Element Information________________

Display Element Information

This command displays raceway element characteristics. If either a one-line, a straightsection, a fitting within a run, or an RCP within a run is selected, then run information isdisplayed. This information includes: segment lengths, location and radius of each bend inthe run, and coordinate location of ends and bends.

If a fitting or an RCP that is at the termination of a run is selected, then the four key attributesassociated with the fitting are displayed.

Steps

1. Select the Display Element Information command.


Select the element you want to review.

— OR —


3. Accept/reject

Press <D> to accept the element and display that element’s information. Return to step2.

— OR —

Press <R> to reject the highlighted element and select another element. Return to step2.

301


302

12. Utilities

Utilities Commands________________

12. Utilities Commands

The Utilities commands highlight elements within your design file based on the identificationcriteria (ASID ID, sector/word position) you provide. You can also use the commands todisplay the identification criteria of specified elements and the system and one-line type of anidentified element. In addition, you can highlight propagation errors in the design file.

Commands

Toggle Construction Display On/Off — Turns the display ofconstruction class elements on or off.

Highlight Element by Sector/Word — Highlights elements with a givensector/word position.

Highlight Element by ASID ID — Highlights an element with a given

ASID ID.

Highlight Element by Link — Highlights an element with given entityand mslink values.

Highlight Propagation Errors — Identifies existing propagation errors ina design file.

Display Sector/Word Value — Displays the sector/word position of anidentified element.

Display Element Type and ASID ID — Displays the element type andASID ID of an identified element.

Display Link — Displays the entity and mslink values of an identifiedelement.

Display System and One-Line Type — Displays the associated system

and one-line type of an identified element.

303


Coordinate System — Activates the Design Volume Coordinate Systemor Plant Coordinate System associated with the design file, or shows thecoordinate system currently active.

304

12. Utilities

Using the Utilities Commands________________

Using the Utilities Commands




You must be familiar with precision input and its functions before using any of the Modifycommands, because it is through the Precision Input form that you will enter values for theplacement of points and for the location of raceway elements. For detailed information aboutprecision input, seePrecision Input Form, page 119 .

Group Workflow

In general, you will use those commands that display the attribute information of an element(Display ASID ID, for example) before the commands that highlight elements based on theattribute information you specify (Highlight Element by ASID ID, for example).



305


Toggle Construction Display On/Off

This command turns On and Off the display for construction elements within each individualview in the design file.

All non-displayed EE text elements are automatically placed in construction class. Therefore,this command allows you to view all the non-displayed EE elements as well as any otherconstruction class elements.

Steps

1. Select the Toggle Construction Display On/Off command from the menu.

The top of the prompt area displays all views in which the Toggle ConstructionDisplay On/Off command is toggled to On.

2. Select view

Place a data point in the view in which you want the annotation display toggled On orOff. When construction display is On, the view number displays in a prompt.

3. Press <R> to exit the command.

Once you have exited the command, select the Update View command to see theresults of the display toggle.

306

12. Utilities

Highlight Element by Sector/Word________________

Highlight Element by Sector/Word

This command highlights elements by a sector/word position that you specify. The positionof the sector and word are compatible with EDG, and both are relative to 1. If the position isvalid, the element highlights, but is not added to a working set. If the element is part of acomplex element, the entire complex element highlights. The sector/word position must bethe location of an element type 2 (cell), 3 (line), 4 (line string), 6 (shape), 7 (text node), or 17(text).

Highlight Sector/Word With Filename

You can specify a filename instead of the sector/word position to highlight an element. Thefile must contain the sector/word position of the element(s) you want to highlight. The filewill display in a form on the screen, allowing you to select the sector/word value from thedisplayed file. If you do not specify a pathname for the file, the command searches for it inthe <current_project>/rway/tmp directory.

Steps

1. Select the Highlight Element By Sector/Word command.

2. Key in sector and word value or file name

Key in the sector and word value separated by a space.

— OR —

Key in the name of a file containing the sector and word values. Go to Step 4.

3. Point to view for window

Identify the view in which you want the element to highlight.

4. Element highlighted

The element with the specified sector and word highlights in the view you identified.

Key in another sector/word combination to continue highlighting elements by sectorand word. Press <Esc> to exit.

307


5. Select sector and word value from form

A File Display form displays after you enter the filename.

Identify a line that contains a sector and word value.

After you select a line, select Confirm (√) to accept the sector and word value in theline. Go to Step 6.

— OR —

Select the Return button to cancel the file display form. Return to Step 1.

— OR —



Identify the view where you want the element highlighted.

7. Element highlighted Point to continue/Reset to exit the file

The element with the specified sector and word highlights in the view you identified.

Press <D> to select another sector/word value from the File Display form. (When youpress <D> the form redisplays.) Go to Step 4.

— OR —

Press <R> to exit the file you identified in Step 1. Return to Step 1.

308

12. Utilities

Highlight Element by ASID ID________________

Highlight Element by ASID ID

This command highlights elements by an ASID identification (ID) that you specify. If theASID ID you specify is valid, the raceway element highlights, but is not added to the workingset.

Highlight ASID ID With Filename

You can specify a filename instead of the ASID ID to highlight an element. The file mustcontain the ASID ID of the element(s) you want to highlight. For example, to see wherepropagation errors exist in your design file, you can specify the file pro.err. The file willdisplay in a form on the screen, allowing you to select the ASID ID from the displayed file. Ifyou do not specify a pathname for a file, the command searches for it in the<current_project>/rway/tmp directory.

Steps

1. Select the Highlight Element By Asid Id command.

The Select hilite asid mode form displays.

2. Select the appropriate Highlight by ASID ID button.

The All Elements button highlights all raceway elements associated with the elementhaving the given ASID ID: the element itself and all of its children.

The Parent of Elements button highlights the raceway elements that are the parents ofthe element having the given ASID ID.

The Children of Elements button highlights the raceway elements that are the childrenof the element having the given ASID ID.

The Only the Element button highlights only the raceway element having the givenASID ID.

— OR —

Select Cancel to exit the command.

309


3. Key in asid id or file name

Key in the ASID ID.

— OR —

Key-in the filename of a file containing the ASID IDs. Go to step 6.

— OR —

Press <R> to select a different Highlight by ASID ID mode. Return to step 2.

— OR —

Press <Esc> to exit the command. Return to step 1.


Identify the view in which you want the elements highlighted.


The raceway element(s) associated with the specified ASID ID highlight in the view youidentified.

Key in another ASID ID to continue highlighting raceway elements. Continuehighlighting the elements according to the specified Highlight by ASID ID mode.

— OR —

Press <Esc> to exit.

— OR —

Press <R> to select a different Highlight by ASID ID mode. Return to step 2.

6. Select asid id from form

After you enter the filename, a file display form displays.

310

12. Utilities

Highlight Element by ASID ID________________ Select a line that contains an ASID ID.

7. After you select a line, select Confirm (√) to accept the ASID ID in the line. Go to step8.

— OR —

Select the Return button to cancel the File Display form. Return to step 2.

— OR —

Select Cancel (X) to modify the highlight by asid mode. Return to step 1.


Identify the view in which you want the element(s) highlighted.

9. Point to continue/Reset to exit the file

The element(s) associated with the specified ASID ID highlight in the view youidentified.

Press <D> to select another ASID ID from the file display form. (When you press <D>the form redisplays.) Go to step 5.

— OR —

Press <R> to exit the file you identified in step 3. Return to step 3.

311


Highlight Element by Link

This command highlights elements by given entity (table) and mslink values that you specify.If the entity and mslink are valid, the element highlights, but is not added to a working set. Ifthe element is part of a complex element, the entire complex element highlights. The entityand mslink values must correspond with an element type 2 (cell), 3 (line), 4 (line string), 6(shape), 7 (text node), or 17 (text).

Highlight Link With Filename

You can specify a filename instead of the entity and mslink combination to highlight anelement. The file must contain the entity and mslink of the element(s) you want to highlight.The file will display in a form on the screen, allowing you to select the mslink from thedisplayed file. If you do not specify a pathname for the file, the command searches for it inthe <current project>/rway/tmp directory.

Steps

1. Select the Highlight Element By Link command.

2. Key in entity and mslink (###:###) or filename

Key in the entity and mslink values separated by a :.

— OR —

Key in the name of a file containing the entity and mslink values. Go to Step 4.


Identify the view in which you want the element to highlight.


The element with the specified entity and mslink values highlights in the view youidentified.

Key in another entity/mslink combination to continue highlighting elements by mslink.Press <Esc> or <R> to exit.

5. Select entity/mslink value from form

A File Display form displays after you enter the filename.

Identify a line that contains the entity and mslink values.

312

12. Utilities

Highlight Element by Link________________ After you select a line, select Confirm (√) to accept the entity and mslink values in theline. Go to Step 6.

— OR —

Select the Return button to cancel the File Display form. Return to Step 1.

— OR —



Point to the view where you want the element highlighted.

7. Element highlighted Point to continue/Reset to exit the file

The element with the specified entity and mslink values highlights in the view youidentified.

Press <D> to select more entity and mslink values from the file display form. (Whenyou press <D> the form redisplays.) Go to Step 4.

— OR —

Press <R> to exit the file you identified in Step 1. Return to Step 1.

313


Highlight Propagation Errors

This command highlights propagation errors in the design file.

Steps

1. Select the Highlight Propagation Errors command.

The pro.err file displays.

2. Review the errors listed on the form. To highlight a particular error(s) in the designfile, select the error(s) from the list, and select Confirm (√).

The propagation error(s) highlights in the design file, and the pro.err form redisplays.

— OR —

Exit the form without highlighting any propagation errors.

3. Continue highlighting propagation errors. Go to step 2.

— OR —

Select Reset or Cancel (X) to exit the command.

314

12. Utilities

Display Sector/Word Value________________

Display Sector/Word Value

This command displays the sector and word position, in the MicroStation command window,of an identified element.

Steps

1. Select the Display Sector/Word command.

2. Identify element

Select the element to display the sector/word for, and accept it with a <D>.

The sector and word for the selected element displays in the MicroStation commandwindow.

— OR —


315


Display Element Type and ASID ID

This command displays the element type and the ASID identification (ID), in theMicroStation command window, of an identified element.

Steps

1. Select the Display Element Type and ASID ID command.

2. Identify element

Select the element for which to display the ASID ID and accept it with <D>.

The element type and ASID ID display in the MicroStation command window.

— OR —

Press <R> or <Esc> to exit the command.

316

12. Utilities

Display Link________________

Display Link

This command displays the entity (table) and mslink, in the MicroStation command window,of an identified element.

Steps

1. Select the Display Link command.

2. Identify element

Select the element you want to display the link for and accept it with <D>.

The entity and mslink values display in the MicroStation command window in thefollowing format: Entity (table number) = <value>, mslink = <value>

— OR —

Press <R> or <Esc> to exit the command.

317


Display System and One-Line Type

This command displays the system and one-line type associated with an element you identify.




Steps

1. Select the Display System and One-Line Type command from the menu.

The precision input form displays, along with the Print System and One-Line Typeform.


Identify an element in the design file.


— OR —

Exit the command.

318

12. Utilities

Display System and One-Line Type________________



The fields on the form fill with information about the element’s one-line type, system,and subsystems (if applicable). The system prompts you to identify another element.

— OR —


The system prompts you to identify another element. Go to step 2.

4. Continue identifying elements in the design file. Go to step 2.

— OR —

Exit the command.

319


Active Coordinate System

This palette provides the Active Design Volume Coordinate System, Activate PlantCoordinate System, and Show Active Coordinate System commands.

Commands

Activate Design Volume Coordinate System — Activates the Design VolumeCoordinate System (DVCS) allowing you to define a local coordinate system for aparticular model.

Activate Plant Coordinate System — Activates the Plant Coordinate System (PCS).The Plant Coordinate System is common to all models and drawings in a project.

Show Active Coordinate System — Displays the active coordinate system in thestatus field.

When the coordinate system is switched between the PCS and DVCS, modelgraphics do not rotate to reflect the active coordinate system. Instead, thecoordinate system rotates when the active coordinate system is changed.

Activate Design Volume Coordinate System

The Activate Design Volume Coordinate System command allows you to work in theDesign Volume Coordinate System.

Activate Plant Coordinate System

The Activate Plant Coordinate System command allows you to work in the PlantCoordinate System. The Plant Coordinate System is common to all models and drawings in aproject. The Plant Coordinate System uses this global coordinate system to maintain therelationships among the various models. This becomes important when attaching referencemodels to the active model.

Show Active Coordinate System

The Show Active Coordinate System command displays the active coordinate system in thestatus field. If you desire to change the coordinate system, you can select either the ActivateDesign Volume Coordinate System or Activate Plant Coordinate System commands.

320

13. Datab

ase

Database Commands________________

13. Database Commands

The Database commands are used to load and run reports from the database. The Databasepalette is activated by selecting Database from the EERWAY Command Menu Bar, thenselecting Palette from the resulting pull-down menu.

Topics

Load Database — Loads the project database with information generated from the EERaceway drawing.

Reports — Displays the information in an EE Raceway database.

Rulecheck — Displays the design rule errors occurring in the design process.

321


Using the Database Commands


Use these command to run limited database commands while still in the graphic designsession.


Refer to the individual command descriptions for any requirements which may be necessarybefore using each command.

Group Workflow

You must load the database before you can run a report or rulecheck.


Because the operating sequence, command key-ins, and screen prompts vary for eachcommand, instructions for using these commands are described in each individual commandsection.

322

13. Datab

ase

Load Database________________

Load Database

This command loads a relational database with information generated by the EE Racewaydesign file. Information in the design file is merged with information from the referenceschema and loaded into the project schema.

All RCP’s and segments must have a tag number before using this command.

When you run the Load Database command on a design file that has been loaded previouslyinto the database, the command removes the occurrences of the previous load and completelyreloads the design file.

You must create a RIS schema on an existing relational database before loading, using theDatabase Utilities option from the EE Project Menu Both a project and a reference schemamust exist before running the Load Database process.

This process calculates the following values:

Table Name Column Name Comments

rcp_to_drw pds_east* The PDS east coordinate of the corresponding RCP’sorigin.

rcp_to_drw pds_north* The PDS north coordinate of the correspondingRCP’s origin.

rcp_to_drw pds_elev* The PDS elevation coordinate of the correspondingRCP’s origin.

rcp_to_sys ee_percent*** Indicates what portion of the corresponding RCP isset aside for the corresponding system.

drop_point ee_dist_down_ol** The distance down the one-line to the point on theone-line closest to the drop point origin.

drop_point ee_dist_to_rcp** The orthogonal distance from the drop point origin tothe RCP’s origin, and the orthogonal distance fromthe drop point origin to the closest point on the one-line.

one_line ee_ol_length** The total graphical length of the one-line in masterunits.

ol_to_sys ee_percent*** Indicates what portion of the corresponding one-lineis set aside for the corresponding system.

323

EE Raceway Modeling Reference Guide - February 2003________________ straight ee_tl_length The graphical length of the straight in master units.

straight pds_east* The PDS east coordinate of the center point of thestraight’s range.

straight pds_north* The PDS north coordinate of the center point of thestraight’s range.

straight pds_elev* The PDS elevation coordinate of the center point ofthe straight’s range.

str_to_sys ee_percent*** Indicates what portion of the corresponding straightis set aside for the corresponding system.

fitting pds_east* The PDS east coordinate of the center point of thefitting’s range.

fitting pds_north* The PDS north coordinate of the center point of thefitting’s range.

fitting pds_elev* The PDS elevation coordinate of the center point ofthe fitting’s range.

fit_to_sys ee_percent*** Indicates what portion of the corresponding fitting isset aside for the corresponding system.

* The Raceway bill of material by volume report relies on these columns to be in the fittingand straight tables. The columns are optional for Load Database.

** You can override the value for these columns by annotating the appropriate elements in thedesign file.

*** These values indicate the portion of a split raceway dedicated to each system withinthe split raceway.

324

13. Datab

ase

Steps________________

Steps

1. Select Load database command.

The Load database screen displays.

2. Enter error and output filenames.

Key in unique filenames in the Error file and Output file fields, or accept thedisplayed defaults.

The default error and message files will be overwritten every time theprocess runs. You must specify unique filenames to save the defaultfiles.

3. Accept will load database.

When you are finished completing the input information, select Confirm (√), and theprocess begins.

When complete, the process will return one of two messages (described below) to thescreen.

Messages

Error occurred during process

If any errors occur, the message above displays. The error file lists all the errors thatoccurred during processing. This file will be displayed automatically to the screen,where you may review the errors.

Process successfully completed

If no errors occurred, the message above displays. The message file is created on everyrun of the process, and is displayed automatically to the screen. It lists everything thatwas loaded into the database.

325


Report

This command accesses the standard EE Raceway reports. These reports report on the projectand reference databases. You must load the project database before running any reports.

All reports are kept in the /reports directory; see Create Project for thedirectory structure.

Overview

This section contains general information about running all EE Raceway reports. SeeReports, page 545 for more detailed information about individual reports.

The system manager can change the names of the reports that display in thelisting area and can add additional reports by editing the report.dat file(win32app\eerway\data).

When you process a report, an input screen displays, allowing you to enter all input necessaryto run the report.

Key in any information that is not supplied by default. You can change the name of theoutput file or error file. To change the output filename, select the output file box and key in anew name. (No file extension is automatically appended to the name you key in.)

326

13. Datab

ase

Report________________

If you want to save reports throughout a project, you should name the output filesyourself. If a new output file has the same name as an existing file, the new filewill overwrite that file. You should give each report you want to save a uniquename.

Steps

1. Select the Report command.

2. Select the report you want to run from the list.


4. Define the report input form as needed and select Confirm (√) to process the report.


When running a Bill of Materials by Volume report, you are required to define a low and highrange in PDS coordinates. These low and high ranges define a cubic volume from which thereport is pulled.

Any Raceway component extending outside the clipping volume defined by the High andLow Range Coordinates will not be included in the report output.

You can find the coordinates you want to use by using the active point coordinate display onthe precision input form. The coordinate values need to be in subunits and entered in the formfield with a space between the coordinates: easting northing elevation For example, 234532 34

It should be understood that westing and southing coordinates must be thenegative of their opposite directional coordinate. For instance, a westingcoordinate of 100 should be keyed in as a value of -100 in the easting

327

EE Raceway Modeling Reference Guide - February 2003________________ direction, and a southing coordinate of 3000 should be keyed in as a value of-3000 in the northing direction.

328

13. Datab

ase

Rule Checks________________

Rule Checks

This command accesses the standard EE Raceway Rule Checks. These rule checks arereports that identify violations of certain design rules by working on the project database. Youmust load the project database before running any rule checks.

Overview

This section contains general information about running all EE Raceway rule checks. Formore detailed information about each rule check, see Reports, page 545 .

The system manager can change the names of the reports or add new reports tothe listing area by editing the rule_chk.dat file in win32app\eerway\data.

When you process a rule check, an input screen displays.

The name of the rule check report displays at the top. Accept the default information thatdisplays in the input fields, or change that information according to your specifications.

329


If you want to save reports throughout a project, you should name the output filesyourself. If a new output file has the same name as another file created previously,the new file will destroy the previously created file. You should give each reportthat you want to save a unique name.

Steps

1. Select the Rule command.

2. Select the rule check report you want to run from the listing area.


4. Define the input form as needed and select Confirm (√) to process the rule checkreport.

330

14. EE

RW

AY

P

rocesses

Raceway Processes________________

14. Raceway Processes

This chapter provides detailed descriptions of EE Raceway processes. You will run all EERaceway processes from the Process menu found on the EE Raceway Drawing menu. (SeeProcess in the section entitled EE Raceway Environment for information about running allprocesses.) The individual EE Raceway processes are described in the following sections:

Load Database — Loads the project database with information generated from the EERaceway drawing.

Unload Design — Removes all the information associated with a particular drawingfrom the project database, based on the design filename you specify.

Unload Sheet — Removes all the information associated with a particular drawingfrom the project database, based on the internal sheet name you specify.

Cleanup Database — Removes any data from a project database that is not currentlyassociated with a design in the project’s ../rway/dgn directory.

Create Interference Envelope (default name) — Reads the design file and creates adata file that contains envelopes for input to Plant Design interference detection tasks.

Create Interference Envelope (given name) — Reads the design file and creates adata file, with the name you specify, that contains envelopes for input to Plant Designinterference detection tasks.

331


Load Database

This process loads a relational database with information generated by an EERWAY designfile. Information in the design file is merged with information from the reference schema andloaded into the project schema.

1. You must create a RIS schema on an existing relational database before

loading, using the Database Utilities option from the EE Project Menu.Both a project and a reference schema must exist before running theLoad Database process.

2. Load database tracks drawing information based on the "Drawing"table of the project database. Thus, you must annotate the drawing ormodel and enter the unique "SHEET" information, using the LockModel and the Annotate Model commands respectively.

This process calculates the following values:

Table Name Column Name Comments

rcp_to_drw pds_east* The PDS east coordinate of the corresponding RCP’sorigin.

rcp_to_drw pds_north* The PDS north coordinate of the correspondingRCP’s origin.

rcp_to_drw pds_elev* The PDS elevation coordinate of the correspondingRCP’s origin.

rcp_to_sys ee_percent*** Indicates what portion of the corresponding RCP isset aside for the corresponding system.

drop_point ee_dist_down_ol** The distance down the one-line to the point on theone-line closest to the drop point origin.

drop_point ee_dist_to_rcp** The orthogonal distance from the drop point origin tothe RCP’s origin, and the orthogonal distance fromthe drop point origin to the closest point on the one-line.

one_line ee_ol_length** The total graphical length of the one-line in masterunits.

ol_to_sys ee_percent*** Indicates what portion of the corresponding one-lineis set aside for the corresponding system.

straight ee_tl_length The graphical length of the straight in master units.straight pds_east* The PDS east coordinate of the center point of the

straight’s range.straight pds_north* The PDS north coordinate of the center point of the

straight’s range.straight pds_elev* The PDS elevation coordinate of the center point of

the straight’s range.

332

14. EE

RW

AY

P

rocesses

Load Database________________ str_to_sys ee_percent*** Indicates what portion of the corresponding straight

is set aside for the corresponding system.fitting pds_east* The PDS east coordinate of the center point of the

fitting’s range.fitting pds_north* The PDS north coordinate of the center point of the

fitting’s range.fitting pds_elev* The PDS elevation coordinate of the center point of

the fitting’s range.fit_to_sys ee_percent*** Indicates what portion of the corresponding fitting is

set aside for the corresponding system.

* The Raceway bill of material by volume report relies on these columns to be in the fittingand straight tables. The columns are optional for Load Database.

** You can override the value for these columns by annotating the appropriate elements in thedesign file.

*** These values indicate the portion of a split raceway dedicated to each system withinthe split raceway.

Steps

1. Select Load database from the Process menu, and select Confirm (√).

The Load database screen displays.

2. Enter drawing name.

Select a design file from the Drawing List or key in a design filename (you mayspecify multiple design files).

333





4. Select the desired operating mode.

The current operating mode is displayed in a box at the lower right of the screen.

You may choose between Foreground, Background, and Batch operating modes formost processes (see Process, page 64 ).

5. Confirm your selections.

When you are finished completing the input information, select Confirm (√), and theprocess begins. When complete, the process will return one of two messages (describedbelow) to the screen.

Messages


If any errors occur, the message above displays. The error file lists all the errors that occurredduring processing. This file will be displayed automatically to the screen, where you mayreview the errors.


If no errors occurred, the message above displays. The message file is created on every run ofthe process, and is displayed automatically to the screen. It lists everything that was loadedinto the database.

You can view both files using the Output option on the Utilities page.

334

14. EE

RW

AY

P

rocesses

Batch File Option________________

Batch File Option

The load database process can be executed from a batch file. Setup an rway.bat file to exportthe necessary Microstation and EERWAY environment variables to execute the load databaseprocess. Include the following EERWAY environment variables:

EES_REFDB — RIS Schema name for reference database

EE_SCHEMA — RIS Schema name for project database

EERD_MSGS — Directory path for EERWAY message files

EERD_TBLS — Directory path for EERWAY database table files

Example of rway.bat:

SET MS=D:\WIN32APP\USTATIONSET MS_EXE=D:\WIN32APP\USTATIONSET EES_REFDB=CERT60_REFSET EE_SCHEMA=CERT60_PRJSET EERD_MSGS=D:\WIN32APP\INGR\EERWAY\MSG\SET EERD_TBLS=D:\WIN32APP\INGR\EERWAY\MSG\

335


Unload Design

This process unloads a design from a relational database, based on the design filename youspecify. You must have loaded the database using the Load Database process beforeunloading. The Unload Design process deletes all records of raceway connect points (RCP),one-lines, and three-lines that are part of the specified drawing. The process will not modifyanything in the reference database, nor will it delete information from user-defined tables.

Steps

1. Select Unload from the Process menu, and select Confirm (√).

The Unload Design database screen displays.

2. Enter design name.

Select a design file from the Drawing List or key in a design filename (you mayspecify multiple design files).

3. Key in unique filenames for the error and message files (or accept the defaultfilenames).

The default error and message filenames are displayed in appropriate fields. You maychange the defaults by selecting the fields and keying in new names.

The default error and message files will be overwritten every time theprocess is run, unless you specify unique filenames in these fields.

336

14. EE

RW

AY

P

rocesses

Unload Design________________



You may choose between foreground, background, and batch operating modes formost processes (see Process, page 64 ).



Messages


If any errors occur, the message above displays. The .err file, an ASCII file located inthe current working directory, lists all the errors that occurred during processing. Thefile is automatically displayed to the screen for your review.


If no errors occurred, the message above displays. The .msg file, an ASCII file locatedin the current working directory, is created on every run of the process, and listseverything that was loaded into the database. The file is automatically displayed to thescreen for your review.


337


Unload Sheet

This process unloads an EE Raceway drawing from a relational database, based on theinternal sheet name you specify. You must have loaded the database using the LoadDatabase process before unloading.

The Unload Sheet process deletes all records of raceway connect points (RCP), one-lines, andthree-lines that are part of the specified drawing. The process will not modify anything in thereference database.

The drawing you are unloading must have a title block, and the sheet name in the title blockmust match the database entry for that drawing, since the process keys off the sheet name inthe title block. If the sheet name contains blanks, it must be specified in single quotes.

Steps

1. Select Unload Sheet from the Process menu, and select Confirm (√).

The Unload Sheet database screen displays.

2. Key in a sheet name.

3. Key in unique filenames for the error and message files (or accept the defaultfilenames).

The default error and message filenames are displayed in appropriate fields. You maychange the defaults by selecting the fields and keying in new names.

338

14. EE

RW

AY

P

rocesses

Unload Sheet________________

The default error and message files will be overwritten every time theprocess is run, unless you specify unique filenames in these fields.



You may choose between foreground, background, and batch operating modes formost processes (see Process, page 64 ).



Messages


If any errors occur, the message above displays. The .err file, an ASCII file located in thecurrent working directory, lists all the errors that occurred during processing. The file isautomatically displayed to the screen for your review.


If no errors occurred, the message above displays. The .msg file, an ASCII file located in thecurrent working directory, is created on every run of the process, and lists everything that wasloaded into the database. The file is automatically displayed to the screen for your review.


339


Cleanup Database

This process removes information from the database that is not in any drawing currentlyloaded in the database.

For example, information may have been added through the Relational Database ManagementSystem (RDBMS) to test for a special case or to create customized tables. This process alsoremoves information on any EE Raceway drawing which has been deleted, but for somereason was not removed from the database.

The Cleanup Database process deletes all records of raceway connect points (RCP), one-lines, and three-lines that are part of the project database but which are not part of anyraceway design file. This process will not unload records of customized tables in thedatabase. The process uses the filenames in the drawing table of all current drawings. It thenmakes a list of all valid drawings, and deletes anything from the database which is notconnected to one of these drawings. This process will not delete drawings. It will delete fromthe database only that information which is not in any current drawing.

Steps

1. Select Cleanup Database from the Process Menu, and select Confirm (√).

The Cleanup Database screen displays.



340

14. EE

RW

AY

P

rocesses

Cleanup Database________________




You may choose between Foreground, Background, and Batch operating modes formost processes (see Process, page 64 ).


When you are finished completing the input information, select Confirm (√). Theprocess begins. When complete, the process will return one of two messages (describedbelow) to the screen.

Messages


If any errors occur, the message above displays. The .err file, an ASCII file located in thecurrent working directory, lists all the errors that occurred during processing.


If no errors occurred, the message above displays. The .msg file, an ASCII file located in thecurrent working directory, is created. It will display mostly zeroes, and it includes a log ofwhat was unloaded during processing.

You can view either file using the Output option on the Utilities screen.

341


Create Interference Envelope (defaultname)

This process reads a design file and creates from that design a data file containing envelopes(spaces in which valid raceway shapes reside). Upon completion, the process writes the fileto <current_project>.prj/rway/dgn/<filename.env>.

After running the Interference Detection process in EE Raceway, you may send the file toPlant Design software and run it against PDS interference detection. The purpose of the entireprocess is to ensure that each raceway does not occupy the same space as other raceways.

Steps

1. Select Interference Detection from the Process menu and select the Confirm button(√).

The Create Interference Detection Envelope form displays.


— OR —

Select a design file from the Drawing List (use the Select All button to select all filesfrom the list) or key in a design filename.

3. Key in unique filenames for the error and output files (or accept the displayed defaultfilenames).

The default error and output files will be overwritten every time you runthe process unless you specify unique filenames in the fields.

342

14. EE

RW

AY

P

rocesses

Create Interference Envelope (default name)________________


The current operating mode displays in a box at the lower right of the screen.

You may choose between foreground, background, and batch operating modes (seethe section entitled EE Raceway Environment for information about operating modes).


When you finish completing the input information, select the Confirm button (√). Theprocess begins. When complete, the process returns one of the two messages (describedbelow) to the screen.

Messages


If any errors occur, the above message displays. The .err file, an ASCII file located in the<current_project>.prj/rway/tmp directory, lists all errors that occurred during the process.This file displays immediately to the screen for your review. Otherwise, you can view the filethrough the Output option on the Utilities screen.


If no errors occurred, the above message displays. The .msg file, an ASCII file located in the<current_project>.prj/rway/tmp directory, displays all processing information. This filedisplays immediately to the screen for your review. Otherwise, you can view the file throughthe Output option on the Utilities screen.

343


Create Interference Envelope (given name)

This process reads a design file and creates from that design a data file containing envelopes(spaces in which valid raceway shapes reside). Upon completion, the process writes the fileto <current_project>.prj/rway/dgn/<filename.env>.

After running the Interference Detection process in EE Raceway, you may send the file toPlant Design software and run it against PDS interference detection. The purpose of the entireprocess is to ensure that each raceway does not occupy the same space as other raceways.

Steps

1. Select Interference Detection from the Process menu and select the Confirm button(√).

The Create Interference Detection Envelope form displays:


— OR —

Select a design file from the Drawing List (use the Select All button to select all filesfrom the list) or key in a design filename.

3. Key in a name for the envelope file.

4. Key in unique filenames for the error and output files (or accept the displayed defaultfilenames).

The default error and output files will be overwritten every time you runthe process unless you specify unique filenames in the fields.

344

14. EE

RW

AY

P

rocesses

Create Interference Envelope (given name)________________


The current operating mode displays in a box at the lower right of the screen.

You may choose between foreground, background, and batch operating modes (seethe section entitled EE Raceway Environment for information about operating modes).


When you finish completing the input information, select the Confirm button (√). Theprocess begins. When complete, the process returns one of the two messages (describedbelow) to the screen.

Messages


If any errors occur, the above message displays. The .err file, an ASCII file located in the<current_project>.prj/rway/tmp directory, lists all errors that occurred during the process.This file displays immediately to the screen for your review. Otherwise, you can view the filethrough the Output option on the Utilities screen.


If no errors occurred, the above message displays. The .msg file, an ASCII file located in the<current_project>.prj/rway/tmp directory, displays all processing information. This filedisplays immediately to the screen for your review. Otherwise, you can view the file throughthe Output option on the Utilities screen.

345


346

15. Ed

en

Pro

cesses

Eden Processes________________

15. Eden Processes

This chapter provides detailed descriptions of available Eden processes. You will use theseprocesses to compile Eden symbols, manipulate the Eden symbol library, and edit the Edensymbol file.

You will access the Eden processes from the EDEN option found on the EE RacewayDrawing Menu. For information about accessing the processes, see Electrical Engineer (EE)Raceway Environment, page 59 .

The path to the symbol library called in many of the Eden processes is defined by the variableRWAY_EDEN_LIB. The delivered default symbol library path is win32app\eerway\eden. Ifyou want to place your Eden library in a different directory, then edit the .EErc file in yourhome directory, exporting RWAY_EDEN_LIB to specify the appropriate directory.

The path to the extracted symbol source file called in many of the Eden processes is definedby the variable RWAY_EDEN_SRC. The delivered default symbol source file path is<current_project>/rway/tmp. If you want to place your source symbol files in a differentdirectory, then edit the to specify the appropriate directory.

For a general description of Eden symbol generation, see the PDS Eden Interface ReferenceGuide. You should also consult the appendix in this guide entitled Eden Symbol Generation .

Each Eden process is described in a separate section, as follows:

Compile EDEN Symbol — Compiles an Eden symbol file, and gives you the optionof placing the symbol in an Eden symbol library.

Delete EDEN Symbol — Deletes an Eden symbol from the Eden symbol library.

List EDEN Symbol Library — Lists Eden symbols in a selected Eden symbol library.

List EDEN User Functions — Lists Eden user functions in a selected Eden symbollibrary.

Merge EDEN Symbol Libraries — Merges the contents of two Eden symbollibraries into one library.

Compress EDEN Symbol Library — Compresses an Eden symbol library to removeunused space left by deleted symbols.

Extract EDEN Symbol From Library — Extracts a specified symbol from an Edensymbol library.

Extract EDEN User Function From Library — Extracts a specified user functionfrom an Eden symbol library.

347

EE Raceway Modeling Reference Guide - February 2003________________ Edit EDEN Symbol File — Uses a standard ASCII editor to edit a specified symbolsource file.

348

15. Ed

en

Pro

cesses

Compile EDEN Symbol________________

Compile EDEN Symbol

This process compiles an Eden symbol file, and gives you the option of placing the compiledsymbol in an Eden symbol library.

Output file — Displays the file to which process messages are sent. To change thedisplayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change thedisplayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. Forinformation about the path to the symbol library, see the description at the beginning ofthis chapter. To change the displayed default library name, select the field, and key in anew library name.

Enter symbol source file — Displays the name of the symbol source file to compile.For information about the path to the symbol source file, see the description at thebeginning of this chapter. To enter the symbol source file, select the field, and key in afilename.

Enter option — Displays the default compile option (-o). The -o option lists thecompiled Eden symbol file, and then adds the symbol to the specified library. The -loption simply lists the compiled Eden symbol file. To change the displayed option,select the field, and key in a new option.


You must create an Eden symbol file. SeeEden Symbol Generation, page 513 for information about symbol file creation.

349


Steps

1. Select Compile EDEN Symbol from the list, and select Confirm (√).

The Compile EDEN Symbol form displays.



The current operating mode displays in a box at the lower right of the screen. You canchoose between foreground, background, and batch operating modes. Forinformation about operating modes, see EDEN, page 67 .


When you have completed the input information, select Confirm (√), and the Edenprocess begins.

Messages


If any errors occur, the message above displays. The .err file, an ASCII file located in thecurrent working directory, lists all the errors that occurred during processing. The .err filedisplays immediately to the screen for your review.


If no errors occurred, the above message displays. The .msg file, an ASCII file located in thecurrent working directory, contains any output from the process. The file displaysimmediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

350

15. Ed

en

Pro

cesses

Delete EDEN Symbol________________

Delete EDEN Symbol

This process deletes an Eden symbol from the Eden symbol library.



Enter library name — Displays the default Eden symbol library name. To change thedisplayed library name, select the field, and key in a new library name.

For information about the path to the symbol library, see the description at thebeginning of this chapter.

Enter symbol name — Displays the name of the symbol you intend to delete from thelibrary. To enter the symbol name, select the field, and key in the name.

For information about the path to the symbol source file, see the description at thebeginning of this chapter.

351


Steps

1. Select Delete EDEN Symbol from the list, and select Confirm (√).

The Delete EDEN Symbol form displays.






Messages


If any errors occur, the message above displays. The .err file, an ASCII file located inthe current working directory, lists all the errors that occurred during processing. The.err file displays immediately to the screen for your review.


If no errors occurred, the above message displays. The .msg file, an ASCII file locatedin the current working directory, contains any output from the process. The filedisplays immediately to the screen for your review.


352

15. Ed

en

Pro

cesses

List EDEN Symbol Library________________

List EDEN Symbol Library

This process lists the Eden symbols in the selected Eden library.





353


Steps

1. Select List EDEN Symbol Library from the list, and select Confirm (√).

The List EDEN Symbol Library form displays.

2. Set up the form parameters to meet you specifications.





Messages






354

15. Ed

en

Pro

cesses

List EDEN User Functions________________

List EDEN User Functions

This process lists the Eden user functions in the selected Eden library.





Steps

1. Select List EDEN Symbol Library from the list, and select Confirm (√).

The List EDEN User Functions form displays.

2. Set up the form parameters to meet you specifications.



355



When you have completed the input information, select Confirm (√), and the list willdisplay.

Messages






356

15. Ed

en

Pro

cesses

Merge EDEN Symbol Libraries________________

Merge EDEN Symbol Libraries

This process merges two Eden symbol libraries into one.



Merge into library name — Displays the name of the symbol library into which youwill merge the contents of a second library. To enter a library name, select the field,and key in a name.


Merge from library name — Displays the name of the symbol library whose contentsyou will merge with first library. To enter a library name, select the field, and key in aname.


Steps

1. Select Merge EDEN Symbol Libraries from the list, and select Confirm (√).

The Merge EDEN Symbol Libraries form displays.


357






Messages






358

15. Ed

en

Pro

cesses

Compress EDEN Symbol Library________________

Compress EDEN Symbol Library

This process compresses the selected Eden symbol library. Compressing the library removesthe unused space left by deleted symbols.



Enter library name — Displays the default Eden symbol library name. To change thedisplayed library name, select the field, and key in the name of the library you intend tocompress.


Steps

1. Select Compress EDEN Symbol Library from the list, and select Confirm (√).

The Compress EDEN Symbol Library form displays.




359




Messages






360

15. Ed

en

Pro

cesses

Extract EDEN Symbol From Library________________

Extract EDEN Symbol From Library

This process extracts a symbol from the selected library. The extracted symbol is the form ofan ASCII file that you can edit using a standard editor (vi or emacs, for example). Thesymbol is not deleted from the library when you extract it.

The path to the extracted symbol source file is defined by the variable RWAY_EDEN_SRC.The delivered default source symbol path is win32app\eerway\eden. If you want to storeyour source symbol files in another directory, then edit the .EErc file in win32app\eenuc,exporting RWAY_EDEN_SRC to define the appropriate directory.





Enter symbol name — Displays the name of the symbol you intend to extract from thelibrary. To enter the symbol name, select the field, and key in the name.

361


Steps

1. Select Extract EDEN Symbol From Library from the list, and select Confirm (√).

The Extract EDEN Symbol From Library form displays.






Messages






362

15. Ed

en

Pro

cesses

Extract EDEN User Function From Library________________

Extract EDEN User Function From Library

This process extracts a user function from the selected library. The extracted user function isthe form of an ASCII file that you can edit using a standard editor (vi or emacs, for example).The user function is not deleted from the library when you extract it.

The path to the extracted user function source file is defined by the variableRWAY_EDEN_SRC. The delivered default source user function path iswin32app\eerway\eden. If you want to store your source user function files in anotherdirectory, then edit the .EErc file in win32app\eenuc, exporting RWAY_EDEN_SRC todefine the appropriate directory.





Enter symbol name — Displays the name of the user function you intend to extractfrom the library. To enter the user function name, select the field, and key in the name.

363


Steps

1. Select Extract EDEN User Function From Library from the list, and select Confirm(√).

The Extract EDEN User Function From Library form displays.






Messages



364

15. Ed

en

Pro

cesses

Extract EDEN User Function From Library________________ Process successfully completed



365


Edit EDEN Symbol File

This process allows you to edit a symbol source file using a standard ASCII editor. It is onlyavailable on a graphics terminal.



Enter editor — Displays the name of the default ASCII editor (vi) that you will use toedit the Eden symbol file. To change the displayed editor, select the field, and key in anew standard ASCII editor name.

Enter symbol file name — Displays the name of the symbol file you intend to edit. Toenter a symbol filename, select the field, and key in a symbol file name.

For information about the path to the symbol source file, see the description at thebeginning of this chapter.

366

15. Ed

en

Pro

cesses

Steps________________

Steps

1. Select Edit EDEN Symbol File from the list, and select Confirm (√).

The Edit EDEN Symbol File form displays:






Messages






367


368

16. Integ

rated

Co

mm

and

s

Integrated Commands________________

16. Integrated Commands

The Integrated Commands are common to EE Raceway and several other PDS modules,providing greater interoperability among the various disciplines. These commands allow youto review an element’s attributes, review the PDS clashes in a model, create a windowcontaining a specific element, and display information about the reference models attached tothe current model.

The Integrated Commands are only available when running EE Racewayinside PDS, not when running standalone EE Raceway.

The Integrated Commands palette is activated by selecting Integrated Commands from theEE Raceway File Menu Bar, then selecting Palette from the resulting pull-down menu.

369


Using the Integrated Commands




Review PDS Attributes – You must have an existing component in the active modelor in an attached PDS reference file.

Reference PDS Model – There are no prerequisite conditions for using this command.

Window to Named PDS Item – You must have existing items in the active model or inan attached PDS reference file.

Review PDS Clash – You must first have run IFC Clash Detection, and must have anexisting clash in the design area.

Group Workflow




370

16. Integ

rated

Co

mm

and

s

Review PDS Attributes________________

16.1 Review PDS Attributes

The Review PDS Attributes command displays the database attributes of a selectedcomponent. Items being reviewed can be in the active model or in an attached PDS referencefile.

To view pipe centerlines (to review the line segments), you need to displayconstruction type elements. Use the MicroStation Settings > View Attributes> Turn on construction command.

Parameters

Attribute Name – Lists the item’s attributes.

Value – Displays the item’s attribute value that is defined in the database.

Close – Exits the Review PDS Attributes dialog box.

371


16.2 Reference PDS Model

The Reference PDS Model command attaches and detaches models from the PDS project tothe model as reference files. The model to attach can be from any discipline and design areain the project.

Parameters

Disciplines – Lists all disciplines. Select the discipline which contains the model youwant to attach; then, click Attach.

Areas – Lists all design areas defined in the active project. Select the design areawhich contains the model you want to attach; then, click Attach.

Area/Model – Specifies whether to attach all models in a design area or an individualmodel.

— Attach by Area – Attaches all model in the selected design area.

— Attach by Model – Displays all models in the design area so you can select whichmodel you want to attach.

Propagated/Sparse – Specify whether you want to attach the sparse model or thecorresponding propagated model. This option only displays if you are attaching astructural model.

Attach – Attaches a reference model. You must select a Discipline and a Design Areabefore you can select a reference model to attach.

Detach – Detaches the selected reference model. You must click Show Attachmentsand select the reference model you want to detach before clicking Detach.

372

16. Integ

rated

Co

mm

and

s

Reference PDS Model________________ Show Attachments – Displays all reference models attached to the active model.

Exit – Exits the Reference Model command.

373


16.3 Window to Named PDS Item

The Window to Named PDS Item command zooms in on an item whose attribute youidentify. You can search for items in the active model or in attached PDS reference files.

Options

Active Model / Reference Files – Specifies whether to look for the item in the activemodel or in the attached reference files.

Discipline – Specifies the discipline of the item you are looking for. You can select:Piping, Equipment, PE HVAC, or Raceway. Depending on which discipline you select,the item attributes you can search for changes.

— Piping Attributes – Line Number Label, Line ID, Inspection Iso ID, PipingComponent Number, Pipe Tag, Instrument Component Number, or Pipe SupportNumber

— Equipment Attributes – Equipment Number or Equipment and Nozzle Number

— PE HVAC Attributes – System ID or Item ID

— Raceway Attributes – RCP Tag, One Line Tag, Drop Point Tag, or Equipment ID

Item Name – Specify the attribute value to search for.

Restore View of Model – Restores the view setting.

374

16. Integ

rated

Co

mm

and

s

Review PDS Clash________________

16.4 Review PDS Clash

The Review PDS Clash command edits and reviews existing clashes and approves existingclashes.

Parameters

Project Name – Displays the active project name.

Design Area – Displays the active design area name.

Clash Type – Displays the clash type.

Date – Displays the date and time the clashes were detected.

Unapprove Clash – Changes the status of the clash from approved to unapproved.

Approve Real Clash – Approves the clash as a real clash in the Project ControlDatabase.

Approve False Clash – Approves the clash as a false clash in the Project ControlDatabase.

Review Unapproved Clash / Review Approved Clash – Specifies if you want toreview approved or unapproved clashes.

Clash Marker – Displays the number of the current clash. Select a marker numberwith the left and right arrows; or, select the field and key in a marker number.

375

EE Raceway Modeling Reference Guide - February 2003________________ Item A – Displays the model name and the corresponding design area that has the oneitem of the clash. The descriptions of the clashing component display below the modelname and design area.

Item B – Displays the model name and the corresponding design area that has the oneitem of the clash. The descriptions of the clashing component display below the modelname and design area.

Comments – Displays existing comments about the active clash. You can also selectthe field and type in any additional information.

Highlight Clash – Highlights the clash in the selected view.

Select View – Zooms in and updates the selected view. Click Select View then selectthe view you want to update.

376

A: E

rror

Messag

es

Appendix A: Error Messages________________

Appendix A Error Messages

This appendix has an alphabetical listing of error messages you may receive when you are running EE RacewayModeling. The likely reason for the error and the recovery are listed with the error message wherever this ispossible.

Active Raceway type not found

Reason: There is no active one-line type defined in the design file.

Recovery: Use the Set Active One-Line Type to set an active one-line type.

Ambiguous Command

Reason: The command name you keyed in is not unique.

Recovery: Key in an acceptable command name.

Asid <numeric value>, fitting connected to invalid oneline!

Reason: The fitting is connected to a one-line that failed to load.

Recovery: Make corrections so that the one-line loads without errors.

Asid <numeric value>, fitting connected to invalid system!

Reason: The fitting is attached to a one-line or RCP belonging to a system that failed to load.

Recovery: Make corrections so that the system loads without errors.

Asid <numeric value>, <string> connected to invalidsystem!

Reason: The element belongs to a system that failed to load.

Recovery: Make corrections so that the system loads without errors.

377


Asid <numeric value>, <string> has invalid codelist value!

Reason: Element annotation does not match with entries in a codelist table.

Recovery: Change element annotation.

Asid <numeric value>, <string> not on valid racewayconnect point!

Reason: The element is attached to an RCP that failed to load.

Recovery: Make corrections to the RCP so that it loads without errors.

Asid <numeric value>, part could not be found for fitting!

Reason: A part matching the description of the fitting could not be found in the part table.

Recovery: Review the fitting in the design. If the fitting is a specification-driven part, then the givenspecification does not have that part defined in its part table.

Asid <numeric value>, raceway connect point connectedto invalid system!

Reason: The RCP belongs to a system that failed to load.

Recovery: Make corrections so that the system will load without errors.

Asid <numeric value>, raceway connect point has invalidcodelist value!

Reason: Element annotation does not match with entries in a codelist table.

Recovery: Change element annotation.

Asid <numeric value>, straight connected to invalidoneline!

Reason: The straight is attached to a one-line that failed to load.

Recovery: Make corrections so that the one-line will load without errors.

378

A: E

rror

Messag

es


Asid <numeric value>, straight connected to invalidsystem!

Reason: The straight is attached to a one-line belonging to a system that failed to load.

Recovery: Make corrections so that the system will load without errors.

Asid:<numeric value> <string>

Reason: Display the element’s asid number along with a message, when highlighting by sector and word.

Recovery: None.

Bad user data on raceway element

Reason: Element has been corrupted.

Recovery: Contact Intergraph support.

Bad user data in design file: cannot continue!



Cannot access filelist <string>!

Reason: The file containing the filelist is not available.

Recovery: Give the correct filename or access to the file.

Cannot attach to database

Reason: The database does not exist or you do not have privilege.

Recovery: Be sure the database exists and that you have privilege.

379


Cannot convert to RAD50: <<string>>

Reason: A key-in contains characters that cannot be converted to RAD50.

Recovery: Key-in in only characters, digits, "$", or ".".

Cannot Place Cross Section. Invalid olt on oneline.

Reason: There is a corrupt one-line segment or the one-line type user element has been removed.

Recovery: Verify that a valid one-line type is active, and replace the one-line. If the problem persists, callIntergraph support.

Cannot Override <string>

Reason: The field or key cannot be overridden.

Recovery: The program will restore the original text.

Cannot Place Cross Section. Invalid sys on oneline.

Reason: There is a corrupt one-line segment or the system user element has been removed.

Recovery: Verify that a valid system is active, and replace the one-line. If the problem persists, call Intergraphsupport.

Cell <string> not found in library

Reason: The cell name you keyed in does not exist in the cell library.

Recovery: Key in another cell name.

Cell exists in library: <string>

Reason: During cell creation, the name input already exists in the attached cell library.

Recovery: Either key in another name or delete the cell from the cell library so it may be recreated.

380

A: E

rror

Messag

es


Color not in range 0 to 127

Reason: The input is not within the valid range for a color.

Recovery: Enter a new value within the range 0 to 127.

Column does not exist

Reason: The given column number is greater than the number of columns in the table.

Recovery: Key in another column number for the given table.

Corrupt or no informational link on raceway element



Could Not Read PDS Data Element

Reason: The PDS user element is not found in the design file. Either the element was removed externally orthis design file is not a Raceway or PDS design file.

Recovery: None.

Could not find alias file

Reason: The alias file containing the command names and acceptable key- ins is not in the proper location.

Recovery: Have the system manager place the file where it belongs.

Could not find a cross section on one line

Reason: Cross section was removed using the Delete command.

Recovery: Use the Delete command to remove the associated one-lines and then replace them.

381


Could not find EE_CURPRJ. Please export this variable.

Reason: Environment variable EE_CURPRJ needs to be exported in order to run this process from thecommand line.

Recovery: Export EE_CURPRJ = <current or project directory>

Could not get defaults from reference db

Reason: Entries for element not found in reference database.

Recovery: Add entries to appropriate tables.

Could not get one line type from user data.

Reason: Corrupt user data on one-line or RCP.

Recovery: Replace the corrupted element or call Intergraph support.

Could not get one line type part table from user data.

Reason: Corrupt user data on one-line or RCP.

Recovery: Replace the corrupted element or call Intergraph support.

Could not open <string>

Reason: No permission to open file or the file does not exist.

Recovery: Check the file permissions and the existence of the file.

Could not open design file



382

A: E

rror

Messag

es


Could not open file <string>



Could not open logfile <string>

Reason: A number of factors may result in this error.

Recovery: There are various recoveries, based on cause of error.

Could not read one-line user element

Reason: Rmon could not read the one-line user element.

Recovery: Check to see that the design file has a type 63 element and at least 7 blocks in it.

Could not read the PDS 1 user element

Reason: The Raceway design file was not created using a PDS or EE Raceway seed file.

Recovery: None.

Could not read the PDS 2 user element

Reason: The Raceway design file was not created using a PDS or EE Raceway seed file.

Recovery: None.

Could not read system user element

Reason: Rmon could not read the system user element.


383


Could not read the Raceway user element

Reason: Rmon could not read the Raceway user element.


Could not retrieve codelist values

Reason: The value placed in the codelist column does not appear in the codelist table.

Recovery: Change the value to one that appears in the codelist table.

Could not retrieve specifications for key <string>

Reason: You key in a value for the key to the secondary table.

Recovery: Key in a new key value.

Could not write to TCB, status = <numeric value>

Reason: The process tried to write a TCB variable to the design file.

Recovery: Make sure you have write access to the design file.

Cutback Error at oneline <numeric value>

Reason: Problems occurred in calculating the cutback from the fitting at the end of a one-line.

Defaults do not exist for <string> key = <string>

Reason: An entry in the database does not exist for the specified key.

Recovery: Make sure the key is correct. The database is case-dependent. If the key does not exist, insert it intothe reference database.

Design file <string> does not exist!

Reason: The referenced design file was cannot be found.

Recovery: Enter correct filename.

384

A: E

rror

Messag

es


Design file name <string> too long

Reason: The filename you specified exceeds 128 characters.

Recovery: Key in a filename with fewer than 128 characters.

Design filename required!

Reason: No filename entered.

Recovery: Enter design filename.

Directory <string> not found

Reason: A referenced directory cannot be found.

Recovery: Enter correct directory name.

Drop point cell ‘‘<string>’’ not found in library

Reason: The drop point cell does not exist in the library.

Recovery: Create a drop point cell and/or enter the correct drop point cell name in the EE Raceway defaultsform.

Elbow Error with cutback <numeric value> at index<numeric value>.

Reason: There was inadequate room to place fitting, so it will go past the previous fitting or end of linestring.

Recovery: Modify the radius or extension of the fitting, change the spec, or replace the one-line so that it hasenough room to create the fitting.

Elbow Error: acute angle at oneline index <numericvalue>.

Reason: Acute bends are not supported in this release.

Recovery: None.

385


Elbow Error: contradictory heights at index <numericvalue>.

Reason: Height of the cross sections must be equal.

Recovery: Modify cross section dimensions.

Elbow Error: contradictory widths at index <numericvalue>.

Reason: Widths of the cross sections must be equal.


Elbow Error: contradictory vertical directions at index<numeric value>.

Reason: The cross sections were not placed with the same vertical orientation.

Recovery: Try to rotate cross sections or place one-line again.

Elbow Error: contradictory horizontal directions at index<numeric value>.

Reason: The cross sections were not placed with the same horizontal orientation.

Recovery: Try to rotate cross sections or place one-line again.

Elbow Error: skewed angle at oneline index <numericvalue>.

Reason: Cross section cannot be propagated around bend without being skewed.

Recovery: Rotate the cross section or place one-line again.

386

A: E

rror

Messag

es


Element has no parent

Reason: The element with the given asid has no parent element.

Recovery: Enter a new asid number.

Element not found

Reason: There does not exist an element with the given sector/word or asid.

Recovery: Enter a new value.

Error building user data

Reason: Could not build user data.

Recovery: Exit the command and retry.

Error closing propagation log file.

Reason: File pro.err did not close properly. Propagation status may not be recorded.

Recovery: Make sure the pro.err file and the rway/tmp directory have read/write privileges.

Error could not write to design file!

Reason: No write access to design file.

Recovery: Change access to design file.

Error could not write user element!

Reason: No write access to design file.

Recovery: Change access to design file.

387


Error getting annotation information for element!

Reason: Element in design file is corrupt.

Recovery: Delete and replace element in design file.

Error getting column names from reference for table<string>!

Reason: No privilege.

Recovery: Add privilege to database.

Error getting information from <string> table!

Reason: Table not found in schema.

Recovery: Add table to schema or change schema.

Error getting mslinks for tables!

Reason: Tables missing in project database.

Recovery: Add appropriate tables to project database.

Error getting sheet name from design file!

Reason: Title block not found or not annotated.

Recovery: Place or annotate title block.

Error getting values from reference for table <string>!

Reason: Values for table not found in reference database.

Recovery: Add entries to reference database.

388

A: E

rror

Messag

es


Error in graphic bang placement.

Reason: Internal error.

Recovery: Call Intergraph support.

Error initializing eden library ‘‘<string>’’.

Reason: Could not open Eden symbol library.

Recovery: Make sure that RWAY_EDEN_LIB and EDEN_LIB are set up properly in your .EErc file.

Error initializing unique table!

Reason: ee_unique table missing from the reference database.

Recovery: Add the ee_unique table to the reference database.

Error initializing validity table!

Reason: Mscodelist table not found.

Recovery: Add mscodelist table to reference table.

Error invalid column name in unique table!

Reason: Incorrect entry in ee_unique table.

Recovery: Correct entry.

Error loading drawing!

Reason: No privilege for operation.


389


Error loading drop point!

Reason: No privilege for this operation.

Recovery: Add privilege to the database.

Error loading fittings!



Error loading one-lines!



Error loading raceway connect points!



Error loading straights!



Error loading systems!



390

A: E

rror

Messag

es


Error loading to equipment!

Reason: No privilege for this operation.

Recovery: Add privilege to the database.

Error marking elements for deletion!

Reason: ee_to_drw column missing a table.

Recovery: Add columns and try again.

Error merging annotation from design file!

Reason: Element annotation columns do not match columns in project database.

Recovery: Change annotation of element.

Error No Placepoints or No Elements.

Reason: The Eden symbol definition must contain at least one placepoint, one datum point, and one element.

Recovery: Modify the Eden symbol.

Error opening database!

Reason: Schema not found.

Recovery: Add schema or enter correct schema name.

Error opening design file <string>, ustn returned status of<numeric value>!

Reason: Microstation could not open specified design file.

Recovery: Refer to Microstation documentation for recovery.

391


Error opening project database!


Recovery: Add schema to database or change schema name.

Error opening reference database!


Recovery: Add schema to database or change EES_REFDB.

Error parsing cross section

Reason: An error occurred while parsing a cross section.

Recovery: Delete the one-line containing the RCP and place it again.

Error parsing one-line

Reason: An error occurred while parsing a one-line.

Recovery: Delete the one-line and place it again.

Error parsing RCP

Reason: An error occurred while parsing a raceway connect point (RCP).

Recovery: Delete the one-line containing the RCP and place it again.

Error querying ref db for mscatalog

Reason: The mscatalog table does not exist or there is no connect permission.

Recovery: Run the Create Database process with the rwayref.sql file.

392

A: E

rror

Messag

es


Error querying ref db for mscodelist

Reason: The mscodelist table does not exist or there is no connect permission.

Recovery: Run the Create Database process with the rwayref.sql file.

Error reading TCB of design file!

Reason: TCB corrupted.


Error reading database column names!

Reason: No access to column names.

Recovery: Add privileges to database.

Error reading database table names!

Reason: Table name in mscatalog table invalid.

Recovery: Correct entry in mscatalog.

Error reading file list <string>!

Reason: No access to read file list.

Recovery: Change file list name or protection on file list.

Error reading user element of design file!

Reason: User element missing or corrupt in design file.


393


Error saving symbology - Design file may be corrupted

Reason: Could not save the symbology to the design file.


Error sheet name cannot be duplicated!

Reason: A drawing with the given sheet name already exists in the database.

Recovery: Edit the sheet name. The sheet name must be unique within the database.

Error spawning server

Reason: Could not open reference schema.

Recovery: Return to the environment and make sure you are using the correct reference schema.

Error unloading Sheet!

Reason: Sheet not found.

Recovery: Enter correct sheet name.

Error unloading connect points!

Reason: No privilege to delete from database.

Recovery: Add privilege.

Error unloading drawing!

Reason: No privilege to delete from database.


394

A: E

rror

Messag

es


Error starting or stopping graphic bang.



Error updating row in <string> table!

Reason: No privilege to write to database.


Errors existed during unload

Reason: Errors in other procedures.

Recovery: Fix other errors.

Errors occurred during interference detection process!

Reason: Fatal error occurred during process.

Recovery: Read previous error messages to determine cause.

Fatal error! Vector length was negative.

Reason: Interference detection found an item of size = 0 (length).

Recovery: None. The process creates a zero-length envelope.

Field may not contain an empty value

Reason: Field cannot be left blank.

Recovery: Key in a value.

395


File <string> exists, overwrite or append?

Reason: The specified file already exists.

Recovery: Write over the existing file or attach new file to existing file.

Fitting Cutback Error at RCP asid <numeric value>.

Reason: There was inadequate room to place fitting, so it will go past the previous fitting or linestring.

Recovery: Modify the radius, extension or transition of the fitting, change the spec, or replace the one-line sothat it has enough room to create the fitting.

Fitting Error: contradicting at RCP asid <numeric value>.

Reason: Heights of cross sections are inconsistent.


Fitting Error: contradicting widths at RCP asid <numericvalue>.

Reason: Widths of cross sections are inconsistent and no reducing fitting is allowed in this case.


Fitting Error: Illegal angle at RCP asid <numeric value>.

Reason: An illegal angle exists. For example, at a cross, all four one-lines must be at right angles to each other.

Recovery: Replace the one-line that forms the illegal angle.

Fitting Orientation Error at RCP asid <numeric value>.

Reason: The cross sections cannot be propagated at the fitting without being skewed.

Recovery: Try rotating cross sections or replacing the one-lines.

396

A: E

rror

Messag

es


Font not in range 0 to 255

Reason: The input was not within valid range for a font.


Form could not be created

Reason: A form could not be created by the software. Possible memory allocation problem.


Form could not be displayed

Reason: Once created, a form could not be displayed by the software.

Recovery: Fatal error. Try to exit and re-enter the software.

Form creation error

Reason: The software could not create a form.

Recovery: Exit and re-enter the product.

Form error could not find form file <string>

Reason: The referenced form file could not be found in the path defined by EE_FORM_PATH.

Recovery: Make sure the referenced form file exists in the path defined by EE_FORM_PATH which is definedin the product.

Form error reading form file <string>

Reason: I-Forms could not read the referenced form file.

Recovery: Make sure the referenced form file exists in the path defined by EE_FORM_PATH which is definedin the product.

397


Forms environment not initialized

Reason: Fatal error.

Recovery: Exit and reenter the product.

Function locked out: no permission

Reason: This function has been disallowed by the system manager.

Recovery: Remove the function name from the EERWAY_LOCKED_OUT variable in the ./config/assign file.

Graphic group not found

Reason: No elements found in the design file with the given graphic group.

Integer not in range -2147483648 to 2147483647: <string>

Reason: The value entered exceeds the range or the input is corrupted.

Recovery: Enter a value within the range of -2147483648 to 2147483647.

Integer not in range -32768 to 32767: <string>

Reason: The value entered exceeds the range or the input is corrupted.

Recovery: Enter a value within the range of -32768 to 32767.

Interference Detection initialization error!

Reason: Could not open design filelist or read the design file.

Recovery: Fix problem as specified by earlier error messages.

Invalid annotation type

Reason: Annotation of the wrong type was found inside the fence block annotation when trying to close a cell.

Recovery: Delete the highlighted element or move it outside the fence area.

398

A: E

rror

Messag

es


Invalid asid id

Reason: An element cannot be found in the design file with the given asid id.

Recovery: Key in another asid id.

Invalid cell: <string>

Reason: The given cell is not the type the command expected. For example, Place Title Block must be givena title block cell.

Recovery: Key in a cell of the type the command is expecting.

Invalid Connection

Reason: The identified RCP has a higher priority level than the identified one-line.

Recovery: Make sure the priority level of the identified RCP is less than or equal to the priority level of theone-line.

Invalid drop point cell: ‘‘<string>’’

Reason: The cell is not a valid drop point.

Recovery: Create a valid drop point cell through cell creation.

Invalid Eden Processor Input. <numeric value>.

Reason: Could not create Eden symbol with the given criteria.

Recovery: Change the criteria on the Manual Placement form or modify the symbol.

Invalid Eden Symbolname ’<string>’.

Reason: The symbolname is blank.

Recovery: Modify the reference database to contain a symbolname for each part.

399


Invalid graphic group number

Reason: The graphic group number is outside the valid range.

Recovery: Select another graphic group number.

Invalid height/width for cross section type <string>.

Reason: The height or width is less than or equal to zero.

Recovery: Modify reference database height/width for the active specification.

Invalid input

Reason: You entered an incorrect value.

Recovery: Key in another value.

Invalid integer: <string>

Reason: The value entered is not a valid integer.

Recovery: Enter an integer value.

Invalid key in - quantity can not be set to 0

Reason: The value you entered is not a valid input. For example, quantity must be an integer greater than 0.

Recovery: Key in a new value greater than 0. If it is a cable entry, click on the REMOVE button to delete.

Invalid mix of EDF and text: <string>

Reason: Field consists of text and Enter Data Fields for the same string.

Recovery: Make the field either all text or all EDF.

400

A: E

rror

Messag

es


Invalid Part Found at RCP asid <numeric value>.

Reason: The fitting at the RCP cannot be verified with the database.

Recovery: Turn Part Verification off OR add the fitting to the database.

Invalid Part Found at oneline asid <numeric value>, vertex<numeric value>.

Reason: The elbow or straight at the one-line cannot be verified with the database.

Recovery: Turn Part Verification off OR add the elbow or straight to the database.

Invalid RCP – No one-lines attached

Reason: There are no one-lines associated with the raceway connect point (RCP).

Recovery: Delete the RCP and place the one-line again.

Invalid RCP - Only two one-lines can be attached

Reason: The RCP has more or fewer than two one-lines attached.

Recovery: You can only remove an RCP with exactly two one-lines attached.

Invalid real number: <string>

Reason: The value entered must contain a decimal with a preceding number.

Recovery: Re-enter a valid real number.

Invalid response

Reason: You entered an invalid response to a system prompt.

Recovery: Enter a valid response.

401


Invalid/No ris link on element

Reason: An element with the given entity/mslink could not be found in the design file.

Recovery: Enter another entity/mslink.

Invalid sector/word values

Reason: An element could not be found at the given sector/word location in the design file.

Recovery: Enter another sector/word value.

Invalid title block

Reason: Not a valid title block.

Recovery: Key in another title block cell name.

Invalid equipment pointer cell: ‘‘<string>’’

Reason: The cell is not a valid equipment pointer.

Recovery: Create a valid equipment pointer through cell creation.

Invalid ulink on element

Reason: Not a valid ulink for the element.

Recovery: Delete the element and place it again or recreate the element.

Level not in range 1 to 63

Reason: The input was not within the valid range for a level.

Recovery: Enter a new value within the range of 1 to 63.

402

A: E

rror

Messag

es


Load initialization error!

Reason: Some other initialization error procedure failed.

Recovery: Fix other problems.

Max run angle = <numeric value>, current = <numericvalue>

Reason: The sum of all the angles in the current one-line exceeds the maximum as defined in the one-line type.

Recovery: Terminate before exceeding the max, and place the element or RCP.

Mismatched annotation

Reason: Annotation was found that has no parent inside of the fence area.

Recovery: Delete the highlighted area.

More than one title block found!

Reason: More than one title block exists in the design file.

Recovery: Delete all but one title block.

Multiple annotation for column <numeric value>

Reason: Only one annotation element per column is allowed.

Recovery: Delete all but one of the highlighted elements.

Must be LT, LC, LB, CT, CC, CB, RT, RC, or RB.

Reason: Invalid text justification entered.

Recovery: Enter LT, LC, ...or RB in the justification field.

403


Must enter cell name to close

Reason: You tried to close a cell without keying in a name.

Recovery: Key in a cell name to close or exit the command.

No active group defined

Reason: The selected group operation requires that you define an active group.

Recovery: Specify a group to be active.

No active one line type defined

Reason: You did not define an active one-line type in the design file.

Recovery: Define an active one-line type using the Set Active One-Line Type command.

No active system defined

Reason: You did not define an active system in the design file.

Recovery: Define an active system using the Set Active System command.

No cell library attached

Reason: A cell library is not attached to the design file.

Recovery: Attach a cell library (rc=celllibraryname.cel).

No columns available for annotation

Reason: The database does not contain the EE Raceway database tables.

Recovery: Add the EE Raceway tables to the database.

404

A: E

rror

Messag

es


No Duplicate Group Name Allowed

Reason: The new group name matches the name of an existing group.

Recovery: Key in another name.

No elements in fence

Reason: The defined fence does not contain a valid element within its borders.

Recovery: Redefine the fence to include a valid element.

No memory available for form

Reason: The forms software could not allocate enough memory for creation of the form.

Recovery: Exit completely and re-enter the product.

No memory available!

Recovery: Exit the process and re-enter and/or reboot the workstation.

No or Illegal Cross section type <string>.

Reason: The cross section must be of type A, B, or C in the active specification.

Recovery: Modify the reference database to include A, B, C for the cross section type.

No overrides allowed without override button on

Reason: The Override button is not depressed.

Recovery: Press the Override button and key in the value again.

No raceway one-line type defined

Reason: You must have at least one one-line type defined from the reference database in the design file.

Recovery: Define a one-line type from the reference database using the Define One-Line Type command.

405


No read/write access to file <string>

Reason: No permission to read and write to the specified file.

Recovery: Add read/write permissions to file.

No systems defined in this design file

Reason: You must have at least one system defined from the reference database in the design file.

Recovery: Define a system from the reference database using the Define System command.

No valid dimensions exist for this oneline type

Reason: The database has no parts for this specification of the one-line type.

Recovery: Populate the database with parts.

No valid elements in group

Reason: The active group does not contain any valid elements for the specified group manipulation command.

No valid parts exist for this oneline type

Reason: The database has no parts for this specification of the one-line type.

Recovery: Populate the database with parts.

No valid spec exist for this oneline type

Reason: No specifications exist in the database for this one-line type.

Recovery: Populate the database.

No valid spec keys exist for this oneline type

Reason: Problem retrieving the active specification.

Recovery: Make sure the active specification is in the database through Define Raceway Parameters.

406

A: E

rror

Messag

es


No valid special part tables exist

Reason: There are no special parts tables in the database.


No valid special parts exist for this table

Reason: There are no special parts defined in the active table.


No values found in the codelist

Reason: The codelist table contains no rows.

Recovery: Insert the rows into the codelist table that corresponds to the column.

No write access to cell library

Reason: The attached cell library is read only.

Recovery: Attach a cell library that has read/write permissions or assign write permission to the current celllibrary.

Not an EE RACEWAY design file

Reason: The design file was not seeded with the EE Raceway seed file.

Recovery: The design file must be created using the EE Raceway seed file.

One-line is a member of a different system

Recovery: Change the active systems to that of the identified one-line.

One-lines do not contain same systems

Recovery: Identify one-lines that contain the same systems.

407


Option not allowed

Reason: The selected option is not allowed.

Recovery: Select another option.

Placepoints/Datumpoints are not defined properly.

Reason: Eden symbol must have at least one datumpoint and at least one placepoint defined.

Recovery: Modify the Eden symbol.

Placing Straight Section with No Length.

Reason: The straight must be place with a length greater than 0.

Recovery: Give length in the Length field on the Manual Placement form.

Problem retrieving symbology from one line type element.

Reason: One-line type user data corrupt on one-line OR the system symbology user elements have beencorrupted.

Problem with shared memory!



Project schema not defined

Reason: EE_SCHEMA has not been exported.

Recovery: Export the variable EE_SCHEMA.

Projecting oneline with asid <numeric value>.

Reason: This identifies which one-line is being projected.

Recovery: None.

408

A: E

rror

Messag

es


Raceway element not found

Reason: Unable to locate a valid raceway element (one-line, three-line, title block, RCP).

Recovery: Identify one of these elements.

Raceway title block not found

Reason: Unable to locate a title block in the design file.

Recovery: Place a title block in the design file.

Reference schema name required!

Reason: EES_REFDB has not been exported.

Recovery: Export EES_REFDB.

Reference schema table missing required columns

Reason: A required column in the table for the element you are annotating is NOT in the table or in themscolumns table. The required columns’ names are prefixed with "ee_".

Recovery: Create the appropriate table.

Schema name required

Reason: No schema name entered.

Recovery: Enter schema name.

Select failed, no rows found fitting the given criteria

Reason: Could not find rows in the database fitting the specified find criteria.

Recovery: Specify new find criteria.

409


Sheet Name is required

Reason: No sheet name entered.

Recovery: Enter sheet name.

Sheet not found in database!

Reason: Sheet name not in drawing table.

Recovery: Change sheet name.

Style not in range 0 to 7

Reason: The input was not within the valid range for style.


Symbol file not found: <string>

Reason: The symbol file EE_SYM_FILE could not be found in the symbol path EE_SYM_PATH.

Recovery: Make sure EE_SYM_FILE and EE_SYM_PATH are defined in the directory.

Table number <numeric value> not in mscatalog

Reason: The specified table number / table name entry does not exist in the reference database.

Recovery: Add the missing entry into the mscatalog table by loading the mscat.unl file or inserting a rowthrough SQL.

Text element not found

Reason: A text element could not be located.

Recovery: Identify a valid text element.

410

A: E

rror

Messag

es


The value must be greater than zero

Reason: The width must be greater than zero.

Recovery: Enter a new value greater than zero.

Title block placed - Some fields review only

Reason: Some fields are locked once you place the title block and, therefore, cannot be edited.

Recovery: None.

Too many one-lines at RCP <numeric value>

Reason: Cannot propagate with this many one lines.

Recovery: Place a manual fitting.

Truncated <numeric value> characters

Reason: The number of characters allowed in the field has been exceeded by <numeric value> characters.

Recovery: None

Unload initialization error!

Reason: No privilege to read table or column names.

Recovery: Add privileges to the database.

Warning Cannot calculate envelope for non-planarcomplex shape with Asid = <numeric value>

Reason: Found a cell containing a complex shape which does not meet any lines or surfaces at a 90 degreeangle. The system cannot calculate the height and direction of projection of this complex shape.

Recovery: Highlight the cell with that Asid and look to see if an envelope needs to be built for the complexshape in that cell. Rebuild cell so that the complex shape meets a line or surface at 90 degrees. To ensure ameasure of 90 degrees, snap to the angle.

411


Warning Column <string> found in reference, not inproject!

Reason: The referenced column was found in the reference not the project database.

Recovery: If necessary, you can add a column to the project database and copy the values over.

Warning Drawing not valid type!

Reason: The title block annotation does not match the annotation type table.

Recovery: Change the title block annotation.

Warning Fittings at oneline <numeric value> overlap

Reason: Fittings at either end of the one-line overlap.

Recovery: Modify the specification or parts through annotation OR modify or replace the one-lines.

Warning invalid form path: <string>

Reason: The form path EE_FORM_PATH could not be found.

Recovery: Make sure EE_FORM_PATH is defined in the ./config/assign file and that its value is a full path.

Warning invalid symbol path: <string>

Reason: The symbol path EE_SYM_PATH could not be found.

Recovery: Make sure EE_SYM_PATH is defined in the ./config/assign file and that its value is a full path.

Warning must accept/reject One Line Type selection

Reason: You must accept/reject the one-line type selection form before performing a group operation.

Recovery: Accept or reject the one-line type selection form.

412

A: E

rror

Messag

es


Warning must accept/reject System selection

Reason: You must accept/reject the system selection form before performing a group operation.

Recovery: Accept or reject the system selection form.

Warning must keyin a group name

Reason: When performing the selected group operation, you must key in a group name.

Recovery: Key in the desired group name.

Weight not in range 0 to 31

Reason: The input was not in the valid range for weight.

Recovery: Enter a new value within the range of 0 to 31.

413


414

B: S

ystem/A

pp

M

gm

t.

Appendix B: System/Application Manager Information________________

Appendix B System/ApplicationManager Information

This appendix and the following appendices outline the responsibilities forthe EE Raceway system or application manager. Included in theseappendices are important references and procedures needed to prepare andcustomize the EE Raceway product:

Appendix C: EE Databases describes the EE databases and containsschema descriptions for both the reference and project databases. Importantnew procedures related to RIS and the databases are described in thissection.

Appendix D: Specification describes vendor specifications and how toprepare them.

Appendix E: Eden Symbol Generation describes generation of Edensymbols and provides a sample symbol processor file.

Appendix F: EE File Structure contains the file structure for both EENucleus and EE Raceway. It identifies the files that can be modified anddescribes some important files. You will need this appendix to locate filesthat you want to modify.

Appendix G: Customizing Environment Files explains how to modify thefiles that list the processes, reports, rule checks, and printers in the EERaceway Environment.

Appendix H: alias.cmd file contains the alias.cmd file as it is delivered.The key-in names for commands can be modified by editing these files.Also included in this appendix are two descriptions and printouts related tocustomizing the alias.cmd file and customizing menus.

Appendix I: rway.cmds contains the rway.cmds file. This file is runautomatically when you enter EE Raceway. It attaches the panel menu.You can modify or disable this function through the file.

Appendix J: Reports contains detailed descriptions of the standard andrule checks reports delivered with the product.

Appendix K: RIS Schema Manager contains a detailed description of theRIS Schema Manager utility.

Appendix L: RIS Schema Definition File describes the file that maintainsall schema definitions known to RIS.

415

EE Raceway Modeling Reference Guide - February 2003________________ Appendix M: EE Manager contains a description of the EE Managerutility and its Edit Database process.

Appendix N: EE Configure describes the EE environment variables andhow to configure them.

416

B: S

ystem/A

pp

M

gm

t.

Appendix B: Customizing________________

Customizing

Some simple customization is described in the appendices entitledCustomizing, alias.cmd, and rway.cmds (all involve modifying existing textfiles using an editor). More extensive customization is possible foradvanced users. Such customization includes writing processes and usercommands using the MicroStation software. Refer to the MicroStationApplications Programmer’s Guide for this latter procedure.

Precision Input Form

Several designs of the precision input form are delivered with EE Raceway.The available precision input forms (described below) reside inwin32app\eerway\sym.

Form Name Descriptionpiform* defaultpiform_tal1 tall/thin (design 1)piform_tal2 tall/thin (design 2)piform_thn1 long/thin (design 1)piform_thn2 long/thin (design 2)

* The chapter entitled Precision Input Form contains a detailed illustrationof the default form design (piform).

To change the form design, set the variable EE_PIFORM in the .EErc file(win32app\eenuc) to a different form name.

Adding a One-Line Type

This section outlines the basic steps necessary to add a new one-line type tothe reference database. For detailed information about editing your .unlfiles and database tables, consult the appendix entitled EE Databases.These instructions are intended as a basic workflow.

1. Add the <one-line_type>_spec and <one-line_type>_part tables tothe reference database, as in the following example:

create table trench_spec(

vendor integer not null,ee_units integer not null,ee_dimension_1 real,ee_out_ht_diam real not null,ee_dimension_2 real,ee_out_width real,ee_extension real,

417


ee_transition real,ee_radius real,weight real,material char(20),ee_xs_cell char(6),ee_spec_key char(28) not null,description char(40)

);create index i_fsvendor on trench_spec(vendor);create index i_fsheight on trench_spec(ee_out_ht_diam);create index i_fswidth on trench_spec(ee_out_width);create unique index i_fseekey on trench_spec(ee_spec_key);grant all on trench_spec to public;

create table trench_part(

ee_tl_type integer,ee_tl_subtype integer,ee_tl_qual integer,ee_angle real,ee_weight real,ee_part char(20),ee_symbol char(6),ee_spec_key char(28),ee_spec2_key char(28),ee_part_key char(28) not null,ee_description char(40)

);create index i_fpskey on trench_part(ee_spec_key);create unique index i_fpeekey on fit_part(ee_part_key);grant all on trench_part to public;

2. Add any new vendors to the vendor table in the reference database.

You can add the necessary rows directly to the vendor codelist tablein the database, or you can add the data to your vendor.unl file.

All delivered .unl files reside in win32app\eerway\db.

3. Create a <one-line_type>_spec.unl file and a <one-line_type>_part.unl file which contain the required default values forthe one-line type.

For sample files, refer to the tray_spec and tray_part .unl files thatare delivered with EE Raceway.

418

B: S

ystem/A

pp

M

gm

t.

Appendix B: Customizing________________

4. Add the newly-created <one-line_type>_spec.unl file and the <one-line_type>_part.unl files to the rwayref.cmd file, in a format like thefollowing:

FILE "tray_part.unl" DELIMITER "|";INSERT INTO tray_part;

5. Add records to the mscatalog table (in the reference database) forboth the <one-line_type>_spec and the <one-line_type>_part tables.

You can accomplish this either by adding rows directly to themscatalog table or by inserting records in the mscatref.unl file.

6. Add records to the mscolumns table (in the reference database) forboth the <one-line_type>_spec and the <one-line_type>_part tables.

You can accomplish this either by adding rows directly to themscolumns table or by inserting records in the mscolref.unl file.

7. Add necessary rows to the mscodelist table in the reference databasefor any columns that are codelisted for the one-line type.

You can accomplish this either by adding rows directly to themscodelist table or by inserting records in the mscodref.unl file. Forinformation about codelists, see the appendix entitled EE Databases.

8. Add the new one-line type to the ol_type table.

You can accomplish this either by adding the row directly to theol_type table or by inserting records in the olt.unl file.

9. Run the Update reference schema process to add your new one-linetype to the database.

Adding a Special Fitting

This section outlines the basic steps necessary to add a special fitting to thereference database. For detailed information about editing your .unl filesand database tables, consult the appendix entitled EE Databases. Theseinstructions are intended as a basic workflow.

1. Add the special fitting table to the reference database, as in thefollowing example:

create table transit(

vendor integer not null,

419


ee_units integer not null,ee_out_ht_diam real not null,ee_out_width real,ee_dimension_1 real,weight real,material char(20),ee_part char(20),ee_symbol char(6),ee_part_key char(28) not null,ee_description char(40)

);create index i_tsitvendor on transit(vendor);create index i_tsitheight on transit(ee_out_ht_diam);create index i_tsitwidth on transit(ee_out_width);create index i_tsitdepth on transit(ee_dimension_1);create unique index i_tsiteekey on transit(ee_part_key);grant all on transit to public;

2. Add any new vendors to the vendor table in the reference database.

You can add rows directly to the vendor codelist table in the database,or you can insert records in the vendor.unl file.

3. Add the new special fitting to the three-line type codelist table.

You can add the entry directly to the tl_type table in the database, oryou add the data to your tlt.unl file.

4. Create any new Eden symbols needed to graphically display the newspecial fitting.

For basic information about creating Eden symbols, see the appendixentitled Eden Symbol Generation.

5. Create a <special fitting>.unl that contains the required default valuesfor your fitting.

For a sample special fitting .unl file, refer to the pullbox.unl file thatis delivered with EE Raceway.

6. Add the newly-created <special fitting>.unl file to the rwayref.cmdfile, in a format like the following:

FILE "pullbox.unl" DELIMITER "|";INSERT INTO pullbox;

7. Add a row to the mscatalog table (in the reference database) for thespecial fitting table.

420

B: S

ystem/A

pp

M

gm

t.

Appendix B: Customizing________________ You can accomplish this either by adding a row directly to themscatalog table, or by inserting a record in the mscatref.unl file.

8. Add a row to the mscolumns table (in the reference database) for thespecial fitting table.

You can accomplish this either by adding the row directly to themscolumns table in the database, or by inserting a record in themscolref.unl file.

9. Add necessary rows to the mscodelist table (in the reference database)for any columns that are codelisted for the special fitting.

You can accomplish this either by adding rows directly to themscodelist table or by inserting records in the mscodref.unl file. Forinformation about codelists, see the appendix entitled EE Databases.

10. Add the new special fitting entry to the manual part table.

You can accomplish this either by adding a row to the manual_parttable in the database, or by inserting a record in the manprt.unl file.

11. Run the Update reference schema process to add your new specialfitting to the database.

Reports

You can create or modify standard and rule check reports. The reporttemplate library is delivered in the win32app\eerway\report directory.Delivered reports are created using the RISRPT product and are compatiblewith the DB Access (DBA) product. Reports may also be created using thenative RDBMS report writing product.

Error Messages

Error messages for the delivered commands are located in the error.msgfiles in both win32app\eerway\msg and win32app\eenuc\msg. In these files,the hard-coded error message name is to the left of each = (equal sign). Youcannot change this name. To the right of each = is the message itself, whichyou can modify. Use a standard text editor to modify the error.msg files.

421


EE Environment Variables

This section lists and describes the environment variables that are delivered when youdownload EE Raceway. They include Microstation, EE Nucleus, and EE Raceway-specificvariables.

These environment variables can be modified using the Start > Programs > EENUC > EEConfigure command.

The following environment variables are defined in the win32app\eerway\ee.cfg file:

For MicroStation:

MS_CELL Sets the directory that holds the cell libraries.MS_APP Sets the directory where application executable files are found when

activated from a user command TSK statement.MS_EXE Used as a pointer to application programs.MS_APPMEN Sets the directory where application-/user-defined menus are to found

when activated from an "am=n,cs", "am=n,h1", or "am=n,sb" (i.e."am=ustn,sb1").

MS_DATA Sets the directory that holds the menu file mgds.men, the fileMicroStation uses to save data about the attached menu. This directoryis also the location of user command index (.ndx) files.

MS_TMP Sets the directory for temporary files.MS_HELPFILE Sets the directory for the on-line Help files.MS_HELPPATH Defines the path to the on-line Help files.

The MicroStation\Program\MicroStation\config\msconfig.cfg file containsdetailed descriptions of the MicroStation and Umenu environment variables.

For EE Raceway:

EERD_COMPRESS Compresses the file when you exit a design session.EERD_MSGS Directory for the message files.EERD_TBLS Directory for the database table filesRWAY_FORM_PATH Directory path to the EE Raceway forms.EE_SYM_PATH Directory path to the EE Raceway symbols.EE_SYM_FILE File containing EE Raceway symbols.

The following environment variable is defined in the win32app\eerway\bin\c400 orc100/rmonshell file:

MS_CACH Sets the memory to be allocated for a design file editing session. Thisvariable will override the user preferences setting.

422

B: S

ystem/A

pp

M

gm

t.

Appendix B: EE Environment Variables________________ The following are the environment variables that are recognized by the EE Nucleus product.An asterisk (*) indicates that you cannot override a particular value.

EE_CURPRJ* Directory path for current EE project.EE_DBS* Directory path and project database name.EE_NODENAME Default nodename for archive/restore.EE_REMDIR Default remote path for archive/restore.EE_SCHEMA Schema name for project database.EE_USERNAME Default username for archive/restore.SYS_PASSW_FILE Directory path and filename of password file to enter system manager

page.EE_CUSTOM_SQL User-defined project database sql file.EE_CUSTOM_CMD User-defined project database cmd file.EE_CUSTOM_REFSQL User-defined reference database sql file.EE_CUSTOM_REFCMD User-defined reference database cmd file.

The following are the environment variables defined in the win32app\eenuc\.EErc file,delivered with the EE Nucleus product. An asterisk (*) indicates that you cannotoverride a particular value.

For EE Raceway:

EE_RWAY* Directory path for the EE Raceway product.EERWAY_DAT Directory path for data files.EERWAY_SEED Directory path for seed files.RWAY_CMD Project Database cmd file.RWAY_SQL Project Database sql file.RWAYREF_CMD Reference Database cmd file.RWAYREF_SQL Reference Database sql file.EDEN_LIB Filename for the Eden symbol library.RWAY_EDEN_LIB Directory path for the Eden symbol library.EE_PIFORM Name of the precision input form that displays during the design

session.

The following are the environment variables defined in the win32app\eenuc\bin\EE file,delivered when you download the EE Nucleus product.

MS_USERPREF Directory path and filename of user preference file.MS_CMDWINDRSC Directory path and filename of command window resource file.MS_SYSFONTS Font used by MicroStation for window and menu display.EE_TERM Defines the "tty" type you are running on.ORACLE_SID A variable used for ORACLE databases; it must be set to "A".

The following are the environment variables defined using the EE Configure command,delivered when you download the EE Nucleus product. An asterisk (*) indicates thatyou cannot override a particular value.

MS_DIR Directory path for the MicroStation product.RIS_DIR Directory path for the RIS product.EE_NUC* Directory path for EE Nucleus product.ENV_MSGS Directory path for message files.EENUC_DAT Directory path for data files.

423

EE Raceway Modeling Reference Guide - February 2003________________ DBA_SUPPORT Data files for DB Access Support.EES_REFDB Schema name for reference database.EES_REFSER EE reference database server process.EE_FORM_PATH Directory path for EE forms.EE_SYM_FILE Filename of EE symbol file.EE_SYM_PATH Directory path for EE symbol file.

For ORACLE databases:

ORACLE_HOME Directory path for ORACLE executables.

For INGRES databases:

II_SYSTEM Directory path for INGRES executables.

For INFORMIX databases:

INFORMIXDIR Directory path for INFORMIX executables.

424

C: E

E D

atabases

Appendix C: EE Databases________________

Appendix C EE Databases

All EE databases you create will be relational databases; that is, they are based on the relational data model inwhich a relation is a two-dimensional table comprised of rows and columns. Most relational databases useStandard Query Language (SQL).

The EE products attach to their relational databases through Intergraph Corporation’s Relational InterfaceSystem (RIS), a generic relational database interface. RIS isolates the differences in specific vendors’Relational Database Management Systems (RDBMS), allowing generic network access to all EE databasesgenerated with the following RDBMS’s: Standard Engine (SE) Informix, On-line Informix, Oracle, and Ingres.

This section contains:

Descriptions of the EE databases and the Intergraph software, RIS, that supports it.

Procedures that must be followed by new users of the EE product.

Procedures that must be followed by existing users of the EE product.

Processes needed in the procedures above.

Schema descriptions for the EE project database and the EE reference database.

The Electrical Engineer product line is supported by two relational databases: a project database and a referencedatabase.

The project database contains information applicable to a particular project. A project is an associatedcollection of drawings and their database.

The reference database contains information applicable to multiple projects, such as symbol and partinformation. (For those familiar with EDES, the reference database replaces the concept of shared part entityfiles and active entity files.) One reference database can be accessed by multiple project databases. Thus, youare not forced to re-enter common information for each project. The reference database is identified when youenter a project. You can report and query from the reference database as well as the project database.

425


Relational Interface System (RIS)

All EE products use a RIS schema, which you define, to attach to an SQL-type database. The RIS schemaidentifies a unique database/user combination in a given commercial database system. Different RDBMS’sestablish users in different ways; in fact, the very concept of a database differs greatly from one RDBMS toanother. Through the use the RIS risschema_mgr product, you can update schemas without knowing either thedifferences between RDBMS’s or the syntax of the RIS create schema statement. (See the appendix entitledRIS Schema Manager for more information on the RIS Schema Manager product.)

426

C: E

E D

atabases

Appendix C: Database and RIS Procedures________________

Database and RIS Procedures

You must adhere to the procedures that follow before using EE with a relational database.

For New Users

You must first create an empty database and a user name through your chosen RDBMS. You should consult theindividual RDBMS documentation on installation procedures.

INFORMIX users will now have to create all databases in ANSI mode. Check thedocumentation delivered with the product for information on infxcreate, or see INFORMIXdocumentation for other creation methods.

After you have created an empty database, you must use the RIS Schema Manager product to create a schema.Access RIS Schema Manager through the Database Utilities option in the EE Environment. (See the appendixentitled RIS Schema Manager for detailed information on using the RIS Schema Manager product.) Thisprocess will create the risschema definition file. You can usually locate this file in the RIS product directory,but it can exist anywhere as long as the parameters file (win32app\ingr\share\RISversion\parms) points to it.The risschema file is an ASCII file that contains the names, ownerships, and locations of all RIS schemas anddatabases. The risschema_mgr process updates and maintains the file. You can manage the risschema file inany of the following ways:

— You can create and maintain your own risschema file, using the risschema_mgr process. The processresides locally on your machine and recognizes any RIS schema on any database, local or remote, that wascreated using RIS Schema Manager.

— You can locate the risschema file from another workstation using the risschema_mgr process and access anyschemas created on that machine.

Once you have created a schema on your empty database, you need to populate that database with EE tables anddefault information. To do so, use the Update Schema option under Database Utilities (see Database Utilities,page 50). For more information about the risschema file, see the appendix entitled RIS Schema Definition File.

427


Update Schema (create_db) Process

You can use this program to do the following:

Update an existing empty RIS schema with EE tables and default information.

— OR —

Modify an existing RIS schema’s tables to conform to the structure of a given .sql file. If Updateschema is used with a .sql file that has a different structure than the original .sql file, the process will:

— add new tables listed in the .sql file.

— modify existing tables if the definition of that table has changed in the .sql file. The process replacesthe old table definition with the new table definition keeping column data where column namesmatch.

— load those tables having a unique index with data from the .unl files that are listed in the .cmd files.Where a table lacks a unique index, the process loads it only if the table is empty.

You should run the Update schema process from the EE Environment Project Menu. To run it outside of theEE Environment, you must first export the variable ENV_MSGS to win32app\ingr\eenuc\msg, and then key inthe command line syntax for the process.

This is the command line syntax for the Update schema process:

win32app\eenuc\bin\create_db [-v] [-q .sql file] [-c .cmd file] schema name

-v displays SQL commands as they are executed-q .sql file schema definition file-c .cmd file command file to load schema

To create a new schema, you must have at least:

— an SQL (.sql) file which contains the table and column structure.

If you want to load a schema with default information, you can also include:

— a command (.cmd) file that defines which .unl files to load into which tables;

— AND —

— the corresponding .unl file(s) which contain default information.

428

C: E

E D

atabases

Appendix C: Update Schema (create_db) Process________________

Example:

$ create_db -q win32app\ingr\eerway\db\rwayref.sql -c\win32app\ingr\eerway\db\rwayref.cmd sample_ref

This will populate an empty sample_ref schema, created through the risschema_mgr process on an existingschema, with EE Raceway tables and default reference information.

You can use this process to execute ANY valid RIS-supported SQL statement upon an existingschema. Simply place it in a file and call that filename with the -q option.

429


Reference Schema - General Description

The Electrical Engineer reference database is a multi-table relational database containing default attributeinformation and specification information. You can establish default attributes for drawings, raceway connectpoints (RCPs), one-lines, drop points, and equipment pointers. All specification information is carried in thereference database.

You will access the reference database during the following procedures:

1. When editing/reviewing annotation for EE Raceway elements (title blocks, one-lines, RCPs, straights,fittings, and so forth) during a design session.

2. Selecting the active one-line type parameters during a design session.

3. Reporting.

Default Attributes

Some tables exist in the reference schema to support default attributes, including, for example, the drawing,one-line, RCP, tray_spec, and tray_part tables. Each table must contain at least a subset of the column/attributestructure as its corresponding table in the project schema. For example, if the reference schema is custom-built,the project schema must be custom-built accordingly. But if the project schema is custom-built, the referenceschema needs to be custom-built only if you want defaults for any new column to exist in the reference schema.

Some of the columns in the reference schema tables are required and cannot be modified ordeleted.

Keys

In addition to the default attribute columns, the reference schema tables contains two additional columns:key_column and key_description. The actual column names are defined by the values of the key_columns andkey_description in the mscatalog entry for the given table. The key_column field is a unique index used toidentify a particular row of default attributes in the reference schema. Each of the tables is delivered with oneentry called DEFAULT. If the system cannot find a key for some reason, it uses the DEFAULT key attributes.

Raceway One-Line Keys

A key is stored for each one-line type within a drawing. You will identify these keys through the Active One-Line Type Parameters form. Each of these keys will be the default key for all one-lines of a given one-linetype unless you override the key during annotation for an individual one-line. The one-line table is deliveredwith both the DEFAULT and METRIC DEFAULT keys. The DEFAULT key is used with the seed designfile using English measurements, while the METRIC DEFAULT is used with the seed design file using Metricmeasurements.

430

C: E

E D

atabases

Appendix C: Reference Schema - General Description________________

Raceway Connect Point Keys

You will identify the key for RCPs through the Raceway Defaults form. The key you specify will serve as thedefault key for all RCPs unless you override the key during annotation for an individual RCP. Text annotationoverrides any default values.

Equipment Pointer Keys

You will identify the key for equipment pointers through the Raceway Defaults form. The key you specify willserve as the default key for all equipment pointers unless you override the key during annotation for anindividual equipment pointer. Text annotation overrides any default values.

Drop Point Keys

You will identify the key for drop points through the Raceway Defaults form. The key you specify will serveas the default key for all drop points unless you override the key during annotation for an individual drop point.Text annotation overrides any default values.

431


Codelists

Codelists are tables in the reference database which contain all available values for a particular column of atable in the project database. For example, the codelist table ol_type in the reference database will contain allpossible values that can be loaded into the column ol_type in the straight, fitting, and one_line tables in theproject database.

During loads of the project database, the reference database codelists are matched to the annotated values. Onlyvalues in the reference database codelist tables are loaded into the project database. The system issues you awarning if an annotated value does not match a value in the codelist.

You must be familiar with the codelist tables that follow.

Approval Status Codelist Table

The approv_status codelist table defines the available approval status values. You can add newapproval status rows to this table, but you must not remove any of the existing rows.

COLUMN_NAME TYPE DESCRIPTION

index_column integer approval status index numberindex_value char(20) approval status description

The approval status rows delivered with EE Raceway are:

index_column index_value

1 1 - blank2 2 - approved3 3 - approved4 4 - approved5 5 - approved6 6 - approved7 7 - approved8 8 - approved9 9 - approved10 10 - approved11 11 - not approved

432

C: E

E D

atabases

Appendix C: Codelists________________

Cardinal Codelist Table

The cardinal codelist table defines the available cardinal point routing justification locations. Youmust not add or remove to this table.


ee_car_num integer cardinal index numberee_cardinal char(20) cardinal description

The cardinal point values delivered with EE Raceway are:

ee_car_num ee_cardinal

0 TOP LEFT1 CENTER LEFT2 BOTTOM LEFT6 TOP CENTER7 CENTER CENTER8 BOTTOM CENTER12 TOP RIGHT13 CENTER RIGHT14 BOTTOM RIGHT

Drawing Type Codelist Table

The drawing_type codelist table defines the available drawing types. You can add new drawing typesto this table, but you must not remove the existing row.


code Char(20) drawing type

unknown unknown unknown

The drawing type delivered with EE Raceway is:

code

RACEWAY

Manual Fitting Part Codelist Table

The manual_part codelist table defines the manually-placed special fittings available with the product.The table contains the index_column column, which is an integer value that the software uses touniquely identify an index value. The table also contains the ee_part_table column which itselfcontains the mscatalog number of the table holding the part information. The ee_rcp_ol_type columncontains the index_column value for the one-line type to which the RCP is assigned.

433

EE Raceway Modeling Reference Guide - February 2003________________ COLUMN_NAME TYPE DESCRIPTION

index_column integer manual_part index numberindex_value char(20) manual_part descriptionee_part_table integer special fitting parts table numberee_rcp_ol_type integer one-line type index column numberee_manpart_type integer manual part type index number

The special manual fittings delivered with EE Raceway are:

index_column index_value ee_part_table ee_rcp_ol_type ee_manpart_type

1 conduit body 246 3 02 pullbox 249 3 03 light fixture 250 3 1

One-Line Type Codelist Table

The ol_type table defines the one-line types that are available in a raceway project. The table containsthe index_column column, which is an integer value the software uses to uniquely identify an indexvalue. The table also contains the ee_spec, ee_part, ee_ol, and ee_rcp_part tables which define thetables containing specification information for each one-line type. The ee_priority_level columndefines the routing priority for each one-line type.


index_column integer one-line type index numberindex_value char(20) one-line type descriptionee_spec_table integer specification table mscatalog numberee_part_table integer spec parts table mscatalog numberee_ol_table integer one-line table mscatalog numberee_rcp_part_table integer special fitting parts table numberee_max_run_angle integer maximum bends allowed per runee_priority_level integer one-line type nest level

The one-line types delivered with EE Raceway are:

indx_col index_value ee_spec ee_part ee_ol rcp_part run_angle priority

1 TRAY 240 241 204 0 0 52 WIREWAY 242 243 204 0 0 53 CONDUIT 244 245 204 246 360 104 AIRWAY 247 248 204 0 0 105 DUCTBANK 260 0 204 0 0 7

434

C: E

E D

atabases


RCP Type Codelist Table

This table defines how the EE Raceway software uses RCPs (Raceway Connect Points). The rcp_typetable contains the index_column column, which is an integer value the software uses to uniquelyidentify an index value. You must not add or remove rows from this table, nor should you modify theindex_column values. You can modify the index_value values.


index_column integer rcp type index numberindex_value char(20) rcp type description

The RCP types delivered with EE Raceway are:

index_column index_value description

1 <blank> general raceway connect point2 ROUTE raceway connect point and route point

System Codelist Table

The ee_system table must be loaded in the reference database before you can create any raceway designfiles. You can add, remove, or update any of the systems delivered with EE Raceway. The systemtable contains the system_num column, which is an integer value the software uses to uniquely identifya system name.


system_num integer system index numbersystem_name char(20) system name

435

EE Raceway Modeling Reference Guide - February 2003________________ The systems delivered with EE Raceway are:

system_num system_name

1 Control2 Communication3 High Voltage4 Low Voltage5 Alarm6 Instrumentation7 Signal8 Digital9 Analog10 Thermocouple11 RTD12 Medium Voltage13 Normal Lighting14 Emergency Lighting15 Security16 Fire Safety17 DC Power18 Control and Signal

Three-Line Type Codelist Table

The tl_type table defines the three-line types that are available with the EE Raceway product. Thetable contains the index_column column, which is an integer value the software uses to uniquelyidentify an index value. You must not add or remove rows from the table, nor should you modify theindex_column values. You can modify the index_value values.


index_column integer three-line type index numberindex_value char(20) three-line type description

The three-line types delivered with EE Raceway are:


1 STRAIGHT2 ELBOW3 WYE4 CROSS11 PULLBOX12 CONDUIT BODY14 DROPOUT

436

C: E

E D

atabases


Three_Line Subtype Codelist Table

The tl_subtype table further defines the available three-line types. The table contains the index_columncolumn, which is an integer value the software uses to uniquely identify an index value. You must notadd or remove rows from the table, nor should you modify the index_column values. You can modifythe index_value values.


index_column integer three-line subtype index numberindex_value char(20) three-line subtype description

The three-line subtypes delivered with EE Raceway are:


1 <blank>2 VERTICAL3 INSIDE VERTICAL4 OUTSIDE VERTICAL5 HORIZONTAL6 LEFT HORIZONTAL7 RIGHT HORIZONTAL8 REDUCER9 LEFT REDUCER10 RIGHT REDUCER

Three-Line Qualifier Codelist Table

The tl_qual table further defines the three-line types. The table contains the index_column column,which is an integer value the software uses to uniquely identify an index value. You must not add orremove rows from the table, nor should you modify the index_column values. You can modify theindex_value values.


index_column integer three-line qualifier index numberindex_value char(20) three-line qualifier description

437

EE Raceway Modeling Reference Guide - February 2003________________ The three-line qualifiers delivered with EE Raceway are:


1 <blank>2 RIGID3 BENDABLE4 FLEXIBLE5 ADJUSTABLE

Units Codelist Table

This table (ee_unit) defines the units that are used for one-line dimension values. The unit tablecontains the index_column column, which is an integer value the software uses to uniquely identify anindex value. You must not add or remove rows from this table, nor should you modify theindex_column values. You can modify the index_value values.


index_column integer units index numberindex_value char(20) units description

The units delivered with EE Raceway are:


1 English2 Metric

Vendor Codelist Table

You must have a vendor in the vendor codelist table before loading any specification tables in thedatabase. You can add vendors as necessary to this table, but do not remove the rows delivered withthe product. The vendor table contains the index_column column, which is an integer value thesoftware uses to uniquely identify a vendor name.


index_column integer vendor index numberindex_value char(20) vendor namecatalog char(20) catalog

438

C: E

E D

atabases

Appendix C: Codelists________________ The vendors delivered with EE Raceway are:

index_column index_value catalog

1 default delivered blank2 sample delivered blank3 unknown delivered blank4 English sample delivered blank

Wire/Cable Code Codelist Table

This table (ee_pcbl_code) defines the wire/cable code that are used for selecting a Wire/Cable duringthe EERWAY command CONDUIT SIZING. The wire/cable code table contains the index_columncolumn, which is an abbreviated value the software uses to uniquely identify an index value. You mayadd or remove rows from this table, the values of the index_column should include all the wire/cablecodes represented in the data of the Wire/Cable (ee_pseudo_cable) table code column. Theindex_value provides a more complete description of the entry.


index_column char(20)not null

wire/cable code index value

index_value char(20) wire/cable code description

The wire/cable codes delivered with EE Raceway are:


AC ACAD ADAG AGAH AHAM AMAN ANAP APAR ARAS ASCP CPCQ CQCV CVCW CWCX CX

439


Wire/Cable Configuration Codelist Table

This table (ee_pcbl_config) defines the wire/cable configuration that are used for selecting aWire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable configuration tablecontains the index_column column, which is an abbreviated value the software uses to uniquelyidentify an index value. You may add or remove rows from this table, the values of the index_columnshould include all the wire/cable configurations represented in the data of the Wire/Cable(ee_pseudo_cable) table config column. The index_value provides a more complete description of theentry.



wire/cable configuration index value

index_value char(20) wire/cable configuration description

The wire/cable configurations delivered with EE Raceway are:


\C single conductorPR "pair 2 conductorsTR "triad" 3 conductors

Wire/Cable Size Codelist Table

This table (ee_pcbl_size) defines the wire/cable size that are used for selecting a Wire/Cable during theEERWAY command CONDUIT SIZING. The wire/cable size table contains the index_columncolumn, which is an abbreviated value the software uses to uniquely identify an index value. You mayadd or remove rows from this table, the values of the index_column should include all the wire/cablesizes represented in the data of the Wire/Cable (ee_pseudo_cable) table cable_size column. Theindex_value provides a more complete description of the entry.



wire/cable size index value

index_value char(20) wire/cable size description

The wire/cable sizes delivered with EE Raceway are:


36 AWG 36 AWG34 AWG 34 AWG32 AWG 32 AWG30 AWG 30 AWG28 AWG 28 AWG27 AWG 27 AWG

440

C: E

E D

atabases

Appendix C: Codelists________________ 26 AWG 26 AWG24 AWG 24 AWG22 AWG 22 AWG20 AWG 20 AWG18 AWG 18 AWG16 AWG 16 AWG14 AWG 14 AWG12 AWG 12 AWG10 AWG 10 AWG8 AWG 8 AWG6 AWG 6 AWG4 AWG 4 AWG3 AWG 3 AWG2 AWG 2 AWG1 AWG 1 AWG1/0 AWG 1/0 AWG2/0 AWG 2/0 AWG3/0 AWG 3/0 AWG4/0 AWG 4/0 AWG250 MCM 250 MCM300 MCM 300 MCM350 MCM 350 MCM400 MCM 400 MCM500 MCM 500 MCM600 MCM 600 MCM700 MCM 700 MCM750 MCM 750 MCM800 MCM 800 MCM900 MCM 900 MCM1000 MCM 1000 MCM1250 MCM 1250 MCM1500 MCM 1500 MCM1750 MCM 1750 MCM2000 MCM 2000 MCM

Wire/Cable Color Codelist Table

This table (ee_pcbl_color) defines the wire/cable insulation color that are used for selecting aWire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation color tablecontains the index_column column, which is an abbreviated value the software uses to uniquelyidentify an index value. You may add or remove rows from this table, the values of the index_columnshould include all the wire/cable insulation colors represented in the data of the Wire/Cable(ee_pseudo_cable) table color column. The index_value provides a more complete description of theentry.

441

EE Raceway Modeling Reference Guide - February 2003________________ COLUMN_NAME TYPE DESCRIPTION


wire/cable insulation color index value

index_value char(20) wire/cable insulation color description

The wire/cable insulation colors delivered with EE Raceway are:


BLK BLACKW WHITER REDGR GREENORN ORANGEBL BLUEW/BLK WHITE/BLACKR/BLK RED/BLACKGR/BLK GREEN/BLACKORN/BLK ORANGE/BLACKBL/BLK BLUE/BLACKBLK/W BLACK/WHITER/W RED/WHITEGR/W GREEN/WHITEBL/W BLUE/WHITEBLK/R BLACK/REDW/R WHITE/REDORN/R ORANGE/REDBL/R BLUE/REDR/GR RED/GREENORN/GR ORANGE/GREENBLK/W/R BLACK/WHITE/REDW/BLK/R WHITE/BLACK/REDR/BLK/W RED/BLACK/WHITEGR/BLK/W GREEN/BLACK/WHITEORN/BLK/W ORANGE/BLACK/WHITEBL/BLK/W BLUE/BLACK/WHITEBLK/R/GR BLACK/RED/GREENW/R/GR WHITE/RED/GREENR/BLK/GR RED/BLACK/GREENGR/BLK/ORN GREEN/BLACK/ORANGEORN/BLK/GR ORANGE/BLACK/GREENBL/W/ORN BLUE/WHITE/ORANGEBLK/W/ORN BLACK/WHITE/ORANGEW/R/ORN WHITE/RED/ORANGEORN/W/BL ORANGE/WHITE/BLUEW/R/BL WHITE/RED/BLUEBLK/W/GR BLACK/WHITE/GREENW/BLK/GR WHITE/BLACK/GREENR/W/GR RED/WHITE/GREENGR/W/BL GREEN/WHITE/BLUEORN/R/GR ORANGE/RED/GREEN

442

C: E

E D

atabases

Appendix C: Codelists________________ BL/R/GR BLUE/RED/GREENBLK/W/BL BLACK/WHITE/BLUEW/BLK/BL WHITE/BLACK/BLUER/W/BL RED/WHITE/BLUEGR/ORN/R GREEN/ORANGE/REDGR/R/BL GREEN/RED/BLUEBL/R/ORN BLUE/RED/ORANGEBLK/ORN/R BLACK/ORANGE/REDBRN BROWNY YELLOW

Wire/Cable Voltage Codelist Table

This table (ee_pcbl_volt) defines the wire/cable insulation voltage rating that are used for selecting aWire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation voltagerating table contains the index_column column, which is an abbreviated value the software uses touniquely identify an index value. You may add or remove rows from this table, the values of theindex_column should include all the wire/cable insulation voltage ratings represented in the data of theWire/Cable (ee_pseudo_cable) table voltage column. The index_value provides a more completedescription of the entry.



wire/cable insulation voltage rating index value

index_value char(40) wire/cable insulation voltage rating description

The wire/cable voltage ratings delivered with EE Raceway are:


120 Low (Single phase, 2 wire system)120/240 Low (Single phase, 3 wire system)208Y/120 Low (Three phase, 4 wire system)240/120 Low (Three phase, 4 wire system)240 Low (Three phase, 3 wire system)480Y/277 Low (Three phase, 4 wire system)480 Low (Three phase, 3 wire system)600 Low (Three phase, 3 wire system)2400 Medium (Three phase, 3 wire system)4160Y/2400 Medium (Three phase, 4 wire system)4160 Medium (Three phase, 3 wire system)4800 Medium (Three phase, 3 wire system)6900 Medium (Three phase, 3 wire system)8320Y/4800 Medium (Three phase, 4 wire system)12000Y/6930 Medium (Three phase, 4 wire system)12470Y/7200 Medium (Three phase, 4 wire system)13200Y/7620 Medium (Three phase, 4 wire system)13200 Medium (Three phase, 3 wire system)13800Y/7970 Medium (Three phase, 4 wire system)

443

EE Raceway Modeling Reference Guide - February 2003________________ 13800 Medium (Three phase, 3 wire system)20780Y/12000 Medium (Three phase, 4 wire system)22860Y/13200 Medium (Three phase, 4 wire system)23000 Medium (Three phase, 3 wire system)24940Y/14400 Medium (Three phase, 4 wire system)34500Y/19920 Medium (Three phase, 4 wire system)34500 Medium (Three phase, 3 wire system)46000 Medium (Three phase, 3 wire system)69000 Medium (Three phase, 3 wire system)

Wire/Cable Insulation Type Codelist Table

This table (ee_pcbl_insul) defines the wire/cable insulation type that are used for selecting aWire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation type tablecontains the index_column column, which is an abbreviated value the software uses to uniquelyidentify an index value. You may add or remove rows from this table, the values of the index_columnshould include all the wire/cable insulation types represented in the data of the Wire/Cable(ee_pseudo_cable) table insulation column. The index_value provides a more complete description ofthe entry.



wire/cable insulation type index value

index_value char(100) wire/cable insulation type description

The wire/cable insulation types delivered with EE Raceway are:


A Asbestos (Without asbestos braid)AA Asbestos (With suitable braid material)AI Asbestos (Without asbestos braid)AIA Impregnated Asbestos (With suitable braid material)A VA Impregnated Asbestos & Varnished CambricAVB Impregnated Asbestos & Varnished Cambric (Flame retardant, cotton braid)AVL Impregnated Asbestos & Varnished Cambric (AVL-lead sheath)FEP Fluorinated Ethylene PropyleneFEPB Fluorinated Ethylene Propylene (Glass braid Asbestos or other Suitable braid material)MI Magnesium Oxide (Copper)MTW Flame-, Moisture-, Heat- and Oil-Resistant ThermoplasticPFA PerfluoroalkoxyPFAH PerfluoroalkoxyRH Heat-Resistant Rubber (Moisture-resistant, flame- non-metallic covering)RHH Heat-Resistant Rubber (Moisture-resistant, flame- non-metallic covering)RHW Moisture- and Heat-Resistant Rubber (Moisture-resistant, flame-non-metallic covering)SA Silicone Rubber (Asbestos, glass or other suitable braid material)SIS Heat-Resistant RubberTA Thermo-plastic and Asbestos (Flame-retardant, non-metallic covering)TBS Thermo-plastic (Flame-retardant, non-metallic covering)

444

C: E

E D

atabases

Appendix C: Codelists________________ TFE Extruded Polytetra-fluoro-ethyleneTHHN Flame-, Heat-Resistant Thermoplastic (Nylon jacket or equivalent)THHN/THWN Flame-, (Moisture-) & Heat-Resistant Thermoplastic (Nylon jacket or equivalent)THW Flame-, Moisture- & Heat-Resistant ThermoplasticTHWN Flame-, Moisture- & Heat-Resistant Thermoplastic (Nylon jacket or equivalent)TW Flame-Retardant, Moisture- and Heat-Resistant ThermoplasticUF Moisture-Resistant, Moisture- and Heat-Resistant (Integral with insulation)USE Heat- and Moisture-Resistant (Moisture-resistant non-metallic covering)V Varnished Cambric (Nonmetallic covering or lead sheath)XHHN Flame-Retardant Cross-Linked Synthetic PolymerZ Modified Ethylene Tetrafluoro-ethylene

Yes-No Codelist Table

The ee_yes_no codelist table defines the available positive and negative user responses. You must notadd or remove rows from this table.


index_column integer yes-no response index numberindex_value char(20) yes-no response description

The Yes-No values delivered with EE Raceway are:


0 NO1 Yes

445


Fitting Environment Rules

The fitting environment rules are the rules stored in the reference database table tl_fit_env that control the PlaceFitting by Rule commands. The software compares the one-line environment at an RCP in the design file withthe rules stored in this table to determine which fitting to place at the RCP. You can add, remove, or update anyof the rules delivered with EE Raceway. The software, at least, compares the number of intersection one-lines,the one-line type, and the angles between the intersectin one-lines with the rules in the fitting environment tableto find a match. If found, the symbol in the part table stored will be placed at the RCP.


ee_ol_type integer intersecting one-line’s one-line type numberee_tl_type integer intersecting one-line’s three-line type number, zero if not applicableee_tl_subtype integer intersecting one-line’s three-line subtype number, zero if not applicableee_tl_qual integer intersecting one-line’s three-line qualifier number, zero if not

applicableee_num_ols integer number of intersecting one-linesee_pln_angles char(40) planar angles between the intersecting one-lines. Angles must be

defined relative to a single one-line.ee_prp_angles char(40) non-planar angles between the intersecting one-lines. Angles must be

defined relative to a single one-line.ee_part_table integer fitting mscatalog table numberee_symbol char(6) fitting EDEN symbol name

The fitting environment rules delivered with EE Raceway are:

olt tlt tlst tlq nol pln prp tbl sym

3 0 0 0 2 180 - 246 CC3 0 0 0 2 90 - 246 CLB3 0 0 0 3 90,180 - 246 CT3 0 0 0 3 90 90 246 CGUAM3 0 0 0 4 90,180,270 - 246 CX3 0 0 0 4 90,180 90 246 CGUAW3 0 0 0 5 90,180,270 90 246 CEABY

446

C: E

E D

atabases

Appendix C: Fitting Environment Rules________________

Intersecting Conduit One-lines

Planar Angles = 90, 180, 270

Non-Planar Angle = 90

447


Project Schema - General Description

The project schema contains information about the drawings that are part of a particular project. The schemastores information associated with the elements in each drawing; its one-lines, RCPs, and three-lines. Defaultand specification information is copied from the reference schema into the project schema when you run LoadDatabase.

448

C: E

E D

atabases

Appendix C: Updating Schemas________________

Updating Schemas

Before you can update (that is, load with EE tables and default data) a schema, you must create the schemasusing one of the currently-supported RDBMS’s (INFORMIX, ORACLE, INGRES). Additionally, you mustuse the schema creation form in RIS Schema Manager to create a valid RIS schema on the database.

Updating a Project Schema

Update the project schema from the Database Utilities menu in the Electrical Engineer environment, using theUpdate project schema option. The following fields accept your input for the Update schema process:

Schema name

This field accepts the name of the RIS schema to be updated. No paths are required, since this is a schemaname, not a database name. Given the schema name, RIS will know where the appropriate database is located.

Schema password

This field accepts the name of the password for the specified schema, if one exists.

Sql and Cmd Files

Accept the names of the sql and cmd (command) files associated with each application. The sql file containsthe commands used to create tables, views, and to grant permissions within the schema, while the command fileloads the schema tables with default data. These fields require a full path to the files.

The application checkboxes to the left of these fields allow you to specify which EE product(s) are supplyingthe sql and cmd files to the process. If you select multiple applications, then Update project schema runs eachapplication sequentially against the database.

Updating Reference Schemas

Update the reference schema from the Database Utilities menu in the Electrical Engineer environment, usingthe Update reference schema option. The following fields accept your input for the Update schema process:

Schema name

This field accepts the name of the RIS schema to be updated. No paths are required, since this is a schemaname, not a database name. Given the schema name, RIS will know where the appropriate database is located.

Schema password

This field accepts the name of the password for the specified schema, if one exists.

Sql and Cmd Files

449

EE Raceway Modeling Reference Guide - February 2003________________ Accept the names of the sql and cmd (command) files associated with each application. The sql file containsthe commands used to create tables, views, and to grant permissions within the schema, while the command fileloads the schema tables with default data. These fields require a full path to the files.

The application checkboxes to the left of these fields allow you to specify which EE product(s) are supplyingthe sql and cmd files to the process. If you select multiple applications, then Update reference schema runseach application sequentially against the database.

Schema Names

When creating your RIS schemas, you should use the same name as your project, since this will be the defaultname when you enter the project. However, you can override the default by exporting the $EE_SCHEMAvariable in your $HOME/.EErc file to be your project schema name.

450

C: E

E D

atabases

Appendix C: Modifying the Reference Schema________________

Modifying the Reference Schema

You can customize the database schema before creating a schema or after the schema exists. To modify thedatabase schema before schema creation, simply include the necessary changes in the .sql file before Updateschema is executed. The .sql file is a series of SQL statements recognized by RIS to create your database

An existing database schema can also be modified. The SQL statements in the .sql file are the input to theUpdate schema process. The table definitions that exist in this file determine how the tables will look whencomplete. Therefore, columns can be added or removed from an existing schema according to the "createtable" statements in the .sql file. For example, columns are added into the .sql file for the one_line table, thesecolumns will be added into the existing rows of the existing one_line table. When this process finds a "createtable" statement for a table that exists in the schema, the following actions take place:

1. Saves rows from existing table.

2. Drops existing table (also drops indexes).

3. Creates new table according to "create table" statement.

4. Loads new table with saved row information for column names that were in previous definition.

If rows exist in the updated table, any new columns that are added will be blank in each row. The newtable will have only those columns specified in the "create table" statement in the table definition.Therefore, you need only to modify the ".sql" file in order to modify a schema.

The following is a list of schema modification rules for Update Schema to keep in mind.

1. You lose any columns and column information that you have not specified in the "create table" statement.If you had used the RDBMS to alter the table by adding a column and then run Update schema withoutmaking the appropriate change to the ".sql" file, you would lose any data that may have been on thatcolumn.

2. Columns that you added into an existing loaded table would have no data stored in them.

3. Renaming of a column is processed by removing the column and adding another. The removed column insuch a case will lose its data and the added column will be blank.

4. You can modify the size of a column, for example, from "char(10)" to "char(200)" or "smallint" to"integer", but changing from "char" to "integer" is dangerous and an illegal conversion can occur. If youmodify a character column to make it smaller (resizing char(20) to be char(10), for example), then anyrow containing data which exceeds the new character limit will be lost.

5. The .unl file will always be loaded into a table which has a unique index. Any duplicate rows will becounted and ignored; the unique index prevents the entry of duplicate information when updating any EEapplication. If a table does not have a unique index, then the .unl file will be loaded only if the table isempty.

Table names can be changed except for table names that begin with the letters "ms" and "ee_". They must alsobe changed appropriately in the MSCATALOG table in order for the software to run properly. Keep in mindthat the columns within the tables in the reference schema must be a subset of the columns of the correspondingtables in the project schema.

451

EE Raceway Modeling Reference Guide - February 2003________________ The databases are initially loaded with the *.unl files as defined in the command file. The Update schemaprocess initiates the command file which automatically finds and loads the information in the .unl files into thedatabase. These files can be edited by the system manager to include additional defaults, part data, and codelistvalues. Use caution when editing these files since they are in a format for loading sequentially into a table.Certain columns are defined in the .sql file as being non-null which means the data entered from the .unl filemust not be null for that column.

There are two ways to modify existing rows in the reference schema.

The .unl files can be modified before the schema is updated.

— OR —

You can modify the rows in the created schema through

1. the RDBMS’s interactive query product, such as INFORMIX’s ISQL or FORMS, or ORACLE’ssqlplus, or INGRES’s SQL.

2. the RIS Interactive Query Utility (win32app\ingr\share\ris\bin\risgui.exe).

3. DB Access’s Database Edit Utility (see the section in the appendix entitled EE Manager for moreinformation on this utility)

4. the EE Database Utilities (risschema_mgr utility – win32app\ingr\share\ris\bin\rismgr.exe)

The following steps can be used as a guideline for modifying the reference schema before it is updated:

1. To see which .unl files are being loaded into the reference database, look at the command (.cmd) file youwill be using. The following is a typical example of what can be contained in this file:

FILE "olt.unl" DELIMITER "|";INSERT INTO ol_type;

These lines tell the update schema process that the file "olt.unl" is to be inserted into the ol_type table. Inthis case the "olt.unl" file will exist in the current directory but a full path name can be specified on thisfile (e.g. FILE win32app\ingr\eerway\db\olt.unl). The delimiter is one character long. It tells the processthat the "|" character separates each column of data in the olt.unl file.

Do not remove any lines from this file that would effect the current .unl files from beingloaded. All existing .unl files must be loaded for proper product execution.

2. Edit the desired .unl file making sure the delimiter "|" is used between each field. Each line represents arow to be inserted into the database and each field represents the corresponding column in the database.

The following is an example of what a line in the "olt.unl" file might look like:

1|TRAY|240|241|204|0|0|1|

452

C: E

E D

atabases

Appendix C: Modifying the Reference Schema________________ In this example, "1" is the index_column value, "TRAY" is the index_value column value, "240" is theee_spec_table column, etc. If in the "olt.unl" file you would like to add additional entries, you can editthis file. Make sure you line up the delimited fields with the tables’ columns.

The following example demonstrates how to load a new .unl file containing your own specification informationinto the reference database.

1. cd win32app\ingr\eerway\db

2. Edit the command file rwayref.cmd. Insert the following lines into this file:

FILE "catalog.unl" DELIMITER "|";INSERT INTO tray_spec;

3. Create a new file in the current directory, naming it catalog.unl. Edit this file to include any trayspecification information you want to load into the reference database, separating each column of datawith a pipe symbol (|). For example:

1|1|4|18|18|0|0|12|10|STEEL|A|0418SHV|4x18 VENTRIB SHV|1|1|4|24|24|0|0|12|10|STEEL|A|0424SHV|4x24 VENTRIB SHV|

4. When you have finished editing the .unl file, run the Update reference schema process to load thespecification information into the tray_spec table.

453


EE Raceway Reference Database SchemaDescription

This section lists and describes the tables in the EE Raceway reference database schema, and includes detailedinformation about the columns that comprise each table.

An asterisk (*) indicates that you must not modify the column name. You should not modifythose column names having a prefix of "ee_".

approv_status

This codelist table defines the available approval status values: blank, approved, not approved, and soforth. See the section entitled Codelists earlier in this appendix for a detailed description of this table.

Column Name Type Index Nullindex_column integer no noindex_value Char(20) no yes

index_column: an integer value used by the software to uniquely identify an approved statusdescription.

index_value: the column that contains the name of each available approved status.

away_part

This table stores the part specification information for the one-line type AIRWAY.

Column Name Type Index Nullee_tl_type* integer no yesee_tl_subtype* integer no yesee_tl_qual* integer no yesee_angle* real no yesee_symbol* Char( 6) no yesee_spec_key* Char( 28) dups yesee_spec2_key* Char( 28) no yesee_part_key* Char( 28) uniq noee_description* Char( 40) no yes

ee_tl_type: the codelisted column used to define the three-line type.

ee_tl_subtype: the codelisted column used to define the three-line subtype.

ee_tl_qual: the codelisted column used to define additional information about the three-line type.

454

C: E

E D

atabases

Appendix C: EE Raceway Reference Database Schema Description________________ ee_angle: the column used to define the airway fitting bend angle.

ee_symbol: the column used to define the airway part EDEN symbol name to the EE software.

ee_spec_key: the key to the appropriate airway specification table row containing general specificationinformation.

ee_spec2_key: if the current airway part is a reducer, this column is the key to the row in the otherairway specification.

ee_part_key: the unique key to the appropriate reference database record for the default values.

ee_description: the description of the default values for each ee_part_key.

away_spec

This table stores the general specification information for the one-line type AIRWAY. EE Racewayuses airways to reserve space for the routing of cable or other raceway material, and also to maintainconnectivity to a raceway system.

Column Name Type Index Nullee_units* integer no noee_out_ht_diam* real dups noee_out_width* real no yesee_extension* real no yesee_transition* real no yesee_radius* real no yesee_xs_cell* Char( 6) no yesee_spec_key* Char( 28) uniq noee_description Char( 40) no yes

ee_units: the codelisted column used to define the units of measurement.

ee_out_ht_diam: the column used to define the airway outside diameter or height to the EE racewaysoftware.

ee_out_width: the column used to define the airway outside width to the EE raceway software.

ee_extension: the column used to define the airway fitting extension length to the EE racewaysoftware.

ee_transition: the column used to define the airway fitting transition length to the EE racewaysoftware.

ee_radius: the column used to define the airway fitting bend radius to the EE raceway software.

455

EE Raceway Modeling Reference Guide - February 2003________________ ee_xs_cell: the column used to define the airway cross section graphic that is used during sketchpropagation. The only valid entries are: A, B, or C. The associated shapes are shown below.

ee_spec_key: the unique key to the appropriate reference database record for the default values.

ee_description: the description of the default values for each ee_spec_key.

cardinal

This codelist table defines the available cardinal point locations (top left, center left, bottom left, and soforth). Refer to the section entitled Codelists earlier in this appendix for a detailed description of thistable.

Column Name Type Index Nullee_car_num integer uniq noee_cardinal Char( 20) dups yes

ee_car_num: an integer value used by the software to uniquely identify a cardinal point description.

ee_cardinal: the column that contains the name of each available cardinal point.

456

C: E

E D

atabases

Appendix C: EE Raceway Reference Database Schema Description________________

cond_body

This table stores the specification information for the manual fitting CONDUIT BODY.

Column Name Type Index Nullvendor integer dups noee_units* integer no nonominal_size_1 real no yesnominal_size_2 real no yesweight real no yesmaterial Char( 20) no yesee_part* Char( 20) no yesee_symbol* Char( 6) no yesee_dimension_1* real no yesee_dimension_2* real no yesee_dimension_3* real no yesee_dimension_4* real no yesee_dimension_5* real no yesee_dimension_6* real no yesee_part_key* Char( 28) uniq noee_description* Char( 40) no yesee_tl_type* integer no novolume real no yesstyle Char( 20) no yesee_pull_point integer no yes

vendor: the codelisted column used to define the vendor of the conduit body special fitting.


nominal_size_1: the column used to define a conduit body nominal size.

nominal_size_2: the column used to define a conduit body nominal size.

weight: the column used to define the conduit body weight.

material: the column used to define the conduit body material.

ee_part: the column used to define the conduit body part number.

ee_symbol: the column used to define the conduit body part EDEN symbol name to the EE software.

ee_dimension_1: the column used to define a conduit body dimension value to eden and the racewayreports.



457

EE Raceway Modeling Reference Guide - February 2003________________ ee_dimension_4: the column used to define a conduit body dimension value to eden and the racewayreports.






volume: the column used to define a conduit body volume.

style:the column used to describe the conduit body style or type.

ee_pull_point: the codelisted column used to define the conduit body as a cable pull point.

cond_fill_calc

This table is used to specify the maximum allowable percent fill of a conduit based on the armor typeof the cable outer jackets and number of cables within the conduit. This calculation assumes ahomogeneous mixture of either all LEAD or all NON-LEAD armor types for the cable outer jackets forthe cables routed within the same conduit. If the cables contained in a conduit exceed the maximumallowable conduit fill, then the conduit is marked as being overfilled.

Column Name Type Index Nullee_rule_set Char( 20) no yesee_jacket_armor Char( 10) no yesee_num_cables integer no noee_max_fill real no yes

ee_rule_set: identification of the rule set that applies to the raceway system fill calculations, forexample NEC 1990.

ee_jacket_armor: material type of the cable outer jacket armor.

ee_num_cables: number of cables in the conduit.

ee_max_fill: maximum allowable percent fill.

458

C: E

E D

atabases


cond_part

This table stores the part specification information for the one-line type CONDUIT.

Column Name Type Index Nullee_tl_type* integer no noee_tl_subtype* integer no noee_tl_qual* integer no noee_angle* real no yesee_weight* real no yesee_part* Char( 20) no yesee_symbol* Char( 6) no yesee_spec_key* Char( 28) dups yesee_spec2_key* Char( 28) no yesee_part_key* Char( 28) uniq noee_description* Char( 40) no yes




ee_angle: the column used to define the conduit fitting bend angle.

ee_weight: the column used to define the conduit part weight.

ee_part: the column used to define the conduit part number.

ee_symbol: the column used to define the conduit part EDEN symbol name to the EE software.

ee_spec_key: the key to the appropriate conduit specification table row containing generalspecification information.

ee_spec2_key: if the current conduit part is a reducer, this column is the key to the row in the otherconduit specification.



459


cond_spec

This table stores the general specification information for the one-line type CONDUIT.

Column Name Type Index Nullvendor integer dups noee_units* integer no nonominal_size real no yesee_dimension_1* real no yesee_out_ht_diam* real dups noee_extension* real no yesee_transition* real no yesee_radius* real no yesweight real no yesmaterial Char( 20) no yesee_const_type integer no noee_xs_cell* Char( 6) no yesee_spec_key* Char( 28) uniq noee_description Char( 40) no yes

vendor: the codelisted column used to define the vendor of the conduit specification.


nominal_size: the column used to define a conduit nominal size.

ee_dimension_1: the column used to define a conduit dimension value to eden and the racewayreports.

ee_out_ht_diam: the column used to define the conduit outside diameter to the EE raceway software.

ee_extension: the column used to define the conduit fitting extension length to the EE racewaysoftware.

ee_transition: the column used to define the conduit fitting transition length to the EE racewaysoftware.

ee_radius: the column used to define the conduit fitting bend radius to the EE raceway software.

weight: the column used to define the conduit weight per unit length.

material: the column used to define the conduit material.

ee_const_type: the column used to define construction type.

460

C: E

E D

atabases

Appendix C: EE Raceway Reference Database Schema Description________________ ee_xs_cell: the column used to define the conduit cross section graphic that is used during sketchpropagation. The only valid entries are: A, B, or C. The associated shapes are shown below.



drawing

This table defines both the columns that you can annotate for title blocks and their default columnvalues.

Column Name Type Index Nulldrawing_type* Char( 20) no nosheet* Char( 20) no yesee_key* Char( 28) uniq noee_description* Char( 40) no yes

drawing_type: the column used to define the EE product drawing type.

sheet: the column used to define the EE drawing sheet name.

ee_key: the unique key to the appropriate reference database record for the default values.

ee_description: the description of the default values for each ee_key.

drawing_type

This codelist table defines what drawing types are available for use. Refer to the section entitledCodelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Nullee_code Char(20) uniq nocode_desc Char(20) no yes

ee_code: the column used by the software to uniquely identify a drawing type description.

code_desc: the column that contains the description of each available drawing type.

461


drop_point

This table defines both the columns you can annotate for drop point symbols and their default columnvalues.

Column Name Type Index Nulltag Char(20) no yesee_dist_down_ol* real no yesee_dist_to_rcp* real no yesee_key* Char(28) unique noee_description* Char(40) no yes

tag: the column used to define the drop point tag.

ee_dist_down_ol: the column used to define the distance along the one-line to the drop point.

ee_dist_to_rcp: the column used to define the distance between the one-line and the rcp.



duct_spec

This table stores the general specification information for the one-line type DUCTBANK.

Column Name Type Index Nullee_units integer no noee_out_ht_diam real dups noee_out_width real dups yesmaterial Char( 20) no yesee_xs_cell Char( 6) no yesee_spec_key Char( 28) uniq noee_description Char( 40) no yes


ee_out_ht_diam: the column used to define the ductbank outside height to the EE Raceway software.

ee_out_width: the column used to define the ductbank outside width to the EE Raceway software.

material: the column used to define the ductbank material.

462

C: E

E D

atabases

Appendix C: EE Raceway Reference Database Schema Description________________ ee_xs_cell: the column used to define the ductbank cross section graphic that is used during sketchpropagation. The only valid entries are: A, B, or C. The associated shapes are shown below.



ee_cond_x_area

This table stores the cross sectional area of conduit identified by its nominal size.

Column Name Type Index Nullnominal_size real uniq noee_dimension_1 real no yesee_area real no yes

nominal_size: the column used to define a conduit nominal size that corresponds to the same columnin the cond_spec table.

ee_dimension_1: the column used to define a conduit dimension value that corresponds to the samecolumn in the cond_spec table.

ee_area: the column used to define the cross sectional area of the conduit of the given nominal size.

ee_graphic_only

EE applications use this table to define which columns in the project database cannot be posted back tographics through the Post Attribute process.

Column Name Type Index Nulltable_name Char( 32) uniq yescolumn_name Char( 32) uniq yes

table_name: the name of the desired table containing a column that cannot be posted.

column_name: the column within table_name that cannot be posted back to the graphics.

463


ee_pcbl_code

This codelist table defines the codes that are used in the ee_pseudo_cable table for the EERWAYConduit Sizing command. Refer to the section entitled Codelists earlier in this appendix for a detaileddescription of this table.

Column Name Type Index Nullindex_column Char( 20) uniq noindex_value Char( 20) dups yes

index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_codedescription.

index_value: the column that contains the description of each available ee_pcbl_code.

ee_pcbl_color

This codelist table defines the colors that are used in the ee_pseudo_cable table for the EE RacewayConduit Sizing command. Refer to the section entitled Codelists earlier in this appendix for a detaileddescription of this table.


index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_colordescription.

index_value: the column that contains the description of each available ee_pcbl_color color.

ee_pcbl_config

This codelist table defines the cable configurations that are used in the ee_pseudo_cable table for theEE Raceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendixfor a detailed description of this table.


index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_configdescription.

index_value: the column that contains the description of each available ee_pcbl_config.

464

C: E

E D

atabases


ee_pcbl_insul

This codelist table defines the insulation types that are used in the ee_pseudo_cable table for the EERaceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix fora detailed description of this table.

Column Name Type Index Nullindex_column Char( 20) uniq noindex_value Char(100) dups yes

index_column: an abbreviated value used by the software to uniquely identify an eepcbl_insuldescription.

index_value: the column that contains the description of each available ee_pcbl_insul.

ee_pcbl_size

This codelist table defines the cable/wire sizes that are used in the ee_pseudo_cable table for the EERaceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix fora detailed description of this table.


index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_sizedescription.

index_value: the column that contains the description of each available ee_pcbl_size.

ee_pcbl_volt

This codelisted table defines the cable/wire voltage ratings that are used in the ee_pseudo_cable tablefor the EE Raceway Conduit Sizing command.


index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_voltdescription.

index_value: the column that contains the description of each available ee_pcbl_volt.

465


ee_pseudo_cable

This table defines the cable/wires that are used in the EE Raceway Conduit Sizing command.

Column Name Type Index Nullee_code Char( 20) no yesconfig Char( 20) no yescable_size Char( 20) no yesee_color Char( 20) no yesvoltage Char( 20) no yesinsulation Char( 20) no yesitem_no Char( 20) uniq yesee_area real no yesee_units integer no no

ee_code: the cable code of the cable.

config: the cable configuration of the cable.

cable_size: the size of the wire/cable.

ee_color: the insulation color of the wire/cable.

voltage: the insulation voltage rating of the wire/cable.

insulation: the insulation type of the wire/cable.

item_no: the unique identifier for each wire/cable.

ee_area: the cross sectional area of the wire/cable.


ee_system

This codelist table defines the systems that are available to contain EE Raceway graphics. Refer to thesection entitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Nullsystem_num integer uniq nosystem_name Char( 20) dups yes

system_num: an integer value used by the software to uniquely identify a system name.

system_name: the column that contains the name of each available system.

466

C: E

E D

atabases


ee_units

This codelist table defines the units that are used for one-line dimension values. Refer to the sectionentitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Nullindex_column* integer uniq noindex_value* Char( 20) dups yes

index_column: an integer value used by the software to uniquely identify an ee_unit description.

index_value: the column that contains the description of each available ee_unit.

ee_unique

EE applications use this table to define which columns make a row in a table unique for single dataentry. If a table is not represented in the ee_unique table, a row will be loaded into the appropriatetable for each graphic element.

Column Name Type Index Nulltable_name Char( 32) uniq yescolumn_name Char( 32) uniq yesee_comp_type* Char( 10) uniq yesblank_allowed integer no yes

table_name: the name of the table that requires single data entry. Multiple rows in the database couldcontain the same table name if multiple columns are required to make an entry unique.

column_name: the name of the column in table_name that makes an entry unique.

ee_comp_type: is used by the EE processors to define what product will use the entry. In someentries, where the information crosses products, this column is used to further describe what wouldmake an entry unique.

blank_allowed: is used to define whether or not the column in column_name is allowed to be blank.If not, then a blank column value would cause the EE processes to create a new row in the database.

ee_yes_no

This codelist table defines the possible column values for a ’yes/no’ question in a table column. Referto the section entitled Codelists earlier in this appendix for a detailed description of this table.

Column Name Type Index Nullindex_column* integer uniq yesindex_value* Char( 20) dups yes

index_column: an integer value used by the software to uniquely identify the ’yes/no’ response.

467

EE Raceway Modeling Reference Guide - February 2003________________ index_value: the column that contains the ’yes/no’ column value.

envelope

This table defines both the columns you can annotate for space envelopes and their default columnvalues. EE Raceway uses space envelopes to reserve blocks of space for raceway without maintainingconnectivity to any raceway system.

Column Name Type Index Nulltag Char( 20) no yesee_key* Char( 28) uniq noee_description* Char( 40) no yes

tag: the column used to define the space envelope tag.



Space envelopes are not available with EE Raceway at the time of this printing.

468

C: E

E D

atabases


light_fixture

This table stores the specification information for the manually placed equipment LIGHT_FIXTURE.

Column Name Type Index Nullee_symbol Char( 6) no yesvoltage integer no yesee_dimension_1 real no yesee_dimension_2 real no yesee_dimension_3 real no yesee_part_key Char( 28) uniq nofl_amps real no yesee_dimension_4 real no yesee_dimension_5 real no yesee_dimension_6 real no yesee_description Char( 40) no yesitem_type Char( 3) no yesee_dimension_7 real no yesee_dimension_8 real no yesee_dimension_9 real no yesitem_code_num Char( 20) no yesvendor integer dups nonum_wires Char( 4) no yesnum_phase_wires integer no yespower_factor real no yesarea_class Char( 6) no yesoper_temp_deg_c integer no yestext_1 Char( 32) no yestext_2 Char( 32) no yestext_3 Char( 32) no yestext_4 Char( 32) no yesee_units integer no noee_pull_point integer no yes

ee_symbol: the column used to define the light fixture EDEN symbol name to the EE software.

voltage: the column used to define the light fixture’s voltage.

ee_dimension_1: the column used to define a light fixture dimension value to EDEN and the racewayreports.



ee_part_key: the unique key to appropriate reference database record for the default values.

469

EE Raceway Modeling Reference Guide - February 2003________________ fl_amps: the column used to define a light fixture’s full load amps.




ee_description: the description of the default values for each ee_part_key

item_type: the column used to define a light fixture’s item type.




item_code_num: the column used to define a light fixture’s item code number.

vendor: the codelisted column used to define the vendor of the equipment light fixture.

num_wires: the column used to define the number of wires in a light fixture.

num_phase_wires: the column used to define the number of phase wires in a light fixture.

power_factor: the column used to define a light fixture’s power factor.

area_class: the column used to define a light fixture’s area class.

oper_temp_deg_c: the column used to define a light fixture’s operating temperature.

text_1: the column used to describe characteristics about the light fixture.





ee_pull_point: the codelisted column used to define a light fixture as a cable pull point.

470

C: E

E D

atabases


manual_part

This codelist table defines the available manually-placed special fittings (conduit body, pullbox).Refer to the section entitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Nullindex_column* integer uniq noindex_value* Char( 20) dups yesee_part_table* integer no yesee_rcp_ol_type* integer no yesee_manpart_type integer no yes

index_column: an integer value used by the software to uniquely identify a manual_part description.

index_value: the column that contains the description of each available manual_part.

ee_part_table: an mscatalog number of the table containing special fitting part specificationinformation.

ee_rcp_ol_type: the index_column number from the one-line type codelist table for the EE racewayconnect point of the special fitting.

ee_manpart_type: the column used to tell the load processor to load the manual part into either theproject database "fitting" table or the "panel" table.

mscatalog

Microstation 32 requires that every database used in graphics contain a table called mscatalog. Thistable holds the entity numbers for all other tables in the database. In general, there will be one row inmscatalog for each database table that is linked to graphic elements. Any table not directly linked tographics/EE elements does not need to appear in mscatalog. Both DBAccess and RISRPT (RIS ReportWriter) use this table.

Column Name Type Index Nulltablename Char( 32) no noentitynum integer uniq noscreenform Char( 64) no yesreporttable Char( 64) no yessqlreview Char(240) no yesfencefilter Char(240) no yesdastable Char(32) no yesalias_name Char( 64) no yeskey_columns Char( 80) no yeskey_description Char( 32) no yes

tablename: the name of the table in the database. It must exactly match the name of the desired table.

471

EE Raceway Modeling Reference Guide - February 2003________________ entitynum: the entity number assigned to a table. It must be a positive integer in the range of 1 to65535. The entity number uniquely identifies a particular table in the database. The MicroStation 32database interface places the entity number of a table in the linkage it creates between a graphicselement and a table row. EE places the entity number in the EE header linkage of annotation in orderto identify which table the text is linked to.

screenform: not currently used by MicroStation 32.

reporttable: a temporary table used by MicroStation 32. Is is created for each table having graphiclinkages within a fence.

sqlreview: an sql select statement that MicroStation 32 uses to review rows and columns.

fencefilter: an sql select statement that MicroStation 32 uses to restrict elements during fenceoperations.

dastable: specifies the name of the table that maps displayable attribute types to the sql selectstatements used by MicroStation 32 for loading text into displayable attributes.

alias_name: a column used by EE that contains the descriptive alias of tablename.

key_columns: a column containing the column_name which uniquely identifies a particular row in thetable. EE uses key_columns as the correlation key.

key_description: the descriptive alias for key_columns.

mscodelist

This table provides limited support for DMRS-like codelists. A codelist is a data structure thatrepresents a character string which is then represented in the database by integer or character codes.The codelist approach minimizes storage requirements and simplifies database administration.

MicroStation 32, RISRPT, and DBAccess all support this table. EE uses this table to restrict input fora particular column to a pre-defined set of values.

Column Name Type Index Nulltable_name Char( 32) uniq nocolumn_name Char( 32) uniq nojoin_table Char( 32) no nocode_column Char( 32) no notext_column Char( 32) no noindex_column* Char( 32) no yesindex_value* integer no yes

table_name: the name of the desired table containing a column with codelist values.

column_name: the column within table_name which contains codelist values.

472

C: E

E D

atabases

Appendix C: EE Raceway Reference Database Schema Description________________ join_table: the codelist table.

code_column: the column in join_table that contains the code values.

text_column: the column that contains the actual values represented by the corresponding code valuein code_column.

index_column: a column name that, if not NULL, will impose additional conditions to allow multiplecodelists to be represented in the same database table.

index_value: the column that provides the index to a specific list within a multiple codelist table.

mscolumns

This table specifies column-specific data for EE tables. In general, there is one row in mscolumns foreach column in an attribute table (for those attributes that exist in annotation). EE uses the mscolumnsinformation to control display of column information during annotation. A column that does not existas annotation linked to a graphics/EE element does not need to appear in mscolumns. The order inwhich attributes appear on the annotation form is determined by the value in the columnee_column_order.

Column Name Type Index Nullentitynum integer uniq noattrnum integer uniq nocolumn_name Char( 32) no noalias_name Char( 32) no yesaccess_flag smallint no nowork_mode smallint no noee_column_order smallint no no

entitynum: the entity number assigned to the table whose columns are being described. Entitynumbers between mscatalog and mscolumns must be consistent.

attrnum: the attribute number assigned to a particular column within a table.

column_name: the name of a column in the database. It must exactly match the column name in thedatabase.

alias_name: the column containing the descriptive alias of column_name.

access_flag: the column containing a code used to identify the accessibility of a particular column byan EE user. A value of 0 indicates that the column is read_only, while a value of 1 indicates that itallows read/write access.

work_mode: the column containing the code that identifies the use of a particular column by the EEsoftware. This column can be thought of as a filter which restricts the display of certain attributesdepending on the mode of work the user is performing. Since all EE Raceway column values aredisplayed on the primary form, the work_mode value is set to zero.

473

EE Raceway Modeling Reference Guide - February 2003________________ ee_column_order: the column used to determine the order in which to display attributes on theannotation form.

ol_type

This codelist table defines the available one-line types (tray, wireway, conduit, and so forth). Refer tothe section entitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Nullindex_column* integer uniq noindex_value* Char( 20) dups yesee_spec_table* integer no yesee_part_table* integer no yesee_ol_table* integer no yesee_rcp_part_table* integer no yesee_max_run_angle* integer no yesee_priority_level* integer no yes

index_column: an integer value used by the software to uniquely identify an ol_type description.

index_value: the column that contains the description of each available ol_type.

ee_spec_table: an mscatalog number of the table containing general specification information.

ee_part_table: an mscatalog number of the table containing the part specification information.

ee_ol_table: an mscatalog number of the table containing general one-line information.

ee_rcp_part_table: an mscatalog number of the table containing special fitting part specificationinformation.

ee_max_run_angle: an integer containing the maximum allowed value of the sum of all bend anglesin a run. A value of zero states that the sum of all bend angles in a run is unlimited.

ee_priority_level: an integer value used to define the routing priority level of the one-line type. Thisvalue is used to determine whether one one-line type can break or attach to another one-line type.

474

C: E

E D

atabases


one_line

This table defines both the columns you can annotate for raceway one-lines and their default columnvalues.

Column Name Type Index Nulltag Char( 20) no yesadd_weight real no yesee_ol_length* real no yesee_spec_key* Char( 28) no noee_key* Char( 28) uniq noee_description* Char( 40) no yes

tag: the column used to define the one-line tag.

add_weight: the column used to define an additional weight per unit length.

ee_ol_length: the column used to define the weight per unit length.

ee_spec_key: the key to the appropriate reference database record for the general specificationinformation on the three-line elements.



panel

This table defines both the columns you can annotate for panels/equipment and their default columnvalues.

Column Name Type Index Nullpanel Char( 20) no yespanel_descrip Char( 20) no yesee_approv_status integer no yesee_approv_date Char( 40) no yesee_create_date Char( 40) no yesee_last_rev_dat Char( 40) no yesee_key Char( 28) uniq noee_description Char( 40) no yes

panel: the column which defines the panel/equipment name.

panel_descrip: the column which defines the panel/equipment description.

ee_approv_status: the codelisted column used to define the approval status.

475

EE Raceway Modeling Reference Guide - February 2003________________ ee_approv_date: the column used to define the date the approval status was changed.

ee_create_date: the column used to define the date the panel/equipment was created.

ee_last_rev_dat: the column used to define the date the panel/equipment was last revised.


ee_description: the description of the default values for each ee_key

project

This table stores information for the project.

Column Name Type Index Nullprj_number char(20) dups yesprj_name char(60) no yeslocation char(60) no yesprj_rule_set char(20) no yesbase_rule_set char(20) no yesee_key char(28) uniq noee_description char(60) no yes

prj_number: this column contains the project number.

prj_name: this column contains the project name.

location: this column contains the location.

prj_rule_set: this column contains the project rule set.

base_rule_set: this column contains the base rule set.

ee_key: this column contains the EE Reference database key.

ee_description:this column contains the key description.

476

C: E

E D

atabases


pullbox

This table stores the specification information for the manual fitting PULLBOX.

Column Name Type Index Nullvendor integer dups noee_units* integer no noee_out_ht_diam* real dups noee_out_width* real dups yesee_dimension_1 real dups yesweight real no yesmaterial char(20) no yesee_part* char(20) no yesee_symbol* char(6) no yesee_part_key* char(28) uniq noee_description char(40) no yesee_tl_type integer no noee_pull_point integer no yes

vendor: the codelisted column used to define the pullbox vendor.

ee_units: the codelisted column used to define the untis of measurement.

ee_out_ht_diam: the column used to define the pullbox outside height to the EERWAY software.

ee_out_width: the column used to define the pullbox outside width to the EERWAY software .

ee_dimension_1: the column used to define the pullbox dimension value to Eden and the racewayreports.

weight: the column used to define the pullbox weight.

material: the column used to define the pullbox weight material.

ee_part: the column used to define the pullbox part number.

ee_symbol: the column used to define the pullbox part Eden symbol name to the EE software.




ee_pull_point: the codelisted column used to define a pullbox as a cable pull point.

477


rcp

This table defines both the columns you can annotate for raceway connect points (RCPs) and theirdefault column values.

Column Name Type Index Nulltag Char( 20) no yesee_rcp_type* integer no yesee_extension* real no yesee_transition* real no yesee_radius* real no yesee_part_key* Char( 28) no yesee_key* Char( 28) uniq noee_description* Char( 40) no yes

tag: the column used to define the raceway connect point tag.

ee_rcp_type: the codelisted column used to define the raceway connect point type.

ee_extension: the column used to define the raceway connect point fitting extension length.

ee_transition: the column used to define the raceway connect point fitting transition length.

ee_radius: the column used to define the raceway connect point fitting bend radius.

ee_part_key: the key to the appropriate reference database record for the values on the manuallyplaced fitting.



rcp_type

This codelist table defines additional information about EE Raceway connect points (RCPs). Refer tothe section entitled Codelists earlier in the appendix for a detailed description of this table.


index_column: an integer value used by the software to uniquely identify a rcp_type description.

index_value: the column that contains the description of each available rcp_type.

478

C: E

E D

atabases


tl_fit_env

This table is used by the manual fitting command to determine which fitting to place at an RCP basedon the intersecting one-lines and the fitting environment rules listed in this table.

Column Name Type Index Nullee_ol_type integer uniq noee_tl_type integer no noee_tl_subtype integer no noee_tl_qual integer no noee_num_ols integer uniq yesee_pln_angles Char( 40) uniq yesee_prp_angles Char( 40) uniq yesee_part_table integer no yesee_symbol Char( 6) dups yes

ee_ol_type: the index_column number from the one-line type codelist table of the intersecting one-lines.

ee_tl_type: the index_column number from the three_line type codelist table of the fitting to be placedat the RCP. Zero if no check is to be performed.

ee_tl_subtype: the index_column number from the three_line subtype codelist table of the fitting to beplaced at the RCP. Zero if no check is to be performed.

ee_tl_qual: the index_column number from the three_line qualifier codelist table of the fitting to beplaced at the RCP. Zero if no check is to be performed.

ee_num_ols: the column that contains the number of intersecting one-lines.

ee_pln_angles: the column that contains the planar angles between the intersecting one-lines. Anglesmust be defined relative from a single one-line.

ee_prp_angles: the column that contains the non-planar angles between the intersecting one-lines.Angles must be defined relative from a single one-line.

ee_part_table: an mscatalog number of the table containing the fitting to be placed at the RCP.

ee_symbol: the column used to define the fitting EDEN symbol name to the EE software.

479


tl_qual

This codelist table defines additional information about the available three-line types (rigid, bendable,flexible, and so forth). Refer to the section entitled Codelists earlier in the appendix for a detaileddescription of this table.


index_column: an integer value used by the software to uniquely identify a tl_qual description.

index_value: the column that contains the description of each available tl_qual.

tl_subtype

This codelist table defines the available three-line subtypes (vertical, horizontal, reducer, and so forth).Refer to the section entitled Codelists earlier in the appendix for a detailed description of this table.


index_column: an integer value used by the software to uniquely identify a tl_subtype description.

index_value: the column that contains the description of each available tl_subtype.

tl_type

This codelist table defines the available three-line types (straight, elbow, wye, cross, and so forth).Refer to the section entitled Codelists earlier in the appendix for a detailed description of this table.


index_column: an integer value used by the software to uniquely identify a tl_type description.

index_value: the column that contains the description of each available tl_type.

480

C: E

E D

atabases


to_equip

This table defines both the columns that you can annotate for equipment pointer symbols and theirdefault column values.

Column Name Type Index Nullee_eqp_table Char( 32) no yesee_part_key Char( 28) no yesee_eqp_key* Char( 28) uniq noee_description* Char( 40) no yes

ee_eqp_table: the name of the reference database table containing the equipment specificationinformation.

ee_part_key: the key to the appropriate reference database record for the values on the equipment.

ee_eqp_key: the unique key to the appropriate reference database record for the default values.


to_support

This table defines both the columns you can annotate for support equipment symbols and their defaultcolumn values.

Column Name Type Index Nulltag Char( 20) no yesee_key* Char( 28) uniq noee_description* Char( 40) no yes

tag: the column used to define the support pointer tag.



to_support symbols are not available with EE Raceway at the time of this printing.

481


tray_part

This table stores the part specification information for the one-line type TRAY.

Column Name Type Index Nullee_tl_type* integer no noee_tl_subtype* integer no noee_tl_qual* integer no noee_angle* real no yesee_weight* real no yesee_part* Char( 20) no yesee_symbol* Char( 6) no yesee_spec_key* Char( 28) dups yesee_spec2_key* Char( 28) no yesee_part_key* Char( 28) uniq noee_description* Char( 40) no yes




ee_angle: the column used to define the tray fitting bend angle.

ee_weight: the column used to define the tray part weight.

ee_part: the column used to define the tray part number.

ee_symbol: the column used to define the tray part EDEN symbol name to the EE software.

ee_spec_key: the key to the appropriate tray specification table row containing general specificationinformation.

ee_spec2_key: if the current tray part is a reducer, this column is the key to the row in the other trayspecification.



482

C: E

E D

atabases


tray_spec

This table stores the general specification information for the one-line type TRAY.

Column Name Type Index Nullvendor integer dups noee_units* integer no noee_dimension_1* real no yesee_out_ht_diam* real dups noee_dimension_2* real no yesee_out_width* real dups yesee_extension* real no yesee_transition* real no yesee_radius* real no yesweight real no yesmaterial Char( 20) no yesee_const_type integer no noee_xs_cell* Char( 6) no yesee_spec_key* Char( 28) uniq noee_description Char( 40) no yes

vendor: the codelisted column used to define the vendor of the tray specification.


ee_dimension_1: the column used to define a tray dimension value to eden and the raceway reports.

ee_out_ht_diam: the column used to define the tray outside height to the EE raceway software.

ee_dimension_2: the column used to define a tray dimension value to eden and the raceway reports.

ee_out_width: the column used to define the tray outside width to the EE raceway software.

ee_extension: the column used to define the tray fitting extension length to the EE raceway software.

ee_transition: the column used to define the tray fitting transition length to the EE raceway software.

ee_radius: the column used to define the tray fitting bend radius to the EE raceway software.

weight: the column used to define the tray weight per unit length.

material: the column used to define the tray material.


483

EE Raceway Modeling Reference Guide - February 2003________________ ee_xs_cell: the column used to define the tray cross section graphic that is used during sketchpropagation. The only valid entries are: A, B, or C. The associated shapes are shown below.



vendor

This codelist table defines the vendors that are available for specifications. Refer to the section entitledCodelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Nullindex_column* integer uniq noindex_value* Char( 20) dups yescatalog char(20) no yea

index_column: an integer value used by the software to uniquely identify a vendor name.

index_value: the column that contains the name of each available vendor.

catalog: the column that contains catalog information.

wway_part

This table stores the part specification information for the one-line type WIREWAY.

Column Name Type Index Nullee_tl_type* integer no yesee_tl_subtype* integer no yesee_tl_qual* integer no yesee_angle* real no yesee_weight* real no yesee_part* Char( 20) no yesee_symbol* Char( 6) no yesee_spec_key* Char( 28) dups yesee_spec2_key* Char( 28) no yesee_part_key* Char( 28) uniq noee_description* Char( 40) no yes


484

C: E

E D

atabases

Appendix C: EE Raceway Reference Database Schema Description________________ ee_tl_subtype: the codelisted column used to define the three-line subtype.


ee_angle: the column used to define the wireway fitting bend angle.

ee_weight: the column used to define the wireway part weight.

ee_part: the column used to define the wireway part number.

ee_symbol: the column used to define the wireway part EDEN symbol name to the EE software.

ee_spec_key: the key to the appropriate wireway specification table row containing generalspecification information.

ee_spec2_key: if the current wireway part is a reducer, this column is the key to the row in the otherwireway specification.



wway_spec

This table stores the general specification information for the one-line type WIREWAY.

Column Name Type Index Nullvendor integer dups noee_units* integer no noee_dimension_1* real no yesee_out_ht_diam* real dups noee_dimension_2* real no yesee_out_width* real dups yesee_extension* real no yesee_transition* real no yesee_radius* real no yesweight real no yesmaterial Char( 20) no yesee_const_type integer no noee_xs_cell* Char( 6) no yesee_spec_key* Char( 28) uniq noee_description Char( 40) no yes

vendor: the codelisted column used to define the vendor of the wireway specification.


ee_dimension_1: the column used to define a wireway dimension value to eden and the racewayreports.

485

EE Raceway Modeling Reference Guide - February 2003________________ ee_out_ht_diam: the column used to define the wireway outside height to the EE raceway software.

ee_dimension_2: the column used to define a wireway dimension value to eden and the racewayreports.

ee_out_width: the column used to define the wireway outside width to the EE raceway software.

ee_extension: the column used to define the wireway fitting extension length to the EE racewaysoftware.

ee_transition: the column used to define the wireway fitting transition length to the EE racewaysoftware.

ee_radius: the column used to define the wireway fitting bend radius to the EE raceway software.

weight: the column used to define the wireway weight per unit length.

material: the column used to define the wireway material.


ee_xs_cell: the column used to define the wireway cross section graphic that is used during sketchpropagation. The only valid entries are: A, B, or C. The associated shapes are shown below.



486

C: E

E D

atabases

Appendix C: EE Raceway Project Database Schema Description________________

EE Raceway Project Database SchemaDescription

This section lists and describes the tables in the EE Raceway project database schema, and includes detailedinformation about the columns that comprise each table.

An asterisk (*) indicates that you must not modify the column name. You should not modifythose column names having a prefix of "ee_".

cabsch_spec

This table contains information about the cable schedule for underground cable design.

Column Name Type Index Nullrevision_numb Char( 3) no yescable_numb Char( 8) uniq yesnumb_cables integer no yesnumb_conductor Char( 5) no yesconductor_size Char( 8) no yescable_type_code Char( 6) no yesservice_voltage Char( 7) no yesundgrnd_length real no yesabvgrnd_length real no yesfrom_equi_numb Char( 15) no yesfrom_detail Char( 8) no yesnot_used Char( 6) no yesplan_assem_dwg Char( 20) no yesto_equi_numb Char( 15) no yesto_detail Char( 8) no yesto_plan_drw_num Char( 20) no yescont_sta_type Char( 4) no yesquan_term_kits Char( 6) no yesol_diagram_numb Char( 20) no yesnot_used2 Char( 8) no yesremarks Char( 38) no yesdrawing_numb Char( 20) uniq yesdrawing_rev Char( 2) no yes

revision_numb: the column containing the revision number.

cable_numb: the column containing the area number, cable number, and cable number ID.

numb_cables: the column containing the number of cables.

numb_conductor: the column containing the number of conductors.

487

EE Raceway Modeling Reference Guide - February 2003________________ conductor_size: the column containing the conductor size.

cable_type_code: the column containing the cable type.

service_voltage: the column containing the service voltage.

undgrnd_length: the column containing the underground length.

abvgrnd_length: the column containing the above ground length.

from_equi_numb: the column containing the From Equipment Number.

from_detail: the column containing the From Detail Number.

not_used: this column is reserved for later use.

plan_assem_dwg: the column containing plan drawings or standard assembly drawing number.

to_equi_numb: the column containing the To Equipment Number.

to_detail: the column containing the To Detail Number.

to_plan_drw_num: the column containing the To Plan drawing number.

cont_sta_type: the column containing the control station type.

quan_term_kits: the column containing the quantity of term.

ol_diagram_numb: the column containing the one-line diagram number.

not_used2: this column is reserved for later use.

remarks: the column containing the remarks for cable schedule.

drawing_numb: the column containing the drawing number.

drawing_rev: the column containing the drawing revision.

drawing_numb can have duplicate values but the combination of drawing_numb andcable_numb should be unique.

488

C: E

E D

atabases


cndsch_spec

This table contains information about conduit schedule for underground conduit design.

Column Name Type Index Nullrevision_numb Char( 2) no yesconduit_numb Char( 10) uniq yesconduit_for Char( 12) no yescnd_from_where Char( 20) no yescnd_to_where Char( 20) no yesundgrnd_cnd_size Char( 6) no yesundgrnd_cnd_type Char( 5) no yesundgrnd_cnd_length real no yesabvgrnd_cnd_size Char( 6) no yesabvgrnd_cnd_type Char( 4) no yesabvgrnd_cnd_length real no yescnd_detail_numb Char( 7) no yesdetail_drw_numb Char( 12) no yescnd_ac_dimension Char( 12) no yescnd_station Char( 6) no yespow_conduct_volt Char( 5) no yespow_conduct_numb integer no yespow_conduct_size Char( 7) no yespow_conduct_type Char( 4) no yespow_conduct_length real no yescon_conduct_numb integer no yescon_conduct_size Char( 7) no yescon_conduct_type Char( 4) no yescon_conduct_length real no yesgrnd_wire_size Char( 6) no yesgrnd_wire_type Char( 4) no yesgrnd_wire_length real no yesol_diagram_numb Char( 10) no yesremarks Char( 16) no yesdrawing_numb Char( 20) uniq yesdrawing_rev Char( 2) no yes

revision_numb: the column containing the conduit schedule revision number.

conduit_numb: the column containing the area number, conduit number, and conduit number ID.

drawing_numb can have duplicate values, but the combination of drawing_numb andconduit_numb should be unique.

conduit_for: the column defines the purpose of the conduit, for example power, control, and so forth.

cnd_from_where: the column containing the location name where the conduit starts from.

cnd_to_where: the column containing the location name where the conduit goes to.

489

EE Raceway Modeling Reference Guide - February 2003________________ undgrnd_cnd_siz: the column containing the underground conduit size.

undgrnd_cnd_typ: the column containing the underground conduit type.

undgrnd_cnd_len: the column containing the length of the underground conduit.

abvgrnd_cnd_siz: the column containing the above ground conduit size.

abvgrnd_cnd_typ: the column containing the above ground conduit type.

abvgrnd_cnd_len: the column containing the length of the above ground conduit.

cnd_detail_numb: the column containing the conduit detail number.

detail_drw_numb: the column containing the detail drawing number.

cnd_ac_dimensio: the column containing the data for AC DIM.

cnd_station: the column containing the information for control station.

pow_conduct_vol: the column containing the power conductor voltage.

pow_conduct_num: the column containing the power conductor number.

pow_conduct_siz: the column containing the power conductor size.

pow_conduct_typ: the column containing the power conductor type code.

pow_conduct_len: the column containing the power conductor length.

con_conduct_num: the column containing the control conductor number.

con_conduct_siz: the column containing the control conductor size.

con_conduct_typ: the column containing the control conductor type code.

con_conduct_len: the column containing the control conductor length.

grnd_wire_size: the column containing the ground wire size.

grnd_wire_type: the column containing the ground wire type code.

grnd_wire_lengt: the column containing the ground wire length.

ol_diagram_numb: the column containing the one-line diagram number.

remarks: the column containing remarks for the conduit schedule.

drawing_numb: the column containing the drawing number.

490

C: E

E D

atabases

Appendix C: EE Raceway Project Database Schema Description________________ drawing_rev: the column containing the drawing revision.

drawing

This table, used by all EE products, contains general information about each EE design file.

Column Name Type Index Null

mslink* integer uniq nodrawing_type* Char( 20) no noee_filename* Char( 80) no nosheet* Char( 20) uniq noload_date* Char( 26) no noref_db* Char( 80) no no

mslink: a unique integer value used by the software to identify a row in the drawing table.

drawing_type: the column used to define the type of EE drawing.

ee_filename: the column containing the drawing file name and path.

sheet: the column used to contain the drawing sheet name.

load_date: the column containing the date that the load processor loaded the drawing into the projectdatabase.

ref_db: the column containing the schema name of the EE reference database.

drop_point

This table associates a row in the rcp table with a row in the one-line table.


mslink* integer uniq noee_to_drw* integer no noee_to_ol* integer dups yesee_to_rcp* integer dups yesee_dist_down_ol* real no yesee_dist_to_rcp* real no yestag Char( 20) no yes

mslink: a unique integer value used by the software to identify a row in the drop_point table.

ee_to_drw: the column containing the mslink of a row in the drawing table.

ee_to_ol: the column containing the mslink of a row in the one_line table.

491

EE Raceway Modeling Reference Guide - February 2003________________ ee_to_rcp: the column containing the mslink of a row in the rcp table.

ee_dist_down_ol: the column containing the distance along the one-line to the drop point.

ee_dist_to_rcp: the column containing the distance between the one-line and the rcp.

tag: the column that contains the name of the drop point.

duct_fill

This table defines the cable/conduit that are placed in a duct one-line.

Column Name Type Index Nullee_to_ol integer dups yesee_to_drw integer dups yesee_duct_cc_row integer no yesee_duct_cc_col integer no yesee_duct_cc_numb Char( 12) no yesee_drawing_numb Char( 20) no yes

ee_to_ol: the column containing the mslink of a row in the one-line table.


ee_duct_cc_row: the row index of the conduit/cable.

ee_duct_cc_col: the column index of the conduit/cable.

ee_duct_cc_numb: cable/conduit area number, cable number, and cable number number ID.

ee_drawing_numb: detail drawing number of the conduit/cable schedule.

ee_pseudo_cable

This table defines the wires/cables that fill conduit. This is performed with the EE Raceway ConduitSizing command.

Column Name Type Index Nullmslink integer uniq noee_to_ol integer no noee_to_drw integer no noee_quantity integer no yesitem_no Char( 20) dups yes

mslink: a unique integer value used by the software to identify a row in the ee_pseudo_cable table.


492

C: E

E D

atabases

Appendix C: EE Raceway Project Database Schema Description________________ ee_to_drw: the column containing the mslink of a row in the drawing table.

ee_quantity: the number of wires/cables associated with the given one-line of a given item_no.

item_no: the column containing the unique key to the ee_pseudo_cable table of the reference schema.

ee_system

This table contains the names of all systems from every EE Raceway drawing loaded into the projectdatabase.


mslink* integer uniq nosystem_name Char( 20) dups yes

mslink: a unique integer value used by the software to identify a row in the ee_system table.

system_name: the column that contains the names of the systems.

envelope

This table contains information about the raceway envelopes found in the drawing.


mslink* integer uniq noee_to_drw* integer no notag Char( 20) dups yes

mslink: a unique integer value used by the software to identify a row in the envelope table.


tag: the column that contains the envelope tag.

Space envelopes are not available at time of printing.

493


fitting

This table contains information about the raceway fittings found in the drawing.


mslink* integer uniq noee_to_drw* integer no noee_to_ol* integer dups yesee_to_rcp* integer dups yesee_out_ht_diam* real no yesee_out_width* real no yesee_out_width2 real no yesee_dimension_1* real no yesee_angle* real no yesee_weight* real no yescab_weight real no yespds_east* real no yespds_north* real no yespds_elev* real no yesvendor Char( 20) no yesee_units* Char( 20) no yesee_tl_type* Char( 20) no yesee_tl_subtype* Char( 20) no yesee_tl_qual* Char( 20) no yesee_ol_type* Char( 20) no yesee_part* Char( 20) dups yesee_description Char( 40) no yes

mslink: a unique integer value used by the software to identify a row in the fitting table.



ee_to_rcp: the column containing the mslink of a row in the rcp table.

ee_out_ht_diam: the column containing the outside height or diameter of the fitting.

ee_out_width: the column containing the outside width of the fitting.

ee_out_width2: the column containing the outside width of the reducer.

ee_dimension_1: the column containing a dimension of the fitting.

ee_angle: the column containing the fitting bend angle.

ee_weight: the column containing the fitting weight per unit length.

494

C: E

E D

atabases

Appendix C: EE Raceway Project Database Schema Description________________ cab_weight: the column containing the cable weight per unit length.

pds_east: the column containing the PDS east coordinate of the fitting (calculated by Load Database).

pds_north: the column containing the PDS north coordinate of the fitting (calculated by LoadDatabase).

pds_elev: the column containing the PDS elevation coordinate of the fitting (calculated by LoadDatabase).

vendor: the column containing the codelist value of the vendor of the one-line type specification.

ee_units: the column containing the codelist value of the design file units.

ee_tl_type: the column containing the codelist value of the three-line type.

ee_tl_subtype: the column containing the codelist value of the three-line subtype.

ee_tl_qual: the column containing the codelist value of the three-line qualifier.

ee_ol_type: the column containing the codelist value of the one-line type.

ee_part: the column containing the straight section part number.

ee_description: the column containing the fitting part description.

fit_to_sys

This table links a fitting to each system of which it is a member.


ee_to_fit* integer dups noee_to_sys* integer dups noee_percent* real no yes

ee_to_fit: the column containing the mslink of a row in the fitting table.

ee_to_sys: the column containing the mslink of a row in the ee_system table.

ee_percent: the column containing the percent amount of the fitting is contained in the systemidentified by the mslink stored in ee_to_sys.

495


mscatalog

This table contains the entity (table) numbers for all the tables in the EE Raceway project database.There will be one row in the mscatalog for each database table.


tablename Char( 32) no noentitynum integer uniq noscreenform Char( 64) no yesreporttable Char( 64) no yessqlreview Char(240) no yesfencefilter Char(240) no yesdastable Char(32) no yesalias_name Char(32) no yeskey_columns Char( 80) no yeskey_description Char( 32) no yes

tablename: the name of the table in the database. It must exactly match the name of the desired table.

entitynum: The entity number assigned to a table. It must be a positive integer in the range of 1 to65535. The entity number uniquely identifies a particular table in the database.

screenform: not currently used by MicroStation 32.

reporttable: a temporary table used by MicroStation 32. Is is created for each table having graphiclinkages within a fence.

sqlreview: an sql select satement that MicroStation 32 uses to review rows and columns.

fencefilter: an sql select statement that MicroStation 32 uses to restrict elements during fenceoperations.

dastable: specifies the name of the table that maps displayable attribute types to the sql selectstatements used by MicroStation 32 for loading text into displayable attributes.

alias_name: a column used by EE that contains the descriptive alias of tablename.

key_columns: a column containing the column_name which uniquely identifies a particular row in thetable. EE uses key_columns as the correlation key.

key_description: the descriptive alias for key_columns.

496

C: E

E D

atabases


mscolumns

This table specifies column-specific data for EE tables. There is one row in mscolumns for eachcolumn in an attribute table. RISRPT and DBAccess use this table for reports. Currently, there are noEE processors using this table.


entitynum uniq uniq noattrnum integer uniq nocolumn_name Char( 32) no noalias_name Char( 64) no yesaccess_flag smallint no nowork_mode smallint no noee_column_order* smallint no no

entitynum: the entity number assigned to the table whose columns are being described. Entitynumbers between mscatalog and mscolumns must be consistent.

attrnum: the attribute number assigned to a particular column within a table.

column_name: the name of a column in the database. It must exactly match the column name in thedatabase.

alias_name: the column containing the descriptive alias of column_name.

access_flag: the column containing a code used to identify the accessibility of a particular column byan EE user. A value of 0 indicates that the column is read_only, while a value of 1 indicates that itallows read/write access.

work_mode: the column containing the code that identifies the use of a particular column by an EEuser. This column can also be thought of as a filter. Display of certain attributes can be restricteddepending on the mode of work the user is performing. Since all EE Raceway column values aredisplayed on the primary form, the work_mode value is set to zero.

ee_column_order: the column used to determine the order to display the attributes on the annotationform.

497


ol_to_sys

This table links a one-line to each system of which it is a member.


ee_to_ol* integer dups noee_to_sys* integer dups noee_percent* real no yesprj_rule_applied integer no yes



ee_percent: the column containing the percent amount of the straight section is contained in thesystem identified by the mslink stored in ee_to_sys.

prj_rule_applied: the column containing the applied project rule.

one_line

This table contains information about the raceway one-lines found in the drawing.


mslink* integer uniq noee_to_drw* integer no noee_to_rcp1* integer dups noee_to_rcp2* integer dups noee_out_ht_diam* real no yesee_out_width* real no yesee_dimension_1* real no yesee_dimension_2* real no yesee_ol_length* real no yesweight real no yescab_weight real no yesvendor Char( 20) dups yesee_units* Char( 20) no yesee_ol_type* Char( 20) no yesee_spec_key* Char( 28) dups yestag Char( 20) dups yesee_radius real no yesee_const_type char no yes

mslink: a unique integer value used by the software to identify a row in the one_line table.

498

C: E

E D

atabases

Appendix C: EE Raceway Project Database Schema Description________________ ee_to_drw: the column containing the mslink of a row in the drawing table.

ee_to_rcp1: the column containing the mslink of the rcp placed at the start of the one-line in the designfile.

ee_to_rcp2: the column containing the mslink of the rcp placed at the end of the one-line in the designfile.

ee_out_ht_diam: the column containing the outside height or diameter of the one-line type.

ee_out_width: the column containing the outside width of the one-line type.

ee_dimension_1: the column containing a dimension of the one-line type.

ee_dimension_2: the column containing a dimension of the one-line type.

ee_ol_length: the column containing the run length of the one-line.

weight: the column containing the one-line type weight per unit length.

cab_weight: the column containing the cable weight per unit length.




ee_spec_key: the column containing the unique key to the one-line type specification table.

tag: the column that contains the name of the one-line.

ee_radius: the column that contains the fitting bend radius of the three-line type specification.

ee_const_type: the column that contains the construction type.

499


panel

This table contains information about all panels/equipment found in the drawing.

Column Name Type Index Nullmslink integer uniq nopanel Char( 20) dups yespanel_descrip Char( 20) no yesee_approv_status integer no yesee_approv_date Char( 26) no yesee_create_date Char( 26) no yesee_last_rev_dat Char( 26) no yesee_eqp_table Char( 32) no yesee_part_key Char( 28) no yes

mslink: a unique integer value used by the software to identify a row in the panel table.

panel: the column containing the panel/equipment name

panel_descrip: the column containing the panel/equipment description.

ee_approv_status: the column containing the approval status of the panel/equipment.

ee_approv_date: the column containing the date when the approval status changed.

ee_create_date: the column containing the panel/equipment creation date.

ee_last_rev_dat: the column containing the date the panel/equipment was last revised.

ee_eqp_table: the column containing the name of the reference database table that contains additionalequipment information.

ee_part_key: the column containing the unique key to the appropriate record of equipmentinformation in the reference database table.

project

This table contains specification information for the project.

Column Name Type Index Nullmslink integer uniq noprj_number Char( 20) uniq yesprj_name Char( 40) uniq nolocation Char( 60) no noprj_rule_set Char( 20) no nobase_rule_set Char( 20) no yes

500

C: E

E D

atabases

Appendix C: EE Raceway Project Database Schema Description________________ mslink: a unique integer value used by the software to identify a row in the panel table.

prj_number: the column containing the project number

prj_name: the column containing the project name description.

location: the column containing location.

prl_rule_set: the column containing the project rule set.

base_rule_set: column containing the base rule set.

panel_to_drw

This table links a panel/equipment to each drawing in which it exists.

Column Name Type Index Nullee_to_panel integer dups noee_asid integer no noee_to_drw integer dups noee_to_rcp integer dups yesee_status integer no no

ee_to_panel: the column containing the mslink of a row in the panel table.

ee_asid: the column containing the asid number of the panel/equipment element in the design fileidentified by the mslink stored in ee_to_drw.


ee_to_rcp: the column containing the mslink of a row in the RCP table.

ee_status: the column containing the revision status of the panel element in the design file (used bythe Load Database process).

rcp

This table contains information about all raceway connect points (RCPs) found in the drawing.


mslink* integer uniq noee_rcp_type* Char( 10) no yestag Char( 20) no yesee_radius real no no

mslink: a unique integer value used by the software to identify a row in the rcp table.

501

EE Raceway Modeling Reference Guide - February 2003________________ ee_rcp_type: the column containing the codelist value of the type of rcp.

tag: the column that contains the name of the rcp.

ee_radius: the column containing the fitting bend radius.

rcp_to_drw

This table links an rcp to each drawing in which it exists.


ee_to_rcp* integer dups noee_asid* integer no noee_to_drw* integer dups nopds_east* real no yespds_north* real no yespds_elev* real no yes


ee_asid: the column containing the asid number of the rcp element in the drawing identified by themslink stored in ee_to_drw.


pds_east: the column containing the PDS east coordinate of the rcp (calculated by Load Database).

pds_north: the column containing the PDS north coordinate of the rcp (calculated by LoadDatabase).

pds_elev: the column containing the PDS elevation coordinate of the rcp (calculated by LoadDatabase).

rcp_to_sys

This table links an rcp to each system of which it is a member.


ee_to_rcp* integer dups noee_to_sys* integer dups noee_percent* real no yes



502

C: E

E D

atabases

Appendix C: EE Raceway Project Database Schema Description________________ ee_percent: the column containing the percent amount of the fitting is contained in the systemidentified by the mslink stored in ee_to_sys.

straight

This table contains information about the raceway straight sections found in the drawing.


mslink* integer uniq noee_to_drw* integer no noee_to_ol* integer dups noee_out_ht_diam* real no yesee_out_width* real no yesee_tl_length* real no yesee_dimension_1* real no yesee_dimension_2* real no yesee_weight* real no yescab_weight real no yespds_east* real no yespds_north* real no yespds_elev* real no yesvendor Char( 20) dups yesee_units* Char( 20) no yesee_ol_type* Char( 20) no yesee_spec_key* Char( 28) dups yesee_part* Char( 20) no yesmaterial Char( 20) no yesee_description Char( 40) no yes

mslink: a unique integer value used by the software to identify a row in the straight table.



ee_out_ht_diam: the column containing the outside height or diameter of the straight section.

ee_out_width: the column containing the outside width of the straight section.

ee_tl_length: the column containing the length of the straight section.

ee_dimension_1: the column containing a dimension of the straight section.

ee_dimension_2: the column containing a dimension of the straight section.

ee_weight: the column containing the straight section weight per unit length.

503

EE Raceway Modeling Reference Guide - February 2003________________ cab_weight: the column containing the cable weight per unit length.

pds_east: the column containing the PDS east coordinate of the straight section (calculated by LoadDatabase).

pds_north: the column containing the PDS north coordinate of the straight section (calculated byLoad Database).

pds_elev: the column containing the PDS elevation coordinate of the straight section (calculated byLoad Database).




ee_spec_key: the column containing the unique key to the one-line type specification table.

ee_part: the column containing the straight section part number.

material: the column containing the straight section material.

ee_description: the column containing the straight section part description.

str_to_sys

This table links a straight section to each system of which it is a member.


ee_to_str* integer dups noee_to_sys* integer dups noee_percent* real no yes

ee_to_str: the column containing the mslink of a row in the straight table.


ee_percent: the column containing the percent amount of the straight section is contained in thesystem identified by the mslink stored in ee_to_sys.

504

C: E

E D

atabases


sys_to_drw

This table links a system name to each drawing in which the system exists.


ee_to_sys* integer dups noee_asid* integer no noee_to_drw* integer dups no


ee_asid: the column containing the asid number of the system element in the drawing identified by themslink stored in ee_to_drw.


to_support

This table links the raceway one-line with a support.


mslink* integer uniq noee_to_drw* integer no noee_to_ol* integer no noee_ol_coord* real no yestag Char( 20) dups yes

mslink: a unique integer value used by the software to identify a row in the to_support table.



ee_ol_coord: the column containing the distance along the one-line to the support.

tag: the column that contains the support tag.

to_support symbols are not available at time of printing.

505


506

D: S

pecs

Appendix D: Specification________________

Appendix D Specification

Your reference database contains the specification tables (<one-line type>_part and <one-line type>_spec) thatdrive the EE Raceway product. These tables contain all attribute information for the available one-line types.The <one-line type>_spec table contains all specifications, while the <one-line type>_part table contains therelevant data for each of the fittings within a specification. The specifications available at the time of printingare for tray, wireway, airway, and conduit.

For special fittings like conduit bodies and pullboxes, the reference database contains one table for each fittingtype. The two special fittings delivered by default with EE Raceway are conduit body and pullbox.

Preparing the Specifications

Preparing the specifications is one of the first tasks the system manager performs when setting up the EERaceway product. The first step in this preparation is to create two ASCII data files (<one-line type>_part.unland <one-line type>_spec.unl) to contain all the relevant data from the vendor catalogs. You can edit these filesmanually using a standard ASCII editor or you can use the SPEC process delivered with EE Raceway. Thisprocess allows you to add records to an existing .unl file or to create a new .unl file easily and efficiently.

SPEC Process

The SPEC process resides in the win32app\eerway\bin directory. If you intend to add records to an existing.unl file, copy the appropriate <one-line type>_spec.unl to a file called <one-line type>_spec.sav beforerunning the process. The process will then write all records to this .sav file.

To initiate the process, key in SPEC at the command prompt. The following information displays to thescreen:

Enter schema name:Enter table name:Is this a restart (y/n)

Respond to the prompts according to your requirements. Enter your reference schema name and the appropriatetable name. The system will attach a .sav extension to the specified table name, and will then write all recordsto that file. Indicate whether or not you are adding records to an existing file (Is this a restart(y/n). If you answer n to the prompt, the system will overwrite any records already existing in the specified.sav file.

507

EE Raceway Modeling Reference Guide - February 2003________________ The system processes the information, and then displays the column values for the table name you specified, ina format similar to the following example (for tray_spec):

vendor <code list> ()ee_units <code list> ()ee_dimension_1 <real> ()ee_out_ht_diam <real> ()ee_dimension_2 <real> ()ee_out_width <real> ()ee_extension <real> ()ee_transition <real> ()ee_radius <real> ()weight <real> ()material <char-20> ()ee_xs_cell <char-6> ()ee_spec_key <char-28> ()ee_description <char-40> ()

Key in values to the right of the () for each column value. Each value is verified according to the parametersdefined inside the < >. Once you enter the final value for the displayed table, the system writes theinformation to the .sav file and redisplays the column names. It also displays the column values you entered forthe previous record. For subsequent records, press <RETURN> to accept the displayed values (in ()) or keyin new values as necessary. Continue this process as long as you wish to add records to your .sav file.

You can exit the process at any point by pressing CTRL -C. Copy the .sav file back to the corresponding .unlfile to keep the records you have added.

508

D: S

pecs

Appendix D: Sample .unl Files________________

Sample .unl Files

The following are examples of .unl files you will load into your reference database tables. Note that the | servesas a delimiter between column values.

tray_spec.unl

2|1|0|50|0|600|0|0|600|0|HOT DIP STEEL|A|6060SHV|VENTRIB SHV A2|1|0|50|0|600|0|0|300|0|HOT DIP STEEL|A|6030SHV|VENTRIB SHV A2|1|0|50|0|450|0|0|600|0|HOT DIP STEEL|A|4560SHV|VENTRIB SHV A2|1|0|50|0|450|0|0|300|0|HOT DIP STEEL|A|4530SHV|VENTRIB SHV A2|1|0|50|0|300|0|0|600|0|HOT DIP STEEL|A|3060SHV|VENTRIB SHV A2|1|0|50|0|300|0|0|300|0|HOT DIP STEEL|A|3030SHV|VENTRIB SHV A2|1|0|50|0|150|0|0|600|0|HOT DIP STEEL|A|1560SHV|VENTRIB SHV A2|1|0|50|0|150|0|0|300|0|HOT DIP STEEL|A|1530SHV|VENTRIB SHV A2|1|0|85|0|600|0|0|600|0|HOT DIP STEEL|A|6060SV|VENTRIB SV C12|1|0|85|0|600|0|0|300|0|HOT DIP STEEL|A|6030SV|VENTRIB SV C12|1|0|85|0|450|0|0|600|0|HOT DIP STEEL|A|4560SV|VENTRIB SV C12|1|0|85|0|450|0|0|300|0|HOT DIP STEEL|A|4530SV|VENTRIB SV C12|1|0|85|0|300|0|0|600|0|HOT DIP STEEL|A|3060SV|VENTRIB SV C12|1|0|85|0|300|0|0|300|0|HOT DIP STEEL|A|3030SV|VENTRIB SV C12|1|0|85|0|150|0|0|600|0|HOT DIP STEEL|A|1560SV|VENTRIB SV C12|1|0|85|0|150|0|0|300|0|HOT DIP STEEL|A|1530SV|VENTRIB SV C12|1|0|50|0|600|0|0|600|0|ALUMINUM|A|6060AHV|VENTRIB AHV A2|1|0|50|0|600|0|0|300|0|ALUMINUM|A|6030AHV|VENTRIB AHV A2|1|0|50|0|450|0|0|600|0|ALUMINUM|A|4560AHV|VENTRIB AHV A2|1|0|50|0|450|0|0|300|0|ALUMINUM|A|4530AHV|VENTRIB AHV A2|1|0|50|0|300|0|0|600|0|ALUMINUM|A|3060AHV|VENTRIB AHV A

509


tray_part.unl

2|2|5|90|0|A-15VA|VEL|1530AS| |A-15VA|Vertical Adjustable Elbow2|2|5|90|0|A-30VA|VEL|3030AS| |A-30VA|Vertical Adjustable Elbow2|2|5|90|0|A-45VA|VEL|4530AS| |A-45VA|Vertical Adjustable Elbow2|2|5|90|0|A-60VA|VEL|6030AS| |A-60VA|Vertical Adjustable Elbow2|2|5|90|0|AD-15VA|VEL|1530ADS| |AD-15VA|Vertical Adjustable Elbow2|2|5|90|0|AD-30VA|VEL|3030ADS| |AD-30VA|Vertical Adjustable Elbow2|2|5|90|0|AD-45VA|VEL|4530ADS| |AD-45VA|Vertical Adjustable Elbow2|2|5|90|0|AD-60VA|VEL|6030ADS| |AD-60VA|Vertical Adjustable Elbow4|5|1|90|0|ADL-15X-90|HRC|1590ADL| |ADL-15X-90|Horizontal Cross1|8|1|0|0|ADL-30R15|CR|1560ADL|3060ADL|ADL-30R15-60|Concentric Reducer1|8|1|0|0|ADL-30R15|CR|1590ADL|3090ADL|ADL-30R15-90|Concentric Reducer1|9|1|0|0|ADL-30RL15|LR|1560ADL|3060ADL|ADL-30RL15-60|Left Reducer1|9|1|0|0|ADL-30RL15|LR|1590ADL|3090ADL|ADL-30RL15-90|Left Reducer1|10|1|0|0|ADL-30RR15|RR|1560ADL|3060ADL|ADL-30RR15-60|Right Reducer1|10|1|0|0|ADL-30RR15|RR|1590ADL|3090ADL|ADL-30RR15-90|Right Reducer1|1|1|0|0|ADL-30ST|STS|3060ADL| |ADL-30ST-60|Straight Section1|1|1|0|0|ADL-30ST|STS|3090ADL| |ADL-30ST-90|Straight Section3|5|1|90|0|ADL-30T-60|HRT|3060ADL| |ADL-30T-60|Horizontal Tee3|5|1|90|0|ADL-30T-90|HRT|3090ADL| |ADL-30T-90|Horizontal Tee


Once created, the .unl files are input to the Update Reference Schema process which loads information in the<one-line type>_part and <one-line type>_spec tables. As described previously, the spec table contains allspecifications, while the part table contains the relevant data for each of the fittings within a specification.

For information about running Update Reference Schema, see Update Reference Schema in the sectionentitled Electrical Engineer (EE) Environment.

Sample Specification Tables

This section describes the required column names of sample specification tables, tray_spec and tray_part.

tray_spec table

Column Name Description

vendor* the index_column (codelist) value from the vendor table.ee_units* the index_column (codelist) value from the ee_units table.ee_dimension_1 a dimension variable used by Eden.ee_out_ht_diam the outside height dimension in sub-units.ee_dimension_2 a dimension variable used by Eden.ee_out_width the outside width dimension in sub-units.ee_extension the fitting extension.

510

D: S

pecs

Appendix D: Sample .unl Files________________ ee_transition the fitting transition length.ee_radius the fitting bend radius.weight the weight per unit length of the run.material the tray material.ee_const_type the construction type.ee_xs_cell the cross section symbol.ee_spec_key the unique tray specification key.ee_description the tray specification description.

tray_part table

Column Name Description

ee_tl_type* the index_column value from the tl_type table.ee_tl_subtype* the index_column value from the tl_subtype table.ee_tl_qual* the index_column value from the tl_qual table.ee_angle the fitting turn angle.ee_weight the tray part weight.ee_part the tray part catalog number.ee_symbol the Eden symbol.ee_spec_key the tray specification key.ee_spec2_key the secondary tray specification key for reducers.ee_key the unique tray part key.ee_description the tray part description.

* For information about the codelist values, see the appendix entitled EE Databases .

511


Available Fittings

The following is a list of the fittings currently supported by the EE Raceway Modeling product:

FITTING TYPE ANGLE

StraightElbow Horizontal 30,45,60,90, and

AdjustableElbow Inside Vertical 30,45,60,90, and

AdjustableElbow Outside Vertical 30,45,60,90, and

AdjustableWye Horizontal 90,45 left and 45

rightWye Vertical 90Wye Reducer 90Cross Horizontal 90Cross Vertical 90Reducer Left HorizontalReducer Right HorizontalReducer ConcentricConduitbodyPullbox

512

E: E

den

Sym

bo

ls

Appendix E: Eden Symbol Generation________________

Appendix E Eden SymbolGeneration

Eden is a high-level symbol definition language (modeled after the FORTRAN programming language) thatallows you to design your own symbols for raceway straight sections, fittings, and special parts (conduit bodies,pullboxes, etc.).

You do not need a programming background to write Eden programs. However, you should be familiar with astandard ASCII editor like vi or emacs. You can write Eden code using whatever case conventions make iteasiest for you to read.

Eden provides drawing commands called primitives. Primitives allow you to construct complex symbols byusing a combination of simple commands (place_line, draw_arc, etc.).

For additional information about the Eden symbol language, see the PDS Eden Interface Reference Guide.

Symbol Processor File

A symbol processor file is the controlling function or logic used to produce the raceway straight sections,fittings, and special parts. The delivered symbol library is called eden.lib and resides in win32app\eerway\eden.The library and its path are defined using the EE Configure command. To review or modify the symbols inthis library, use the delivered Eden processes. (See the chapter entitledEden Processes for more information about running these processes.)

Every Raceway symbol must contain a symbol processor definition and at least one of each of the following:

Placepoint (EE attachment point)

Datum point (EE RCP point)

Graphical element

513

EE Raceway Modeling Reference Guide - February 2003________________ The best way to explain how a symbol processor file works is to show an example:

Before creating an Eden symbol processor file, you should have consulted the PDS EdenInterface Reference Guide or have taken a course in Eden symbol generation.

=========================================================================!! Symbol Name: HEL!! Description: Horizontal Tray Elbow, with or without extensions.!=========================================================================

SYMBOL_PROCESSOR ’HEL’

#DESC = Tray Horizontal Elbow

r8 halfwid, height, radius, extension, angle, val1, val2, val3,val4, val5, val6

!! Get Dimensions Required to create the horizontal elbow.!

angle = DIMENSION[4]height = DIMENSION[21]halfwid = DIMENSION[22] / 2.0extension = DIMENSION[23]radius = DIMENSION[25]

ORG = 19BND1 = 20BND2 = 21EXT1 = 22EXT2 = 23ARC = 24

NUMPTS = 4

If ( halfwid .eq. 0.0 .or. height .eq. 0.0 .or. angle .eq. 0.0) thenCall ABORT ( 0 )

Endif

Call Begin ( NOHOLE )Call Begin ( SURFACE )

!! Add dimension of tray to radius!

radius = radius + halfwid

!! Calculate distances distance variables!! val1 = bendpoint on primary oneline! val2 = primary distance to bendpoint on bent oneline! val3 = secondary distance to bendpoint on bent oneline! val4 = extension point on primary oneline! val5 = primary distance to extpoint on bent oneline! val6 = secondary distance to extpoint on bent oneline!

514

E: E

den

Sym

bo

ls

Appendix E: Eden Symbol Generation________________ radius = radius + halfwidval1 = radius * DTAND( angle / 2.0 )val2 = val1 * DSIND( angle )val3 = val1 * DCOSD( angle )val4 = val1 + extensionval5 = val4 * DSIND( angle )val6 = val4 * DCOSD( angle )

!! Define bendpoints (point2 and point3) and bend origin (point4)!

Call Define_Datum_Point( DP[1], Point[0] )Call Define_Point ( Point[ORG], Point[0], 0, 0, 0, 0 )Call Define_Point ( Point[BND1], Point[0], -val1, 0, 0, 0 )Call Define_Point ( Point[BND2], Point[0], val3, val2, 0, 0 )Call Define_Point ( Point[EXT1], Point[0], -val4, 0, 0, 0 )Call Define_Point ( Point[EXT2], Point[0], val6, val5, 0, 0 )Call Define_Point ( Point[ARC], Point[0], -val1, radius, 0, 0 )

!! Define Placepoints!

Call Define_Active_Point ( Point[EXT2] )Call Define_Orientation_By_Points ( Point[ORG], Point[BND2],Point[ARC] )Call Rotate_Orientation( 180.0, NORMAL )Call Define_Placepoint ( PP2, Point[0] )

Call Define_Active_Point ( Point[EXT1] )Call Define_Orientation_By_Points ( Point[BND1], Point[ORG],Point[BND2] )Call Define_Placepoint ( PP1, Point[0] )

!! Define cross section points!

Call Define_Active_Point ( Point[BND1] )

Call Define_Point (Point[1], Point[0], 0, halfwid, height, 0 )Call Define_Point (Point[2], Point[0], 0, halfwid, 0, 0 )Call Define_Point (Point[3], Point[0], 0, -halfwid, 0, 0 )Call Define_Point (Point[4], Point[0], 0, -halfwid, height, 0 )

!! Draw First Extension!

If ( extension .ne. 0 ) thenDo i = 1, NUMPTS, 1

Call Define_Point( Point[NUMPTS+i], Point[i],-extension, 0,0, 0)

EnddoCall Draw_Complex_Surface ( 1, 0 )Call Draw_Line_String ( NUMPTS, Point[1] )Call Draw_Line_String ( NUMPTS, Point[NUMPTS+1] )Call Draw_Complex_Surface ( -4, 0 )Do i = 1, NUMPTS, 1

Call Draw_Line ( Point[i], Point[NUMPTS+i] )EnddoCall Draw_Complex_Surface ( -99, 0 )

Endif

515

EE Raceway Modeling Reference Guide - February 2003________________ !! Draw revolved shape!

Call Define_Orientation_By_Points(Point[1],Point[2],Point[3])

Call Define_Active_Point ( Point[ARC] )Call Draw_Revolved_Shape ( EL_LINESTR, -angle, 1, Point[1], NUMPTS,0 )

!! Draw Second Extension!

If ( extension .ne. 0 ) then

Call Define_Active_Point ( Point[BND2] )Call Define_Orientation_By_Points(Point[ORG],Point[BND2],Point[ARC])

Call Define_Point (Point[1], Point[0], 0, halfwid, height, 0 )Call Define_Point (Point[2], Point[0], 0, halfwid, 0, 0 )Call Define_Point (Point[3], Point[0], 0, -halfwid, 0, 0 )Call Define_Point (Point[4], Point[0], 0, -halfwid, height, 0 )

Do i = 1, NUMPTS, 1Call Define_Point(Point[NUMPTS+i], Point[i], extension, 0,

0, 0)Enddo

Call Draw_Complex_Surface ( 1, 0 )Call Draw_Line_String ( NUMPTS, Point[1] )Call Draw_Line_String ( NUMPTS, Point[NUMPTS+1] )Call Draw_Complex_Surface ( -4, 0 )

Do i = 1, NUMPTS, 1Call Draw_Line ( Point[i], Point[NUMPTS+i] )

EnddoCall Draw_Complex_Surface ( -99, 0 )

Endif

Stop

End

The first line of this file should always be:

SYMBOL_PROCESSOR ’<name>’

The last two lines of the file should always be:

Stop

End

This line defines the symbol name. When defining parts in the reference database, the name of the symbolshould correspond with the ee_symbol in the part table. For more information see the description ofdatabases in the Workflow and Procedures chapter.

516

E: E

den

Sym

bo

ls

Appendix E: Eden Symbol Generation________________ The symbol in the example defines the symbol name as Tray Horizontal Elbow.

The symbol derives the values for angle, height, width, extension, and radius from the global arrayDIMENSION. EE Raceway fills the DIMENSION array with values extracted from the reference database.For a description of which database columns are associated with what dimensions, see the table immediatelyfollowing this description.

EE Raceway uses a Datum Point to define the location of the RCP relative to the symbol. It uses Placepoints todefine the point by which you can place a fitting using manual placement. In general, the one-line will passthrough a placepoint on the symbol and will terminate at the RCP.

The creation of the horizontal elbow symbol is fairly straightforward given a knowledge of Eden primitives.The RCP is defined in the active location with the active orientation, while other critical points are definedrelative to the origin. Then the placepoints are defined at either end of the elbow. If the fitting has extensions,they are drawn as a surface of projection of a line string. The elbow is drawn as a surface of revolution.

DIMENSIONS

The DIMENSION structure contains specific information that has been extracted from the database and passedthrough to Eden.

For specification-driven parts, the structure is as follows:

Dimension What From

1 Three Line Type Manual Placement Form or Calculated2 Three Line Subtype Manual Placement Form or Calculated3 Three Line Qualifier Manual Placement Form or Calculated4 Angle Manual Placement Form or Calculated11 Length Manual Placement Form or Calculated

These are from the specification table:

21 Height Spec Table - ee_out_ht_diam22 Width Spec Table - ee_out_wid23 Extension Spec Table - ee_extension24 Transition Spec Table - ee_transition25 Radius Spec Table - ee_radius26 Dimension 1 Spec Table - ee_dimension_127 Dimension 2 Spec Table - ee_dimension_2.. ........... ............ ........... ............ ........... ..........50 Dimension 25 Spec Table - ee_dimension_25

These are from the secondary specification (if one exists):

51 Height_2 Spec Table - ee_out_ht_diam52 Width_2 Spec Table - ee_out_wid53 Extension_2 Spec Table - ee_extension

517

EE Raceway Modeling Reference Guide - February 2003________________ 54 Transition_2 Spec Table - ee_transition55 Radius_2 Spec Table - ee_radius56 Dimension 1 Spec Table - ee_dimension_157 Dimension 2 Spec Table - ee_dimension_2.. ........... ............ ........... ............ ........... ..........80 Dimension 25 Spec Table - ee_dimension_25

The following structure is used for special parts:

Dimension What From

26 Dimension 1 Part Table - ee_dimension_127 Dimension 2 Part Table - ee_dimension_2.. ........... ............ ........... ............ ........... ..........80 Dimension 60 Part Table - ee_dimension_60

518

F: F

ile Stru

cture

Appendix F: EE File Structure________________

Appendix F EE File Structure

This section describes the file structure for EE Nucleus and EE Raceway. It also describes the contentsof directories and some files. It identifies those files you can modify.

By default, the PDS Component Loader delivers these files to \win32app\ingr.

The directory tree for EENUC and EERWAY is shown below.

519


EE Nucleus File Structure

EE Nucleus (EE Nuc) is the core product for the EE product line. The product may reside on any filesystem. EE Nucleus will reside under the /usr#/ip32/eenuc directory. The list may differ slightlydepending on which options are selected during installation. The following files exist under the../eenuc directory:

Any file followed by a slash (name/) is a directory. Any file followed by an asterisk (*)is an executable.

/usr/ip32/eenuc:

/usr/ip32/eenuc/bin:

/usr/ip32/eenuc/bin/c100:

/usr/ip32/eenuc/config:

/usr/ip32/eenuc/data:

/usr/ip32/eenuc/db:

520

F: F

ile Stru

cture

Appendix F: EE Nucleus File Structure________________ /usr/ip32/eenuc/doc:

/usr/ip32/eenuc/forms:

/usr/ip32/eenuc/msg:

/usr/ip32/eenuc/sym:

The following list gives a brief description of some of the files. The files are grouped by directory.

eenuc/

— README – file containing description of product features and any fixes, problems,comments, etc.

— product.def – product definition file.

— remove.sh – shell script used by the remove utility in deltools used to remove EE Nucleusfrom the machine.

— .EErc – File containing global symbol definitions.

— EEnotice.txt – File containing release notices.

— legend – copyright notice file.

bin/ – contains the EE shell script and the environment process. The EE shell script sets upvariables specifying the location of MicroStation 32, INFORMIX, EE Nucleus, and EE WPD,and then invokes the EE environment. C100 for C100 executables or C400 for C400executables.

521


— background – process that reports the exit status of a process run in the background.

— batch – process that reports the exit status of a process run in batch mode.

— clip – clears interprocess communication left after a process finishes. Also kills strayprocesses.

— create_db – create database process.

— dba_rpt – DBAccess report process.

— dba_shell – shell executed around dba_rpt.

— EE – Electrical Engineer environment shell script.

— EEmgr – Electrical Enginner manager environment shell script.

— eemgr – system manager environment process.

— eeprj – environment process.

— eeqpr – script to print 132 column reports to the laser printer.

— menu_shell – shell executed around eemgr to run the Edit Database process.

— mount – supports less disk installation.

— mscrecol.sh – shell script to create mscolumns table for reference database.

— reeprj – remote environment process.

— risql – EE reporting utility.

— 132_header – file to allow printing in 132 column format.

— infx_ol – file used for compression of on-line INFORMIX databases.

— infxcompress – file used for compression of standard engine databases.

config/ – Contains the file that assigns and exports any required variables. The file assignsMicroStation 32 variables, INFORMIX variables, and product variables.

— assign – shell script that assigns and exports any required variables. This file can be edited.

— eeconfig – file that maintains EE product configuration for workstation/server.

data/ – Contains the ASCII files used to control certain environment procedures.

— print.dat – ASCII file for output file management.

522

F: F

ile Stru

cture

Appendix F: EE Nucleus File Structure________________

— manager.dat – ASCII file for manager function management.

— dba* files – DB Access files.

— ustn_tsk – DB Access file.

db/ – directory that contains the DB Access menu library (mgrdba_lib). Required DBAccessfiles are also delivered in this directory.

doc/ – directory that contains documentation.

— lessd.txt – less disk information.

— eepsp.txt – EE project setup information.

forms/ – directory that contains all the environment forms.

msg/ – contains EE Nucleus message files.

sym/ – contains EE symbol files.

523


EE Raceway File Structure

This section lists and describes the directories and files delivered with EE Raceway.

/usr/ip32/eerway:

/usr/ip32/eerway/bin:

/usr/ip32/eerway/bin/c100:

/usr/ip32/eerway/cfg:

/usr/ip32/eerway/config:

/usr/ip32/eerway/data:

524

F: F

ile Stru

cture

Appendix F: EE Raceway File Structure________________ /usr/ip32/eerway/db:

/usr/ip32/eerway/dgn:

/usr/ip32/eerway/dgn/seed:

/usr/ip32/eerway/doc:

/usr/ip32/eerway/eden:

/usr/ip32/eerway/help_source:

525

EE Raceway Modeling Reference Guide - February 2003________________ /usr/ip32/eerway/help_source/help_graphics:

/usr/ip32/eerway/mdlapps:

/usr/ip32/eerway/menus:

/usr/ip32/eerway/msg:

/usr/ip32/eerway/report:

526

F: F

ile Stru

cture

Appendix F: EE Raceway File Structure________________ /usr/ip32/eerway/sym:

/usr/ip32/eerway/tmp: delivered empty


eerway/

— README – file containing a description of the product features and any fixes, problems,comments, etc.

— product.def – product definition file.

— remove.sh – shell script used by the remove utility in deltools used to remove EE Racewayfrom the machine.

bin/ – contains all process delivered with the EE Raceway product.

— idet – Interference Detection Envelope File Creation process.

— load – processor to load the project database.

— rmon – Controlling processor for interactive manipulations. unload_cln – contains theunload sheet, unload drawing, and clean database processes.

cfg/ – Contains the application menu configuration files.

— menu.cfg – EE Raceway menu configuration file.

config/ – Contains the file that defines and exports all variables required by EE Raceway andthose MicroStation 32 variables required by EE Raceway.

— assign – shell script that defines and exports any required variables.

data/ – Contains the ASCII files used to control process and report management for the EERaceway product. These files can be modified.

527


— eden.dat – controls Eden processes.

— process.dat – controls process management.

— report.dat – controls standard report management.

— rule_chk.dat – controls rule check report management.

db/ – Contains the delivered sql files for the project and reference database. Also contains .unlfiles required for bulk loading special tables and the mscatalog table in the project database.Sample .unl files for bulk loading reference database tables are also provided.

dgn/ – Contains the seed file directory, available cell libraries, and any design files deliveredwith the product.

— seed/ – contains the available seed design files.

– seed.dgn – delivered English drawing seed file. This may be customized.

– msseed.dgn – delivered metric drawing seed file. This may be customized.

doc/ – contains documentation information on EE Raceway including README files fromprevious releases.

eden/ – contains the Eden symbol library.

— eden.lib – the Eden symbol library file.

help_source/ – contains the text and source files required to support on-line Help.

— help_rway.hp – help pointer file.

— help_rway.s – help source file.

— help_graphics – contains the graphics used in on-line Help.

— mstr_rway.hp – master help pointer file containing pointers to both MicroStation 32 and EERaceway Help.

— mstr_rway.s – master help source file.

menus/ – Contains the all menus (panel and bar) supporting the product. Also contains allsymbol and icon files required to support delivered menus. You can supply additional menufiles.

— rway.cmds – command file for EE commands invoked by MicroMenu. Attaches thefunction bar menu, function key menu, and cell library.

— rway_bar – bar menu for schematic commands.

528

F: F

ile Stru

cture

Appendix F: EE Raceway File Structure________________

— merge_pnl/ – directory containing the merged panel menu consisting of EE Raceway andMicroStation.

– merge_pnl – panel menu file.

— rway.bar – bar menu source file.

— rway.pnl – panel menu source file.

— rway_pnl/ – contains the rway_pnl binary menu files.

– rway_pnl – panel menu palette file.

msg/ – Contains EE Raceway message files and the file to correlate key-ins to EE Racewaycommands.

— alias.cmd – file used to correlate key-ins to commands. This file can be extended.

— command.msg – message file containing all messages for the command field. Thesemessages can be edited but messages can not be added.

— error.msg – message file containing all error messages for the error field. These messagescan be edited but messages can not be added.

— prompt.msg – message file containing all messages for the prompt field. These messagescan be edited but messages can not be added.

— rway_prj.tbl – file containing the entity numbers for the project database tables.

— rway_ref.tbl – file containing the entity numbers for the reference database tables.

— status.msg – message file containing messages for status field, prompting messages, andlogo. These messages can be edited but messages can not be added.

report/ – Contains the source (.ace)and compiled (.arc) SQL files for all delivered sch reports.The source files may be edited by the user. There is an .ace and an .arc file for each report listedbelow.

— rwaydba_lib – DB Access template library.

sym/ – Contains all symbol files for EE Raceway menus. This directory also contains theavailable precision input forms.

— annot_form – form file for annotation.

— rwaybar.sym – symbol file for the bar menu.

— rwaypnl.sym – symbol file for the panel menu.

tmp/ – Holds any temporary files. The software requires this directory.

529


530

G: C

usto

mizin

g

En

viron

men

t

Appendix G: Customizing Environment Files________________

Appendix G CustomizingEnvironment Files

This appendix contains printouts of the following files as they are delivered with EE Raceway:

File Location

eden.dat win32app\ingr\eerway\dataprocess.dat win32app\ingr\eerway\datareport.dat win32app\ingr\eerway\datarule_chk.dat win32app\ingr\eerway\dataprint.dat win32app\ingr\eenuc\datamanager.dat win32app\ingr\eenuc\data

process.dat, report.dat, rule_chk.dat, and print.dat control the scrolling lists for the Process, Report,Rule, and Output menus, respectively. You may want to write your own processes, reports or rulechecks or change their names from what is delivered. This section describes the syntax needed tomodify the scrolling list for the Process, Report, Rule, and Output.

The manager.dat file controls the scrolling list for the options available through the system managermenu. You can add defaults to this screen by modifying the file.

eden.dat

#ident "@(#)Eden processes:eden.dat 13.1 0.0 (EE Raceway) 12/14/93"

#

# Note: No blanks lines allowed in this file.

#

# eden.dat

# This file is stored under the %EE_RWAY%\data directory.

# The syntax of this data file is :

#

# Title | Command Line | Prompt,Default,Path,Switch | , , ...

#

# The first column for a comment line must be the ’#’ character.

# The ’\’ is the line continuation character.

#

# The first field is the title which will appear on the scrolling list.

#

# The second field is a command line containing the name of the executable.

#

# The third field and each subsequent field will contain three sub-fields

# using the comma (,) as the delimeter

#

# They are :

# Prompt,Default,Path,Switch

# The default can be a global symbol or file.

# Any of the sub-fields in the third field can be omitted

#

# Change History:

# Added the ability to list/extract user functions 31-May-95

#

Compile EDEN Symbol | %EE_RWAY%\bin\eden.bat -c \

| Enter library name ,%EDEN_LIB%,, \

| Enter symbol source file ,,,\

| Enter option (-l=list or -o=insert),-O,,

#

531


#

#

Delete EDEN Symbol | %EE_RWAY%\bin\eden.bat -d\


| Enter symbol name ,,,

#

#

#

List EDEN Symbol Library | %EE_RWAY%\bin\eden.bat -l \

| Enter library name ,%EDEN_LIB%,,

#

#

#

List EDEN User Functions | %EE_RWAY%\bin\eden.bat -u \


#

#

#Create Parameteric Help Library | %EE_RWAY%\bin\eden.bat -C \

# | Enter library name ,%EDEN_LIB%,,

#

#

#

Merge EDEN Symbol Libraries | %EE_RWAY%\bin\eden.bat -m \

| Merge into library name ,,, \

| Merge from library name ,,,

#

#

#

Compress EDEN Symbol Library | %EE_RWAY%\bin\eden.bat -s \


#

#

#

Extract EDEN Symbol From Library| %EE_RWAY%\bin\eden.bat -e \



#

#

Extract EDEN User Function From Library| %EE_RWAY%\bin\eden.bat -eu \



#

#

Edit EDEN Symbol File | %EE_RWAY%

n\den.bat

-E

|

Enter

ed

tor,notepad,, | Enter symbol file name,,,

#

#

532

G: C

usto

mizin

g

En

viron

men

t

Appendix G: process.dat________________

process.dat

#ident "@(#)data:process.dat 13.1 0.0 (EE Raceway) 12/14/93"

#


#

# process.dat

# This file is stored under the %EE_SCH%\data directory.


#


#



#


#


#



#

# They are :




#

# NOTE: Many processes run off the project or reference schema (or both).

# Two environment symbols have been set up for these schemas: EE_SCHEMA

# for the project schema and EES_REFDB for the reference. These symbols

# are exported by the EE environment when a project is entered. This was

# done to handle schema passwords. The symbol is exported as

# <schema_name>.<password> if a password is keyed in on the project form.

# So, any customized processes written should read these symbols in the

# process instead of passing them on the command line. The password will

# have to be handled accordingly.

#

#

Load Database | %EE_RWAY%\bin\load.exe \

| Enter design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-f

#

#

#

Unload Design | %EE_RWAY%\bin\unld_cln.exe \

| Enter design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-F

#

#

Unload Sheet | %EE_RWAY%\bin\unld_cln.exe -s \

| Enter sheet,,,

#

#

Cleanup database | %EE_RWAY%\bin\unld_cln.exe

#

#

Create Interference Envelope (default name) | %EE_RWAY%\bin\idet.exe \

| Enter design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-f

#

#

Create Interference Envelope (given name) | %EE_RWAY%\bin\idet.exe \

| Enter one design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-f \

| Enter envelope name,,,-e

533


report.dat

#ident "@(#)data:report.dat 7.1 0.0 (EE Raceway) 6/1/92"

#


#

# report.dat

# The syntax of this data file :

# Title | Command Line | Report Name | Prompt,Default | , , ...

#


# The second field is the command field.

# The third field is the name of the report which can be a global symbol

# or a file name.

# The fourth field and each subsequent field will contain two sub-fields

# using the comma (,) as the delimeter.

#

# They are:

# Prompt,Default


# Any of the sub_fields in the third field can be omitted.

#

#

Project drawing list | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \

| drwlst \

| Enter project schema,%EE_SCHEMA%

#

#

Material takeoff report | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \

| mto_rpt \


#

#

Raceway bill of materials report| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \

| rway_bom \


#

#

Raceway bill of materials by volume| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \

| rway_bom_v \

| Enter project schema,%EE_SCHEMA% \

| Enter low range (PDS coordinates: east north elev) \

| Enter high range (PDS coordinates: east north elev)

#

#

Raceway Conduit Body report| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib dummy %EE_RPTDB% \

| cond_body \

| Enter Reference schema,%EES_REFDB%

#

#

534

G: C

usto

mizin

g

En

viron

men

t

Appendix G: rule_chk.dat________________

rule_chk.dat

#ident "@(#)data:rule_chk.dat 13.1 0.0 (EE Raceway) 12/14/93"

#


#

# rule_chk.dat


# Title | Command Line | Report Name | Prompt, Default | , , ...

#


# The second field is the command field.

# The third field is the report name which can be a global symbol or file.

# The fourth field and each subsequent field will contain two sub-fields

# using the comma (,) as the delimiter

#

# They are: Prompt,Default


# Any of the sub_fields in the third field can be omitted.

#

#

Material takeoff blank part ID’s | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \

| blank_ids \


#

#

535


print.dat

#ident "@(#)env_data:print.dat 21.1 0.0 (EE Schematic) 3/9/94"

#


#

# print.dat

# This file is stored under %EE_NUC%\data directory.

# The first column of comment line must be #.


# TITLE | COMMAND | PROMPT,DEFAULT,PATH,SWITCH...

# The titles are the messages on the scrolling list.

# The command can be any command to output a file.

# The third field is made up of four parts: prompt,default,path and switch.

# (The path is not relevant). This field should be used to pass

# information to the command. A file name is automatically appended to

# the command as the last parameter.

#

TO SCREEN| SCREEN

#

# Local line printer

#

Local Printer| lp

#

# NQS print command to print to a laser printer

#

Laser Printer 80 columns | qpr -t text\

| Enter queue name,,,-q

#

Laser Printer 132 columns | %EE_NUC%\bin\eeqpr \

| Enter queue name,,,

#

# This is an example of a way to print to a VAX. The command "vaxprint"

# could be a shell script or an exported shell function.

#

#VAX Line Printer| vaxprint

#

536

G: C

usto

mizin

g

En

viron

men

t

Appendix G: manager.dat________________

manager.dat

#ident "@(#)env:manager.dat 21.1 0.0 (EE Nucleus) 3/9/94"

#


#

# manager.dat

# This file is stored under the %EE_NUC%\data directory.


#


#



#


#


#



#

# They are :




#

#

Edit database | %EE_NUC%

n

ba_rpt.exe

-m

dbed

tnt -l %EE_NUC%\db\mgrdba_lib \| Enter schema name,,, -s

#

#

#Compress database - INFORMIX SE | vterm -x %EE_NUC%\bin\infxcompress -T compress

#

#

#Compress database - INFORMIX Online | vterm -x %EE_NUC%\bin\infx_ol -T compress

#

Create mscolumns table | %EE_NUC%\bin\mscrecol.cmd \

|Enter schema name,,,

537


538

H: alias.cm

d file

Appendix H: alias.cmd file________________

Appendix H alias.cmd file

This appendix contains a description and printout of the alias.cmd file.

The alias.cmd file is an ASCII file located in win32app\ingr\eerway\msg. You can use any text editorto modify the file. The alias.cmd file contains instructions for adding an entry, the format of such anentry, a sample entry, and a list of EE Raceway command names and the hard-code for each command.

The example in the alias.cmd file explains how to create an alias for a particular command. To the leftof the equal sign (=) in this example is the user-definable alias key-in name. The fixed (hard-coded)command name is to the right of the equal sign. If you were to add this example to the alias.cmd file,then the key-in EERWAY Remove Element would invoke the command EERWAY DeleteElement, just as would the key-in EERWAY Delete Element.

You do not need to add entries to the alias.cmd file; the command name key-ins in the file will invokethe commands to which they correspond.

You need to key in just enough of the key-in name to make it unique. For example, ifthe sample alias entry (in the file below) were added to alias.cmd, you would need onlyto key in r e to invoke the command.

Since the EE Raceway software has a reserved set of names for each Raceway commandwhich are hard-coded into the EE Raceway software, any alias you add to this file must notmatch any of the command name key-ins or hard-coded names listed below.

The following is a print-out of the alias.cmd file (the # symbols indicate comment lines):

#ident "@(#)rdmsg:alias.cmd 13.1 0.0 (EE Raceway) 12/14/93"

# To create an alias for an EE Raceway command add an entry to this# file consisting of the alas and the hardcode for that command in# the following format:## <alias> = <hardcode>## The list of possible hardcodes follows:## Command Name Hardcode# ———— ——–# EERWAY Active OLT Parameters - rwp# EERWAY Add System Group - addsysg# EERWAY Annotate Element - annotate# EERWAY Annotate Group - anntgrp# EERWAY Annotate Title Block - anntblk# EERWAY Clone Element - clone# EERWAY Clone Group - cloneg# EERWAY Conduit Sizing - rtwform# EERWAY Copy Element - cpele# EERWAY Copy Group - cpeleg# EERWAY Create Cell - crecell# EERWAY Delete Coincident RCPs - coinrcp# EERWAY Define Duct Cross Section - ductform

539

EE Raceway Modeling Reference Guide - February 2003________________ # EERWAY Delete Duplicate One Lines - dupols# EERWAY Delete Element - dltele# EERWAY Delete Group - dlteleg# EERWAY Delete Title Block - dlttblk# EERWAY Design Parameters - ueleform# EERWAY Display Element Info - eleinfo# EERWAY Display Entity and Mslink - prtrlnk# EERWAY Display Fitting Info - tlfinfo# EERWAY Display Run Info - runinfo# EERWAY Display Sector and Word - prtsw# EERWAY Display System and OLT - prtsysol# EERWAY Display Type and Asid - prtasid# EERWAY Edit Manual Fitting - manedit# EERWAY Exit - rexit# EERWAY Fitting Environment Element - rulefit# EERWAY Fitting Environment Group - rulefitg# EERWAY Group Control - grpform# EERWAY Highlight Asid - hiasid# EERWAY Highlight Entity and Mslink - hirlnk# EERWAY Highlight Graphic Group - higg# EERWAY Highlight Propagation Errors - hiprerr# EERWAY Highlight Sector and Word - hisw# EERWAY Highlight System Elements - hisys# EERWAY Insert One Line Vertex - insolvert# EERWAY Insert RCP - addrcp# EERWAY Levels Control - levels# EERWAY Load Database - loaddb# EERWAY Minimize Joints - minjnt# EERWAY Minimize Joints Group - minjntg# EERWAY Modify One Line - modol# EERWAY Move Element - mvele# EERWAY Move One Line Segment - mvolseg# EERWAY Move One Line Vertex - mvolvert# EERWAY Move Title Block - mvtblk# EERWAY OLT Definition - oltdef# EERWAY Place Drop Point - plcdpnt# EERWAY Place Equipment Pointer - plctoeqp# EERWAY Place Manual Fitting - manform# EERWAY Place One Line - plcol# EERWAY Place Title Block - plctblk# EERWAY Propagate Element - prjele# EERWAY Propagate Group - prjeleg# EERWAY Propagation Control - propform# EERWAY Remove Fitting - rmfit# EERWAY Remove One Line Vertex - rmolvert# EERWAY Remove RCP - rmrcp# EERWAY Replace System Group - repsysg# EERWAY Rotate Cross Section - rotcs# EERWAY Route Around Vessel - rtvess# EERWAY Run Reports - runrpt# EERWAY Run Rule Checks - runrul# EERWAY Set Active OLT - actolt# EERWAY Set Active OLT Parameters - setact# EERWAY Set Active Point - actpnt# EERWAY Set Active System - actsys# EERWAY Set Conduit Sizing Attributes - setcsa# EERWAY Set Symbology Control - setgsc# EERWAY Symbology Control - symbform# EERWAY System Definition - sysdef# EERWAY Text Defaults - txtdef# EERWAY Toggle Spider Display - togspider#

540

H: alias.cm

d file

Appendix H: alias.cmd file________________ # example: EERWAY Remove Element = dltele#

541


542

I: rway.cm

ds

Appendix I: rway.cmd________________

Appendix I rway.cmd

The file rway.cmd is the MicroMenu (umenu) command file that is used to attach the EE Racewaymenus. It is run automatically when you enter the EE Raceway environment. This file is located in thedirectory path win32app\eerway\db and activates the rway.ammfile.

If you do not want the rway.cmd file to be executed, you can comment out the exportvariable RWAY_CMD using the EE Configure command.

The rway.cmd file may also be edited by the user. MicroStation reads this file and processes thecommands as if keyed in by the user. You can disable any of these features by commenting out theline(s) that enable the feature. (Place a pound sign (#) in front of any line you do not want executed.)Below is the file as it is delivered in the product directory:

m,prAttaching EE Raceway Menus...add mmenus ee_rway:menu.cfgactive mmenus ee_rway:rway.ammm,pr

543


544

J: Rep

orts

Appendix J: Reports________________

Appendix J Reports

This section describes each report delivered with EE Raceway. It specifies the attributes used in thereport and describes some of the internal operation behind report generation. This information will behelpful if you want to use a delivered report as a template for a customized report. The EE Racewayreports report on the project database, the reference database and, in some cases, both.

All EE Raceway reports are currently written for RIS-DBACCESS. Documentation explaining how tocreate and compile customized reports with RIS-DB ACCESS is available in the DB ACCESSReference Guide, the Project Data View Reference Guide, and the RIS Report-Writer Reference Guide.All EE Raceway reports are compatible for use with either RIS Report-Writer (RISRPT) or DB Access(DBA).

RIS Report Processing

A report processor is provided with EE Raceway to run RIS-based reports. Report templates createdthrough DB Access, RIS Dataview or RIS Report Writer are all supported by this processor. Any RIS-supported relational database, either local or remote, is supported.

Usage:

dba_rpt [-?] -s <schema> -l<template library>[-t<template>|-M<menu template>] -w<where clause> -o<output file>-S<schema list> [-F<database find>] [wtr_p0]...[wtr_p5]

[-?] Returns a usage statement like the one listed above.

-s <schema name> This is the name of any current RIS schema, It is used as a "default"schema to enter DB Access. It doesn’t have to be the schema yourreport is running off of.

-l <template library> This is the library of templates created to run reports from. Createdthrough DB Access, Project Dataview, or RIS Report-Writer this isyour report source code, layout, and print conditions.

-t <report template> The name of the report you wish to run from your report templatelibrary.

-M <menu template> The name of the menu you wish to run from your menu templatelibrary.

-w <where clause> Used to restrict the report output to a certain type of condition, i.e."where name = ’joe smith’ and number = 32".

545

EE Raceway Modeling Reference Guide - February 2003________________ -o <output filename> All reports have a hardcoded, default file name that they write to. If

you wish to override this name, the "-o" option can be used. (Thecurrent standard is that the output filename be the same as the templatename, with a ".rpt" added to the end.)

-S <schema list> This is the list of schemas your report actually runs through. *

-F <database find> selects one character string from the database based on the selectstatement entered (i.e. "select value_a from table_bwhere....") and places the result into the third parameter (wtr_p2))

[wtr_p0]...[wtr_p5] These are parameters that can be passed to a report template, andreferenced by the literal string "wtr_p0"... The first parameter is readinto wtr_p0, etc. up to a maximum of six parameters (wtr_p5).

When you create a template, and use a schema from the schema list, whatever thatschema’s position was in that list (first, second, third, etc.) the report template will lookat the schema in that same position when it is executed. Thus, be careful of how yourlist looks before you develop a report template.

Certain variables may be exported, and will be picked up as defaults if switches are not used. Theyare:

DBA_SCHEMA (the "-s schema". A default schema used to enter RIS)DBA_SCHEMA_LIST (schema list the report runs off of) *DBA_LIB (the report template library)

It is useful to export these variables before entering DB Access, RIS Dataview or RIS Report-Writer tocreate or alter existing templates.

* (The schemas in this list need to be in the same order as they were in DBA_SCHEMA_LIST whenthe report was originally developed. The correct order is <project schema> <referenceschema>, since all EE Raceway reports were developed with the project schema listed first and thereference schema listed second. Example: "-S prj_schema ref_schema".)

546

J: Rep

orts

Appendix J: Project Drawing List (drwlst)________________

Project Drawing List (drwlst)

This report lists all drawings currently loaded in the project database, and sorts them by sheet name.

Information Output:

Drawing.drawing_type, filename, sheet, load_date, ref_db.

Sorted by (Highest to lowest priority)

drawing.sheet

Associated Software/Files

1. Project Database

2. drwlst (RIS) - a template in the $EE_RWAY/report/rwaydba_lib template library data file.

This file: Selects the desired database tables;Selects the desired columns from those tables;Sorts the information according to given sort parameters and;Formats information into readable form.

3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_libdrwlst template.

547


Material Takeoff Report (mto_rpt)

This report outputs information from both the straight and the fitting tables, and outputs the related system namefor the particular straight or fitting.

Information Output:

System.system_name

Straight.ee_ol_type, ee_tl_length, ee_out_width, ee_out_ht_diam, ee_part,description

Fitting.ee_ol_type, ee_tl_type, ee_tl_subtype, ee_out_width,ee_out_ht_diam, ee_part


1. Project Database

2. mto_rpt - a template in the $EE_RWAY/report/rwaydba_lib template library data file.


3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_libmto_rpt template.

548

J: Rep

orts

Appendix J: Raceway Bill of Materials Report (rway_bom)________________

Raceway Bill of Materials Report(rway_bom)

This report adds the length of the straight sections for each part ID, and outputs the number of fittings for eachpart ID. For flexible conduit elbow fittings, the length of the elbows is added to the straight sections.

Information Output:




1. Project Database

2. rway_bom - a template in the $EE_RWAY/report/rwaydba_lib template library data file.


3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_librway_bom template.

549


Raceway Bill of Materials by VolumeReport (rway_bom_vol)

This report adds the length of the straight sections for each part ID, and outputs the number of fittings for eachpart ID. For flexible conduit elbow fittings, the length of the elbows is added to the straight sections. Theoutput is only for a specified volume from the input parameters.


When running a Bill of Materials by Volume report, you are required to define a low and high range in PDScoordinates. These low and high ranges define a cubic volume from which the report is pulled.

Any Raceway component extending outside the clipping volume defined by the High and Low RangeCoordinates will not be included in the report output.

You can find the coordinates you want to use by using the active point coordinate display on the precision inputform. The coordinate values need to be in subunits and entered in the form field with a space between thecoordinates: easting northing elevation For example, 234 532 34

It should be understood that westing and southing coordinates must be the negative of theiropposite directional coordinate. For instance, a westing coordinate of 100 should be keyed in asa value of -100 in the easting direction, and a southing coordinate of 3000 should be keyed in asa value of -3000 in the northing direction.

550

J: Rep

orts

Appendix J: Raceway Bill of Materials by Volume Report (rway_bom_vol)________________

Information Output:




1. Project Database

2. rway_bom_vol - a template in the $EE_RWAY/report/rwaydba_lib template library data file.


3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_librway_bom_vol template.

551


Raceway Blank Part IDs (blank_ids)

This report outputs information from both the straight and the fitting tables whose part id (ee_part) informationis blank, and outputs the related system name for the particular straight or fitting.

Information Output:

System.system_name




1. Project Database

2. blank_ids - a template in the $EE_RWAY/report/rwaydba_lib template library data file.


3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_libblank_ids template.

552

K: R

IS S

chem

a M

gr.

Appendix K: RIS Schema Manager________________

Appendix K RIS Schema Manager

The RIS Schema Manager is a stand-alone utility for creating, changing, and dropping RIS schemas. Itcan also be used to display information about any existing schemas. You can access RIS SchemaManager from EE Database Utilities or by clicking Start > Programs > RIS version number > RISSchema Manager. This form consists of a list of all the schemas known to RIS and several buttonscorresponding to the actions of the Schema Manager. If you select any of the buttons, RIS initiates thatparticular action by displaying one of the forms defined below. If you select one of the schemas in thelist, then information about that schema is displayed.

When you select Reset, any active secondary forms are erased, and the RIS Schema Manager rereadsthe risschema file. When you select Cancel (X), RIS Schema Manager terminates.

For more detailed information on the RIS Schema Manager, refer to the Relational Interface System(RIS) Reference Guide.

553


Schema Information Form

This form is, with the exception of the Schema Name field, a read only form. It reads informationabout existing schemas. You can specify a schema in two ways: either by keying in the schema namein the Schema Name field, or by choosing a schema from the list on the RIS Schema Manager form.

Selecting Cancel (X) exits the Schema Information form.

554

K: R

IS S

chem

a M

gr.

Appendix K: Create Schema Form________________

Create Schema Form

This form creates new RIS schemas, and corresponds directly to the RIS create schemastatement. You can enter database-specific information on the Create Schema form using one of threemethods:

1. Key in all information in the input fields. This is your only alternative if the schema is createdon a database which is unknown to RIS.

2. Select an existing schema on the RIS Schema Manager form. The database-specificinformation about that schema is entered in the Create Schema input fields. This method isparticularly convenient when creating additional schemas for a database.

3. Select the Display Databases button. A form listing all the known RIS databases is displayed.If you select one of the databases, information about that database is entered into the CreateSchema input fields.

Selecting the Local Machine button fills the Node Address field with the addresses of the localmachine.

Selecting the Force button forces the system to create the schema despite corrupted data or other errorsit may encounter.

To change the order of the Network Protocol fields, select one of the Network Protocol fields; itsvalue will be replaced with the value of the field below it. The value you selected originally moves tothe bottom of the list.

If the selected database type requires additional information, input fields for that information display.Once you have entered all necessary information, select Run to create the schema.

Selecting Reset clears all input fields on the form. Selecting Cancel (X) exits the form.

555


Drop Schema Form

This form drops RIS schemas. To select a schema to drop, either enterthe schema name in the Schema Name field, or select a schema fromthe list on the RIS Schema Manager form. Selecting Run drops theschema, while selecting Reset clears all the fields on the form.Selecting Cancel (X) exits the form.

Alter Schema Form

This form performs three functions: it modifies the schema password, theuser password, and the schema node. When you select one of these options,only those gadgets associated with the action are enabled.

To select the schema to be altered, either enter the schema name in theSchema Name field, or select a schema from the list on the RIS SchemaManager form.

You must enter both the original and new passwords to modify the schemapassword. To modify the user password, you need only to enter the newpassword.

To modify the schema node, enter the new addresses in the Node Addressfields. This action can also be used to change the order of the fields or tochange the order of the protocols. When you have entered all necessaryinformation, select Run to alter the schema. Selecting Reset clears all thefields on the form. Selecting Cancel (X) exits the form.

556

K: R

IS S

chem

a M

gr.

Appendix K: Data Definition Form________________

Data Definition Form

This form consists of a list of all the tables, views, andindexes defined for the schema specified in the schemaname field. The form buttons represent the datadefinition actions of the Schema Manager. Selectingany of these buttons initiates an action, and displays oneof the subforms defined in following sections. If theselected schema requires a password, then you mustenter it before the subforms (Create Table, DropTable, and Alter Table) will accept input.

Selecting Reset cancels any subforms, and clears thelist. Selecting Cancel (X) exits the Data Definitionform.

Table Information Form

This form displays the definition of the specifiedtable. The column position, column name, columntype, and whether or not nulls are allowed in thecolumn are displayed for each column in the table.

You can specify a table either by keying in the tablename in the Table Name field, or by choosing thetable from the list on the Data Definition form. Afield to search for a specific column is also provided.Selecting Cancel (X) exits the Table Informationform.

557


Create Table Form

This form creates tables in the schema specified on the Data Definition form.

If the name of an existing table is entered into the Table Name field, or chosen from the liston the Data Definition form, the definition of that table will be loaded into the Create Tableform. This can be useful when creating several similar tables.

This form has two sets of Control buttons. There is the usual set, in the upper right corner ofthe form, which behaves as expected. Then there is the second set, referred to as the ModeControl buttons, which is used to execute and reset the different modes of the form. TheCreate Table operates in three modes which are represented by the three buttons: InsertColumn, Drop Column, and Modify Column. These three buttons place the form in aparticular mode, while choosing the Mode Run button actually causes the action to takeplace. Selecting the Mode Reset button clears the form mode.

In Insert Column Mode, new columns can be added to the table definition. If a column ischosen in the table definition list, the new column is inserted in front of the chosen column.Otherwise the new column is appended to the list. Select the Mode Run button to insert thecolumn.

In Drop Column Mode, columns can be dropped from the table definition. The column to bedropped must be specified by keying in the column name in the Column Name Search field,or by selecting the column in the table definition list. Select the Mode Run button to drop thecolumn.

In Modify Column Mode, column definitions can be modified. The column to be modifiedmust be specified by keying in the column name in the Column Name Search field, or byselecting the column in the table definition list. Select the Mode Run button to modify thecolumn.

Once the table definition is complete, select Run to create the table. Select Reset to clear theform. Select Cancel (X) to exit the form.

The Create Table form is used only to create new tables. It cannot be used to modifyexisting tables. The ability to load existing table definitions into the form exists just toprovide a template or starting point for a new table.

558

K: R

IS S

chem

a M

gr.

Appendix K: Create Table Form________________

Drop Table Form

This form drops tables in the schema specified on the DataDefinition form. The table to be dropped can be specified bykeying in the table name in the Table Name field or by selectingthe table from the list on the Data Definition form. Selecting Rundrops the table. Selecting Reset clears the form. Selecting Cancel(X) exits the form.

Alter Table Form

This form alters existing tables in the schema specified on the Data Definition form. Thisform behaves in the same way as the RIS Alter Table command. It can only append onenew column to an existing table.

Once the new column is defined, select Run to alter the table. Selecting Reset clears theform. Selecting Cancel (X) exits the form.

559


Schema File Form

This form locates the risschema file that you are using on the network. Additionally, itprovides a Checksum Schema File option, an error-checking mechanism that ensures that thedata EE reads from a remote risschema file is correct.

Selecting Reset clears the form. Selecting Cancel (X) exits the form.

Set Form

This form allows you to toggle the database mode ANSI setting on and off, and it also allowsyou to specify which RDBMS(s) your schemas can use. Selecting Reset clears the formsettings. Selecting Cancel (X) exits the form.

560

L: S

chem

a D

efinitio

n

Appendix L: RIS Schema Definition File________________

Appendix L RIS Schema DefinitionFile

The RIS schema definition file maintains all schema definitions known to RIS. It is stored in a centrallocation on the network and is used by all RIS client programs to ensure that all RIS clients use thesame set of schema definitions.

Although you can use multiple files, it is still advisable to use only one schema file.Multiple files often result in a large number of inconsistencies.

Access to the schema file is controlled by the presence of another file. This file is the schema lock file.The name of the schema lock file is the same as the schema file with the addition of the .LCKextension. The schema file is accessible only if the schema lock file exists. If the lock file does notexist, then the schema file is in use. Sometimes when RIS is abnormally terminated, the schema lockfile is not replaced as it should be. In these cases, the lock file must be replaced manually.

The location of the schema definition file must be in the ris/parameters file on the client machine. Theparameters file describes the network address and filename of the schema definition file. Thelocate schfile command in the interactive utility can be used to put the appropriate entry in theparameters file.

If there is no network address given, the schema definition file will be created or used on the localmachine.

If the filename is not a full pathname, RIS will look for the file in the directory where RIS wasinstalled on the given machine.

The parameters file is shipped with a default schema definition file specification, referencing the filerisschema in the directory where RIS was installed.

The schema definition file consists of database and schema entries which are associated by a DBID(database ID) key value. There can be multiple schema entries for each database entry. A lineseparates entries. Here is a description of the fields in the schema definition file:

DBID The database ID; a unique key to identify the databaseDTYPE The database type; currently supported values are X for

Informix, I for Ingres, O for Oracle, and D for DB2DBNAME The database name as in the create schema statement. It must

be a name or pathname as required by the dbms.PARMS The values found in the create schema option clause.PROTOCOL The communication protocol to be used to communicate with

the database. Currently supported values are X for XNS, T forTCP/IP, D for DNP (DECnet), L for LU6.2

NETADDR The network address (must be an address, not a name)SCHNAME The name of the schemaUSR The database user nameUSRPASS The database user password (encrypted)

561

EE Raceway Modeling Reference Guide - February 2003________________ ARCH The system architecture that the RIS/DBMS runs on. This

value is case-sensitive. The valid value is s370 and the defaultvalue is s370.

OS The operating system that the RIS/DBMS uses. This value iscase-sensitive. The valid value is mvs and the default value ismvs.

ENV The environment that the RIS/DBMS uses. This value iscase-sensitive. The valid value is cics and the default value iscics.

NET_PROTOCOL The network protocol that RIS uses to get to the IBM machinewhere the DBMS resides. This value is case-sensitive. Thevalid value is lu6.2 and the default value is lu6.2.

RIS_LU orHOST_LU

the name of the Clipper System Administrator assigned to thelogical unit that allows communication to the RIS program onthe IBM machine. There are two logical units, one on theClipper, the other on the IBM. The LU names are generatedwhen RIS is installed. This value is case-sensitive.

MODE The name the Clipper System Administrator assigned to themode that allows communication to the RIS program on theIBM machine.

HOST_PROGRAM The name the IBM System Administrator called the RISserver when it was installed on the IBM, the CICS transactionname.

A schema file must be readable and writable by all users. All users must be able tocreate and delete files in the directory where the schema file is located.

Following is a sample schema definition file:

CHECKSUM:1249378903TIMESTAMP:728930074——————————————————————————–DBID=2DTYPE=XDBNAME=/usr/ee/sample_refPROTOCOL=XNETADDR=0001349b.08-00-36-32-e4-00PROTOCOL=TNETADDR=129.135.142.155PROTOCOL=NETADDR=PROTOCOL=NETADDR=DIR=/usr/informixSQLEXEC=DBTEMP=TBCONFIG=——————————————————————————–DBID=1DTYPE=XDBNAME=/usr/ee/samplePROTOCOL=XNETADDR=0001349b.08-00-36-32-e4-00PROTOCOL=TNETADDR=129.135.142.155PROTOCOL=

562

L: S

chem

a D

efinitio

n

Appendix L: RIS Schema Definition File________________ NETADDR=PROTOCOL=NETADDR=DIR=/usr/informixSQLEXEC=DBTEMP=TBCONFIG=——————————————————————————–SCHNAME=sample_refUSR=eeUSRPASS=pz_-!=%#oa/#@?%qHt%h&jXJ2vj(tyeY%i)pVBEGIN_GRANTEESEND_GRANTEESDBID=2——————————————————————————–SCHNAME=sampleUSR=eeUSRPASS=’<j8,H:.zW%wU5yg)U:IeK9tGB6R@Ezn:˜>’kBEGIN_GRANTEESEND_GRANTEESDBID=1

Note that there is a list of protocols in the database entry. This allows for additional protocols in thefuture. Currently, only the first protocol in the list will be used.

All these entries are created by the create schema statement. If the file is corrupted or removed,they can be recreated by reissuing the create schema statements.

563


564

M: E

E M

anag

er

Appendix M: EE Manager________________

Appendix M EE Manager

EE Manager is an environment created specifically for system manager functions. It is a processseparate from the EE environment and should only be run by a system manager or by someone whohas a working knowledge of the overall EE system.

To run EE Manager, the environment variable SYS_PASSW_FILE must be set to a complete path ofa password file. For detailed information on setting environment variables, see Appendix N.

SYS_PASSW_FILE=d:\users\EEpasswd

where \users is the path and \EEpasswd is the password file name. The password file will be createdthe first time you enter EE Manager using the file name you specified. Make sure the directory pathto the password file exists. Once SYS_PASSW_FILE is set, double click on the EE Manager icon todisplay the Verify Password form.

EE Manager will prompt you for a password and, if you are entering the environment for the firsttime, will prompt you to re-enter the password for verification. Once you have successfully enteredyour password, the EE Manager form displays:

565


The password can be a maximum of 8 characters and is not case sensitive.

In this Appendix

Edit Database edits any schema that exists in the RIS dictionary. It uses DB Access to queryand edit tables, delete rows, and update rows.

566

M: E

E M

anag

er

Appendix M: Database Edit Functions________________

Database Edit Functions

To enter the Database Edit environment, select and confirm the Edit database option from the SystemManager menu.

Buttons at the bottom of the Database Edit form provide functions for manipulating the attached relationaldatabase. These buttons include various Query functions, which allow you to search the database, and functionswhich enable you to change, delete, and insert a row or group of rows.

A group of rows that match the current "query" criteria is called a universe. A universe is located by selectingProcess Query in the Database Edit environment.

Field Descriptions

Initialize Query — Initializes (clears) the current find criteria.

Edit Query — Displays the Edit Query screen, which shows the current find criteria. From this screenyou can edit the current find criteria, save the current find criteria as a file to the attached library, or loadfind criteria from a file in the attached library.

Current Row — Controls the display of rows in the current universe. Select the arrows to move forwardand backward through the rows in the universe. To go directly to a certain row, place the screen cursor onthe slide bar button, press and hold the middle button on the mouse and drag the button. The number onthe button changes to reflect the row. Release the mouse button to display the row. You can place thescreen cursor at any point along the slide bar and press <D> to move the slide bar button directly to a newrow, or edit the value displayed in the field.

Process Query — Searches the database to find all rows of the current table that meet the find criteria. Ifno find criteria exist, this command finds all rows in the current table.

567

EE Raceway Modeling Reference Guide - February 2003________________ Review — Generates a formatted column-by-column listing of the current universe. You can generate areview for all rows with database linkages to graphic elements within a fenced area in a design file.

Update Active — Lets you enter data without changing the displayed row in the database. When youselect Update Active, you can enter data on the displayed row without changing the database. When youare certain the data is correct, you can use the Insert Row command to add the displayed data as a row tothe database. You can also use the Update Active command to enter information for a new row whenattaching new linkages in graphics.

Fields On/Off — Toggles all column fields ON or OFF. You can toggle individual fields ON or OFF byselecting the field’s corresponding column name on the Database Edit screen.

Add Query — Used with the AND/OR toggle and relational operators to establish find criteria.Selecting Add Query puts the screen in Add Query mode. As long as this command is active, any key-inin the screen menu is added as find criteria and is NOT made as a change in the database. RelationalOperators let you search for ranges of column values such as greater than and less than. The field underthe AND/OR toggle lets you edit the active relational operator. You can either edit the displayed value orselect the right side of the field (a small box with dashes). A box containing a list of the various relationaloperators displays. You can select a relational operator from the list to make it the active relationaloperator.

The following are the available relational operators:

= : equal to (default)!= : not equal to< : less than> : greater than<= : less than or equal to>= : greater than or equal to!! : substring search

The AND/OR toggle lets you establish either a logical AND or OR operation. AND finds any rows thatcontain both the previous find criteria and any current column value you specify. OR finds any row thatcontains either the previous find criteria or any current column value you specify. Multiple columnsearches are processed in order, with logical AND having precedence over logical OR.

Change All — Changes the value for one or multiple columns for all rows in the current universe.

Change Row — Activates the Change Row mode, which overrides the key-in mode for Key Columns,Add Query columns, and Update Active fields. Fields with these key-in modes are placed only whenyou customize a screen menu. By default, the Database Edit screen has only Change Row fields.

Insert Row — Inserts a new row based on the column values for the displayed row.

Insert Row will not create a new row if a column is a SERIAL column (INFORMIX) or if it has aUNIQUE INDEX and a displayed column value duplicates the value for an existing row. You can use theUpdate Active command to enter the column values you want for a row and then Insert Row to create arow with the displayed information.

Delete All — Deletes all rows in the current universe from the database upon user verification.

568

M: E

E M

anag

er

Appendix M: Database Edit Functions________________ Delete Row — Deletes the displayed row from the database upon user verification.

569


570

N: E

E C

on

figu

re

Appendix N: EE Configure________________

Appendix N EE Configure

EE Configure is a process created specifically for setting environment variables for EE Raceway on aWindows NT platform. This process is separate from EE Environment and allows changes to the valueof a variable in the ee.cfg file. Double-click on the EE Config icon to display the Configure EEEnvironment form.

Field Descriptions

Enter the EE File Name — The field below this label contains the complete path and filenamewhere the current configuration file ee.cfg is located.

User Environment Variables — The list below this label contains the list of all theenvironment variables along with their path.

Variable — The field next to this label displays the Environment Variable name when any rowis selected in the list menu.

Value — The field next to this label displays the value of the Environment Variable when anyrow is selected in the list menu.

Descrip — The field next to this label displays the description associated with the selectedEnvironment Variable.

Set — The Set button writes the corresponding variable and its value to the list.

Delete — The Delete button deletes the corresponding variable and its value from the list.

Reset — The Reset button writes the contents of the ee.cfg file to the list.

571

EE Raceway Modeling Reference Guide - February 2003________________ Browse — The Browse button lets you select the required ee.cfg file.

Steps

1. Double click on the EE Configure icon, the Configure EE Environment form displays the listof user environment variables and their corresponding value.

2. Select the environment variable you want to change from the User Environment Variables list.

3. The name of the environment variable appears in the Variable field. This same field can beused to add a new variable.

4. The corresponding value of the environment variable appears in the Value field. Thedescription, if any, appears in the Descrip field.

5. Edit the entry in the Value field.

6. Click on the Set button to accept the new value. The User Environment Variables list nowcontains the new value for this variable.

7. To delete the variable, click on the Delete button. The variable will no longer appear in the UserEnvironment Variables list.

8. To edit the values of other variables, continue the same process as above. When complete, clickon OK to accept the changes and to overwrite the ee.cfg file. Click on Cancel to disregard anychanges.

572

N: E

E C

on

figu

re

Glossary________________

Glossary

absolute path name The sequence of directories, beginning with the root directory (/) thatlocates a file. See also path name and relative path name.

active depth The plane in a 3-D design upon which you can place elements and performmanipulations.

active process The process which is displayed in the Process ID field; it controls themessage fields, the menus, and the keyboard. The active process has ahighlighted window icon strip.

application software Software designed to meet specific needs, unlike system software whichruns other software.

batch processing A method of processing data which collects a series of operations into agroup (or ‘‘batch’’) and executes the group in a continuous stream withoutuser intervention.

batch queue A queue, or channel for moving requests, created through NQS. A batchqueue handles scheduling for processes submitted through the Batchoptions screen menu.

branch point A point on a pipeline which separates piping segments so that they can beassigned different segment parameters. A branch point allows forplacement of branch components.

cancel button The button located in the upper right corner of a form containing a red X orthe word cancel. Select the cancel button to exit the form or option.

cell A permanent association of elements that can be stored and placed as agroup, and then manipulated as individual elements.

character A column data type that stores alphanumeric character data.

client In network operations, a node which accesses data or performs a function onthe remote resource (usually a server). All network operations (database,NFS, NQS) between two or more nodes establish a client/serverrelationship.

column An attribute of a database table. A group of columns defines a table in adatabase.

command Instructions from the user to perform a function on specified data.

confirm button A button that appears in the upper right corner of a form and contains agreen check mark or the word confirm. Select the confirm button to initiatea specified option.

573


coordinate The location of a point along the X, Y, or Z axis.

coordinate system A geometric relation used to denote the location of points in the designcube. The most common coordinate system is the rectangular coordinatesystem, whereby points are located by traversing the X, Y, and Z axes of thedesign cube. Normally, coordinate systems have their origin defined as0,0,0, though this is not required. Other coordinate systems are used to moreeasily express the coordinates of specific geometric entities. For example,you can use a spherical coordinate system to help define points on a sphere,and you can use a cylindrical coordinate system to help define points on acylinder.

coordinates An ordered set of absolute or relative data values that specify a location in acoordinate system.

core files The image files written by System V for a number of reasons, the mostcommon of which are memory violations, illegal instructions, bus errors,and user-generated quit signals.

cursor The pointer that the user moves on the screen to indicate an item or area.

data button The mouse button used to place data points and tentative points, to acceptpreviously selected elements, and to select commands from forms andmenus.

data entry field The field on a screen used to accept user-supplied data. Also known askey-in field.

data point A point placed by pressing the data button on the mouse. Data points selectcommands from the panel menus and Menu Bar, place elements, identifyand accept elements, and activate windows and perform windowmanipulations.

database A collection of comprehensive informational files having predeterminedstructure and organization that can then be communicated, interpreted, orprocessed by a specific program.

database table The part of the database that is made of rows and columns and containsinformation about the project and design elements.

default The predetermined value of a parameter that is automatically supplied bythe system or program whenever a value is not specified by the user.

delete To remove, destroy, eliminate, or erase.

delimiter A separating mark or space; a character or sequence of contiguouscharacters that mark the end of a string of characters.

device A nonaddressable component of a network, that is, a component onto whicha user cannot log, for example, tape drive, disk drive, and floppy disk.

574

N: E

E C

on

figu

re

Glossary________________

directory A file that contains the names of other files.

display-list box A small box with horizontal dashes located at the end of a form key-in field.When selected, a list of the data available for that field is displayed. Inputcan then be selected from the list with a data point instead of keying in theinformation.

domain The set of acceptable values for a value within a component.

dragging Another term for the dynamic function that attaches the cursor to an elementso you can see it move.

easting A term used in plane surveying that describes an east, or positive, differencein longitude.

entity An object (project, drawing, element, and so forth.) of interest about whichinformation is stored; a relational database table.

envelope file See interference envelope.

file specification A path name that tells the system where to locate a file.

filename A user-defined name given to an interactively created file. The name shouldbe relevant to the contents of the file.

form An interface or screen menu designed with the I/FORMS product. Becausemany of the screen menus in the application software are built withI/FORMS, you must have the FORMS_S product on your workstation.

full path name The name of the entire path or directory hierarchy to a file, including the filename. See also relative path name.

gadget A portion of a form, such as a button, a field, or a checklist, that responds toinformation. Gadgets can display default values or act as data entry areas.

header The first items of information in a file which precede any actual data. Theheader contains information on the structure and contents of the file.

hierarchy A classified structure with superiors (roots) and subordinates (dependents)for grouping files or commands.

icon A pictorial representation or image; a symbol that graphically identifies acommand.

Informix A relational database management system supported by RIS.

Ingres A relational database management system supported by RIS.

interference envelope An equipment modeling primitive or parametric component that is used inconjunction with or instead of model graphics for interference checking.Interference envelopes are given different levels and display symbology todistinguish them from primitives.

575


invert elevation The lowest point on the internal diameter of the pipe.

isometric Relating to or being a drafting system characterized by three equal axes atright angles; a view in which the horizontal lines of an element are drawn atan angle to the horizontal and all verticals are projected at an angle from thebase.

key An attribute (column) in a table which is chosen as the access vehicle toindividual rows of the table.

key-in field The field on a screen used to accept user-supplied data. Also known as adata entry field.

keypoint A point on an element, including vertices, to which you can snap.

keyword A word recognized by the software that provides access to a certainfunction.

menubar The strip at the top of the screen that contains icons for selectingcommands.

message area The area that appears in the MicroStation Command Window when you areworking in a design file. It is divided into the Command Status field, theCurrent Command field, the Prompt field, and the Key-in field.

model A graphic representation or schema.

network An interconnection of host computers and workstations that enables them toshare data and control. The term network can mean the devices that connectthe system, or it can mean the connected system.

NFS Network File System, the system that provides access to data that isdistributed among machines through an interconnection of host computersand workstations. NFS allows you to mount a remote resource to your localworkstation so you can access the data as though it were local. NFS isusually used to access centralized data on a server.

node Any addressable device (such as a workstation or a server) that is connectedto a network. The network enables the connected nodes to share data andsystem control.

node address The hard-wired Ethernet address assigned to each node when it ismanufactured. It is necessary for each node to identify and communicatewith another node in the network.

node name A name, or alias, that can be assigned to the node address of a device on anetwork.

northing A term used to describe a north coordinate location in the plant coordinatesystem.

576

N: E

E C

on

figu

re

Glossary________________

nozzle A special equipment modeling primitive that contains the connection pointto piping. This point does NOT include a gasket allowance, but ratherrepresents the face-of-flange coordinate.

NQS Network Queuing System, the software package that allows you to definenetwork-wide batch and device queues. Use of NQS involves setting uplocal resource queues on the system(s) where the resources reside andsetting up ‘‘pipe queues’’ on the systems that are to have access to theresources.

Oracle A relational database management system supported by RIS.

origin In coordinate geometry, the point where the x, y, and z-axes intersect.

origin point The point at which the coordinate system is placed.

orthogonal view A view which is a projection of the model onto a plane along lines whichare orthogonal to the plane.

parameter A property whose value determines the characteristics or behavior ofsomething.

path A sequence of directories leading to a file or a sequence of menus leading toa command.

path name The sequence of directories leading to a file. See also absolute path nameand relative path name.

PDS Plant Design System

pipe queue A controlled channel for moving requests to batch or device queues onremote systems and for receiving status and/or data in response.

place data point To identify a specific element, or indicate a specific point in the design file.

plane A spatial element in geometry that may or may not have a boundary, but islevel, having no elevations or depressions, and is three-dimensional.

RDB Reference Database.

reference database A collection of reference data containing information relative to industrydesign codes, vendor’s catalog data, job specifications, commodity libraries,graphics symbology, label descriptions, report formats and otherinformation of a similar manner.

relative path name The sequence of directories leading from the current directory to a particularfile. See also path name and absolute path name.

rotate To turn; to change the angular orientation; to transform by revolution abouta specific axis.

577


row A unit of related information in a table. One collection of column values fora table.

rubberbanding The animation dynamic that enables you to specify the position of a datapoint while the element changes as you move the cursor.

schema A description of the overall structure of the rulebase or database.

schema file A file that outlines the overall logical structure of a rule base or a database.

server In network operations, the node which maintains common data or performsa common task needed by clients. All network operations (database, NFS,NQS) between two or more nodes establish a client/server relationship.

Structured QueryLanguage SQL

Language developed by IBM for creating, modifying, and queryingrelational databases.

style The symbology of an element such as continuous dashes, dash-dot, solid,and so forth.

surface The skin of a three-dimensional geometric element.

symbology The display style of an element, including color, style, and weight.

table A collection of data for quick reference, either stored in sequential locationsin memory or printed as an array of rows and columns of data items of thesame type.

toggle To switch; to change between two alternatives.

user name A name that provides access to an account on the system.

values Data, either entered by the user or determined by the software, that arestored in an attribute.

variable A quantity that may assume any one of a set of values.

vector A quantity possessing both magnitude and direction, generally representedas a line. Vectors can be manipulated geometrically and are represented asa coordinate triple (x,y,z).

view The defined area of vision on a screen. A view allows you to see aprescribed volume of the design cube. Views are created with their own x,y, and z axes. The x,y plane of the view is parallel to the screen, while thez-axis can be thought of as coming straight out of the view towards you.The view axes maintain this relationship regardless of the rotation withrespect to the design cube. See also active depth.

virtual memory External memory for a computer that can be used as if it were an extensionof the computer’s internal memory. The software uses virtual memory tostore data. This means that unneeded files and data, stay on the disk untilthey are called for. Because the internal processing memory stores aminimal amount of data, the software can perform processing more quickly.

578

N: E

E C

on

figu

re

Glossary________________

working directory The directory from which you are accessing files.

579


580

N: E

E C

on

figu

re

Index________________

Index

Aaccess column 179, 234, 290activate

design volume coordinate system 320plant coordinate system 320

activeangle 256one-line type parameters

access column 290clear 291display toggle 290list column 290override 291save to memory 289select 290

parameters 146point

coordinates display 121define 145

active coordinate system 320add

query 568systems 245

airwayplace 132

alias.cmd 529, 539alter

schema form 556table form 559

angleactive 256

annotateelement 178

access column 179, 234by group 233clear button 180, 235display toggle 179, 234list column 179, 234override button 180, 235override keys 179, 234select button 180, 235source column 179, 234

model 285one-line 178, 233RCP 178

annot_form 529application

manager information 27, 109, 415, 425approval status codelist 432archive

form 46option 86

archive projectnetwork protocol

TCP/XNS 46remote node name/address 46

asid iddisplay 316highlight 309

assign 522, 527attributes

default 430setting raceway 256

automaticfit 151propagation 298size 151

Bbackground 522bar commands

palette 98basic

conceptsdatabase 115drawing 108propagation 113

setup 27, 110workstation skills 26

batch 522bill of materials 549

by volume 72, 327, 550bin/ 521, 527blank part ids 552

Ccable

code codelist 439color codelist 441configuration codelist 440insulation type codelist 444

581

EE Raceway Modeling Reference Guide - February 2003________________ cable (continued)

size codelist 440voltage codelist 443

cardinal point codelist 433cell

create commands 269drop point 277, 278, 279equipment pointer 274, 275, 276model 271

library 269, 271cfg/ 527change

all 568row 568

change system parameters 221changing

one-line type 294parameters

one-line type 289propagation 297raceway 256

symbology 264system 295

cleanupdatabase 340

clearannotate element 180, 235one-line type parameters 291

clip 522clone element 188

by group 239codelists 432

approval status 432cardinal point 433drawing type 433manual fitting 433one-line type 434RCP type 435system 435three-line

qualifier 437subtype 437type 436

units 438vendor 438wire/cable

code 439color 441configuration 440insulation type 444voltage 443

codelists (continued)wire/cable size 440yes/no 445

coincident RCP checks 209color

parameters 256combine coincident RCPs 209command

palettes 97command.msg 529commands

construct point 123extend/reduce run 125midpoint

on segment 123Commands

Integrated 368compile

eden symbol 349compress

eden symbol library 359conduit

place 132place stub up 167seamless tubing 114sizing 155

attributes 268config/ 522, 527construct point 123construction class

display 306control

number 165set symbology 262symbology 264

coordinatesystem

design volume 320plant 320show active 320

coordinate system 320coordinates

display 121copy

clone element 188by group 239

element 184by group 231

menu 43option 78

582

N: E

E C

on

figu

re

Index________________ create

cell 269drop point 277, 278, 279equipment pointer 274, 275, 276model 271

menu 39option 61schema form 555tables 558

drop mode 558insert mode 558modify mode 558

three-lines 194create_db 428, 522cross section

ductbank definition 164rotate 140rotation angle 256scale factor 256

crosses 195cutback mode 150

Ddata

definition form 557files 522, 527

database 321, 425cleanup 340edit 567

add query 568change all 568change row 568current row box 567delete all 568edit query 567initialize query 567insert row 568process query 567review 568toggle 568update active 568

load 323, 332batch file 335

palette 102procedures 427project 115reference 115relational 427report 326rule checks 329setup 33

database (continued)utilities 50

RIS schema utilities 51update project schema 52update reference schema 55

db/ 523, 528dba_rpt 522dba_shell 522DbEdit 567defaults

attributes 430raceway 256RCP key 257text 266

defineactive point 145duct cross section 164group 226one-line type 260parameters 146raceway defaults 256system 258

deleteall 568duplicate one-lines 211eden symbol 351element 212

by group 251fitting 216menu 44one-line vertex 217option 79RCP 214

designcommands 129conduit sizing 155define duct cross section 164file

command menu bar 96insert one-line vertex 160insert RCP 138option 63palette 99place

drop point 142equipment pointer 144manual fitting 147one-line 132

rotate cross section 140route around vessel 135set

583

EE Raceway Modeling Reference Guide - February 2003________________ design (continued)

set (continued)active parameters 146

unload 336design volume coordinate system 320dgn/ 528directory

structure 520display

annotation 306asid id 316construction class 306element information 301element type 316field 121link 317one-line type 318screen 93sector/word 315system 318toggle

annotate element 179, 234one-line type parameters 290

documentorganization 19outline 25purpose 19

downloading 29drawing

process 108setup 110type codelist table 433

droppoint

create cell 277, 278, 279keys 431place 142

schema form 556table form 559

ductbankcross section definition 164place 132

duplicate one-line checking 211DVCS 320

Eeden/ 528eden

example 514list functions 355mode 113

eden (continued)option 67

batch mode 69operating modes 68

processes 347compile symbol 349compress symbol library 359delete symbol 351edit symbol file 366extract symbol 361extract user function 363list symbol library 353list user functions 355merge symbol libraries 357

symbolcompile 349compress library 359delete 351edit file 366extract 361generation 513list library 353merge libraries 357processor file 513

user functionextract 363

eden.dat 528edit

eden symbol file 366manual fitting 198model annotation 285query 567

EEconfigure 571databases 425environment 35forms

archive 46restore 48

manager 565menus 36

copy 43create 39database utilities 50delete 44enter 40product menu 42

nucleusfile structure 520

racewayfile structure 524

584

N: E

E C

on

figu

re

Index________________ ee.bar 529eeconfig 522eemgr 522eeprj 522eeqpr 522EERWAY

command menu bar 96environment 59

create 61design 63eden 67


processes 64batch mode 66operating modes 65

reports 70rule checks 73utilities 75, 78, 79, 80, 81, 82, 83, 84, 86, 87,

89palette 97palettes 97

elbows 195elements

annotate 178by group 233

clone 188by group 239

copy 184by group 231

delete 212by group 251

display information 301highlight

by asid id 309by link 312by sector/word 307

identifying 103modify commands 173modifying 175move 186placing 129propagate 194

by group 241type

display 316engineering

units 267enter

menu 40

environmentEE 35EE Raceway 59variables 422

environment rules for fittings 446environments

graphicspalettes 97

equipmentpointer

create 274, 275, 276keys 431place 144

error.msg 529errors

messages 377propagation 314

extend/reduce run 125extract

eden symbol from library 361eden user function from library 363

Ffield routed raceway 161filename

highlightasid id 309

highlight link 312files

data 522, 527eden

symbol processor 513password 565purge 81rway.cmd 543seed

English 528metric 528

structureEE

nucleus 520EE raceway 524

fittings 195, 512delete 216edit/insert manual fitting 198environment rules 446place by rule 207

by group 243place manual fitting 147

floppy/network toggle 86

585

EE Raceway Modeling Reference Guide - February 2003________________ force 555forms/ 523forms

maximize/minimize 120precision input

customizing 417function

edenlibrary 355

Ggraphic

symbology 262, 264, 266graphics environment

palettes 97group

annotate 233copy 231define 226delete 251minimize joints 248propagate 241

Hhelp_graphics 528help_rway.hp 528help_rway.s 528help_source/ 528highlight

elementby asid id 309by link 312by sector/word 307

propagation errors 314horizontal spacing 165

Iidentifying

elements 103IGDS toggle 83increase size only 157increase/decrease size 157information about elements 301initialize query 157, 567input

precision 119insert

one-line vertex 160RCP 138row 568

installation 27databases 33downloading 29

Integrated Commands 368palette 97Using 369

interferencedetection 118, 342, 344

introduction 25

Jjoints

minimize 219by group 248

Kkey-ins

precision 104, 119keys 430

drop point 431equipment pointer 431one-line 430override 115RCP 431

Llevels

set active 299library

cell 269, 271eden symbol 353, 357, 359, 361eden user function 363eden user functions 355

linkdisplay 317highlight 312

listcolumn 179, 234, 290eden symbol library 353user functions 355

load 527database 323, 332

batch file 335lock model 282

Mmain form

EEarchive 46restore 48

586

N: E

E C

on

figu

re

Index________________ main menu

EE 36copy 43create 39database utilities 50delete 44enter 40product menu 42

EERWAYcreate 61design 63eden 67processes 64report 70rule checks 73utilities 75

manual fittingedit/insert 198part codelist table 433place 147

material takeoff 548maximize form 120menu.cfg 527menus 91

command menu bar 96directory 528EERWAY command menu bar 96

menu_shell 522merge

eden symbol libraries 357merge_pnl/ 529merge_pnl 529messages

display fields 93error 377

MicroMenu umenu 543midpoint

on segment 123minimize form 120minimize joints 219

by group 248model

annotate 285move annotation 283

commands 280using 281

create model cell 271lock 282unlock 284

model commandspalette 101

modify 173add systems by group 245annotate element 178

by group 233clone element 188

by group 239combine coincident RCPs 209copy element 184

by group 231define group 226delete

duplicate one-lines 211element 212

by group 251fitting 216one-line vertex 217RCP 214

edit/insert manual fitting 198elements 175group commands 223

define group 226minimize joints 219

by group 248move

element 186one-line segment 190one-line vertex 192

one-line route 204palette 99place fitting by rule 207

by group 243propagate element 194

by group 241reference schema 451remove RCP 214replace systems by group 246

modify elementpalette 98

modify grouppalette 100

moveelement 186model annotation 283move/move to toggle 121one-line segment 190one-line vertex 192

mscrecol.sh 522msg/ 523, 529mslink

display 317highlight 312

587

EE Raceway Modeling Reference Guide - February 2003________________ msseed.dgn 528mstr_rway.hp 528mstr_rway.s 528

Nnetwork/floppy toggle 86new users

database preparation 427nucleus

file structure 520

Oone-line

annotate 233changing sizes 178, 233delete

duplicates 211vertex 217

insert vertex 160keys 430modify route 204move segment 190move vertex 192place 132route around vessel 135type

codelist table 434define 260display 318parameters 289

access column 290clear 291display toggle 290list column 290override 291override keys 290save to memory 289select 290

priority 434set active 294

types 110output option 89override

buttonannotate element 180, 235

keys 115, 179, 234, 290one-line type

parameters 291setting 263

Ppalettes

bar commands 98database 102design 99EERWAY 97Integrated Commands 97MicroStation commands 98model commands 101modify 99modify element 98modify group 100runtime setup 101setup commands 100utilities 102

parametersactive 111active angle 256color 256one-line type 289

access column 290clear 291display toggle 290list column 290override 291override keys 290save to memory 289select 290

propagation 297raceway 256set active 146, 289

part verification 297password

echo toggle 46, 48, 52, 55file 565

PCS 320PDS

reference model from 372review attributes 371review clash 375window to named PDS item 374

percent fill 157percentage of raceway

changing 221place

drop point 142equipment pointer 144field routed raceway 161fitting by rule 207

by group 243manual fitting 147

588

N: E

E C

on

figu

re

Index________________ place (continued)

one-line 112, 132RCP 138stub up 167

placepoint 150plant coordinate system 320precision

input 119active point

coordinates display 121construct point 123customizing 417display fields 121extend/reduce run 125midpoint on segment 123move/move to toggle 121

key-ins 104prerequisite 26print.dat 522, 536priority 434procedures 107process query 157, 567process.dat 528, 533processes 331

cleanup database 340eden 347interference detection 342, 344load database 332

batch file 335option 64


unloaddesign 336sheet 338

processing toggle 53, 55, 65processor

file 513product

menu 42removal 521, 527

product.def 521, 527project

database 115schema description 487

drawing list 547schema

general description 448update 449

prompt.msg 529

propagate 113automatic propagation 298element 194

by group 241fittings 195highlight errors 314modes 297

eden 113, 297sketch 113, 297

parameters 111part verification 297setup 297style 297

purge option 81

Qquery

add 568edit 567initialize 567process 567

Rraceway

defaultsset 256

field routed 161processes 331

RCPs 112combine coincident RCPs 209default key 257delete 214insert 138keys 431type

codelist table 435weight 257

README 521, 527receive

option 84reduce run 125reducers 195reeprj 522reference

database 115schema description 454

guide 25schema 510

description 430modifying 451updating 449

589

EE Raceway Modeling Reference Guide - February 2003________________ reference PDS model 372relational

databases 427interface system (RIS) 426

report processing 545relational interface system (RIS)

alter schema 556alter table 559data definition 557drop schema 556drop table 559schema creation 555schema file 560set 560table creation 558table information 557

removeone-line vertex 217RCP 214script 521, 527

renameoption 82

replace systems by group 246report.dat 528, 534reports 117, 545

bill of materials 549by volume 72, 327, 550

blank part ids 552database 326directory 529material takeoff 548option 70project drawing list 547templates 546

restoreform 48option 87

restore project from archiveTCP/XNS toggle 48XNS/TCP toggle 48

reviewPDS attributes 371PDS clash 375

RIS 115, 426procedures 427schema manager 553

alter schema form 556alter table form 559create schema form 555create table form 558data definition form 557

RIS (continued)schema manager (continued)

drop schema form 556drop table form 559force 555schema file form 560schema information form 554set form 560table information form 557

schema utilities 51rotate

cross section 140orientation 151

rotation anglecross section 256

rule checksdatabase 329option 73templates 546

rule_chk.dat 528, 535runs 112runtime setup 287

display element information 301palette 101propagation setup 297set active

levels 299one-line type 294one-line type parameters 289system 295

rway_bar 528rwaybar.sym 529rway.cmd file 543rway.cmds 528rwayh_pnl 529rway.pnl 529rwaypnl.sym 529rway_prj.tbl 529rway_ref.tbl 529

Ssave to memory 289scale factor

cross section 256schema 115

create 555definition file 561

fields 561description 454, 487drop 556file 560

590

N: E

E C

on

figu

re

Index________________ schema (continued)

information form 554modifying reference 451names 450project 448reference 430update 428, 449

project 449reference 449

utilities 51screen

display 93seamless tubing 114sector/word

display 315highlight 307

seed/ 528seed.dgn 528select

buttonannotate element 180, 235

one-line type parameters 290send

option 83set 560

activelevels 299one-line type 294one-line type parameters 289parameters 146point 145system 295

conduit sizing attributes 268defaults 256symbology control 262text defaults 266

setupcommands 253conduit sizing attributes 268create cell 269define

one-line type 260system 258

lock model 282model 280model annotation 285

move 283propagation 297set

raceway defaults 256symbology control 262

setup (continued)set (continued)

text defaults 266symbology control 264system manager 27, 109unlock model 284

setup commandspalette 100

sheetunload 338

showactive coordinate system 320

sizechanging one-line size 178, 233

sizing conduit 155sizing attributes 268

sketchmode 113

skillsworkstation 26

softwaredownloading 29

source column 179, 234SPEC process 507specification 507specification tables 510start-up sequence 92status.msg 529straights 195structure

EE Raceway 524file 520

stub up 167subsystems 295sym/ 523, 529symbol

edencompile 349compress 359delete 351extract 361list library 353merge libraries 357

fileedit eden 366

generation 513example 514

processor file 513symbology 110

changing 264control 264

591

EE Raceway Modeling Reference Guide - February 2003________________ symbology (continued)

control (continued)set 262

system 110, 295add 245codelist table 435define 258display 318manager information 27, 109, 415, 425replace systems group 246set active 295

system percentagechanging 221

Ttables

codelists 432information form 557

TCP/XNS protocolarchive project 46

TCP/XNS togglerestore project from archive 48

templatesreports 546rule checks 546

textdefaults 266

set 266text nodes 266text strings 266

nodes 266strings 266

three-linecodelist table 436create 194qualifier codelist table 437subtype codelist table 437

tmp/ 529toggle

construction display on/off 306IGDS 83network/floppy 86password echo 46, 48, 52, 55processing 53, 55, 65

toolsreference PDS model 372review PDS attributes 371review PDS clash 375window to named PDS item 374

trayplace 132

tray_part table 511tray_spec table 510typefaces 21

Uumenu 543undelete 80units

codelist table 438engineering 267working 104

.unl files 509unload 527

design 336sheet 338

unlock model 284update

active 568schema 428, 449

project 52, 449reference 55, 449

upgradingworkstation 28

user functioneden

extract 363utilities 303

displayelement type and asid id 316link 317sector/word 315system and one-line type 318

highlightby asid id 309by link 312by sector/word 307propagation errors 314

option 75archive 86copy 78delete 79output 89purge 81receive 84rename 82restore 87send 83undelete 80

palette 102reference PDS model 372review PDS attributes 371

592

N: E

E C

on

figu

re

Index________________ utilities (continued)

review PDS clash 375schema 51toggle construction display on/off 306window to named PDS item 374

Vvendor

codelist table 438specification 507

vertical spacing 165vessel

routing around 135volume

bill of materials 72, 327, 550

Wweight

RCP 257window to named PDS item 374wire

code codelist 439color codelist 441configuration codelist 440insulation type codelist 444size codelist 440voltage codelist 443

wirewayplace 132

workflow 107databases 115drawing process 108drawing setup 110eden symbol generation 513one-line types 110parameters 111place one-line 112propagation 113propagation parameters 111reports 117setup 109, 110symbology 110systems 110

workingunits 104

workstationskills 26upgrading 28

wyes 195

XXNS/TCP toggle

archive project 46

593


594

EE Raceway Modeling Reference Guide Addendum February 2003 DPDS3-PB-200005C For PDS version 07.02.00.** This document supplements DPDS3-PB-200005B.

EE Raceway Modeling Reference Guide Addendum – February 2003

596

Table of Contents PDS Electrical Raceway Environment .................................................................... 597

Modeling......................................................................................................................... 598 Load Reference Schema ................................................................................................. 599 Utilities ........................................................................................................................... 601

Palettes in the EE Raceway Graphics Environment (replaces 5.4).......................... 602 Modify Element Commands (replaces 9.2) ............................................................. 607

Rotate Element................................................................................................................ 609 Rotate Copy Element...................................................................................................... 611 Mirror Element ............................................................................................................... 613 Mirror Copy Element...................................................................................................... 615

Modify Group Commands (replaces 9.3) ................................................................ 617 Rotate Group................................................................................................................... 619 Rotate Copy Group......................................................................................................... 621 Mirror Group .................................................................................................................. 623 Mirror Copy Group......................................................................................................... 625 Move Group.................................................................................................................... 627

Annotate Model........................................................................................................ 628 Reference PDS Model (replaces 16.2) ..................................................................... 629 EE Raceway Project Database Schema Description (replaces panel) ..................... 631 EE File Structure (replaces Appendix F) ................................................................. 633

EE Nucleus File Structure .............................................................................................. 634 EE Raceway File Structure ............................................................................................. 637

597

PDS Electrical Raceway Environment When you select the Electrical Raceway Environment command on the PD_Shell form, the EE Raceway Environment form displays.

Commands Modeling – Allows you to open a design file in the PDS Raceway modeling

environment.

Load Reference Schema – Allows you to update the Raceway reference schema.

Utilities – Allows you to access EE Raceway commands for EE Raceway processes, EDEN symbols, reporting, and rule checks.


598

Modeling This option allows you to select a design file to open in the modeling environment.

Steps 1. Select a design area from the list.

2. Click Accept.

The Raceway Designer form displays.

3. Select a model from the list.

4. Click Accept.

The selected model displays in MicroStation.

599

Load Reference Schema This option allows you to update the reference schema for the active project. You can use this command to update an existing empty RIS schema with EE tables and default information, or to modify the tables in an existing RIS schema to conform to the structure of a given .sql file. If you update the schema with a .sql file that has a different structure from the original .sql file, the command makes the following changes:

— Adds new tables listed in the .sql file.

— Modifies existing tables if the definition of that table has changed in the .sql file. The process replaces the old table definition with the new table definition, keeping column data where column names match.

— Load those tables that have unique index numbers with data from the .unl files that are listed in the .cmd files. If a table lacks a unique index, the process loads it only if the table is empty.

Field Descriptions Reference Schema – Specifies the reference schema for the active project.

SQL File Network Address – Specifies the network address of the SQL file containing the correct table and column structure.

SQL File Path – Specifies the file path of the SQL file containing the correct table and column structure.

SQL Filename – Specifies the file name of the SQL file containing the correct table and column structure.

CMD File Network Address – Specifies the network address of the CMD file that defines which .unl files to load into which tables.


600

CMD File Path – Specifies the file path of the CMD file that defines which .unl files to load into which tables.

CMD Filename – Specifies the file name of the CMD file that defines which .unl files to load into which tables.

601

Utilities This option accesses the EE Raceway Process, EDEN, Report, and Rule commands.

Commands Process – This command accesses all available EE Raceway processes. These

processes allow you to manipulate drawings and the project database. Refer to sections 4 and 14 of the EE Raceway Reference Guide for more information on this command.

EDEN – This command allows you to design and maintain your own symbols for Raceway elements. Refer to sections 4 and 15 of the EE Raceway Reference Guide for more information on this command.

Report – This command accesses the standard EE Raceway reports. These reports contain information on the project and reference databases. Refer to section 4 and Appendix J of the EE Raceway Reference Guide for more information on this command.

Rule – This command accesses the standard EE Raceway Rule Checks. These rule checks are reports that identify violations of certain design rules by working on the project database. Refer to section 5 and Appendix J for more information on this command.


602

Palettes in the EE Raceway Graphics Environment (replaces 5.4) Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 103-108 in the PDS 7.1 version of the document).

The following information has been modified:

• Rotate, Rotate Copy, Mirror, and Mirror Copy commands on the Modify Element and Modify Group palettes

• Move Group command on the Modify Group palette See the following text for details.

This section presents the palettes that are used in the EE Raceway graphics environment. Palettes are groups of commands that are accessible from the EERWAY command menu bar on the MicroStation command window. This section presents the palettes in the order that they are accessible if you look at each menu going from left to right across the EERWAY command menu bar on the MicroStation command window.

Next to each icon is the name of the form or command it represents. You should become familiar with the name and functionality of each command on each palette. Each command is described in full in later sections of this text.

EERWAY This palette is activated by selecting File from the MicroStation command window, then selecting EERWAY from the resulting menu.

Integrated Commands This palette is activated by selecting File from the MicroStation command window, then selecting Integrated Commands > Palette from the resulting menu.

603

Bar Commands This palette is activated by selecting File from the MicroStation command window, then selecting Bar Commands from the resulting menu. This palette contains the MicroStation commands as discussed in the MicroStation documentation.

Modify Element This palette is activated by selecting Modify Element from the EERWAY palette, or it can be activated by selecting Modify Element from the Modify palette as shown later in this section.

This palette can also be activated by selecting Modify from the MicroStation command window, then selecting Modify Element Commands from Modify menu, then selecting Palette.


604

Design This palette is activated by selecting Design from the MicroStation command window, then selecting Palette from the resulting menu.

Modify This palette is activated by selecting Design from the MicroStation command window, then selecting Modify from the resulting menu.

605

Modify Group This palette is activated by selecting Modify Group from the Modify Palette. You can also activate this palette by selecting Modify from the MicroStation command window, then selecting Modify Group Commands, then selecting Palette.

Setup Commands This palette is activated by selecting Setup from the MicroStation command window, then selecting Palette.


606

Model Commands This palette is activated by selecting Model Commands from the Setup Commands palette.

Runtime Setup This palette is activated by selecting Runtime from the MicroStation command window, then selecting Palette.

607

Modify Element Commands (replaces 9.2) Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 181-182 in the PDS 7.1 version of the document).


• Rotate, Rotate Copy, Mirror, and Mirror Copy commands See the following text for details.

The Modify Element palette is activated by selecting the Modify Element command from the Modify palette, or by selecting Modify from the EERWAY Command Menu Bar, then selecting Modify Element Commands, then selecting Palette.

The Modify Element commands manipulate individual elements, including RCPs, one-lines, and three-lines, within the design file. You can use individual commands to move, copy, and delete specified elements, to review or edit element annotation, and to check for duplicate one-lines and coincident RCPs in the design file. Modify Element commands also allow you to propagate one-lines in your raceway model.

Note: Do not use MicroStation commands to manipulate or modify EE Raceway elements (one-line, three-lines, annotation, and so forth). Doing so will cause serious problems and/or destroy the EE Raceway model. Use only these EE Raceway modify commands to manipulate EE Raceway elements.

Annotate Element — Places, reviews, and edits intelligent annotation for raceway elements.

Copy Element — Copies an element as specified within the design file.

Move Element — Moves an element to a specified location in the design file.

Clone Element — Copies an element multiple times in the same direction.


608

Move One-Line Segment — Moves a one-line segment while maintaining connectivity to existing elements.

Move One-Line Vertex — Moves an internal one-line vertex.

Propagate Element — Expands one-line elements into three-dimensional elements.

Edit/Insert Manual Fitting — Modifies fittings that were manually placed in the model.

Modify One-Line — Modifies the route of an existing one-line element.

Place Fitting by Rule — Places a non-standard fitting at an RCP using a set of rules defined in the reference database.

Check Coincident RCPs — Checks for coincident RCPs in the design file.

Check Duplicate One-lines — Checks for duplicate or overlapping one-lines in the design file.

Delete Element — Removes a valid raceway element, and elements associated with it, from the design file.

Remove RCP — Deletes a specified RCP (raceway connect point) from the design file.

Delete Fitting — Removes fittings from the design file.

Remove One-Line Vertex — Deletes an internal vertex from an existing one-line.

Minimize Joints — Reduces the number of vertices in an identified one-line to a minimum.

Change System Parameters — Changes the system percentage and the project rule for a selected element.

Rotate Element — Rotates an element to a specified location in the design file.

Rotate Copy Element — Copies an element and rotates the copy to a specified location in the design file.

Mirror Element — Flips an element about a specified point in the design file.

Mirror Copy Element — Copies an element and flips the copy about a specified point in the design file.

609

Rotate Element This command rotates individual raceway elements as specified within the design file. You can use this command to move one-lines, RCPs, drop points, equipment pointers, and annotation. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved.

If a one-line is rotated, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.

Field Descriptions Rotation Point – Displays the location of the rotation point.

Plan View – Specifies the angle at which to rotate the element on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point.

East Elevation – Specifies the angle at which to rotate the element on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point.

North Elevation – Specifies the angle at which to rotate the element on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point.

Angle – Key-in field used to specify the angle for each plane. To change the angle, click the button for the plane and type the angle in the Angle field.

Before Using This Command You can enter all values for the placement of points through a precision input form. Using the form, you can locate elements, route one-lines, accept input, reject input, reset a command action, and exit a command. You must be familiar with precision input and its functions before using this command. For detailed information about precision input, see Precision Input Form.


610

At any point during this operating sequence, you can exit the command session either by pressing <Esc> or by selecting Cancel (X) on the precision input form. To reset a command action by one step or to reject a highlighted element, press <R> or select Reject on the precision input form.

Steps 1. Select the Rotate Element command.

The Rotate Element precision input form displays.

2. Identify the element you intend to rotate and accept it with <D>.

The system highlights the specified element. If you do not locate an acceptable element, the system displays the message Element not found. The message disappears when you identify a valid element.

3. Specify the point around which to rotate the element.

The Specify Rotation form displays.

4. Specify the planes and angles at which to rotate the element.

5. Click Accept.

The element rotates to the specified position.

611

Rotate Copy Element This command creates rotated copies of individual raceway elements as specified within the design file. You can use this command to copy and rotate one-lines and their associated elements.


Plan View – Specifies the angle at which to rotate the element on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point.

East Elevation – Specifies the angle at which to rotate the element on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point.

North Elevation – Specifies the angle at which to rotate the element on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point.





612

Steps 1. Select the Rotate Copy Element command.

The Rotate Copy Element precision input form displays.

2. Identify the element you intend to rotate and copy and accept it with <D>.


3. Specify the point around which to rotate the element.


4. Specify the planes and angles at which to rotate the element.

5. Click Accept.

The element copy displays at the specified position.

613

Mirror Element This command flips individual raceway elements about a point as specified within the design file. You can use this command to mirror one-lines, RCPs, drop points, equipment pointers, and annotation. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved.

If a one-line is mirrored, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.

Field Descriptions Mirror Point – Displays the location of the specified mirror point. The primary

vector of the orientation tee denotes the mirror plane’s normal vector. The elements are rotated about the plane formed by the secondary and the normal.

Angle – Specifies the angle by which to rotate the orientation tee. To change the displayed angle, select the field and type a new angle.

About – Specifies the axis about which to rotate the orientation tee. To change the displayed axis, toggle among the three axes (Primary, Secondary, Normal) until the appropriate axis displays.

I Button – Reorients the orientation tee along the identity matrix. It realigns the Primary axis with the positive X axis, the Secondary axis with the positive Y axis, and the Normal axis with the positive Z axis.


At any point during this operating sequence, you can exit the command session either by pressing <Esc> or by selecting Cancel (X) on the precision input form. To reset a


614

command action by one step or to reject a highlighted element, press <R> or select Reject on the precision input form.

Steps 1. Select the Mirror Element command.

The Mirror Element precision input form displays.

2. Identify the element you intend to mirror and accept it with <D>.


3. Specify the point about which to mirror the element.

The Orient Mirror form displays.

4. Specify the mirror plane on which to mirror the element. The primary vector of the orientation tee denotes the mirror plane’s normal vector.

5. Click Accept.

The element rotates to the specified position.

615

Mirror Copy Element This command creates mirrored copies of individual raceway elements as specified within the design file. You can use this command to copy and mirror one-lines and their associated elements.








Steps 1. Select the Mirror Copy Element command.

The Mirror Copy Element precision input form displays.


616

2. Identify the element you intend to mirror and copy and accept it with <D>.


3. Specify the point around which to mirror the element.


4. Specify the plane on which to mirror the element. The primary vector of the orientation tee denotes the mirror plane’s normal vector.

5. Click Accept.

The element copy displays at the specified position.

617

Modify Group Commands (replaces 9.3) Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 229-230 in the PDS 7.1 version of the document).


• Rotate, Rotate Copy, Mirror, Mirror Copy, and Move Group commands

See the following text for details.

The Modify Group commands define and manipulate groups within a design file. Groups are temporary associations of Raceway and other elements in your model. The Modify Group commands allow you first to define a group of elements and then to manipulate the group in part or as a whole.

The Modify Group palette is activated by selecting the Modify Group command from the Modify palette, or by selecting Modify from the EERWAY Command Menu Bar, then selecting Modify Group Commands, then selecting Palette.

You can use individual Modify Group commands to move, copy, and delete elements of specified groups, and to review or edit element annotation. You can also propagate one-lines in a particular group using these commands.

Note: Do not use MicroStation commands to manipulate or modify EE Raceway elements (one-line, three-lines, annotation, and so forth). Doing so will cause serious problems and/or destroy the EE Raceway model. Use only these EE Raceway modify commands to manipulate EE Raceway elements.


618

Topics Define Group — Identifies raceway elements for inclusion in a particular group.

Copy Element by Group — Copies within the design file some or all elements of a specified group.

Annotate Element by Group — Places, reviews, and edits intelligent annotation for raceway elements within a specified group.

Clone Group — Copies a group multiple times in the same direction.

Propagate Element by Group — Expands some or all one-line elements of a specified group into three-dimensional elements.

Place Fitting by Rule Group — Places non-standard fittings using a set of rules defined in the reference database.

Add Systems Group — Defines multiple systems for a single one-line.

Replace Systems Group — Changes the defined active system type of a one-line.

Minimize Joints by Group — Reduces to a minimum the number of vertices of some or all one-lines in a specified group.

Delete Element by Group — Removes from the design file some or all elements of a specified group.

Rotate Group – Rotates some or all elements of a specified group to a new location in the design file.

Rotate Copy Group – Copies and rotates some or all elements from a specified group to a new location in the design file.

Mirror Group – Mirrors some or all elements from a specified group to a new location in the design file.

Mirror Copy Group – Copies and mirrors some or all elements from a specified group to a new location in the design file.

Move Group – Moves some or all elements from a specified group to a new location in the design file.

619

Rotate Group This command rotates a group of raceway elements as specified within the design file. You can use this command to move one-lines, RCPs, drop points, equipment pointers, and annotation. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved.

If a one-line is rotated, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.


Plan View – Specifies the angle at which to rotate the group on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point.

East Elevation – Specifies the angle at which to rotate the group on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point.

North Elevation – Specifies the angle at which to rotate the group on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point.




620


Steps 1. Select the Rotate Group command.

The Rotate Group precision input form displays.

2. Identify the group you intend to rotate and accept it with <D>.

The system highlights the specified group. If you do not locate an acceptable group, the system displays the message Group not found. The message disappears when you identify a valid group.

3. Specify the point around which to rotate the group.


4. Specify the planes and angles at which to rotate the group.

5. Click Accept.

The group rotates to the specified position.

Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the rotation point and planes for each accepted element.

621

Rotate Copy Group This command creates a rotated copy of a group of raceway elements as specified within the design file.


Plan View – Specifies the angle at which to rotate the group on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point.

East Elevation – Specifies the angle at which to rotate the group on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point.

North Elevation – Specifies the angle at which to rotate the group on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point.




Steps 1. Select the Rotate Copy Group command.


622

The Rotate Copy Group precision input form displays.

2. Identify the group you intend to rotate and copy and accept it with <D>.


3. Specify the point around which to rotate the group.


4. Specify the planes and angles at which to rotate the group.

5. Click Accept.

The group copy displays at the specified position.

Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the rotation point and planes for each accepted element.

623

Mirror Group This command flips a group of raceway elements about a point as specified within the design file. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved.

If one-lines are mirrored, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.







At any point during this operating sequence, you can exit the command session either by pressing <Esc> or by selecting Cancel (X) on the precision input form. To reset a


624

command action by one step or to reject a highlighted element, press <R> or select Reject on the precision input form.

Steps 1. Select the Mirror Group command.

The Mirror Group precision input form displays.

2. Identify the group you intend to mirror and accept it with <D>.


3. Specify the point about which to mirror the group.


4. Specify the mirror plane on which to mirror the group.

5. Click Accept.

The group moves to the specified position.

Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the mirror point and mirror plane for each accepted element.

625

Mirror Copy Group This command creates a mirrored copy of a group of raceway elements as specified within the design file.








Steps 1. Select the Mirror Copy Group command.

The Mirror Copy Group precision input form displays.


626

2. Identify the group you intend to mirror and copy and accept it with <D>.


3. Specify the point around which to mirror the group.


4. Specify the plane on which to mirror the group.

5. Click Accept.

The group copy displays at the specified position.

Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the mirror point and mirror plane for each accepted element.

627

Move Group This command moves a group of raceway elements to a new location in the design file.



Steps 1. Select the Move Group command.

The Move Group precision input form displays.

2. Identify the group you intend to move and accept it with <D>.


3. Specify an origin point from which to move the group.

4. Specify a placement point to which to move the group.

The group moves to the specified position.


628

Annotate Model Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (p. 285 in the PDS 7.1 version of the document).


• Automatic sheet number See the following text for details.

This command adds or changes the annotation for the model. This command cannot prevent the duplication of sheet numbers within a project. The Load Database process, however, will prevent such duplication. The sheet number should be unique for each drawing. If the user does not specify a sheet number, the sheet number is automatically set to match the .dgn file name of the raceway model.

Steps 1. Select the Annotate Model command.

The Annotate Element form displays.

2. Select the Column value field for sheet on the form and key in a new sheet number.

If you want to display the annotation in the model, toggle the Display fields in the form to On.

3. Select Confirm to accept the new annotation.

—OR —


4. If you toggled Display to On, you are prompted to place the annotation in the model.

629

Reference PDS Model (replaces 16.2) Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 372-373 in the PDS 7.1 version of the document).


• Display, Snap, and Locate toggles See the following text for details.

The Reference PDS Model command attaches and detaches models from the PDS project to the model as reference files. The model to attach can be from any discipline and design area in the project.

Parameters Disciplines – Lists all disciplines. Select the discipline that contains the model you

want to attach; then, click Attach.

Areas – Lists all design areas defined in the active project. Select the design area that contains the model you want to attach; then, click Attach.

Area/Model – Specifies whether to attach all models in a design area or an individual model.

— Attach by Area – Attaches all model in the selected design area.

— Attach by Model – Displays all models in the design area so you can select which model you want to attach.

Propagated/Sparse – Specify whether you want to attach the sparse model or the corresponding propagated model. This option only displays if you are attaching a structural model.

Display Toggle – Specify whether to display the reference model in the active model views.

Snap Toggle –Allows you to snap to any segment in the reference file.


630

Locate Toggle – Allows you to data point to any component in the reference file.

Apply To Discipline – Defines the settings for the Display, Snap, or Locate toggles for the all attached models in the discipline of the selected model.

Apply To All – Defines the settings for the Display, Snap, or Locate toggles for all the attached models in all disciplines.

Attach – Attaches a reference model. You must select a Discipline and a Design Area before you can select a reference model to attach.

Detach – Detaches the selected reference model. You must click Show Attachments and select the reference model you want to detach before clicking Detach.

Show Attachments – Displays all reference models attached to the active model.

Exit – Exits the Reference Model command.

631

EE Raceway Project Database Schema Description (replaces panel) Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 487 and 500 in the PDS 7.1 version of the document).


• PDS coordinates in Panel table • Note about ee72upg.exe file

See the following text for details.

This section lists and describes the tables in the EE Raceway project database schema, and includes detailed information about the columns that comprise each table.

Note: An asterisk (*) indicates that you must not modify the column name. You should not modify those column names having a prefix of "ee_".

panel This table contains information about all panels/equipment found in the drawing.

Note: For project databases created with EE Raceway versions prior to 7.2, it is necessary to use the ee72upg.exe utility in the \eenuc\bin folder to add the new pds_east, pds_north, and pds_elev columns to the panel and msconfig tables of the existing project database. Before running the upgrade utility, use EE Configure to verify that values are set for EERD_TBLS, PROJECT_LOCATION, and EE_SCHEMA.


mslink integer uniq no

panel Char( 20) dups yes

panel_descrip Char( 20) no yes

ee_approv_status integer no yes

ee_approv_date Char( 26) no yes

ee_create_date Char( 26) no yes

ee_last_rev_dat Char( 26) no yes

ee_eqp_table Char( 32) no yes

ee_part_key Char( 28) no yes


632

pds_east real no yes

pds_north real no yes

pds_elev real no yes

mslink: a unique integer value used by the software to identify a row in the panel table.

panel: the column containing the panel/equipment name

panel_descrip: the column containing the panel/equipment description.

ee_approv_status: the column containing the approval status of the panel/equipment.

ee_approv_date: the column containing the date when the approval status changed.

ee_create_date: the column containing the panel/equipment creation date.

ee_last_rev_dat: the column containing the date the panel/equipment was last revised.

ee_eqp_table: the column containing the name of the reference database table that contains additional equipment information.

ee_part_key: the column containing the unique key to the appropriate record of equipment information in the reference database table.

pds_east: the column containing the PDS east coordinate of the panel (calculated by Load Database).

pds_north: the column containing the PDS north coordinate of the panel (calculated by Load Database).

pds_elev: the column containing the PDS elevation coordinate of the panel (calculated by Load Database).

633

EE File Structure (replaces Appendix F) Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 529-540 in the PDS 7.1 version of the document).


• Windows folder listings replace CLIX directory structure See the following text for details.

This section describes the file structure for EE Nucleus and EE Raceway. It also describes the contents of directories and some files. It identifies those files you can modify.

By default, the PDS Component Loader delivers these files to /win32app/ingr/.

The directory tree for EENUC and EERWAY is shown below.


634

EE Nucleus File Structure EE Nucleus (EE Nuc) is the core product for the EE product line. The product may reside on any file system. EE Nucleus will reside under the win32app\ingr\eenuc directory. The list may differ slightly depending on which options are selected during installation. The following files exist under the ..\eenuc directory:

\eenuc

\eenuc\bin

\eenuc\data

\eenuc\db

\eenuc\doc

\eenuc\font

\eenuc\forms

635

\eenuc\help

\eenuc\msg

\eenuc\share

\eenuc\sym


eenuc

— readme.txt – file containing description of product features and any fixes, problems, comments, etc.

— remove.exe – command used to remove EE Nucleus from the machine.

— .EErc – File containing global symbol definitions.

— EEnotice.txt – File containing release notices.

— license.txt– copyright notice file.

bin – contains the EE executable files and the environment process. The EE executable files set up variables specifying the location of MicroStation, INFORMIX, EE Nucleus, and EE Raceway, and then invokes the EE environment.

— background – process that reports the exit status of a process run in the background.

— batch – process that reports the exit status of a process run in batch mode.

— create_db – create database process.

— dba_rpt – DBAccess report process.

— dba_shell.cmd – command executed around dba_rpt.


636

— ee72upg.exe – executable command that updates the EE Raceway Project Database.

— eeconfig – file that maintains EE product configuration for workstation/server.

— Eemgr.exe – Electrical Engineer manager environment executable.

— eeprj.exe – environment process.

— eeqpr.bat – batch file to print 132 column reports to the laser printer.

— menu_shel.cmd – command executed around eemgr to run the Edit Database process.

— mscrecol.cmd – command to create mscolumns table for reference database.

— reeprj – remote environment process.

data – Contains the ASCII files used to control certain environment procedures.

— print.dat – ASCII file for output file management.

— manager.dat – ASCII file for manager function management.

— dba* files – DB Access files.

db – directory that contains the DB Access menu library (mgrdba_lib). Required DBAccess files are also delivered in this directory.

doc – directory that contains documentation.

forms – directory that contains all the environment forms.

help

msg – contains EE Nucleus message files.

share

sym – contains EE symbol files.

637

EE Raceway File Structure This section lists and describes the directories and files delivered with EE Raceway.

\eerway

\eerway\bin

\eerway\data

\eerway\db

\eerway\dgn


638

\eerway\doc

\eerway\eden

\eerway\mdlapps

\eerway\msg

\eerway\report

\eerway\sym

\eerway\tmp

Delivered empty


eerway

— readme.txt – file containing a description of the product features and any fixes, problems, comments, etc.

639

— remove.exe – executable file used to remove EE Raceway from the machine.

bin – contains all process delivered with the EE Raceway product.

— idet – Interference Detection Envelope File Creation process.

— load – processor to load the project database.

— rmon – Controlling processor for interactive manipulations.

— unload_cln – contains the unload sheet, unload drawing, and clean database processes.

data – Contains the ASCII files used to control process and report management for the EE Raceway product. These files can be modified.

— eden.dat – controls Eden processes.

— process.dat – controls process management.

— report.dat – controls standard report management.

— rule_chk.dat – controls rule check report management.

db – Contains the delivered sql files for the project and reference database. Also contains .unl files required for bulk loading special tables and the mscatalog table in the project database.

Sample .unl files for bulk loading reference database tables are also provided.

dgn – Contains the seed file directory, available cell libraries, and any design files delivered with the product.

— rway_schma.dgn – displays the structure of the EE Schema.


640

— rway_view.dgn – explains the structure of the Raceway views.

641

— seed – contains the available seed design files.

— seed.dgn – delivered English drawing seed file. This may be customized.

— msseed.dgn – delivered metric drawing seed file. This may be customized.

doc – contains documentation information on EE Raceway including README files from previous releases.

eden – contains the Eden symbol library.

— eden.lib – the Eden symbol library file.

mdlapps

msg – Contains EE Raceway message files and the file to correlate key-ins to EE Raceway commands.

— alias.cmd – file used to correlate key-ins to commands. This file can be extended.

— command.msg – message file containing all messages for the command field. These messages can be edited but messages cannot be added.

— error.msg – message file containing all error messages for the error field. These messages can be edited but messages cannot be added.

— prompt.msg – message file containing all messages for the prompt field. These messages can be edited but messages cannot be added.


642

— rway_prj.tbl – file containing the entity numbers for the project database tables.

— rway_ref.tbl – file containing the entity numbers for the reference database tables.

— status.msg – message file containing messages for status field, prompting messages, and logo. These messages can be edited but messages cannot be added.

report – Contains the source (.ace)and compiled (.arc) SQL files for all delivered sch reports.

The source files may be edited by the user. There is an .ace and an .arc file for each report listed below.

— rwaydba_lib – DB Access template library.

sym – Contains all symbol files for EE Raceway menus. This directory also contains the available precision input forms.

— rwaybar.sym – symbol file for the bar menu.

— rwaypnl.sym – symbol file for the panel menu.

tmp – Holds any temporary files. The software requires this directory.

643

Index annotate

model, 629 Annotate Model command, 629 EE

file structure, 634 Nucleus

file structure, 635 Raceway

file structure, 638 element

mirror, 614 mirror copy, 616 modify, 608 rotate copy, 610, 612

file structure EE, 634 EE Nucleus, 635 EE Raceway, 638

group mirror, 624 mirror copy, 626 modify, 618 move, 628 rotate, 620 rotate copy, 622

intergrated commands Reference PDS Model, 630

Load Reference Schema command, 599 Mirror Copy Element command, 616 Mirror Copy Group command, 626 Mirror Element command, 614

Mirror Group command, 624 model

annotate, 629 Modify Element commands, 608 Modify Group commands, 618 Move Group command, 628 palettes

bar commands, 604 design, 605 EE Raceway, 602 EERway, 602 Intergrated Commands, 602 model commands, 607 modify, 605 modify element, 604, 608 modify group, 606, 618 runtime setup, 607 setup, 606

PDS reference model, 630

Reference PDS Model command, 630 reference schema

load, 599 Rotate Copy Element command, 612 Rotate Copy Group command, 622 Rotate Element command, 610 Rotate Group command, 620 schema

load reference, 599 utilities, 601