PDS EE Raceway Reference Guide

EE Raceway Modeling
Reference Guide
Version 2011 (V12)

June 2011
DPDS3-PB-200005I
Copyright
Copyright 1991-2011 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 from Intergraph
Corporation.
U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the
United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
P.O. Box 240000
Huntsville, AL 35813
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the
licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license
for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this
software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee
permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and
delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or
redistribution.
Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or
applicable license for the software product signed by Intergraph Corporation, 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.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of
Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered
trademarks of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation
and/or its affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands and product
names are trademarks of their respective owners.
Contents
Preface PDS ................................................................................................................................................. 9
What's New in PDS EERACEWAY ........................................................................................................... 11
Introduction ................................................................................................................................................ 13
About the Reference Guide .................................................................................................................. 13
Basic Workstation Skills ........................................................................................................................ 13
Installation Instructions ............................................................................................................................ 15
Upgrading the Workstation ................................................................................................................... 15
Databases ............................................................................................................................................. 19
Electrical Engineer (EE) Environment ..................................................................................................... 21
Create ................................................................................................................................................... 24
Enter ...................................................................................................................................................... 25
Product Menu ........................................................................................................................................ 27
Copy ...................................................................................................................................................... 28
Delete .................................................................................................................................................... 29
Archive .................................................................................................................................................. 31
Restore .................................................................................................................................................. 33
Database Utilities .................................................................................................................................. 34
RIS schema utilities ........................................................................................................................ 35
Update Project Schema.................................................................................................................. 36
Update Reference Schema ............................................................................................................ 40
PDS Electrical Raceway Environment ..................................................................................................... 45
Modeling ................................................................................................................................................ 46
Load Reference Schema ...................................................................................................................... 46
Utilities ................................................................................................................................................... 48
Electrical Engineer (EE) Raceway Environment .................................................................................... 49
Create ................................................................................................................................................... 50
Design ................................................................................................................................................... 52
Process ................................................................................................................................................. 53
EDEN .................................................................................................................................................... 55
Report ................................................................................................................................................... 59
Rule Checks .......................................................................................................................................... 62
Utilities ................................................................................................................................................... 64
Copy ............................................................................................................................................... 66
Delete ............................................................................................................................................. 67
Undelete ......................................................................................................................................... 68
Purge .............................................................................................................................................. 69
Rename .......................................................................................................................................... 70
Send ............................................................................................................................................... 71
Receive ........................................................................................................................................... 72
Archive ............................................................................................................................................ 73
EE Raceway Modeling Reference Guide
Contents
Restore ........................................................................................................................................... 74
Output ............................................................................................................................................. 75
EE Graphics Interface Elements .............................................................................................................. 77
Start-up Sequence ................................................................................................................................ 77
Screen Display ...................................................................................................................................... 78
EERWAY Command Menu Bar ............................................................................................................ 80
Palettes in the EE Raceway Graphics Environment ............................................................................. 81
Identifying Elements .............................................................................................................................. 86
Working Units and Precision Key-ins .................................................................................................... 86
Workflow and Procedures ........................................................................................................................ 89
The Drawing Process ............................................................................................................................ 89
Databases ............................................................................................................................................. 95
Reports .................................................................................................................................................. 97
Interference Detection ........................................................................................................................... 97
Precision Input Form ............................................................................................................................. 97
Design Commands .................................................................................................................................. 107
Using the Design Commands ............................................................................................................. 108
Place One-Line ................................................................................................................................... 109
Route Around Vessel .......................................................................................................................... 111
Insert RCP........................................................................................................................................... 115
Rotate Cross Section .......................................................................................................................... 117
Place Drop Point ................................................................................................................................. 119
Place Equipment Pointer .................................................................................................................... 121
Define Active Point .............................................................................................................................. 122
Set Active Parameters ........................................................................................................................ 122
Place Manual Fitting ........................................................................................................................... 123
Conduit Sizing ..................................................................................................................................... 131
Insert One-Line Vertex ........................................................................................................................ 135
Place Field Routed Raceway .............................................................................................................. 137
Define Duct Cross Section .................................................................................................................. 139
Place Stub Up ..................................................................................................................................... 143
Modify Commands .................................................................................................................................. 147
Using the Modify Commands .............................................................................................................. 147
Modify Element Commands ................................................................................................................ 148
Using the Modify Element Commands ......................................................................................... 151
Annotate Element ......................................................................................................................... 151
Copy Element ............................................................................................................................... 156
Move Element ............................................................................................................................... 158
Clone Element .............................................................................................................................. 160
Move One-Line Segment ............................................................................................................. 163
Move One-Line Vertex.................................................................................................................. 166
Propagate Element ....................................................................................................................... 168
Edit/Insert Manual Fitting .............................................................................................................. 173
Modify One-Line ........................................................................................................................... 178
Place Fitting by Rule ..................................................................................................................... 180
Combine Coincident RCPs ........................................................................................................... 182
Delete Duplicate One-Lines ......................................................................................................... 183
Contents
Delete Element ............................................................................................................................. 184
Remove RCP ................................................................................................................................ 186
Delete Fitting ................................................................................................................................ 188
Remove One-Line Vertex ............................................................................................................. 189
Minimize Joints ............................................................................................................................. 191
Change System Parameters ........................................................................................................ 193
Rotate Element ............................................................................................................................. 194
Rotate Copy Element ................................................................................................................... 196
Mirror Element .............................................................................................................................. 197
Mirror Copy Element..................................................................................................................... 198
Modify Group Commands ................................................................................................................... 199
Using the Modify Group Commands ............................................................................................ 202
Define Group ................................................................................................................................ 202
Copy Element by Group ............................................................................................................... 206
Annotate Element by Group ......................................................................................................... 208
Clone Element by Group .............................................................................................................. 212
Propagate by Group ..................................................................................................................... 214
Place Fitting by Rule by Group ..................................................................................................... 215
Add Systems Group ..................................................................................................................... 216
Replace Systems by Group .......................................................................................................... 217
Minimize Joints by Group ............................................................................................................. 219
Delete Element by Group ............................................................................................................. 221
Rotate Group ................................................................................................................................ 222
Rotate Copy Group ....................................................................................................................... 224
Mirror Group ................................................................................................................................. 225
Mirror Copy Group ........................................................................................................................ 226
Move Group .................................................................................................................................. 228
Database Commands ......................................................................................................................... 229
Using the Database Commands .................................................................................................. 229
Load Database ............................................................................................................................. 230
Report ........................................................................................................................................... 233
Rule Checks ................................................................................................................................. 236
Setup Commands .................................................................................................................................... 239
Using the Setup Commands ............................................................................................................... 240
Set Raceway Defaults ......................................................................................................................... 241
Define System ..................................................................................................................................... 242
Define One-Line Type ......................................................................................................................... 244
Set Symbology Control ....................................................................................................................... 245
Symbology Control .............................................................................................................................. 246
Set Text Defaults................................................................................................................................. 248
Set Conduit Sizing Attributes .............................................................................................................. 249
Create Cell Commands ....................................................................................................................... 250
Using the Create Cell Commands ................................................................................................ 250
Create Model Cell ......................................................................................................................... 251
Create Equipment Pointer Cell ..................................................................................................... 253
Create Drop Point Cell.................................................................................................................. 255
Model Commands ............................................................................................................................... 257
Using the Model Commands ........................................................................................................ 258
Lock Model ................................................................................................................................... 259
Move Model Annotation ................................................................................................................ 259
Unlock Model ................................................................................................................................ 260
Annotate Model ............................................................................................................................ 260
Contents
Runtime Setup Commands..................................................................................................................... 263
Using the Runtime Setup Commands ................................................................................................ 264
Set Active One-Line Type Parameters ............................................................................................... 264
Set Active One-Line Type ................................................................................................................... 268
Set Active System ............................................................................................................................... 269
Propagation Setup .............................................................................................................................. 271
Set Active Levels................................................................................................................................. 272
Display Element Information ............................................................................................................... 273
Utilities Commands ................................................................................................................................. 275
Using the Utilities Commands ............................................................................................................. 276
Toggle Construction Display On/Off ................................................................................................... 277
Highlight Element by Sector/Word ...................................................................................................... 277
Highlight Element by ASID ID ............................................................................................................. 278
Highlight Element by Link ................................................................................................................... 281
Highlight Propagation Errors ............................................................................................................... 282
Display Sector/Word Value ................................................................................................................. 283
Display Element Type and ASID ID .................................................................................................... 283
Display Link ......................................................................................................................................... 284
Display System and One-Line Type ................................................................................................... 284
Active Coordinate System ................................................................................................................... 286
Activate Design Volume Coordinate System................................................................................ 286
Activate Plant Coordinate System ................................................................................................ 286
Show Active Coordinate System .................................................................................................. 286
Raceway Processes ................................................................................................................................ 287
Load Database .................................................................................................................................... 287
Unload Design..................................................................................................................................... 290
Unload Sheet ...................................................................................................................................... 292
Cleanup Database .............................................................................................................................. 294
Create Interference Envelope (default name) ..................................................................................... 296
Create Interference Envelope (given name) ....................................................................................... 297
Eden Processes ....................................................................................................................................... 301
Compile EDEN Symbol ....................................................................................................................... 302
Delete EDEN Symbol .......................................................................................................................... 304
List EDEN Symbol Library .................................................................................................................. 306
List EDEN User Functions .................................................................................................................. 307
Merge EDEN Symbol Libraries ........................................................................................................... 309
Compress EDEN Symbol Library........................................................................................................ 311
Extract EDEN Symbol From Library ................................................................................................... 312
Extract EDEN User Function From Library ......................................................................................... 314
Edit EDEN Symbol File ....................................................................................................................... 317
Integrated Commands ............................................................................................................................. 319
Using the Integrated Commands ........................................................................................................ 319
Reference PDS Model ........................................................................................................................ 320
Window to Named PDS Item .............................................................................................................. 321
Area Volume Graphics ........................................................................................................................ 323
Contents
Error Messages ........................................................................................................................................ 327
System/Application Manager Information ............................................................................................ 349
EE Databases ........................................................................................................................................... 359
EE Raceway Reference Database Schema Description .................................................................... 381
Specification ............................................................................................................................................ 423
Eden Symbol Generation ........................................................................................................................ 429
EE File Structure ...................................................................................................................................... 435
Customizing Environment Files ............................................................................................................. 443
alias.cmd file ............................................................................................................................................ 451
rway.cmds ................................................................................................................................................ 455
Reports ..................................................................................................................................................... 457
RIS Schema Manager .............................................................................................................................. 463
RIS Schema Definition File ..................................................................................................................... 471
EE Manager .............................................................................................................................................. 473
Database Edit Functions ..................................................................................................................... 475
EE Configure ............................................................................................................................................ 477
Index ......................................................................................................................................................... 479
Contents
Preface PDS
This document provides command reference information and procedural instructions for the Plant
Design System (PDS) EE Raceway modeling task.
List of PDS Documentation
DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide

DPDS3-PB-200004 - Drawing Manager (PD_Draw) User's Guide
DPDS3-PB-200005 - EE Raceway Modeling Reference Guide
DPDS3-PB-200006 - Interference Checker/Manager (PD_Clash) User's Guide
DPDS3-PB-200010 - PDS 3D Theory User's Guide
DPDS3-PB-200013 - PDS EDEN Interface Reference Guide Volume I : Piping
DPDS3-PB-200015 - PDS Equipment Modeling (PD_EQP) User's Guide
DPDS3-PB-200017 - PDS ISOGEN Reference Guide, Vol. 1
DPDS3-PB-200022 - PDS Piping Component Data Reference Guide
DPDS3-PB-200023 - PDS Project Setup Technical Reference
DPDS3-PB-200025 - PDS Stress Analysis Interface (PD_Stress) User's Guide
DPDS3-PB-200026 - Pipe Supports Modeler Reference Guide
DPDS3-PB-200028 - Piping Design Graphics (PD_Design) Reference Guide
DPDS3-PB-200030 - Project Administrator (PD_Project) Reference Guide
DPDS3-PB-200033 - Project Engineer HVAC (PE-HVAC) Reference Guide
DPDS3-PB-200034 - Reference Data Manager (PD_Data) Reference Guide
DPDS3-PB-200035 - Report Manager (PD_Report) User's Guide
DPDS3-PB-200041 - PDS EDEN Interface Reference Guide Volume 2 : Equipment
DPDS3-PB-200042 - PDS EDEN Interface Reference Guide Volume 3 : Pipe Supports
DPDS3-PE-200016 - PDS Express Project Creation Quick Start Guide
DPDS3-PE-200052 - PDS Ortho Draw User's Guide
DPDS3-PE-200029 - Piping Model Builder (PD_Model) Reference Guide
DPDS3-PE-200031 - Project Engineer HVAC Getting Started Guide
DPDS3-PE-200032 - Project Engineer HVAC Overview
DPDS3-PE-200045 - PDS Label Library Merger Utility
DPDS3-PE-200047 - PDS Reference Data Auditing Tool
DPDS3-PE-200048 - Pipe Supports Explorer Utility
DPDS3-PE-200050 - Batch Services Quick Start Guide
DPDS3-PE-200051 - Batch Services User's Guide
Preface PDS
10
What's New in PDS EERACEWAY

The following changes have been made to PDS EERACEWAY:
Version 2011 (V12)
A new toggle has been provided for unload design command to reset the mslinkgaes after
unloading design. (CR PB:112969)
11
What's New in PDS EERACEWAY
12
SECTION 1
Introduction
EE Raceway allows you to design, modify, and model electrical raceway systems in a three
dimensional environment.
EE Raceway serves a variety of general purposes, including:
Model building Uses either a centerline or a three-line component graphic to build a
three-dimensional raceway model.
Interference detection Creates the raceway component interference envelope files for input
to the PDS interference detection task.
Material takeoff Extracts a list of material required to construct a raceway model.
You can also use EE Raceway models as background drawings for designs created in other PDS
facility design disciplines.
About the Reference Guide

This document, the EE Raceway Modeling Reference Guide, provides descriptions of EE
Raceway commands and processes. It describes the basic workflow for creating an electrical
raceway model. Separate sections outline the preparation and responsibilities for the system
and/or application manager.
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
13
Introduction
14
SECTION 2
Installation Instructions
This section is an instruction sheet both for initial installation and for updating the workstation
software. The software covered includes baseline and application software, Electrical Engineer
(EE) Nucleus software, and EE Raceway Modeling.
Assumptions
The following assumptions have been made in the writing of this section.
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: MS SQL or Oracle. You will
need to consult individual documentation for these products for detailed information.
Overview
This chapter covers the following topics pertaining to installation/upgrading:
Upgrading the Workstation (on page 15)
Installation Procedure (on page 15)
Databases (on page 19)
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.
This section's examples assume that you are running the loader delivered with PDS; the loader
delivered to stand-alone EE Raceway sites may vary slightly.
15
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 system.
1. First, connect to the drive on which the distribution software resides. This may be a networked
drive, or it may be on your local system.
2. Double-click on setup.exe to invoke the Intergraph PDS Component Loader.
3. Select Continue to invoke the Intergraph Registration Data form. This form expects your user
name, company, and serial number (as delivered). Pressing Enter will have no effect until all
fields have been entered, including a valid serial number. The Continue button will remain
inactive until a valid serial number has been keyed in.
4. Select Continue when the button is no longer inactive. This will invoke the product selection
form.
16
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.
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.
17
6. Before executing the software, you must set the environment variables in your ee.cfg file.
Copy the ee.cfg file found in the win32app/ingr/eenuc directory into another directory not in
the EE or PDS structure. (Your login directory will be fine; you will modify this copied file, and
it needs to be placed somewhere that it will not be over-written when you next update the
software.)
7. Double-click on the EE Configure icon to display the Configure EE Environment form.
8. Use the browse command to locate and open the new ee.cfg file that you copied in the earlier
step.
The Reset command should always be used at this point to ensure that the
environment variables in the display window are those that belong to the file you just selected,
and not to a previously-selected file.
9. Set your user environment variables. Before you can enter the EE environment, you will need
to set at least the following variables:
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.
18
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.
For detailed information about creating and updating databases, see RIS Schema 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 (on page 34) in this reference guide.
For information about using the RIS Schema Manager product, see the appendix entitled
RIS Schema Manager (on page 463) in this reference guide or refer to the Relational
Interface System (RIS) Reference Manual.
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 (on page 34) section in this reference guide. The Database
Utilities section contains instructions for updating both project and reference schemas.
19
20
SECTION 3
Electrical Engineer (EE) Environment

Electrical Engineer (EE) products are accessed through the Electrical Engineer (EE) form. To
enter the Electrical Engineer form, click Electrical Raceway Environment on the main PD_Shell
form. When you key in EE, the Project Menu displays:
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.
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.
21
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.
Scrolling Through Listings

The listing area in the EE form provides you access to the projects and design files you will
manage using the available menu options. When a particular option is active, the item you select
from the listing area will display in the appropriate input field.
When listings fill more than one page, you can scroll up and down the list using the scroll bar. The
bar above the arrows indicates where you are in the listing. If the bar fills the space above the
arrows, all of the available listings are currently displayed.
Icons
There are three icons that can display on EE forms, in any combination:
22
accepts the current form settings, and executes the active process.
Reset returns you to the previous form and cancels the current form settings.
Cancel (X) exits the EE application entirely.
The menus will not allow you to perform illegal operations. For example, 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
.
Project Menu Options

The individual Project Menu options are discussed in the following sections:
Create (on page 24) Creates new EE projects.
Enter (on page 25) Accesses available EE applications and enters existing EE projects.
EE Product Menu (see "Product Menu" on page 27) Displays (and allows you to select
from) those EE applications that are loaded on the workstation, if there are more than one.
Copy (on page 28) Copies existing project files to new projects.
Delete (on page 29) Deletes EE project files.
Archive (on page 31) Archives EE project files to a floppy disk or network nodes.
Restore (on page 33) Restores archived EE project files from a floppy disk or network
nodes.
Database Utilities (on page 34) Accesses EE Update Schema utilities and RIS Schema
Manager.
23
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.
Field Descriptions
Project name --- This field allows you to enter the project name in uppercase or lowercase
letters, though uppercase letters are automatically converted to lowercase. Your project name
should have eight or fewer characters. A .prj extension is automatically appended to the
project file name when you select Confirm (), so you are not required to key in this extension.
Steps
1. Select Create from the Project Menu option list.
The Project name field displays below the scrolling area.

2. Select the Project name field, and key in the new project name.
3. Select Confirm () to create the project.
You may also want to create a new project schema when you create a project. For
information about creating a project schema, see RIS Schema Manager (on page 463).
OR
24

Select another option to ignore your input and cancel the Create process.
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.
25
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.
Password Echo This toggle controls whether or not the password is displayed in the
respective password fields.
Steps
1. Select Enter from the Project Menu option list.
The project listing displays.

2. Select a project from the listing area.
OR
Select the Project name field, and key in a project name.
The project schema (defaults to project name) and the current reference schema display
automatically.
You can make modifications to these fields, if needed.
3. Enter schema passwords if they were created for either schema. Identify the appropriate
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 (on page 463).
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.
26
Product Menu
The Product Menu form displays all of the available EE products on your workstation. If only one
EE product exists on your workstation, then the environment bypasses the Product Menu and
goes directly into the selected product's Design Menu.
Only the EE products you actually have installed on your workstation will be displayed on
this menu.
Steps
1. Select the desired EE application from the Product Menu form.
The Design Menu displays. (See the chapter entitled Electrical Engineer Raceway
Environment for more information about the Design Menu.)
27
Copy
This option copies all the files within an existing project to a new project.
Field Descriptions
Copy project from Key in the source project name (or select it from the list).
Copy project to Key in the destination project name; this cannot be the name of a project
that already exists.
Steps
1. Select Copy from the Project Menu option list.
2. Select a project to be copied from the listing area.
OR
Select the Copy project from input field, and key in a project to be copied.
3. Select the Copy project to input field, and key in the new project name.
You cannot key in the name of an existing project in the Copy project to field.
4. Select Confirm () to copy the project.
OR
28

Select another option to ignore your input and cancel the Copy process.
Delete
This option completely deletes all the files and databases within an existing project.
Field Descriptions
Project name Key in (or select from the list) the project to be deleted.
Steps
1. Select Delete from the Project Menu option list.
2. Select the project name from the listing area.
OR
Select the Project name field, and key in the project name.
29

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.
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 (on page 463).
If a database does not exist in the project directory, a warning displays indicating that you are
about to delete an entire project.
30

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.
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.
31
Password This field accepts the password (if one exists) for the destination node. A
password is required if you are using the TCP option.
Steps
1. Select Archive from the Project Menu option list.
2. Select the Project name from the scrolling area.
OR
Select the Project name field, and key in a project name.
3. Select the storage facility for your project files.
Network is the default setting on the Network/Floppy toggle. Toggling to Floppy changes
the displayed form information.
Default values for the remote node name, user name, and remote directory may be assigned
in the user's .EErc file, using the global symbols EE_NODENAME, EE_USERNAME, and
EE_REMDIR. (If you need more information about the .EErc file, contact your system
administrator.)
When archiving using a floppy disk, you must have a formatted floppy disk placed in
the disk drive.
4. Select Confirm () to begin archiving.
OR
Select another option to ignore your input and cancel the Archive process.
32
Restore
This option retrieves an entire project and any associated database from a network or a floppy
disk.
When restoring from a network, you cannot restore a project that is currently listed in the
listing area. You must delete or rename the current project to complete the restore process.
When restoring from a floppy, you can restore a project that is currently listed in your
listing area. The project on the floppy will overwrite the project in your directory. Be sure to verify
that archived project will not overwrite existing projects with the same name.
Field Descriptions
Remote node name/address This field accepts the node name or address of the system
from which to receive the project.
TCP/XNS This toggle allows you to choose between TCP and XNS network protocols. A
password is required if you use the TCP option.
Remote path/directory This field accepts a key-in for the project's node of origin.)
Password Echo This toggle allows you to display the user password you enter in the
Password field.
Username on remote node This field accepts the user name for the node of origin.
33
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.
Steps
1. Select Restore from the Project Menu.
2. Select the Project name field, and key in a project name.
3. Indicate the storage location for your project.
Network is the default setting on the Network/Floppy toggle. Toggling to Floppy changes
the displayed form information.
When restoring from a floppy disk, you must have the disk in the disk drive.
4. Select Confirm to begin restoring.
OR
Select another option to ignore your input and cancel the Restore process.
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 (on page 35)
Update Project Schema (on page 36)
Update Reference Schema (on page 40)
34
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 (on page 463) supplies examples of Create Schema
input for several RDBMSs.
Normally this is a procedure for a system or application manager.
35

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 (on page 463).
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.
36

For additional information about updating schemas, see EE Databases (on page 359).
Field Descriptions
Output file Defines the processing message file name.

Error file Defines the error processing message file name.
Schema name Defines the project database's schema name. To enter the schema name,
select the field and key in the name of an existing project schema.
Schema password Defines the schema password, if one exists. To enter the password,
select the field and key in the name of the password corresponding to the schema name you
entered.
Password Echo/No echo This toggle defines if you want to display the schema password
input. To display the schema password input, set the toggle to Echo.
Application checkboxes -- These boxes allow you to select the EE application(s) with which
you are updating the schema. Only those products loaded on your workstation will display as
options. You can update the schema with multiple products, though doing so will slow
processing time.
37
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 (on page 53).
Steps
1. Select the Update project schema option from the Database Utilities form.
The Update project schema form displays:

2. Set up the form to meet your specifications.
3. Select Confirm () to update the project schema.
The update process displays the message Processing ...
OR
Select Reset to return to the Database Utilities form without retaining your input. Return to
step 1.
4. When Update project schema finishes processing, it will display one of two message files to
the screen:
38
If the schema is updated without errors, the system displays a processing message file
(create_db.msg).
OR
39

If errors occur during the update process, the system displays an error message file
(create_db.err).
You can also access these message files, located in the current project's /tmp
directory, using the Output option on the Utilities form. For more information, see Output (on
page 75).
5. Select Reset on the message file form to return to the Update project schema form.
6. Select Reset again to exit the process and return to the Database Utilities form.
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 (on page 359).
Field Descriptions
40
Output file Defines the processing message file name.

Error file Defines the error processing message file name.
Schema name Defines the reference database's schema name. To enter information,
select the field, and key in the name of an existing reference schema.
Schema password Define the schema password, if one exists. To enter information,
select the field, and key in the name of the password corresponding to the schema name you
entered.
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 (on page 53).
Steps
1. Select the Update reference schema option from the Database Utilities form.
The Update reference schema form displays.

2. Set up the form to meet your specifications.
3. Select Confirm () to update the reference schema.
The update process displays the message Processing ...

OR
Select Reset to return to the Database Utilities form without retaining the form parameters.
Return to step 1.
4. When Update reference schema finishes processing, it will display one of two message files.
41

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

If errors occur during the update process, the system displays an error message file
(create_db.err).
You can also access these message files, located in the current project's /tmp
directory, using the Output option on the Utilities form. For more information, see Output (on
page 75).
5. Select Reset on the message file form to return to the Update reference schema form.
6. Select Reset again to exit the process and return to the Database Utilities form.
43
SECTION 4
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 (on page 46) Allows you to open a design file in the PDS Raceway modeling
environment.
Load Reference Schema (on page 46) Allows you to update the Raceway reference
schema.
Utilities (on page 48) Allows you to access EE Raceway commands for EE Raceway
processes, EDEN symbols, reporting, and rule checks.
45
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.
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.
46
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.
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.
47
Utilities
This option accesses the EE Raceway Process, EDEN, Report, and Rule commands.
Commands
48
Process (on page 53) 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 (see "Eden Processes" on page 301) 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 (on page 59) 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 (see "Rule Checks" on page 62) 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.
SECTION 5
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 (on page 27) for more information)
OR
The EE Raceway Design Menu.
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 (on page 50) Allows you to create a design file.
49
Electrical Engineer (EE) Raceway Environment
Design (on page 52) Allows you to enter a design file and attaches the EE menus.
Process (on page 53) Allows you to list and select EE Raceway processes. It also
processes work on design files and/or databases.
EDEN (on page 55) Allows you to design your own symbols for raceway elements.
Report (on page 59) Displays the information in an EE Raceway database.
Rule (see "Rule Checks" on page 62) Displays the design rule errors occurring in the
design process.
Utilities (on page 64) Allows you to access functions needed to manipulate EE Raceway
design, rule, report, and message files.
Create
This option creates design files, based on a specified seed file.
When you create a drawing, you are actually copying a seed file (a template). The seed file
contains basic information that EE Raceway uses. A seed file can also contain customized
information like company borders and logos.
EE Raceway is delivered with both a metric (mseed.dgn) and English seed file (seed.dgn). You
can also use seed files that were generated in a Plant Design (PDS) environment. EE Raceway
will convert PDS seed files to raceway design files the first time you enter the EE Raceway
graphics environment.
50

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.
A file extension of .dgn is automatically appended to the drawing name if you do not enter
your own file extension.
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.
51
Design
This option accesses the graphics environment, taking you into a specified existing design file.
Steps
1. Select Design from the Design Menu.
2. Select the drawing name from the listing area.
The system invokes the graphics environment.

OR
Select another option from the Design Menu to ignore your input and cancel the Design
process.
52
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
(on page 287) 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.
53

When you enter a specific process, an input screen displays.
You must key in any information not already shown as defaults. You can override default values
by keying in your own information. All drawings are displayed on the screen scrolling area. An
asterisk (*), when placed in the Enter Drawing Name input field, is a wild card character which
can be used to list a subset of your drawings. For example, if you enter a*, all drawings beginning
with the letter "a" will be displayed. The ? character can also be used as a wild card for a single
character. Once you have entered all necessary information, select Confirm () to execute the
process.
Operating Modes
The Processing toggle allows you to select the operating mode for a process. The default mode
is Foreground, but you can toggle between that option and the Background and Batch 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.
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
54

colon (hour:minute). The suffix AM or PM may be appended; otherwise, a 24-hour clock (military
time) is understood. The system also recognizes the names NOON, MIDNIGHT, NOW and NEXT.
Optionally, you can specify a date using either a month name followed by a day number or a day of
the week (fully spelled or abbreviated to three characters). The system recognizes the words
TODAY and TOMORROW. If you input no date, the system assumes it should run the job TODAY
if the specified hour is greater than the current hour, and TOMORROW if the specified hour is less
than the current hour.
Legitimate commands include:
0815am Jan 24
8:15am Jan 24
Now + 1 day
5pm Friday
Steps
1. Select Process from the Design Menu.
2. Select a process from the listing area.
3. Select Confirm to invoke the input form for the specified process.
OR
Select another option from the Design Menu to ignore your input and cancel the Process
option.
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.
55

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.
his section provides general information about running all Eden program options. For
detailed information about individual Eden options, see Eden Processes (on page 301).
56

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

Entering Time in Batch Mode
If you select batch mode, an input box displays, allowing you to enter the time and date when you
want the option to begin processing.
The time can be entered as 1, 2 or 4 digits. One- and two-digit numbers are taken to be hours, four
digits to be hours and minutes. The time can also be specified as two numbers separated by a
colon (hour:minute). The suffix AM or PM may be appended; otherwise, a 24-hour clock (military
time) is understood. The special names NOON, MIDNIGHT, NOW and NEXT are also recognized.
You can specify an optional date in the form of either a month name followed by a day number or
a day of the week (spelled in its entirety or abbreviated to three characters). The system accepts
the words TODAY and TOMORROW. If you input no date, the system assumes that if the
specified hour is greater than the current hour, it will run the job TODAY, and if the specified hour
is less than the current hour, it will run the job TOMORROW.
Legitimate commands include:
0815am Jan 24
8:15am Jan 24
Now + 1 day
5pm Friday
58
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 (on
page 457) 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).
59

When you process a report, an input screen displays, allowing you to enter all input necessary to
run the report.
Key in any information that is not supplied by default. You can change the name of the output file
or error file. To change the output filename, select the output file box and key in a new name. (No
file extension is automatically appended to the name you key in.)
If you want to save reports throughout a project, you should name the output files
yourself. If a new output file has the same name as an existing file, the new file will overwrite that
file. You should give each report you want to save a unique name.
Steps
1. Select Report from the Design Menu.
2. Select a report from the listing area.
3. Select Confirm () to invoke the input form for the specified process.
OR
Select another option from the Design Menu to ignore your input and cancel the Report
option.
60

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.
61
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 (on page 457).
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.
62

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.
yourself. If a new output file has the same name as another file created previously, the new file will
destroy the previously created file. You should give each report that you want to save a unique
name.
Steps
1. Select Rule from the Design Menu.
2. Select a rule check report from the listing area.
3. Select Confirm () to invoke the input form for the specified process.
OR
Select another option from the Design Menu to ignore your input and cancel the Rule option.
63
Utilities
This option manipulates files within a project. All manipulations are performed on those files
residing in the current project's directories.
64

When you select Utilities from the Design Menu, the Drawing Utility Menu displays.
Files in the current project sub-directories will be listed in four columns. Each column will list a
different subdirectory.
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 (on page 66) Copies a file.
Delete (on page 67) Deletes a file (mark for purging).
Undelete (on page 68) Undeletes a file (unmark for purging).
Purge (on page 69) Purges (permanently deletes) a file.
Rename (on page 70) Renames a file.
Send (on page 71) Sends a file to a network node.
65
Receive (on page 72) Receives a file from a network node.

