EE Raceway Modeling

Reference Guide
Document Number DPDS3-PB-200005B DPDS3-PB-200005C DPDS3-PB-200005D Version PDS 7.2 PDS 7.2 PDS 7.3 Date February 2003 February 2003 October 2004 Pages 1-594 595-643 644-679

Copyright
Copyright 1984-2004 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 law, trade secret law, and international treaty, 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) of the Contractor Rights in Technical Data clause at DFARS 252.2277013, subparagraph (b) of the Rights in Computer Software or Computer Software Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of the License clause at DFARS 252.227-7015, 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

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. Intergraph believes the information in this publication is accurate as of its publication date. The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible 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. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Trademarks
Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, and PDS are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. ISOGEN is a registered trademark of Alias Limited. Other brands and product names are trademarks of their respective owners.

_ _______________
Table of Contents
If You Need Assistance ........................................................................................................ Intergraph Directory ............................................................................................................. Preface ................................................................................................................................................. Document Purpose ................................................................................................................ Document Prerequisites / Audience ...................................................................................... Related Documents/Products ................................................................................................ About this Document ............................................................................................................ Ordering Information ............................................................................................................ Additional Information ......................................................................................................... General Conventions .................................................................................................................... Keyboard Conventions ......................................................................................................... Terminology ......................................................................................................................... 1. Introduction .................................................................................................................................. About the Reference Guide .......................................................................................................... Basic Workstation Skills .............................................................................................................. 2. Installation Instructions ................................................................................................................ Assumptions ......................................................................................................................... Overview ............................................................................................................................... Upgrading the Workstation .......................................................................................................... Installation Procedure .................................................................................................................. Databases ..................................................................................................................................... 3. Electrical Engineer (EE) Environment ......................................................................................... Using the Electrical Engineer Menus ........................................................................................... Create ........................................................................................................................................... Enter ............................................................................................................................................. Product Menu ............................................................................................................................... Copy ............................................................................................................................................. Delete ........................................................................................................................................... Archive ......................................................................................................................................... Restore ......................................................................................................................................... Database Utilities ......................................................................................................................... RIS schema utilities .............................................................................................................. Update Project Schema .........................................................................................................

Table of Contents

17 17 19 19 19 19 19 20 20 21 22 23 25 25 26 27 27 27 28 29 33 35 36 39 40 42 43 44 46 48 50 51 52

_ _______________
Update Reference Schema .................................................................................................... 4. Electrical Engineer (EE) Raceway Environment ......................................................................... Create ........................................................................................................................................... Design .......................................................................................................................................... Process ......................................................................................................................................... Overview ............................................................................................................................... Operating Modes .................................................................................................................. EDEN ........................................................................................................................................... Operating Modes .................................................................................................................. Entering Time in Batch Mode .............................................................................................. Report ........................................................................................................................................... Overview ............................................................................................................................... A Special Note for Bill of Materials by Volume .................................................................. Rule Checks ................................................................................................................................. Overview ............................................................................................................................... Utilities ......................................................................................................................................... Copy ...................................................................................................................................... Delete .................................................................................................................................... Undelete ................................................................................................................................ Purge ..................................................................................................................................... Rename ................................................................................................................................. Send ...................................................................................................................................... Receive ................................................................................................................................. Archive ................................................................................................................................. Restore .................................................................................................................................. Output ................................................................................................................................... 5. EE Graphics Interface Elements .................................................................................................. Start-up Sequence ........................................................................................................................ Screen Display ............................................................................................................................. EERWAY Command Menu Bar .................................................................................................. Palettes in the EE Raceway Graphics Environment .................................................................... Identifying Elements .................................................................................................................... Working Units and Precision Key-ins ......................................................................................... Working Units in MU:SU:PU .............................................................................................. Precision Key-ins .................................................................................................................. 55 59 61 63 64 64 65 67 68 69 70 70 72 73 73 75 78 79 80 81 82 83 84 86 87 89 91 92 93 96 97 103 104 104 105

_ _______________
6. Workflow and Procedures ............................................................................................................ The Drawing Process ................................................................................................................... System Manager Setup ......................................................................................................... Drawing Setup ...................................................................................................................... Define Systems and Set Active Systems .............................................................................. Define One-Line Type and Set Active One-Line Type ........................................................ Set Symbology ...................................................................................................................... Set Active Parameters ........................................................................................................... Set Propagation Parameters .................................................................................................. Place One-Line ..................................................................................................................... Propagation ........................................................................................................................... Sketch and Eden Modes ........................................................................................................ Manual Fitting Placement ..................................................................................................... Seamless Tubing Representations ........................................................................................ Databases ..................................................................................................................................... Reference Database ............................................................................................................... Project Database ................................................................................................................... Reports ......................................................................................................................................... Interference Detection .................................................................................................................. 7. Precision Input Form .................................................................................................................... View ...................................................................................................................................... Maximize/Minimize ............................................................................................................. Cancel ................................................................................................................................... Reject .................................................................................................................................... Accept ................................................................................................................................... Move/Move To Toggle ......................................................................................................... Display Fields ....................................................................................................................... Active Point Coordinates Display ........................................................................................ Justification Point ................................................................................................................. Height and Width .................................................................................................................. Construct Point ............................................................................................................................ Midpoint/Any Point on Segment ................................................................................................. Extend/Reduce Run ..................................................................................................................... Distance and Direction ................................................................................................................. Runtime Setup .............................................................................................................................. 8. Design Commands ....................................................................................................................... Commands ............................................................................................................................ Using the Design Commands .......................................................................................................

Table of Contents

107 108 109 110 110 110 110 111 111 112 113 113 113 114 115 115 115 117 118 119 120 120 120 120 120 121 121 121 122 122 123 123 125 126 127 129 129 131

_ _______________
When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Place One-Line ............................................................................................................................. Steps ...................................................................................................................................... Route Around Vessel ................................................................................................................... Steps ...................................................................................................................................... Insert RCP .................................................................................................................................... Steps ...................................................................................................................................... Rotate Cross Section .................................................................................................................... Steps ...................................................................................................................................... Place Drop Point .......................................................................................................................... Steps ...................................................................................................................................... Place Equipment Pointer .............................................................................................................. Steps ...................................................................................................................................... Define Active Point ...................................................................................................................... Steps ...................................................................................................................................... Set Active Parameters .................................................................................................................. Steps ...................................................................................................................................... Place Manual Fitting .................................................................................................................... Conduit Sizing ............................................................................................................................. Field Descriptions ........................................................................................... Insert One-Line Vertex ................................................................................................................ Place Field Routed Raceway ....................................................................................................... Define Duct Cross Section ........................................................................................................... Place Stub Up ............................................................................................................................... Steps ................................................................................................................ 131 131 131 131 132 134 135 136 138 138 140 140 142 142 144 144 145 145 146 146 147 155 156 160 161 164 167 169

_ _______________
9. Modify Commands ...................................................................................................................... Using the Modify Commands ...................................................................................................... When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Modify Element Commands ........................................................................................................ Using the Modify Element Commands ................................................................................ When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Annotate Element ................................................................................................................. Field Descriptions ................................................................................................................. Copy Element ....................................................................................................................... Steps ................................................................................................................ Move Element ....................................................................................................................... Steps ................................................................................................................ Clone Element ...................................................................................................................... Steps ................................................................................................................ Move One-Line Segment ...................................................................................................... Steps ................................................................................................................ Move One-Line Vertex ......................................................................................................... Propagate Element ................................................................................................................ Edit/Insert Manual Fitting ..................................................................................................... Modify One-Line .................................................................................................................. Place Fitting by Rule ............................................................................................................ Combine Coincident RCPs ................................................................................................... Delete Duplicate One-Lines .................................................................................................. Delete Element ...................................................................................................................... Remove RCP ........................................................................................................................ Delete Fitting ........................................................................................................................ Remove One-Line Vertex ..................................................................................................... Minimize Joints .................................................................................................................... Steps ................................................................................................................

Table of Contents

173 174 174 174 174 174 175 177 177 177 177 177 178 179 184 185 186 187 188 189 190 191 192 194 198 204 207 209 211 212 214 216 217 219 220

_ _______________
Change System Parameters ................................................................................................... Modify Group Commands ........................................................................................................... Topics ................................................................................................................................... Using the Modify Group Commands ................................................................................... When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Define Group ........................................................................................................................ Steps ................................................................................................................ Copy Element by Group ....................................................................................................... Annotate Element by Group ................................................................................................. Clone Element by Group ...................................................................................................... Propagate by Group .............................................................................................................. Place Fitting by Rule by Group ............................................................................................ Steps ................................................................................................................ Add Systems Group .............................................................................................................. Replace Systems by Group ................................................................................................... Minimize Joints by Group .................................................................................................... Delete Element by Group ..................................................................................................... 10. Setup Commands ....................................................................................................................... Using the Setup Commands ......................................................................................................... When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Set Raceway Defaults .................................................................................................................. Define System .............................................................................................................................. Define One-Line Type ................................................................................................................. Set Symbology Control ................................................................................................................ Steps ................................................................................................................ Symbology Control ...................................................................................................................... Set Text Defaults .......................................................................................................................... Set Conduit Sizing Attributes ...................................................................................................... Create Cell Commands ................................................................................................................ Using the Create Cell Commands ......................................................................................... When to Use These Commands ............................................................................................ 221 223 223 225 225 225 225 225 226 230 231 233 239 241 243 244 245 246 248 251 253 255 255 255 255 255 256 258 260 262 263 264 266 268 269 270 270

_ _______________
Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Create Model Cell ................................................................................................................. Create Equipment Pointer Cell ............................................................................................. Create Drop Point Cell .......................................................................................................... Model Commands ........................................................................................................................ Using the Model Commands ................................................................................................ When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Lock Model ........................................................................................................................... Move Model Annotation ....................................................................................................... Unlock Model ....................................................................................................................... Annotate Model .................................................................................................................... 11. Runtime Setup Commands ......................................................................................................... Using the Runtime Setup Commands .......................................................................................... When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Set Active One-Line Type Parameters ......................................................................................... Set Active One-Line Type ........................................................................................................... Set Active System ........................................................................................................................ Propagation Setup ........................................................................................................................ Set Active Levels ......................................................................................................................... Display Element Information ....................................................................................................... 12. Utilities Commands .................................................................................................................... Using the Utilities Commands ..................................................................................................... When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Toggle Construction Display On/Off ........................................................................................... Highlight Element by Sector/Word ............................................................................................. Highlight Sector/Word With Filename .................................................................................

Table of Contents

270 270 270 271 274 277 280 281 281 281 281 281 282 283 284 285 287 288 288 288 288 288 289 294 295 297 299 301 303 305 305 305 305 305 306 307 307

_ _______________
Highlight Element by ASID ID ................................................................................................... Highlight ASID ID With Filename ....................................................................................... Highlight Element by Link .......................................................................................................... Highlight Link With Filename .............................................................................................. Highlight Propagation Errors ....................................................................................................... Display Sector/Word Value ......................................................................................................... Display Element Type and ASID ID ........................................................................................... Display Link ................................................................................................................................. Display System and One-Line Type ............................................................................................ Active Coordinate System ........................................................................................................... 13. Database Commands .................................................................................................................. Using the Database Commands ................................................................................................... When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... Load Database .............................................................................................................................. Steps ................................................................................................................ Report ........................................................................................................................................... A Special Note for Bill of Materials by Volume .................................................................. Rule Checks ................................................................................................................................. 14. Raceway Processes ..................................................................................................................... Load Database .............................................................................................................................. Batch File Option ............................................................................................ Unload Design ............................................................................................................................. Unload Sheet ................................................................................................................................ Cleanup Database ......................................................................................................................... Create Interference Envelope (default name) .............................................................................. Create Interference Envelope (given name) ................................................................................. 15. Eden Processes ........................................................................................................................... Compile EDEN Symbol ............................................................................................................... Delete EDEN Symbol .................................................................................................................. 309 309 312 312 314 315 316 317 318 320 321 322 322 322 322 322 323 325 326 327 329 331 332 335 336 338 340 342 344 347 349 351

10

_ _______________
Steps ................................................................................................................ List EDEN Symbol Library ......................................................................................................... Steps ................................................................................................................ List EDEN User Functions .......................................................................................................... Merge EDEN Symbol Libraries ................................................................................................... Compress EDEN Symbol Library ............................................................................................... Extract EDEN Symbol From Library .......................................................................................... Steps ................................................................................................................ Extract EDEN User Function From Library ................................................................................ Edit EDEN Symbol File .............................................................................................................. Steps ................................................................................................................ 16. Integrated Commands ................................................................................................................ Using the Integrated Commands .................................................................................................. When to Use These Commands ............................................................................................ Before Using These Commands ........................................................................................... Group Workflow ................................................................................................................... Operating Information .......................................................................................................... 16.1 Review PDS Attributes ............................................................................................................ Parameters ............................................................................................................................. 16.2 Reference PDS Model .............................................................................................................. Parameters ............................................................................................................................. 16.3 Window to Named PDS Item ................................................................................................... Options .................................................................................................................................. 16.4 Review PDS Clash ................................................................................................................... Parameters ............................................................................................................................. Appendix A: Appendix B: Error Messages ........................................................................................................... System/Application Manager Information .................................................................

Table of Contents

352 353 354 355 357 359 361 362 363 366 367 369 370 370 370 370 370 371 371 372 372 374 374 375 375 377 415 417 422

Customizing ................................................................................................................................. EE Environment Variables ..........................................................................................................

11

_ _______________
Appendix C: EE Databases .............................................................................................................. 425 426 427 427 428 430 430 430 432 432 433 433 433 434 435 435 436 437 437 438 438 439 440 440 441 443 444 445 446 448 449 449 449 450 451 454 454 454 455 456 457 458 Relational Interface System (RIS) ............................................................................................... Database and RIS Procedures ...................................................................................................... For New Users ...................................................................................................................... Update Schema (create_db) Process ............................................................................................ Reference Schema - General Description .................................................................................... Default Attributes ................................................................................................................. Keys ...................................................................................................................................... Codelists ............................................................................................................................... Approval Status Codelist Table ............................................................................................ Cardinal Codelist Table ........................................................................................................ Drawing Type Codelist Table ............................................................................................... Manual Fitting Part Codelist Table ....................................................................................... One-Line Type Codelist Table ............................................................................................. RCP Type Codelist Table ..................................................................................................... System Codelist Table .......................................................................................................... Three-Line Type Codelist Table ........................................................................................... Three_Line Subtype Codelist Table ..................................................................................... Three-Line Qualifier Codelist Table ..................................................................................... Units Codelist Table ............................................................................................................. Vendor Codelist Table .......................................................................................................... Wire/Cable Code Codelist Table .......................................................................................... Wire/Cable Configuration Codelist Table ............................................................................ Wire/Cable Size Codelist Table ............................................................................................ Wire/Cable Color Codelist Table ......................................................................................... Wire/Cable Voltage Codelist Table ...................................................................................... Wire/Cable Insulation Type Codelist Table ......................................................................... Yes-No Codelist Table ......................................................................................................... Fitting Environment Rules .................................................................................................... Project Schema - General Description ......................................................................................... Updating Schemas ....................................................................................................................... Updating a Project Schema ................................................................................................... Updating Reference Schemas ............................................................................................... Schema Names ...................................................................................................................... Modifying the Reference Schema ................................................................................................ EE Raceway Reference Database Schema Description ............................................................... approv_status ........................................................................................................................ away_part .............................................................................................................................. away_spec ............................................................................................................................. cardinal ................................................................................................................................. cond_body ............................................................................................................................. cond_fill_calc .......................................................................................................................

12

_ _______________
cond_part .............................................................................................................................. cond_spec ............................................................................................................................. drawing ................................................................................................................................. drawing_type ........................................................................................................................ drop_point ............................................................................................................................. duct_spec .............................................................................................................................. ee_cond_x_area .................................................................................................................... ee_graphic_only .................................................................................................................... ee_pcbl_code ........................................................................................................................ ee_pcbl_color ........................................................................................................................ ee_pcbl_config ...................................................................................................................... ee_pcbl_insul ........................................................................................................................ ee_pcbl_size .......................................................................................................................... ee_pcbl_volt .......................................................................................................................... ee_pseudo_cable ................................................................................................................... ee_system .............................................................................................................................. ee_units ................................................................................................................................. ee_unique .............................................................................................................................. ee_yes_no ............................................................................................................................. envelope ................................................................................................................................ light_fixture .......................................................................................................................... manual_part .......................................................................................................................... mscatalog .............................................................................................................................. mscodelist ............................................................................................................................. mscolumns ............................................................................................................................ ol_type .................................................................................................................................. one_line ................................................................................................................................. panel ...................................................................................................................................... project ................................................................................................................................... pullbox .................................................................................................................................. rcp ......................................................................................................................................... rcp_type ................................................................................................................................ tl_fit_env ............................................................................................................................... tl_qual ................................................................................................................................... tl_subtype .............................................................................................................................. tl_type ................................................................................................................................... to_equip ................................................................................................................................ to_support ............................................................................................................................. tray_part ................................................................................................................................ tray_spec ............................................................................................................................... vendor ................................................................................................................................... wway_part ............................................................................................................................. wway_spec ............................................................................................................................ EE Raceway Project Database Schema Description .................................................................... cabsch_spec .......................................................................................................................... cndsch_spec .......................................................................................................................... drawing ................................................................................................................................. drop_point .............................................................................................................................

Table of Contents

459 460 461 461 462 462 463 463 464 464 464 465 465 465 466 466 467 467 467 468 469 471 471 472 473 474 475 475 476 477 478 478 479 480 480 480 481 481 482 483 484 484 485 487 487 489 491 491

13

_ _______________
duct_fill ................................................................................................................................. ee_pseudo_cable ................................................................................................................... ee_system .............................................................................................................................. envelope ................................................................................................................................ fitting ..................................................................................................................................... fit_to_sys ............................................................................................................................... mscatalog .............................................................................................................................. mscolumns ............................................................................................................................ ol_to_sys ............................................................................................................................... one_line ................................................................................................................................. panel ...................................................................................................................................... project ................................................................................................................................... panel_to_drw ........................................................................................................................ rcp ......................................................................................................................................... rcp_to_drw ............................................................................................................................ rcp_to_sys ............................................................................................................................. straight .................................................................................................................................. str_to_sys .............................................................................................................................. sys_to_drw ............................................................................................................................ to_support ............................................................................................................................. Appendix D: Specification ............................................................................................................... 492 492 493 493 494 495 496 497 498 498 500 500 501 501 502 502 503 504 505 505 507 507 509 510 512 513 513 519 520 524 531 531 533 534 535 536 537

Preparing the Specifications ........................................................................................................ Sample .unl Files .................................................................................................... Update Reference Schema ........................................................................................................... Available Fittings .................................................................................................................. Appendix E: Eden Symbol Generation ............................................................................................

Symbol Processor File .......................................................................................................... Appendix F: EE File Structure .........................................................................................................

EE Nucleus File Structure ............................................................................................................ EE Raceway File Structure .......................................................................................................... Appendix G: Customizing Environment Files .................................................................................

eden.dat ........................................................................................................................................ process.dat .................................................................................................................................... report.dat ...................................................................................................................................... rule_chk.dat .................................................................................................................................. print.dat ........................................................................................................................................ manager.dat ..................................................................................................................................

14

_ _______________
Appendix H: alias.cmd file .............................................................................................................. Appendix I: rway.cmd ...................................................................................................................... Appendix J: Reports ......................................................................................................................... RIS Report Processing .......................................................................................................... Project Drawing List (drwlst) ...................................................................................................... Information Output: .............................................................................................................. Sorted by (Highest to lowest priority) .................................................................................. Associated Software/Files .................................................................................................... Material Takeoff Report (mto_rpt) .............................................................................................. Information Output: .............................................................................................................. Associated Software/Files .................................................................................................... Raceway Bill of Materials Report (rway_bom) ........................................................................... Information Output: .............................................................................................................. Associated Software/Files .................................................................................................... Raceway Bill of Materials by Volume Report (rway_bom_vol) ................................................. A Special Note for Bill of Materials by Volume .................................................................. Information Output: .............................................................................................................. Associated Software/Files .................................................................................................... Raceway Blank Part IDs (blank_ids) ........................................................................................... Information Output: .............................................................................................................. Associated Software/Files .................................................................................................... Appendix K: RIS Schema Manager .................................................................................................

Table of Contents

539 543 545 545 547 547 547 547 548 548 548 549 549 549 550 550 551 551 552 552 552 553 554 555 556 556 557 557 558 559 559 560 560

Schema Information Form ........................................................................................................... Create Schema Form .................................................................................................................... Drop Schema Form ...................................................................................................................... Alter Schema Form ...................................................................................................................... Data Definition Form ................................................................................................................... Table Information Form ....................................................................................................... Create Table Form ................................................................................................................ Drop Table Form .................................................................................................................. Alter Table Form .................................................................................................................. Schema File Form ........................................................................................................................ Set Form .......................................................................................................................................

15

_ _______________
Appendix L: Appendix M: RIS Schema Definition File ........................................................................................ EE Manager ............................................................................................................... 561 565 566 567 571 573 581 In this Appendix ................................................................................................................... Database Edit Functions .............................................................................................................. Appendix N: EE Configure ..............................................................................................................

Glossary ............................................................................................................................................... Index ....................................................................................................................................................

16

_ _______________
If You Need Assistance
Intergraph Online
Our web site brings you fast, convenient, up-to-the-minute information about Intergraphs products, services, and direction. Our web address is: http://www.intergraph.com.

Table of Contents

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 upto-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
Document Purpose

Preface

This document is a reference guide for Intergraph Corporations 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 Users Guide Intergraph Corporations 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 Section 2 Sections 3 & 4 Provides an overview of the product and the document. Provides installation instructions. Describe the product environment. This includes information on accessing the product and creating and manipulating product files. Describes the graphics environment for the product. This includes information on the screen display, menus, forms, and on-line Help. Describes the typical workflow using EE Raceway. Describe the command groups and operating sequences of each command within the command groups.

Section 5

Section 6 Sections 7-16

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 readme.txt Contents 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

_ _______________
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.

Preface

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> <D> <R> <T> Command button Data button (usually the left mouse button) Reset/reject button (usually the right mouse button) 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 CTRL DEL ENTER ESC CTRL+z ESC,k Alternate key Control key Delete key Enter key Escape key To hold down the Control key and press Z. To press the Escape key, then K.

22

_ _______________
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. 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. To key a character string into a text box. 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.

Preface

Double-click

Type Key in

23

_ _______________
EE Raceway Modeling Reference Guide - February 2003

24

_ _______________
1. Introduction
EE Raceway allows you to design, modify, and model electrical raceway systems in a threedimensional 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.

Introduction

1. Introduction

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

_ _______________
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.

Installation Instructions

Assumptions
The following assumptions have been made in the writing of this section. You must be familiar with the PDS Loader. You must be familiar with a text editor, such as vi, EMACS, or Notepad. If you are updating, all projects have been archived. Products will be used with any one of the following databases: Standard Engine (SE) Informix, On-line Informix, Oracle, or Ingres. You will need to consult individual documentation for these products for detailed information.

2. Download/Install

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
This sections 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. Double-click on setup.exe to invoke the Intergraph PDS Component Loader.

Installation Procedure

2.

2. Download/Install

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. Select Continue when the button is no longer inactive. This will invoke the product selection form.

4.

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

2. Download/Install

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

Databases

2. Download/Install

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

_ _______________
3. Electrical Engineer (EE) Environment

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:

3. EE Environment

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

_ _______________
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.

Using the Electrical Engineer Menus

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.

3. EE Environment

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

Create

3. EE Environment

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. 3. Select the Project name field, and key in the new project name. 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

_ _______________
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.

Enter

Password Echo This toggle controls whether or not the password is displayed in the respective password fields.

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

3. EE Environment

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 products 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
This option copies all the files within an existing project to a new project.

Copy

Field Descriptions
Copy project from Key in the source project name (or select it from the list). Copy project to Key in the destination project name; this cannot be the name of a project that already exists.

3. EE Environment

Steps
1. 2. Select Copy from the Project Menu option list. 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. 2. Select Delete from the Project Menu option list. 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.

3. EE Environment

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

_ _______________
Steps
1. 2. Select Archive from the Project Menu option list. 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 users .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. 4. Select Confirm ( ) to begin archiving. OR Select another option to ignore your input and cancel the Archive process.

Archive

3. EE Environment

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

_ _______________
Steps
1. 2. 3. Select Restore from the Project Menu. Select the Project name field, and key in a project name. 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.

Restore

3. EE Environment

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

RIS schema utilities

3. EE Environment

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

_ _______________
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 .

Update Project Schema

Steps
3. EE Environment
1. Select the Update project schema option from the Database Utilities form. The Update project schema form displays: 2. 3. Set up the form to meet your specifications. 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 projects /tmp directory, using the Output option on the Utilities form. For more information, see Output, page 89 . 5. 6. Select Reset on the message file form to return to the Update project schema form. Select Reset again to exit the process and return to the Database Utilities form.

54

_ _______________
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 .

Update Reference Schema

Field Descriptions
Output file Defines the processing message file name. Error file Defines the error processing message file name. Schema name Defines the reference databases 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. 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 .

3. EE Environment

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. 3. Set up the form to meet your specifications. 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 projects /tmp directory, using the Output option on the Utilities form. For more information, see Output, page 89 . 5. 6. Select Reset on the message file form to return to the Update reference schema form. Select Reset again to exit the process and return to the Database Utilities form.

3. EE Environment

57

_ _______________
EE Raceway Modeling Reference Guide - February 2003

58

_ _______________
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

Electrical Engineer (EE) Raceway Environment

The EE Raceway Design Menu.

4. EERWAY Environment

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
This option creates design files, based on a specified seed file.

Create

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.

4. EERWAY Environment

Steps
1. Select Create from the Design Menu. If there is only one seed file, it is displayed as the default. If there is more than 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. 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. 4.

62

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

Design

Steps
1. 2. 3. Select Design from the Design Menu. Select the drawing name from the listing area. Select Confirm ( ). The system invokes the graphics environment. OR Select another option from the Design Menu to ignore your input and cancel the Design process.

4. EERWAY Environment

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

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

Process

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

4. EERWAY Environment

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. 2. 3. Select Process from the Design Menu. Select a process from the listing area. 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
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.

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.

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

4. EERWAY Environment

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

_ _______________
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.

EDEN

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

4. EERWAY Environment

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

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

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. 2. 3. Select Report from the Design Menu. Select a report from the listing area. 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.

4. EERWAY Environment

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

4. EERWAY Environment

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. 2. 3. Select Rule from the Design Menu. Select a rule check report from the listing area. 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 projects directories.

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

4. EERWAY Environment
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. 2. Select Utilities from the Design Menu. Select the desired option from the Drawing Utility Menu, and then select the file(s) on which to perform that option. Enter necessary form information for the active option.

3.

76

_ _______________
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.

Utilities

4. EERWAY Environment

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.

4. EERWAY Environment

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
This option permanently removes all the files you marked for deletion using the Delete option. Once you Purge a file, you cannot recover it.

Purge

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.

4. EERWAY Environment

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

Send

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

4. EERWAY Environment

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

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

Receive

4. EERWAY Environment

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

Restore

Field Descriptions
4. EERWAY Environment
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
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.

Output

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

_ _______________
5. EE Graphics Interface Elements

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.

5. EERWAY Graphics

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
The screen display you will see when you enter a design file is described below.

Screen Display

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:

5. EERWAY Graphics

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. Working Area - displays elements as you place them. All your design work occurs in the screen working area. 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.

3.

4.

94

_ _______________
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. 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.

Screen Display

5. EERWAY Graphics

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

Palettes in the EE Raceway Graphics Environment

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.

5. EERWAY Graphics

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

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

Palettes in the EE Raceway Graphics Environment

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

5. EERWAY Graphics

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

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

Palettes in the EE Raceway Graphics Environment

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

5. EERWAY Graphics

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

Identifying Elements

5. EERWAY Graphics

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 1 Master Unit 1 Subunit 1 Positional Unit Imperial 1 foot = 12 subunits 1 inch = 8000 positional units 1/8000 inch Metric 1 meter = 1000 subunits 1 millimeter = 10 positional units 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

_ _______________
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)

Working Units and Precision Key-ins

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.

5. EERWAY Graphics

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

_ _______________
6. Workflow and Procedures

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 threedimensional 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 designs 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

_ _______________
Set Active Parameters

Drawing Setup

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
A one-dimensional raceway is composed of one-line segments. To convert this onedimensional 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 elements 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.

Propagation

6. Workflow

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

Databases

