You are on page 1of 643

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, or
implied 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 considered
commitments 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 this
license.

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

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

Copyright
 1984-2003 Intergraph Corporation
All Rights Reserved
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright and trade secret law and may not
be 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 Technical
Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of Commercial Computer
Software — 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 ........................................................................................................ 17
Intergraph Directory ............................................................................................................. 17

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

Document Purpose ................................................................................................................ 19


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

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

Keyboard Conventions ......................................................................................................... 22


Terminology ......................................................................................................................... 23

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

About the Reference Guide .......................................................................................................... 25


Basic Workstation Skills .............................................................................................................. 26

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

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

Upgrading the Workstation .......................................................................................................... 28


Installation Procedure .................................................................................................................. 29
Databases ..................................................................................................................................... 33

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

Using the Electrical Engineer Menus ........................................................................................... 36


Create ........................................................................................................................................... 39
Enter ............................................................................................................................................. 40
Product Menu ............................................................................................................................... 42
Copy ............................................................................................................................................. 43
Delete ........................................................................................................................................... 44
Archive ......................................................................................................................................... 46
Restore ......................................................................................................................................... 48
Database Utilities ......................................................................................................................... 50

RIS schema utilities .............................................................................................................. 51


Update Project Schema ......................................................................................................... 52

3
________________
Update Reference Schema .................................................................................................... 55

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

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

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

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

Operating Modes .................................................................................................................. 68


Entering Time in Batch Mode .............................................................................................. 69

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

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

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

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

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

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

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

Start-up Sequence ........................................................................................................................ 92


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

Working Units in MU:SU:PU .............................................................................................. 104


Precision Key-ins .................................................................................................................. 105

4
________________ Table of Contents

6. Workflow and Procedures ............................................................................................................ 107

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

System Manager Setup ......................................................................................................... 109


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

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

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


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

Reports ......................................................................................................................................... 117


Interference Detection .................................................................................................................. 118

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

View ...................................................................................................................................... 120


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

Construct Point ............................................................................................................................ 123


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

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

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

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

5
________________
When to Use These Commands ............................................................................................ 131
Before Using These Commands ........................................................................................... 131
Group Workflow ................................................................................................................... 131
Operating 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 .................................................................................................................... 147


Conduit Sizing ............................................................................................................................. 155

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

Insert One-Line Vertex ................................................................................................................ 160


Place Field Routed Raceway ....................................................................................................... 161
Define Duct Cross Section ........................................................................................................... 164
Place Stub Up ............................................................................................................................... 167

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

6
________________ Table of Contents

9. Modify Commands ...................................................................................................................... 173

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

When to Use These Commands ............................................................................................ 174


Before Using These Commands ........................................................................................... 174
Group Workflow ................................................................................................................... 174
Operating Information .......................................................................................................... 174

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

Using the Modify Element Commands ................................................................................ 177


When to Use These Commands ............................................................................................ 177
Before Using These Commands ........................................................................................... 177
Group Workflow ................................................................................................................... 177
Operating Information .......................................................................................................... 177
Annotate Element ................................................................................................................. 178
Field Descriptions ................................................................................................................. 179
Copy 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 ......................................................................................................... 192


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

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

7
________________
Change System Parameters ................................................................................................... 221

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

Topics ................................................................................................................................... 223


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

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

Copy Element by Group ....................................................................................................... 231


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

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

Add Systems Group .............................................................................................................. 245


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

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

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

When to Use These Commands ............................................................................................ 255


Before Using These Commands ........................................................................................... 255
Group Workflow ................................................................................................................... 255
Operating Information .......................................................................................................... 255

Set Raceway Defaults .................................................................................................................. 256


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

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

Symbology Control ...................................................................................................................... 264


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

Using the Create Cell Commands ......................................................................................... 270


When to Use These Commands ............................................................................................ 270

8
________________ Table of Contents

Before Using These Commands ........................................................................................... 270


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

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

Using the Model Commands ................................................................................................ 281


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

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

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

When to Use These Commands ............................................................................................ 288


Before Using These Commands ........................................................................................... 288
Group Workflow ................................................................................................................... 288
Operating Information .......................................................................................................... 288

Set Active One-Line Type Parameters ......................................................................................... 289


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

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

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

When to Use These Commands ............................................................................................ 305


Before Using These Commands ........................................................................................... 305
Group Workflow ................................................................................................................... 305
Operating Information .......................................................................................................... 305

Toggle Construction Display On/Off ........................................................................................... 306


Highlight 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 ....................................................................................................... 314


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

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

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

When to Use These Commands ............................................................................................ 322


Before Using These Commands ........................................................................................... 322
Group Workflow ................................................................................................................... 322
Operating Information .......................................................................................................... 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 ............................................................................................................................. 336


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

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

Compile EDEN Symbol ............................................................................................................... 349


Delete EDEN Symbol .................................................................................................................. 351

10
________________ Table of Contents

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

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

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

List EDEN User Functions .......................................................................................................... 355


Merge EDEN Symbol Libraries ................................................................................................... 357
Compress EDEN Symbol Library ............................................................................................... 359
Extract EDEN Symbol From Library .......................................................................................... 361

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

Extract EDEN User Function From Library ................................................................................ 363


Edit EDEN Symbol File .............................................................................................................. 366

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

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

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

When to Use These Commands ............................................................................................ 370


Before Using These Commands ........................................................................................... 370
Group Workflow ................................................................................................................... 370
Operating Information .......................................................................................................... 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 ................................................................................................................................. 417


EE Environment Variables .......................................................................................................... 422

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

Relational Interface System (RIS) ............................................................................................... 426


Database and RIS Procedures ...................................................................................................... 427

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

Update Schema (create_db) Process ............................................................................................ 428


Reference Schema - General Description .................................................................................... 430

Default Attributes ................................................................................................................. 430


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

Project Schema - General Description ......................................................................................... 448


Updating Schemas ....................................................................................................................... 449

Updating a Project Schema ................................................................................................... 449


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

Modifying the Reference Schema ................................................................................................ 451


EE Raceway Reference Database Schema Description ............................................................... 454

approv_status ........................................................................................................................ 454


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

12
________________ Table of Contents

cond_part .............................................................................................................................. 459


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

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

cabsch_spec .......................................................................................................................... 487


cndsch_spec .......................................................................................................................... 489
drawing ................................................................................................................................. 491
drop_point ............................................................................................................................. 491

13
________________
duct_fill ................................................................................................................................. 492
ee_pseudo_cable ................................................................................................................... 492
ee_system .............................................................................................................................. 493
envelope ................................................................................................................................ 493
fitting ..................................................................................................................................... 494
fit_to_sys ............................................................................................................................... 495
mscatalog .............................................................................................................................. 496
mscolumns ............................................................................................................................ 497
ol_to_sys ............................................................................................................................... 498
one_line ................................................................................................................................. 498
panel ...................................................................................................................................... 500
project ................................................................................................................................... 500
panel_to_drw ........................................................................................................................ 501
rcp ......................................................................................................................................... 501
rcp_to_drw ............................................................................................................................ 502
rcp_to_sys ............................................................................................................................. 502
straight .................................................................................................................................. 503
str_to_sys .............................................................................................................................. 504
sys_to_drw ............................................................................................................................ 505
to_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 ............................................................................................................ 520


EE Raceway File Structure .......................................................................................................... 524

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

eden.dat ........................................................................................................................................ 531


process.dat .................................................................................................................................... 533
report.dat ...................................................................................................................................... 534
rule_chk.dat .................................................................................................................................. 535
print.dat ........................................................................................................................................ 536
manager.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: .............................................................................................................. 547


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

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

Information Output: .............................................................................................................. 548


Associated Software/Files .................................................................................................... 548

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

Information Output: .............................................................................................................. 549


Associated Software/Files .................................................................................................... 549

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

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


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

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

Information Output: .............................................................................................................. 552


Associated Software/Files .................................................................................................... 552

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

Schema Information Form ........................................................................................................... 554


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

Table Information Form ....................................................................................................... 557


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

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


Set 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
________________ Table of Contents

If You Need Assistance

Intergraph Online
Our web site brings you fast, convenient, up-to-the-minute information about Intergraph’s
products, 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 to
http://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 at
http://www.intergraph.com.

Intergraph Directory
The following numbers are only valid in the United States unless otherwise indicated. If you
are 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 & Offshore
300 Intergraph Way
Madison, Alabama 35758
U.S.A.

You can also reach us by electronic mail at info@intergraph.com.

17
________________
Documentation Contacts
We are constantly working on updates and improvements to the documents and other
educational media. If you have any suggestions on where we can improve the documentation
or where you think more information is needed, let us know. You can reach us by:

Mail Intergraph Process, Power & Offshore


Documentation Manager
300 Intergraph Way
Madison, 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, and
model 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 than
presenting a typical work flow. Use this guide when you need to look up a specific EE Raceway function. It is
recommended that you work through the EE Raceway Modeling Course Guide to learn the basic concepts of the
product.

Document Prerequisites / Audience


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

Related Documents/Products
MicroStation  software is required to operate EE Raceway. Information about MicroStation capabilities can
be 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 a
relational 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 the
design process is controlled by executing commands, much of this document is devoted to a description of those
commands, 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 product
and creating and manipulating product files.

Section 5 Describes the graphics environment for the product. This includes information on the
screen 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 the
command 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 purchased
your workstation.

Additional Information
The following informational files are delivered with the EE Raceway software in the win32app\ingr\eerway
directory.

File Name Contents

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

20
________________ Preface

General Conventions
This document contains many visual cues to help you understand the meaning of certain
words or phrases. The use of different fonts for different types of information allows you to
scan the document for key concepts or commands. Symbols help abbreviate and identify
commonly used words, phrases, or groups of related information.

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

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. Command
paths 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 by
the user. For example,

Select first segment of alignment

Bold Typewriter
Indicates what you should literally type in. For example,

Key in original.dat to load the ASCII file.

Normal Typewriter
Indicates 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 special
information:

<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 is


doing 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 the
exercises.

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

ALT Alternate key


CTRL Control key
DEL Delete key
ENTER Enter key
ESC 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 an
action. For example,

Click Apply to save the changes.

Select To mark an item by highlighting it with key combinations or by picking


it with your cursor. Selecting does not initiate an action. After
selecting an item, you click the action you want to affect the item. For
example,

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

In addition, you would select items to define parameters, such as


selecting toggle buttons. This also applies to selecting graphic
elements 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 design


file. If you are using the Windows NT operating system, you
tentative-select by pressing a left-button, right-button chord.

Double-click To select and execute a command by clicking the mouse or hand-held


cursor button twice in rapid succession. This term implies that you are
clicking 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 or
hand-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 the
default action.

In a dialog box, pressing TAB after keying in data will


enter the data and move the cursor to the next field.

23
________________
EE Raceway Modeling Reference Guide - February 2003

24
________________ Introduction

1. 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 a


three-dimensional raceway model.

Interference detection – Creates the raceway component interference envelope files for
input 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 other
PDS facility design disciplines.

About the Reference Guide


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

25
________________
EE Raceway Modeling Reference Guide - February 2003

Basic Workstation Skills


The following basic workstation drafting skills are necessary to use the EE Raceway
Modeling 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
________________ Installation Instructions

2. Installation Instructions
This section is an instruction sheet both for initial installation and for updating the
workstation 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.

Download/Install
2.
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 individual
documentation for these products for detailed information.

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

Upgrading the Workstation

Installation Procedure

Databases

27
________________
EE Raceway Modeling Reference Guide - February 2003

Upgrading the Workstation


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

The chapter also outlines the basic workflow for database setup and refers you to appropriate
database 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 and
decide 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 database
remotely on a server.

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

28
________________ Installation Procedure

Installation Procedure
This section’s examples assume that you are running the loader delivered with PDS; the
loader 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 a
networked drive, or it may be on your local system.

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

Download/Install
2.
3. Select Continue to invoke the Intergraph Registration Data form. This form expects
your user name, company, and serial number (as delivered). Pressing Enter will have
no effect until all fields have been entered, including a valid serial number. The
Continue 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 product
selection form.

29
________________
EE Raceway Modeling Reference Guide - February 2003

5. Place an X next to the software you wish to install. This will invoke the installation
data form for each selection. Among other installation options that vary according to
product, 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 to
install 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 be
hosting the session, as well as path to the software on the server, and a local path
to the icon associated with the software.

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

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

30
________________ Installation Procedure

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

When the software has successfully loaded, the EENUC (Common) program group
will be created. This program group contains the EE Manager, EE Configure, EE

Download/Install
2.
Readme.txt, EE Help, and EE Nucleus icons.

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

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

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


form.

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

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

9. Set your user environment variables. Before you can enter the EE environment, you
will 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 that
variable. To modify the value of that variable, key the desired value into the Value
field, then select Set.

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

This will close the EE Configure utility.

32
________________ Databases

Databases
This section provides an overview of the workflow involved in creating a database and
schemas. What follows is a very basic outline, and you should consult your individual
RDBMS 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 location


options. Also, see your individual RDBMS documentation for installation

Download/Install
2.
instructions 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 about
the RIS products. Also, see the Relational Interface System (RIS) Reference
Manual.

3. Create new databases/upgrade existing databases.

In order for the EE Raceway project to integrate to PDS there must be


two entries in pdtable_102 corresponding to type_of_rdb_data: 200 for
project schema, and 202 for reference schema. Only after these entries
are in the table will the user be able to update the project and reference
database for use with PDS.

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

— For detailed information about creating and updating databases, see Appendix C of
this 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 Manager
product.

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

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

33
________________
EE Raceway Modeling Reference Guide - February 2003

5. Update your project and reference schemas.

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

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

34
________________ Electrical Engineer (EE) Environment

3. Electrical Engineer (EE)


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

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

35
________________
EE Raceway Modeling Reference Guide - February 2003

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 before
you 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, and
then 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 input
fields, 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 system
manager.

36
________________ 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 will
manage using the available menu options. When a particular option is active, the item you
select 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 scroll
bar. The bar above the arrows indicates where you are in the listing. If the bar fills the space
above 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.

Environment
3. EE
Cancel (X) exits the EE application entirely.

The menus will not allow you to perform illegal operations. For example, you
are 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 in
the message area at the bottom of the form. You can monitor lengthy processes by reviewing
the message area.

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

37
________________
EE Raceway Modeling Reference Guide - February 2003

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 EE


applications 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 Schema


Manager.

38
________________ Create

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

Environment
3. EE
Field Descriptions
Project name — This field allows you to enter the project name in uppercase or
lowercase letters, though uppercase letters are automatically converted to lowercase.
Your project name should have eight or fewer characters. A .prj extension is
automatically appended to the project file name when you select Confirm (√), so you
are 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 a
project. For information about creating a project schema, see RIS
Schema Manager, page 553 .

— OR —

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

39
________________
EE Raceway Modeling Reference Guide - February 2003

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

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

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

This field may also be defined by the environment variable


EE_SCHEMA. Refer to the section about EE Environment Variables
in Appendix B of this document for more information on environment
variables.

Reference schema — This field is automatically updated with the reference schema
name associated with the selected project name. You can override the default selection
by 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 B
of 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 has
been entered, depending on the setting of the appropriate Password Echo toggle.

40
________________ Enter

Password Echo — This toggle controls whether or not the password is displayed in the
respective 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 display
automatically.

You can make modifications to these fields, if needed.

3. Enter schema passwords if they were created for either schema. Identify the appropriate

Environment
3. EE
Schema password field, and key in the password. If no password was defined for the
schemas, 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 environment


bypasses the Product Menu and goes directly into the Drawing Menu.

41
________________
EE Raceway Modeling Reference Guide - February 2003

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

Only the EE products you actually have installed on your workstation will be
displayed 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 more
information about the Design Menu.)

42
________________ Copy

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

Field Descriptions

Environment
3. EE
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 a
project 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 project
to field.

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

— OR —

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

43
________________
EE Raceway Modeling Reference Guide - February 2003

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.

3. Select Confirm (√).

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

44
________________ Delete

Selecting Accept on the warning form deletes the project and its database, while
selecting 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 that
you are about to delete an entire project.

Environment
3. EE
Selecting Accept on the warning form deletes the project, while selecting Cancel
cancels the Delete function.

— OR —

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

45
________________
EE Raceway Modeling Reference Guide - February 2003

Archive
This option stores an entire project and associated database on a network host or on a floppy
disk.

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

TCP/XNS — This toggle allows you to choose between TCP and XNS network
protocols. 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 the
project. The project name is appended to this path. The path must exist on the remote
node.

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

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

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

46
________________ 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 Floppy


changes the displayed form information.

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

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

Environment
3. EE
4. Select Confirm (√) to begin archiving.

— OR —

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

47
________________
EE Raceway Modeling Reference Guide - February 2003

Restore
This option retrieves an entire project and any associated database from a network or a floppy
disk.

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

When restoring from a floppy, you can restore a project that is currently listed in your
listing area. The project on the floppy will overwrite the project in your directory. Be
sure to verify that archived project will not overwrite existing projects with the same
name.

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

TCP/XNS — This toggle allows you to choose between TCP and XNS network
protocols. 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 the
Password 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. A
password is required if you are using the TCP option.

48
________________ 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 Floppy


changes the displayed form information.

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

4. Select Confirm (√) to begin restoring.

— OR —

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

Environment
3. EE

49
________________
EE Raceway Modeling Reference Guide - February 2003

Database Utilities
This option accesses the RIS Schema Manager environment and the EE schema updating
processes.

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

RIS schema utilities

Update Project Schema

Update Reference Schema

50
________________ 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 your
relational database management system (RDBMS) documentation for specific information
about database installation. RIS Schema Manager, page 553 supplies examples of Create
Schema input for several RDBMSs.

Environment
3. EE
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 from
the Database Utilities menu.

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

51
________________
EE Raceway Modeling Reference Guide - February 2003

Update Project Schema


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

For additional information about updating schemas, see


EE 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 schema
name, select the field and key in the name of an existing project schema.

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

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

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

52
________________ Update Project Schema

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

Sql and Cmd file — These fields display the command and SQL files associated with
each application. The delivered default files are defined in the
win32app\eenuc\bin\.EErc file. You can redefine the defaults by editing this .EErc file
or 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 the
User Defined checkbox, and key in the full pathname for those files, or export
EE_CUSTOM_SQL and EE_CUSTOM_CMD for the customized SQL and command
files.

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

Steps

Environment
3. EE
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 message
files to the screen:

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

53
________________
EE Raceway Modeling Reference Guide - February 2003

— 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 current
project’s /tmp directory, using the Output option on the Utilities
form. For more information, see
Output, 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
________________ Update Reference Schema

Update Reference Schema


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

For additional information about updating schemas, see


EE 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 name
you entered.

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

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

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

Sql and Cmd File — These fields display the command and SQL files associated with
each application. The delivered default files are defined in the
win32app\eenuc\bin\.EErc file. You can redefine the defaults by editing this .EErc file
or 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 the
User Defined checkbox, and key in the full pathname for those files, or export
EE_CUSTOM_REFSQL and EE_CUSTOM_REFCMD for the customized SQL and
command 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 more
information about operating modes, see Process, page 64 .

55
________________
EE Raceway Modeling Reference Guide - February 2003

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 form
parameters. Return to step 1.

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

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

— OR —

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

56
________________ Update Reference Schema

You can also access these message files, located in the current
project’s /tmp directory, using the Output option on the Utilities
form. For more information, see
Output, page 89 .

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

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

57
________________
EE Raceway Modeling Reference Guide - February 2003

58
________________ 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 the
workstation (see
Product Menu, page 42 for more information).

— OR —

The EE Raceway Design Menu.

Environment
4. EERWAY
The rest of this chapter describes all the options on this menu. If you are a
new 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 when
each 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 processes
work 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
________________ 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 file
contains basic information that EE Raceway uses. A seed file can also contain customized
information 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. EE
Raceway will convert PDS seed files to raceway design files the first time you enter the EE
Raceway graphics environment.

Environment
4. EERWAY
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 one
seed 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_SEED
symbol 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 you
select 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 file
extension.

61
________________
EE Raceway Modeling Reference Guide - February 2003

A file extension of .dgn is automatically appended to the drawing name if you do not
enter your own file extension.

4. Select Confirm (√).

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

— OR —

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

62
________________ Design

Design
This option accesses the graphics environment, taking you into a specified existing design
file.

Steps
1. Select Design from the Design Menu.

2. Select the drawing name from the listing area.

3. Select Confirm (√).

Environment
4. EERWAY
The system invokes the graphics environment.

— OR —

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

63
________________
EE Raceway Modeling Reference Guide - February 2003

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

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

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

64
________________ 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 default
values by keying in your own information. All drawings are displayed on the screen scrolling
area. An asterisk (*), when placed in the Enter Drawing Name input field, is a wild card
character 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 used
as a wild card for a single character. Once you have entered all necessary information, select
Confirm (√) to execute the process.

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

Environment
4. EERWAY
options.

A process in Foreground runs immediately, and you do not regain control until the
process is finished. In other words, you cannot perform other functions within the same
window 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 time
and/or date when you want the process to start. After providing this information, you
regain control immediately.

65
________________
EE Raceway Modeling Reference Guide - February 2003

Entering Time in Batch Mode


If you select Batch mode, an input box displays, allowing you to enter the time and date when
you 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 separated
by a colon (hour:minute). The suffix AM or PM may be appended; otherwise, a 24-hour
clock (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 a
day of the week (fully spelled or abbreviated to three characters). The system recognizes the
words TODAY and TOMORROW. If you input no date, the system assumes it should run the
job TODAY if the specified hour is greater than the current hour, and TOMORROW if the
specified hour is less than the current hour.

Legitimate commands include:

0815am Jan 24
8:15am Jan 24
Now + 1 day
5pm 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 the
Process option.

66
________________ EDEN

EDEN
Eden is a high-level symbol definition language (modeled after the FORTRAN programming
language) 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 program
options. For detailed information about individual Eden options, see Eden
Processes, page 347 .

Environment
4. EERWAY

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 the
default values that already display, and key in your own information.

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

Operating Modes
A box on the right side of the menu allows you to select the operating mode for the selected
option. The default mode is foreground. The circular arrow on the right indicates that this
box 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 until
the process is finished. In other words, you cannot perform other functions within the
window 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 time
and/or date when you want the process to start. After providing this information, you
regain control immediately.

68
________________ EDEN

Entering Time in Batch Mode


If you select batch mode, an input box displays, allowing you to enter the time and date when
you 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 separated
by a colon (hour:minute). The suffix AM or PM may be appended; otherwise, a 24-hour
clock (military time) is understood. The special names NOON, MIDNIGHT, NOW and
NEXT are also recognized.

You can specify an optional date in the form of either a month name followed by a day
number or a day of the week (spelled in its entirety or abbreviated to three characters). The
system accepts the words TODAY and TOMORROW. If you input no date, the system
assumes 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 24
8:15am Jan 24
Now + 1 day
5pm Friday

Environment
4. EERWAY

69
________________
EE Raceway Modeling Reference Guide - February 2003

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

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

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

70
________________ Report

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

Key in any information that is not supplied by default. You can change the name of the
output file or error file. To change the output filename, select the output file box and key in a
new 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 files
yourself. If a new output file has the same name as an existing file, the new file
will overwrite that file. You should give each report you want to save a unique
name.

Steps
1. Select Report from the Design Menu.

Environment
4. EERWAY
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 the
Report option.

71
________________
EE Raceway Modeling Reference Guide - February 2003

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 high
range in PDS coordinates. 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 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 on
the precision input form. The coordinate values need to be in subunits and entered in the form
field with a space between the coordinates: easting northing elevation For example, 234
532 34

It should be understood that westing and southing coordinates must be the


negative of their opposite directional coordinate. For instance, a westing
coordinate of 100 should be keyed in as a value of -100 in the easting
direction, and a southing coordinate of 3000 should be keyed in as a value of
-3000 in the northing direction.

72
________________ Rule Checks

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

Overview
This section contains general information about running all EERWAY rule checks. For more

Environment
4. EERWAY
detailed information about each rule check, see Reports, page 545 .

The system manager can change the names of the reports or add new reports to
the 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 that
displays 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 files
yourself. 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 report
that 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.

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 the Rule
option.

74
________________ Utilities

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

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

Environment
4. EERWAY

Files in the current project sub-directories will be listed in four columns. Each column will list
a 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 by
standard 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 later
in 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) on
which to perform that option.

3. Enter necessary form information for the active option.

76
________________ 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.

Environment
4. EERWAY

77
________________
EE Raceway Modeling Reference Guide - February 2003

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

Field Descriptions
Copy file from — This field displays the name of the file to be copied; elect a file from
the 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 be
called; key in a unique destination file name into this field.

78
________________ Delete

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

Environment
4. EERWAY

79
________________
EE Raceway Modeling Reference Guide - February 2003

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

80
________________ Purge

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

Field Descriptions
Purge Files toggle — This toggle allows you to choose between purging ALL files that
have 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 list
by placing a data point on them. To de-select a selected file, place a data point on it.

Environment
4. EERWAY

81
________________
EE Raceway Modeling Reference Guide - February 2003

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

Field Descriptions
Rename file from — This field displays the current filename. You can select the file
from 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
________________ Send

Send
This option copies a file to a network node. Be sure to include the entire filename including
the extension (for example, test1.dgn). If you are sending a design file to a VAX, turn on the
IGDS 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 password
of 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 transfer
uses the TCP or XNS protocol to communicate between machines.

Environment
4. EERWAY
IGDS/No IGDS toggle — This toggle should be set to the IGDS setting when sending
to 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 select
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 the
machine to which you want to send the file.

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

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

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

83
________________
EE Raceway Modeling Reference Guide - February 2003

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 be
placed 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 password
of 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 transfer
uses the TCP or XNS protocol to communicate between machines.

File name — This field reflects the name of the file to be received. You can either
select 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 the
machine from which you want to receive the file.

Remote path directory — This field expects the path on the remote machine from
which 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 on
the sending machine. The password may or may not be visible in the field, depending
on the setting of the Password Echo toggle.

84
________________ Receive

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

Environment
4. EERWAY

85
________________
EE Raceway Modeling Reference Guide - February 2003

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

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

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

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

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

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

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

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

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

86
________________ Restore

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

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

Field Descriptions

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

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

Network/Floppy toggle — The setting of this toggle determines if the file will be
archived 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 be
restored.

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

Remote path directory — This field expects the path on the remote machine from
which 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 on
the remote machine. The password may or may not be visible in the field, depending
on the setting of the Password Echo toggle.

88
________________ 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 an
output 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) controls


the 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 support
specific output requirements.

Field Descriptions

Environment
4. EERWAY
File name — Key in the name of the file to be submitted to the output process, or select
it from the list.

Output Destination List — Select the appropriate output device.

89
________________
EE Raceway Modeling Reference Guide - February 2003

90
________________ EE Graphics Interface Elements

5. EE Graphics Interface Elements


This chapter describes the graphics environment you will encounter while working in a design
file. It also documents the on-line Help system and provides other general information needed
to 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 and
the bar menu to select the commands. By default, the panel menu is located on the right side
of your screen and the bar menu is at the top. You can also invoke commands by keying in
the command name and pressing <Return>. This chapter contains more detailed information
about using menus.

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

Graphics
5. EERWAY

91
________________
EE Raceway Modeling Reference Guide - February 2003