Archive (on page 73) Archives a file to a network node or floppy disk.
Restore (on page 74) Restores an archived file from a network node or floppy disk.
Output (on page 75) Outputs a file to a printer, screen, or plotter.
Steps
1. Select Utilities from the Design Menu.
2. Select the desired option from the Drawing Utility Menu, and then select the file(s) on which
to perform that option.
3. Enter necessary form information for the active option.
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.
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.
66

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.
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.
67
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.
68
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 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.
69
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
70
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.
Send
This option copies a file to a network node. Be sure to include the entire filename including the
extension (for example, test1.dgn). If you are sending a design file to a VAX, turn on the IGDS
toggle. Doing so will store the file in contiguous blocks on the VAX.
Field Descriptions
Password Echo toggle The setting of this toggle determines whether the password of the
remote machine is visible or hidden upon keyin to the password field.
TCP/XNS Protocol toggle The setting of this toggle determines whether the transfer uses
the TCP or XNS protocol to communicate between machines.
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.
71
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.
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
72
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.
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.
sending machine. The password may or may not be visible in the field, depending on the
Local path (dgn, rpt, chk, tmp) This field expects the path to the desired location of the file
being received.
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 (on page
31).
Field Descriptions
archiving machine is visible or hidden upon keyin to the password field.
73
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.
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.
remote machine. The password may or may not be visible in the field, depending on the
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 (on page 33).
This option will overwrite any file having the same name as the file you are restoring.
74
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.
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.
Username on remote node This field expects the username on the remote machine.
remote machine. The password may or may not be visible in the field, depending on the
Output
This option sends files to the printer, screen, plotter, or laser printer. Invalid operationssending a
drawing to the printer, for exampleare not allowed. If you do not specify an output destination,
the selection displayed at the top of the list is the default selection.
75

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
76
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.
SECTION 6
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 (on page 77)
Screen Display (on page 78)
EERWAY Command Menu Bar (on page 80)
Palettes in the EERWAY Graphics Environment (see "Palettes in the EE Raceway Graphics
Environment" on page 81)
Identifying Elements (on page 86)
Working Units and Precision Key-ins (on page 86)
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.
Start-up Sequence
When you enter an EERWAY design file (see Design (on page 52)), 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.
77
Screen Display
The screen display you will see when you enter a design file is described below.
If you have modified the default application menu configuration file, as described in the
previous section, your screen display may be different. (Check with your system manager if you
have a customized rway.cmds file.)
1. MicroStation Command Window contains the following fields that display system
messages and your inputs from the keyboard:
78
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.
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.
KeyIn 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
pulldown menu of available commands or command palettes.
3. Working Area displays elements as you place them. All your design work occurs in the
screen working area.
4. Windows provide ways for you to change the way you look at your design. The number
and name of each view appears in the window title area.
Window Manipulation buttons provide ways to manipulate windows.

Window Menu button displays a list of window actions. Doubleclicking 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.
79
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.
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 pulldown menu that
contains commands for various EERWAY tasks; you can also access command palettes from
these pulldown menus, when applicable.
To select a keyword, place the cursor over the button and press <D>.
For instance, selecting File initializes the File pulldown 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
frequentlyused MicroStation commands.
Remove Palettes Removes all palettes that have been invoked.
Compress Design Invokes MicroStation's Compress Design command.
Exit Executes the File Design command, and exits the graphics environment to return
control to the EE Raceway menu interface.
Integrated Commands Invokes the Integrated Commands menu.
80
Palettes in the EE Raceway Graphics Environment

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

Bar Commands
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.
82

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

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

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.
Utilities
This palette is activated by selecting Utilities from the MicroStation command window, then
selecting Palette.
85

Database
This palette is activated by selecting Database from the MicroStation command window, then
selecting Palette.
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.
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)
86

In EERWAY, predetermined values for working units in imperial and metric projects were used to
create the delivered cell library. If using this cell library, we recommend that you use these default
settings:
Unit
Imperial
Metric
1 Master Unit
1 foot = 12 subunits
1 meter = 1000 subunits
1 Subunit
1 inch = 8000 positional units
1 millimeter = 10 positional units
1 Positional Unit
1/8000 inch
1/10 millimeter
While these are the suggested working units for delivered cell libraries, you are not limited
to using only them. You may set your working units to any desired value, if a user-created cell
library is being used. (See your system manager for more information about the working units
settings used at your location.)
Below are some examples of values and how to key them in:
1/2 foot
= :6 (6 subunits)
= .5 (1/2 master unit)
1/2 inch
= :.5 (1/2 subunit)
= :1/2 (1/2 subunit)
= :0:4000 (4000 positional units)
18 inches
= 1.5 (1-1/2 master units)
= 1:6 (1 master unit and 6 subunits)
Precision Key-ins
Precision key-ins let you place points accurately to create elements and shapes with exact lengths
and areas. You specify a distance and an angle from the last point placed, or you can specify the
delta values in X and Y to place another point. Key-ins are entered through the alphanumeric
keyboard.
There are several ways to key in precision points, as described below:
DI=(distance, direction) - To place a precision point, key in the distance in MU:SU:PU
working units and the direction in degrees that you want the point to be placed. The new point
is placed relative to the previous point. For example, if you want to place a point 10 inches
directly to the right, key in DI=0:10,0.
DL= (delta coordinates) - To place a precision point, key in the delta x and delta y in
MU:SU:PU that you want the point to be placed. The new point is placed relative to the
previous point. For example, if you want to place a point 18 inches over and 18 inches up, key
in DX=1:6,1:6.
XY= (absolute coordinates) - To place a precision point, key in its absolute x and y
coordinates.
87
88
SECTION 7
Workflow and Procedures

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 (on page 349).
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.
The Drawing Process

Before outlining a typical workflow for drawing a raceway, it is important to describe basic raceway
concepts.
Typically you begin drawing raceways with one-line elements (one-lines). These one-line
drawings are the centerlines of raceways and through propagation become the three-dimensional
shapes (three-lines) that occupy the volume of the raceways. EE Raceway Modeling software
allows you to place one-lines and then propagate them into three-lines or raceways.
The figure below displays one-line elements on the left. On the right are the same elements after
propagation.
This section is divided into individual descriptions of the steps involved in the drawing process. In
general, you should perform these steps in the order in which they are described. The following
steps comprise the drawing process and this section:
System manager setup
Drawing setup
89
Place one-lines
Propagation
System Manager Setup

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 (on page 423)
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.
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 (see "Define System" on page 242) 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 (on page 269) 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 (on page 244) 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 (on page 268) for more information.
Set Symbology
Once you have defined your systems and one-line types, you can change the default symbology
settings for them. Doing so involves two commands: Set Symbology Control and Symbology
Control.
Use the Set Symbology Control command to define the matrix of systems and one-line types for
the design's symbology control. See Set Symbology Control (on page 245) 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 (on page 246) for more information.
90

Set Active Parameters
Each one-line type has its own set of parameters or catalogs. As you place one-line segments,
you are also placing the data associated with that one-line type in the reference database 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 (on
page 264) 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.
SeePropagation Setup (see "Propagation Setup" on page 271) for more information.
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 (on page 109); Place Manual
Fitting (on page 123); and Precision Input Form (on page 97) 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.
91

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).
Once you place and accept a run, you can continue placing one-lines. See Design Commands (on
page 107) for a description of the Place One-Line command.
Propagation
A one-dimensional raceway is composed of one-line segments. To convert this one-dimensional
view of the raceway to a three-dimensional view, use the Propagate command, see Propagate
Element (on page 168) for more information.
When you propagate a one-line segment into a three-line element, the three-line element's shape
is determined by the one-line type (tray, for example). The length of each three-line segment is
determined by the length of the one-line, and the width and height (or diameter) of a segment are
determined by the active parameters when you placed the one-line. The default fitting radius
determines the radius of any bends between raceway segments. This radius is used to propagate
fittings between straight segments.
Sketch and Eden Modes

There are two modes of propagation in EE Raceway: Sketch and Eden.
Sketch: In Sketch mode, one-lines are propagated into three-lines based on the cross section
and the radius, extension, and transition information stored for the one-lines and RCPs.
Sketch is the quicker mode of propagation for two reasons. First, all information necessary for
sketching the three-line is stored in the design file, so reference database access is not
required. Second, the three-dimensional elements are drawn in-line without accessing the
Eden symbol library.
Sketch propagation places the sketched fittings based on the environment in which the
one-lines come together. For example, where two tray sections come together at a 90 degree
angle, propagation will automatically sketch a 90 degree elbow.
92
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 (see "Place Manual Fitting" on page 123) 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.
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 (on page 282). For a detailed description of these
error messages, see Error Messages (on page 327).
93

Seamless Tubing Representations
In the following three-line representations of a bend 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 of the circles to be placed on level 63, the propagation mode must be se to sketch.
94
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.
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
95

below the annotation input area (see Annotate Element (on page 151)). 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.
With the addition of RIS to the EE Raceway product, a distinction is now made between schema
and database. The database is the file where the non-graphic drawing data (one-lines, three-lines,
etc.) are stored. A schema is a RIS-specific file that contains a description of the columns and
tables of the database, and also identifies which users will be allowed to use the database.
96
Reports
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 (on page 49) for general information about
running reports. For more detailed information about the individual reports, see Reports (on page
457).
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) (on page 296) for more information about the
Interference Detection process.
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.
Identify an absolute point.
Specify a delta coordinate to move.
Specify an absolute coordinate to move.
Specify a series of coordinate changes to move.
97

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 for instructions about changing the form design.
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. To change the displayed working view, select the field, and scroll through the
available views until the appropriate view displays.
Pressing <D> in a view for the placement of points simultaneously overrides the active
view setting.
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>.
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 keyin for distance, while only Move To accepts a data point for input.
98
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.
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 oneline type.
The middle field displays the active oneline 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
99

Justification Point The justification point defines
the location of the threeline duct bank graphic in relation to the oneline graphic. Three
justification points are available: lower left, lower center, and lower right. This option is available
when placing ductbanks.
100
Height and Width These fields are used to define a ductbank element's
dimensions during placement. This option is available when placing ductbanks.
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.
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 oneline. When you
identify a oneline, 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 OneLine Segment.
Identify the oneline 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 oneline segment.
The command highlights one of the segment's endpoints.

OR
Press <R> to reject the segment, and return to the previous step to identify another oneline.
4. Accept/reject end point
Press <D> to accept the highlighted endpoint as your reference point.
OR
101

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 oneline, 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.
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
oneline 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 oneline type, or half the height/width of the active
oneline 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 oneline type, or half the height/width of the active
102

oneline 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.
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:
103
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.
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.
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 (on page 263) for more information
on the available commands.
104
105
SECTION 8
Design Commands
The Design palette is activated by selecting Design from the EERWAY Command Menu Bar,
then selecting Palette from the resulting pull-down menu.
The commands on this palette place raceway elements -- one-lines, manual fittings, raceway
connect points (RCPs), drop points, and equipment pointer symbols -- in the design file. You can
also use these commands to enter an active point, change the active design parameters, rotate
cross sections, and size conduit and duct banks. There are also commands available for routing
one-lines around vessels and for inserting vertices in an existing one-line.
Using the Design Commands (on page 108) Outlines the prerequisites, group workflow, and
basic instructions for using the Design commands.
Place One-Line (on page 109) Places the centerlines of raceway elements.
Route Around Vessel (on page 111) Routes elements parallel to an arc, circle, and
right cylinder.
Insert RCP (on page 115) Places a raceway connect point (RCP) in your raceway
model.
Rotate Cross Section (on page 117) Rotates a cross section at the current cross
section angle.
Place Drop Point (on page 119) Places a drop point symbol in the design file.
Place Equipment Pointer (on page 121) Places an equipment pointer symbol in the
design file.
Define Active Point (on page 122) Places an active point in the design file.
107
Design Commands
Set Active Parameters (on page 122) Sets the active parameters in the design file
based on an identified one-line or RCP.
Place Manual Fitting (on page 123) Places a manual fitting in the design file at the
specified orientation and location.
Conduit Sizing (on page 131) Sizes conduit by "placing" cables in the conduit to
determine the percent fill.
Insert One-Line Vertex (on page 135) Places a vertex in an existing one-line.
Place Field Routed Raceway (on page 137) 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 (on page 139) Defines the cross section configuration of
the contained conduit for an underground conduit duct bank.
Place Stub Up (on page 143) Places conduit stub ups from an underground
ductbank.
Using the Design Commands

When to Use These Commands
Once you have performed the necessary setups, you can use these commands throughout the
design session.
Before Using These Commands

These commands require that you have an active system and one-line type defined in the design
file. See Setup Commands (on page 239) and Runtime Setup Commands (on page 263) for
instructions about setting up your systems and one-line types.
You must have conduit one-lines placed in the design file before you can use the Conduit Sizing
command. Likewise, you must have ductbank one-lines placed before you can use the Define
Duct Cross Section command.
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 (on page 97).
108
Design Commands
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.
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.
109
Design Commands
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.
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.
If a new RCP is placed on a cross section, a drop point symbol is placed at the beginning
and/or termination point.
You can attach to or continue manually placed straights.
If you reject all routing options for the beginning and/or termination points of a one-line, then
the command places a new RCP by default. This allows RCPs to be placed on top of one
another without establishing connectivity, though it is not a recommended practice.
If the beginning or termination action is break, attach, or continue, then the identified one-line
or RCP must have at least one system in common with the active systems.
If the beginning and termination actions are continue, then the two identified one-lines must
have all systems in common.
If the beginning or termination action is break, attach, or continue, then the identified one-line
must be of the same one-line type as the active one-line type.
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 (on page 97).
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
110
Design Commands
and Set Active System in Runtime Setup Commands (on page 263). In addition, you should be
familiar with the Set Raceway Defaults command (see Set Raceway Defaults (on page 241)).
Steps
1. Select the Place One-Line command.
The Place One-Line precision input form displays.

2. Begin entering points to sketch the one-lines. Refer to the description of routing options at the
beginning of this section to determine proper routing.
3. Complete the routing.
The system places cross sections and RCPs (if they do not already exist) on the ends of the
one-line.
4. Data Point Accepts, Reset Rotates
Press <D> to accept the cross section rotation, and return to step 2.
The system saves the rotation and returns to the beginning of the command, prompting you to
Enter first data point.
OR
Press <R> to rotate the cross section by the rotation angle defined in Raceway Defaults.
The system rotates the cross section and prompts you again to accept or continue rotating it.
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.
111
Design Commands
A fitting on the RCP can only have two attach points, such as an elbow. Wye and tee
fittings cannot be used.
112
Design Commands
step or to reject a highlighted element, press <R> or select Reject on the precision input form.
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.
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
113
Design Commands
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.
114
Design Commands
Insert RCP
This command breaks an identified one-line in the design file and inserts a raceway connect point
(RCP).
115
Design Commands

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.
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.
116
Design Commands
OR
Exit the command.
Rotate Cross Section

This command rotates a cross section using the current cross section rotation angle. For duct
bank cross sections, this command does not rotate duct bank's cross section, but changes the
duct bank justification location.
117
Design Commands
You can change the rotation angle in the EE Raceway Defaults form, see Set Raceway Defaults
(on page 241) for more information.
118
Design Commands
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.
The system highlights a valid cross section. If you do not locate an acceptable element, the
system displays the message Element not found. The message disappears when you identify a
valid cross section.
OR
Exit the command.
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
(on page 241) 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.
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.
119
Design Commands
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.

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

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.
120
Design Commands
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.

Steps
1. Select the Place Equipment Pointer command.
Identify an RCP in the design file and accept it.
The system highlights a valid RCP. If you do not locate an acceptable element, the system
displays the message Element not found. The message disappears when you identify a valid
RCP.
OR
3. Enter data point to place
Place a data point at the desired location for the equipment pointer symbol.
The system places the equipment pointer symbol as specified.

Continue placing equipment pointer symbols in the design.
OR
Press <R> to select another RCP.
121
Design Commands
Define Active Point

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

Steps
1. Select the Define Active Point command.
The Enter Active Point precision input form displays.

2. Enter active point
Specify a data point in the design file where you want the active point to be.
The command makes the specified data point the active point, and exits the command.
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.

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.

122
Design Commands
OR
3. Accept/reject
Press <D> to accept the element as the one to use.
The system sets the active one-line type, system, and one-line type parameters based on the
highlighted element. The command exits automatically.
OR
Press <R> to reject the highlighted element. Return to step 2.
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.
123
Design Commands
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 (on
page 122).
Set Active System Displays the current active system and allows you to select a new
active system. See Set Active System (on page 269).
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 (on page 268).
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 (on page 122).
Field Descriptions
124
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.
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.
Design Commands
When placing a fitting (such as a vertical tee), if the placepoints and RCPs do not line
up correctly, key in a negative angle, (-90 degrees) to shift the RCPs and placepoints to the
correct location.
Length Displays the length by which to project a straight. If straight is not your active Type,
the Length field does not display on the form. To change the displayed length, select the field,
and key in the new value.
Part Displays the active part. The list contains all available parts for the current
specification. To change the displayed part, select a value from the list.
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.
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.
125
Design Commands
List Indicates whether or not a column value has an associated codelist. If an * displays in
the List column, then the column value has an associated codelist. To display the codelist,
select the *.
Select Retrieves the row(s) from the specification table that meet the select criteria defined
in the form. If only one row matches this criteria, then the Column values fill in with the
matching row's values. If more than one row matches the criteria, then a second form,
containing all matching rows, displays.
126
You can use certain relational operators as search criteria. For a list of valid operators,
see Annotate Element (on page 151).
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.
Design Commands
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.
Automatic Size Automatically selects the correct size fitting. You must specify the manual
fitting type before using the button.
The fitting size is determined by comparing the spec table nominal size of all onelines 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 oneline 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.
127
Design Commands
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.
Field Descriptions
128
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.
Design Commands
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 (on page 97).
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. Specificationdriven fittings rely on the
specification information (width, height, radius, etc.) to construct the threeline 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 specificationdriven and those that are special parts:
SpecificationDriven Fittings
Special Parts
straight
pullbox
elbow
conduit body
wye
light fixture
cross
dropout
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
129
Design Commands
To derive fitting attributes from a special part table in the database, set the toggle to Driven
By Table. Go to step 4.
3. Change fitting descriptions, orientations, and location until the desired fitting is seen in
dynamics (phantom mode) in the design file.
4. Select Accept to accept the fitting with the current settings, orientation, and location.
The system accepts the fitting at the specified location and orientation.
5. Continue placing manual fittings.
OR
Exit the command.
130
Design Commands
Conduit Sizing
This command places cables (wires) in a conduit to determine the correct conduit size based on
the conduit's percent fill calculation.
131
Design Commands
132
Design Commands
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
Description
equal to
numeric
This is the default operator. If you

do not enter another operator, the
system assumes =.
>
greater than
numeric
This operator indicates that the

queried values should be greater
than the given value.
<
less than
numeric

queried values should be less
than the given value.
>=
greater than or
equal to
numeric

queried values should be greater
than or equal to the given value.
<=
less than or equal to numeric

queried values should be less
than or equal to the given value.
!=
not equal to
numeric

queried values should NOT be
equal to the given value.
wild card
CHAR
This operator is a wild card,

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

representing a single character.
The queried values must have
every character aside from the
underline in common with the
given value.
133
Design Commands
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 *.
Initialize Query Clears all entries in the Value fields.

Process Query Queries the database to find cables matching the search criteria defined in
the Value fields. If only one cable is found that matches the criteria, it is added to the conduit.
If more than one cable matches the search criteria, the Pseudo-Cable form displays, from
which you can select a cable or cables to route in the conduit.
Increase Size ONLY / Increase/Decrease size Defines how the conduit should be sized.
There are two methods to choose from:
Increase Size ONLY When a conduit is calculated to be full, the next size larger
conduit in the spec table is used until an adequately sized conduit is found.
Increase/Decrease size The smallest conduit available in the spec that meets the
percent fill criteria is used.
Percent Fill Displays how full the conduit is as a percentage. The field displays in red and
the message Warning: Percent Fill exceeds maximum allowed displays when the conduit has
reached its capacity as defined by the electrical code you are using. The Percent Fill
calculation is based on the conduit's cross-sectional area divided by the summation of all of
that conduit's cables' cross-sectional areas.
Conduit Size Displays the size of the conduit in spec units.
Selected Cables Displays information on all cables that have been selected to go in the
active conduit.
Select Conduit Displays the Conduit Sizing precision input form. Using this form you can
select another conduit in which to route cables without having to exit the command.
Copy Contents Copies cables from a selected conduit into the active conduit. Any cables
in the active conduit before the copy are removed.
134
Design Commands
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.
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).

You must use the Set Conduit Sizing Attributes command to define how the conduit sizes will
be selected. See Set Conduit Sizing Attributes (on page 249) for more information.
Steps
1. Select the Conduit Sizing command.
The Conduit Sizing precision input form displays.

2. Identify CONDUIT
Identify the conduit to size and accept it with <D>
The Conduit Sizing form displays.

3. Define the cables for the conduit. You can query the database and select them from the form
or copy them from a conduit that has "cable" in it.
4. Set the Increase size ONLY / Increase/Decrease size toggle to the sizing method you want.
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.
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 (on page 166) for more information.

135
Design Commands
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.
136
Design Commands
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.
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.
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
137
Design Commands
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.
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.)
Length of Placed Raceway Field Displays the length by which to project the one-line
along the orientation tee from the first point. To change the displayed length, select the field,
and key in a new value.

Steps
1. Select the Place Field Routed Raceway command.

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.
138
Design Commands
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.
139
Design Commands
Field Descriptions
140
Button Matrix Each button represents an area in the duct bank's cross section that
extends the size of the duct bank. By assigning a conduit, cable or gap to a button, you assign
that area in the duct bank. All assigned buttons (areas) are then used to calculate the duct
bank's cross section. Unassigned or unused buttons in the matrix are not used in calculating
the ductbank's cross sectional size unless they are in the middle of assigned buttons.
Copy section layout from Copies an existing duct cross section layout from a specified
duct into the active duct.
Design Commands
Add Assigns a conduit, cable or gap to a matrix button. A form displays all available
conduit/cables in the project database for the defined control number. The conduit/cable
identification will appear on the button after assignment.
Delete Removes a conduit/cable or gap from a matrix button.

Move Moves a conduit/cable or gap from one matrix button to another.
Modify Removes an existing button assignment and replaces it with new assignment.
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 (on page 241) 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.

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
141
Design Commands
matrix and the outside of the ductbank in the EE Raceway Defaults form. See Set Raceway
Defaults (on page 241) for more information.
Steps
1. Select the Define Duct Cross Section command.

2. Identify duct element
Select the duct bank element for which to define the cross section layout and accept it with
<D>.
The Duct Cross Section Layout form displays.

3. Define cross section layout using the various commands.
4. Select Confirm () to exit the form and save your changes.
The duct bank section layout, all conduit/cable information, is assigned to the duct one-line.
The duct bank size is checked and resized as necessary, both width and height. If Automatic
Propagation is on, the duct bank will automatically repropagate.
OR
Select Cancel to exit the form without saving any changes.
If you select Cancel after having modified the ductbank's layout, a warning form
displays confirming that you want to exit without saving changes. If you select Confirm () on
the warning form, any changes you made will be ignored. If you select Cancel on the warning
form, you cancel your "exit without saving" and are returned to the command.
142
Design Commands
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.
You must define conduit as an available one-line type using the Define One-Line Type
command. See Define One-Line Type (on page 244).
You must define conduit as the active one-line type using the Set Active One-Line Type
command. See Set Active One-Line Type (on page 268).
You must define the conduit sizing attributes using the Set Conduit Sizing Attributes
command. See Set Conduit Sizing Attributes (on page 249).
You must define the duct cross section layout using the Define Duct Cross Section command.
See Define Duct Cross Section (on page 139).
You must select the a conduit specification using the Set Active One-Line Type Parameters
command. See Set Active One-Line Type Parameters (on page 264).
The conduit specification and the conduit sizing attributes (for example, vendor, units,
material) are used to determine the conduit stub up sizes available.
143
Design Commands
Field Descriptions
Button Matrix Each button represents an area in the duct bank's cross section that has or
has not been assigned during the Define Duct Cross Section command. This matrix is used
in the Change Association and Place Stub Up options to identify which cross section (that
is, conduit/cable) to manipulate.
Select Duct Segment Selects an existing duct segment in the raceway model as the active
duct segment.
Delete Stub Up Deletes a conduit stub up.
Change Association Changes the association of a conduit stub up from the currently
associated conduit/cable to another conduit/cable in the active duct segment.
Place Stub Up Places a conduit stub up in the raceway model associated with a
conduit/cable in the active duct segment.
Stub Up Size After selecting the Place Stub Up button and selecting a conduit/cable from
the active duct segment, this field displays the associated conduit stub up size. You can
optionly override the displyed value by selecting a conduit stub up size from the available sizes
as determined by matching the conduit sizing attributes to the active conduit specification.
If underground conduit routing is selected for this model, the size of stub up will be retrieved
from the conduit schedule table in project schema based upon conduit number that user
selected from matrix.
If underground cable routing is selected for this model or the conduit size is not defined for the
conduit number, you are required to select the desired size from the available sizes. The
displayed value is simply the value from the previous place stub up selection.
Stub Up Length Displays the conduit stub up length as measured in the model master
units (feet, meters) The user can optionally override the displayed value.
Steps
1. Select the Place Stub Up command.
The Place Stub Up form displays.

2. Select Option
Select the Select Duct Segment option.
OR
Select the Delete Stub Up option. Go to Step 6.
OR
Select the Change Association option. Go to Step 9.
OR
Select the Place Stub Up option. Go to Step 14.
OR
Select Cancel (X) to exit the command.
3. Select the Select Duct Segment option.

4. Identify duct element
Identify a duct one-line in the design file.
The identified element highlights.

OR
Exit the option. Go to Step 2.
144
Design Commands
5. Raceway one line
Accept/reject
Accept the highlighted element. Go to Step 2.
The identified duct one-line's cross section layout displays in the Button Matrix.
OR
Reject the highlighted element. Go to Step 4.
6. Select the Delete Stub Up option.

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

OR
8. Raceway one line
Accept/reject
Accept the highlighted element. It also deletes all cross sections, propagated elements,
annotation, and RCP's that are associated with the selected one-line. Go to Step 7.
OR
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.

OR
11. Raceway one line
Accept/reject
Accept the highlighted element.
12.
13.
14.
15.
OR
Conduit/Cable Number = [conduit/cable number]
Select another cable/conduit to modify existing stub up.
Select a button from the Button Matrix.
Stub up spec. has been changed.
Go to Step 2.
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.
145
Design Commands
16. Select a button from the Button Matrix.

17. Select location to place stub up.
Select location to place stub up. displays in the message field.
Place a data point at the desired location for the top of the conduit stub up. The system places
the stub up and connects it to the duct bank by means of a drop point located on the duct bank
one-line closest to the bottom of the conduit stub up.
The stub up is placed down from the given data point.
Go to Step 14.
OR
Override the stub up size or length. Go to Step 17.
OR
Exit the placement of the selected conduit/cable. Go to Step 2.
146
SECTION 9
Modify Commands
The Modify commands manipulate elements, such as RCPs, one-lines, and three-lines, within
the design file. Available element manipulations include copying, moving, deleting, annotating,
and propagation. You can elect to manipulate either single elements or those elements belonging
to an active group.
Do not use MicroStation commands to manipulate or modify EE Raceway elements
(one-line, three-lines, annotation, and so forth). Doing so will cause serious problems and/or
destroy the EE Raceway model. Use only these EE Raceway modify commands to manipulate EE
Raceway elements.
The Modify palette is activated by selecting Modify from the EERWAY Command Menu Bar, then
selecting Palette.
Commands
The commands on the Modify palette both activate other command palettes. These palettes and
their commands will be described in this chapter.
Using the Modify Commands (on page 147) Outlines the prerequisites, group workflow, and
basic instructions for using the Modify commands.
Modify Element Commands (on page 148) Manipulate single elements within
the design file.
Modify Group Commands (on page 199) Define elements for inclusion in a
group and manipulate elements belonging to the active group.
Using the Modify Commands

design session. For reliable results, you should use these commands, not MicroStation
manipulation commands, any time you are modifying raceway elements.

