Scribd
Upload
91 views7 pages

OpenRoads Notes

Uploaded by

V
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
91 views7 pages

OpenRoads Notes

Uploaded by

V
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

FDOT Plans Development Workflow – Ch 2 & 3 Key Sheets & Typical

Section Sheets - https://www.youtube.com/watch?v=PmcZIOg8HUc 


 2.1 Creating the Key Sheet 
 2.4 Placing the Specific Standards Note  
 2.6 Placing the Project Location Labels  
 2.5 Placing the Range and Township Map Label  
 2.2 Creating and Placing the Key Sheet Index  
 2.3 Creating and Placing the Components of Plan Set List  
 Create Key Sheet without a Map 
 2.8 Printing the Key Sheet 
 4.2 Creating the Roadway Typical Section Sheet  
  
FDOT Plans Development Workflow – Ch 4 & 5 Plan-Profile Sheets,
Project Notes, & Project Layout - https://www.youtube.com/watch?
v=VuUQXqKdi3M&spfreload=5 
 5.1 Exporting the Profile Information to the GPK  
 5.2 Creating the Profile DGN File and Laying out the Profile  
 5.3 Creating the Clip DGN File and Laying out the Clip Borders  
 5.4 Generating the Plan Profile Sheets 
 5.5 Clipping Plan Sheets Using Live Nesting  
 6.1 Creating the Project Note Sheet 
 6.2 Creating the Project Layout Sheet 
  
FDOT Plans Development Workflow – Ch 6 Cross Sections & Sheets
- https://www.youtube.com/watch?v=vSdKNRlT6NU 
 7.1 Create Existing Cross Sections 
 7.5 Annotate Cross Sections 
 7.2 Place Ancillary Features 
 7.3 Borehole Navigator 
 7.8 Calculate Earthwork and Create a Final Cross Section Model  
 7.7 Create Cross Section Sheets 
 Drainage Structures Sheets 
  
 
 
  
FDOT Plans Development Workflow – Ch 7, 8 & 9 SWPPP Plans, Traffic
Control Plans & Utility Adjustments - https://www.youtube.com/watch?
v=fohejQX9gwE 
 8.1 Creating the SWPPP Notes Sheet 
 8.2 Placing a Raster Map  
 9.1 Loading the Traffic Control Menu and Features  
 9.4 Importing the Traffic Control Alignment   
 9.5 Creating the Temporary Roadway 
 9.6 Delineating the Temporary Pavement and Work Zones  
 9.9 Layout maintenance of Traffic Sheets 
 10.1 Loading the Utility Features 
 10.4 Laying Out Proposed Utilities using SUE Features  
 10.6 Labeling Utility Adjustment Plans 
 10.5 Creating Clip Boundaries for Utility Sheets  
 

 Template Lesson Learned:

Sent via email July 19, 2017: 


 
The way we model roads for our projects is still a work in progress. We learn new things on each job and
all of us probably do things differently.  Please feel free to offer opinions on those types of topics.  Some
of these things, Brad, Richard and I have been talking about for a while, and we don’t always agree or
have changed our minds about them. 
  
Template Naming is one example. When I started using OpenRoads someone in our Atlanta office
suggested we name templates by station range, so on SR 9B we started that way. This became
cumbersome when we wanted to insert a different template in the middle, because it would mean we
had to rename three different templates with new station ranges – the new one and the ones on either
side of it.  Then you would have to reload the newly named template into the corridor.  Working on FCX
some templates were named by the corridor name – FCX1_1, FCX!_2, etc. -  but there was nothing to
differentiate where it was or what was happening in the template, so we started naming them by what
they were – MSE_WALL, or DITCH_Section, etc.  We did not go back and rename every template at that
stage, but as we made new ones we tried to give them names that would help us to know what they
were used for.  This may change, but we should try to be consistent across a job as we start new
projects.  This will help as new people start working on the project. 
  
Related to the template naming is issues with Revising Templates.  On one model I was looking at
recently a template was updated due to a design change.  This will happen often on some jobs.  The
problem was that the template that was revised, was being used in two other areas of the corridor and
that design change only referred to one station range, not all three.  So, when someone went in later to
cut the cross sections a very large section was now all incorrect.  If you are revising a template in a
corridor .itl file you MUST make sure that template is not already being used somewhere else.  The
safest thing to do is to copy the original template and rename it – to include the design change in the
title perhaps – and use the new template for the area with the design change.   

