Port of Long Beach Engineering. CADD Standards Manual

Transcription

1 Port of Long Beach Engineering CADD Standards Manual

2 Port of Long Beach CADD Standards Manual June 10, 2010 Current Standards Version: 1.3 Revision History: 1.2 Draft released December, Draft released October, Released January 12, 2008 Detailed change history available upon request. Questions related to this manual should contact The Port of Long Beach CADD Manager: Port of Long Beach Engineering Design 925 Harbor Plaza Long Beach, CA Page i

3 Table of Contents 1. INTRODUCTION Introduction Scope and Purpose Source Compliance Request for Variance Procedures to Change This Manual CADD Standards Change Request Form SOFTWARE REQUIREMENTS Introduction Compatibility Software Version SEED FILES AND COORDINATE SYSTEMS Seed File (2D) POLB Seed 2D.dgn Seed File (3D) POLB Seed 3D.dgn Seed File (3D) POLB Survey Seed 3D.dgn Seed File (3D) POLB Structural-Architectural Seed 3D.dgn Primary Coordinate System NAD EPOCH Other Coordinate Systems DRAWING FILE Introduction Design Model Design Cube Global Origin Working Units WORKSPACE Introduction PROJECTWISE Introduction Non-ProjectWise Documents Page ii

4 Creating a Non-ProjectWise Document Updating a Non-ProjectWise Document in ProjectWise Importing a Non-ProjectWise Document Design History / ProjectWise Versioning ProjectWise Dependency Viewer Project Explorer and Link Sets INROADS Introduction Workflow Starting a Project in ProjectWise Other InRoads Related Start-up Items Project Defaults Folder / File Information / Structure The XIN File InRoads Text Sizes InRoads Preferences Global Scale Factors InRoads Fix InRoads Text tool InRoads Changes and Additions PROJECT ORGANIZATION AND FILE NAMING CONVENTION Introduction Folder Structure Example of a typical project folder structure Types of Drawing Files Model Files Sheet Files Base Maps File Naming Convention (Model and Sheet Files) Project Designator, Character Facility Code, Characters 10 and Discipline Designator, Character Major Discipline Code, Characters 15 and Page iii

5 Minor Discipline Code, Characters 15 and CADD File Type Designator, Character Sequence Number, Characters Sheet Set Layout File Naming Convention (Base Maps) File Naming Convention (InRoads and other non-cadd data files) LEVEL ASSIGNMENTS Introduction Levels Defined Level Naming Conventions Filters DRAFTING STANDARDS Introduction DGN Libraries (DGNLIBS) Graphic Attributes Linestyles Caltrans Styles POLB Styles (1 of 4) POLB Styles (2 of 4) POLB Styles (3 of 4) POLB Styles (4 of 4) Cells Text Attributes Fonts Text Styles (ANSI A 8-1/2 x 11) Text Styles (ANSI D 22x34 or larger) Text Orientation Leader Lines Terminators Dimension Attributes Dimension Styles Border Files Page iv

6 Border Sheets Border Saved Views Title Blocks Title Block Seal Frame Consultant Border Sheet Inserting and Updating the Title Block Logical Names Reference Attachments Raster and PDF Attachments Symbols Level Overrides View Display Attributes OLE Object Links Digital Signatures / Digital Rights ELECTRONIC FILE TRANSFER Introduction Contents Format Media ANNOTATION LEVEL PROPERTIES Introduction Level Assignments GENERAL LEVEL PROPERTIES Introduction Level Assignments DETAIL LEVEL PROPERTIES Introduction Level Assignments ARCHITECTURAL LEVEL PROPERTIES Introduction Level Assignments CIVIL LEVEL PROPERTIES Page v

7 Introduction Level Assignments PROCESS LEVEL PROPERTIES Introduction Level Assignments ELECTRICAL LEVEL PROPERTIES Introduction Level Assignments FIRE PROTECTION LEVEL PROPERTIES Introduction Level Assignments HAZARDOUS MATERIALS LEVEL PROPERTIES Introduction Level Assignments INTERIORS LEVEL PROPERTIES Introduction Level Assignments LANDSCAPE LEVEL PROPERTIES Introduction Level Assignments MECHANICAL LEVEL PROPERTIES Introduction Level Assignments OPERATIONS STANDADS Introduction Level Assignments PLUMBING LEVEL PROPERTIES Introduction Level Assignments EQUIPMENT LEVEL PROPERTIES Introduction Level Assignments Page vi

8 27. RESOURCE LEVEL PROPERTIES Introduction Level Assignments STRUCTURAL LEVEL PROPERTIES Introduction Level Assignments TELECOMMUNICATIONS LEVEL PROPERTIES Introduction Level Assignments SURVEYING/MAPPING LEVEL PROPERTIES Introduction Level Assignments Glossary Page vii

9 Page viii

10 1. INTRODUCTION Introduction The Port of Long Beach (POLB) CADD Standards Manual comprehensively details all required standards for use on CADD projects at POLB. This document includes guidelines for product versions, product configurations, folder structure, file naming, drafting standards, level assignments, electronic deliverables, etc. Scope and Purpose The purpose of this manual is to establish specific requirements and standards for the development and delivery of CADD files and hard copy prints for all Port design, construction and mapping projects. Source POLB CADD Standards Manual was developed using portions of the National CADD standards, version 4.0 as a reference but customized for use at POLB. Compliance Compliance to these standards is required by the terms and conditions of each project contract. All groups shall adhere to these standards for all electronic and hard copy deliverables during and at the conclusion of a project. These requirements apply to all design group personnel, survey group personnel, and consultants (including sub-consultants) who are providing electronic documents or hard copies. To ensure compliance, all consultants and sub-consultants should use the workspace configurations provided by POLB. The prime consultant is responsible for adherence to these standards and for all CADD deliverables including those deliverables provided by their sub-consultants. All electronic files and hard copies will be checked for compliance with these standards. Any modification of the workspace or standard herein shall only be done with the express written permission of POLB CADD Manager. For bridge and freeway projects, POLB will conform to Caltrans CADD standards unless otherwise approved by POLB. INTRODUCTION Page 1-1

11 Request for Variance When variance from POLB CADD Standards is required, a request for variance shall be submitted in writing to POLB CADD Manager prior to committing the changes. Procedures to Change This Manual Consultant proposed changes to the CADD Standards Manual shall be submitted to POLB CADD Manager using the form provided on Page 1-3. POLB staff can use the electronic form called CADD Standards Change Request Form.docx, which is located in the ProjectWise folder 4.7 POLB CADD Standards. This form can also be copied from page 1-3 of the CADD Standards Manual. All requested changes will be reviewed by POLB CADD Manager & CAC Members. If approved, the changes will be implemented as part of the next scheduled update. INTRODUCTION Page 1-2

12 CADD Standards Change Request Form Requestor: Date: Requestor: Company/Department: Phone: CADD Standards Manual: Subject: Section: Sub-section: Page: Justification for Change: Existing Provisions are: Incomplete Inaccurate Redundant Conflicting Obsolete Other Or New provision not covered in the current manual Detailed Justification: Description of Change(s): Send Request to: Port of Long Beach Engineering Design - CADD Manager 925 Harbor Plaza P.O. Box 570 Long Beach, CA Reviewed by: CADD Manager: Circle decision: Approved / Disapproved / Need more information Date: CAC Review date: Approved / Disapproved / Need more information Comments: INTRODUCTION Page 1-3

13 INTRODUCTION Page 1-4

14 2. SOFTWARE REQUIREMENTS Introduction This chapter identifies the software packages and file formats used at POLB in the production and maintenance of project documentation. Compatibility All electronic files (construction documents, as-builts, specifications, etc.) delivered to POLB must be in the applicable format listed below. Software Type Product Manufacturer Format Operating System Windows XP/Vista/Windows 7 Microsoft, Inc. Document Mgmt. Software ProjectWise V8i Selectseries 1 Bentley Systems, Inc. CADD Software MicroStation V8i Selectseries 1 Bentley Systems, Inc. dgn Plot Software IPLOT V8i Selectseries 1 Bentley Systems, Inc. i, m Civil Software InRoads V8i Selectseries 1 Bentley Systems, Inc. dgn, dtm, alg, itl, ird, xml, dft, xin GIS Software Bentley Map V8i Selectseries 1 ArcGIS Bentley Systems, Inc. ESRI Dgn SHP Survey Software InRoads Survey V8i Selectseries 1 Bentley Systems, Inc. dgn, fwd Word Processing Word 2003 / 2007 Microsoft, Inc. doc, docx Spreadsheet Excel 2003 / 2007 Microsoft, Inc. xls, xlsx MS Project Project 2007 Microsoft mpp PDF Adobe Reader 9.x Adobe Systems, Inc. pdf Version In general, POLB uses the latest versions of all software products. However, the consultant is required to confirm the version to be used with POLB CADD Manager prior to beginning project work. SOFTWARE REQUIREMENTS Page 2-1

15 SOFTWARE REQUIREMENTS Page 2-2

16 3. SEED FILES AND COORDINATE SYSTEMS Seed files are templates used by MicroStation to create new design files. Seed files contain standard drawing parameters such as working units, view attributes, etc. Use of the following seed files supplied with this manual on all CADD design files for POLB will ensure compatibility with POLB base maps and design files. POLB s seed files should not be altered in any way. Seed File (2D) POLB Seed 2D.dgn The 2D seed file is used when creating design files which require a two dimensional working area. Parameter Default Model Global Origin 0,0 Format Master Units MU US Survey Feet Master Units Label Sub Units Sub Units Label Survey Tenths TN Linear Accuracy Angle Format Angle Mode DD MM SS Bearing Angle Accuracy 0.12 ACS Triad Projection Name Resolution Working Area Solids Area Solids Accuracy Off NAD83-VF (applied to all views) per Survey Feet Miles 0.6 Miles E-008 Survey Feet SEED FILES AND COORDINATE SYSTEMS Page 3-1

17 Seed File (3D) POLB Seed 3D.dgn The 3D seed file is used when creating design files which require a three dimensional working area, such as InRoads files. Parameter Default Model Global Origin 0,0,0 Format Master Units MU US Survey Feet Master Units Label Sub Units Sub Units Label Survey Tenths TN Linear Accuracy Angle Format Angle Mode DD MM SS Bearing Angle Accuracy 0.12 ACS Triad Projection Name Resolution Working Area Solids Area Solids Accuracy Off NAD83-VF (applied to all views) per Survey Feet Miles 0.6 Miles E-008 Survey Feet SEED FILES AND COORDINATE SYSTEMS Page 3-2

18 Seed File (3D) POLB Survey Seed 3D.dgn Use the Survey 3D seed file when using the InRoads Survey applications which require three dimensional design files. The Survey 3D seed file is preconfigured to use a global linestyle scale of 40 and comes with annotation scale lock turned off. Parameter Default Model Global Origin 0,0,0 Format Master Units MU US Survey Feet Master Units Label Sub Units Sub Units Label Survey Tenths TN Linear Accuracy Angle Format Angle Mode DD MM SS Bearing Angle Accuracy 0.12 ACS Triad Projection Name Resolution Working Area Solids Area Solids Accuracy Off NAD83-VF (applied to all views) per Survey Feet Miles 0.6 Miles E-008 Survey Feet SEED FILES AND COORDINATE SYSTEMS Page 3-3

19 Seed File (3D) POLB Structural-Architectural Seed 3D.dgn The Structural-Architectural 3D seed file is used when creating design files that require three dimensional working areas with the sub units defined as US Survey Inches. Parameter Default Model Global Origin 0,0,0 Format Master Units MU US Survey Feet Master Units Label Sub Units US Survey Inches Sub Units Label Linear Accuracy Angle Format Angle Mode DD.DDDD Conventional Angle Accuracy 0.12 ACS Triad Projection Name Resolution Working Area Solids Area Solids Accuracy Off NAD83-VF (applied to all views) per Survey Feet Miles 0.6 Miles E-008 Survey Feet SEED FILES AND COORDINATE SYSTEMS Page 3-4

20 Primary Coordinate System NAD EPOCH The primary coordinate system is based on NAD83 using the EPOCH. Detailed information on this coordinate system is provided below. Example Port based data Coordinate System State Plane Coordinate Lambert Conformal Conic Longitude of Origin: 118º00 00 W Latitude of Origin: 33º30 00 N Standard Parallel 1 34º02 00 N Standard Parallel 2 35º28 00 N False Easting 2,000,000 meters False Northing 500,000 meters Geodetic Datum North American 1983 Epoch Ellipsoid GRS80 GRS80 Equatorial Radius 6,378,137 meters Polar Radius 6,356, meters Eccentricity Flattening Flattening Inverse Units and Format Latitude and Longitude Degrees-Minutes-Seconds Northing and Easting U.S. Feet Height U.S. Feet Description Vertical Datum Current Port Standard North American Vertical Orthometric Average Undulation ft SEED FILES AND COORDINATE SYSTEMS Page 3-5

21 Other Coordinate Systems While the current standard coordinate system used at POLB is NAD 83_ , other coordinate systems have been used in the past and one may encounter drawings using one of the coordinate systems listed below. Should one receive data in a different coordinate system or have the need to switch coordinate systems, please contact POLB Project Manager and POLB CADD Manager prior to proceeding. Name DMG GIS90 NAD27 NAD83_ NAD83_2007 LDP2007 Description A rectangular survey system established by the US Engineers in 1859 using monument Deadman Island. A local adjustment of POLB control based on the NAD27 datum. GIS90 coordinates have been truncated by 4,000,000 in the Northing and 4,200,000 in the Easting. GIS90 values vary by only a few hundredths from NAD27. This coordinate system is based on NAD27 State Plane using control provided by RBF Consulting and Johnson and Frank Assoc. This coordinate system is based on NAD83 State Plane using control provided by Digital Mapping Inc. The refers to the EPOCH from the National Geodetic Survey Adjustment. This coordinate system is based on NAD83 CA State Plane using control provided by Digital Mapping Inc. The 2007 refers to the EPOCH from the National Geodetic Survey Adjustment. This coordinate system is based on NAD83 Low Distortion Projection created by Keson Geodetic Services for POLB. Coordinate system use: All POLB seed files have the coordinate system defined using the MicroStation geographic coordinate system tools and contain corresponding coordinate system cells as defined by POLB. These are required, and should not be removed or changed. Therefore the use of POLB standard seed files is required for all new files being created. Coordinate systems are stored in the file format of MicroStation V8i and are not compatible with previous versions, such as XM. This also complicates data conversion to other CADD formats and is not recommended. All delivered files must contain coordinates systems compatible with MicroStation V8i. SEED FILES AND COORDINATE SYSTEMS Page 3-6

22 The seed files have the coordinate system applied to all views in the Auxiliary Coordinates dialog box as shown. This should be properly set prior to delivering these files to POLB. At no time should coordinate systems be changed using NADCON (or similar tools) to convert coordinate systems. Built-in MicroStation reprojection tools are not to be used. Should it be required to change coordinates systems, please refer to POLB Coordinate System Macro Documentation for more details. Macro and documentation is available upon request, please contact POLB CADD Manager. SEED FILES AND COORDINATE SYSTEMS Page 3-7

23 SEED FILES AND COORDINATE SYSTEMS Page 3-8

24 4. DRAWING FILE Introduction This chapter defines the MicroStation concept of the Design Model, the Design Cube, the Global Origin and Working Units. Use of the Seed File, provided with this document and as defined in Chapter 3, will ensure compatibility with POLB base maps and design files. Design Model Each MicroStation design file (DGN) can contain one or more models, either design models or sheet models. A design model is a container for design geometry and can be either 2D or 3D. A design model can also be used as a reference or placed as a cell. Each model within a design file has its own set of working units and coordinate space, but all models within a design file share a common set of levels. By default, the view windows of a design model have black backgrounds. For more information on the relationship between design files, design models, and sheet models, consult the help file delivered with MicroStation. Unless otherwise noted, all POLB DGN files are to contain only one design model. Design Cube MicroStation V8i utilizes a finite design cube that has 9.00 x Units of Resolution (U.O.R.) in each axis (x, y, z). These points are grouped to comprise the model s Working Units. Working Units are made up of Master Units, Sub Units, and a Resolution. Global Origin All models within MicroStation design files have an origin and that origin is known as the global origin. The Global Origin used in all seed files and projects shall be 0,0,0. DRAWING FILE Page 4-1