These commands require that you have existing raceway elements in your design file (see the
Design Commands (on page 107) 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 (on
147
Modify Commands
page 239) and Runtime Setup Commands (on page 263) for instructions about setting up your
systems and one-line types.
You must be familiar with precision input and its functions before using any of the Modify
Group Workflow
There is no required or suggested sequence for the commands in this group.
Modify Element Commands

The Modify Element palette is activated by selecting the Modify Element command from the
Modify palette, or by selecting Modify from the EERWAY Command Menu Bar, then selecting
Modify Element Commands, then selecting Palette.
The Modify Element commands manipulate individual elements, including RCPs, one-lines, and
three-lines, within the design file. You can use individual commands to move, copy, and delete
specified elements, to review or edit element annotation, and to check for duplicate one-lines and
coincident RCPs in the design file. Modify Element commands also allow you to propagate
one-lines in your raceway model.
Raceway elements.
148
Modify Commands
Commands
Using the Modify Element Commands (on page 151) Outlines the prerequisites, group
workflow, and basic instructions for using the Modify Element commands.
Annotate Element (on page 151) Places, reviews, and edits intelligent
annotation for raceway elements.
Copy Element (on page 156) Copies an element as specified within the design
file.
Move Element (on page 158) Moves an element to a specified location in the
design file.
Clone Element (on page 160) Copies an element multiple times in the same
direction.
Move One-Line Segment (on page 163) Moves a one-line segment while
maintaining connectivity to existing elements.
Move One-Line Vertex (on page 166) Moves an internal one-line vertex.
Propagate Element (on page 168) Expands one-line elements into

three-dimensional elements.
Edit/Insert Manual Fitting (on page 173) Modifies fittings that were manually
placed in the model.
Modify One-Line (on page 178) Modifies the route of an existing one-line
element.
149
Modify Commands
Place Fitting by Rule (on page 180) Places a non-standard fitting at an RCP
using a set of rules defined in the reference database.
Check Coincident RCPs (see "Combine Coincident RCPs" on page 182)

Checks for coincident RCPs in the design file.
Check Duplicate One-lines (see "Delete Duplicate One-Lines" on page 183)

Checks for duplicate or overlapping one-lines in the design file.
Delete Element (on page 184) Removes a valid raceway element, and
elements associated with it, from the design file.
Remove RCP (on page 186) Deletes a specified RCP (raceway connect point)
from the design file.
Delete Fitting (on page 188) Removes fittings from the design file.
Remove One-Line Vertex (on page 189) Deletes an internal vertex from an
existing one-line.
Minimize Joints (on page 191) Reduces the number of vertices in an identified
one-line to a minimum.
Change System Parameters (on page 193) Changes the system percentage
and the project rule for a selected element.
Rotate Element (on page 194) Rotates an element to a specified location in the design file.
Rotate Copy Element (on page 196) Copies an element and rotates the copy to a specified
location in the design file.
Mirror Element (on page 197) Flips an element about a specified point in the design file.
150
Modify Commands
Mirror Copy Element (on page 198) Copies an element and flips the copy about a specified
point in the design file.
Using the Modify Element Commands


These commands require that you have existing raceway elements in your design file (see Design
Commands (on page 107) 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 (on
You must be familiar with precision input and its functions before using any of the Modify Element
Group Workflow
Raceway elements.
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.
151
Modify Commands
The following graphic shows the Annotate Element form for an RCP.
The following graphic shows the Annotate Element for for a one-line.
Field Descriptions
152
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.
Modify Commands
Column value Displays the current value for the column whose alias displays in the
Column name field. You can review and modify the values in this field. To change the values
associated with the element, select the field, and key in the new value. You can enter blank
spaces into the design, using your keyboard space bar. Empty <Return>s, however, enter
nothing into the design. Entering a space or a text value for an attribute will override that value
in the reference database. To delete an override on a reference database attribute, select the
Column value field and delete the blank character. Once you have deleted the override, a
value will display in the field only if the value can be retrieved from the reference database.
Otherwise, the field remains null.
If blanks exist for a field, the cursor will jump to the end of the blanks when the field is
tagged beyond value.
Source Displays the source of the corresponding column value. If Ref displays in the
column, then the value derives from the reference database. If Dgn displays in the column,
then the value derives from the design file. If you change a column value, the column displays
New until you select Confirm to save your changes. The next time you enter the annotation
form, the Source column will display either Ref or Dgn, where New had displayed. Where UD
displays in the column, the corresponding column value comes from user data. When
modified, the value is saved back to user data.
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.
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.
153
Modify Commands
in the form. The select criteria are those values that display in the Column value column on
the lower portion of the annotation form. You can use relational operators when keying in your
own select criteria. Available operators are described later in this section.
If only one row matches the select criteria you provide, then the Column values fill in with the
matching row's values. If more than one row matches the criteria, then a second form
containing all matching rows displays.
From this form you can select the row(s) containing the desired values. To add values from
the displayed specification table rows, select the row you want, and then select Confirm (). If
you select Cancel (X), the system cancels the form and retrieves the values from the EE spec
key field on the original form.
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.
This command accepts certain relational operators as search criteria. You should be familiar
with the following operators:
This command accepts certain relational operators as search criteria. You should be familiar with
the following operators:
154
Symbol
Name
Data Type
Description
equal to
numeric
This is the default operator. If you do not enter another

operator, the system assumes =.
>
greater than
numeric
This operator indicates that the queried values should

be greater than the given value.
<
less than
numeric

be less than the given value.
>=
greater than or numeric

equal to

be greater than or equal to the given value.
!=
not equal to

NOT be equal to the given value.
numeric
Modify Commands
Symbol
Name
Data Type
Description
wild chard
CHAR
This operator is a wild card, representing zero or more

characters. The queried values must have every
character aside from the % in common wit the given
value.
underline
CHAR
This operator is a wild card, representing a single

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

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
valid element.
OR
Exit the command.
3. Accept/Reject
Press <D> to accept the highlighted element.
The annotation form displays when you accept the element. The form displays all the current
values associated with the element. It also identifies all the possible values (column values)
associated with this element.
OR
Press <R> to reject the highlighted element. Return to step 2.
4. Set up the form parameters to meet your specifications.
5. Select Confirm () to save your changes and exit the annotation form.
OR
Select Cancel (X) to exit the annotation form without saving your changes. Return to Step 2.
6. Placing [column alias]
Data point <D> to place, reset <R> to skip.
The prompt indicates the column alias being placed. The column value displays in drag mode
attached to the cursor.
Position the column value, and place a data point.
155
Modify Commands
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.
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.
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.
156
Modify Commands
Equipment pointers and drop points cannot be copied using this command.
157
Modify Commands
Steps
1. Select the Copy Element command.
The Copy Element precision input form displays.

Identify the one-line or RCP element you intend to copy and accept it with <D>.
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.
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.
158
Modify Commands
If a one-line is moved, all attached RCPs will be moved and all attached one-lines will be re-routed
to the new one-line position. All associated annotation, three-line fittings, and equipment pointers
will also be moved.
159
Modify Commands
Steps
1. Select the Move Element command.
The Move Element precision input form displays.

Identify the element you intend to move and accept it with <D>.
valid element.
OR
Specify the new location for the element.
The system moves the element to the specified location.

Repeat this step.
OR
Press <R> to select another element to move. Return to Step 2.
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.
160
Modify Commands
Equipment pointers and drop points cannot be copied using this command.
161
Modify Commands
Steps
1. Select the Clone Element command.
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
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.
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.
162
Modify Commands
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.
163
Modify Commands

Steps
1. Select the Move One-Line Segment command.
2. Identify Raceway One-Line Segment
Select the one-line segment you want to move and accept it with <D>.
The point that identifies the one-line segment in this step will be reference point used
when placing the one-line segment at the new location.
The selected one-line segment highlights.

OR
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.
164
Modify Commands
If you have the Automatic Propagation toggle set to on, the one-line will automatically
repropagate after the move. See Propagation Setup (on page 271) for more information on
this toggle.
165
Modify Commands
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.
166
Modify Commands

Steps
1. Select the Move One-Line Vertex command.
2. Identify Raceway One-Line Vertex
Select the vertex of the one-line you want to move and accept it with <D>.
The one-line vertex closest to the point where you identify the one-line is automatically
selected.
The selected vertex highlights.

OR
Identify the new location of the vertex. Repeat this step.
OR
Press <R> to select another one-line vertex.
167
Modify Commands
If you have the Automatic Propagation toggle set to on, the one-line will automatically
repropagate after the move. See Propagation Setup (on page 271) for more information on
this toggle.
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.
168
Modify Commands
To view errors that occur during propagation, select the Highlight Propagation Errors
command, see Highlight Propagation Errors (on page 282). This command displays to the screen
the pro.err file, which resides in the <current_project>/rway/tmp directory.
169
Modify Commands
To view errors that occur during propagation, select the Highlight Propagation Errors (on page
282) command. 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.

You can set active parameters for propagation through the Propagation Setup form. For
information about the form, see Propagation Setup (on page 271).
Steps
1. Select the Propagate Element command.
The Project Run precision input form displays.

Identify a raceway one-line or RCP.
The system highlights the specified element. If you do not locate an acceptable one-line or
RCP, the system displays the message Element not found. The message disappears when you
identify a valid element.
170
Modify Commands
OR
Exit the command. Go to step 1.
3. Accept/reject
The system propagates the identified one-line and returns you to step 2 to continue identifying
elements for propagation.
OR
Reject the highlighted element. Go to step 2.
Fittings
This section describes some of the fittings available with the delivered raceway one-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 (on page 423).
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.
The following illustrations detail some of the fittings available for each raceway one-line type:
Tray Fittings
171
Modify Commands
Wireway Fittings
Conduit Fittings
172
Modify Commands
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 (on page
186).
Type Displays the active threeline type for the current specification. The list contains all
available threeline types (elbow, straight, wye, etc.) for that specification. To change the
displayed threeline 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.
173
Modify Commands
When placing a fitting (such as a vertical tee), if the placepoints and RCPs do not line
up correctly, key in a negative angle, (90 degrees) to shift the RCPs and placepoints to the
correct location.
Length Displays the length by which to project a straight. If straight is not your active Type,
the Length field does not display on the form. To change the displayed length, select the field,
and key in the new value.
Part Displays the active part. The list contains all available parts for the current
specification. To change the displayed part, select a value from the list. You can also change
any of the values for Type, Subtype, Qualifier, Spec1, and (if applicable) Spec2.
Spec1 Displays the active specification for the displayed Type, Subtype, and Qualifier.
The list contains all available specifications.
To change the displayed specification, select a value from the list.
To display the specification itself, select the corresponding Display button.
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.
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 *.
174
Modify Commands
Select Retrieves the row(s) from the specification table that meet the select criteria
defined in the form. If only one row matches this criteria, then the Column values fill in
with the matching row's values. If more than one row matches the criteria, then a second
form containing all matching rows displays.
You can use certain relational operators as search criteria. For a list of valid operators,
see Annotate Element (on page 151).
Clear Clears the Column values from the lower portion of the form, and then
automatically depresses the Override button so that you can select a different row(s)
from the specification.
Override Allows you to override those columns whose access is Read Only (R). You
can activate the Override button by selecting it directly or by selecting the Clear button,
which automatically activates it.
Spec2 Displays the active secondary specification, if any, for the given Spec1, Type,
Subtype, and Qualifier. The list contains all available secondary specifications for the current
settings. Secondary specifications are generally used with reducers.
You can display the current specification itself by selecting the Display button. Doing so
displays a specification form. See Spec1 for a description of the form.
Overrides from the secondary specification are not passed to the Eden symbol.
Placepoint Defines the point of attachment for the fitting you are currently placing. To
change the active placepoint, select the slide bar, and drag it along the scale until it reaches
the appropriate value.
Automatic Size Automatically selects the appropriate size fitting base on the one-lines
connected to the fitting.
The fitting size is determined by comparing the spec table nominal size of all one-lines at the
RCP and selecting the largest nominal size among them. That nominal size is then compared
to the fitting table nominal sizes. If in the fitting table there is a nominal size the same as the
largest one-line nominal size, then that fitting is used. If there is no fitting of that nominal size,
then the first fitting that is of greater nominal size than the one-line nominal size is used. If
there is no nominal size fitting larger than the one-line nominal size, then the largest fitting
available is used.
Automatic Fit Correctly orients the fitting to the one-lines.
Rotate Orientation These fields define the orientation matrix:
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.)
175
Modify Commands
If you set the Driven By Spec/Table toggle to Table, the form changes.
Field Descriptions
176
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, then 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. 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.
Modify Commands
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.

You should be familiar with precision input and its functions. For more information, see Precision
Input Form (on page 97).
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. Specificationdriven fittings rely on the
specification information (width, height, radius, etc.) to construct the threeline 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 specificationdriven and those that are special parts.
SpecificationDriven Fittings
Special Parts
straight
pullbox
elbow
conduit body
wye
light fixture
cross
dropout
Steps
1. Select the Edit/Insert Manual Fitting command.
2. Identify Raceway Fitting or RCP
Select the fitting or RCP you want to edit and accept it with <D>.
The Edit/Insert Manual Fitting form displays.

OR
177
Modify Commands
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.
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>.

Steps
1. Select the Modify One-Line command.
The Modify One-Line precision input form displays.

Identify a one-line in the design.
178
Modify Commands
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 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.
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.
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.
179
Modify Commands
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.
180
Modify Commands
The spec table and the fitting table are defined in the rule.

181
Modify Commands
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 (on page 359) for a list of the
delivered default rules.
Steps
1. Select the Place Fitting by Rule command.
Select the RCP on which you want to place the fitting.
If no rule is defined for the selected RCP's situation, then the message Unable to find a rule
that applies. displays. Otherwise the correct fitting as defined by the rule is placed on the
RCP.
OR
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
182
Modify Commands
If coincident RCPs are found, the Combine Coincident RCPs form displays listing the
coincident RCP information.
Each set of coincident RCPs is listed in the form separated by the horizontal dotted line.
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.
2. For each set of coincident RCPs, select the RCP information on the form to highlight the
associated elements in the model.
3. Choose which RCP in the set of RCPs you want to keep and leave that line highlighted.
4. Select the Combine button to merge that set of coincident RCPs.
The RCPs are combined, and the Status of the remaining RCP, the one you selected, changes
to Kept. The status of the removed RCP changes to Combined.
You cannot combine RCPs that have an Invalid status.
Delete Duplicate One-Lines

This command is used to check for and correct duplicate one-lines (having only two vertices) that
occupy the same geographical space and terminate on the same RCPs.
Steps
1. Select the Delete Duplicate One-Lines command.
If no duplicate one-lines are found, then the message No duplicate one-lines found displays
and the command exits.
OR
183
Modify Commands
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.
3. Choose which one-line out of each set you want to keep. The Status of the one-line you chose
changes to Save.
4. Select the Delete button to delete the other one-line(s).
The one-line is deleted and its Status changes to Deleted. The Status of the one-line you
wanted to keep changes to Kept.
5. Continue to select the one-line to keep and deleting the other. Select Cancel when finished.
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.
184
Modify Commands

185
Modify Commands
Steps
1. Select the Delete Element command from the menu.
The Delete Element precision input form displays.

Identify an element for deletion.
valid element.
OR
3. Raceway [element]
Accept/reject
Press <D> to accept the element for deletion.
If you accept the highlighted element, the system deletes it. It also deletes all 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.
Remove RCP
This command removes a raceway connect point (RCP) from the design file. You cannot use the
Delete Element commands to remove an RCP, unless the RCP has no one-lines attached.
The command will remove an identified RCP only if all of the following conditions are true:
Two one-lines are attached to the RCP.
The two attached one-lines are of the same one-line type.
The two attached one-lines belong to identical systems.
Once such an RCP is removed, the two one-lines form a single one-line element. If both one-lines
are annotated, the annotation for the second one-line is deleted.
186
Modify Commands

187
Modify Commands
Steps
1. Select the Remove RCP command.
The Remove RCP precision input form displays.

Identify an RCP to remove.
The system highlights the specified element. If you do not locate an acceptable RCP, the
valid RCP.
OR
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.
Delete Fitting
This command deletes the raceway fitting from a selected RCP, useful for removing manually
placed special fittings (like pullboxes and conduit bodies) and replacing them with bends. This
command does not remove the RCP.
Steps
1. Select the Delete Fitting command.
Select the fitting, or the fitting's RCP, to delete.
OR
3. Accept/Reject
Press <D> to accept the highlighted fitting and delete it. Return to step 2.
OR
Press <R> to reject the highlighted fitting and return to step 2.
188
Modify Commands
Remove One-Line Vertex

This command deletes an internal one-line vertex.
You cannot delete the end points of the one-line using this command.
189
Modify Commands

190
Modify Commands
Steps
1. Select the Remove One-Line Vertex command.
2. Identify Raceway One-Line Vertex
Select the vertex of the one-line you want to remove.
The one-line vertex closest to the point where you identify the one-line is automatically
selected.
The selected vertex highlights.

OR
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.
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 (on page 271) for information
about the Automatic Propagation toggle.)
191
Modify Commands
The following example demonstrates the effect of the Minimize oints command on a one-line.
(Automatic propagation is on to show the resulting seamless representation.)
Automatic propagation must be toggled on in order for the results of this command to be
visible.

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.
192
Modify Commands
Change System Parameters

This command changes the system parameters, the system Percent and the Project Rule, for
the systems associated with a single raceway element.
Field Descriptions
Primary System Displays the primary system. The primary system determines the
symbology of the elements.
Project Rule Set Displays the Project Electrical Code from the project schema's project
table. This is defined in EEmgr with the EE CMS Project Definition process. The Project Rule
Set determines which rules can be assigned to the active systems. If the Project Rule Set is
not defined, Project Rules cannot be assigned. This option is no longer used.
Systems Displays all the systems associated with the selected element.
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 Percent is displayed in the field at the bottom of the Percent column. All the selected
systems percentages are summed to calculate the total percentage. The Percent represents
the portion of the raceway's width assigned to that system. This Percent is used when
calculating the cable fill of the raceway section in the EECMS product.
Project Rule Displays the Project Rule assigned to each of the selected systems for
calculating raceway fill. When a row is selected, a list of available rules for the Project Rule
Set defined with the EE CMS Project Definition process is displayed for review and selection.
To clear the Project Rule, select the row and select the Cancel (X) on the list of Rules. This
option is no longer used.
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 *. This
193
Modify Commands
Steps
1. Select the Change System Parameters command.

Identify an element in the design file.

OR
Exit the command.
Accept/reject
5. Select
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.
Rotate Element
This command rotates individual raceway elements as specified within the design file. You can
an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All
194
Modify Commands
If a one-line is rotated, all attached RCPs will be moved and all attached one-lines will be rerouted
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 updown 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 eastwest 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 northsouth 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.

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>.
valid element.
3. Specify the point around which to rotate the element.
195
Modify Commands
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.
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
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.
Steps
1. Select the Rotate Copy Element command.
196
Modify Commands
The Rotate Copy Element precision input form displays.
2. Identify the element you intend to rotate and copy and accept it with <D>.
valid element.
3. Specify the point around which to rotate the element.

4. Specify the planes and angles at which to rotate the element.
5. Click Accept.
The element copy displays at the specified position.
Mirror Element
This command flips individual raceway elements about a point as specified within the design file.
You can use this command to mirror one-lines, RCPs, drop points, equipment pointers, and
annotation. If an RCP is rotated, all attached one-lines will be rerouted to the new position of the
RCP. All associated annotation, three-line fittings, and equipment pointers will also be moved.
If a one-line is mirrored, all attached RCPs will be moved and all attached one-lines will be
rerouted to the new one-line position. All associated annotation, three-line fittings, and equipment
pointers will also be moved.
Field Descriptions
Mirror Point Displays the location of the specified mirror point. The primary vector of the
orientation tee denotes the mirror plane's normal vector. The elements are rotated about the
plane formed by the secondary and the normal.
Angle Specifies the angle by which to rotate the orientation tee. To change the displayed
angle, select the field and type a new angle.
About Specifies the axis about which to rotate the orientation tee. To change the displayed
axis, toggle among the three axes (Primary, Secondary, Normal) until the appropriate axis
displays.
197
Modify Commands
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>.
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 plane's normal vector.
5. Click Accept.
The element rotates to the specified position.
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
198
Modify Commands
displays.

Steps
1. Select the Mirror Copy Element command.
The Mirror Copy Element precision input form displays.

2. Identify the element you intend to mirror and copy and accept it with <D>.
valid element.
3. Specify the point around which to mirror the element.

4. Specify the plane on which to mirror the element. The primary vector of the orientation tee
denotes the mirror plane's normal vector.
5. Click Accept.
The element copy displays at the specified position.
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.
199
Modify Commands
The Modify Group palette is activated by selecting the Modify Group command from the Modify
palette, or by selecting Modify from the EERWAY Command Menu Bar, then selecting Modify
Group Commands, then selecting Palette.
You can use individual Modify Group commands to move, copy, and delete elements of specified
groups, and to review or edit element annotation. You can also propagate one-lines in a particular
group using these commands.
Raceway elements.
Topics
Using the Modify Group Commands (on page 202) Outlines the prerequisites, group workflow,
and basic instructions for using the Modify Group commands.
Define Group (on page 202) Identifies raceway elements for inclusion in a
particular group.
Copy Element by Group (on page 206) Copies within the design file some or all
elements of a specified group.
Annotate Element by Group (on page 208) Places, reviews, and edits
intelligent annotation for raceway elements within a specified group.
Clone Group (see "Clone Element by Group" on page 212) Copies a group
multiple times in the same direction.
200
Modify Commands
Propagate Element by Group (see "Propagate by Group" on page 214)

Expands some or all one-line elements of a specified group into three-dimensional elements.
Place Fitting by Rule Group (see "Place Fitting by Rule by Group" on page 215)
Places non-standard fittings using a set of rules defined in the reference database.
Add Systems Group (on page 216) Defines multiple systems for a single
one-line.
Replace Systems Group (see "Replace Systems by Group" on page 217)

Changes the defined active system type of a one-line.
Minimize Joints by Group (on page 219) Reduces to a minimum the number of
vertices of some or all one-lines in a specified group.
Delete Element by Group (on page 221) Removes from the design file some or
all elements of a specified group.
Rotate Group (on page 222) Rotates some or all elements of a specified group to a new
Rotate Copy Group (on page 224) Copies and rotates some or all elements from a specified
group to a new location in the design file.
Mirror Group (on page 225) Mirrors some or all elements from a specified group to a new
Mirror Copy Group (see "Mirror Group" on page 225) Copies and mirrors some or all elements
from a specified group to a new location in the design file.
Move Group (on page 228) Moves some or all elements from a specified group to a new
201
Modify Commands
Using the Modify Group Commands


These commands require that you have existing raceway elements in your design file (see Design
Commands (on page 107) 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 (on
You must be familiar with precision input and its functions before using any of the Modify Group
Group Workflow
You must use the Define Group command to create and activate an element group before using
other Modify Group commands.
Raceway elements.
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.
202
Modify Commands
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.
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).
203
Modify Commands
To initiate the Drop operation, select a group from the Available Groups list, select Drop,
and then select Accept.
Copy Copies the specified contents of one group to a new group.
To initiate the Copy action, select an existing group from the Available Groups list, select
Copy, and key in a new group name.
Add to Adds elements you specify from the EE Element Types list to an existing group.
The system compiles the elements using the selection method you specified in the Graphic
Method list.
To initiate the Add to operation, select an existing group from the Available Groups list,
select Add to, and then select Accept. The system compiles the elements using the selection
method you specified in the Graphic Method list. When processing is complete, review the
form Message Area for information about the number of elements added to the group.
Drop from Removes elements you specify in the EE Element Types list from an existing
group. If you remove all elements from a group, the system automatically drops the entire
group.
To initiate the Drop from action, select an existing group from the Available Groups list,
select Drop from, and then select Accept. The system drops the elements using 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.
Select All Selects every element type from the EE Element Types list.
Clear All Clears all selected element types from the EE Element Types list.
EE Method This list displays optional restrictions for the items selected in the EE Element
Types list. You can use the three options in this list to restrict the elements in your group to
those belonging to particular one-line types or systems.
One-Line Type Displays a list of available one-line types.
When you select a one-line type from this list, only those element types (RCPs, one-lines,
three-lines, and so forth) belonging to that one-line type will be included in your group.
You can select individual one-line types from this list, or you can select all displayed one-line
types (using Select All). Clear All cancels the selections you have made from the list.
204
Modify Commands
Once you have displayed the One-Line Type list, you must Cancel (X) or
selections before selecting the Accept button on the main form.
System Displays a list of available systems.
your
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.
When you select an element type from this list, an attribute list form displays for that element
type in which you can specify the attributes to include in the group identification.
Once you have defined the attributes, select the Accept button on the main form. To reset out
of the attribute list form and disregard the attributes, select the Cancel (X) button on the
attribute form.
Graphic Method Displays the available methods for selecting group elements. You will use
these methods to identify elements for group creation, insertion into groups, or deletion from
groups. These methods can serve to further restrict the element types you are including in
your group.
For example, if you identified one-line trays for insertion into a group, and select Fence Block
from this list, the system inserts into the group only those one-line trays contained within the
fence you place.
Selection Prompts you to identify specified element types in the design file to drop
from or include in a group.
Fence Block Drops from or includes in a group those specified element types
contained within a fence block you place in the design.
Fence Shape Drops from or includes in a group those specified element types
contained within a fence shape you place in the design.
205
Modify Commands
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.
Steps
1. Select the Define Group command.
The Groups form displays.

2. Create a group of elements:
Key in a name for the group in the field provided.
Select the Create button under Group Operations.
Use the EE Element Types, EE Method, and Graphic Method lists to define which
elements to place in the group and how you want to select them in the design file.
Select the Process button at the top of the form.
Using the Graphic Method you defined, select your elements for the group.
The group is created. The number of elements added to the group displays at the bottom of the
form.
OR
Select one of the available group from the list
3. Set the Entire Group/Single Element and Hilite On/Hilite Off toggles the way you want.
4. Select one of the group modification commands.
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.

You must define a temporary group of elements, using the Define Group (on page 202) command.
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.
206
Modify Commands
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.
Accept/reject
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.

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.
207
Modify Commands
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.
Field Descriptions
208
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 name field. You can review and modify the values in this field.
Modify Commands
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.
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
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.
cannot delete it.
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.
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
. If the toggle is set to Single for the
same RCP annotation, the system will modify annotation only for that RCP when you select
.
209
Modify Commands
own select criteria. Available operators are described later in this section.
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
. If
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.
This command accepts certain relational operators as search criteria. You should be familiar
with the following operators:
210
Symbol
Name
Data Type
Description
equal to
numeric

>
greater than
numeric

<
less than
numeric

>=

equal to

Modify Commands
Symbol
Name
Data Type
Description
!=
not equal to
numeric

wild chard
CHAR

value.
underline
CHAR

the given value.

You must define a temporary group of elements, using the Define Group command. (For
information about the command, see Define Group (on page 202).) 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 Annotate Element by Group command from the menu.
The Annotate by Group precision input form displays.

If there is not a fence in the design, go to step 3.
The system highlights the group contents.

OR
Reject the contents of the fence.
The command exits automatically. Go to step 1.

Accept/reject
Accept the highlighted group element.
The system displays the Annotate Element form for the identified element.
OR
Reject the highlighted group element.
The system highlights another group element. Repeat this step. If no group elements remain,
the command exits.
211
Modify Commands
5. Select
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.
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.
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.

Steps
1. Select the Clone Group command.
The Clone Group precision input form displays. If you have not defined a group, the message
212
Modify Commands
No active group defined displays.
Accept/reject
Accept the highlighted element. Go to step 6.
OR
OR

5. Define origin
Identify a point in the group to use as the origin for the copies.
6. Key in number of clones
Key in the number of times to clone the identified group.
A warning box displays verifying the number of times you want to clone the identified group.
7.
the number of time to clone the group.
OR
Cancel the form and reenter the number of clones.
Identify the location of the first copy. If you are placing more than one clone, 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.
213
Modify Commands
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 (on page 168).
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 (on page 282).

You can set active parameters for propagation through the Propagation Setup form. For
information about the form, see Propagation Setup (on page 271).
Steps
1. Select the Propagate by Group command from the menu.
The Project by Group precision input form displays.

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.
OR
214
Modify Commands
Accept/reject
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
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.
The system propagates every element belonging to the group.

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

215
Modify Commands
overrides the active group. You must define the rules in the reference database. See EE
Databases (on page 359) for a list of the delivered default rules.
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.
Accept/reject
OR
If no rule is defined for the selected RCP's situation, then the message Unable to find a rule
that applies. displays. Otherwise the correct fitting as defined by the rule is placed on the
RCP.
OR
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.
216
Modify Commands
If you try to add a system that already exists on the element, it will not be duplicated.
Before Using this Command

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
The system(s) is added.

OR
Select Cancel to exit the form and command.
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.
217
Modify Commands
Changing the active system will cause the graphic symbology to change to the symbology
define for the new system.
Field Descriptions
218
Systems This button allows the selection of 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 This button allows the selection of subsystems. While this button is depressed,
the Percent and Project Rule can be defined for each subsystem.
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. This option is no longer used.
Systems Displays all the available systems. Selecting a row in this field defines the Active
System or Subsystem.
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 Percent is displayed in the field at the bottom of the Percent column. All of the
selected systems percentages are summed to calculate the total percentage. The Percent
represents the portion of the raceway's width assigned to that system. This Percent is used
when calculating the cable fill of the raceway section in the EECMS product.
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 *. This
Modify Commands
Before Using this Command
When defining the group for this command, you must define a group that contains all
elements that have connectivity. You cannot 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.

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
The active group is changed to the new system type.

OR
Select Cancel to exit the form and the command.
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 (on page 271)
for information about the Automatic Propagation toggle.)
219
Modify Commands
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.

Steps
1. Select the Minimize Joints by Group command from the menu.
The Minimize Joints Group precision input form displays.

If Entire Group is the active toggle on the Define Group form, the vertices of 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.
220
Modify Commands
OR

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])
The system minimizes the number of vertices for all valid one-line elements within the group.
OR
Delete Element by Group

This command deletes all or selected valid elements in an active group from the design file.

Steps
1. Select the Delete Element by Group command from the menu.
The Delete by Group precision input form displays. If you have not defined a group, the
message No active group defined displays.
221
Modify Commands
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
Accept/reject
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
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.
The system deletes all valid elements within the group. The command exits automatically.
OR
Rotate Group
This command rotates a group of raceway elements as specified within the design file. You can
an RCP is rotated, all attached one-lines will be rerouted to the new position of the RCP. All
222
Modify Commands
If a one-line is rotated, all attached RCPs will be moved and all attached one-lines will be rerouted
will also be moved.
Field Descriptions

Plan View Specifies the angle at which to rotate the group on the plan view plane. The
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
rotation point.

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.

223
Modify Commands
4. Specify the planes and angles at which to rotate the group.
5. Click Accept.
The group rotates to the specified position.

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.
Rotate Copy Group

This command creates a rotated copy of a group of raceway elements as specified within the
design file.
Field Descriptions
Plan View Specifies the angle at which to rotate the group on the plan view plane. The
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
rotation point.
Steps
1. Select the Rotate Copy Group command.
224
Modify Commands
The Rotate Copy Group precision input form displays.
2. Identify the group you intend to rotate and copy and accept it with <D>.
valid group.
3. Specify the point around which to rotate the group.

4. Specify the planes and angles at which to rotate the group.
5. Click Accept.
The group copy displays at the specified position.

Element mode, you can accept or reject constituent elements and set the rotation point and
planes for each accepted element.
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
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
displays.
225
Modify Commands

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>.
valid group.
3. Specify the point about which to mirror the group.

4. Specify the mirror plane on which to mirror the group.
5. Click Accept.
The group moves to the specified position.

Element mode, you can accept or reject constituent elements and set the mirror point and
mirror plane for each accepted element.
Mirror Copy Group

This command creates a mirrored copy of a group of raceway elements as specified within the
design file.
226
Modify Commands
Field Descriptions
displays.
with the positive X axis, the Secondary axis with the positive Y
axis, and the Normal axis with the positive Z axis.

Steps
1. Select the Mirror Copy Group command.
The Mirror Copy Group precision input form displays.

2. Identify the group you intend to mirror and copy and accept it with <D>.
valid group.
3. Specify the point around which to mirror the group.

4. Specify the plane on which to mirror the group.
5. Click Accept.
The group copy displays at the specified position.

Element mode, you can accept or reject constituent elements and set the mirror point and
mirror plane for each accepted element.
227
Modify Commands
Move Group
This command moves a group of raceway elements to a new location in the design file.

Steps
1. Select the Move Group command.
The Move Group precision input form displays.

2. Identify the group you intend to move and accept it with <D>.
valid group.
3. Specify an origin point from which to move the group.
Specify a placement point to which to move the group.
The group moves to the specified position.
228
SECTION 10
Database Commands
The Database commands are used to load and run reports from the database. The Database
palette is activated by selecting Database from the EERWAY Command Menu Bar, then selecting
Palette from the resulting pull-down menu.
Topics
Using the Database Commands (on page 229) Outlines the prerequisites, group workflow, and
basic instructions for using the Database commands.
Load Database (on page 230) Loads the project database with information
generated from the EE Raceway drawing.
Reports (see "Report" on page 233) Displays the information in an EE Raceway

database.
Rulecheck (see "Rule Checks" on page 236) Displays the design rule errors
occurring in the design process.
Using the Database Commands

Use these command to run limited database commands while still in the graphic design session.

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 rule check.
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.
229
Modify Commands
Load Database
This command loads a relational database with information generated by the EE Raceway design
file. Information in the design file is merged with information from the reference schema and
loaded into the project schema.
All RCP's and segments must have a tag number before using this command.
When you run the Load Database command on a design file that has been loaded previously into
the database, the command removes the occurrences of the previous load and completely
reloads the design file.
You must create a RIS schema on an existing relational database before loading, using the
Database Utilities option from the EE Project Menu Both a project and a reference schema must
exist before running the Load Database process.
This process calculates the following values:
230
Table Name
Column Name
Comments
rcp_to_drw
pds_east*
The PDS east coordinate of the corresponding

RCP's origin.
rcp_to_drw
pds_north*
The PDS north coordinate of the corresponding

RCP's origin.
rcp_to_drw
pds_elev*
The PDS elevation coordinate of the corresponding

RCP's origin.
rcp_to_sys
ee_percent***
Indicates what portion of the corresponding RCP is

set aside for the corresponding system.
drop_point
ee_dist_down_ol**
The distance down the one-line to the point on the

one-line closest to the drop point origin.
drop_point
ee_dist_to_rcp**
The orthogonal distance from the drop point origin to

the RCP's origin, and the orthogonal distance from
the drop point origin to the closest point on the
one-line.
one_line
ee_ol_length**
The total graphical length of the one-line in master

units.
ol_to_sys
ee_percent***
Indicates what portion of the corresponding one-line

is set aside for the corresponding system.
straight
ee_tl_length
The graphical length of the straight in master units.
straight
pds_east*
The PDS east coordinate of the center point of the

straight's range.
straight
pds_north*
The PDS north coordinate of the center point of the

straight's range.
straight
pds_elev*
The PDS elevation coordinate of the center point of

the straight's range.
Modify Commands
Table Name
Column Name
Comments
str_to_sys
ee_percent***
Indicates what portion of the corresponding straight

fitting
pds_east*

fitting's ange.
fitting
pds_north*

fitting's range.
fitting
pds_elev*

the fitting's range.
fit_to_sys
ee_percent***
Indicates what portion of the corresponding fitting is

* 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 command.
The Load database screen displays.
2. Enter error and output filenames.