6. Workflow

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 (onelines, 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

_ _______________
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.

Precision Input Form

7. Precision Input

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

_ _______________
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.

Precision Input Form

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.

7. Precision Input

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 elements dimensions during placement.

122

_ _______________
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 nonorthogonally. 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.

Construct Point

Midpoint/Any Point on Segment

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 segments endpoints. OR Press <R> to reject the segment, and return to the previous step to identify another one-line.

7. Precision Input

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

7. Precision Input

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

7. Precision Input

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

_ _______________
8. Design Commands

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

8. Design

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
When to Use These Commands
Once you have performed the necessary setups, you can use these commands throughout the design session.

Using the Design Commands

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 oneline 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. 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 oneline, 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.

8. Design

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

3.

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

_ _______________
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.

Route Around Vessel

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

_ _______________
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.

Insert RCP

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

_ _______________
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. 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.

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.

8. Design

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

_ _______________
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 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.

Place Drop Point

8. Design

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. 2. Select the Place Equipment Pointer command. 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
This command defines a new active point in your design file.

Define Active Point

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
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 system derives the default orientation for placing the new fitting from the placement point.

Place Manual Fitting

8. Design

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

_ _______________
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.

Place Manual Fitting

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

8. Design

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

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

Place Manual 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 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 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.

8. Design

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

_ _______________
Before Using This Command
You should be familiar with precision input and its functions. For more information, see Precision Input Form, page 119 .

Place Manual Fitting

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 straight elbow wye cross dropout Special Parts pullbox conduit body light fixture

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. Select Accept to accept the fitting with the current settings, orientation, and location. The system accepts the fitting at the specified location and orientation.

4.

153

_ _______________
EE Raceway Modeling Reference Guide - February 2003 5. Continue placing manual fittings. OR Exit the command.

154

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

Conduit Sizing

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 Type numeric Description

equal to

This is the default operator. If you do not enter another operator, the system assumes =. This operator indicates that the queried values should be greater than the given value. This operator indicates that the queried values should be less than the given value. This operator indicates that the queried values should be greater than or equal to the given value. This operator indicates that the queried values should be less than or equal to the given value. This operator indicates that the queried values should NOT be equal to the given value. 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. 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.

>

greater than

numeric

<

less than

numeric

>=

greater than or equal to less than or equal to not equal to

numeric

<=

numeric

!=

numeric

wild card

CHAR

underline

CHAR

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

_ _______________
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 PseudoCable form displays, from which you can select a cable or cables to route in the conduit.

Field Descriptions

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. 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 conduits cross-sectional area divided by the summation of all of that conduits 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.

8. Design

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. Set the Increase size ONLY / Increase/Decrease size toggle to the sizing method you want.

4.

158

_ _______________
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.

Field Descriptions

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

Place Field Routed Raceway

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

_ _______________
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.

Place Field Routed Raceway

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 banks 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 banks cross section. Unassigned or unused buttons in the matrix are not used in calculating the ductbanks 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

_ _______________
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.

Define Duct Cross Section

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

8. Design

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. 4. Define cross section layout using the various commands. 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 ductbanks 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 banks 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
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.

Steps

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-lines 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 RCPs 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

_ _______________
Select a button from the Button Matrix. 13. Stub up spec. has been changed. Go to Step 2. 14. 15. Select the Place Stub Up option. 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. 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.

Steps

8. Design

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

_ _______________
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.

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

Modify Element Commands

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 onelines in your raceway model. Do not use MicroStation commands to manipulate or modify EE Raceway elements (oneline, 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 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.

Using the Modify Element Commands

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

Field Descriptions

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

9. Modify

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

_ _______________
This command accepts certain relational operators as search criteria. You should be familiar with the following operators: Symbol Name Data Type numeric Description = equal to This is the default operator. If you do not enter another operator, the system assumes =. This operator indicates that the queried values should be greater than the given value. This operator indicates that the queried values should be less than the given value. This operator indicates that the queried values should be greater than or equal to the given value. This operator indicates that the queried values should be less than or equal to the given value. This operator indicates that the queried values should NOT be equal to the given value. 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. 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.

Field Descriptions

>

greater than

numeric

<

less than

numeric

>=

greater than or equal to less than or equal to not equal to

numeric

<=

numeric

!=

numeric

wild card

CHAR

underline

CHAR

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.

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. 5. Set up the form parameters to meet your specifications. 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

_ _______________
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.

Field Descriptions

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

Steps

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

Steps

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
1. 2. Select the Clone Element command. 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 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.

Steps

9. Modify

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
1. 2. Select the Move One-Line Segment command. 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.

Steps

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. 2. Select the Move One-Line Vertex command. 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

_ _______________
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.

Move One-Line Vertex

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

_ _______________
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.

Propagate Element

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

_ _______________
Conduit Fittings

Propagate Element

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

_ _______________
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.

Edit/Insert Manual Fitting

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 rows 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 onelines 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

_ _______________
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.)

Edit/Insert Manual Fitting

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

9. Modify

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 straight elbow wye cross dropout Special Parts pullbox conduit body light fixture

202

_ _______________
Steps
1. 2. Select the Edit/Insert Manual Fitting command. 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.

Edit/Insert Manual Fitting

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

_ _______________
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 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.

Modify One-Line

9. Modify

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

Place Fitting by 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. 2. Select the Place Fitting by Rule command. Identify Raceway Fitting or RCP Select the RCP on which you want to place the fitting. If no rule is defined for the selected RCPs 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.

9. Modify

Each set of coincident RCPs is listed in the form separated by the horizontal dotted line. Combine Merges the coincident RCPs into one RCP. One-Line Type Displays which one-line type each RCP belongs to. Systems Displays which system each RCP belongs to. Status Defines if the RCPs can be merged. If Combinable, then the 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. Choose which RCP in the set of RCPs you want to keep and leave that line highlighted. 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. 3. 4.

210

_ _______________
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.

Delete Duplicate One-Lines

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. Choose which one-line out of each set you want to keep. The Status of the one-line you chose changes to Save. 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.

9. Modify

3.

4.

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

_ _______________
OR Press <R> to exit the command. 3. Raceway [element] Accept/reject Press <D> to accept the element for deletion.

Delete Element

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

_ _______________
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.

Remove RCP

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. 2. Select the Delete Fitting command. Identify Raceway Fitting or RCP Select the fitting, or the fittings 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
This command deletes an internal one-line vertex. You can not delete the end points of the one-line using this command.

Remove One-Line 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.

9. Modify

Steps
1. 2. Select the Remove One-Line Vertex command. 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
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 oneline. (Automatic propagation is on to show the resulting seamless representation.)

Minimize Joints

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.

9. Modify

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
This command changes the system parameters, the system Percent and the Project Rule, for the systems associated with a single raceway element.

Change System Parameters

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 schemas 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 raceways 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. 5. Set up the form parameters to meet your specifications. 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
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.

Modify Group Commands

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

Using the Modify Group Commands

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 oneline 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 using other Modify Group commands.

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.

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

_ _______________
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.

Define Group

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

9. Modify

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, onelines, 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

_ _______________
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.

Define Group

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. Select one of the group modification commands.

4.

230

_ _______________
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.

Copy Element by 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
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.

Annotate Element by Group

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

_ _______________
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 rows values. If more than one row matches the criteria, then a second form containing all matching rows displays.

Annotate Element by Group

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

9. Modify

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 Types numeric Description = equal to This is the default operator. If you do not enter another operator, the system assumes =. This operator indicates that the queried values should be greater than the given value. This operator indicates that the queried values should be less than the given value. This operator indicates that the queried values should be greater than or equal to the given value. This operator indicates that the queried values should be less than or equal to the given value. This operator indicates that the queried values should NOT be equal to the given value. 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. 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.

>

greater than

numeric

<

less than

numeric

>=

greater than or equal to less than or equal to not equal to

numeric

<=

numeric

!=

numeric

wild card

CHAR

underline

CHAR

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

_ _______________
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

Annotate Element by Group

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. 5. Set up the form parameters to meet your specifications. 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
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.

Clone Element by 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
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 .

Propagate by 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. You can set active parameters for propagation through the Propagation Setup form. For information about the form, see Propagation Setup, page 297 .

9. Modify

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

Place Fitting by Rule by 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.

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

Add Systems Group

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

9. Modify

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 schemas "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 raceways width assigned to that system. This Percent is used when calculating the cable fill of the raceway section in the EECMS product.

246

_ _______________
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 *.

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.

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 oneline. (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

_ _______________
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.

Minimize Joints by Group

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
This command deletes all or selected valid elements in an active group from the design file.

Delete Element by 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 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

_ _______________
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.

Setup Commands

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

10. Setup

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

Using the Setup Commands

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

_ _______________
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.

Set Raceway Defaults

Steps
1. Select the Set Raceway Defaults command. The EE Raceway Defaults form displays. 2. 3. Set up the form parameters to meet your requirements. 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

_ _______________
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.

Define System

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

_ _______________
3. Select Confirm ( ) to save your changes and exit the command. OR Select Cancel (X) to exit the command without saving your changes.

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.

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

Steps

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

_ _______________
Steps
1. Select the Symbology Control command. The Symbology Control form displays. 2. 3. Set up the form parameters to meet your requirements. Select Confirm ( ) to save your changes and exit the command. OR Select Cancel (X) to exit the command without saving your changes.

Symbology Control

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

_ _______________
Engineering Units These fields (Master units, Sub units, and Positional units) display the current PDS engineering units. You can only review the displayed settings.

Set Text Defaults

Steps
1. Select the Set Text Defaults command. The Text form displays. 2. 3. Set up the form parameters to meet your requirements. 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
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 nonproduction 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.

Create Cell Commands

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

Create Model Cell

This command allows you to create a model cell and to store that cell permanently in your cell library.

Steps
1. Select the Create Cell command. The Select cell type form displays.

2. 3.

Select the Model button from the form. 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

_ _______________
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.

Create Model Cell

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 ( ). 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.

12.

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

Select the To Equipment button from the form. 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

_ _______________
6. When you accept the fence, a form displays prompting you to Close or Annotate.

Create Equipment Pointer Cell

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 ( ). 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.

12.

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 onelines 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. 3.

Select the Drop Point button from the form. 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

_ _______________
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.

Create Drop Point Cell

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 ( ). 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.

12.

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

Using the Model Commands

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
This command moves the model annotation within a design.

Move Model 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 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. 2. Select the Unlock Model command. 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

_ _______________
11. Runtime Setup Commands
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.

Runtime Setup Commands

11. Runtime

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

Set Active One-Line Type Parameters

11. Runtime

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

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

Set Active One-Line Type Parameters

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 Type numeric Description = equal to This is the default operator. If you do not enter another operator, the system assumes =. This operator indicates that the queried values should be greater than the given value. This operator indicates that the queried values should be less than the given value. This operator indicates that the queried values should be greater than or equal to the given value. This operator indicates that the queried values should be less than or equal to the given value. This operator indicates that the queried values should NOT be equal to the given value. 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. 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.

>

greater than

numeric

<

less than

numeric

>=

greater than or equal to less than or equal to not equal to

numeric

<=

numeric

!=

numeric

wild card

CHAR

underline

CHAR

Steps
1. Select the Set Active One-Line Type Parameters command. An Active One-Line Type Parameters form displays. 2. 3. Set up the form parameters to meet your requirements. Select Confirm ( ) to save your changes and exit the command. OR Select Cancel (X) to exit the command without saving your changes.

292

_ _______________
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.

Set Active One-Line Type Parameters

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

Set Active System

11. Runtime

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 schemas 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 raceways 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. Define the percentages and the project rules you want to use. Select Confirm ( ) to save your changes and exit the command. OR Select Cancel (X) to exit the command without saving your changes.

3. 4.

296

_ _______________
Propagation Setup
This command sets the active parameters for propagating one-line elements in the design file. For additional information about propagation, see The Drawing Process, page 108 .

Propagation Setup

11. Runtime

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. 3. Define the form parameters to meet your specifications. 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
This command displays the current active level(s) and allows you both to turn off any active levels and to activate new levels.

Set Active Levels

11. Runtime

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 oneline 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. 3. Set up the form parameters to meet your requirements. 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
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.

Display Element Information

11. Runtime

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. 2. Select the Display Element Information command. 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 elements 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

_ _______________
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.

Utilities Commands

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
When to Use These Commands
Once you have performed the necessary setups, you can use these commands throughout the design session.

Using the Utilities Commands

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
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 Element by Sector/Word

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. 2. Select the Highlight Element By Sector/Word command. 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 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.

12. Utilities

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

_ _______________
Select a line that contains an ASID ID. 7. 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.

Highlight Element by ASID ID

After you select a line, select Confirm ( ) to accept the ASID ID in the line. Go to step 8.

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. 2. Select the Highlight Element By Link command. 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

_ _______________
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

Highlight Element by Link

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
This command displays the sector and word position, in the MicroStation command window, of an identified element.

Display Sector/Word Value

Steps
1. 2. Select the Display Sector/Word command. 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.

12. Utilities

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. 2. Select the Display Element Type and ASID ID command. 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
This command displays the entity (table) and mslink, in the MicroStation command window, of an identified element.

Display Link

Steps
1. 2. Select the Display Link command. 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.

12. Utilities

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

_ _______________
3. Raceway [element] Accept/reject Accept the highlighted element. The fields on the form fill with information about the elements one-line type, system, and subsystems (if applicable). The system prompts you to identify another element.

Display System and One-Line Type

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

_ _______________
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.

Database Commands

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
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 RCPs and segments must have a tag number before using this command.

Load Database

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 rcp_to_drw Column Name pds_east* Comments The PDS east coordinate of the corresponding RCPs origin. The PDS north coordinate of the corresponding RCPs origin. The PDS elevation coordinate of the corresponding RCPs origin. Indicates what portion of the corresponding RCP is set aside for the corresponding system. The distance down the one-line to the point on the one-line closest to the drop point origin. The orthogonal distance from the drop point origin to the RCPs origin, and the orthogonal distance from the drop point origin to the closest point on the oneline. The total graphical length of the one-line in master units. Indicates what portion of the corresponding one-line is set aside for the corresponding system.

13. Database

rcp_to_drw

pds_north*

rcp_to_drw

pds_elev*

rcp_to_sys

ee_percent***

drop_point

ee_dist_down_ol**

drop_point

ee_dist_to_rcp**

one_line

ee_ol_length**

ol_to_sys

ee_percent***

323

_ _______________
EE Raceway Modeling Reference Guide - February 2003 straight straight ee_tl_length pds_east* The graphical length of the straight in master units. The PDS east coordinate of the center point of the straights range. The PDS north coordinate of the center point of the straights range. The PDS elevation coordinate of the center point of the straights range. Indicates what portion of the corresponding straight is set aside for the corresponding system. The PDS east coordinate of the center point of the fittings range. The PDS north coordinate of the center point of the fittings range. The PDS elevation coordinate of the center point of the fittings range. Indicates what portion of the corresponding fitting is set aside for the corresponding system. straight pds_north*

straight

pds_elev*

str_to_sys

ee_percent***

fitting

pds_east*

fitting

pds_north*

fitting

pds_elev*

fit_to_sys

ee_percent***

* 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
1. Select Load database command. The Load database screen displays.

Steps

2.

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.

13. Database

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

_ _______________
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.

Report

Steps
1. 2. 3. 4. Select the Report command. Select the report you want to run from the list. Select Confirm ( ) to invoke the input form for the specified process. 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 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.

13. Database

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. 2. 3. 4. Select the Rule command. Select the rule check report you want to run from the listing area. Select Confirm ( ) to invoke the input form for the specified process. Define the input form as needed and select Confirm ( ) to process the rule check report.

330

_ _______________
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:

Raceway Processes

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 projects ../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.

14. EERWAY Processes

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

2.

This process calculates the following values: Table Name rcp_to_drw rcp_to_drw rcp_to_drw rcp_to_sys drop_point drop_point Column Name pds_east* pds_north* pds_elev* ee_percent*** ee_dist_down_ol** ee_dist_to_rcp** Comments The PDS east coordinate of the corresponding RCPs origin. The PDS north coordinate of the corresponding RCPs origin. The PDS elevation coordinate of the corresponding RCPs origin. Indicates what portion of the corresponding RCP is set aside for the corresponding system. The distance down the one-line to the point on the one-line closest to the drop point origin. The orthogonal distance from the drop point origin to the RCPs origin, and the orthogonal distance from the drop point origin to the closest point on the oneline. The total graphical length of the one-line in master units. Indicates what portion of the corresponding one-line is set aside for the corresponding system. The graphical length of the straight in master units. The PDS east coordinate of the center point of the straights range. The PDS north coordinate of the center point of the straights range. The PDS elevation coordinate of the center point of the straights range.

one_line ol_to_sys straight straight straight straight

ee_ol_length** ee_percent*** ee_tl_length pds_east* pds_north* pds_elev*

332

_ _______________
str_to_sys fitting fitting fitting fit_to_sys ee_percent*** pds_east* pds_north* pds_elev* ee_percent***

Load Database

Indicates what portion of the corresponding straight is set aside for the corresponding system. The PDS east coordinate of the center point of the fittings range. The PDS north coordinate of the center point of the fittings range. The PDS elevation coordinate of the center point of the fittings range. 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.

14. EERWAY Processes

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

Batch File Option

SET SET SET SET SET SET

MS=D:\WIN32APP\USTATION MS_EXE=D:\WIN32APP\USTATION EES_REFDB=CERT60_REF EE_SCHEMA=CERT60_PRJ EERD_MSGS=D:\WIN32APP\INGR\EERWAY\MSG\ EERD_TBLS=D:\WIN32APP\INGR\EERWAY\MSG\

14. EERWAY Processes

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

_ _______________
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.

Unload Design

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.

14. EERWAY Processes

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

Key in a sheet name. 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

_ _______________
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.

Unload Sheet

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.

14. EERWAY Processes

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), onelines, 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

_ _______________
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.

Cleanup Database

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.

14. EERWAY Processes

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

_ _______________
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.

Create Interference Envelope (default name)

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.

14. EERWAY Processes

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. 4. Key in a name for the envelope file. 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

_ _______________
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.

Create Interference Envelope (given name)

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.

14. EERWAY Processes

345

_ _______________
EE Raceway Modeling Reference Guide - February 2003

346

_ _______________
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.

Eden Processes

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

15. Eden Processes

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
This process compiles an Eden symbol file, and gives you the option of placing the compiled symbol in an Eden symbol library.

Compile EDEN Symbol

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.

15. Eden Processes

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. 3. Set up the form parameters to meet your specifications. 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
This process deletes an Eden symbol from the Eden symbol library.

Delete EDEN Symbol

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.

15. Eden Processes

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. 3. Set up the form parameters to meet your specifications. 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
This process lists the Eden symbols in the selected Eden library.

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

15. Eden Processes

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. 3. Set up the form parameters to meet you specifications. 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
This process lists the Eden user functions in the selected Eden library.

List EDEN User Functions

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. 3. Set up the form parameters to meet you specifications.

15. Eden Processes

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
This process merges two Eden symbol libraries into one.

Merge EDEN Symbol Libraries

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.

15. Eden Processes

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
This process compresses the selected Eden symbol library. Compressing the library removes the unused space left by deleted symbols.

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

15. Eden Processes

2. 3.

Set up the form parameters to meet your specifications. 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
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.

Extract EDEN Symbol From 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 extract from the library. To enter the symbol name, select the field, and key in the name.

15. Eden Processes

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. 3. Set up the form parameters to meet your specifications. 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 from the library. To enter the user function name, select the field, and key in the name.

15. Eden Processes

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. 3. Set up the form parameters to meet your specifications. 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

_ _______________
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.

Extract EDEN User Function From Library

15. Eden Processes

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
1. Select Edit EDEN Symbol File from the list, and select Confirm ( ). The Edit EDEN Symbol File form displays: 2. 3. Set up the form parameters to meet your specifications. 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.

Steps

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.

15. Eden Processes

367

_ _______________
EE Raceway Modeling Reference Guide - February 2003

368

_ _______________
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 elements 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.

Integrated Commands

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.

16. Integrated Commands

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

_ _______________
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.

Review PDS Attributes

Parameters
Attribute Name Lists the items attributes. Value Displays the items attribute value that is defined in the database. Close Exits the Review PDS Attributes dialog box.

16. Integrated Commands

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

_ _______________
Show Attachments Displays all reference models attached to the active model. Exit Exits the Reference Model command.

Reference PDS Model

16. Integrated Commands

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

_ _______________
16.4 Review PDS Clash
The Review PDS Clash command edits and reviews existing clashes and approves existing clashes.

Review PDS Clash

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

16. Integrated Commands

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

A: Error Messages
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!

A: Error Messages
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 elements 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. Recovery: Enter a new value within the range 0 to 127.

A: Error Messages

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. Recovery: Check the file permissions and the existence of the file.

A: Error Messages

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. Recovery: Key in a filename with fewer than 128 characters.

A: Error Messages

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. Recovery: Enter a new asid number.

A: Error Messages

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. Recovery: Call Intergraph support.

A: Error Messages

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. Recovery: Add privilege to the database.

A: Error Messages

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. Recovery: Run the Create Database process with the rwayref.sql file.

A: Error Messages

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. Recovery: Call Intergraph support.

A: Error Messages

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. Recovery: Enter a new value within the range 0 to 255.

A: Error Messages

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. Recovery: Key in another asid id.

A: Error Messages

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. Recovery: Turn Part Verification off OR add the fitting to the database.

A: Error Messages

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. Recovery: Fix other problems.

A: Error Messages

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. Recovery: Key in another name.

A: Error Messages

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. Recovery: Populate the database.

A: Error Messages

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). Recovery: Identify one of these elements.

A: Error Messages

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. Recovery: Enter a new value greater than zero.

A: Error Messages

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. Recovery: Accept or reject the system selection form.

A: Error Messages

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

B: System/App Mgmt.

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 Programmers Guide for this latter procedure.

Precision Input Form

B: System/App Mgmt.
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 piform* piform_tal1 piform_tal2 piform_thn1 piform_thn2 Description default tall/thin (design 1) tall/thin (design 2) long/thin (design 1) 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 ee_radius weight material ee_xs_cell ee_spec_key description real, real, real, char(20), char(6), char(28) not null, 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 <oneline_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: 4. Add the newly-created <one-line_type>_spec.unl file and the <oneline_type>_part.unl files to the rwayref.cmd file, in a format like the following: FILE "tray_part.unl" DELIMITER "|"; INSERT INTO tray_part;

Customizing

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 mscatalog table or by inserting records in the mscatref.unl file.

B: System/App Mgmt.

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 ee_out_ht_diam ee_out_width ee_dimension_1 weight material ee_part ee_symbol ee_part_key ee_description integer not null, real not null, real, real, real, char(20), char(20), char(6), char(28) not null, 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: 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.

Customizing

Add necessary rows to the mscodelist table (in the reference database) for any columns that are codelisted for the special fitting.

B: System/App Mgmt.

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 MS_APP MS_EXE MS_APPMEN Sets the directory that holds the cell libraries. Sets the directory where application executable files are found when activated from a user command TSK statement. Used as a pointer to application programs. 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"). 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. Sets the directory for temporary files. Sets the directory for the on-line Help files. Defines the path to the on-line Help files.

MS_DATA

MS_TMP MS_HELPFILE MS_HELPPATH

The MicroStation\Program\MicroStation\config\msconfig.cfg file contains detailed descriptions of the MicroStation and Umenu environment variables.

For EE Raceway: EERD_COMPRESS EERD_MSGS EERD_TBLS RWAY_FORM_PATH EE_SYM_PATH EE_SYM_FILE Compresses the file when you exit a design session. Directory for the message files. Directory for the database table files Directory path to the EE Raceway forms. Directory path to the EE Raceway symbols. 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: 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* EE_DBS* EE_NODENAME EE_REMDIR EE_SCHEMA EE_USERNAME SYS_PASSW_FILE EE_CUSTOM_SQL EE_CUSTOM_CMD EE_CUSTOM_REFSQL EE_CUSTOM_REFCMD

EE Environment Variables

Directory path for current EE project. Directory path and project database name. Default nodename for archive/restore. Default remote path for archive/restore. Schema name for project database. Default username for archive/restore. Directory path and filename of password file to enter system manager page. User-defined project database sql file. User-defined project database cmd file. User-defined reference database sql file. User-defined reference database cmd file.

B: System/App Mgmt.

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* EERWAY_DAT EERWAY_SEED RWAY_CMD RWAY_SQL RWAYREF_CMD RWAYREF_SQL EDEN_LIB RWAY_EDEN_LIB EE_PIFORM

Directory path for the EE Raceway product. Directory path for data files. Directory path for seed files. Project Database cmd file. Project Database sql file. Reference Database cmd file. Reference Database sql file. Filename for the Eden symbol library. Directory path for the Eden symbol library. 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 MS_CMDWINDRSC MS_SYSFONTS EE_TERM ORACLE_SID Directory path and filename of user preference file. Directory path and filename of command window resource file. Font used by MicroStation for window and menu display. Defines the "tty" type you are running on. 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 RIS_DIR EE_NUC* ENV_MSGS EENUC_DAT Directory path for the MicroStation product. Directory path for the RIS product. Directory path for EE Nucleus product. Directory path for message files. Directory path for data files.

423

_ _______________
EE Raceway Modeling Reference Guide - February 2003 DBA_SUPPORT EES_REFDB EES_REFSER EE_FORM_PATH EE_SYM_FILE EE_SYM_PATH For ORACLE databases: ORACLE_HOME For INGRES databases: II_SYSTEM For INFORMIX databases: INFORMIXDIR Directory path for INFORMIX executables. Directory path for INGRES executables. Directory path for ORACLE executables. Data files for DB Access Support. Schema name for reference database. EE reference database server process. Directory path for EE forms. Filename of EE symbol file. Directory path for EE symbol file.

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 Corporations 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 RDBMSs: Standard Engine (SE) Informix, On-line Informix, Oracle, and Ingres. This section contains: Descriptions of the EE databases and the Intergraph software, RIS, that supports it. Procedures that must be followed by new users of the EE product. Procedures that must be followed by existing users of the EE product. Processes needed in the procedures above. Schema descriptions for the EE project database and the EE reference database. The Electrical Engineer product line is supported by two relational databases: a project database and a 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.

C: EE Databases

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

C: EE Databases

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 schemas 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 -q .sql file -c .cmd file displays SQL commands as they are executed schema definition 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. Selecting the active one-line type parameters during a design session. Reporting.

2. 3.

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 OneLine 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 index_column index_value TYPE integer char(20) DESCRIPTION approval status index number approval status description

The approval status rows delivered with EE Raceway are: index_column 1 2 3 4 5 6 7 8 9 10 11 index_value 1 - blank 2 - approved 3 - approved 4 - approved 5 - approved 6 - approved 7 - approved 8 - approved 9 - approved 10 - approved 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 ee_car_num ee_cardinal TYPE integer char(20) DESCRIPTION cardinal index number cardinal description

The cardinal point values delivered with EE Raceway are: ee_car_num 0 1 2 6 7 8 12 13 14 ee_cardinal TOP LEFT CENTER LEFT BOTTOM LEFT TOP CENTER CENTER CENTER BOTTOM CENTER TOP RIGHT CENTER RIGHT BOTTOM RIGHT

C: EE Databases

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 code unknown TYPE Char(20) unknown DESCRIPTION drawing type 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 index_column index_value ee_part_table ee_rcp_ol_type ee_manpart_type TYPE integer char(20) integer integer integer DESCRIPTION manual_part index number manual_part description special fitting parts table number one-line type index column number manual part type index number

The special manual fittings delivered with EE Raceway are: index_column 1 2 3 index_value conduit body pullbox light fixture ee_part_table 246 249 250 ee_rcp_ol_type 3 3 3 ee_manpart_type 0 0 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 index_column index_value ee_spec_table ee_part_table ee_ol_table ee_rcp_part_table ee_max_run_angle ee_priority_level TYPE integer char(20) integer integer integer integer integer integer DESCRIPTION one-line type index number one-line type description specification table mscatalog number spec parts table mscatalog number one-line table mscatalog number special fitting parts table number maximum bends allowed per run one-line type nest level

The one-line types delivered with EE Raceway are: indx_col 1 2 3 4 5 index_value TRAY WIREWAY CONDUIT AIRWAY DUCTBANK ee_spec 240 242 244 247 260 ee_part 241 243 245 248 0 ee_ol 204 204 204 204 204 rcp_part 0 0 246 0 0 run_angle 0 0 360 0 0 priority 5 5 10 10 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 index_column index_value TYPE integer char(20) DESCRIPTION rcp type index number rcp type description

The RCP types delivered with EE Raceway are: index_column 1 2 index_value <blank> ROUTE description general raceway connect point 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 system_num system_name TYPE integer char(20) DESCRIPTION system index number system name

435

_ _______________
EE Raceway Modeling Reference Guide - February 2003 The systems delivered with EE Raceway are: system_num 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 system_name Control Communication High Voltage Low Voltage Alarm Instrumentation Signal Digital Analog Thermocouple RTD Medium Voltage Normal Lighting Emergency Lighting Security Fire Safety DC Power 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 index_column index_value TYPE integer char(20) DESCRIPTION three-line type index number three-line type description

The three-line types delivered with EE Raceway are: index_column 1 2 3 4 11 12 14 index_value STRAIGHT ELBOW WYE CROSS PULLBOX CONDUIT BODY 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 index_column index_value TYPE integer char(20) DESCRIPTION three-line subtype index number three-line subtype description

The three-line subtypes delivered with EE Raceway are: index_column 1 2 3 4 5 6 7 8 9 10 index_value <blank> VERTICAL INSIDE VERTICAL OUTSIDE VERTICAL HORIZONTAL LEFT HORIZONTAL RIGHT HORIZONTAL REDUCER LEFT REDUCER RIGHT REDUCER

C: EE Databases

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 index_column index_value TYPE integer char(20) DESCRIPTION three-line qualifier index number three-line qualifier description

437

_ _______________
EE Raceway Modeling Reference Guide - February 2003 The three-line qualifiers delivered with EE Raceway are: index_column 1 2 3 4 5 index_value <blank> RIGID BENDABLE FLEXIBLE 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 index_column index_value TYPE integer char(20) DESCRIPTION units index number units description

The units delivered with EE Raceway are: index_column 1 2 index_value English 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 index_column index_value catalog TYPE integer char(20) char(20) DESCRIPTION vendor index number vendor name catalog

438

_ _______________
Appendix C: The vendors delivered with EE Raceway are: index_column 1 2 3 4 index_value default sample unknown English sample catalog delivered blank delivered blank delivered blank delivered blank

Codelists

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 index_column index_value TYPE char(20) not null char(20) DESCRIPTION wire/cable code index value wire/cable code description

C: EE Databases

The wire/cable codes delivered with EE Raceway are: index_column AC AD AG AH AM AN AP AR AS CP CQ CV CW CX index_value AC AD AG AH AM AN AP AR AS CP CQ CV CW 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 index_column index_value TYPE char(20) not null char(20) DESCRIPTION wire/cable configuration index value wire/cable configuration description

The wire/cable configurations delivered with EE Raceway are: index_column \C PR TR index_value single conductor "pair 2 conductors "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 index_column index_value TYPE char(20) not null char(20) DESCRIPTION wire/cable size index value wire/cable size description