25 Working Units Master Units = Largest units in common use in a model. By default, the Master Units for the POLB DGN files are set to US Survey Feet. Sub Units = Units that master units are divided into in the working unit definition. For example, if Master Units are US Survey Feet, a convenient setting for the Sub Units would be US Survey Inches or US Survey Tenths. The Sub Units in POLB 2D and 3D Seed files are set to US Survey Tenths. The Sub Units in the Structural-Architectural file is set to US Survey Inches. Changing the Sub Unit value does not affect the size or position of elements within the model. Resolution (Advanced Setting) = Number of addressable points across a given area. For example, output device resolution is measured in lines per inch, while screen resolution is usually given with two numbers indicating the number of pixels across the width and height of the largest image that can be displayed. Port uses a resolution of U.O.R / survey foot for all CADD files. DO NOT CHANGE THE RESOLUTION SINCE DOING SO WILL CHANGE THE SIZE OF THE ELEMENTS IN THE DGN FILE. Solids Accuracy (Advanced Setting) = Required by the Parasolid solids modeling engine used by MicroStation. It defines an upper boundary that limits the extents of any single solid such that it can be modeled to a fixed precision. This precision value is displayed in the Advanced Unit Settings dialog box as Solids Accuracy. POLB uses a solids working area of 0.6 miles which results in a solids accuracy of E-008 survey feet. The working units may be changed in the Drawing Scale dialog or by the following keyins: For US Survey Feet / US Survey Inches: set units "survey feet" "survey inches" For US Survey Feet / US Survey Tenths: set units "survey feet" "survey tenths" DRAWING FILE Page 4-2

26 5. WORKSPACE Introduction A workspace is a custom MicroStation environment or configuration. By selecting a workspace, you customize MicroStation for a specific discipline, project, or task. ProjectWise, described in Chapter 6, increases consistency by assigning a workspace to a project, folder or document. The POLB Workspace has been designed to work with ProjectWise as well as externally on its own. The POLB Workspace provides productivity-enhancing tools that will automate many of the more tedious drafting processes, ensure the proper placement of symbols and drawing components, and eliminate errors related to element color, style, weight and level placement allowing for the proper completion and submittal of POLB electronic files and hard copy plots. All sub-consultants will use the POLB Workspace when it is required by contract. To assist consultants and sub-consultants working on POLB-related projects, a deliverable version of the POLB workspace has been created. All required MicroStation data resources are provided with the deliverable workspace, including cell libraries, font resources files, DGN libraries, macros and settings files. Please contact the POLB CADD Manager to obtain a copy of the POLB CADD Standards and workspace. The following is a list of workspace components: User This component in effect points to the active workspace's Project and Interface components. The user name identifies the user configuration file (.ucf), which is stored in Bentley's "..WorkSpace\Users" directory. Project A project consists of customized data files, such as cell libraries and line style libraries, identified by configuration variables in the project configuration file (.pcf). The data files in the sample projects provided with MicroStation are delivered as modules in directories under Bentley's "..\WorkSpace\Projects\Examples" directory. Interface A customized user interface can be defined in a personal DGN library that is stored in a directory under Bentley's "..\WorkSpace\Interfaces\MicroStation" directory. The personal DGN library is created when you create a new interface component. (User) Preferences Customized user preferences are defined in a user preference file (<user_name>.upf) in the "..\Local Settings\Application Data\Bentley\MicroStation\ prefs" directory. You can select any available user, project, and interface as the components of the active workspace. The active workspace components are identified by the user configuration file. ProjectWise handles workspaces using configuration settings blocks and/or workspace profiles. You can use one convention exclusively, or you can configure and use both conventions in the same datasource. WORKSPACE Page 5-1

27 WORKSPACE Page 5-2

28 6. PROJECTWISE Introduction The POLB has implemented Bentley ProjectWise as the content management system for all survey, design, and GIS data. ProjectWise allows for the creation and organization of project documents throughout the survey, design, construction, and mapping phases. Each project team using ProjectWise can depend on a single, consistent set of data. The POLB ProjectWise data source is available internally to the POLB Engineering staff via the ProjectWise Explorer client installed on all CADD workstations. The POLB datasource will be made available to consultants and contractors on a project by project basis. POLB Standard Datasource Structure: Non-ProjectWise Documents All project related documents will be contained within ProjectWise unless otherwise specified. The following is a list of file types that will be managed inside ProjectWise but may be edited outside of ProjectWise by using the Export / Import tool. InRoads Geometry Projects (ALG)* STAAD and SAP 2000 Structural Files * Only if Geometry Project requires multi-user access. PROJECTWISE Page 6-1

29 The owner will be responsible for maintaining the file outside of ProjectWise. The owner will be in charge of the following three scenarios: Creating a Non-ProjectWise Document Use the following procedure to create a new document in ProjectWise and then export it to a location outside of ProjectWise for editing. Under this scenario, the file in ProjectWise will be locked to other ProjectWise users, preventing them from making any edits to the file. The file can be edited from its location outside of ProjectWise and then imported back in when the editing is complete. The import process is described in more detail in the next section. 1. Create the file outside of ProjectWise. 2. Drag and drop the file into 4.0 Design Data inside the ProjectWise Project. Note: The original file will not be deleted when it is imported into ProjectWise. 3. Right click on ProjectWise document click Export. PROJECTWISE Page 6-2

30 4. The Document Export Wizard will open. Click Next to continue. PROJECTWISE Page 6-3

31 5. Select the Export option and set the correct Export folder (K:\2 Projects\xxxx-xxx\4.0 Design Data, where xxxx-xxx is the project folder name), then click Next. 6. Click Finish. 7. Note how the document is displayed in the ProjectWise Explorer with a disk next to it indicating that the file has been exported. Other users will see a lock displayed in the first column of the ProjectWise Explorer indicating that the file is checked out by another user. PROJECTWISE Page 6-4

32 Updating a Non-ProjectWise Document in ProjectWise Once a file has been exported from ProjectWise, it can be edited from its exported location. It is a good idea to update the document in ProjectWise on a regular basis so that other project participants can view changes made to the exported document and to make sure the file is backed up to a secure location. 1. Open the Local Document Organizer from the ProjectWise Explorer by going to Tools > Local Document Organizer. 2. Select the Exports view by clicking on the disk icon. Alternatively, this can be selected from View > Exports which will display all the file(s) that have been exported. 3. Right click on the document(s) needing to be updated and select Update Server Copy. PROJECTWISE Page 6-5

33 4. Enter a comment if desired and select OK to continue. 5. The contents of the file will be copied to the ProjectWise server while the document will remain exported. Updates to these files may continue outside of the ProjectWise environment if needed but they will need to be updated again. PROJECTWISE Page 6-6

34 Importing a Non-ProjectWise Document After completing the edits to the file, it can be brought back into ProjectWise using the Import tool which will check the file back in. This will allow other users to Check Out or Export the file. 1. Open the Local Document Organizer from the ProjectWise Explorer by going to Tools > Local Document Organizer. 2. Select the Exports View by clicking on the disk icon. Alternatively, this can be selected from View > Exports which will display all the file(s) that have been exported. 3. Right click on the document needing to be imported and select Import. Note: ProjectWise will import the document from the location it was exported to. If it does not find the file in the exported location, it will prompt the user to browse to the location of the exported file. PROJECTWISE Page 6-7

35 4. Enter a comment if desired and click OK. 5. The contents of the file will be copied to the ProjectWise server and the document will be checked in so that other ProjectWise users can edit it. The file in the exported location will be deleted. PROJECTWISE Page 6-8

36 Design History / ProjectWise Versioning Design History in MicroStation allows for the tracking of incremental changes made to all models in a file and for the rollback of a model to a prior state. Additionally, the Design History tools allow for the review of the changes made whenever a change was committed to the design file. Design history will be turned on in the POLB Seed 2D and POLB Seed 3D Files. Each user will determine when to commit changes. ProjectWise also has a method for managing prior versions of files by creating a read-only copy of a file which can be recalled and made into the current version of a file at any time. ProjectWise versions can be created for any type of file, while Design History can only be used on a MicroStation DGN file. The project engineer will determine how versioning is to be used. PROJECTWISE Page 6-9

37 ProjectWise Dependency Viewer When installed, this tool will graphically show file structure of a project. When combined with the Authoring tool, it will allow dependencies to be set at on fields. Currently, POLB is only using the client feature shown below. PROJECTWISE Page 6-10

38 Project Explorer and Link Sets MicroStation design files can contain Link Sets which are a way to establish links to other documents such as PDFs, Word documents, etc. from a DGN file. Links can be added to individual elements in a design file so that when the element is selected in MicroStation, it is possible to navigate to the document The Project Explorer is the interface in MicroStation where links can be displayed and managed. If a file containing Link Sets is located in a ProjectWise project, the Link Sets will be displayed in the Datasource Pane of the ProjectWise Explorer. Here is what Link Sets look like inside Project Explorer inside MicroStation: Here is the same link set in the ProjectWise Project: Page 6-11

39 Page 6-1

40 7. INROADS Introduction This chapter identifies the requirements for InRoads data and provides a basic understanding of how InRoads is to be used at POLB. Additional documentation beyond the scope of this manual may be available on request. These additional documents include the Survey Coding Handbook & Field Collection Guide and DTM QA / QC Checklist. Workflow The basic schematic workflow (from Survey to Design and back) as it relates to InRoads is as follows: 1) The Project Engineer/Project Manager submits a Survey collection request and meets with Survey to review the survey request and discuss the specific collection requirements 2) The requesting group creates a ProjectWise Project & copies appropriate InRoads configuration files (XIN and DFT) to the ProjectWise Project 3) Survey performs Electronic Data Collection per POLB coding standards and downloads the Data Collection locally and moves it in the correct project folder within ProjectWise 4) The survey field data is processed, analyzed and corrected as needed with InRoads Survey 5) The Senior Surveyor will ensure that the final survey deliverables are placed in the corresponding ProjectWise Project and checked a. The survey deliverables include: i. Original source data collection files ii. The final InRoads Survey Fieldbook. This should be the source file for the existing DTM and ALG. The InRoads Survey fieldbook should not contain any errors and should be a complete record of the field collection iii. DGN CADD file base map, per CADD File QA / QC Checklist, to include: 1. DGN file created using POLB Survey MicroStation Seed file 2. Base map topography features on the correct Survey levels 3. Existing contours at an appropriate interval density with labels properly spaced along the contour iv. Existing DTM per the DTM QA / QC Checklist is required on all projects except for location type work where a surface model wouldn t apply INROADS Page 7-1

41 v. Existing ALG exported after the Fieldbook is completed is required on all survey work. Design will use this in lieu of the CADD display of point numbers vi. ASCII comma delimited Text file export of the completed work Pt #, N, E, Z, Code, Description or Note vii. Consultant and Sub-consultant should also deliver their XIN file along with the project data files viii. Optional Any special request any deviations from the standard survey deliverables should be specifically requested 6) After the final deliverables have been checked and run through POLB QA / QC processes, they are issued to the requestor. During this checking process, the CADD Support group may also check the deliverables for compliance to POLB standards 7) Design project coordination meeting 8) Design work commences 9) Once the design is well established, consultants and/or the Drafting group will use MicroStation and InRoads drafting tools to create sheet files 10) Design completes the construction drawings 11) The Project Engineer/Project Manager will ensure the QA / QC process is performed on the drawings, surfaces & geometry files once design is completed 12) All design deliverables are contained within the project folders within ProjectWise including: a. MicroStation Plan Sheets, DGN file(s) b. InRoads Design Surface Model(s), DTM file(s) c. InRoads Design Geometry Project(s), ALG file(s) 13) A hand-off meeting occurs between Survey & Design at the time of construction staking request 14) Survey then proceeds with construction staking using the InRoads Design files and final construction drawings Starting a Project in ProjectWise The ProjectWise Project Template does not contain InRoads configuration files and therefore must be manually copied from the POLB Standards folder into the Project Configuration folder. The files that are required by InRoads are primarily the POLB.XIN file, and secondarily the POLB_notes.DFT drafting notes file. These files should be copied into the project 7.0 Configuration Files folder at the time of the Project creation. If these files do not exist or become corrupted, they can be found and copied from the INROADS Page 7-2

42 subfolders located in this ProjectWise directory ProjectWise\Documents\4 Standards\4.1 Workspaces\POLB_Workspace\InRoads\ Other InRoads Related Start-up Items In addition to the XIN and DFT file there are a few other items that must be considered. There are several customized XSL report templates that are provided with the standard POLB Workspace. These reports should be used in lieu of the standard Bentley out-of-the-box templates. InRoads Application Add-ins and Variable Manager settings also come into play when using InRoads. These settings are defined using a login script at POLB, however they can be toggled on and off by the user so be aware that there is no assurance that these settings will be defined correctly. When using InRoads Survey, the Import tool accesses both TIW and TEW files to interpret the format of the files coming into InRoads Survey as well as reports exported from InRoads Survey. POLB provides supplemental TIW and TEW files that are used by POLB s XIN file. Project Defaults POLB CADD Standards are integrated into the InRoads XIN and DFT files. In order to hard code these files to InRoads the InRoads File> Project Defaults are used. The Project Defaults should be used to establish the location of the XIN, DFT files and Default Directory Paths. The Project Default Directory is a local folder outside of ProjectWise. Likewise the Style Sheet path should point outside of ProjectWise to the POLB standards folder located on the K: drive as shown on page 7-4 of this manual. INROADS Page 7-3

43 INROADS Page 7-4

44 Folder / File Information / Structure Files will maintain the same name both internally and externally for the InRoads files. When working in ProjectWise the Descriptions should also be identical. Also working within ProjectWise the InRoads Internal name, the ProjectWise File Name and the ProjectWise Name will all be the same. These names should use the naming conventions identified in section 8 of this manual whenever possible. See example: Internal InRoads naming requirements such as Design Feature names, horizontal and vertical alignment names, names of typical sections and names of roadway corridors are left to the discretion of the user; however descriptive intuitive naming is required. If a simplistic naming convention is used, please incorporate a description that adds value to the overall identification of the data for other users. Please refer to the folder structure in section 8 of this document for the precise placement of the InRoads data files, along with other support files either imported into or exported from InRoads. The XIN File The InRoads XIN contains several key pieces of information. 1) The survey field codes 2) Existing and Proposed Styles used to create Intelligent surface models 3) Geometry Styles used to control the display of horizontal and vertical alignments 4) Collections of settings called Preferences that control the standards that appear in the various dialog boxes within InRoads POLB has developed an XIN file that contains most everything that is required for any survey work performed at POLB. An extensive collection of field codes, all tied to POLB CADD Standards as well as ties to the construction of an intelligent surface model has been completed. The Design aspect of the XIN contains the key settings needed for most design work done at POLB. These settings include: INROADS Page 7-5

45 1) Existing, Proposed and Abandoned Utility Styles designed to display and annotate in Plan, Profile and Cross Section per POLB CADD Standards, and Seed Utilities Styles that can be used to create any utility information not already created 2) Grading displays for site grading, including Contour display, DTM triangle network, contour labeling and others 3) Profile and Cross Sections configured to POLB standards 4) Horizontal alignment Stationing along with Geometry display and Tabling for horizontal layout and point geometry 5) Vertical alignment display and annotation within a profile window InRoads Text Sizes It is very important to note that the textual information (annotation) coming from InRoads does not work with the MicroStation Annotation Scaling. InRoads Preferences Since InRoads does not utilize Annotation Scaling it is important to load the correct InRoads Preference when viewing something from InRoads. Global Scale Factors In addition to loading the correct Preference, InRoads contains a tool called the Global Scale Factors. This tool is installed by checking it on under InRoads > Tools > Global Scale Factors. The Text scale INROADS Page 7-6

46 should be entered here, and the Apply button selected, before viewing any annotation from InRoads (if the scale is important to the display). InRoads Fix InRoads Text tool A special tool has been created and integrated into the POLB MicroStation menu. The Fix InRoads Text tool can be used to rescale any text displayed by InRoads to the proper scale. There are several scale selections in the pick list; otherwise you can simply type the scale that you need into the available field. InRoads Changes and Additions All change requests should be submitted using the Change Request form found on page 1-3 of this manual. These could include additional survey codes for field use, additional InRoads Styles for design use, or symbology changes to By-Level settings used by InRoads. Consultants and Sub-Consultants should coordinate with either the Survey Group or Design Group to discuss their changes prior to submitting an official revision to the POLB CADD Manager. INROADS Page 7-7

47 INROADS Page 7-8

48 8. PROJECT ORGANIZATION AND FILE NAMING CONVENTION Introduction This chapter outlines the folder structure for each project. There are three types of drawing files names being used (Models, Sheets and Base Maps) in the standards. Folder Structure The project folder will be named according to the project number and will contain the following subfolders (if using ProjectWise these will be created automatically from a standard project template): 0.0 Base Maps At the beginning of the project, the base map DGN files must be copied into this folder from the GIS Base Maps. (POLB stores these files in 0 Base Maps folder in ProjectWise) 1.0 Project Management The Project Management folder will contain all documents pertaining to project management including the contract, meeting minutes, agendas, cost estimates, etc. 1.1 PIF & Cash Flow Project initiation Form and Cost 1.2 Documents Reports, notes and diagrams 1.3 Schedule Project Schedules (Microsoft Project) 1.4 Estimates Cost estimates 1.5 Minutes Meeting Minutes 1.6 Permits Permit related data (HDP) 1.7 Specification Project Specifications 2.0 Correspondence The Correspondence folder will include all correspondence documents including transmittal covers, s, letters, memos, etc. 3.0 Survey Data The Survey folder will include all raw survey data and survey deliverables such as field books, DTMs, and InRoads ALG files. 3.1 Photos and Videos Field photos and videos 3.2 As-builts Field Data 3.3 Control files 3.4 DTMs InRoads Digital Terrain Models 3.5 Hydrographic 3.6 Monitoring 3.7 Alignments InRoads ALG files 3.8 Stakeout Reports 3.9 Topo PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-1