Key in unique filenames in the Error file and Output file fields, or accept the displayed
defaults.
The default error and message files will be overwritten every time the process runs.
You must specify unique filenames to save the default files.
3. Accept will load database.
231
Modify Commands
When you are finished completing the input information, select
begins.
, and the process
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.
232
Modify Commands
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 (see "Create" on page 50)
for the directory structure.
Overview
This section contains general information about running all EE Raceway reports. See Reports (on
page 457) 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).
233
Modify Commands
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.)
yourself. If a new output file has the same name as an existing file, the new file will overwrite that
file. You should give each report you want to save a unique name.
Steps
1. Select the Report command.
2. Select the report you want to run from the list.
3. Select
to invoke the input form for the specified process.
4. Define the report input form as needed and select Confirm () to process the report.

pulled.
234
Modify Commands
with a space between the coordinates: easting northing elevation. For example, 234 532 34.
235
Modify Commands
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
This section contains general information about running all EE Raceway rule checks. For more
detailed information about each rule check, see Reports (on page 457).
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.
236
Modify Commands
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.
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
to invoke the input form for the specified process.
Define the input form as needed and select
to process the rule check report.
237
SECTION 11
Setup Commands
The Setup commands allow you to define, review, and modify the default parameters, systems,
one-line types, and symbology settings for your design file. The Setup palette is activated by
selecting Setup from the EERWAY Command Menu Bar, then selecting Palette from the resulting
pulldown menu.
In a new design file, you must use the Setup commands before using any other command group.
Your system/application manager should ensure that the reference database contains the
necessary systems and one-line types before you use these commands.
Commands
Using the Setup Commands (on page 240) Outlines the prerequisites, group workflow, and
basic instructions for using the Setup commands.
Set Raceway Defaults (on page 241) Defines, reviews, and modifies the raceway
default parameters for symbols, working view, model annotation, RCPs, report IDs, and cross
sections.
Define System (on page 242) Selects any or all systems from those available in the
reference database for use in the design file.
Define One-Line Type (on page 244) Selects any or all available one-line types from
those available in the reference database for use in the design file.
Set Symbology Control (on page 245) Selects the standard graphic symbology
control for all systems and one-line types in a design file.
Symbology Control (on page 246) Defines, reviews, and modifies the graphic
symbology control for those one-line types you specified using the Set Symbology Control
command.
239
Setup Commands
Set Text Defaults (on page 248) Defines, reviews, and modifies the default
parameters for text, text nodes, and engineering units.
Set Conduit Sizing Attributes (on page 249) Defines which conduit attributes will be
used selecting the correct size conduit in the Conduit Sizing command.
Cell Creation Commands (see "Create Cell Commands" on page 250) Create
various types of raceway cells necessary for creating EE Raceway models.
Model Commands (on page 257) Place and manipulate a model information in the
design file.
Using the Setup 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.

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.
See individual command descriptions for specific operating information.
240
Setup Commands
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 (on page 139) 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 (on page 139) 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.
241
Setup Commands
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.
Default Key Displays the current default keys for RCP (raceway connect point), equipment
pointer, and drop point annotation. You can review, define, and/or modify this key. To display the
current default data from the database for a particular element (RCP, equipment pointer, or drop
point), select first the key field and then the Display button. The information will display in the
scrollable list in the lower right corner of the form. You can only view this data.
Steps
1. Select the Set Raceway Defaults command.
The EE Raceway Defaults form displays.

2. Set up the form parameters to meet your requirements.
3. Select
OR
Select Cancel (X) to exit without saving your changes.
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.
242
Setup Commands
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.
The systems you select are deleted from the To Design column and will no longer be defined
in the design file.
3. Select
OR
Select Cancel (X) to exit the command without saving your changes.
243
Setup Commands
Define One-Line Type

This command allows you to select any or all available one-line types from the reference database
for use in the design file. The One Line Type Definition form displays those one-line types
available in the database, as well as those already selected for the current design file.
If you need one-line types not available to you, you should ask the system/application manager to
add them to the reference database. Caution should be used when adding these to the database,
so as to avoid duplication of elements.
You must define one-line types for the design file before you can use related commands,
such as Set Active One-Line Type and Place One-Line Type.
Steps
1. Select the Define One-Line Type command.
The One Line Type Definition form displays.

2. Select the one-line types in the From Database column that you want to define in the present
design file. To define ALL one-line types from the reference database in the design file, select
the Select All button.
The one-line types you select display in the To Design column and will be defined in the
design file once you select the Confirm button ().
OR
Select those one-line types listed in the To Design column that you no longer want defined for
the design file. To remove ALL one-line types from definition in the design file, select the Clear
All button.
The one-line types you select are deleted from the To Design column and will no longer be
244
Setup Commands
defined in the design file.
3. Select
OR
Set Symbology Control

This command defines the standard graphic symbology for all systems and one-line types in a
design file. The Set Graphic Symbology Control form displays a matrix of systems and one-line
types and the standard graphic symbology assigned to each system (all one-line types within a
system are originally assigned the same symbology).
When you enter a new design file, all symbology is taken from the system defaults. Therefore, to
make any changes in symbology, you must first use the Set Symbology Control command to
specify the systems and one-line types that can be changed. You can specify the one-line types
for which to change the standard symbology by setting them to override mode.
In cases where you do not specify overrides for the one-line types within a system, those one-line
types will use a system default. The Symbology Control command allows you to set up the
symbology details for all the override cases within a system. You can also modify the system
default symbology details if necessary. For more information, see Symbology Control (on page
246).
245
Setup Commands
You must have defined at least one system and one-line type in the design file. For more
information, see Define System (on page 242) and Define One-Line Type (on page 244).
Steps
1. Select the Set Symbology Control command.
The Set Graphic Symbology Control form displays.

2. Using your cursor, select the individual area that matches a system and one-line type to "turn
on" an override for that case.
OR
Toggle the Available button in each field to None to change the defaults symbology for all
one-line types within a system. Each one-line type within the system will then have its own
symbology defined, so default symbology is not necessary for that system.
OR
Select a one-line type from the list to "turn on" the override for that type in all systems.
The Override setting displays in the appropriate field(s).

OR
Select the individual Override settings you wish to "turn off" (return to default status). To turn
off ALL selected Override settings, select the No Overrides button.
The Override settings you selected are deleted from the Override field and the default settings
restored.
3. Select
OR
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 (on page
245) for more information about this command).
The Symbology Control form displays the current symbology settings for all systems and
corresponding one-line types.
246
Setup Commands
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.
Steps
1. Select the Symbology Control command.
The Symbology Control form displays.

3. Select
OR
247
Setup Commands
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
248
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.
Setup Commands
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.
Engineering Units --- These fields (Master units, Sub units, and Positional units) display the
current PDS engineering units. You can only review the displayed settings.
Steps
1. Select the Set Text Defaults command.
The Text form displays.

3. Select
OR
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
249
Setup Commands
Select
to save your changes and exit the form.
OR
Select Cancel (X) to exit the form without saving any changes.
Create Cell Commands

The Create Cell commands create various types of raceway cells necessary for creating EE
Raceway models. The cells you create using this command are stored, along with all existing
cells, in your cell library.
You must have a cell library attached to the design file in order to activate the Create Cell
commands. EE Raceway is delivered with a sample cell library, rway.cel, which resides in
win32app\eerway\dgn. If you want to modify the delivered library, copy it to a non-production
directory, and modify the copied version. You must have write access to the library before
modifying it.
This section contains detailed descriptions of the following commands:
Using the Create Cell Commands (on page 250) Outlines the prerequisites, group
workflow, and basic instructions for using the Create Cell commands.
Create Model Cell (on page 251) Creates or recreates a model cell to carry the sheet name
of a drawing.
Create Equipment Pointer Cell (on page 253) Creates an equipment pointer symbol for
later placement in the design file.
Create Drop Point Cell (on page 255) Creates a drop point symbol for later placement in the
design file.
Using the Create Cell Commands

design session.

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
Group Workflow
There is no required or suggested sequence for using the Create Cell commands.
250
Setup Commands
Create Model Cell

This command allows you to create a model cell and to store that cell permanently in your cell
library.
Make sure you have a cell library attached to the design file before using this command
and be sure the library is not read only. To display a list of available cell libraries, key in rc=.
Steps
1. Select the Create Cell command.
The Select cell type form displays.
2. Select the Model button from the form.

3. Enter first fence point
If no fence is defined, place the first data point of a fence block diagonal. Include all the
graphic elements of the component. Be sure to include any existing annotation that you want
as part of the cell. Make enough room within the fence to include all text elements within the
fence. Do not include any elements within the fence that you do not want as part of the cell.
OR
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.
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.
251
Setup Commands
The Annotate Element form displays, allowing you to add annotation to the cell and
displaying those values already in the cell.
7. 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 (on page 151).
When complete, save your modifications by selecting
.
OR
Select Cancel (X) to exit the command without saving the changes. Return to step 7.
8. 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>.
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.
9. If you try to close with the fence around invalid elements, various error messages will display.
Refer to Error Messages (on page 327) for descriptions of these messages.
When you select Close, the Close cell parameters form displays.
252
Setup Commands
10. 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
.
11. 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.
Create Equipment Pointer Cell

This command allows you to create a equipment pointer symbol and to store that cell permanently
in your cell library.
Steps
1. Select the Create Cell command from the command menu.
2. Select the To Equipment button from the form.

OR
OR
253
Setup Commands

7. The Annotate Element form displays, allowing you to add annotation to the cell and
.
OR
9. Placing equipment tag, etc.
254
Setup Commands
Confirm ().
fenced elements.
OR
Create Drop Point Cell

This command allows you to create a drop point symbol and to store that cell permanently in your
cell library. Your cell library must contain a drop point cell for the placement of one-lines in the
design file (the drop point establishes connectivity between an RCP and a one-line where the two
are of a different one-line type).
Steps
1. Select the Create Cell command from the command menu.
2. Select the Drop Point button from the form.

OR
255
Setup Commands
OR

7. The Annotate Element form displays, allowing you to add annotation to the cell and
.
OR
9. Placing drop point tag, etc.
256
Setup Commands
.
fenced elements.
OR
Model Commands
These commands are used to place and manipulate model information in your design file.
257
Setup Commands
Commands
Using the Model Commands (on page 258) Outlines the prerequisites, group workflow, and
basic instructions for using the Model commands.
Lock Model (on page 259) Locks the symbology control parameters, the
defined systems, and the defined one-line types.
Move Model Annotation (on page 259) Moves the model annotation within the
design file.
Unlock Model (on page 260) Unlocks the model.
Annotate Model (on page 260) Adds, changes, or reviews the sheet name in a
model.
Using the Model 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.

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
Group Workflow
Before you can annotate or move annotation in the model, you must have locked the model using
the Lock Model command.
258
Setup Commands
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.
Move Model Annotation

This command moves the model annotation within a design.

Steps
1. Select the Move Model Annotation command.
The Move Model Annotation precision input form displays. The command checks the design
file for the existing model annotation and places it in drag mode.
Move the annotation to the desired location, and place it.
OR
Exit the command.
259
Setup Commands
Unlock Model
This command unlocks the model. If you want to change the symbology control or add new
systems and one-line types to a model that has been locked, you must first unlock the model using
this command.
Steps
1. Select the Unlock Model command.
2. A warning form displays.
3. Select
to unlock the model.
OR
Select Cancel (X) to exit the command without unlocking the 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. 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.
260
Setup Commands
The Annotate Element form displays.
2. Select the Column value field for sheet on the form and key in a new sheet number.
If a model is not annotated, the assigned model number will be the sheet number.
If you want to display the annotation in the model, toggle the Display fields in the form to On.
3. Select
to accept the new annotation.
OR
4. If you toggled Display to On, you are prompted to place the annotation in the model.
261
Setup Commands
262
SECTION 12
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.
Commands
Using the Runtime Setup Commands (on page 264) Outlines the prerequisites, group
workflow, and basic instructions for using the Runtime Setup commands.
Set Active One-Line Parameters (see "Set Active One-Line Type Parameters" on page
264) 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 (on page 268) Displays the current active one-line type
and allows you to select a new active one-line type.
Set Active System (on page 269) Displays the current active system and allows you
to set a new active system.
Propagation Setup (on page 271) Sets the active parameters for propagation in the
design file.
Set Active Levels (on page 272) Displays the current active level(s) and allows you
to turn Off displayed levels and to turn On new level displays.
Display Element Information (on page 273) Displays characteristics of selected

elements.
263
Using the Runtime Setup Commands

design session.

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 (on page 239) for more information about defining
Group Workflow
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 (on page
268)).
264

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.
with the specified one-line type. You can only review the information in this field.
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.
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.
the List column, then the column value has a corresponding codelist. To display the codelist,
select the *.
265
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.
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.
own select criteria.
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
. If
266

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.
Symbol
Name
Data Type
Description
equal to
numeric

>
greater than
numeric

<
less than
numeric

>=

equal to

!=
not equal to
numeric

wild chard
CHAR

value.
underline
CHAR

the given value.
Steps
1. Select the Set Active One-Line Type Parameters command.
An Active One-Line Type Parameters form displays.

3. Select
OR
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.
267
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 (on page 244)). 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
OR
268
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
(on page 242)). Using the Set Active System form, you can select a new active system from the
set of those available.
You can have multiple systems defined for a single one-line type as a way of defining split trays or
elements. This is done by specifying a system and one or more subsystems. The active system is
automatically included as a subsystem. The active system determines the symbology of the
one-line type, whereas subsystems do not.
You can have no more than six systems active for each one-line type.
Field Descriptions
Systems Selects the active system. When a new active system is selected, the
subsystems are all unselected. The active system is automatically included as a subsystem.
The active system determines the symbology of the raceway.
Subsystem Selects the subsystems. While this button is depressed, the Percent and
Project Rule can be defined for each subsystem.
Active System Displays the active system which determines the symbology of the
raceway.
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. This option is no longer used.
Systems Column Displays all the available systems. Selecting a row in this field defines
the Active System or Subsystems.
269
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
percent is displayed in the field at the bottom of the Percent column. All the selected systems
percentages are summed to calculate the total percentage. The Percent represents the
portion of the raceway's width assigned to that system. This Percent is used when calculating
the cable fill of the raceway section in the EECMS product.
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 *. This option is no longer
used.
Steps
1. Select the Set Active System command.
The Active System form displays.

2. Select the system and subsystem(s) you want to make active. To access the list of
subsystems, press the Subsystem button.
3. Define the percentages and the project rules you want to use.
4. Select
OR
5. Select Cancel (X) to exit the command without saving your changes.
270
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 (on page 89).
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.
271
If Eden is the active propagation mode, part verification will be performed, regardless
of the status of this toggle.
Automatic Propagation Enables or disables the automatic propagation of elements.
If you set the toggle to On, elements are automatically propagated when placed. Also, any
changes you make to an element, like editing the size, that affect the graphical display of the
propagation, will cause the propagation to be deleted and redrawn to reflect the change.
When the toggle is set to Off, automatic propagation is disabled.
Steps
1. Select the Propagation Setup command.
The Propagation Setup form displays.

2. Define the form parameters to meet your specifications.
3. Select
to save your changes and to exit the command.
OR
Select Cancel (X) to exit the command without saving any changes to the form.
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.
272
View Displays the active view. All level display settings on the form are valid for whatever
view is active. To change the active view, select a value from the list, or select the field, and
key in a new value.
Levels Indicate what levels display in the design. They also allow you to turn off or on the
display of some or all available levels.
1 - 63 indicate whether or not each available level displays in the design. When a level has its
display turned on, the button appears to be depressed. To turn on or off the display of a
particular level, select the appropriate level number.
All On Turns on the display of all levels in the design.
All Off Turns off the display of all levels in the design.
Restore Returns the display of levels in the selected view to its state prior to entering the
Set Active Levels command.
Turn Levels On/Off This toggle enables or disables the display for the levels associated
with the one-line types in your design file.
To turn on or off the display of a particular level, select the Turn Levels On/Off toggle, and
then select the desired level number displayed in the Systems/One Line list.
Systems/One Line Displays the available systems, their corresponding one-line types,
and the levels on which they display. You can only review the system and one-line information
in these fields, but can select the level numbers (in combination with the Turn Levels On/Off
toggle).
Graphics Displays the level display for title block annotation in the design file.
Steps
1. Select the Set Active Levels command.
The Levels form displays.

3. Select
to save your changes and to exit the command.
OR
4. Select Cancel (X) to exit the command without saving your changes.
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.
If a fitting or an RCP that is at the termination of a run is selected, then the four key attributes
associated with the fitting are displayed.
Steps
1. Select the Display Element Information command.
273

Select the element you want to review.
OR
3. Accept/reject
Press <D> to accept the element and display that element's information. Return to step 2.
OR
Press <R> to reject the highlighted element and select another element. Return to step 2.
274
SECTION 13
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.
Using the Utilities Commands (on page 276) This section outlines the prerequisites, group
workflow, and basic instructions for using the Utilities commands.
Commands
Toggle Construction Display On/Off (on page 277) Turns the display of construction
class elements on or off.
Highlight Element by Sector/Word (on page 277) Highlights elements with a given
sector/word position.
Highlight Element by ASID ID (on page 278) Highlights an element with a given
ASID ID.
Highlight Element by Link (on page 281) Highlights an element with given entity and
mslink values.
Highlight Propagation Errors (on page 282) Identifies existing propagation errors in
a design file.
Display Sector/Word Value (on page 283) Displays the sector/word position of an
identified element.
Display Element Type and ASID ID (on page 283) Displays the element type and
ASID ID of an identified element.
275
Utilities Commands
Display Link (on page 284) Displays the entity and mslink values of an identified
element.
Display System and One-Line Type (on page 284) Displays the associated system
and one-line type of an identified element.
Coordinate System (see "Active Coordinate System" on page 286) Activates the
Design Volume Coordinate System or Plant Coordinate System associated with the design file, or
shows the coordinate system currently active.
Using the Utilities Commands

design session.

You must be familiar with precision input and its functions before using any of the Modify
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).
276
Utilities Commands
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.
Highlight Element by Sector/Word

This command highlights elements by a sector/word position that you specify. The position of the
sector and word are compatible with EDG, and both are relative to 1. If the position is valid, the
element highlights, but is not added to a working set. If the element is part of a complex element,
the entire complex element highlights. The sector/word position must be the location of an
element type 2 (cell), 3 (line), 4 (line string), 6 (shape), 7 (text node), or 17 (text).
Highlight Sector/Word With Filename

You can specify a filename instead of the sector/word position to highlight an element. The file
must contain the sector/word position of the element(s) you want to highlight. The file will display
in a form on the screen, allowing you to select the sector/word value from the displayed file. If you
do not specify a pathname for the file, the command searches for it in the
<current_project>/rway/tmp directory.
Steps
1. Select the Highlight Element By Sector/Word command.
2. Key in sector and word value or file name
Key in the sector and word value separated by a space.
OR
Key in the name of a file containing the sector and word values. Go to Step 4.
277
Utilities Commands
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.
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
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.
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.
Steps
1. Select the Highlight Element By Asid Id command.
278
Utilities Commands
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.
3. Key in asid id or file name
Key in the ASID ID.
OR
Key-in the filename of a file containing the ASID IDs. Go to step 6.
OR
Press <R> to select a different Highlight by ASID ID mode. Return to step 2.
OR
Press <Esc> to exit the command. Return to step 1.
Identify the view in which you want the elements highlighted.
The raceway element(s) associated with the specified ASID ID highlight in the view 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
279
Utilities Commands
After you enter the filename, a file display form displays.
Select a line that contains an ASID ID.

7. After you select a line, select
to accept the ASID ID in the line. Go to step 8.
OR
Select the Return button to cancel the File Display form. Return to step 2.
OR
Select Cancel (X) to modify the highlight by asid mode. Return to step 1.
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.
280
Utilities Commands
Highlight Element by Link

This command highlights elements by given entity (table) and mslink values that you specify. If the
entity and mslink are valid, the element highlights, but is not added to a working set. If the element
is part of a complex element, the entire complex element highlights. The entity and mslink values
must correspond with an element type 2 (cell), 3 (line), 4 (line string), 6 (shape), 7 (text node), or
17 (text).
Highlight Link With Filename

You can specify a filename instead of the entity and mslink combination to highlight an element.
The file must contain the entity and mslink of the element(s) you want to highlight. The file will
display in a form on the screen, allowing you to select the mslink from the displayed file. If you do
not specify a pathname for the file, the command searches for it in the <current project>/rway/tmp
directory.
Steps
1. Select the Highlight Element By Link command.
2. Key in entity and mslink (###:###) or filename
Key in the entity and mslink values separated by a :.
OR
Key in the name of a file containing the entity and mslink values. Go to Step 4.
Identify the view in which you want the element to highlight.
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.
After you select a line, select
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
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.
281
Utilities Commands
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.
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
.
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.
282
Utilities Commands
Display Sector/Word Value

This command displays the sector and word position, in the MicroStation command window, of an
identified element.
Steps
1. Select the Display Sector/Word command.
2. Identify element
Select the element to display the sector/word for, and accept it with a <D>.
The sector and word for the selected element displays in the MicroStation command window.
OR
Display Element Type and ASID ID

This command displays the element type and the ASID identification (ID), in the MicroStation
command window, of an identified element.
Steps
1. Select the Display Element Type and ASID ID command.
2. Identify element
Select the element for which to display the ASID ID and accept it with <D>.
The element type and ASID ID display in the MicroStation command window.
OR
Press <R> or <Esc> to exit the command.
283
Utilities Commands
Display Link
This command displays the entity (table) and mslink, in the MicroStation command window, of an
identified element.
Steps
1. Select the Display Link command.
2. Identify element
Select the element you want to display the link for and accept it with <D>.
The entity and mslink values display in the MicroStation command window in the following
format: Entity (table number) = <value>, mslink = <value>
OR
Press <R> or <Esc> to exit the command.
Display System and One-Line Type

This command displays the system and one-line type associated with an element you identify.

Steps
1. Select the Display System and One-Line Type command from the menu.
284
Utilities Commands
The precision input form displays, along with the Print System and One-Line Type form.

Identify an element in the design file.

OR
Exit the command.
Accept/reject
The fields on the form fill with information about the element's one-line type, system, and
subsystems (if applicable). The system prompts you to identify another element.
OR
The system prompts you to identify another element. Go to step 2.

4. Continue identifying elements in the design file. Go to step 2.
OR
Exit the command.
285
Utilities Commands
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 (on page 286) Activates the Design Volume
Coordinate System (DVCS) allowing you to define a local coordinate system for a particular
model.
Activate Plant Coordinate System (on page 286) Activates the Plant Coordinate System
(PCS). The Plant Coordinate System is common to all models and drawings in a project.
Show Active Coordinate System (on page 286) 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.
286
SECTION 14
Raceway Processes
This chapter provides detailed descriptions of EE Raceway processes. You will run all EE
Raceway processes from the Process menu found on the EE Raceway Drawing menu. (See
Process in the section entitled EE Raceway Environment for information about running all
processes.) The individual EE Raceway processes are described in the following sections:
Load Database (on page 287) Loads the project database with information generated from
the EE Raceway drawing.
Unload Design (on page 290) Removes all the information associated with a particular
drawing from the project database, based on the design filename you specify.
Unload Sheet (on page 292) Removes all the information associated with a particular
drawing from the project database, based on the internal sheet name you specify.
Cleanup Database (on page 294) Removes any data from a project database that is not
currently associated with a design in the project's ../rway/dgn directory.
Create Interference Envelope (default name) (on page 296) 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) (on page 297) 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.
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.
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.
This process calculates the following values:
Table Name
Column Name
Comments
rcp_to_drw
pds_east*
The PDS east coordinate of the corresponding

RCP's origin.
rcp_to_drw
pds_north*
The PDS north coordinate of the corresponding

RCP's origin.
rcp_to_drw
pds_elev*
The PDS elevation coordinate of the corresponding

RCP's origin.
rcp_to_sys
ee_percent***
Indicates what portion of the corresponding RCP is

287
Raceway Processes
Table Name
Column Name
Comments
drop_point
ee_dist_down_ol**
The distance down the one-line to the point on the

one-line closest to the drop point origin.
drop_point
ee_dist_to_rcp**
The orthogonal distance from the drop point origin to

the RCP's origin, and the orthogonal distance from
the drop point origin to the closest point on the
one-line.
one_line
ee_ol_length**
The total graphical length of the one-line in master

units.
ol_to_sys
ee_percent***
Indicates what portion of the corresponding one-line

straight
ee_tl_length
The graphical length of the straight in master units.
straight
pds_east*

straight's range.
straight
pds_north*

straight's range.
straight
pds_elev*

the straight's range.
str_to_sys
ee_percent***
Indicates what portion of the corresponding straight

fitting
pds_east*

fitting's ange.
fitting
pds_north*

fitting's range.
fitting
pds_elev*

the fitting's range.
fit_to_sys
ee_percent***
Indicates what portion of the corresponding fitting is

* 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
288
Raceway Processes
The Load database screen displays.
2. Enter drawing name.

Select a design file from the Drawing List or key in a design filename (you may specify
multiple design files).
You can load a .dgn file with any sheet number. Plant Design System (PDS) does not
expect a unique sheet number.
If you try to load a .dgn file that has already been loaded with a different sheet name, Plant
Design System (PDS) reloads the .dgn file with the model annotation as the sheet name.
defaults.
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 (on page 53)).
5. Confirm your selections.
, and the process
begins.
289
Raceway Processes
Messages
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.
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.
Batch File Option

The load database process can be executed from a batch file. Setup an rway.bat file to export the
necessary Microstation and EERWAY environment variables to execute the load database
process. Include the following EERWAY environment variables:
EES_REFDB --- RIS Schema name for reference database
EE_SCHEMA --- RIS Schema name for project database
EERD_MSGS --- Directory path for EERWAY message files
EERD_TBLS --- Directory path for EERWAY database table files
Example of rway.bat:
SET MS=D:\WIN32APP\USTATION
SET MS_EXE=D:\WIN32APP\USTATION
SET EES_REFDB=CERT60_REF
SET EE_SCHEMA=CERT60_PRJ
SET EERD_MSGS=D:\WIN32APP\INGR\EERWAY\MSG\
SET EERD_TBLS=D:\WIN32APP\INGR\EERWAY\MSG\
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
290
Raceway Processes
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. Select an option for resetting Mslink numbers.
Do Not Reset Mslink Numbers is the default setting on the Do Not Reset Mslink
Numbers/Reset Mslink Numbers toggle.
Resetting the Mslink numbers ensures that there are no duplicate MS_linkage
numbers when you load to the database in the master site.
4. 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.
You may choose between foreground, background, and batch operating modes for most
291
Raceway Processes
begins.
, and the process
Messages
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.
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.
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
292
Raceway Processes
The Unload Sheet database screen displays.
2. Key in a sheet name.

3. Key in unique filenames for the error and message files (or accept the default filenames).
The default error and message filenames are displayed in appropriate fields. You may change
the defaults by selecting the fields and keying in new names.
The default error and message files will be overwritten every time the process is run,
unless you specify unique filenames in these fields.
You may choose between foreground, background, and batch operating modes for most
, and the process
begins. When complete, the process will return one of two messages (described below) to the
screen.
Messages
293
Raceway Processes
working directory, lists all the errors that occurred during processing. The file is automatically
displayed to the screen for your review.
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.
Cleanup Database
This process removes information from the database that is not in any drawing currently loaded in
the database.
For example, information may have been added through the Relational Database Management
System (RDBMS) to test for a special case or to create customized tables. This process also
removes information on any EE Raceway drawing which has been deleted, but for some reason
was not removed from the database.
The Cleanup Database process deletes all records of raceway connect points (RCP), one-lines,
and three-lines that are part of the project database but which are not part of any raceway design
file. This process will not unload records of customized tables in the database. The process uses
the filenames in the drawing table of all current drawings. It then makes a list of all valid drawings,
and deletes anything from the database which is not connected to one of these drawings. This
process will not delete drawings. It will delete from the database only that information which is not
in any current drawing.
Steps
1. Select Cleanup Database from the Process Menu, and select
294
Raceway Processes
The Cleanup Database screen displays.

defaults.
You may choose between Foreground, Background, and Batch operating modes for most
.
The process begins. When complete, the process will return one of two messages (described
below) to the screen.
Messages
working directory, lists all the errors that occurred during processing.
295
Raceway Processes
current working directory, is created. It will display mostly zeroes, and it includes a log of what was
unloaded during processing.
You can view either file using the Output option on the Utilities screen.
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.

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.
296
Raceway Processes
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.
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 (see "Electrical Engineer (EE) Raceway
Environment" on page 49) for information about operating modes).
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
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.
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.
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>.
297
Raceway Processes
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:

OR
Select a design file from the Drawing List (use the Select All button to select all files from the
list) or key in a design filename.
3. Key in a name for the envelope file.
4. Key in unique filenames for the error and output files (or accept the displayed default
filenames).
The default error and output files will be overwritten every time you run the process
unless you specify unique filenames in the fields.
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).
298
Raceway Processes
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
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.
<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.
299
Raceway Processes
300
SECTION 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 (on page 49).
The path to the symbol library called in many of the Eden processes is defined by the variable
RWAY_EDEN_LIB. The delivered default symbol library path is win32app\eerway\eden. If you
want to place your Eden library in a different directory, then edit the .EErc file in your home
directory, exporting RWAY_EDEN_LIB to specify the appropriate directory.
The path to the extracted symbol source file called in many of the Eden processes is defined by
the variable RWAY_EDEN_SRC. The delivered default symbol source file path is
<current_project>/rway/tmp. If you want to place your source symbol files in a different directory,
then edit the to specify the appropriate directory.
For a general description of Eden symbol generation, see the PDS Eden Interface Reference
Guide. You should also consult the appendix in this guide entitled Eden Symbol Generation (on
page 429).
Each Eden process is described in a separate section, as follows:
Compile EDEN Symbol (on page 302) Compiles an Eden symbol file, and gives you the
option of placing the symbol in an Eden symbol library.
Delete EDEN Symbol (on page 304) Deletes an Eden symbol from the Eden symbol library.
List EDEN Symbol Library (on page 306) Lists Eden symbols in a selected Eden symbol
library.
List EDEN User Functions (on page 307) Lists Eden user functions in a selected Eden
symbol library.
Merge EDEN Symbol Libraries (on page 309) Merges the contents of two Eden symbol
libraries into one library.
Compress EDEN Symbol Library (on page 311) Compresses an Eden symbol library to
remove unused space left by deleted symbols.
Extract EDEN Symbol From Library (on page 312) Extracts a specified symbol from an
Eden symbol library.
Extract EDEN User Function From Library (on page 314) Extracts a specified user function
from an Eden symbol library.
Edit EDEN Symbol File (on page 317) Uses a standard ASCII editor to edit a specified
symbol source file.
301
Eden Processes
Compile EDEN Symbol

This process compiles an Eden symbol file, and gives you the option of placing the compiled
symbol in an Eden symbol library.
Output file Displays the file to which process messages are sent. To change the displayed
output filename, select the field, and key in a new filename.
Error file Displays the file to which error messages are sent. To change the displayed error
filename, select the field, and key in a new filename.
Enter library name Displays the default Eden symbol library name. For information about
the path to the symbol library, see the description at the beginning of this chapter. To change
the displayed default library name, select the field, and key in a new library name.
Enter symbol source file Displays the name of the symbol source file to compile. For
information about the path to the symbol source file, see the description at the beginning of
this chapter. To enter the symbol source file, select the field, and key in a filename.
Enter option Displays the default compile option (-o). The -o option lists the compiled Eden
symbol file, and then adds the symbol to the specified library. The -l option simply lists the
compiled Eden symbol file. To change the displayed option, select the field, and key in a new
option.

