Best Practices - CAD

3/28/2014

1

© 2014 Bentley Systems, Incorporated

OpenRoads Best PracticesOpenRoads Best PracticesBob Rolle, Civil Application Engineer

Best PracticesBest Practices

• This presentation teaches many of the best practices discovered by the Bentley team during the Open Roads d l t b t d th l t f F lldevelopment, beta program and the last year of use. For all Bentley Civil users.

2 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

3/28/2014

2

Learning ObjectivesLearning Objectives

After this session you will be able:

• use the best practice for the use of reference files in various• use the best practice for the use of reference files in various types of projects.

• select the most appropriate file type (2D or 3D) for various components.

• understand the general use of native databases moving f d i SELECT i 3


forward in SELECT series 3

• This guide is equally applicable for the MX, InRoads or GEOPAK families of products.

NotesNotes

• Utilizing OpenRoads technology, each product contains the identical Bentley Civil toolset and identical workflow.

• However, the transitioning tasks may vary, so the differences will be identified.


3/28/2014

3

• Keep in mind that there is no ONE best practice. • This presentation and associated guide presents

DisclaimerDisclaimer

This presentation and associated guide presents suggestions and best practices and it is the responsibility of each organization to determine how the Best Practices fits into your standard policies, procedures and operations.


Best Practices DocumentationBest Practices Documentation


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

3/28/2014

4



3/28/2014

5

2D or 3D?2D or 3D?


Best Practice Recommendations:

Geometry FilesGeometry Files

• Store horizontal geometry in 2-D DGN models.

• Name your profiles based on rules from native products.

.


3/28/2014

6


Terrain Files Terrain Files

Store terrains in 3-D DGN models.

If stored in 2-D model, a 3-D model is automatically created.

.



Survey Files Survey Files

• Store survey data in 3-D DGN models.

• Flatten if needed for 2-D downstream uses.

.


3/28/2014

7

Best Practice Recommendations: Start with 2D Model.

Corridor Modeling Files Corridor Modeling Files

Start with 2D Model. • Modeling creates both 2D and 3D elements• Isolate the 2D elements from 3D elements;

separation makes easier picking of elements / components

.


2D and 3D Summary2D and 3D Summary


3/28/2014

8

Reference FilesReference Files


DGN Based ObjectsDGN Based Objects Geometry

Plan

3 D Models

Terrain Models

imetrics


3-D ModelssSurvey

Superelevation

3/28/2014

9

• Just Reference the data you need.• It is all file management

WorkflowWorkflow

• It is all file management• The way you break files up depends on:

• Your organization• The Project• The amount of interactive change you want


Terrain Topo Alignment #1

Example #1Example #1

e a opo #1

Alignment #2

Alignment #3


• Alignment files include: Alignments, Super, corridors, etc.

3/28/2014

10

Terrain Topo Alignments


p g

Superelevation Corridors Cross Sections


• Alignment files include: Alignments, Super, corridors, etc.

Terrain #1 Terrain #2 Topo #1 Topo #2


Alignment #1 Alignment #2 Superelevation #1

Superelevation #2

Corridor #1 Corridor #2 Cross Section #1

Cross Section #2


• Everything is broken up into individual files

3/28/2014

11

Do I Have to Use Reference Files?Do I Have to Use Reference Files?

• No, reference files are NOT required. – Simple project.– Preservation / rehabilitation projects.– Individual designer or very small work team.– Utilize models within a single file in lieu of referencing separate files.

• Base reference file usage on workflow / workteams, rather than size of project.


• Excellent to provide granularity to projects.

Limitations of ReferencesLimitations of References

• Profiles must reside in same file as associated geometry

• Supers can be in their own file and referenced to corridor but• Supers can be in their own file and referenced to corridor, but assignment must be from corridor file.

• Edit handlers / manipulators only available in active file. – Activate– Exchange


3/28/2014

12

Reference FilesReference Files

Best Practice Recommendations:– Separate geometry for working with large work teams.– Separate corridors into areas of interest.– Use an all_geometry.dgn, all_corridor.dgn, etc. so users don’t have

to search to find data. – Be “Nesting” aware to capture wanted data, but not duplicates of

data. – Attach by relative paths so folders can be moved.


– Careful when detaching as you may leave orphan objects.

W k dW k dWorkspaces and Workspaces and ResourcesResources


3/28/2014

13

Delivered Civil WorkspacesDelivered Civil Workspaces

• Bentley-Civil-Imperial

• Bentley-Civil-Metric• Bentley-Civil-Metric


BentleyBentley--CivilCivil--ImperialImperial• Power Geopak

– C:\ProgramData\Bentley\PowerGEOPAK V8i (SELECTseries3)\WorkSpace\Projects\Examples\Bentley-Civil-Imperial

• MicroStation– C:\ProgramData\Bentley\MicroStation V8i

(SELECTseries)\WorkSpace\Projects\Examples\Bentley-Civil-Imperial

• Common Standards


– C:\ProgramData\Bentley\Civil\Standards\8.11.9\en