The wire/cable sizes delivered with EE Raceway are: index_column 36 AWG 34 AWG 32 AWG 30 AWG 28 AWG 27 AWG index_value 36 AWG 34 AWG 32 AWG 30 AWG 28 AWG 27 AWG

440

_ _______________
Appendix C: 26 AWG 24 AWG 22 AWG 20 AWG 18 AWG 16 AWG 14 AWG 12 AWG 10 AWG 8 AWG 6 AWG 4 AWG 3 AWG 2 AWG 1 AWG 1/0 AWG 2/0 AWG 3/0 AWG 4/0 AWG 250 MCM 300 MCM 350 MCM 400 MCM 500 MCM 600 MCM 700 MCM 750 MCM 800 MCM 900 MCM 1000 MCM 1250 MCM 1500 MCM 1750 MCM 2000 MCM 26 AWG 24 AWG 22 AWG 20 AWG 18 AWG 16 AWG 14 AWG 12 AWG 10 AWG 8 AWG 6 AWG 4 AWG 3 AWG 2 AWG 1 AWG 1/0 AWG 2/0 AWG 3/0 AWG 4/0 AWG 250 MCM 300 MCM 350 MCM 400 MCM 500 MCM 600 MCM 700 MCM 750 MCM 800 MCM 900 MCM 1000 MCM 1250 MCM 1500 MCM 1750 MCM 2000 MCM

Codelists

C: EE Databases

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 index_column index_value TYPE char(20) not null char(20) DESCRIPTION wire/cable insulation color index value wire/cable insulation color description The wire/cable insulation colors delivered with EE Raceway are: index_column BLK W R GR ORN BL W/BLK R/BLK GR/BLK ORN/BLK BL/BLK BLK/W R/W GR/W BL/W BLK/R W/R ORN/R BL/R R/GR ORN/GR BLK/W/R W/BLK/R R/BLK/W GR/BLK/W ORN/BLK/W BL/BLK/W BLK/R/GR W/R/GR R/BLK/GR GR/BLK/ORN ORN/BLK/GR BL/W/ORN BLK/W/ORN W/R/ORN ORN/W/BL W/R/BL BLK/W/GR W/BLK/GR R/W/GR GR/W/BL ORN/R/GR index_value BLACK WHITE RED GREEN ORANGE BLUE WHITE/BLACK RED/BLACK GREEN/BLACK ORANGE/BLACK BLUE/BLACK BLACK/WHITE RED/WHITE GREEN/WHITE BLUE/WHITE BLACK/RED WHITE/RED ORANGE/RED BLUE/RED RED/GREEN ORANGE/GREEN BLACK/WHITE/RED WHITE/BLACK/RED RED/BLACK/WHITE GREEN/BLACK/WHITE ORANGE/BLACK/WHITE BLUE/BLACK/WHITE BLACK/RED/GREEN WHITE/RED/GREEN RED/BLACK/GREEN GREEN/BLACK/ORANGE ORANGE/BLACK/GREEN BLUE/WHITE/ORANGE BLACK/WHITE/ORANGE WHITE/RED/ORANGE ORANGE/WHITE/BLUE WHITE/RED/BLUE BLACK/WHITE/GREEN WHITE/BLACK/GREEN RED/WHITE/GREEN GREEN/WHITE/BLUE ORANGE/RED/GREEN

442

_ _______________
Appendix C: BL/R/GR BLK/W/BL W/BLK/BL R/W/BL GR/ORN/R GR/R/BL BL/R/ORN BLK/ORN/R BRN Y BLUE/RED/GREEN BLACK/WHITE/BLUE WHITE/BLACK/BLUE RED/WHITE/BLUE GREEN/ORANGE/RED GREEN/RED/BLUE BLUE/RED/ORANGE BLACK/ORANGE/RED BROWN YELLOW

Codelists

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 index_column index_value

TYPE char(20) not null char(40)

DESCRIPTION wire/cable insulation voltage rating index value wire/cable insulation voltage rating description

The wire/cable voltage ratings delivered with EE Raceway are: index_column 120 120/240 208Y/120 240/120 240 480Y/277 480 600 2400 4160Y/2400 4160 4800 6900 8320Y/4800 12000Y/6930 12470Y/7200 13200Y/7620 13200 13800Y/7970 index_value Low (Single phase, 2 wire system) Low (Single phase, 3 wire system) Low (Three phase, 4 wire system) Low (Three phase, 4 wire system) Low (Three phase, 3 wire system) Low (Three phase, 4 wire system) Low (Three phase, 3 wire system) Low (Three phase, 3 wire system) Medium (Three phase, 3 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 3 wire system) Medium (Three phase, 3 wire system) Medium (Three phase, 3 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 3 wire system) Medium (Three phase, 4 wire system)

443

_ _______________
EE Raceway Modeling Reference Guide - February 2003 13800 20780Y/12000 22860Y/13200 23000 24940Y/14400 34500Y/19920 34500 46000 69000 Medium (Three phase, 3 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 3 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 4 wire system) Medium (Three phase, 3 wire system) Medium (Three phase, 3 wire system) 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 index_column index_value TYPE char(20) not null char(100) DESCRIPTION wire/cable insulation type index value wire/cable insulation type description

The wire/cable insulation types delivered with EE Raceway are: index_column A AA AI AIA A VA AVB AVL FEP FEPB MI MTW PFA PFAH RH RHH RHW SA SIS TA TBS index_value Asbestos (Without asbestos braid) Asbestos (With suitable braid material) Asbestos (Without asbestos braid) Impregnated Asbestos (With suitable braid material) Impregnated Asbestos & Varnished Cambric Impregnated Asbestos & Varnished Cambric (Flame retardant, cotton braid) Impregnated Asbestos & Varnished Cambric (AVL-lead sheath) Fluorinated Ethylene Propylene Fluorinated Ethylene Propylene (Glass braid Asbestos or other Suitable braid material) Magnesium Oxide (Copper) Flame-, Moisture-, Heat- and Oil-Resistant Thermoplastic Perfluoroalkoxy Perfluoroalkoxy Heat-Resistant Rubber (Moisture-resistant, flame- non-metallic covering) Heat-Resistant Rubber (Moisture-resistant, flame- non-metallic covering) Moisture- and Heat-Resistant Rubber (Moisture-resistant, flame-non-metallic covering) Silicone Rubber (Asbestos, glass or other suitable braid material) Heat-Resistant Rubber Thermo-plastic and Asbestos (Flame-retardant, non-metallic covering) Thermo-plastic (Flame-retardant, non-metallic covering)

444

_ _______________
Appendix C: TFE THHN THHN/THWN THW THWN TW UF USE V XHHN Z Extruded Polytetra-fluoro-ethylene Flame-, Heat-Resistant Thermoplastic (Nylon jacket or equivalent) Flame-, (Moisture-) & Heat-Resistant Thermoplastic (Nylon jacket or equivalent) Flame-, Moisture- & Heat-Resistant Thermoplastic Flame-, Moisture- & Heat-Resistant Thermoplastic (Nylon jacket or equivalent) Flame-Retardant, Moisture- and Heat-Resistant Thermoplastic Moisture-Resistant, Moisture- and Heat-Resistant (Integral with insulation) Heat- and Moisture-Resistant (Moisture-resistant non-metallic covering) Varnished Cambric (Nonmetallic covering or lead sheath) Flame-Retardant Cross-Linked Synthetic Polymer Modified Ethylene Tetrafluoro-ethylene

Codelists

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 index_column index_value TYPE integer char(20) DESCRIPTION yes-no response index number yes-no response description

C: EE Databases

The Yes-No values delivered with EE Raceway are: index_column 0 1 index_value NO 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 ee_ol_type ee_tl_type ee_tl_subtype ee_tl_qual ee_num_ols ee_pln_angles ee_prp_angles ee_part_table ee_symbol TYPE integer integer integer integer integer char(40) char(40) integer char(6) DESCRIPTION intersecting one-lines one-line type number intersecting one-lines three-line type number, zero if not applicable intersecting one-lines three-line subtype number, zero if not applicable intersecting one-lines three-line qualifier number, zero if not applicable number of intersecting one-lines planar angles between the intersecting one-lines. Angles must be defined relative to a single one-line. non-planar angles between the intersecting one-lines. Angles must be defined relative to a single one-line. fitting mscatalog table number fitting EDEN symbol name