You must create an Eden symbol file. See Eden Symbol Generation (on page 429) for information
about symbol file creation.
302
Eden Processes
Steps
1. Select Compile EDEN Symbol from the list, and select
The Compile EDEN Symbol form displays.

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 (on page 55).
When you have completed the input information, select
, and the Eden process
begins.
Messages
working directory, lists all the errors that occurred during processing. The .err file displays
immediately to the screen for your review.
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 (on page 75).
303
Eden Processes
Delete EDEN Symbol

This process deletes an Eden symbol from the Eden symbol library.
Enter library name Displays the default Eden symbol library name. To change 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.
Steps
1. Select Delete EDEN Symbol from the list, and select
The Delete EDEN Symbol form displays.

304
Eden Processes
begins.
Messages
305
Eden Processes
List EDEN Symbol Library

This process lists the Eden symbols in the selected Eden library.
Steps
1. Select List EDEN Symbol Library from the list, and select
The List EDEN Symbol Library form displays.

Set up the form parameters to meet you specifications.
306
Eden Processes
begins.
Messages
List EDEN User Functions

This process lists the Eden user functions in the selected Eden library.
307
Eden Processes
Steps
1. Select List EDEN Symbol Library from the list, and select
The List EDEN User Functions form displays.

, and the list will display.
Messages
308
Eden Processes
Merge EDEN Symbol Libraries

This process merges two Eden symbol libraries into one.
Merge into library name Displays the name of the symbol library into which 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.
Steps
1. Select Merge EDEN Symbol Libraries from the list, and select
The Merge EDEN Symbol Libraries form displays.

309
Eden Processes
begins.
Messages
310
Eden Processes
Compress EDEN Symbol Library

This process compresses the selected Eden symbol library. Compressing the library removes the
unused space left by deleted symbols.
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
The Compress EDEN Symbol Library form displays.

311
Eden Processes
begins.
Messages
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.
312
Eden Processes
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.
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.
Steps
1. Select Extract EDEN Symbol From Library from the list, and select
The Extract EDEN Symbol From Library form displays.

313
Eden Processes
begins.
Messages
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.
314
Eden Processes
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.
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.
Steps
1. Select Extract EDEN User Function From Library from the list, and select
The Extract EDEN User Function From Library form displays.

315
Eden Processes
begins.
Messages
316
Eden Processes
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.
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.
Steps
1. Select Edit EDEN Symbol File from the list, and select
The Edit EDEN Symbol File form displays:

317
Eden Processes
begins.
Messages
318
SECTION 16
Integrated Commands
The Integrated Commands are common to EE Raceway and several other PDS modules,
providing greater interoperability among the various disciplines. These commands allow you to
review an element's attributes, review the PDS clashes in a model, create a window containing a
specific element, display information about the reference models attached to the current model,
and view the area volume graphics for clash and design areas.
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.
Using the Integrated Commands

design session.
Review PDS Attributes You must have an existing component in the active model or in an
attached PDS reference file.
Reference PDS Model (on page 320) There are no prerequisite conditions for using this
command.
Window to Named PDS Item (on page 321) 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 (on page 323) - You must turn Construction Graphics on in
MicroStation. See the command description for more details.
Group Workflow
The Utilities > 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.
319
Integrated Commands
To view pipe centerlines (to review the line segments), you need to display construction
type elements. Use the MicroStation Settings > View Attributes > Turn on construction
command.
Parameters
Attribute Name Lists the item's attributes.

Value Displays the item's attribute value that is defined in the database.
Close Exits the Review PDS Attributes dialog box.
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
320
Disciplines Lists all disciplines. Select the discipline which contains the model you want to
attach; then, click Attach.
Integrated Commands
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. 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.
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.
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.
321
Integrated Commands
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.
The Review PDS Clash command edits and reviews existing clashes and approves existing
clashes.
In order to review clashes involving structural models, the structural models must be
propagated. Please refer to the FrameWorks Plus documentation set for more details on
propagating models.
Parameters
Project Name Displays the active project name.
Design Area Displays the active design area name.
322
Integrated Commands
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.
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.
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:
323
Integrated Commands
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
324
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.
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.
Integrated Commands
325
APPENDIX 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.
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.
327
Error Messages
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>

Reason: Display the element's asid number along with a message, when highlighting by sector
and word.
Recovery: None.
Bad user data on raceway element

Reason: Element has been corrupted.
Recovery: Contact Intergraph support.
Bad user data in design file: cannot continue!

Cannot access filelist <string>!

Reason: The file containing the filelist is not available.
Recovery: Give the correct filename or access to the file.
Cannot attach to database

Reason: The database does not exist or you do not have privilege.
Recovery: Be sure the database exists and that you have privilege.
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.
328
Error Messages
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.
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

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.
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>
329
Error Messages
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

Could not open file <string>

Could not open logfile <string>

Reason: A number of factors may result in this error.
Recovery: There are various recoveries, based on cause of error.
Could not read one-line user element

Reason: Rmon could not read the one-line user element.
Recovery: Check to see that the design file has a type 63 element and at least 7 blocks in it.
Could not read the PDS 1 user element

Reason: The Raceway design file was not created using a PDS or EE Raceway seed file.
Recovery: None.
Could not read the PDS 2 user element

Reason: The Raceway design file was not created using a PDS or EE Raceway seed file.
Recovery: None.
Could not read system user element

Reason: Rmon could not read the system user element.
330
Error Messages
Could not read the Raceway user element
Reason: Rmon could not read the Raceway user element.
Could not retrieve codelist values

Reason: The value placed in the codelist column does not appear in the codelist table.
Recovery: Change the value to one that appears in the codelist table.
Could not retrieve specifications for key <string>

Reason: You key in a value for the key to the secondary table.
Recovery: Key in a new key value.
Could not write to TCB, status = <numeric value>

Reason: The process tried to write a TCB variable to the design file.
Recovery: Make sure you have write access to the design file.
Cutback Error at oneline <numeric value>

Reason: Problems occurred in calculating the cutback from the fitting at the end of a one-line.
Defaults do not exist for <string> key = <string>

Reason: An entry in the database does not exist for the specified key.
Recovery: Make sure the key is correct. The database is case-dependent. If the key does not
exist, insert it into the reference database.
Design file <string> does not exist!

Reason: The referenced design file was cannot be found.
Recovery: Enter correct filename.
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.
331
Error Messages
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.
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.
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.
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.
332
Error Messages
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>!

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.
333
Error Messages
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.
Error loading drop point!

Reason: No privilege for this operation.
Recovery: Add privilege to the database.
Error loading fittings!

Error loading one-lines!

Error loading raceway connect points!

Error loading straights!

Error loading systems!

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.
334
Error Messages
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.
Error opening project database!

Recovery: Add schema to database or change schema name.
Error opening reference database!

Recovery: Add schema to database or change EES_REFDB.
Error parsing cross section

Reason: An error occurred while parsing a cross section.
Recovery: Delete the one-line containing the RCP and place it again.
Error parsing one-line

Reason: An error occurred while parsing a one-line.
Recovery: Delete the one-line and place it again.
Error parsing RCP

Reason: An error occurred while parsing a raceway connect point (RCP).
Recovery: Delete the one-line containing the RCP and place it again.
Error querying ref db for mscatalog

Reason: The mscatalog table does not exist or there is no connect permission.
Recovery: Run the Create Database process with the rwayref.sql file.
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.
335
Error Messages
Error reading TCB of design file!
Reason: TCB corrupted.
Error reading database column names!

Reason: No access to column names.
Recovery: Add privileges to database.
Error reading database table names!

Reason: Table name in mscatalog table invalid.
Recovery: Correct entry in mscatalog.
Error reading file list <string>!

Reason: No access to read file list.
Recovery: Change file list name or protection on file list.
Error reading user element of design file!

Reason: User element missing or corrupt in design file.
Error saving symbology - Design file may be corrupted

Reason: Could not save the symbology to the design file.
Error sheet name cannot be duplicated!

Reason: A drawing with the given sheet name already exists in the database.
Recovery: Edit the sheet name. The sheet name must be unique within the database.
Error spawning server

Reason: Could not open reference schema.
Recovery: Return to the environment and make sure you are using the correct reference schema.
Error unloading Sheet!

Reason: Sheet not found.
Recovery: Enter correct sheet name.
Error unloading connect points!

Reason: No privilege to delete from database.
Recovery: Add privilege.
Error unloading drawing!

Reason: No privilege to delete from database.
336
Error Messages
Error starting or stopping graphic bang.
Error updating row in <string> table!

Reason: No privilege to write to database.
Errors existed during unload

Reason: Errors in other procedures.
Recovery: Fix other errors.
Errors occurred during interference detection process!

Reason: Fatal error occurred during process.
Recovery: Read previous error messages to determine cause.
Fatal error! Vector length was negative.

Reason: Interference detection found an item of size = 0 (length).
Recovery: None. The process creates a zero-length envelope.
Field may not contain an empty value

Reason: Field cannot be left blank.
Recovery: Key in a value.
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.
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.
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.
337
Error Messages
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.
Form could not be created

Reason: A form could not be created by the software. Possible memory allocation problem.
Form could not be displayed

Reason: Once created, a form could not be displayed by the software.
Recovery: Fatal error. Try to exit and re-enter the software.
Form creation error

Reason: The software could not create a form.
Recovery: Exit and re-enter the product.
Form error could not find form file <string>

Reason: The referenced form file could not be found in the path defined by EE_FORM_PATH.
Recovery: Make sure the referenced form file exists in the path defined by EE_FORM_PATH
which is 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.
338
Error Messages
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.
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.
339
Error Messages
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.
Invalid Part Found at RCP asid <numeric value>.

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

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

Reason: The RCP has more or fewer than two one-lines attached.
Recovery: You can only remove an RCP with exactly two one-lines attached.
Invalid real number: <string>

Reason: The value entered must contain a decimal with a preceding number.
Recovery: Re-enter a valid real number.
340
Error Messages
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.
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.
341
Error Messages
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.
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.
342
Error Messages
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.
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.
343
Error Messages
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.
No valid special parts exist for this table

Reason: There are no special parts defined in the active table.
No values found in the codelist

Reason: The codelist table contains no rows.
Recovery: Insert the rows into the codelist table that corresponds to the column.
No write access to cell library

Reason: The attached cell library is read only.
Recovery: Attach a cell library that has read/write permissions or assign write permission to the
current 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.

Reason: One-line type user data corrupt on one-line OR the system symbology user elements
have been corrupted.
344
Error Messages
Problem with shared memory!
Project schema not defined

Reason: EE_SCHEMA has not been exported.
Recovery: Export the variable EE_SCHEMA.
Projecting oneline with asid <numeric value>.

Reason: This identifies which one-line is being projected.
Recovery: None.
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

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.
345
Error Messages
Style not in range 0 to 7
Reason: The input was not within the valid range for style.
Symbol file not found: <string>

Reason: The symbol file EE_SYM_FILE could not be found in the symbol path EE_SYM_PATH.
Recovery: Make sure EE_SYM_FILE and EE_SYM_PATH are defined in the directory.
Table number <numeric value> not in mscatalog

Reason: The specified table number / table name entry does not exist in the reference database.
Recovery: Add the missing entry into the mscatalog table by loading the mscat.unl file or inserting
a 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.
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.
346
Error Messages
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.
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.
347
Error Messages
348
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 (see "EE Databases" on page 359) 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 (see "Specification" on page 423) describes vendor specifications and
how to prepare them.
Appendix E: Eden Symbol Generation (see "Eden Symbol Generation" on page 429) describes
generation of Eden symbols and provides a sample symbol processor file.
Appendix F: EE File Structure (see "EE File Structure" on page 435) 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 (see "Customizing Environment Files" on page 443)
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 (see "alias.cmd file" on page 451) 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 (see "rway.cmds" on page 455) 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 (see "Reports" on page 457) contains detailed descriptions of the standard
and rule checks reports delivered with the product.
Appendix K: RIS Schema Manager (see "RIS Schema Manager" on page 463) contains a detailed
description of the RIS Schema Manager utility.
Appendix L: RIS Schema Definition File (see "RIS Schema Definition File" on page 471) describes
the file that maintains all schema definitions known to RIS.
Appendix M: EE Manager (see "EE Manager" on page 473) contains a description of the EE
Manager utility and its Edit Database process. (see "Database Edit Functions" on page 475)
Appendix N: EE Configure (see "EE Configure" on page 477) describes the EE environment
variables and how to configure them.
Customizing
Some simple customization is described in the appendices entitled Customizing, alias.cmd, and
rway.cmds (all involve modifying existing text files using an editor). More extensive customization
is possible for advanced users. Such customization includes writing processes and user
commands using the MicroStation software. Refer to the MicroStation Applications Programmer's
Guide for this latter procedure.
349

Precision Input Form
Several designs of the precision input form are delivered with EE Raceway. The available
precision input forms (described below) reside in win32app\eerway\sym.
Form Name
Description
piform*
default
piform_tal1
tall/thin (design 1)
piform_tal2
tall/thin (design 2)
piform_thn1
long/thin (design 1)
piform_thn2
long/thin (design 2)
* The chapter entitled Precision Input Form contains a detailed illustration of the default form
design (piform).
To change the form design, set the variable EE_PIFORM in the .EErc file (win32app\eenuc) to a
different form name.
Adding a One-Line Type

This section outlines the basic steps necessary to add a new one-line type to the reference
database. For detailed information about editing your .unl files and database tables, consult the
appendix entitled EE Databases. These instructions are intended as a basic workflow.
1. Add the <one-line_type>_spec and <one-line_type>_part tables to the reference database,
as in the following example:
create table trench_spec
(
vendor integer not null,
ee_units integer not null,
ee_dimension_1 real,
ee_out_ht_diam real not null,
ee_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) not null,
description char(40)
);
create index i_fsvendor on trench_spec(vendor);
create index i_fsheight on trench_spec(ee_out_ht_diam);
create index i_fswidth on trench_spec(ee_out_width);
create unique index i_fseekey on trench_spec(ee_spec_key);
grant all on trench_spec to public;
350

create table trench_part
(
ee_tl_type integer,
ee_tl_subtype integer,
ee_tl_qual integer,
ee_angle real,
ee_weight real,
ee_part char(20),
ee_symbol char(6),
ee_spec_key char(28),
ee_spec2_key char(28),
ee_part_key char(28) not null,
ee_description char(40)
);
create index i_fpskey on trench_part(ee_spec_key);
create unique index i_fpeekey on fit_part(ee_part_key);
grant all on trench_part to public;
2. Add any new vendors to the vendor table in the reference database.
You can add the necessary rows directly to the vendor codelist table in the database, or you
can add the data to your vendor.unl file.
All delivered .unl files reside in win32app\eerway\db.
3. Create a <one-line_type>_spec.unl file and a <one-line_type>_part.unl file which contain the
required default values for the one-line type.
For sample files, refer to the tray_spec and tray_part .unl files that are delivered with EE
Raceway.
4. Add the newly-created <one-line_type>_spec.unl file and the <one-line_type>_part.unl files to
the rwayref.cmd file, in a format like the following:
FILE "tray_part.unl" DELIMITER "|";
INSERT INTO tray_part;
5. Add records to the mscatalog table (in the reference database) for both the
<one-line_type>_spec and the <one-line_type>_part tables.
You can accomplish this either by adding rows directly to the mscatalog table or by inserting
records in the mscatref.unl file.
6. Add records to the mscolumns table (in the reference database) for both the
<one-line_type>_spec and the <one-line_type>_part tables.
You can accomplish this either by adding rows directly to the mscolumns table or by inserting
records in the mscolref.unl file.
7. Add necessary rows to the mscodelist table in the reference database for any columns that
are codelisted for the one-line type.
You can accomplish this either by adding rows directly to the mscodelist table or by inserting
records in the mscodref.unl file. For information about codelists, see EE Databases (on page
359).
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.
351

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,
ee_units integer not null,
ee_out_ht_diam real not null,
ee_out_width real,
weight real,
material char(20),
ee_part char(20),
ee_symbol char(6),
ee_part_key char(28) not null,
ee_description char(40)
);
create index i_tsitvendor on transit(vendor);
create index i_tsitheight on transit(ee_out_ht_diam);
create index i_tsitwidth on transit(ee_out_width);
create index i_tsitdepth on transit(ee_dimension_1);
create unique index i_tsiteekey on transit(ee_part_key);
grant all on transit to public;
2. Add any new vendors to the vendor table in the reference database.
You can add rows directly to the vendor codelist table in the database, or you can insert
records in the vendor.unl file.
3. Add the new special fitting to the three-line type codelist table.
You can add the entry directly to the tl_type table in the database, or you add the data to your
tlt.unl file.
4. Create any new Eden symbols needed to graphically display the new special fitting.
For basic information about creating Eden symbols, see Eden Symbol Generation (see "EE
Databases" on page 359).
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.
352
8.
9.
10.
11.
You can accomplish this either by adding a row directly to the mscatalog table, or by inserting
a record in the mscatref.unl file.
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.
Add necessary rows to the mscodelist table (in the reference database) for any columns that
are codelisted for the special fitting.
You can accomplish this either by adding rows directly to the mscodelist table or by inserting
records in the mscodref.unl file. For information about codelists, see EE Databases (on page
359).
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.
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.
EE Environment Variables
This section lists and describes the environment variables that are delivered when you download
EE Raceway. They include Microstation, EE Nucleus, and EE Raceway-specific variables.
These environment variables can be modified using the Start > Programs > EENUC > EE
Configure command.
The following environment variables are defined in the win32app\eerway\ee.cfg file:
For MicroStation:
MS_CELL
Sets the directory that holds the cell libraries.
MS_APP
Sets the directory where application executable files

are found when activated from a user command TSK
statement.
MS_EXE
Used as a pointer to application programs.
MS_APPMEN
Sets the directory where application-/user-defined

menus are to found when activated from an
"am=n,cs", "am=n,h1", or "am=n,sb"
(i.e."am=ustn,sb1").
353

MS_DATA
Sets the directory that holds the menu file mgds.men,

the file MicroStation uses to save data about the
attached menu. This directory is also the location of
user command index (.ndx) files.
MS_TMP
Sets the directory for temporary files.
MS_HELPFILE
Sets the directory for the on-line Help files.
MS_HELPPATH
Defines the path to the on-line Help files.
The MicroStation\Program\MicroStation\config\msconfig.cfg file contains detailed

descriptions of the MicroStation and Umenu environment variables.
For EE Raceway:
EERD_COMPRESS
Compresses the file when you exit a design session.
EERD_MSGS
Directory for the message files.
EERD_TBLS
Directory for the database table files
RWAY_FORM_PATH
Directory path to the EE Raceway forms.
EE_SYM_PATH
Directory path to the EE Raceway symbols.
EE_SYM_FILE
File containing EE Raceway symbols.
The following environment variable is defined in the win32app\eerway\bin\c400 or
c100/rmonshell file:
MS_CACH
Sets the memory to be allocated for a design file

editing session. This variable will override the user
preferences setting.
The following are the environment variables that are recognized by the EE Nucleus
product. An asterisk (*) indicates that you cannot override a particular value.
You may need to resize the Help window to view the tables below in their entirety.
EE_CURPRJ*
Directory path for current EE project.
EE_DBS*
Directory path and project database name.
EE_NODENAME
Default nodename for archive/restore.
EE_REMDIR
Default remote path for archive/restore.
EE_SCHEMA
Schema name for project database.
EE_USERNAME
Default username for archive/restore.
SYS_PASSW_FILE
Directory path and filename of password file to enter

system manager page.
EE_CUSTOM_SQL
User-defined project database sql file.
EE_CUSTOM_CMD
User-defined project database cmd file.
EE_CUSTOM_REFSQL
User-defined reference database sql file.
EE_CUSTOM_REFCMD
User-defined reference database cmd file.
The following are the environment variables defined in the win32app\eenuc\.EErc file,
delivered with the EE Nucleus product. An asterisk (*) indicates that you cannot override a
particular value.
354

You may need to resize the Help window to view the tables below in their entirety.
For EE Raceway:
EE_RWAY*
Directory path for the EE Raceway product.
EERWAY_DAT
Directory path for data files.
EERWAY_SEED
Directory path for seed files.
RWAY_CMD
Project Database cmd file.
RWAY_SQL
Project Database sql file.
RWAYREF_CMD
Reference Database cmd file.
RWAYREF_SQL
Reference Database sql file.
EDEN_LIB
Filename for the Eden symbol library.
RWAY_EDEN_LIB
Directory path for the Eden symbol library.
EE_PIFORM
Name of the precision input form that displays during

the design session.
The following are the environment variables defined in the win32app\eenuc\bin\EE file,
delivered when you download the EE Nucleus product.
MS_USERPREF
Directory path and filename of user preference file.
MS_CMDWINDRSC
Directory path and filename of command window

resource file.
MS_SYSFONTS
Font used by MicroStation for window and menu

display.
EE_TERM
Defines the "tty" type you are running on.
ORACLE_SID
A variable used for ORACLE databases; it must be

set to "A".
The following are the environment variables defined using the EE Configure command,
delivered when you download the EE Nucleus product. An asterisk (*) indicates that you
cannot override a particular value.
MS_DIR
Directory path for the MicroStation product.
RIS_DIR
Directory path for the RIS product.
EE_NUC*
Directory path for EE Nucleus product.
ENV_MSGS
Directory path for message files.
EENUC_DAT
Directory path for data files.
DBA_SUPPORT
Data files for DB Access Support.
EES_REFDB
Schema name for reference database.
EES_REFSER
EE reference database server process.
EE_FORM_PATH
Directory path for EE forms.
EE_SYM_FILE
Filename of EE symbol file.
EE_SYM_PATH
For ORACLE databases:
Directory path for EE symbol file.
355

ORACLE_HOME
356
Directory path for ORACLE executables.
357
358
APPENDIX C
EE Databases
All EE databases you create will be relational databases; that is, they are based on the relational
data model in which a relation is a two-dimensional table comprised of rows and columns. Most
relational databases use Standard Query Language (SQL).
The EE products attach to their relational databases through Intergraph Corporation's Relational
Interface System (RIS), a generic relational database interface. RIS isolates the differences in
specific vendors' Relational Database Management Systems (RDBMS), allowing generic network
access to all EE databases generated with the following RDBMS's: Oracle and MS SQL.
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.
Relational Interface System (RIS)

All EE products use a RIS schema, which you define, to attach to an SQL-type database. The RIS
schema identifies a unique database/user combination in a given commercial database system.
Different RDBMS's establish users in different ways; in fact, the very concept of a database differs
greatly from one RDBMS to another. Through the use the RIS risschema_mgr product, you can
update schemas without knowing either the differences between RDBMS's or the syntax of the
RIS create schema statement. (See RIS Schema Manager (on page 463) for more information
on the RIS Schema Manager product.)
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.
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 RIS Schema Manager (on page 463) for detailed information on using the RIS
359
EE Databases
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.
After 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 (on page 34)). For more information about the risschema file, see
RIS Schema Definition File. (see "RIS Schema Definition File" on page 471).
Update Schema (create_db) Process

You can use this program to do the following:
Update an existing empty RIS schema with EE tables and default information.
OR
Modify an existing RIS schema's tables to conform to the structure of a given .sql file. If Update
schema is used with a .sql file that has a different structure than the original .sql file, the
process will:
add new tables listed in the .sql file.
modify existing tables if the definition of that table has changed in the .sql file. The process
replaces the old table definition with the new table definition keeping column data where
column names match.
load those tables having a unique index with data from the .unl files that are listed in the
.cmd files. Where a table lacks a unique index, the process loads it only if the table is
empty.
You should run the Update schema process from the EE Environment Project Menu. To run it
outside of the EE Environment, you must first export the variable ENV_MSGS to
win32app\ingr\eenuc\msg, and then key in the command line syntax for the process.
This is the command line syntax for the Update schema process:
win32app\eenuc\bin\create_db [-v] [-q .sql file] [-c .cmd file] schema name
-v
displays SQL commands as they are executed
-q .sql file
schema definition file
-c .cmd file
command file to load schema
To create a new schema, you must have at least:

an SQL (.sql) file which contains the table and column structure.
If you want to load a schema with default information, you can also include:
a command (.cmd) file that defines which .unl files to load into which tables;
AND
the corresponding .unl file(s) which contain default information.
360
EE Databases
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.
Reference Schema - General Description

The Electrical Engineer reference database is a multi-table relational database containing default
attribute information and specification information. You can establish default attributes for
drawings, raceway connect points (RCPs), one-lines, drop points, and equipment pointers. All
specification information is carried in the reference database.
You will access the reference database during the following procedures:
1. When editing/reviewing annotation for EE Raceway elements (title blocks, one-lines, RCPs,
straights, fittings, and so forth) during a design session.
2. Selecting the active one-line type parameters during a design session.
3. Reporting.
Default Attributes
Some tables exist in the reference schema to support default attributes, including, for example,
the drawing, one-line, RCP, tray_spec, and tray_part tables. Each table must contain at least a
subset of the column/attribute structure as its corresponding table in the project schema. For
example, if the reference schema is custom-built, the project schema must be custom-built
accordingly. But if the project schema is custom-built, the reference schema needs to be
custom-built only if you want defaults for any new column to exist in the reference schema.
Some of the columns in the reference schema tables are required and cannot be modified
or deleted.
Keys
In addition to the default attribute columns, the reference schema tables contains two additional
columns: key_column and key_description. The actual column names are defined by the values of
the key_columns and key_description in the mscatalog entry for the given table. The key_column
field is a unique index used to identify a particular row of default attributes in the reference
schema. Each of the tables is delivered with one entry called DEFAULT. If the system cannot find
a key for some reason, it uses the DEFAULT key attributes.
Raceway One-Line Keys

A key is stored for each one-line type within a drawing. You will identify these keys through the
Active One-Line Type Parameters form. Each of these keys will be the default key for all
one-lines of a given one-line type unless you override the key during annotation for an individual
one-line. The one-line table is delivered with both the DEFAULT and METRIC DEFAULT keys.
The DEFAULT key is used with the seed design file using English measurements, while the
METRIC DEFAULT is used with the seed design file using Metric measurements.
361
EE Databases
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.
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 I in the reference
database will contain all possible values that can be loaded into the I in the straight, fitting, and Ie
tables in the project database.
During loads of the project database, the reference database codelists are matched to the
annotated values. Only values in the reference database codelist tables are loaded into the
project database. The system issues you a warning if an annotated value does not match a value
in the codelist.
You must be familiar with the codelist tables that follow.
Approval Status Codelist Table

The approv_status codelist table defines the available approval status values. You can add new
approval status rows to this table, but you must not remove any of the existing rows.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
approval status index number
index_value
char(20)
approval status description
The approval status rows delivered with EE Raceway are:
362
index_column
index_value
1 - blank
2 - approved
3 - approved
4 - approved
5 - approved
6 - approved
7 - approved
8 - approved
EE Databases
9
9 - approved
10
10 - approved
11
11 - not approved
Cardinal Codelist Table

The cardinal codelist table defines the available cardinal point routing justification locations. You
must not add or remove to this table.
COLUMN_NAME
TYPE
DESCRIPTION
ee_car_num
integer
cardinal index number
ee_cardinal
char(20)
cardinal description
The cardinal point values delivered with EE Raceway are:

ee_car_num
ee_cardina
TOP LEFT
CENTER LEFT
BOTTOM LEFT
TOP CENTER
CENTER CENTER
BOTTOM CENTER
12
TOP RIGHT
13
CENTER RIGHT
14
BOTTOM RIGHT
Drawing Type Codelist Table

The drawing_type codelist table defines the available drawing types. You can add new drawing
types to this table, but you must not remove the existing row.
COLUMN_NAME
TYPE
DESCRIPTION
code
Char(20)
drawing type
unknown
unknown
unknown
The drawing type delivered with EE Raceway is:
code
RACEWAY
Manual Fitting Part Codelist Table

The manual_part codelist table defines the manually-placed special fittings available with the
product. The table contains the index_column column, which is an integer value that the software
uses to uniquely identify an index value. The table also contains the ee_part_table column which
itself contains the mscatalog number of the table holding the part information. The ee_rcp_ol_type
column contains the index_column value for the one-line type to which the RCP is assigned.
363
EE Databases
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
manual_part index number
index_value
char(20)
manual_part description
ee_part_table
integer
special fitting parts table number
ee_rcp_ol_type
integer
one-line type index column number
ee_manpart_type
integer
manual part type index number
The special manual fittings delivered with EE Raceway are:
index_column
index_value
ee_part_table
ee_rcp_ol_type
ee_manpart_type
conduit body
246
pullbox
249
light fixture
250
31
One-Line Type Codelist Table

The ol_type table defines the one-line types that are available in a raceway project. The table
contains the index_column column, which is an integer value the software uses to uniquely
identify an index value. The table also contains the ee_spec, ee_part, ee_ol, and ee_rcp_part
tables which define the tables containing specification information for each one-line type. The
ee_priority_level column defines the routing priority for each one-line type.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
one-line type index number
index_value
char(20)
one-line type description
ee_spec_table
integer
specification table mscatalog number
ee_part_table
integer
spec parts table mscatalog number
ee_ol_table
integer
one-line table mscatalog number
ee_rcp_part_table
integer
special fitting parts table number
ee_max_run_angle
integer
maximum bends allowed per run
ee_priority_level
integer
one-line type nest level
The one-line types delivered with EE Raceway are:
indx_col
index_value
ee_spec
ee_part
ee_ol
rcp_part
run_angle
priority
TRAY
240
241
204
WIREWAY
242
243
204
CONDUIT
244
245
204
246
360
10
AIRWAY
247
248
204
10
DUCTBANK 260
204
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
364
EE Databases
uniquely identify an index value. You must not add or remove rows from this table, nor should you
modify the index_column values. You can modify the index_value values.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
rcp type index number
index_value
char(20)
rcp type description
The RCP types delivered with EE Raceway are:
index_column
index_value
description
<blank>
general raceway connect point
ROUTE
raceway connect point and route point
System Codelist Table

The ee_system table must be loaded in the reference database before you can create any
raceway design files. You can add, remove, or update any of the systems delivered with EE
Raceway. The system table contains the system_num column, which is an integer value the
software uses to uniquely identify a system name.
COLUMN_NAME
TYPE
DESCRIPTION
system_num
integer
system index number
system_name
char(20)
The systems delivered with EE Raceway are:
system_num
system_name
Control
Communication
High Voltage
Low Voltage
Alarm
Instrumentation
Signal
Digital
Analog
10
Thermocouple
11
RTD
12
Medium Voltage
13
Normal Lighting
14
Emergency Lighting
15
Security
16
Fire Safety
system name
365
EE Databases
17
DC Power
18
Control and Signal
Three-Line Type Codelist Table

The tl_type table defines the three-line types that are available with the EE Raceway product. The
table contains the index_column column, which is an integer value the software uses to uniquely
identify an index value. You must not add or remove rows from the table, nor should you modify
the index_column values. You can modify the index_value values.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
three-line type index number
index_value
char(20)
three-line type description
The three-line types delivered with EE Raceway are:

index_column
index_value
STRAIGHT
ELBOW
WYE
CROSS
11
PULLBOX
12
CONDUIT BODY
14
DROPOUT
The index_column = 3 is for branching components (WYEs and TEEs). WYEs and TEEs
cannot go under any number other than 3.
Three_Line Subtype Codelist Table

The tl_subtype table further defines the available three-line types. The table contains the
index_column column, which is an integer value the software uses to uniquely identify an index
value. You must not add or remove rows from the table, nor should you modify the index_column
values. You can modify the index_value values.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
three-line subtype index number
index_value
char(20)
three-line subtype description
The three-line subtypes delivered with EE Raceway are:
366
index_column
index_value
<blank>
VERTICAL
INSIDE VERTICAL
EE Databases
4
OUTSIDE VERTICAL
HORIZONTAL
LEFT HORIZONTAL
RIGHT HORIZONTAL
REDUCER
LEFT REDUCER
10
RIGHT REDUCER
Three-Line Qualifier Codelist Table

