Download - Transitioning to MX SELECTSeries 3 and OpenRoads Technology€¦ · Transitioning to MX SELECTSeries 3 ... •Note this uses the example workspace and so Mxroad ... Transitioning

The MX Association of Australasia 28-30th July 2013

Transitioning to MX SELECTSeries 3

and OpenRoads Technology

Ian Rosam, Product Manager, BSW – Development, Civil Design


Workshop Agenda (1.5hrs including Q&A)

• What is OpenRoads (5 mins)

• Delivered civil workspaces (15mins)

– What you need to know about the supplied civil workspaces

• Administration and setup Essentials for OpenRoads (20mins)

– Civil Features Definitions / import from pss and setup of features

– Civil Terrain Definitions and Element Templates

• User Essentials of MX SS3 integration (40mins)

– MX Seed files, the active MX model and managed civil models

– Default civil styleset concept and how to control features in normal use and passing back geometry to MX


What is OpenRoads?


http://www.bentley.com/en-US/Promo/OpenRoads/OpenRoads+Technology.htm

OpenRoads is…





OpenRoads is… • the common technology for Bentley civil products that offers

immersive interaction of survey, corridor modeling, geometry, terrain modeling, dynamic sections, and much more.

• immersive interaction of – Survey

– Geometry – Terrain modeling – Corridor modeling

– Dynamic cross sections

– Civil cells – Design intent – Design-time visualization

OpenRoads


MX SELECTseries 3

MX SELECTseries 3 includes all the core MX functionality and enhanced integration with the OpenRoads technology • Civil Geometry saved to MX writes to the MX log

• Enhanced Feature Definition Toolbar

– Includes MX model control

– Associate MX strings option

• Enhanced support for DGN models

• Enhanced MXSRIPT options

OpenRoads


SELECTseries 3

http://Learn.Bentley.com © 2013 Bentley Systems, Incorporated

8

@BentleyCivil

Bentley Learn Server

Lectures

BCR2LC1 - Administering Bentley Civil Software

BCR2LC2 - Transitioning to OpenRoads Technology

BCR3LC17 - Jump Start with Civil Workspaces

BCR3LC11 - Understanding Features

Workshops

BCR2WK5 - Administering Bentley Civil Software Workshop

BCR4WK5 - Moving to SELECTSeries 3 for Bentley Civil Users


9

@BentleyCivil

Learning Paths: Ready-Made Training Plans

Choose from: – Bentley recommendations

– Configure your own

• Organizational

• Personal

Select: – Product(s) and version(s)

– Language

– Training type

Enroll team members in: – One learning path

– Multiple learning paths


10

@BentleyCivil

Learning Path:

Here’s the name and link to a short learning path that includes this session and recommended modules that you may share with your colleagues:

V8i (SELECTseries 3) OpenRoads Technology Learning Path

http://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=104292#.UYkxZxK2r9s.email

http://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=104292




I downloaded and installed the software and I’m thoroughly overwhelmed.. Where do I start?

Delivered civil workspaces


What is a MicroStation Workspace?

– A custom MicroStation environment or configuration.

– By selecting a defined workspace, you customize

MicroStation for a specific discipline, project, task, or

standard.


Civil Workspace


Exercise – Using Workspaces with MX


Objective – Create MX Projects using workspaces and review

– Project 1

– Create a new project

C:\MX Conference 2013\MXSS3 Civil

• Ensure the following settings

– Project 2

Create a new project

C:\MX Conference 2013\MXSS3 MX

• Ensure the following settings


Summary – Startup panel – MXStartup Panel

• User Untitled is essentially the same default mode as in SELECTseries 2

• User Example allows access to the example delivered workspace Project ‘Bentley Civil Metric’

– MX project associates to a MSTN workspace and is recalled when selecting the MX Project • {MX Project name}.mss

Note - Advisable to exit completely to change projects if they use different workspaces


Summary – Workspaces – Example Civil Workspace

• Used by all Bentley Training material / workshops • Different colour pallette (default MSTN), seed files, working

units, • Default Civil styleset is new Civil_Features_metric.pss • The MX_Active_Model is Default

– Untitled Workspace • Essentially the same as SELECTseries 2 • Includes MXRoad feature definitions • The MX_Active_Model is MX • Default Seed file for 2d / 3d is different

– MX project associates to a MSTN workspace • {MX Project name}.mss


Administration / Setup Essentials for OpenRoads


Installation

• Allows Side by Side installation with previous versions of MX

Differentiator in the default installation is

C:\Program Files (x86)\Bentley\MX V8i

C:\Program Files (x86)\Bentley\MX V8i (SELECTSeries 3)

Or will have build indicator for updated files

..\08.11.09


Advance Preparation - MicroStation

• Review current MicroStation resources – are they in DGNLibs or can they go there?

• Development of MicroStation element templates for Terrains and graphical filters

• Review CAD standards – changes due to managed civil models and use of reference files in workflows