49 4.0 Design Data The Design Data folder will contain supporting documents and information used in design such as spreadsheets, calculations, InRoads files, photos, MathCAD files, AutoTURN files, etc. filed by discipline. 4.1 Photos and Videos Field photos and videos 4.2 Civil Civil discipline related files, hydraulic calculations and Hydrology 4.3 Structural Structural discipline related files 4.4 Traffic Traffic discipline related files 5.0 Drawings The Drawings folder will contain all design files and reference files that are used in the creation and output of project deliverables. 5.1 Survey The Survey drawing folder will contain survey related DGN files. 5.2 Design The Design drawing folder will contain all model and sheet files for design. 5.3 As-built The As-built delivered files. 5.4 Archive The Archive folder will contain all sheet files pertaining to the Mapping department. 5.5 PDF PDF output of design files and IPlot sets. 6.0 Construction Support The Construction Support folder will contain documents pertaining to construction management, such as RFI s initiated by the Design group. 7.0 Configuration Files Support files for MicroStation and InRoads including project-specific XINs, project-specific RSC files, IPS files, etc. Due to Configuration limitations, some configuration files are copied out of ProjectWise and stored on the K Drive. These files will be updated and maintained by the POLB CADD Manager. For more details regarding non-projectwise documents, please see Chapter 6 PROJECTWISE. PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-2

50 Example of a typical project folder structure: PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-3

51 Types of Drawing Files There are three types of CADD files for work at POLB: Model Files, Sheet Files, and Base Maps. Model Files Model Files are full scale DGNs that show the big picture of a project and are to be drawn in the default model. Examples include design information such as roads, utilities, wharfs, etc. These files are then used as a reference in other models and sheets. Files should only contain one model with the exception of details which can be organized using multiple models. Sheet Files Sheet Files correspond to the final plotted CADD drawing. Typically, only one sheet will be created in the Default model of the DGN file. Sheet models are not to be used except in special situations such as mapping exhibits. Sheet Files include annotation, notes, call-outs, dimensions, etc. with the Model File(s) referenced into the sheet and are used to communicate the design to the contractor and others. The border is referenced to the sheet and scaled per the sheet scale. The referenced Model File(s) are clipped within the border sheet to display the portion of the design pertinent to the sheet. Some sheets may be created using multiple models. One example is detail sheets. The detail sheet will be created in the Default model of the DGN file, and then the border file would be referenced in at a scale of 1.0. Other design models containing the actual details will have their own annotation scale such as 1 =40. A saved view will be created in the design model where the detail resides, which will then be subsequently referenced into the Default model of the detail sheet. Each of these saved views will be referenced into the detail sheet at a scale of 1.0. The output will be one sheet in the Default model that will print out at 1 =1-0. Base Maps Base maps are generated by the POLB GIS/Mapping Group and represent the most current set of asbuilt plans at POLB. These maps will be copied into the project s 0.0 Base Maps folder when the project is initiated and will be referenced in as the existing conditions. Consultants can obtain a current copy of the Base Map files by requesting them from the Project Manager/Engineer. All GIS attributes are accessible by using Bentley Map. Read-only imodels can also be made available upon request. PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-4

52 File Naming Convention (Model and Sheet Files) There are seven defined file name data fields which make up a file name: Project Designator (P) Drawing Number provided by the POLB Record Center 8 Characters including dash - Required Facility Code (F) 2 Characters Required Discipline Code (D) 1 Character Required Major Discipline Code (M) 2 Characters Required Minor Discipline Code (N) 2 Characters - Required CADD file Type designator (C) 1 Character - Required Sequence Code (U) 3 Characters Required To help make this clearer, we will build the file name based on an example project. The Project Designator will be and the file will be a water main so the facility will be 00. The Discipline designator is Civil, the major code is Water, minor code is a Plan and the sequence code will indicate that this is the first of three similar sheets. Example CAD file name: C-WT-PL-S-001.dgn Data fields are separated from adjacent fields by a dash ( - ) for clarity. All characters in any of the fields are always capitalized. The layout is as follows: P P - P P P P P - F F - D - M M - N N - C - U U U.dgn Project Designator, Character 1-8 The Project Designator field provides 8 characters allocated for the numeric Drawing Number as designated by the POLB Record Center. The project number does not have to fill all the fields. For instance if the Drawing Number is , then the project number field would look like: F F - D - M M - N N - C - U U U.dgn PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-5

53 Facility Code, Characters 10 and 11 Each facility in the project will have a project specific code. Examples include individual buildings, roads and bridges. The codes will be numeric such as 01, 02, 03, 04, 05, etc. If the model file or sheet file spans all facilities, use the facility code of D - M M - N N - C - U U U.dgn Discipline Designator, Character 13 The following table displays the Discipline Designator codes for each Discipline. This field is required for all model files. For the drawing names, we will be using the 1 character discipline designators. In our example, we are designing a water line so this would be C for Civil C - M M - N N - C - U U U.dgn Character Discipline Examples: A Architectural Floor plans (uncommon - See Appendix C for detailed coding) B GIS As-builts, Leases and Maps C Civil Plans, Profiles, Grading E Electrical Plans, Isometric, Details G General Borders, Title Sheets, Project Location M Mechanical R Railroad Rail Plans, Profiles S Structural Bridges, Structures, Wharfs T Telecommunications Telephone, Fiber, Coax V Surveying/Mapping As-Builts, Survey, Lidar, Hydrographic X Miscellaneous Not defined PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-6

54 Major Discipline Code, Characters 15 and 16 The major discipline code designates the category of file that the DGN represents. This field is required. The following table displays the Major Discipline codes per Discipline. The Discipline IDs are only used to order the sheets in a plan set; they are not used in the file name and not all ID s listed will be used in every plan set. Continuing in building our example, we show the Major Discipline as Water C - W T - N N - C - U U U.dgn Discipline Discipline ID Major Discipline Code Description G (General) 010 TT Cover - Title Sheet / Project Location G (General) 020 IN Sheet Index G (General) 030 AB Abbreviations G (General) 040 NO Notes, Legends and Symbols G (General) 050 GN Project Work Areas/Site Plan/Contractor Lay down area G (General) 060 TP Access and Traffic Plan G (General) 070 FA Fire Access Plan G (General) 080 CS Construction Sequence/Phasing Plan G (General) 090 CC Coordinate Control Map and Bench Mark C (Civil) 100 EC Erosion Control C (Civil) 110 BL Boring Log/ Pot Hole C (Civil) 120 CO Contaminated Soil C (Civil) 130 HZ Hazmat C (Civil) 140 DM Demolition C (Civil) 150 DR Dredging/Excavation/Fill C (Civil) 160 SD Storm Drain PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-7

55 Discipline Discipline ID Major Discipline Code Description C (Civil) 170 SS Sanitary Sewer C (Civil) 180 WT Water E (Electrical Site) 190 EL Electrical (For Building Projects) E (Electrical Site) 200 TL Telecommunication (For Building Projects) A (Architectural) Architectural (See Appendix B for details) C (Civil) 290 UT Other Utilities S (Structural) 300 ST Building S (Structural) 310 BR Bridge S (Structural) 320 WF Wharf S (Structural) 330 MS Miscellaneous R (Railroad) 340 RR Railroad R (Railroad) 350 TM Train in Motion R (Railroad) 360 CA Compressor Air R (Railroad) 370 DT Track Construction Details C (Civil) 400 RD Roadway C (Civil) 410 GP Grading/Paving C (Civil) 420 PV Paving C (Civil) 430 GR Grading C (Civil) 440 SR Striping C (Civil) 450 SP Striping and Signage C (Civil) 460 FN Fencing C (Civil) 470 SF Striping/Fencing C (Civil) 480 SN Traffic Sign PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-8

56 Discipline Discipline ID Major Discipline Code Description C (Civil) 490 TC Traffic Control C (Civil) 500 TD Detour C (Civil) 510 TS Traffic Signal C (Civil) 520 TE Traffic Electrical C (Civil) 530 LP Landscape C (Civil) 540 IR Irrigation X (Miscellaneous) 580 RS Resource V (Survey/Mapping) 590 SV Survey X (Miscellaneous) 600 ZZ Contractor/Shop Drawing X (Miscellaneous) 610 PR Process PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-9

57 Minor Discipline Code, Characters 15 and 16 The minor discipline code designates the sub-category of file that the DGN represents. This field is a required field. The following table displays the Minor Discipline codes. The Minor Disciplines are mutual for all Major Discipline categories C - W T - P L - C - U U U.dgn Minor Discipline Code AL CP DT EL IS MD MS PF PL PP XS Minor Discipline Alignment Construction Phasing Detail Elevation Isometric Multi Discipline Miscellaneous Profile Plan Plan and Profile Cross Section PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-10

58 CADD File Type Designator, Character 21 The CADD file type designator will be either a value of D for a data file, M for a model file or S for a sheet file C - W T - P L - S - U U U.dgn Sequence Number, Characters For most Model Files, the sequence number will be 001. Certain Model Files such as Traffic Control may have more than one file and therefore more than one sequence number (ie. 001 for Phase 1, 002 for Phase 2, etc.) For Sheet Files, the sequence number represents the number of a sheet within a set of similar sheets (ie. a series of consecutive plan/profile sheets). The sequence number is for CADD file identification only and is not related to the sheet number in the entire project set C - W T - P L - S dgn Sheet Set Layout The primary scale for POLB plan sheets is 1 =40. The sheets shall be organized within the plan set by Discipline ID as described earlier in this section on page 8-7. PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-11

59 File Naming Convention (Base Maps) The following table shows the standard file naming convention to be used on the current Base Maps that are extracted from the POLB Enterprise GIS and stored in the folder 0 Base Maps. File Name Basemap_Contours.dgn Basemap_Detail.dgn Basemap_Striping.dgn Vicinity_Map.dgn Utility_Gas_LBGO_LBGO_NAD83_1991.dgn Utility_Sewer_NAD83_1991.dgn Utility_Stormwater_NAD83_1991.dgn Utility_Water_NAD83_1991.dgn Utility_Communication_NAD83_1991.dgn Utility_Electric_NAD83_1991.dgn Utility_Fiber_Optic_NAD83_1991.dgn Lease_Boundary.dgn Utility_Oil.shp Utility_Oil.dbf Utiltity_Transmission.dgn Transportation_Railroad.dgn Transportation_Road.dgn Facility_Port.dgn Structure.dgn Cathodic_Protection.dgn Description Aerial Photogrammetry - Contours Aerial Photogrammetry Aerial Photogrammetry - Striping Port Vicinity Map for Project Location Natural Gas lines Obtained from Long Beach Gas and Oil Sanitary sewer lines Storm water lines Water lines Communication lines Electric lines (Prior Approval Required) Fiber Optic Network Property, right-of-way, and lease lines Oil Lines - ESRI SHP files are obtained from other sources and are not maintained by POLB. (Not Provided by POLB) Transmission lines and Overhead lines (Not Provided by POLB) Railroads (Not Provided by POLB) Roadways (Not Provided by POLB) Wharf facilities (Not Provided by POLB) Structures (Not Provided by POLB) Cathodic protection features The maps will be copied, not referenced, from pw:\0 Base Maps\ into the project folder 0.0 Base Maps at the kick-off of each project. Use the saved view named POLB to create location map sheets. PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-12

60 File Naming Convention (InRoads and other non-cadd data files) The InRoads/data file naming standard is different than the CADD file naming convention. There are 4 defined file name data fields, which make up a file name: Project Designator (P) Either a Survey or Design Project number (Capital, Spec, Maintenance, Real Estate, or Survey Request) Example: HA1324, S2233, HB5330, SR10168 Discipline Designator (D) currently 1 Character. This refers to the owner or creator of the surface, not the type or content of the surface. Examples: Civil = C, Survey = V, Structural = S, Rail = R (Refer to the section entitled Discipline Designator, Character 13 on page 8-6 for a complete list of available discipline codes). Data Type (T) This shows whether this data is existing or design, or for other purposes. X = Existing, D = Design, B = Contains both existing & design data, O = Other Content Descriptor (C) These are flexible, user-defined characters that describe the InRoads/data file content. Between 1 to 8 characters can be used. This descriptor should help someone understand the file content. Examples: RD-ALT1, RD-ALT2, TEMP1, TEMP2, FINAL, UTILS, ROW, ELEC, SITE1, RAMP, FIN-7, SUBBASE, SUBGRADE, AREA1, AREA2, EX-LOW-9, GIRDER, RAIL-G, PIER-T, NORTH, NW-AREA, STAGE1, RD-LFT, RD-RT, DRAINAGE, PENTABLE Note: Full descriptions should also be added to the InRoads file that will be readable from within InRoads, and another from within ProjectWise. Code fields are separated from adjacent fields by a dash ( - ) for clarity. All characters in any of the fields are always capitalized. The layout is as follows: P P P P P P P P - D - T - C1 C2 C3 C4 C5 C6 C7 C8.ext Examples: Demo Design Surface, Alt 1 H A C - D - D E M O - A 1.DTM Demo Design Surface, Alt 2 H A C - D - D E M O - A 2.DTM Existing Underground Utilities H A C - X - U T I L S - E X.DTM Proposed Electric Main Line Geo S C - D - E L E C M A I N.ALG Fieldbook for Harbor Blvd East H B V - X - H A R B L V D E.FWD Ex. Geometry, Harbor Blvd East H B V - X - H A R B L V D E.ALG Existing Surface, Pier G Rail yard S R V - X - P I E R G - R R.DTM Structural Bridge Girder Layout H A S - D - B R - G R D R S.ALG Load all InRoads Project Data H B C - B - L O A D - A L L.RWK PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-13

61 PROJECT ORGANIZATION AND FILE NAMING CONVENTION Page 8-14

62 9. LEVEL ASSIGNMENTS Introduction This chapter explains the use of levels in both the model and the sheet files, the conventions used to name levels, and the use of referenced model files in the creation of the sheet files. Levels Defined The information represented by individual levels is grouped into two primary types: model-specific information and sheet-specific information. Model-specific information includes site, roads, buildings or other objects depicting existing and/or proposed conditions. This information is often shared among drawings. Examples include utilities, roads, retaining walls, bridges, illumination, drainage, signing, rail yard layouts, etc. Model-specific information may be either literal (e.g., curbs, walls) or symbolic (e.g., manholes, light poles). Sheet-specific information may include notes, annotative symbols, and titles. This type of information is usually not shared between drawings. Level Naming Conventions The level is the basic tool used in CADD for managing graphic information. The levels defined within these standards are based on the recommendations set forth by the American Institute of Architects (AIA) in the 2007 AIA CADD Layer Guidelines: U.S. NCS Version 4.0, with modifications for use on Port projects. This manual uses the AIA method for level naming consisting of the following: C - XXXX - XXXX - XXXX Minor Group 2 Code (4) Characters (e.g., MAJR for Major Contour Lines, MINR for Minor Contour Lines) Minor Group 1 code (4) Characters (e.g., PROF for Profile, GRID for Gridlines) Major Group Code (4) Characters (e.g., STRM for STORM DRAIN, ROAD for Road) Discipline Code (1) Character (e.g., C for Civil, A Architectural) LEVEL ASSIGNMENTS Page 9-1

63 The level assignment tables in Chapters 12 through 29 include: The levels assigned to each discipline. The level number assigned to each level. The level name assigned to each level. A detailed description of each level. The line style, weight, and color associated with each level. LEVEL ASSIGNMENTS Page 9-2

64 Filters Filters are a method of grouping levels together to make it easier to view levels only related to a specific purpose or discipline. POLB standard Level Filters reside in Filters_POLB_Levels.dgnlib. The filters have been broken out as follows: Other Level Filters may be added to individual DGN files. No naming convention has been established. LEVEL ASSIGNMENTS Page 9-3

65 LEVEL ASSIGNMENTS Page 9-4

66 10. DRAFTING STANDARDS Introduction This chapter identifies basic drafting standards used in creating construction documents for POLB projects. When possible, these standards have been pre-established in POLB Seed Files and/or the POLB Workspace. DGN Libraries (DGNLIBS) The basic philosophy for the DGNLIBS at POLB is to separate out the level definitions for each discipline of interest and then to define common DGNLIBS for text styles, shared levels, tasks, linestyles and dimension styles. POLB will be using the following DGNLIBS in its configuration and setup. Standard DGNLIBS shall not be altered without prior consent of the POLB CADD Manager (see form on page 1-3). DGNLIB Name POLB GUI.dgnlib <X>_POLB_Levels.dgnlib ANNO_POLB_Levels.dgnlib Filters_POLB_Levels.dgnlib POLB Linestyles.dgnlib POLB Styles.dgnlib <user>.dgnlib Description Contains POLB MicroStation interface customizations (menus and tasks). Contains POLB level definitions for each discipline, where <X> is the discipline code. Contains POLB level definitions for each annotation levels for all disciplines. Contains the common POLB level filter definitions. (future) Will contain POLB linestyles. Currently, the linestyles are contained in a file called POLB Styles.rsc. Contains POLB text styles and dimension styles. User specific dgnlib. This is set aside for users that wish to add tasks and make GUI changes that are not defined in the GUI dgnlib. This is not to be used to define additional layers, linestyles, dimension styles or text styles. See CADD Manager for more details. Graphic Attributes In general, the graphic attributes are defined as ByLevel attributes and include line weight, line style and color. This section offers additional information for the choices made. DRAFTING STANDARDS Page 10-1