The fitting environment rules delivered with EE Raceway are: olt 3 3 3 3 3 3 3 tlt 0 0 0 0 0 0 0 tlst 0 0 0 0 0 0 0 tlq 0 0 0 0 0 0 0 nol 2 2 3 3 4 4 5 pln 180 90 90,180 90 90,180,270 90,180 90,180,270 prp 90 90 90 tbl 246 246 246 246 246 246 246 sym CC CLB CT CGUAM CX CGUAW 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 RDBMSs (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. 2. 3. 4. Saves rows from existing table. Drops existing table (also drops indexes). Creates new table according to "create table" statement. 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. Columns that you added into an existing loaded table would have no data stored in them. 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. 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. 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.

2. 3.

4.

5.

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 RDBMSs interactive query product, such as INFORMIXs ISQL or FORMS, or ORACLEs sqlplus, or INGRESs SQL. the RIS Interactive Query Utility (win32app\ingr\share\ris\bin\risgui.exe). DB Accesss Database Edit Utility (see the section in the appendix entitled EE Manager for more information on this utility) the EE Database Utilities (risschema_mgr utility win32app\ingr\share\ris\bin\rismgr.exe)

2. 3.

4.

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: 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. 2. cd win32app\ingr\eerway\db 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:

Modifying the Reference Schema

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 index_column index_value Type integer Char(20) Index no no Null 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 ee_tl_type* ee_tl_subtype* ee_tl_qual* ee_angle* ee_symbol* ee_spec_key* ee_spec2_key* ee_part_key* ee_description* Type integer integer integer real Char( 6) Char( 28) Char( 28) Char( 28) Char( 40) Index no no no no no dups no uniq no Null yes yes yes yes yes yes yes 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 ee_units* ee_out_ht_diam* ee_out_width* ee_extension* ee_transition* ee_radius* ee_xs_cell* ee_spec_key* ee_description Type integer real real real real real Char( 6) Char( 28) Char( 40) Index no dups no no no no no uniq no Null no no yes yes yes yes yes no yes

C: EE Databases

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 ee_car_num ee_cardinal Type integer Char( 20) Index uniq dups Null no 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:

_ _______________
Type integer integer real real real Char( 20) Char( 20) Char( 6) real real real real real real Char( 28) Char( 40) integer real Char( 20) integer Index dups no no no no no no no no no no no no no uniq no no no no no Null no no yes yes yes yes yes yes yes yes yes yes yes yes no yes no yes yes yes

EE Raceway Reference Database Schema Description

cond_body
This table stores the specification information for the manual fitting CONDUIT BODY. Column Name vendor ee_units* nominal_size_1 nominal_size_2 weight material ee_part* ee_symbol* ee_dimension_1* ee_dimension_2* ee_dimension_3* ee_dimension_4* ee_dimension_5* ee_dimension_6* ee_part_key* ee_description* ee_tl_type* volume style ee_pull_point

C: EE Databases

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 ee_rule_set ee_jacket_armor ee_num_cables ee_max_fill Type Char( 20) Char( 10) integer real Index no no no no Null yes yes 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:

_ _______________
Type integer integer integer real real Char( 20) Char( 6) Char( 28) Char( 28) Char( 28) Char( 40) Index no no no no no no no dups no uniq no Null no no no yes yes yes yes yes yes no yes

EE Raceway Reference Database Schema Description

cond_part
This table stores the part specification information for the one-line type CONDUIT. Column Name ee_tl_type* ee_tl_subtype* ee_tl_qual* ee_angle* ee_weight* ee_part* ee_symbol* ee_spec_key* ee_spec2_key* ee_part_key* ee_description*

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

C: EE Databases

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 vendor ee_units* nominal_size ee_dimension_1* ee_out_ht_diam* ee_extension* ee_transition* ee_radius* weight material ee_const_type ee_xs_cell* ee_spec_key* ee_description Type integer integer real real real real real real real Char( 20) integer Char( 6) Char( 28) Char( 40) Index dups no no no dups no no no no no no no uniq no Null no no yes yes no yes yes yes yes yes no yes 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 drawing_type* sheet* ee_key* ee_description* Type Char( 20) Char( 20) Char( 28) Char( 40) Index no no uniq no Null no yes no yes

C: EE Databases

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 ee_code code_desc Type Char(20) Char(20) Index uniq no Null 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 tag ee_dist_down_ol* ee_dist_to_rcp* ee_key* ee_description* Type Char(20) real real Char(28) Char(40) Index no no no unique no Null yes yes yes 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 ee_units ee_out_ht_diam ee_out_width material ee_xs_cell ee_spec_key ee_description Type integer real real Char( 20) Char( 6) Char( 28) Char( 40) Index no dups dups no no uniq no Null no no yes yes yes 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 nominal_size ee_dimension_1 ee_area Type real real real Index uniq no no Null no yes 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 table_name column_name Type Char( 32) Char( 32) Index uniq uniq Null yes 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 index_column index_value Type Char( 20) Char( 20) Index uniq dups Null no 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 index_column index_value Type Char( 20) Char( 20) Index uniq dups Null no 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 index_column index_value Type Char( 20) Char( 20) Index uniq dups Null no 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 index_column index_value Type Char( 20) Char(100) Index uniq dups Null no 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. Column Name index_column index_value Type Char( 20) Char( 20) Index uniq dups Null no yes

C: EE Databases

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 index_column index_value Type Char( 20) Char( 40) Index uniq dups Null no 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 ee_code config cable_size ee_color voltage insulation item_no ee_area ee_units 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. Type Char( 20) Char( 20) Char( 20) Char( 20) Char( 20) Char( 20) Char( 20) real integer Index no no no no no no uniq no no Null yes yes yes yes yes yes yes yes no

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 system_num system_name Type integer Char( 20) Index uniq dups Null no 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:

_ _______________
Type integer Char( 20) Index uniq dups Null no yes

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 index_column* index_value*

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 table_name column_name ee_comp_type* blank_allowed Type Char( 32) Char( 32) Char( 10) integer Index uniq uniq uniq no Null yes yes yes yes

C: EE Databases

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 index_column* index_value* Type integer Char( 20) Index uniq dups Null yes 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 tag ee_key* ee_description* Type Char( 20) Char( 28) Char( 40) Index no uniq no Null yes 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:

_ _______________
Type Char( 6) integer real real real Char( 28) real real real real Char( 40) Char( 3) real real real Char( 20) integer Char( 4) integer real Char( 6) integer Char( 32) Char( 32) Char( 32) Char( 32) integer integer Index no no no no no uniq no no no no no no no no no no dups no no no no no no no no no no no Null yes yes yes yes yes no yes yes yes yes yes yes yes yes yes yes no yes yes yes yes yes yes yes yes yes no yes

EE Raceway Reference Database Schema Description

light_fixture
This table stores the specification information for the manually placed equipment LIGHT_FIXTURE. Column Name ee_symbol voltage ee_dimension_1 ee_dimension_2 ee_dimension_3 ee_part_key fl_amps ee_dimension_4 ee_dimension_5 ee_dimension_6 ee_description item_type ee_dimension_7 ee_dimension_8 ee_dimension_9 item_code_num vendor num_wires num_phase_wires power_factor area_class oper_temp_deg_c text_1 text_2 text_3 text_4 ee_units ee_pull_point

C: EE Databases

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 fixtures 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 fixtures 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 fixtures 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 fixtures 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 fixtures power factor. area_class: the column used to define a light fixtures area class. oper_temp_deg_c: the column used to define a light fixtures 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:

_ _______________
Type integer Char( 20) integer integer integer Index uniq dups no no no Null no yes yes yes yes

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 index_column* index_value* ee_part_table* ee_rcp_ol_type* ee_manpart_type

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 tablename entitynum screenform reporttable sqlreview fencefilter dastable alias_name key_columns key_description Type Char( 32) integer Char( 64) Char( 64) Char(240) Char(240) Char(32) Char( 64) Char( 80) Char( 32) Index no uniq no no no no no no no no Null no no yes yes yes yes yes yes yes 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 table_name column_name join_table code_column text_column index_column* index_value* Type Char( 32) Char( 32) Char( 32) Char( 32) Char( 32) Char( 32) integer Index uniq uniq no no no no no Null no no no no no yes 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 entitynum attrnum column_name alias_name access_flag work_mode ee_column_order

Type integer integer Char( 32) Char( 32) smallint smallint smallint

Index uniq uniq no no no no no

Null no no no yes no 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 index_column* index_value* ee_spec_table* ee_part_table* ee_ol_table* ee_rcp_part_table* ee_max_run_angle* ee_priority_level* Type integer Char( 20) integer integer integer integer integer integer Index uniq dups no no no no no no Null no yes yes yes yes yes yes 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:

_ _______________
Type Char( 20) real real Char( 28) Char( 28) Char( 40) Index no no no no uniq no Null yes yes yes no no yes

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 tag add_weight ee_ol_length* ee_spec_key* ee_key* ee_description*

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 panel panel_descrip ee_approv_status ee_approv_date ee_create_date ee_last_rev_dat ee_key ee_description Type Char( 20) Char( 20) integer Char( 40) Char( 40) Char( 40) Char( 28) Char( 40) Index no no no no no no uniq no Null yes yes yes yes yes yes 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 prj_number prj_name location prj_rule_set base_rule_set ee_key ee_description Type char(20) char(60) char(60) char(20) char(20) char(28) char(60) Index dups no no no no uniq no Null yes yes yes yes yes 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:

_ _______________
Type integer integer real real real real char(20) char(20) char(6) char(28) char(40) integer integer Index dups no dups dups dups no no no no uniq no no no Null no no no yes yes yes yes yes yes no yes no yes

EE Raceway Reference Database Schema Description

pullbox
This table stores the specification information for the manual fitting PULLBOX. Column Name vendor ee_units* ee_out_ht_diam* ee_out_width* ee_dimension_1 weight material ee_part* ee_symbol* ee_part_key* ee_description ee_tl_type ee_pull_point

vendor: the codelisted column used to define the pullbox vendor. ee_units: the codelisted column used to define the untis of measurement. ee_out_ht_diam: the column used to define the pullbox outside height to the EERWAY software. ee_out_width: the column used to define the pullbox outside width to the EERWAY software . ee_dimension_1: the column used to define the pullbox dimension value to Eden and the 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.

C: EE Databases

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 tag ee_rcp_type* ee_extension* ee_transition* ee_radius* ee_part_key* ee_key* ee_description* Type Char( 20) integer real real real Char( 28) Char( 28) Char( 40) Index no no no no no no uniq no Null yes yes yes yes yes yes 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 index_column* index_value* Type integer Char( 20) Index uniq dups Null no 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:

_ _______________
Type integer integer integer integer integer Char( 40) Char( 40) integer Char( 6) Index uniq no no no uniq uniq uniq no dups Null no no no no yes yes yes yes yes

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 ee_ol_type ee_tl_type ee_tl_subtype ee_tl_qual ee_num_ols ee_pln_angles ee_prp_angles ee_part_table ee_symbol

ee_ol_type: the index_column number from the one-line type codelist table of the intersecting onelines. 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 index_column* index_value* Type integer Char( 20) Index uniq dups Null no 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 index_column* index_value* Type integer Char( 20) Index uniq dups Null no 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 index_column* index_value* Type integer Char( 20) Index uniq dups Null no 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:

_ _______________
Type Char( 32) Char( 28) Char( 28) Char( 40) Index no no uniq no Null yes yes no yes

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 ee_eqp_table ee_part_key ee_eqp_key* ee_description*

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
This table defines both the columns you can annotate for support equipment symbols and their default column values. Column Name tag ee_key* ee_description* Type Char( 20) Char( 28) Char( 40) Index no uniq no Null yes no yes

C: EE Databases

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 ee_tl_type* ee_tl_subtype* ee_tl_qual* ee_angle* ee_weight* ee_part* ee_symbol* ee_spec_key* ee_spec2_key* ee_part_key* ee_description* Type integer integer integer real real Char( 20) Char( 6) Char( 28) Char( 28) Char( 28) Char( 40) Index no no no no no no no dups no uniq no Null no no no yes yes yes yes yes yes 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:

_ _______________
Type integer integer real real real real real real real real Char( 20) integer Char( 6) Char( 28) Char( 40) Index dups no no dups no dups no no no no no no no uniq no Null no no yes no yes yes yes yes yes yes yes no yes no yes

EE Raceway Reference Database Schema Description

tray_spec
This table stores the general specification information for the one-line type TRAY. Column Name vendor ee_units* ee_dimension_1* ee_out_ht_diam* ee_dimension_2* ee_out_width* ee_extension* ee_transition* ee_radius* weight material ee_const_type ee_xs_cell* ee_spec_key* ee_description

vendor: the codelisted column used to define the vendor of the tray specification. 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.

C: EE Databases

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 index_column* index_value* catalog Type integer Char( 20) char(20) Index uniq dups no Null no yes 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 ee_tl_type* ee_tl_subtype* ee_tl_qual* ee_angle* ee_weight* ee_part* ee_symbol* ee_spec_key* ee_spec2_key* ee_part_key* ee_description* Type integer integer integer real real Char( 20) Char( 6) Char( 28) Char( 28) Char( 28) Char( 40) Index no no no no no no no dups no uniq no Null yes yes yes yes yes yes yes yes yes 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 vendor ee_units* ee_dimension_1* ee_out_ht_diam* ee_dimension_2* ee_out_width* ee_extension* ee_transition* ee_radius* weight material ee_const_type ee_xs_cell* ee_spec_key* ee_description Type integer integer real real real real real real real real Char( 20) integer Char( 6) Char( 28) Char( 40) Index dups no no dups no dups no no no no no no no uniq no Null no no yes no yes yes yes yes yes yes yes no yes 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 revision_numb cable_numb numb_cables numb_conductor conductor_size cable_type_code service_voltage undgrnd_length abvgrnd_length from_equi_numb from_detail not_used plan_assem_dwg to_equi_numb to_detail to_plan_drw_num cont_sta_type quan_term_kits ol_diagram_numb not_used2 remarks drawing_numb drawing_rev Type Char( 3) Char( 8) integer Char( 5) Char( 8) Char( 6) Char( 7) real real Char( 15) Char( 8) Char( 6) Char( 20) Char( 15) Char( 8) Char( 20) Char( 4) Char( 6) Char( 20) Char( 8) Char( 38) Char( 20) Char( 2) Index no uniq no no no no no no no no no no no no no no no no no no no uniq no Null yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes

C: EE Databases

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 revision_numb conduit_numb conduit_for cnd_from_where cnd_to_where undgrnd_cnd_size undgrnd_cnd_type undgrnd_cnd_length abvgrnd_cnd_size abvgrnd_cnd_type abvgrnd_cnd_length cnd_detail_numb detail_drw_numb cnd_ac_dimension cnd_station pow_conduct_volt pow_conduct_numb pow_conduct_size pow_conduct_type pow_conduct_length con_conduct_numb con_conduct_size con_conduct_type con_conduct_length grnd_wire_size grnd_wire_type grnd_wire_length ol_diagram_numb remarks drawing_numb drawing_rev Type Char( 2) Char( 10) Char( 12) Char( 20) Char( 20) Char( 6) Char( 5) real Char( 6) Char( 4) real Char( 7) Char( 12) Char( 12) Char( 6) Char( 5) integer Char( 7) Char( 4) real integer Char( 7) Char( 4) real Char( 6) Char( 4) real Char( 10) Char( 16) Char( 20) Char( 2) Index no uniq no no no no no no no no no no no no no no no no no no no no no no no no no no no uniq no Null yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes

C: EE Databases

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: drawing_rev: the column containing the drawing revision.

EE Raceway Project Database Schema Description

drawing
This table, used by all EE products, contains general information about each EE design file. Column Name mslink* drawing_type* ee_filename* sheet* load_date* ref_db* Type integer Char( 20) Char( 80) Char( 20) Char( 26) Char( 80) Index uniq no no uniq no no Null no no no no no no

mslink: a unique integer value used by the software to identify a row in the drawing table. drawing_type: the column used to define the type of EE drawing. ee_filename: the column containing the drawing file name and path.

C: EE Databases

sheet: the column used to contain the drawing sheet name. load_date: the column containing the date that the load processor loaded the drawing into the project database. ref_db: the column containing the schema name of the EE reference database.

drop_point
This table associates a row in the rcp table with a row in the one-line table. Column Name mslink* ee_to_drw* ee_to_ol* ee_to_rcp* ee_dist_down_ol* ee_dist_to_rcp* tag Type integer integer integer integer real real Char( 20) Index uniq no dups dups no no no Null no no yes yes yes yes yes

mslink: a unique integer value used by the software to identify a row in the drop_point table. ee_to_drw: the column containing the mslink of a row in the drawing table. ee_to_ol: the column containing the mslink of a row in the one_line table.

491

_ _______________
EE Raceway Modeling Reference Guide - February 2003 ee_to_rcp: the column containing the mslink of a row in the rcp table. ee_dist_down_ol: the column containing the distance along the one-line to the drop point. ee_dist_to_rcp: the column containing the distance between the one-line and the rcp. tag: the column that contains the name of the drop point.

duct_fill
This table defines the cable/conduit that are placed in a duct one-line. Column Name ee_to_ol ee_to_drw ee_duct_cc_row ee_duct_cc_col ee_duct_cc_numb ee_drawing_numb Type integer integer integer integer Char( 12) Char( 20) Index dups dups no no no no Null yes yes yes yes yes yes

ee_to_ol: the column containing the mslink of a row in the one-line table. ee_to_drw: the column containing the mslink of a row in the drawing table. ee_duct_cc_row: the row index of the conduit/cable. ee_duct_cc_col: the column index of the conduit/cable. ee_duct_cc_numb: cable/conduit area number, cable number, and cable number number ID. ee_drawing_numb: detail drawing number of the conduit/cable schedule.

ee_pseudo_cable
This table defines the wires/cables that fill conduit. This is performed with the EE Raceway Conduit Sizing command. Column Name mslink ee_to_ol ee_to_drw ee_quantity item_no Type integer integer integer integer Char( 20) Index uniq no no no dups Null no no no yes yes

mslink: a unique integer value used by the software to identify a row in the ee_pseudo_cable table. ee_to_ol: the column containing the mslink of a row in the one-line table.

492

_ _______________
Appendix C: ee_to_drw: the column containing the mslink of a row in the drawing table. ee_quantity: the number of wires/cables associated with the given one-line of a given item_no. item_no: the column containing the unique key to the ee_pseudo_cable table of the reference schema.

EE Raceway Project Database Schema Description

ee_system
This table contains the names of all systems from every EE Raceway drawing loaded into the project database. Column Name mslink* system_name Type integer Char( 20) Index uniq dups Null no yes

mslink: a unique integer value used by the software to identify a row in the ee_system table. system_name: the column that contains the names of the systems.

envelope
This table contains information about the raceway envelopes found in the drawing. Column Name mslink* ee_to_drw* tag Type integer integer Char( 20) Index uniq no dups Null no no yes

C: EE Databases

mslink: a unique integer value used by the software to identify a row in the envelope table. ee_to_drw: the column containing the mslink of a row in the drawing table. tag: the column that contains the envelope tag. Space envelopes are not available at time of printing.

493

_ _______________
EE Raceway Modeling Reference Guide - February 2003

fitting
This table contains information about the raceway fittings found in the drawing. Column Name mslink* ee_to_drw* ee_to_ol* ee_to_rcp* ee_out_ht_diam* ee_out_width* ee_out_width2 ee_dimension_1* ee_angle* ee_weight* cab_weight pds_east* pds_north* pds_elev* vendor ee_units* ee_tl_type* ee_tl_subtype* ee_tl_qual* ee_ol_type* ee_part* ee_description Type integer integer integer integer real real real real real real real real real real Char( 20) Char( 20) Char( 20) Char( 20) Char( 20) Char( 20) Char( 20) Char( 40) Index uniq no dups dups no no no no no no no no no no no no no no no no dups no Null no no yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes

mslink: a unique integer value used by the software to identify a row in the fitting table. ee_to_drw: the column containing the mslink of a row in the drawing table. ee_to_ol: the column containing the mslink of a row in the one-line table. ee_to_rcp: the column containing the mslink of a row in the rcp table. ee_out_ht_diam: the column containing the outside height or diameter of the fitting. ee_out_width: the column containing the outside width of the fitting. ee_out_width2: the column containing the outside width of the reducer. ee_dimension_1: the column containing a dimension of the fitting. ee_angle: the column containing the fitting bend angle. ee_weight: the column containing the fitting weight per unit length.

494

_ _______________
Appendix C: cab_weight: the column containing the cable weight per unit length. pds_north: the column containing the PDS north coordinate of the fitting (calculated by Load Database). pds_elev: the column containing the PDS elevation coordinate of the fitting (calculated by Load Database). vendor: the column containing the codelist value of the vendor of the one-line type specification. ee_units: the column containing the codelist value of the design file units. ee_tl_type: the column containing the codelist value of the three-line type. ee_tl_subtype: the column containing the codelist value of the three-line subtype. ee_tl_qual: the column containing the codelist value of the three-line qualifier. ee_ol_type: the column containing the codelist value of the one-line type. ee_part: the column containing the straight section part number. ee_description: the column containing the fitting part description.

EE Raceway Project Database Schema Description

pds_east: the column containing the PDS east coordinate of the fitting (calculated by Load Database).

C: EE Databases

fit_to_sys
This table links a fitting to each system of which it is a member. Column Name ee_to_fit* ee_to_sys* ee_percent* Type integer integer real Index dups dups no Null no no yes

ee_to_fit: the column containing the mslink of a row in the fitting table. ee_to_sys: the column containing the mslink of a row in the ee_system table. ee_percent: the column containing the percent amount of the fitting is contained in the system identified by the mslink stored in ee_to_sys.

495

_ _______________
EE Raceway Modeling Reference Guide - February 2003

mscatalog
This table contains the entity (table) numbers for all the tables in the EE Raceway project database. There will be one row in the mscatalog for each database table. Column Name tablename entitynum screenform reporttable sqlreview fencefilter dastable alias_name key_columns key_description Type Char( 32) integer Char( 64) Char( 64) Char(240) Char(240) Char(32) Char(32) Char( 80) Char( 32) Index no uniq no no no no no no no no Null no no yes yes yes yes yes yes yes yes

tablename: the name of the table in the database. It must exactly match the name of the desired table. entitynum: The entity number assigned to a table. It must be a positive integer in the range of 1 to 65535. The entity number uniquely identifies a particular table in the database. screenform: not currently used by MicroStation 32. reporttable: a temporary table used by MicroStation 32. Is is created for each table having graphic linkages within a fence. sqlreview: an sql select satement that MicroStation 32 uses to review rows and columns. fencefilter: an sql select statement that MicroStation 32 uses to restrict elements during 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.

496

_ _______________
Appendix C:

EE Raceway Project Database Schema Description

mscolumns
This table specifies column-specific data for EE tables. There is one row in mscolumns for each column in an attribute table. RISRPT and DBAccess use this table for reports. Currently, there are no EE processors using this table. Column Name entitynum attrnum column_name alias_name access_flag work_mode ee_column_order* Type uniq integer Char( 32) Char( 64) smallint smallint smallint Index uniq uniq no no no no no Null no no no yes no 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 an EE user. This column can also be thought of as a filter. Display of certain attributes can be restricted 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. ee_column_order: the column used to determine the order to display the attributes on the annotation form.

C: EE Databases

497

_ _______________
EE Raceway Modeling Reference Guide - February 2003

ol_to_sys
This table links a one-line to each system of which it is a member. Column Name ee_to_ol* ee_to_sys* ee_percent* prj_rule_applied Type integer integer real integer Index dups dups no no Null no no yes yes

ee_to_ol: the column containing the mslink of a row in the one-line table. ee_to_sys: the column containing the mslink of a row in the ee_system table. ee_percent: the column containing the percent amount of the straight section is contained in the system identified by the mslink stored in ee_to_sys. prj_rule_applied: the column containing the applied project rule.

one_line
This table contains information about the raceway one-lines found in the drawing. Column Name mslink* ee_to_drw* ee_to_rcp1* ee_to_rcp2* ee_out_ht_diam* ee_out_width* ee_dimension_1* ee_dimension_2* ee_ol_length* weight cab_weight vendor ee_units* ee_ol_type* ee_spec_key* tag ee_radius ee_const_type Type integer integer integer integer real real real real real real real Char( 20) Char( 20) Char( 20) Char( 28) Char( 20) real char Index uniq no dups dups no no no no no no no dups no no dups dups no no Null no no no no yes yes yes yes yes yes yes yes yes yes yes yes yes yes

mslink: a unique integer value used by the software to identify a row in the one_line table.

498

_ _______________
Appendix C: ee_to_drw: the column containing the mslink of a row in the drawing table. ee_to_rcp2: the column containing the mslink of the rcp placed at the end of the one-line in the design file. ee_out_ht_diam: the column containing the outside height or diameter of the one-line type. ee_out_width: the column containing the outside width of the one-line type. ee_dimension_1: the column containing a dimension of the one-line type. ee_dimension_2: the column containing a dimension of the one-line type. ee_ol_length: the column containing the run length of the one-line. weight: the column containing the one-line type weight per unit length. cab_weight: the column containing the cable weight per unit length. vendor: the column containing the codelist value of the vendor of the one-line type specification. ee_units: the column containing the codelist value of the design file units. ee_ol_type: the column containing the codelist value of the one-line type. ee_spec_key: the column containing the unique key to the one-line type specification table. tag: the column that contains the name of the one-line. ee_radius: the column that contains the fitting bend radius of the three-line type specification. ee_const_type: the column that contains the construction type.

EE Raceway Project Database Schema Description

ee_to_rcp1: the column containing the mslink of the rcp placed at the start of the one-line in the design file.

C: EE Databases

499

_ _______________
EE Raceway Modeling Reference Guide - February 2003

panel
This table contains information about all panels/equipment found in the drawing. Column Name mslink panel panel_descrip ee_approv_status ee_approv_date ee_create_date ee_last_rev_dat ee_eqp_table ee_part_key Type integer Char( 20) Char( 20) integer Char( 26) Char( 26) Char( 26) Char( 32) Char( 28) Index uniq dups no no no no no no no Null no yes yes yes yes yes yes yes yes

mslink: a unique integer value used by the software to identify a row in the panel table. panel: the column containing the panel/equipment name panel_descrip: the column containing the panel/equipment description. ee_approv_status: the column containing the approval status of the panel/equipment. ee_approv_date: the column containing the date when the approval status changed. ee_create_date: the column containing the panel/equipment creation date. ee_last_rev_dat: the column containing the date the panel/equipment was last revised. ee_eqp_table: the column containing the name of the reference database table that contains additional equipment information. ee_part_key: the column containing the unique key to the appropriate record of equipment information in the reference database table.

project
This table contains specification information for the project. Column Name mslink prj_number prj_name location prj_rule_set base_rule_set Type integer Char( 20) Char( 40) Char( 60) Char( 20) Char( 20) Index uniq uniq uniq no no no Null no yes no no no yes

500

_ _______________
Appendix C: mslink: a unique integer value used by the software to identify a row in the panel table. prj_number: the column containing the project number prj_name: the column containing the project name description. location: the column containing location. prl_rule_set: the column containing the project rule set. base_rule_set: column containing the base rule set.

EE Raceway Project Database Schema Description

panel_to_drw
This table links a panel/equipment to each drawing in which it exists. Column Name ee_to_panel ee_asid ee_to_drw ee_to_rcp ee_status Type integer integer integer integer integer Index dups no dups dups no Null no no no yes no

C: EE Databases

ee_to_panel: the column containing the mslink of a row in the panel table. ee_asid: the column containing the asid number of the panel/equipment element in the design file identified by the mslink stored in ee_to_drw. ee_to_drw: the column containing the mslink of a row in the drawing table. ee_to_rcp: the column containing the mslink of a row in the RCP table. ee_status: the column containing the revision status of the panel element in the design file (used by the Load Database process).

rcp
This table contains information about all raceway connect points (RCPs) found in the drawing. Column Name mslink* ee_rcp_type* tag ee_radius Type integer Char( 10) Char( 20) real Index uniq no no no Null no yes yes no

mslink: a unique integer value used by the software to identify a row in the rcp table.

501

_ _______________
EE Raceway Modeling Reference Guide - February 2003 ee_rcp_type: the column containing the codelist value of the type of rcp. tag: the column that contains the name of the rcp. ee_radius: the column containing the fitting bend radius.

rcp_to_drw
This table links an rcp to each drawing in which it exists. Column Name ee_to_rcp* ee_asid* ee_to_drw* pds_east* pds_north* pds_elev* Type integer integer integer real real real Index dups no dups no no no Null no no no yes yes yes

ee_to_rcp: the column containing the mslink of a row in the rcp table. ee_asid: the column containing the asid number of the rcp element in the drawing identified by the mslink stored in ee_to_drw. ee_to_drw: the column containing the mslink of a row in the drawing table. pds_east: the column containing the PDS east coordinate of the rcp (calculated by Load Database). pds_north: the column containing the PDS north coordinate of the rcp (calculated by Load Database). pds_elev: the column containing the PDS elevation coordinate of the rcp (calculated by Load Database).

rcp_to_sys
This table links an rcp to each system of which it is a member. Column Name ee_to_rcp* ee_to_sys* ee_percent* Type integer integer real Index dups dups no Null no no yes

ee_to_rcp: the column containing the mslink of a row in the rcp table. ee_to_sys: the column containing the mslink of a row in the ee_system table.

502

_ _______________
Appendix C: ee_percent: the column containing the percent amount of the fitting is contained in the system identified by the mslink stored in ee_to_sys.

EE Raceway Project Database Schema Description

straight
This table contains information about the raceway straight sections found in the drawing. Column Name mslink* ee_to_drw* ee_to_ol* ee_out_ht_diam* ee_out_width* ee_tl_length* ee_dimension_1* ee_dimension_2* ee_weight* cab_weight pds_east* pds_north* pds_elev* vendor ee_units* ee_ol_type* ee_spec_key* ee_part* material ee_description Type integer integer integer real real real real real real real real real real Char( 20) Char( 20) Char( 20) Char( 28) Char( 20) Char( 20) Char( 40) Index uniq no dups no no no no no no no no no no dups no no dups no no no Null no no no yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes

C: EE Databases

mslink: a unique integer value used by the software to identify a row in the straight table. ee_to_drw: the column containing the mslink of a row in the drawing table. ee_to_ol: the column containing the mslink of a row in the one-line table. ee_out_ht_diam: the column containing the outside height or diameter of the straight section. ee_out_width: the column containing the outside width of the straight section. ee_tl_length: the column containing the length of the straight section. ee_dimension_1: the column containing a dimension of the straight section. ee_dimension_2: the column containing a dimension of the straight section. ee_weight: the column containing the straight section weight per unit length.

503

_ _______________
EE Raceway Modeling Reference Guide - February 2003 cab_weight: the column containing the cable weight per unit length. pds_east: the column containing the PDS east coordinate of the straight section (calculated by Load Database). pds_north: the column containing the PDS north coordinate of the straight section (calculated by Load Database). pds_elev: the column containing the PDS elevation coordinate of the straight section (calculated by Load Database). vendor: the column containing the codelist value of the vendor of the one-line type specification. ee_units: the column containing the codelist value of the design file units. ee_ol_type: the column containing the codelist value of the one-line type. ee_spec_key: the column containing the unique key to the one-line type specification table. ee_part: the column containing the straight section part number. material: the column containing the straight section material. ee_description: the column containing the straight section part description.

str_to_sys
This table links a straight section to each system of which it is a member. Column Name ee_to_str* ee_to_sys* ee_percent* Type integer integer real Index dups dups no Null no no yes

ee_to_str: the column containing the mslink of a row in the straight table. ee_to_sys: the column containing the mslink of a row in the ee_system table. ee_percent: the column containing the percent amount of the straight section is contained in the system identified by the mslink stored in ee_to_sys.

504

_ _______________
Appendix C:

EE Raceway Project Database Schema Description

sys_to_drw
This table links a system name to each drawing in which the system exists. Column Name ee_to_sys* ee_asid* ee_to_drw* Type integer integer integer Index dups no dups Null no no no

ee_to_sys: the column containing the mslink of a row in the ee_system table. ee_asid: the column containing the asid number of the system element in the drawing identified by the mslink stored in ee_to_drw. ee_to_drw: the column containing the mslink of a row in the drawing table.

to_support
This table links the raceway one-line with a support. Column Name mslink* ee_to_drw* ee_to_ol* ee_ol_coord* tag Type integer integer integer real Char( 20) Index uniq no no no dups Null no no no yes yes

C: EE Databases

mslink: a unique integer value used by the software to identify a row in the to_support table. ee_to_drw: the column containing the mslink of a row in the drawing table. ee_to_ol: the column containing the mslink of a row in the one-line table. ee_ol_coord: the column containing the distance along the one-line to the support. tag: the column that contains the support tag. to_support symbols are not available at time of printing.

505

_ _______________
EE Raceway Modeling Reference Guide - February 2003

506

_ _______________
Appendix D:

Specification

Appendix D Specification
Your reference database contains the specification tables (<one-line type>_part and <one-line type>_spec) that drive the EE Raceway product. These tables contain all attribute information for the available one-line types. The <one-line type>_spec table contains all specifications, while the <one-line type>_part table contains the relevant data for each of the fittings within a specification. The specifications available at the time of printing are for tray, wireway, airway, and conduit. For special fittings like conduit bodies and pullboxes, the reference database contains one table for each fitting type. The two special fittings delivered by default with EE Raceway are conduit body and pullbox.

Preparing the Specifications

Preparing the specifications is one of the first tasks the system manager performs when setting up the EE Raceway product. The first step in this preparation is to create two ASCII data files (<one-line type>_part.unl and <one-line type>_spec.unl) to contain all the relevant data from the vendor catalogs. You can edit these files manually using a standard ASCII editor or you can use the SPEC process delivered with EE Raceway. This process allows you to add records to an existing .unl file or to create a new .unl file easily and efficiently.

SPEC Process
The SPEC process resides in the win32app\eerway\bin directory. If you intend to add records to an existing .unl file, copy the appropriate <one-line type>_spec.unl to a file called <one-line type>_spec.sav before running the process. The process will then write all records to this .sav file. To initiate the process, key in SPEC at the command prompt. The following information displays to the screen: Enter schema name: Enter table name: Is this a restart (y/n) Respond to the prompts according to your requirements. Enter your reference schema name and the appropriate table name. The system will attach a .sav extension to the specified table name, and will then write all records to that file. Indicate whether or not you are adding records to an existing file (Is this a restart (y/n). If you answer n to the prompt, the system will overwrite any records already existing in the specified .sav file.

D: Specs

507

_ _______________
EE Raceway Modeling Reference Guide - February 2003 The system processes the information, and then displays the column values for the table name you specified, in a format similar to the following example (for tray_spec): vendor <code list> () ee_units <code list> () ee_dimension_1 <real> () ee_out_ht_diam <real> () ee_dimension_2 <real> () ee_out_width <real> () ee_extension <real> () ee_transition <real> () ee_radius <real> () weight <real> () material <char-20> () ee_xs_cell <char-6> () ee_spec_key <char-28> () ee_description <char-40> ()

Key in values to the right of the () for each column value. Each value is verified according to the parameters defined inside the < >. Once you enter the final value for the displayed table, the system writes the information to the .sav file and redisplays the column names. It also displays the column values you entered for the previous record. For subsequent records, press <RETURN> to accept the displayed values (in ()) or key in new values as necessary. Continue this process as long as you wish to add records to your .sav file. You can exit the process at any point by pressing CTRL -C. Copy the .sav file back to the corresponding .unl file to keep the records you have added.

508

_ _______________
Appendix D:

Sample .unl Files

Sample .unl Files

The following are examples of .unl files you will load into your reference database tables. Note that the | serves as a delimiter between column values. tray_spec.unl

2|1|0|50|0|600|0|0|600|0|HOT DIP STEEL|A|6060SHV|VENTRIB SHV A 2|1|0|50|0|600|0|0|300|0|HOT DIP STEEL|A|6030SHV|VENTRIB SHV A 2|1|0|50|0|450|0|0|600|0|HOT DIP STEEL|A|4560SHV|VENTRIB SHV A 2|1|0|50|0|450|0|0|300|0|HOT DIP STEEL|A|4530SHV|VENTRIB SHV A 2|1|0|50|0|300|0|0|600|0|HOT DIP STEEL|A|3060SHV|VENTRIB SHV A 2|1|0|50|0|300|0|0|300|0|HOT DIP STEEL|A|3030SHV|VENTRIB SHV A 2|1|0|50|0|150|0|0|600|0|HOT DIP STEEL|A|1560SHV|VENTRIB SHV A 2|1|0|50|0|150|0|0|300|0|HOT DIP STEEL|A|1530SHV|VENTRIB SHV A 2|1|0|85|0|600|0|0|600|0|HOT DIP STEEL|A|6060SV|VENTRIB SV C1 2|1|0|85|0|600|0|0|300|0|HOT DIP STEEL|A|6030SV|VENTRIB SV C1 2|1|0|85|0|450|0|0|600|0|HOT DIP STEEL|A|4560SV|VENTRIB SV C1 2|1|0|85|0|450|0|0|300|0|HOT DIP STEEL|A|4530SV|VENTRIB SV C1 2|1|0|85|0|300|0|0|600|0|HOT DIP STEEL|A|3060SV|VENTRIB SV C1 2|1|0|85|0|300|0|0|300|0|HOT DIP STEEL|A|3030SV|VENTRIB SV C1 2|1|0|85|0|150|0|0|600|0|HOT DIP STEEL|A|1560SV|VENTRIB SV C1 2|1|0|85|0|150|0|0|300|0|HOT DIP STEEL|A|1530SV|VENTRIB SV C1 2|1|0|50|0|600|0|0|600|0|ALUMINUM|A|6060AHV|VENTRIB AHV A 2|1|0|50|0|600|0|0|300|0|ALUMINUM|A|6030AHV|VENTRIB AHV A 2|1|0|50|0|450|0|0|600|0|ALUMINUM|A|4560AHV|VENTRIB AHV A 2|1|0|50|0|450|0|0|300|0|ALUMINUM|A|4530AHV|VENTRIB AHV A 2|1|0|50|0|300|0|0|600|0|ALUMINUM|A|3060AHV|VENTRIB AHV A

D: Specs

509

_ _______________
EE Raceway Modeling Reference Guide - February 2003 tray_part.unl 2|2|5|90|0|A-15VA|VEL|1530AS| |A-15VA|Vertical Adjustable Elbow 2|2|5|90|0|A-30VA|VEL|3030AS| |A-30VA|Vertical Adjustable Elbow 2|2|5|90|0|A-45VA|VEL|4530AS| |A-45VA|Vertical Adjustable Elbow 2|2|5|90|0|A-60VA|VEL|6030AS| |A-60VA|Vertical Adjustable Elbow 2|2|5|90|0|AD-15VA|VEL|1530ADS| |AD-15VA|Vertical Adjustable Elbow 2|2|5|90|0|AD-30VA|VEL|3030ADS| |AD-30VA|Vertical Adjustable Elbow 2|2|5|90|0|AD-45VA|VEL|4530ADS| |AD-45VA|Vertical Adjustable Elbow 2|2|5|90|0|AD-60VA|VEL|6030ADS| |AD-60VA|Vertical Adjustable Elbow 4|5|1|90|0|ADL-15X-90|HRC|1590ADL| |ADL-15X-90|Horizontal Cross 1|8|1|0|0|ADL-30R15|CR|1560ADL|3060ADL|ADL-30R15-60|Concentric Reducer 1|8|1|0|0|ADL-30R15|CR|1590ADL|3090ADL|ADL-30R15-90|Concentric Reducer 1|9|1|0|0|ADL-30RL15|LR|1560ADL|3060ADL|ADL-30RL15-60|Left Reducer 1|9|1|0|0|ADL-30RL15|LR|1590ADL|3090ADL|ADL-30RL15-90|Left Reducer 1|10|1|0|0|ADL-30RR15|RR|1560ADL|3060ADL|ADL-30RR15-60|Right Reducer 1|10|1|0|0|ADL-30RR15|RR|1590ADL|3090ADL|ADL-30RR15-90|Right Reducer 1|1|1|0|0|ADL-30ST|STS|3060ADL| |ADL-30ST-60|Straight Section 1|1|1|0|0|ADL-30ST|STS|3090ADL| |ADL-30ST-90|Straight Section 3|5|1|90|0|ADL-30T-60|HRT|3060ADL| |ADL-30T-60|Horizontal Tee 3|5|1|90|0|ADL-30T-90|HRT|3090ADL| |ADL-30T-90|Horizontal Tee

Update Reference Schema

Once created, the .unl files are input to the Update Reference Schema process which loads information in the <one-line type>_part and <one-line type>_spec tables. As described previously, the spec table contains all specifications, while the part table contains the relevant data for each of the fittings within a specification. For information about running Update Reference Schema, see Update Reference Schema in the section entitled Electrical Engineer (EE) Environment.

Sample Specification Tables

This section describes the required column names of sample specification tables, tray_spec and tray_part. tray_spec table Column Name vendor* ee_units* ee_dimension_1 ee_out_ht_diam ee_dimension_2 ee_out_width ee_extension Description the index_column (codelist) value from the vendor table. the index_column (codelist) value from the ee_units table. a dimension variable used by Eden. the outside height dimension in sub-units. a dimension variable used by Eden. the outside width dimension in sub-units. the fitting extension.

510

_ _______________
Appendix D: ee_transition ee_radius weight material ee_const_type ee_xs_cell ee_spec_key ee_description the fitting transition length. the fitting bend radius. the weight per unit length of the run. the tray material. the construction type. the cross section symbol. the unique tray specification key. the tray specification description.

Sample .unl Files

tray_part table Column Name ee_tl_type* ee_tl_subtype* ee_tl_qual* ee_angle ee_weight ee_part ee_symbol ee_spec_key ee_spec2_key ee_key ee_description Description the index_column value from the tl_type table. the index_column value from the tl_subtype table. the index_column value from the tl_qual table. the fitting turn angle. the tray part weight. the tray part catalog number. the Eden symbol. the tray specification key. the secondary tray specification key for reducers. the unique tray part key. the tray part description.

* For information about the codelist values, see the appendix entitled EE Databases .

D: Specs

511

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Available Fittings
The following is a list of the fittings currently supported by the EE Raceway Modeling product:

FITTING Straight Elbow Elbow Elbow Wye Wye Wye Cross Cross Reducer Reducer Reducer Conduit body Pullbox

TYPE

ANGLE

Horizontal Inside Vertical Outside Vertical Horizontal Vertical Reducer Horizontal Vertical Left Horizontal Right Horizontal Concentric

30,45,60,90, and Adjustable 30,45,60,90, and Adjustable 30,45,60,90, and Adjustable 90,45 left and 45 right 90 90 90 90

512

_ _______________
Appendix E:

Eden Symbol Generation

Appendix E

Eden Symbol Generation

Eden is a high-level symbol definition language (modeled after the FORTRAN programming language) that allows you to design your own symbols for raceway straight sections, fittings, and special parts (conduit bodies, pullboxes, etc.). You do not need a programming background to write Eden programs. However, you should be familiar with a standard ASCII editor like vi or emacs. You can write Eden code using whatever case conventions make it easiest for you to read. Eden provides drawing commands called primitives. Primitives allow you to construct complex symbols by using a combination of simple commands (place_line, draw_arc, etc.). For additional information about the Eden symbol language, see the PDS Eden Interface Reference Guide.

Symbol Processor File

A symbol processor file is the controlling function or logic used to produce the raceway straight sections, fittings, and special parts. The delivered symbol library is called eden.lib and resides in win32app\eerway\eden. The library and its path are defined using the EE Configure command. To review or modify the symbols in this library, use the delivered Eden processes. (See the chapter entitled Eden Processes for more information about running these processes.) Every Raceway symbol must contain a symbol processor definition and at least one of each of the following: Placepoint (EE attachment point) Datum point (EE RCP point) Graphical element

E: Eden Symbols

513

_ _______________
EE Raceway Modeling Reference Guide - February 2003 The best way to explain how a symbol processor file works is to show an example: Before creating an Eden symbol processor file, you should have consulted the PDS Eden Interface Reference Guide or have taken a course in Eden symbol generation.
========================================================================= ! ! Symbol Name: HEL ! ! Description: Horizontal Tray Elbow, with or without extensions. ! ========================================================================= SYMBOL_PROCESSOR HEL #DESC = Tray Horizontal Elbow r8 halfwid, height, radius, extension, angle, val1, val2, val3, val4, val5, val6 ! ! !

Get Dimensions Required to create the horizontal elbow.

angle height halfwid extension radius ORG BND1 BND2 EXT1 EXT2 ARC = = = = = = 19 20 21 22 23 24

= = = = =

DIMENSION[4] DIMENSION[21] DIMENSION[22] / 2.0 DIMENSION[23] DIMENSION[25]

NUMPTS = 4 If ( halfwid .eq. 0.0 .or. height .eq. 0.0 .or. angle .eq. 0.0) then Call ABORT ( 0 ) Endif Call Begin ( NOHOLE ) Call Begin ( SURFACE ) ! ! !

Add dimension of tray to radius

radius = radius + halfwid ! ! ! ! ! ! ! ! ! !

Calculate distances distance variables val1 val2 val3 val4 val5 val6 = = = = = = bendpoint on primary oneline primary distance to bendpoint on bent oneline secondary distance to bendpoint on bent oneline extension point on primary oneline primary distance to extpoint on bent oneline secondary distance to extpoint on bent oneline

514

_ _______________
Appendix E:
radius val1 = val2 = val3 = val4 = val5 = val6 = ! ! ! Call Call Call Call Call Call Call ! ! ! = radius + halfwid radius * DTAND( angle / 2.0 ) val1 * DSIND( angle ) val1 * DCOSD( angle ) val1 + extension val4 * DSIND( angle ) val4 * DCOSD( angle )

Eden Symbol Generation

Define bendpoints (point2 and point3) and bend origin (point4)

Define_Datum_Point( DP[1], Define_Point ( Point[ORG], Define_Point ( Point[BND1], Define_Point ( Point[BND2], Define_Point ( Point[EXT1], Define_Point ( Point[EXT2], Define_Point ( Point[ARC],

Point[0] ) Point[0], 0, 0, Point[0], -val1, 0, Point[0], val3, val2, Point[0], -val4, 0, Point[0], val6, val5, Point[0], -val1, radius,

0, 0, 0, 0, 0, 0,

0 0 0 0 0 0

) ) ) ) ) )

Define Placepoints

Call Define_Active_Point ( Point[EXT2] ) Call Define_Orientation_By_Points ( Point[ORG], Point[BND2], Point[ARC] ) Call Rotate_Orientation( 180.0, NORMAL ) Call Define_Placepoint ( PP2, Point[0] ) Call Define_Active_Point ( Point[EXT1] ) Call Define_Orientation_By_Points ( Point[BND1], Point[ORG], Point[BND2] ) Call Define_Placepoint ( PP1, Point[0] ) ! ! !

Define cross section points

Call Define_Active_Point ( Point[BND1] ) Call Call Call Call ! ! ! Define_Point Define_Point Define_Point Define_Point (Point[1], (Point[2], (Point[3], (Point[4], Point[0], Point[0], Point[0], Point[0], 0, halfwid, height, 0 ) 0, halfwid, 0, 0 ) 0, -halfwid, 0, 0 ) 0, -halfwid, height, 0 )

Draw First Extension

E: Eden Symbols

If ( extension .ne. 0 ) then Do i = 1, NUMPTS, 1 Call Define_Point( Point[NUMPTS+i], Point[i],-extension, 0, 0, 0) Enddo Call Draw_Complex_Surface ( 1, 0 ) Call Draw_Line_String ( NUMPTS, Point[1] ) Call Draw_Line_String ( NUMPTS, Point[NUMPTS+1] ) Call Draw_Complex_Surface ( -4, 0 ) Do i = 1, NUMPTS, 1 Call Draw_Line ( Point[i], Point[NUMPTS+i] ) Enddo Call Draw_Complex_Surface ( -99, 0 ) Endif

515

_ _______________
EE Raceway Modeling Reference Guide - February 2003
! ! ! Draw revolved shape Call Define_Orientation_By_Points(Point[1],Point[2],Point[3]) Call Define_Active_Point ( Point[ARC] ) Call Draw_Revolved_Shape ( EL_LINESTR, -angle, 1, Point[1], NUMPTS, 0 ) ! ! !

Draw Second Extension

If ( extension .ne. 0 ) then Call Define_Active_Point ( Point[BND2] ) Call Define_Orientation_By_Points(Point[ORG],Point[BND2],Point[ARC]) Call Call Call Call Define_Point Define_Point Define_Point Define_Point (Point[1], (Point[2], (Point[3], (Point[4], Point[0], Point[0], Point[0], Point[0], 0, halfwid, height, 0 ) 0, halfwid, 0, 0 ) 0, -halfwid, 0, 0 ) 0, -halfwid, height, 0 )

Do i = 1, NUMPTS, 1 Call Define_Point(Point[NUMPTS+i], Point[i], extension, 0, 0, 0) Enddo Call Call Call Call Draw_Complex_Surface ( 1, 0 ) Draw_Line_String ( NUMPTS, Point[1] ) Draw_Line_String ( NUMPTS, Point[NUMPTS+1] ) Draw_Complex_Surface ( -4, 0 )

Do i = 1, NUMPTS, 1 Call Draw_Line ( Point[i], Point[NUMPTS+i] ) Enddo Call Draw_Complex_Surface ( -99, 0 ) Endif Stop End

The first line of this file should always be:

SYMBOL_PROCESSOR <name>

The last two lines of the file should always be:

Stop End

This line defines the symbol name. When defining parts in the reference database, the name of the symbol should correspond with the ee_symbol in the part table. For more information see the description of databases in the Workflow and Procedures chapter.

516

_ _______________
Appendix E: The symbol in the example defines the symbol name as Tray Horizontal Elbow. The symbol derives the values for angle, height, width, extension, and radius from the global array DIMENSION. EE Raceway fills the DIMENSION array with values extracted from the reference database. For a description of which database columns are associated with what dimensions, see the table immediately following this description. EE Raceway uses a Datum Point to define the location of the RCP relative to the symbol. It uses Placepoints to define the point by which you can place a fitting using manual placement. In general, the one-line will pass through a placepoint on the symbol and will terminate at the RCP. The creation of the horizontal elbow symbol is fairly straightforward given a knowledge of Eden primitives. The RCP is defined in the active location with the active orientation, while other critical points are defined relative to the origin. Then the placepoints are defined at either end of the elbow. If the fitting has extensions, they are drawn as a surface of projection of a line string. The elbow is drawn as a surface of revolution.

Eden Symbol Generation

DIMENSIONS
The DIMENSION structure contains specific information that has been extracted from the database and passed through to Eden. For specification-driven parts, the structure is as follows: Dimension 1 2 3 4 11 What Three Line Type Three Line Subtype Three Line Qualifier Angle Length From Manual Placement Form or Calculated Manual Placement Form or Calculated Manual Placement Form or Calculated Manual Placement Form or Calculated Manual Placement Form or Calculated

These are from the specification table: 21 22 23 24 25 26 27 .. .. .. 50 Height Width Extension Transition Radius Dimension 1 Dimension 2 ........... ........... ........... Dimension 25 Spec Table - ee_out_ht_diam Spec Table - ee_out_wid Spec Table - ee_extension Spec Table - ee_transition Spec Table - ee_radius Spec Table - ee_dimension_1 Spec Table - ee_dimension_2 .......... .......... .......... Spec Table - ee_dimension_25

E: Eden Symbols

These are from the secondary specification (if one exists): 51 52 53 Height_2 Width_2 Extension_2 Spec Table - ee_out_ht_diam Spec Table - ee_out_wid Spec Table - ee_extension

517

_ _______________
EE Raceway Modeling Reference Guide - February 2003 54 55 56 57 .. .. .. 80 Transition_2 Radius_2 Dimension 1 Dimension 2 ........... ........... ........... Dimension 25 Spec Table - ee_transition Spec Table - ee_radius Spec Table - ee_dimension_1 Spec Table - ee_dimension_2 .......... .......... .......... Spec Table - ee_dimension_25

The following structure is used for special parts: Dimension 26 27 .. .. .. 80 What Dimension 1 Dimension 2 ........... ........... ........... Dimension 60 From Part Table - ee_dimension_1 Part Table - ee_dimension_2 .......... .......... .......... Part Table - ee_dimension_60

518

_ _______________
Appendix F:

EE File Structure

Appendix F

EE File Structure
F: File Structure

This section describes the file structure for EE Nucleus and EE Raceway. It also describes the contents of directories and some files. It identifies those files you can modify. By default, the PDS Component Loader delivers these files to \win32app\ingr. The directory tree for EENUC and EERWAY is shown below.

519

_ _______________
EE Raceway Modeling Reference Guide - February 2003

EE Nucleus File Structure

EE Nucleus (EE Nuc) is the core product for the EE product line. The product may reside on any file system. EE Nucleus will reside under the /usr#/ip32/eenuc directory. The list may differ slightly depending on which options are selected during installation. The following files exist under the ../eenuc directory: Any file followed by a slash (name/) is a directory. Any file followed by an asterisk (*) is an executable. /usr/ip32/eenuc:

/usr/ip32/eenuc/bin:

/usr/ip32/eenuc/bin/c100:

/usr/ip32/eenuc/config:

/usr/ip32/eenuc/data:

/usr/ip32/eenuc/db:

520

_ _______________
Appendix F: /usr/ip32/eenuc/doc: /usr/ip32/eenuc/forms:

EE Nucleus File Structure

F: File Structure

/usr/ip32/eenuc/msg:

/usr/ip32/eenuc/sym:

The following list gives a brief description of some of the files. The files are grouped by directory. eenuc/ README file containing description of product features and any fixes, problems, comments, etc. product.def product definition file. remove.sh shell script used by the remove utility in deltools used to remove EE Nucleus from the machine. .EErc File containing global symbol definitions. EEnotice.txt File containing release notices. legend copyright notice file. bin/ contains the EE shell script and the environment process. The EE shell script sets up variables specifying the location of MicroStation 32, INFORMIX, EE Nucleus, and EE WPD, and then invokes the EE environment. C100 for C100 executables or C400 for C400 executables.

521

_ _______________
EE Raceway Modeling Reference Guide - February 2003 background process that reports the exit status of a process run in the background. batch process that reports the exit status of a process run in batch mode. clip clears interprocess communication left after a process finishes. Also kills stray processes. create_db create database process. dba_rpt DBAccess report process. dba_shell shell executed around dba_rpt. EE Electrical Engineer environment shell script. EEmgr Electrical Enginner manager environment shell script. eemgr system manager environment process. eeprj environment process. eeqpr script to print 132 column reports to the laser printer. menu_shell shell executed around eemgr to run the Edit Database process. mount supports less disk installation. mscrecol.sh shell script to create mscolumns table for reference database. reeprj remote environment process. risql EE reporting utility. 132_header file to allow printing in 132 column format. infx_ol file used for compression of on-line INFORMIX databases. infxcompress file used for compression of standard engine databases. config/ Contains the file that assigns and exports any required variables. The file assigns MicroStation 32 variables, INFORMIX variables, and product variables. assign shell script that assigns and exports any required variables. This file can be edited. eeconfig file that maintains EE product configuration for workstation/server. data/ Contains the ASCII files used to control certain environment procedures. print.dat ASCII file for output file management.

522

_ _______________
Appendix F: manager.dat ASCII file for manager function management. dba* files DB Access files. ustn_tsk DB Access file. db/ directory that contains the DB Access menu library (mgrdba_lib). Required DBAccess files are also delivered in this directory. doc/ directory that contains documentation. lessd.txt less disk information. eepsp.txt EE project setup information. forms/ directory that contains all the environment forms. msg/ contains EE Nucleus message files. sym/ contains EE symbol files.

EE Nucleus File Structure

F: File Structure

523

_ _______________
EE Raceway Modeling Reference Guide - February 2003

EE Raceway File Structure

This section lists and describes the directories and files delivered with EE Raceway. /usr/ip32/eerway:

/usr/ip32/eerway/bin:

/usr/ip32/eerway/bin/c100:

/usr/ip32/eerway/cfg:

/usr/ip32/eerway/config:

/usr/ip32/eerway/data:

524

_ _______________
Appendix F: /usr/ip32/eerway/db:

EE Raceway File Structure

F: File Structure

/usr/ip32/eerway/dgn:

/usr/ip32/eerway/dgn/seed:

/usr/ip32/eerway/doc:

/usr/ip32/eerway/eden:

/usr/ip32/eerway/help_source:

525

_ _______________
EE Raceway Modeling Reference Guide - February 2003 /usr/ip32/eerway/help_source/help_graphics:

/usr/ip32/eerway/mdlapps:

/usr/ip32/eerway/menus:

/usr/ip32/eerway/msg:

/usr/ip32/eerway/report:

526

_ _______________
Appendix F: /usr/ip32/eerway/sym:

EE Raceway File Structure

F: File Structure

/usr/ip32/eerway/tmp: delivered empty

The following list gives a brief description of some of the files. The files are grouped by directory. eerway/ README file containing a description of the product features and any fixes, problems, comments, etc. product.def product definition file. remove.sh shell script used by the remove utility in deltools used to remove EE Raceway from the machine. bin/ contains all process delivered with the EE Raceway product. idet Interference Detection Envelope File Creation process. load processor to load the project database. rmon Controlling processor for interactive manipulations. unload_cln contains the unload sheet, unload drawing, and clean database processes. cfg/ Contains the application menu configuration files. menu.cfg EE Raceway menu configuration file. config/ Contains the file that defines and exports all variables required by EE Raceway and those MicroStation 32 variables required by EE Raceway. assign shell script that defines and exports any required variables. data/ Contains the ASCII files used to control process and report management for the EE Raceway product. These files can be modified.

527

_ _______________
EE Raceway Modeling Reference Guide - February 2003 eden.dat controls Eden processes. process.dat controls process management. report.dat controls standard report management. rule_chk.dat controls rule check report management. db/ Contains the delivered sql files for the project and reference database. Also contains .unl files required for bulk loading special tables and the mscatalog table in the project database. Sample .unl files for bulk loading reference database tables are also provided. dgn/ Contains the seed file directory, available cell libraries, and any design files delivered with the product. seed/ contains the available seed design files. seed.dgn delivered English drawing seed file. This may be customized. msseed.dgn delivered metric drawing seed file. This may be customized.

doc/ contains documentation information on EE Raceway including README files from previous releases. eden/ contains the Eden symbol library. eden.lib the Eden symbol library file. help_source/ contains the text and source files required to support on-line Help. help_rway.hp help pointer file. help_rway.s help source file. help_graphics contains the graphics used in on-line Help. mstr_rway.hp master help pointer file containing pointers to both MicroStation 32 and EE Raceway Help. mstr_rway.s master help source file. menus/ Contains the all menus (panel and bar) supporting the product. Also contains all symbol and icon files required to support delivered menus. You can supply additional menu files. rway.cmds command file for EE commands invoked by MicroMenu. Attaches the function bar menu, function key menu, and cell library. rway_bar bar menu for schematic commands.

528

_ _______________
Appendix F: merge_pnl/ directory containing the merged panel menu consisting of EE Raceway and MicroStation. merge_pnl panel menu file. rway.bar bar menu source file. rway.pnl panel menu source file. rway_pnl/ contains the rway_pnl binary menu files. rway_pnl panel menu palette file.

EE Raceway File Structure

F: File Structure

msg/ Contains EE Raceway message files and the file to correlate key-ins to EE Raceway commands. alias.cmd file used to correlate key-ins to commands. This file can be extended. command.msg message file containing all messages for the command field. These messages can be edited but messages can not be added. error.msg message file containing all error messages for the error field. These messages can be edited but messages can not be added. prompt.msg message file containing all messages for the prompt field. These messages can be edited but messages can not be added. rway_prj.tbl file containing the entity numbers for the project database tables. rway_ref.tbl file containing the entity numbers for the reference database tables. status.msg message file containing messages for status field, prompting messages, and logo. These messages can be edited but messages can not be added. report/ Contains the source (.ace)and compiled (.arc) SQL files for all delivered sch reports. The source files may be edited by the user. There is an .ace and an .arc file for each report listed below. rwaydba_lib DB Access template library. sym/ Contains all symbol files for EE Raceway menus. This directory also contains the available precision input forms. annot_form form file for annotation. rwaybar.sym symbol file for the bar menu. rwaypnl.sym symbol file for the panel menu. tmp/ Holds any temporary files. The software requires this directory.

529

_ _______________
EE Raceway Modeling Reference Guide - February 2003

530

_ _______________
Appendix G:

Customizing Environment Files

Appendix G

Customizing Environment Files

This appendix contains printouts of the following files as they are delivered with EE Raceway: File eden.dat process.dat report.dat rule_chk.dat print.dat manager.dat Location win32app\ingr\eerway\data win32app\ingr\eerway\data win32app\ingr\eerway\data win32app\ingr\eerway\data win32app\ingr\eenuc\data win32app\ingr\eenuc\data

G: Customizing Environment

process.dat, report.dat, rule_chk.dat, and print.dat control the scrolling lists for the Process, Report, Rule, and Output menus, respectively. You may want to write your own processes, reports or rule checks or change their names from what is delivered. This section describes the syntax needed to modify the scrolling list for the Process, Report, Rule, and Output. The manager.dat file controls the scrolling list for the options available through the system manager menu. You can add defaults to this screen by modifying the file.

eden.dat
#ident "@(#)Eden processes:eden.dat 13.1 0.0 (EE Raceway) 12/14/93" # # Note: No blanks lines allowed in this file. # # eden.dat # This file is stored under the %EE_RWAY%\data directory. # The syntax of this data file is : # # Title | Command Line | Prompt,Default,Path,Switch | , , ... # # The first column for a comment line must be the # character. # The \ is the line continuation character. # # The first field is the title which will appear on the scrolling list. # # The second field is a command line containing the name of the executable. # # The third field and each subsequent field will contain three sub-fields # using the comma (,) as the delimeter # # They are : # Prompt,Default,Path,Switch # The default can be a global symbol or file. # Any of the sub-fields in the third field can be omitted # # Change History: # Added the ability to list/extract user functions 31-May-95 # Compile EDEN Symbol | %EE_RWAY%\bin\eden.bat -c \ | Enter library name ,%EDEN_LIB%,, \ | Enter symbol source file ,,,\ | Enter option (-l=list or -o=insert),-O,, #

531

_ _______________
EE Raceway Modeling Reference Guide - February 2003
# # Delete EDEN Symbol | %EE_RWAY%\bin\eden.bat -d\ | Enter library name ,%EDEN_LIB%,, \ | Enter symbol name ,,, # # # List EDEN Symbol Library | %EE_RWAY%\bin\eden.bat -l \ | Enter library name ,%EDEN_LIB%,, # # # List EDEN User Functions | %EE_RWAY%\bin\eden.bat -u \ | Enter library name ,%EDEN_LIB%,, # # #Create Parameteric Help Library | %EE_RWAY%\bin\eden.bat -C \ # | Enter library name ,%EDEN_LIB%,, # # # Merge EDEN Symbol Libraries | %EE_RWAY%\bin\eden.bat -m \ | Merge into library name ,,, \ | Merge from library name ,,, # # # Compress EDEN Symbol Library | %EE_RWAY%\bin\eden.bat -s \ | Enter library name ,%EDEN_LIB%,, # # # Extract EDEN Symbol From Library| %EE_RWAY%\bin\eden.bat -e \ n | Enter library name ,%EDEN_LIB%,, \ \ ,,, | Enter symbol name d # e n # . Extract EDEN User Function From Library| %EE_RWAY%\bin\eden.bat -eu \ b | Enter library name ,%EDEN_LIB%,, \ a t ,,, | Enter symbol name # # E Edit EDEN Symbol File | %EE_RWAY% tor,notepad,, # # | E n t e r e d

| Enter symbol file name,,,

532

_ _______________
Appendix G:

process.dat

process.dat
#ident "@(#)data:process.dat 13.1 0.0 (EE Raceway) 12/14/93" # # Note: No blanks lines allowed in this file. # # process.dat # This file is stored under the %EE_SCH%\data directory. # The syntax of this data file is : # # Title | Command Line | Prompt,Default,Path,Switch | , , ... # # The first column for a comment line must be the # character. # The \ is the line continuation character. # # The first field is the title which will appear on the scrolling list. # # The second field is a command line containing the name of the executable. # # The third field and each subsequent field will contain three sub-fields # using the comma (,) as the delimeter # # They are : # Prompt,Default,Path,Switch # The default can be a global symbol or file. # Any of the sub-fields in the third field can be omitted # # NOTE: Many processes run off the project or reference schema (or both). # Two environment symbols have been set up for these schemas: EE_SCHEMA # for the project schema and EES_REFDB for the reference. These symbols # are exported by the EE environment when a project is entered. This was # done to handle schema passwords. The symbol is exported as # <schema_name>.<password> if a password is keyed in on the project form. # So, any customized processes written should read these symbols in the # process instead of passing them on the command line. The password will # have to be handled accordingly. # # Load Database | %EE_RWAY%\bin\load.exe \ | Enter design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-f # # # Unload Design | %EE_RWAY%\bin\unld_cln.exe \ | Enter design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-F # # Unload Sheet | %EE_RWAY%\bin\unld_cln.exe -s \ | Enter sheet,,, # # Cleanup database | %EE_RWAY%\bin\unld_cln.exe # # Create Interference Envelope (default name) | %EE_RWAY%\bin\idet.exe \ | Enter design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-f # # Create Interference Envelope (given name) | %EE_RWAY%\bin\idet.exe \ | Enter one design name,%RWAY_DGN%, %EE_CURPRJ%\rway\dgn,-f \ | Enter envelope name,,,-e

G: Customizing Environment

533

_ _______________
EE Raceway Modeling Reference Guide - February 2003

report.dat
#ident "@(#)data:report.dat 7.1 0.0 (EE Raceway) 6/1/92" # # Note: No blanks lines allowed in this file. # # report.dat # The syntax of this data file : # Title | Command Line | Report Name | Prompt,Default | , , ... # # The first field is the title which will appear on the scrolling list. # The second field is the command field. # The third field is the name of the report which can be a global symbol # or a file name. # The fourth field and each subsequent field will contain two sub-fields # using the comma (,) as the delimeter. # # They are: # Prompt,Default # The default can be a global symbol or file. # Any of the sub_fields in the third field can be omitted. # # Project drawing list | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \ | drwlst \ | Enter project schema,%EE_SCHEMA% # # Material takeoff report | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \ | mto_rpt \ | Enter project schema,%EE_SCHEMA% # # Raceway bill of materials report| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \ | rway_bom \ | Enter project schema,%EE_SCHEMA% # # Raceway bill of materials by volume| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \ | rway_bom_v \ | Enter project schema,%EE_SCHEMA% \ | Enter low range (PDS coordinates: east north elev) \ | Enter high range (PDS coordinates: east north elev) # # Raceway Conduit Body report| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib dummy %EE_RPTDB% \ | cond_body \ | Enter Reference schema,%EES_REFDB% # #

534

_ _______________
Appendix G:

rule_chk.dat

rule_chk.dat
#ident "@(#)data:rule_chk.dat 13.1 0.0 (EE Raceway) 12/14/93" # # Note: No blanks lines allowed in this file. # # rule_chk.dat # The syntax of this data file is : # Title | Command Line | Report Name | Prompt, Default | , , ... # # The first field is the title which will appear on the scrolling list. # The second field is the command field. # The third field is the report name which can be a global symbol or file. # The fourth field and each subsequent field will contain two sub-fields # using the comma (,) as the delimiter # # They are: Prompt,Default # The default can be a global symbol or file. # Any of the sub_fields in the third field can be omitted. # # Material takeoff blank part IDs | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \ | blank_ids \ | Enter project schema,%EE_SCHEMA% # #

G: Customizing Environment

535

_ _______________
EE Raceway Modeling Reference Guide - February 2003

print.dat
#ident "@(#)env_data:print.dat 21.1 0.0 (EE Schematic) 3/9/94" # # Note: No blanks lines allowed in this file. # # print.dat # This file is stored under %EE_NUC%\data directory. # The first column of comment line must be #. # The syntax of this data file is : # TITLE | COMMAND | PROMPT,DEFAULT,PATH,SWITCH... # The titles are the messages on the scrolling list. # The command can be any command to output a file. # The third field is made up of four parts: prompt,default,path and switch. # (The path is not relevant). This field should be used to pass # information to the command. A file name is automatically appended to # the command as the last parameter. # TO SCREEN| SCREEN # # Local line printer # Local Printer| lp # # NQS print command to print to a laser printer # Laser Printer 80 columns | qpr -t text\ | Enter queue name,,,-q # Laser Printer 132 columns | %EE_NUC%\bin\eeqpr \ | Enter queue name,,, # # This is an example of a way to print to a VAX. The command "vaxprint" # could be a shell script or an exported shell function. # #VAX Line Printer| vaxprint #

536

_ _______________
Appendix G:

manager.dat

manager.dat
#ident "@(#)env:manager.dat 21.1 0.0 (EE Nucleus) 3/9/94" # # Note: No blanks lines allowed in this file. # # manager.dat # This file is stored under the %EE_NUC%\data directory. # The syntax of this data file is : # # Title | Command Line | Prompt,Default,Path,Switch | , , ... # # The first column for a comment line must be the # character. # The \ is the line continuation character. # # The first field is the title which will appear on the scrolling list. # # The second field is a command line containing the name of the executable. # # The third field and each subsequent field will contain three sub-fields # using the comma (,) as the delimeter n # # They are : b # Prompt,Default,Path,Switch a # The default can be a global symbol or file. _ # Any of the sub-fields r in the third field can be omitted p # t # . Edit database | %EE_NUC%etnt -l %EE_NUC%\db\mgrdba_lib \ | Enter x schema name,,, -s e # # m #Compress database - INFORMIX SE | vterm -x %EE_NUC%\bin\infxcompress -T compress # d # b e #Compress database - INFORMIX Online | vterm -x %EE_NUC%\bin\infx_ol -T compress d # Create mscolumns table | %EE_NUC%\bin\mscrecol.cmd \ |Enter schema name,,,

G: Customizing Environment

537

_ _______________
EE Raceway Modeling Reference Guide - February 2003

538

_ _______________
Appendix H:

alias.cmd file

Appendix H alias.cmd file

This appendix contains a description and printout of the alias.cmd file. The alias.cmd file is an ASCII file located in win32app\ingr\eerway\msg. You can use any text editor to modify the file. The alias.cmd file contains instructions for adding an entry, the format of such an entry, a sample entry, and a list of EE Raceway command names and the hard-code for each command. The example in the alias.cmd file explains how to create an alias for a particular command. To the left of the equal sign (=) in this example is the user-definable alias key-in name. The fixed (hard-coded) command name is to the right of the equal sign. If you were to add this example to the alias.cmd file, then the key-in EERWAY Remove Element would invoke the command EERWAY Delete Element, just as would the key-in EERWAY Delete Element. You do not need to add entries to the alias.cmd file; the command name key-ins in the file will invoke the commands to which they correspond. You need to key in just enough of the key-in name to make it unique. For example, if the sample alias entry (in the file below) were added to alias.cmd, you would need only to key in r e to invoke the command. Since the EE Raceway software has a reserved set of names for each Raceway command which are hard-coded into the EE Raceway software, any alias you add to this file must not match any of the command name key-ins or hard-coded names listed below.

H: alias.cmd file

The following is a print-out of the alias.cmd file (the # symbols indicate comment lines):
#ident "@(#)rdmsg:alias.cmd # # # # # # # # # # # # # # # # # # # # # # # 13.1 0.0 (EE Raceway) 12/14/93"

To create an alias for an EE Raceway command add an entry to this file consisting of the alas and the hardcode for that command in the following format: <alias> = <hardcode> The list of possible hardcodes follows: Command Name EERWAY Active OLT Parameters EERWAY Add System Group EERWAY Annotate Element EERWAY Annotate Group EERWAY Annotate Title Block EERWAY Clone Element EERWAY Clone Group EERWAY Conduit Sizing EERWAY Copy Element EERWAY Copy Group EERWAY Create Cell EERWAY Delete Coincident RCPs EERWAY Define Duct Cross Section Hardcode rwp addsysg annotate anntgrp anntblk clone cloneg rtwform cpele cpeleg crecell coinrcp ductform

539

_ _______________
EE Raceway Modeling Reference Guide - February 2003
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY EERWAY Delete Duplicate One Lines Delete Element Delete Group Delete Title Block Design Parameters Display Element Info Display Entity and Mslink Display Fitting Info Display Run Info Display Sector and Word Display System and OLT Display Type and Asid Edit Manual Fitting Exit Fitting Environment Element Fitting Environment Group Group Control Highlight Asid Highlight Entity and Mslink Highlight Graphic Group Highlight Propagation Errors Highlight Sector and Word Highlight System Elements Insert One Line Vertex Insert RCP Levels Control Load Database Minimize Joints Minimize Joints Group Modify One Line Move Element Move One Line Segment Move One Line Vertex Move Title Block OLT Definition Place Drop Point Place Equipment Pointer Place Manual Fitting Place One Line Place Title Block Propagate Element Propagate Group Propagation Control Remove Fitting Remove One Line Vertex Remove RCP Replace System Group Rotate Cross Section Route Around Vessel Run Reports Run Rule Checks Set Active OLT Set Active OLT Parameters Set Active Point Set Active System Set Conduit Sizing Attributes Set Symbology Control Symbology Control System Definition Text Defaults Toggle Spider Display dupols dltele dlteleg dlttblk ueleform eleinfo prtrlnk tlfinfo runinfo prtsw prtsysol prtasid manedit rexit rulefit rulefitg grpform hiasid hirlnk higg hiprerr hisw hisys insolvert addrcp levels loaddb minjnt minjntg modol mvele mvolseg mvolvert mvtblk oltdef plcdpnt plctoeqp manform plcol plctblk prjele prjeleg propform rmfit rmolvert rmrcp repsysg rotcs rtvess runrpt runrul actolt setact actpnt actsys setcsa setgsc symbform sysdef txtdef togspider

540

_ _______________
Appendix H:
# # example: EERWAY Remove Element = dltele

alias.cmd file

H: alias.cmd file

541

_ _______________
EE Raceway Modeling Reference Guide - February 2003

542

_ _______________
Appendix I:

rway.cmd

Appendix I

rway.cmd

The file rway.cmd is the MicroMenu (umenu) command file that is used to attach the EE Raceway menus. It is run automatically when you enter the EE Raceway environment. This file is located in the directory path win32app\eerway\db and activates the rway.ammfile. If you do not want the rway.cmd file to be executed, you can comment out the export variable RWAY_CMD using the EE Configure command. The rway.cmd file may also be edited by the user. MicroStation reads this file and processes the commands as if keyed in by the user. You can disable any of these features by commenting out the line(s) that enable the feature. (Place a pound sign (#) in front of any line you do not want executed.) Below is the file as it is delivered in the product directory:
m,prAttaching EE Raceway Menus... add mmenus ee_rway:menu.cfg active mmenus ee_rway:rway.amm m,pr

I: rway.cmds

543

_ _______________
EE Raceway Modeling Reference Guide - February 2003

544

_ _______________
Appendix J:

Reports

Appendix J

Reports

This section describes each report delivered with EE Raceway. It specifies the attributes used in the report and describes some of the internal operation behind report generation. This information will be helpful if you want to use a delivered report as a template for a customized report. The EE Raceway reports report on the project database, the reference database and, in some cases, both. All EE Raceway reports are currently written for RIS-DBACCESS. Documentation explaining how to create and compile customized reports with RIS-DB ACCESS is available in the DB ACCESS Reference Guide, the Project Data View Reference Guide, and the RIS Report-Writer Reference Guide. All EE Raceway reports are compatible for use with either RIS Report-Writer (RISRPT) or DB Access (DBA).

RIS Report Processing

A report processor is provided with EE Raceway to run RIS-based reports. Report templates created through DB Access, RIS Dataview or RIS Report Writer are all supported by this processor. Any RISsupported relational database, either local or remote, is supported. Usage: dba_rpt [-?] -s <schema> -l<template library> [-t<template>|-M<menu template>] -w<where clause> -o<output file> -S<schema list> [-F<database find>] [wtr_p0]...[wtr_p5] [-?] -s <schema name> Returns a usage statement like the one listed above. This is the name of any current RIS schema, It is used as a "default" schema to enter DB Access. It doesnt have to be the schema your report is running off of. This is the library of templates created to run reports from. Created through DB Access, Project Dataview, or RIS Report-Writer this is your report source code, layout, and print conditions. The name of the report you wish to run from your report template library. The name of the menu you wish to run from your menu template library. Used to restrict the report output to a certain type of condition, i.e. "where name = joe smith and number = 32".

J: Reports

-l <template library>

-t <report template>

-M <menu template>

-w <where clause>

545

_ _______________
EE Raceway Modeling Reference Guide - February 2003 -o <output filename> All reports have a hardcoded, default file name that they write to. If you wish to override this name, the "-o" option can be used. (The current standard is that the output filename be the same as the template name, with a ".rpt" added to the end.) This is the list of schemas your report actually runs through. * selects one character string from the database based on the select statement entered (i.e. "select value_a from table_b where....") and places the result into the third parameter (wtr_p2)) These are parameters that can be passed to a report template, and referenced by the literal string "wtr_p0"... The first parameter is read into wtr_p0, etc. up to a maximum of six parameters (wtr_p5). -S <schema list> -F <database find>

[wtr_p0]...[wtr_p5]

When you create a template, and use a schema from the schema list, whatever that schemas position was in that list (first, second, third, etc.) the report template will look at the schema in that same position when it is executed. Thus, be careful of how your list looks before you develop a report template. Certain variables may be exported, and will be picked up as defaults if switches are not used. They are: DBA_SCHEMA (the "-s schema". A default schema used to enter RIS) DBA_SCHEMA_LIST (schema list the report runs off of) * DBA_LIB (the report template library) It is useful to export these variables before entering DB Access, RIS Dataview or RIS Report-Writer to create or alter existing templates. * (The schemas in this list need to be in the same order as they were in DBA_SCHEMA_LIST when the report was originally developed. The correct order is <project schema> <reference schema>, since all EE Raceway reports were developed with the project schema listed first and the reference schema listed second. Example: "-S prj_schema ref_schema".)

546

_ _______________
Appendix J:

Project Drawing List (drwlst)

Project Drawing List (drwlst)

This report lists all drawings currently loaded in the project database, and sorts them by sheet name.

Information Output:
Drawing. drawing_type, filename, sheet, load_date, ref_db.

Sorted by (Highest to lowest priority)

drawing.sheet

Associated Software/Files
1. 2. Project Database drwlst (RIS) - a template in the $EE_RWAY/report/rwaydba_lib template library data file. This file: Selects the desired database tables; Selects the desired columns from those tables; Sorts the information according to given sort parameters and; Formats information into readable form. 3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_lib drwlst template.

J: Reports

547

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Material Takeoff Report (mto_rpt)

This report outputs information from both the straight and the fitting tables, and outputs the related system name for the particular straight or fitting.

Information Output:
System. system_name Straight. ee_ol_type, ee_tl_length, ee_out_width, ee_out_ht_diam, ee_part, description Fitting. ee_ol_type, ee_tl_type, ee_tl_subtype, ee_out_width, ee_out_ht_diam, ee_part

Associated Software/Files
1. 2. Project Database mto_rpt - a template in the $EE_RWAY/report/rwaydba_lib template library data file. This file: Selects the desired database tables; Selects the desired columns from those tables; Sorts the information according to given sort parameters and; Formats information into readable form. 3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_lib mto_rpt template.

548

_ _______________
Appendix J:

Raceway Bill of Materials Report (rway_bom)

Raceway Bill of Materials Report (rway_bom)

This report adds the length of the straight sections for each part ID, and outputs the number of fittings for each part ID. For flexible conduit elbow fittings, the length of the elbows is added to the straight sections.

Information Output:
Straight. ee_ol_type, ee_tl_length, ee_out_width, ee_out_ht_diam, ee_part, description Fitting. ee_ol_type, ee_tl_type, ee_tl_subtype, ee_out_width, ee_out_ht_diam, ee_part

Associated Software/Files
1. 2. Project Database rway_bom - a template in the $EE_RWAY/report/rwaydba_lib template library data file. This file: Selects the desired database tables; Selects the desired columns from those tables; Sorts the information according to given sort parameters and; Formats information into readable form. 3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_lib rway_bom template.

J: Reports

549

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Raceway Bill of Materials by Volume Report (rway_bom_vol)

This report adds the length of the straight sections for each part ID, and outputs the number of fittings for each part ID. For flexible conduit elbow fittings, the length of the elbows is added to the straight sections. The output is only for a specified volume from the input parameters.

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.

550

Appendix J:

_ _______________

Raceway Bill of Materials by Volume Report (rway_bom_vol)

Information Output:
Straight. ee_ol_type, ee_tl_length, ee_out_width, ee_out_ht_diam, ee_part, description Fitting. ee_ol_type, ee_tl_type, ee_tl_subtype, ee_out_width, ee_out_ht_diam, ee_part

Associated Software/Files
1. 2. Project Database rway_bom_vol - a template in the $EE_RWAY/report/rwaydba_lib template library data file. This file: Selects the desired database tables; Selects the desired columns from those tables; Sorts the information according to given sort parameters and; Formats information into readable form. 3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_lib rway_bom_vol template.

J: Reports

551

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Raceway Blank Part IDs (blank_ids)

This report outputs information from both the straight and the fitting tables whose part id (ee_part) information is blank, and outputs the related system name for the particular straight or fitting.

Information Output:
System. system_name Straight. ee_ol_type, ee_tl_length, ee_out_width, ee_out_ht_diam, ee_part, description Fitting. ee_ol_type, ee_tl_type, ee_tl_subtype, ee_out_width, ee_out_ht_diam, ee_part

Associated Software/Files
1. 2. Project Database blank_ids - a template in the $EE_RWAY/report/rwaydba_lib template library data file. This file: Selects the desired database tables; Selects the desired columns from those tables; Sorts the information according to given sort parameters and; Formats information into readable form. 3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the $EE_RWAY/report/rwaydba_lib blank_ids template.

552

_ _______________
Appendix K:

RIS Schema Manager

Appendix K RIS Schema Manager

K: RIS Schema Mgr.
The RIS Schema Manager is a stand-alone utility for creating, changing, and dropping RIS schemas. It can also be used to display information about any existing schemas. You can access RIS Schema Manager from EE Database Utilities or by clicking Start > Programs > RIS version number > RIS Schema Manager. This form consists of a list of all the schemas known to RIS and several buttons corresponding to the actions of the Schema Manager. If you select any of the buttons, RIS initiates that particular action by displaying one of the forms defined below. If you select one of the schemas in the list, then information about that schema is displayed. When you select Reset, any active secondary forms are erased, and the RIS Schema Manager rereads the risschema file. When you select Cancel (X), RIS Schema Manager terminates. For more detailed information on the RIS Schema Manager, refer to the Relational Interface System (RIS) Reference Guide.

553

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Schema Information Form

This form is, with the exception of the Schema Name field, a read only form. It reads information about existing schemas. You can specify a schema in two ways: either by keying in the schema name in the Schema Name field, or by choosing a schema from the list on the RIS Schema Manager form. Selecting Cancel (X) exits the Schema Information form.

554

_ _______________
Appendix K:

Create Schema Form

Create Schema Form

K: RIS Schema Mgr.
This form creates new RIS schemas, and corresponds directly to the RIS create schema statement. You can enter database-specific information on the Create Schema form using one of three methods: 1. Key in all information in the input fields. This is your only alternative if the schema is created on a database which is unknown to RIS. Select an existing schema on the RIS Schema Manager form. The database-specific information about that schema is entered in the Create Schema input fields. This method is particularly convenient when creating additional schemas for a database. Select the Display Databases button. A form listing all the known RIS databases is displayed. If you select one of the databases, information about that database is entered into the Create Schema input fields.

2.

3.

Selecting the Local Machine button fills the Node Address field with the addresses of the local machine. Selecting the Force button forces the system to create the schema despite corrupted data or other errors it may encounter. To change the order of the Network Protocol fields, select one of the Network Protocol fields; its value will be replaced with the value of the field below it. The value you selected originally moves to the bottom of the list. If the selected database type requires additional information, input fields for that information display. Once you have entered all necessary information, select Run to create the schema. Selecting Reset clears all input fields on the form. Selecting Cancel (X) exits the form.

555

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Drop Schema Form

This form drops RIS schemas. To select a schema to drop, either enter the schema name in the Schema Name field, or select a schema from the list on the RIS Schema Manager form. Selecting Run drops the schema, while selecting Reset clears all the fields on the form. Selecting Cancel (X) exits the form.

Alter Schema Form

This form performs three functions: it modifies the schema password, the user password, and the schema node. When you select one of these options, only those gadgets associated with the action are enabled. To select the schema to be altered, either enter the schema name in the Schema Name field, or select a schema from the list on the RIS Schema Manager form. You must enter both the original and new passwords to modify the schema password. To modify the user password, you need only to enter the new password. To modify the schema node, enter the new addresses in the Node Address fields. This action can also be used to change the order of the fields or to change the order of the protocols. When you have entered all necessary information, select Run to alter the schema. Selecting Reset clears all the fields on the form. Selecting Cancel (X) exits the form.

556

_ _______________
Appendix K:

Data Definition Form

Data Definition Form

K: RIS Schema Mgr.
This form consists of a list of all the tables, views, and indexes defined for the schema specified in the schema name field. The form buttons represent the data definition actions of the Schema Manager. Selecting any of these buttons initiates an action, and displays one of the subforms defined in following sections. If the selected schema requires a password, then you must enter it before the subforms (Create Table, Drop Table, and Alter Table) will accept input. Selecting Reset cancels any subforms, and clears the list. Selecting Cancel (X) exits the Data Definition form.

Table Information Form

This form displays the definition of the specified table. The column position, column name, column type, and whether or not nulls are allowed in the column are displayed for each column in the table. You can specify a table either by keying in the table name in the Table Name field, or by choosing the table from the list on the Data Definition form. A field to search for a specific column is also provided. Selecting Cancel (X) exits the Table Information form.

557

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Create Table Form

This form creates tables in the schema specified on the Data Definition form.

If the name of an existing table is entered into the Table Name field, or chosen from the list on the Data Definition form, the definition of that table will be loaded into the Create Table form. This can be useful when creating several similar tables. This form has two sets of Control buttons. There is the usual set, in the upper right corner of the form, which behaves as expected. Then there is the second set, referred to as the Mode Control buttons, which is used to execute and reset the different modes of the form. The Create Table operates in three modes which are represented by the three buttons: Insert Column, Drop Column, and Modify Column. These three buttons place the form in a particular mode, while choosing the Mode Run button actually causes the action to take place. Selecting the Mode Reset button clears the form mode. In Insert Column Mode, new columns can be added to the table definition. If a column is chosen in the table definition list, the new column is inserted in front of the chosen column. Otherwise the new column is appended to the list. Select the Mode Run button to insert the column. In Drop Column Mode, columns can be dropped from the table definition. The column to be dropped must be specified by keying in the column name in the Column Name Search field, or by selecting the column in the table definition list. Select the Mode Run button to drop the column. In Modify Column Mode, column definitions can be modified. The column to be modified must be specified by keying in the column name in the Column Name Search field, or by selecting the column in the table definition list. Select the Mode Run button to modify the column. Once the table definition is complete, select Run to create the table. Select Reset to clear the form. Select Cancel (X) to exit the form. The Create Table form is used only to create new tables. It cannot be used to modify existing tables. The ability to load existing table definitions into the form exists just to provide a template or starting point for a new table.

558

_ _______________
Appendix K:

Create Table Form

Drop Table Form

This form drops tables in the schema specified on the Data Definition form. The table to be dropped can be specified by keying in the table name in the Table Name field or by selecting the table from the list on the Data Definition form. Selecting Run drops the table. Selecting Reset clears the form. Selecting Cancel (X) exits the form.

K: RIS Schema Mgr.

Alter Table Form

This form alters existing tables in the schema specified on the Data Definition form. This form behaves in the same way as the RIS Alter Table command. It can only append one new column to an existing table. Once the new column is defined, select Run to alter the table. Selecting Reset clears the form. Selecting Cancel (X) exits the form.

559

_ _______________
EE Raceway Modeling Reference Guide - February 2003

Schema File Form

This form locates the risschema file that you are using on the network. Additionally, it provides a Checksum Schema File option, an error-checking mechanism that ensures that the data EE reads from a remote risschema file is correct. Selecting Reset clears the form. Selecting Cancel (X) exits the form.

Set Form
This form allows you to toggle the database mode ANSI setting on and off, and it also allows you to specify which RDBMS(s) your schemas can use. Selecting Reset clears the form settings. Selecting Cancel (X) exits the form.

560

_ _______________
Appendix L:

RIS Schema Definition File

Appendix L

RIS Schema Definition File

The RIS schema definition file maintains all schema definitions known to RIS. It is stored in a central location on the network and is used by all RIS client programs to ensure that all RIS clients use the same set of schema definitions. Although you can use multiple files, it is still advisable to use only one schema file. Multiple files often result in a large number of inconsistencies. Access to the schema file is controlled by the presence of another file. This file is the schema lock file. The name of the schema lock file is the same as the schema file with the addition of the .LCK extension. The schema file is accessible only if the schema lock file exists. If the lock file does not exist, then the schema file is in use. Sometimes when RIS is abnormally terminated, the schema lock file is not replaced as it should be. In these cases, the lock file must be replaced manually. The location of the schema definition file must be in the ris/parameters file on the client machine. The parameters file describes the network address and filename of the schema definition file. The locate schfile command in the interactive utility can be used to put the appropriate entry in the parameters file. If there is no network address given, the schema definition file will be created or used on the local machine. If the filename is not a full pathname, RIS will look for the file in the directory where RIS was installed on the given machine. The parameters file is shipped with a default schema definition file specification, referencing the file risschema in the directory where RIS was installed. The schema definition file consists of database and schema entries which are associated by a DBID (database ID) key value. There can be multiple schema entries for each database entry. A line separates entries. Here is a description of the fields in the schema definition file: DBID DTYPE DBNAME PARMS PROTOCOL The database ID; a unique key to identify the database The database type; currently supported values are X for Informix, I for Ingres, O for Oracle, and D for DB2 The database name as in the create schema statement. It must be a name or pathname as required by the dbms. The values found in the create schema option clause. The communication protocol to be used to communicate with the database. Currently supported values are X for XNS, T for TCP/IP, D for DNP (DECnet), L for LU6.2 The network address (must be an address, not a name) The name of the schema The database user name The database user password (encrypted)

L: Schema Definition

NETADDR SCHNAME USR USRPASS

561

_ _______________
EE Raceway Modeling Reference Guide - February 2003 ARCH OS ENV The system architecture that the RIS/DBMS runs on. This value is case-sensitive. The valid value is s370 and the default value is s370. The operating system that the RIS/DBMS uses. This value is case-sensitive. The valid value is mvs and the default value is mvs. The environment that the RIS/DBMS uses. This value is case-sensitive. The valid value is cics and the default value is cics. The network protocol that RIS uses to get to the IBM machine where the DBMS resides. This value is case-sensitive. The valid value is lu6.2 and the default value is lu6.2. the name of the Clipper System Administrator assigned to the logical unit that allows communication to the RIS program on the IBM machine. There are two logical units, one on the Clipper, the other on the IBM. The LU names are generated when RIS is installed. This value is case-sensitive. The name the Clipper System Administrator assigned to the mode that allows communication to the RIS program on the IBM machine. The name the IBM System Administrator called the RIS server when it was installed on the IBM, the CICS transaction name.

NET_PROTOCOL

RIS_LU or HOST_LU

MODE

HOST_PROGRAM

A schema file must be readable and writable by all users. All users must be able to create and delete files in the directory where the schema file is located. Following is a sample schema definition file:
CHECKSUM:1249378903 TIMESTAMP:728930074 DBID=2 DTYPE=X DBNAME=/usr/ee/sample_ref PROTOCOL=X NETADDR=0001349b.08-00-36-32-e4-00 PROTOCOL=T NETADDR=129.135.142.155 PROTOCOL= NETADDR= PROTOCOL= NETADDR= DIR=/usr/informix SQLEXEC= DBTEMP= TBCONFIG= DBID=1 DTYPE=X DBNAME=/usr/ee/sample PROTOCOL=X NETADDR=0001349b.08-00-36-32-e4-00 PROTOCOL=T NETADDR=129.135.142.155 PROTOCOL=

562

_ _______________
Appendix L:
NETADDR= PROTOCOL= NETADDR= DIR=/usr/informix SQLEXEC= DBTEMP= TBCONFIG= SCHNAME=sample_ref USR=ee USRPASS=pz_-!=%#oa/#@?%qHt%h&jXJ2vj(tyeY%i)pV BEGIN_GRANTEES END_GRANTEES DBID=2 SCHNAME=sample USR=ee USRPASS=<j8,H:.zW%wU5yg)U:IeK9tGB6R@Ezn:>k BEGIN_GRANTEES END_GRANTEES DBID=1

RIS Schema Definition File

L: Schema Definition

Note that there is a list of protocols in the database entry. This allows for additional protocols in the future. Currently, only the first protocol in the list will be used. All these entries are created by the create schema statement. If the file is corrupted or removed, they can be recreated by reissuing the create schema statements.

563

_ _______________
EE Raceway Modeling Reference Guide - February 2003

564

_ _______________
Appendix M:

EE Manager

Appendix M EE Manager
EE Manager is an environment created specifically for system manager functions. It is a process separate from the EE environment and should only be run by a system manager or by someone who has a working knowledge of the overall EE system. To run EE Manager, the environment variable SYS_PASSW_FILE must be set to a complete path of a password file. For detailed information on setting environment variables, see Appendix N.
SYS_PASSW_FILE=d:\users\EEpasswd

where \users is the path and \EEpasswd is the password file name. The password file will be created the first time you enter EE Manager using the file name you specified. Make sure the directory path to the password file exists. Once SYS_PASSW_FILE is set, double click on the EE Manager icon to display the Verify Password form.

M: EE Manager

EE Manager will prompt you for a password and, if you are entering the environment for the first time, will prompt you to re-enter the password for verification. Once you have successfully entered your password, the EE Manager form displays:

565

_ _______________
EE Raceway Modeling Reference Guide - February 2003

The password can be a maximum of 8 characters and is not case sensitive.

In this Appendix
Edit Database edits any schema that exists in the RIS dictionary. It uses DB Access to query and edit tables, delete rows, and update rows.

566

_ _______________
Appendix M:

Database Edit Functions

Database Edit Functions

To enter the Database Edit environment, select and confirm the Edit database option from the System Manager menu.

M: EE Manager

Buttons at the bottom of the Database Edit form provide functions for manipulating the attached relational database. These buttons include various Query functions, which allow you to search the database, and functions which enable you to change, delete, and insert a row or group of rows. A group of rows that match the current "query" criteria is called a universe. A universe is located by selecting Process Query in the Database Edit environment.

Field Descriptions
Initialize Query Initializes (clears) the current find criteria. Edit Query Displays the Edit Query screen, which shows the current find criteria. From this screen you can edit the current find criteria, save the current find criteria as a file to the attached library, or load find criteria from a file in the attached library. Current Row Controls the display of rows in the current universe. Select the arrows to move forward and backward through the rows in the universe. To go directly to a certain row, place the screen cursor on the slide bar button, press and hold the middle button on the mouse and drag the button. The number on the button changes to reflect the row. Release the mouse button to display the row. You can place the screen cursor at any point along the slide bar and press <D> to move the slide bar button directly to a new row, or edit the value displayed in the field. Process Query Searches the database to find all rows of the current table that meet the find criteria. If no find criteria exist, this command finds all rows in the current table.

567

_ _______________
EE Raceway Modeling Reference Guide - February 2003 Review Generates a formatted column-by-column listing of the current universe. You can generate a review for all rows with database linkages to graphic elements within a fenced area in a design file. Update Active Lets you enter data without changing the displayed row in the database. When you select Update Active, you can enter data on the displayed row without changing the database. When you are certain the data is correct, you can use the Insert Row command to add the displayed data as a row to the database. You can also use the Update Active command to enter information for a new row when attaching new linkages in graphics. Fields On/Off Toggles all column fields ON or OFF. You can toggle individual fields ON or OFF by selecting the fields corresponding column name on the Database Edit screen. Add Query Used with the AND/OR toggle and relational operators to establish find criteria. Selecting Add Query puts the screen in Add Query mode. As long as this command is active, any key-in in the screen menu is added as find criteria and is NOT made as a change in the database. Relational Operators let you search for ranges of column values such as greater than and less than. The field under the AND/OR toggle lets you edit the active relational operator. You can either edit the displayed value or select the right side of the field (a small box with dashes). A box containing a list of the various relational operators displays. You can select a relational operator from the list to make it the active relational operator. The following are the available relational operators: = != < > <= >= !! : equal to (default) : not equal to : less than : greater than : less than or equal to : greater than or equal to : substring search

The AND/OR toggle lets you establish either a logical AND or OR operation. AND finds any rows that contain both the previous find criteria and any current column value you specify. OR finds any row that contains either the previous find criteria or any current column value you specify. Multiple column searches are processed in order, with logical AND having precedence over logical OR. Change All Changes the value for one or multiple columns for all rows in the current universe. Change Row Activates the Change Row mode, which overrides the key-in mode for Key Columns, Add Query columns, and Update Active fields. Fields with these key-in modes are placed only when you customize a screen menu. By default, the Database Edit screen has only Change Row fields. Insert Row Inserts a new row based on the column values for the displayed row. Insert Row will not create a new row if a column is a SERIAL column (INFORMIX) or if it has a UNIQUE INDEX and a displayed column value duplicates the value for an existing row. You can use the Update Active command to enter the column values you want for a row and then Insert Row to create a row with the displayed information. Delete All Deletes all rows in the current universe from the database upon user verification.

568

_ _______________
Appendix M: Delete Row Deletes the displayed row from the database upon user verification.

Database Edit Functions

M: EE Manager

569

_ _______________
EE Raceway Modeling Reference Guide - February 2003

570

_ _______________
Appendix N:

EE Configure

Appendix N EE Configure
EE Configure is a process created specifically for setting environment variables for EE Raceway on a Windows NT platform. This process is separate from EE Environment and allows changes to the value of a variable in the ee.cfg file. Double-click on the EE Config icon to display the Configure EE Environment form.

Field Descriptions
Enter the EE File Name The field below this label contains the complete path and filename where the current configuration file ee.cfg is located.

N: EE Configure

User Environment Variables The list below this label contains the list of all the environment variables along with their path. Variable The field next to this label displays the Environment Variable name when any row is selected in the list menu. Value The field next to this label displays the value of the Environment Variable when any row is selected in the list menu. Descrip The field next to this label displays the description associated with the selected Environment Variable. Set The Set button writes the corresponding variable and its value to the list. Delete The Delete button deletes the corresponding variable and its value from the list. Reset The Reset button writes the contents of the ee.cfg file to the list.

571

_ _______________
EE Raceway Modeling Reference Guide - February 2003 Browse The Browse button lets you select the required ee.cfg file.

Steps
1. Double click on the EE Configure icon, the Configure EE Environment form displays the list of user environment variables and their corresponding value. Select the environment variable you want to change from the User Environment Variables list. The name of the environment variable appears in the Variable field. This same field can be used to add a new variable. The corresponding value of the environment variable appears in the Value field. The description, if any, appears in the Descrip field. Edit the entry in the Value field. Click on the Set button to accept the new value. The User Environment Variables list now contains the new value for this variable. To delete the variable, click on the Delete button. The variable will no longer appear in the User Environment Variables list. To edit the values of other variables, continue the same process as above. When complete, click on OK to accept the changes and to overwrite the ee.cfg file. Click on Cancel to disregard any changes.

2. 3.

4.

5. 6.

7.

8.

572

_ _______________
Glossary
absolute path name The sequence of directories, beginning with the root directory (/) that locates a file. See also path name and relative path name. The plane in a 3-D design upon which you can place elements and perform manipulations. The process which is displayed in the Process ID field; it controls the message fields, the menus, and the keyboard. The active process has a highlighted window icon strip. Software designed to meet specific needs, unlike system software which runs other software. A method of processing data which collects a series of operations into a group (or batch) and executes the group in a continuous stream without user intervention. A queue, or channel for moving requests, created through NQS. A batch queue handles scheduling for processes submitted through the Batch options screen menu. A point on a pipeline which separates piping segments so that they can be assigned different segment parameters. A branch point allows for placement of branch components. The button located in the upper right corner of a form containing a red X or the word cancel. Select the cancel button to exit the form or option. active depth

Glossary

active process

application software

batch processing

batch queue

branch point

cancel button

N: EE Configure

cell

A permanent association of elements that can be stored and placed as a group, and then manipulated as individual elements. A column data type that stores alphanumeric character data. In network operations, a node which accesses data or performs a function on the remote resource (usually a server). All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship. An attribute of a database table. A group of columns defines a table in a database. Instructions from the user to perform a function on specified data. A button that appears in the upper right corner of a form and contains a green check mark or the word confirm. Select the confirm button to initiate a specified option.

character client

column

command confirm button

573

_ _______________
EE Raceway Modeling Reference Guide - February 2003 coordinate coordinate system The location of a point along the X, Y, or Z axis. A geometric relation used to denote the location of points in the design cube. The most common coordinate system is the rectangular coordinate system, whereby points are located by traversing the X, Y, and Z axes of the design cube. Normally, coordinate systems have their origin defined as 0,0,0, though this is not required. Other coordinate systems are used to more easily express the coordinates of specific geometric entities. For example, you can use a spherical coordinate system to help define points on a sphere, and you can use a cylindrical coordinate system to help define points on a cylinder. An ordered set of absolute or relative data values that specify a location in a coordinate system. The image files written by System V for a number of reasons, the most common of which are memory violations, illegal instructions, bus errors, and user-generated quit signals. The pointer that the user moves on the screen to indicate an item or area. The mouse button used to place data points and tentative points, to accept previously selected elements, and to select commands from forms and menus. The field on a screen used to accept user-supplied data. Also known as key-in field. A point placed by pressing the data button on the mouse. Data points select commands from the panel menus and Menu Bar, place elements, identify and accept elements, and activate windows and perform window manipulations. A collection of comprehensive informational files having predetermined structure and organization that can then be communicated, interpreted, or processed by a specific program. The part of the database that is made of rows and columns and contains information about the project and design elements. The predetermined value of a parameter that is automatically supplied by the system or program whenever a value is not specified by the user. To remove, destroy, eliminate, or erase. A separating mark or space; a character or sequence of contiguous characters that mark the end of a string of characters. A nonaddressable component of a network, that is, a component onto which a user cannot log, for example, tape drive, disk drive, and floppy disk.

coordinates

core files

cursor data button

data entry field

data point

database

database table

default

delete delimiter

device

574

_ _______________
directory display-list box A file that contains the names of other files.

Glossary

A small box with horizontal dashes located at the end of a form key-in field. When selected, a list of the data available for that field is displayed. Input can then be selected from the list with a data point instead of keying in the information. The set of acceptable values for a value within a component. Another term for the dynamic function that attaches the cursor to an element so you can see it move. A term used in plane surveying that describes an east, or positive, difference in longitude. An object (project, drawing, element, and so forth.) of interest about which information is stored; a relational database table. See interference envelope. A path name that tells the system where to locate a file. A user-defined name given to an interactively created file. The name should be relevant to the contents of the file. An interface or screen menu designed with the I/FORMS product. Because many of the screen menus in the application software are built with I/FORMS, you must have the FORMS_S product on your workstation. The name of the entire path or directory hierarchy to a file, including the file name. See also relative path name.

domain dragging

easting

entity

envelope file file specification filename

form

full path name

N: EE Configure

gadget

A portion of a form, such as a button, a field, or a checklist, that responds to information. Gadgets can display default values or act as data entry areas. The first items of information in a file which precede any actual data. The header contains information on the structure and contents of the file. A classified structure with superiors (roots) and subordinates (dependents) for grouping files or commands. A pictorial representation or image; a symbol that graphically identifies a command. A relational database management system supported by RIS. A relational database management system supported by RIS. An equipment modeling primitive or parametric component that is used in conjunction with or instead of model graphics for interference checking. Interference envelopes are given different levels and display symbology to distinguish them from primitives.

header

hierarchy

icon

Informix Ingres interference envelope

575

_ _______________
EE Raceway Modeling Reference Guide - February 2003 invert elevation isometric The lowest point on the internal diameter of the pipe. Relating to or being a drafting system characterized by three equal axes at right angles; a view in which the horizontal lines of an element are drawn at an angle to the horizontal and all verticals are projected at an angle from the base. An attribute (column) in a table which is chosen as the access vehicle to individual rows of the table. The field on a screen used to accept user-supplied data. Also known as a data entry field. A point on an element, including vertices, to which you can snap. A word recognized by the software that provides access to a certain function. The strip at the top of the screen that contains icons for selecting commands. The area that appears in the MicroStation Command Window when you are working in a design file. It is divided into the Command Status field, the Current Command field, the Prompt field, and the Key-in field. A graphic representation or schema. An interconnection of host computers and workstations that enables them to share data and control. The term network can mean the devices that connect the system, or it can mean the connected system. Network File System, the system that provides access to data that is distributed among machines through an interconnection of host computers and workstations. NFS allows you to mount a remote resource to your local workstation so you can access the data as though it were local. NFS is usually used to access centralized data on a server. Any addressable device (such as a workstation or a server) that is connected to a network. The network enables the connected nodes to share data and system control. The hard-wired Ethernet address assigned to each node when it is manufactured. It is necessary for each node to identify and communicate with another node in the network. A name, or alias, that can be assigned to the node address of a device on a network. A term used to describe a north coordinate location in the plant coordinate system.

key

key-in field

keypoint keyword

menubar

message area

model network

NFS

node

node address

node name

northing

576

_ _______________
nozzle A special equipment modeling primitive that contains the connection point to piping. This point does NOT include a gasket allowance, but rather represents the face-of-flange coordinate. Network Queuing System, the software package that allows you to define network-wide batch and device queues. Use of NQS involves setting up local resource queues on the system(s) where the resources reside and setting up pipe queues on the systems that are to have access to the resources. A relational database management system supported by RIS. In coordinate geometry, the point where the x, y, and z-axes intersect. The point at which the coordinate system is placed. A view which is a projection of the model onto a plane along lines which are orthogonal to the plane. A property whose value determines the characteristics or behavior of something. NQS

Glossary

Oracle origin origin point orthogonal view

parameter

path

A sequence of directories leading to a file or a sequence of menus leading to a command. The sequence of directories leading to a file. See also absolute path name and relative path name. Plant Design System A controlled channel for moving requests to batch or device queues on remote systems and for receiving status and/or data in response.

path name

PDS pipe queue

N: EE Configure

place data point plane

To identify a specific element, or indicate a specific point in the design file. A spatial element in geometry that may or may not have a boundary, but is level, having no elevations or depressions, and is three-dimensional. Reference Database. A collection of reference data containing information relative to industry design codes, vendors catalog data, job specifications, commodity libraries, graphics symbology, label descriptions, report formats and other information of a similar manner. The sequence of directories leading from the current directory to a particular file. See also path name and absolute path name. To turn; to change the angular orientation; to transform by revolution about a specific axis.

RDB reference database

relative path name

rotate

577

_ _______________
EE Raceway Modeling Reference Guide - February 2003 row A unit of related information in a table. One collection of column values for a table. The animation dynamic that enables you to specify the position of a data point while the element changes as you move the cursor. A description of the overall structure of the rulebase or database. A file that outlines the overall logical structure of a rule base or a database. In network operations, the node which maintains common data or performs a common task needed by clients. All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship. Language developed by IBM for creating, modifying, and querying relational databases. The symbology of an element such as continuous dashes, dash-dot, solid, and so forth. The skin of a three-dimensional geometric element. The display style of an element, including color, style, and weight. A collection of data for quick reference, either stored in sequential locations in memory or printed as an array of rows and columns of data items of the same type. To switch; to change between two alternatives. A name that provides access to an account on the system. Data, either entered by the user or determined by the software, that are stored in an attribute. A quantity that may assume any one of a set of values. A quantity possessing both magnitude and direction, generally represented as a line. Vectors can be manipulated geometrically and are represented as a coordinate triple (x,y,z). The defined area of vision on a screen. A view allows you to see a prescribed volume of the design cube. Views are created with their own x, y, and z axes. The x,y plane of the view is parallel to the screen, while the z-axis can be thought of as coming straight out of the view towards you. The view axes maintain this relationship regardless of the rotation with respect to the design cube. See also active depth. External memory for a computer that can be used as if it were an extension of the computers internal memory. The software uses virtual memory to store data. This means that unneeded files and data, stay on the disk until they are called for. Because the internal processing memory stores a minimal amount of data, the software can perform processing more quickly. rubberbanding schema schema file server

Structured Query Language SQL style

surface symbology table

toggle user name values

variable vector

view

virtual memory

578

_ _______________
working directory The directory from which you are accessing files.

Glossary

N: EE Configure

579

_ _______________
EE Raceway Modeling Reference Guide - February 2003

580

_ _______________
Index
A access column 179, 234, 290 activate design volume coordinate system 320 plant coordinate system 320 active angle 256 one-line type parameters access column 290 clear 291 display toggle 290 list column 290 override 291 save to memory 289 select 290 parameters 146 point coordinates display 121 define 145 active coordinate system 320 add query 568 systems 245 airway place 132 alias.cmd 529, 539 alter schema form 556 table form 559 angle active 256 annotate element 178 access column 179, 234 by group 233 clear button 180, 235 display toggle 179, 234 list column 179, 234 override button 180, 235 override keys 179, 234 select button 180, 235 source column 179, 234 model 285 one-line 178, 233 RCP 178 annot_form 529 application manager information 27, 109, 415, 425 approval status codelist 432 archive form 46 option 86 archive project network protocol TCP/XNS 46 remote node name/address 46 asid id display 316 highlight 309 assign 522, 527 attributes default 430 setting raceway 256 automatic fit 151 propagation 298 size 151 B background 522 bar commands palette 98 basic concepts database 115 drawing 108 propagation 113 setup 27, 110 workstation skills 26 batch 522 bill of materials 549 by volume 72, 327, 550 bin/ 521, 527 blank part ids 552 C cable code codelist 439 color codelist 441 configuration codelist 440 insulation type codelist 444

Index

N: EE Configure

581

_ _______________
EE Raceway Modeling Reference Guide - February 2003 cable (continued) size codelist 440 voltage codelist 443 cardinal point codelist 433 cell create commands 269 drop point 277, 278, 279 equipment pointer 274, 275, 276 model 271 library 269, 271 cfg/ 527 change all 568 row 568 change system parameters 221 changing one-line type 294 parameters one-line type 289 propagation 297 raceway 256 symbology 264 system 295 cleanup database 340 clear annotate element 180, 235 one-line type parameters 291 clip 522 clone element 188 by group 239 codelists 432 approval status 432 cardinal point 433 drawing type 433 manual fitting 433 one-line type 434 RCP type 435 system 435 three-line qualifier 437 subtype 437 type 436 units 438 vendor 438 wire/cable code 439 color 441 configuration 440 insulation type 444 voltage 443 codelists (continued) wire/cable size 440 yes/no 445 coincident RCP checks 209 color parameters 256 combine coincident RCPs 209 command palettes 97 command.msg 529 commands construct point 123 extend/reduce run 125 midpoint on segment 123 Commands Integrated 368 compile eden symbol 349 compress eden symbol library 359 conduit place 132 place stub up 167 seamless tubing 114 sizing 155 attributes 268 config/ 522, 527 construct point 123 construction class display 306 control number 165 set symbology 262 symbology 264 coordinate system design volume 320 plant 320 show active 320 coordinate system 320 coordinates display 121 copy clone element 188 by group 239 element 184 by group 231 menu 43 option 78

582

_ _______________
create cell 269 drop point 277, 278, 279 equipment pointer 274, 275, 276 model 271 menu 39 option 61 schema form 555 tables 558 drop mode 558 insert mode 558 modify mode 558 three-lines 194 create_db 428, 522 cross section ductbank definition 164 rotate 140 rotation angle 256 scale factor 256 crosses 195 cutback mode 150 D data definition form 557 files 522, 527 database 321, 425 cleanup 340 edit 567 add query 568 change all 568 change row 568 current row box 567 delete all 568 edit query 567 initialize query 567 insert row 568 process query 567 review 568 toggle 568 update active 568 load 323, 332 batch file 335 palette 102 procedures 427 project 115 reference 115 relational 427 report 326 rule checks 329 setup 33 database (continued) utilities 50 RIS schema utilities 51 update project schema 52 update reference schema 55 db/ 523, 528 dba_rpt 522 dba_shell 522 DbEdit 567 defaults attributes 430 raceway 256 RCP key 257 text 266 define active point 145 duct cross section 164 group 226 one-line type 260 parameters 146 raceway defaults 256 system 258 delete all 568 duplicate one-lines 211 eden symbol 351 element 212 by group 251 fitting 216 menu 44 one-line vertex 217 option 79 RCP 214 design commands 129 conduit sizing 155 define duct cross section 164 file command menu bar 96 insert one-line vertex 160 insert RCP 138 option 63 palette 99 place drop point 142 equipment pointer 144 manual fitting 147 one-line 132 rotate cross section 140 route around vessel 135 set

Index

N: EE Configure

583

_ _______________
EE Raceway Modeling Reference Guide - February 2003 design (continued) set (continued) active parameters 146 unload 336 design volume coordinate system 320 dgn/ 528 directory structure 520 display annotation 306 asid id 316 construction class 306 element information 301 element type 316 field 121 link 317 one-line type 318 screen 93 sector/word 315 system 318 toggle annotate element 179, 234 one-line type parameters 290 document organization 19 outline 25 purpose 19 downloading 29 drawing process 108 setup 110 type codelist table 433 drop point create cell 277, 278, 279 keys 431 place 142 schema form 556 table form 559 ductbank cross section definition 164 place 132 duplicate one-line checking 211 DVCS 320 E eden/ 528 eden example 514 list functions 355 mode 113 eden (continued) option 67 batch mode 69 operating modes 68 processes 347 compile symbol 349 compress symbol library 359 delete symbol 351 edit symbol file 366 extract symbol 361 extract user function 363 list symbol library 353 list user functions 355 merge symbol libraries 357 symbol compile 349 compress library 359 delete 351 edit file 366 extract 361 generation 513 list library 353 merge libraries 357 processor file 513 user function extract 363 eden.dat 528 edit eden symbol file 366 manual fitting 198 model annotation 285 query 567 EE configure 571 databases 425 environment 35 forms archive 46 restore 48 manager 565 menus 36 copy 43 create 39 database utilities 50 delete 44 enter 40 product menu 42 nucleus file structure 520 raceway file structure 524

584

_ _______________
ee.bar 529 eeconfig 522 eemgr 522 eeprj 522 eeqpr 522 EERWAY command menu bar 96 environment 59 create 61 design 63 eden 67 batch mode 69 operating modes 68 processes 64 batch mode 66 operating modes 65 reports 70 rule checks 73 utilities 75, 78, 79, 80, 81, 82, 83, 84, 86, 87, 89 palette 97 palettes 97 elbows 195 elements annotate 178 by group 233 clone 188 by group 239 copy 184 by group 231 delete 212 by group 251 display information 301 highlight by asid id 309 by link 312 by sector/word 307 identifying 103 modify commands 173 modifying 175 move 186 placing 129 propagate 194 by group 241 type display 316 engineering units 267 enter menu 40 environment EE 35 EE Raceway 59 variables 422 environment rules for fittings 446 environments graphics palettes 97 equipment pointer create 274, 275, 276 keys 431 place 144 error.msg 529 errors messages 377 propagation 314 extend/reduce run 125 extract eden symbol from library 361 eden user function from library 363 F field routed raceway 161 filename highlight asid id 309 highlight link 312 files data 522, 527 eden symbol processor 513 password 565 purge 81 rway.cmd 543 seed English 528 metric 528 structure EE nucleus 520 EE raceway 524 fittings 195, 512 delete 216 edit/insert manual fitting 198 environment rules 446 place by rule 207 by group 243 place manual fitting 147 floppy/network toggle 86

Index

N: EE Configure

585

_ _______________
EE Raceway Modeling Reference Guide - February 2003 force 555 forms/ 523 forms maximize/minimize 120 precision input customizing 417 function eden library 355 G graphic symbology 262, 264, 266 graphics environment palettes 97 group annotate 233 copy 231 define 226 delete 251 minimize joints 248 propagate 241 H help_graphics 528 help_rway.hp 528 help_rway.s 528 help_source/ 528 highlight element by asid id 309 by link 312 by sector/word 307 propagation errors 314 horizontal spacing 165 I identifying elements 103 IGDS toggle 83 increase size only 157 increase/decrease size 157 information about elements 301 initialize query 157, 567 input precision 119 insert one-line vertex 160 RCP 138 row 568 installation 27 databases 33 downloading 29 Integrated Commands 368 palette 97 Using 369 interference detection 118, 342, 344 introduction 25 J joints minimize 219 by group 248 K key-ins precision 104, 119 keys 430 drop point 431 equipment pointer 431 one-line 430 override 115 RCP 431 L levels set active 299 library cell 269, 271 eden symbol 353, 357, 359, 361 eden user function 363 eden user functions 355 link display 317 highlight 312 list column 179, 234, 290 eden symbol library 353 user functions 355 load 527 database 323, 332 batch file 335 lock model 282 M main form EE archive 46 restore 48

586

_ _______________
main menu EE 36 copy 43 create 39 database utilities 50 delete 44 enter 40 product menu 42 EERWAY create 61 design 63 eden 67 processes 64 report 70 rule checks 73 utilities 75 manual fitting edit/insert 198 part codelist table 433 place 147 material takeoff 548 maximize form 120 menu.cfg 527 menus 91 command menu bar 96 directory 528 EERWAY command menu bar 96 menu_shell 522 merge eden symbol libraries 357 merge_pnl/ 529 merge_pnl 529 messages display fields 93 error 377 MicroMenu umenu 543 midpoint on segment 123 minimize form 120 minimize joints 219 by group 248 model annotate 285 move annotation 283 commands 280 using 281 create model cell 271 lock 282 unlock 284 model commands palette 101 modify 173 add systems by group 245 annotate element 178 by group 233 clone element 188 by group 239 combine coincident RCPs 209 copy element 184 by group 231 define group 226 delete duplicate one-lines 211 element 212 by group 251 fitting 216 one-line vertex 217 RCP 214 edit/insert manual fitting 198 elements 175 group commands 223 define group 226 minimize joints 219 by group 248 move element 186 one-line segment 190 one-line vertex 192 one-line route 204 palette 99 place fitting by rule 207 by group 243 propagate element 194 by group 241 reference schema 451 remove RCP 214 replace systems by group 246 modify element palette 98 modify group palette 100 move element 186 model annotation 283 move/move to toggle 121 one-line segment 190 one-line vertex 192 mscrecol.sh 522 msg/ 523, 529 mslink display 317 highlight 312

Index

N: EE Configure

587

_ _______________
EE Raceway Modeling Reference Guide - February 2003 msseed.dgn 528 mstr_rway.hp 528 mstr_rway.s 528 N network/floppy toggle 86 new users database preparation 427 nucleus file structure 520 O one-line annotate 233 changing sizes 178, 233 delete duplicates 211 vertex 217 insert vertex 160 keys 430 modify route 204 move segment 190 move vertex 192 place 132 route around vessel 135 type codelist table 434 define 260 display 318 parameters 289 access column 290 clear 291 display toggle 290 list column 290 override 291 override keys 290 save to memory 289 select 290 priority 434 set active 294 types 110 output option 89 override button annotate element 180, 235 keys 115, 179, 234, 290 one-line type parameters 291 setting 263 P palettes bar commands 98 database 102 design 99 EERWAY 97 Integrated Commands 97 MicroStation commands 98 model commands 101 modify 99 modify element 98 modify group 100 runtime setup 101 setup commands 100 utilities 102 parameters active 111 active angle 256 color 256 one-line type 289 access column 290 clear 291 display toggle 290 list column 290 override 291 override keys 290 save to memory 289 select 290 propagation 297 raceway 256 set active 146, 289 part verification 297 password echo toggle 46, 48, 52, 55 file 565 PCS 320 PDS reference model from 372 review attributes 371 review clash 375 window to named PDS item 374 percent fill 157 percentage of raceway changing 221 place drop point 142 equipment pointer 144 field routed raceway 161 fitting by rule 207 by group 243 manual fitting 147

588

_ _______________
place (continued) one-line 112, 132 RCP 138 stub up 167 placepoint 150 plant coordinate system 320 precision input 119 active point coordinates display 121 construct point 123 customizing 417 display fields 121 extend/reduce run 125 midpoint on segment 123 move/move to toggle 121 key-ins 104 prerequisite 26 print.dat 522, 536 priority 434 procedures 107 process query 157, 567 process.dat 528, 533 processes 331 cleanup database 340 eden 347 interference detection 342, 344 load database 332 batch file 335 option 64 batch mode 66 operating modes 65 unload design 336 sheet 338 processing toggle 53, 55, 65 processor file 513 product menu 42 removal 521, 527 product.def 521, 527 project database 115 schema description 487 drawing list 547 schema general description 448 update 449 prompt.msg 529 propagate 113 automatic propagation 298 element 194 by group 241 fittings 195 highlight errors 314 modes 297 eden 113, 297 sketch 113, 297 parameters 111 part verification 297 setup 297 style 297 purge option 81 Q query add 568 edit 567 initialize 567 process 567 R raceway defaults set 256 field routed 161 processes 331 RCPs 112 combine coincident RCPs 209 default key 257 delete 214 insert 138 keys 431 type codelist table 435 weight 257 README 521, 527 receive option 84 reduce run 125 reducers 195 reeprj 522 reference database 115 schema description 454 guide 25 schema 510 description 430 modifying 451 updating 449

Index

N: EE Configure

589

_ _______________
EE Raceway Modeling Reference Guide - February 2003 reference PDS model 372 relational databases 427 interface system (RIS) 426 report processing 545 relational interface system (RIS) alter schema 556 alter table 559 data definition 557 drop schema 556 drop table 559 schema creation 555 schema file 560 set 560 table creation 558 table information 557 remove one-line vertex 217 RCP 214 script 521, 527 rename option 82 replace systems by group 246 report.dat 528, 534 reports 117, 545 bill of materials 549 by volume 72, 327, 550 blank part ids 552 database 326 directory 529 material takeoff 548 option 70 project drawing list 547 templates 546 restore form 48 option 87 restore project from archive TCP/XNS toggle 48 XNS/TCP toggle 48 review PDS attributes 371 PDS clash 375 RIS 115, 426 procedures 427 schema manager 553 alter schema form 556 alter table form 559 create schema form 555 create table form 558 data definition form 557 RIS (continued) schema manager (continued) drop schema form 556 drop table form 559 force 555 schema file form 560 schema information form 554 set form 560 table information form 557 schema utilities 51 rotate cross section 140 orientation 151 rotation angle cross section 256 rule checks database 329 option 73 templates 546 rule_chk.dat 528, 535 runs 112 runtime setup 287 display element information 301 palette 101 propagation setup 297 set active levels 299 one-line type 294 one-line type parameters 289 system 295 rway_bar 528 rwaybar.sym 529 rway.cmd file 543 rway.cmds 528 rwayh_pnl 529 rway.pnl 529 rwaypnl.sym 529 rway_prj.tbl 529 rway_ref.tbl 529 S save to memory 289 scale factor cross section 256 schema 115 create 555 definition file 561 fields 561 description 454, 487 drop 556 file 560

590

_ _______________
schema (continued) information form 554 modifying reference 451 names 450 project 448 reference 430 update 428, 449 project 449 reference 449 utilities 51 screen display 93 seamless tubing 114 sector/word display 315 highlight 307 seed/ 528 seed.dgn 528 select button annotate element 180, 235 one-line type parameters 290 send option 83 set 560 active levels 299 one-line type 294 one-line type parameters 289 parameters 146 point 145 system 295 conduit sizing attributes 268 defaults 256 symbology control 262 text defaults 266 setup commands 253 conduit sizing attributes 268 create cell 269 define one-line type 260 system 258 lock model 282 model 280 model annotation 285 move 283 propagation 297 set raceway defaults 256 symbology control 262 setup (continued) set (continued) text defaults 266 symbology control 264 system manager 27, 109 unlock model 284 setup commands palette 100 sheet unload 338 show active coordinate system 320 size changing one-line size 178, 233 sizing conduit 155 sizing attributes 268 sketch mode 113 skills workstation 26 software downloading 29 source column 179, 234 SPEC process 507 specification 507 specification tables 510 start-up sequence 92 status.msg 529 straights 195 structure EE Raceway 524 file 520 stub up 167 subsystems 295 sym/ 523, 529 symbol eden compile 349 compress 359 delete 351 extract 361 list library 353 merge libraries 357 file edit eden 366 generation 513 example 514 processor file 513 symbology 110 changing 264 control 264

Index

N: EE Configure

591

_ _______________
EE Raceway Modeling Reference Guide - February 2003 symbology (continued) control (continued) set 262 system 110, 295 add 245 codelist table 435 define 258 display 318 manager information 27, 109, 415, 425 replace systems group 246 set active 295 system percentage changing 221 T tables codelists 432 information form 557 TCP/XNS protocol archive project 46 TCP/XNS toggle restore project from archive 48 templates reports 546 rule checks 546 text defaults 266 set 266 text nodes 266 text strings 266 nodes 266 strings 266 three-line codelist table 436 create 194 qualifier codelist table 437 subtype codelist table 437 tmp/ 529 toggle construction display on/off 306 IGDS 83 network/floppy 86 password echo 46, 48, 52, 55 processing 53, 55, 65 tools reference PDS model 372 review PDS attributes 371 review PDS clash 375 window to named PDS item 374 tray place 132 tray_part table 511 tray_spec table 510 typefaces 21 U umenu 543 undelete 80 units codelist table 438 engineering 267 working 104 .unl files 509 unload 527 design 336 sheet 338 unlock model 284 update active 568 schema 428, 449 project 52, 449 reference 55, 449 upgrading workstation 28 user function eden extract 363 utilities 303 display element type and asid id 316 link 317 sector/word 315 system and one-line type 318 highlight by asid id 309 by link 312 by sector/word 307 propagation errors 314 option 75 archive 86 copy 78 delete 79 output 89 purge 81 receive 84 rename 82 restore 87 send 83 undelete 80 palette 102 reference PDS model 372 review PDS attributes 371

592

_ _______________
utilities (continued) review PDS clash 375 schema 51 toggle construction display on/off 306 window to named PDS item 374 V vendor codelist table 438 specification 507 vertical spacing 165 vessel routing around 135 volume bill of materials 72, 327, 550 W weight RCP 257 window to named PDS item 374 wire code codelist 439 color codelist 441 configuration codelist 440 insulation type codelist 444 size codelist 440 voltage codelist 443 wireway place 132 workflow 107 databases 115 drawing process 108 drawing setup 110 eden symbol generation 513 one-line types 110 parameters 111 place one-line 112 propagation 113 propagation parameters 111 reports 117 setup 109, 110 symbology 110 systems 110 working units 104 workstation skills 26 upgrading 28 wyes 195 X XNS/TCP toggle archive project 46

Index

N: EE Configure

593

_ _______________
EE Raceway Modeling Reference Guide - February 2003

594

EE Raceway Modeling
Reference Guide Addendum
February 2003

DPDS3-PB-200005C
For PDS version 07.02.00.** This document supplements DPDS3-PB-200005B.

EE Raceway Modeling Reference Guide Addendum February 2003

Table of Contents
PDS Electrical Raceway Environment .................................................................... 597
Modeling......................................................................................................................... 598 Load Reference Schema ................................................................................................. 599 Utilities ........................................................................................................................... 601

Palettes in the EE Raceway Graphics Environment (replaces 5.4).......................... 602 Modify Element Commands (replaces 9.2) ............................................................. 607
Rotate Element................................................................................................................ 609 Rotate Copy Element...................................................................................................... 611 Mirror Element ............................................................................................................... 613 Mirror Copy Element...................................................................................................... 615

Modify Group Commands (replaces 9.3) ................................................................ 617

Rotate Group................................................................................................................... 619 Rotate Copy Group ......................................................................................................... 621 Mirror Group .................................................................................................................. 623 Mirror Copy Group......................................................................................................... 625 Move Group.................................................................................................................... 627

Annotate Model........................................................................................................ 628 Reference PDS Model (replaces 16.2)..................................................................... 629 EE Raceway Project Database Schema Description (replaces panel) ..................... 631 EE File Structure (replaces Appendix F) ................................................................. 633
EE Nucleus File Structure .............................................................................................. 634 EE Raceway File Structure............................................................................................. 637

596

PDS Electrical Raceway Environment

When you select the Electrical Raceway Environment command on the PD_Shell form, the EE Raceway Environment form displays.

Commands
Modeling Allows you to open a design file in the PDS Raceway modeling environment. Load Reference Schema Allows you to update the Raceway reference schema. Utilities Allows you to access EE Raceway commands for EE Raceway processes, EDEN symbols, reporting, and rule checks.

597

EE Raceway Modeling Reference Guide Addendum February 2003

Modeling
This option allows you to select a design file to open in the modeling environment.

Steps
1. Select a design area from the list. 2. Click Accept. The Raceway Designer form displays. 3. Select a model from the list. 4. Click Accept. The selected model displays in MicroStation.

598

Load Reference Schema

This option allows you to update the reference schema for the active project. You can use this command to update an existing empty RIS schema with EE tables and default information, or to modify the tables in an existing RIS schema to conform to the structure of a given .sql file. If you update the schema with a .sql file that has a different structure from the original .sql file, the command makes the following changes: Adds new tables listed in the .sql file. Modifies existing tables if the definition of that table has changed in the .sql file. The process replaces the old table definition with the new table definition, keeping column data where column names match. Load those tables that have unique index numbers with data from the .unl files that are listed in the .cmd files. If a table lacks a unique index, the process loads it only if the table is empty.

Field Descriptions
Reference Schema Specifies the reference schema for the active project. SQL File Network Address Specifies the network address of the SQL file containing the correct table and column structure. SQL File Path Specifies the file path of the SQL file containing the correct table and column structure. SQL Filename Specifies the file name of the SQL file containing the correct table and column structure. CMD File Network Address Specifies the network address of the CMD file that defines which .unl files to load into which tables.
599

EE Raceway Modeling Reference Guide Addendum February 2003

CMD File Path Specifies the file path of the CMD file that defines which .unl files to load into which tables. CMD Filename Specifies the file name of the CMD file that defines which .unl files to load into which tables.

600

Utilities
This option accesses the EE Raceway Process, EDEN, Report, and Rule commands.

Commands
Process This command accesses all available EE Raceway processes. These processes allow you to manipulate drawings and the project database. Refer to sections 4 and 14 of the EE Raceway Reference Guide for more information on this command. EDEN This command allows you to design and maintain your own symbols for Raceway elements. Refer to sections 4 and 15 of the EE Raceway Reference Guide for more information on this command. Report This command accesses the standard EE Raceway reports. These reports contain information on the project and reference databases. Refer to section 4 and Appendix J of the EE Raceway Reference Guide for more information on this command. Rule This command accesses the standard EE Raceway Rule Checks. These rule checks are reports that identify violations of certain design rules by working on the project database. Refer to section 5 and Appendix J for more information on this command.

601

EE Raceway Modeling Reference Guide Addendum February 2003

Palettes in the EE Raceway Graphics Environment (replaces 5.4)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 103-108 in the PDS 7.1 version of the document). The following information has been modified: Rotate, Rotate Copy, Mirror, and Mirror Copy commands on the Modify Element and Modify Group palettes Move Group command on the Modify Group palette See the following text for details.

This section presents the palettes that are used in the EE Raceway graphics environment. Palettes are groups of commands that are accessible from the EERWAY command menu bar on the MicroStation command window. This section presents the palettes in the order that they are accessible if you look at each menu going from left to right across the EERWAY command menu bar on the MicroStation command window. Next to each icon is the name of the form or command it represents. You should become familiar with the name and functionality of each command on each palette. Each command is described in full in later sections of this text.

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

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

602

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.

603

EE Raceway Modeling Reference Guide Addendum February 2003

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.

604

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.

605

EE Raceway Modeling Reference Guide Addendum February 2003

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.

606

Modify Element Commands (replaces 9.2)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 181-182 in the PDS 7.1 version of the document). The following information has been modified: Rotate, Rotate Copy, Mirror, and Mirror Copy commands See the following text for details.

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

The Modify Element commands manipulate individual elements, including RCPs, onelines, and three-lines, within the design file. You can use individual commands to move, copy, and delete specified elements, to review or edit element annotation, and to check for duplicate one-lines and coincident RCPs in the design file. Modify Element commands also allow you to propagate one-lines in your raceway model. Note: Do not use MicroStation commands to manipulate or modify EE Raceway elements (one-line, three-lines, annotation, and so forth). Doing so will cause serious problems and/or destroy the EE Raceway model. Use only these EE Raceway modify commands to manipulate EE Raceway elements. Annotate Element Places, reviews, and edits intelligent annotation for raceway elements. Copy Element Copies an element as specified within the design file. Move Element Moves an element to a specified location in the design file. Clone Element Copies an element multiple times in the same direction.

607

EE Raceway Modeling Reference Guide Addendum February 2003

Move One-Line Segment Moves a one-line segment while maintaining connectivity to existing elements. Move One-Line Vertex Moves an internal one-line vertex. Propagate Element Expands one-line elements into three-dimensional elements. Edit/Insert Manual Fitting Modifies fittings that were manually placed in the model. Modify One-Line Modifies the route of an existing one-line element. Place Fitting by Rule Places a non-standard fitting at an RCP using a set of rules defined in the reference database. Check Coincident RCPs Checks for coincident RCPs in the design file. Check Duplicate One-lines Checks for duplicate or overlapping one-lines in the design file. Delete Element Removes a valid raceway element, and elements associated with it, from the design file. Remove RCP Deletes a specified RCP (raceway connect point) from the design file. Delete Fitting Removes fittings from the design file. Remove One-Line Vertex Deletes an internal vertex from an existing one-line. Minimize Joints Reduces the number of vertices in an identified one-line to a minimum. Change System Parameters Changes the system percentage and the project rule for a selected element. Rotate Element Rotates an element to a specified location in the design file. Rotate Copy Element Copies an element and rotates the copy to a specified location in the design file. Mirror Element Flips an element about a specified point in the design file. Mirror Copy Element Copies an element and flips the copy about a specified point in the design file.

608

Rotate Element
This command rotates individual raceway elements as specified within the design file. You can use this command to move one-lines, RCPs, drop points, equipment pointers, and annotation. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved. If a one-line is rotated, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.

Field Descriptions
Rotation Point Displays the location of the rotation point. Plan View Specifies the angle at which to rotate the element on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point. East Elevation Specifies the angle at which to rotate the element on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point. North Elevation Specifies the angle at which to rotate the element on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point. Angle Key-in field used to specify the angle for each plane. To change the angle, click the button for the plane and type the angle in the Angle field.

Before Using This Command

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

609

EE Raceway Modeling Reference Guide Addendum February 2003

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

Steps
1. Select the Rotate Element command. The Rotate Element precision input form displays. 2. Identify the element you intend to rotate and accept it with <D>. The system highlights the specified element. If you do not locate an acceptable element, the system displays the message Element not found. The message disappears when you identify a valid element. 3. Specify the point around which to rotate the element. The Specify Rotation form displays. 4. Specify the planes and angles at which to rotate the element. 5. Click Accept. The element rotates to the specified position.

610

Rotate Copy Element

This command creates rotated copies of individual raceway elements as specified within the design file. You can use this command to copy and rotate one-lines and their associated elements.

Field Descriptions
Rotation Point Displays the location of the rotation point. Plan View Specifies the angle at which to rotate the element on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point. East Elevation Specifies the angle at which to rotate the element on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point. North Elevation Specifies the angle at which to rotate the element on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point. Angle Key-in field used to specify the angle for each plane. To change the angle, click the button for the plane and type the angle in the Angle field.

Before Using This Command

You can enter all values for the placement of points through a precision input form. Using the form, you can locate elements, route one-lines, accept input, reject input, reset a command action, and exit a command. You must be familiar with precision input and its functions before using this command. For detailed information about precision input, see Precision Input Form. 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.

611

EE Raceway Modeling Reference Guide Addendum February 2003

Steps
1. Select the Rotate Copy Element command. The Rotate Copy Element precision input form displays. 2. Identify the element you intend to rotate and copy and accept it with <D>. The system highlights the specified element. If you do not locate an acceptable element, the system displays the message Element not found. The message disappears when you identify a valid element. 3. Specify the point around which to rotate the element. The Specify Rotation form displays. 4. Specify the planes and angles at which to rotate the element. 5. Click Accept. The element copy displays at the specified position.

612

Mirror Element
This command flips individual raceway elements about a point as specified within the design file. You can use this command to mirror one-lines, RCPs, drop points, equipment pointers, and annotation. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved. If a one-line is mirrored, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.

Field Descriptions
Mirror Point Displays the location of the specified mirror point. The primary vector of the orientation tee denotes the mirror planes normal vector. The elements are rotated about the plane formed by the secondary and the normal. Angle Specifies the angle by which to rotate the orientation tee. To change the displayed angle, select the field and type a new angle. About Specifies the axis about which to rotate the orientation tee. To change the displayed axis, toggle among the three axes (Primary, Secondary, Normal) until the appropriate axis displays. I Button Reorients the orientation tee along the identity matrix. It realigns the Primary axis with the positive X axis, the Secondary axis with the positive Y axis, and the Normal axis with the positive Z axis.

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

613

EE Raceway Modeling Reference Guide Addendum February 2003

command action by one step or to reject a highlighted element, press <R> or select Reject on the precision input form.

Steps
1. Select the Mirror Element command. The Mirror Element precision input form displays. 2. Identify the element you intend to mirror and accept it with <D>. The system highlights the specified element. If you do not locate an acceptable element, the system displays the message Element not found. The message disappears when you identify a valid element. 3. Specify the point about which to mirror the element. The Orient Mirror form displays. 4. Specify the mirror plane on which to mirror the element. The primary vector of the orientation tee denotes the mirror planes normal vector. 5. Click Accept. The element rotates to the specified position.

614

Mirror Copy Element

This command creates mirrored copies of individual raceway elements as specified within the design file. You can use this command to copy and mirror one-lines and their associated elements.

Field Descriptions
Mirror Point Displays the location of the specified mirror point. The primary vector of the orientation tee denotes the mirror planes normal vector. The elements are rotated about the plane formed by the secondary and the normal. Angle Specifies the angle by which to rotate the orientation tee. To change the displayed angle, select the field and type a new angle. About Specifies the axis about which to rotate the orientation tee. To change the displayed axis, toggle among the three axes (Primary, Secondary, Normal) until the appropriate axis displays. I Button Reorients the orientation tee along the identity matrix. It realigns the Primary axis with the positive X axis, the Secondary axis with the positive Y axis, and the Normal axis with the positive Z axis.

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. 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 Mirror Copy Element command. The Mirror Copy Element precision input form displays.
615

EE Raceway Modeling Reference Guide Addendum February 2003

2. Identify the element you intend to mirror and 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. Specify the point around which to mirror the element. The Orient Mirror form displays. 4. Specify the plane on which to mirror the element. The primary vector of the orientation tee denotes the mirror planes normal vector. 5. Click Accept. The element copy displays at the specified position.

616

Modify Group Commands (replaces 9.3)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 229-230 in the PDS 7.1 version of the document). The following information has been modified: Rotate, Rotate Copy, Mirror, Mirror Copy, and Move Group commands See the following text for details.

The Modify Group commands define and manipulate groups within a design file. Groups are temporary associations of Raceway and other elements in your model. The Modify Group commands allow you first to define a group of elements and then to manipulate the group in part or as a whole. The Modify Group palette is activated by selecting the Modify Group command from the Modify palette, or by selecting Modify from the EERWAY Command Menu Bar, then selecting Modify Group Commands, then selecting Palette.

You can use individual Modify Group commands to move, copy, and delete elements of specified groups, and to review or edit element annotation. You can also propagate onelines in a particular group using these commands. Note: Do not use MicroStation commands to manipulate or modify EE Raceway elements (one-line, three-lines, annotation, and so forth). Doing so will cause serious problems and/or destroy the EE Raceway model. Use only these EE Raceway modify commands to manipulate EE Raceway elements.

617

EE Raceway Modeling Reference Guide Addendum February 2003

Topics
Define Group Identifies raceway elements for inclusion in a particular group. Copy Element by Group Copies within the design file some or all elements of a specified group. Annotate Element by Group Places, reviews, and edits intelligent annotation for raceway elements within a specified group. Clone Group Copies a group multiple times in the same direction. Propagate Element by Group Expands some or all one-line elements of a specified group into three-dimensional elements. Place Fitting by Rule Group Places non-standard fittings using a set of rules defined in the reference database. Add Systems Group Defines multiple systems for a single one-line. Replace Systems Group Changes the defined active system type of a one-line. Minimize Joints by Group Reduces to a minimum the number of vertices of some or all one-lines in a specified group. Delete Element by Group Removes from the design file some or all elements of a specified group. Rotate Group Rotates some or all elements of a specified group to a new location in the design file. Rotate Copy Group Copies and rotates some or all elements from a specified group to a new location in the design file. Mirror Group Mirrors some or all elements from a specified group to a new location in the design file. Mirror Copy Group Copies and mirrors some or all elements from a specified group to a new location in the design file. Move Group Moves some or all elements from a specified group to a new location in the design file.

618

Rotate Group
This command rotates a group of raceway elements as specified within the design file. You can use this command to move one-lines, RCPs, drop points, equipment pointers, and annotation. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved. If a one-line is rotated, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.

Field Descriptions
Rotation Point Displays the location of the rotation point. Plan View Specifies the angle at which to rotate the group on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point. East Elevation Specifies the angle at which to rotate the group on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point. North Elevation Specifies the angle at which to rotate the group on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point. Angle Key-in field used to specify the angle for each plane. To change the angle, click the button for the plane and type the angle in the Angle field.

Before Using This Command

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

619

EE Raceway Modeling Reference Guide Addendum February 2003

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 Group command. The Rotate Group precision input form displays. 2. Identify the group you intend to rotate and accept it with <D>. The system highlights the specified group. If you do not locate an acceptable group, the system displays the message Group not found. The message disappears when you identify a valid group. 3. Specify the point around which to rotate the group. The Specify Rotation form displays. 4. Specify the planes and angles at which to rotate the group. 5. Click Accept. The group rotates to the specified position. Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the rotation point and planes for each accepted element.

620

Rotate Copy Group

This command creates a rotated copy of a group of raceway elements as specified within the design file.

Field Descriptions
Rotation Point Displays the location of the rotation point. Plan View Specifies the angle at which to rotate the group on the plan view plane. The selected elements are rotated about the up-down axis passing through the rotation point. East Elevation Specifies the angle at which to rotate the group on the east elevation plane. The selected elements are rotated about the east-west axis passing through the rotation point. North Elevation Specifies the angle at which to rotate the group on the north elevation plane. The selected elements are rotated about the north-south axis passing through the rotation point. Angle Key-in field used to specify the angle for each plane. To change the angle, click the button for the plane and type the angle in the Angle field.

Before Using This Command

You can enter all values for the placement of points through a precision input form. Using the form, you can locate elements, route one-lines, accept input, reject input, reset a command action, and exit a command. You must be familiar with precision input and its functions before using this command. For detailed information about precision input, see Precision Input Form. 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 Copy Group command.

621

EE Raceway Modeling Reference Guide Addendum February 2003

The Rotate Copy Group precision input form displays. 2. Identify the group you intend to rotate and copy and accept it with <D>. The system highlights the specified group. If you do not locate an acceptable group, the system displays the message Group not found. The message disappears when you identify a valid group. 3. Specify the point around which to rotate the group. The Specify Rotation form displays. 4. Specify the planes and angles at which to rotate the group. 5. Click Accept. The group copy displays at the specified position. Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the rotation point and planes for each accepted element.

622

Mirror Group
This command flips a group of raceway elements about a point as specified within the design file. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved. If one-lines are mirrored, all attached RCPs will be moved and all attached one-lines will be rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment pointers will also be moved.

Field Descriptions
Mirror Point Displays the location of the specified mirror point. The primary vector of the orientation tee denotes the mirror planes normal vector. The elements are rotated about the plane formed by the secondary and the normal. Angle Specifies the angle by which to rotate the orientation tee. To change the displayed angle, select the field and type a new angle. About Specifies the axis about which to rotate the orientation tee. To change the displayed axis, toggle among the three axes (Primary, Secondary, Normal) until the appropriate axis displays. I Button Reorients the orientation tee along the identity matrix. It realigns the Primary axis with the positive X axis, the Secondary axis with the positive Y axis, and the Normal axis with the positive Z axis.

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

623

EE Raceway Modeling Reference Guide Addendum February 2003

command action by one step or to reject a highlighted element, press <R> or select Reject on the precision input form.

Steps
1. Select the Mirror Group command. The Mirror Group precision input form displays. 2. Identify the group you intend to mirror and accept it with <D>. The system highlights the specified group. If you do not locate an acceptable group, the system displays the message Group not found. The message disappears when you identify a valid group. 3. Specify the point about which to mirror the group. The Orient Mirror form displays. 4. Specify the mirror plane on which to mirror the group. 5. Click Accept. The group moves to the specified position. Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the mirror point and mirror plane for each accepted element.

624

Mirror Copy Group

This command creates a mirrored copy of a group of raceway elements as specified within the design file.

Field Descriptions
Mirror Point Displays the location of the specified mirror point. The primary vector of the orientation tee denotes the mirror planes normal vector. The elements are rotated about the plane formed by the secondary and the normal. Angle Specifies the angle by which to rotate the orientation tee. To change the displayed angle, select the field and type a new angle. About Specifies the axis about which to rotate the orientation tee. To change the displayed axis, toggle among the three axes (Primary, Secondary, Normal) until the appropriate axis displays. I Button Reorients the orientation tee along the identity matrix. It realigns the Primary axis with the positive X axis, the Secondary axis with the positive Y axis, and the Normal axis with the positive Z axis.

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. 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 Mirror Copy Group command. The Mirror Copy Group precision input form displays.

625

EE Raceway Modeling Reference Guide Addendum February 2003

2. Identify the group you intend to mirror and copy and accept it with <D>. The system highlights the specified group. If you do not locate an acceptable group, the system displays the message Group not found. The message disappears when you identify a valid group. 3. Specify the point around which to mirror the group. The Orient Mirror form displays. 4. Specify the plane on which to mirror the group. 5. Click Accept. The group copy displays at the specified position. Note: These steps are applicable for groups in Entire Group mode. For groups in Single Element mode, you can accept or reject constituent elements and set the mirror point and mirror plane for each accepted element.

626

Move Group
This command moves a group of raceway elements to a new location in 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. 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 Group command. The Move Group precision input form displays. 2. Identify the group you intend to move and accept it with <D>. The system highlights the specified group. If you do not locate an acceptable group, the system displays the message Group not found. The message disappears when you identify a valid group. 3. Specify an origin point from which to move the group. 4. Specify a placement point to which to move the group. The group moves to the specified position.

627

EE Raceway Modeling Reference Guide Addendum February 2003

Annotate Model
Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (p. 285 in the PDS 7.1 version of the document). The following information has been modified: Automatic sheet number See the following text for details.

This command adds or changes the annotation for the model. This command cannot prevent the duplication of sheet numbers within a project. The Load Database process, however, will prevent such duplication. The sheet number should be unique for each drawing. If the user does not specify a sheet number, the sheet number is automatically set to match the .dgn file name of the raceway model.

Steps
1. Select the Annotate Model command. The Annotate Element form displays.

2. Select the Column value field for sheet on the form and key in a new sheet number. If you want to display the annotation in the model, toggle the Display fields in the form to On. 3. Select Confirm to accept the new annotation. OR 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.

628

Reference PDS Model (replaces 16.2)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 372-373 in the PDS 7.1 version of the document). The following information has been modified: Display, Snap, and Locate toggles See the following text for details.