Start-up Sequence
When you enter an EERWAY design file (see
Design, 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
________________ 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, as


described in the previous section, your screen display may be different. (Check
with your system manager if you have a customized rway.cmds file.)

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

Graphics
5. EERWAY

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

93
________________
EE Raceway Modeling Reference Guide - February 2003

— Sink Box - moves the command window below views and other windows of its
own 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 a
command.

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

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

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

94
________________ Screen Display

Window Manipulation Buttons - provide ways to manipulate windows.

Window Menu Button - displays a list of window actions. Double-clicking on this


button deletes the window. To select an action from the menu, press and hold the data
button and move the cursor through the list. When the correct item highlights, release
the data button.

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


location.

Move - moves a window around the workspace.

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

Minimize - collapses a window.

Maximize - enlarges a window to its maximum size. If you select this entry on a
window that is already at its maximum size, the window is restored to its
previous 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 the
maximize button on a window that is already at its maximum size, the window is
restored 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 and
hold the data button to move the window.

Vertical Arrows - appear when the cursor is placed at the top or bottom border. Press
and 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. Press
and hold the data button to change the width of the window as you move the cursor.
Graphics
5. EERWAY

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

95
________________
EE Raceway Modeling Reference Guide - February 2003

EERWAY Command Menu Bar


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

Using the Command Menu Bar


The command menu bar is a logical menu. Each keyword leads to a pull-down menu that
contains commands for various EERWAY tasks; you can also access command palettes from
these 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 the
following commands:

EERWAY Palette - Invokes the EERWAY command palette.

Bar Commands - Invokes the Bar Commands palette, which allows access to the most
frequently-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 return
control to the EE Raceway menu interface.

Integrated Commands - Invokes the Integrated Commands menu.

96
________________ Palettes in the EE Raceway Graphics Environment

Palettes in the EE Raceway Graphics


Environment
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.

Graphics
5. EERWAY

97
________________
EE Raceway Modeling Reference Guide - February 2003

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.

98
________________ Palettes in the EE Raceway Graphics Environment

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.

Graphics
5. EERWAY

99
________________
EE Raceway Modeling Reference Guide - February 2003

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.

100
________________ Palettes in the EE Raceway Graphics Environment

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.

Graphics
5. EERWAY

101
________________
EE Raceway Modeling Reference Guide - February 2003

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

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

102
________________ Identifying Elements

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

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

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

Graphics
5. EERWAY

103
________________
EE Raceway Modeling Reference Guide - February 2003

Working Units and Precision Key-ins


When you place elements or manipulate them, you can often use data points, but placing data
points does not always provide the accuracy you need. Therefore, EERWAY lets you key in
values (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 on
Master Units, Subunits, and Positional Units, also known as MU:SU:PU. You must
understand 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, are
established based on the project type (metric or English).

Working units are coordinate units corresponding to the position and definition of a point in
the design file. The working unit dictates the degree of accuracy for placement of elements in
a drawing and determines the scale relationship of elements in the design. The following
explains 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 were
used to create the delivered cell library. If using this cell library, we recommend that you use
these 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 are
not limited to using only them. You may set your working units to any desired
value, if a user-created cell library is being used. (See your system manager for
more information about the working units settings used at your location.)

104
________________ 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 exact
lengths and areas. You specify a distance and an angle from the last point placed, or you can
specify the delta values in X and Y to place another point. Key-ins are entered through the
alphanumeric 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:PU


working units and the direction in degrees that you want the point to be placed. The
new point is placed relative to the previous point. For example, if you want to place a
point 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 in
MU:SU:PU that you want the point to be placed. The new point is placed relative to the
previous point. For example, if you want to place a point 18 inches over and 18 inches
up, key in DX=1:6,1:6.
Graphics
5. EERWAY

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

105
________________
EE Raceway Modeling Reference Guide - February 2003

106
________________ Workflow and Procedures

6. Workflow and Procedures

6. Workflow
This section describes the overall workflow of EE Raceway Modeling software, as an operator
would typically use it. This includes setting up the design file, creating a raceway model, and
running reports and processes on the file. Preparation for the application or system manager
is 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 the
document, this section will refer you to other documentation wherever
possible.

107
________________
EE Raceway Modeling Reference Guide - February 2003

The Drawing Process


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

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

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

This section is divided into individual descriptions of the steps involved in the drawing
process. 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
________________ System Manager Setup

System Manager Setup

6. Workflow
Before you begin an individual drawing, the system/application manager should determine the
defaults 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 (see
Specification, 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 Set
Raceway Defaults command (see the section entitled Setup Commands for information about
this command). Your system manager should also tell you the project name and design
filename.

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

109
________________
EE Raceway Modeling Reference Guide - February 2003

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 must
have 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 the
reference database. The command displays all systems available in the reference database. If
you need systems not available to you, ask the system manager to add them to reference
database. See Define System, page 258 for more information.

Then, use the Set Active System command to specify the system you want active as you are
drawing raceways. You can change the active system throughout the design session. See
Set 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 an
active system, you must have at least one one-line type defined and active in order to draw
raceways.

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

Then, use the Set Active One-Line Type command to specify the one-line type you want
active as you are drawing raceways. You can change the active one-line type throughout your
drawing 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 default
symbology settings for them. Doing so involves two commands: Set Symbology Control
and Symbology Control.

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

Use the Symbology Control command to review and modify the symbology settings for
those 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. See
Symbology Control, page 264 for more information.

110
________________ Drawing Setup

Set Active Parameters

6. Workflow
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 into
the design file for loading later into the project database. To review and modify this data you
will use the Set Active One-Line Parameters command. See Set Active One-Line Type
Parameters, page 289 for more information.

Set Propagation Parameters


Before you propagate one-lines in your model, you should review the active propagation
parameters. These parameters determine how the system defines fittings, what one-lines will
be 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. See
Propagation Setup, page 297 for more information.

111
________________
EE Raceway Modeling Reference Guide - February 2003

Place One-Line
You will place all one-lines, regardless of type, using the Place One-Line or Place Manual
Fitting commands, and the Precision Input form. See
Place One-Line, page 132 ; Place Manual Fitting, page 147 ; and
Precision Input Form, page 119 for more information on these commands. To draw a
raceway, first place one-line segments (centerlines) in connected groups called runs. A run is
a group of connected segments that do not branch or change specification. initially in
phantom mode, placing tentative segments, until you accept them with the Accept option on
the 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 later
choose to delete it). An accepted run has a Raceway Connect Point (RCP) attached to each
end of the run. Each run has a cross section on each end depicting the type of raceway and its
orientation (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 Design
Commands, page 129 for a description of the Place One-Line command.

112
________________ Propagation

Propagation

6. Workflow
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’s
shape is determined by the one-line type (tray, for example). The length of each three-line
segment is determined by the length of the one-line, and the width and height (or diameter) of
a segment are determined by the active parameters when you placed the one-line. The default
fitting radius determines the radius of any bends between raceway segments. This radius is
used 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 section
and 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 necessary
for sketching the three-line is stored in the design file, so reference database access is not
required. Second, the three-dimensional elements are drawn in-line without accessing the
Eden 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 degree
angle, propagation will automatically sketch a 90 degree elbow.

Eden: In Eden mode, one-lines are propagated into three-lines based on the specification
information. The system analyzes the environment in which the one-lines meet when
determining the type of fitting to place. It then searches the database for the appropriate part
for the proper specification. Once found, the specification dimensions and part information
are 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 the
shape of your fittings. For example, EE Raceway provides rounded tray elbows. If you
require mitred elbows for production, you can define the fitting through Eden. Eden
propagation allows you greater detail and accuracy in three-dimensional fitting design. This
may 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 147
for more information. You can use manual placement in situations where placing a sparse
model will not be sufficient or is not possible. For example, you may need to place fittings
manually when dealing with tight spaces, unusual angles, or fitting-to-fitting placement. All
special 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. Any
repropagation of such fittings will yield the same Eden symbols as well, regardless of the
active propagation mode. This ensures that fittings will always be repropagated with the same
orientation, definition, and specification.

After propagation (whether performed in sketch or Eden mode), the one-line elements remain
in 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 Errors
command, see
Highlight Propagation Errors, page 314 . For a detailed description of these error messages,
see
Error Messages, page 377 .

Seamless Tubing Representations


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

114
________________ Databases

Databases

6. Workflow
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 raceway
models. There are two databases that can be associated with your drawing: the reference
database and the project database.

Reference Database
A large amount of annotation is used in raceway models. Much of this annotation is
repetitious and not unique to any element in the drawing. The EE Raceway reference
database provides a simple method for generating this repetitious annotation. The reference
database automatically supplies default annotation values for the project database. (The
system manager may customize these values.) You can also add this information to this
drawing 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 parameter
information is supplied from the vendor catalog in the reference database, using the
annotation forms.

Override Keys
EE Raceway supports EE reference database override keys. The override key gives you the
ability 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 reference
database. The default annotation information, supplied by the reference database, can now be
overridden by specifying another valid database key.

The Annotate Element command is used to place and modify the override key linkages. The
form that displays with this command contains the reference database key value in a separate
field below the annotation input area (see Annotate Element, page 178 ). You can both key in
override 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 created
when the project is created. (The project database can be created any time before the Load
Database process is run.) It will contain information about a particular drawing only after the
Load 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 Raceway
Drawing Menu.

115
________________
EE Raceway Modeling Reference Guide - February 2003

With the addition of RIS to the EE Raceway product, a distinction is now made between
schema 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 description
of the columns and tables of the database, and also identifies which users will be allowed to
use the database.

116
________________ Reports

Reports

6. Workflow
Currently, there are several reports delivered with the EE Raceway Modeling software: four
standard reports and a rule check report. You can access these reports from the EE Raceway
Drawing Menu by selecting the Report option. These reports run on the project and reference
databases.

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

117
________________
EE Raceway Modeling Reference Guide - February 2003

Interference Detection
Interference detection is processed through Plant Design software. However, the EE
Raceway Modeling product creates an envelope file for input to the Plant Design interference
detection task.

You will use the Interference Detection Envelope File Creation process to create the
envelope file needed for interference detection. This process reads the design file and then
creates 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 the
Interference Detection process.

118
________________ Precision Input Form

7. Precision Input Form


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

The precision input form is used to:

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

Input
7. Precision
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 in
view as long as you are working in the command. This section describes each button and
field 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 instructions
about changing the form design.

119
________________
EE Raceway Modeling Reference Guide - February 2003

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

Pressing <D> in a view for the placement of points simultaneously overrides


the active view setting.

To change the displayed working view, select the field, and scroll through the available views
until 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 a
command at any point by selecting Cancel.

Reject
Enters a negative response to an active prompt. It can also reset a current command action by
one 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 have
entered 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
________________ Precision Input Form

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

The Move (delta move) toggle allows you to specify the distance and
direction to place an active point. Using Move, you will select a directional
button and key in a distance to place a point. For example, by selecting
North and keying in 20, you move to a point that is 20 master units north
of the original active point.

Input
7. Precision
The Move To (absolute move) toggle allows you to place an active point at
an exact coordinate. Using Move To, you will select a directional button
and key in an absolute coordinate. For example, by selecting North and
keying 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 the
active system and one-line type. The middle field displays the active one-line type
specification 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/West
North/South
Elevation

The following two options are only available when placing ductbanks.

121
________________
EE Raceway Modeling Reference Guide - February 2003

Justification Point

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

By using the justification point and the height and width option described below, you can
build 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
________________ Construct Point

Construct Point
This command specifies a series of movement options before accepting the shortest distance
to 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 only
tentative until you select the Accept button. If you do select Accept, only the coordinates of
the last point you placed are accepted by the command. Selecting the Reject button
discontinues the command and returns you to the last point you placed before entering
Construct Point mode.

Midpoint/Any Point on Segment

Input
7. Precision
This command identifies a midpoint or any point on a segment at which to place an active
point. 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 enters
its midpoint.

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

1. Activate the Any Point option.

Select the Midpoint/Any Point command on the precision


input form, and set the toggle to Any Point if it is not already
active.

2. Identify Raceway One-Line Segment

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


point.

The command highlights the identified segment.

3. Raceway one line


Accept/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 previous


step to identify another one-line.

123
________________
EE Raceway Modeling Reference Guide - February 2003

4. Accept/reject end point

Press <D> to accept the highlighted endpoint as your reference


point.

— OR —

Press <R> to highlight the other segment endpoint, and then


press <D> to accept it as the reference point.

5. Specify Distance

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

The command calculates the distance from the endpoint and


then enters the point on the segment. If the specified distance
exceeds the length of the one-line, the command still
calculates the point from the endpoint, moving in the direction
of the segment.

— OR —

Select Accept to enter the active endpoint.

— OR —

Press <R> to return to Step 2.

124
________________ Extend/Reduce Run

Extend/Reduce Run
The Extend/Reduce Run command allows you to extend or reduce the length of an
upcoming run by the value you specify. The command accepts as values the height and width
of 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 active
point 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 an

Input
7. Precision
upcoming run by the value you specify.

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

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

The Reduce Run toggle allows you to reduce the length of an


upcoming segment by the value you specify.

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

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

125
________________
EE Raceway Modeling Reference Guide - February 2003

Distance and Direction


The Distance and Direction command specifies the distance and direction from an active
point to place a point or vertex. You can define distance with this command using the Move
To and Move toggles or by specifying the true length from an active point. You can define
direction 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 the
angles 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 be
defined.

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

Move - These options define the change in the selected coordinate for the point in
the 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 vertical
angles initially displayed.

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

126
________________ Distance and Direction

The direction is always determined by both the horizontal and the

Input
7. Precision
vertical angles.

The horizontal angle can be measured clockwise or counterclockwise. If clockwise, the


horizontal angle starts at the North coordinate (zero degrees). If counterclockwise, the
horizontal angle starts at the east coordinate (zero degrees). This option is set in the
PDS 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 to
the main Precision Input form.

— OR —

Select the Reset button or press <R> to reject the distance and direction option and
return 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 drawing
parameters in your design file. See
Runtime Setup Commands, page 287 for more information on the available commands.

127
________________
EE Raceway Modeling Reference Guide - February 2003

128
________________ 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, raceway
connect points (RCPs), drop points, and equipment pointer symbols – in the design file. You
can 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 for
routing one-lines around vessels and for inserting vertices in an existing one-line.

Commands

8. Design
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 an
identified one-line or RCP.

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

129
________________
EE Raceway Modeling Reference Guide - February 2003

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

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

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

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

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

130
________________ 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 the
design session.

Before Using These Commands


These commands require that you have an active system and one-line type defined in the
design file. See Setup Commands, page 253 and
Runtime 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 Conduit
Sizing command. Likewise, you must have ductbank one-lines placed before you can use the
Define Duct Cross Section command.

8. Design
You must be familiar with precision input and its functions before using any of the Design
commands, because it is through the Precision Input form that you will enter values for the
placement of points and for the location of raceway elements. For detailed information about
precision input, see
Precision 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 session
by pressing <Esc> or by selecting Cancel (X) on the precision input form. Pressing <R> or
selecting Reject on the precision input form will either reset the active command by one step
or reject a highlighted element in the design file.

131
________________
EE Raceway Modeling Reference Guide - February 2003

Place One-Line
This command places the centerlines of raceway elements based on points you give it. The
active 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 raceway
parameters 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 required
when you are changing the system, one-line type, or specifications of a one-line, or when you
place a fitting. Whenever you begin or terminate a one-line segment, you will have at least
one of five possible routing options. The following list describes each routing option in
detail:

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

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

Continue One-Line — If you identify an RCP for the beginning and/or termination
point, you can resume routing an existing one-line. You can also combine two existing
one-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 a
beginning and/or termination point.

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

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

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

132
________________ Place One-Line

In the above chart:

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

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

8. Design
First — Indicates that the one-line you are placing is assigned the parameters of the
first 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 not
allow 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 placed
on top of one another without establishing connectivity, though it is not a recommended
practice.

If the beginning or termination action is break, attach, or continue, then the identified
one-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-lines
must have all systems in common.

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

133
________________
EE Raceway Modeling Reference Guide - February 2003

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, page 119.

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. You must set an active one-line type and system in the design file. See
Set 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 Set
Raceway 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 routing
options 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 of
the 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, prompting
you to Enter first data point.

— OR —

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

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

134
________________ Route Around Vessel

Route Around Vessel


This command routes the active one-line type around a vessel (represented by an arc, circle, or
right cylinder) selected in either the active or reference design file. The arc, circle, or right
cylinder 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 and
around the vessel. If the RCP does not have a fitting, the route will come off the RCP at a 90
degree angle to the one-line.

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

8. Design
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, page 119.

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.

135
________________
EE Raceway Modeling Reference Guide - February 2003

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, which
you 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. You
cannot key in a negative value.

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

If you want the route to maintain the minimum distance all the way
around the vessel, be sure that the distance from the RCPs to the vessel
is 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
________________ 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. The
number 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.

8. Design

137
________________
EE Raceway Modeling Reference Guide - February 2003

Insert RCP
This command breaks an identified one-line in the design file and inserts a raceway connect
point (RCP).

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, page 119.

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 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-line
element, the system displays the message Element not found. The message
disappears when you identify a valid element.

138
________________ Insert RCP

3. Raceway one line


Accept/reject

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.

8. Design

139
________________
EE Raceway Modeling Reference Guide - February 2003

Rotate Cross Section


This command rotates a cross section using the current cross section rotation angle. For duct
bank cross sections, this command does not rotate duct bank’s cross section, but changes the
duct bank justification location.

You can change the rotation angle in the EE Raceway Defaults form, see Set Raceway
Defaults, page 256 for more information.

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, page 119.

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 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 cross
section, go to step 4. Otherwise continue to step 3.

140
________________ 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 when
you identify a valid cross section.

— OR —

Exit the command.

3. Data Point Accepts, Reset Rotates

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 orientation
angle.

— OR —

Press <R> to rotate the cross section.

The system rotates the cross section by the defined rotation angle. See Set Raceway
Defaults, page 256 for information about changing the angle of rotation.

Repeat this step.

8. Design
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
________________
EE Raceway Modeling Reference Guide - February 2003

Place Drop Point


This command places a drop point symbol in the design file. Drop points establish
connectivity between a RCP and a one-line. You can place drop points between RCPs and
one-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-line
type in the database. You can, for instance, establish connectivity between a piece of conduit
and a tray at the point where the cables drop out of the tray into the conduit. You can also
establish connectivity between two one-lines where graphic coincidence does not occur.

The values which determine priority status are defined in the


ee_priority_level column in the ol_type table; a higher number
indicates 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 by
determining the closest point on the one-line to the drop point symbol.

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, page 119.

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 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, the
system displays the message Element not found. The message disappears when you
identify a valid RCP.

142
________________ Place Drop Point

3. Raceway connect point


Accept/reject

Accept the highlighted RCP.

— OR —

Reject the highlighted RCP.

The system prompts you to identify another RCP. Go to step 2.

4. Identify Raceway One-Line

Identify a one-line in the design file. The identification point is the point at which the
system 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.

5. Raceway one line

8. Design
Accept/reject

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
________________
EE Raceway Modeling Reference Guide - February 2003

Place Equipment Pointer


This command places an equipment pointer symbol in the design file. An equipment pointer
symbol serves as a tag that identifies a particular piece of equipment. The equipment pointer
should match the corresponding symbol in the PDS Equipment Modeling product.

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, page 119.

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 Place Equipment Pointer command.

2. Identify Raceway RCP

Identify an RCP in the design file and accept it.

The system highlights a valid RCP. If you do not locate an acceptable element, the
system displays the message Element not found. The message disappears when you
identify a valid RCP.

— OR —

Press <R> to exit the command.

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
________________ Define Active Point

Define Active Point


This command defines a new active point in your design file.

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, page 119.

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

8. Design
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
________________
EE Raceway Modeling Reference Guide - February 2003

Set Active Parameters


This command sets the active parameters; active systems, one-line type, and raceway
parameters; to those of a one-line or RCP you identify.

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, page 119.

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 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 —

Press <R> to exit the command.

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 on
the highlighted element. The command exits automatically.

— OR —

Press <R> to reject the highlighted element. Return to step 2.

146
________________ Place Manual Fitting

Place Manual Fitting


This command identifies a unique part from the reference database and places it in the design
file at whatever orientation and location you specify.

You will use manual placement in situations where placing a sparse model will not be
sufficient or is not possible. For example, you may need to place fittings manually when
dealing with tight spaces, unusual angles, or fitting-to-fitting placement. You can place
special 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 active
point. If the active point lies in the vicinity of a fitting, the system locates the closest
attachment point on that fitting. If the new fitting and the existing one do not share the same
system and one-line type, then the system places the new fitting by itself. Such a fitting is
placed with its own RCP. When placing a straight section, or placing a fitting on the end of a
straight section, the system extends the one-line for that straight to terminate on the RCP of
the fitting. Otherwise, the new fitting is attached to the existing fitting and a one-line is
automatically placed.

When attaching a manual fitting to the placement point of another fitting (or a straight), the

8. Design
system derives the default orientation for placing the new fitting from the placement point.

147
________________
EE Raceway Modeling Reference Guide - February 2003

Commands

Define Active Point — Defines the active point in the design file for the placement of
fittings. 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 Active
Point, page 145 .

Set Active System — Displays the current active system and allows you to select a new
active system. See Set Active System, page 295 .

Set Active One-Line Type — Displays the current active one-line type and allows you to
select a new active one-line type. Selecting a new active one-line type updates the part
information 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 type
parameters in the design. Changing the active parameters updates the part information
elsewhere on the form. See Set Active Parameters, page 146 .

Field Descriptions
Type — Displays the active three-line type for the current specification. The list
contains 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 the
value 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 contains
all available subtypes (vertical, horizontal, inside vertical, etc.) for the active type and
subtype in the current specification. To change the displayed subtype, select a value
from the list. Modifying the value for Type also may change the active and available
subtypes.

Qualifier — Displays the active qualifier for the displayed Type and Subtype. The list
contains all available qualifiers (adjustable, rigid, etc.) for the active type and subtype in
the current specification. To change the displayed qualifier, select a value from the list.
Modifying Type or Subtype values may change the available qualifiers.

148
________________ Place Manual Fitting

Symbol — Displays the name of the Eden symbol you are placing. You can only
review the values in this field.

Angle — Displays the active angle associated with the Type, Subtype, and Qualifier
for the current specification. The list contains available angles. To change the
displayed angle, select an angle from the list or select the field, and key in the new
value.

When placing a fitting (such as a vertical tee), if the placepoints and


RCPs do not line up correctly, key in a negative angle, (-90 degrees) to
shift the RCPs and placepoints to the correct location.

Length — Displays the length by which to project a straight. If straight is not your

8. Design
active Type, the Length field does not display on the form. To change the displayed
length, select the field, and key in the new value.

Part — Displays the active part. The list contains all available parts for the current
specification. 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, and
Qualifier. 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. Doing so
displays a specification form.

149
________________
EE Raceway Modeling Reference Guide - February 2003

Column name - Displays the aliases of those columns in the database that are
associated with the specified type. You can only review the information in this column.

Column value - Displays the column name values currently associated with the
specified type. You can review and modify the values in this column. To change a
value, 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. To
display the codelist, select the *.

Select - Retrieves the row(s) from the specification table that meet the select criteria
defined in the form. If only one row matches this criteria, then the Column values fill
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
valid operators, see Annotate Element, page 178 .

Clear - Clears the Column values from the lower portion of the form, and then
automatically 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). You
can activate the Override button by selecting it directly or by selecting the Clear
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 specifications
for the current settings. Secondary specifications are generally used with reducers.

You can display the current specification itself by selecting the Display button. Doing
so 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 it
reaches the appropriate value.

Cutback Mode — Defines whether a straight section is to be cutback when placing a


manual fitting. If Cutback Mode is on, the existing RCP location is fixed. If Cutback
Mode is off, the RCP will be moved accordingly.

150
________________ Place Manual Fitting

Automatic Size — Automatically selects the correct size fitting. You must specify the
manual fitting type before using the button.

The fitting size is determined by comparing the spec table nominal size of all one-lines
at the RCP and selecting the largest nominal size among them. That nominal size is
then compared to the fitting table nominal sizes. If in the fitting table there is a nominal
size the same as the largest one-line nominal size, then that fitting is used. If there is no
fitting of that nominal size, 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 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 the
displayed angle, select the field, and key in a new value.

About - Defines the axis about which to rotate the orientation tee. To change the
displayed axis, select the field, and toggle between the three axes (Primary,
Secondary, Normal) until the appropriate axis displays.

— OR —

8. Design
Identify the appropriate axis name (text) on the orientation matrix diagram (to the right
of the Angle and About fields.)

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.

If you set the Driven By Spec/Table toggle to Table, the Place Manual Fitting form
displays.

151
________________
EE Raceway Modeling Reference Guide - February 2003

Field Descriptions
Table — Displays the active special part table from the database. The list contains the
available 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 Key
attributes 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 desired
Part Key.

For example, you set the active Table to cond_body. size, type, material, and vendor
display as the active attributes. Each attribute displays only those values that have
corresponding matching values for the other three attributes in the database. In other
words, if you set material to feraloy, vendor to 3, and size to 1/2 inch, then only those
types that are 1/2 inch in size from vendor 3 and made of feraloy will be displayed in
the types list. Similarly, if you set type to form 7c, material to feraloy, and vendor to
3, then only the sizes the form 7c comes in, made of feraloy from vendor 3, will be
displayed in the size list.

Select/All toggles — Overrides the interactive queries of the attribute fields. When set
to All, all available values for that attribute are displayed in the list, regardless of the
other attribute settings.

Part Key — Displays the current part for the displayed Table that matches the attribute
values. 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 Display
button.

See the description of the Spec1 field earlier in this section for detailed information
about the form parameters.

For information about the Placepoint and Rotate Orientation fields as


well as the form commands, see the descriptions earlier in this section.
These fields and the commands operate identically in either Driven By
Spec or Driven By Table modes.

152
________________ Place Manual Fitting

Before Using This Command


You should be familiar with precision input and its functions. For more information, see
Precision Input Form, page 119 .

When deciding whether your fitting information will come from a specification or from a
table in the database, you should first consider a few points. Specification-driven fittings rely
on the specification information (width, height, radius, etc.) to construct the three-line
symbols. All parts of a given specification will inherit the attributes of that specification. On
the other hand, some fittings derive their information from their own database tables because
they are not so easily classified into a common group of parts. Such fittings are called special
parts. The following table indicates fittings that are specification-driven and those that are
special parts:

Specification-Driven Fittings Special Parts

straight pullbox
elbow conduit body
wye light fixture
cross
dropout

8. Design
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 Driven
By Spec.

— OR —

To derive fitting attributes from a special part table in the database, set the toggle to
Driven By Table. Go to step 4.

3. Change fitting descriptions, orientations, and location until the desired fitting is seen in
dynamics (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
________________
EE Raceway Modeling Reference Guide - February 2003

5. Continue placing manual fittings.

— OR —

Exit the command.

154
________________ Conduit Sizing

Conduit Sizing
This command places cables (wires) in a conduit to determine the correct conduit size based
on the conduit’s percent fill calculation.

8. Design

155
________________
EE Raceway Modeling Reference Guide - February 2003

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 cables
in the database. This command also accepts certain relational operators as search
criteria. You should be familiar with the following operators:

Symbol Name Data Description


Type

= equal to numeric This is the default operator. If you do not enter another
operator, the system assumes =.

> greater than numeric This operator indicates that the queried values should
be greater than the given value.

< less than numeric This operator indicates that the queried values should
be less than the given value.

>= greater than numeric This operator indicates that the queried values should
or equal to be greater than or equal to the given value.

<= less than or numeric This operator indicates that the queried values should
equal to be less than or equal to the given value.

!= not equal to numeric This operator indicates that the queried values should
NOT be equal to the given value.

% wild card CHAR This operator is a wild card, representing zero or more
characters. The queried values must have every
character aside from the % in common with the given
value.

_ underline CHAR This operator is a wild card, representing a single


character. The queried values must have every
character aside from the underline in common with the
given value.

Code List — Indicates whether a Value has an associated code list. A code list is a list
of valid database values for that Column Alias. If an * displays in the column, then the
Value has an associated code list. To display the code list, select the *.

156
________________ Field Descriptions

Initialize Query — Clears all entries in the Value fields.

Process Query — Queries the database to find cables matching the search criteria
defined in the Value fields. If only one cable is found that matches the criteria, it is
added 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 the
conduit.

Increase Size ONLY / Increase/Decrease size — Defines how the conduit should be
sized. There are two methods to choose from:

— Increase Size ONLY - When a conduit is calculated to be full, the next size larger
conduit in the spec table is used until an adequately sized conduit is found.

8. Design
— Increase/Decrease size - The smallest conduit available in the spec that meets the
percent fill criteria is used.

Percent Fill — Displays how full the conduit is as a percentage. The field displays in
red and the message Warning: Percent Fill exceeds maximum allowed displays
when the conduit has reached its capacity as defined by the electrical code you are
using. The Percent Fill calculation is based on the conduit’s cross-sectional area
divided 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 in
the active conduit.

Select Conduit — Displays the Conduit Sizing precision input form. Using this form
you can select another conduit in which to route cables without having to exit the
command.

Copy Contents — Copies cables from a selected conduit into the active conduit. Any
cables in the active conduit before the copy are removed.

Append Contents — Adds cables from a selected conduit into the active conduit
leaving 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 available
only when Remove Cable is selected.

Quantity — Defines the number of cables of that type. This field can be edited to take
positive integers other than zero (zero and blank are invalid entries).

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, page 119.

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.

You must use the Set Conduit Sizing Attributes command to define how the conduit sizes
will 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 the
form 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 you
want.

158
________________ Field Descriptions

5. Select Accept to calculate and size the conduit.

If the largest size conduit available does not satisfy the percent fill calculation, a
warning message displays.

— OR —

Select Cancel to exit the command and ignore any changes you have made.

8. Design

159
________________
EE Raceway Modeling Reference Guide - February 2003

Insert One-Line Vertex


This command places a vertex in an existing one-line. To move an inserted vertex, use the
Move One-Line Vertex command, see Move One-Line Vertex, page 192 for more
information.

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, page 119.

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 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 the
vertex 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 repropagate
and the vertex will display with its cross-section.

— OR —

Press <R> to reject the one-line.

160
________________ Place Field Routed Raceway

Place Field Routed Raceway


The Place Field Routed Raceway command places short raceway sections from the raceway
model to equipment. These sections represent raceway components that are field routed by
the installer. For example, conduit less than a particular size is typically not modeled in the
plant model but is installed in the field by the installer. Similarly, there are instances where
the 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 are
needed to get appropriate material takeoff (MTO) reports and to facilitate cable routing. This
command is intended primarily to support field routed conduit and airways, but can also be
used for other raceway types that are field routed.

8. Design
Field Descriptions
Column name — Displays the aliases for the columns (attributes) in the reference
schema that unique identify equipment. The column names reside in the ee_unique
table in the reference schema. This field is informational only.

Column value — Defines a value for the corresponding equipment identifying attribute
in the Column name field. To change the value, select the field and key in the new
value.

Display — Enables or disables the annotation of the Column value. When on, the
value is displayed in the design. You are prompted to position the annotation after the
equipment pointer is placed in the design.

Keyin/Calculate — Defines the method for entering the distance from the beginning of
the 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 placed
one-line. This length represents the estimated length of raceway to the equipment from
the beginning point of the placed one-line. To change the displayed length, select the
field 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 the
location of the equipment. The software calculates the orthogonal distance (that is, sum
of the x, y, z deltas) from the beginning of the placed one-line to the identified
equipment location. The calculated distance is stored with the one-line as field routed
length.

First Point & Orientation/Beginning & Ending Point — Defines the method for
entering the plant coordinates of the one-line element. When placing the one-line
element using the First Point & Orientation method the Rotate Orientation gadgets
display.

After specifying the orientation and the length of the one-line, you are prompted for the
first point (that is, placement point) of the one-line element.

When placing the one-line element using the Beginning & Ending Point method, you
are 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 the
displayed angle, select the field, and key in a new value.

About — Defines the axis about which to rotate the orientation tee. To change the
displayed axis, select the field, and toggle between the three axis (Primary, Secondary,
Normal) until the appropriate axis displays. Or you can identify the appropriate axis
name (text) on the orientation matrix diagram (to the right of the Angle and About
fields.)

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.

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, select
the field, and key in a new value.

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, page 119.

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.

162
________________ Place Field Routed Raceway

Operator Sequence
1. Select the Place Field Routed Raceway command.

The precision input form displays.

2. Identify Raceway One-Line

Identify a one-line element to which you want to connect the field routed raceway
section 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.

8. Design

163
________________
EE Raceway Modeling Reference Guide - February 2003

Define Duct Cross Section


This command defines the cross section configuration of the contained conduit or cable for
underground duct banks. The duct bank will automatically resize after configuration to
accommodate the defined conduit or cable.

Field Descriptions
Button Matrix — Each button represents an area in the duct bank’s cross section that
extends the size of the duct bank. By assigning a conduit, cable or gap to a button, you
assign that area in the duct bank. All assigned buttons (areas) are then used to calculate
the duct bank’s cross section. Unassigned or unused buttons in the matrix are not used
in calculating the ductbank’s cross sectional size unless they are in the middle of
assigned buttons.

Copy section layout from — Copies an existing duct cross section layout from a
specified duct into the active duct.

164
________________ Define Duct Cross Section

Add — Assigns a conduit, cable or gap to a matrix button. A form displays all
available conduit/cables in the project database for the defined control number. The
conduit/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 new


assignment.

8. Design
Control Number — Displays the control number to use for retrieving the conduit/cable
information from the project database. You can define any control number that is
loaded to the project database.

You define whether you are routing conduit or cables by setting the Duct toggle in the
EE Raceway Defaults form. See Set Raceway Defaults, page 256 for more
information.

If conduit routing is selected, this information is retrieved from the drawing_numb


column of the cndsch_spec table. If cable routing is selected, this information is
retrieved from the drawing_numb column of the cabsch_spec table. These tables are
the cable/conduit schedule listings used for this project. The cable schedule is not the
same 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 is
measured from the center of the left conduit/cable to the center of the right
conduit/cable and can only be defined on the top row of buttons. The gap distance will
appear on the button after assignment.

165
________________
EE Raceway Modeling Reference Guide - February 2003

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, page 119.

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.

Define whether you are placing conduit or cables in the duct bank by setting the Duct toggle
in the EE Raceway Defaults form. Likewise, you can define a margin width, a space
between the button matrix and the outside of the ductbank in the EE Raceway Defaults form.
See
Set Raceway Defaults, page 256 for more information.

Steps
1. Select the Define Duct Cross Section command.

The precision input form displays.

2. Identify duct element

Select the duct bank element for which to define the cross section layout and accept it
with <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 duct
one-line. The duct bank size is checked and resized as necessary, both width and
height. 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 warning
form displays confirming that you want to exit without saving changes. If
you select Confirm (√) on the warning form, any changes you made will be
ignored. If you select Cancel on the warning form, you cancel your "exit
without saving" and are returned to the command.

166
________________ Place Stub Up

Place Stub Up
This command manipulates conduit stub ups. Stub ups are pieces of conduit associated with a
conduit or cable contained in an underground duct bank and are placed in the raceway model
for making above ground conduit connections. The stub up is connected to the corresponding
underground duct bank section by means of a drop point.

8. Design
Before Using this Command
You must define conduit as an available one-line type using the Define One-Line Type
command. See Define One-Line Type, page 260 .

You must define conduit as the active one-line type using the Set Active One-Line Type
command. See Set Active One-Line Type, page 294 .

You must define the conduit sizing attributes using the Set Conduit Sizing Attributes
command. See Set Conduit Sizing Attributes, page 268 .

You must define the duct cross section layout using the Define Duct Cross Section
command. See Define Duct Cross Section, page 164 .

You must select the a conduit specification using the Set Active One-Line Type Parameters
command. 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 sizes
available.

167
________________
EE Raceway Modeling Reference Guide - February 2003

Field Descriptions
Button Matrix — Each button represents an area in the duct bank’s cross section that
has or has not been assigned during the Define Duct Cross Section command. This
matrix is used in the Change Association and Place Stub Up options to identify which
cross section (that is, conduit/cable) to manipulate.

Select Duct Segment — Selects an existing duct segment in the raceway model as the
active duct segment.

Delete Stub Up — Deletes a conduit stub up.

Change Association — Changes the association of a conduit stub up from the currently
associated 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 a
conduit/cable in the active duct segment.

Stub Up Size — After selecting the Place Stub Up button and selecting a
conduit/cable from the active duct segment, this field displays the associated conduit
stub up size. You can optionly override the displyed value by selecting a conduit stub
up size from the available sizes as determined by matching the conduit sizing attributes
to the active conduit specification.

If underground conduit routing is selected for this model, the size of stub up will be
retrieved from the conduit schedule table in project schema based upon conduit number
that user selected from matrix.

If underground cable routing is selected for this model or the conduit size is not defined
for the conduit number, you are required to select the desired size from the available
sizes. The displayed value is simply the value from the previous place stub up
selection.

Stub Up Length — Displays the conduit stub up length as measured in the model
master units (feet, meters) The user can optionally override the displayed value.

168
________________ 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.

8. Design
— OR —

Select Cancel (X) to exit the command.

3. Select the Select Duct Segment option.

The precision input form displays.

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.

5. Raceway one line


Accept/reject

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
________________
EE Raceway Modeling Reference Guide - February 2003

6. Select the Delete Stub Up option.

The precision input form displays.

7. Identify stub up element

Identify a stub up one-line in the design file.

The identified element highlights.

— OR —

Exit the option. Go to Step 2.

8. Raceway one line


Accept/reject

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 —

Reject the highlighted element. Go to Step 7.

9. Select the Change Association option.

Select stub up for modification. is displays in the form message field. The precision
input form displays.

10. Identify stub up element

Identify a stub up one-line in the design file.

The identified element highlights.

— OR —

Exit the option. Go to Step 2.

11. Raceway one line


Accept/reject

Accept the highlighted element.

— OR —

Reject the highlighted element. Go to Step 10.

12. Conduit/Cable Number = [conduit/cable number]


Select another cable/conduit to modify existing stub up.

170
________________ 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.

The precision input form displays.

17. Select location to place stub up.

8. Design
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 system
places the stub up and connects it to the duct bank by means of a drop point located on
the 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
________________
EE Raceway Modeling Reference Guide - February 2003

172
________________ Modify Commands

9. Modify Commands
The Modify commands manipulate elements, such as RCPs, one-lines, and three-lines, within
the design file. Available element manipulations include copying, moving, deleting,
annotating, and propagation. You can elect to manipulate either single elements or those
elements 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 serious
problems and/or destroy the EE Raceway model. Use only these EE Raceway
modify commands to manipulate EE Raceway elements.

The Modify palette is activated by selecting Modify from the EERWAY Command Menu
Bar, then selecting Palette.

Commands
The commands on the Modify palette both activate other command palettes. These palettes
and their commands will be described in this chapter.

Modify Element Commands — Manipulate single elements within the design file.

9. Modify
Modify Group Commands — Define elements for inclusion in a group and
manipulate elements belonging to the active group.

173
________________
EE Raceway Modeling Reference Guide - February 2003

Using the Modify Commands


When to Use These Commands
Once you have performed the necessary setups, you can use these commands throughout the
design session. For reliable results, you should use these commands, not MicroStation
manipulation commands, any time you are modifying raceway elements.

Before Using These Commands


These commands require that you have existing raceway elements in your design file (see the
Design Commands, page 129 for information about placing elements in the model). You
must also have an active system and one-line type defined in the design file. See
Setup Commands, page 253 and Runtime 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 Modify
commands, because it is through the Precision Input form that you will enter values for the
placement of points and for the location of raceway elements. For detailed information about
precision input, see
Precision Input Form, page 119 .

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

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

174
________________ Modify Element Commands

Modify Element Commands


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.

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.

Commands

Annotate Element — Places, reviews, and edits intelligent annotation for raceway elements.

9. Modify
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 existing
elements.

Move One-Line Vertex — Moves an internal one-line vertex.

Propagate Element — Expands one-line elements into three-dimensional elements.

175
________________
EE Raceway Modeling Reference Guide - February 2003

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.

176
________________ Using the Modify Element Commands

Using the Modify Element Commands

When to Use These Commands


Once you have performed the necessary setups, you can use these commands throughout the
design session. For reliable results, you should use these commands, not MicroStation
manipulation commands, any time you are modifying raceway elements.

Before Using These Commands


These commands require that you have existing raceway elements in your design file (see
Design Commands, page 129 for information about placing elements in the model). You
must also have an active system and one-line type defined in the design file. See
Setup Commands, page 253 and
Runtime 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 Modify
Element commands, because it is through the Precision Input form that you will enter values
for the placement of points and for the location of raceway elements. For detailed information
about precision input, see
Precision Input Form, page 119 .

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

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

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.

177
________________
EE Raceway Modeling Reference Guide - February 2003

Annotate Element
This command places, reviews, and edits intelligent annotation for individual raceway
elements. By definition, intelligent annotation is recognized by the EE Raceway product and
can be added to an EE database. You can also add cosmetic text to a raceway model for
display purposes, though the product does not recognize such annotation nor 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 the
annotation.

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
________________ Field Descriptions

Field Descriptions
Column name — Displays the aliases for those columns in the database that are
associated with the specified element. The displayed columns reside in the mscolumns
table 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 the
Column 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 new value. 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 text value for
an attribute will override that value in the reference database. To delete an override on
a reference database attribute, select the Column value field and delete the blank
character. Once you have deleted the override, a value will display in the field only if
the value can be retrieved from the reference database. Otherwise, the field remains
null.

If blanks exist for a field, the cursor will jump to the end of the blanks
when the field is tagged beyond value.

Source — Displays the source of the corresponding column value. If Ref displays in
the column, then the value derives from the reference database. If Dgn displays in the
column, then the value derives from the design file. If you change a column value, 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 Ref or Dgn, where
New had displayed. Where UD displays in the column, the corresponding column
value 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. To
display the codelist, select the *.

9. Modify
Access — Indicates whether or not you can manipulate a particular column value. If
you can view and modify (read and write) the column value, the Access column
displays a R/W. If you can only view (read) the column value, then it will display an
R. 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. 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 the
reference database.

When you enter a new value in the EE Reference Database Key field, 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 displays and the annotation form returns to the previous values. Any
annotation you placed in the drawing will override the reference database defaults on
the 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 be
retrieved 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 or
the Default key will be used to locate default data. If the linkage is not present on a
connect point or one-line, the key specified in the user element is used. If no key exists
in the user element, the Default key is used. Once you place an override key on an
element, 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 current
EE Reference Database Key. You can only review the information in this field.

The lower portion of the Active [One_Line Type] Parameters form displays a
specification table. The EE spec key field on the upper portion of the form is used as
the 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 criteria
defined in the form. The select criteria are those values that display in the Column
value column on the lower portion of the annotation form. You can use relational
operators when keying in your own select criteria. Available operators are described
later in this section.

If only one row matches the select criteria you provide, then the Column values fill in
with the matching row’s values. If more than one row matches the criteria, then a
second form containing all matching rows displays.

From this form you can select the row(s) containing the desired values. To add values
from the displayed specification table rows, select the row you want, and then select
Confirm (√). If you select Cancel (X), the system cancels the form and retrieves the
values from the EE spec key field on the original form.

Clear — Clears the Column values from the lower portion of the form, and then
automatically depresses the Override button to select a different row(s) from the
specification 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 Read
Only (R). You can activate the Override button by selecting it directly or by selecting
the Clear button, which automatically activates it.

180
________________ Field Descriptions

This command accepts certain relational operators as search criteria. You should be familiar
with the following operators:

Symbol Name Data Description


Type

= equal to numeric This is the default operator. If you do not enter another
operator, the system assumes =.

> greater than numeric This operator indicates that the queried values should be
greater than the given value.

< less than numeric This operator indicates that the queried values should be
less than the given value.

>= greater than numeric This operator indicates that the queried values should be
or equal to greater than or equal to the given value.

<= less than or numeric This operator indicates that the queried values should be
equal to less than or equal to the given value.

!= not equal to numeric This operator indicates that the queried values should
NOT be equal to the given value.

% wild card CHAR This operator is a wild card, representing zero or more
characters. The queried values must have every
character aside from the % in common with the given
value.

_ underline CHAR This operator is a wild card, representing a single


character. The queried values must have every character
aside from the underline in common with the given

9. Modify
value.

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, page 119.

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.

181
________________
EE Raceway Modeling Reference Guide - February 2003

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, or
RCP).

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.

— 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 the
current 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 to
Step 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 drag
mode 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. When
there are no more values to place, return to Step 2.

182
________________ Field Descriptions

Any value placed with the Annotate Element command will be entered
into the drawing and, optionally, displayed. When you load the project
database, these values are loaded into the project database.

When you annotate any raceway element, if you see graphics extending
into the next raceway element, repropagate all of the connected raceway
elements.

9. Modify

183
________________
EE Raceway Modeling Reference Guide - February 2003

Copy Element
This command copies raceway elements to specified locations within the design file. You can
use this command to copy one-lines and their associated elements. This command will copy a
single RCP provided that no one-lines are attached.

Equipment pointers and drop points cannot be copied using this command.

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, page 119.

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.

184
________________ Steps

Steps
1. Select the Copy Element command.

The Copy Element precision input form displays.

2. Identify Raceway One-Line or RCP

Identify the one-line or RCP element you intend to copy 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. 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.

9. Modify

185
________________
EE Raceway Modeling Reference Guide - February 2003

Move Element
This command moves 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 moved, 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 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, and
equipment pointers will also be moved.

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, page 119.

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.

186
________________ Steps

Steps
1. Select the Move Element command.

The Move Element precision input form displays.

2. Identify Raceway element

Identify the element you intend to move 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.

— OR —

Press <R> to exit the command.

3. Enter placement point

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.

9. Modify

187
________________
EE Raceway Modeling Reference Guide - February 2003

Clone Element
This command copies raceway elements multiple times to specified locations within the
design file. You can use this command to copy one-lines and their associated elements. This
command will copy a single RCP provided that no one-lines are attached.

Equipment pointers and drop points cannot be copied using this command.

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, page 119.

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.

188
________________ Steps

Steps
1. Select the Clone Element command.

2. Identify Raceway One-Line or RCP

Identify the element you want to clone (copy) and accept it with <D>. The point you
identify the element with becomes the origin of the copy.

The element highlights.

— OR —

Press <R> to exit the command.

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 identified
element.

4. Confirm (√) the number of times to clone the element.

— OR —

Cancel the form and reenter the number of clones.

5. Enter placement point

Identify the location of the first copy. If you are placing more than one clone, each

9. Modify
successive clone is placed the same distance and direction from the previous clone as
the first clone is from the original element.

The clone elements are placed in the design file.

Return to step 2.

189
________________
EE Raceway Modeling Reference Guide - February 2003

Move One-Line Segment


This command moves one-line segments. Segments attached to the moved one-line segment
will stretch or shrink to maintain connections with the moved one-line segment. If the first or
last segment of a one-line is moved, the attached RCP will also move. Any one-lines attached
to 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 RCP
and the drop point are coincident.

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, page 119.

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.

190
________________ 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 be
reference point used when placing the one-line segment at the new
location.

The selected one-line segment highlights.

— OR —

Press <R> to exit the command.

3. Enter data point to place

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 will
automatically repropagate after the move. See
Propagation Setup, page 297 for more information on this toggle.

9. Modify

191
________________
EE Raceway Modeling Reference Guide - February 2003

Move One-Line Vertex


This command moves a one-line vertex. Any segments attached to a moved vertex will
stretch 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 is
associated with the RCP, also move with the vertex.

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, page 119.

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 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-line
is automatically selected.

The selected vertex highlights.

— OR —

Press <R> to exit the command.


192
________________ Move One-Line Vertex

3. Enter data point to place

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-line
will automatically repropagate after the move. See
Propagation Setup, page 297 for more information on this toggle.

9. Modify

193
________________
EE Raceway Modeling Reference Guide - February 2003

Propagate Element
This command expands one-line segments and RCPs into three-dimensional elements (a
process called propagation). Manually placed or edited fittings will propagate exactly as
placed. All other element will propagate depending on the specific situation of the element.

To view errors that occur during propagation, select the Highlight Propagation Errors
command, see
Highlight Propagation Errors, page 314 . This command displays to the screen the pro.err
file, 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 some
of the delivered fittings follows the operating sequence in this section.

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, page 119.

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.

You can set active parameters for propagation through the Propagation Setup form. For
information about the form, see Propagation Setup, page 297 .

194
________________ Propagate Element

Steps
1. Select the Propagate Element command.

The Project Run precision input form displays.

2. Identify Raceway element

Identify a raceway one-line or RCP.

The system highlights the specified element. If you do not locate an acceptable one-line
or RCP, the system displays the message Element not found. The message disappears
when you identify a valid element.

— OR —

Exit the command. Go to step 1.

3. Accept/reject

Accept the highlighted element.

The system propagates the identified one-line and returns you to step 2 to continue
identifying elements for propagation.

— OR —

Reject the highlighted element. Go to step 2.

Fittings

9. Modify
This section describes some of the fittings available with the delivered raceway one-line
types. The attributes associated with each fitting are contained in the tray_part table in the
reference database. For information about this table, see
Specification, 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-line


segments 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
________________
Propagate Element

Conduit Fittings

9. Modify

197
________________
EE Raceway Modeling Reference Guide - February 2003

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 list
contains 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 the
value 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 contains
all available subtypes (vertical, horizontal, inside vertical, etc.) for the active type and
subtype in the current specification. To change the displayed subtype, select a value
from the list. Modifying the value for Type also changes the active and available
subtypes.

Qualifier — Displays the active qualifier for the displayed Type and Subtype. The list
contains all available qualifiers (adjustable, rigid, etc.) for the active type and subtype in
the 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 only
review the values in this field.

Angle — Displays the active angle associated with the Type, Subtype, and Qualifier
for the current specification. The list contains available angles. To change the
displayed angle, select an angle from the list or select the field, and key in the new
value.

198
________________ Edit/Insert Manual Fitting

When placing a fitting (such as a vertical tee), if the placepoints and RCPs do
not line up correctly, key in a negative angle, (-90 degrees) to shift the RCPs
and placepoints to the correct location.

Length — Displays the length by which to project a straight. If straight is not your
active Type, the Length field does not display on the form. To change the displayed
length, select the field, and key in the new value.

Part — Displays the active part. The list contains all available parts for the current
specification. To change the displayed part, select a value from the list. You can also
change any of the values for Type, Subtype, Qualifier, Spec1, and (if applicable)
Spec2.

Spec1 — Displays the active specification for the displayed Type, Subtype, and
Qualifier. 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.

9. Modify
The specification form has these parameters:

— Column name - Displays the aliases of those columns in the database that are
associated with the specified type. You can only review the information in this
column.

— Column value - Displays the column name values currently associated with the
specified type. You can review and modify the values in this column. To change a
value, select the Override button. Then select the field, and key in a new value.

199
________________
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 an associated codelist. To
display the codelist, select the *.

— Select - Retrieves the row(s) from the specification table that meet the select criteria
defined in the form. If only one row matches this criteria, then the Column values
fill 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 valid
operators, see Annotate Element, page 178 .

— Clear - Clears the Column values from the lower portion of the form, and then
automatically 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).

You can activate the Override button by selecting it directly or by selecting the
Clear 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 specifications
for the current settings. Secondary specifications are generally used with reducers.

You can display the current specification itself by selecting the Display button. Doing
so 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 it
reaches 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-lines
at the RCP and selecting the largest nominal size among them. That nominal size is
then compared to the fitting table nominal sizes. If in the fitting table there is a nominal
size the same as the largest one-line nominal size, then that fitting is used. If there is no
fitting of that nominal size, 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 fitting available is used.

Automatic Fit — Correctly orients the fitting to the one-lines.

Rotate Orientation — These fields define the orientation matrix:

200
________________ Edit/Insert Manual Fitting

— Angle - Defines the angle by which to rotate the orientation tee. To change the
displayed angle, select the field, and key in a new value.

— About - Defines the axis about which to rotate the orientation tee. To change the
displayed 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
right of the Angle and About fields.)

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.