67 DRAFTING STANDARDS Page 10-2

68 DRAFTING STANDARDS Page 10-3

69 Linestyles The linestyles included in the POLB Workspace are a combination of linestyles adopted from Caltrans and custom linestyles developed at POLB. All linestyles will be drawn at 1 =1 inside model files. If necessary, the linestyles will then be scaled up in the sheet files using the active linestyle scale. The following tables show the linestyles included in the POLB Workspace as well as the scale required to place the linestyle at 1 =1. Caltrans Styles DRAFTING STANDARDS Page 10-4

70 POLB Styles (1 of 4) DRAFTING STANDARDS Page 10-5

71 POLB Styles (2 of 4) DRAFTING STANDARDS Page 10-6

72 POLB Styles (3 of 4) DRAFTING STANDARDS Page 10-7

73 POLB Styles (4 of 4) DRAFTING STANDARDS Page 10-8

74 Cells The cells included in the POLB Workspace provide symbols for Port drawings. The cells are contained within the following cell libraries: Cell Library Name POLB_Areapat.cel POLB_Cells.cel POLB_Piping.cel POLB_Rail.cel POLB_Sheets.cel POLB_Signs.cel POLB_Signs2.cel POLB_Traffic.cel Description Cells for patterning areas using ANSI standard symbols (not shown) Main cell library containing symbols for a variety of disciplines Cell library that primarily contains cells related to water / piping Cell library that primarily contains cells related to railroads Cell library containing symbols for every sheet, for example scale bars and the north arrow Cell library that primarily contains cells related to signage Secondary cell library containing additional signage cells (not shown) Cell library that primarily contains cells related to temporary road facilities DRAFTING STANDARDS Page 10-9

75 DRAFTING STANDARDS Page 10-10

76 DRAFTING STANDARDS Page 10-11

77 DRAFTING STANDARDS Page 10-12

78 DRAFTING STANDARDS Page 10-13

79 DRAFTING STANDARDS Page 10-14

80 DRAFTING STANDARDS Page 10-15

81 DRAFTING STANDARDS Page 10-16

82 DRAFTING STANDARDS Page 10-17

83 DRAFTING STANDARDS Page 10-18

84 DRAFTING STANDARDS Page 10-19

85 DRAFTING STANDARDS Page 10-20

86 DRAFTING STANDARDS Page 10-21

87 DRAFTING STANDARDS Page 10-22

88 DRAFTING STANDARDS Page 10-23

89 DRAFTING STANDARDS Page 10-24

90 DRAFTING STANDARDS Page 10-25

91 DRAFTING STANDARDS Page 10-26

92 DRAFTING STANDARDS Page 10-27

93 DRAFTING STANDARDS Page 10-28

94 DRAFTING STANDARDS Page 10-29

95 DRAFTING STANDARDS Page 10-30

96 DRAFTING STANDARDS Page 10-31

97 DRAFTING STANDARDS Page 10-32

98 DRAFTING STANDARDS Page 10-33

99 Text Attributes The following are guidelines for the application of text strings and text nodes on all construction documents. POLB uses MicroStation Text Styles to maintain consistency within POLB projects. Fonts The approved CADD font for all construction documents is Engineering (FT=3). The text width will always be 0.8 x the text height. The annotation scale will be applied to the base size to create the actual size on the sheet. However, for certain conditions such as presentation graphics, titles, and sheet numbers, other fonts may be more desirable. Text Styles (ANSI A 8-1/2 x 11) Name Description Weight Text Height (in) Line Spacing Justification POLB_ANSIA_Background Text with background to mask elements underneath Left-Top POLB_ANSIA_InRoads_Survey Survey points POLB_ANSIA_Matchline Match Lines Center- Center Center- Bottom POLB_ANSIA_Schedule POLB_ANSIA_Standard Text in tables and schedules General notes, standard text, dimensions, callouts Left-Center Left-Center POLB_ANSIA_Title_ POLB_ANSIA_Title_2 Subtitles POLB_ANSIA_Title_3 Titles Center- Center Center- Center Center- Center DRAFTING STANDARDS Page 10-34

100 Text Styles (ANSI D 22x34 or larger) Name Description Weight Text Height (in) Line Spacing Justification POLB_ANSID_Background Left-Top POLB_ANSID_InRoads_Design POLB_ANSID_InRoads_Design_Background Center- Center.5 Center- Center POLB_ANSID_InRoads_Design_LJ Left-Center POLB_ANSID_InRoads_Design_RJ POLB_ANSID_InRoads_Grid Right- Center.5 Center- Center POLB_ANSID_Matchline Match Lines Center- Bottom POLB_ANSID_Schedule POLB_ANSID_Standard Text in tables and schedules General notes, standard text, dimensions, callouts Left-Center Left-Center POLB_ANSID_Title_ POLB_ANSID_Title_2 Subtitles POLB_ANSID_Title_3 Titles Center- Center Center- Center Center- Center DRAFTING STANDARDS Page 10-35

101 Text Orientation Leader Lines Leader lines shall be created using the Place Note command in MicroStation and are typically placed with a weight of 0. Use the appropriate dimension style as shown in the Dimension Attributes section. Terminators The approved line terminator for notes on all construction documents is the standard filled terminator in the dimension settings. The size of the filled terminators is a width of 0.5 and length of 1.5 times the text height. Dimension Attributes The following are guidelines for the application of dimensions on all construction documents. In general, these settings have been pre-established in POLB DGN Libraries. Terminators The approved line terminator for dimensions on all construction documents is the standard filled terminator in the dimension settings. The size of the filled terminators is a width of 0.5 and length of 1.5 times the text height. Dimensioning Dimensions shall be placed with a justification of Center-Bottom. Line spacing shall be at least 1/2 of the overall height of the capitalized font. Text will be placed above the dimension line. If two lines of text are required on the dimension, the second line of text may be placed below the dimension line. When using the dimension tools, use semi-automatic mode with association turned on. In general, do not edit dimension text. Dimension Styles The following table shows the dimension styles available in POLB Workspace. DRAFTING STANDARDS Page 10-36

102 Dimension Styles DRAFTING STANDARDS Page 10-37

103 Border Files Use the following guidelines for Border Sheets on all construction documents: Border Sheets Border files are referenced to the Sheet File with the appropriate Border Base File based on the chart below. Use the sizes that are shaded for work performed for POLB. The Border Sheet reference files are scaled per the plot scale of the Sheet File. ANSI Letter ANSI Inches ARCH Letter ARCH Inches File Name A 8.5 X 11.0 A 9.0 X 12.0 POLBBDR8511.DGN B 11.0 X 17.0 B 12.0 X 18.0 C 17.0 X 22.0 C 18.0 X 24.0 D 22.0 X 34.0 D 24.0 X 36.0 POLBBDR2234.DGN E 34.0 X 44.0 E 30.0 X 42.0 Border Saved Views When referencing the border file, use one of the following saved views: Saved View Name Description When to Use BDR_PLAN Plan View Plan Sheets, Detail Sheets, etc. BDR_PLAN_PROFILE Plan and Profile View Plan and Profile Sheets BDR_PROFILE Full Profile View Sheets with Profile Only DRAFTING STANDARDS Page 10-38

104 Title Blocks Title block cells contain tags linked to ProjectWise and are placed in the border from POLB cell libraries. The title block cells are scaled to the same value as the reference border sheet with the insertion point being the lower right hand corner of the border sheet. Once placed, title blocks are automatically updated as properties are changed inside ProjectWise. Title blocks may be updated two ways: 1. If using ProjectWise Select the file and then press the spacebar to open the Properties dialog. Go to the Attributes tab and update the title block information. Click Save, then Close. The title block information will be updated in the DGN the next time the DGN is opened. 2. Inside MicroStation keyin: titleblock modify or select in the Port of Long Beach menu. Update the information in the Attributes tab. Click Save, then Close. The tagged information is updated inside the DGN. DRAFTING STANDARDS Page 10-39

105 Title Block Seal Frame The title block area designated as the seal frame can be expanded to accommodate two seals. This is done by turning off the G_ANNO_TTLB_1 Level and turning on the G_ANNO_TTLB_2 Level. G_ANNO_TTLB_1 The diagram above shows the standard title bock configuration with the G_ANNO_TTLB_1 Level turned on and the G_ANNO_TTLB_2 Level turned off. This layout should be used when placing a single seal in the title block. G_ANNO_TTLB_2 The diagram above shows the standard title bock with the G_ANNO_TTLB_1 Level turned off and the G_ANNO_TTLB_2 Level turned on to expand the area for the placement of seals. This layout should be used when placing a two seals in the title block. DRAFTING STANDARDS Page 10-40

106 Consultants Logo Location Consultant Border Sheet The Consultant border file contains the same basic layout as the internal POLB border with the addition of a location for the Consultant s logos. The space in the upper-right corner of the title block is reserved for the Consultant s logo. All consultant logos must fit inside this designated location indicated by the figure on this page. Inserting and Updating the Title Block Consultants must use the same POLB_TTLB cell inserted into the lower right hand corner of the border sheet to place the title block tags in the drawing. The automatic updating of title block attributes will not be available if the drawing is not in ProjectWise. However, the Edit Tags command in MicroStation can be used to edit the values of the title block attributes. The Edit Tags command can be started by selecting the command from the Tags Tool Box or keying in the command Edit Tags in the MicroStation Key-in browser. Select one of the title block tags and the Edit Tags dialog will appear. From here, you can enter the desired values of the different title block attributes and then select OK when finished. DRAFTING STANDARDS Page 10-41

107 Logical Names Logical names will be assigned to reference file attachments to control the display while plotting. The following list shows the logical names used by POLB. POLB Standard Logical Names File Name Logical Name Output Color 1. *.dgn BDR As Displayed 1. *.dgn Grey1-* (Files will be RGB Color 96 ) 1. *.dgn Grey2-* (Files will be RGB Color 128 ) 1. *.dgn Grey3-* (Files will be RGB Color 160 ) DRAFTING STANDARDS Page 10-42

108 Reference Attachments Model files and the border file will be attached to a sheet file without saving the full path to the reference. The default settings for POLB attachments are as follows: Raster and PDF Attachments Raster files and PDFs may be attached to DGNs via Raster Manager. POLB Aerials are available in the folder 1 Rasters for reference and background usage. All raster attachments shall be placed on the G_RAST level for added flexibility. Symbols Sheet File symbols such as North Arrows, Seals (if allowed by profession), and Graphic Scales are placed in the Sheet File. Standard symbols are stored in POLB cell libraries. DRAFTING STANDARDS Page 10-43

109 Level Overrides Level overrides allow the user to change the way MicroStation displays active file and reference file levels without changing the actual attributes of each element. Level overrides will not affect printing when using IPLOT settings. Level override view display is off by default in POLB seed files. Level overrides prove useful when displaying the base maps in the background using a grey color. Adding a color to the overrides for a reference file proves useful when comparing files. Another way to use level overrides is to apply them to references from adjacent projects that are in close proximity to the current project. View Display Attributes The POLB Seed 2D and POLB Seed 3D files have the following view display attributes set: OLE Object Links Links from Excel into MicroStation are not supported by the POLB Workspace. Digital Signatures / Digital Rights Digital signatures and digital rights are currently not being accepted on POLB projects. DRAFTING STANDARDS Page 10-44

110 11. ELECTRONIC FILE TRANSFER Introduction This chapter identifies the requirements for electronic file transfers. It includes details regarding which files are required for the transfers, and the methods and media to be used in the transfer process. The intent of this electronic file transfer is to provide a complete archive of the entire project for retention requirements and future use, as well as an update of base map information required for inclusion into the POLB GIS. Please refer to the Consultant Deliverable Guideline Document for more information regarding the delivery of electronic files to POLB. Contents The consultant will include in the file transfer the following: Sheet Files - Design files that represent each sheet in the project drawing set including all reference files used in the development of the design files. Model Files - Design files representing any changes to POLB Master Maps as a result of the project in question. Resource Files - Any resource and configuration files (i.e., font resources, pen tables, and seed files) necessary for the use and production of the project design files. Format All files must meet the software and file format requirements detailed in Chapters 2 and 3, and must be delivered in the directory structure described in Chapter 8. Media All file transfers are to be written to a 650MB Recordable Compact Disc or DVD compatible with a standard FAT or NTFS file system. Files are to be placed on the CD or DVD uncompressed in the file format specified in these standards. The CD or DVD shall be delivered in a standard jewel case. The case and the CD or DVD shall be appropriately labeled. Before a file is recorded onto the delivery media, the following procedures should be performed: Remove all extraneous graphics outside the border area, and set the active parameters to a standard setting or to those settings stored in the seed file. Remove any nested reference attachments. Make sure all reference files are attached without device or directory specifications. Include all files, both graphic and non-graphic, required for the project (color tables, pen tables, user command files, plot files, etc.). Include any standard sheets (abbreviation sheets, standard symbol sheets, etc.) necessary to reproduce a complete project. ELECTRONIC FILE TRANSFER Page 11-1

111 ELECTRONIC FILE TRANSFER Page 11-2

112 12. ANNOTATION LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of annotation for all disciplines for POLB. The asterisk denotes the discipline character. Annotation levels may be used for any discipline. The annotation levels make up the first eight numbers of each discipline. All annotation levels are found in ANNO_POLB_Levels.dgnlib. Text styles may be found in Chapter 10 Drafting Standards. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority XXX0 *_ANNO_DIMS Witness/extension lines, dimension terminators, dimension text - Text should be weight /2 XXX1 *_ANNO_KEYN Reference keynotes with associated leaders XXX2 *_ANNO_NOTE General notes and general remarks XXX3 *_ANNO_NPLT Non-plotting graphic information XXX4 *_ANNO_PATT Patterning, poche, shading, and hatching XXX5 *_ANNO_RDME Read-me information XXX6 *_ANNO_SYMB Miscellaneous symbols XXX7 *_ANNO_TEXT Miscellaneous text and callouts with associated leaders ANNOTATION LEVEL PROPERTIES Page 12-1

113 ANNOTATION LEVEL PROPERTIES Page 12-2

114 13. GENERAL LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of General sheet files and base files for POLB. The levels are found in G_POLB_Levels.dgnlib. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority 7008 G_ANNO_GRID_BOTT Border: Plan and Profile Gridlines G_ANNO_GRID_MAJR Annotation: Grid: Major G_ANNO_GRID_MINR Annotation: Grid: Minor G_ANNO_LEGN Annotation: Legend, symbol keys G_ANNO_LINE Annotation: Lines G_ANNO_MATC Annotation: Match lines G_ANNO_TICK Annotation: Tick marks G_ANNO_TTLB Border: Titleblock G_ANNO_TTLB_1 Border: Single Engineering Seal Frame G_ANNO_TTLB_2 Border: Dbl Eng. Seal Frame GENERAL LEVEL PROPERTIES Page 13-1

115 Number Name Description Color Linestyle Weight Transparency Priority 7018 G_ANSIA Border: ANSI A Sheet Limits G_ANSID Border: ANSI D Sheet Limits G_ARCHD Border: ARCH D Sheet Limits G_AXIS_LABL_BOTM 7022 G_AXIS_LABL_LEFT 7023 G_AXIS_LABL_RGHT 7024 G_AXIS_LINE 7025 G_AXIS_TITL_BOTM 7026 G_AXIS_TITL_LEFT 7027 G_AXIS_TITL_RGHT Cross-section/Profile Axis Lines: Labels: Bottom Cross-section/Profile Axis Lines: Labels: Left Cross-section/Profile Axis Lines: Labels: Right Cross-section/Profile Axis Lines: Lines Cross-section/Profile Axis Lines: Drawing or detail titles: Bottom Cross-section/Profile Axis Lines: Drawing or detail titles: Left Cross-section/Profile Axis Lines: Drawing or detail titles: Right G_MARK_GRID Border: Grid for Markup Usage G_RAST Raster Images GENERAL LEVEL PROPERTIES Page 13-2

116 14. DETAIL LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of detail sheets for POLB. The levels are found in D_POLB_Levels.dgnlib. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority 4008 D_ANNO_MISC Miscellaneous D_ANNO_PATT_CONC Concrete D_ANNO_PATT_ERTH Earth D_ANNO_PATT_GRVL Gravel D_ANNO_PATT_SOIL Soil D_ANNO_PATT_STEL Steel D_ELEC_SLDG Electrical Single Line Diagram D_LINE_CENT Centerlines D_LINE_GEOM Geometry D_LINE_HIDD Hidden Lines D_LINE_SECT Section Lines DETAIL LEVEL PROPERTIES Page 14-1

