Bentley MX - 2004 Edition MXROAD - Introduction 022004

Bentley MXROAD 2004 Edition
Introduction
DAA034400−1/0001
ii MXROAD Intr oduction
Trademarks
Trademarks
Bentley, the ’B’ Bentley logo, and MircoStation are registered trademarks of
Bentley Systems, Incorporated or Bentley Software, Inc.
MX, the MX logo, Infrasoft, Arenium and the Arenium logo are registered
trademarks of Infrasoft.
Adobe, the Adobe logo, Acrobat, the Acrobat logo, Distiller, Exchange and
PostScript are trademarks of Adobe Systems Incorporated.
AutoCAD, and AutoCAD Map are registered trademarks of Autodesk, Inc.
HOOPS is a registered trademark of Tech Soft America.
OpenGL is a registered trademark of Silicon Graphics, Inc.
NetWare® is a trademark of Novell, Inc.
Internet Explorer, MDAC, Windows, Windows NT, Windows 2000 and

Windows XP and True Type are registered trademarks of Microsoft
Corporation.
Copyright
Copyright

2004 Bentley Systems, Incorporated.
All rights reserved under the copyright laws of the United States.
Portions Copyright © ComponentOne, LLC 1991−2002. All Rights Reserved
DWGdirect 2002 by OpenDWG Alliance Inc. All rights reserved..
MXROAD Intr oduction iii

iv MXROAD Intr oduction
Table of Contents
MX Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−1
MX Basics − Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−1
What is String Modeling? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−2
MX Environment − Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−8
Common Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−11
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−15
AutoCAD Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
MicroStation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−22
The Applications Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−28
Starting MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−30
Starting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−31
Typical Project Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−33
Creating a survey model from imported data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−33
Assigning model defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−35
Creating a working display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−35
Viewing the working display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−37
Producing a design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−38
Analyzing the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−40
Modifying the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−42
Creating drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−43
Producing visualizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−44
Creating reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−45
Exporting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−46
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−46
System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−49
User Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−52
MXROAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1
MXROAD − Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1
Standard String Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−2
Options in MXROAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−2
Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−2
Surface Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−3
Alignment Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−4
Road Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−7
Intersection Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−11
Pavement and Subgrade Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−12
Modifying the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−14
Project Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−15
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i−1
MXROAD Intr oduction v

Table of Contents
vi MXROAD Intr oduction

1
MX Basics
MX Basics − Overview
This section gives an overview of MX and describes the basic principles of
operation. In particular, the concepts of string modeling are given together with
a description of how MX data may be manipulated from any of the three MX
environments; Windows, AutoCAD or MicroStation. An overview of each MX
option is also provided in a typical project sequence.
This section covers the following topics:
What is string modeling?
The MX environments − Windows, AutoCAD and MicroStation
The Applications toolbar
Starting MX
Starting a project
Typical project sequence
Using the on−line help and tutorials
System administration
User support
The next section deals with the options specific to MXROAD.
MXROAD Intr oduction 1−1

1
MX Basics
What is String Modeling?

In any project, MX uses a simple hierarchy of models, strings and points to
store data. Each model can be thought of as a separate surface. Models are
stored in a model file and contain strings which are made up of 3D coordinate
points (X, Y, Z) linked together. These strings are used to represent physical
features. Generally, all project data is stored in a single folder on your PC.
The model file and models

The illustration below shows the content of a typical model file for a project.
There is only one model file for each project, but many models can coexist
within the model file, each storing a specific set of data. For example, one
model may contain survey data while the other is used for the proposed design.
Isopachyte
Survey Alignment Triangulation
Survey
Stations
Existing Design Boundary

Ground
Triangulation Sections Drainage
Contours Visualization
Figure 1 − The model file
1−2 MXROAD Intr oduction

MX Basics
Strings and string links

All MX data is held as strings. A string is a series of points, each joined to its
predecessor and successor by a straight or curve−fitted line. This is referred to
as a string link. Strings in MX have dimensions at each point, where a
dimension is simply a piece of data such as an X, Y or Z coordinate, or another
attribute such as the bearing at the point.
MX recognizes many types of string:
Station strings link survey instrument stations. The dimensions of each
station are the X,Y and Z co−ordinates and the name of the station, so a
station string is a 4D string.
Contour strings represent contours. The dimensions of each point are the
X and Y co−ordinates, so a contour string is a 2D string. The elevation of
the contour (the Z value) is only stored once because it is common to all
string points.
Feature strings define either linear ground features such as a ridge or the
base of a hill, or design features such as a roadway edge or back of unpaved
shoulder. The dimensions of each point in the string are the X,Y and Z
co−ordinates of the point, so a feature string is a 3D string.
Point strings represent discrete items such as manholes and lamp columns.
A point string records the X,Y and Z co−ordinates of a set of like items, but
there is no physical continuity from item to item, ie, there is no string link.
MX processes these strings differently from other strings, particularly when
sectioning or triangulating. Point strings generally record detail in survey
models.
Master strings are used to represent road or railroad alignment center lines
and other master design lines. They are 6D strings. The first three
dimensions of each point in the string are the X,Y and Z co−ordinates,
followed by the station along the string, the bearing of the string at that
point, and the radius of curvature.
Section strings represent cross−sections, profiles or baseline sections
(profiles taken along a straight baseline). These are all 5D strings. With
cross−sections, for example, the first three dimensions of each point are the
X,Y and Z coordinates, followed by the offset of the point from the
reference string, and the name of the string that was cut to produce the
section.
When MX creates section strings, elevations are linearly interpolated to the
point at which the section line intersects the string link.
Earthwork strings represent the outer limits of embankments and cuttings.
These are 5D strings. The first three dimensions of each point are the X,Y
and Z coordinates, followed by the offset and bearing of a line normal to
the line used to generate the string (called the reference line).
Volume strings generally contain earthwork volumes. These are 10D strings
and are used to store volumes calculated between successive sections. The

1
MX Basics
first three dimensions of each point are the X,Y and Z coordinates,
followed by the station and the volume between the sections of two
specified models (usually ground and design models). The remaining
dimensions record volumes between the various strata, though since this
information is not always available, these dimensions are often zero.
Mass−haul strings contain accumulated mass−haul balances along a road
design. These are 10D strings, the first three dimensions of each point are
the X,Y and Z coordinates, followed by the station and the accumulated
mass−haul balance at that station. The remaining dimensions record
cumulative balances for various strata, where these are known; otherwise
they are zero.
Triangulation strings contain a lattice of links between 3D triangle vertices.
Adjacent triangle information is also stored to optimize the display and
analysis of a triangulated surface. MX always includes string links when
triangulating.
Text strings are multi−dimensional strings that hold character information
for naming items in drawings. The first two dimensions of each point are
the X and Y coordinates of the start of the text. The third dimension
specifies the height of the characters when plotted. The fourth dimension
is the bearing of the baseline of the characters, and subsequent dimensions
contain the characters themselves.
All strings must have a four−character name, but cannot include spaces or
special characters. ABCD, 1234, and XA45 are valid examples, though MX uses
a convention for names to indicate the type of the string. Some string types
such as cross section strings only require a single character − MX automatically
allocates the remainder. These conventions are stored in feature sets, which are
described in more detail later.
Points
Within a string, a point is held as a set of dimensions that are associated with
each other. Each point has a set of coordinates and may also have other
information, for example, to define geometry. For example:
On a contour, a point is just two dimensions X and Y. The Z value is
stored only once because it is common to all the points in the string.
Along a ridge or a curb line, three dimensions X, Y and Z are used.
On a road center line, there are six dimensions; X, Y and Z, station,
bearing, and radius of curvature (ch, b, rad).
A point can have any number of dimensions between 2 and 15, depending on
the information needed to record in addition to its position. The following
illustration shows the dimensions of points on contour, ridge and road center
line strings.

MX Basics
(x, y, z, ch, b, rad)

(x, y, z)
(x, y, z)
(x, y, z)
(x, y)
(x, y)
(x, y)
Figure 2 − String points
Point numbers
Strings consist of sequences of points and, to address and retrieve individual
points, MX assigns each point a number relative to the start of the string. The
number always remains relative to the start of the string, so if a string has 24
points and point 12 is deleted, the old point 13 becomes point 12, and so on to
the last point.
Discontinuities
There are two types of discontinuity used in MX; a discontinuity between
points on a string, so creating a gap, and a discontinuity of bearing, which
indicates an instantaneous change of direction at a point.
Gaps
It may be that one or more gaps or discontinuities in a string are required, for
instance, to create a break or gate in a fence. In this case, MX creates a string as
a series of part sections of the same string, with a common name.
This technique avoids a profusion or duplication of strings and difficulties in
names.
before CASI
after CASI
CASI
gap
Figure 3 − Gaps in strings

1
MX Basics
Bearing discontinuities
These are used to mark a change in direction within a string, such as in estate
roads where curbs often turn through 90 degrees.
Null elevations
In horizontal alignment design, master alignment strings are created without
elevations, and the elevations are added later in vertical alignment design.
Because, the horizontal alignment is defined as a 6D master alignment string,
MX assigns a null elevation of −999.0 to every point on the string. In this way
MX is able to register the presence of a elevation while ignoring its value.
Null elevations are also useful when recording feature strings for objects such
as hedges and fences, where elevations are often not required. Again, MX
automatically assigns null elevations to create a 3D string. Null levels are
ignored when creating a triangulation of a surface.
Feature sets
Feature sets are a means of grouping strings and identifying them with a
description. They are used throughout MX to make it easier for you to select
strings for subsequent operations. The strings belonging to a feature set are
specified using a partial string name.
As an example, a design feature set might include the following:
Feature Partial Name String Type
Road Center Line MC?? Master
Carriageway (Edge) CE?? Feature
Carriageway (Top of Curb) CT?? Feature
Shoulders (Edge) ES?? Feature
Shoulders (Unpaved shoulder) EV?? Feature
When a model is created, you can associate a feature set with the model using
Tools ⇒ Model Defaults. This sets up a string naming convention for the model.
Different models can have different feature sets.
Default feature sets are provided with the software.

Style sets
A style set is a collection of styles which is used to draw a complete model or a
selected part of it. Different style sets are used to draw different types of
model. Many style sets are provided with MX and you may add your own style
sets if you wish.

MX Basics
For example, there is a style set to draw a complete contour model with all
contours drawn as solid lines and curve fitted. Prominent contours are also
drawn for every 5 normal contours with the contour height embedded in the
contour line.
Another style set draws a plan view of a road design model with different line
styles for each feature type, the alignment with station annotation and the
vertical intersection points with their associated elevations and grades.
Style sets rely heavily on the string naming convention used for a model. For
this reason, they are closely associated with feature sets and by convention are
given the same name as the feature set with which they are associated.
Model defaults
You can specify which feature set and which style set to associate with a model
when you create it. You can also specify these defaults for an existing model
using Tools ⇒ Model Defaults. Once these defaults have been set up, they are
automatically used for every relevant option, such as when you display or create
a string. Another way to assign model defaults is to click the right hand mouse
button in any model name field on a panel, or on the model name field of the
MX Toolbox.
You can also make these assignments automatically if you use a standard model
naming convention.
Standard string naming convention