3/28/2014

14

Civil GeometryCivil Geometry

GPKGPK

ALGALG


FILFIL

Importing GeometryImporting Geometry

Limitations:

• Can’t import extremely complex geometry• Can t import extremely complex geometry.

• Complex geometry may not be “ruled.”

• Can’t bring in profile only (must be associated with a chain).

• Can only import within a product.


3/28/2014

15

Exporting GeometryExporting Geometry

• Manual or automatic

• Review what is exported• Review what is exported– Centerlines and Baselines– Right of Way when needed for plats, parcels and other geometry

layouts– Survey data needed for the GEOPAK export to drainage application– Data needed for staking when using GEOPAK as the native

application


application.

• Keep in mind limitations in native products, i.e., naming of elements.

ADVANTAGES DISADVANTAGESAuto Export No additional steps are

required.Process is fairly invisible to the user.Supports horizontal station

Inexperienced user create unintended changes in the native database. Not design file specific. Elementsin copied files react to Supports horizontal station

annotation.Always “in sync”

ppersistence.

Manual Export

Choose exactly which elements are exported Does not depend on feature

Requires extra step to export.Snap-shot in time; subsequent h i dditi l


not depend on feature setting.

changes require an additional export.Auto annotation is not supported.

3/28/2014

16

Native Databases:Native Databases:

XINXIN

DDB, SMDDDB, SMD


PSSPSS

Best Practice Recommendations: • Exercise patience as there’s more work to come

Native DatabasesNative Databases

• Exercise patience, as there s more work to come…• Link to your native database, watching for duplicate

names.• Augment as needed for new features or items that are

currently not supported within the databases.


• Start with a few element templates and expand as needed during test / pre-deployment.

3/28/2014

17

+ More capability than styles (i.e., material assignments)+ Access to text styles

Element TemplatesElement Templates

+ Access to text styles

- Can’t handle stationing and other specializedannotation

- Can’t handle quantities / pay item data


Can t handle quantities / pay item data

Best PracticeRecommendations:

Create Element TemplatesCreate Element Templates


3/28/2014

18

Best Practices Recommendations:Do NOT delete feature definitions and start over.

Changes in Native DatabasesChanges in Native Databases

Do NOT delete feature definitions and start over.Just link again• New items are added.• Existing items remain intact. • Changes in symbology are updated


• Changes in symbology are updated.Users’ existing element need to be edited to force symbology redraw.

Seed File Suggested Considerations…• Set DGN File Civil Settings appropriately

Seed FilesSeed Files

• Set Default Drawing Scale• Set default Snap Divisor to 1• Turn off clip volume for all views in view attributes• Delete unused fonts in keyin field• Set default text style• Attach default cell library


ttac de au t ce b a y• GEOPAK must change Civil Settings Station Equation to “By

Region” for auto annotate to function properly• Turn off Camera View Attribute in 3D seed files• Set GCS

3/28/2014

19

Historically, GCS were infrequently used, however, there are now numerous advantages to setting the GCS in your DGN fil

GEOGRAPHIC COORDINATE SYSTEMS (GCS)GEOGRAPHIC COORDINATE SYSTEMS (GCS)

DGN files:

• DGN files based on different GCS (where the GCS is defined within the file) can be referenced and re-projected on-the-fly so the data is in sync.

• Interface with Google Earth and other widely available data regardless of the source data GCS.MicroStation interface with GPS devices


• MicroStation interface with GPS devices.• Created objects without additional steps needed for transformation /

reprojection.

• The best practice for setting GCS in seed files is based on the number of GCS systems used by your

i ti If th i ti tili i l t

GEOGRAPHIC COORDINATE SYSTEMS (GCS)GEOGRAPHIC COORDINATE SYSTEMS (GCS)

organization. If the organization utilizes a single system, then it should be set in the seed file.

• If your organization utilizes several systems, you would have to set up one for each system thereby increasing the number of seed files. In this case you may not want to set the GCS


3/28/2014

20

Design Standards Design Standards -- Review horizontal and vertical Review horizontal and vertical Design Standards Design Standards –– validate local standardsvalidate local standards


• Material Assignments

Material AssignmentsMaterial Assignments

– Can be set per DGN Level• One material per level

– Can be set per Element Template• Allows for different materials on same level (i.e. Level Name =

Pavement)


– Important for adequate 3D Model visualization

3/28/2014

21

Material AssignmentsMaterial Assignments

• Material Assignments using Element Templates

“Best Practice”Best Practice


User Preferences Settings LocationUser Preferences Settings Location

• Do not attempt to locate your SS2 version of your MicroStation UPF (User Preference File) to the

f ld SS3 UPF l ti Thi illsame folder as your SS3 UPF location. This will cause UPF corruption when switching between versions.


3/28/2014

22

© 2014 Bentley Systems, Incorporated

OpenRoads Best PracticesOpenRoads Best PracticesBob Rolle, Civil Application Engineer

Documents

Best Practices - CAD