Advance Preparation - Civil • Review Design File Settings within Seed Files –

Determine default settings for Civil Formatting • Review Workspace Preferences – View Options >

Civil • Review new configuration variables • Review new workflows and determine which areas

may be moved forward to new methods. • Are there any customized workflows that need to

be integrated? • Review reports; determine defaults, deficiencies


Advance Preparation - Engineering

• Review horizontal and vertical design standards – validate local standards.

• Superelevation tables

– SRL

– External Calculation / Import


Resource Usage

Reuse: – MS levels, fonts, cells, line styles

– Element templates

– DGN Libraries

– Survey TIW files

– XIN, PSS, DDB, SMD (XML)

– XSL style sheets (reporting)

Create: – Element templates

– Graphical filters

– DGN libraries

– Project settings

– Civil cells

Upgrade: – Template library – add superelevation

flag

– Design Standards – add vertical


What are feature definitions and how can I use my own styles ?


What is a “Feature Definition”?

• What is a “Feature Definition”?

– Defines the properties used to control how a feature is to be displayed, annotated, computed, etc..

– These are customizeable.

– These should normally be created in advance by an administrator and propagated across an organization in order to standardize designs.


Types of Feature Definitions • 3 types of feature definitions are supported.

– Point Feature • Lighting column • Control Point • Sign post

– Linear Feature • Kerb & Gutter • Wall • Ditch

– Surface Feature • Existing Ground • Aggregate Base • Asphalt Pavement


Project Explorer • Feature Definitions are created, modified and

reviewed in MicroStation’s Project Explorer application.

– MicroStation File > Project Explorer > Civil Standards

– Note: Tab Display Controlled by Settings > Project Explorer


Project Explorer

• The Civil Standards tab will show you what Feature Definitions are contained in your current file, as well as those in any specified DGN Libraries.

Current File

DGN Libraries


Civil_ContentManagementDGNLiblist

• This variable is used to define which specific DGN Libraries are to be used to define your features.

• If this variable is not set, then all the DGN Libraries will be read and any that contain features will be listed.


Link to Native (MX)

• Creates an actual link back to a user specified PSS File


Link to Native (MX)

• Since the PSS has no categories/folders, none are available to be carried through to the Feature Definitions.


Link to Native (MX)

• However, right-clicking gives you the ability to create categories.


Link to Native (MX)

• MX String dimensions dictate the resulting mapping to Civil Feature Definitions.

• Linear

– All Feature strings are given Linear Feature Definitions

– All Section Strings are given both Linear and Surface Feature Definitions

• Point

– All Point String types are given Point Feature Definitions.

• Surface

– MX Triangulation.pts stylesets are given a surface feature definitions.

Note - Cross and long section pss result in both linear and surface definitions


Link to Native (MX) • Feature Names must be unique. As such, each Feature Definition

may contain multiple Feature Types.

• Any Surface Definition Automatically maps to an Element Template not the native style.


Link to Native (MX)

• You could then use standard cut/paste techniques to re-organize your feature definitions.


Link to Native (MX)

• Right-Clicking on any feature definition give you access to multiple options, including the ability to review the properties.


Link to Native (MX) • Notice that the Feature Definition is automatically linked back

to the native style in the PSS. This is where it would get the symbology properties, annotation properties, etc.


Link to Native (MX) • If you wish to override this automatic designation with another

selection from your PSS, you can do this by simply selecting another style from the drop down.


Best Practice • Linking to your legacy style files is intended to be a

‘starting point’ to help you get your feature definitions created quickly.

Best practice is to do this only once. After the initial linking has been done, any structural

changes to the feature definition tree (new features, renaming of features, etc.) should be made directly in the DGN Lib.

Note: An exception would be changes to symbology or annotation, which would be made in the legacy style file.

http://www.google.com/url?sa=i&rct=j&q=best+practice&source=images&cd=&cad=rja&docid=7nj3IXkeJjhHfM&tbnid=2f0tK6Ox5p2w-M:&ved=0CAUQjRw&url=http://blog.pluralsight.com/2013/01/29/who-decides-what-is-a-best-practice/&ei=fwpwUYO2L_Gs4AO5lYHQCw&bvm=bv.45368065,d.dmg&psig=AFQjCNFJ27PfHg6qTjosBdwfMunxw3fc1A&ust=1366383563645141


Exercise – Importing PSS and Creating Feature Definitions


Objective – Import Styleset to Create Feature Definitions and Review

– Open the project C:\MX Conference 2013\MXSS3 Civil • Note this uses the example workspace and so Mxroad

features are not available to use.

– Create a new DGN – MXRoad Features.DGN – Project Explorer > Feature Definitions > Link

MXRoad.PSS • Review results in Project Explorer and discuss • Review Feature Definitions properties in Element Information

– Project Explorer > Feature Definitions > Link MFW Triangulation.pts • Review Element Templates • Add and configure Terrain Element Templates