A standard string naming convention has been introduced to allow you to take
full advantage of the power and flexibility of feature sets and style sets. It may
be switched on or off on a per project basis from the message box which
appears when you start a new project, or from the System Parameters tab on the
Project Settings panel. It uses the feature and style sets MXROAD.fns and
MXROAD.pss for the design model.
If you have purchased MXROAD, an application developed for highway design,

you must use the standard string naming convention.

1
MX Basics
MX Environment − Overview
MX can run in any of three environments; Windows, AutoCAD and
MicroStation.
Windows
AutoCAD MicroStation
Figure 4 − MX Environments
When running under Windows, MX uses its own built−in frame and user
interface, presented in the usual way as a series of menus and panels. When
running in either of the other two CAD environments, similar options and
panels are available from an MX menu which is added to the AutoCAD or
MicroStation menu bar. In this way, when you are running in a CAD
environment, you have access to both the MX options and the standard CAD
options at the same time.
Data interoperability and drawings
Whichever environment you are using, MX creates working displays (DPWs) or
drawing page files (DPFs) to store the MX graphical elements you create from
the model file data.
However, MicroStation uses DGN files and AutoCAD uses DWG files. MX
addresses this difference by presenting you with a DGN or DWG file, but in
the background it is constantly updating a working display or drawing page file.
The name of the working display or drawing page file corresponds to your
current CAD drawing file. In this way, although you are using MX in one
environment, for example, MicroStation, the MX drawings created may be
opened and edited in any MX environment, for example, AutoCAD. Whichever
environment you are using, changes to the drawing are also passed on to the
model file where appropriate.

MX Basics
In MX, there is a fundamental difference between a DPW and a DPF. A DPW

is an elastic area that grows to accommodate changes to the graphics it holds,
and so lets you create, assess, and edit model data to design the project. Once
the design is complete, paged drawings are needed, and it is at this point that a
DPF is created. This file also displays the MX graphics, but does not let you
edit the model data; the only operation available is the addition of lines and text
(enhancements).

1
MX Basics
MX Data
Model file DPW or DPF
MX Environment
Windows
User Interface
AutoCAD or MicroStation
DWG or DGN
CAD−only layers/levels MX layers/levels
User Interface
Figure 5 − MX data interoperability

MX Basics
Common Components
Common Components
Many components of the MX interface are common to all environments, and
these are described in the following paragraphs.
The MX user interface is Windows compliant. This means that many of the
operations you have learned in other Windows software, such as Open, Save
and Browse are just as valid in MX. Help is obtained for an item on a panel by
clicking the question mark icon on the panel header and dragging it onto the
item in question. What’s This Help is then automatically displayed. You can also
press the F1 key.
The following sections do not provide all the answers about how to work with
MX, they do however provide enough information to begin with. Much
MX−specific information is provided as Help and there are many books written
about working in the Windows environment, although there is no substitute for
trying for yourself. Given that all data critical operations require confirmation
before they are carried out, and that Cancel provides an escape route,
experimentation will quickly make you proficient.
The mouse
The mouse is used to interact with the display, the data input panels, toolbars
and menus. Essentially, the left−hand mouse button selects the data under the
position of the cursor. For example if a string name is to be entered in a panel
field, move the cursor over the string on the display and click the left−hand
button.
You can also click and hold the left−hand button to expand menus, display lists,
increment values using spinners and so on. Simple clicking selects items from a
list.
The right hand mouse button presents available options. For example, if you
click in an XY field on a panel to provide focus, and then click the right hand
button the Point Selection Method (PSM) options appropriate to that field are
listed. Click the PSM you require to reposition the tick (√) marking the current
method.
Three types of cursor are used in MX to help you recognize the type of input
the program is expecting. By default, these are as follows:
the Windows cursor − used in panels and for manipulating Windows.
the CAD cursor − used when specifying CAD commands in

AutoCAD or MicroStation.
the MX cursor − used when specifying MX options

1
MX Basics
Common Components
The keyboard
The keyboard is used for entering data into a field or working in the MX
Linemode panel. Shortcut keys are available, they are marked by _ and activated
by using ALT + the character key. For example, use ALT F to gain access to the
File menu.
Panels
There are many panels, each providing access to one or more MX options. You
will find that, in most cases, you can have more than one MX panel open at any
one time.
Some panels are arranged to appear in sequence, this sequence is known as a
Wizard. A Wizard is a simple means of guiding you through a complex process,
making sure that you provide all the information necessary to complete the
task.
The panel below is typical and shows the key elements, for which explanations
follow;
Figure 6 − Typical panel layout
1. The panel header bar and the title Design a String: Intersection of Two Slopes
defines the function of the panel.

MX Basics
Common Components
2. To find out more about any of the panel data requirements click the ?
button, place it on the text about which you need to know more, and click
again. What’s This help will be displayed. What’s This help tells you how to
complete the data field, and provides other essential information.
3. Clicking this button will dismiss the panel without completing the function.
4. Rather than using 3, use one of these three buttons; OK completes the
function with the data you have supplied and then dismisses the panel,
Apply completes the function with the data you have supplied and keeps
the panel displayed, Cancel dismisses the panel.
5. These tabs allow you to get at all the data fields for the option. The left or
top tab contains all the mandatory fields, subsequent tabs and their fields
are optional.
6. Radio buttons permit you to select one of a number of choices, the one
with the black center is the one currently selected. On this particular panel
changing the option will gray out some of the other data fields as they are
not relevant for the selected option.
7. Clicking the list button will give you a list of models, strings or options
from which to choose. As you run the cursor down the list, the highlight
moves, and clicking transfers your selection to the data field.
8. Click and hold the up or down spinner to increment the value in the data
field.
9. Click either the up or down arrow button to define the direction of the
slope.
10. Click in the check box to apply normal offset. This will change the text
beside the data field beneath, as the value to be entered into the field
changes.
11. The panel id. If ever you have a problem, and need more information than
the help gives, quoting the panel id to your MX support engineer will help
locate where you are and what you are trying to do.
MX menu bar
The standard MX menu or menu bar choices are File, View, Tools, Design,
Analysis, Modify, Display, Draw, Visualize, Report, Add−Ins and Help. You will
quickly learn which options are available from each of the pull down menus, but
a click on each will display the menu content.
In the CAD environments, MX appears as a separate entry on the AutoCAD or
MicroStation menu bar. Once a project is opened, the MX menu changes to
reveal all the MX options which are available to you. If you wish, you can
display the MX options as an alternative menu bar to the CAD menu bar by
selecting MX ⇒ MX Menu.
You may find some options are grayed out in the menus. This may be because
they are not installed, you are not licensed to use them or they are not suitable
for use at that particular moment.

1
MX Basics
Common Components
Toolbars
There are a number of MX toolbars which provide shortcuts to the MX
options. You can display the toolbars so that they are docked to the frame, you
can move toolbars to different screen locations, or turn them off using the MX
option View ⇒ Toolbars.
To dock or undock a toolbar, double−click the toolbar header.

The Plan with Tools toolbar is shown below. If an icon needs explanation, rest the
cursor on it to display its tool tip.
Figure 7 − Plan with Tools toolbar
Message boxes
If you make a mistake or MX wants to communicate with you, a message box
will be displayed. You will have to acknowledge the message by clicking the OK
button.
Generally, if you have made a mistake, such as missing a mandatory data field,
the message will tell you what’s wrong and how to correct the error. You will
have to click OK to dismiss the message before you can re−apply focus to the
panel field requiring correction.
The MX output window
The MX output window shows the commands sent to the MX engine to carry
out your instructions throughout your MX session. It is not necessary to
understand these commands, but they can be decoded using the Linemode
Reference Help. The window also displays errors and warnings, and these
together with the messages and prompts may assist you in changing the option
data to achieve the results you require.
In AutoCAD, when focus is in the AutoCAD application you can display the
output window by pressing SHIFT−F2. AutoCAD output and command
prompts are displayed in the AutoCAD text window, which you can access by
pressing the F2 key. You can also direct MX output to the AutoCAD text
window from the View ⇒ Configuration panel.
Moving MX data to other Windows applications
Using standard Windows cut and paste techniques, or simply by opening MX
data files in editor applications you can transfer MX data to any other Windows
compliant application. Once there, the data can be re−formatted, tabulated into
columns or totally reorganized using standard word processing options. This
means that you can transfer MX data to tender or contract documents, and
present it in any way you choose.

MX Basics
Windows Environment
Windows Environment
MX in Windows runs within a frame, but has other windows within the frame.
When you start a new project, two windows are displayed within the MX frame,
the display window and the output window. The output window is docked
within the frame, and can be detached and moved to any location.
Figure 8 − The MX frame
You can only have one drawing open at any time, but within the MX frame you
can create additional viewports, showing different views of the drawing.

1
MX Basics
AutoCAD Environment
AutoCAD Environment
MX runs within AutoCAD, so that when you start the program, the only
obvious changes from standard AutoCAD are that there is an extra MX menu
and two extra toolbars, the MX Controls toolbar at the foot of the graphics
window and the MX toolbar. The MX toolbar controls which model an object is
added to when it is drawn, and which type of feature is created. As with
standard AutoCAD, the display reflects the contents of the DWG file, but with
MX in AutoCAD, some or all of the layers in the DWG file contain data which
is linked to the MX model file via an MX drawing file. In this way, you can
create a DWG file containing both MX layers and layers which contain only
AutoCAD data.
Figure 9 − The AutoCAD frame

MX Basics
AutoCAD Environment
MX strings in AutoCAD
You can use either MX options or AutoCAD commands to create and draw
MX model information such as strings in an AutoCAD DWG file. A string is a
sequence of points which represents a physical feature, such as a fence or a
hedge, or it can represent a non−physical feature such as a contour. MX strings
which are related to each other are stored in models, for example, all strings
which represent a survey are stored in a survey model, and all strings which
represent a proposed design are stored in a design model. The set of features
used by a model is stored in a feature set and associated with the model.
MX model data is displayed on layers created with the same names as the
features or a group of features in the model’s associated feature set. These
layers are called MX layers, in that anything you draw on them can be linked to
the MX model file. You must associate a feature set with the model before
using the MX options to ensure that the strings are correctly displayed in their
relevant layers.
Using AutoCAD commands, when you create a polyline on an active MX layer,

MX in AutoCAD creates and displays an MX string custom object and a
corresponding string is also written to the MX model file. The string is
automatically given the next name in the feature set corresponding to the name
of the layer.
A custom object is an object such as an MX string which is not a native

AutoCAD object, but is created by another program (in this case, MX in
AutoCAD). When you modify or delete an MX string, both the MX string
custom object in the drawing and the string itself (in the MX model file) are
updated. Custom objects can also be exploded back to equivalent AutoCAD
objects and the corresponding data removed (optionally) from the model file.
You can use layers which are not MX layers for information which is not
required by MX, so you can work in AutoCAD (possibly constructing objects
or adding annotation) on a layer such as layer 0 and the data is not sent to the
MX model file.
The MX Toolbar
The MX toolbar gives you control of the creation of MX strings when using
AutoCAD commands. It has no effect when you use MX options.
For example, in MX in AutoCAD you can use most of the AutoCAD Draw and
Modify commands such as PLINE and MOVE to create and edit MX strings.
With no objects selected, the MX toolbar lets you know what will happen if you
create a new AutoCAD object. It tells you if you can successfully create MX
strings, in which MX model any new strings will be created, and the feature that
will be created.