The tl_qual table further defines the three-line types. The table contains the index_column
column, which is an integer value the software uses to uniquely identify an index value. You must
not add or remove rows from the table, nor should you modify the index_column values. You can
modify the index_value values.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
three-line qualifier index number
index_value
char(20)
three-line qualifier description
The three-line qualifiers delivered with EE Raceway are:
index_column
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
TYPE
DESCRIPTION
index_column
integer
units index number
index_value
char(20)
The units delivered with EE Raceway are:
index_column
index_value
English
Metric
units description
367
EE Databases
Vendor Codelist Table
You must have a vendor in the vendor codelist table before loading any specification tables in the
database. You can add vendors as necessary to this table, but do not remove the rows delivered
with the product. The vendor table contains the index_column column, which is an integer value
the software uses to uniquely identify a vendor name.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
vendor index number
index_value
char(20)
vendor name
catalog
char(20)
The vendors delivered with EE Raceway are:
catalog
index_column
index_value
catalog
default
delivered blank
sample
delivered blank
unknown
delivered blank
English sample
delivered blank
Wire/Cable Code Codelist Table

This table (ee_pcbl_code) defines the wire/cable code that are used for selecting a Wire/Cable
during the EERWAY command CONDUIT SIZING. The wire/cable code table contains the
index_column column, which is an abbreviated value the software uses to uniquely identify an
index value. You may add or remove rows from this table, the values of the index_column should
include all the wire/cable codes represented in the data of the Wire/Cable (ee_pseudo_cable)
table code column. The index_value provides a more complete description of the entry.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
char(20) not null
wire/cable code index value
index_value
char(20)
The wire/cable codes delivered with EE Raceway are:
368
index_column
index_value
AC
AC
AD
AD
AG
AG
AH
AH
AM
AM
AN
AN
AP
AP
AR
AR
AS
AS
CP
CP
wire/cable code description
EE Databases
index_column
index_value
CQ
CQ
CV
CV
CW
CW
CX
CX
Wire/Cable Configuration Codelist Table

This table (ee_pcbl_config) defines the wire/cable configuration that are used for selecting a
Wire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable configuration table
contains the index_column column, which is an abbreviated value the software uses to uniquely
identify an index value. You may add or remove rows from this table, the values of the
index_column should include all the wire/cable configurations represented in the data of the
Wire/Cable (ee_pseudo_cable) table config column. The index_value provides a more complete
description of the entry.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
char(20) not null
wire/cable configuration index value
index_value
char(20)
wire/cable configuration description
The wire/cable configurations delivered with EE Raceway are:
index_column
index_value
\C
single conductor
PR
"pair 2 conductors
TR
"triad" 3 conductors
Wire/Cable Size Codelist Table

This table (ee_pcbl_size) defines the wire/cable size that are used for selecting a Wire/Cable
during the EERWAY command CONDUIT SIZING. The wire/cable size table contains the
index_column column, which is an abbreviated value the software uses to uniquely identify an
index value. You may add or remove rows from this table, the values of the index_column should
include all the wire/cable sizes represented in the data of the Wire/Cable (ee_pseudo_cable) table
cable_size column. The index_value provides a more complete description of the entry.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
char(20) not null
wire/cable size index value
index_value
char(20)
The wire/cable sizes delivered with EE Raceway are:
index_column
index_value
36 AWG
36 AWG
34 AWG
34 AWG
32 AWG
32 AWG
30 AWG
30 AWG
wire/cable size description
369
EE Databases
370
index_column
index_value
28 AWG
28 AWG
27 AWG
27 AWG
26 AWG
26 AWG
24 AWG
24 AWG
22 AWG
22 AWG
20 AWG
20 AWG
18 AWG
18 AWG
16 AWG
16 AWG
14 AWG
14 AWG
12 AWG
12 AWG
10 AWG
10 AWG
8 AWG
8 AWG
6 AWG
6 AWG
4 AWG
4 AWG
3 AWG
3 AWG
2 AWG
2 AWG
1 AWG
1 AWG
1/0 AWG
1/0 AWG
2/0 AWG
2/0 AWG
3/0 AWG
3/0 AWG
4/0 AWG
4/0 AWG
250 MCM
250 MCM
300 MCM
300 MCM
350 MCM
350 MCM
400 MCM
400 MCM
500 MCM
500 MCM
600 MCM
600 MCM
700 MCM
700 MCM
750 MCM
750 MCM
800 MCM
800 MCM
900 MCM
900 MCM
1000 MCM
1000 MCM
1250 MCM
1250 MCM
1500 MCM
1500 MCM
EE Databases
index_column
index_value
1750 MCM
1750 MCM
2000 MCM
2000 MCM
Wire/Cable Color Codelist Table

This table (ee_pcbl_color) defines the wire/cable insulation color that are used for selecting a
Wire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation color
table contains the index_column column, which is an abbreviated value the software uses to
uniquely identify an index value. You may add or remove rows from this table, the values of the
index_column should include all the wire/cable insulation colors represented in the data of the
Wire/Cable (ee_pseudo_cable) table color column. The index_value provides a more complete
description of the entry.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
char(20) not null
wire/cable insulation color index value
index_value
char(20)
wire/cable insulation color description
The wire/cable insulation colors delivered with EE Raceway are:
index_column
index_value
BLK
BLACK
WHITE
RED
GR
GREEN
ORN
ORANGE
BL
BLUE
W/BLK
WHITE/BLACK
R/BLK
RED/BLACK
GR/BLK
GREEN/BLACK
ORN/BLK
ORANGE/BLACK
BL/BLK
BLUE/BLACK
BLK/W
BLACK/WHITE
R/W
RED/WHITE
GR/W
GREEN/WHITE
BL/W
BLUE/WHITE
BLK/R
BLACK/RED
W/R
WHITE/RED
ORN/R
ORANGE/RED
BL/R
BLUE/RED
R/GR
RED/GREEN
371
EE Databases
372
index_column
index_value
ORN/GR
ORANGE/GREEN
BLK/W/R
BLACK/WHITE/RED
W/BLK/R
WHITE/BLACK/RED
R/BLK/W
RED/BLACK/WHITE
GR/BLK/W
GREEN/BLACK/WHITE
ORN/BLK/W
ORANGE/BLACK/WHITE
BL/BLK/W
BLUE/BLACK/WHITE
BLK/R/GR
BLACK/RED/GREEN
W/R/GR
WHITE/RED/GREEN
R/BLK/GR
RED/BLACK/GREEN
GR/BLK/ORN
GREEN/BLACK/ORANGE
ORN/BLK/GR
ORANGE/BLACK/GREEN
BL/W/ORN
BLUE/WHITE/ORANGE
BLK/W/ORN
BLACK/WHITE/ORANGE
W/R/ORN
WHITE/RED/ORANGE
ORN/W/BL
ORANGE/WHITE/BLUE
W/R/BL
WHITE/RED/BLUE
BLK/W/GR
BLACK/WHITE/GREEN
W/BLK/GR
WHITE/BLACK/GREEN
R/W/GR
RED/WHITE/GREEN
GR/W/BL
GREEN/WHITE/BLUE
ORN/R/GR
ORANGE/RED/GREEN
BL/R/GR
BLUE/RED/GREEN
BLK/W/BL
BLACK/WHITE/BLUE
W/BLK/BL
WHITE/BLACK/BLUE
R/W/BL
RED/WHITE/BLUE
GR/ORN/R
GREEN/ORANGE/RED
GR/R/BL
GREEN/RED/BLUE
BL/R/ORN
BLUE/RED/ORANGE
BLK/ORN/R
BLACK/ORANGE/RED
BRN
BROWN
YELLOW
EE Databases
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.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
char(20) not null
wire/cable insulation voltage rating index

value
index_value
char(40)
wire/cable insulation voltage rating

description
The wire/cable voltage ratings delivered with EE Raceway are:
index_column
index_value
120
Low (Single phase, 2 wire system)
120/240
Low (Single phase, 3 wire system)
208Y/120
Low (Three phase, 4 wire system)
240/120
240
480Y/277
480
600
2400
Medium (Three phase, 3 wire system)
4160Y/2400
4160
4800
6900
8320Y/4800
12000Y/6930
12470Y/7200
13200Y/7620
13200
13800Y/7970
13800
20780Y/12000
22860Y/13200
373
EE Databases
index_column
index_value
23000
24940Y/14400
34500Y/19920
34500
46000
69000
Wire/Cable Insulation Type Codelist Table

This table (ee_pcbl_insul) defines the wire/cable insulation type that are used for selecting a
Wire/Cable during the EERWAY command CONDUIT SIZING. The wire/cable insulation type
table contains the index_column column, which is an abbreviated value the software uses to
uniquely identify an index value. You may add or remove rows from this table, the values of the
index_column should include all the wire/cable insulation types represented in the data of the
Wire/Cable (ee_pseudo_cable) table insulation column. The index_value provides a more
complete description of the entry.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
char(20) not null
wire/cable insulation type index value
index_value
char(100)
wire/cable insulation type description
The wire/cable insulation types delivered with EE Raceway are:
374
index_column
index_value
Asbestos (Without asbestos braid)
AA
Asbestos (With suitable braid material)
AI
Asbestos (Without asbestos braid)
AIA
Impregnated Asbestos (With suitable braid material)
A VA
Impregnated Asbestos & Varnished Cambric
AVB
Impregnated Asbestos & Varnished Cambric (Flame retardant,

cotton braid)
AVL
Impregnated Asbestos & Varnished Cambric (AVL-lead sheath)
FEP
Fluorinated Ethylene Propylene
FEPB
Fluorinated Ethylene Propylene (Glass braid Asbestos or other

Suitable braid material)
MI
Magnesium Oxide (Copper)
MTW
Flame-, Moisture-, Heat- and Oil- Resistant Thermoplastic
PFA
Perfluoroalkoxy
PFAH
Perfluoroalkoxy
RH
Heat-Resistant Rubber (Moisture- resistant, flame- non-metallic

covering)
EE Databases
index_column
index_value
RHH
Heat-Resistant Rubber (Moisture- resistant, flame- non-metallic

covering)
RHW
Moisture- and Heat-Resistant Rubber (Moisture-resistant,

flame-non-metallic covering)
SA
Silicone Rubber (Asbestos, glass or other suitable braid material)
SIS
Heat-Resistant Rubber
TA
Thermo-plastic and Asbestos (Flame- retardant, non-metallic

covering)
TBS
Thermo-plastic (Flame-retardant, non- metallic covering)
TFE
Extruded Polytetra-fluoro-ethylene
THHN
Flame-, Heat-Resistant Thermoplastic (Nylon jacket or equivalent)
THHN/THWN
Flame-, (Moisture-) & Heat-Resistant Thermoplastic (Nylon jacket

or equivalent)
THW
Flame-, Moisture- & Heat-Resistant Thermoplastic
THWN
Flame-, Moisture- & Heat-Resistant Thermoplastic (Nylon jacket

or equivalent)
TW
Flame-Retardant, Moisture- and Heat- Resistant Thermoplastic
UF
Moisture-Resistant, Moisture- and Heat-Resistant (Integral with

insulation)
USE
Heat- and Moisture-Resistant (Moisture-resistant non-metallic

covering)
Varnished Cambric (Nonmetallic covering or lead sheath)
XHHN
Flame-Retardant Cross-Linked Synthetic Polymer
Modified Ethylene Tetrafluoro-ethylene
Yes-No Codelist Table

The ee_yes_no codelist table defines the available positive and negative user responses. You
must not add or remove rows from this table.
COLUMN_NAME
TYPE
DESCRIPTION
index_column
integer
yes-no response index number
index_value
char(20)
The Yes-No values delivered with EE Raceway are:
index_column
index_value
NO
Yes
yes-no response description
375
EE Databases
Fitting Environment Rules
The fitting environment rules are the rules stored in the reference database table tl_fit_env that
control the Place Fitting by Rule commands. The software compares the one-line environment at
an RCP in the design file with the rules stored in this table to determine which fitting to place at the
RCP. You can add, remove, or update any of the rules delivered with EE Raceway. The software,
at least, compares the number of intersection one-lines, the one-line type, and the angles
between the intersectin one-lines with the rules in the fitting environment table to find a match. If
found, the symbol in the part table stored will be placed at the RCP.
COLUMN_NAME
TYPE
DESCRIPTION
ee_ol_type
integer
intersecting one-line's one-line type

number
ee_tl_type
integer
intersecting one-line's three-line type

number, zero if not applicable
ee_tl_subtype
integer
intersecting one-line's three-line

subtype number, zero if not applicable
ee_tl_qual
integer
intersecting one-line's three-line

qualifier number, zero if not applicable
ee_num_ols
integer
number of intersecting one- lines
ee_pln_angles
char(40)
planar angles between the intersecting

one-lines. Angles must be defined
relative to a single one-line.
ee_prp_angles
char(40)
non-planar angles between the

intersecting one-lines. Angles must be
defined relative to a single one-line.
ee_part_table
integer
fitting mscatalog table number
ee_symbol
char(6)
fitting EDEN symbol name
The fitting environment rules delivered with EE Raceway are:
376
olt
tlt
tlst
tlq
nol
pln
prp
tbl
sym
180
246
CC
90
246
CLB
90,180
246
CT
90
90
246
CGUAM
90,180,270
246
CX
90,180
90
246
CGUAW
90,180,270
90
246
CEABY
EE Databases
Intersecting Conduit One-lines

Planar Angles = 90, 180, 270
Non-Planar Angle = 90
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.
Updating Schemas
Before you can update (that is, load with EE tables and default data) a schema, you must create
the schemas using one of the currently-supported RDBMS's (INFORMIX, ORACLE, INGRES).
Additionally, you must use the schema creation form in RIS Schema Manager to create a valid
RIS schema on the database.
377
EE Databases
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.
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
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.
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
378
EE Databases
An existing database schema can also be modified. The SQL statements in the .sql file are the
input to the Update schema process. The table definitions that exist in this file determine how the
tables will look when complete. Therefore, columns can be added or removed from an existing
schema according to the "create table" statements in the .sql file. For example, columns are
added into the .sql file for the one_line table, these columns will be added into the existing rows of
the existing one_line table. When this process finds a "create table" statement for a table that
exists in the schema, the following actions take place:
1. Saves rows from existing table.
2. Drops existing table (also drops indexes).
3. Creates new table according to "create table" statement.
4. Loads new table with saved row information for column names that were in previous
definition.
If rows exist in the updated table, any new columns that are added will be blank in each row.
The new table will have only those columns specified in the "create table" statement in the
table definition. Therefore, you need only to modify the ".sql" file in order to modify a schema.
The following is a list of schema modification rules for Update Schema to keep in mind.
1. You lose any columns and column information that you have not specified in the "create table"
statement. If you had used the RDBMS to alter the table by adding a column and then run
Update schema without making the appropriate change to the ".sql" file, you would lose any
data that may have been on that column.
2. Columns that you added into an existing loaded table would have no data stored in them.
3. Renaming of a column is processed by removing the column and adding another. The
removed column in such a case will lose its data and the added column will be blank.
4. You can modify the size of a column, for example, from "char(10)" to "char(200)" or "smallint"
to "integer", but changing from "char" to "integer" is dangerous and an illegal conversion can
occur. If you modify a character column to make it smaller (resizing char(20) to be char(10),
for example), then any row containing data which exceeds the new character limit will be lost.
5. The .unl file will always be loaded into a table which has a unique index. Any duplicate rows
will be counted and ignored; the unique index prevents the entry of duplicate information when
updating any EE application. If a table does not have a unique index, then the .unl file will be
loaded only if the table is empty.
Table names can be changed except for table names that begin with the letters "ms" and "ee_".
They must also be changed appropriately in the MSCATALOG table in order for the software to
run properly. Keep in mind that the columns within the tables in the reference schema must be a
subset of the columns of the corresponding tables in the project schema.
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 Cautionwhen 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
a. the RDBMS's interactive query product, such as INFORMIX's ISQL or FORMS, or
ORACLE's sqlplus, or INGRES's SQL.
b. the RIS Interactive Query Utility (win32app\ingr\share\ris\bin\risgui.exe).
379
EE Databases
c. DB Access's Database Edit Utility (see the section in the appendix entitled EE Manager
(on page 473) for more information on this utility)
d. the EE Database Utilities (risschema_mgr utility -- win32app\ingr\share\ris\bin\rismgr.exe)
The following steps can be used as a guideline for modifying the reference schema before it is
updated:
1. To see which .unl files are being loaded into the reference database, look at the command
(.cmd) file you will be using. The following is a typical example of what can be contained in this
file:
FILE "olt.unl" DELIMITER "|";
INSERT INTO ol_type;
These lines tell the update schema process that the file "olt.unl" is to be inserted into the
ol_type table. In this case the "olt.unl" file will exist in the current directory but a full path name
can be specified on this file (e.g. FILE win32app\ingr\eerway\db\olt.unl). The delimiter is one
character long. It tells the process that the "|" character separates each column of data in the
olt.unl file.
Do not remove any lines from this file that would effect the current .unl files from being
loaded. All existing .unl files must be loaded for proper product execution.
2. Edit the desired .unl file making sure the delimiter "|" is used between each field. Each line
represents a row to be inserted into the database and each field represents the corresponding
column in the database.
The following is an example of what a line in the "olt.unl" file might look like:
1|TRAY|240|241|204|0|0|1|
In this example, "1" is the index_column value, "TRAY" is the index_value column value, "240"
is the ee_spec_table column, etc. If in the "olt.unl" file you would like to add additional entries,
you can edit this file. Make sure you line up the delimited fields with the tables' columns.
The following example demonstrates how to load a new .unl file containing your own specification
information into the reference database.
1. cd win32app\ingr\eerway\db
2. Edit the command file rwayref.cmd. Insert the following lines into this file:
FILE "catalog.unl" DELIMITER "|";
INSERT INTO tray_spec;
3. Create a new file in the current directory, naming it catalog.unl. Edit this file to include any tray
specification information you want to load into the reference database, separating each
column of data with a pipe symbol (|). For example:
1|1|4|18|18|0|0|12|10|STEEL|A|0418SHV|4x18 VENTRIB SHV|
1|1|4|24|24|0|0|12|10|STEEL|A|0424SHV|4x24 VENTRIB SHV|
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.
380
EE Databases
EE Raceway Reference Database Schema Description

This section lists and describes the tables in the EE Raceway reference database schema, and
includes detailed information about the columns that comprise each table.
An asterisk (*) indicates that you must not modify the column name. You should not modify
those column names having a prefix of "ee_".
approv_status
This codelist table defines the available approval status values: blank, approved, not approved,
and so forth. See the section entitled Codelists earlier in this appendix for a detailed description of
this table.
Column Name
Type
Index
Null
index_column
integer
no
no
index_value
Char(20)
no
yes
index_column: an integer value used by the software to uniquely identify an approved status
description.
index_value: the column that contains the name of each available approved status.
away_part
This table stores the part specification information for the one-line type AIRWAY.
Column Name
Type
Index
Null
ee_tl_type*
integer
no
yes
ee_tl_subtype*
integer
no
yes
ee_tl_qual*
integer
no
yes
ee_angle*
real
no
yes
ee_symbol*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
dups
yes
ee_spec2_key*
Char( 28)
no
yes
ee_part_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
ee_tl_type: the codelisted column used to define the three-line type.
ee_tl_subtype: the codelisted column used to define the three-line subtype.
ee_tl_qual: the codelisted column used to define additional information about the three-line type.
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.
381
EE Databases
ee_description: the description of the default values for each ee_part_key.
away_spec
This table stores the general specification information for the one-line type AIRWAY. EE Raceway
uses airways to reserve space for the routing of cable or other raceway material, and also to
maintain connectivity to a raceway system.
Column Name
Type
Index
Null
ee_units*
integer
no
no
ee_out_ht_diam*
real
dups
no
ee_out_width*
real
no
yes
ee_extension*
real
no
yes
ee_transition*
real
no
yes
ee_radius*
real
no
yes
ee_xs_cell*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
uniq
no
ee_description
Char( 40)
no
yes
ee_units: the codelisted column used to define the units of measurement.