117 Number Name Description Color Linestyle Weight Transparency Priority 4019 D_REIN_RBAR Rebar D_ROAD_MRKG Striping D_TABL_LINE Table Lines D_TABL_TEXT Table Text DETAIL LEVEL PROPERTIES Page 14-2

118 15. ARCHITECTURAL LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Architectural sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details ARCHITECTURAL LEVEL PROPERTIES Page 15-1

119 Page 15-2

120 16. CIVIL LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Civil sheet files and base files for POLB. The levels are found in C_POLB_Levels.dgnlib. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority 3008 C_ANNO_GRID_COOR 3009 C_ANNO_GRID_DATM 3010 C_ANNO_GRID_ELEV 3011 C_ALGN_COMM Annotation: Grid: Coordinate Annotation: Grid: Datum Annotation: Grid: Elevation Alignment: Communications ut_comm C_ALGN_DATA Alignment: Data C_ALGN_ELEC 3014 C_ALGN_ELMT_TABL Alignment: Electrical Alignment: Element: Data tables 3 ut_elec C_ALGN_EVNT Alignment: Event CIVIL LEVEL PROPERTIES Page 16-1

121 Number Name Description Color Linestyle Weight Transparency Priority 3016 C_ALGN_GAS~ Alignment: Gas 52 ut_gas C_ALGN_GENL 3018 C_ALGN_HORZ Alignment: General Alignment: Horizontal C_ALGN_LINE Alignment: Lines C_ALGN_PONT_TABL 3021 C_ALGN_SSWR 3022 C_ALGN_STAN_MAJR 3023 C_ALGN_STAN_MINR 3024 C_ALGN_STAN_TICK 3025 C_ALGN_STRM Alignment: Point: Data tables Alignment: Sanitary sewer Alignment: Stationing: Major Alignment: Stationing: Minor Alignment: Stationing: Tick marks Alignment: Storm Sewer ut_sewer ut_stdrain 1 CIVIL LEVEL PROPERTIES Page 16-2

122 Number Name Description Color Linestyle Weight Transparency Priority 3026 C_ALGN_SYMB Alignment: Reference symbols C_ALGN_TEXT Alignment: Text C_ALGN_VERT 3029 C_ALGN_VERT_ANNO 3030 C_ALGN_VERT_HIGH 3031 C_ALGN_VERT_LOWP 3032 C_ALGN_WATR Alignment: Vertical Alignment: Vertical: Annotation Alignment: Vertical: High point Alignment: Vertical: Low point Alignment: Water supply ut_water ut_water C_BORE Borings C_CATH_ANNO Cathodic protection: Annotation CIVIL LEVEL PROPERTIES Page 16-3

123 Number Name Description Color Linestyle Weight Transparency Priority 3035 C_CATH_LINE 3036 C_CATH_PONT 3037 C_CHAN_CNTR 3038 C_CHAN_LIMT 3039 C_CHAN_SLOP_LINE 3040 C_CHAN_TOE~ 3041 C_CHAN_TOPB 3042 C_DTCH_BOTM 3043 C_DTCH_CNTR Cathodic protection: Lines Cathodic protection: Point Navigable channels: Center Navigable channels: Limit Navigable channels: Slope: Lines Navigable channels: Toe of channel Navigable channels: Top of bank Ditches or washes: Bottom Ditches or washes: Center CIVIL LEVEL PROPERTIES Page 16-4

124 Number Name Description Color Linestyle Weight Transparency Priority 3044 C_DTCH_LIMT 3045 C_DTCH_SLOP_LINE 3046 C_DTCH_TOE~ 3047 C_DTCH_TOPB 3048 C_DTM~_ANNO 3049 C_DTM~_BNDY_COOR 3050 C_DTM~_BORE 3051 C_DTM~_BRKL Ditches or washes: Limit Ditches or washes: Slope: Lines Ditches or washes: Toe of channel Ditches or washes: Top of bank Digital terrain model: Annotation Digital terrain model: Boundary: Coordinate Digital terrain model: Borings Digital terrain model: Break lines CIVIL LEVEL PROPERTIES Page 16-5

125 Number Name Description Color Linestyle Weight Transparency Priority 3052 C_DTM~_BRKL_INFD 3053 C_DTM~_COOR 3054 C_DTM~_CTUR 3055 C_DTM~_CTUR_COOR 3056 C_DTM~_EXTR 3057 C_DTM~_FTUR_COOR 3058 C_DTM~_GRND_EXST Digital terrain model: Break lines: Inferred Digital terrain model: Coordinate Digital terrain model: Contour breakline Digital terrain model: Contour breakline: Coordnate Digital terrain model: Exterior Digital terrain model: Feature: Coordinate Digital terrain model: Ground: Existing to remain CIVIL LEVEL PROPERTIES Page 16-6

126 Number Name Description Color Linestyle Weight Transparency Priority 3059 C_DTM~_GRND_PROP 3060 C_DTM~_HING 3061 C_DTM~_INTR 3062 C_DTM~_MAJR 3063 C_DTM~_MAJR_ANNO 3064 C_DTM~_MAJR_DEPR 3065 C_DTM~_MINR 3066 C_DTM~_MINR_ANNO Digital terrain model: Ground: New work Digital terrain model: Hinge point Digital terrain model: Interior Digital terrain model: Major Digital terrain model: Major : Annotation Digital terrain model: Major : Depression Digital terrain model: Minor Digital terrain model: Minor : Annotation v_depression_line CIVIL LEVEL PROPERTIES Page 16-7

127 Number Name Description Color Linestyle Weight Transparency Priority 3067 C_DTM~_MINR_DEPR 3068 C_DTM~_MMTC 3069 C_DTM~_NULL 3070 C_DTM~_PMTR 3071 C_DTM~_PONT 3072 C_DTM~_RIDG 3073 C_DTM~_RTWL 3074 C_DTM~_SCUT 3075 C_DTM~_SLOP Digital terrain model: Minor : Depression Digital terrain model: Mismatched elevation Digital terrain model: Null point Digital terrain model: Perimeter Digital terrain model: Point Digital terrain model: Ridgeline Digital terrain model: Retaining wall Digital terrain model: Sawcut Digital terrain model: Slope 4 v_depression_line CIVIL LEVEL PROPERTIES Page 16-8

128 Number Name Description Color Linestyle Weight Transparency Priority 3076 C_DTM~_SLOP_ANNO 3077 C_DTM~_SLOP_BNCH 3078 C_DTM~_SLOP_CUT~ 3079 C_DTM~_SLOP_FILL 3080 C_DTM~_SLOP_TOPT 3081 C_DTM~_SLOP_TRAV 3082 C_DTM~_SPOT Digital terrain model: Slope: Annotation Digital terrain model: Slope: Bench Digital terrain model: Slope: Cut line Digital terrain model: Slope: Fill and cover material Digital terrain model: Slope: Top toe of slope Digital terrain model: Slope: Transverse Digital terrain model: Spot elevations CIVIL LEVEL PROPERTIES Page 16-9

129 Number Name Description Color Linestyle Weight Transparency Priority 3083 C_DTM~_TRGL 3084 C_DTM~_XBRK 3085 C_DTM~_XING Digital terrain model: Triangle Digital terrain model: Crossing breaklines Digital terrain model: Crossing point C_FENC Fences 10 rd-fence C_GAS~_CAPS Gas: Cap C_GAS~_DEVC Gas: Devices C_GAS~_LINE Gas: Lines 52 ut_gas C_GAS~_METR Gas: Meter C_GAS~_RDCR Gas: Reducer C_GAS~_RISR Gas: Risers C_GAS~_TANK Gas: Storage tanks C_GAS~_TSTB Gas: Tee stubout C_GAS~_VALV Gas: Valves CIVIL LEVEL PROPERTIES Page 16-10

130 Number Name Description Color Linestyle Weight Transparency Priority 3096 C_GAS~_VENT Gas: Vents C_GAS~_VERT_BEND 3098 C_GAS~_XING Gas: Vertical: Bend Gas: Crossing point C_LEVE_CNTR Levee: Center C_LEVE_OTLN Levee: Outline C_LEVE_TOE~ 3102 C_LEVE_TOPB Levee: Toe of channel Levee: Top of bank C_PRKG Parking lots C_PROP_BNDY_OWNR 3105 C_PROP_BNDY_POLB Property boundary: Boundary: Owner Property boundary: Boundary: Port of Long Beach 12 v_property_line 0 12 map_port_bndy_line 0 CIVIL LEVEL PROPERTIES Page 16-11

131 Number Name Description Color Linestyle Weight Transparency Priority 3106 C_PROP_ESMT 3107 C_PROP_LEAS 3108 C_PROP_RWAY Property boundary: Easement Property boundary: Lease Property boundary: Rightof-way 12 v_right_of_way 0 12 map_leasecirc 0 12 v_right_of_way C_RAIL_BUMP Railroad: Bumper C_RAIL_CNTR Railroad: Center C_RAIL_CRAN Railroad: Crane C_RAIL_SGNL Railroad: Signal C_RAIL_SWCH Railroad: Switches C_RAIL_TRAK Railroad: Track C_ROAD_ASPH Roadways: Asphalt C_ROAD_BARR Roadways: Barrier C_ROAD_BASE Roadways: Base course CIVIL LEVEL PROPERTIES Page 16-12

132 Number Name Description Color Linestyle Weight Transparency Priority 3118 C_ROAD_CNTR Roadways: Center C_ROAD_CONC 3120 C_ROAD_CRSH Roadways: Concrete Roadways: Crash Cushions C_ROAD_CURB Roadways: Curb C_ROAD_CURB_BACK 3123 C_ROAD_CURB_FLOW 3124 C_ROAD_CURB_GUTR_LIP~ 3125 C_ROAD_CURB_TOP~ 3126 C_ROAD_DRAN 3127 C_ROAD_ELEC 3128 C_ROAD_EOP~ Roadways: Curb: Back of Curb Roadways: Curb: Flowline of Curb Roadways: Curb: Lip of Gutter Roadways: Curb: Top of Curb Roadways: Drainage slope indications Roadways: Electrical Lighting Roadways: Edge of pavement CIVIL LEVEL PROPERTIES Page 16-13

133 Number Name Description Color Linestyle Weight Transparency Priority 3129 C_ROAD_GRAL Roadways: Guard rail 3 rd-mbgr-p C_ROAD_GRVL Roadways: Gravel C_ROAD_MRKG 3132 C_ROAD_MRKG_DASH Roadways: Pavement Markings and Striping Roadways: Striping (Dashed) rd-lnstrpdsh C_ROAD_SGNL Roadways: Signals C_ROAD_SHLD 3135 C_ROAD_SIGN 3136 C_ROAD_SUBB 3137 C_ROAD_SWLK Roadways: Shoulder Roadways: Signage Roadways: Subbase Roadways: Sidewalks : Back of Sidewalk CIVIL LEVEL PROPERTIES Page 16-14

134 Number Name Description Color Linestyle Weight Transparency Priority 3138 C_ROAD_TEMP 3139 C_ROAD_UPVD 3140 C_SITE_BLDG 3141 C_SITE_BLDG_FNDN 3142 C_SITE_BLDG_FTNG 3143 C_SITE_BOTB Roadways: Temporary Pavement Markings and Traffic Control Devices Roadways: Unpaved surface Site: Building Edge or Points Site: Building Foundations Site: Building Footings Site: Bottom of Bank or Slope C_SITE_BRKL Site: Breaklines C_SITE_EDGE_ASPH 3146 C_SITE_EDGE_CONC Site: Edge of Asphalt Pavement Site: Edge of Concrete Pavement CIVIL LEVEL PROPERTIES Page 16-15

135 Number Name Description Color Linestyle Weight Transparency Priority 3147 C_SITE_ENCL 3148 C_SITE_EQPM 3149 C_SITE_FENC_BARB 3150 C_SITE_FENC_LINK 3151 C_SITE_MISC 3152 C_SITE_MRKG 3153 C_SITE_MRKR Site: Equipment Enclosure Site: Equipment or Container Site: Barbed Wire Fence Site: Chain Link Fence Site: Miscellaneous Site Features Site: Pavement Markings Site: Pavement Markers C_SITE_PADS_ASPH Site: Asphalt Pads C_SITE_PADS_CONC Site: Concrete Pads C_SITE_PAVR Site: Unit Pavers CIVIL LEVEL PROPERTIES Page 16-16

136 Number Name Description Color Linestyle Weight Transparency Priority 3157 C_SITE_POND 3158 C_SITE_RAMP Site: Top/Bottom of Detention or Retention Ponds Site: Structural Loading Ramp C_SITE_SIGN Site: Signs C_SITE_SLAB Site: Structural Slab C_SITE_SWLK Site: Sidewalks C_SITE_TOPB 3163 C_SITE_VEGE_BRSL 3164 C_SITE_VEGE_TREE 3165 C_SITE_VEGE_TRLN Site: Top of Bank or Slope Site: Trees, shrubs, and other vegetation Site: Trees, shrubs, and other vegetation Site: Trees, shrubs, and other vegetation map_brush map_treeline 0 CIVIL LEVEL PROPERTIES Page 16-17

137 Number Name Description Color Linestyle Weight Transparency Priority 3166 C_SSWR_CAPS 3167 C_SSWR_CLNO 3168 C_SSWR_LIFT 3169 C_SSWR_LINE 3170 C_SSWR_MHOL 3171 C_SSWR_MHOL_NVRT 3172 C_SSWR_PUMP 3173 C_SSWR_TANK 3174 C_SSWR_TSTB 3175 C_SSWR_VERT_BEND Sanitary sewer: Cap Sanitary sewer: Cleanout Sanitary sewer: Lift station Sanitary sewer: Lines Sanitary sewer: Manhole Sanitary sewer: Manhole: Invert Sanitary sewer: Pump station Sanitary sewer: Storage tanks Sanitary sewer: Tee stubout Sanitary sewer: Vertical: Bend ut_sewer CIVIL LEVEL PROPERTIES Page 16-18

138 Number Name Description Color Linestyle Weight Transparency Priority 3176 C_SSWR_WSTB 3177 C_SSWR_XING 3178 C_STRC_BDNG Sanitary sewer: Wye stub out Sanitary sewer: Crossing point Structural: Bedding C_STRC_FENC Structural: Fences 5 rd-fence C_STRC_RRAP Structural: Riprap C_STRM_CLNO 3182 C_STRM_CLRF 3183 C_STRM_CULV 3184 C_STRM_HWAL Storm sewer: Cleanout Storm sewer: Clarifier Storm sewer: Culvert Storm sewer: Headwall C_STRM_INLT Storm sewer: Inlet C_STRM_LINE Storm sewer: Lines 12 ut_stdrain 1 CIVIL LEVEL PROPERTIES Page 16-19

139 Number Name Description Color Linestyle Weight Transparency Priority 3187 C_STRM_MHOL 3188 C_STRM_OUTF 3189 C_STRM_PUMP 3190 C_STRM_SIGN 3191 C_STRM_SUMP 3192 C_STRM_XING 3193 C_TRAL_CNTR 3194 C_TRAL_EDGE Storm sewer: Manhole Storm sewer: Outfall point Storm sewer: Pump station Storm sewer: Signage Storm sewer: Sump Storm sewer: Crossing point Trails or paths: Center Trails or paths: Edge C_TRCH_CNTR Trench: Center C_TRCH_TOE~ Trench: Toe of channel C_TRCH_TOP~ Trench: Top CIVIL LEVEL PROPERTIES Page 16-20

140 Number Name Description Color Linestyle Weight Transparency Priority 3198 C_WALL Walls 3 rd_wall C_WARF_BERT_ANNO Wharf: Berth: Annotation C_WARF_CABL Wharf: Cable C_WARF_CONC Wharf: Concrete C_WARF_DLPH Wharf: Dolphin C_WARF_DOCK 3204 C_WARF_DOCK_MISC 3205 C_WARF_DOCK_STEP Wharf: Decks, docks, floats, piers Wharf: Decks, docks, floats, piers: Miscellaneous Wharf: Decks, docks, floats, piers: Steps & Ladders C_WARF_FNDR Wharf: Fenders C_WARF_MISC Wharf: Miscellaneous C_WARF_PONT Wharf: Point CIVIL LEVEL PROPERTIES Page 16-21

141 Number Name Description Color Linestyle Weight Transparency Priority 3209 C_WATR_BCFL Water supply: Back of flow C_WATR_CAPS Water supply: Cap C_WATR_FIRE_LINE 3212 C_WATR_HYDT 3213 C_WATR_LINE 3214 C_WATR_LINE_ABND 3215 C_WATR_METR 3216 C_WATR_MHOL 3217 C_WATR_MHOL_NVRT 3218 C_WATR_POST Water supply: Fire protection: Lines Water supply: Hydrants and connections Water supply: Lines Water supply: Lines: Abandoned Water supply: Meter Water supply: Manhole Water supply: Manhole: Invert Water supply: Posts ut_water 1 1 ut_abnd_water CIVIL LEVEL PROPERTIES Page 16-22