1
MX Basics
AutoCAD Environment
Convert Object
Traffic Lights Hide Current Model
Current Model Current Feature
Create New Feature
Display Current Model with Style Set
Set Active Document
Figure 10 − The MX toolbar
If you select an object, the toolbar provides information about the object you
select. If the object is an MX string, then the model and feature of the string are
displayed in the toolbar.
The toolbar is described in more detail in the following paragraphs.
Traffic Lights
The traffic lights indicate whether you can create MX strings using AutoCAD
commands.
If a green light is displayed, then when you create an AutoCAD object on
an MX layer it will be automatically converted to an MX string in the
currently displayed model.
If an amber light is displayed, then when you create an AutoCAD object
you can manually convert it to an MX string by clicking the Convert Object
button and then selecting the objects to be converted.
To switch between automatic and manual conversion, you click the
auto−convert box at the foot of the frame.
So, if you were to use an AutoCAD command on the layer Roadway_Edge and
the current model’s feature set contained the feature description Roadway (Edge)
then you would see a green (or amber) light and the resultant MX string would
have a string name of CE??.
Show/Hide Current Model
The Show/Hide Current Model icons provide a quick way to hide or redisplay all
the drawn information from the model in the current model field. For example,
you can hide the ground model so that only the design model is displayed.
Current MX Model
The current MX model is the model in which MX strings will be created. This
field is grayed out if you select an object which is not in the current model.
Current Feature
The current feature is the feature type which is given to any MX string you
create using AutoCAD options. The field lists all the features in the feature set
associated with the current model.

MX Basics
AutoCAD Environment
If you create an AutoCAD object, it will be created on the layer associated with
this feature.
To create a layer corresponding to a feature, just select the feature from the list.
If you select an object, the current feature list changes to reflect the feature of
the object you have selected.
You can change the feature type of an object by simply selecting the object and
then selecting a feature from the list.
Convert Object Button
If an amber traffic light is displayed, select the object to be converted to an MX
string, then click this button . The object will be converted to the feature
corresponding to the layer that the object is on.
Auto−Convert Mode
Auto−convert allows you to toggle between the automatic and manual modes of
creating MX strings from AutoCAD objects. The auto−convert toggle box is
located at the bottom of the MX frame.
With auto−convert on, if the current layer is an active MX layer, when you create
an AutoCAD object it is automatically converted to an MX string. The traffic
light is green in this case.
With auto−convert off, if the current layer is an active MX layer, when you
create an AutoCAD object it is not converted to an MX string. The traffic light
is amber in this case. To convert it manually, use the Convert Object icon.
A red traffic light indicates a plain AutoCAD layer or an inactive MX layer, ie, a
layer whose corresponding features do not exist in the current model.
The auto−convert setting has no effect if you modify an MX string; the MX

model will be automatically updated.
The auto−convert setting has no effect if you change the layer property of an
object to an active MX layer; the object is automatically converted to an MX
string.
Create New Feature
The Create New Feature button allows you to add features to your feature set
and to create additional AutoCAD layers from the feature set descriptions. If
you use an MX option to display an MX model (for example, Display ⇒ Plan
with Style Set), then you will find that the MX layers are automatically created for
you. You only need to use Create New Feature if you want to create a new MX
layer and feature for use with AutoCAD commands.
You can create a new layer from a feature in the current feature set just by
selecting the feature from the MX toolbar.
Any feature you create must have an entry in the corresponding style set so that
MX knows how to draw it. Use the Style Set Editor to modify the appropriate
style set.

1
MX Basics
AutoCAD Environment
Set Active Document
The Set Active Document button defines which drawing is the current MX
drawing. In AutoCAD, you may have more than one drawing open at any one
time, but MX operates on one drawing only.
MX and AutoCAD commands
You may use either MX options or AutoCAD commands to create and edit MX
strings. For details of the operation of individual AutoCAD commands, refer to
the on−line Help.
When you select an MX option from the pulldown menus, it is processed and
the AutoCAD command prompt is replaced by an MX prompt. At this stage,
some AutoCAD menus, such as Layer and Linestyle, will be grayed out, because
MX in AutoCAD is expecting an MX screen selection. If you then want to use
an AutoCAD command, click in the command window or the graphics area,
and press the Esc key.
To review any information on the command line, press the F2 key to display the
full AutoCAD text window. Use SHIFT F2 to display the MX output window,
which contains details of the MX options which are processed.
In general, only 2D and 3D MX strings can be edited using AutoCAD

commands, although 6D master strings can be moved, copied or rotated. This
is because MX uses different types of strings for sections, master alignments,
geometry, cadastre, earthworks and drainage, with information stored in extra
dimensions of the string that standard AutoCAD commands cannot maintain.
AutoCAD grips are therefore not available for these string types.
MX in AutoCAD configuration
The MX in AutoCAD Configuration panel is used to configure the way in
which MX interacts with AutoCAD. It is available from both the MX View
Configuration option and from the MX tab of AutoCAD Tools ⇒ Options panel.
There are four tabs on the panel:
File handling
General
Data conversion
Warnings
There is one additional tab on the Configuration panel; MX Custom.
A summary of the available preferences is given below, but for full details, refer
to the on−line help.
File handling
The file handling settings allow you to define the AutoCAD drawing templates
for creating new DWG files. You can also specify where macros created by MX
in AutoCAD are stored, and whether or not to leave an MX drawing open if
you change the active MX drawing.

MX Basics
AutoCAD Environment
General
These settings determine whether objects are displayed according to the MX

style set or the current AutoCAD line style and color settings. There are several
other settings which relate to how MX data is treated following certain
AutoCAD operations.
Data conversion
The data conversion settings allow you to define how block attributes are
converted, the curve step tolerance, the model and paper space scale factors,
and the default auto−convert setting.
Warnings
You can choose to display warnings when strings are modified which indicate
the effects of certain operations. It is recommended that you leave MX in
AutoCAD warnings enabled until you are familiar with MX in AutoCAD.
MX Custom
These settings allow you to view line widths and enable AutoCAD geometry
snaps to MX string points. You can also set geometry snap tolerances to control
how the geometry of an object is reconstructed from an MX string, and define
how null levels are interpreted by AutoCAD.

1
MX Basics
MicroStation Environment
The MicroStation environment
MX runs within MicroStation, so that when you start the program, the only
obvious changes from standard MicroStation are that there is an extra MX
menu, an extra panel called the MX Toolbox and an MX output window. The
MX Toolbox controls which model an element is added to when it is drawn. As
with standard MicroStation, the display reflects the contents of the DGN file,
but with MX in MicroStation, some or all of the levels in the DGN file contain
data which is linked to the MX model file via an MX drawing file. In this way,
you can create a DGN file containing both MX levels and levels which contain
only MicroStation data.
MX output, such as that from commands and reports, is displayed in the MX
output window.
Figure 11 − The MicroStation frame

MX Basics
MX strings in MicroStation
You can use either MX options or MicroStation tools to create and draw MX
model information such as strings in a MicroStation DGN file. A string is a
sequence of points which represents a physical feature, such as a fence or a
hedge, or it can represent a non−physical feature such as a contour. MX strings
which are related to each other are stored in models, for example, all strings
which represent a survey are stored in a survey model, and all strings which
represent a proposed design are stored in a design model. The set of features
used by a model is stored in a feature set and associated with the model.
MX model data is displayed on levels created with the same names as the
features or a group of features in the model’s associated feature set. These
levels are known as MX levels, because anything you draw on them can be
linked to the MX model file. You must associate a feature set with the model
before using the MX options to ensure that the strings are correctly displayed
on their relevant levels.
Using MicroStation tools, when you create a SmartLine on an active MX level,
MX in MicroStation also creates a corresponding string in the MX model file.
The string is automatically given the next name in the feature set corresponding
to the name of the level.
You can use levels which are not MX levels for information which is not
required by MX, so you can work in MicroStation (possibly constructing
elements or adding annotation) and the data is not sent to the MX model file.

1
MX Basics
The MX Toolbox
The MX Toolbox gives you control of the creation of MX strings when using
MicroStation tools. It has no effect when you use MX options.
For example, in MX in MicroStation you can use many of the MicroStation
tools to create and edit MX strings.
With no elements selected, the MX Toolbox lets you know what will happen if
you create a new MicroStation element. It tells you if you can successfully
create MX strings, the MX model in which any new strings will be created, and
their feature type. It also gives you control over whether the elements you draw
are converted to strings automatically or whether the elements are to be
converted later.
View/change System Parameters
Locked/Unlocked Autoconvert ON/OFF

Single/Multi Pick List of MX Keyins
MX/MicroStation focus
Convert Element
Traffic Lights Hide Current Model
Current Model Current Feature
Create New Feature
Display Current Model with Style Set
Figure 12 − MX Toolbox and MX Controls
If you select an element, the toolbox provides information about the element
you select. If the element is an MX string, then the model containing the string
is displayed in the toolbox.
The toolbox is described in more detail in the following paragraphs.
Traffic Lights
The traffic lights provide a visual indication of whether you can create MX
strings using MicroStation tools.
If a green light is displayed, then when you create a MicroStation element
on an MX level it will be automatically converted to an MX string in the
currently displayed model.
If an amber light is displayed, then when you create a MicroStation element
you can manually convert it to an MX string by clicking the Convert Element
button and then selecting the elements to be converted.

MX Basics
To switch between automatic and manual conversion, you click the

auto−convert box on the MX Controls toolbar..
So, if you were to use a MicroStation tool on a level named Roadway_Edge and
the current model’s feature set contained the feature description Roadway (Edge)
then you would see a green (or amber) light and the resultant MX string would
have a string name beginning with CE?? if this were the partial string name
corresponding to the feature.
Show/Hide Current Model
The Show/Hide Current Model icons provide a quick way to hide or redisplay all
the drawn information from the model in the current model field. For example,
you can hide the ground model so that only the design model is displayed.
Current MX Model
The current MX model is the model in which MX strings will be created.

If you select an element, the current model is updated to reflect the model
containing the element you have selected.
Current Feature
The current feature is the feature type which is given to any MX string you
create using MicroStation tools. The field lists all the features in the feature set
associated with the current model.
If you create a MicroStation element, it will be created on the level associated
with this feature.
If you select an element, the current feature is updated to reflect the feature of
the element you have selected.
Convert Element
If an amber traffic light is displayed, select the element to be converted to an

MX string, then click this button . The element will be converted to the
MX feature corresponding to the level that the element is on.
Create Feature Set
The Create Feature Set button creates a feature set from all the named
MicroStation levels. This feature is useful if all you have is a MicroStation
drawing and you wish to create a feature set to match. In this way, you can
create a feature set having feature names derived from MicroStation level
names.
Any feature you create must have an entry in the corresponding style set so that
MX knows how to draw it.