Summary – Feature Definitions – Project Explorer / Element Information

• Feature definition – naming prefix

• Linear Default Settings – Auto create 3D

– Corridor Template

– Terrain Model Feature Type

– Create Template Geometry

• Plan – Native Style or Element Template

– Auto Annotate (requires native style)

– Auto Export (recommend setting False)

• 3D / Profile / Intersecting Profile / Cross Section – Native Style or Element Template


Summary – Feature Definitions

– Surfaces

• Must use Element Templates

• Cad Standards for – Contours – major / minor / depression

– Triangles

– Triangle vertices

– Flow Arrows

– High and Low Points

– Save to DGNlib


How do MX and the OpenRoads tools integrate?


MX Configuration Essentials • MX > View > Configuration

• General – Active MX model

• File Management – Seed files

– Changes to mx_seed_m_3d+2d.dgn

• Data Conversion – Delete Strings from Model on Drop or Delete


(Linear) Features Toolbar

• With no Active model all available features will be available. – the feature does not maintain a link to the styleset this comes from the

active model

– With no active MX model present and the feature does not call a element template but requires the pss to define it’s display it reverts to the configuration variable defining default styleset

MX_DEFAULTCIVILSTYLESET=publicstyles/mxroad.pss

# for untitled workspace

• The processes here are very similar to the MX conversion toolbar for converting CAD graphics to MX string features.


(Linear) Features Toolbar

• The model picker is not the same as normal MX listings, so no right click options for model defaults etc. Use Display toolbar or similar.

• With a Active Model only features appropriate to that styleset will be listed. – Exceptions to this rule

• Feature names must be unique

• Construction

• Make use of ‘Use Active Feature’


Import from MX • Import

– From file - browse to a model.fil

– From MX geom from Halgn, Valgn, Verat

– From Active MX project model.fil

• Import and Create Civil Rules – Makes editable geometry

– Will not auto save changes # can be toggled on

• Note

– G Strings as Alignments with Profile

– M Strings to 3D linear elements


Export to MX

• The Active Model provides the storage model for export

Hint - Use selection set for multiple features to the same model – Note Refresh 1 will include ability to use ‘Graphical Filters’ to be defined

that will aid in selection and exporting completed corridor designs linear features


Audit Trail

• Export Geometry – Writes to the MX log Halgn, Valgn, Verat

– Writes to the MXData folder Halgn, Valgn, Verat • Note it will overwrite but history is provided in the log file

• Import Geometry – Writes Major Option ‘Script’ information to the log file

• This can be captured and used in input files to push geometry from MX if required.

– Writes to the MXData folder Halgn, Valgn, Verat • Note it will overwrite but history is provided in the log file


Audit Trail / Input files – MX option ‘Script’ • MX uses the major option ’script’ to suspend the MXengine and allows

processing of external / CAD operations. This process was originally implemented to facilitate Final Drawings annotation and page layout as well as attachment of reference files.

• Script can be used to call Microstation key-in commands directly using commands and parameters.

• Syntax Script, key-in {command}, {parameter}

The following example can be used to reset the view extents of the drawing. script,FIT VIEW EXTENDED 1

• Terrain Example script, terrainmodel import file=model.fil model=DESIGN edgemethod=NoRemove

• Geometry Example script, geometry file import model=PROPOSED name=GC20


Exercise – Integrating MX & OpenRoads


Objective – Use MX features in OpenRoads

– Open the project C:\AU 2013\MXSS3 Civil – Open – MXRoad Features.DGN created in the last session – Create 2 Models

• MXRoad – associating MXRoad.pss • MX Detail Design – associating MX Detail Design.pss

– Project Explorer > Feature Definitions > Link MX Detail Design.PSS

– Use Feature Toolbar to set each model active and review features

– Project Explorer > Feature Definitions > Link MFW Triangulation.pts • Review Element Templates • Add and configure Terrain Element Templates


Summary – MX Features and OpenRoads

– Import / Export of Civil Features to MX

• M&G Strings

• 3D

• Log file


56

@BentleyCivil

Bentley Learn Server Lectures

BCR2LC1 - Administering Bentley Civil Software

BCR2LC2 - Transitioning to OpenRoads Technology

BCR3LC17 - Jump Start with Civil Workspaces

BCR3LC11 - Understanding Features

Workshops

BCR2WK5 - Administering Bentley Civil Software Workshop

BCR4WK5 - Moving to SELECTSeries 3 for Bentley Civil Users


57

@BentleyCivil

Learning Paths: Ready-Made Training Plans

Choose from: – Bentley recommendations

– Configure your own

• Organizational

• Personal

Select: – Product(s) and version(s)

– Language

– Training type

Enroll team members in: – One learning path

– Multiple learning paths


Transitioning to MX SELECTSeries 3

and OpenRoads Technology

Ian Rosam, Product Manager, BSW – Development, Civil Design