142 Number Name Description Color Linestyle Weight Transparency Priority 3219 C_WATR_RDCR 3220 C_WATR_RISR 3221 C_WATR_SHSV 3222 C_WATR_TRST 3223 C_WATR_TSTB 3224 C_WATR_VALT 3225 C_WATR_VALV 3226 C_WATR_VERT_BEND 3227 C_WATR_XING Water supply: Reducer Water supply: Risers Water supply: Ship to shore service Water supply: Thrust block Water supply: Tee stubout Water supply: Vault Water supply: Valves Water supply: Vertical: Bend Water supply: Crossing point CIVIL LEVEL PROPERTIES Page 16-23

143 CIVIL LEVEL PROPERTIES Page 16-24

144 17. PROCESS LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Process sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details PROCESS LEVEL PROPERTIES Page 17-1

145 PROCESS LEVEL PROPERTIES Page 17-2

146 18. ELECTRICAL LEVEL PROPERTIES Introduction This chapter includes level assignments and cell library documentation that supports the development of Electrical sheet files and base files for POLB. The levels are found in E_POLB_Levels.dgnlib. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority 5008 E_DEVC Electrical: Devices E_LINE Electrical: Lines 3 ut_elec E_LITE Electrical: Lighting ELECTRICAL LEVEL PROPERTIES Page 18-1

147 ELECTRICAL LEVEL PROPERTIES Page 18-2

148 19. FIRE PROTECTION LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Fire Protection sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details FIRE PROTECTION LEVEL PROPERTIES Page 19-1

149 FIRE PROTECTION LEVEL PROPERTIES Page 19-2

150 20. HAZARDOUS MATERIALS LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Hazardous Materials sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details HAZARDOUS MATERIALS LEVEL PROPERTIES Page 20-1

151 HAZARDOUS MATERIALS LEVEL PROPERTIES Page 20-2

152 21. INTERIORS LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Interiors sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details INTERIORS LEVEL PROPERTIES Page 21-1

153 INTERIORS LEVEL PROPERTIES Page 21-2

154 22. LANDSCAPE LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Landscape sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details LANDSCAPE LEVEL PROPERTIES Page 22-1

155 LANDSCAPE LEVEL PROPERTIES Page 22-2

156 23. MECHANICAL LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Mechanical sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details MECHANICAL LEVEL PROPERTIES Page 23-1

157 Page 23-1

158 24. OPERATIONS STANDADS Introduction This chapter includes level assignments that support the development of Operations sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details OPERATIONS STANDADS Page 24-2

159 Page 24-1

160 25. PLUMBING LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Plumbing sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details PLUMBING LEVEL PROPERTIES Page 25-2

161 Page 25-1

162 26. EQUIPMENT LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Equipment sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details EQUIPMENT LEVEL PROPERTIES Page 26-2

163 Page 26-1

164 27. RESOURCE LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Resource sheet files and base files for POLB. The levels are not included in any DGN Library. Level Assignments Name Description Color Linestyle Weight Transparency Priority See National CADD Standards for more details RESOURCE LEVEL PROPERTIES Page 27-2

165 Page 27-1

166 28. STRUCTURAL LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Structural sheet files and base files for POLB. The levels are found in S_POLB_Levels.dgnlib. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority S_ACCS_ADIT Adits in galleries and passages S_ACCS_CHAM Chambers S_ACCS_EVTR Elevators S_ACCS_GLRY Galleries, cross overs, trenches, etc S_ACCS_HTCH Hatches S_ACCS_LADD Ladders and ladder safety devices S_ACCS_MHOL Manholes S_ACCS_MISC Miscellaneous access S_ACCS_STRS Stairs S_ACCS_STRS_FRMG Stair framing S_ACCS_TUNL Tunnels STRUCTURAL LEVEL PROPERTIES Page 28-2

167 Number Name Description Color Linestyle Weight Transparency Priority S_ARMR_CRNR S_ARMR_LINR Corner protection, corner cap casting Protective liner (used for walls, culverts, etc.) S_ARMR_MISC Miscellaneous armor S_ARMR_WALL Wall armor S_BEAM_CNTR Beam centerlines S_BEAM_PRIM Continuous beam or primary beam of two-way beam system S_BEAM_RBAR Beam rebar S_BEAM_SECD S_BLDG_OTLN Girders or secondary beams of twoway beam system Structural: Buildings and primary structures: Outline S_BRCG_DIA~ Diagonal bracing S_BRCG_HORZ Horizontal bracing S_BRCG_VERT Vertical bracing S_BRDG_CNTR Structural: Bridge: Center STRUCTURAL LEVEL PROPERTIES Page 28-3

168 Number Name Description Color Linestyle Weight Transparency Priority S_BRDG_OTLN Structural: Bridge: Outline S_COLS_CNTR Column centerlines/working lines S_COLS_PRIM Primary columns S_COLS_RBAR Column rebar S_COLS_SECD Secondary columns S_CONC Elements made of concrete S_CONC_MASN Elements made of Concrete Masonry S_CRAN_HORN Crane Horn S_CRAN_RAIL Crane Rail S_CRAN_STOP Crane Stop S_CRAN_TRCH Crane Trench S_CRAN_VALT Crane Vault S_CURB Structural Curb S_DECK_FLOR Floor deck S_DECK_ROOF Roof deck S_EROS_BARR Vapor/capillary water barriers STRUCTURAL LEVEL PROPERTIES Page 28-4

169 Number Name Description Color Linestyle Weight Transparency Priority S_EROS_GABN Gabions S_EROS_PVMT Slope paving S_EROS_RRAP S_FABR_EMBD Riprap, stone protection, jetties, breakwaters Embedded metals (framing around openings) S_FABR_HOIS Hoist structures S_FABR_HOOK Line hooks, lifting hooks, check posts etc S_FABR_MOOR Mooring bits, chocks, rings S_FABR_PLAT Plates S_FABR_TRSH Trash racks, intake screens S_FNDN_ANCH Anchor piles, blocks, strands, deadmen, soil/rock anchors S_FNDN_CNTR Foundation centerlines S_FNDN_DRAN Foundation drainage features and objects S_FNDN_FTNG Footings STRUCTURAL LEVEL PROPERTIES Page 28-5

170 Number Name Description Color Linestyle Weight Transparency Priority S_FNDN_FTNG_RBAR Footing rebar S_FNDN_GRBM Grade beams S_FNDN_PCAP Pile caps S_FNDN_PEDS Foundation pedestals/pads S_FNDN_PIER Piers, drilled shafts, caissons S_FNDN_PILE Piles S_FNDN_PILE_GRID Pile Grid S_FNDN_RIBS Ribbed mat foundation S_FNDN_TRMT Foundation treatment (grouting) S_FNDN_TUNL Service tunnel/duct banks S_FSTN_ABLT Anchor bolts S_FSTN_MISC Fasteners and connections (nonspecific) S_GATE_ANCH Gate anchorages S_GATE_ANCH_DEAD Dead man anchorage S_GATE_ARMS Arm S_GATE_AXIS Gate axis and centerlines STRUCTURAL LEVEL PROPERTIES Page 28-6

171 Number Name Description Color Linestyle Weight Transparency Priority S_GATE_BLKH Bulkhead S_GATE_BLKH_NDLB Bulkhead needles beam S_GATE_BLKH_NDLS Bulkhead needles S_GATE_CONN Gate connects, links S_GATE_DIA~ Diagonals, gussets, sleeve nut S_GATE_DIA~_CHAN Diagonal channels S_GATE_DIA~_GUST Diagonal gusset plate S_GATE_DIA~_SUPT Diagonal gusset plate support S_GATE_DIAP Diaphragms S_GATE_FEND Gate fenders S_GATE_FLNG Flange S_GATE_FLNG_DNST Downstream flange S_GATE_FLNG_GIRD Girder flange S_GATE_FLNG_UPST Upstream flange S_GATE_GIRD_WEB~ Girder web plates S_GATE_GUDG Gudgeon STRUCTURAL LEVEL PROPERTIES Page 28-7

172 Number Name Description Color Linestyle Weight Transparency Priority S_GATE_GUDG_HOOD Gudgeon hood S_GATE_GUDG_HUB~ Gudgeon hub S_GATE_GUDG_PIN~ Gudgeon pin S_GATE_GUDG_STIF Gudgeon (hood) stiffener S_GATE_GUDG_SUPT Gudgeon (pin) support S_GATE_HORZ Horizontal rolled shapes S_GATE_ICST Intercostals S_GATE_JACK Gate jack S_GATE_JACK_HORZ Gate jack - horizontal S_GATE_JACK_VERT Gate jack - vertical S_GATE_LIFT Lifting mechanism S_GATE_LTCH Latching device S_GATE_LTCH_BOTM Latching device - bottom S_GATE_LTCH_TOP~ Latching device - top S_GATE_LUBE Lubrication system S_GATE_MISC Gates incidental to structure STRUCTURAL LEVEL PROPERTIES Page 28-8

173 Number Name Description Color Linestyle Weight Transparency Priority S_GATE_MITR_ASSY Miter guide assembly S_GATE_PIN~ Gate pins S_GATE_PNTL Pintle ball, bushing & base S_GATE_PNTL_CAST Pintle casting S_GATE_QOIN Quoin S_GATE_QOIN_FLNG Quoin flange S_GATE_QOIN_MITR Quion, miter S_GATE_QOIN_STIF Quoin stiffener S_GATE_QOIN_TRST Quoin thrust plate S_GATE_QOIN_WALL Quoin, wall S_GATE_QOIN_WEB~ Quoin web S_GATE_RAIL Rails and guides S_GATE_SEAL Gate seal S_GATE_SEAL_HORZ Gate seal - horizontal S_GATE_SEAL_VERT Gate seal - vertical S_GATE_SHOE Gate shoe STRUCTURAL LEVEL PROPERTIES Page 28-9

174 Number Name Description Color Linestyle Weight Transparency Priority S_GATE_SKIN Skin plates S_GATE_STIF Stiffener S_GATE_STIF_LONG Stiffener - longitudinal S_GATE_STIF_TRAN Stiffener - transverse S_GATE_STOP Stoplogs S_GATE_THBL Thimble S_GATE_TRST Thrust plate S_GATE_TRUN Trunion S_GATE_VALV Valves (general shape) S_GATE_VERT Rolled vertical shapes S_GATE_WALK Walkway S_GATE_WALK_FRMG Walkway - framing S_GATE_WALK_GRTG Walkway - grating S_GATE_WALK_SUPT Walkway - support S_GATE_WEB~ Web S_GRID_DIMS Column Grid Dimensions STRUCTURAL LEVEL PROPERTIES Page 28-10

175 Number Name Description Color Linestyle Weight Transparency Priority S_GRID_HORZ Grid lines (horizontal) S_GRID_HORZ_IDEN Column I.D. tags (horizontal) S_GRID_VERT Grid lines (vertical) S_GRID_VERT_IDEN Column I.D. tags (vertical) S_HYDR_BAFL Baffle blocks, splash pads S_HYDR_BASN Stilling and settling basins S_HYDR_CHAN Channel (Does not include earthen structures) S_HYDR_COFF Cofferdam S_HYDR_COND Diversionary/bypass conduits and culverts S_HYDR_DAM~ Dam S_HYDR_FISH Fish ladder or passage S_HYDR_FLUM Flume S_HYDR_INTK Intake, outlet S_HYDR_NOVR Non-overflow structures S_HYDR_STRC_POWR Powerhouse STRUCTURAL LEVEL PROPERTIES Page 28-11

176 Number Name Description Color Linestyle Weight Transparency Priority S_HYDR_SWAY Spillway S_HYDR_WEIR Weirs and sluiceways S_JNTS_CNTJ S_JNTS_CTLJ S_JNTS_EXPJ S_JNTS_STUC Construction/lift joints - (Do not use when 3D modeling) Control/contraction joints (saw cut) - (Do not use when 3D modeling) Expansion joints, joint materials (e.g., felt) - (Do not use when 3D modeling) Stucco joints - (Do not use when 3D modeling) S_JNTS_WTRS Waterstops S_JOIS_BRDG Bridging S_JOIS_GIRD Joist girders S_JOIS_PMTR Perimeter channel or rim joist S_JOIS_PRIM Primary joists S_JOIS_SECD Secondary joists S_JOIS_TRIM Partial length or trimmer floor joist STRUCTURAL LEVEL PROPERTIES Page 28-12