1
MX Basics
MX Control
Point Selection Methods
The Point Selection Method mode controls how points are selected from an
MX option on MX strings. As an alternative, you could use MicroStation
tentative points instead of MX Point Selection Methods.
Auto−Convert Mode
Auto−convert allows you to toggle between the automatic and manual modes of
creating MX strings from MicroStation elements.
With auto−convert on, if the current level is an active MX level, when you create
a MicroStation element it is automatically converted to an MX string. The
traffic light is green in this case.
With auto−convert off, if the current level is an active MX level, when you
create a MicroStation element it is not converted to an MX string. The traffic
light is amber in this case. To convert it manually, use the Convert Element option.
A red traffic light indicates a standard MicroStation level (ie, a level having no
interaction with MX) or an inactive MX level, ie, a level whose corresponding
feature is not assigned to the current model.
The auto−convert setting has no effect if you modify an MX string; the MX

model will be automatically updated.
MX and MicroStation tools

You may use either MX options or MicroStation tools to create and edit MX
strings. For details of the operation of individual MicroStation tools, refer to the
MicroStation on−line help.
Only 2D and 3D MX strings can be edited using MicroStation tools. MX uses

different types of strings for sections, master alignments, geometry, cadastre,
earthworks and drainage, with information stored in extra dimensions of the
string that standard MicroStation tools cannot maintain.
MX and MicroStation drawings

MX creates working displays or drawing page files with a suffix of either DPW
or DPF respectively. These files hold the MX graphics, and can also be plotted.
However, MicroStation uses DGN files. MX in MicroStation addresses this
difference by presenting you with a DGN file, but in the background it is
constantly updating a working display or drawing page file. The name of the
working display or drawing page file corresponds to your current MicroStation
DGN file. In this way, although you are using MX in MicroStation, the MX
drawings created may be opened and edited in any MX environment, for
example, using MX in AutoCAD.

MX Basics
In MX, there is a fundamental difference between a working display and a

drawing page. A working display, like a DGN, is an elastic area that grows to
accommodate changes to the graphics it holds. A working display lets you
create, assess, and edit model data to design the project. Once the design is
complete, paged drawings are needed, and it is at this point that a DPF is
created. This file also displays the MX graphics, but does not let you edit the
model data; the only operation available is the addition of lines and text
(enhancements). The DPF is therefore similar to a MicroStation sheet file.
Configuration
The Configuration panels are used to configure the way in which MX interacts
with MicroStation. A summary of the available preferences is given below, but
for full details, refer to the on−line help.
MX to MicroStation
Mappings − define how fonts, line styles, macro line styles, line widths and
macro symbols are mapped.
Options − you can choose to ignore line widths, and change the seed file
used to create a DGN from MX data. You can also define whether MX
standard point symbols are reproduced as points, and whether elements
defining the geometry of a string are created as individual vectors and arcs
or as complex chains.
MicroStation to MX
Mappings − defines whether cells are mapped to macro symbols or model

data.
Options − define whether level overrides are considered, the curve step
tolerance, the default MX drawing scale and whether construction lines are
stored in the MX model file. You can also define whether information is
deleted from the model file when it is erased from the drawing.
Convert elements − defines which settings are used when drawing elements
(MX or MicroStation).
General
Mappings − defines how colors and line styles are mapped and how features
are mapped to levels.
Options − defines how MX null elevations are interpreted in MicroStation,
the default marker size and a check box for scaling to world coordinates, ie,
1:1..

1
MX Basics
The Applications Toolbar

The Applications toolbar is a special toolbar which provides access to any
applications you have purchased, such as MXRAIL or MXRENEW.
Figure 13 − The Applications toolbar
MXROAD is an application developed for highway design. It provides all you

need for preliminary design, roadway widening, superelevation, intersection,
pavement layer and subgrade design. You can also customize reports using the
report generator and modify designs using the cross section editor. MXROAD
requires the standard string naming convention to be in operation, and that all
strings (such as alignments) created outside of MXROAD conform to the
convention.
MXRENEW is an application for the realignment, resurfacing and rehabilitation
of existing roads. Parametric fitting is used to automatically generate a new
profile with specified minimum overlay depth, cross slope tolerances and design
speed.
MXURBAN is an application for the design of road improvements in urban
areas. It caters for all kinds of urban rehabilitation works, from overlays within
the existing curb lines to full reconstruction of both the road and sidewalks.
MXDRAINAGE is an integrated environment for the design of drainage
networks for any MX project − road, railway or airport design; urban
redevelopment schemes and road upgrades; industrial and residential estate
design; landscape design and rehabilitation works. It can be applied at any stage
of the design process, from preliminary analysis through to detailed design.
MXRAIL is used for the design of railway alignments, light railway alignments,
and intersection layouts. It enables you to design three−dimensional alignments
representing plain line track, simple turnouts, grade crossings, crossovers and
complex multi−lead layouts. Used in conjunction with MXSITE, the MXRAIL
package allows you to integrate the design of railroad associated developments,
such as depots or freight terminals. Used in conjunction with MXROAD,
railroads can be interfaced with highway schemes or street−running light
railroads.
MXSITE is an application for the design of housing and industrial estate
layouts. It enables you to design three dimensional surfaces representing roads,
intersections, cul−de−sacs, building slabs, car parks and earthworks. You can also
design storm and foul drainage networks. Sections, volumes, quantities and
drawings can all be produced making MXSITE a comprehensive design system.

MX Basics
MXDRAW is used to produce final drawings from working drawings in a rapid

and efficient manner. You can create layouts for plans, profiles, composite plans
and profiles, and cross sections. In addition, because the final drawings are
created using views of a working drawing, any changes you make to the design
are automatically reflected in the final drawings so that they are always
up−to−date and ready to plot. MXDRAW also provides a suite of geometric
annotation tools. You can annotate geometric elements such as arcs, spirals,
straights, grades and vertical curves by transferring information from a tool tip
directly to the drawing in a pre−defined style. Any annotation you add to the
drawing is dynamically updated if the design changes.
A link is provided to the Bentley Home Page on the Web.
Arenium is a technology which enables MX to be used for collaborative
engineering projects over a local or wide area network or the Internet. It
provides all the file management and communication facilities required for
multiple users to create and complete an MX project no matter where they are
located in the world. It also acts as a project control system as it records all
events and actions carried out on data.
For further information on Arenium, refer to the Arenium User Guide.

1
MX Basics
Starting MX
Starting MX
There are several ways of invoking MX. These are:
Click Start ⇒ Programs ⇒ Bentley MX ⇒ MXROAD. Once the program
starts up, an MX menu is loaded in the main menu bar and the MX startup
panel is displayed.
Open the MX Program Group and double−click on the MXROAD icon.
Alternatively, create a shortcut to this program and place it in a convenient
location, such as on your desktop.
Once you have created and saved a project, you can double−click on the
project icon (.mmd) and the project will be opened automatically from
within MX (provided that this was the association you chose at installation
time). Alternatively, create a shortcut to this project and place it in a
convenient location, such as on your desktop.

MX Basics
Starting a Project
Starting a Project
Creating a new project
When you start MX, a startup panel is displayed. The startup panel gives you
quick access to the options on the initial File menu (Windows) or MX menu
(AutoCAD and MicroStation), as well as providing additional facilities for
accessing Help and your project settings.
Figure 14 − The MX menu on the MicroStation menu bar
Figure 15 − Typical startup panel

1
MX Basics
Starting a Project
From either the startup panel or the File/MX menu, you can create a new
project, open an existing project, archive projects using the zip/unzip facility or
access the on−line Help. In addition, the most recently opened projects are
listed at the bottom of the menu.
MX uses projects to group information which relates to a particular design
scheme, such as the survey and design models, the drawings and the design
parameters used for the project.
To create a new project, click the New Project button on the Startup panel or
select New Project from the MX menu bar, then specify the name of your
project, its location and the location of the design parameters to be used for this
project. If the folder you specify does not already exist, it is created for you.
You are also given the opportunity to edit the default project settings as you
create the project. It is a good idea to look at these even if you do not think you
will want to change them, to familiarize yourself with the settings that are
available.
An empty model file is created in your project folder when you start a new
project. However, if MX finds that there is already a model file in the folder,
you can choose to keep it rather than overwrite it with an empty one. This gives
you the opportunity to move an existing model file in to place so you can
continue with a design.
if you are working on a project on the network, perhaps because several people
need access to the project, you can use the network project facility to copy the
project temporarily to your local disk, work on the project, then copy it back
again when you have finished.
You should only have one project in a folder.
You should not create project folders within the MX program structure, ie,
C:\Program Files\mfw.

MX Basics
Typical Project Sequence
Typical Project Sequence

The MX project sequence is a broad sequence of activities that must be
followed to design any project with MX. The sequence is as follows:
NTF Draw GENIO
Alignment Report
DXF MIFILE
Plan with Style Set Design Perspective
SURVEY Modify Visualization VOLUMES
Plan with Tools Sections

Print
GENIO DXF
Analysis
Plot
IMAGE SETOUT
Import Display Design Output Export
Figure 16 − Typical project sequence
import existing survey data

create a working display
design, analyze and, if necessary, modify the new work
output new work in all required forms.
Creating a survey model from imported data

The survey model describes the existing ground and any other features which
are present in the area of your proposed design. It is essential that the data
describing this model is both complete and accurate, as any errors could have a
serious impact on the proposed design. It is also important that the string
names in the import file conform to a string naming convention used in a
feature set and style set combination. You can either change the names of the
strings in your import file to suit an existing feature set and style set, or you can
create new ones (see Assigning model defaults).

1
MX Basics
Creating a survey model from imported data
The data describing the survey model can be input to MX in any of the
following formats:
MX Input
MX GENIO
MX Survey
General ASCII
MicroStation DGN
AutoCAD DXF / DWG
Ordnance Survey NTF (UK only)
Softdesk Alignment and DTM
Autodesk LDDT
Eagle Point Triangulation
LandXML
Figure 17 − File menu
If you are running MX in AutoCAD or MicroStation, to import data from an

AutoCAD DWG, a MicroStation DGN or a DXF file, first open the drawing in
AutoCAD or MicroStation. Once you have set the layer or level names to match
a feature set for a model (see Assigning model defaults below), open your MX
project, select the elements and use the Convert Object/Element button on the
AutoCAD MX toolbar or the MicroStation MX Toolbox to store the data in the
MX model file.

MX Basics
Assigning model defaults
To import data in ASCII file format, select File ⇒ Input for any of the MX
formats (eg, GENIO) or File ⇒ Import for the external formats. If the imported
file contains drawing information, the survey model will be created and drawn
on the screen; otherwise you will need to create a plan working display. See
Creating a working display for details.
If you already have a model file and wish to use the models in MX, you should
exit MX, copy the model file into your project folder and then restart MX.
To create a new, empty model, use Modify ⇒ Edit Models ⇒ Create Model.
Assigning model defaults

Now that you have created the survey model, you can set up model defaults by
associating a feature set and a style set with it using Tools ⇒ Model Defaults. If
you do not have a feature set or a style set which match the string naming
convention you have used, you must create them to take full advantage of the
automatic features in MX.
Figure 18 − Tools menu
To create a new style set, use Tools ⇒ Style Set Editor to open a similar style set.
When you have finished, save the style set with a different name. A
corresponding feature set is automatically created.
Feature sets have the file extension ’.fns’.
Plan style sets have the file extension ’.pss’.
Creating a working display