The Reference PDS Model command attaches and detaches models from the PDS project to the model as reference files. The model to attach can be from any discipline and design area in the project.

Parameters
Disciplines Lists all disciplines. Select the discipline that contains the model you want to attach; then, click Attach. Areas Lists all design areas defined in the active project. Select the design area that contains the model you want to attach; then, click Attach. Area/Model Specifies whether to attach all models in a design area or an individual model. Attach by Area Attaches all model in the selected design area. Attach by Model Displays all models in the design area so you can select which model you want to attach. Propagated/Sparse Specify whether you want to attach the sparse model or the corresponding propagated model. This option only displays if you are attaching a structural model. Display Toggle Specify whether to display the reference model in the active model views. Snap Toggle Allows you to snap to any segment in the reference file.

629

EE Raceway Modeling Reference Guide Addendum February 2003

Locate Toggle Allows you to data point to any component in the reference file. Apply To Discipline Defines the settings for the Display, Snap, or Locate toggles for the all attached models in the discipline of the selected model. Apply To All Defines the settings for the Display, Snap, or Locate toggles for all the attached models in all disciplines. Attach Attaches a reference model. You must select a Discipline and a Design Area before you can select a reference model to attach. Detach Detaches the selected reference model. You must click Show Attachments and select the reference model you want to detach before clicking Detach. Show Attachments Displays all reference models attached to the active model. Exit Exits the Reference Model command.