177 Number Name Description Color Linestyle Weight Transparency Priority S_METL_MISC Miscellaneous Metal S_OTLN_BLDG Building outline S_OTLN_FLOR Floor outline S_OTLN_OPNG Openings S_OTLN_ROOF Roof S_OTLN_STRC Misc. structures S_PADS_EQPM Equipment pads S_PIPE_CULV Precast/manufactured culverts S_PLAT_FRMG Platform frame/stringers S_PLAT_GRTG Platform grating (add a second minor group to indicate platform # or elev) S_PLAT_WALK Platform walkway S_REIN_RBAR Steel reinforcing, welded wire fabric S_REIN_TEND_HORZ Horizontal Tendons S_REIN_TEND_VERT Vertical Tendons S_SAFE_FENC Fencing rails, fabric, supports, and gates STRUCTURAL LEVEL PROPERTIES Page 28-13

178 Number Name Description Color Linestyle Weight Transparency Priority S_SAFE_GRAL Guardrails S_SAFE_HRAL Handrails, railings S_SAFE_PARA Parapet/jersey barrier S_SAFE_PARA_RBAR Parapet/jersey barrier rebar S_SAFE_WATR Waterway safety barriers S_SIGN_EXTN Extrusions S_SIGN_FRMG Framing & connections S_SIGN_GAGE Staff gages S_SIGN_PANL Sign panels S_SIGN_SPRT Supports S_SIGN_TEXT Signage text S_SLAB_APPR Approach slab S_SLAB_APPR_RBAR Approach slab rebar S_SLAB_EDGE Edge of slab S_SLAB_JOIN S_SLAB_RBAR Slab rebar STRUCTURAL LEVEL PROPERTIES Page 28-14

179 Number Name Description Color Linestyle Weight Transparency Priority S_SLAB_SECD Second pour, slab cap S_SLAB_SILL Sill S_STEL Elements made of structural steel S_STEL_BEAM Structural Steel Beams S_STEL_PLAT Structural Steel Plates S_STEL_STUD Structural Steel Studs S_STIF_LONG Stiffeners - longitudinal S_STIF_TRAN Stiffeners - transverse S_TRCH Trench S_TRUS_PRIM Primary trusses S_TRUS_SECD Secondary trusses S_WALL_ABUT Abutments S_WALL_CELL Cell S_WALL_COFF Cutoff wall S_WALL_CURT Curtain/breast wall S_WALL_FULL Wall going to the top of the structure STRUCTURAL LEVEL PROPERTIES Page 28-15

180 Number Name Description Color Linestyle Weight Transparency Priority S_WALL_GARD Guard/guide walls S_WALL_LOAD Load bearing walls S_WALL_MONO Wall monoliths S_WALL_MSE~ Mechanically stabilized earth (MSE) wall S_WALL_NONL Non-load bearing walls S_WALL_PCST Pre-cast concrete walls S_WALL_PRHT Wall that does not reach to the top of the structure S_WALL_RBAR Wall rebar S_WALL_RTWL Retaining wall (flood walls, wingwalls, etc.) S_WALL_SHEA Shear walls S_WALL_STUD Stud walls S_WARF Wharf S_WARF_BOLL Wharf-bollard S_WARF_CRAN Wharf-crane S_WARF_FNDR Wharf-fender STRUCTURAL LEVEL PROPERTIES Page 28-16

181 Number Name Description Color Linestyle Weight Transparency Priority S_WARF_PILE Wharf-piling S_WARF_SEIS_VALT Seismic Vault S_WARF_TIBK Wharf-tieback S_WARF_TIDN Tiedown S_WARF_TIDN_CVR~ Tiedown cover S_WARF_TRAN_RNWY Wharf-trans-runway S_WATR_SURF Water surface S_WOOD Elements made of Wood S_WWAY_DLPH Dolphins (associated with but not part of bridges, locks and guidewalls) S_WWAY_FEND Fenders S_WWAY_MOOR Mooring cells STRUCTURAL LEVEL PROPERTIES Page 28-17

182 29. TELECOMMUNICATIONS LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Telecommunications sheet files and base files for POLB. The levels are found in T_POLB_Levels.dgnlib. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority T_COMM_LINE Telecommunications: Devices: Lines T_COMM_PONT Telecommunications: Line: Point TELECOMMUNICATIONS LEVEL PROPERTIES Page 29-1

183 Page 29-1

184 30. SURVEYING/MAPPING LEVEL PROPERTIES Introduction This chapter includes level assignments that support the development of Surveying/Mapping sheet files and base files for POLB. The levels are found in V_POLB_Levels.dgnlib. Level Assignments Number Name Description Color Linestyle Weight Transparency Priority V_ANNO_GRID Annotation: Grid V_ANNO_GRID_MAJR Annotation: Grid: Major V_ANNO_GRID_MINR Annotation: Grid: Minor V_ANNO_LEGN Annotation: Legend, symbol keys V_ALGN_DATA Alignment: Data V_ALGN_LINE Alignment: Lines V_ALGN_MAJR Alignment: Major V_ALGN_MARK Alignment: Markers, break marks, leaders V_ALGN_MINR Alignment: Minor V_ALGN_STAN Alignment: Stationing SURVEYING/MAPPING LEVEL PROPERTIES Page 30-2

185 Number Name Description Color Linestyle Weight Transparency Priority V_ALGN_SYMB Alignment: Reference symbols V_ALGN_TEXT Alignment: Text V_BORE_PONT Borings: Point V_BRDG Bridge V_BRDG_CNTR Bridge: Center V_BRDG_RAIL Bridge: Rail 0 map_bridgerl V_BRDG_SIGN Bridge: Signage V_CATH_ANNO Cathodic protection: Annotation V_CATH_LINE Cathodic protection: Lines 0 ut_cath V_CATH_LINE_ABND Cathoid protection: Lines: Abandoned 0 ut_abnd_cath V_CATH_PONT Cathodic protection: Point V_CHAN_BANK_TOP~ Navigable channels: Top V_CHAN_BNCH Navigable channels: Bench SURVEYING/MAPPING LEVEL PROPERTIES Page 30-3

186 Number Name Description Color Linestyle Weight Transparency Priority V_CHAN_CNTR Navigable channels: Center V_CHAN_LIMT Navigable channels: Limit V_CHAN_SLOP_LINE V_CHAN_TOE~ V_CMPA_LINE V_CMPA_LINE_ABND V_CMPA_PONT V_COMM_ALRM V_COMM_ALRM_ABND Navigable channels: Slope: Lines Navigable channels: Toe of channel Compressed / processed air systems: Lines Compressed / processed air systems: Lines: Abandoned Compressed / processed air systems: Points Telephone communications: Alarm Telephone communications: Alarm: Abandoned ut_compair 2 1 ut_abnd_comp_air ut_fire_alarm 0 6 ut_abnd_fire_alarm 0 SURVEYING/MAPPING LEVEL PROPERTIES Page 30-4

187 Number Name Description Color Linestyle Weight Transparency Priority V_COMM_CATV V_COMM_CATV_ABND V_COMM_FIBR V_COMM_FIBR_ABND V_COMM_LINE V_COMM_LINE_ABND V_COMM_PONT V_COMM_PUBL Telephone communications: Cable television Telephone communications: Cable television: Abandoned Telephone communications: Fiber optics cable Telephone communications: Fiber optics cable: Abandoned Telephone communications: Lines Telephone communications: Lines: Abandoned Telephone communications: Point Communications: Public Address 6 ut_tv 0 6 ut_abnd_tv 0 6 ut_fiber_optic 0 6 ut_abnd_fiber_optic 0 6 ut_comm 1 6 ut_abnd_comm ut_pubadd 0 SURVEYING/MAPPING LEVEL PROPERTIES Page 30-5

188 Number Name Description Color Linestyle Weight Transparency Priority V_COMM_PUBL_ABND V_COMM_STRC_LINE V_CTRL_BMRK V_CTRL_INST Communications: Public Address abandoned Telephone communications: Structure line Control points: Benchmarks Control points: Instrumentation 6 ut_abnd_pub_add V_CTRL_LINE Control points: Lines V_CTRL_PHL~ Control points 126 v_pier_head_line V_CTRL_PONT Control points: Point V_CTRL_SYMB Control points: Reference symbols V_DTCH_LINE Ditches or washes: Lines V_DTM~_DRED_FAZ1 Digital terrain model: Dredging surface: Phase number SURVEYING/MAPPING LEVEL PROPERTIES Page 30-6

189 Number Name Description Color Linestyle Weight Transparency Priority V_DTM~_DRED_FAZ V_DTM~_DRED_FAZ V_DTM~_DRED_FAZ V_DTM~_DRED_FAZ V_DTM~_MMTC V_DTM~_PONT V_DTM~_TRGL V_DTM~_XBRK V_ELEC_LINE Digital terrain model: Dredging surface: Phase number 2 Digital terrain model: Dredging surface: Phase number 3 Digital terrain model: Dredging surface: Phase number 4 Digital terrain model: Dredging surface: Phase number 5 Digital terrain model: Mismatched elevation Digital terrain model: Point Digital terrain model: Triangle Digital terrain model: Crossing breaklines Electrical system, telecom plan: Lines ut_elec 1 SURVEYING/MAPPING LEVEL PROPERTIES Page 30-7

190 Number Name Description Color Linestyle Weight Transparency Priority V_ELEC_LINE_ABND V_ELEC_LITE V_ELEC_PONT V_ELEC_STRC V_ELEC_STRC_LINE Electrical system, telecom plan: Lines: Abandoned Electrical system, telecom plan: Lights, lighting Electrical system, telecom plan: Point Electrical system, telecom plan: Structures Electrical system, telecom plan: Structures Line 3 ut_abnd_elec V_ENV~_LINE Environmental: Lines V_ENV~_LINE_ABND Environmental: Lines: Abandoned V_ENV~_PONT Environmental: Point V_GAS~_LINE Gas: Lines 52 ut_gas V_GAS~_LINE_ABND Gas: Lines: Abandoned 52 ut_abnd_gas V_GAS~_PONT Gas: Point V_GUTL General utilities V_GUTL_CASE General utilities: Casing 0 map_casing 0 SURVEYING/MAPPING LEVEL PROPERTIES Page 30-8

191 Number Name Description Color Linestyle Weight Transparency Priority V_GUTL_PONT General utilities: Point V_GUTL_UNKN V_GUTL_UNKN_LINE V_GUTL_UNKN_XING_SYMB General utilities: Unknown General utilities: Unknown Line General utilities: Unknown Xing Point ut_unknown V_OIL~_CHEM_LINE Oil: Chemical Lines 5 ut_chem V_OIL~_CHEM_LINE_ABND Oil: Chemical Lines Abandoned 5 ut_abnd_chem V_OIL~_GAS~_DRY~ Oil: Gas Dry 5 ut_dry_gas V_OIL~_GAS~_DRY~_ABND Oil: Abandoned Gas Dry 5 ut_abnd_dry_gas V_OIL~_GAS~_WET~ Oil: Water Wet 5 ut_wet_gas V_OIL~_GAS~_WET~_ABND Oil: Water Wet Abandoned 5 ut_abnd_wet_gas V_OIL~_LINE Oil: Lines 5 ut_oil V_OIL~_LINE_ABND Oil: Lines: Abandoned 5 ut_abnd_oil V_OIL~_PONT Oil: Point SURVEYING/MAPPING LEVEL PROPERTIES Page 30-9

192 Number Name Description Color Linestyle Weight Transparency Priority V_OIL~_STRC_LINE Oil: Structure Line V_OIL~_TRCH Oil: Trench V_OIL~_WATR_INJC Oil: Water 5 ut_water_inj V_OIL~_WATR_INJC_ABND Oil: Water INJC Abandoned 5 ut_abnd_water_inj V_OIL~_WATR_LINE Oil: Water Lines 5 ut_oil_water V_OIL~_WATR_LINE_ABND Oil: Abandoned Water Lines 5 ut_abnd_oil_water V_OIL~_WELL_RTWL Oil: Well Retaining Wall 5 rd-wall-p V_PRKG Parking lots V_PROP Property boundary 2 v_property_line V_PROP_ANNO V_PROP_LL~~ V_PROP_OSA~ V_PROP_OSA~_ANNO Property boundary: Annotation Property boundary: Lease line Property boundary: Oil Set Aside Property boundary: Oil Set Aside: Annotation map_leaseline SURVEYING/MAPPING LEVEL PROPERTIES Page 30-10

193 Number Name Description Color Linestyle Weight Transparency Priority V_PROP_PORT_BNDY V_PROP_RES~ Property boundary: Boundary Property boundary: Lease Line 0 map_port_bndy_line 2 11 map_leaseline V_RAIL Railroad: Crane Rail 7 map_crane_rail V_RAIL_EQPM Railroad: Equipment V_RAIL_LAST_TIE~ Railroad: Last Common Tie V_RAIL_LINE Railroad: Lines 6 map_railroads V_RAIL_LINE_ABND V_RAIL_LINE_ANNO Railroad: Lines: Abandoned Railroad: Lines: Annotation 6 map_railroads V_RAIL_PONT Railroad: Point V_RAIL_SGNL Railroad: Signal V_RAIL_TOUT Railroad: Turnout V_ROAD_ANNO Roadways: Annotation V_ROAD_BARR Roadways: Barrier SURVEYING/MAPPING LEVEL PROPERTIES Page 30-11

194 Number Name Description Color Linestyle Weight Transparency Priority V_ROAD_BERM_CNTR Roadways: Berm Center 0 map_berm V_ROAD_BERM_EDGE Roadways: Berm Edge V_ROAD_CURB Roadways: Curb V_ROAD_CURB_BACK Roadways: Back of Curb V_ROAD_CURB_ETYP_TOP~ Roadways: Top of Curb Type E V_ROAD_CURB_FACE Roadways: Curb Face V_ROAD_CURB_FLOW Roadways: Curb Flow V_ROAD_CURB_FLOW_ETYP Roadways: Curb Flow Type E V_ROAD_CURB_GUTR_LIP~ Roadways: Lip of Gutter V_ROAD_DRIV Roadways: Driveway points V_ROAD_EDGE Roadways: Edge V_ROAD_FLOW Roadways: Flowline 6 v_storm_flow V_ROAD_GRAL Roadways: Guard rail 5 rd-mbgr-x V_ROAD_GUTT Roadways: Gutter 5 map_concrete V_ROAD_LINE Roadways: Lines SURVEYING/MAPPING LEVEL PROPERTIES Page 30-12

195 Number Name Description Color Linestyle Weight Transparency Priority V_ROAD_LINE_ANNO Roadways: Lines: Annotation V_ROAD_MEDN Roadways: Median 5 map_lowwall V_ROAD_MRKG V_ROAD_MRKG_DASH Roadways: Pavement markings Roadways: Pavement markings dashed rd-lnstrpdsh V_ROAD_PONT Roadways: Point V_ROAD_RAMP Roadways: Accessible ramp V_ROAD_SIGN Roadways: Signage V_ROAD_SWLK Roadways: Sidewalks 5 map_concrete V_ROAD_UNIM Roadways V_ROAD_UPVD Roadways: Unpaved V_SITE Site features V_SSWR_ANNO Sanitary sewer: Annotation V_SSWR_LINE Sanitary sewer: Lines 2 ut_sewer 1 SURVEYING/MAPPING LEVEL PROPERTIES Page 30-13

196 Number Name Description Color Linestyle Weight Transparency Priority V_SSWR_LINE_ABND Sanitary sewer: Lines: Abandoned 2 ut_abnd_sewer V_SSWR_PONT Sanitary sewer: Point V_SSWR_STRC_LINE Sanitary sewer: Structure Line V_STRC_BARR Structural: Barrier V_STRC_BLDG Structural: Building points V_STRC_BLDG_OTLN V_STRC_CNDT Structural: Building Outline Structural: Diversionary / bypass conduit / culvert 4 v_building_outline V_STRC_CONC Structural: Concrete 4 map_concrete V_STRC_FENC Structural: Fences 4 v_fence V_STRC_FENC_BLOC_WALL V_STRC_FENC_GATE V_STRC_MASN Structural: Fence Block Wall Structural: Fences: Fence Gate Structural: Existing features for concrete masonry elements 4 map_blockwl 0 0 v_fence_gate SURVEYING/MAPPING LEVEL PROPERTIES Page 30-14

197 Number Name Description Color Linestyle Weight Transparency Priority V_STRC_MISC Structural: Miscellaneous V_STRC_MISC_UNDR Structural: Miscellaneous Underground V_STRC_PILE Structural: Piles V_STRC_PONT Structural: Point V_STRC_RTWL Structural: Retaining Wall 0 rd-wall-p V_STRC_SCAL Structural: Turck or rail scale V_STRC_SHT~_PILE Structural: Piles 2 st_sheet_piles V_STRC_STEL Structural: Existing features for structural steel elements V_STRC_STEP Structural: Steps V_STRC_TANK Structural: Storage tanks V_STRC_TRNT_RUNW Structural: Transtainer Runway V_STRC_TUNL Structural: Tunnel V_STRC_UNKN Structural: Unknown SURVEYING/MAPPING LEVEL PROPERTIES Page 30-15

198 Number Name Description Color Linestyle Weight Transparency Priority V_STRC_WALL Structural: Wall V_STRC_WALL_CNTN Structural: Containment Wall 4 rd_wall V_STRC_WALL_HIGH Structural: Wall 4 map_lowwall V_STRC_WOOD Structural: Wood V_STRC_WSTP Structural: Wheel stop V_STRM_ANNO Storm sewer: Annotation V_STRM_AREA_DRN~ Storm sewer: Area: Drain V_STRM_FLOW Storm sewer: Flow 12 v_storm_flow V_STRM_LINE Storm sewer: Lines 12 ut_stdrain V_STRM_LINE_ABND Storm sewer: Lines: Abandoned 12 ut_abnd_storm_drain V_STRM_OUTF_LINE Storm sewer: Outfall 12 ut_outfall V_STRM_OUTF_LINE_ABND V_STRM_POND Storm sewer: Abandoned Outfall Storm sewer: Retention pond 12 ut_abnd_outfall V_STRM_PONT Storm sewer: Point SURVEYING/MAPPING LEVEL PROPERTIES Page 30-16

199 Number Name Description Color Linestyle Weight Transparency Priority V_STRM_STRC_LINE V_STRM_TRCH_DRN~ Storm sewer: Structure Line Storm sewer: Trench Drain v_trench_drain V_SURV_ANNO Survey: Annotation V_SURV_AREA Survey: Area V_SURV_LINE Survey: Lines V_SURV_MISC Survey: Miscellaneous V_SURV_NPCD Survey: No Pcode V_SURV_PONT Survey: Point V_SURV_SOUN Survey: Baseline Sounding 0 v_rock_dike_ref_line V_TOPO_BNDY_EXTR V_TOPO_BNDY_INTR V_TOPO_BRKL V_TOPO_BRKL_INFD Topographic feature: Boundary: Exterior Topographic feature: Boundary: Interior Topographic feature: Break lines Topographic feature: Break lines: Inferred SURVEYING/MAPPING LEVEL PROPERTIES Page 30-17

200 Number Name Description Color Linestyle Weight Transparency Priority V_TOPO_DIKE Topographic feature: Dike 0 map_dike V_TOPO_DTCH V_TOPO_EDGE V_TOPO_MAJR V_TOPO_MAJR_ANNO V_TOPO_MAJR_DEPR V_TOPO_MINR V_TOPO_MINR_ANNO V_TOPO_MINR_DEPR V_TOPO_PONT Topographic feature: Ditches or washes Topographic feature: Edge Topographic feature: Major Topographic feature: Major : Annotation Topographic feature: Major : Depression Topographic feature: Minor Topographic feature: Minor : Annotation Topographic feature: Minor : Depression Topographic feature: Point v_depression_line v_depression_line SURVEYING/MAPPING LEVEL PROPERTIES Page 30-18

201 Number Name Description Color Linestyle Weight Transparency Priority V_TOPO_PONT_TEXT V_TOPO_SIGN V_TOPO_SLOP_TOE~ V_TOPO_SLOP_TOP~ V_TOPO_SLUR V_TOPO_SPOT V_TOPO_SPOT_TEXT V_TOPO_SURF_PMTR V_TOPO_VEGE_BRSL V_TOPO_VEGE_TREE Topographic feature: Point: Text Topographic feature: Signage Topographic feature: Toe of slope Topographic feature: Top of slope Topographic feature: Slurry Topographic feature: Spot elevations Topographic feature: Spot elevations: Text Topographic feature: Surface areas: Perimeter Topographic feature: Brushline Topographic feature: Trees, shrubs, and other vegetation ut_slptoe 0 0 rd_slope 0 0 v_slurry map_brush SURVEYING/MAPPING LEVEL PROPERTIES Page 30-19

202 Number Name Description Color Linestyle Weight Transparency Priority V_TOPO_VEGE_TRLN V_TOPO_WATR Topographic feature: Tree line Topographic feature: Water edge pond/lake 2 map_treeline V_WARF_BERT_ANNO Wharf: Berth: Annotation V_WARF_CABL Wharf: Cable V_WARF_CONC Wharf: Concrete V_WARF_DLPH Wharf: Dolphin V_WARF_DOCK V_WARF_DOCK_MISC V_WARF_DOCK_STEP Wharf: Decks, docks, floats, piers Wharf: Decks, docks, floats, piers: Miscellaneous Wharf: Decks, docks, floats, piers: Steps V_WARF_MISC Wharf: Miscellaneous V_WARF_PIER_FACE Wharf: Pier Face 0 v_pier_head_line V_WARF_PONT Wharf: Survey point shot V_WATR_BCFL_LINE Water: Backflow line 1 ut_water_bcfl 0 SURVEYING/MAPPING LEVEL PROPERTIES Page 30-20

203 Number Name Description Color Linestyle Weight Transparency Priority V_WATR_LINE Water Supply: Lines 1 ut_water V_WATR_LINE_ABND V_WATR_PONT Water Supply: Lines: Abandoned Water Supply: Survey point shot 1 ut_abnd_water V_WATR_SPKL Water Supply: Sprinkler 1 ut_sprinkler V_WATR_SPKL_ABND V_WATR_STRC_LINE Water Supply: Sprinkler Abandoned Water Supply: Structure Line 1 ut_abnd_sprinkler V_WETL Wetlands SURVEYING/MAPPING LEVEL PROPERTIES Page 30-21

204 31. Glossary Epoch - NAD83( ) is a realization of the NAD83 datum resulting from statewide geodetic network upgrades performed by the US National Geodetic Survey (NGS) between 1989 and 1997 called High Precision Geodetic Network (HPGN) or High Accuracy Reference Network (HARN). The HPGN in California was observed by the California Department of Transportation (CALTRANS) and NGS as a statewide GPS control network. The network was first visited in 1991 and again in 1992 in response to the Landers earthquake. NAD83 coordinates resulting from the adjustment of the statewide GPS measurements refer to an epoch of (equivalent to May 7, 1991) Epoch - (NSRS2007) is the most recent realization of the NAD83 datum resulting from a nationwide readjustment of GPS networks including CORS, FBN, CBN, UDN and Airport survey stations about 69,117 control stations across the U.S. The NAD83 (NSRS2007) was released by the NGS in February, ACS Triad - A three-arrow representation display to indicate axes of an Auxiliary Coordinate System (ACS) and origin in a MicroStation view. AIA American Institute of Architects. ALG InRoads Geometry file containing Horizontal and Vertical alignments as well as COGO Points. The data in the ALG can be existing or design information. Annotation Cell MicroStation Cells that obey the rules of annotation scale. When cells are placed with annotation scale lock on, they are scaled by the current annotation scale. Changing the annotation scale in a model will cause the annotation cells to be resized accordingly. Annotation Scale - Optional scale factor applicable to text and dimension elements in a MicroStation Model. Turn on the Annotation Scale lock to apply the annotation scale if you will create your sheet model by scaling the drawing border to fit your design. Applying the annotation scale will ensure that when the scaled print is created, annotations are at the correct physical size. ANSI A/B/D Standard paper sizes, in inches, as established by the American National Standards Institute. ANSI A 8 ½ x 11 ANSI B 11 x 17 ANSI D 22 x 34 As-Builts - A set of drawings which depict the actual as-built conditions of the completed construction. AutoTurn Vehicle turn simulation software from Transoft Solutions. AutoTurn runs on both AutoCAD and MicroStation CAD platforms. Glossary Page 31-1

205 Base Maps - Base Maps are MicroStation DGN files generated by POLB GIS/Mapping Group and represent the most current set of as-built plans at POLB. Bearing A method of displaying angle measurements in MicroStation based upon the angle s rotation from an axis. Bentley Map Desktop GIS application from Bentley that is based upon MicroStation. Border The graphical elements that represent the outside boundary of a printed CAD file and contain elements such as the title block, revision block, and information related to the project participants. In POLB workflow the border is typically a reference file. CAC POLB Computer Application Committee. Its goals include the following: Exchange information and discuss issues relating to the current and future use of computer applications among the varied sections of the Engineering Division. Evaluate division wide computer related training needs, and make computer training recommendations to the CMC (Computer Management Committee). Evaluate current and future application needs, and make recommendations to the CMC. Lead smaller division, section, and/or application specific user s groups. Regularly meet with user s groups to increase computer productivity by disseminating information from the CAC, exchanging ideas, discussing issues, and holding focused training seminars. CADD Standards A set of standards that have been created to improve productivity and interchange of Computer-aided design documents between different organizations and CAD programs, especially in architecture and engineering. CAD/CADD Computer Aided Design/Computer Aided Drafting and Design. Caltrans California Department of Transportation. Cell - A complex element composed of a group of primitive or other complex elements that is stored in a cell library for repeated placement. Models can be used as a cell if defined as a cell. Cell library A collection of cells stored in a single file. MicroStation Cell libraries are typically saved with a.cel extension. Certificates A digital certificate is an electronic document which uses a digital signature to bind together a public key with an identity information such as the name of a person or an organization, their address, and so forth. The certificate can be used to verify that a public key belongs to an individual. Glossary Page 31-2

206 COGO A program that is aimed at coordinate geometry problems in civil engineering and surveying. COGO also relates to InRoads geometry and specifically refers to the points and tools that manipulate or work with geometry point data. Coincident - A method of attaching a reference in MicroStation by aligning the coordinates of its design plane with those of the active DGN file, without any rotation, scaling, or offset. Coincident World - A method of attaching a reference in MicroStation by aligning the references with the active model with regard to both Global Origin and design plane coordinates. Content Management System Refers to a class of software solutions that allow for the management of data in a collaborative environment. Custom Line Styles MicroStation are user defined linestyles stored in a DGN library file or resource file. DAT An InRoads data file that contains Drainage Structure or rainfall information. Datasource A ProjectWise container for folders and documents. POLB datasource is named POLB ProjectWise. Descartes An image management program from Bentley that adds raster editing and manipulation functionality to MicroStation. Design Cube - The space in which elements are created in a 3D MicroStation design. Design History A MicroStation feature which stores a record of changes made to a DGN file. When a user wants to commit a set of changes to a design file to its history, a revision is created. Earlier revisions of a design file can be recalled and restored at any time. Design Model A model in a MicroStation DGN file that consists of 2D or 3D design geometry. A MicroStation DGN file can consist of one or more design models. DGN MicroStation design file. A DGN file can contain one or more models. DGNLIB - Design Library. A type of MicroStation Design file that contains standards information such as levels, menu customization, font styles, and dimension styles. DGN Library files are saved with a.dgnlib extension. Digital Signatures A technology that demonstrates the authenticity of a digital file. MicroStation provides tools which allow for the use of digital signatures in DGN files. Dimension Style A group of dimension settings such as terminators, units, formats and symbology that are typically stored in a DGN library for shared usage. Displayset A feature in MicroStation that displays a group of elements selected by the user while all other elements are hidden. Glossary Page 31-3

207 DMG - A rectangular survey system established by the US Engineers in 1859 using monument Deadman Island. Documentum An Enterprise Document Management System by EMC. Documentum has been chosen as the Enterprise Content Management System at POLB. Drawing Model A subset of a 2D or 3D MicroStation design model, used to apply annotations, dimensions, callouts, and other embellishments to a design. By default, the view windows of a drawing model have gray backgrounds. DSR Design Service Request. DTM InRoads data file that contains a collection of 3-D information about a particular area or region. A DTM consists of 3-D Features and a triangle network produced by an interrelationship of that 3-D data. Ellipsoid - A reference ellipsoid is a mathematically-defined surface that approximates the geoid, the truer figure of the Earth, or other planetary body. Feature codes From an InRoads Survey perspective, Feature Codes refer to survey data collection and the assigning of a code number or name to the data being located in the field. Feature Codes relate to the InRoads Style Manager which contains the Feature Code master list. Fonts A style of lettering. MicroStation supports the use of its own fonts stored in a resource file. AutoCAD and Windows true type fonts are also supported. Free A file management command in ProjectWise which cancels the check out of a document. Documents can only be freed by the user who originally checked the document out or a ProjectWise Administrator. FWD InRoads Survey Field Book file. This file is generally created by importing field collected data into InRoads Survey. GIS Geographic Information System. GIS90 - A local adjustment of Port control based on the NAD27 datum. GIS90 coordinates have been truncated by 4,000,000 in the Northing and 4,200,000 in the Easting. GIS90 values vary by only a few hundredths from NAD27. Global Origin (GO) The location of X=0, Y=0, and Z=0 (for 3D files) in a MicroStation design file. Typically, the global origin is at the center of the design plane. GRS 80 Geodetic Reference System GUI Graphical User Interface. The elements of a computer application that allows people to interact in methods other than typing on a keyboard. IDF InRoads Drainage settings file that contains Intensity-Duration-Frequency rainfall data. Glossary Page 31-4

208 imodel A file format developed by Bentley for the exchange of 2D/3D geometry and business data. InRoads Civil Engineering based software from Bentley Systems that contains a collection of design tools to assist the designer in roadway and site design. The InRoads family of products consists of InRoads Bridge, InRoads Site, InRoads Storm & Sanitary, InRoads Survey, and InRail. IPARM/.i /.m Files that are used and generated by InterPlot. An IPARM contains plotting parameters and uses the.i extension. An Interplot metafile is the intermediate plot file created when submitting plots from IPlot and uses the.m extension. IPS InterPlot Plot Set. A file which is used as a container to store the plot settings for one or more MicroStation DGN files. Typically used for batch plotting a set of files. IRD InRoads Roadway Designer file. ITL InRoads Template Library file that contains standards as well as project specific typical sections that are used to construct a design surface model. Keyin A method of input in MicroStation using commands entered into the keyboard. Lambert Conformal Conic A method of map projection which superimposes a cone over the sphere of the earth. Level A method of separating and organizing drawing objects. In the MicroStation V8 DGN file format, the number of levels is unlimited, and the minimum number of levels is 1. Level Filters A capability of MicroStation to limit the list of levels displayed in the Level Manager and Level Display dialog boxes to only those that match a pre-determined criteria. Level Symbology Overrides A MicroStation view setting that, when turned on, causes all elements on a particular level to be displayed with an alternate set of element symbology than the default. LIDAR (Light Detection and Ranging) An optical remote sensing technology that measures the properties of scattered light to find range and/or other information of a distant target. Link Sets A MicroStation feature which enables the linking of elements in a design file to other documents such a Word document, PDF, and other design files. The Link Set hierarchy can be navigated from inside MicroStation via the Project Explorer or in the ProjectWise Explorer the Link Set is contained in a ProjectWise project. Live Nesting / Nested Attachments An option when attaching reference files in MicroStation that causes the children of an attached reference file to be automatically referenced as well. Local Document Organizer A utility in ProjectWise that displays the documents a user has checked out or copied out of ProjectWise. Glossary Page 31-5

209 Logical Names A method of naming reference file attachments in MicroStation that enables the elements in that reference file to be processed as a group in a design script or pen table for plotted output. Managed / Unmanaged Workspace A Managed Workspace is a collection of configuration settings in ProjectWise that allows MicroStation to get its workspace information from a ProjectWise datasource. An Unmanaged Workspace is a ProjectWise configuration that simply points MicroStation to a network location outside of ProjectWise for its workspace resources. Master Units/Sub Units When the working units of a MicroStation design file are defined the master units and sub units define the real world units to be used in the design. Master Units are the largest measuring unit used in the design file and are commonly defined as meters or feet. Sub Units specify the smaller measuring unit, typically centimeters or inches, used in the design file. MathCAD Engineering calculation software from Parametric Technology Corporation. MicroStation A 2D/3D Computer Aided Design software developed by Bentley. MicroStation Basic Macro A programmed customization to MicroStation based upon the BASIC programming language. Though still supported, MicroStation Basic macros have largely been superseded by MicroStation VBA macros. MicroStation Tags A method of storing non-graphical attributes to elements in a MicroStation design file. MicroStation V8i An update to MicroStation V8 which was released in MicroStation VBA Macro A programmed customization made to MicroStation based upon the Visual Basic language developed by Microsoft. MicroStation VBA macros use the.mvba file extension. MicroStation XM An update to MicroStation V8 which was released in MicroStation XM has subsequently been replaced by MicroStation V8i. Model Files - A MicroStation DGN file that contains information that spans multiple sheets. Model files are typically referenced into the plotted Sheet files. NAD27 - Coordinate system is based on NAD27 State Plane using control provided by RBF Consulting and Johnson Frank and Associates. NAD 83 - The North American Datum is the official datum used for the primary geodetic network in North America. NCS The United States National CAD Standard. The National CAD Standard is published by the BuildingSmart Alliance and consists of the American Institute of Architect s CAD Layer Guidelines, the Construction Specification Institute s Uniform Drawing System, and the Plotting Guideline. Glossary Page 31-6

210 OLE OLE refers to Object Linking and Embedding which is a technology developed by Microsoft that allows embedding and linking of information between documents created by different applications. PDF Portable Document Format. A file format developed by Adobe Systems for document exchange. Pen Tables Also known as Design Scripts, pen tables allow for the resymbolization of plotted output based a set of criteria. For example, a pen table can be used to determine the thickness of a plotted line based upon the weight of an element in a design file. Personal Workspace A type of Managed Workspace in ProjectWise that allows the user to customize MicroStation settings through the use of configuration variables. Duplicates much of the functionality of MicroStation user configuration files (.ucf). Photogrammetry - The practice of determining the geometric properties of objects from photographic images. PIF - Project Initiation Form. Plotting / Printing The process of creating a hard copy or electronic file output of data stored in a digital file. Example output formats include a standard printer for A and B size prints, a large format plotter for D size sheets, and a PDF for electronic output. POLB Port of Long Beach. POLB CAC See CAC. Project Explorer A utility in MicroStation that allows for the management of Link Sets. Projection The process of reprojecting design data from one Geographic coordinate system to another. ProjectWise A Content Management System developed by Bentley which is used at POLB to manage documents related to survey, engineering, and GIS data. ProjectWise Document An item in a ProjectWise folder which represents an electronic file or is a placeholder for information that may not be stored in ProjectWise such as a physical file. ProjectWise InterPlot Organizer An application from Bentley for plotting Engineering data such as MicroStation design files, raster files, and Bentley Digital Print Format (DPR) files. ProjectWise Folder A container for documents and other folders in a ProjectWise datasource. ProjectWise InterPlot - A plotting solution from Bentley that is used to plot MicroStation Design files and Raster Data. Raster References MicroStation has the capability of attaching image files in a variety of raster file formats as background information. Glossary Page 31-7

211 Records Center The POLB Records Center facilitates the retention and management of crucial documents and media for the entire Harbor Department. Reference Clipping A method to control what part of a reference file will display in a MicroStation view by using a boundary to define the limits of its display. References - A model attached to and displayed with the active model for printing or construction purposes. A reference cannot be modified. You can attach, as a reference, a model that resides in either the open DGN file or some other DGN file. Resolution design file A MicroStation design file setting that determines the size and accuracy of the working area. Resolution The MicroStation working units settings which determine the accuracy of the design plane/cube. RSC - Resource File. A MicroStation file which contains the definitions for fonts and line styles. SAP 2000 Structural Analysis program by Computers and Structures Inc. Saved View - A named view definition saved in a DGN file for later recall or for attaching to another model file as a reference. SDB SAP 2000 model File. Shared Cell Similar to a graphic cell but the graphics and cell definition are stored in the current file rather than a library. Seed File A file which is used by MicroStation as a template for new files. Sheet File A MicroStation DGN file that contains the information in a plotted sheet. Sheet Model A type of model in a MicroStation design file which has additional parameters beyond a design model that apply to a plotted sheet of paper such as paper size and scale. Solids A type of complex element in a design file specific to 3D files. SS1 / Select Series 1 The latest release of MicroStation V8 which was released in The official title is MicroStation V8i SelectSeries 1. SSR Survey Service Request. STAAD Structural Analysis and Design software from Bentley. Survey Feet / International Feet An international foot is defined as meters. The United States survey foot is defined as exactly 1200/3937meters, approximately m. Template Library See ITL file. Glossary Page 31-8

212 Text Styles A named group of text attributes such as font, text width, and text height that are typically stored in a DGN library for shared usage. Title Block The area of a design file border that contains textual information that describes the plotted sheet. The standard Port title block is linked document attributes which are stored in ProjectWise. Title Block Attributes The document attributes stored in ProjectWise which are linked to title block tags in a MicroStation design file. Turning Template Produced using AutoTURN software, turning templates are used in the design of roadway facilities for vehicle access evaluation. Update Server Copy A ProjectWise file management command which saves the latest changes to a file from the user s workstation to the ProjectWise server. V8 The current version of the MicroStation DGN file format. This format became the standard for MicroStation files when the initial release of MicroStation V8 was introduced in The current release of MicroStation is MicroStation V8i Selectseries 1. Versioning A ProjectWise feature which allows for the creation of multiple versions of a document. Not to be confused with MicroStation design history which stores the revisions made to a MicroStation within the DGN file container. View Attributes The different properties of a MicroStation view such as Line Styles, Weights, and Text which can be toggled on and off to filter certain element types and properties. Weight A MicroStation element attribute that determines the thickness of the lines used to draw or plot a graphic element. Each element in a MicroStation design file has its own weight. Working Units The real-world units such as meters or feet that a design plane in a MicroStation DGN file is configured to. The settings for the working units determine the size and accuracy of the working area in a design file. Workspace - A collection of files and configurations which define the standards used in a MicroStation session. Many organizations, including POLB make their MicroStation Workspace available to consultants as a method of distributing their CADD Standards. XIN InRoads master settings file that contains the CADD standards and intelligent tagging information for InRoads Surfaces, Geometry and Survey data. Glossary Page 31-9

213 925 Harbor Plaza Long Beach CA