A working display is a plan drawing which is not divided into pages, but is used
to display model information while a project is in progress. From a working
display, you can create plan drawings with the scale and page layout you require
at any stage in a project using the Draw options.
There are several options which are used in association with a working display.
These are accessed from the Display menu:
Figure 19 − Display Menu

1
MX Basics
Creating a working display
Plan with Style Set is a quick and simple method of displaying information from
one or more models in a predefined style. You specify the features to be drawn
(or all the features), and a style set is used to interpret each feature and display it
on the screen with any associated annotation. Different style sets are required
for different types of model; for example, there is a default style set MfW Simple
Survey.pss which can be used for displaying survey models. Each style set is
associated with a feature set to ensure that all features in the feature set are
drawn appropriately.
Many standard style sets are provided with MX and you should experiment with
them to decide whether you can use them directly or whether you need to
modify them to suit your own requirements. Use Tools ⇒ Style Set Editor to
browse, create or modify style sets.
Plan with Tools provides a series of individual display options which may be used
to display and annotate features. They may be used either instead of or in
combination with Plan with Style Set. The styles used by the Plan with Tools
options, such as line color, line style etc, are not stored in style sets, but are
accessed from the Styles Toolbar. The Styles Toolbar can also be used to
change the style and color of features which have already been drawn. You can
display the Styles Toolbar by selecting View Toolbars Styles Toolbar.
Erase Display erases the contents of the working display. No model information
is deleted.
Raster is used to add an image as a background to your model, such as an aerial
photograph or map data. You can either add the image directly or drape the
image over a triangulation giving a relief effect. You can then draw over the
image using the other Display options. A complete list of supported image
formats is provided in the on−line Help.

MX Basics
Viewing the working display
Viewing the working display

Once you have a working display on your screen, you can use the View menu
options and the native zoom facilities to examine the survey model in more
detail.
Figure 20 − View menu
Status is an interactive tool for providing information from the display, such as
the distance between two points, or information about a point.
You can temporarily or permanently remove information from the working
display using Show/Hide Graphics. For example, you can hide spot elevations
while you are working on the design. Although information may be hidden on
the display, it is still present in the model file.
Linemode provides access to the MX command language (not available in MX
Standard). This is a powerful tool for manipulating and drawing MX model data
using commands typed in from the keyboard or processed from an input file.
The Toolbars option is used to switch toolbars on and off. Toolbars provide
rapid access to many of the menu options. In particular, the Applications
toolbar is used to launch the additional applications MXROAD, MXRENEW,
MXSITE, MXRAIL and MXDRAW.
The Output Window is used to display reported information and the commands
which are sent to MX. Use this option to hide or display the window, or use the
Shift F2 key.
Preferences are used to configure various settings, such as the display of tool tips
and the startup panel.
Panel Position sets the default position of panels on your screen; for example, you
can set the panel position so that panels are always displayed at the top left of
the screen.

1
MX Basics
Producing a design
MX Toolbar (AutoCAD) or MX Toolbox (MicroStation) gives you control of the

creation of MX strings when using CAD commands. It has no effect when you
use MX options. For example, in MX in MicroStation you can use most of the
MicroStation placement, manipulation and modification tools to create and edit
MX strings.
Configuration is used to configure the way in which MX interacts with AutoCAD
or MicroStation.
You can also correct any discrepancies you find in the model using the Report
and Modify options.
Producing a design
With the survey model in place, you can now begin to create your design. The
design options are located on the Design menu:
Figure 21 − Design menu
Some of the options in this menu may be grayed−out dependent on which

applications such as MXROAD, MXRAIL or MXRENEW, you have purchased.
You may also find some of the Modify options useful in the course of your
design.

MX Basics
Producing a design
Alignment is used to create the master string on which the rest of your design is
based; typically, this would be a highway or railway center line or equivalent.
Firstly, in Alignment, you create your alignment horizontally using any of the
available methods; Element, Intersection Point (PI) or Spline. The Element
method allows you to construct an alignment from a series of elements, either
straights or circular arcs, connected by spiral curves as required. The PI method
produces the same end result but allows you to construct the alignment by
entering a series of intersection points. The lines joining these points are
tangential to the curves which connect the straight elements. Spirals can also be
included if required. Finally, the Spline method allows you to specify a series of
points through which a cubic spline curve is fitted.
In all three methods, design and display parameters govern the properties of the
curves and how they are displayed on the screen.
Once the horizontal design is in place, you can do the vertical design, ie, add
elevations to the alignment. Again, three methods are available to you, and to
assist you in specifying the elevations, a profile of the ground from the survey
model is displayed so you can see where to position the alignment.
When the alignment is completed, two strings are created in your design model;
the master string and its associated geometry string which describes the
geometry of the alignment.
In addition to smooth alignments, non−tangential alignments can be created for

the design of car parks, house pads etc.
Design a String options are used to derive additional strings from a master string;
typically, for a highway project, these would be strings such as roadway edge or
hard shoulder strings. The different options allow you to specify different
information to create the strings, for example, you can specify a horizontal and
a vertical offset from the master string, or a horizontal offset and a cross slope.
Feature sets are particularly useful here as you can select the type of feature you
want (eg, shoulder) and the next available string name is automatically assigned.
Amend a String options are similar to those described above, except that they
amend existing strings rather than create new ones.
The Earthworks Wizard is used to create earthworks strings, ie, strings which
define the intersection between your design and the ground. The earthwork
design relies on the specification of earthwork styles, together with any
alternative strategies to be used when certain criteria are met. These strategies
determine the shape of the earthworks slope in particular situations.
To make the procedure as simple as possible, the Wizard has access to a library
of earthwork styles such as simple slope and slope/bench combination styles,
which can be used immediately. Additionally, you can create your own custom
earthworks styles specific to the current design or your national design rules.
These custom earthwork styles can be saved in your own library for future use.
Once created, the earthworks strings may be drawn with tadpole annotation or
with slope signature strings.

1
MX Basics
Analyzing the design
MXDRAINAGE creates a drainage network from manhole positions you

specify by linking them with pipes. You can place manholes individually or
offset them from an existing string. Once the manholes have been linked, inlets
can also be added. Data from the drainage network can be exchanged between
MX and an external program which analyzes the data and calculates pipe sizes
and elevations according to the layout of the network and the hydraulic
constraints. Total and impervious sub−catchment areas can also be calculated
for each pipe in the network.
Drainage proximity checking searches for a clash between manholes and
selected strings. If the distance between the manhole and the string is less than
a specified value the clash position is displayed on screen with a warning, and an
alternative position is offered.

When you have a preliminary design, you may wish to analyze the design model
to check for any errors or to see if the design can be improved in any way. You
can do this with the Analysis options:
Figure 22 − Analysis menu
The Triangle options create various types of triangulation. A triangulation is a

mesh of triangles created from all the string points in a model. If you imagine
that the model strings are the frame of your model, then triangulation is the
process of applying a skin over the frame. The links in the strings form triangle
sides unless the points contain null elevations. Using a triangulation, the surface
can be analyzed anywhere and not just at the string locations.
Section is used to create cross sections from a string, and profiles along a string
or a straight line. Both types of section are useful for checking the quality of a
design, and cross sections can also be used to calculate volumes. The sections
created are displayed in a separate viewer which can be docked to the MX
frame. In the viewer, you can add many types of annotation and inspect the
design for any errors or weaknesses. At any time, you can create a working
drawing of the sections you are viewing.
Contour generates height contours from a triangulation. The contours are
categorized as either index contours or normal contours, where index contours
are used to indicate a significant height interval, for example, an index contour
can be generated for every five normal contours.
Generate ridge, valley and flow lines creates ridge and valley strings from which flow
lines can be generated to work out surface water run−off.
The Area options calculate the plan or surface area of a model. You can define
the part of the model whose area is required either by boundary strings or by
means of two strings limited in extent by normals to a reference string.

MX Basics
Volume is used to calculate volumes from either triangulated surfaces or

sections.
Surface Checker is used to check a surface created from surveyed data once it has
been input to MX. It can be used to check any surface in applications such as
landfill and quarrying to identify incorrect or incomplete data. This includes null
levels, zero levels, single point strings, high points, low points, coincident points
and intersection points. The results may be output graphically or as a report.
Surface Analysis is a Wizard which simplifies the analysis processes and displays
the results in graphical form. You can perform analyses to show elevations,
slopes or aspect bands, or show all slopes which are less than a specified grade.
You can also display flat spots and flow arrows. The Wizard also handles
sectioning and triangulation automatically.
Volumetric Analysis is a Wizard for calculating cut and fill areas and volumes,
either between two surfaces, or between a surface and a plane. It has many
potential uses in civil engineering, from the analysis of linear schemes such as
roads and railroads, through to quarrying and dredging works. Comparing two
surfaces could be used to analyze the difference between the existing ground
and a pad for a building, or the bottom of a layer of contaminated material.
Comparing a surface with a plane could be used to model navigation channels
(where the plane could be the mean low water level), or to model retaining
structures such as reservoir dams.
Cross Slope Checker displays a graphical analysis of the superelevation applied to a
roadway. The superelevation can be displayed using either drop/rise or
percentage diagrams. A superelevation report is then displayed in a separate
window, which you can save or print.
Visibility checks and dynamically displays the analysis of through visibility,
visibility at junctions and radial visibility. The analysis can then be output as a
report. You can then save or print the report.

1
MX Basics
Modifying the design

At any stage of the design, you can edit any of your data using the Modify
options:
Figure 23 − Modify menu
Edit Models allows you to create, rename or delete a model as well as providing
trimming, security options, and automated generation of composite models.
Trimming allows you to trim a model to a boundary, while the security options
allow you to provide read−only access to a model.
Edit Strings and Edit Points give you complete control over the strings in your
model. Although you normally design your main strings using the Design
options, you can also create strings with Modify, and you can also edit any part of
a string and the points within a string. You can also automatically generate
boundary strings around a model.
Copy, Move and the Copy Transformation Wizard may be used to copy an entire
model, copy or move information from one model to another, or copy or move
strings within a model. Model information can also be transformed by defining
shift, rotation, scaling, tilt or mirror parameters.
Explorer is a project management tool which allows you to manage the model
file and other information in your project. You use Explorer in the same way as
you would use Windows or Internet Explorer, except that it works on MX files
rather than all files on your disk.

MX Basics
Creating drawings
Creating drawings
So far, you have seen how to use Display to draw your model information on the
screen without dividing it up into pages. To create a series of drawing pages
from a working display, you use the Draw options.
Figure 24 − Draw menu
Draw divides the drawings that MX can create into distinct groups of working
and final drawings. Working drawings are those needed by the engineer during
the design phase of a project, and final drawings are those required for the
construction phase of a project.
The final drawings functionality is only available in the CAD environments and
uses CAD drawing techniques and drawing style sets to quickly and efficiently
create and annotate the final drawings to a pre−defined standard.
Working Drawings Create New Drawing creates a series of drawing pages from
the current working display. Firstly, you select an existing page setup or create a
page setup interactively to define the page size, margins, grids etc. There are
different page setups for plan, cross section and long section drawings.
Depending upon the page setup you select, you are presented with different
options.
For cross and long sections, the appropriate viewer is invoked (as from the
Analysis menu) and you display the sections and annotation you wish to draw,
either by starting from scratch or by using previously saved settings. You then
click the Create a Drawing icon to create a full working drawing of the
information you have viewed.
For plan drawings, you are led through the process of dynamically placing the
pages, either along a string or as adjacent pages in rows and columns. Once you
have created your layout, you can save it for future use, and then optionally
create the drawing pages. You have full control over the position of every page
in the layout.
Working Drawings Recreate Existing Drawing recreates a set of drawing pages
from a saved page layout.
Working Drawings Enhance Drawing is a drawing toolbox used for adding
annotation to a drawing. It may be used to draw lines, boxes, circles, arcs,
symbols, fill areas and text. The major difference between Display Plan with
Tools and Enhance Drawing is that Enhance Drawing adds information to the
drawing only, it does not add any information to the model.