ee_out_ht_diam: the column used to define the airway outside diameter or height to the EE
raceway software.
ee_out_width: the column used to define the airway outside width to the EE raceway software.
ee_extension: the column used to define the airway fitting extension length to the EE raceway
software.
ee_transition: the column used to define the airway fitting transition length to the EE raceway
software.
ee_radius: the column used to define the airway fitting bend radius to the EE raceway software.
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.
382
EE Databases
cardinal
This codelist table defines the available cardinal point locations (top left, center left, bottom left,
and so forth). Refer to the section entitled Codelists earlier in this appendix for a detailed
description of this table.
Column Name
Type
Index
Null
ee_car_num
integer
uniq
no
ee_cardinal
Char( 20)
dups
yes
ee_car_num: an integer value used by the software to uniquely identify a cardinal point
description.
ee_cardinal: the column that contains the name of each available cardinal point.
cond_body
This table stores the specification information for the manual fitting CONDUIT BODY.
Column Name
Type
Index
Null
vendor
integer
dups
no
ee_units*
integer
no
no
nominal_size_1
real
no
yes
nominal_size_2
real
no
yes
weight
real
no
yes
material
Char( 20)
no
yes
ee_part*
Char( 20)
no
yes
ee_symbol*
Char( 6)
no
yes
ee_dimension_1*
real
no
yes
ee_dimension_2*
real
no
yes
ee_dimension_3*
real
no
yes
ee_dimension_4*
real
no
yes
ee_dimension_5*
real
no
yes
ee_dimension_6*
real
no
yes
ee_part_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
ee_tl_type*
integer
no
no
volume
real
no
yes
style
Char( 20)
no
yes
ee_pull_point
integer
no
yes
vendor: the codelisted column used to define the vendor of the conduit body special fitting.
nominal_size_1: the column used to define a conduit body nominal size.
383
EE Databases
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.
raceway reports.
raceway reports.
raceway reports.
raceway reports.
raceway reports.
volume: the column used to define a conduit body volume.
style:the column used to describe the conduit body style or type.
ee_pull_point: the codelisted column used to define the conduit body as a cable pull point.
cond_fill_calc
This table is used to specify the maximum allowable percent fill of a conduit based on the armor
type of the cable outer jackets and number of cables within the conduit. This calculation assumes
a homogeneous mixture of either all LEAD or all NON-LEAD armor types for the cable outer
jackets for the cables routed within the same conduit. If the cables contained in a conduit exceed
the maximum allowable conduit fill, then the conduit is marked as being overfilled.
Column Name
Type
Index
Null
ee_rule_set
Char( 20)
no
yes
ee_jacket_armor
Char( 10)
no
yes
ee_num_cables
integer
no
no
ee_max_fill
real
no
yes
ee_rule_set: identification of the rule set that applies to the raceway system fill calculations, for
example NEC 1990.
ee_jacket_armor: material type of the cable outer jacket armor.
ee_num_cables: number of cables in the conduit.
ee_max_fill: maximum allowable percent fill.
cond_part
This table stores the part specification information for the one-line type CONDUIT.
384
EE Databases
Column Name
Type
Index
Null
ee_tl_type*
integer
no
no
ee_tl_subtype*
integer
no
no
ee_tl_qual*
integer
no
no
ee_angle*
real
no
yes
ee_weight*
real
no
yes
ee_part*
Char( 20)
no
yes
ee_symbol*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
dups
yes
ee_spec2_key*
Char( 28)
no
yes
ee_part_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
ee_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 for reporting.
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
ee_spec2_key: if the current conduit part is a reducer, this column is the key to the row in the
other conduit specification.
cond_spec
This table stores the general specification information for the one-line type CONDUIT.
Column Name
Type
Index
Null
vendor
integer
dups
no
ee_units*
integer
no
no
nominal_size
real
no
yes
ee_dimension_1*
real
no
yes
ee_out_ht_diam*
real
dups
no
ee_extension*
real
no
yes
ee_transition*
real
no
yes
ee_radius*
real
no
yes
weight
real
no
yes
385
EE Databases
Column Name
Type
Index
Null
material
Char( 20)
no
yes
ee_const_type
integer
no
no
ee_xs_cell*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
uniq
no
ee_description
Char( 40)
no
yes
vendor: the codelisted column used to define the vendor of the conduit specification.
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.
ee_xs_cell: the column used to define the conduit cross section graphic that is used during sketch
drawing
This table defines both the columns that you can annotate for title blocks and their default column
values.
386
Column Name
Type
Index
Null
drawing_type*
Char( 20)
no
no
sheet*
Char( 20)
no
yes
ee_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
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
Type
Index
Null
ee_code
Char(20)
uniq
no
code_desc
Char(20)
no
yes
ee_code: the column used by the software to uniquely identify a drawing type description.
code_desc: the column that contains the description of each available drawing type.
drop_point
This table defines both the columns you can annotate for drop point symbols and their default
column values.
Column Name
Type
Index
Null
tag
Char(20)
no
yes
ee_dist_down_ol*
real
no
yes
ee_dist_to_rcp*
real
no
yes
ee_key*
Char(28)
unique
no
ee_description*
Char(40)
no
yes
tag: the column used to define the drop point tag.
ee_dist_down_ol: the column used to define the distance along the one-line to the drop point.
ee_dist_to_rcp: the column used to define the distance between the one-line and the rcp.
duct_spec
This table stores the general specification information for the one-line type DUCTBANK.
Column Name
Type
Index
Null
ee_units
integer
no
no
ee_out_ht_diam
real
dups
no
ee_out_width
real
dups
yes
material
Char( 20)
no
yes
ee_xs_cell
Char( 6)
no
yes
ee_spec_key
Char( 28)
uniq
no
ee_description
Char( 40)
no
yes
387
EE Databases
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.
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_cond_x_area
This table stores the cross sectional area of conduit identified by its nominal size.
Column Name
Type
Index
Null
nominal_size
real
uniq
no
ee_dimension_1
real
no
yes
ee_area
real
no
yes
nominal_size: the column used to define a conduit nominal size that corresponds to the same
column in the cond_spec table.
ee_dimension_1: the column used to define a conduit dimension value that corresponds to the
same column in the cond_spec table.
ee_area: the column used to define the cross sectional area of the conduit of the given nominal
size.
ee_graphic_only
EE applications use this table to define which columns in the project database cannot be posted
back to graphics through the Post Attribute process.
Column Name
Type
Index
Null
table_name
Char( 32)
uniq
yes
column_name
Char( 32)
uniq
yes
table_name: the name of the desired table containing a column that cannot be posted.
column_name: the column within table_name that cannot be posted back to the graphics.
388
EE Databases
ee_pcbl_code
This codelist table defines the codes that are used in the ee_pseudo_cable table for the EERWAY
Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix for a
detailed description of this table.
Column Name
Type
Index
Null
index_column
Char( 20)
uniq
no
index_value
Char( 20)
dups
yes
index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_code
description.
index_value: the column that contains the description of each available ee_pcbl_code.
ee_pcbl_color
This codelist table defines the colors that are used in the ee_pseudo_cable table for the EE
Raceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this appendix
for a detailed description of this table.
Column Name
Type
Index
Null
index_column
Char( 20)
uniq
no
index_value
Char( 20)
dups
yes
index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_color
description.
index_value: the column that contains the description of each available ee_pcbl_color color.
ee_pcbl_config
This codelist table defines the cable configurations that are used in the ee_pseudo_cable table for
the EE Raceway Conduit Sizing command. Refer to the section entitled Codelists earlier in this
appendix for a detailed description of this table.
Column Name
Type
Index
Null
index_column
Char( 20)
uniq
no
index_value
Char( 20)
dups
yes
index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_config
description.
index_value: the column that contains the description of each available ee_pcbl_config.
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
Column Name
Type
Index
Null
index_column
Char( 20)
uniq
no
index_value
Char(100)
dups
yes
389
EE Databases
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
Column Name
Type
Index
Null
index_column
Char( 20)
uniq
no
index_value
Char( 20)
dups
yes
index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_size
description.
index_value: the column that contains the description of each available ee_pcbl_size.
ee_pcbl_volt
This codelisted table defines the cable/wire voltage ratings that are used in the ee_pseudo_cable
table for the EE Raceway Conduit Sizing command.
Column Name
Type
Index
Null
index_column
Char( 20)
uniq
no
index_value
Char( 40)
dups
yes
index_column: an abbreviated value used by the software to uniquely identify an ee_pcbl_volt
description.
index_value: the column that contains the description of each available ee_pcbl_volt.
ee_pseudo_cable
This table defines the cable/wires that are used in the EE Raceway Conduit Sizing command.
Column Name
Type
Index
Null
ee_code
Char( 20)
no
yes
config
Char( 20)
no
yes
cable_size
Char( 20)
no
yes
ee_color
Char( 20)
no
yes
voltage
Char( 20)
no
yes
insulation
Char( 20)
no
yes
item_no
Char( 20)
uniq
yes
ee_area
real
no
yes
ee_units
integer
no
ee_code: the cable code of the cable.
config: the cable configuration of the cable.
cable_size: the size of the wire/cable.
390
no
EE Databases
ee_color: the insulation color of the wire/cable.
voltage: the insulation voltage rating of the wire/cable.
insulation: the insulation type of the wire/cable.
item_no: the unique identifier for each wire/cable.
ee_area: the cross sectional area of the wire/cable.
ee_system
This codelist table defines the systems that are available to contain EE Raceway graphics. Refer
to the section entitled Codelists earlier in the appendix for a detailed description of this table.
Column Name
Type
Index
Null
system_num
integer
uniq
no
system_name
Char( 20)
dups
yes
system_num: an integer value used by the software to uniquely identify a system name.
system_name: the column that contains the name of each available system.
ee_units
This codelist table defines the units that are used for one-line dimension values. Refer to the
section entitled Codelists earlier in the appendix for a detailed description of this table.
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
index_column: an integer value used by the software to uniquely identify an ee_unit description.
index_value: the column that contains the description of each available ee_unit.
ee_unique
EE applications use this table to define which columns make a row in a table unique for single data
entry. If a table is not represented in the ee_unique table, a row will be loaded into the appropriate
table for each graphic element.
Column Name
Type
Index
Null
table_name
Char( 32)
uniq
yes
column_name
Char( 32)
uniq
yes
ee_comp_type*
Char( 10)
uniq
yes
blank_allowed
integer
no
yes
table_name: the name of the table that requires single data entry. Multiple rows in the database
could contain the same table name if multiple columns are required to make an entry unique.
column_name: the name of the column in table_name that makes an entry unique.
ee_comp_type: is used by the EE processors to define what product will use the entry. In some
entries, where the information crosses products, this column is used to further describe what
would make an entry unique.
391
EE Databases
blank_allowed: is used to define whether or not the column in column_name is allowed to be
blank. If not, then a blank column value would cause the EE processes to create a new row in the
database.
ee_yes_no
This codelist table defines the possible column values for a 'yes/no' question in a table column.
Refer to the section entitled Codelists earlier in this appendix for a detailed description of this
table.
Column Name
Type
Index
Null
index_column*
integer
uniq
yes
index_value*
Char( 20)
dups
yes
index_column: an integer value used by the software to uniquely identify the 'yes/no' response.
index_value: the column that contains the 'yes/no' column value.
envelope
This table defines both the columns you can annotate for space envelopes and their default
column values. EE Raceway uses space envelopes to reserve blocks of space for raceway
without maintaining connectivity to any raceway system.
Column Name
Type
Index
Null
tag
Char( 20)
no
yes
ee_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
tag: the column used to define the space envelope tag.
Space envelopes are not available with EE Raceway at the time of this printing.
light_fixture
This table stores the specification information for the manually placed equipment
LIGHT_FIXTURE.
392
Column Name
Type
Index
Null
ee_symbol
Char( 6)
no
yes
voltage
integer
no
yes
ee_dimension_1
real
no
yes
ee_dimension_2
real
no
yes
ee_dimension_3
real
no
yes
ee_part_key
Char( 28)
uniq
no
fl_amps
real
no
yes
ee_dimension_4
real
no
yes
ee_dimension_5
real
no
yes
EE Databases
Column Name
Type
Index
Null
ee_dimension_6
real
no
yes
ee_description
Char( 40)
no
yes
item_type
Char( 3)
no
yes
ee_dimension_7
real
no
yes
ee_dimension_8
real
no
yes
ee_dimension_9
real
no
yes
item_code_num
Char( 20)
no
yes
vendor
integer
dups
no
num_wires
Char( 4)
no
yes
num_phase_wires
integer
no
yes
power_factor
real
no
yes
area_class
Char( 6)
no
yes
oper_temp_deg_c
integer
no
yes
text_1
Char( 32)
no
yes
text_2
Char( 32)
no
yes
text_3
Char( 32)
no
yes
text_4
Char( 32)
no
yes
ee_units
integer
no
no
ee_pull_point
integer
no
yes
ee_symbol: the column used to define the light fixture EDEN symbol name to the EE software.
voltage: the column used to define the light fixture's voltage.
ee_dimension_1: the column used to define a light fixture dimension value to EDEN and the
raceway reports.
raceway reports.
raceway reports.
ee_part_key: the unique key to appropriate reference database record for the default values.
fl_amps: the column used to define a light fixture's full load amps.
raceway reports.
raceway reports.
raceway reports.
ee_description: the description of the default values for each ee_part_key
item_type: the column used to define a light fixture's item type.
393
EE Databases
raceway reports.
raceway reports.
raceway reports.
item_code_num: the column used to define a light fixture's item code number.
vendor: the codelisted column used to define the vendor of the equipment light fixture.
num_wires: the column used to define the number of wires in a light fixture.
num_phase_wires: the column used to define the number of phase wires in a light fixture.
power_factor: the column used to define a light fixture's power factor.
area_class: the column used to define a light fixture's area class.
oper_temp_deg_c: the column used to define a light fixture's operating temperature.
text_1: the column used to describe characteristics about the light fixture.
ee_pull_point: the codelisted column used to define a light fixture as a cable pull point.
manual_part
This codelist table defines the available manually-placed special fittings (conduit body, pullbox).
Refer to the section entitled Codelists earlier in the appendix for a detailed description of this table.
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
ee_part_table*
integer
no
yes
ee_rcp_ol_type*
integer
no
yes
ee_manpart_type
integer
no
yes
index_column: an integer value used by the software to uniquely identify a manual_part
description.
index_value: the column that contains the description of each available manual_part.
ee_part_table: an mscatalog number of the table containing special fitting part specification
information.
ee_rcp_ol_type: the index_column number from the one-line type codelist table for the EE
raceway connect point of the special fitting.
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
394
EE Databases
linked to graphics/EE elements does not need to appear in mscatalog. Both DBAccess and
RISRPT (RIS Report Writer) use this table.
Column Name
Type
Index
Null
tablename
Char( 32)
no
no
entitynum
integer
uniq
no
screenform
Char( 64)
no
yes
reporttable
Char( 64)
no
yes
sqlreview
Char(240)
no
yes
fencefilter
Char(240)
no
yes
dastable
Char(32)
no
yes
alias_name
Char( 64)
no
yes
key_columns
Char( 80)
no
yes
key_description
Char( 32)
no
yes
tablename: the name of the table in the database. It must exactly match the name of the desired
table.
entitynum: the entity number assigned to a table. It must be a positive integer in the range of 1 to
65535. The entity number uniquely identifies a particular table in the database. The MicroStation
32 database interface places the entity number of a table in the linkage it creates between a
graphics element and a table row. EE places the entity number in the EE header linkage of
annotation in order to identify which table the text is linked to.
screenform: not currently used by MicroStation 32.
reporttable: a temporary table used by MicroStation 32. Is is created for each table having
graphic linkages within a fence.
sqlreview: an sql select statement that MicroStation 32 uses to review rows and columns.
fencefilter: an sql select statement that MicroStation 32 uses to restrict elements during fence
operations.
dastable: specifies the name of the table that maps displayable attribute types to the sql select
statements used by MicroStation 32 for loading text into displayable attributes.
alias_name: a column used by EE that contains the descriptive alias of tablename.
key_columns: a column containing the column_name which uniquely identifies a particular row in
the table. EE uses key_columns as the correlation key.
key_description: the descriptive alias for key_columns.
mscodelist
This table provides limited support for DMRS-like codelists. A codelist is a data structure that
represents a character string which is then represented in the database by integer or character
codes. The codelist approach minimizes storage requirements and simplifies database
administration.
MicroStation 32, RISRPT, and DBAccess all support this table. EE uses this table to restrict input
for a particular column to a pre-defined set of values.
Column Name
Type
Index
Null
table_name
Char( 32)
uniq
no
395
EE Databases
Column Name
Type
Index
Null
column_name
Char( 32)
uniq
no
join_table
Char( 32)
no
no
code_column
Char( 32)
no
no
text_column
Char( 32)
no
no
index_column*
Char( 32)
no
yes
index_value*
integer
no
yes
table_name: the name of the desired table containing a column with codelist values.
column_name: the column within table_name which contains codelist values.
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.
Column Name
Type
Index
Null
entitynum
integer
uniq
no
attrnum
integer
uniq
no
column_name
Char( 32)
no
no
alias_name
Char( 32)
no
yes
access_flag
smallint
no
no
work_mode
smallint
no
no
ee_column_order
smallint
no
no
entitynum: the entity number assigned to the table whose columns are being described. Entity
numbers between mscatalog and mscolumns must be consistent.
attrnum: the attribute number assigned to a particular column within a table.
column_name: the name of a column in the database. It must exactly match the column name in
the database.
alias_name: the column containing the descriptive alias of column_name.
access_flag: the column containing a code used to identify the accessibility of a particular column
by an EE user. A value of 0 indicates that the column is read_only, while a value of 1 indicates that
it allows read/write access.
396
EE Databases
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.
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
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
ee_spec_table*
integer
no
yes
ee_part_table*
integer
no
yes
ee_ol_table*
integer
no
yes
ee_rcp_part_table*
integer
no
yes
ee_max_run_angle*
integer
no
yes
ee_priority_level*
integer
no
yes
index_column: an integer value used by the software to uniquely identify an ol_type description.
index_value: the column that contains the description of each available ol_type.
ee_spec_table: an mscatalog number of the table containing general specification information.
ee_part_table: an mscatalog number of the table containing the part specification information.
ee_ol_table: an mscatalog number of the table containing general one-line information.
ee_rcp_part_table: an mscatalog number of the table containing special fitting part specification
information.
ee_max_run_angle: an integer containing the maximum allowed value of the sum of all bend
angles in a run. A value of zero states that the sum of all bend angles in a run is unlimited.
ee_priority_level: an integer value used to define the routing priority level of the one-line type.
This value is used to determine whether one one-line type can break or attach to another one-line
type.
one_line
This table defines both the columns you can annotate for raceway one-lines and their default
column values.
Column Name
Type
Index
Null
tag
Char( 20)
no
yes
add_weight
real
no
yes
ee_ol_length*
real
no
yes
ee_spec_key*
Char( 28)
no
no
ee_key*
Char( 28)
uniq
no
397
EE Databases
Column Name
Type
Index
Null
ee_description*
Char( 40)
no
yes
tag: the column used to define the one-line tag.
add_weight: the column used to define an additional weight per unit length.
ee_ol_length: the column used to define the weight per unit length.
ee_spec_key: the key to the appropriate reference database record for the general specification
information on the three-line elements.
panel
This table defines both the columns you can annotate for panels/equipment and their default
column values.
Column Name
Type
Index
Null
panel
Char( 20)
no
yes
panel_descrip
Char( 20)
no
yes
ee_approv_status
integer
no
yes
ee_approv_date
Char( 40)
no
yes
ee_create_date
Char( 40)
no
yes
ee_last_rev_dat
Char( 40)
no
yes
ee_key
Char( 28)
uniq
no
ee_description
Char( 40)
no
yes
panel: the column which defines the panel/equipment name.
panel_descrip: the column which defines the panel/equipment description.
ee_approv_status: the codelisted column used to define the approval status.
ee_approv_date: the column used to define the date the approval status was changed.
ee_create_date: the column used to define the date the panel/equipment was created.
ee_last_rev_dat: the column used to define the date the panel/equipment was last revised.
ee_description: the description of the default values for each ee_key
project
This table stores information for the project.
398
Column Name
Type
Index
Null
prj_number
char(20)
dups
yes
prj_name
char(60)
no
yes
location
char(60)
no
yes
prj_rule_set
char(20)
no
yes
EE Databases
Column Name
Type
Index
Null
base_rule_set
char(20)
no
yes
ee_key
char(28)
uniq
no
ee_description
char(60)
no
yes
prj_number: this column contains the project number.
prj_name: this column contains the project name.
location: this column contains the location.
prj_rule_set: this column contains the project rule set.
base_rule_set: this column contains the base rule set.
ee_key: this column contains the EE Reference database key.
ee_description:this column contains the key description.
pullbox
This table stores the specification information for the manual fitting PULLBOX.
Column Name
Type
Index
Null
vendor
integer
dups
no
ee_units*
integer
no
no
ee_out_ht_diam*
real
dups
no
ee_out_width*
real
dups
yes
ee_dimension_1
real
dups
yes
weight
real
no
yes
material
char(20)
no
yes
ee_part*
char(20)
no
yes
ee_symbol*
char(6)
no
yes
ee_part_key*
char(28)
uniq
no
ee_description
char(40)
no
yes
ee_tl_type
integer
no
no
ee_pull_point
integer
no
yes
vendor: the codelisted column used to define the pullbox vendor.
ee_units: the codelisted column used to define the untis of measurement.
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.
399
EE Databases
ee_pull_point: the codelisted column used to define a pullbox as a cable pull point.
rcp
This table defines both the columns you can annotate for raceway connect points (RCPs) and
their default column values.
Column Name
Type
Index
Null
tag
Char( 20)
no
yes
ee_rcp_type*
integer
no
yes
ee_extension*
real
no
yes
ee_transition*
real
no
yes
ee_radius*
real
no
yes
ee_part_key*
Char( 28)
no
yes
ee_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
tag: the column used to define the raceway connect point tag.
ee_rcp_type: the codelisted column used to define the raceway connect point type.
ee_extension: the column used to define the raceway connect point fitting extension length.
ee_transition: the column used to define the raceway connect point fitting transition length.
ee_radius: the column used to define the raceway connect point fitting bend radius.
ee_part_key: the key to the appropriate reference database record for the values on the manually
placed fitting.
rcp_type
This codelist table defines additional information about EE Raceway connect points (RCPs). Refer
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
index_column: an integer value used by the software to uniquely identify a rcp_type description.
index_value: the column that contains the description of each available rcp_type.
400
EE Databases
tl_fit_env
This table is used by the manual fitting command to determine which fitting to place at an RCP
based on the intersecting one-lines and the fitting environment rules listed in this table.
Column Name
Type
Index
Null
ee_ol_type
integer
uniq
no
ee_tl_type
integer
no
no
ee_tl_subtype
integer
no
no
ee_tl_qual
integer
no
no
ee_num_ols
integer
uniq
yes
ee_pln_angles
Char( 40)
uniq
yes
ee_prp_angles
Char( 40)
uniq
yes
ee_part_table
integer
no
yes
ee_symbol
Char( 6)
dups
yes
ee_ol_type: the index_column number from the one-line type codelist table of the intersecting
one-lines.
ee_tl_type: the index_column number from the three_line type codelist table of the fitting to be
placed at the RCP. Zero if no check is to be performed.
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.
tl_qual
This codelist table defines additional information about the available three-line types (rigid,
bendable, flexible, and so forth). Refer to the section entitled Codelists earlier in the appendix for a
detailed description of this table.
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
401
EE Databases
index_column: an integer value used by the software to uniquely identify a tl_qual description.
index_value: the column that contains the description of each available tl_qual.
tl_subtype
This codelist table defines the available three-line subtypes (vertical, horizontal, reducer, and so
forth). Refer to the section entitled Codelists earlier in the appendix for a detailed description of
this table.
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
index_column: an integer value used by the software to uniquely identify a tl_subtype
description.
index_value: the column that contains the description of each available tl_subtype.
tl_type
This codelist table defines the available three-line types (straight, elbow, wye, cross, and so forth).
Refer to the section entitled Codelists earlier in the appendix for a detailed description of this table.
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
index_column: an integer value used by the software to uniquely identify a tl_type description.
index_value: the column that contains the description of each available tl_type.
to_equip
This table defines both the columns that you can annotate for equipment pointer symbols and their
default column values.
Column Name
Type
Index
Null
ee_eqp_table
Char( 32)
no
yes
ee_part_key
Char( 28)
no
yes
ee_eqp_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
ee_eqp_table: the name of the reference database table containing the equipment specification
information.
ee_part_key: the key to the appropriate reference database record for the values on the
equipment.
ee_eqp_key: the unique key to the appropriate reference database record for the default values.
to_support
This table defines both the columns you can annotate for support equipment symbols and their
default column values.
402
EE Databases
Column Name
Type
Index
Null
tag
Char( 20)
no
yes
ee_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
tag: the column used to define the support pointer tag.
to_support symbols are not available with EE Raceway at the time of this printing.
tray_part
This table stores the part specification information for the one-line type TRAY.
Column Name
Type
Index
Null
ee_tl_type*
integer
no
no
ee_tl_subtype*
integer
no
no
ee_tl_qual*
integer
no
no
ee_angle*
real
no
yes
ee_weight*
real
no
yes
ee_part*
Char( 20)
no
yes
ee_symbol*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
dups
yes
ee_spec2_key*
Char( 28)
no
yes
ee_part_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
ee_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 for reporting.
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
ee_spec2_key: if the current tray part is a reducer, this column is the key to the row in the other
tray specification.
tray_spec
This table stores the general specification information for the one-line type TRAY.
403
EE Databases
Column Name
Type
Index
Null
vendor
integer
dups
no
ee_units*
integer
no
no
ee_dimension_1*
real
no
yes
ee_out_ht_diam*
real
dups
no
ee_dimension_2*
real
no
yes
ee_out_width*
real
dups
yes
ee_extension*
real
no
yes
ee_transition*
real
no
yes
ee_radius*
real
no
yes
weight
real
no
yes
material
Char( 20)
no
yes
ee_const_type
integer
no
no
ee_xs_cell*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
uniq
no
ee_description
Char( 40)
no
yes
vendor: the codelisted column used to define the vendor of the tray specification.
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.
404
EE Databases
ee_xs_cell: the column used to define the tray cross section graphic that is used during sketch
vendor
This codelist table defines the vendors that are available for specifications. Refer to the section
entitled Codelists earlier in the appendix for a detailed description of this table.
Column Name
Type
Index
Null
index_column*
integer
uniq
no
index_value*
Char( 20)
dups
yes
catalog
char(20)
no
yes
index_column: an integer value used by the software to uniquely identify a vendor name.
index_value: the column that contains the name of each available vendor.
catalog: the column that contains catalog information.
wway_part
This table stores the part specification information for the one-line type WIREWAY.
Column Name
Type
Index
Null
ee_tl_type*
integer
no
yes
ee_tl_subtype*
integer
no
yes
ee_tl_qual*
integer
no
yes
ee_angle*
real
no
yes
ee_weight*
real
no
yes
ee_part*
Char( 20)
no
yes
ee_symbol*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
dups
yes
ee_spec2_key*
Char( 28)
no
yes
ee_part_key*
Char( 28)
uniq
no
ee_description*
Char( 40)
no
yes
405
EE Databases
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 for reporting.
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
ee_spec2_key: if the current wireway part is a reducer, this column is the key to the row in the
other wireway specification.
wway_spec
This table stores the general specification information for the one-line type WIREWAY.
Column Name
Type
Index
Null
vendor
integer
dups
no
ee_units*
integer
no
no
ee_dimension_1*
real
no
yes
ee_out_ht_diam*
real
dups
no
ee_dimension_2*
real
no
yes
ee_out_width*
real
dups
yes
ee_extension*
real
no
yes
ee_transition*
real
no
yes
ee_radius*
real
no
yes
weight
real
no
yes
material
Char( 20)
no
yes
ee_const_type
integer
no
no
ee_xs_cell*
Char( 6)
no
yes
ee_spec_key*
Char( 28)
uniq
no
ee_description
Char( 40)
no
yes
vendor: the codelisted column used to define the vendor of the wireway specification.
ee_dimension_1: the column used to define a wireway dimension value to eden and the raceway
reports.
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.
406
EE Databases
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_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 Raceway Project Database Schema Description

This section lists and describes the tables in the EE Raceway project database schema, and
includes detailed information about the columns that comprise each table.
An asterisk (*) indicates that you must not modify the column name. You should not modify
those column names having a prefix of "ee_".
cabsch_spec
This table contains information about the cable schedule for underground cable design.
Column Name
Type
Index
Null
revision_numb
Char( 3)
no
yes
cable_numb
Char( 8)
uniq
yes
numb_cables
integer
no
yes
numb_conductor
Char( 5)
no
yes
conductor_size
Char( 8)
no
yes
cable_type_code
Char( 6)
no
yes
service_voltage
Char( 7)
no
yes
undgrnd_length
real
no
yes
abvgrnd_length
real
no
yes
from_equi_numb
Char( 15)
no
yes
from_detail
Char( 8)
no
yes
407
EE Databases
Column Name
Type
Index
Null
not_used
Char( 6)
no
yes
plan_assem_dwg
Char( 20)
no
yes
to_equi_numb
Char( 15)
no
yes
to_detail
Char( 8)
no
yes
to_plan_drw_num
Char( 20)
no
yes
cont_sta_type
Char( 4)
no
yes
quan_term_kits
Char( 6)
no
yes
ol_diagram_numb
Char( 20)
no
yes
not_used2
Char( 8)
no
yes
remarks
Char( 38)
no
yes
drawing_numb
Char( 20)
uniq
yes
drawing_rev
Char( 2)
no
yes
revision_numb: the column containing the revision number.
cable_numb: the column containing the area number, cable number, and cable number ID.
numb_cables: the column containing the number of cables.
numb_conductor: the column containing the number of conductors.
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.
408
EE Databases
cndsch_spec
This table contains information about conduit schedule for underground conduit design.
Column Name
Type
Index
Null
revision_numb
Char( 2)
no
yes
conduit_numb
Char( 10)
uniq
yes
conduit_for
Char( 12)
no
yes
cnd_from_where
Char( 20)
no
yes
cnd_to_where
Char( 20)
no
yes
undgrnd_cnd_size
Char( 6)
no
yes
undgrnd_cnd_type
Char( 5)
no
yes
undgrnd_cnd_length
real
no
yes
abvgrnd_cnd_size
Char( 6)
no
yes
abvgrnd_cnd_type
Char( 4)
no
yes
abvgrnd_cnd_length
real
no
yes
cnd_detail_numb
Char( 7)
no
yes
detail_drw_numb
Char( 12)
no
yes
cnd_ac_dimension
Char( 12)
no
yes
cnd_station
Char( 6)
no
yes
pow_conduct_volt
Char( 5)
no
yes
pow_conduct_numb
integer
no
yes
pow_conduct_size
Char( 7)
no
yes
pow_conduct_type
Char( 4)
no
yes
pow_conduct_length
real
no
yes
con_conduct_numb
integer
no
yes
con_conduct_size
Char( 7)
no
yes
con_conduct_type
Char( 4)
no
yes
con_conduct_length
real
no
yes
grnd_wire_size
Char( 6)
no
yes
grnd_wire_type
Char( 4)
no
yes
grnd_wire_length
real
no
yes
ol_diagram_numb
Char( 10)
no
yes
remarks
Char( 16)
no
yes
drawing_numb
Char( 20)
uniq
yes
drawing_rev
Char( 2)
no
yes
revision_numb: the column containing the conduit schedule revision number.
409
EE Databases
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.
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.
drawing_rev: the column containing the drawing revision.
drawing
This table, used by all EE products, contains general information about each EE design file.
410
Column Name
Type
Index
Null
mslink*
integer
uniq
no
drawing_type*
Char( 20)
no
no
ee_filename*
Char( 80)
no
no
sheet*
Char( 20)
uniq
no
EE Databases
Column Name
Type
Index
Null
load_date*
Char( 26)
no
no
ref_db*
Char( 80)
no
no
mslink: a unique integer value used by the software to identify a row in the drawing table.
drawing_type: the column used to define the type of EE drawing.
ee_filename: the column containing the drawing file name and path.
sheet: the column used to contain the drawing sheet name.
load_date: the column containing the date that the load processor loaded the drawing into the
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
Type
Index
Null
mslink*
integer
uniq
no
ee_to_drw*
integer
no
no
ee_to_ol*
integer
dups
yes
ee_to_rcp*
integer
dups
yes
ee_dist_down_ol*
real
no
yes
ee_dist_to_rcp*
real
no
yes
tag
Char( 20)
no
yes
mslink: a unique integer value used by the software to identify a row in the drop_point table.
ee_to_drw: the column containing the mslink of a row in the drawing table.
ee_to_ol: the column containing the mslink of a row in the one_line table.
ee_to_rcp: the column containing the mslink of a row in the rcp table.
ee_dist_down_ol: the column containing the distance along the one-line to the drop point.
ee_dist_to_rcp: the column containing the distance between the one-line and the rcp.
tag: the column that contains the name of the drop point.
duct_fill
This table defines the cable/conduit that are placed in a duct one-line.
Column Name
Type
Index
Null
ee_to_ol
integer
dups
yes
ee_to_drw
integer
dups
yes
ee_duct_cc_row
integer
no
yes
ee_duct_cc_col
integer
no
yes
ee_duct_cc_numb
Char( 12)
no
yes
ee_drawing_numb
Char( 20)
no
yes
411
EE Databases
ee_to_ol: the column containing the mslink of a row in the one-line table.
ee_duct_cc_row: the row index of the conduit/cable.
ee_duct_cc_col: the column index of the conduit/cable.
ee_duct_cc_numb: cable/conduit area number, cable number, and cable number number ID.
ee_drawing_numb: detail drawing number of the conduit/cable schedule.
ee_pseudo_cable
This table defines the wires/cables that fill conduit. This is performed with the EE Raceway
Conduit Sizing command.
Column Name
Type
Index
Null
mslink
integer
uniq
no
ee_to_ol
integer
no
no
ee_to_drw
integer
no
no
ee_quantity
integer
no
yes
item_no
Char( 20)
dups
yes
mslink: a unique integer value used by the software to identify a row in the ee_pseudo_cable
table.
ee_quantity: the number of wires/cables associated with the given one-line of a given item_no.
item_no: the column containing the unique key to the ee_pseudo_cable table of the reference
schema.
ee_system
This table contains the names of all systems from every EE Raceway drawing loaded into the
project database.
Column Name
Type
Index
Null
mslink*
integer
uniq
no
system_name
Char( 20)
dups
yes
mslink: a unique integer value used by the software to identify a row in the ee_system table.
system_name: the column that contains the names of the systems.
envelope
This table contains information about the raceway envelopes found in the drawing.
Column Name
Type
Index
Null
mslink*
integer
uniq
no
ee_to_drw*
integer
no
no
tag
Char( 20)
dups
yes
mslink: a unique integer value used by the software to identify a row in the envelope table.
412
EE Databases
tag: the column that contains the envelope tag.
Space envelopes are not available at time of printing.
fitting
This table contains information about the raceway fittings found in the drawing.
Column Name
Type
Index
Null
mslink*
integer
uniq
no
ee_to_drw*
integer
no
no
ee_to_ol*
integer
dups
yes
ee_to_rcp*
integer
dups
yes
ee_out_ht_diam*
real
no
yes
ee_out_width*
real
no
yes
ee_out_width2
real
no
yes
ee_dimension_1*
real
no
yes
ee_angle*
real
no
yes
ee_weight*
real
no
yes
cab_weight
real
no
yes
pds_east*
real
no
yes
pds_north*
real
no
yes
pds_elev*
real
no
yes
vendor
Char( 20)
no
yes
ee_units*
Char( 20)
no
yes
ee_tl_type*
Char( 20)
no
yes
ee_tl_subtype*
Char( 20)
no
yes
ee_tl_qual*
Char( 20)
no
yes
ee_ol_type*
Char( 20)
no
yes
ee_part*
Char( 20)
dups
yes
ee_description
Char( 40)
no
yes
mslink: a unique integer value used by the software to identify a row in the fitting 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.
413
EE Databases
ee_angle: the column containing the fitting bend angle.
ee_weight: the column containing the fitting weight per unit length.
cab_weight: the column containing the cable weight per unit length.
pds_east: the column containing the PDS east coordinate of the fitting (calculated by Load
Database).
pds_north: the column containing the PDS north coordinate of the fitting (calculated by 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.
fit_to_sys
This table links a fitting to each system of which it is a member.
Column Name
Type
Index
Null
ee_to_fit*
integer
dups
no
ee_to_sys*
integer
dups
no
ee_percent*
real
no
yes
ee_to_fit: the column containing the mslink of a row in the fitting table.
ee_to_sys: the column containing the mslink of a row in the ee_system table.
ee_percent: the column containing the percent amount of the fitting is contained in the system
identified by the mslink stored in ee_to_sys.
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.
414
Column Name
Type
Index
Null
tablename
Char( 32)
no
no
entitynum
integer
uniq
no
screenform
Char( 64)
no
yes
reporttable
Char( 64)
no
yes
sqlreview
Char(240)
no
yes
fencefilter
Char(240)
no
yes
dastable
Char(32)
no
yes
EE Databases
Column Name
Type
Index
Null
alias_name
Char(32)
no
yes
key_columns
Char( 80)
no
yes
key_description
Char( 32)
no
yes
tablename: the name of the table in the database. It must exactly match the name of the desired
table.
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.
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
Type
Index
Null
entitynum
uniq
uniq
no
attrnum
integer
uniq
no
column_name
Char( 32)
no
no
alias_name
Char( 64)
no
yes
access_flag
smallint
no
no
work_mode
smallint
no
no
ee_column_order*
smallint
no
no
entitynum: the entity number assigned to the table whose columns are being described. Entity
numbers between mscatalog and mscolumns must be consistent.
attrnum: the attribute number assigned to a particular column within a table.
column_name: the name of a column in the database. It must exactly match the column name in
the database.
alias_name: the column containing the descriptive alias of column_name.
access_flag: the column containing a code used to identify the accessibility of a particular column
by an EE user. A value of 0 indicates that the column is read_only, while a value of 1 indicates that
it allows read/write access.
415
EE Databases
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.
ol_to_sys
This table links a one-line to each system of which it is a member.
Column Name
Type
Index
Null
ee_to_ol*
integer
dups
no
ee_to_sys*
integer
dups
no
ee_percent*
real
no
yes
prj_rule_applied
integer
no
yes
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.
416
Column Name
Type
Index
Null
mslink*
integer
uniq
no
ee_to_drw*
integer
no
no
ee_to_rcp1*
integer
dups
no
ee_to_rcp2*
integer
dups
no
ee_out_ht_diam*
real
no
yes
ee_out_width*
real
no
yes
ee_dimension_1*
real
no
yes
ee_dimension_2*
real
no
yes
ee_ol_length*
real
no
yes
weight
real
no
yes
cab_weight
real
no
yes
vendor
Char( 20)
dups
yes
ee_units*
Char( 20)
no
yes
ee_ol_type*
Char( 20)
no
yes
ee_spec_key*
Char( 28)
dups
yes
EE Databases
Column Name
Type
Index
Null
tag
Char( 20)
dups
yes
ee_radius
real
no
yes
ee_const_type
char
no
yes
mslink: a unique integer value used by the software to identify a row in the one_line table.
ee_to_rcp1: the column containing the mslink of the rcp placed at the start of the one-line in the
design file.
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.
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.
panel
This table contains information about all panels/equipment found in the drawing.
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
Type
Index
Null
mslink
integer
uniq
no
panel
Char( 20)
dups
yes
panel_descrip
Char( 20)
no
yes
ee_approv_status
integer
no
yes
ee_approv_date
Char( 26)
no
yes
ee_create_date
Char( 26)
no
yes
ee_last_rev_dat
Char( 26)
no
yes
417
EE Databases
Column Name
Type
Index
Null
ee_eqp_table
Char( 32)
no
yes
ee_part_key
Char( 28)
no
yes
pds_east
real
no
yes
pds_north
real
no
yes
pds_elev
real
no
yes
mslink: a unique integer value used by the software to identify a row in the panel table.
panel: the column containing the panel/equipment name
panel_descrip: the column containing the panel/equipment description.
ee_approv_status: the column containing the approval status of the panel/equipment.
ee_approv_date: the column containing the date when the approval status changed.
ee_create_date: the column containing the panel/equipment creation date.
ee_last_rev_dat: the column containing the date the panel/equipment was last revised.
ee_eqp_table: the column containing the name of the reference database table that contains
additional equipment information.
ee_part_key: the column containing the unique key to the appropriate record of equipment
information in the reference database table.
pds_east: the column containing the PDS east coordinate of the panel (calculated by Load
Database).
pds_north: the column containing the PDS north coordinate of the panel (calculated by Load
Database).
pds_elev: the column containing the PDS elevation coordinate of the panel (calculated by Load
Database).
project
This table contains specification information for the project.
Column Name
Type
Index
Null
mslink
integer
uniq
no
prj_number
Char( 20)
uniq
yes
prj_name
Char( 40)
uniq
no
location
Char( 60)
no
no
prj_rule_set
Char( 20)
no
no
base_rule_set
Char( 20)
no
yes
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.
418
EE Databases
panel_to_drw
This table links a panel/equipment to each drawing in which it exists.
Column Name
Type
Index
Null
ee_to_panel
integer
dups
no
ee_asid
integer
no
no
ee_to_drw
integer
dups
no
ee_to_rcp
integer
dups
yes
ee_status
integer
no
no
ee_to_panel: the column containing the mslink of a row in the panel table.
ee_asid: the column containing the asid number of the panel/equipment element in the design file
identified by the mslink stored in ee_to_drw.
ee_to_rcp: the column containing the mslink of a row in the RCP table.
ee_status: the column containing the revision status of the panel element in the design file (used
by the Load Database process).
rcp
This table contains information about all raceway connect points (RCPs) found in the drawing.
Column Name
Type
Index
Null
mslink*
integer
uniq
no
ee_rcp_type*
Char( 10)
no
yes
tag
Char( 20)
no
yes
ee_radius
real
no
no
mslink: a unique integer value used by the software to identify a row in the rcp table.
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
Type
Index
Null
ee_to_rcp*
integer
dups
no
ee_asid*
integer
no
no
ee_to_drw*
integer
dups
no
pds_east*
real
no
yes
pds_north*
real
no
yes
pds_elev*
real
no
yes
419
EE Databases
ee_asid: the column containing the asid number of the rcp element in the drawing identified by the
mslink stored in ee_to_drw.
pds_east: the column containing the PDS east coordinate of the rcp (calculated by Load
Database).
pds_north: the column containing the PDS north coordinate of the rcp (calculated by 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
Type
Index
Null
ee_to_rcp*
integer
dups
no
ee_to_sys*
integer
dups
no
ee_percent*
real
no
yes
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.
straight
This table contains information about the raceway straight sections found in the drawing.
420
Column Name
Type
Index
Null
mslink*
integer
uniq
no
ee_to_drw*
integer
no
no
ee_to_ol*
integer
dups
no
ee_out_ht_diam*
real
no
yes
ee_out_width*
real
no
yes
ee_tl_length*
real
no
yes
ee_dimension_1*
real
no
yes
ee_dimension_2*
real
no
yes
ee_weight*
real
no
yes
cab_weight
real
no
yes
pds_east*
real
no
yes
pds_north*
real
no
yes
pds_elev*
real
no
yes
vendor
Char( 20)
dups
yes
ee_units*
Char( 20)
no
yes
EE Databases
Column Name
Type
Index
Null
ee_ol_type*
Char( 20)
no
yes
ee_spec_key*
Char( 28)
dups
yes
ee_part*
Char( 20)
no
yes
material
Char( 20)
no
yes
ee_description
Char( 40)
no
yes
mslink: a unique integer value used by the software to identify a row in the straight table.
ee_out_ht_diam: the column containing the outside height or diameter of the straight section.
ee_out_width: the column containing the outside width of the straight section.
ee_tl_length: the column containing the length of the straight section.
ee_dimension_1: the column containing a dimension of the straight section.
ee_dimension_2: the column containing a dimension of the straight section.
ee_weight: the column containing the straight section weight per unit length.
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).
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
Type
Index
Null
ee_to_str*
integer
dups
no
ee_to_sys*
integer
dups
no
ee_percent*
real
no
yes
ee_to_str: the column containing the mslink of a row in the straight table.
ee_percent: the column containing the percent amount of the straight section is contained in the
system identified by the mslink stored in ee_to_sys.
421
EE Databases
sys_to_drw
This table links a system name to each drawing in which the system exists.
Column Name
Type
Index
Null
ee_to_sys*
integer
dups
no
ee_asid*
integer
no
no
ee_to_drw*
integer
dups
no
ee_asid: the column containing the asid number of the system element in the drawing identified
by the mslink stored in ee_to_drw.
to_support
This table links the raceway one-line with a support.
Column Name
Type
Index
Null
mslink*
integer
uniq
no
ee_to_drw*
integer
no
no
ee_to_ol*
integer
no
no
ee_ol_coord*
real
no
yes
tag
Char( 20)
dups
yes
mslink: a unique integer value used by the software to identify a row in the to_support table.
ee_ol_coord: the column containing the distance along the one-line to the support.
tag: the column that contains the support tag.
to_support symbols are not available at time of printing.
422
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.
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):
423
Specification
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.
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|85|0|600|0|0|600|0|HOT DIP STEEL|A|6060SV|VENTRIB SV C1
2|1|0|50|0|600|0|0|600|0|ALUMINUM|A|6060AHV|VENTRIB AHV A
tray_part.unl
424
Specification
2|2|5|90|0|A-15VA|VEL|1530AS| |A-15VA|Vertical Adjustable Elbow
2|2|5|90|0|AD-15VA|VEL|1530ADS| |AD-15VA|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 (on
page 40) 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
Description
vendor*
the index_column (codelist) value from the vendor table.
ee_units*
the index_column (codelist) value from the ee_units table.
ee_dimension_1
a dimension variable used by Eden.
ee_out_ht_diam
the outside height dimension in sub-units.
ee_dimension_2
a dimension variable used by Eden.
ee_out_width
the outside width dimension in subunits.
ee_extension
the fitting extension.
ee_transition
the fitting transition length.
ee_radius
the fitting bend radius.
weight
the weight per unit length of the run.
material
the tray material.
425
Specification
Column Name
Description
ee_const_type
the construction type.
ee_xs_cell
the cross section symbol.
ee_spec_key
the unique tray specification key.
ee_description
the tray specification description.
tray_part table
Column Name
Description
ee_tl_type*
the index_column value from the tl_type table.
ee_tl_subtype*
the index_column value from the tl_subtype table.
ee_tl_qual*
the index_column value from the tl_qual table.
ee_angle
the fitting turn angle.
ee_weight
the tray part weight.
ee_part
the tray part catalog number.
ee_symbol
the Eden symbol.
ee_spec_key
the tray specification key.
ee_spec2_key
the secondary tray specification key for reducers.
ee_key
the unique tray part key.
ee_description
the tray part description.
* For information about the codelist values, see the appendix entitled EE Databases (on page
359).
Available Fittings
The following is a list of the fittings currently supported by the EE Raceway Modeling product:
426
FITTING
TYPE
ANGLE
Straight Elbow
Horizontal
30,45,60,90, and Adjustable
Elbow
InsideVertical
Elbow
Outside Vertical
Wye
Horizontal
90,45 left and 45 right
Wye
Vertical
90
Wye
Reducer
90
Cross
Horizontal
90
Cross
Vertical
90
Reducer
Left Horizontal
Reducer
Right Horizontal
Reducer
Concentric
Specification
FITTING
TYPE
ANGLE
Conduit body
Pullbox
427
Specification
428
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 (on page 301) 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
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.
!
429