630

EE Raceway Project Database Schema Description (replaces panel)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 487 and 500 in the PDS 7.1 version of the document). The following information has been modified: PDS coordinates in Panel table Note about ee72upg.exe file See the following text for details.

This section lists and describes the tables in the EE Raceway project database schema, and includes detailed information about the columns that comprise each table. Note: An asterisk (*) indicates that you must not modify the column name. You should not modify those column names having a prefix of "ee_".

panel
This table contains information about all panels/equipment found in the drawing. Note: For project databases created with EE Raceway versions prior to 7.2, it is necessary to use the ee72upg.exe utility in the \eenuc\bin folder to add the new pds_east, pds_north, and pds_elev columns to the panel and msconfig tables of the existing project database. Before running the upgrade utility, use EE Configure to verify that values are set for EERD_TBLS, PROJECT_LOCATION, and EE_SCHEMA. Column Name mslink panel panel_descrip ee_approv_status ee_approv_date ee_create_date ee_last_rev_dat ee_eqp_table ee_part_key Type integer Char( 20) Char( 20) integer Char( 26) Char( 26) Char( 26) Char( 32) Char( 28) Index uniq dups no no no no no no no Null no yes yes yes yes yes yes yes yes

631

EE Raceway Modeling Reference Guide Addendum February 2003