1
MX Basics
Producing visualizations
The Final Drawings option uses components of MXDRAW to produce final

drawings from a working drawing in a rapid and efficient manner. You can
create layouts for plans, profiles, composite plans and profiles, and cross
sections. In addition, because the final drawings are created using views of a
working drawing, any changes you make to the design are automatically
reflected in the final drawings so that they are always up−to−date and ready to
plot.
Final Drawings also provides a suite of geometric annotation tools. You can
annotate geometric elements such as arcs, spirals, straights, grades and vertical
curves by transferring information from a tool tip directly to the drawing in a
pre−defined style. Any annotation you add to the drawing is dynamically
updated if the design changes.
You can specify the content of each view with a high degree of flexibility. MX
objects provide access to model information, while MX style sets and layering
techniques define the way in which the information is presented.
Producing visualizations
Visualization is useful for checking the accuracy of a model at any stage in a
design (provided elevations have been assigned to the strings in the model), and
also for presentation of a design when it is complete. The visualization options
are:
Figure 25 − Visualize menu
Simple Perspective creates a wire frame view from anywhere in a model. You
specify the eye and target points, and whether or not you wish hidden lines to
be removed. The resulting perspective view can be enhanced in the same way as
any other drawing.
For a greater degree of realism, you can use 3D View and Flythrough to produce
full colored textured renderings of your design. You can also create and save
animated 3D views as AVI files. Alternatively, you can use any of the AutoCAD
or MicroStation 3D viewing and rendering capabilities at any time.

MX Basics
Creating reports
Creating reports
Figure 26 − Report menu
Dynamic Reports provides access to a wide range of reporting options from an

expanding toolbar. You can include information from models, strings and
points, as well as perpendiculars, normals and intersections. You can use the
information to annotate the working display or save it to a file for importing
into a spreadsheet.
Alignment Reports
The alignment report options allow you to create customized reports of
horizontal alignment, vertical alignment and setting out data which can be
output to the screen or to a file. You can also use cut and paste techniques to
copy the data to a spreadsheet.
Figure 27 − Alignment Reports

1
MX Basics
Exporting data
Horizontal Alignment Report provides details of the horizontal geometry of the

alignment, including details of arcs, spirals and straights such as arc length,
radius and intersection point coordinates.
Vertical Alignment Report provide details of the vertical geometry of the
alignment, including details of curves, spirals and grades such as curve length,
radius, stations and elevations.
Many other types of reports can be produced in MX which are written to the
output window. You can then copy and paste these reports using standard
techniques in to any suitable Windows application.
Exporting data
Model and drawing data can be exported in several forms from MX. This allows
your design to be transferred easily between different sites, different computer
types and other drawing packages. Supported file formats are:
MX GENIO
MX MIFILE
DXF
plus any of the native AutoCAD or MicroStation export formats.
Add−Ins
You use the Add−In Manager to add or remove applications so that you can
invoke them from within MX for your convenience. For example, you can add
Windows Explorer to the Add−In menu using the Add−In Manager.
Add−In programs (previously known as Bonus Tools) are available to all Bentley
SELECT users from the Bentley web−site at www.Bentley.com.
Help
The Help menu gives access to the on−line help, tutorials, Bentley Web Site
information and information about the version of MX currently installed on
your machine.
Figure 28 − Help menu

MX Basics
Help
Help About MX gives information about the license you are using, and the
currently installed version of MX. It also provides access to the security report
which defines the applications that you are authorized to use.
For further details about the on−line help and tutorials, refer to Using the Online
Help and Tutorials.
Overview
The MX Online Documentation suite links together all the documentation for
the different MX products. You can access the help, tutorials and various online
documents in Adobe PDF format from the relevant Contents page for each
product.
MX Help
The MX Help system dynamically updates depending upon the MX
environment you are using. It contains information on the following:
MX Online Documentation − contains a navigation page, essential information,
a guide to using the help, Release Notes and System Configuration.
MX − gives access to three folders; Help, Tutorials and Linemode. For
details of the content of each folder please see below.
Getting Started − an overview of MX.
Using MX in Windows / Using MX in AutoCAD/MicroStation − an overview
of features specific to Windows / AutoCAD / MicroStation, and details of
how MX interacts with the CAD application. Plus information about CAD
specific commands and configuration settings.
Administration − information on how to configure your MX software.
Options in MX − contains detailed information about each main menu
option.
Reference Information − contains reference material for all file formats
(including style sets), and software fonts.
Tutorials − contains the tutorials for MX in each of the environments,
Windows, AutoCAD and MicroStation.
Linemode − contains complete Help for Linemode. The help has enhanced
navigation functions available at the bottom of the frame allowing selection
of help by Major and/or Minor option number.
Applications − contains information about MX application packages,
including; MXROAD, MXRENEW, MXRAIL, MXSITE, MXDRAW,
MXURBAN and MXDRAINAGE. Each of these sections includes both
Help and Tutorials for the application
Glossary − contains the definition of terms used in the MX products. The
glossary is also directly accessed from the Help by clicking red text.
Technical Information Resources − contains information about Bentley and
shortcut access to many of the Bentley websites.

1
MX Basics
Help
Accessing help and documentation

Help and documentation can be accessed in a variety of ways as follows:
By selecting Start ⇒ Programs ⇒ Bentley MX ⇒ Help and Tutorials
By selecting either the Help ⇒ Contents or Help ⇒ Contents Docked option
on the MX menu bar within MX itself.
By pressing the F1 key on the current panel (ie, the panel with the highlit
bar at the top). This method provides in−context Help by taking you
directly to the topic associated with the panel.
By clicking on the Help (?) button at the top right of any panel to obtain
What’s This? Help. When you click the button, the cursor changes to a ?
which you can then place and click over any piece of text on the panel for
which you require Help.
Tutorials
The MX tutorials provide step−by−step instructions about how to use many of
the options in MX. They are written in a typical project sequence. You can
access them from the relevant Contents page in the MX Online Documentation
suite.
Online Manuals
These are provided in Adobe PDF format for online viewing and printing. You
can access them from the relevant Contents page in the MX Online
Documentation suite.

MX Basics
System Administration
Backing up your projects
You should take backup copies of all your project files at regular intervals. You
should also back up any style sets, styles, macro symbols, or macro lines which
you have created. Note that these may not be contained in your project folder;
for example, you may have created a new style set and stored it in the
…\??_styles folder in the MXROAD software structure. It is important that
you organize your work in such a way that you know where all your files are
located so you can back them up.
The options Zip Project and Unzip Project, which are available from the File menu,
create a compressed backup file of an entire project in WinZip compatible
format. See the on−line help for further details.
It is also a good idea to take a backup copy of your system files (ie, the
MXROAD software structure) at less frequent intervals.
You should not create any project folders under the MXROAD software
structure.
Checking and backing up your model file

Many options in MX make extensive use of temporary models. Although these
models are deleted on completion of an option, the space taken up in the model
file is not regained automatically; you must compress the model file in order to
regain the space.
It is advisable that you carry out a model integrity check and take a fresh
backup prior to compressing. The process can be interrupted and fail where
there is insufficient disk space, a power supply problem or a corruption in the
data. Should a failure occur in compression for any of these reasons the model
file will have to be restored from a backup.
The compression process requires that the models are written to a temporary
model file, deleted from the original model file and then read back into the
original model file. To do this, you need three times the original model file size
of free space available on your hard disk.
It is recommended that a regular backup of the model.fil is taken, ideally on a

daily basis. This avoids data loss should a problem occur.
Problems with model files are very rare, but this should not lead to
complacency in maintaining backups. The procedure below describes how to
compress a model file.
1. Open Windows Explorer
2. Browse the folders to get to your project folder, for example, c:\mx tutorial.
3. Locate the file model.fil, and click on it with the right mouse button.

1
MX Basics
4. From the menu, select Copy.

5. Click the right mouse button again, and select Paste.
A new file is created, called Copy of model.fil. This is a copy of the MX model file.
Note that there is no problem doing this even though MX is still running,
although you should not have any MX panels open.
1. From the File pull down, select File Management ⇒ Report Model file
Figure 29 − Report Model File
The Check Model File Records option is checked by default.

1. Click Apply to run this check.
The results are displayed in the output window; you will probably need to scroll
up a few lines to see it all. It lists the number of records in the model file which
are actually filled with data, out of the total number that have been used, and
also the total space that will be available after compression.
Before you compress the model file, there are two options that you can use to
check that it is OK.
1. On the Report Model File panel, click Check Model Pointers, followed by Apply.
MX looks through the model file, and checks it to ensure that each of the
models is arranged correctly inside the model file. The results of this are
displayed in the output window again with a summary at the end, where the text
should say ‘END OF POINTER CHECK − 0 POINTER ERROR(S)
FOUND’, which indicates that the model file is OK. If there is a number here
other than zero, it means that there is a problem with one or more of the
models on the model file, which must be investigated before continuing with
any MX work. Scrolling up the list in the output window will show you which
model(s) and string(s) are affected. These need to be deleted using the MX
options on the Modify pull down, until running this report indicates that there
are no pointer errors.
1. On the Report Model File panel, click Cancel.
2. In Windows Explorer, click on View ⇒ Refresh.
3. Browse the folders to get back to your project folder, and check the size of
the model file model.fil.

MX Basics
4. Ensure that the Status bar shows there to be at least three times the size of
the model file available as free disk space.
If there is not, you will have to create extra free space on the hard disk before
you can safely compress the model file. Once you have done this:
1. From the File menu, select File Management ⇒ Compress.
2. On the Compress panel, click Model File.
3. Click OK.
The option may take a few moments to run, then a note in the output window,
if visible, should say W127 Model file stored & initializsed. If this message is not
given, you should contact your System Administrator, or your MX supplier for
further advice.
Disk maintenance
In order to maintain optimum performance from MXROAD, you should
manually delete files from your temporary directory (normally C:\temp) to
ensure that it does not become full (you can use Windows Explorer to do this).
You should also empty the Recycle Bin on your desktop at regular intervals.
Select the Recycle Bin, click the right hand mouse button and select Empty
Recycle Bin. Alternatively, double−click the Recycle Bin icon and check the
contents first.

1
MX Basics
User Support
User Support
United States and Canada
For support on this release, please e−mail the Bentley Helpdesk at:
support@bentley.com
Alternatively, phone the number below:
Tel: +1 800−BENTLEY
Elsewhere
For worldwide local contacts, see the contacts list on our Web site at
http://www.bentley.com to contact your local MX supplier.