StormCAD:

Video Links 
 
 Bentley Learn 
Drainage Design Using StormCad for OpenRoads - In this video series, we will explore the drainage design
capabilities of StormCAD for OpenRoads. We will cover layout of drainage networks, hydraulic analysis of surface
inlets and underground piping networks, and see how the use of scenarios can help you explore options for your
drainage design. We will also explore some advanced drainage capabilities 
http://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=106800# 
 
 
 Bentley Communities 
Subsurface Utilities (SUE and SUDA) Video Clips, TechNotes & FAQs 
 
https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/12600.
subsurface-utilities-sue-and-suda-video-clips-technotes-faqs 

Trouble Shooting your Model:

Parent-Child Relationships:

Many of the templates that the FDOT created already have parent/child relationships.  An example may
be a template that looks for guardrail and only draws it if it finds guardrail.  Then the miscellaneous
pavement and anything else associated with the guardrail may be set up as a child of the parent
guardrail.  If the guardrail, or parent, doesn’t show up, then anything that is a child of it will not either. 
  
I had a section of a model where the shoulder base was not showing up, but I could see it in the
template.  When I opened up the component for the shoulder base in the template I could see that it
had a parent relationship. 
  
                         
I hadn’t added this, but it was still there from the original FDOT template I used to make this one.  Once I
removed the parent component, the base always showed up.  In this section it was not showing up
because the unpaved shoulder was below the existing ground, so the RT_CLEARZONE component (the
brown line in this picture) was not solving.  So, if the parent isn’t plotted, the child isn’t either. 
  
Parent/Child relationships can be very helpful when you have a template that has a lot of choices, but
can also be the reason something is not showing up correctly.  You can find all of these relationships
quickly by going to the Active Template tab of the template editor. It is in the lower left.                  
     
      

 
  
In the circled section you can see that two components are children of the component RT_CLEARZONE. 
To remove them you can right click on them in the list and select edit and it will let you remove the
parent component.  You can also double click on the component itself in the template to edit it. 
 

Sent via email July 28, 2017 


Procedures:
Template:

Template Naming   
When I started using OpenRoads someone in our Atlanta office suggested we name templates by station
range, so on SR 9B we started that way. This became cumbersome when we wanted to insert a different
template in the middle, because it would mean we had to rename three different templates with new
station ranges – the new one and the ones on either side of it.  Then you would have to reload the newly
named template into the corridor.  Working on FCX some templates were named by the corridor name –
FCX1_1, FCX1_2, etc. -  but there was nothing to differentiate where it was or what was happening in
the template, so we started naming them by what they were – MSE_WALL, or DITCH_Section, etc.  We
did not go back and rename every template at that stage, but as we made new ones we tried to give
them names that would help us to know what they were used for.  This may change, but we should try
to be consistent across a job as we start new projects.  This will help as new people start working on the
project. 
  
Related to the template naming is issues with Revising Templates.  On one model I was looking at
recently a template was updated due to a design change.  This will happen often on some jobs.  The
problem was that the template that was revised, was being used in two other areas of the corridor and
that design change only referred to one station range, not all three.  So, when someone went in later to
cut the cross sections a very large section was now all incorrect.  If you are revising a template in a
corridor .itl file you MUST make sure that template is not already being used somewhere else.  The
safest thing to do is to copy the original template and rename it – to include the design change in the
title perhaps – and use the new template for the area with the design change.   
 
 
 
Template Drop Descriptions 
 
If you have not already done so, please start using the description field in your template drops.  This will
help someone who is looking at the model, or who may be checking it, to know what is happening in
each template drop.  If your project  
  
Here is an example: 
  
This template drop is of Typical Section 1 – if you are working from a set of plans with numbered typical
sections this would definitely help someone who is reviewing the model, it is the westbound road (TS1
includes WB and EB, but our model is split up) and there is an MSE wall on the outside of the section.  
  
  
If you forget to type in the description you can go into the Corridor Objects and add it there.  
  

You might also like