angle
= DIMENSION[4]
height = DIMENSION[21]
halfwid = DIMENSION[22] / 2.0
extension = DIMENSION[23]
radius = DIMENSION[25]
ORG = 19
BND1 = 20
BND2 = 21
EXT1 = 22
EXT2 = 23
ARC = 24
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 = bendpoint on primary oneline
!
val2 = primary distance to bendpoint on bent oneline
!
val3 = secondary distance to bendpoint on bent oneline
!
val4 = extension point on primary oneline
!
val5 = primary distance to extpoint on bent oneline
!
val6 = secondary distance to extpoint on bent oneline
!
radius = radius + halfwid
val1 = radius * DTAND( angle / 2.0 )
val2 = val1 * DSIND( angle )
val3 = val1 * DCOSD( angle )
val4 = val1 + extension
val5 = val4 * DSIND( angle )
val6 = val4 * DCOSD( angle )
!
!
Define bendpoints (point2 and point3) and bend origin (point4)
!
Call Define_Datum_Point( DP[1], Point[0] )
Call Define_Point ( Point[ORG], Point[0],
0,
0, 0, 0 )
Call Define_Point ( Point[BND1], Point[0], -val1,
0, 0, 0 )
Call Define_Point ( Point[BND2], Point[0], val3, val2, 0, 0 )
Call Define_Point ( Point[EXT1], Point[0], -val4,
0, 0, 0 )
Call Define_Point ( Point[EXT2], Point[0], val6, val5, 0, 0 )
Call Define_Point ( Point[ARC], Point[0], -val1, radius, 0, 0 )
!
!
Define Placepoints
!
430

Call Define_Active_Point ( Point[EXT2] )
Call Define_Orientation_By_Points ( Point[ORG], Point[BND2],
Point[ARC] )
Call Rotate_Orientation( 180.0, NORMAL )
Call Define_Placepoint ( PP2, Point[0] )
Call Define_Active_Point ( Point[EXT1] )
Call Define_Orientation_By_Points ( Point[BND1], Point[ORG],
Point[BND2] )
Call Define_Placepoint ( PP1, Point[0] )
!
!
Define cross section points
!
Call Define_Active_Point ( Point[BND1] )
Call Define_Point (Point[1], Point[0], 0, halfwid, height, 0 )
Call Define_Point (Point[2], Point[0], 0, halfwid, 0, 0 )
Call Define_Point (Point[3], Point[0], 0, -halfwid, 0, 0 )
Call Define_Point (Point[4], Point[0], 0, -halfwid, height, 0 )
!
!
Draw First Extension
!
If ( extension .ne. 0 ) 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
Endif
!
!
Draw revolved shape
!
Call Define_Orientation_By_Points(Point[1],Point[2],Point[3])
Call Define_Active_Point ( Point[ARC] )
Call Draw_Revolved_Shape ( EL_LINESTR, -angle, 1, Point[1], NUMPTS,
0 )
!
!
Draw Second Extension
!
If ( extension .ne. 0 ) then
Call Define_Active_Point ( Point[BND2] )
Call
Define_Orientation_By_Points(Point[ORG],Point[BND2],Point[ARC])
Call Define_Point (Point[1], Point[0], 0, halfwid, height, 0 )
Call Define_Point (Point[2], Point[0], 0, halfwid, 0, 0 )
Call Define_Point (Point[3], Point[0], 0, -halfwid, 0, 0 )
Call Define_Point (Point[4], Point[0], 0, -halfwid, height, 0 )
431

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] )
Do i = 1, NUMPTS, 1
Call Draw_Line ( Point[i], Point[NUMPTS+i] )
Enddo
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 (see "Databases" on page 95) chapter.
The symbol in the example defines the symbol name as 'HEL,' and includes a description of the
symbol, 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.
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:
432
Dimension
What
From
Three Line Type
Manual Placement Form or Calculated

Dimension
What
From
Three Line Subtype
Three Line Qualifier
Angle
11
Length
These are from the specification table:

21
Height
Spec Table - ee_out_ht_diam
22
Width
Spec Table - ee_out_wid
23
Extension
Spec Table - ee_extension
24
Transition
Spec Table - ee_transition
25
Radius
Spec Table - ee_radius
26
Dimension 1
Spec Table - ee_dimension_1
27
Dimension 2
..
...........
..........
..
...........
..........
..
...........
..........
50
Dimension 25
These are from the secondary specification (if one exists):

51
Height_2
Spec Table - ee_out_ht_diam
52
Width_2
Spec Table - ee_out_wid
53
Extension_2
Spec Table - ee_extension
54
Transition_2
Spec Table - ee_transition
55
Radius_2
Spec Table - ee_radius
56
Dimension 1
433

Dimension
What
From
57
Dimension 2
..
...........
..........
..
...........
..........
..
...........
..........
80
Dimension 25
The following structure is used for special parts:
434
Dimension
What
From
26
Dimension 1
Part Table - ee_dimension_1
27
Dimension 2
..
...........
..........
..
...........
..........
..
...........
..........
80
Dimension 60
APPENDIX F
EE 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.
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:
Any file followed by a slash (name/) is a directory. Any file followed by an asterisk (*)
is an executable.
435
EE File Structure
\eenuc:
\eenuc\bin:
\eenuc\data:
\eenuc\db:
\eenuc\doc:
\eenuc\font
\eenuc\forms:
\eenuc\help
\eenuc\msg:
\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, 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.
436
EE File Structure
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.
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.
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:
437
EE File Structure
/usr/ip32/eerway/config:
/usr/ip32/eerway/data:
/usr/ip32/eerway/db:
/usr/ip32/eerway/dgn:
/usr/ip32/eerway/dgn/seed:
/usr/ip32/eerway/doc:
/usr/ip32/eerway/eden:
/usr/ip32/eerway/help_source:
/usr/ip32/eerway/help_source/help_graphics:
/usr/ip32/eerway/mdlapps:
438
EE File Structure
/usr/ip32/eerway/menus:
/usr/ip32/eerway/msg:
/usr/ip32/eerway/report:
/usr/ip32/eerway/sym:
\win32app\ingr\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.
eden.dat controls Eden processes.
process.dat controls process management.
report.dat controls standard report management.
rule_chk.dat controls rule check report management.
439
EE File Structure
440
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.
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.
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.
EE File Structure
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.
441
EE File Structure
442
APPENDIX G
Customizing Environment Files

This appendix contains printouts of the following files as they are delivered with EE Raceway:
File
Location
eden.dat
win32app\ingr\eerway\data
process.dat
report.dat
rule_chk.dat
print.dat
win32app\ingr\eenuc\data
manager.dat
win32app\ingr\eenuc\data
process.dat, report.dat, rule_chk.dat, and print.dat control the scrolling lists for the Process,
Report, Rule, and Output menus, respectively. You may want to write your own processes, reports
or 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.
To view the following files in Help, you may need to resize the Help window.
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.
443

# 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,,
#
#
#
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 \
#
#
#Create Parameteric Help Library | %EE_RWAY%\bin\eden.bat -C \
#
#
#
#
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 \
#
#
n
#
\
Extract EDEN Symbol From Library|d%EE_RWAY%\bin\eden.bat -e \
| Enter library name ,%EDeN_LIB%,, \
| Enter symbol name ,,, n
#
.
#
b
Extract EDEN User Function From Labrary| %EE_RWAY%\bin\eden.bat -eu \
| Enter library name ,%EDtN_LIB%,, \
| Enter symbol name ,,,
#
#
E
444

Edit EDEN Symbol File | %EE_RWAY%
name,,,
#
#
E
e
tor,notepad,,
| Enter symbol file
process.dat
#ident "@(#)data:process.dat 13.1 0.0 (EE Raceway) 12/14/93"
#
#
# process.dat
# This file is stored under the %EE_SCH%\data directory.
#
#
#
#
#
#
# The third field and each subsequent field will contain three sub-fields
#
# They are :
#
Prompt,Default,Path,Switch
# 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
#
445

#
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
report.dat
#ident "@(#)data:report.dat 7.1 0.0 (EE Raceway) 6/1/92"
#
#
# report.dat
# The syntax of this data file :
# Title | Command Line | Report Name | Prompt,Default | , , ...
#
# The second field is the command field.
# The third field is the name of the report which can be a global symbol
# or a file name.
# The fourth field and each subsequent field will contain two sub-fields
# using the comma (,) as the delimeter.
#
# They are:
#
Prompt,Default
# Any of the sub_fields in the third field can be omitted.
#
#
Project drawing list | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB%
%EE_RWAY%\report\rwaydba_lib
%EE_RPTDB% dummy \
| drwlst \
| Enter project schema,%EE_SCHEMA%
#
#
Material takeoff report | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM% %EE_RPTDB%
%EE_RWAY%\report\rwaydba_lib
%EE_RPTDB% dummy \
| mto_rpt \
#
446

#
Raceway bill of materials report| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM%
%EE_RPTDB%
%EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \
| rway_bom \
#
#
Raceway bill of materials by volume| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM%
%EE_RPTDB% %EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \
| rway_bom_v \
| Enter project schema,%EE_SCHEMA% \
| Enter low range (PDS coordinates: east north elev) \
| Enter high range (PDS coordinates: east north elev)
#
#
Raceway Conduit Body report| %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM%
%EE_RPTDB% %EE_RWAY%\report\rwaydba_lib
dummy %EE_RPTDB% \
| cond_body \
| Enter Reference schema,%EES_REFDB%
#
#
rule_chk.dat
#ident "@(#)data:rule_chk.dat 13.1 0.0 (EE Raceway) 12/14/93"
#
#
# rule_chk.dat
# Title | Command Line | Report Name | Prompt, Default | , , ...
#
# The second field is the command field.
# The third field is the report name which can be a global symbol or file.
# The fourth field and each subsequent field will contain two sub-fields
# using the comma (,) as the delimiter
#
# They are:
Prompt,Default
# Any of the sub_fields in the third field can be omitted.
#
#
Material takeoff blank part ID's | %EE_NUC%\bin\dbashell.cmd %EE_RPTNAM%
%EE_RPTDB%
%EE_RWAY%\report\rwaydba_lib %EE_RPTDB% dummy \
| blank_ids \
#
#
447
print.dat
#ident "@(#)env_data:print.dat 21.1 0.0 (EE Schematic) 3/9/94"
#
#
#
#print.dat
# This file is stored under %EE_NUC%\data directory.
# The first column of comment line must be #.
# TITLE | COMMAND | PROMPT,DEFAULT,PATH,SWITCH...
# The titles are the messages on the scrolling list.
# The command can be any command to output a file.
# The third field is made up of four parts: prompt,default,path and switch.
# (The path is not relevant). This field should be used to pass
# information to the command. A file name is automatically appended to
# the command as the last parameter.
#
TO SCREEN| SCREEN
#
# Local line printer
#
Local Printer| lp
#
# NQS print command to print to a laser printer
#
Laser Printer 80 columns | qpr -t text\
| Enter queue name,,,-q
#
Laser Printer 132 columns | %EE_NUC%\bin\eeqpr \
| Enter queue name,,,
#
# This is an example of a way to print to a VAX. The command "vaxprint"
# could be a shell script or an exported shell function.
#
#VAX Line Printer| vaxprint
#
manager.dat
#ident "@(#)env:manager.dat 21.1 0.0 (EE Nucleus) 3/9/94"
#
#
# manager.dat
# This file is stored under the %EE_NUC%\data directory.
#
#
#
448

#
#
#
# The third field and eanh subsequent field will contain three sub-fields
#
b
# They are :
a
#
Prompt,Default,P_th,Switch
# The default can be a grobal symbol or file.
# Any of the sub-fields pn the third field can be omitted
#
t
#
.
Edit database | %EE_NUC%e
xtnt -l %EE_NUC%\db\mgrdba_lib \
| Enter schema name,,, -s
#
#
#Compress database - INFORMIX SE | vterm -x %EE_NUC%\bin\infxcompress -T
compress
#
#
d
#Compress database - INFORMIX Online | vterm -x %EE_NUC%\bin\infx_ol -T
compress
#
e
Create mscolumns table |d%EE_NUC%\bin\mscrecol.cmd \
|Enter schema name,,,
449
450
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.
The following is a print-out of the alias.cmd file (the # symbols indicate comment lines):
#ident "@(#)rdmsg:alias.cmd
13.1
0.0 (EE Raceway) 12/14/93"
#
To create an alias for an EE Raceway command add an entry to this
#
file consisting of the alas and the hardcode for that command in
#
the following format:
#
#
<alias> = <hardcode>
#
#
The list of possible hardcodes follows:
#
#
Command Name
Hardcode
#
------------------#
EERWAY Active OLT Parameters
rwp
#
EERWAY Add System Group
addsysg
#
EERWAY Annotate Element
annotate
#
EERWAY Annotate Group
anntgrp
#
EERWAY Annotate Title Block
anntblk
#
EERWAY Clone Element
clone
#
EERWAY Clone Group
cloneg
#
EERWAY Conduit Sizing
rtwform
#
EERWAY Copy Element
cpele
#
EERWAY Copy Group
cpeleg
#
EERWAY Create Cell
crecell
#
EERWAY Delete Coincident RCPs
coinrcp
#
EERWAY Define Duct Cross Section
ductform
#
EERWAY Delete Duplicate One Lines
dupols
#
EERWAY Delete Element
dltele
451
alias.cmd file
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
452
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 Group
dlteleg
Delete Title Block
dlttblk
Design Parameters
ueleform
Display Element Info
eleinfo
Display Entity and Mslink
prtrlnk
Display Fitting Info
tlfinfo
Display Run Info
runinfo
Display Sector and Word
prtsw
Display System and OLT
prtsysol
Display Type and Asid
prtasid
Edit Manual Fitting
manedit
Exit
rexit
Fitting Environment Element
rulefit
Fitting Environment Group
rulefitg
Group Control
grpform
Highlight Asid
hiasid
Highlight Entity and Mslink
hirlnk
Highlight Graphic Group
higg
Highlight Propagation Errors
hiprerr
Highlight Sector and Word
hisw
Highlight System Elements
hisys
Insert One Line Vertex
insolvert
Insert RCP
addrcp
Levels Control
levels
Load Database
loaddb
Minimize Joints
minjnt
Minimize Joints Group
minjntg
Modify One Line
modol
Move Element
mvele
Move One Line Segment
mvolseg
Move One Line Vertex
mvolvert
Move Title Block
mvtblk
OLT Definition
oltdef
Place Drop Point
plcdpnt
Place Equipment Pointer
plctoeqp
Place Manual Fitting
manform
Place One Line
plcol
Place Title Block
plctblk
Propagate Element
prjele
Propagate Group
prjeleg
Propagation Control
propform
Remove Fitting
rmfit
Remove One Line Vertex
rmolvert
Remove RCP
rmrcp
Replace System Group
repsysg
Rotate Cross Section
rotcs
Route Around Vessel
rtvess
Run Reports
runrpt
Run Rule Checks
runrul
Set Active OLT
actolt
Set Active OLT Parameters
setact
Set Active Point
actpnt
Set Active System
actsys
Set Conduit Sizing Attributes
setcsa
alias.cmd file
#
#
#
#
#
#
#
#
EERWAY
EERWAY
EERWAY
EERWAY
EERWAY
Set Symbology Control

Symbology Control
System Definition
Text Defaults
Toggle Spider Display
setgsc
symbform
sysdef
txtdef
togspider
example: EERWAY Remove Element = dltele
453
alias.cmd file
454
APPENDIX I
rway.cmds
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.amm file.
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
455
rway.cmds
456
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 RIS-supported relational database, either local or remote, is supported.
Usage:
dba_rpt [-?] -s <schema> -l<template library>
[-t<template>|-M<menu template>] -w<where clause> -o<output file>
-S<schema list> [-F<database find>] [wtr_p0]...[wtr_p5]
[-?]
Returns a usage statement like the one listed above.
-s <schema name>
This is the name of any current RIS schema, It is used as a

"default" schema to enter DB Access. It doesn't have to be
the schema your report is running off of.
-l <template library>
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.
-t <report template>
The name of the report you wish to run from your report
template library.
-M <menutemplate>
The name of the menu you wish to run from your menu
templatelibrary.
-w <where clause>
Used to restrict the report output to a certain type of

condition, i.e. "where name = 32".
-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.)
-S <schema list>
This is the list of schemas your report actually runs through.

*
457
Reports
-F <database find>
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))
[wtr_p0]...[wtr_p5]
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).
When you create a template, and use a schema from the schema list, whatever that
schema's 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".)
To view any of the following templates in Help, you may need to resize the Help window.
Project Drawing List (drwlst)

This report lists all drawings currently loaded in the project database, and sorts them by sheet
name.
Information Output:
Drawing.
drawing_type, filename, sheet, load_date, ref_db.
Sorted by (Highest to lowest priority)

drawing.sheet
Associated Software/Files
1. Project Database
2. drwlst (RIS) - a template in the $EE_RWAY/report/rwaydba_lib template library data file.
This file: Selects the desired database tables;
Selects the desired columns from those tables;
Sorts the information according to given sort parameters and;
Formats information into readable form.
3. dba_rpt - the RIS process, found in $EE_NUC/bin, used to execute the
$EE_RWAY/report/rwaydba_lib drwlst template.
458
Reports
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
1. Project Database
2. mto_rpt - a template in the $EE_RWAY/report/rwaydba_lib template library data file.
$EE_RWAY/report/rwaydba_lib mto_rpt template.
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.
description
Fitting.
1. Project Database
2. rway_bom - a template in the $EE_RWAY/report/rwaydba_lib template library data file.
$EE_RWAY/report/rwaydba_lib rway_bom template.
459
Reports
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.

pulled.
with a space between the coordinates: easting northing elevation For example, 234 532 34
Information Output:
Straight.
description
Fitting.
460
Reports
1. Project Database
2. rway_bom_vol - a template in the $EE_RWAY/report/rwaydba_lib template library data file.
$EE_RWAY/report/rwaydba_lib rway_bom_vol template.
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.
description
Fitting.
1. Project Database
2. blank_ids - a template in the $EE_RWAY/report/rwaydba_lib template library data file.
$EE_RWAY/report/rwaydba_lib blank_ids template.
461
Reports
462
APPENDIX K
RIS Schema Manager

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.
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.
Create Schema Form

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.
463
RIS Schema Manager

2. 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.
3. Select the Display Databases button. A form listing all the known RIS databases is
displayed. If you select one of the databases, information about that database is entered into
the Create Schema input fields.
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.
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.
464
RIS Schema Manager

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.
465
RIS Schema Manager

Data Definition Form
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.
466
RIS Schema Manager

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.
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.
467
RIS Schema Manager

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.
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.
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.
468
RIS Schema Manager

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.
469
RIS Schema Manager
470
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
The database ID; a unique key to identify the database
DTYPE
The database type
DBNAME
The database name as in the create schema statement.

It must be a name or pathname as required by the
dbms.
PARMS
The values found in the create schema option clause.
PROTOCOL
The communication protocol to be used to communicate

with the database. Currently supported values are X for
XNS, T for TCP/IP, D for DNP (DECnet), L for LU6.2
NETADDR
The network address (must be an address, not a name)
SCHNAME
The name of the schema
USR
The database user name
USRPASS
The database user password (encrypted)
ARCH
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.
471
RIS Schema Definition File

OS
The operating system that the RIS/DBMS uses. This

value is case-sensitive. The valid value is mvs and the
default value is mvs.
ENV
The environment that the RIS/DBMS uses. This value is

case- sensitive. The valid value is cics and the default
value is cics.
NET_PROTOCOL
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.
RIS_LU or HOST_LU
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.
MODE
The name the Clipper System Administrator assigned to

the mode that allows communication to the RIS program
on the IBM machine.
HOST_PROGRAM
The name the IBM System Administrator called the RIS

server when it was installed on the IBM, the CICS
transaction name.
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.
472
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 EE
Configure (on page 477).
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.
473
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:
The password can be a maximum of 8 characters and is not case sensitive.
In this Appendix
474
Edit Database (see "Database Edit Functions" on page 475) edits any schema that exists in
the RIS dictionary. It uses DB Access to query and edit tables, delete rows, and update rows.
EE Manager
Database Edit Functions

To enter the Database Edit environment, select and confirm the Edit database option from the
System Manager menu.
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.
475
EE Manager
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 field's corresponding column name on the Database Edit screen.
Add Query Used with the AND/OR toggle and relational operators to establish find criteria.
Selecting Add Query puts the screen in Add Query mode. As long as this command is active,
any key-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:
=
476
: 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 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.
Delete Row Deletes the displayed row from the database upon user verification.
APPENDIX N
EE Configure
EE Configure is a process created specifically for setting environment variables for EE Raceway
on a Windows 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.
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.
Browse The Browse button lets you select the required ee.cfg file.
477
EE Configure
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.
2. Select the environment variable you want to change from the User Environment Variables list.
3. The name of the environment variable appears in the Variable field. This same field can be
used to add a new variable.
4. The corresponding value of the environment variable appears in the Value field. The
description, if any, appears in the Descrip field.
5. Edit the entry in the Value field.
6. Click on the Set button to accept the new value. The User Environment Variables list now
contains the new value for this variable.
7. To delete the variable, click on the Delete button. The variable will no longer appear in the
User Environment Variables list.
8. 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.
478
Index
A
About the Reference Guide 13
Activate Design Volume Coordinate System
286
Activate Plant Coordinate System 286
Active Coordinate System 286
Add Systems Group 216
alias.cmd file 451
Annotate Element 151
Annotate Element by Group 208
Annotate Model 260
Archive 31, 73
Area Volume Graphics 324
Define Duct Cross Section 139

Define Group 202
Define One-Line Type 244
Define System 242
Delete 29, 67
Delete Duplicate One-Lines 183
Delete EDEN Symbol 304
Delete Element 184
Delete Element by Group 221
Delete Fitting 188
Design 52
Design Commands 107
Display Element Information 273
Display Element Type and ASID ID 283
Display Link 284
Display Sector/Word Value 283
Display System and One-Line Type 284
Basic Workstation Skills 13
E
C
Change System Parameters 193
Cleanup Database 294
Clone Element 160
Clone Element by Group 212
Combine Coincident RCPs 182
Compile EDEN Symbol 302
Compress EDEN Symbol Library 311
Conduit Sizing 131
Copy 28, 66
Copy Element 156
Copy Element by Group 206
Create 24, 50
Create Cell Commands 250
Create Drop Point Cell 255
Create Equipment Pointer Cell 253
Create Interference Envelope (default
name) 296
Create Interference Envelope (given name)
297
Create Model Cell 251
Customizing Environment Files 443
EDEN 55
Eden Processes 301
Eden Symbol Generation 429
Edit EDEN Symbol File 317
Edit/Insert Manual Fitting 173
EE Configure 477
EE Databases 359
EE File Structure 435
EE Graphics Interface Elements 77
EE Manager 473
EE Raceway Reference Database Schema
Description 381
EERWAY Command Menu Bar 80
Electrical Engineer (EE) Environment 21
Electrical Engineer (EE) Raceway
Environment 49
Enter 25
Error Messages 327
Extract EDEN Symbol From Library 312
Extract EDEN User Function From Library
314
H
D
Database Commands 229
Database Edit Functions 475
Database Utilities 34
Databases 19, 95
Define Active Point 122
Highlight Element by ASID ID 278

Highlight Element by Link 281
Highlight Element by Sector/Word 277
Highlight Propagation Errors 282
479
Index
I
Identifying Elements 86
Insert One-Line Vertex 135
Insert RCP 115
Installation Instructions 15
Integrated Commands 319
Interference Detection 97
Introduction 13
L
List EDEN Symbol Library 306
List EDEN User Functions 307
Load Database 230, 287
Load Reference Schema 46
Lock Model 259
M
Merge EDEN Symbol Libraries 309
Minimize Joints 191
Minimize Joints by Group 219
Mirror Copy Element 198
Mirror Copy Group 226
Mirror Element 197
Mirror Group 225
Model Commands 257
Modeling 46
Modify Commands 147
Modify Element Commands 148
Modify Group Commands 199
Modify One-Line 178
Move Element 158
Move Group 228
Move Model Annotation 259
Move One-Line Segment 163
Move One-Line Vertex 166
O
Output 75
P
Palettes in the EE Raceway Graphics
Environment 81
PDS Electrical Raceway Environment 45
Place Drop Point 119
Place Equipment Pointer 121
Place Field Routed Raceway 137
Place Fitting by Rule 180
Place Fitting by Rule by Group 215
Place Manual Fitting 123
Place One-Line 109
480
Place Stub Up 143

Precision Input Form 97
Preface PDS 9
Process 53
Product Menu 27
Propagate by Group 214
Propagate Element 168
Propagation Setup 271
Purge 69
R
Raceway Processes 287
Receive 72
Reference PDS Model 320
Remove One-Line Vertex 189
Remove RCP 186
Rename 70
Replace Systems by Group 217
Report 59, 233
Reports 97, 457
Restore 33, 74
RIS Schema Definition File 471
RIS Schema Manager 463
RIS schema utilities 35
Rotate Copy Element 196
Rotate Copy Group 224
Rotate Cross Section 117
Rotate Element 194
Rotate Group 222
Route Around Vessel 111
Rule Checks 62, 236
Runtime Setup Commands 263
rway.cmds 455
S
Screen Display 78
Send 71
Set Active Levels 272
Set Active One-Line Type 268
Set Active One-Line Type Parameters 264
Set Active Parameters 122
Set Active System 269
Set Conduit Sizing Attributes 249
Set Raceway Defaults 241
Set Symbology Control 245
Set Text Defaults 248
Setup Commands 239
Show Active Coordinate System 286
Specification 423
Start-up Sequence 77
Symbology Control 246
Index
349
T
The Drawing Process 89
Toggle Construction Display On/Off 277
U
Undelete 68
Unload Design 290
Unload Sheet 292
Unlock Model 260
Update Project Schema 36
Update Reference Schema 40
Upgrading the Workstation 15
Using the Create Cell Commands 250
Using the Database Commands 229
Using the Design Commands 108
Using the Integrated Commands 319
Using the Model Commands 258
Using the Modify Commands 147
Using the Modify Element Commands 151
Using the Modify Group Commands 202
Using the Runtime Setup Commands 264
Using the Setup Commands 240
Using the Utilities Commands 276
Utilities 48, 64
Utilities Commands 275
W
What's New in PDS EERACEWAY 11
Window to Named PDS Item 322
Workflow and Procedures 89
Working Units and Precision Key-ins 86
481

PDS EE Raceway Reference Guide

Uploaded by

Copyright:

Available Formats

PDS EE Raceway Reference Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDS EE Raceway Reference Guide

Uploaded by

Copyright:

Available Formats

EE Raceway Modeling

Version 2011 (V12)

U.S. Government Restricted Rights Legend

Warranties and Liabilities

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

List of PDS Documentation

DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

What's New in PDS EERACEWAY

EE Raceway Modeling Reference Guide

What's New in PDS EERACEWAY

EE Raceway Modeling Reference Guide

About the Reference Guide

Basic Workstation Skills

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

Upgrading the Workstation

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

Using the Electrical Engineer Menus

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

Scrolling Through Listings

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

Cancel (X) exits the EE application entirely.

Project Menu Options

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

The Project name field displays below the scrolling area.

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

The project listing displays.

The EE Product Menu displays.

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

EE Raceway Modeling Reference Guide

Electrical Engineer (EE) Environment

EE Raceway Modeling Reference Guide