2
MXROAD
MXROAD − Overview
MXROAD is an application constructed of a number of modules to permit the
efficient design of a road scheme from the input of the existing ground data
through to the production of drawings and reports defining the scheme.
Throughout the design, tools are available to permit analysis or visualization of
the design so that you can check and confirm each step of the design process.
The modules that make up MXROAD are:
Quick Alignment
Road Design and Delete String Groups.
Shoulder Design and Roadway Widening
Rule−Based Superelevation
Intersection Design
Pavement and Subgrade Design
Cross Sectional Editor
Report Generator
Other MX options such as MX Explorer and Surface Analysis are included on

the MXROAD toolbar for your convenience.
The options within the modules can be accessed via the main menu bar or via
the MXROAD toolbar, which in turn is accessed from the Applications toolbar.
The method of access is not important; however, the advantage of the
MXROAD toolbar is that the order of the options reflects the order of a typical
project sequence.
Figure 30 − MXROAD toolbar

2
MXROAD
Standard String Naming Convention
Standard String Naming Convention

The MX standard string naming convention (SNC) has been introduced to give
automatic integration of any design produced from any of the MXROAD
options. It may be switched on or off on a per project basis from the message
which appears when you start a new project, or from Tools ⇒ System Parameters.
Strings created by the MXROAD options are assigned names which store the
following information:
the string type (first character, eg, M for master string)
the specific road feature (second character, eg, C for center line)
the associated master alignment which defines the string group (third
character, eg, 0 for the first alignment)
the side of the master alignment on which the string was created (fourth
character, eg, 0 for the left hand side, I for the right hand side)
Because many of the options within MXROAD rely on the information
returned from the string names, it is not possible to use MXROAD on models
that do not follow the convention.
Any alignment you create and intend to use with MXROAD options must
conform to the convention, ie, the first two characters must be MC, and the
third character must be unique.
You must assign the feature set MXROAD.fns to any design model which uses
MXROAD options. You can do this using Tools ⇒ Model Defaults.
For full details of the SNC, refer to the on−line help.
Options in MXROAD
This section describes the options which are available from MXROAD. All the
options in MXROAD can be found within the standard menus, such as Design
and Edit. They are also available from the MXROAD toolbar (accessed from
the Applications toolbar) for your convenience to help you with the project
sequence.
For all the options in MXROAD, you can find more detailed information in the
on−line help.
Import
Although not strictly an MXROAD option, File ⇒ Import allows you to import
existing ground data on which the road design scheme is to be implemented.
The data may be imported in one of several formats:

MXROAD
Surface Analysis
AutoCAD DXF (*.dxf)

National Transfer Format NTF (*.ntf)
MX GENIO (*.txt)
MX Survey data (*.inp)
Softdesk Alignment and DTM
Eagle Point Triangulation
LandXML
In all cases, a model is created from the ground data. You should assign a
default feature set and style set immediately to the new ground model which
you can then draw using the option Display ⇒ Plan with Style Set if required.
If you have MX in Windows, but not MX in MicroStation or MX in AutoCAD,

you can still import data from a MicroStation DGN or AutoCAD DWG file.
You can either convert the file to DXF format or use the MX data translator
program MX Change.
NTF file format is used by the United Kingdom Ordnance Survey for map
data.
Surface Analysis
This option lets you perform analyses of the surface on which the design is to
be built. This is essential to confirm that the imported data is correct and
contains no errors. Typically the analysis will highlight errors in level and will
also provide a graphical representation of the existing surface; both of which
can provide essential information for your design.
There are nine different types of analysis each taking you through the necessary
steps in a minimum amount of time. The options are:
Display contours
Elevation bands
Slope bands
Aspect bands
Flat spots
Steep slopes
Flow arrows
Simple profile
Display triangulation

2
MXROAD
Alignment Design
Figure 31 − Ground model showing contours
In MX in Windows, you can also highlight any errors in elevation by color filling
the triangulation and illuminating the view from the Zoom toolbar.
Alignment Design
The Alignment Design options enable you to create the alignment for the road
design. You may use either the Quick Alignment options Horizontal Design and
Vertical Profile, or Alignment which gives greater flexibility but may take longer to
learn.
Whichever method is used, the end result is the same, a complete alignment
defined both horizontally and vertically. The alignment is converted to a master
string which is generally used as the center line along which a roadway and other
features can be designed.

MXROAD
Alignment Design
Figure 32 − Alignment Design
Quick Alignment
Horizontal Design
Horizontal Design enables you to create horizontal alignments using dynamic
Intersection Point (PI) placement and manipulation.
The following layout options are available:
Add PI − adds an PI to an alignment.
Move PI − dynamically moves an PI to a new location.
Insert PI − inserts an PI between existing PIs
Remove PI − select a point near the PI to be removed.
Other features enable you to:
edit curves
view details of the currently selected curve
draw clearance lines and circles
amend the design parameters
delete a whole alignment

2
MXROAD
Alignment Design
snap PIs to an existing point

alter the position of a finished alignment
undo up to 20 previous actions.
You can also obtain a printed report of the horizontal alignment.
Vertical Profile
Vertical Profile enables you to create vertical alignments using dynamic PI

placement and manipulation. The backcloth is a vertical profile of an existing
horizontal alignment extracted from the triangulation model of the ground.
The following options are available:
Add PIs
Move PIs
Remove PIs
Insert PIs
Lock PIs
Delete profile
Calculate overall cut and fill
Calculate grade and radius
View details of a curve
Change the vertical exaggeration
Amend design parameters
Set the curve data
Change the view of the display area.
There is also a table editor which you can use instead of dynamic placement to
specify values such as grade and curve radius using the keyboard.

MXROAD
Road Design
Alignment
Alignment is used to design alignments for roads and other engineering features.
An alignment describes the basic horizontal and vertical position of a design
from which all other surface features are generated. For a road, the alignment
usually represents the center line, but may represent a pavement edge or any
other convenient feature.
Alignments are created in two stages: first the horizontal design, then the
vertical design.
For both horizontal and vertical design, there are three design methods; the
Element method, the Intersection Point (PI) method and the Spline method.
The Element method allows you to construct an alignment from a series of
elements, either straights or circular arcs, connected by spiral curves as required.
The PI method produces the same end result but allows you to construct the
alignment by entering a series of intersection points. The lines joining these
points are tangential to the curves which connect the straight elements. Spirals
can also be included if required. Finally, the Spline method allows you to specify
a series of points through which a cubic spline curve is fitted.
Complete alignments are converted to master strings for use with the other
MXROAD options.
Road Design
Road Design is a series of options that take you through the process of
designing a road from an existing master string. It consists of a number of
stages; Roadways, Rule−based Superelevation, Road Widening, Shoulder Design and
Curbs, Shoulders and Sidewalks.

2
MXROAD
Road Design
Figure 33 − Road Design
Roadways
Roadways creates a road surface using either a standard template or one you have
customized yourself. The templates contain all the details of the road surface,
including the roadway width and the cross slope or vertical offset to the
roadway edge strings. There are standard templates for many different types of
roadway, including single roads, with a single lane either side, and dual roadways
with two or three lanes.
The process you follow through the Road Design Roadways Wizard is as
follows:
Specify the model and master string along which you wish to create the
roadway. This will generally be the model containing the alignment created
using one of the Alignment options.
Select the template to be applied.
Check the template design details and modify them if required.
Specify the start and end of the roadway design.
Generate the roadway strings (including a center line level string).
Repeat the operation with another template, if the start and end of the
roadway was not the whole extent of the alignment.
You should design the roadway along your alignment in one session of the Road
Design Wizard.
If you change templates along the master string, you can choose to join the
equivalent strings in the two portions of roadway automatically. The roadway

MXROAD
Road Design
strings are joined either linearly or with a reverse curve, both horizontally and
vertically. If you include a central reserve in one roadway but not the other, you
may need to modify the center line level string to include a vertical step at the
correct position.
If the results are not what you want, you can remove the roadway strings using
Modify Design ⇒ Edit Strings ⇒ Delete String Groups. This option allows you to
select all the roadway strings and delete them. Recreating the roadway using a
modified template is quickly achieved.
Rule−based Superelevation
Rule−based Superelevation provides a simple approach to the application of
superelevation to a road. The superelevation applied is based on parameters
specified in design rules files, which conform to either a local or national
standard.
The process is defined by the following steps:
Specify the master string of the road to which you wish to add
superelevation.
Specify the design rules and design speed to be used. The design rules will
determine whether single or dual roadway parameters are to be used.
Select the pivot method to be used.
Choose a linear, reverse curve or biquadratic curve application (only the
linear type is available for some pivot methods).
Select the roadway edge strings to which you wish to apply superelevation.
The calculations are then made and a summary of the results is displayed.
Before you apply the superelevation, you can confirm that the superelevation is
correct or amend the calculated values if required. Following the review
process, the superelevation is applied to the roadway.
Road Widening
The Road Widening Wizard provides a simple approach to the process of road
widening, and can be used to create extra lanes, bypass lanes, parking areas or
intersection widening.
Select the road center line and the string to widen.
Select the type of taper to apply, either linear (as illustrated below) or
reverse curve.
Define how the taper is to be specified; by length, by ratio to the width or
by station.
Specify the length and width of the widening.
Specify either projected cross slope or hinged cross slope as the method of
application for the widened section.
Create the widening.

2
MXROAD
Road Design
Road string to widen
after
before
Length of
taper
Road center line
Figure 34 − Road Widening
You can retain the original roadway string along the widening, or you can delete
it.
Shoulder Design
Shoulder Design is used to create shoulders from the edge of the roadway. Several
different methods are available to apply the cross slope across the shoulder, and
the method can be changed automatically when certain criteria are met.
The standard shoulder methods are:
Fixed cross slope − specify the cross slope from the roadway edge to the
shoulder.
Follow roadway cross slope − use the same cross slope for the shoulder as
that used for the roadway.
There are other methods which you can specify for the outside curve of a
shoulder. These include:
Maximum shoulder break − uses the standard shoulder settings until the
roadway is superelevated and a maximum cross slope difference between
the roadway and shoulder is reached. At this point, the shoulder cross slope
is set to a specified value or to match the roadway cross slope, depending
on the option selected. The transition length between the maximum cross
slope difference and the point at which the new values are in force may be
specified, and may also be offset along the roadway from the point of
maximum cross slope difference.
Shoulder rollover − this works in a similar way to the maximum shoulder
break method, except that during restoration the shoulder is split in two
widthways so that the cross slope break at the edge of the roadway is
decreased.
Maximum algebraic difference − uses the standard shoulder settings until
the roadway is superelevated and a maximum cross slope difference

MXROAD
Intersection Design
between the roadway and shoulder is reached. From this point until the
roadway achieves full superelevation, the shoulder cross slope is varied so
that the maximum algebraic difference is maintained.
Maximum algebraic difference (part width) − for this method, the shoulder
is split in two widthways by a new string and cross slope is applied to the
outer portion in the same way as for the maximum algebraic difference
method. For the inner portion, ie, between the roadway edge and the new
string, the standard shoulder cross slope is applied at the point of
maximum algebraic distance, which gradually changes to the roadway cross
slope at the point where full superelevation begins. It is also over this
distance that the new string is created.
Curbs, Shoulders and Sidewalks

