1. Using OpenRoads Effectively
Marc Bachand P.E.

2. Using OpenRoads Effectively
This course is intended for OpenRoads users looking to gain further insight on how to set up and manage a project in Bentley’s OpenRoads environment.

3. Using OpenRoads Effectively
Topics Covered
File management and naming
Importing ALG File for Alignments
Managing model control geometry
Superelevation
Corridors
End Conditions

4. Using OpenRoads Effectively
Effective OpenRoads Use = Effective File Management
OpenRoads files are Microstation files
OpenRoads files contain model information not just graphics
Attaching a file as a reference allows access to the data contained within the reference file.
The more model information you add to a file the “heavier” it gets. Adding all model information to a single file, while possible, is not an effective way to manage OpenRoads data
Slower file load times
Slower processing times
Unexpected modeling results
Potential for complete data loss due to file corruption

5. Using OpenRoads Effectively
Effective OpenRoads Use = Effective File Management (cont.)
Parsons “Lean and Mean” file management approach to OpenRoads data
Model information is separated into individual files, grouped by model category type
i.e. Alignments, Corridors, Superelevation, End Conditions, etc.
Model file data is accessed using reference files
The amount of data broken in to separate files is user dependent.
ALWAYS CREATE NEW OPENROADS FILES FROM SEED FILE. NEVER USE “SAVE AS”.
Be careful of Live Nesting; only use it when necessary.

6. Using OpenRoads Effectively
OpenRoads File Management at Parsons
File Naming
* File type in not all inclusive. Additional file types may be required to complete modeling.
Example
123456_2_COR_EBWB.dgn = Segment 2 Corridor file for EB to WB ramp
123456_3_GEO_ALG.dgn = Segment 3 ALG geometry (more to come on this later on)
Project Description
Segment ID
Inroads File Type*
Description
123456
ITL
Template 1A
COR
Corridor
Corridor Name 1B
GEO
Geometry 2
BRD
Structure
Bridge ID 3
INT
Intersection
Intersecting Streets 4A
SUP
Superelevation 4B
CTN
Container 5

7. Using OpenRoads Effectively
Model Geometry
ALG Alignments
Super elevation
Corridors
(Backbones)
Cor A
Corridor Container
Cor B
Cor C
For Corridor Clipping
End Conditions
EC A
End Condition Container
EC B
EC C
Bridges
Bridge 1
Bridge Container
Bridge 2
OpenRoads Model
Live Nesting Depth = 2

8. Using OpenRoads Effectively
Implementing OpenRoads
ALG Alignments
The ALG file from native Inroads SS2 is maintained as the management tool for alignment geometry (Horizontal and Vertical control geometry and sometimes model geometry)
Benefits of maintaining an ALG file as source geometry
Requires no additional training for users
Supports copying of alignments, both horizontal and vertical
ALG is required for plan production even if OpenRoads geometry is fully implemented
ALG alignments are imported in to the DGN file.
As changes are made to the alignments in the ALG file they are reimported, updating the information previously imported.

9. Using OpenRoads Effectively
Import alignments from ALG file
Open the ALG file using Inroads Explorer. Then select this button.
Import Inroads from Memory
Alignments that have not been imported previously are NOT checked here.
No need for Civil Rules so uncheck this box when importing

10. Using OpenRoads Effectively
Alignments that are checked here have been imported previously and will update when imported again.
No need for Civil Rules so uncheck this box when importing

11. Using OpenRoads Effectively
ALG Alignments (cont.)
Do’s and Don’ts when working with the ALG Model
DO NOT delete the imported graphics from previous ALG imports. Corridors are tied to the GUID of these particular graphical elements. Deleting them will render you corridors useless.
Importing a previously imported alignment will simply modify the graphics
You MUST maintain the original name of the internal ALG file and the imported alignments for proper updating to occur.
Graphics are imported on the active Microstation symbology. You can change the symbology after the fact or assign an OpenRoads feature definition.
Do not assign a feature definition that allows auto-export of the ALG graphics.

12. Using OpenRoads Effectively
Model Control Geometry
Geometry used for model manipulation
Edge of pavement, shoulder, turn lane transitions, of any other geometry required to properly model corridors.
The ALG graphics are referenced to this file
Geometry in this file can be developed using SS4 ruled geometry or imported and managed in an ALG file
Ruled Geometry
Updates as changes are made to control geometry
Better suited for new construction work or when geometry has some definable relationship to control geometry, i.e consistent offsets, tapers, etc.

13. Using OpenRoads Effectively
Model Control Geometry (cont.)
ALG Management
User manages model geometry in ALG file similar to SS2 workflows
Changes must be reimported similar to alignment geometry. Must follow the same Do’s and Don’ts of alignment geometry importing
Better suited for rehabilitation projects where proposed geometry is irregular, i.e. matching existing EOPs, sawcut lines, etc.
A combination of both approaches is also possible

14. Using OpenRoads Effectively
Superelevation
Developed in a separate file with ALG model referenced
Superelevation sections for each corridor are developed in this file.
Create unique levels to help manage the display of multiple superelevation sections. For example:
Levels based on type of roadway i.e. freeway, ramp, arterials
Levels for each corridor/alignment

15. Using OpenRoads Effectively
Superelevation (cont.)
Standards file for calculations?
Allows quick calculation of maximum “e” and transition rates
Changes to alignment geometry will propagate through and super sections will update automatically
If manual edits to super stations have been made these changes will be lost due to automatic updates
Tip: Set minimum tangent length between curves to 100,000 so that one section is developed over entire alignment length

16. Using OpenRoads Effectively
Corridors
One corridor per DGN file is the preferred approach but not required.
Alignments and Model Control Geometry are referenced to corridor files as well as any CAD design files (i.e. proposed work or base mapping files)
Attach superelevation file as required
Corridors are pulled together using a container file.
Can be backbone only or backbone and end conditions (user choice).

17. Using OpenRoads Effectively
End Conditions
End conditions can be developed as separate files or within the corridor files.
End conditions can be developed as linear templates or corridors.
Current practice is using a linear template but this has downfalls (see below).
The end condition template in the ITL file is developed in one direction (i.e. left to right). Upon placement the user decides what direction the template should be applied.
Linear templates can be applied on any geometry, within the 2d or 3d model.

18. Using OpenRoads Effectively
End Conditions (cont.)
Benefits of Linear Templates:
Only one template is developed and maintained. The user decides whether to apply the template to the left or right side of the geometry
Greater control on the ranges where particular end condition solutions are applied. Multiple liner templates can be developed and applied over different station ranges of the corridor.
Drawbacks of Linear Templates:
Cannot specify key stations. Template drop intervals are based on linear stroking definition of origin element.
Cannot include critical stations like external control points
You might not get a template drop at locations where you would ideally want one.

19. Using OpenRoads Effectively
OpenRoads in Use

20. Using OpenRoads Effectively

21. Using OpenRoads Effectively
Level 1
Level 2
Level 3
Level 4
Level 5