If you set the Driven By Spec/Table toggle to Table, the form changes.

Field Descriptions

9. Modify
Table — Displays the active special part table from the database. The list contains the
available 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 Key
attributes 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 desired
Part Key.

For example, you set the active Table to cond_body. size, type, material, and vendor
display as the active attributes. Each attribute displays only those values that have
corresponding matching values for the other three attributes in the database. In other
words, if you set material to feraloy, vendor to 3, and size to 1/2 inch, then only those
types that are 1/2 inch in size from vendor 3 and made of feraloy will be displayed in
the types list. Similarly, if you set type to form 7c, material to feraloy, and vendor to
3, then only the sizes the form 7c comes in, made of feraloy from vendor 3, will be
displayed in the size list.

201
________________
EE Raceway Modeling Reference Guide - February 2003

Select/All toggles — Overrides the interactive queries of the attribute fields. When set
to All, all available values for that attribute are displayed in the list, regardless of the
other attribute settings.

Part Key — Displays the current part for the displayed Table. The list contains all
available 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 Display
button.

See the description of the Spec1 field earlier in this section for detailed information
about the form parameters.

For information about the Placepoint and Rotate Orientation fields as well as
the form commands, see the descriptions earlier in this section. These fields
and the commands operate identically in either Driven By Spec or Driven By
Table modes.

Before Using This Command


You should be familiar with precision input and its functions. For more information, see
Precision Input Form, page 119 .

When deciding whether your fitting information will come from a specification or from a
table in the database, you should first consider a few points. Specification-driven fittings rely
on the specification information (width, height, radius, etc.) to construct the three-line
symbols. All parts of a given specification will inherit the attributes of that specification. On
the other hand, some fittings derive their information from their own database tables because
they are not so easily classified into a common group of parts. Such fittings are called special
parts. The following table indicates fittings that are specification-driven and those that are
special parts.

Specification-Driven Fittings Special Parts

straight pullbox
elbow conduit body
wye light fixture
cross
dropout

202
________________ Edit/Insert Manual Fitting

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 —

Press <R> to exit the command.

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 Driven
By Spec.

— OR —

To derive fitting attributes from a special part table in the database, set the toggle to
Driven 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.

9. Modify

203
________________
EE Raceway Modeling Reference Guide - February 2003

Modify One-Line
This command modifies the route of an existing one-line. You cannot modify the termination
points 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 line
weight; the other segment appears as a dashed line. The dashed segment will then be
modified. You can reverse the segment to be modified by pressing <R>.

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, page 119.

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 Modify One-Line command.

The Modify One-Line 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, the
system displays the message Element not found. The message will disappear when
you identify a valid element.

204
________________ Modify One-Line

3. Raceway one-line
Accept/reject

Accept the highlighted element. Accepting the element identifies the one-line for
modification.

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 this
step.

— 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 the
last segment drawn. To terminate the new routes, place a data point on the original

9. Modify
one-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.

6. Data Point Accepts, Reset Rotates

Accept the cross section, and return to step 2.

The system saves the rotation and returns to the beginning of the command, prompting
you 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 continue
rotating it.

7. Accept the rotation and return to step 2.

— OR —

Continue rotating the cross section.

206
________________ 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 the
reference database. For example, one rule might define that at a 90 degree intersection of two
conduits, a LB fitting be placed. You can add to or replace the delivered rule set by editing
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 the
RCP and selecting the largest nominal size among them. That nominal size is then compared
to the fitting table nominal sizes. If in the fitting table there is a nominal size the same as the
largest one-line nominal size, then that fitting is used. If there is no fitting of that nominal
size, 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 fitting
available is used.

The spec table and the fitting table are defined in the rule.

9. Modify
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, page 119.

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. You must define the rules in the reference database. See
EE Databases, page 425 for a list of the delivered default rules.

207
________________
EE Raceway Modeling Reference Guide - February 2003

Steps
1. Select the Place Fitting by Rule command.

2. Identify Raceway Fitting or RCP

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 find
a rule that applies. displays. Otherwise the correct fitting as defined by the rule is
placed on the RCP.

— OR —

Press <R> to exit the command.

208
________________ Combine Coincident RCPs

Combine Coincident RCPs


This command is used to check for coincident RCPs in the design file. If coincident RCPs are
found and can be combined, you are given a choice of which RCP to keep. RCPs can be
combined 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 displays
and the command exits.

— OR —

If coincident RCPs are found, the Combine Coincident RCPs form displays listing the
coincident RCP information.

Each set of coincident RCPs is listed in the form separated by the horizontal dotted line. 9. Modify

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 RCPs
can be merged. If Invalid, then you need to fix the coincident RCPs in your
model.

209
________________
EE Raceway Modeling Reference Guide - February 2003

2. For each set of coincident RCPs, select the RCP information on the form to highlight
the 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
________________ 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 found
displays 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 the
form to highlight that one-line in the model.

9. Modify
3. Choose which one-line out of each set you want to keep. The Status of the one-line
you 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-line
you wanted to keep changes to Kept.

5. Continue to select the one-line to keep and deleting the other. Select Cancel when
finished.

211
________________
EE Raceway Modeling Reference Guide - February 2003

Delete Element
This command removes elements from the design file. You can use this command to delete
one-lines, RCPs (only if no one-lines are attached), cosmetic graphics, drop points, equipment
pointers, and annotation.

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, page 119.

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 Delete Element command from the menu.

The Delete Element precision input form displays.

2. Identify Raceway element

Identify an element for deletion.

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.

212
________________ Delete Element

— OR —

Press <R> to exit the command.

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 cross
sections, 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.

9. Modify

213
________________
EE Raceway Modeling Reference Guide - February 2003

Remove RCP
This command removes a raceway connect point (RCP) from the design file. You cannot use
the 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.

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, page 119.

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.

214
________________ Remove RCP

Steps
1. Select the Remove RCP command.

The Remove RCP precision input form displays.

2. Identify Raceway RCP

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 when
you identify a valid RCP.

— OR —

Press <R> to exit the command.

3. Raceway connect point


Accept/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 the
screen.

— 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.

9. Modify

215
________________
EE Raceway Modeling Reference Guide - February 2003

Delete Fitting
This command deletes the raceway fitting from a selected RCP, useful for removing manually
placed 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.