Curbs, Shoulders and Sidewalks is similar in operation to Roadways, except that a
different set of templates is used to create the required strings. You can choose
to apply the templates on either the left of the roadway, the right of the roadway
or both sides.
Normally, you would use this option after you have applied superelevation and
completed any intersection design.
Intersection Design
The Intersection Design options are used to create a T intersection between a
through road and an intersecting road.
Figure 35 − Intersection Design

2
MXROAD
Before attempting intersection design you must have completed the design of
both roadways including widening at the intersection and applied
superelevation. Once the intersection design is complete, you can complete the
design and add curbs, unpaved shoulders or sidewalks.
You can also create cross roads by adding fillets to all corners of two
intersecting roadways. You may create fillets from circular arcs or three center
curves, and then regrade the entire intersection by dynamically editing the
vertical profile using information from the roadway edges. This may be to
improve water flow across the intersection or to relocate a low spot.
Once this is done, you can add traffic islands from a pre−defined traffic island
style library, and then complete the intersection by automatically joining the
fillets to the roadway edges.
Earthworks Wizard
The Earthworks Wizard is a standard MX option which is used to design an
earthworks structure between two models, the design model containing the new
design surface and the existing ground model. The earthwork design relies on
the specification of an earthwork style, together with a number of strategies to
be used when specified criteria are met.
The Wizard guides you through the process of specifying models, section sets,
earthwork styles and strategies, the criteria to trigger the strategies and so on,
until you apply your earthwork design requirement to the models.
Specify the models and essential strings.
Assign styles to the four style definition areas (left and right cut and fill).
Set up analysis control.
Create the earthwork design.
To make the procedure as simple as possible, the Wizard has access to a library
of earthwork styles such as simple slope and slope/bench combinations. You
can apply different earthwork styles and strategies to lengths of the road by
specifying the start and end points. Alternatively, you can create your own
custom earthworks styles specific to the current design or your national design
rules. These custom earthwork styles can then be saved in your own library for
future use.

The Pavement and Subgrade Design Wizard is used to create pavement layers
and the subgrade for a roadway. You can also produce working drawings of the
cross sections, which show the pavement construction in detail, and calculate
volumes between the different construction surfaces and the existing ground.

MXROAD
Pavement and Subgrade Design requires the following information before you
begin your design:
the design model and center line of the roadway
existing cross sections for every point on the road center line (ie, the
master string) for both the ground model and the design model. For
example, if you have generated cross sections at tangent points on the
master string in your design model, these must also exist in the ground
model.
Figure 36 − Cross section showing pavement layers

2
MXROAD
Figure 37 − Modify
Edit Strings and Edit Points
You can use the standard MX Edit options during all stages of an engineering
design as follows:
for the existing surface − to correct erroneous elevations and the ground
position of points and strings.
for feature design − to remove redundant parts of strings where they
intersect other features, or to insert non−standard features.
for analysis − to create boundaries within which areas or volumes are
derived.
for visualization − to enhance and improve model information for drawings.
Delete String Groups
The MXROAD option Delete String Groups is particularly useful because it allows
you to delete strings of a particular type in one operation. For example, if you
create a roadway and wish to re−design it using the same alignment, you can
delete all the roadway strings associated with the alignment.
The cross sectional editor allows you to view cross sections and modify the
points on them. The changes you make to the cross sections are reflected in the
model data. For example, you can use this to adjust earthworks slopes so that
they lie within the land take limits of your construction project.

MXROAD
Project Sequence
Sections can be dynamically edited at individual stations by specifying an offset,

elevation or slope. You can either edit a cross section element in isolation, ie,
without affecting the elements which lie outside of the element you are editing,
or you can edit an element and have all outer elements retain the same relative
position.
Volumes can be calculated at any time between the ground and design models
within a selected station range.
Project Sequence
The project sequence is critical in MXROAD. For example, you cannot use road
widening if the roadway has not been created, and, if you wish to superelevate
the roadway, you must do this before creating an intersection.
The MXROAD project sequence is shown below:
Horizontal Alignment
Vertical Alignment
Roadways
Rule−based Superelevation
Road Widening
Create Fillet
Regrade Intersection
Create Traffic Island
Tidy Intersection
Shoulder Design
Curbs, Shoulders and Sidewalks
Earthworks Wizard
Not all steps need to be carried out each time; for details of which options are
mandatory and which are optional at any particular stage, refer to the on−line
help.

2
MXROAD
Project Sequence

Index
Numbers DXF format, 2−3
3D View, 1−44 exporting, 1−46
3D View and Flythough, 1−44 Dynamic reports, 1−45
E
A
E−mail address, 1−52
Add−In menu, 1−46
Eagle Point Triangulation, importing, 1−34
Alignment, creating, 1−39
Earthworks wizard, 1−39, 2−12
Alignment design, 2−4 Editing strings and points, 2−14
Alignment reports, 1−45 Exporting data, 1−46
Analysis menu, 1−40
Analysis options, 1−40 F
Applications toolbar, 1−28
Feature set, definition of, 1−6
Area calculation, 1−40
File menu, 1−34
Final drawings, 1−44
B Flythrough, 1−44
Backing up projects, 1−49 Full alignment, 2−7
C G
Configuration Gaps, 1−5
MX in AutoCAD, 1−20 GENIO format, 1−34, 2−3
MX in MicroStation, 1−27 exporting, 1−46
Contours, generating, 1−40
Cross sections, editing, 2−14 H
Cross Slope Checker, 1−41 Help desk, 1−52
Curbs, shoulders and sidewalks option, 2−11 Help menu, 1−46
Horizontal design, 2−5
D
I
Data interoperability, 1−8
Deleting strings, 2−14 Import option, 2−2
Design menu, 1−38 Importing data, 1−33
Design options, 1−38 Intersection design, 2−11
Disk maintenance, 1−51
Disontinuities. See Gaps L
Display, Menu, 1−35 LandXML, 1−34
Display options, 1−43
Drainage networks, 1−40 M
Draw menu, 1−43 Menu, Display, 1−35
Draw options, 1−43 Menu bar, 1−13
MXROAD Intr oduction i−1

Index
Model defaults, 1−35 Q

how to assign, 1−7 Quick alignment, 2−4
Model file, 1−2
Models, editing, 1−42 R
Modify menu, 1−42 Raster backcloth, 1−36
Modify options, 1−42 Report menu, 1−45
Mouse, use of buttons, 1−11 Report options, 1−45
MX Basics, 1−1 Road design options, 2−7
MX Controls toolbar, 1−26 Road widening option, 2−9
MX environments, 1−8 Roadways option, 2−8
AutoCAD, 1−16 Rule−based superelevation, 2−9
MicroStation, 1−22
Windows, 1−15 S
MX toolbar, 1−17 Security Report, 1−47
MX Toolbox, 1−24 Shoulder design option, 2−10
MXDRAINAGE, 1−28 Shoulder rollover, 2−10
MXDRAW, 1−29 SNC, 2−2
MXRAIL, 1−28 Standard string naming convention, 1−7, 2−2
MXRENEW, 1−28 Starting MX, 1−30
MXROAD, 1−28 Startup panel, 1−31
MXSITE, 1−28 Strings
MXURBAN, 1−28 editing, 1−42
types of, 1−3
Style set
N definition of, 1−6
Null elevations, 1−6 using to create a working display, 1−36
Support, 1−52
Surface analysis, 1−41
O of the ground, 2−3
Output window, 1−14
Overview, 2−1 T
Toolbars, 1−14
Tools menu, 1−35
P
Triangulation, creating, 1−40
Panels, components of, 1−12
Pavement and subgrade design, 2−12 U
Perspective views, 1−44 User support, 1−52
Points, 1−4
Preferences, 1−37 V
Profiles, creating, 1−40 Vertical design, 2−6
Project, creating, 1−31 View menu, 1−37
Project sequence, 1−33 Visibility, 1−41
i−2 MXROAD Intr oduction

Index
Visualize options, 1−44 Widening, 2−9

Visualize menu, 1−44 Working display, creating, 1−35
Volume calculation, 1−41 Working drawings, 1−43
W
Web page address, 1−52
MXROAD Intr oduction i−3

Index
i−4 MXROAD Intr oduction

Bentley MX - 2004 Edition MXROAD - Introduction 022004

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Bentley MX - 2004 Edition MXROAD - Introduction 022004

Hochgeladen von

Copyright:

Verfügbare Formate

Bentley MXROAD 2004 Edition

AutoCAD, and AutoCAD Map are registered trademarks of Autodesk, Inc.

HOOPS is a registered trademark of Tech Soft America.

OpenGL is a registered trademark of Silicon Graphics, Inc.

NetWare® is a trademark of Novell, Inc.

Internet Explorer, MDAC, Windows, Windows NT, Windows 2000 and

Portions Copyright © ComponentOne, LLC 1991−2002. All Rights Reserved

DWGdirect 2002 by OpenDWG Alliance Inc. All rights reserved..

MXROAD Intr oduction iii

MXROAD Intr oduction v

vi MXROAD Intr oduction

MXROAD Intr oduction 1−1

What is String Modeling?

The model file and models

Existing Design Boundary

Triangulation Sections Drainage

Figure 1 − The model file

1−2 MXROAD Intr oduction

Strings and string links

MXROAD Intr oduction 1−3

1−4 MXROAD Intr oduction

(x, y, z, ch, b, rad)

Figure 2 − String points

Figure 3 − Gaps in strings

MXROAD Intr oduction 1−5

Feature Partial Name String Type

Road Center Line MC?? Master

Carriageway (Edge) CE?? Feature

Carriageway (Top of Curb) CT?? Feature

Shoulders (Edge) ES?? Feature

Shoulders (Unpaved shoulder) EV?? Feature

Default feature sets are provided with the software.

1−6 MXROAD Intr oduction

Standard string naming convention

If you have purchased MXROAD, an application developed for highway design,

MXROAD Intr oduction 1−7

1−8 MXROAD Intr oduction

In MX, there is a fundamental difference between a DPW and a DPF. A DPW

MXROAD Intr oduction 1−9

Model file DPW or DPF

CAD−only layers/levels MX layers/levels

Figure 5 − MX data interoperability

1−10 MXROAD Intr oduction

the Windows cursor − used in panels and for manipulating Windows.

the CAD cursor − used when specifying CAD commands in

the MX cursor − used when specifying MX options

MXROAD Intr oduction 1−11

Figure 6 − Typical panel layout

1−12 MXROAD Intr oduction

MXROAD Intr oduction 1−13

To dock or undock a toolbar, double−click the toolbar header.

Figure 7 − Plan with Tools toolbar

1−14 MXROAD Intr oduction

Figure 8 − The MX frame

MXROAD Intr oduction 1−15

Figure 9 − The AutoCAD frame

1−16 MXROAD Intr oduction

Using AutoCAD commands, when you create a polyline on an active MX layer,

A custom object is an object such as an MX string which is not a native

MXROAD Intr oduction 1−17

Figure 10 − The MX toolbar

1−18 MXROAD Intr oduction

The auto−convert setting has no effect if you modify an MX string; the MX