pds_east pds_north pds_elev

real real real

no no no

yes yes yes

mslink: a unique integer value used by the software to identify a row in the panel table. panel: the column containing the panel/equipment name panel_descrip: the column containing the panel/equipment description. ee_approv_status: the column containing the approval status of the panel/equipment. ee_approv_date: the column containing the date when the approval status changed. ee_create_date: the column containing the panel/equipment creation date. ee_last_rev_dat: the column containing the date the panel/equipment was last revised. ee_eqp_table: the column containing the name of the reference database table that contains additional equipment information. ee_part_key: the column containing the unique key to the appropriate record of equipment information in the reference database table. pds_east: the column containing the PDS east coordinate of the panel (calculated by Load Database). pds_north: the column containing the PDS north coordinate of the panel (calculated by Load Database). pds_elev: the column containing the PDS elevation coordinate of the panel (calculated by Load Database).

632

EE File Structure (replaces Appendix F)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 529-540 in the PDS 7.1 version of the document). The following information has been modified: Windows folder listings replace CLIX directory structure See the following text for details.

This section describes the file structure for EE Nucleus and EE Raceway. It also describes the contents of directories and some files. It identifies those files you can modify. By default, the PDS Component Loader delivers these files to /win32app/ingr/. The directory tree for EENUC and EERWAY is shown below.