2. Identify Raceway Fitting or RCP

Select the fitting, or the fitting’s RCP, to delete.

— OR —

Press <R> to exit the command.

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
________________ 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.

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, page 119.

At any point during this operating sequence, you can exit the command session either by

9. Modify
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 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-line
is automatically selected.

The selected vertex highlights.

— OR —

Press <R> to exit the command.


217
________________
EE Raceway Modeling Reference Guide - February 2003

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
________________ Minimize Joints

Minimize Joints
This command reduces to a minimum the number of vertices in an identified one-line, while
retaining the original geometry of the one-line. If automatic propagation is toggled on, the
command will repropagate the one-line. (See Propagation 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 this


command to be visible.

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

9. Modify
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, page 119.

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.

219
________________
EE Raceway Modeling Reference Guide - February 2003

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, the
system displays the message Element not found. The message will disappear when
you identify a valid element.

3. Raceway one line


Accept/reject

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
________________ Change System Parameters

Change System Parameters


This command changes the system parameters, the system Percent and the Project Rule, for
the systems associated with a single raceway element.

Field Descriptions
Primary System — Displays the primary system. The primary system determines the
symbology of the elements.

Project Rule Set — Displays the Project Electrical Code from the your project
schema’s project table. This is defined in EEmgr with the EE CMS Project Definition
process. The Project Rule Set determines which rules can be assigned to the active
systems. If the Project Rule Set is not defined, Project Rules cannot be assigned.

Systems — Displays all the systems associated with the selected element.

9. Modify
Percent — Specifies the current Percent space allocation assigned to each of the
selected systems. The total Percent space allocation cannot exceed 100 percent. The
total of the system Percents is displayed in the field at the bottom of the Percent
column. All the selected systems percentages are summed to calculate the total
percentage. The Percent represents the portion of the raceway’s width assigned to that
system. This Percent is used when calculating the cable fill of the raceway section in
the EECMS product.

Project Rule — Displays the Project Rule assigned to each of the selected systems for
calculating raceway fill. When a row is selected, a list of available rules for the Project
Rule Set defined with the EE CMS Project Definition process is displayed for review
and selection. To clear the Project Rule, select the row and select the Cancel (X) on the
list of Rules.

List — Indicates whether or not a Project Rule can be assigned. If an * displays in the
List column, then the Project Rule can be assigned. To display a list of available rules
for the Project Rule Set defined with the EE CMS Project Definition process, select the
*.

221
________________
EE Raceway Modeling Reference Guide - February 2003

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, page 119.

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 Change System Parameters command.

The precision input form displays.

2. Identify Raceway element

Identify an element in the design file.

The identified element highlights.

— OR —

Exit the command.

3. Raceway [element]
Accept/reject

Accept the highlighted element.

4. Set up the form parameters to meet your specifications.

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 selected
element.

222
________________ Modify Group Commands

Modify Group Commands


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.

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.

Topics

9. Modify
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.

223
________________
EE Raceway Modeling Reference Guide - February 2003

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.

224
________________ Using the Modify Group Commands

Using the Modify Group Commands

When to Use These Commands


Once you have performed the necessary setups, you can use these commands throughout the
design session. For reliable results, you should use these commands, not MicroStation
manipulation commands, any time you are modifying raceway elements.

Before Using These Commands


These commands require that you have existing raceway elements in your design file (see
Design Commands, page 129 for information about placing elements in the model). You
must also have an active system and one-line type defined in the design file. See
Setup Commands, page 253 and
Runtime 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 Modify
Group commands, because it is through the Precision Input form that you will enter values
for the placement of points and for the location of raceway elements. For detailed information
about precision input, see
Precision Input Form, page 119 .

Group Workflow
You must use the Define Group command to create and activate an element group before

9. Modify
using other Modify Group commands.

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

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.

225
________________
EE Raceway Modeling Reference Guide - February 2003

Define Group
This command compiles a group from elements you specify. A group is a temporary
association of Raceway elements in your model. Once you have defined a group of Raceway
elements 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 their
contents.

All groups you create using this command are dropped when you exit the EE Raceway design
session.

Single Element/Entire Group — Determines how Modify Group commands will act
upon existing groups. If the toggle is set to Single Element, then a command will
prompt you to accept/reject every element within a specified group before performing
the command action. If the toggle is set to Entire Group, then a command will prompt
you once to accept/reject the specified group as a whole before performing the
command action.

Use caution when you are manipulating groups in Entire Group mode. The
system prompts you just once to accept/reject a group for manipulation.

Available Groups — Lists the groups you have already created. The active group is
highlighted in the list. The key-in field above the list accepts input for group name
when you are defining a new group. To change the active group, select a group from
the 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 Element
Types list. The system adds the elements using the selection method you specified in
the Graphic Method list.

226
________________ Define Group

To initiate the Create operation, select the button, key in a group name, and select
Accept. The system then compiles a group according to your specifications. When
processing is complete, review the form Message Area for information about the
number of elements the new group contains.

Drop — Removes the active group (the highlighted group in the Available Groups
list).

To initiate the Drop operation, select a group from the Available Groups list, select
Drop, 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 existing
group. The system compiles the elements using the selection method you specified in
the Graphic Method list.

To initiate the Add to operation, select an existing group from the Available Groups
list, select Add to, and then select Accept. The system compiles the elements using the
selection method you specified in the Graphic Method list. When processing is
complete, review the form Message Area for information about the number of elements
added to the group.

Drop from — Removes elements you specify in the EE Element Types list from an
existing group. If you remove all elements from a group, the system automatically
drops the entire group.

To initiate the Drop from action, select an existing group from the Available Groups
list, select Drop from, and then select Accept. The system drops the elements using

9. Modify
the selection method you specified in the Graphic Method list. When processing is
complete, review the form message display for information about the number of
elements 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 automatically
highlights the group contents in the drawing.

Clear Hilite — Clears all highlighting placed in the design when you use the Hilite
command.

EE Element Types — Displays all available element types available for inclusion in or
deletion from a group. Types include one-lines, three-lines, RCPs, drop points, to
equipment, and all annotation. You must choose at least one element type when
creating, 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 EE
Element Types list. You can use the three options in this list to restrict the elements in
your 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 your
group.

You can select individual one-line types from this list, or you can select all displayed
one-line types (using Select All). Clear All cancels the selections you have made from
the 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 (√) your
selections before you can select the Accept button on the main form.

– Attributes - Displays a list of available element types from which you can define
selection attributes.

228
________________ Define Group

When you select an element type from this list, an attribute list form displays for that
element type in which you can specify the attributes to include in the group
identification.

Once you have defined the attributes, select the Accept button on the main form. To
reset 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. You
will use these methods to identify elements for group creation, insertion into groups, or
deletion from groups. These methods can serve to further restrict the element types you
are including in your group.

For example, if you identified one-line trays for insertion into a group, and select Fence
Block from this list, the system inserts into the group only those one-line trays
contained within the fence you place.

– Selection - Prompts you to identify specified element types in the design file to drop
from or include in a group.

– Fence Block - Drops from or includes in a group those specified element types
contained within a fence block you place in the design.

– Fence Shape - Drops from or includes in a group those specified element types
contained within a fence shape you place in the design.

– View - Drops from or includes in a group those specified elements types contained in
a view you identify.

– All Elements - Drops from or includes in a group all specified element types in the
design.

9. Modify

229
________________
EE Raceway Modeling Reference Guide - February 2003

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 define
which elements to place in the group and how you want to select them in the design
file.

— 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 the
bottom 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 you
want.

4. Select one of the group modification commands.

230
________________ 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 the
defined group.

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, page 119.

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.

You must define a temporary group of elements, using the Define Group command, see
Define Group, page 226. Placing a fence around elements in the design also constitutes a
group 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.

9. Modify
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
________________
EE Raceway Modeling Reference Guide - February 2003

3. Raceway [element]
Accept/reject

Accept the highlighted element.

— OR —

Reject the highlighted element.

The system highlights another group element if any elements remain uncopied. Repeat
this 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.

6. Enter placement point

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 remain
uncopied, 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
________________ Annotate Element by Group

Annotate Element by Group


This command places, reviews, and edits intelligent annotation for some or all raceway
elements associated with a specified group. Intelligent annotation is recognized by the EE
Raceway product and can be added to an EE database. You can also add cosmetic text to a
raceway model for display purposes, though the product does not recognize such annotation
nor 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 the
annotation (read only access).

Using this command, you can change the specifications or sizes of raceway components.

9. Modify
Field Descriptions
Column name — Displays the aliases for those columns in the database that are
associated with the specified element. The displayed columns reside in the mscolumns
table 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 the
Column 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 new
value. 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 text
value for an attribute will override that value in the reference database. To delete an
override on a reference database attribute, select the column value field and delete the
blank character. Once you have deleted the override, a value will display in the field
only if the value can be retrieved from the reference database. Otherwise, the field
remains null.

233
________________
EE Raceway Modeling Reference Guide - February 2003

If blanks exist for a field, the cursor will jump to the end of the blanks when
the field is tagged beyond value.

Source — Dislays the source of the corresponding column value. If Ref displays in the
column, then the value derives from the reference database. If Dgn displays in the
column, then the value has been defined from the design file. If you change a column
value, 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 Ref
or Dgn, where New had displayed. Where UD displays in the column, the
corresponding column value comes from user data. When modified, the value is saved
back to user data.

List column — 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.
To display the codelist, select the *.

Access column — Indicates whether or not you can manipulate a particular column
value. If you can view and modify (read and write) the column value, the Access
column displays a R/W. If you can only view (read) the column value, then it will
display an R. You can only review the information in this column.

Display On/Off — This toggle 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.
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 the
reference database. When you enter a new value in the EE Reference Database Key
field, 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 displays and the annotation form returns to the previous values. Any
annotation you placed in the 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 be
retrieved 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 or
the Default key will be used to locate default data. If the linkage is not present on a
connect point or one-line, the key specified in the user element is used. If no key exists
in the user element, the Default key is used. Once you place an override key on an
element, 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 current
EE Reference Database Key. You can only review the information in this field.

234
________________ Annotate Element by Group

Global/Single — Determines whether or not the annotation modifications you are


making to the specified element will be applied to all identical element types within the
group. For example, setting the toggle to Global while annotating an RCP will change
the annotation for all RCPs within the group when you select Confirm (√). If the
toggle is set to Single for the same RCP annotation, the system will modify annotation
only for that RCP when you select Confirm (√).

The lower portion of the Active [One_Line Type] Parameters form displays a
specification table. The EE spec key field on the upper portion of the form is used as
the 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 criteria
defined in the form. The select criteria are those values that display in the Column
value column on the lower portion of the annotation form. You can use relational
operators when keying in your own select criteria. Available operators are described
later in this section.

If only one row matches the select criteria you provide, then the Column values fill in
with the matching row’s values. If more than one row matches the criteria, then a
second form containing all matching rows displays.

From this form you will select the row(s) containing the desired values. To add values

9. Modify
from the displayed specification table rows, select the row you want, and then select
Confirm (√). If you select Cancel (X), the system cancels the form and retrieves the
values from the EE spec key field on the original form.

Clear — Clears the Column values from the lower portion of the form, and then
automatically depresses the Override button to select a different row(s) from the
specification 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 Read
Only (R). You can activate the Override button by selecting it directly or by selecting
the 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 familiar
with the following operators:

Symbol Name Data Description


Types

= equal to numeric This is the default operator. If you do not enter


another operator, the system assumes =.

> greater than numeric This operator indicates that the queried values should
be greater than the given value.

< less than numeric This operator indicates that the queried values should
be less than the given value.

>= greater than numeric This operator indicates that the queried values should
or equal to be greater than or equal to the given value.

<= less than or numeric This operator indicates that the queried values should
equal to be less than or equal to the given value.

!= not equal to numeric This operator indicates that the queried values should
NOT be equal to the given value.

% wild card CHAR This operator is a wild card, representing zero or


more characters. The queried values must have every
character aside from the % in common with the given
value.

_ underline CHAR This operator is a wild card, representing a single


character. The queried values must have every
character aside from the underline in common with
the given value.

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, page 119.

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. You must define a temporary group of elements, using the Define
Group 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 this
command. A fence group overrides the active group.

236
________________ 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 you have a fence in the design, go to step 2.

— If there is not a fence in the design, go to step 3.

2. Accept/reject fence contents

Accept the contents of the fence to define them as a group.

The system highlights the group contents.

— OR —

Reject the contents of the fence.

The command exits automatically. Go to step 1.

3. Raceway [element]
Accept/reject

Accept the highlighted group element.

The system displays the Annotate Element form for the identified element.

— OR —

9. Modify
Reject the highlighted group element.

The system highlights another group element. Repeat this step. If no group elements
remain, the command exits.

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. Go to Step
3.

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 in
drag 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 displayed
annotation for the specified element.

If you set the toggle to Global, the system places the same annotation for all identical
element types in the group. When there are no more values to place for the element
type, the system prompts you to annotate other element types within the group. Go to
step 3.

— OR —

If you set the toggle to Single, the system returns you to step 3 to annotate other
elements within the group. Go to step 3.

Any value placed with the Annotate Element by Group command will
be entered into the drawing and, optionally, displayed. When you load
the project database, these values are loaded into the project database.

238
________________ Clone Element by Group

Clone Element by Group


This command copies the active group multiple times, useful when the same elements are to
be placed at regular intervals.

Equipment pointers and drop points are not copied even if they are part of the
defined group.

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, page 119.

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.

You must define a temporary group of elements, using the Define Group command, see
Define Group, page 226. Placing a fence around elements in the design also constitutes a
group for the purposes of this command. A fence group overrides the active group.

Steps
1. Select the Clone Group command.

9. Modify
The Clone 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.

239
________________
EE Raceway Modeling Reference Guide - February 2003

3. Raceway [element]
Accept/reject

Accept the highlighted element. Go to step 6.

— OR —

Reject the highlighted element.

The system highlights another group element if any elements remain uncopied. Repeat
this 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

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 identified
group.

7. Confirm (√) the number of time to clone the group.

— OR —

Cancel the form and reenter the number of clones.

8. Enter placement point

Identify the location of the first copy. If you are placing more than one clone, each
successive clone is placed the same distance and direction from the previous clone as
the first clone is from the original group.

The clone elements are placed in the design file.

Return to step 2.

240
________________ Propagate by Group

Propagate by Group
This command expands into three-dimensional elements all or selected valid one-line
segments 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 of
some of the delivered fittings, see Propagate Element, page 194 .

To view errors that occur during propagation, select the Highlight Propagation Errors
command. 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, see
Highlight Propagation Errors, page 314 .

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, page 119.

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.

You must define a temporary group of elements, using the Define Group command, see
Define Group, page 226. Placing a fence around elements in the design also constitutes a
group for the purposes of this command. A fence group overrides the active group.

9. Modify
You can set active parameters for propagation through the Propagation Setup form. For
information 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.

— 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.

241
________________
EE Raceway Modeling Reference Guide - February 2003

2. Accept/reject fence contents

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 command
propagates all valid elements within the fence, and exits automatically. Go to step
1.

— If Single Element is the active toggle on the Define Group form, go to step 3.

— OR —

Reject the contents of the fence.

The command exits automatically.

3. Raceway [element]
Accept/reject

Accept the highlighted element.

The system propagates the element, and then highlights another group element for
propagation. If no group elements remain, the command exits automatically.

Repeat this step until you have processed all elements within the group, or until you
exit the command.

— OR —

Reject the highlighted element.

The system highlights another group element for propagation. If no group elements
remain for propagation, the command exits automatically.

Repeat this step until you have processed all elements within the group, or until you
exit the command.

4. Accept/reject Group [group name]

Accept the active group.

The system propagates every element belonging to the group.

— OR —

Reject the active group.

242
________________ 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 the
reference database. For example, one rule might define that a CLB fitting be placed at a 90
degree intersection of two conduits. You can add to or replace the delivered rule set by
editing 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 the
RCP and selecting the largest nominal size among them. That nominal size is then compared
to the fitting table nominal sizes. If in the fitting table there is a nominal size the same as the
largest one-line nominal size, then that fitting is used. If there is no fitting of that nominal
size, 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 fitting
available is used.

The spec table and the fitting table are defined in the rule.

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, page 119.

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.

9. Modify
You must define a temporary group of elements, using the Define Group command, see
Define Group, page 226. Placing a fence around elements in the design also constitutes a
group for the purposes of this command. A fence group overrides the active group. You must
define the rules in the reference database. See
EE Databases, page 425 for a list of the delivered default rules.

243
________________
EE Raceway Modeling Reference Guide - February 2003

Steps
1. Select the Place Fitting by Rule by Group command.

The Group Place Fitting by Rule 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.

3. Raceway [element]
Accept/reject

Accept the highlighted element.

— OR —

Reject the highlighted element.

The system highlights another group element if any elements remain uncopied. Repeat
this step. Otherwise, the command exits automatically.

4. Accept/reject Group [group name]

Accept the active group.

If no rule is defined for the selected RCP’s situation, then the message Unable to find
a rule that applies. displays. Otherwise the correct fitting as defined by the rule is
placed on the RCP.

— OR —

Reject the active group.

The command exits automatically.

244
________________ Add Systems Group

Add Systems Group


This command defines multiple systems for a single one-line. This command will not change
the master system, the system defined at placement. It will only append systems to the
element. For example, using this command you can add an alarm and control system to an
existing element with a communication system.

If you try to add a system that already exists on the element, it will not be duplicated.

Before Using this Command


You must define a temporary group of elements using the Define Group command and the
group mode must be set to Entire Group, see Define Group, page 226 . Placing a fence
around elements in the design also constitutes a group for this command. A fenced group will
override the active temporary group.

Steps

9. Modify
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
________________
EE Raceway Modeling Reference Guide - February 2003

Replace Systems by Group


This command changes the defined active system(s) for a group. For example, use this
command when you want to change an existing high voltage tray to a low voltage tray. This
command performs a total replacement of all systems; that is, all defined systems for the
group are removed and replaced by the new systems.

Changing the active system will cause the graphic symbology to change to the
symbology define for the new system.

Field Descriptions
Systems — This button allows the selection of the active system. When a new active
system is selected, the subsystem are all unselected. The active system is automatically
included as a subsystem. The active system determines the symbology of the raceway.

Subsystem — This button allows the selection of subsystems. While this button is
depressed, the Percent and Project Rule can be defined for each subsystem.

Project Rule Set — Displays the Project Electrical Code from the your project
schema’s "project" table. This is defined in EEmgr with the EE CMS Project
Definition process. The Project Rule Set determines which rules can be assigned to the
active 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 the
Active System or Subsystems.

Percent — Displays the current Percent space allocation assigned to each of the
selected systems. The total Percent space allocation cannot exceed 100 percent. The
total of the system Percents is displayed in the field at the bottom of the Percent
column. All the selected systems percentages are summed to calculate the total
percentage. The Percent represents the portion of the raceway’s width assigned to that
system. This Percent is used when calculating the cable fill of the raceway section in
the EECMS product.

246
________________ Replace Systems by Group

Project Rule — Displays the Project Rule assigned to each of the selected systems for
calculating raceway fill. When a row is selected, a list of available rules for the Project
Rule Set defined with the EE CMS Project Definition process is displayed for review
and selection. To clear the Project Rule, select the row and select the Cancel (X) on the
list of Rules.

List — Indicates whether or not a Project Rule can be assigned. If an * displays in the
List column, then the Project Rule can be assigned. To display a list of available rules
for the Project Rule Set defined with the EE CMS Project Definition process, select the
*.

Before Using this Command


You must define a temporary group of elements using the Define Group command and the
group mode must be set to Entire Group, see Define Group, page 226 . Placing a fence
around elements in the design also constitutes a group for this command. A fenced group will
override the active temporary group.

When defining the group for this command, you must define a group that contains
all elements that have connectivity. You can not replace a system on just one
element in a network of elements that have connectivity. A network may be
thought of as all RCPs, drop points, one-lines, and so forth that are associated
through a series of graphically connected one-lines.

Steps
1. Select the Replace Systems by Group command.

The active group to be changed highlights.

9. Modify
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
________________
EE Raceway Modeling Reference Guide - February 2003

Minimize Joints by Group


This command reduces to a minimum the number of vertices in valid one-line(s) within the
active group, while retaining the original geometry of the one-line(s). If automatic
propagation is toggled on, the command will repropagate each affected one-line. (See
Propagation 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 this


command to be visible.

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, page 119.

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.

You must define a temporary group of elements, using the Define Group command, see
Define Group, page 226. Placing a fence around elements in the design also constitutes a
group for the purposes of this command. A fence group overrides the active group.

248
________________ 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 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.

— If Entire Group is the active toggle on the Define Group form, the vertices of all
one-lines within the fence are reduced to a minimum number, and the command
exits automatically.

— If Single Element is the active toggle on the Define Group form, the system
prompts you to minimize the number of vertices for each one-line within the fence.
Go to step 3.

— OR —

Reject the contents of the fence.

The command exits automatically.

9. Modify
3. Raceway one line
Accept/reject

Accept the highlighted one-line.

The system minimizes the number of vertices comprising the one-line, and then
identifies another valid one-line within the group (if any remain). Repeat this step. If
there 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. Repeat
this step. If there are no valid one-lines remaining in the group, the command exits
automatically.

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 the
group. The command exits automatically.

— OR —

Reject the active group.

The command exits automatically.

250
________________ Delete Element by Group

Delete Element by Group


This command deletes all or selected valid elements in an active group from the design file.

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, page 119.

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.

You must define a temporary group of elements, using the Define Group command, see
Define Group, page 226. Placing a fence around elements in the design also constitutes a
group for the purposes of this command. A fence group overrides the active group.

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.

9. Modify
— 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.

— If Entire Group is the active toggle on the Define Group form, the contents of the
group are deleted, and the command exits automatically.

— If Single Element is the active toggle on the Define Group form, the system
prompts you to delete each element within the fence. Go to step 3.

— OR —

Reject the contents of the fence.

251
________________
EE Raceway Modeling Reference Guide - February 2003

The command exits automatically.

3. Raceway [element]
Accept/reject

Accept the highlighted element.

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 command
exits automatically.

— OR —

Reject the highlighted element.

The system prompts you to delete another group element if any remain for deletion. If
there are no remaining group elements for deletion, the command exits automatically.

4. Accept/reject Group [group name]

Accept the active group.

The system deletes all valid elements within the group. The command exits
automatically.

— OR —

Reject the active group.

The command exits automatically.

252
________________ 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 by
selecting Setup from the EERWAY Command Menu Bar, then selecting Palette from the
resulting 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 necessary
systems and one-line types before you use these commands.

Commands

Set Raceway Defaults — Defines, reviews, and modifies the raceway default parameters for
symbols, working view, model annotation, RCPs, report IDs, and cross sections.

Define System — Selects any or all systems from those available in the reference database for
use in the design file.

Define One-Line Type — Selects any or all available one-line types from those available in the
reference database for use in the design file.

Set Symbology Control — Selects the standard graphic symbology control for all systems and
one-line types in a design file.

Symbology Control — Defines, reviews, and modifies the graphic symbology control for those
one-line types you specified using the Set Symbology Control command.

Set Text Defaults — Defines, reviews, and modifies the default parameters for text, text nodes,
10. Setup

and engineering units.

Set Conduit Sizing Attributes — Defines which conduit attributes will be used selecting the
correct size conduit in the Conduit Sizing command.

Cell Creation Commands — Create various types of raceway cells necessary for creating EE
Raceway models.

253
________________
EE Raceway Modeling Reference Guide - February 2003

Model Commands — Place and manipulate a model information in the design file.

254
________________ Using the Setup Commands

Using the Setup Commands


When to Use These Commands
You will typically use Setup commands when you enter a design file for the first time. Some
of the setups performed by this group of commands are required for later design work and
database operations.

Before Using These Commands


You must have a valid reference database attached to your design file before using the Setup
commands. For individual command prerequisites, see the appropriate command
descriptions.

Group Workflow
Before using the symbology commands in this group (Set Symbology Control and
Symbology Control), you must have defined at least one system and one-line type from the
database using the Define System and Define One-Line Type commands.

Operating Information
See individual command descriptions for specific operating information.

10. Setup

255
________________
EE Raceway Modeling Reference Guide - February 2003

Set Raceway Defaults


This command defines, reviews, and modifies raceway defaults, including cross section
parameters, symbol defaults, and Raceway Connect Point (RCP) parameters. It also allows
you to view the reference database contents for RCP. You will enter all raceway default
values through the EE Raceway Defaults form.

Parameters — Displays the EE Raceway default digitizing parameters, such as Color


or Active Angle. You can review, define, and/or modify any of the values in these
fields. To change a displayed value, select the field, and key in a new value. Use these
fields to set the default symbology for different systems in a design file.

Changes in these fields do not affect existing systems. Use the Set
Symbology Control to make changes to individual, existing systems.
Default settings are applied to new systems created in or added to a
design file.

Duct — Specifies whether to use conduit or cable when using the Define Duct Cross
Section command, see
Define 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 Define
Duct Cross Section command, see Define Duct Cross Section, page 164 for more
information.

Global Symbology — Displays the default symbology settings for Model Annotation.
The system uses these settings when annotating the model either during cell creation or
after you have placed one in the design file. You can review, define, and/or modify the
settings. 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 cross
sections. You can review, define, and/or modify the values in these fields. To change a
displayed value, select the field, and key in a new value.

256
________________ Set Raceway Defaults

Working view — Displays the current working view for the design file. The working
view 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 the
design. To change the current working view, select the slide bar, and drag it along the
scale 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 drop
points. 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/or
modify the value in this field. This value will also become the default RCP weight on
the Symbology Control form. To change the displayed value, select the field, and key
in 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 modify
this 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 Display
button. The information will display in the scrollable list in the lower right corner of
the 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.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit without saving your changes.

10. Setup

257
________________
EE Raceway Modeling Reference Guide - February 2003

Define System
This command allows you to select any or all available systems from the reference database
for use in the design file. The System Definition form displays those systems available for
selection from the reference database, as well as those already selected for the current design
file.

If you need systems not available to you, you should ask the system/application manager to
add them to the reference database. Caution should be used when adding these to the
database, so as to avoid duplication of elements.

In order to place one-lines, you must have at least one system defined in the
design 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 present
design file. To define ALL systems from the reference database in the present design
file, select the Select All button.

The systems you select display in the To Design column and will be defined in the
design file once you select the Confirm button (√).

— OR —

Select those systems listed in the To Design column that you no longer want defined
for the design file. To remove ALL systems from definition in the design file, select the
Clear All button.

258
________________ Define System

The systems you select are deleted from the To Design column and will no longer be
defined in the design file.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

10. Setup

259
________________
EE Raceway Modeling Reference Guide - February 2003

Define One-Line Type


This command allows you to select any or all available one-line types from the reference
database 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 design
file.

If you need one-line types not available to you, you should ask the system/application
manager to add them to the reference database. Caution should be used when adding these to
the database, so as to avoid duplication of elements.

You must define one-line types for the design file before you can use related
commands, 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 the
present design file. To define ALL one-line types from the reference database in the
design file, select the Select All button.

The one-line types you select display in the To Design column and will be defined in
the design file once you select the Confirm button (√).

— OR —

Select those one-line types listed in the To Design column that you no longer want
defined for the design file. To remove ALL one-line types from definition in the design
file, select the Clear All button.

260
________________ Define One-Line Type

The one-line types you select are deleted from the To Design column and will no longer
be defined in the design file.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

10. Setup

261
________________
EE Raceway Modeling Reference Guide - February 2003

Set Symbology Control


This command defines the standard graphic symbology for all systems and one-line types in a
design file. The Set Graphic Symbology Control form displays a matrix of systems and
one-line types and the standard graphic symbology assigned to each system (all one-line types
within 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 Control
command to specify the systems and one-line types that can be changed. You can specify the
one-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 up
the symbology details for all the override cases within a system. You can also modify the
system default symbology details if necessary. For more information, see
Symbology Control, page 264 .

Before Using This Command


You must have defined at least one system and one-line type in the design file. For more
information, see Define System, page 258 and
Define One-Line Type, page 260 .

262
________________ 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 for
all one-line types within a system. Each one-line type within the system will then have
its 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 default
settings restored.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

10. Setup

263
________________
EE Raceway Modeling Reference Guide - February 2003

Symbology Control
This command defines, reviews, and modifies the graphic symbology for those one-line types
you specified using the Set Symbology Control command (see Set Symbology Control, page
262 for more information about this command).

The Symbology Control form displays the current symbology settings for all systems and
corresponding one-line types.

You must have at least one system and one-line type defined for the design file
in order to use this command.

System — Displays the system for which you can currently change the symbology
settings. The display list contains a list of available systems. To change the displayed
system, select another system from the list, or select the field, and key in a system
name.

One Line Type Overrides — Displays the one-line type within the displayed system
for which you can change the symbology settings. The display list contains a list of
available 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 type
from the list, or select the field, and key in the new value.

Symbology — Displays the symbology settings for the selected system and one-line
type. You can review and edit these settings. To change a value in the list, select the
field, and key in a new value.

264
________________ Symbology Control

Steps
1. Select the Symbology Control command.

The Symbology Control form displays.

2. Set up the form parameters to meet your requirements.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

10. Setup

265
________________
EE Raceway Modeling Reference Guide - February 2003

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 of
master units to sub units (#:#).

Line length — Displays the default length for lines of text in a ratio of master units to
sub units (#:#).

Text String — These buttons and the associated display list display the current
justification for text strings in the design file. You can modify the justification using
either the buttons or the list. To change the current text string justification, select the
button that graphically represents the desired justification, or select a value from the
list.

Text Nodes — These buttons and the associated display list display the current
justification for text nodes in the design file. You can modify the justification using
either the buttons or the list. To change the current text node justification, select the
button that graphically represents the desired justification, or select a value from the
list.

266
________________ 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.

2. Set up the form parameters to meet your requirements.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

10. Setup

267
________________
EE Raceway Modeling Reference Guide - February 2003

Set Conduit Sizing Attributes


This command defines which conduit attributes will be used in selecting the correct size
conduit 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
________________ Create Cell Commands

Create Cell Commands


The Create Cell commands create various types of raceway cells necessary for creating EE
Raceway models. The cells you create using this command are stored, along with all existing
cells, in your cell library.

You must have a cell library attached to the design file in order to activate the Create Cell
commands. EE Raceway is delivered with a sample cell library, rway.cel, which resides in
win32app\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 the
library 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 a
drawing.

Create Equipment Pointer Cell — Creates an equipment pointer symbol for later
placement in the design file.

Create Drop Point Cell — Creates a drop point symbol for later placement in the
design file.

10. Setup

269
________________
EE Raceway Modeling Reference Guide - February 2003

Using the Create Cell Commands

When to Use These Commands


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

Before Using These Commands


You must have a cell library with read/write privileges attached to the design file. To display
a 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 Create
Cell commands, because it is through the Precision Input form that you will enter values for
the placement of points and for the location of raceway elements. For detailed information
about precision input, see
Precision Input Form, page 119 .

Group Workflow
There is no required or suggested sequence for using the Create Cell commands.

Operating Information
See individual command descriptions for specific operating information.

270
________________ Create Model Cell

Create Model Cell


This command allows you to create a model cell and to store that cell permanently in your cell
library.

Make sure you have a cell library attached to the design file before using this
command and be sure the library is not read only. To display a list of
available 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 all
the graphic elements of the component. Be sure to include any existing annotation that
you want as part of the cell. Make enough room within the fence to include all text
elements within the fence. Do not include any elements within the fence that you do
not want as part of the cell.

— OR —

Press <R> to exit the command.

4. Enter second fence point

Place the second data point of a fence block diagonal. Include all the graphic elements
of the component. Be sure to make room to include any text elements within the fence.
10. Setup

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
________________
EE Raceway Modeling Reference Guide - February 2003

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 and
displaying 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. Turn
the Display toggle on for any text attribute you want displayed in the cell. For detailed
information 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. Any
values (including empty enter data fields) already present in the cell are edited
automatically. The prompt tells you which value you are placing.

Underlines (for empty enter data fields) will not be displayed on the
screen cursor like other new values. However, they will be placed in the
cell (and visible) when you press <D>.

272
________________ 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 data
field. When complete, you are returned to step 7. All new non-displayed text attributes
are placed at the center of the active fence.

10. If you try to close with the fence around invalid elements, various error messages will
display. Refer to
Error 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 a
change or correction, select the input box again and key in the new value. You must
enter a cell name. The description is optional. When complete, confirm your entries
by selecting Confirm (√).

12. Identify cell origin

Place a data point to define the cell origin. This point must be within the graphic extent
of the fenced elements.

The cell is created and placed into the attached cell library. The message
Accept/reject Successful Completion displays as long as the fence is still active.

— OR —

Press <R> to reject the cell. Return to step 11.

10. Setup

273
________________
EE Raceway Modeling Reference Guide - February 2003

Create Equipment Pointer Cell


This command allows you to create a equipment pointer symbol and to store that cell
permanently in your cell library.

Make sure you have a cell library attached to the design file before using this
command and be sure the library is not read only. To display a list of
available cell libraries, key in rc=.

Steps
1. Select the Create Cell command from the command menu.

The Select cell type form displays.

2. Select the To Equipment 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 all
the graphic elements of the component. Be sure to include any existing annotation that
you want as part of the cell. Make enough room within the fence to include all text
elements within the fence. Do not include any elements within the fence that you do
not want as part of the cell.

— OR —

Press <R> to exit the command.

4. Enter second fence point

Place the second data point of a fence block diagonal. Include all the graphic elements
of 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.

274
________________ Create Equipment Pointer Cell

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 11.

7. The Annotate Element form displays, allowing you to add annotation to the cell and
displaying 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. Turn
the Display toggle on for any text attribute you want displayed in the cell. For detailed
information 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 equipment tag, etc.


Data point <D> to place, reset <R> to skip
10. Setup

For all new displayed text attributes, you are prompted to place any new values. Any
values (including empty enter data fields) already present in the cell are edited
automatically. The prompt tells you which value you are placing.

Underlines (for empty enter data fields) will not be displayed on the
screen cursor like other new values. However, they will be placed in the
cell (and visible) when you press <D>.

275
________________
EE Raceway Modeling Reference Guide - February 2003

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 data
field. When complete, you are returned to step 7. All new non-displayed text attributes
are placed at the center of the active fence.

10. If you try to close with the fence around invalid elements, various error messages will
display. Refer to
Error 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 a
change or correction, select the input box again and key in the new value. You must
enter a cell name. The description is optional. When complete, confirm your entries
by selecting Confirm (√).

12. Identify cell origin

Place a data point to define the cell origin. This point must be within the graphic extent
of the fenced elements.

The cell is created and placed into the attached cell library. The message
Accept/reject Successful Completion displays as long as the fence is still active.

— OR —

Press <R> to reject the cell. Return to step 11.

276
________________ Create Drop Point Cell

Create Drop Point Cell


This command allows you to create a drop point symbol and to store that cell permanently in
your 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-line
where the two are of a different one-line type).

Make sure you have a cell library attached to the design file before using this
command and be sure the library is not read only. To display a list of
available cell libraries, key in rc=.

Steps
1. Select the Create Cell command from the command menu.

The Select cell type form displays.

2. Select the Drop Point 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 all
the graphic elements of the component. Be sure to include any existing annotation that
you want as part of the cell. Make enough room within the fence to include all text
elements within the fence. Do not include any elements within the fence that you do
not want as part of the cell.

— OR —

Press <R> to exit the command.

4. Enter second fence point 10. Setup

Place the second data point of a fence block diagonal. Include all the graphic elements
of 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.


277
________________
EE Raceway Modeling Reference Guide - February 2003

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 11.

7. The Annotate Element form displays, allowing you to add annotation to the cell and
displaying 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. Turn
the Display toggle on for any text attribute you want displayed in the cell. For detailed
information 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 drop point tag, etc.


Data point <D> to place, reset <R> to skip

For all new displayed text attributes, you are prompted to place any new values. Any
values (including empty enter data fields) already present in the cell are edited
automatically. The prompt tells you which value you are placing.

Underlines (for empty enter data fields) will not be displayed on the
screen cursor like other new values. However, they will be placed in the
cell (and visible) when you press <D>.

278
________________ Create Drop Point 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 data
field. When complete, you are returned to step 7. All new non-displayed text attributes
are placed at the center of the active fence.

10. If you try to close with the fence around invalid elements, various error messages will
display. Refer to
Error 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 a
change or correction, select the input box again and key in the new value. You must
enter a cell name. The description is optional. When complete, confirm your entries
by selecting Confirm (√).

12. Identify cell origin

Place a data point to define the cell origin. This point must be within the graphic extent
of the fenced elements.

The cell is created and placed into the attached cell library. The message
Accept/reject Successful Completion displays as long as the fence is still active.

— OR —

Press <R> to reject the cell. Return to step 11.

10. Setup

279
________________
EE Raceway Modeling Reference Guide - February 2003

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 the
defined 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
________________ Using the Model Commands

Using the Model Commands

When to Use These Commands


You may want to use the Lock Model command after performing basic design setups to lock
the symbology control parameters and the defined systems and one-line types. However, you
can use these commands throughout the design session.

You must lock the model in order to load the drawing into the project database.

Before Using These Commands


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 Model
commands, because it is through the Precision Input form that you will enter values for the
placement of points and for the location of raceway elements. For detailed information about
precision input, see
Precision Input Form, page 119 .

Group Workflow
Before you can annotate or move annotation in the model, you must have locked the model
using the Lock Model command.

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

10. Setup

281
________________
EE Raceway Modeling Reference Guide - February 2003

Lock Model
This command locks the model. The locking of the model locks the symbology control
parameters and the defined systems and one-line types. Therefore, you should lock your
model 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, the
message Model is already locked displays.

282
________________ Move Model Annotation

Move Model Annotation


This command moves the model annotation within a design.

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, page 119.

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 Move Model Annotation command.

The Move Model Annotation precision input form displays. The command checks the
design file for the existing model annotation and places it in drag mode.

2. Enter placement point

Move the annotation to the desired location, and place it.

— OR —

Exit the command.

10. Setup

283
________________
EE Raceway Modeling Reference Guide - February 2003

Unlock Model
This command unlocks the model. If you want to change the symbology control or add new
systems and one-line types to a model that has been locked, you must first unlock the model
using 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
________________ Annotate Model

Annotate Model
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.

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 —

Select Cancel (X) to exit the command without saving your changes.

4. If you toggled Display to On, you are prompted to place the annotation in the model.

10. Setup

285
________________
EE Raceway Modeling Reference Guide - February 2003

286
________________ Runtime Setup Commands

11. Runtime Setup Commands

11. Runtime
The Runtime Setup commands allow you to define, modify, and review the active drawing
parameters in your design file.

The Runtime Setup palette is activated by selecting Setup from the EE Raceway Command
Menu Bar, then selecting Palette from the resulting pull-down menu.

Commands

Set Active One-Line Parameters — Displays the active one-line parameters, based on the
current 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 to
select a new active one-line type.

Set Active System — Displays the current active system and allows you to set a new active
system.

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 Off
displayed levels and to turn On new level displays.

Display Element Information — Displays characteristics of selected elements.

287
________________
EE Raceway Modeling Reference Guide - February 2003

Using the Runtime Setup Commands


When to Use These Commands
Once you have performed the necessary setups, you can use these commands throughout the
design session.

Before Using These Commands


You must have at least one system and one-line type defined in the design file in order to use
these commands. See
Setup Commands, page 253 for more information about defining systems and one-line types.

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

Operating Information
See individual command descriptions for specific operating information.

288
________________ Set Active One-Line Type Parameters

Set Active One-Line Type Parameters

11. Runtime
This command displays the active one-line parameters based on the current active one-line
type 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 the
appropriate form, which is based on the current active one-line type. For example, if you
defined tray as your active one-line type, then the Active TRAY Parameters form will
display when you use this command.

Column name — Displays the aliases for those columns in the database that are
associated with the specified one-line type. You can only review the information in this
field.

Column value — Displays the current value for the column whose alias displays in the
Column 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 the
new value. You can enter blank spaces into the design, but empty <Return>s enter
nothing into the design. Entering a space or a text value for an attribute will override
that value in the reference database. To delete an override on a reference database
attribute, select the column value field and delete the blank character. Once you have
deleted the override, a value will display in the field only if the value can be retrieved
from the reference database. Otherwise, the field remains null.

If blanks exist for a field, the cursor will jump to the end of the blanks when
the 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 the
overrides and specifications you saved to memory. The previous set of specifications
becomes 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. To
display the codelist, select the *.

Access — Indicates whether or not you can manipulate a particular column value. If
you can view and modify (read and write) the column value, the Access column
displays a R/W. If you can only view (read) the column value, then it will display an
R. 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. You
will 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 the
reference database. When you enter a new value in the EE Reference Database Key
field, 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 displays
and the annotation form returns to the previous values. Any annotation you placed in
the 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 be
retrieved 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 or
the Default key will be used to locate default data. If the linkage is not present on a
connect point or one-line, the key specified in the user element is used. If no key exists
in the user element, the Default key is used. Once you place an override key on an
element, you can modify it, but cannot delete it. To change the displayed value, select
the field, and key in a new value.

Key Description — This field displays the description from the reference database of
the current EE Reference Database Key. You can only review the information in this
field.

The lower portion of the Active [One_Line Type] Parameters form displays a
specification table. The EE spec key field on the upper portion of the form is used as
the 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 criteria
defined in the form. The select criteria are those values that display in the Column
value column on the lower portion of the annotation form. You can use relational
operators when keying in your own select criteria.

290
________________ Set Active One-Line Type Parameters

If only one row matches the select criteria you provide, then the Column values fill in
with the matching row’s values. If more than one row matches the criteria, then a
second form containing all matching rows displays.

11. Runtime
From this form you will select the row(s) containing the desired values. To add values
from the displayed specification table rows, select the row you want, and then select
Confirm (√). If you select Cancel (X), the system cancels the form and retrieves the
values from the EE spec key field on the original form.

Clear button — This button clears the Column values from the lower portion of the
form, 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 is
Read Only (R). You can activate the Override button by selecting it directly or by
selecting 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 familiar
with the following operators:

Symbol Name Data Description


Type

= equal to numeric This is the default operator. If you do not enter


another operator, the system assumes =.

> greater than numeric This operator indicates that the queried values should
be greater than the given value.

< less than numeric This operator indicates that the queried values should
be less than the given value.

>= greater than numeric This operator indicates that the queried values should
or equal to be greater than or equal to the given value.

<= less than or numeric This operator indicates that the queried values should
equal to be less than or equal to the given value.

!= not equal to numeric This operator indicates that the queried values should
NOT be equal to the given value.

% wild card CHAR This operator is a wild card, representing zero or


more characters. The queried values must have every
character aside from the % in common with the given
value.

_ underline CHAR This operator is a wild card, representing a single


character. The queried values must have every
character aside from the underline in common with
the given value.

Steps
1. Select the Set Active One-Line Type Parameters command.

An Active One-Line Type Parameters form displays.

2. Set up the form parameters to meet your requirements.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

292
________________ Set Active One-Line Type Parameters

Any value you place with the Set Active One-line Parameters
command will be entered into the drawing and, optionally, displayed.
When you load the project database, these values are loaded into the
project database.

11. Runtime

293
________________
EE Raceway Modeling Reference Guide - February 2003

Set Active One-Line Type


This command displays all one-line types available in the design file, based on your selections
from the reference database using the Define One-Line Type command (see
Define One-Line Type, page 260 ). The command also highlights the current active one-line
type 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 Type
command.

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.

3. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

294
________________ Set Active System

Set Active System

11. Runtime
This command displays the current active system and all available systems, based on those
you selected from the reference database using the Define System command (see
Define System, page 258 ). Using the Set Active System form, you can select a new active
system from the set of those available.

You can have multiple systems defined for a single one-line type as a way of defining split
trays or elements. This is done by specifying a system and one or more subsystems. The
active system is automatically included as a subsystem. The active system determines the
symbology 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, the
subsystems are all unselected. The active system is automatically included as a
subsystem. The active system determines the symbology of the raceway.

Subsystem — Selects the subsystems. While this button is depressed, the Percent and
Project Rule can be defined for each subsystem.

Active System — Displays the active system which determines the symbology of the
raceway.

Project Rule Set — Displays the Project Electrical Code from the your project
schema’s project table. This is defined in EEmgr with the EE CMS Project Definition
process. The Project Rule Set determines which rules can be assigned to the active
systems. 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 field
defines the Active System or Subsystems.

295
________________
EE Raceway Modeling Reference Guide - February 2003

Percent — Displays the current percent space allocation assigned to each of the
selected systems. The total space allocation cannot exceed 100 percent. The total of
the system percents is displayed in the field at the bottom of the Percent column. All
the selected systems percentages are summed to calculate the total percentage. The
Percent represents the portion of the raceway’s width assigned to that system. This
Percent is used when calculating the cable fill of the raceway section in the EECMS
product.

Project Rule — Displays the Project Rule assigned to each of the selected systems for
calculating raceway fill. When a row is selected, a list of available rules for the Project
Rule Set defined with the EE CMS Project Definition process is displayed for review
and selection. To clear the Project Rule, select the row and select the Cancel (X) on the
list of Rules.

List — Indicates whether or not a Project Rule can be assigned. If an * displays, then a
Project Rule can be assigned. To display a list of available rules for the Project Rule
Set 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 of
subsystems, press the Subsystem button.

3. Define the percentages and the project rules you want to use.

4. Select Confirm (√) to save your changes and exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

296
________________ Propagation Setup

Propagation Setup

11. Runtime
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 cross
sections and the transition, radius, and extension on the one-lines and RCPs. Sketch
propagation is considerably faster than Eden propagation, but lacks the detail that Eden
propagation provides.

Eden - Retrieves one-line type and RCP dimensions from specifications in the database
and from overrides. Propagation sends these dimensions to the Eden symbol.

All fittings you place manually are propagated with Eden, regardless of
the settings on this form.

Part Verification — Enables or disables part verification. Set the toggle to On to


verify that an element exists in the database before you propagate it. Set the toggle to
Off to skip part verification before propagation.

297
________________
EE Raceway Modeling Reference Guide - February 2003

If Eden is the active propagation mode, part verification will be


performed, 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 graphical
display of the propagation, will cause the propagation to be deleted and redrawn to
reflect 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
________________ Set Active Levels

Set Active Levels

11. Runtime
This command displays the current active level(s) and allows you both to turn off any active
levels and to activate new levels.

View — Displays the active view. All level display settings on the form are valid for
whatever view is active. To change the active view, select a value from the list, or
select the field, and key in a new value.

Levels — Indicate what levels display in the design. They also allow you to turn off or
on the display of some or all available levels.

1 - 63 indicate whether or not each available level displays in the design. When a level
has its display turned on, the button appears to be depressed. To turn on or off the
display 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 to
entering the Set Active Levels command.

Turn Levels On/Off — This toggle enables or disables the display for the levels
associated 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/Off
toggle, and then select the desired level number displayed in the Systems/One Line list.

Systems/One Line — Displays the available systems, their corresponding one-line


types, 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 with
the 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.

2. Set up the form parameters to meet your requirements.

3. Select Confirm (√) to save your changes and to exit the command.

— OR —

Select Cancel (X) to exit the command without saving your changes.

300
________________ Display Element Information

Display Element Information

11. Runtime
This command displays raceway element characteristics. If either a one-line, a straight
section, a fitting within a run, or an RCP within a run is selected, then run information is
displayed. This information includes: segment lengths, location and radius of each bend in
the 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 attributes
associated with the fitting are displayed.

Steps
1. Select the Display Element Information command.

2. Identify Raceway element

Select the element you want to review.

— OR —

Press <R> to exit the command.

3. Accept/reject

Press <D> to accept the element and display that element’s information. Return to step
2.

— OR —

Press <R> to reject the highlighted element and select another element. Return to step
2.

301
________________
EE Raceway Modeling Reference Guide - February 2003

302
________________ Utilities Commands

12. Utilities Commands


The Utilities commands highlight elements within your design file based on the identification
criteria (ASID ID, sector/word position) you provide. You can also use the commands to
display the identification criteria of specified elements and the system and one-line type of an
identified element. In addition, you can highlight propagation errors in the design file.

12. Utilities
Commands
Toggle Construction Display On/Off — Turns the display of
construction class elements on or off.

Highlight Element by Sector/Word — Highlights elements with a given


sector/word position.

Highlight Element by ASID ID — Highlights an element with a given


ASID ID.

Highlight Element by Link — Highlights an element with given entity


and mslink values.

Highlight Propagation Errors — Identifies existing propagation errors in


a design file.

Display Sector/Word Value — Displays the sector/word position of an


identified element.

Display Element Type and ASID ID — Displays the element type and
ASID ID of an identified element.

Display Link — Displays the entity and mslink values of an identified


element.

Display System and One-Line Type — Displays the associated system


and one-line type of an identified element.

303
________________
EE Raceway Modeling Reference Guide - February 2003

Coordinate System — Activates the Design Volume Coordinate System


or Plant Coordinate System associated with the design file, or shows the
coordinate system currently active.

304
________________ Using the Utilities Commands

Using the Utilities Commands


When to Use These Commands
Once you have performed the necessary setups, you can use these commands throughout the
design session.

Before Using These Commands

12. Utilities
You must be familiar with precision input and its functions before using any of the Modify
commands, because it is through the Precision Input form that you will enter values for the
placement of points and for the location of raceway elements. For detailed information about
precision input, see
Precision 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 the
attribute information you specify (Highlight Element by ASID ID, for example).

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

305
________________
EE Raceway Modeling Reference Guide - February 2003

Toggle Construction Display On/Off


This command turns On and Off the display for construction elements within each individual
view 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 other
construction 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 Construction
Display 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 or
Off. 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 the
results of the display toggle.

306
________________ Highlight Element by Sector/Word

Highlight Element by Sector/Word


This command highlights elements by a sector/word position that you specify. The position
of the sector and word are compatible with EDG, and both are relative to 1. If the position is
valid, the element highlights, but is not added to a working set. If the element is part of a
complex element, the entire complex element highlights. The sector/word position must be
the 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

12. Utilities
You can specify a filename instead of the sector/word position to highlight an element. The
file must contain the sector/word position of the element(s) you want to highlight. The file
will display in a form on the screen, allowing you to select the sector/word value from the
displayed file. If you do not specify a pathname for the file, the command searches for it in
the <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 sector


and word. Press <Esc> to exit.

307
________________
EE Raceway Modeling Reference Guide - February 2003

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 the
line. Go to Step 6.

— OR —

Select the Return button to cancel the file display form. Return to Step 1.

— OR —

Select Cancel (X) to exit the command.

6. Point to view for window

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 you
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.

308
________________ Highlight Element by ASID ID

Highlight Element by ASID ID


This command highlights elements by an ASID identification (ID) that you specify. If the
ASID ID you specify is valid, the raceway element highlights, but is not added to the working
set.

Highlight ASID ID With Filename


You can specify a filename instead of the ASID ID to highlight an element. The file must
contain the ASID ID of the element(s) you want to highlight. For example, to see where

12. Utilities
propagation errors exist in your design file, you can specify the file pro.err. The file will
display in a form on the screen, allowing you to select the ASID ID from the displayed file. If
you 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 element
having 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 of
the element having the given ASID ID.

The Children of Elements button highlights the raceway elements that are the children
of the element having the given ASID ID.

The Only the Element button highlights only the raceway element having the given
ASID ID.

— OR —

Select Cancel to exit the command.

309
________________
EE Raceway Modeling Reference Guide - February 2003

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.

4. Point to view for window

Identify the view in which you want the elements highlighted.

5. Element highlighted

The raceway element(s) associated with the specified ASID ID highlight in the view you
identified.

Key in another ASID ID to continue highlighting raceway elements. Continue


highlighting 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
________________ 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 step
8.

— 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.

12. Utilities
8. Point to view for window

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 you
identified.

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
________________
EE Raceway Modeling Reference Guide - February 2003

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. If
the element is part of a complex element, the entire complex element highlights. The entity
and 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 an
element. 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 the
displayed file. If you do not specify a pathname for the file, the command searches for it in
the <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.

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 entity and mslink values highlights in the view you
identified.

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
________________ Highlight Element by Link

After you select a line, select Confirm (√) to accept the entity and mslink values in the
line. Go to Step 6.

— OR —

Select the Return button to cancel the File Display form. Return to Step 1.

— OR —

Select Cancel (X) to exit the command.

6. Point to view for window

12. Utilities
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 you
identified.

Press <D> to select more entity and mslink values from the file display form. (When
you 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
________________
EE Raceway Modeling Reference Guide - February 2003

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 design
file, 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
________________ 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

12. Utilities
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 command
window.

— OR —

Press <R> to exit the command.

315
________________
EE Raceway Modeling Reference Guide - February 2003

Display Element Type and ASID ID


This command displays the element type and the ASID identification (ID), in the
MicroStation 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
________________ Display Link

Display Link
This command displays the entity (table) and mslink, in the MicroStation command window,
of an identified element.

Steps

12. Utilities
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 the
following format: Entity (table number) = <value>, mslink = <value>

— OR —

Press <R> or <Esc> to exit the command.

317
________________
EE Raceway Modeling Reference Guide - February 2003

Display System and One-Line Type


This command displays the system and one-line type associated with an element you identify.

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, page 119.

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 Display System and One-Line Type command from the menu.

The precision input form displays, along with the Print System and One-Line Type
form.

2. Identify Raceway element

Identify an element in the design file.

The identified element highlights.

— OR —

Exit the command.

318
________________ Display System and One-Line Type

3. Raceway [element]
Accept/reject

Accept the highlighted element.

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.

12. Utilities
— OR —

Reject the highlighted element.

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
________________
EE Raceway Modeling Reference Guide - February 2003

Active Coordinate System


This palette provides the Active Design Volume Coordinate System, Activate Plant
Coordinate System, and Show Active Coordinate System commands.

Commands
Activate Design Volume Coordinate System — Activates the Design Volume
Coordinate System (DVCS) allowing you to define a local coordinate system for a
particular 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 the
status field.

When the coordinate system is switched between the PCS and DVCS, model
graphics do not rotate to reflect the active coordinate system. Instead, the
coordinate 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 the
Design Volume Coordinate System.

Activate Plant Coordinate System


The Activate Plant Coordinate System command allows you to work in the Plant
Coordinate System. The Plant Coordinate System is common to all models and drawings in a
project. The Plant Coordinate System uses this global coordinate system to maintain the
relationships among the various models. This becomes important when attaching reference
models to the active model.

Show Active Coordinate System


The Show Active Coordinate System command displays the active coordinate system in the
status field. If you desire to change the coordinate system, you can select either the Activate
Design Volume Coordinate System or Activate Plant Coordinate System commands.

320
________________ Database Commands

13. Database Commands


The Database commands are used to load and run reports from the database. The Database
palette is activated by selecting Database from the EERWAY Command Menu Bar, then
selecting Palette from the resulting pull-down menu.

Topics

Load Database — Loads the project database with information generated from the EE
Raceway drawing.

Reports — Displays the information in an EE Raceway database.

13. Database
Rulecheck — Displays the design rule errors occurring in the design process.

321
________________
EE Raceway Modeling Reference Guide - February 2003

Using the Database Commands


When to Use These Commands
Use these command to run limited database commands while still in the graphic design
session.

Before Using These Commands


Refer to the individual command descriptions for any requirements which may be necessary
before using each command.

Group Workflow
You must load the database before you can run a report or rulecheck.

Operating Information
Because the operating sequence, command key-ins, and screen prompts vary for each
command, instructions for using these commands are described in each individual command
section.

322
________________ Load Database

Load Database
This command loads a relational database with information generated by the EE Raceway
design file. Information in the design file is merged with information from the reference
schema 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 previously
into the database, the command removes the occurrences of the previous load and completely
reloads the design file.

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 the Load Database process.

This process calculates the following values:

Table Name Column Name Comments

13. Database
rcp_to_drw pds_east* The PDS east coordinate of the corresponding RCP’s
origin.

rcp_to_drw pds_north* The PDS north coordinate of the corresponding


RCP’s origin.

rcp_to_drw pds_elev* The PDS elevation coordinate of the corresponding


RCP’s origin.

rcp_to_sys ee_percent*** Indicates what portion of the corresponding RCP is


set aside for the corresponding system.

drop_point ee_dist_down_ol** The distance down the one-line to the point on the
one-line closest to the drop point origin.

drop_point ee_dist_to_rcp** The orthogonal distance from the drop point origin to
the RCP’s origin, and the orthogonal distance from
the 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 master


units.

ol_to_sys ee_percent*** Indicates what portion of the corresponding one-line


is 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 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.

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 fitting
and straight tables. The columns are optional for Load Database.

** You can override the value for these columns by annotating the appropriate elements in the
design file.

*** These values indicate the portion of a split raceway dedicated to each system within
the split raceway.

324
________________ 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 the

13. Database
displayed defaults.

The default error and message files will be overwritten every time the
process runs. You must specify unique filenames to save the default
files.

3. Accept will load database.

When you are finished completing the input information, select Confirm (√), and the
process begins.

When complete, the process will return one of two messages (described below) to the
screen.

Messages
Error occurred during process

If any errors occur, the message above displays. The error file lists all the errors that
occurred 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 every
run of the process, and is displayed automatically to the screen. It lists everything that
was loaded into the database.

325
________________
EE Raceway Modeling Reference Guide - February 2003

Report
This command accesses the standard EE Raceway reports. These reports report on the project
and reference databases. You must load the project database before running any reports.

All reports are kept in the /reports directory; see Create Project for the
directory structure.

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

The system manager can change the names of the reports that display in the
listing 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 necessary
to run the report.

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

326
________________ Report

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

Steps
1. Select the Report command.

2. Select the report you want to run from the list.

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

4. Define the report input form as needed and select Confirm (√) to process the report.

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 high
range in PDS coordinates. These low and high ranges define a cubic volume from which the

13. Database
report is pulled.

Any Raceway component extending outside the clipping volume defined by the High and
Low 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 on
the precision input form. The coordinate values need to be in subunits and entered in the form
field with a space between the coordinates: easting northing elevation For example, 234
532 34

It should be understood that westing and southing coordinates must be the


negative of their opposite directional coordinate. For instance, a westing
coordinate 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
________________ Rule Checks

Rule Checks
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. You
must load the project database before running any rule checks.

Overview

13. Database
This section contains general information about running all EE Raceway rule checks. For
more detailed information about each rule check, see Reports, page 545 .

The system manager can change the names of the reports or add new reports to
the 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 that
displays in the input fields, or change that information according to your specifications.

329
________________
EE Raceway Modeling Reference Guide - February 2003

If you want to save reports throughout a project, you should name the output files
yourself. 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 report
that 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.

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

4. Define the input form as needed and select Confirm (√) to process the rule check
report.

330
________________ Raceway Processes

14. Raceway Processes


This chapter provides detailed descriptions of EE Raceway processes. You will run all EE
Raceway processes from the Process menu found on the EE Raceway Drawing menu. (See
Process in the section entitled EE Raceway Environment for information about running all
processes.) The individual EE Raceway processes are described in the following sections:

Load Database — Loads the project database with information generated from the EE
Raceway drawing.

Unload Design — Removes all the information associated with a particular drawing
from the project database, based on the design filename you specify.

Unload Sheet — Removes all the information associated with a particular drawing
from the project database, based on the internal sheet name you specify.

Cleanup Database — Removes any data from a project database that is not currently
associated with a design in the project’s ../rway/dgn directory.

Create Interference Envelope (default name) — Reads the design file and creates a
data file that contains envelopes for input to Plant Design interference detection tasks.

Create Interference Envelope (given name) — Reads the design file and creates a
data file, with the name you specify, that contains envelopes for input to Plant Design
interference detection tasks.

Processes
14. EERWAY

331
________________
EE Raceway Modeling Reference Guide - February 2003

Load Database
This process loads a relational database with information generated by an EERWAY design
file. Information in the design file is merged with information from the reference schema and
loaded 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 the
Load Database process.

2. Load database tracks drawing information based on the "Drawing"


table of the project database. Thus, you must annotate the drawing or
model and enter the unique "SHEET" information, using the Lock
Model 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’s


origin.
rcp_to_drw pds_north* The PDS north coordinate of the corresponding
RCP’s origin.
rcp_to_drw pds_elev* The PDS elevation coordinate of the corresponding
RCP’s origin.
rcp_to_sys ee_percent*** Indicates what portion of the corresponding RCP is
set aside for the corresponding system.
drop_point ee_dist_down_ol** The distance down the one-line to the point on the
one-line closest to the drop point origin.
drop_point ee_dist_to_rcp** The orthogonal distance from the drop point origin to
the RCP’s origin, and the orthogonal distance from
the 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 master
units.
ol_to_sys ee_percent*** Indicates what portion of the corresponding one-line
is 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
________________ 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 fitting
and straight tables. The columns are optional for Load Database.

** You can override the value for these columns by annotating the appropriate elements in the
design file.

*** These values indicate the portion of a split raceway dedicated to each system within
the split raceway.

Steps
1. Select Load database from the Process menu, and select Confirm (√).

The Load database screen displays.

Processes
14. EERWAY

2. Enter drawing name.

Select a design file from the Drawing List or key in a design filename (you may
specify multiple design files).

333
________________
EE Raceway Modeling Reference Guide - February 2003

3. Enter error and output filenames.

Key in unique filenames in the Error file and Output file fields, or accept the
displayed defaults.

The default error and message files will be overwritten every time the
process runs. You must specify unique filenames to save the default
files.

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 for
most processes (see Process, page 64 ).

5. Confirm your selections.

When you are finished completing the input information, select Confirm (√), and the
process begins. When complete, the process will return one of two messages (described
below) to the screen.

Messages
Error occurred during process

If any errors occur, the message above displays. The error file lists all the errors that occurred
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 every run of
the process, and is displayed automatically to the screen. It lists everything that was loaded
into the database.

You can view both files using the Output option on the Utilities page.

334
________________ Batch File Option

Batch File Option


The load database process can be executed from a batch file. Setup an rway.bat file to export
the necessary Microstation and EERWAY environment variables to execute the load database
process. 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\USTATION
SET MS_EXE=D:\WIN32APP\USTATION
SET EES_REFDB=CERT60_REF
SET EE_SCHEMA=CERT60_PRJ
SET EERD_MSGS=D:\WIN32APP\INGR\EERWAY\MSG\
SET EERD_TBLS=D:\WIN32APP\INGR\EERWAY\MSG\

Processes
14. EERWAY

335
________________
EE Raceway Modeling Reference Guide - February 2003

Unload Design
This process unloads a design from a relational database, based on the design filename you
specify. You must have loaded the database using the Load Database process before
unloading. 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 modify
anything 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 may
specify multiple design files).

3. Key in unique filenames for the error and message files (or accept the default
filenames).

The default error and message filenames are displayed in appropriate fields. You may
change the defaults by selecting the fields and keying in new names.

The default error and message files will be overwritten every time the
process is run, unless you specify unique filenames in these fields.

336
________________ Unload Design

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 for
most processes (see Process, page 64 ).

5. Confirm your selections.

When you are finished completing the input information, select Confirm (√), and the
process begins. When complete, the process will return one of two messages (described
below) to the screen.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in
the current working directory, lists all the errors that occurred during processing. The
file is automatically displayed to the screen for your review.

Process successfully completed

If no errors occurred, the message above displays. The .msg file, an ASCII file located
in the current working directory, is created on every run of the process, and lists
everything that was loaded into the database. The file is automatically displayed to the
screen for your review.

You can view both files using the Output option on the Utilities page.

Processes
14. EERWAY

337
________________
EE Raceway Modeling Reference Guide - February 2003

Unload Sheet
This process unloads an EE Raceway drawing from a relational database, based on the
internal sheet name you specify. You must have loaded the database using the Load
Database process before unloading.

The Unload Sheet 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 modify anything in the
reference database.

The drawing you are unloading must have a title block, and the sheet name in the title block
must match the database entry for that drawing, since the process keys off the sheet name in
the 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 default
filenames).

The default error and message filenames are displayed in appropriate fields. You may
change the defaults by selecting the fields and keying in new names.

338
________________ Unload Sheet

The default error and message files will be overwritten every time the
process is run, unless you specify unique filenames in these fields.

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 for
most processes (see Process, page 64 ).

5. Confirm your selections.

When you are finished completing the input information, select Confirm (√), and the
process begins. When complete, the process will return one of two messages (described
below) to the screen.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The file is
automatically displayed to the screen for your review.

Process successfully completed

If no errors occurred, the message above displays. The .msg file, an ASCII file located in the
current working directory, is created on every run of the process, and lists everything that was
loaded into the database. The file is automatically displayed to the screen for your review.

Processes
14. EERWAY
You can view both files using the Output option on the Utilities page.

339
________________
EE Raceway Modeling Reference Guide - February 2003

Cleanup Database
This process removes information from the database that is not in any drawing currently
loaded in the database.

For example, information may have been added through the Relational Database Management
System (RDBMS) to test for a special case or to create customized tables. This process also
removes information on any EE Raceway drawing which has been deleted, but for some
reason 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 any
raceway design file. This process will not unload records of customized tables in the
database. The process uses the filenames in the drawing table of all current drawings. It then
makes a list of all valid drawings, and deletes anything from the database which is not
connected to one of these drawings. This process will not delete drawings. It will delete from
the 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.

2. Enter error and output filenames.

Key in unique filenames in the Error file and Output file fields, or accept the
displayed defaults.

340
________________ Cleanup Database

The default error and message files will be overwritten every time the
process runs. You must specify unique filenames to save the default
files.

3. 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 for
most processes (see Process, page 64 ).

4. Confirm your selections.

When you are finished completing the input information, select Confirm (√). The
process begins. When complete, the process will return one of two messages (described
below) to the screen.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing.

Process successfully completed

If no errors occurred, the message above displays. The .msg file, an ASCII file located in the
current working directory, is created. It will display mostly zeroes, and it includes a log of
what was unloaded during processing.

Processes
14. EERWAY
You can view either file using the Output option on the Utilities screen.

341
________________
EE Raceway Modeling Reference Guide - February 2003

Create Interference Envelope (default


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 file
to <current_project>.prj/rway/dgn/<filename.env>.

After running the Interference Detection process in EE Raceway, you may send the file to
Plant Design software and run it against PDS interference detection. The purpose of the entire
process 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.

2. Enter design name.

— OR —

Select a design file from the Drawing List (use the Select All button to select all files
from the list) or key in a design filename.

3. Key in unique filenames for the error and output files (or accept the displayed default
filenames).

The default error and output files will be overwritten every time you run
the process unless you specify unique filenames in the fields.

342
________________ Create Interference Envelope (default name)

4. Select the desired operating mode.

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 (see
the section entitled EE Raceway Environment for information about operating modes).

5. Confirm your selections.

When you finish completing the input information, select the Confirm button (√). The
process begins. When complete, the process returns one of the two messages (described
below) to the screen.

Messages
Error occurred during process

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 file
through the Output option on the Utilities screen.

Process successfully completed

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 file
displays immediately to the screen for your review. Otherwise, you can view the file through
the Output option on the Utilities screen.

Processes
14. EERWAY

343
________________
EE Raceway Modeling Reference Guide - February 2003

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 file
to <current_project>.prj/rway/dgn/<filename.env>.

After running the Interference Detection process in EE Raceway, you may send the file to
Plant Design software and run it against PDS interference detection. The purpose of the entire
process 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:

2. Enter design name.

— OR —

Select a design file from the Drawing List (use the Select All button to select all files
from 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 default
filenames).

The default error and output files will be overwritten every time you run
the process unless you specify unique filenames in the fields.

344
________________ Create Interference Envelope (given name)

5. Select the desired operating mode.

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 (see
the section entitled EE Raceway Environment for information about operating modes).

6. Confirm your selections.

When you finish completing the input information, select the Confirm button (√). The
process begins. When complete, the process returns one of the two messages (described
below) to the screen.

Messages
Error occurred during process

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 file
through the Output option on the Utilities screen.

Process successfully completed

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 file
displays immediately to the screen for your review. Otherwise, you can view the file through
the Output option on the Utilities screen.

Processes
14. EERWAY

345
________________
EE Raceway Modeling Reference Guide - February 2003

346
________________ Eden Processes

15. Eden Processes


This chapter provides detailed descriptions of available Eden processes. You will use these
processes to compile Eden symbols, manipulate the Eden symbol library, and edit the Eden
symbol file.

You will access the Eden processes from the EDEN option found on the EE Raceway
Drawing 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 variable
RWAY_EDEN_LIB. The delivered default symbol library path is win32app\eerway\eden. If
you want to place your Eden library in a different directory, then edit the .EErc file in your
home 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 defined
by 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 different
directory, then edit the to specify the appropriate directory.

For a general description of Eden symbol generation, see the PDS Eden Interface Reference
Guide. 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 option
of 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 symbol
library.

Merge EDEN Symbol Libraries — Merges the contents of two Eden symbol
libraries into one library.

Compress EDEN Symbol Library — Compresses an Eden symbol library to remove


Processes
15. Eden
unused space left by deleted symbols.

Extract EDEN Symbol From Library — Extracts a specified symbol from an Eden
symbol library.

Extract EDEN User Function From Library — Extracts a specified user function
from 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 symbol
source file.

348
________________ Compile EDEN Symbol

Compile EDEN Symbol


This process compiles an Eden symbol file, and gives you the option of placing the compiled
symbol in an Eden symbol library.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. For
information about the path to the symbol library, see the description at the beginning of
this chapter. To change the displayed default library name, select the field, and key in a
new 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 the
beginning of this chapter. To enter the symbol source file, select the field, and key in a
filename.

Enter option — Displays the default compile option (-o). The -o option lists the
compiled Eden symbol file, and then adds the symbol to the specified library. The -l
option simply lists the compiled Eden symbol file. To change the displayed option,
select the field, and key in a new option.
Processes
15. Eden

Before Using This Command


You must create an Eden symbol file. See
Eden Symbol Generation, page 513 for information about symbol file creation.

349
________________
EE Raceway Modeling Reference Guide - February 2003

Steps
1. Select Compile EDEN Symbol from the list, and select Confirm (√).

The Compile EDEN Symbol form displays.

2. Set up the form parameters to meet your specifications.

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

350
________________ Delete EDEN Symbol

Delete EDEN Symbol


This process deletes an Eden symbol from the Eden symbol library.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. To change the
displayed 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 the
beginning of this chapter.

Enter symbol name — Displays the name of the symbol you intend to delete from the
library. 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 the
beginning of this chapter.

Processes
15. Eden

351
________________
EE Raceway Modeling Reference Guide - February 2003

Steps
1. Select Delete EDEN Symbol from the list, and select Confirm (√).

The Delete EDEN Symbol form displays.

2. Set up the form parameters to meet your specifications.

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in
the current working directory, lists all the errors that occurred during processing. The
.err file displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located
in the current working directory, contains any output from the process. The file
displays immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

352
________________ List EDEN Symbol Library

List EDEN Symbol Library


This process lists the Eden symbols in the selected Eden library.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. To change the
displayed 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 the
beginning of this chapter.

Processes
15. Eden

353
________________
EE Raceway Modeling Reference Guide - February 2003

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.

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

354
________________ List EDEN User Functions

List EDEN User Functions


This process lists the Eden user functions in the selected Eden library.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. To change the
displayed 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 the
beginning of this chapter.

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.


Processes
15. Eden

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

355
________________
EE Raceway Modeling Reference Guide - February 2003

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the list will
display.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

356
________________ Merge EDEN Symbol Libraries

Merge EDEN Symbol Libraries


This process merges two Eden symbol libraries into one.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Merge into library name — Displays the name of the symbol library into which you
will merge the contents of a second library. To enter a library name, select the field,
and key in a name.

For information about the path to the symbol library, see the description at the
beginning of this chapter.

Merge from library name — Displays the name of the symbol library whose contents
you will merge with first library. To enter a library name, select the field, and key in a
name.

For information about the path to the symbol library, see the description at the
beginning of this chapter. Processes
15. Eden

Steps
1. Select Merge EDEN Symbol Libraries from the list, and select Confirm (√).

The Merge EDEN Symbol Libraries form displays.

2. Set up the form parameters to meet your specifications.

357
________________
EE Raceway Modeling Reference Guide - February 2003

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

358
________________ Compress EDEN Symbol Library

Compress EDEN Symbol Library


This process compresses the selected Eden symbol library. Compressing the library removes
the unused space left by deleted symbols.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. To change the
displayed library name, select the field, and key in the name of the library you intend to
compress.

For information about the path to the symbol library, see the description at the
beginning of this chapter.

Steps
1. Select Compress EDEN Symbol Library from the list, and select Confirm (√).

The Compress EDEN Symbol Library form displays.


Processes
15. Eden

2. Set up the form parameters to meet your specifications.

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

359
________________
EE Raceway Modeling Reference Guide - February 2003

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

360
________________ 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 of
an ASCII file that you can edit using a standard editor (vi or emacs, for example). The
symbol 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 store
your source symbol files in another directory, then edit the .EErc file in win32app\eenuc,
exporting RWAY_EDEN_SRC to define the appropriate directory.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. To change the
displayed 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 the
beginning of this chapter.

Enter symbol name — Displays the name of the symbol you intend to extract from the
library. To enter the symbol name, select the field, and key in the name.
Processes
15. Eden

361
________________
EE Raceway Modeling Reference Guide - February 2003

Steps
1. Select Extract EDEN Symbol From Library from the list, and select Confirm (√).

The Extract EDEN Symbol From Library form displays.

2. Set up the form parameters to meet your specifications.

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

362
________________ 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 is
the 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 variable
RWAY_EDEN_SRC. The delivered default source user function path is
win32app\eerway\eden. If you want to store your source user function files in another
directory, then edit the .EErc file in win32app\eenuc, exporting RWAY_EDEN_SRC to
define the appropriate directory.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter library name — Displays the default Eden symbol library name. To change the
displayed 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 the
beginning of this chapter.

Enter symbol name — Displays the name of the user function you intend to extract
Processes
15. Eden

from the library. To enter the user function name, select the field, and key in the name.

363
________________
EE Raceway Modeling Reference Guide - February 2003

Steps
1. Select Extract EDEN User Function From Library from the list, and select Confirm
(√).

The Extract EDEN User Function From Library form displays.

2. Set up the form parameters to meet your specifications.

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

364
________________ Extract EDEN User Function From Library

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

Processes
15. Eden

365
________________
EE Raceway Modeling Reference Guide - February 2003

Edit EDEN Symbol File


This process allows you to edit a symbol source file using a standard ASCII editor. It is only
available on a graphics terminal.

Output file — Displays the file to which process messages are sent. To change the
displayed output filename, select the field, and key in a new filename.

Error file — Displays the file to which error messages are sent. To change the
displayed error filename, select the field, and key in a new filename.

Enter editor — Displays the name of the default ASCII editor (vi) that you will use to
edit the Eden symbol file. To change the displayed editor, select the field, and key in a
new standard ASCII editor name.

Enter symbol file name — Displays the name of the symbol file you intend to edit. To
enter 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 the
beginning of this chapter.

366
________________ Steps

Steps
1. Select Edit EDEN Symbol File from the list, and select Confirm (√).

The Edit EDEN Symbol File form displays:

2. Set up the form parameters to meet your specifications.

3. Select the desired operating mode.

The current operating mode displays in a box at the lower right of the screen. You can
choose between foreground, background, and batch operating modes. For
information about operating modes, see EDEN, page 67 .

4. Confirm your selections.

When you have completed the input information, select Confirm (√), and the Eden
process begins.

Messages
Error occurred during process

If any errors occur, the message above displays. The .err file, an ASCII file located in the
current working directory, lists all the errors that occurred during processing. The .err file
displays immediately to the screen for your review.

Process successfully completed

If no errors occurred, the above message displays. The .msg file, an ASCII file located in the
current working directory, contains any output from the process. The file displays
immediately to the screen for your review.

You can view either file on the screen, see Output, page 89.

Processes
15. Eden

367
________________
EE Raceway Modeling Reference Guide - February 2003

368
________________ 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 you
to review an element’s attributes, review the PDS clashes in a model, create a window
containing a specific element, and display information about the reference models attached to
the current model.

The Integrated Commands are only available when running EE Raceway


inside PDS, not when running standalone EE Raceway.

The Integrated Commands palette is activated by selecting Integrated Commands from the
EE Raceway File Menu Bar, then selecting Palette from the resulting pull-down menu.

Commands
16. Integrated

369
________________
EE Raceway Modeling Reference Guide - February 2003

Using the Integrated Commands


When to Use These Commands
Once you have performed the necessary setups, you can use these commands throughout the
design session.

Before Using These Commands


Review PDS Attributes – You must have an existing component in the active model
or 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 in
an attached PDS reference file.

Review PDS Clash – You must first have run IFC Clash Detection, and must have an
existing clash in the design area.

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

Operating Information
See individual command descriptions for specific operating information.

370
________________ Review PDS Attributes

16.1 Review PDS Attributes


The Review PDS Attributes command displays the database attributes of a selected
component. Items being reviewed can be in the active model or in an attached PDS reference
file.

To view pipe centerlines (to review the line segments), you need to display
construction 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.

Commands
16. Integrated

371
________________
EE Raceway Modeling Reference Guide - February 2003

16.2 Reference PDS Model


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 which contains the model you
want to attach; then, click Attach.

Areas – Lists all design areas defined in the active project. Select the design area
which 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.

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.

372
________________ Reference PDS Model

Show Attachments – Displays all reference models attached to the active model.

Exit – Exits the Reference Model command.

Commands
16. Integrated

373
________________
EE Raceway Modeling Reference Guide - February 2003

16.3 Window to Named PDS Item


The Window to Named PDS Item command zooms in on an item whose attribute you
identify. 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 active
model 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, Piping
Component Number, Pipe Tag, Instrument Component Number, or Pipe Support
Number

— 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
________________ Review PDS Clash

16.4 Review PDS Clash


The Review PDS Clash command edits and reviews existing clashes and approves existing
clashes.

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 Control
Database.

Approve False Clash – Approves the clash as a false clash in the Project Control
Database.
Commands
16. Integrated

Review Unapproved Clash / Review Approved Clash – Specifies if you want to


review approved or unapproved clashes.

Clash Marker – Displays the number of the current clash. Select a marker number
with 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 one
item of the clash. The descriptions of the clashing component display below the model
name and design area.

Item B – Displays the model name and the corresponding design area that has the one
item of the clash. The descriptions of the clashing component display below the model
name and design area.

Comments – Displays existing comments about the active clash. You can also select
the 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 select
the view you want to update.

376
________________ Appendix A: Error Messages

Appendix A Error Messages

Messages
A: Error
This appendix has an alphabetical listing of error messages you may receive when you are running EE Raceway
Modeling. The likely reason for the error and the recovery are listed with the error message wherever this is
possible.

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 invalid


system!
Reason: The element belongs to a system that failed to load.

Recovery: Make corrections so that the system loads without errors.

377
________________
EE Raceway Modeling Reference Guide - February 2003

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 raceway


connect 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 given
specification does not have that part defined in its part table.

Asid <numeric value>, raceway connect point connected


to 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 invalid


codelist value!
Reason: Element annotation does not match with entries in a codelist table.

Recovery: Change element annotation.

Asid <numeric value>, straight connected to invalid


oneline!
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
________________ Appendix A: Error Messages

Asid <numeric value>, straight connected to invalid


system!

Messages
A: Error
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!


Reason: Element has been corrupted.

Recovery: Contact Intergraph support.

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
________________
EE Raceway Modeling Reference Guide - February 2003

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, call
Intergraph 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 Intergraph
support.

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
________________ Appendix A: Error Messages

Color not in range 0 to 127


Reason: The input is not within the valid range for a color.

Messages
A: Error
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


Reason: Element has been corrupted.

Recovery: Contact Intergraph support.

Could Not Read PDS Data Element


Reason: The PDS user element is not found in the design file. Either the element was removed externally or
this 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
________________
EE Raceway Modeling Reference Guide - February 2003

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 the
command 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


Reason: No permission to open file or the file does not exist.

Recovery: Check the file permissions and the existence of the file.

382
________________ Appendix A: Error Messages

Could not open file <string>


Reason: No permission to open file or the file does not exist.

Messages
A: Error
Recovery: Check the file permissions and the existence of the file.

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.

Recovery: Check to see that the design file has a type 63 element and at least 7 blocks in it.

383
________________
EE Raceway Modeling Reference Guide - February 2003

Could not read the Raceway user element


Reason: Rmon could not read the Raceway user element.

Recovery: Check to see that the design file has a type 63 element and at least 7 blocks in it.

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 into
the reference database.

Design file <string> does not exist!


Reason: The referenced design file was cannot be found.

Recovery: Enter correct filename.

384
________________ Appendix A: Error Messages

Design file name <string> too long


Reason: The filename you specified exceeds 128 characters.

Messages
A: Error
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 defaults
form.

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 has
enough room to create the fitting.

Elbow Error: acute angle at oneline index <numeric


value>.
Reason: Acute bends are not supported in this release.

Recovery: None.

385
________________
EE Raceway Modeling Reference Guide - February 2003

Elbow Error: contradictory heights at index <numeric


value>.
Reason: Height of the cross sections must be equal.

Recovery: Modify cross section dimensions.

Elbow Error: contradictory widths at index <numeric


value>.
Reason: Widths of the cross sections must be equal.

Recovery: Modify cross section dimensions.

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 <numeric


value>.
Reason: Cross section cannot be propagated around bend without being skewed.

Recovery: Rotate the cross section or place one-line again.

386
________________ Appendix A: Error Messages

Element has no parent


Reason: The element with the given asid has no parent element.

Messages
A: Error
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
________________
EE Raceway Modeling Reference Guide - February 2003

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
________________ Appendix A: Error Messages

Error in graphic bang placement.


Reason: Internal error.

Messages
A: 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.

Recovery: Add privilege to database.

389
________________
EE Raceway Modeling Reference Guide - February 2003

Error loading drop point!


Reason: No privilege for this operation.

Recovery: Add privilege to the database.

Error loading fittings!


Reason: No privilege for operation.

Recovery: Add privilege to database.

Error loading one-lines!


Reason: No privilege for operation.

Recovery: Add privilege to database.

Error loading raceway connect points!


Reason: No privilege for operation.

Recovery: Add privilege to database.

Error loading straights!


Reason: No privilege for operation.

Recovery: Add privilege to database.

Error loading systems!


Reason: No privilege for operation.

Recovery: Add privilege to database.

390
________________ Appendix A: Error Messages

Error loading to equipment!


Reason: No privilege for this operation.

Messages
A: Error
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
________________
EE Raceway Modeling Reference Guide - February 2003

Error opening project database!


Reason: Schema not found.

Recovery: Add schema to database or change schema name.

Error opening reference database!


Reason: Schema not found.

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
________________ Appendix A: Error Messages

Error querying ref db for mscodelist


Reason: The mscodelist table does not exist or there is no connect permission.

Messages
A: Error
Recovery: Run the Create Database process with the rwayref.sql file.

Error reading TCB of design file!


Reason: TCB corrupted.

Recovery: Call Intergraph support.

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.

Recovery: Call Intergraph support.

393
________________
EE Raceway Modeling Reference Guide - February 2003

Error saving symbology - Design file may be corrupted


Reason: Could not save the symbology to the design file.

Recovery: Call Intergraph support.

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.

Recovery: Add privilege to database.

394
________________ Appendix A: Error Messages

Error starting or stopping graphic bang.


Reason: Internal error.

Messages
A: Error
Recovery: Call Intergraph support.

Error updating row in <string> table!


Reason: No privilege to write to database.

Recovery: Add privilege 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
________________
EE Raceway Modeling Reference Guide - February 2003

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 so
that it has enough room to create the fitting.

Fitting Error: contradicting at RCP asid <numeric value>.


Reason: Heights of cross sections are inconsistent.

Recovery: Modify cross section dimensions.

Fitting Error: contradicting widths at RCP asid <numeric


value>.
Reason: Widths of cross sections are inconsistent and no reducing fitting is allowed in this case.

Recovery: Modify cross section dimensions.

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
________________ Appendix A: Error Messages

Font not in range 0 to 255


Reason: The input was not within valid range for a font.

Messages
A: Error
Recovery: Enter a new value within the range 0 to 255.

Form could not be created


Reason: A form could not be created by the software. Possible memory allocation problem.

Recovery: Call Intergraph support.

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 defined
in 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 defined
in the product.

397
________________
EE Raceway Modeling Reference Guide - February 2003

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
________________ Appendix A: Error Messages

Invalid asid id
Reason: An element cannot be found in the design file with the given asid id.

Messages
A: Error
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 given
a 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 the
one-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
________________
EE Raceway Modeling Reference Guide - February 2003

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
________________ Appendix A: Error Messages

Invalid Part Found at RCP asid <numeric value>.


Reason: The fitting at the RCP cannot be verified with the database.

Messages
A: Error
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
________________
EE Raceway Modeling Reference Guide - February 2003

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
________________ Appendix A: Error Messages

Load initialization error!


Reason: Some other initialization error procedure failed.

Messages
A: Error
Recovery: Fix other problems.

Max run angle = <numeric value>, current = <numeric


value>
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
________________
EE Raceway Modeling Reference Guide - February 2003

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
________________ Appendix A: Error Messages

No Duplicate Group Name Allowed


Reason: The new group name matches the name of an existing group.

Messages
A: Error
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
________________
EE Raceway Modeling Reference Guide - February 2003

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
________________ Appendix A: Error Messages

No valid special part tables exist


Reason: There are no special parts tables in the database.

Messages
A: Error
Recovery: Populate the database.

No valid special parts exist for this table


Reason: There are no special parts defined in the active table.

Recovery: Populate the database.

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 cell
library.

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
________________
EE Raceway Modeling Reference Guide - February 2003

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 been
corrupted.

Problem with shared memory!


Reason: Internal error.

Recovery: Call Intergraph support.

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
________________ Appendix A: Error Messages

Raceway element not found


Reason: Unable to locate a valid raceway element (one-line, three-line, title block, RCP).

Messages
A: Error
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 the
mscolumns 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
________________
EE Raceway Modeling Reference Guide - February 2003

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.

Recovery: Enter a new value within the range 0 to 7.

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 row
through SQL.

Text element not found


Reason: A text element could not be located.

Recovery: Identify a valid text element.

410
________________ Appendix A: Error Messages

The value must be greater than zero


Reason: The width must be greater than zero.

Messages
A: Error
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-planar


complex shape with Asid = <numeric value>
Reason: Found a cell containing a complex shape which does not meet any lines or surfaces at a 90 degree
angle. 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 complex
shape in that cell. Rebuild cell so that the complex shape meets a line or surface at 90 degrees. To ensure a
measure of 90 degrees, snap to the angle.

411
________________
EE Raceway Modeling Reference Guide - February 2003

Warning Column <string> found in reference, not in


project!
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
________________ Appendix A: Error Messages

Warning must accept/reject System selection


Reason: You must accept/reject the system selection form before performing a group operation.

Messages
A: Error
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
________________
EE Raceway Modeling Reference Guide - February 2003

414
________________Appendix B: System/Application Manager Information

Appendix B System/Application
Manager Information
This appendix and the following appendices outline the responsibilities for
the EE Raceway system or application manager. Included in these
appendices are important references and procedures needed to prepare and
customize the EE Raceway product:

Appendix C: EE Databases describes the EE databases and contains

Mgmt.
B: System/App
schema descriptions for both the reference and project databases. Important
new procedures related to RIS and the databases are described in this
section.

Appendix D: Specification describes vendor specifications and how to


prepare them.

Appendix E: Eden Symbol Generation describes generation of Eden


symbols and provides a sample symbol processor file.

Appendix F: EE File Structure contains the file structure for both EE


Nucleus and EE Raceway. It identifies the files that can be modified and
describes some important files. You will need this appendix to locate files
that you want to modify.

Appendix G: Customizing Environment Files explains how to modify the


files that list the processes, reports, rule checks, and printers in the EE
Raceway 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 to
customizing the alias.cmd file and customizing menus.

Appendix I: rway.cmds contains the rway.cmds file. This file is run


automatically 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 and


rule checks reports delivered with the product.

Appendix K: RIS Schema Manager contains a detailed description of the


RIS Schema Manager utility.

Appendix L: RIS Schema Definition File describes the file that maintains
all schema definitions known to RIS.

415
________________
EE Raceway Modeling Reference Guide - February 2003

Appendix M: EE Manager contains a description of the EE Manager


utility and its Edit Database process.

Appendix N: EE Configure describes the EE environment variables and


how to configure them.

416
________________ Appendix B: Customizing

Customizing
Some simple customization is described in the appendices entitled
Customizing, alias.cmd, and rway.cmds (all involve modifying existing text
files using an editor). More extensive customization is possible for
advanced users. Such customization includes writing processes and user
commands using the MicroStation software. Refer to the MicroStation
Applications Programmer’s Guide for this latter procedure.

Precision Input Form

Mgmt.
B: System/App
Several designs of the precision input form are delivered with EE Raceway.
The available precision input forms (described below) reside in
win32app\eerway\sym.

Form Name Description


piform* default
piform_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 illustration


of 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 to
the reference database. For detailed information about editing your .unl
files 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 to


the 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 Raceway Modeling Reference Guide - February 2003

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 table
in 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 for
the one-line type.

For sample files, refer to the tray_spec and tray_part .unl files that
are delivered with EE Raceway.

418
________________ 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 the
following:

FILE "tray_part.unl" DELIMITER "|";


INSERT INTO tray_part;

5. Add records to the mscatalog table (in the reference database) for
both the <one-line_type>_spec and the <one-line_type>_part tables.

You can accomplish this either by adding rows directly to the

Mgmt.
B: System/App
mscatalog table or by inserting records in the mscatref.unl file.

6. Add records to the mscolumns table (in the reference database) for
both the <one-line_type>_spec and the <one-line_type>_part tables.

You can accomplish this either by adding rows directly to the


mscolumns table or by inserting records in the mscolref.unl file.

7. Add necessary rows to the mscodelist table in the reference database


for any columns that are codelisted for the one-line type.

You can accomplish this either by adding rows directly to the


mscodelist table or by inserting records in the mscodref.unl file. For
information 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 the
ol_type table or by inserting records in the olt.unl file.

9. Run the Update reference schema process to add your new one-line
type to the database.

Adding a Special Fitting


This section outlines the basic steps necessary to add a special fitting to the
reference database. For detailed information about editing your .unl files
and database tables, consult the appendix entitled EE Databases. These
instructions are intended as a basic workflow.

1. Add the special fitting table to the reference database, as in the


following example:

create table transit


(
vendor integer not null,

419
________________
EE Raceway Modeling Reference Guide - February 2003

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, or
you add the data to your tlt.unl file.

4. Create any new Eden symbols needed to graphically display the new
special fitting.

For basic information about creating Eden symbols, see the appendix
entitled Eden Symbol Generation.

5. Create a <special fitting>.unl that contains the required default values


for your fitting.

For a sample special fitting .unl file, refer to the pullbox.unl file that
is delivered with EE Raceway.

6. Add the newly-created <special fitting>.unl file to the rwayref.cmd


file, 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 the
special fitting table.

420
________________ Appendix B: Customizing

You can accomplish this either by adding a row directly to the


mscatalog table, or by inserting a record in the mscatref.unl file.

8. Add a row to the mscolumns table (in the reference database) for the
special fitting table.

You can accomplish this either by adding the row directly to the
mscolumns table in the database, or by inserting a record in the
mscolref.unl file.

9. Add necessary rows to the mscodelist table (in the reference database)
for any columns that are codelisted for the special fitting.

Mgmt.
B: System/App
You can accomplish this either by adding rows directly to the
mscodelist table or by inserting records in the mscodref.unl file. For
information 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_part


table in the database, or by inserting a record in the manprt.unl file.

11. Run the Update reference schema process to add your new special
fitting to the database.

Reports
You can create or modify standard and rule check reports. The report
template library is delivered in the win32app\eerway\report directory.
Delivered reports are created using the RISRPT product and are compatible
with the DB Access (DBA) product. Reports may also be created using the
native RDBMS report writing product.

Error Messages
Error messages for the delivered commands are located in the error.msg
files 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). You
cannot change this name. To the right of each = is the message itself, which
you can modify. Use a standard text editor to modify the error.msg files.

421
________________
EE Raceway Modeling Reference Guide - February 2003

EE Environment Variables
This section lists and describes the environment variables that are delivered when you
download EE Raceway. They include Microstation, EE Nucleus, and EE Raceway-specific
variables.

These environment variables can be modified using the Start > Programs > EENUC > EE
Configure 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 file
MicroStation uses to save data about the attached menu. This directory
is 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 contains


detailed 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 files
RWAY_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 or


c100/rmonshell file:

MS_CACH Sets the memory to be allocated for a design file editing session. This
variable will override the user preferences setting.

422
________________ 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.

Mgmt.
B: System/App
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 cannot
override 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 that
you 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
________________ 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 in
which a relation is a two-dimensional table comprised of rows and columns. Most relational databases use
Standard Query Language (SQL).

The EE products attach to their relational databases through Intergraph Corporation’s Relational Interface
System (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 databases
generated 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.

C: EE Databases
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 reference
database.

The project database contains information applicable to a particular project. A project is an associated
collection of drawings and their database.

The reference database contains information applicable to multiple projects, such as symbol and part
information. (For those familiar with EDES, the reference database replaces the concept of shared part entity
files and active entity files.) One reference database can be accessed by multiple project databases. Thus, you
are not forced to re-enter common information for each project. The reference database is identified when you
enter a project. You can report and query from the reference database as well as the project database.

425
________________
EE Raceway Modeling Reference Guide - February 2003

Relational Interface System (RIS)


All EE products use a RIS schema, which you define, to attach to an SQL-type database. The RIS schema
identifies a unique database/user combination in a given commercial database system. Different RDBMS’s
establish users in different ways; in fact, the very concept of a database differs greatly from one RDBMS to
another. Through the use the RIS risschema_mgr product, you can update schemas without knowing either the
differences between RDBMS’s or the syntax of the RIS create schema statement. (See the appendix entitled
RIS Schema Manager for more information on the RIS Schema Manager product.)

426
________________ 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 the
individual RDBMS documentation on installation procedures.

INFORMIX users will now have to create all databases in ANSI mode. Check the
documentation delivered with the product for information on infxcreate, or see INFORMIX
documentation 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 appendix
entitled RIS Schema Manager for detailed information on using the RIS Schema Manager product.) This
process 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 and
databases. The risschema_mgr process updates and maintains the file. You can manage the risschema file in

C: EE Databases
any of the following ways:

— You can create and maintain your own risschema file, using the risschema_mgr process. The process
resides locally on your machine and recognizes any RIS schema on any database, local or remote, that was
created using RIS Schema Manager.

— You can locate the risschema file from another workstation using the risschema_mgr process and access any
schemas created on that machine.

Once you have created a schema on your empty database, you need to populate that database with EE tables and
default 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
________________
EE Raceway Modeling Reference Guide - February 2003

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 Update
schema 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 replaces
the old table definition with the new table definition keeping column data where column names
match.

— 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 the
EE Environment, you must first export the variable ENV_MSGS to win32app\ingr\eenuc\msg, and then key in
the 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
________________ 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 existing
schema, with EE Raceway tables and default reference information.

You can use this process to execute ANY valid RIS-supported SQL statement upon an existing
schema. Simply place it in a file and call that filename with the -q option.

C: EE Databases

429
________________
EE Raceway Modeling Reference Guide - February 2003

Reference Schema - General Description


The Electrical Engineer reference database is a multi-table relational database containing default attribute
information and specification information. You can establish default attributes for drawings, raceway connect
points (RCPs), one-lines, drop points, and equipment pointers. All specification information is carried in the
reference 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/attribute
structure 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 reference
schema 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 or
deleted.

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 and
key_description in the mscatalog entry for the given table. The key_column field is a unique index used to
identify a particular row of default attributes in the reference schema. Each of the tables is delivered with one
entry 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-line
type unless you override the key during annotation for an individual one-line. The one-line table is delivered
with both the DEFAULT and METRIC DEFAULT keys. The DEFAULT key is used with the seed design
file using English measurements, while the METRIC DEFAULT is used with the seed design file using Metric
measurements.

430
________________
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 the
default key for all RCPs unless you override the key during annotation for an individual RCP. Text annotation
overrides any default values.

Equipment Pointer Keys


You will identify the key for equipment pointers through the Raceway Defaults form. The key you specify will
serve as the default key for all equipment pointers unless you override the key during annotation for an
individual 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 serve
as 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.

C: EE Databases

431
________________
EE Raceway Modeling Reference Guide - February 2003

Codelists
Codelists are tables in the reference database which contain all available values for a particular column of a
table in the project database. For example, the codelist table ol_type in the reference database will contain all
possible values that can be loaded into the column ol_type in the straight, fitting, and one_line tables in the
project database.

During loads of the project database, the reference database codelists are matched to the annotated values. Only
values in the reference database codelist tables are loaded into the project database. The system issues you a
warning 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 new
approval 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 number


index_value char(20) approval status description

The approval status rows delivered with EE Raceway are:

index_column index_value

1 1 - blank
2 2 - approved
3 3 - approved
4 4 - approved
5 5 - approved
6 6 - approved
7 7 - approved
8 8 - approved
9 9 - approved
10 10 - approved
11 11 - not approved

432
________________ Appendix C: Codelists

Cardinal Codelist Table


The cardinal codelist table defines the available cardinal point routing justification locations. You
must not add or remove to this table.

COLUMN_NAME TYPE DESCRIPTION

ee_car_num integer cardinal index number


ee_cardinal char(20) cardinal description

The cardinal point values delivered with EE Raceway are:

ee_car_num ee_cardinal

0 TOP LEFT
1 CENTER LEFT
2 BOTTOM LEFT
6 TOP CENTER
7 CENTER CENTER
8 BOTTOM CENTER
12 TOP RIGHT
13 CENTER RIGHT

C: EE Databases
14 BOTTOM RIGHT

Drawing Type Codelist Table


The drawing_type codelist table defines the available drawing types. You can add new drawing types
to this table, but you must not remove the existing row.

COLUMN_NAME TYPE DESCRIPTION

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 to
uniquely identify an index value. The table also contains the ee_part_table column which itself
contains the mscatalog number of the table holding the part information. The ee_rcp_ol_type column
contains 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 number


index_value char(20) manual_part description
ee_part_table integer special fitting parts table number
ee_rcp_ol_type integer one-line type index column number
ee_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 0


2 pullbox 249 3 0
3 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 contains
the index_column column, which is an integer value the software uses to uniquely identify an index
value. The table also contains the ee_spec, ee_part, ee_ol, and ee_rcp_part tables which define the
tables containing specification information for each one-line type. The ee_priority_level column
defines the routing priority for each one-line type.

COLUMN_NAME TYPE DESCRIPTION

index_column integer one-line type index number


index_value char(20) one-line type description
ee_spec_table integer specification table mscatalog number
ee_part_table integer spec parts table mscatalog number
ee_ol_table integer one-line table mscatalog number
ee_rcp_part_table integer special fitting parts table number
ee_max_run_angle integer maximum bends allowed per run
ee_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 5


2 WIREWAY 242 243 204 0 0 5
3 CONDUIT 244 245 204 246 360 10
4 AIRWAY 247 248 204 0 0 10
5 DUCTBANK 260 0 204 0 0 7

434
________________ Appendix C: Codelists

RCP Type Codelist Table


This table defines how the EE Raceway software uses RCPs (Raceway Connect Points). The rcp_type
table contains the index_column column, which is an integer value the software uses to uniquely
identify an index value. You must not add or remove rows from this table, nor should you modify the
index_column values. You can modify the index_value values.

COLUMN_NAME TYPE DESCRIPTION

index_column integer rcp type index number


index_value char(20) rcp type description

The RCP types delivered with EE Raceway are:

index_column index_value description

1 <blank> general raceway connect point


2 ROUTE raceway connect point and route point

System Codelist Table

C: EE Databases
The ee_system table must be loaded in the reference database before you can create any raceway design
files. You can add, remove, or update any of the systems delivered with EE Raceway. The system
table contains the system_num column, which is an integer value the software uses to uniquely identify
a system name.

COLUMN_NAME TYPE DESCRIPTION

system_num integer system index number


system_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 Control
2 Communication
3 High Voltage
4 Low Voltage
5 Alarm
6 Instrumentation
7 Signal
8 Digital
9 Analog
10 Thermocouple
11 RTD
12 Medium Voltage
13 Normal Lighting
14 Emergency Lighting
15 Security
16 Fire Safety
17 DC Power
18 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. 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 or remove rows from the table, nor should you modify the
index_column values. You can modify the index_value values.

COLUMN_NAME TYPE DESCRIPTION

index_column integer three-line type index number


index_value char(20) three-line type description

The three-line types delivered with EE Raceway are:

index_column index_value

1 STRAIGHT
2 ELBOW
3 WYE
4 CROSS
11 PULLBOX
12 CONDUIT BODY
14 DROPOUT

436
________________ Appendix C: Codelists

Three_Line Subtype Codelist Table


The tl_subtype table further defines the available 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 or remove rows from the table, nor should you modify the index_column values. You can modify
the index_value values.

COLUMN_NAME TYPE DESCRIPTION

index_column integer three-line subtype index number


index_value char(20) three-line subtype description

The three-line subtypes delivered with EE Raceway are:

index_column index_value

1 <blank>
2 VERTICAL
3 INSIDE VERTICAL
4 OUTSIDE VERTICAL
5 HORIZONTAL
6 LEFT HORIZONTAL

C: EE Databases
7 RIGHT HORIZONTAL
8 REDUCER
9 LEFT REDUCER
10 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 or
remove rows from the table, nor should you modify the index_column values. You can modify the
index_value values.

COLUMN_NAME TYPE DESCRIPTION

index_column integer three-line qualifier index number


index_value char(20) three-line qualifier description

437
________________
EE Raceway Modeling Reference Guide - February 2003

The three-line qualifiers delivered with EE Raceway are:

index_column index_value

1 <blank>
2 RIGID
3 BENDABLE
4 FLEXIBLE
5 ADJUSTABLE

Units Codelist Table


This table (ee_unit) defines the units that are used for one-line dimension values. The unit table
contains the index_column column, which is an integer value the software uses to uniquely identify an
index value. You must not add or remove rows from this table, nor should you modify the
index_column values. You can modify the index_value values.

COLUMN_NAME TYPE DESCRIPTION

index_column integer units index number


index_value char(20) units description

The units delivered with EE Raceway are:

index_column index_value

1 English
2 Metric

Vendor Codelist Table


You must have a vendor in the vendor codelist table before loading any specification tables in the
database. You can add vendors as necessary to this table, but do not remove the rows delivered with
the product. The vendor table contains the index_column column, which is an integer value the
software uses to uniquely identify a vendor name.

COLUMN_NAME TYPE DESCRIPTION

index_column integer vendor index number


index_value char(20) vendor name
catalog char(20) catalog

438
________________ Appendix C: Codelists

The vendors delivered with EE Raceway are:

index_column index_value catalog

1 default delivered blank


2 sample delivered blank
3 unknown delivered blank
4 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 during
the EERWAY command CONDUIT SIZING. The wire/cable code table contains the index_column
column, which is an abbreviated value the software uses to uniquely identify an index value. You may
add or remove rows from this table, the values of the index_column should include all the wire/cable
codes represented in the data of the Wire/Cable (ee_pseudo_cable) table code column. The
index_value provides a more complete description of the entry.

COLUMN_NAME TYPE DESCRIPTION

index_column char(20) wire/cable code index value

C: EE Databases
not null
index_value char(20) wire/cable code description

The wire/cable codes delivered with EE Raceway are:

index_column index_value

AC AC
AD AD
AG AG
AH AH
AM AM
AN AN
AP AP
AR AR
AS AS
CP CP
CQ CQ
CV CV
CW CW
CX CX

439
________________
EE Raceway Modeling Reference Guide - February 2003

Wire/Cable Configuration Codelist Table


This table (ee_pcbl_config) defines the wire/cable configuration that are used for selecting a
Wire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable configuration table
contains the index_column column, which is an abbreviated value the software uses to uniquely
identify an index value. You may add or remove rows from this table, the values of the index_column
should 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 the
entry.

COLUMN_NAME TYPE DESCRIPTION

index_column char(20) wire/cable configuration index value


not null
index_value char(20) wire/cable configuration description

The wire/cable configurations delivered with EE Raceway are:

index_column index_value

\C single conductor
PR "pair 2 conductors
TR "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 the
EERWAY command CONDUIT SIZING. The wire/cable size table contains the index_column
column, which is an abbreviated value the software uses to uniquely identify an index value. You may
add or remove rows from this table, the values of the index_column should include all the wire/cable
sizes represented in the data of the Wire/Cable (ee_pseudo_cable) table cable_size column. The
index_value provides a more complete description of the entry.

COLUMN_NAME TYPE DESCRIPTION

index_column char(20) wire/cable size index value


not null
index_value char(20) wire/cable size description

The wire/cable sizes delivered with EE Raceway are:

index_column index_value

36 AWG 36 AWG
34 AWG 34 AWG
32 AWG 32 AWG
30 AWG 30 AWG
28 AWG 28 AWG
27 AWG 27 AWG

440
________________ Appendix C: Codelists

26 AWG 26 AWG
24 AWG 24 AWG
22 AWG 22 AWG
20 AWG 20 AWG
18 AWG 18 AWG
16 AWG 16 AWG
14 AWG 14 AWG
12 AWG 12 AWG
10 AWG 10 AWG
8 AWG 8 AWG
6 AWG 6 AWG
4 AWG 4 AWG
3 AWG 3 AWG
2 AWG 2 AWG
1 AWG 1 AWG
1/0 AWG 1/0 AWG
2/0 AWG 2/0 AWG
3/0 AWG 3/0 AWG
4/0 AWG 4/0 AWG
250 MCM 250 MCM
300 MCM 300 MCM
350 MCM 350 MCM
400 MCM 400 MCM

C: EE Databases
500 MCM 500 MCM
600 MCM 600 MCM
700 MCM 700 MCM
750 MCM 750 MCM
800 MCM 800 MCM
900 MCM 900 MCM
1000 MCM 1000 MCM
1250 MCM 1250 MCM
1500 MCM 1500 MCM
1750 MCM 1750 MCM
2000 MCM 2000 MCM

Wire/Cable Color Codelist Table


This table (ee_pcbl_color) defines the wire/cable insulation color that are used for selecting a
Wire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation color table
contains the index_column column, which is an abbreviated value the software uses to uniquely
identify an index value. You may add or remove rows from this table, the values of the index_column
should 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 the
entry.

441
________________
EE Raceway Modeling Reference Guide - February 2003

COLUMN_NAME TYPE DESCRIPTION

index_column char(20) wire/cable insulation color index value


not null
index_value char(20) wire/cable insulation color description

The wire/cable insulation colors delivered with EE Raceway are:

index_column index_value

BLK BLACK
W WHITE
R RED
GR GREEN
ORN ORANGE
BL BLUE
W/BLK WHITE/BLACK
R/BLK RED/BLACK
GR/BLK GREEN/BLACK
ORN/BLK ORANGE/BLACK
BL/BLK BLUE/BLACK
BLK/W BLACK/WHITE
R/W RED/WHITE
GR/W GREEN/WHITE
BL/W BLUE/WHITE
BLK/R BLACK/RED
W/R WHITE/RED
ORN/R ORANGE/RED
BL/R BLUE/RED
R/GR RED/GREEN
ORN/GR ORANGE/GREEN
BLK/W/R BLACK/WHITE/RED
W/BLK/R WHITE/BLACK/RED
R/BLK/W RED/BLACK/WHITE
GR/BLK/W GREEN/BLACK/WHITE
ORN/BLK/W ORANGE/BLACK/WHITE
BL/BLK/W BLUE/BLACK/WHITE
BLK/R/GR BLACK/RED/GREEN
W/R/GR WHITE/RED/GREEN
R/BLK/GR RED/BLACK/GREEN
GR/BLK/ORN GREEN/BLACK/ORANGE
ORN/BLK/GR ORANGE/BLACK/GREEN
BL/W/ORN BLUE/WHITE/ORANGE
BLK/W/ORN BLACK/WHITE/ORANGE
W/R/ORN WHITE/RED/ORANGE
ORN/W/BL ORANGE/WHITE/BLUE
W/R/BL WHITE/RED/BLUE
BLK/W/GR BLACK/WHITE/GREEN
W/BLK/GR WHITE/BLACK/GREEN
R/W/GR RED/WHITE/GREEN
GR/W/BL GREEN/WHITE/BLUE
ORN/R/GR ORANGE/RED/GREEN

442
________________ Appendix C: Codelists

BL/R/GR BLUE/RED/GREEN
BLK/W/BL BLACK/WHITE/BLUE
W/BLK/BL WHITE/BLACK/BLUE
R/W/BL RED/WHITE/BLUE
GR/ORN/R GREEN/ORANGE/RED
GR/R/BL GREEN/RED/BLUE
BL/R/ORN BLUE/RED/ORANGE
BLK/ORN/R BLACK/ORANGE/RED
BRN BROWN
Y YELLOW

Wire/Cable Voltage Codelist Table


This table (ee_pcbl_volt) defines the wire/cable insulation voltage rating that are used for selecting a
Wire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation voltage
rating table contains the index_column column, which is an abbreviated value the software uses to
uniquely identify an index value. You may add or remove rows from this table, the values of the
index_column should include all the wire/cable insulation voltage ratings represented in the data of the
Wire/Cable (ee_pseudo_cable) table voltage column. The index_value provides a more complete
description of the entry.

C: EE Databases
COLUMN_NAME TYPE DESCRIPTION

index_column char(20) wire/cable insulation voltage rating index value


not null
index_value char(40) wire/cable insulation voltage rating description

The wire/cable voltage ratings delivered with EE Raceway are:

index_column index_value

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 a
Wire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation type table
contains the index_column column, which is an abbreviated value the software uses to uniquely
identify an index value. You may add or remove rows from this table, the values of the index_column
should 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 of
the entry.

COLUMN_NAME TYPE DESCRIPTION

index_column char(20) wire/cable insulation type index value


not null
index_value char(100) wire/cable insulation type description

The wire/cable insulation types delivered with EE Raceway are:

index_column index_value

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 Cambric
AVB Impregnated Asbestos & Varnished Cambric (Flame retardant, cotton braid)
AVL Impregnated Asbestos & Varnished Cambric (AVL-lead sheath)
FEP Fluorinated Ethylene Propylene
FEPB Fluorinated Ethylene Propylene (Glass braid Asbestos or other Suitable braid material)
MI Magnesium Oxide (Copper)
MTW Flame-, Moisture-, Heat- and Oil-Resistant Thermoplastic
PFA Perfluoroalkoxy
PFAH Perfluoroalkoxy
RH 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 Rubber
TA Thermo-plastic and Asbestos (Flame-retardant, non-metallic covering)
TBS Thermo-plastic (Flame-retardant, non-metallic covering)

444
________________ Appendix C: Codelists

TFE Extruded Polytetra-fluoro-ethylene


THHN Flame-, Heat-Resistant Thermoplastic (Nylon jacket or equivalent)
THHN/THWN Flame-, (Moisture-) & Heat-Resistant Thermoplastic (Nylon jacket or equivalent)
THW Flame-, Moisture- & Heat-Resistant Thermoplastic
THWN Flame-, Moisture- & Heat-Resistant Thermoplastic (Nylon jacket or equivalent)
TW Flame-Retardant, Moisture- and Heat-Resistant Thermoplastic
UF 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 Polymer
Z Modified Ethylene Tetrafluoro-ethylene

Yes-No Codelist Table


The ee_yes_no codelist table defines the available positive and negative user responses. You must not
add or remove rows from this table.

COLUMN_NAME TYPE DESCRIPTION

index_column integer yes-no response index number


index_value char(20) yes-no response description

C: EE Databases
The Yes-No values delivered with EE Raceway are:

index_column index_value

0 NO
1 Yes

445
________________
EE Raceway Modeling Reference Guide - February 2003

Fitting Environment Rules


The fitting environment rules are the rules stored in the reference database table tl_fit_env that control the Place
Fitting by Rule commands. The software compares the one-line environment at an RCP in the design file with
the rules stored in this table to determine which fitting to place at the RCP. You can add, remove, or update any
of 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 table
to find a match. If found, the symbol in the part table stored will be placed at the RCP.

COLUMN_NAME TYPE DESCRIPTION

ee_ol_type integer intersecting one-line’s one-line type number


ee_tl_type integer intersecting one-line’s three-line type number, zero if not applicable
ee_tl_subtype integer intersecting one-line’s three-line subtype number, zero if not applicable
ee_tl_qual integer intersecting one-line’s three-line qualifier number, zero if not
applicable
ee_num_ols integer number of intersecting one-lines
ee_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 number
ee_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 CC
3 0 0 0 2 90 - 246 CLB
3 0 0 0 3 90,180 - 246 CT
3 0 0 0 3 90 90 246 CGUAM
3 0 0 0 4 90,180,270 - 246 CX
3 0 0 0 4 90,180 90 246 CGUAW
3 0 0 0 5 90,180,270 90 246 CEABY

446
________________ Appendix C: Fitting Environment Rules

Intersecting Conduit One-lines

Planar Angles = 90, 180, 270

Non-Planar Angle = 90

C: EE Databases

447
________________
EE Raceway Modeling Reference Guide - February 2003

Project Schema - General Description


The project schema contains information about the drawings that are part of a particular project. The schema
stores information associated with the elements in each drawing; its one-lines, RCPs, and three-lines. Default
and specification information is copied from the reference schema into the project schema when you run Load
Database.

448
________________ 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 schemas
using one of the currently-supported RDBMS’s (INFORMIX, ORACLE, INGRES). Additionally, you must
use 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 the
Update 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 schema
name, 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.

C: EE Databases
Sql and Cmd Files

Accept the names of the sql and cmd (command) files associated with each application. The sql file contains
the commands used to create tables, views, and to grant permissions within the schema, while the command file
loads 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 supplying
the sql and cmd files to the process. If you select multiple applications, then Update project schema runs each
application sequentially against the database.

Updating Reference Schemas


Update the reference schema from the Database Utilities menu in the Electrical Engineer environment, using
the 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 schema
name, 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 contains
the commands used to create tables, views, and to grant permissions within the schema, while the command file
loads 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 supplying
the sql and cmd files to the process. If you select multiple applications, then Update reference schema runs
each 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 default
name when you enter the project. However, you can override the default by exporting the $EE_SCHEMA
variable in your $HOME/.EErc file to be your project schema name.

450
________________ 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 the
database schema before schema creation, simply include the necessary changes in the .sql file before Update
schema 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 the
Update schema process. The table definitions that exist in this file determine how the tables will look when
complete. Therefore, columns can be added or removed from an existing schema according to the "create
table" statements in the .sql file. For example, columns are added into the .sql file for the one_line table, these
columns will be added into the existing rows of the existing one_line table. When this process finds a "create
table" 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.

C: EE Databases
If rows exist in the updated table, any new columns that are added will be blank in each row. The new
table 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 without
making the appropriate change to the ".sql" file, you would lose any data that may have been on that
column.

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 in
such 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 you
modify a character column to make it smaller (resizing char(20) to be char(10), for example), then any
row 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 be
counted and ignored; the unique index prevents the entry of duplicate information when updating any EE
application. If a table does not have a unique index, then the .unl file will be loaded only if the table is
empty.

Table names can be changed except for table names that begin with the letters "ms" and "ee_". They must also
be changed appropriately in the MSCATALOG table in order for the software to run properly. Keep in mind
that the columns within the tables in the reference schema must be a subset of the columns of the corresponding
tables 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 schema
process initiates the command file which automatically finds and loads the information in the .unl files into the
database. These files can be edited by the system manager to include additional defaults, part data, and codelist
values. 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 file
must 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’s
sqlplus, 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 more
information 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 you
will 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. In
this case the "olt.unl" file will exist in the current directory but a full path name can be specified on this
file (e.g. FILE win32app\ingr\eerway\db\olt.unl). The delimiter is one character long. It tells the process
that 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 being
loaded. 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 a
row 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
________________ Appendix C: Modifying the Reference Schema

In this example, "1" is the index_column value, "TRAY" is the index_value column value, "240" is the
ee_spec_table column, etc. If in the "olt.unl" file you would like to add additional entries, you can edit
this 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 information
into 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 tray
specification information you want to load into the reference database, separating each column of data
with 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|

C: EE Databases
4. When you have finished editing the .unl file, run the Update reference schema process to load the
specification information into the tray_spec table.

453
________________
EE Raceway Modeling Reference Guide - February 2003

EE Raceway Reference Database Schema


Description
This section lists and describes the tables in the EE Raceway reference database schema, and includes detailed
information about the columns that comprise each table.

An asterisk (*) indicates that you must not modify the column name. You should not modify
those column names having a prefix of "ee_".

approv_status
This codelist table defines the available approval status values: blank, approved, not approved, and so
forth. See the section entitled Codelists earlier in this appendix for a detailed description of this table.

Column Name Type Index Null


index_column integer no no
index_value Char(20) no yes

index_column: an integer value used by the software to uniquely identify an approved status
description.

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 Null


ee_tl_type* integer no yes
ee_tl_subtype* integer no yes
ee_tl_qual* integer no yes
ee_angle* real no yes
ee_symbol* Char( 6) no yes
ee_spec_key* Char( 28) dups yes
ee_spec2_key* Char( 28) no yes
ee_part_key* Char( 28) uniq no
ee_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
________________
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 specification
information.

ee_spec2_key: if the current airway part is a reducer, this column is the key to the row in the other
airway 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 Raceway
uses airways to reserve space for the routing of cable or other raceway material, and also to maintain
connectivity to a raceway system.

Column Name Type Index Null

C: EE Databases
ee_units* integer no no
ee_out_ht_diam* real dups no
ee_out_width* real no yes
ee_extension* real no yes
ee_transition* real no yes
ee_radius* real no yes
ee_xs_cell* Char( 6) no yes
ee_spec_key* Char( 28) uniq no
ee_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 raceway
software.

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 raceway
software.

ee_transition: the column used to define the airway fitting transition length to the EE raceway
software.

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 sketch
propagation. 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 so
forth). Refer to the section entitled Codelists earlier in this appendix for a detailed description of this
table.

Column Name Type Index Null


ee_car_num integer uniq no
ee_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
________________
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 Null


vendor integer dups no
ee_units* integer no no
nominal_size_1 real no yes
nominal_size_2 real no yes
weight real no yes
material Char( 20) no yes
ee_part* Char( 20) no yes
ee_symbol* Char( 6) no yes
ee_dimension_1* real no yes
ee_dimension_2* real no yes
ee_dimension_3* real no yes
ee_dimension_4* real no yes
ee_dimension_5* real no yes
ee_dimension_6* real no yes
ee_part_key* Char( 28) uniq no
ee_description* Char( 40) no yes
ee_tl_type* integer no no

C: EE Databases
volume real no yes
style Char( 20) no yes
ee_pull_point integer no yes

vendor: the codelisted column used to define the vendor of the conduit body special fitting.

ee_units: the codelisted column used to define the units of measurement.

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 raceway
reports.

ee_dimension_2: the column used to define a conduit body dimension value to eden and the raceway
reports.

ee_dimension_3: the column used to define a conduit body dimension value to eden and the raceway
reports.

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 raceway
reports.

ee_dimension_5: the column used to define a conduit body dimension value to eden and the raceway
reports.

ee_dimension_6: the column used to define a conduit body dimension value to eden and the raceway
reports.

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.

ee_tl_type: the codelisted column used to define the three-line type.

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 type
of the cable outer jackets and number of cables within the conduit. This calculation assumes a
homogeneous mixture of either all LEAD or all NON-LEAD armor types for the cable outer jackets for
the cables routed within the same conduit. If the cables contained in a conduit exceed the maximum
allowable conduit fill, then the conduit is marked as being overfilled.

Column Name Type Index Null


ee_rule_set Char( 20) no yes
ee_jacket_armor Char( 10) no yes
ee_num_cables integer no no
ee_max_fill real no yes

ee_rule_set: identification of the rule set that applies to the raceway system fill calculations, for
example 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
________________
Appendix C: EE Raceway Reference Database Schema Description

cond_part
This table stores the part specification information for the one-line type CONDUIT.

Column Name Type Index Null


ee_tl_type* integer no no
ee_tl_subtype* integer no no
ee_tl_qual* integer no no
ee_angle* real no yes
ee_weight* real no yes
ee_part* Char( 20) no yes
ee_symbol* Char( 6) no yes
ee_spec_key* Char( 28) dups yes
ee_spec2_key* Char( 28) no yes
ee_part_key* Char( 28) uniq no
ee_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.

C: EE Databases
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 general
specification information.

ee_spec2_key: if the current conduit part is a reducer, this column is the key to the row in the other
conduit 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.

459
________________
EE Raceway Modeling Reference Guide - February 2003

cond_spec
This table stores the general specification information for the one-line type CONDUIT.

Column Name Type Index Null


vendor integer dups no
ee_units* integer no no
nominal_size real no yes
ee_dimension_1* real no yes
ee_out_ht_diam* real dups no
ee_extension* real no yes
ee_transition* real no yes
ee_radius* real no yes
weight real no yes
material Char( 20) no yes
ee_const_type integer no no
ee_xs_cell* Char( 6) no yes
ee_spec_key* Char( 28) uniq no
ee_description Char( 40) no yes

vendor: the codelisted column used to define the vendor of the conduit specification.

ee_units: the codelisted column used to define the units of measurement.

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 raceway
reports.

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 raceway
software.

ee_transition: the column used to define the conduit fitting transition length to the EE raceway
software.

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
________________
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 sketch
propagation. 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.

drawing
This table defines both the columns that you can annotate for title blocks and their default column
values.

Column Name Type Index Null


drawing_type* Char( 20) no no
sheet* Char( 20) no yes

C: EE Databases
ee_key* Char( 28) uniq no
ee_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 entitled
Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Null


ee_code Char(20) uniq no
code_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
________________
EE Raceway Modeling Reference Guide - February 2003

drop_point
This table defines both the columns you can annotate for drop point symbols and their default column
values.

Column Name Type Index Null


tag Char(20) no yes
ee_dist_down_ol* real no yes
ee_dist_to_rcp* real no yes
ee_key* Char(28) unique no
ee_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.

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.

duct_spec
This table stores the general specification information for the one-line type DUCTBANK.

Column Name Type Index Null


ee_units integer no no
ee_out_ht_diam real dups no
ee_out_width real dups yes
material Char( 20) no yes
ee_xs_cell Char( 6) no yes
ee_spec_key Char( 28) uniq no
ee_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 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
________________
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 sketch
propagation. 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.

ee_cond_x_area
This table stores the cross sectional area of conduit identified by its nominal size.

Column Name Type Index Null


nominal_size real uniq no
ee_dimension_1 real no yes
ee_area real no yes

C: EE Databases
nominal_size: the column used to define a conduit nominal size that corresponds to the same column
in the cond_spec table.

ee_dimension_1: the column used to define a conduit dimension value that corresponds to the same
column 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 to
graphics through the Post Attribute process.

Column Name Type Index Null


table_name Char( 32) uniq yes
column_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 Raceway Modeling Reference Guide - February 2003

ee_pcbl_code
This codelist table defines the codes that are used in the ee_pseudo_cable table for the EERWAY
Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix for a detailed
description of this table.

Column Name Type Index Null


index_column Char( 20) uniq no
index_value Char( 20) dups yes

index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_code


description.

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 Raceway
Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix for a detailed
description of this table.

Column Name Type Index Null


index_column Char( 20) uniq no
index_value Char( 20) dups yes

index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_color


description.

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 the
EE Raceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix
for a detailed description of this table.

Column Name Type Index Null


index_column Char( 20) uniq no
index_value Char( 20) dups yes

index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_config


description.

index_value: the column that contains the description of each available ee_pcbl_config.

464
________________
Appendix C: EE Raceway Reference Database Schema Description

ee_pcbl_insul
This codelist table defines the insulation types that are used in the ee_pseudo_cable table for the EE
Raceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix for
a detailed description of this table.

Column Name Type Index Null


index_column Char( 20) uniq no
index_value Char(100) dups yes

index_column: an abbreviated value used by the software to uniquely identify an eepcbl_insul


description.

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 EE
Raceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix for
a detailed description of this table.

C: EE Databases
Column Name Type Index Null
index_column Char( 20) uniq no
index_value Char( 20) dups yes

index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_size


description.

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 table
for the EE Raceway Conduit Sizing command.

Column Name Type Index Null


index_column Char( 20) uniq no
index_value Char( 40) dups yes

index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_volt


description.

index_value: the column that contains the description of each available ee_pcbl_volt.

465
________________
EE Raceway Modeling Reference Guide - February 2003

ee_pseudo_cable
This table defines the cable/wires that are used in the EE Raceway Conduit Sizing command.

Column Name Type Index Null


ee_code Char( 20) no yes
config Char( 20) no yes
cable_size Char( 20) no yes
ee_color Char( 20) no yes
voltage Char( 20) no yes
insulation Char( 20) no yes
item_no Char( 20) uniq yes
ee_area real no yes
ee_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_units: the codelisted column used to define the units of measurement.

ee_system
This codelist table defines the systems that are available to contain EE Raceway graphics. Refer to the
section entitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Null


system_num integer uniq no
system_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
________________
Appendix C: EE Raceway Reference Database Schema Description

ee_units
This codelist table defines the units that are used for one-line dimension values. Refer to the section
entitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Null


index_column* integer uniq no
index_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 data
entry. If a table is not represented in the ee_unique table, a row will be loaded into the appropriate
table for each graphic element.

Column Name Type Index Null

C: EE Databases
table_name Char( 32) uniq yes
column_name Char( 32) uniq yes
ee_comp_type* Char( 10) uniq yes
blank_allowed integer no yes

table_name: the name of the table that requires single data entry. Multiple rows in the database could
contain 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 some
entries, where the information crosses products, this column is used to further describe what would
make 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. Refer
to the section entitled Codelists earlier in this appendix for a detailed description of this table.

Column Name Type Index Null


index_column* integer uniq yes
index_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 column
values. EE Raceway uses space envelopes to reserve blocks of space for raceway without maintaining
connectivity to any raceway system.

Column Name Type Index Null


tag Char( 20) no yes
ee_key* Char( 28) uniq no
ee_description* Char( 40) no yes

tag: the column used to define the space envelope tag.

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.

Space envelopes are not available with EE Raceway at the time of this printing.

468
________________
Appendix C: EE Raceway Reference Database Schema Description

light_fixture
This table stores the specification information for the manually placed equipment LIGHT_FIXTURE.

Column Name Type Index Null


ee_symbol Char( 6) no yes
voltage integer no yes
ee_dimension_1 real no yes
ee_dimension_2 real no yes
ee_dimension_3 real no yes
ee_part_key Char( 28) uniq no
fl_amps real no yes
ee_dimension_4 real no yes
ee_dimension_5 real no yes
ee_dimension_6 real no yes
ee_description Char( 40) no yes
item_type Char( 3) no yes
ee_dimension_7 real no yes
ee_dimension_8 real no yes
ee_dimension_9 real no yes
item_code_num Char( 20) no yes
vendor integer dups no

C: EE Databases
num_wires Char( 4) no yes
num_phase_wires integer no yes
power_factor real no yes
area_class Char( 6) no yes
oper_temp_deg_c integer no yes
text_1 Char( 32) no yes
text_2 Char( 32) no yes
text_3 Char( 32) no yes
text_4 Char( 32) no yes
ee_units integer no no
ee_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 raceway
reports.

ee_dimension_2: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

ee_dimension_3: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

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_dimension_4: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

ee_dimension_5: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

ee_dimension_6: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

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.

ee_dimension_7: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

ee_dimension_8: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

ee_dimension_9: the column used to define a light fixture dimension value to EDEN and the raceway
reports.

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.

text_2: the column used to describe characteristics about the light fixture.

text_3: the column used to describe characteristics about the light fixture.

text_4: the column used to describe characteristics about the light fixture.

ee_units: the codelisted column used to define the units of measurement.

ee_pull_point: the codelisted column used to define a light fixture as a cable pull point.

470
________________
Appendix C: EE Raceway Reference Database Schema Description

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 Null


index_column* integer uniq no
index_value* Char( 20) dups yes
ee_part_table* integer no yes
ee_rcp_ol_type* integer no yes
ee_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 specification
information.

ee_rcp_ol_type: the index_column number from the one-line type codelist table for the EE raceway
connect point of the special fitting.

C: EE Databases
ee_manpart_type: the column used to tell the load processor to load the manual part into either the
project database "fitting" table or the "panel" table.

mscatalog
Microstation 32 requires that every database used in graphics contain a table called mscatalog. This
table holds the entity numbers for all other tables in the database. In general, there will be one row in
mscatalog for each database table that is linked to graphic elements. Any table not directly linked to
graphics/EE elements does not need to appear in mscatalog. Both DBAccess and RISRPT (RIS Report
Writer) use this table.

Column Name Type Index Null


tablename Char( 32) no no
entitynum integer uniq no
screenform Char( 64) no yes
reporttable Char( 64) no yes
sqlreview Char(240) no yes
fencefilter Char(240) no yes
dastable Char(32) no yes
alias_name Char( 64) no yes
key_columns Char( 80) no yes
key_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 to
65535. The entity number uniquely identifies a particular table in the database. The MicroStation 32
database interface places the entity number of a table in the linkage it creates between a graphics
element and a table row. EE places the entity number in the EE header linkage of annotation in order
to 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 graphic
linkages 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 fence
operations.

dastable: specifies the name of the table that maps displayable attribute types to the sql select
statements 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 the
table. 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 that
represents 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 for
a particular column to a pre-defined set of values.

Column Name Type Index Null


table_name Char( 32) uniq no
column_name Char( 32) uniq no
join_table Char( 32) no no
code_column Char( 32) no no
text_column Char( 32) no no
index_column* Char( 32) no yes
index_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
________________
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 value
in code_column.

index_column: a column name that, if not NULL, will impose additional conditions to allow multiple
codelists 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 for
each column in an attribute table (for those attributes that exist in annotation). EE uses the mscolumns
information to control display of column information during annotation. A column that does not exist
as annotation linked to a graphics/EE element does not need to appear in mscolumns. The order in
which attributes appear on the annotation form is determined by the value in the column
ee_column_order.

C: EE Databases
Column Name Type Index Null
entitynum integer uniq no
attrnum integer uniq no
column_name Char( 32) no no
alias_name Char( 32) no yes
access_flag smallint no no
work_mode smallint no no
ee_column_order smallint no no

entitynum: the entity number assigned to the table whose columns are being described. Entity
numbers 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 the
database.

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 by
an EE user. A value of 0 indicates that the column is read_only, while a value of 1 indicates that it
allows read/write access.

work_mode: the column containing the code that identifies the use of a particular column by the EE
software. This column can be thought of as a filter which restricts the display of certain attributes
depending on the mode of work the user is performing. Since all EE Raceway column values are
displayed 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 the
annotation form.

ol_type
This codelist table defines the available one-line types (tray, wireway, conduit, and so forth). Refer to
the section entitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Null


index_column* integer uniq no
index_value* Char( 20) dups yes
ee_spec_table* integer no yes
ee_part_table* integer no yes
ee_ol_table* integer no yes
ee_rcp_part_table* integer no yes
ee_max_run_angle* integer no yes
ee_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 specification
information.

ee_max_run_angle: an integer containing the maximum allowed value of the sum of all bend angles
in 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. This
value is used to determine whether one one-line type can break or attach to another one-line type.

474
________________
Appendix C: EE Raceway Reference Database Schema Description

one_line
This table defines both the columns you can annotate for raceway one-lines and their default column
values.

Column Name Type Index Null


tag Char( 20) no yes
add_weight real no yes
ee_ol_length* real no yes
ee_spec_key* Char( 28) no no
ee_key* Char( 28) uniq no
ee_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 specification
information on the three-line elements.

C: EE Databases
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.

panel
This table defines both the columns you can annotate for panels/equipment and their default column
values.

Column Name Type Index Null


panel Char( 20) no yes
panel_descrip Char( 20) no yes
ee_approv_status integer no yes
ee_approv_date Char( 40) no yes
ee_create_date Char( 40) no yes
ee_last_rev_dat Char( 40) no yes
ee_key Char( 28) uniq no
ee_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_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

project
This table stores information for the project.

Column Name Type Index Null


prj_number char(20) dups yes
prj_name char(60) no yes
location char(60) no yes
prj_rule_set char(20) no yes
base_rule_set char(20) no yes
ee_key char(28) uniq no
ee_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
________________
Appendix C: EE Raceway Reference Database Schema Description

pullbox
This table stores the specification information for the manual fitting PULLBOX.

Column Name Type Index Null


vendor integer dups no
ee_units* integer no no
ee_out_ht_diam* real dups no
ee_out_width* real dups yes
ee_dimension_1 real dups yes
weight real no yes
material char(20) no yes
ee_part* char(20) no yes
ee_symbol* char(6) no yes
ee_part_key* char(28) uniq no
ee_description char(40) no yes
ee_tl_type integer no no
ee_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.

C: EE Databases
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 raceway
reports.

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_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.

ee_tl_type: the codelisted column used to define the three-line type.

ee_pull_point: the codelisted column used to define a pullbox as a cable pull point.

477
________________
EE Raceway Modeling Reference Guide - February 2003

rcp
This table defines both the columns you can annotate for raceway connect points (RCPs) and their
default column values.

Column Name Type Index Null


tag Char( 20) no yes
ee_rcp_type* integer no yes
ee_extension* real no yes
ee_transition* real no yes
ee_radius* real no yes
ee_part_key* Char( 28) no yes
ee_key* Char( 28) uniq no
ee_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 manually
placed fitting.

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.

rcp_type
This codelist table defines additional information about EE Raceway connect points (RCPs). Refer to
the section entitled Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Null


index_column* integer uniq no
index_value* Char( 20) dups yes

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
________________
Appendix C: EE Raceway Reference Database Schema Description

tl_fit_env
This table is used by the manual fitting command to determine which fitting to place at an RCP based
on the intersecting one-lines and the fitting environment rules listed in this table.

Column Name Type Index Null


ee_ol_type integer uniq no
ee_tl_type integer no no
ee_tl_subtype integer no no
ee_tl_qual integer no no
ee_num_ols integer uniq yes
ee_pln_angles Char( 40) uniq yes
ee_prp_angles Char( 40) uniq yes
ee_part_table integer no yes
ee_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 placed
at the RCP. Zero if no check is to be performed.

C: EE Databases
ee_tl_subtype: the index_column number from the three_line subtype codelist table of the fitting to be
placed 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 be
placed 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. Angles
must 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
________________
EE Raceway Modeling Reference Guide - February 2003

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 detailed
description of this table.

Column Name Type Index Null


index_column* integer uniq no
index_value* Char( 20) dups yes

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.

Column Name Type Index Null


index_column* integer uniq no
index_value* Char( 20) dups yes

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.

Column Name Type Index Null


index_column* integer uniq no
index_value* Char( 20) dups yes

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
________________
Appendix C: EE Raceway Reference Database Schema Description

to_equip
This table defines both the columns that you can annotate for equipment pointer symbols and their
default column values.

Column Name Type Index Null


ee_eqp_table Char( 32) no yes
ee_part_key Char( 28) no yes
ee_eqp_key* Char( 28) uniq no
ee_description* Char( 40) no yes

ee_eqp_table: the name of the reference database table containing the equipment specification
information.

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.

ee_description: the description of the default values for each ee_key.

to_support

C: EE Databases
This table defines both the columns you can annotate for support equipment symbols and their default
column values.

Column Name Type Index Null


tag Char( 20) no yes
ee_key* Char( 28) uniq no
ee_description* Char( 40) no yes

tag: the column used to define the support pointer tag.

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.

to_support symbols are not available with EE Raceway at the time of this printing.

481
________________
EE Raceway Modeling Reference Guide - February 2003

tray_part
This table stores the part specification information for the one-line type TRAY.

Column Name Type Index Null


ee_tl_type* integer no no
ee_tl_subtype* integer no no
ee_tl_qual* integer no no
ee_angle* real no yes
ee_weight* real no yes
ee_part* Char( 20) no yes
ee_symbol* Char( 6) no yes
ee_spec_key* Char( 28) dups yes
ee_spec2_key* Char( 28) no yes
ee_part_key* Char( 28) uniq no
ee_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.

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 specification
information.

ee_spec2_key: if the current tray part is a reducer, this column is the key to the row in the other tray
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.

482
________________
Appendix C: EE Raceway Reference Database Schema Description

tray_spec
This table stores the general specification information for the one-line type TRAY.

Column Name Type Index Null


vendor integer dups no
ee_units* integer no no
ee_dimension_1* real no yes
ee_out_ht_diam* real dups no
ee_dimension_2* real no yes
ee_out_width* real dups yes
ee_extension* real no yes
ee_transition* real no yes
ee_radius* real no yes
weight real no yes
material Char( 20) no yes
ee_const_type integer no no
ee_xs_cell* Char( 6) no yes
ee_spec_key* Char( 28) uniq no
ee_description Char( 40) no yes

vendor: the codelisted column used to define the vendor of the tray specification.

C: EE Databases
ee_units: the codelisted column used to define the units of measurement.

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.

ee_const_type: the column used to define construction type.

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 sketch
propagation. 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.

vendor
This codelist table defines the vendors that are available for specifications. Refer to the section entitled
Codelists earlier in the appendix for a detailed description of this table.

Column Name Type Index Null


index_column* integer uniq no
index_value* Char( 20) dups yes
catalog 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 Null


ee_tl_type* integer no yes
ee_tl_subtype* integer no yes
ee_tl_qual* integer no yes
ee_angle* real no yes
ee_weight* real no yes
ee_part* Char( 20) no yes
ee_symbol* Char( 6) no yes
ee_spec_key* Char( 28) dups yes
ee_spec2_key* Char( 28) no yes
ee_part_key* Char( 28) uniq no
ee_description* Char( 40) no yes

ee_tl_type: the codelisted column used to define the three-line type.

484
________________
Appendix C: EE Raceway Reference Database Schema Description

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.

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 general
specification information.

ee_spec2_key: if the current wireway part is a reducer, this column is the key to the row in the other
wireway 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.

C: EE Databases
wway_spec
This table stores the general specification information for the one-line type WIREWAY.

Column Name Type Index Null


vendor integer dups no
ee_units* integer no no
ee_dimension_1* real no yes
ee_out_ht_diam* real dups no
ee_dimension_2* real no yes
ee_out_width* real dups yes
ee_extension* real no yes
ee_transition* real no yes
ee_radius* real no yes
weight real no yes
material Char( 20) no yes
ee_const_type integer no no
ee_xs_cell* Char( 6) no yes
ee_spec_key* Char( 28) uniq no
ee_description Char( 40) no yes

vendor: the codelisted column used to define the vendor of the wireway specification.

ee_units: the codelisted column used to define the units of measurement.

ee_dimension_1: the column used to define a wireway dimension value to eden and the raceway
reports.

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 raceway
reports.

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 raceway
software.

ee_transition: the column used to define the wireway fitting transition length to the EE raceway
software.

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_const_type: the column used to define construction type.

ee_xs_cell: the column used to define the wireway cross section graphic that is used during sketch
propagation. 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.

486
________________
Appendix C: EE Raceway Project Database Schema Description

EE Raceway Project Database Schema


Description
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.

An asterisk (*) indicates that you must not modify the column name. You should not modify
those 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 Null


revision_numb Char( 3) no yes
cable_numb Char( 8) uniq yes
numb_cables integer no yes
numb_conductor Char( 5) no yes
conductor_size Char( 8) no yes

C: EE Databases
cable_type_code Char( 6) no yes
service_voltage Char( 7) no yes
undgrnd_length real no yes
abvgrnd_length real no yes
from_equi_numb Char( 15) no yes
from_detail Char( 8) no yes
not_used Char( 6) no yes
plan_assem_dwg Char( 20) no yes
to_equi_numb Char( 15) no yes
to_detail Char( 8) no yes
to_plan_drw_num Char( 20) no yes
cont_sta_type Char( 4) no yes
quan_term_kits Char( 6) no yes
ol_diagram_numb Char( 20) no yes
not_used2 Char( 8) no yes
remarks Char( 38) no yes
drawing_numb Char( 20) uniq yes
drawing_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 and
cable_numb should be unique.

488
________________
Appendix C: EE Raceway Project Database Schema Description

cndsch_spec
This table contains information about conduit schedule for underground conduit design.

Column Name Type Index Null


revision_numb Char( 2) no yes
conduit_numb Char( 10) uniq yes
conduit_for Char( 12) no yes
cnd_from_where Char( 20) no yes
cnd_to_where Char( 20) no yes
undgrnd_cnd_size Char( 6) no yes
undgrnd_cnd_type Char( 5) no yes
undgrnd_cnd_length real no yes
abvgrnd_cnd_size Char( 6) no yes
abvgrnd_cnd_type Char( 4) no yes
abvgrnd_cnd_length real no yes
cnd_detail_numb Char( 7) no yes
detail_drw_numb Char( 12) no yes
cnd_ac_dimension Char( 12) no yes
cnd_station Char( 6) no yes
pow_conduct_volt Char( 5) no yes
pow_conduct_numb integer no yes

C: EE Databases
pow_conduct_size Char( 7) no yes
pow_conduct_type Char( 4) no yes
pow_conduct_length real no yes
con_conduct_numb integer no yes
con_conduct_size Char( 7) no yes
con_conduct_type Char( 4) no yes
con_conduct_length real no yes
grnd_wire_size Char( 6) no yes
grnd_wire_type Char( 4) no yes
grnd_wire_length real no yes
ol_diagram_numb Char( 10) no yes
remarks Char( 16) no yes
drawing_numb Char( 20) uniq yes
drawing_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 and
conduit_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
________________
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 no


drawing_type* Char( 20) no no
ee_filename* Char( 80) no no
sheet* Char( 20) uniq no
load_dat