Ddot Micro Station v8 Cad Standards Manual September 2005
Ddot Micro Station v8 Cad Standards Manual September 2005
Ddot Micro Station v8 Cad Standards Manual September 2005
Department of Transportation
MicroStation® V8 CAD
Standards Manual
September 2005
Acknowledgement
This document presents the CAD standards of the District of Columbia Department of
Transportation (DDOT). This manual and the DDOT CAD standards and workspace are
based on those of the Maryland State Highway Administration’s (MDSHA).
The new MDSHA V8 CAD standards and workspace were the result of a great deal of effort
and coordination. The final product incorporated resources and comments from MDSHA, the
consultant community and from members of the Consulting Engineering Council of
Maryland. Thus, given the above and the fact that there are numerous streets which are either
bordered by Maryland on one side and DC on the other, or that run through both
jurisdictions, DDOT made the decision to adopt the Maryland State Highway Administration
(MDSHA) CAD Standards.
Incorporated in the MDSHA workspace are numerous macros and tools that aid in increasing
productivity as well as in ensuring compliance with the CAD standards. DDOT has
incorporated these macros and tools into its workspace with minimal, and mostly cosmetic,
modifications. The MDSHA CAD Standards Manual is also the source and foundation for
most of the DDOT CAD Standards Manual. Doing so offers DDOT two benefits: First, the
consultants that work on projects in both jurisdictions would not need to learn a new set of
standards or tools. Second, the association with MDSHA will facilitate the CAD standards
adoption to occur faster than would have been possible had DDOT undertaken to develop all
the tools and macros it needs.
The MDSHA workspace and tools are expected to evolve over time to better serve its
personnel and the consulting community. As major modifications are made by MDSHA,
DDOT will evaluate the updates, and if deemed advisable, update its workspace and replace
applicable sections of its CAD Standards Manual.
We want to thank MDSHA personnel and acknowledge the support they provided as DDOT
was modifying the SHA workspace and CAD Manual to meet its needs. MDSHA had
graciously shared the electronic files needed for the Workspace and CAD manual and
extended permission to DDOT to modify and/or adopt any of the files as needed for the new
DDOT Workspace and CAD Standards Manual. SHA personnel were very generous with
their time, answered numerous questions and provided invaluable help in customizing the
Workspace.
The DDOT Workspace, V8 CAD Standards Manual and associated support files will be
distributed to consultants on a CD. DDOT employees will also be able to access these on the
server and should contact their IT manager for guidance. The guidelines contained in the
DDOT CAD Standards Manual are to be followed for all DDOT projects.
The manual also marks DDOT’s migration to utilizing CAD for drafting and design and
specifically its commitment to use MicroStation V8 and related engineering design add-ons
and custom applications. As stated previously, since the DDOT Standards and Workspace
mirror the MDSHA Standards and Workspace, the CAD Manual will also be updated as
major updates or changes occur in the Maryland CAD standards or workspace. The CAD
manual and workspace might also be updated as major changes are introduced in
MicroStation or Geopak, or as the need arises due to changing or unaddressed needs at
DDOT. Updates will be performed by authorized personnel only. No part of the CAD
Standards and Workspace, including cells, fonts, text sizes, etc. are to be revised without
directions from the Chief Engineer or authorized representative. Suggestions are strongly
encouraged and should be directed to Mr. Ardeshir Nafici, Chief, Program Management
Support Division, IPMA at (202) 671-4689.
Purpose
Users will find that properly using the concepts and tools outlined in this manual will better
equip them to produce high-quality CAD drawings more efficiently and consistently. Thus,
the purpose of having a CAD standards manual and the tools and associated electronic files
can be categorized into three main areas:
3) Consistency between Offices and among Consultants: Use of the details, symbols, seed
files and other elements that are part of the DDOT CAD standards will ensure that drawings
will conform to DDOT’s requirements and are consistent—whether projects are done by
consultants or DDOT personnel.
2) Using the DDOT Workspace shows the MicroStation Manager window and
what Workspace Options should be selected to obtain the new V8 CAD
Standards.
When you start MicroStation using the DDOT Workspace, the MicroStation Manager dialog
box will appear with various options in the Workspace section:
Upon loading the MicroStation, the user will immediately know that they are in the DDOT
Workspace by the presence of the DDOT Main Menu and Toolbox.
The Main Menu has pulldowns that allow the user to select additional discipline-specific
menus, set drawing scale factors and access various custom tools to assist in the drafting
process. The DDOT Workspace does not disable any of the MicroStation tools delivered with
the software, but offers additional tools that help users adhere to various requirements of the
CAD standards such as element symbology, level name, file name, etc.
To setup the network workspace on a user’s machine, perform the following steps:
2) Copy the mslocal.cfg file from the LAN Workspace directory, eg: for IPMA one
might use S:\CAD\Workspace\mslocal.cfg
3) Paste to overwrite the mslocal.cfg file on the local machine typically C:\Program
Files\Bentley\Program\MicroStation\config\mslocal.cfg
This will redirect the Workspace root to the network location. Not only will resource files
and other standard files be maintained on the network, but a directory will automatically be
created for each user to store the following custom support files:
Storing these files on the network promotes portability of each user’s custom settings. If a
user moves to a new workstation or has their current workstation rebuilt, all settings will be
retained. Note also that this is a one-time setup. If new standards are released in the future,
they will automatically pass to the user.
6) When the Properties box opens, append the following text to the Target field (note
that it begins with a space):
-wc”[path]\Workspace\startup.cfg”
Click OK.
Workspace Options
The combination of User, Project and Interface determines the user’s working environment
for MicroStation. The significance of these options is explained below.
Project
The DDOT Workspace does not rely on the Project setting to manage project design files and
resources. Rather, this setting is used in-house by some divisions to define certain discipline-
specific settings and standards.
NOTE: For most DDOT users, the Project setting will be preset based on user login
and does not need to be changed!
External consultants may continue to use the Project configuration as needed to define
specific project working directories, etc.
Interface
The choice of Interface determines what custom pull down menus and toolboxes a user will
receive. Depending how it is set up within the organization, this setting could reflect the
user’s network login name, which would allow individual customization.
For the consultant workspace, the user interface variable is not explicitly defined so users
should continue to see the same Interface options that they normally would.
Main Menu
Upon entering the DDOT Workspace, the Main Menu will appear, along with the IDS
Toolbox. The Main Menu contains key pulldown commands that are applicable to any file in
the Workspace.
NOTE: The Main Menu should always remain loaded. Should it become unloaded or is not
visible, there are three ways to reload it. One could either key-in “mdl load DDOTbarmenu”,
use the DDOT pull down menu as shown below or access it from the IDS Tools menu by
clicking on the “d.” tool.
• The Tools pulldown contains links to various drafting tools, both custom developed and
MicroStation delivered.
DDOT Barmenu
This button opens the DDOT Main Menu.
DDOT Tools
This toolbox contains a collection of design production tools for signals and signage, area
measurement, grid tick placement, placing callout labels and changing symbology.
The SIGNAL TOOLS assist the user in placing symbols for existing and proposed signal
poles and mast arms. The dynamic tool allows the user to interactively specify mast
arm lengths and quantity and number of signal heads per mast arm.
Sign Tools
The SIGN TOOLS assist the user in creating guide signs based on MUTCD standards.
The area impact tools provide a method for measuring, filling and labeling a specified
area in one command. The color, fill type, level, measurement units and label units
can all be adjusted by the user.
Place Label
The place label tool quickly creates callout labels for such things as limits of work.
The GRID TICK PLACEMENT TOOL assists the user in placing grid ticks on plan sheets.
By default, the grid ticks are locked to a grid interval of 250 ft. One to three grid ticks
can be placed. The size of the tick is automatically scaled according to the file’s
drawing scale.
Change Level Symbology allows the user to change level symbology of an element or
of an entire file. This will not change the actual symbology attributes of the element
but only how they are displayed if Level Symbology is turned on. Level symbology
must be checked in the view attributes dialog in order for the user to see the changes.
• File Naming Convention: The new DDOT file naming convention requires that file names
follow the format discussed below. This chapter provides details on how to name
MicroStation V8 CAD files. Topics include the explanations of two components of a
standard CAD file name: File Group and the File Discipline.
• File Naming Wizard: The File Naming Wizard has been incorporated within the DDOT
Workspace and is explained in this chapter. It is a tool that can be used to ensure that files
are named correctly. The File Naming Wizard is adopted from MDSHA’s workspace. Use
of this tool makes it easier to create files with a naming structure that adheres to the new
standard.
• Renaming Files: This chapter includes a discussion on renaming a file after it has been
created by the File Naming Wizard.
• File Management and Directory Structure: The section on directory structure for CAD
files discusses how CAD files must be organized and maintained for DDOT projects. This
convention has to be followed for all projects, including those designed in-house and/or by
consultants.
This chapter will describe the CAD files naming convention that needs to be followed for
each design file and will also discuss directory structures. Standard and nonstandard file
types and file naming conventions are also explained. The new standard requires that a CAD
file name consists of three segments, each separated by a dash (-) and an underscore (_). This
section will describe in detail these three segments starting with the format for the first
segment of CAD file name, followed by the format for the third segment and concludes with
a discussion of the middle segment of CAD file name.
Having an established file naming convention and directory structure will be beneficial under
multiple scenarios:
Projects Designed By Consultants: All work performed by consultants for DDOT projects
which start after the release of the CAD Standards manual must follow the file naming and
directory structure guideline of the new DDOT CAD Standards. Upon design completion,
consultants are expected to submit the electronic version of the design files as specified in
Chapter 6, titled Electronic Data Deliverables. If a consultant follows the new file naming
and file structure convention, DDOT personnel and other consultants will find it easy to
determine which electronic file submitted by a consultant has the information they are
seeking.
gDD-TTNN_ProjectID.dgn
where:
File Naming Convention for the First Segment of a CAD File Name
Under the new file naming convention, the format of the first 3 characters of file names is
consistent for all CAD files and is always a one character File Group followed by two
characters which signify the File Discipline. However, the format of the remaining
characters will vary based on the contents of the file for the specific discipline.
The five File Groups are identified by a single-letter abbreviation, which is used as the first
character in the file name. This first character in the file name essentially specifies whether a
file functions as a reference file, as the final plotted output file or as a file that is neither
plotted nor referenced into plan sheets.
p - Print Files/Contract sheets: Files which are used to generate the final
construction plot files are composed of various design files that are referenced into
the master sheet file. These files are printed to deliver the final products of DDOT
CAD, whether they are contract documents, plan sheets, profile sheets, cross-section
sheets, schedules, brochures or wall displays. Any file that is plotted to generate a
final contract document falls into this group.
m – Model/Design Files: Reference files which form the basis for the project
design. These files will be referenced to final Print files (see above). These
files contain existing and proposed design elements such as centerlines,
profiles, edge of road, MOT plans, signing, pavement marking, cross-
Reference Files
sections, etc.
d - Detail Files: Reference files that contain design details such as typical
sections, street light details, drainage details, curb details, etc.
x -Miscellaneous Files: Reference files that do not fall easily into one of the
other Reference file categories. This could, for example, include the border
file.
s - DGN Support/Work Files: Files that are critical to the CAD design process but
are neither plotted nor referenced into plan sheets. Such files may be necessary for
use of design software (e.g. Geopak pattern files) or may simply be used for
engineering, calculations and measurements by the designer.
The majority of files used in creating contract documents will be either an m-model file or a
p-print file. An illustration of the CAD File Group hierarchy with some example file types is
displayed in the chart on the following page.
Sheet/Display Support
Chapter 3-4
sheets, wetland proposed design “Work” files,
existing features sheet
plats, right-of- features across scratch files,
across the entire
way plats, the entire Examples: pattern and
project
construction project Border files, etc shape files for
drawings, and GEOPAK,
redlines as well as Examples:
Examples: quantity
public display Bridge details,
Examples: Topographic, estimating files
drawings and drainage details,
Alignment files, as-built, right- signal details,
hydraulics files, of-way, utility mechanical
TCP phases, files details, etc
and erosion and
sediment
control phases
2005
File Discipline
The second and third characters in a file name identify the File Discipline. The two-character
abbreviation specifies the exact type of information contained in a file. For example the two-
character abbreviation for Contours is CT, for Right of Way, RW, for Highway Profile, HP
and for Geopak Pattern Lines, PT. The complete list of File Disciplines delivered with the
Workspace is shown in Table 1.
However, this list of two-character abbreviations provided with the new DDOT CAD
Standards does not cover all possible information that might be shown in a design file. If
none of the provided abbreviations describe the specific type of information to be shown in
the design file, a File Discipline abbreviation that defines the broad discipline of information
appearing within a particular design file shall be used. Examples of broad descriptions of
disciplines and their two-letter abbreviation include: Topography (TO), Highway Design
(HD), Landscape Design (LD) and Signing (SN). As shown in Table 1, abbreviations for a
large number of design disciplines have been provided as part of the CAD file naming
convention and workspace.
It should be noted that the File Discipline abbreviations available to choose from will differ
depending on the File Group and are very limited for files in the following three File Groups:
Support files, Detail Reference Files and Miscellaneous Reference Files. Five File
Disciplines are available for Detail Reference Files: Bridge/Structure (BR); Drainage (Plan)
Design (DD); Erosion & Sediment Control (ES); Highway Typical (HT); and Stormwater
Management (SW). Three File Disciplines are available for Miscellaneous Reference Files:
Base Line (BL), Layout (LA) and Legend (LG). Three File Disciplines are available for
Support Files: Air Quality (AQ), Highway (plan) Design (HD) and Pattern Lines (PT)
(Geopak patterns).
If users cannot find a sufficiently descriptive File Discipline for some of these file groups, it
is recommended that they rename the file after creating it using the File Naming Wizard.
Please refer to the discussion below on Renaming Files Created with The File Naming
Wizard.
It is important to note that File Discipline abbreviations can be used for more than one File
Group. For example, the File Discipline abbreviation HD is used for all of the following File
Groups: Sheet files, Model Reference Files and Support Files. The first three characters of
the file name for these three groups will be pHD, mHD and sHD.
Table 1 offers a large selection of abbreviations for File Discipline. However, if none of the
choices from the list fit the content of the CAD file being created, users are encouraged to
inform the contact personnel shown in the Intoduction with their recommendation for
additions.
The third segment of a CAD file name is added to make each file name unique because the
first and middle segments are the same for every project containing that type of information.
(For example, the first and middle segment of reference file names that contain survey
information will be the same for all projects). DDOT plans to put in place document
management software in the near future, and the document check-in and checkout process
will be streamlined if each file name is unique.
The six numerical characters that form the third segment of a CAD file name are abbreviated
in the discussions that follow by the symbol ProjectID. It will have the following format:
ProjectID = CCCCCC
File Naming Convention for the Middle Segment of a CAD File Name
The middle segment of a CAD file name will have four alphanumeric characters whose
format and content is determined by the first segment of the file name. These four characters
will be separated from the File Discipline by a dash (-), and will be separated by an
underscore ( _ ) from the ProjectID. The first two characters of the middle segment of a CAD
file name are known as Sheet Type and the last two as Sequence Number.
Sheet Type
The first two characters of the middle segment of a CAD file name represent the Sheet Type
and will follow one of the formats discussed below. The sheet type can be a one-character
descriptor followed by a zero as a placeholder or both characters can be set to two zeros by
the File Naming Wizard. Due to the fact that a File Discipline abbreviation is not provided
for some types of file contents, there will be instances where a user might need to rename a
file that has been created with the File Naming Wizard. Doing so allows the use of a two-
character descriptive abbreviation that will let everyone know at a glance the file content. For
example, a File Discipline abbreviation is not provided for Model (Reference) files which
contain just the centerline of the project. Thus for projects in which the designer prefers to
have the centerline information shown separately from other geometry information, the File
Discipline for the file name can be set to HD for Highway Design, and the file will be
renamed using “CL” for Sheet Type. Thus the portion of the file name preceding the
sequence number will be mHD-CL
Sequence Number
The last two characters of the middle segment of a CAD file name are known as the
Sequence Number and indicate either the sheet number for Print/Sheet files, or the site or
segment number of Model and Support files. If one of these is not specified, the File Naming
Wizard will assign two zeros to the Sequence Number.
For multi-site or multi-segment projects, consultants will provide a file with each electronic
submittal that describes the site number or segment number convention for the project. (See
the Electronic Data Deliverables chapter in this Manual)
The paragraphs below will first describe the abbreviations and formats that will be given to
the middle segment of a file name by the File Naming Wizard, and will be followed by a
discussion on The File Naming Wizard and on renaming a file after it has been created by the
File Naming Wizard.
The two characters of the Sequence Number are represented as NN in the discussions below.
Depending on the file discipline selected for the first segment of the file name, the
Sheet Type for Print/Sheet file names will follow one of the formats below:
T0NN
TTNN T
Sheet Type
S0NN
Title sheet T
00NN
Index sheet I
Notes N
Where T0 = Sheet Type is represented by a one
Schedules S
character abbreviation (see box on right)
followed by a zero Plan sheet P
Cross Section sheet X
TT = Sheet Type is represented by a two letter Profile sheet V
abbreviation. The abbreviation will Detail sheet D
depend on the file discipline chosen for Redlines R
the first segment of the file name. As-Builts A
Figure / Plate F
S0 = Sheet Type is represented by either an E Wall Display W
for existing or P for proposed, followed by Cartography/Mapping M
zero
The choices for T and TT are extensive. There should be no need to rename any
Print/Sheet reference file after it has been created by the File Naming Wizard.
The Sheet Type for Model (Reference) files will have one of the seven formats
discussed below, depending on the File Discipline of the first segment of the file
name. For each of the seven formats, a table is included that lists the File Discipline
choices that will result in that format for Sheet Type.
The Sequence Number for Model (Reference) files will always be the site number
for multi-site projects, the segment number for multi-segment projects or two zeros
for a single site, single segment project.
00NN
Thus if no Sequence Number is specified, the middle segment of the CAD file
name will be assigned four zeros by the File Naming Wizard.
The table below shows the File Discipline selections for the first segment of
Model (reference) file names that will yield a middle segment with the above
format.
Some File Discipline selections for Model (Reference) Files will yield a middle
segment with the following format:
S0NN
If any of the File Disciplines shown in the table below are chosen for the first
segment of the file name, the second segment of the CAD file name will have the
format S0NN.
Some File Discipline selections for Model (Reference) files will yield a middle
segment with either of the following two formats:
-AANN_ or -00NN_
The File Naming Wizard does not provide an option not to have the two zeros, or
to have non-numerical characters. The table below shows the File Discipline
selections that will yield a middle segment with the above format if the File
Naming Wizard is used.
Two File Discipline selections will yield a middle segment with one of the two
following formats:
S0NN_ or -AANN_
The table below shows the File Discipline selections that will yield a middle
segment of a CAD file name with one of the above two formats.
One File Discipline selection will yield a middle segment having one of two
formats:
AANN
The table below shows the File Discipline selection that will yield a middle
segment having the format AANN if the File Naming Wizard is used.
The TO (Topography) selection for File Discipline will yield a middle segment
having the following format:
L0NN
The table below shows the single letter abbreviations available to choose from
and their descriptions:
00NN_ or -TTNN
The middle segment of Detail (Reference) file names will follow the format below:
00NN
The middle segment of a file name will have four zeros if a Sequence Number is not
specified due to project not having multi-sites or segments.
As stated previously, when creating files in which to draw details, five File
Disciplines are available to choose from when using the File Naming Wizard. These
are: Bridge/Structure (BR); Drainage (Plan) Design (DD); Erosion & Sediment
Control (ES); Highway Typical (HT); and Stormwater Management (SW). For these
five File Disciplines, the Sheet Type will always be 00 if the File Naming Wizard is
used when creating the CAD file.
The middle segment of Miscellaneous (Reference) file names will follow the format
below:
00NN
As stated previously, the File Naming Wizard gives a choice of only three File
Disciplines when creating files in Miscellaneous (Reference) Files group. These File
Disciplines are: Base Linen (BL), Layout (LA) and Legend (LG).
The middle segment of Support file names will follow the format below:
00NN or Q0NN
As stated previously, there are only three File Discipline choices for Support files
when creating files using the File Naming Wizard. Of these, Air Quality (AQ) and
Pattern Lines (PT) will have the format 00NN. The third, Highway (Plan) Design
(HD), will offer a choice of 00NN or Q0NN.
Appendix C shows the characters of the first and middle segment of various file names that
will be assigned by the File Naming Wizard.
PRINT FILES
pDD-STNN_ProjectID.dgn
Where p= the file group character that signifies that it is a sheet file which will be
plotted, or used to generate plot files, depending on the software used to
plot.
DD = two-character File Discipline (See Table 1)
ST = Single character abbreviation for plot file Sheet Type (see table on Page
3-8) followed by zero
NN = two-digit Sequence Number. It should match the sheet number where
possible
ProjectID = CCCCCC
Where CCCCCC = Project Code (6 digits)
REFERENCE FILES
tDD-STNN_ProjectID.dgn
Where t= the file group character that represents one of these file type designations:
m = signifies that it is a model/design file
d = signifies that the file is a detail reference file
x = signifies that the file is a miscellaneous reference file
DD = two-character File Discipline
ST = two-digit Sheet Type as discussed above
NN = two-digit Sequence Number, which will be either the site or segment
number. If none specified, it will be two zeros.
ProjectID = CCCCCC
Where CCCCCC = Project Code (6 digits)
The File Naming Wizard not only constructs the file name but also creates one or multiple
files in numbered sequence using standard seed files. Required fields are labeled in red text:
There are two methods to build a file name using the wizard:
2. Select by Description
The File Naming Wizard is described in detail in the MD SHA’s V8 CAD Standards
Training Guide, which has also been included in the files delivered with the DDOT
Workspace. Please refer to V8CADStdTrainingManul.pdf, which is hyperlinked above and is
located in the following sub-directory of the Workspace: ..\Workspace\Documentation. The
Though an extensive abbreviation for File Discipline and Sheet Type is delivered with the
new workspace, it is possible for users to find that none of the abbreviations adequately
describe the model reference file they are creating. For example there are no abbreviations
for files that contain only the Geopak generated centerline. In such cases, a broad file
discipline such as HD for highway design shall be used along with a descriptive Sheet Type
such as “CL’ for centerline.
For Detail (Reference) Files, Miscellaneous (Reference) Files and Support Files, the File
Disciplines available to choose from when using the File Naming Wizard are as few as three
or five. These do not cover all possible disciplines that need to be created on a project. Thus a
user may either create a CAD file without using the File Naming Wizard or rename it after it
has been created with the File Naming Wizard. Doing so enables one to select a File
Discipline that is more appropriate for the file content. In addition, utilizing a descriptive
two-character abbreviation for Sheet Type when renaming a file would result in a CAD
name that more explicitly describes the file’s contents. For example, a Support file for which
a descriptive abbreviation has not been delivered with the Workspace is the Geopak
superelevation shape file. In such cases, a broad file discipline such as HD for highway
design shall be used in the first segment, along with a descriptive Sheet Type such as “GS’
for Geopak shape file within the middle segment of the file name.
Renamed CAD files shall adhere to the format and character limits discussed previously in
this chapter.
When an abbreviation for Sheet Type is used outside of those delivered with the Workspace,
and for multi-site or multi segment projects, consultants will provide with each electronic
submittal a file that describes the site number, segment number and Sheet Type convention
for the project. (See The Electronic Data Deliverables chapter in this Manual)
File Management
This section discusses the directory structure for the files created for DDOT projects. This
directory format is to be followed whether the project is designed by DDOT personnel or by
consultants.
Though consultants are not required to use this structure at their office, they will
ultimately be responsible for ensuring that project files are submitted on CD at the
completion of a project with the directory structure called for in this CAD
Standards Manual, with the correct reference files attached.
In some instances, DDOT may assign a new task number for supplemental work on an
existing project. In such situations, unless directed by the DDOT project manager, the
original contract number should be utilized for the directory name.
Directory Setup for a Single Site Project Directory Setup for a Multiple Site Project
CCCCCC CCCCCC
├───As-Built
├───As-Built │ ├───Site-11
├───Details │ └───Site-12
├───Plot Files ├───Details
├───plot files
│ ├───30%-2005-01-24 │ ├───30%-2005-01-24
│ ├───60%-2005-06-19 │ │ ├───Common
│ ├───90%-2005-10-21 │ │ ├───Site-11
│ │ └───Site-12
│ └───Final-2005-12-17 │ ├───60%-2005-06-19
├───Ref │ │ ├───Common
├───Sheet Files │ │ ├───Site-11
│ │ └───Site-12
│ ├───30%-2005-01-24 │ ├───90%-2005-10-21
│ ├───60%-2005-06-19 │ │ ├───Common
│ │ ├───Site-11
│ ├───90%-2005-10-21 │ │ └───Site-12
│ └───Final-2005-12-17 │ └───Final-2005-12-17
├───Support │ ├───Common
│ ├───Site-11
│ ├───Calcs-other │ └───Site-12
│ │ ├───30%-2005-01-24 ├───Ref
│ │ ├───60%-2005-06-19 │ ├───Common
│ ├───Site-11
│ │ ├───90%-2005-10-21 │ └───Site-12
│ │ └───Final-2005-12-17 ├───Sheet Files
│ ├───Calcs-quantiies │ ├───30%-2005-01-24
│ │ ├───Common
│ │ ├───30%-2005-01-24 │ │ ├───Site-11
│ │ ├───60%-2005-06-19 │ │ └───Site-12
│ ├───60%-2005-06-19
│ │ ├───90%-2005-10-21 │ │ ├───Common
│ │ └───Final-2005-12-17 │ │ ├───Site-11
│ ├───Geopak │ │ └───Site-12
│ ├───90%-2005-10-21
│ │ ├───Cogo │ │ ├───Common
│ │ │ ├───Criteria │ │ ├───Site-11
│ │ │ ├───Input files │ │ └───Site-12
│ └───Final-2005-12-17
│ │ │ └───Reports │ ├───Common
│ │ ├───DTM │ ├───Site-11
│ │ │ ├───2005-01-24 │ └───Site-12
├───Support
│ │ │ └───2005-02-27 │ ├───Calcs-other
│ │ ├───Misc │ │ ├───30%-2005-01-24
│ │ ├───60%-2005-06-19
│ │ ├───Pref │ │ ├───90%-2005-10-21
│ │ └───Report │ │ └───Final-2005-12-17
│ └───Misc │ ├───Calcs-quantiies
│ │ ├───30%-2005-01-24
├───Survey │ │ ├───60%-2005-06-19
│ ├───2005-01-15 │ │ ├───90%-2005-10-21
│ └───2005-02-26 │ │ └───Final-2005-12-17
│ ├───Geopak
└───Working-temp │ │ ├───Cogo
│ │ │ ├───Criteria
│ │ │ ├───Input files
│ │ │ └───Reports
│ │ ├───DTM
│ │ │ ├───2005-01-24
│ │ │ └───2005-02-27
│ │ ├───Misc
│ │ ├───Pref
│ │ └───Report
│ └───Misc
├───Survey
│ ├───2005-01-15
│ └───2005-02-26
└───Working-temp
• Keep all design files belonging to one project together in the proper folder. They can be
referenced easily if they are kept together. They may become disconnected if they are not
kept in the same folder. Files submitted by consultants or others upon project completion
should not be renamed.
• Update reference files regularly to ensure the most current versions of all design files are
being used. Check the file folder on the server to see if any newer version exists. Also,
keep updated versions of your files on the server so that others can update your files as
their reference files.
● Seed Files lists DDOT’s standard seed files for creating new MicroStation V8 files.
● Standard Settings provides details about the settings contained in the standard
seed files. This includes notes about Working Units, Survey Feet, Coordinate
Readout, Drawing Scale (NEW in V8!), Color Tables and DGN Libraries.
● Standard Elements provides information about the feature symbology that has
been developed for the V8 standards, including level names, line weights, line styles
and text styles.
Seed Files
When a new dgn file is created, MicroStation makes a copy of the specified template file.
Template files are known as seed files. To ensure design file setup consistency, the following
standard seed files have been created for use on DDOT projects. These seed files should
always be used as a basis for developing any new design files including cell libraries.
The following seed file has been developed for use when creating bridge or other detail
sheets in MicroStation 2004.
This seed file consists of multiple V8 Models that are self-referenced at different scales to
facilitate the creation of multiple details at different scales within the same file. (For more
information on working with Multiple Models, refer to the MDSHA V8 CAD Standards
Training Guide in the Documentation directory of the Workspace. As noted previously, in
instances of discrepancy, the DDOT CAD Standards Manual and the DDOT Workspace
shall govern).
The MicroStation V8 file format represents a major change in the way that coordinate
data is stored. The 32-bit integer-based design plane has been replaced by a double
precision floating point coordinate system. This has the following practical effects:
3. Unlike Pre-V8 MicroStation, changing the working units does not affect the
size of elements.
In V7, if you draw an element measuring 10 ft, then change the working units from
feet to meters, the element would measure 10 m long. Now with V8, the same change
from feet to meters would result in an element correctly measuring 3.048 m.
The workspace contains a custom units definition file, units.def, which was created by
MDSHA and which defines survey feet and controls the conversion of V7 files to V8.
Drawing Scale
One of the key features of this CAD Standards is the use of a drawing scale which is
displayed along the top of the MicroStation window. (If it does not appear in your window,
select Scale > Display Current Scale from the Main Menu.)
The drawing scale may be changed by selecting the appropriate scale factor from the Main
Menu pulldown. The scale factor is stored with the file.
All scale-dependent drawing elements, i.e. text, cells and linestyles ,have been defined in the
CAD Standards at a unit (1:1) scale. The element is then scaled up or down by the drawing
scale factor when it is selected from a barmenu. This helps maintain consistency of scale-
dependent drawing features, regardless of the scale being used.
This is a new feature in MicroStation 2004 and has the advantage of being applied at the
Model level (as opposed to the linestyle scale factor which is applied across all models in a
file.)
DGN Library
One of the major new changes to V8 is the use of DGN Library files (DGNLIBS) to
maintain and deliver CAD Standards. The DGNLIB provides these standard items to the user
but locks them from being edited, thus helping to maintain Standards. The standard items can
include the following:
• Levels
• Level Filters
• Text Styles
• Dimension Styles
• Cells
Only level filters and text styles are maintained in the current DDOT’s standard
DGNLIB. All other standard elements are delivered through other methods. Please
refer to the relevant sections below for more information. Once the CAD Standards
mature through testing and use, more of the above items will likely be put into
DGNLIBS.
Features
A feature corresponds in a very specific manner to a single type of design information
contained within a file type. A feature defines not only a specific piece of information but
also how it is to appear within the design file. A single file type may contain hundreds of
features, each with its own unique set of attributes.
A comprehensive survey of all features in use by Maryland SHA has been made available to
DDOT in-house personnel and the consulting community without modification for use as
needed. It is maintained in the IDSIM database received from SHA, along with all primary
attributes (level, color, weight, and style, which are also known as symbology) and secondary
attributes (including text size, font, etc).
The most important attributes assigned to a feature are level, color, weight and style. Many
other parameters, such as text font, text size and so on may be defined for a particular feature,
but these extra parameters are not necessarily used for identification purposes. By definition,
two elements belong to the same feature whenever they have the same cell name or level,
color, weight and style, even if other parameters may be different.
Barmenus
As a general rule, the barmenus are used to find the standard symbology (level, color, style
and weight) for any item that is contained in the file. If you need an item and can’t find it in
the barmenus or Feature Search tool, contact the appropriate individuals listed in the
Introduction of this manual. A new feature might need to be incorporated into the next
release of the DDOT CAD Standards.
Levels
Levels are named slots for graphical elements in a file whose display can be turned on or off.
This allows users to have lots of information saved in one file, even if all material does not
need to be used or viewed at the same time. MicroStation V8 allows you to define an
unlimited number of named levels.
Level Names
The V8 level naming convention developed at MDSHA is based on the guidelines set
forth by the National CAD Standards with changes as needed to accommodate a civil
transportation workflow. DDOT has adopted the same level naming convention, and
this is shown below:
As shown in the examples below, most of the levels defined in the seed files have no
need to define the sub-minor group. Thus the majority of level names are in the
format MAJR-MINR.
Level Libraries
Level names are managed by attaching level libraries. When a barmenu is selected,
the appropriate level library is attached. The library remains attached if you close and
reopen the file. Note that when level libraries are detached, or if the file is opened
outside of the standard DDOT Workspace, used levels will still appear while unused
levels will not.
It is important to mention that levels are not enforced via DGN Libraries for the new
DDOT CAD Standards. Individual level libraries have been created for each file and
can be attached as needed by selecting the appropriate Barmenu from the DDOT
Main Menu. Users also have the option to create new levels as needed and are
encouraged to forward needs and suggestions to the contact person provided in the
Introduction.
Level Filters
Level filters serve two purposes: (1) to limit the number of levels that appear in a
level list and (2) to turn groups of levels on and off when needed. The latter
application is especially useful for controlling level display of attached reference
files.
Line Weights
If plotted line thicknesses are not formally defined, plots tend to have slightly different
appearance depending on the plotter used, the plotting software, driver, pen table, etc. To
avoid this, the DDOT V8 CAD Standards has assigned plotted line thicknesses to
MicroStation weights 0-15 in accordance with industry standard drafting pens.
Standard pen tables for Iplot and PLT files for MicroStation plotting with the above line
thicknesses defined are delivered in the Workspace. (Refer to the Plotting chapter for more
details). In reality, most standard drafting can and should be accomplished using line weights
0-6, as the weights above 6 are extremely thick.
Thin Lines (wt = 0). Thin lines should be used for existing elements such as
baseline/centerline, existing edge of road, existing sidewalks, existing handicap ramps, etc.
These lines should also be used for depicting background object lines, hidden lines, and most
patterning symbols.
Medium Lines (wt = 1). Medium lines should be used for depicting dimension
leaders/witness lines, dimension lines, dimension text, text for notes/callouts, schedule
boxes/charts, text inside schedules, minor object lines, line terminators (arrowheads, dots,
and slashes) and note leader lines.
Medium Thick Lines (wt = 2, 3). Medium thick lines are the default line weight for drawing
most proposed objects including proposed centerline, edge of road, profiles, proposed inlets
and pipes, etc. Medium thick lines should also be used for section titles.
Thick Lines (wt = 4). Thick lines should be used for minor title underlining, text for titles
and object lines requiring special emphasis.
Extra Thick Lines (wt = 6). Extra thick lines should be used sparingly. Extra thick widths
are appropriate for use as elevation grade lines, building footprints or top of grade lines on
section/foundation details.
This appropriate scale factor is applied automatically when these styles are selected from a
barmenu. However, if they are selected through the usual active attribute interface, they may
appear incorrect in the drawing because of an improperly set scale or an on/off toggle that
was pressed accidentally. When this happens, use the commands under the Main Menu to
apply or remove the scale factor setting. (DDOT Main Menu> Scale > Drawing Scale ON,
and so on.)
Cells
One of the key changes to the use of cells in MicroStation V8 is the ability to place cells at
True Scale. E.g., if a cell is drawn 1 foot wideand placed in a metric drawing, it would
measure 0.3048 m. Similarly, V8 will rectify the size of cells drawn in files with different
units of resolution. This is accomplished through the
True Scale setting.
As with the linestyles, most symbol-type cells (i.e. scale-dependent) have been created at a
unit size for easy placement. For these cells, the active scale should be set to match the
drawing scale (i.e. 1”=50’). When selected from one of the barmenus, the correct active scale
will be applied automatically.
Numerous cell libraries are supplied with the MDSHA workspace. These libraries are also
included in the DDOT Workspace. Appendix D lists the MDSHA cell libraries supplied with
the Workspace. The cells in these libraries have not been modified in any way. Users should
use the MDSHA supplied cell libraries only if a cell for that feature does not exist in the
DDOT cell library.
Fonts
The CAD Standards have a single resource file (DDOTfonts.rsc) that contains all fonts.
In order to achieve more consistent plan sets, the following standard fonts are recommended
for use:
Use of these fonts is being encouraged through their implementation as Text Styles.
Text Styles
MicroStation V8 has introduced a new feature to facilitate the placement of text – Text
Styles. Standard text styles can be created with preset font, text height, text width, etc., for
quick and easy placement. The DDOT Workspace takes advantage of Text Styles in the
following ways:
One of the primary advantages of Text Styles, aside from maintaining consistent appearance
of text, is the ability to propagate the drawing scale to the size of the text. As long as the
Drawing Scale has been properly set from the Main Menu, the size of the text will match. In
MicroStation 2004, this is achieved by enabling the Model Annotation Scale Lock.
• Sample text styles have been placed in the seed files. Note that these are
currently not locked for editing by a DGNLIB file.
• Text Styles are automatically scaled by the active Drawing Scale as follows:
MS V8.1 – changing the drawing scale via the Main barmenu triggers
a macro that scales the text size of all text styles in the file by an
appropriate factor.
MS 2004 – text styles are maintained at unit size (1”=1’) but will be
scaled at the time of placement if the Model Annotation Scale Lock is
enabled.
In 2004, the user will be asked if the drawing scale should be applied to existing text… the
recommended response is NO.
If a file was not created based on a standard seed file, it will not contain proper text
style definitions. (This is common for files converted to V8 from an earlier version.)
Similarly, if a file was created in V8.1 and later worked on in 2004, there will likely
be a disconnect with text size (owing to use of the Model Annotation Scale Factor).
To address both of these issues, there is a command on the Main Menu that will
import the standard text styles, scaling them as appropriate. (Main > DDOT Toolbox
> Import DDOT Textstyles) Be careful, however, because this action will delete any
custom text styles you may have created.
Dimension Styles
Dimension Styles are another new MS V8 item. A dimension is a label that shows the linear,
radial or angular measurement of an element. A dimension style is a saved set of
dimensioning settings. Dimension settings can be stored in either a DGN file or a DGN
library. Dimension styles have been created for: Architectural, Structural, Civil, Detail and
Survey. These dimension styles are maintained in the seed files delivered with the CAD
standards rather than in the DGNLIB. As with the Text Styles, missing Dimension Styles
may be imported to a file from the Main Menu (Main > DDOT Toolbox > Import DDOT
Dimension Styles). Once these styles have been refined through use, they may be added to
the DGNLIB file.
• DDOT Border File discusses the use of the standard D-size border file developed for
creation of contract documents at DDOT.
• Text Placement: Model vs. Print Files discusses the proper placement of text in
design files.
The border file has individual saved views created to deliver discipline-specific settings.
When the border file is attached to the plan sheet as a reference file, the appropriate saved
view should be selected. The borders and standard sheets provided in the Workspace are
drawn to the conventional 1" = 1' scale and should be scaled up or down accordingly when
attached. Please refer to MDSHA’s V8 CAD Standards Training Guide for more
information. (As noted previously, in instances of discrepancy, the DDOT CAD Standards
Manual and the DDOT Workspace shall govern).
Reference Files
Many interface changes have been made to the way in which reference files are attached. The
following recommendations are provided to help you understand the new V8 settings.
1. active directory
2. relative path directory
3. MS_RFDIR directory
4. full path directory
Coincident-World
This setting adjusts reference files with different
Global Origins. The Workspace is set up by default
to attach coincident-world orientation. It is
recommended that this option always be enabled.
True Scale
This setting adjusts reference files with different Units
of Resolution. As with Coincident-World, it is
recommended that this option always be enabled.
Such practice, while common to the V7 workflow, creates the undesirable issue of having
multiple versions of the same file in production. If the information in the file needs to
change, there is a likelihood that the changes will not be made uniformly to both. Sooner or
later, confusion arises as to which copy of the file reflects the most up-to-date information.
Repeat: there is no longer a need to convert 3D files to 2D. Don’t do it! If the need arises, set
your active depth to zero and activate the Depth Lock.
The advantage of placing text items in the Model file is that as the design is refined, the
changes can be made globally to the entire project. The disadvantage is that text in a given
Model file often overlaps with text in another Model file, both of which are referenced into
the same plan sheet. When this occurs, the recommended workflow is to resolve the text
conflict in the Print file, NOT in the Model file. As follows:
1. Identify the text item that is least likely to change (e.g. topo text labels)
2. Copy all the text from the level on which the conflicting text is located into
the Print file (i.e. plan sheet).
3. Turn off the Model file level containing the conflicting text.
Note that all text in a given model file should be at the same scale. 1”=20’ is used for most
projects, and topo is generated at that scale unless a specific request is made in advance.
Sometimes, a designer requires the same annotation for different scales (e.g. geometry sheet
stationing, wetland plates). Given the ability in MicroStation 2004 to set the Annotation
Scale at the model level, designers are encouraged to create a separate model within the same
DGN file that is reserved solely for the text at the alternate scale.
MicroStation Files
All drafting for DDOT projects should be done using the version of MicroStation currently in
use at DDOT. If directed otherwise by the DDOT project manager, more current versions of
the software shall be allowed for use on a project. However, older versions of either
MicroStation or Geopak than are in current use at DDOT are not allowed. It is the
consultant’s responsibility to make sure they are using the proper version.
The file naming convention for the MicroStation files shall be as specified in the CAD Files
Management and File Naming Conventions (Chapter 3). All MicroStation files required to
recreate the project including plotted sheets and reference files shall be submitted as well as
any additional resource files used that are not part of the DDOT Workspace, i.e. fonts used to
create a consultant’s name or logo.
• .gpk file
• .prj files
• cogo input files in ASCII format. These input files could be for creating horizontal
alignments, vertical alignments, ROW lines, etc
• COGO output files in ASCII format
• Tin files required to create DTM surface files of existing ground, final design surface, as
well as intermediate and as built surfaces if called for by the contract
• criteria files for creating superelevation shapes
• criteria files for generating cross-sections
• criteria files for creating cross-section layout file
• criteria files for cross-section annotation
• criteria files for calculating earthwork
• criteria files for quantity calculations
• Resource files, i.e. .ddb file, used for drawing elements to aid in quantity calculations
Readme.txt
In order to facilitate future data retrieval, all electronic data submittals should be
accompanied by an electronic file titled readme.txt. This file will contain a list of all the
electronic files that are part of the submittal and will indicate the version of MicroStation and
Geopak used for the project.
The DDOT Workspace and accompanying electronic files, such as seed files and cell
libraries, will be provided by DDOT on a CD. However, these files are subject to change
during a project’s life cycle, and consultants may periodically receive new data files. Thus it
is important to include a note in the readme.txt file that shows the release date of the DDOT
provided data.
For multi-site or multi segment projects, consultants will include in the read me.txt file an
explanation of the site number or segment number convention for the project.
A hard copy of the readme.txt file shall be submitted with each CD containing electronic
submittals.
This chapter describes the plotting procedures to be used at DDOT. Plotting refers to using a
printer or large-format plotter to print a hard copy on paper from CAD drawings. Plots can be
created with either I-PLOT or Standard MicroStation plotting. Resources provided in the V8
Standards for both methods are described in this chapter. MicroStation plotting is commonly
used at DDOT. If DDOT decides to use I-Plot in the future, changing from one method to the
other should not result in different outputs. In order to provide a Standard for baseline
plotting, plot drivers were created for standard MicroStation plotting, including both mono
and full-color plans.
Plotting Standards formalizes the plotting weights and line styles that should be
used when producing DDOT plans from CAD files.
Standard MicroStation Plotting covers using pen tables, identifying the plotting
area, verifying the plotter, setting the scale and more.
Plotting Standards
DDOT is attempting for the first time to standardize plotting characteristics for contract
documents. These parameters include the plotted line thickness (in inches) for standard
MicroStation weights 0-15 and the stroke lengths (in inches) for standard MicroStation line
styles 1-7. The goal is to establish a baseline by which any plots can be duplicated using any
plotting method. The standard plot drivers and IPLOT pen tables included in the Workspace
should serve as a basis for achieving this result.
Large-format Plotters: A roll-feed machine (typically 36-inch rolls) for the production of
larger drawings should be inkjet or thermal. These print a standard-size 34 x 22-inch sheet
from MicroStation for all construction documents and plans. Other sizes are used for large
wall-display boards.
Standard-format LaserJet and Inkjet Printers: Half-size plans are often required (11x 17-
inch, tabloid). This is also used in the production of plats, smaller drawings and related
documents.
Line Widths
The DDOT V8 CAD Standards establishes plotted line thicknesses. If this is not defined, the
line thicknesses that appear on plots will be dictated by the plotter. DDOT has attempted to
correct this by hard coding the plotted line thicknesses into the new MicroStation plot
drivers. This is also done for IPLOT pentables for the convenience of consulting firms which
use IPLOT. Line weights 0-15 have been re-defined to correspond with the thicknesses of
traditional drafting pens, as follows:
Color Table
The standard color table for all DDOT design projects is ClorDDOT.tbl. This color table
defines the RGB values for the MicroStation colors 0-255. The monochromatic (black &
white) pen tables have been set up for use with this table such that all colors plot as black,
with the exception of those color values defined below.
1. Place a fence or arrange within a view, the portion of the drawing you wish to
plot. If you need to plot to a scale, you must place a fence around the sheet border.
2. Start the plot process by keying in PLOT or PRINT in the key-in window.
Alternatively, you may press the accelerator key CTRL, + the P key.
Alternatively, you may select the Print/Plot command from the File pull-down
menu.
3. Examine the status line on the Plot dialog box to ensure that “Fence (View n)”
displays if you intend to plot contents within the fence you have placed.
Otherwise, it will display “View n”.
Plot Drivers:
Plot drivers determine how the MicroStation elements are translated to the printer, including
exact colors and the thickness of various line weights. After identifying the plotting area, you
need to select a plotter driver. The following drivers are delivered in the V8 Standards for
various uses.
FullMono.PLT – For plan sheet production. This will plot all colors, regardless of how they
are displayed, as black, except for the following:
HalfColor.PLT – Identical to FullColor.PLT. However, line weights are scaled for 11 x 17-
inch prints.
The active driver name displays in the Plot dialog box next to the icons. You will normally
use “printer.plt” for your plots. This driver maps to the Windows system printer driver. If
you want to change the plotter driver so that you do not have to use the Windows system
printer, follow these steps:
1. Click the Plotter Driver button, the icon farthest to the right.
2. From the Select Plotter Driver File dialog box, select the appropriate plotter
driver. By doing so , you are indirectly selecting the size of the plot you are going
to generate.
2. Key in the size as a percentage of normal and let MicroStation calculate the scale.
Keep in mind that this is the ratio of design file master units to plotting units. This means
that if you are plotting a drawing created using feet, and the scale is 4 feet per inch, the result
is a final ratio of 48:1 (48 inches, in the drawing, to 1 inch of paper).
The scale factor and the four fields in the Margins section of the Plot Layout dialog box are
interlinked. When you change one, the other values are automatically updated to reflect the
change.
Rotate 90:
The Rotate 90 Degrees option on the Page Setup dialog box is similar to a
portrait/landscape option on printer drivers. Your design may fit more economically on a
sheet of paper if you rotate it 90 degrees.
Plot Options:
The Plot Options icon brings up a list of additional options for plotting your drawing. Some
of the options can be dimmed because they are displayed for information only. If you want to
modify any of the plot options, you will need to do so in the View Attribute dialog box in
the Settings menu.
1. Click on the Plot icon, which launches the plot if “printer.plt” is the driver being
used.
2. If a driver other than “printer.plt” is selected, you are prompted to give the file
name into which the plot data will be placed. The default extension of this file is
.000. MicroStation will then create a plot instruction data file for processing by
the plotter later.
The most common method for transferring plot data to the plotter is to use MicroStation’s
PlotFile batch program. From the DOS prompt, key in PLOTFILE filename and hit Enter.
While transmitting the plot file to the plotter, the computer will not be available for
other work.
Depending on the purpose, you may want to generate the entire project, a drawing sheet or a
close-up view to focus on an issue. Some applications include:
• Renderings/Displays
• Using Utilities>Image>Save
You can actually print from any windows software to HD BW Image, such as Excel, Word
or PowerPoint.
The resolution is high enough for full-size plots with clear text and symbols, and the file size
is small enough to run the files through an Internet Web viewer or to put hundreds of plan
sheet images on a single compact disc. The small file size for such a high resolution is
accomplished because the driver generates a Monochrome (Black and White only) image.
However, it goes further than strictly turning all colors into solid black; the driver transforms
shades of gray or colors into finely speckled black. From a distance, the speckles appear
gray.
When using MicroStation’s standard File > Print command, select the following:
When using MicroStation’s add-on I-PLOT printing software, select the following:
IMPORTANT: Once the files are generated at this location, they should be copied to the
appropriate project directory. ONCE A WEEK, THE FILES IN THIS FOLDER WILL
BE AUTOMATICALLY DELETED WITH NO PRIOR NOTICE.
In addition to the folder where images are printed out, the Administrator implements several
important settings on the plot server which are outlined on the following pages.
The menu above shows the current directory where TIFs will be stored as well as the
Naming Pattern for files that are generated through the printer, which is to use the
DOCROOT, or filename without extension and add the .tif extension at the end.
Select Pattern Setup to change these settings.
Make sure you are on the Device Settings tab of the printer Properties window as
shown below.
Select InterPlot Device Attributes, and you can set up a custom size using the menu
below.
These generate plots with similar line thickness and appearance as a normal plot, including
white background.
TIFF_PPT.PLT – Produces images that are 1024 x 768 pixels in size, which is appropriate
for PowerPoint presentations, inserting smaller images in documents or e-mails. File size is
low – around 140 KB.
Using Utilities>Image>Save
This is useful primarily in 3D renderings as the various rendering shadings (e.g., ray trace)
are available. It has been applied to 2D drawings using wireframe shading to generate
plotlike images.
The results will be WYSIWYG, except that you can generate an image of as high a
resolution as you desire.
This glossary was developed to ensure that terms were consistent in this manual and with
DDOT practices, recognizing that meanings may differ when used outside the context of
these Standards.
MicroStation V8
MicroStation V8 is the current version of Bentley’s CAD software adopted by DDOT. The
upgrade from MicroStation J to MicroStation V8 marks a new milestone in CAD
technologies, introducing several new features:
DDOT’s V8 standards are designed to work with MicroStation Version 08.01.02.15 or later.
GIS Attributes
GIS Attribute flags are necessary to create the needed GIS layers from the CAD File. These
features must be accommodated. Such features include traffic signals, storm drains and
culverts.
Custom software to support workflows will make it easier to work together. Numerous
custom utilities, such as Barmenus, Toolbox and several others are delivered with the
Standards. These utilities simplify adherence to Standards while promoting consistency and
efficiency.
These tools automate the process of creating and drafting project plans. They ensure that the
plotted final result will be consistent and legible. By developing the files consistently, we are
imparting “intelligence” into the files. In other words, the various items in the file are coded
consistently with a knowledge base that tells us what the items are representing. This
intelligence is the foundation for further application development that relies on scanning the
file for the features based on the consistent end product. Some examples are below:
7) Design Rules: CAD Standards accommodate Design Rules. Design Rules are
the component interactions that provide flags for the designer when a design
does not meet DDOT design criteria. For example, during the placement of a
signal pole, a flag appears indicating that it is too close to the curb line and
does not meet DDOT criteria. Therefore, it must be placed in a new location.
Notes
Where:
Shown below are the names that the File Naming Wizard will assign to various file contents.
The middle segment of a file name is separated by a “-“ (dash) from the first segment and by
a “_” (an underscore) from the third segment of a file name. In the tables below, if there are
less than four characters in the middle segment of the file name, please note that the name
would actually have zeros to bring the total number of characters of the middle segment to
four.
** shading may be addressed though alternate workflow, or in separate file named MSH
Miscellaneous Files
MDSHA has numerous cell libraries contained in multiple directories. These cell libraries
have been made available to DDOT personnel as well as to consultants without any
modification. The acronyms used in the cell library names or directory names are based on
the major divisions of MDSHA. Shown below is an explanation of the divisions and
responsibilities of such divisions at MDSHA, provided to make it easier to understand the
cell libraries’ directory structure. However, as stated earlier, the three cell libraries that
contains most, if not all, of the cells required on DDOT projects are named
DDOT_design.cel, DDOT_survey.cel and DDOT_traffic.cel.
• The Office of Materials and Technology (OMT) tests materials for the
planning, design, construction and maintenance offices, focusing on safety
• The Office of Traffic and Safety (OOTS) designs lights, traffic signals,
street signs and traffic control devices and promotes highway safety.
• The Office of Real Estate (ORE) deals with legal issues related to right-of-
way acquisitions and property plats.
1
Note the term UG refers to an underground utility and applies to existing utilities. It is noted as such because that is part
of the linestyle name used in the CAD Workspace files.
2
Size and Type labels shall be added by the designer to all existing utilities and proposed stormdrain lines.
Proposed Underdrain
State Line
ROW
Lot Line
Historic
Parkland
PFA
Bush Line
Wetland Boundary
Woods Line
Floodplain
Existing Railroad
Existing Streetcar
Limit of Disturbance
TRAFFIC ITEMS
Stripe Skip 10 30
Ditch Flow
Flow Path
Baffle Boards
Perimeter Dike/Swale-1
Perimeter Dike/Swale-2
Silt Fence