633

EE Raceway Modeling Reference Guide Addendum February 2003

EE Nucleus File Structure

EE Nucleus (EE Nuc) is the core product for the EE product line. The product may reside on any file system. EE Nucleus will reside under the win32app\ingr\eenuc directory. The list may differ slightly depending on which options are selected during installation. The following files exist under the ..\eenuc directory: \eenuc

\eenuc\bin

\eenuc\data

\eenuc\db

\eenuc\doc

\eenuc\font

\eenuc\forms

634

\eenuc\help

\eenuc\msg

\eenuc\share

\eenuc\sym

The following list gives a brief description of some of the files. The files are grouped by directory. eenuc readme.txt file containing description of product features and any fixes, problems, comments, etc. remove.exe command used to remove EE Nucleus from the machine. .EErc File containing global symbol definitions. EEnotice.txt File containing release notices. license.txt copyright notice file. bin contains the EE executable files and the environment process. The EE executable files set up variables specifying the location of MicroStation, INFORMIX, EE Nucleus, and EE Raceway, and then invokes the EE environment. background process that reports the exit status of a process run in the background. batch process that reports the exit status of a process run in batch mode. create_db create database process. dba_rpt DBAccess report process. dba_shell.cmd command executed around dba_rpt.

635

EE Raceway Modeling Reference Guide Addendum February 2003

ee72upg.exe executable command that updates the EE Raceway Project Database. eeconfig file that maintains EE product configuration for workstation/server. Eemgr.exe Electrical Engineer manager environment executable. eeprj.exe environment process. eeqpr.bat batch file to print 132 column reports to the laser printer. menu_shel.cmd command executed around eemgr to run the Edit Database process. mscrecol.cmd command to create mscolumns table for reference database. reeprj remote environment process. data Contains the ASCII files used to control certain environment procedures. print.dat ASCII file for output file management. manager.dat ASCII file for manager function management. dba* files DB Access files. db directory that contains the DB Access menu library (mgrdba_lib). Required DBAccess files are also delivered in this directory. doc directory that contains documentation. forms directory that contains all the environment forms. help msg contains EE Nucleus message files. share sym contains EE symbol files.

636

EE Raceway File Structure

This section lists and describes the directories and files delivered with EE Raceway. \eerway

\eerway\bin

\eerway\data

\eerway\db

\eerway\dgn

637

EE Raceway Modeling Reference Guide Addendum February 2003

\eerway\doc

\eerway\eden

\eerway\mdlapps

\eerway\msg

\eerway\report

\eerway\sym

\eerway\tmp Delivered empty The following list gives a brief description of some of the files. The files are grouped by directory. eerway readme.txt file containing a description of the product features and any fixes, problems, comments, etc.

638

 remove.exe executable file used to remove EE Raceway from the machine. bin contains all process delivered with the EE Raceway product. idet Interference Detection Envelope File Creation process. load processor to load the project database. rmon Controlling processor for interactive manipulations. unload_cln contains the unload sheet, unload drawing, and clean database processes. data Contains the ASCII files used to control process and report management for the EE Raceway product. These files can be modified. eden.dat controls Eden processes. process.dat controls process management. report.dat controls standard report management. rule_chk.dat controls rule check report management. db Contains the delivered sql files for the project and reference database. Also contains .unl files required for bulk loading special tables and the mscatalog table in the project database. Sample .unl files for bulk loading reference database tables are also provided. dgn Contains the seed file directory, available cell libraries, and any design files delivered with the product. rway_schma.dgn displays the structure of the EE Schema.

639

EE Raceway Modeling Reference Guide Addendum February 2003

rway_view.dgn explains the structure of the Raceway views.

640

 seed contains the available seed design files. seed.dgn delivered English drawing seed file. This may be customized. msseed.dgn delivered metric drawing seed file. This may be customized. doc contains documentation information on EE Raceway including README files from previous releases. eden contains the Eden symbol library. eden.lib the Eden symbol library file. mdlapps msg Contains EE Raceway message files and the file to correlate key-ins to EE Raceway commands. alias.cmd file used to correlate key-ins to commands. This file can be extended. command.msg message file containing all messages for the command field. These messages can be edited but messages cannot be added. error.msg message file containing all error messages for the error field. These messages can be edited but messages cannot be added. prompt.msg message file containing all messages for the prompt field. These messages can be edited but messages cannot be added.

641

EE Raceway Modeling Reference Guide Addendum February 2003

rway_prj.tbl file containing the entity numbers for the project database tables. rway_ref.tbl file containing the entity numbers for the reference database tables. status.msg message file containing messages for status field, prompting messages, and logo. These messages can be edited but messages cannot be added. report Contains the source (.ace)and compiled (.arc) SQL files for all delivered sch reports. The source files may be edited by the user. There is an .ace and an .arc file for each report listed below. rwaydba_lib DB Access template library. sym Contains all symbol files for EE Raceway menus. This directory also contains the available precision input forms. rwaybar.sym symbol file for the bar menu. rwaypnl.sym symbol file for the panel menu. tmp Holds any temporary files. The software requires this directory.

642

Index
annotate model, 629 Annotate Model command, 629 EE file structure, 634 Nucleus file structure, 635 Raceway file structure, 638 element mirror, 614 mirror copy, 616 modify, 608 rotate copy, 610, 612 file structure EE, 634 EE Nucleus, 635 EE Raceway, 638 group mirror, 624 mirror copy, 626 modify, 618 move, 628 rotate, 620 rotate copy, 622 intergrated commands Reference PDS Model, 630 Load Reference Schema command, 599 Mirror Copy Element command, 616 Mirror Copy Group command, 626 Mirror Element command, 614 Mirror Group command, 624 model annotate, 629 Modify Element commands, 608 Modify Group commands, 618 Move Group command, 628 palettes bar commands, 604 design, 605 EE Raceway, 602 EERway, 602 Intergrated Commands, 602 model commands, 607 modify, 605 modify element, 604, 608 modify group, 606, 618 runtime setup, 607 setup, 606 PDS reference model, 630 Reference PDS Model command, 630 reference schema load, 599 Rotate Copy Element command, 612 Rotate Copy Group command, 622 Rotate Element command, 610 Rotate Group command, 620 schema load reference, 599 utilities, 601

643

EE Raceway Modeling
Reference Guide Addendum
October 2004

DPDS3-PB-200005D
For PDS version 07.03.00.** This document supplements DPDS3-PB-200005C.

Table of Contents
Integrated Commands (replaces 16) .........................................................................646 Using the Integrated Commands ..............................................................................647 Reference PDS Model (replaces 16.2)......................................................................648
Area Volume Graphics....................................................................................................650

Appendix A Error Messages.....................................................................................652

645

EE Raceway Modeling Reference Guide Addendum October 2004

Integrated Commands (replaces 16)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 369-370 in the PDS 7.1 version of the document). The following information has been modified: Area Volume Graphics command See the following text for details.

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 elements attributes, review the PDS clashes in a model, create a window containing a specific element, display information about the reference models attached to the current model, and view the area volume graphics for clash and design areas. Note: 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.

646

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. Area Volume Graphics You must turn Construction Graphics on in MicroStation. See the command description for more details.

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.

647

EE Raceway Modeling Reference Guide Addendum October 2004

Reference PDS Model (replaces 16.2)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 629-630 in the PDS 7.2 version of the document). The following information has been modified: Added default value for Sparse/Propagated toggle. See the following text for details.

The Reference PDS Model command attaches and detaches models from the PDS project to the model as reference files. The model to attach can be from any discipline and design area in the project.

Parameters Disciplines Lists all disciplines. Select the discipline that contains the model you want to attach; then, click Attach. Areas Lists all design areas defined in the active project. Select the design area that contains the model you want to attach; then, click Attach. Area/Model Specifies whether to attach all models in a design area or an individual model. Attach by Area Attaches all model in the selected design area. Attach by Model Displays all models in the design area so you can select which model you want to attach. Propagated/Sparse Specify whether you want to attach the sparse model or the corresponding propagated model. This option only displays if you are attaching a structural model. The default value for this toggle is Propagated. Display Toggle Specify whether to display the reference model in the active model views. Snap Toggle Allows you to snap to any segment in the reference file. Locate Toggle Allows you to data point to any component in the reference file.

648

Apply To Discipline Defines the settings for the Display, Snap, or Locate toggles for the all attached models in the discipline of the selected model. Apply To All Defines the settings for the Display, Snap, or Locate toggles for all the attached models in all disciplines. Attach Attaches a reference model. You must select a Discipline and a Design Area before you can select a reference model to attach. Detach Detaches the selected reference model. You must click Show Attachments and select the reference model you want to detach before clicking Detach. Show Attachments Displays all reference models attached to the active model. Exit Exits the Reference Model command.

649

EE Raceway Modeling Reference Guide Addendum October 2004

Area Volume Graphics

The Area Volume Graphics command displays the interference checking and design areas in the model so that you can see their location.

For the Drawing Graphics environment, you can control the symbology of the volume graphics using the PDS Drawing Annotation Category Data option in the Project Data Manager in Project Administrator. Please refer to the Project Administrator Reference Guide for information on changing the volume graphic symbology. Before you can see the volumes in the Equipment, Raceway, PE_HVAC, and FrameWorks Plus environments, you must turn on the Constructions view attribute. You can activate the View Attributes dialog box by pressing CTRL+B. In addition, the following system environment variables must be defined to control the symbology and level of the volumes in the Piping, Equipment, Raceway, PE_HVAC, and FrameWorks Plus environments:
AREA_VOLUME_GRAPHICS_COLOR AREA_VOLUME_GRAPHICS_WEIGHT AREA_VOLUME_GRAPHICS_STYLE AREA_VOLUME_GRAPHICS_LEVEL

Please refer to the Project Setup Technical Reference for more information on setting environment variables.

Commands
Place Diagonal Lines - Displays diagonal lines within the volume marker for easier identification in the model. Add/Revise Graphics Adds design area volume graphics to the model. To add graphics, click Add/Revise Graphics, double-click the desired discipline, and double-click the desired area name. Remove Graphics - Removes the selected area from the model. Hilite Graphics - Highlights the area in the model. Update Graphics - Updates areas that are already displayed in the model. Use this command if the boundaries of the area are changed.

650

Show Displays all the design areas attached to the model. Can be used to exit any of the other commands on this dialog box at any stage. Exit - Closes the dialog box and exits the command.

651

EE Raceway Modeling Reference Guide Addendum October 2004

Appendix A Error Messages

Note: The information in this section supersedes the information in the corresponding section of previous versions of the EE Raceway Reference Guide (pp 377-414 in the PDS 7.1 version of the document). The following information has been modified: Changed color range from 0-127 to 0-255 in Color error message. See the following text for details.

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.

652

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.

Asid <numeric value>, straight connected to invalid system!

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>

653

EE Raceway Modeling Reference Guide Addendum October 2004

Reason: Display the elements 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.

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.

654

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.

Color not in range 0 to 255

Reason: The input is not within the valid range for a color. Recovery: Enter a new value within the range 0 to 255.

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.

655

EE Raceway Modeling Reference Guide Addendum October 2004

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.

Could not open file <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 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.

656

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.

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

Defaults do not exist for <string> key = <string>

657

EE Raceway Modeling Reference Guide Addendum October 2004

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.
A: Error Messages

Design file name <string> too long

Reason: The filename you specified exceeds 128 characters. Recovery: Key in a filename with fewer than 128 characters.

Design filename required!

Reason: No filename entered. Recovery: Enter design filename.

Directory <string> not found

Reason: A referenced directory cannot be found. Recovery: Enter correct directory name.

Drop point cell <string> not found in library

Reason: The drop point cell does not exist in the library. Recovery: Create a drop point cell and/or enter the correct drop point cell name in the EE Raceway 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.

658

Recovery: None.

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.

Element has no parent

Reason: The element with the given asid has no parent element. Recovery: Enter a new asid number.

Element not found

Reason: There does not exist an element with the given sector/word or asid. Recovery: Enter a new value.

Error building user data

Reason: Could not build user data.

659

EE Raceway Modeling Reference Guide Addendum October 2004

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.

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

660

Reason: Values for table not found in reference database. Recovery: Add entries to reference database.

Error in graphic bang placement.

Reason: Internal error. Recovery: Call Intergraph support.

Error initializing eden library <string>.

Reason: Could not open Eden symbol library. Recovery: Make sure that RWAY_EDEN_LIB and EDEN_LIB are set up properly in your .EErc file.

Error initializing unique table!

Reason: ee_unique table missing from the reference database. Recovery: Add the ee_unique table to the reference database.

Error initializing validity table!

Reason: Mscodelist table not found. Recovery: Add mscodelist table to reference table.

Error invalid column name in unique table!

Reason: Incorrect entry in ee_unique table. Recovery: Correct entry.

Error loading drawing!

Reason: No privilege for operation. Recovery: Add privilege to database.

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!

661

EE Raceway Modeling Reference Guide Addendum October 2004

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.

Error loading to equipment!

Reason: No privilege for this operation. Recovery: Add privilege to the database.

Error marking elements for deletion!

Reason: ee_to_drw column missing a table. Recovery: Add columns and try again.

Error merging annotation from design file!

Reason: Element annotation columns do not match columns in project database. Recovery: Change annotation of element.

Error No Placepoints or No Elements.

Reason: The Eden symbol definition must contain at least one placepoint, one datum point, and one element. Recovery: Modify the Eden symbol.

Error opening database!

Reason: Schema not found. Recovery: Add schema or enter correct schema name.

662

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.

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.

Error querying ref db for mscodelist

Reason: The mscodelist table does not exist or there is no connect permission. Recovery: Run the Create Database process with the rwayref.sql file.

Error reading TCB of design file!

Reason: TCB corrupted. Recovery: Call Intergraph support.

663

EE Raceway Modeling Reference Guide Addendum October 2004

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.

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.

664

Error unloading drawing!

Reason: No privilege to delete from database. Recovery: Add privilege to database.

Error starting or stopping graphic bang.

Reason: Internal 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.

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.

665

EE Raceway Modeling Reference Guide Addendum October 2004

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.

Font not in range 0 to 255

Reason: The input was not within valid range for a font. 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.

666

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.

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.

667

EE Raceway Modeling Reference Guide Addendum October 2004

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.

Invalid asid id
Reason: An element cannot be found in the design file with the given asid id. Recovery: Key in another asid id.

Invalid cell: <string>

Reason: The given cell is not the type the command expected. For example, Place Title Block must be 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.

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.

668

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.

Invalid Part Found at RCP asid <numeric value>.

Reason: The fitting at the RCP cannot be verified with the database. Recovery: Turn Part Verification off OR add the fitting to the database.

Invalid Part Found at oneline asid <numeric value>, vertex <numeric value>.
Reason: The elbow or straight at the one-line cannot be verified with the database. Recovery: Turn Part Verification off OR add the elbow or straight to the database.

Invalid RCP No one-lines attached

Reason: There are no one-lines associated with the raceway connect point (RCP). Recovery: Delete the RCP and place the one-line again.

Invalid RCP - Only two one-lines can be attached

Reason: The RCP has more or fewer than two one-lines attached. Recovery: You can only remove an RCP with exactly two one-lines attached.

Invalid real number: <string>

669

EE Raceway Modeling Reference Guide Addendum October 2004

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.

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.

Load initialization error!

Reason: Some other initialization error procedure failed. Recovery: Fix other problems.

670

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.

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

EE Raceway Modeling Reference Guide Addendum October 2004

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.

No Duplicate Group Name Allowed

Reason: The new group name matches the name of an existing group. Recovery: Key in another name.

No elements in fence
Reason: The defined fence does not contain a valid element within its borders. Recovery: Redefine the fence to include a valid element.

No memory available for form

Reason: The forms software could not allocate enough memory for creation of the form. Recovery: Exit completely and re-enter the product.

No memory available!
Recovery: Exit the process and re-enter and/or reboot the workstation.

No or Illegal Cross section type <string>.

Reason: The cross section must be of type A, B, or C in the active specification. Recovery: Modify the reference database to include A, B, C for the cross section type.

No overrides allowed without override button on

Reason: The Override button is not depressed. Recovery: Press the Override button and key in the value again.

No raceway one-line type defined

Reason: You must have at least one one-line type defined from the reference database in the design file.

672

Recovery: Define a one-line type from the reference database using the Define One-Line Type command.

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.

No valid special part tables exist

Reason: There are no special parts tables in the database. Recovery: Populate the database.

No valid special parts exist for this table

673

EE Raceway Modeling Reference Guide Addendum October 2004

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.

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.

674

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.

Raceway element not found

Reason: Unable to locate a valid raceway element (one-line, three-line, title block, RCP). Recovery: Identify one of these elements.

Raceway title block not found

Reason: Unable to locate a title block in the design file. Recovery: Place a title block in the design file.

Reference schema name required!

Reason: EES_REFDB has not been exported. Recovery: Export EES_REFDB.

Reference schema table missing required columns

Reason: A required column in the table for the element you are annotating is NOT in the table or in 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

675

EE Raceway Modeling Reference Guide Addendum October 2004

Reason: Could not find rows in the database fitting the specified find criteria. Recovery: Specify new find criteria.

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.

The value must be greater than zero

Reason: The width must be greater than zero. Recovery: Enter a new value greater than zero.

Title block placed - Some fields review only

Reason: Some fields are locked once you place the title block and, therefore, cannot be edited.

676

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.

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.

677

EE Raceway Modeling Reference Guide Addendum October 2004

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.

Warning must accept/reject System selection

Reason: You must accept/reject the system selection form before performing a group operation. Recovery: Accept or reject the system selection form.

Warning must keyin a group name

Reason: When performing the selected group operation, you must key in a group name. Recovery: Key in the desired group name.

Weight not in range 0 to 31

Reason: The input was not in the valid range for weight. Recovery: Enter a new value within the range of 0 to 31.

678

Index
Area Volume Graphics command ..................650 error messages ................................................652 integrated commands......................................646 Area Volume Graphics ...............................650 Reference PDS Model ................................648 PDS reference model ......................................... 648 Reference PDS Model command................... 648 volume graphics displaying .................................................. 650

679