Post on 19-Jun-2020
transcript
Model Based Design and Construction (MBDC) Guidelines
June 2019
For Digital Delivery
Model Based Design and Construction (MBDC) Guidelines June 2019
June 2019
UDOT Model Based Design and
Construction (MBDC) Guidelines
for Digital Delivery
Model Based Design and Construction (MBDC) Guidelines June 2019
TOC-2 Table of Contents
TABLE OF CONTENTS
CHAPTER 1: General.............................................................................................................1-1
1.1 General .............................................................................................................1-1
1.1.1 MBDC Coordination and Responsibilities ........................................1-1
1.2 Definitions and Acronyms .................................................................................1-1
1.2.1 Definitions ........................................................................................1-1 1.2.2 Acronyms ........................................................................................1-5
CHAPTER 2: Project Management ........................................................................................2-1
2.1 When to Use MBDC ..........................................................................................2-1
2.1.1 Project Management Considerations ...............................................2-1
CHAPTER 3: Workspace............ ............................................................................................3-1
3.1 General .............................................................................................................3-1 3.2 Workspace Setup..............................................................................................3-1
3.2.1 Workspace Customization ...............................................................3-1
CHAPTER 4: Survey...............................................................................................................4-1
4.1 General .............................................................................................................4-1 4.2 Use Survey OpenRoads workspace..................................................................4-1
4.2.1 Meet Geomatics Manual Requirements – Detail and Accuracy ........4-1 4.2.2 Written Report .................................................................................4-2 4.2.3 Topo Confidence Report (Excel Document) .....................................4-2
CHAPTER 5: Design...............................................................................................................5-1
5.1 Deliverables ......................................................................................................5-1
5.1.1 3D vs. 2D Design .............................................................................5-1 5.1.2 Model Authoring ..............................................................................5-1 5.1.3 Design Team ...................................................................................5-2 5.1.4 3D Design Information .....................................................................5-5 5.1.5 2D Design Information .....................................................................5-8 5.1.6 Annotation and Non-Graphic Data ...................................................5-8 5.1.7 Delivery Documentation ...................................................................5-9 5.1.8 Files Advertised as Legal Document vs. For Information Only .........5-9 5.1.9 Files Advertised as Legal Document ................................................5-9 5.1.10 Files Advertised as For Information Only ....................................... 5-10 5.1.11 Deliverable File and Model Naming Convention Spreadsheet ....... 5-10
5.2 Roadway Modeling Considerations ................................................................. 5-10
Model Based Design and Construction (MBDC) Guidelines June 2019
TOC-3 Table of Contents
5.2.1 InRoads vs. OpenRoads ................................................................ 5-11 5.2.2 Modeling Basics ............................................................................ 5-11 5.2.3 Templates – Feature Definitions .................................................... 5-12 5.2.4 Model Detail Areas and Considerations ......................................... 5-14 5.2.5 Template Principles and Practices ................................................. 5-15 5.2.6 Surfaces and Components Delivery Considerations ...................... 5-17 5.2.7 Surface Templates ........................................................................ 5-17
5.3 Structure Modeling Considerations ................................................................. 5-18
5.3.1 3D Design Information ................................................................... 5-18 5.3.2 2D Design Detail Information ......................................................... 5-18 5.3.3 Additional Supporting 2D Documentation ...................................... 5-19 5.3.4 Files Advertised as Legal Document .............................................. 5-19 5.3.5 Files Advertised as For Information Only ....................................... 5-20 5.3.6 Model Relevant Information ........................................................... 5-20 5.3.7 File Naming Convention ................................................................ 5-21 5.3.8 OpenBridge Modeler...................................................................... 5-21 5.3.9 ProStructures................................................................................. 5-21 5.3.10 OBM Libraries................................................................................ 5-21 5.3.11 Special Considerations .................................................................. 5-22 5.3.12 Structures Model Design QA/QC Procedures ................................ 5-24
5.4 Subsurface Utility modeling Considerations .................................................... 5-25
5.4.1 Subsurface Utility Modeling ........................................................... 5-25 5.4.2 ORD Issues ................................................................................... 5-30
CHAPTER 6: QC/QA and Milestone Design Reviews ..........................................................6-1
6.1 MBDC QC/QA Introduction ...............................................................................6-1 6.2 Purpose ............................................................................................................6-1
6.2.1 Alternative QC/QA Procedure Form .................................................6-1
6.3 QC Documentation ...........................................................................................6-1
6.3.1 QC/QA Checklists ............................................................................6-1 6.3.2 Model QC Expectations ...................................................................6-1 6.3.3 DGN Model QC ...............................................................................6-2
6.4 Roadway Model QC Notes ................................................................................6-3 6.5 Milestone Reviews ............................................................................................6-4
CHAPTER 7: Appendix............... ............................................................................................7-1
7.1 DGN File and Models Naming Convention ........................................................7-1 7.2 Publishing i-models Resources .........................................................................7-2 7.3 Publishing GIS Collector Files ...........................................................................7-5 7.4 Publishing Model Based Design Files to Project Explorer .................................7-5
7.4.1 Steps to be Completed by the Designer...........................................7-5 7.4.2 Steps to be Completed by Construction Advertising ...................... 7-19 7.4.3 Saved Searches Definitions ........................................................... 7-20
Model Based Design and Construction (MBDC) Guidelines June 2019
TOC-4 Table of Contents
7.4.4 ProjectWise Advertising Naming Convention Resources ............... 7-21
7.5 Model Review Training Documentation ........................................................... 7-21
7.5.1 ProjectWise ................................................................................... 7-22 7.5.2 Bentley CONNECTED Project ....................................................... 7-22 7.5.3 Bluebeam Studio ........................................................................... 7-22
7.6 Examples of Review items and checklist ......................................................... 7-25
7.6.1 Roadway ....................................................................................... 7-25 7.6.2 Roadway Removals ....................................................................... 7-26 7.6.3 Signing and Striping ...................................................................... 7-26 7.6.4 Drainage ........................................................................................ 7-26 7.6.5 Utilities ........................................................................................... 7-27 7.6.6 Structures ...................................................................................... 7-27
TABLE OF FIGURES
Figure 5.1 – Model Authoring Workflow................................................................................... 5-4
Figure 5.2 – Template Example ............................................................................................ 5-12
Figure 5.3 – Feature Definition Library Example ................................................................... 5-13
Figure 5.4 – Applying Surface Templates .............................................................................. 5-18
Figure 5.5 – OBM Template Management Tab ..................................................................... 5-22
Figure 5.6 – ORD Subsurface Utilities Workflow ................................................................... 5-26
Figure 5.7 – Activate Hydraulic Software in ORD .................................................................. 5-26
Figure 5.8 – Layout Subsurface Utility Features .................................................................... 5-26
Figure 5.9 – Create Utility Model ........................................................................................... 5-27
Figure 5.10 – Workspace Error ............................................................................................. 5-27
Figure 5.11 – OpenRoads Standards Tab ............................................................................. 5-28
Figure 5.12 – Subsurface Utilities Model Tab in Explorer ...................................................... 5-29
Figure 5.13 – Synchronize Drawing to Subsurface Utilities Database in ORD ....................... 5-30
Figure 5.14 – ORD Subsurface Utilities vs. Storm and Sanitary Advantages and Disadvantages
............................................................................................................................................. 5-31
Figure 6.1 – Check Print and QC Legend in DGN ................................................................... 6-2
Figure 6.2 – Drainage QC DGN, Geometry Review ................................................................ 6-2
Model Based Design and Construction (MBDC) Guidelines June 2019
TOC-5 Table of Contents
Figure 6.3 – Drainage Corrected DGN, Geometry Review ...................................................... 6-3
Figure 6.4 – Milestone Review Process Diagram .................................................................... 6-5
Figure 7.1 – Publishing for i-models Location .......................................................................... 7-3
Figure 7.2 – Access the Publishing Dialog .............................................................................. 7-4
Figure 7.3 – Publishing i-models Dialog .................................................................................. 7-4
Figure 7.4 – 3D Model Based Design Review ....................................................................... 7-24
Model Based Design and Construction (MBDC) Guidelines June 2019
1-1 General
CHAPTER 1
General
1.1 GENERAL
Digital Delivery with Model Based Design and Construction (MBDC) is the use and transfer of
digital data in design, construction, and asset management. Digital Delivery with MBDC is not
solely intended to eliminate plan sheets but rather deliver data in more directly consumable
formats for project stakeholders. The intention of this MBDC Guidelines document is to provide
guidance to project teams for the execution of MBDC on Digital Delivery projects.
Current progress, lessons learned, and best practices to date are captured within this
document, though we acknowledge that technology is constantly advancing.
Contact Utah Department of Transportation (UDOT) Central Preconstruction Digital Delivery
personnel for current MBDC efforts to ensure the latest information, tools, and software are
incorporated in the project.
1.1.1 MBDC Coordination and Responsibilities
Digital Delivery with MBDC projects comes with many new deliverable requirements and as a
consequence there are new or expanded responsibilities that must be considered. Engineers
and designers will be creating more detailed and complete models as compared to projects that
had paper or PDF plans. Reviewers will need to not only determine if the design intent meets
the standards, but also confirm that the model geometries and their associated data attributes
accurately and completely match the design intent. Contractors will have to embrace new
mobile applications to use the models in the field in lieu of paper or PDF plans and they may
need to adjust their workflows for leveraging model data inside their specialized software. Lastly
asset management and maintenance workflows may need to evolve to embrace model delivery.
Given these new roles and the nascent nature of the guidelines it may become necessary to
reach out to agency staff for clarification or guidance when it appears that a variation from these
guidelines may be necessary. UDOT has established the following email for project teams to
email all inquiries to: udotdigitaldelivery@utah.gov
1.2 DEFINITIONS AND ACRONYMS
1.2.1 Definitions
2D: Data lacking a value or property representing elevation. 2D geometry is represented at a
single elevation value—often zero. In a 2D-only work environment, the elevation coordinates are
omitted from being reported since all values are the same. On a Cartesian plane, the X and Y
values correspond to the easting and northing (E = X; N = Y) of the survey coordinates system.
2D coordinate systems are graphically represented as a plane.
3D: Data that includes elevation values or is represented in 3D space across a range of
elevation values. 3D coordinate systems are represented as a cube. Typically, in civil
Model Based Design and Construction (MBDC) Guidelines June 2019
1-2 General
engineering, the elevation data is reported as a Z coordinate. The survey coordinate system
equates as follows: X = easting, Y = northing, and Z = elevation.
3D Model: In this document, 3D models refer to the 3D geometrics created that match the
design intent. This is an inclusive term that can mean 2D and 3D linear geometry, mesh, and
solid objects that are stored in the model space and manipulated or authored by CAD software
and their companion civil vertical applications (InRoads, OpenRoads, OpenBridge, etc.).
Automated Machine Guidance (AMG): AMG is a broad spectrum of hardware and software
technologies that enable heavy equipment and other robotic tools to operate with minimal or no
human control. The design intent is represented with 3D geometry published into an instruction
set that activates and manipulates the controls of the machine, such that its operation creates
an output precisely matching the design in the real world. This equipment allows for safer,
faster, and more precise construction and is being implemented on all manner of construction
equipment.
Bentley CONNECTED Project: Projects configured on the Bentley CONNECT portal. This portal
is a cloud-based suite of tools for integrating teams, managing deliverables, publishing content,
resolving issues, collecting field data, sharing files, and driving project performance.
Bluebeam Studio: A third-party collaboration platform that is included with a Bluebeam Revu
license. Bluebeam Studio connects team members on construction projects, giving them the
ability to markup and review documents in real-time. This is bundled with the Bluebeam PDF file
authoring and view suite of tools.
Data Model: The organizational structure, outline, and approach to defining and applying data
attributes to the 3D model. In this document, the term is analogous to a database schema.
The Feature Manipulation Engine (FME): A platform that streamlines the translation of spatial
data between geometric and digital formats.
Federated Model: A collective BIM model that is compiled by importing different models together
into one model. It is intended especially for use with geographic information system (GIS),
computer-aided design (CAD) and raster graphics software.
Infrastructure Consensus Model (ICM): A proprietary Bentley file format created to improve the
downstream sharing of design data with surveyors and contractors. This format is read-only and
allows for a single packaging of data that can be more easily imported into industry standard
applications like Trimble Business Center (TBC) or Topcon MAGNET. It should be noted that
this file format can be created from the Bentley Select Series 4 (SS4) application version and
has been deprecated and removed as an export option in the Bentley CONNECT products.
i-model: A generic term inclusive of a range of Bentley file formats that share some common
traits but are customized to specific usage cases. i-models include the following formats:
• .icm – See ICM definition
• .dgn – Can be viewed in MicroStation and Navigator Desktop
• .imodel – SQL-Lite version of the .dgn format, used inside the Bentley mobile apps
• .iBim – The latest evolution of the i-model formats, this native format to the new Bentley
Navigator CONNECT product replaces .icm and .imodel formats completely
Model Based Design and Construction (MBDC) Guidelines June 2019
1-3 General
These file formats have some notable commonalties: they are all read-only and require some
publishing effort out of MicroStation or other authoring products Bentley supports (e.g., Revit or
Navigator Desktop).
Item Types: A technology introduced in the MicroStation CONNECT edition that allows a
standard library of database attributes to be organized and then applied to the model geometry.
These item types can be created, ad hoc in the .dgn or created in advance and deployed as a
part of the workspace as a DGN library file (.dgnlib). These attributes can be authored and
applied in the CONNECT edition or legacy V8i edition with the use of a custom Visual Basic for
Applications (VBA) recently written by Bentley (i.e. ItemTypes+). This VBA is available on
ProjectWise. There are limits to which property values can be edited in the V8i version, but all
attached attributes will publish out of V8i to the various i-model formats. It should be further
noted that for projects using OpenRoads Designer there is a technology preview available
therein called “Asset Manager” which is poised to replace ItemTypes+ in the near term.
Links: Hyperlinks that can be applied to geometry to allow a user to connect to and access a
wide range of external files and formats. These links are very similar to hyperlinks in the
Microsoft Office products and can be used to link to web addresses, folders, ProjectWise files
and folders, PDF and image files, Microsoft Office files, model spaces inside .dgn files, and a
myriad of other locations.
LOD: This abbreviation can be used in many contexts including but not limited to:
Level of Detail – With respect to 3D modeling, this means to what level of totality and
precision the 3D geometry matches the real world or design intent. For example,
modeling the outside areas or physicality of a concrete structure is a low level of detail; a
model that includes the outside structure, internal rebar, and associated accouterment
would be a high level of detail.
Level of Development – Functionally, this term means the same thing as Level of
Detail, but is a more common way of expressing LOD when discussing BIM projects and
process as a whole. Level of Detail more often occurs when discussing a singular item
or model component. Regardless, the terms can be used, and are used,
interchangeably.
Limit of Deflection – Also known as Allowable Deflection, this is an expression of the
acceptable sag on bend in a structural member under a specific load. This is generally
expressed as a fraction of the span in inches.
In this document we describe which LOD context is intended.
MicroStation CONNECT Edition: The next evolution of the Bentley MicroStation CAD platform.
Unlike previous versions, this release is a true 64-bit application. This edition sports a new
ribbon-style interface and is better able to leverage cloud services. Moving forward,
MicroStation CONNECT becomes the base CAD platform for many vertical products, including
the single-install OpenRoads Designer and OpenBridge Designer.
Model: A term that is used interchangeably for a CAD based software output that defines how a
project will be constructed. It is important to note that preconstruction models developed for
Model Based Design and Construction (MBDC) Guidelines June 2019
1-4 General
owners e.g. departments of transportation (DOT), municipalities, commercial building owners,
etc. are not on the same platform as construction/contractor models. DOT models are typically
produced using Autodesk or Bentley products while contractor models are typically produced
using Agtek, Leica, TopCon, or Trimble Business Center. While the term Model may be used in
this document, it may or may not reconcile whether it is the owner’s model or the construction
model.
Model Space: File-based containers, including .dgn or .dwg files (MicroStation and AutoCAD
native formats, respectively), that store 2D or 3D data. MicroStation has “models” that
correspond to the AutoCAD concepts of a model space versus a paper space. In this document,
model space is used as a generic term for any file-based container that can store any 2D or 3D
geometry.
Native Model: A generic term to describe the file formats and geometries that represent CAD
content and are widespread in the application being referenced.
OpenBridge Modeler (OBM): New software published by Bentley to allow for accurate modeling
of 3D bridge structures. OpenBridge operates as a standalone program allowing use of its own
workspace variables for templates and additional information. Models can be output into design
programs such as LEAP to design specific elements of the structure and then brought back to
OBM to be displayed correctly.
OpenRoads Designer (ORD): A new core civil design toolset by Bentley that is available inside
the legacy Geopak, InRoads, and MX software packages. OpenRoads is an entirely new set of
design tools that is slated to replace the legacy tools in a future single version, simply called
OpenRoads Designer. OpenRoads Designer is a single-install application that includes the
OpenRoads civil tools inside the CONNECT edition of MicroStation. OpenRoads heavily
leverages the very mature InRoads technology while moving all core data out of separate files
and into the MicroStation CAD platform directly.
OpenRoads Navigator (ORN): A Bentley mobile application that allows for cross-platform (iOS,
Android, Windows) leveraging of i-model content. This mobile application is relatively new, with
new functions and features rapidly being added to help deliver design content to the field in a
manner that is accessible and useful enough to replace the need for traditional paper or PDF
plans. In the first quarter of 2019, this product is rebranded as Bentley Navigator.
ProjectWise: A Bentley server-side file management application that integrates into all Bentley
applications and allows users to connect to and manage files across projects and organizations
with a desktop application specific to that task, but not connected to any vertical (i.e. civil,
mechanical, geotechnical, geospatial, etc.) application.
ProStructures: Bentley’s detailing modeling software used to define additional steel and
concrete elements within a structure.
VBA: A visual basic program written or designed to run inside another program.
Model Based Design and Construction (MBDC) Guidelines June 2019
1-5 General
1.2.2 Acronyms
2D, 3D, 4D Two-, Three-, and Four-Dimensional
AMG Automated Machine Guidance
ATMS Advanced Traffic Management Systems
BIM Building Information Model
CAD/CADD Computer-Aided Drafting and Design
CM/GC Construction Manager/General Contractor
D/B/B Design/Bid/Build
DOT Department of Transportation
FHWA Federal Highway Administration
FIO For Information Only
GIS Geographic Information Systems
GPS Global Positioning System
ICM Integrated Consensus Model
IDC Intelligent Design and Construction (Deprecated Term)
MALD Model as the Legal Document
MBDC Model Based Design and Construction
MOT Maintenance of Traffic
NSRS National Spatial Reference System
NTP Notice to Proceed
OBM OpenBridge Modeler (Bentley)
ORD OpenRoads Designer (Bentley)
ORN OpenRoads Navigator (Bentley)
PDBS Project Development Business System
PDF Portable Document Format
PIH Plan-In-Hand
QA/QC Quality Assurance/Quality Control
SHP Environmental Systems Research Institute (ESRI) Shape Files
SR State Route
TBC Trimble Business Center
UDOT Utah Department of Transportation
VBA Visual Basic for Applications
WiFi Wireless local area network products that are based on the Institute of
Electrical and Electronics Engineers' (IEEE) 802.11 standards
Model Based Design and Construction (MBDC) Guidelines June 2019
2-1 Project Management
CHAPTER 2
Project Management
2.1 WHEN TO USE MBDC
There are benefits to virtually every type of project using some parts or all of the MBDC for
Digital Delivery. UDOT leadership is currently in the process of developing a detailed five-year,
MBDC roadmap that will include Digital Delivery goals and percentage of projects targets.
Leadership is also developing tools to assist project managers and regional leadership in the
effort of analyzing viability and risks for each project with respect to MBDC goals. Once this
process has been fully vetted and established, this section will include more details and
guidance.
2.1.1 Project Management Considerations
As Digital Delivery with MBDC develops, project teams continue to advance the design methods
and workflows, impacting scope, schedule, and budget. Below is a list of things to consider as
the project manager of a MBDC delivery project:
• Coordinate with Central Digital Delivery to ascertain if your project should be considered
for a Digital Delivery project
• Coordinate with Region Leadership for support of your project as Digital Delivery
• Reinforce with the project team that MBDC is one of the project goals
• Build a scope and schedule at the scoping meeting that reflect the team’s familiarity and
position on the MBDC project learning curve
• Plan for NTP on survey to be well before scoping. Consider a separate contract for
survey (before the design contract is addressed) if the firm is a full-service firm
consultant.
• Ensure the schedule accommodates the curation, creation, and review of all the digital
files and formats that make up the MBDC submittal
• Have the project team review the MBDC guidelines document prior to the kick-off
meeting
• Conduct a project preview meeting with all local contractors after the plans,
specifications, and estimate (PS&E) submittal to communicate the MBDC aspects of the
project and receive feedback prior to the project bidding
o Publish the following and notify contractors (listserv) of pre-advertising file
previews on UDOT’s Digital Delivery webpage:
1) All anticipated legal files
2) All anticipated FIO files
3) Survey written report
4) Survey topo statistical analysis spreadsheet.
o Coordinate with Central Digital Delivery and Central Estimate Support
Model Based Design and Construction (MBDC) Guidelines June 2019
2-2 Project Management
• Conduct a project pre-bid meeting to communicate the MBDC aspect to all bidding
contractors that may not have attended the project preview meeting
• Determine if any training is needed for professionals involved in the following phases of
the project:
o Project team
o Reviewers
o Inspectors
o Contractors
• Ensure the schedule accommodates time commitments for training, development, and
review during design and construction
• After project award, conduct a mandatory, in person meeting with the following:
o Preconstruction surveyor and the contractor
o Designer (design team) and the contractor modeler
• Bentley Inroads SS2 is no longer supported by Bentley and UDOT, therefore all projects
should plan on using ORD. ORD is still a maturing product that will improve as we use it
and determine best practices. As this product transition takes effect, teams should
account for extra costs.
Model Based Design and Construction (MBDC) Guidelines June 2019
3-1 Workspace
CHAPTER 3
Workspace
3.1 GENERAL
In traditional design and delivery, CAD standards are primarily important for communication
among designers and the appearance of printed plan sheets. Much of the data associated with
these CAD elements, such as level, color, length, area, volume, etc. are lost in the delivery of
plan sheets. Conversely, MBDC projects include delivering CAD elements and associated
properties to contractors and asset managers. Therefore, every element needs to have
consistent and logical names and symbology for optimal downstream usability. The workspace
setup and ability to create project customizations is critical to the outcome of an MBDC
project.
3.2 WORKSPACE SETUP
Start the project with the latest Bentley software, workspace, and configuration. The latest
workspace files are available through the Department’s ProjectWise:
Workspace-CONNECT (UDOT ProjectWise link)
Workspace-CONNECT (Consultant ProjectWise link)
If the project will be worked on inside the Department’s ProjectWise, all resources and
configuration files should load properly. If, however, the project will be worked on outside the
Department’s ProjectWise, it is imperative the latest workspace’s resources and configurations
files are migrated to the host ProjectWise location before design commences. The following
Bentley videos are helpful for setting up and migrating workspaces.
Bentley Workspace Learning Path
3.2.1 Workspace Customization
The standard UDOT workspace will likely not contain all the resources (feature definitions, cells,
levels, etc.) necessary for delivering an MBDC project. The Bentley CONNECT managed
workspace in ProjectWise allows project-specific additions. Designers working on a MBDC
project need to create and deploy custom project CAD resources and notify UDOT via email at
udotdigitaldelivery@utah.gov when this has been done. Workspace customization skills are
broad, detailed, and necessary, yet they are well beyond the scope of this document.
When delivering an OpenBridge/ProStructures model, setup of level names, component names,
and feature definitions are crucial. Features and components are viewed and utilized by all
consumers of the model, so it is important the names are logical, simple, and accurate.
Additionally, it is easier to understand and navigate a model if elements are broken into as many
parts as possible.
Model Based Design and Construction (MBDC) Guidelines June 2019
3-2 Workspace
OpenBridge and ProStructures can use level names, element templates, feature symbology,
and feature definitions. As projects are completed, the libraries can be updated with information
created by the consultants. If new entries are needed, administrators can enter these into the
workspace by opening the structures .dgnlib within OpenBridge or ProStructures and inputting
the new items into the associated lists. The Department will provide the current workspace for
structure modeling all contained in one .dgnlib file. As long as the project workspace files are
pointing to the OpenBridge .dgnlib then all workspace items will be available in every model.
Custom project resource libraries can be created and stored in the project workspace folder.
Designers will need to notify the Department CAD workspace managers of all project custom
resources so that recurrent or widely-needed items can be identified and added to the standard
workspace. It is necessary to provide metadata (notes and information) during the final submittal
to assure any downstream users of the data are aware of the differences between the project
and the standard UDOT environment.
Model Based Design and Construction (MBDC) Guidelines June 2019
4-1 Survey
CHAPTER 4
Survey
4.1 GENERAL
Construction based on a model is only as accurate as the survey on which the model is based.
Survey quality or accuracy is measured by two elements: the accuracy and precision of the
survey control network, and the accuracy of the model of existing conditions or terrain model.
Both of these measures can be met by following the requirements outlined in the current Survey
and Geomatics Standards Manual (2017). Documentation of meeting these standards is
required by the preconstruction surveyor.
4.2 USE SURVEY OPENROADS WORKSPACE
Using the current workspace ensures the proper levels, line styles, and perhaps most
importantly, terrain features are properly discoverable by the design software and tools.
4.2.1 Meet Geomatics Manual Requirements – Detail and Accuracy
The current Survey and Geomatics Standards Manual includes the survey standards and
necessary accuracies, procedures, and reporting to confirm the survey’s precision/how
conforming the survey is to the contractor’s needs and requirements.
To reduce quantity errors in construction, the survey control and model used by the contractor
during construction needs to be the same one used as the basis for design. Provide the
contractors with the preconstruction control network, and even the same control points as the
design survey, where possible. Surfaces need to be collected at sufficient density, detail, and
accuracy to generate a realistic representation of the actual natural ground surface.
Discrepancies in the survey model are viewed as risks by the contractor, which they generally
account for by pricing said risk into their bid. Open communication between the preconstruction
team and the contractor reduces the perceived project risk, leading to more accurate and leaner
bids.
Different assumptions may apply to different locations within the survey area. Hardscape
features are typically held to a higher standard than softscape features, and softscape features
to a higher standard than areas like steep slopes. For example, an area would be defined on a
map that encompasses the paved features, from the crown of the road to the back of walk, and
defined as the “hardscape features” area. These areas and the accuracies required in them
should be identified during scoping of the survey and used throughout the project survey
reports—especially when reporting the accuracies achieved in the confidence report of the
topographic surface.
The contractor will schedule a coordination meeting(s) with the surveyor who completed the
survey control and topography to discuss and clarify any questions or concerns regarding
previously completed survey work, within seven days of NTP and before beginning work. Useful
agenda items include questions and concerns about preconstruction survey control or methods,
Model Based Design and Construction (MBDC) Guidelines June 2019
4-2 Survey
access to survey files on ProjectWise, locations of survey files (reports, CADD, field notes,
pictures, etc.), safety concerns and observations, as well as items related to construction and
inspection, rovers for inspectors, training, and as-builts (refer to Chapter 7 of the UDOT Survey
and Geomatics Standards for additional information).
4.2.2 Written Report
The documentation required under these standards requires preparation of survey control
diagrams and reporting that documents are compliant with the project control network.
Compliance of the terrain model is documented with a survey report and a statistical analysis of
the survey surface. Upload the survey control diagram (SC sheets), statistical analysis, and
report(s) to ProjectWise early during the project, ideally before design activities have begun.
Summarize in the written report the survey methods employed, the basis of the project
coordinate system, and monuments and control points found and set, including checks into the
NSRS. Include all summarized calculation sheets and analysis that formed the basis of the
summary report. As noted in the Survey and Geomatics Standards, these calculations and
support documents include a list of control points (including fields required on the survey control
sheets), point list(s) of topographic survey points, network adjustment reports, post-processing
reports from static GPS, leveling reports, coordinate system definition reports, a statistical
analysis spreadsheet, a control CAD file, photo/sketches of any survey control monuments, and
any other survey files or notes that may be useful for establishing survey control.
4.2.3 Topo Confidence Report (Excel Document)
The accuracy of the survey is tested by determining the 95% confidence interval of survey
points and the survey surface. This measure can be determined either horizontally or vertically.
For the statistical analysis to be valid, there must be at least 40 check shots; striving for
approximately 50 points per mile in each class would represent a good minimal effort. The
observations should be independent and random (see Chapter 6, UDOT Survey and Geomatics
Standards).
Model Based Design and Construction (MBDC) Guidelines June 2019
5-1 Design
CHAPTER 5
Design
5.1 DELIVERABLES
The purpose of this section is to define information, files, and formats necessary for delivery of
MBDC projects.
5.1.1 3D vs. 2D Design
Much of the information the contractor utilizes does not require a 3D component, such as
summary sheets, notes, attribute information, and CAD linework. However, as technological
advances are made, demands for 3D information will continue to increase as the construction
industry pushes towards more automation and data driven integrated delivery.
5.1.2 Model Authoring
Objective
The primary goal of model authoring is to generate a 3D model that provides the information
required to construct the project while achieving the following objectives:
• Provide element data sets that are compatible with other BIM/Civil Information Modeling
(CIM) uses while ensuring element data sets can be used during fabrication and
construction.
• Identify the level of development (LOD) for each element needed to meet the project
requirements.
• Provide a model that minimizes modifications required between the completion of the
design phase and the construction phase of the project.
• Ensure the model is generated such that it easily and accurately conveys the design
intent.
Model Authoring Workflow
The model authoring workflow shown in Figure 5.1 can be broken up into the following four
sections:
• Reference Information
• Design Team
• Exchange
• Project Review Team
Model Based Design and Construction (MBDC) Guidelines June 2019
5-2 Design
5.1.3 Design Team
The design team is responsible for creating and maintaining the model until project completion.
The model authoring workflow is detailed in Figure 5.1 and in the video here. The following
breaks down the different workflow sections.
• Start Model Authoring
o Select software that is compatible with other disciplines (i.e. OpenRoads
Designer, OpenBridge Designer, Tekla Structures, etc.)
o Set up workspace and databases that will be utilized in the model authoring
• Project Oversight and Management
o Review and incorporate the project requirements, concepts, and preliminary
models into the model
• Model Authoring
o Generate all models for each of the following disciplines and in some cases
generate multiple models per disciple to facilitate parallel or shared workflows:
▪ Structures
▪ Roadway
▪ Drainage
▪ Utilities
▪ Signing/Striping
▪ Right-of-Way (ROW)
o Provide all relevant data for each model element (see Section 5.1.4 for 3D
Design Information and Section 5.1.5 for 2D Design Information for required
elements)
o Compile reports and supporting documentation to be attached and linked with
model during the Apply Data Sets step of the workflow
o Create all required 2D additional details for attachment to the model in the Apply
Data Sets step of the workflow
• Apply Data Sets
o Once the design process is completed, apply attributes or properties to the model
elements and link any necessary external data including PDF, XLS, and
hyperlinks to web resources as appropriate. Attributes or properties can be
added with the ItemTypes/Asset Manager tools available in the Bentley
CONNECTED applications. Links to external documents can be applied to
elements using the Links function available in MicroStation. The standard
workflows and workspace support for this is currently a work in progress. The
minimum attributes and attachments to be applied to the model include, but are
not limited to:
▪ Data detailed in model authoring
▪ Pay items
▪ Standard specifications
▪ Special provisions
▪ Measurement and payment
▪ Acceptance and documentation
Model Based Design and Construction (MBDC) Guidelines June 2019
5-3 Design
• Publish i.dgn
o For all models generated during the model authoring, an i.dgn must be created
o Combine all i.dgn files into a single container file
• Publish i.model
o Publish i.model from the container file
Refer to the Appendix, 7.2 Publishing i-models Resources, for best practices for i-model
publishing workflow guidelines.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-4 Design
Figure 5.1 – Model Authoring Workflow
Model Based Design and Construction (MBDC) Guidelines June 2019
5-5 Design
5.1.4 3D Design Information
Below is the 3D information expected in a fully optimized model for construction. Digital
Delivery project teams will optimize their models as completely as their project budget and
schedule allow. As stated in section 2.1.1, Project Management Considerations, modeling best
practices are continually being refined within ORD. Users are encouraged to report any issues
or bugs with Bentley software to udotdigitaldelivery@utah.gov. Include the user's contact
information, a description of the issue, and a Bentley issue number if the issue has been
reported to Bentley.
• Roadway
o A single, complete 3D breakline file that is properly organized to allow for easy
and accurate selection/display of the breaklines for a given design or design
segment. All breaklines must be organized or curated in such a manner as to
allow downstream users to easily display or select the necessary elements to
create accurate surfaces of any layer of the proposed pavement structure in any
CAD, construction, or surveying application. In addition to the breaklines, these
file(s) must contain exterior boundary elements that accurately bound the
proposed triangulated area. In the majority of cases, the exterior for a given area
will be the same extents for the top and bottom surfaces. These file(s) need to be
organized in a manner that it is easy to isolate linear items that are often staked
out, like the top back of curb. Acceptable formats are: DGN, DWG, DXF, and
XML.
o 3D breakline documentation or a metadata file must also be provided. This
documentation must list the levels necessary to display/select to create a given
pavement design layer in any CAD, construction, or surveying application.
Acceptable formats are: TXT, XLS, XLSX, DOC, and DOCX.
o Complete top and bottom surfaces with an accurate exterior boundary, in at least
one of these formats: DTM, XML, TIN, TTN, or OpenRoads terrain.
o All roadway elements will include the following element property (data) attributes:
▪ Pay item name
▪ Pay item number
• Pavement Marking
o All proposed pavement marking will continue to be displayed with geometry at a
constant elevation for both the linear and shape/cell elements. However, it is a
best practice to set the elevation of these elements to some constant that is
higher than the highest elevation of any part of the proposed or existing geometry
so that all markings are visible in the top view of 3D files, including the published
i-models.
o All pavement marking geometry will include the following element property (data)
attributes:
▪ Pay item name
▪ Pay item number
▪ Material (tape or paint)
▪ Type (solid, skip, dotted)
▪ Width
▪ Color
▪ Taper rate, where applicable
Model Based Design and Construction (MBDC) Guidelines June 2019
5-6 Design
• Signing
o All proposed, existing, and relocated signs typically represented by point
graphics or 2D shapes/cells will need to be displayed with 3D geometry
representing the actual sizing in the X, Y, and Z of the foundations and poles. For
existing foundations, estimate the depth for design/conflict detection. 3D
geometry for the sign panels are optional but not required. It is advisable to
develop 3D geometry for larger sign structures though, as this improves
overhead conflict identification and construction staging issues.
o All signing geometry will include the following element property (data) attributes:
▪ Base pay item name and number
▪ Post pay item name and number
▪ Sign pay item name and number
▪ Sign ID
▪ Sign description
▪ Sign color
▪ MUTCD code
• Utilities
o All existing and relocated utilities typically represented by linear geometry need
to be displayed with 3D geometry representing the correct diameter or other
appropriate sizing. All elements need to be displayed at the correct depth at
potholed locations and at assumed depth at all other locations.
o All existing and relocated utilities typically represented by point graphics or 2D
shapes/cells need to be displayed with 3D geometry representing the actual
sizing in the X, Y, and Z. These include, but are not limited to all:
▪ Junction boxes, cabinets, and pedestals
▪ Existing power poles and power lines (to verify height of power lines over
roadways)
o All utility geometry will include the following element property (data) attributes:
▪ Assumptions used for the utility
▪ Utility type
▪ Utility owner
▪ Shape
▪ Size
▪ Material
▪ Pay item name
▪ Pay item number
• Drainage
o All proposed drainage typically represented by linear geometry needs to be
displayed with 3D geometry representing the correct diameter or other
appropriate sizing.
o All proposed drainage typically represented by point graphics or 2D shapes/cells
needs to be displayed with 3D geometry representing the actual sizing in the X,
Y, and Z. These include, but are not limited to all:
▪ Catch basins
▪ Diversion boxes
▪ Manholes
▪ Etc.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-7 Design
o All drainage geometry will include the following element property (data)
attributes:
▪ Element ID
▪ Pay item name
▪ Pay item number
▪ Unit of payment measurement
▪ Pipe attributes (shape, size, length, material, slope, flow rate, velocity)
▪ Drainage structures attributes (grate/cover type and elevation, calculated
spread)
• Signals and Lighting
o All proposed signals and lighting typically represented by linear geometry need to
be displayed with 3D geometry representing the correct diameter or other
appropriate sizing.
o All proposed signals and lighting typically represented by point graphics or 2D
shapes/cells need to be displayed with 3D geometry representing the actual
sizing in the X, Y, and Z. These include, but are not limited to all:
▪ Poles (all)
▪ Foundations
▪ Mast arms
▪ Junction boxes
▪ Cabinets
▪ Etc.
• ATMS
o All proposed ATMS typically represented by linear geometry need to be
displayed with 3D geometry representing the correct diameter or other
appropriate sizing. However, the ATMS lines can be 2D unless a specific
elevation is being specified in the design.
o All proposed ATMS/lighting typically represented by point graphics or 2D
shapes/cells needs to be displayed with 3D geometry representing the actual
sizing in the X, Y, and Z. These include, but are not limited to all:
▪ Foundations
▪ Junction boxes
▪ Cabinets
▪ Etc.
o All ATMS/lighting geometry will include the following element property (data)
attributes:
▪ Pay item name
▪ Pay item number
• Structures
o All structural components, including foundations, walls, girders, decks,
abutments, bents, and boxes will be modeled with geometry that accurately
represents the actual sizing in X, Y, and Z.
o See Section 5.3 Structure Modeling Considerations for more information.
• i-models
o i-models allow for delivery of 2D and 3D geometry, fully attributed, in a read-only
format that the contractor can use in the field on mobile devices. These new
mobile applications replace the function of a traditional paper or PDF based plan
Model Based Design and Construction (MBDC) Guidelines June 2019
5-8 Design
delivery. The mobile format allows for much greater access to attributes data,
more accurate station/offset and other measuring, and many other benefits.
o At a minimum, fully attributed i-model(s) will be published with all of the 3D model
components. These i-model(s) will include all 3D modeled component meshes,
or other manually-modeled 2D and 3D resources required to communicate the
designer’s intent.
5.1.5 2D Design Information
Below is the minimum 2D information required to be delivered to the contractor (if the
documents are created as part of the project):
• All 2D Layout/Design Files
o The required layout/design files and acceptable format(s) to be delivered are as
follows, by discipline:
▪ Roadway design layout file – DGN, DXF
▪ Horizontal alignment file – DGN, DXF
▪ Drainage profiles – DGN, DXF
▪ Signing and marking – DGN, DXF
▪ Structures – See Section 5.3 Structure Modeling Considerations for more
information
• GIS Files
o These files are necessary for the integration of design linework in the UDOT GIS
system. The required files and acceptable format(s) to be delivered are:
▪ Roadway design layout file – DGN, SHP
▪ Roadway shapes of paved areas – DGN, SHP
▪ Signing and marking – DGN, SHP
5.1.6 Annotation and Non-Graphic Data
The following are examples of possible 2D data and non-graphic files that may be delivered to
the contractor:
• Text and Annotation – acceptable formats include DGN, i-models, PDF
o Discipline-specific text files (notes, callouts, dimensions, etc.)
o General notes
• Details – acceptable formats include DGN, i-models, PDF
o Typical sections
o Structures or special details
• Summary Data – acceptable formats include DGN, i-models, XLS, XLXS, PDF
o Summary of items (all bid items and quantities)
o Detailed summary tables (earthwork, surfacing, striping, drainage structures,
etc.)
Model Based Design and Construction (MBDC) Guidelines June 2019
5-9 Design
• Civil Geometry – acceptable formats are DGN, ALG, XML
o Mainline
o Side streets
o Special ditches or grading built from an alignment
o Any special curb return profiles
o Back of sidewalks
5.1.7 Delivery Documentation
The delivery guidance represents anticipated deliverables on a MBDC project. It is expected
that as tools and workflows improve, there will be room to deliver more, and in some cases, the
specific project team may want to explore an improved workflow or technology that will allow for
a final deliverable that is more efficient or more valuable to the MBDC process. All deviations or
variations from the delivery guidance must be documented in a Deviation from UDOT MBDC
Guidelines Form, approved by the Department project manager and region preconstruction
engineer, and be communicated to the MBDC Central Preconstruction staff.
5.1.8 Files Advertised as Legal Document vs. For Information Only
Several categories of data are delivered with MBDC projects:
Required Files: Models and documents that are required to be delivered to the contractor but
are not part of the documents or files defined as the legal document.
The Legal Document: Models and documents that are required to be delivered which the
engineer of record (EOR) certifies as a correct and accurate representation of the design intent.
For Information Only: Additional helpful files, some required and some not required, to be
delivered to the contractor.
5.1.9 Files Advertised as Legal Document
The MBDC process for digital delivery results in many different file types which can be helpful to
the contractor. Some of these files are required deliverables and others are left to the discretion
of the EOR. However, on MBDC projects, only specific electronic files represent the design
intent that the EOR certifies as correct and accurate. The files below, referred to as “the legal
document,” will be the standard that the contractor will be held to during construction.
Currently, very few files delivered on MBDC projects are the legal document. The EOR may
deliver files in a variety of formats if requested by the contractor for their convenience. However,
only the files and specific formats listed below will be considered the legal document for MBDC
projects.
The legal document files and required/acceptable formats:
• Alignments – DGN
• Discipline-specific 2D design files – DGN
• Discipline-specific 3D modeling design file(s) – DGN
• Refined and import-ready 3D breakline file(s) – DGN
Model Based Design and Construction (MBDC) Guidelines June 2019
5-10 Design
• Proposed ROW – DGN, PDF
• Detail sheets – DGN, PDF
• Summary of items tables (quantities) – DGN, XLS, XLXS, PDF
• Project specifications – PDF
• Project measurement and payment – PDF
If the EOR chooses to deliver the above items in additional formats, those files will be treated as
“for information only” and not the legal document.
5.1.10 Files Advertised as For Information Only
The EOR is encouraged to provide other project resources and files to the contractor. These
files can be very useful to expanding the understanding of the design intent and assist
contractors who use a wide array of software and tools and have a preference to certain file
formats during import/conversion. Below are a few examples and suggested formats of these for
information only files:
• Existing topography linework (Extopo) – DGN
• Existing ROW linework (ExROW) – DGN
• Existing utilities linework (ExUtility) – DGN
• Pavement layers surfaces – DTM, XML, TIN, TTN, OpenRoads terrain
• Horizontal and vertical geometry – DGN, ALG, XML
• Template library – ITL
• i-model – .imodel, DGN
• Additional information sheets, summary sheets, etc.
5.1.11 Deliverable File and Model Naming Convention Spreadsheet
With OpenRoads modeling and delivery it becomes necessary to consider the model space
naming in all of the DGN files. Renaming the model spaces to something other than default in
all of these files offers an advantage when dealing with larger projects with many model
segments referenced, but more importantly when publishing i-models. Further, because
OpenRoads automatically creates managed 3D models when creating vertical geometries, it is
critical that the default model is renamed before this managed model space is created.
Renaming either or both models after the managed model has been created will result in file
corruption. If this happens, do not try to revert the names back. This file will not be stable or
trustworthy. In this situation the only prudent course of action is to recover the file from backup
from a date/time before the model space was renamed, then move forward. The best rule of
thumb is to rename your 2D model space immediately after initial file creation. Once
OpenRoads has created a managed 3D model space for the 2D model, do not edit the name of
either model space.
For details on file and model space naming conventions see Appendix Section 7.1.
5.2 ROADWAY MODELING CONSIDERATIONS
Rather than provide a step-by-step for modeling, this section highlights key considerations and
possible approaches to modeling that will help avoid pitfalls and problems during review and
Model Based Design and Construction (MBDC) Guidelines June 2019
5-11 Design
delivery. Many of these fundamentals are gathered from trial and error on pilot MBDC projects.
Even if the project team is taking an alternative approach or solution on a project, it is still
recommended to adhere to the following information.
5.2.1 InRoads vs. OpenRoads
While legacy InRoads and OpenRoads share some foundational code and components (namely
templates), the two technologies are very different. These differences necessitate different
workflows and best practices for optimal performance. The following sections cover concepts
and ideas that have proven beneficial to designers and modelers on earlier projects. The
following table shows a summary of the major differences in the two technologies.
DIFFERENCES INROADS OPENROADS
Models or design dynamically updates in response to changes N Y
Modeling relies on many files external to MicroStation Y N
Relationships between elements are stored and respected N Y
Has highly configurable view(s) for modeling environment N Y
Component meshes are a primary output of modeling N Y
Terrain or DTMs are a primary output of modeling Y N
Automatic profiling abilities on linework N Y
Surface templates – applies depths and layers to surfaces N Y
Linear templates – simple, single template models for detail
areas N Y
Terrain filters – selection of civil linear geometry by civil or
primary attributes N Y
Terrain feature definitions – symbology standards that allow for
dynamic visualization options N Y
Civil AccuDraw – precision input that is coordinate geometry
and model aware N Y
5.2.2 Modeling Basics
Both InRoads and OpenRoads employ templates in the modeling process to create geometry
that matches the design intent. Templates like the one shown in the following Figure 5.2, are
made up of enclosed shapes whose vertices are point elements. The act of modeling is
essentially the extrusion of these templates and points along a horizontal and vertical alignment.
The enclosed component shapes become mesh elements in MicroStation and the points are
connected between template drops with lines in 3D space.
The template drop interval is the mathematical distance the modeling software moves along the
alignment before it applies the geometrics that are defined by the template. The feature
definition applied to the components and points are applied to the meshes and 3D breaklines
respectively as the model processes. These feature definitions determine how things will look in
plan, profile, or cross section views. They also serve as a named attribute that enables the
modeler to differentiate and control the display of features in various views.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-12 Design
Figure 5.2 – Template Example
5.2.3 Templates – Feature Definitions
When delivering a model, the setup of level names, component names, and feature definition
assignments in the templates is crucial. Consistent naming of components and features is less
critical when PDF or paper plan sheets are available because the component meshes are
identified and understood by downstream users based on the symbology of the plans. With
paper or PDF plan sheets the properties, naming, and symbology is most relevant to the
organizational preferences of the modeler.
Digital Delivery is driving the need for consistency as it allows features and components to be
viewed and utilized by all downstream consumers of the model, so it is imperative the names
are logical, simple, and accurate. The symbology of the elements can have an impact on the
usability across platforms and users, so primary attributes like color, weight, and style must also
be considered. The Department is no longer just seeing black and white lines on paper; user
accessibility in digital formats should not be neglected. Additionally, in the case of surface
creation, features must be organized and attributed to enable easy selection of breaklines that
belong in specific surfaces without risk of including errant breaklines.
An example of the importance of proper naming is when the design has untreated base course
(UTBC) in the mainline pavement section and also has UTBC driveways. The features
representing the top of the UTBC driveway will be part of the top mesh surface. However, they
will not be included in the triangulation of the mainline UTBC pavement layer. There must be
Model Based Design and Construction (MBDC) Guidelines June 2019
5-13 Design
two different UTBC feature definition names, or some primary attribute difference (color, weight,
style, etc.). As long as feature definitions have some unique property they can be selected with
predefined terrain creation filters. Most of the time, modelers simply make a new feature
definition name and leave the other attributes the same for all material types.
A clear understanding that there are two different sets or categories of feature definitions is
crucial. In civil geometry design, an organized set of features is applied to drawn elements when
the 2D design file is created. There is also a special folder named “Template Points,” as shown
in the following Figure 5.3. These points all have the prefix “TL” which stands for template line.
These feature definitions are only to be assigned to the points in the templates. Point feature
definitions are passed through to the breaklines when the model is processed. Feature
definitions will also need to be applied outside of the corridor/template modeling process.
Figure 5.3 – Feature Definition Library Example
Model Based Design and Construction (MBDC) Guidelines June 2019
5-14 Design
5.2.4 Model Detail Areas and Considerations
Driveways – There are a myriad of ways to approach driveway modeling. Civil geometry (civil
cells) can work, but usually require corridor clipping which slows corridor processing
performance. In the earliest projects that delivered ICM to Trimble there were some issues with
how these containers of civil cells were imported. Most projects to date have abandoned civil
cells for now.
Modeling of driveways with curb and sidewalk can be accomplished in the mainline template as
long as the sides of the driveway edge are 90 degrees perpendicular to the mainline corridor
alignment. Non-perpendicular driveways can still be modeled but are usually handled in a
similar fashion as side street connections. When modeling the driveway with a template that is
running perpendicular to the mainline alignment, some additional 3D linework will need to be
added at the subgrade at the edges of the driveways. This is necessary to create a proper
bottom mesh. Please see this video for a graphic explanation: Driveway Considerations.
Transition Slopes – Many small areas in legacy projects were never modeled unless
necessary for cross sections or using the model components for renderings or animations. In
the latter case, engineering accuracy was not a concern as long as the slopes looked
reasonable. With model-based delivery comes the need to address these small areas,
particularly where it is anticipated the contractor will use AMG or where surface to surface
quantity comparison is necessary for bidding. Here are some areas to plan for additional
modeling effort:
• Major template changes: Often with major template changes the end conditions change
suddenly and the contractor has historically smoothed this out in the field.
• Driveways: Side slopes and grading around drainage features.
• Side streets: Much like driveways, the ditching around the radii or returns must be
modeled as if grading it by hand with a rake; spikes, gaps, and bow-ties/loops must be
removed.
• Off corridor modeling: Adjacent parking lots, special ditches, or any modeling and design
must tie in the existing ground. In cases where the tie locations are very close to the
mainline slopes and it is assumed it will be practically impossible to work in both areas
without impacting the space between, then model the entire area.
Template Drop Ends – Having vertical or horizontal spikes at the instantaneous point where
templates start and stop is not uncommon. This is an issue when the targeted elements begin or
end at these same stations. Sometimes extending targeting elements or using the final design
stage will resolve these issues.
Undercut Components and Key Stations – Do not assume the model components are
complete under the top when reviewing modeling. Assure the bottom and top of the component
are matched up. Usually these anomalies are easily resolved with a key station. Failure to catch
this detail can impact component quantities as well as the dynamic cross sections.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-15 Design
5.2.5 Template Principles and Practices
Dynamic Templates vs. Static Templates – Learning how to master more than the elementary
functions of template design is critical to becoming an efficient modeler. While having a
separate template for every geometric variation works, this becomes difficult to manage when
curating the feature definition for every breakline. It is considered a best practice to avoid
multiple templates when a single, dynamic template can be used instead.
Make a unique template for each road section that is fundamentally different (i.e. two lanes vs.
four lanes with raised median). The fewer templates, the fewer points need to be checked and
coordinated. Building dynamics into templates enables showing or hiding various components.
Taking the time to build flexible geometry into the design will reduce how many templates are
needed to model a project.
Smart and dynamic templates are the goal and work well if not overdeveloped. It is necessary
to balance the complexity of the template to include only what is needed as overly complex
templates may fail and can be difficult to troubleshoot. If it is not in the design, do not put it in
the template. Remove all items that are not necessary for the design.
Template Visibility Switching via Display Rules – Display rules allow the modeler to add
intelligence and elegance into their templates. This leads to faster processing times and more
robust models with fewer independent elements to QC or troubleshoot when unexpected results
arise. Display rules leverage the power of Boolean expressions to determine the final state of
template display at model process time. These expressions can be used to turn on or off
template components, change slopes, widths, or elevations of components based on adjacent
geometries relationships.
In the past, modelers may have used end conditions in templates as a tool for displaying various
components. The end condition would search for a symbology or feature definition rather than a
surface. All other components that needed to be turned on would be parented to this end
condition. The end condition itself was set to “do not construct” with the goal of creating a simple
logic switch that would turn on geometry.
With the transition to OpenRoads, this use of end conditions is no longer considered a best
practice. Because end conditions are one of the last items that process in the corridor, the
enabling of fresh geometry causes additional processing cycles and can be highly detrimental to
processing performance. Removing or replacing end conditions with display rules, where
possible and logical, will improve corridor processing times.
It is suggested to use caution if using end conditions as a means of controlling the display of
template components. As is often the case, there may be exceptions to this guideline where
using the end condition as a switch for graphics does still make sense despite the impact to
processing time. For example, sometimes it is valuable to use an end condition to both activate
and define the child components position and targeting while leaving the end condition set to
“do not construct.” A possible use-case for this is on driveways where the modeler uses a multi-
segment end condition where each segment defines a series of slopes and widths. The
component meshes that define the driveway materials and depths are visually enabled by the
end condition and the physical location and slopes of these are constrained to the slopes,
widths, and vertices of the parent end-condition.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-16 Design
Display rules can be a frustrating aspect of template creation, but they are key to creating
dynamic templates. Watch these videos to begin understanding display rules:
• MBDC - Understanding Display Rules 01
• MBDC - Understanding Display Rules 02
• MBDC - Understanding Display Rules 03
• MBDC - Understanding Display Rules 04
• MBDC - Understanding Display Rules 05
Zero Width Components Visibility Control – Use display rules to turn off components whose
widths are less that one tenth of a foot (i.e. < 0.1 ft.). It is a best practice to manage model
components and breaklines so that only the breaklines that are necessary for the design are
created. Thus, disabling the visibility of components whose widths are zero or very near zero
can eliminate a significant amount of cleanup and QC time prior to final delivery.
Cases where the design has components like turn lanes, driveway aprons, and median areas
that “grow” from a zero width to some non-zero width are not uncommon. If these components
are displayed when they are “collapsed” to a nominal width (i.e. width < 0.1 ft.) there will be
extraneous breaklines in the design requiring cleanup. A simple display rule that evaluates the
width of two points in the component and turns off the component once the width is zero, or very
close to zero, is a best practice.
Double Components – Make sure there is not more than one template component being
modeled within the same space. This can lead to erroneous component quantities and errors or
confusion during construction. It is not uncommon during model QC to discover duplicate or
double components in areas like medians, where display rules dictate which components or
median options are to be modeled. Being aware of this is important for model QC, but moreover
using workflows and practices that reduce their likelihood is preferred.
One suggested approach to address this problem is to vertically separate the various options in
the template. These vertically separated components will have a parametric label applied to key
points and this label value can be defined in the corridor so as to normalize or correct the
elevation differences in the template once the model processes. This is much easier to
understand when you see it in practice, the following video explains parametric labeling:
• MBDC - Parametric Labels for Vertical Offsets
Component and Feature Name Overrides – Use component and feature name overrides so
the delivered models have breaklines and components with logical and simple names that
translate to non-engineers. With paper or PDF-only deliverables there was no consequence to
anyone other than the modeler what the names of features of components were. It was not
uncommon to have models with complex and obtuse naming schemas. With the move to model-
based delivery it has become a best practice to use these overrides to reduce confusion to the
downstream model stakeholders. The following video explains how these overrides affect the
model and how to use them:
Model Based Design and Construction (MBDC) Guidelines June 2019
5-17 Design
• MBDC - Component and Feature Name Overrides
Delaunay’s Triangulation – Approach template design and modeling with best practices and
workflows that allow for accurate and efficient sharing of models and surface data to other
stakeholders and software. Thanks to mathematician Boris Delaunay (1890-1980), the ability to
create complex triangle networks from points and lines is available. Delaunay’s triangulation has
been the basis of existing and proposed DTM and TIN files for a long time. However, a limitation
with this algorithm is that it will not accurately calculate vertical or overhang surfaces.
InRoads and OpenRoads templates allow for vertical faced components and the mesh
geometry engine native to MicroStation to fully support 3D geometry. Thus, it is imperative the
modeler understands which Delaunay’s meshes will need to be generated from the components
and their corresponding breaklines. In some cases, it is necessary to add a minimal slope to the
component edges to enable proper triangulation. This slope, or “batter” as it is sometimes
called, can be defined with a discrete number or can be parameterized to enable dynamic
adjustment and optimize model process time. Check out the following video that explains how
this works in templates:
• MBDC - Modeling for Delauneys
5.2.6 Surfaces and Components Delivery Considerations
Delivering accurate and Delaunay-compliant surfaces is an important aspect of a Digital
Delivery project. This topic is covered in more detail in the Chapter 5 subsections on templates.
In addition, delivering the various surfaces with logical and understandable names is important.
When generating top and bottom surfaces it is possible, the triangulation and creation of the
exterior boundary of the two surfaces may differ in location. From an estimator’s perspective, it
is desirable for these boundaries to be the same. One common example where these
differences can present themselves is at areas adjacent to the driveway and the mainline. In
these areas, the triangulation between the top and bottom can be quite different, and the
variations can make for large differences in the horizontal location of the external boundary for
each surface. These boundary differences can create both quantity and accuracy doubts and
lead to higher bidding by contractors to account for potential risk.
5.2.7 Surface Templates
Surface templates are influential for modeling irregular areas or filling pavement areas (i.e.
intersections, driveways, parking lots) where there are acute angles relative to some geometry
and the template drop, which is perpendicular to the alignment. For example, a radial drive curb
return intersects with the mainline edge of pavement.
Surface templates are applied to a terrain, as shown in Figure 5.4, and the terrain is made up of
breaklines. Unlike a template push, no new template top breakline features are applied. This is
important because it is standard to use Terrain Graphic Filters based on the feature definition
name to choose all requisite features for a given delivered surface. This is the one exception
where a feature definition applied to the civil geometry, that is usually reserved for template
points, eliminates the need to create a special set of features or additional filters for this use.
The breaklines in other surfaces (everything below the top) may not be displayed automatically.
This is a setting under the properties dialog that can be toggled on to display these features.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-18 Design
Figure 5.4 – Applying Surface Templates
The last consideration is that surface templates are displayed/generated vertically. There is no
option for adding a slope or batter to the edges, which results in a non-Delaunay surface from
these breaklines. Currently, the workflow involves manually creating offset civil geometry from
the bottom features that enable a proper Delaunay’s triangulation. Surface templates are
influential, but they carry this additional effort.
5.3 STRUCTURE MODELING CONSIDERATIONS
This section highlights key considerations and possible approaches to modeling that will help
avoid problems and ensure information needed for a successful project is included in the review
and delivery. This structures section is not a step-by-step manual for creating structural models,
but rather a document of procedures and processes from previous pilot projects. Adherence to
the following information is recommended until improved procedures are discovered.
5.3.1 3D Design Information
Below is the minimum 3D information required for delivery to the contractor.
• Complete solids model of all superstructure and substructure elements
o The .dgn file for the solids model, including all attributes
• Reinforcement models of all concrete elements
o All .dgn files for the reinforcement files, including all attributes
5.3.2 2D Design Detail Information
The following is the minimum 2D information required for delivery to the contractor. This
information is typically created within a .dgn file and attached to the model as a PDF detail
document.
• General notes detail sheet with information similar to traditional situation and layout
(S&L) sheets, containing:
o General design notes, design data, load rating, quantities, list of attachments
• Location plan detail sheet
• Simplified plan view detail sheet
o Include items that are difficult to show within the 3D model
• Simplified elevation view detail sheet
o Show information such as minimum vertical clearances and items difficult to
show within the 3D model
Model Based Design and Construction (MBDC) Guidelines June 2019
5-19 Design
• Simplified section view detail sheet
o Show a simplified section view of information not available within the 3D model
• Working standard sheets applicable to project structure (not an exhaustive list if
applicable):
o Pile details, girder details, intermediate diaphragm details, graffiti cover and
elastomeric pad, deck details, precast panel details, fence details, aesthetic
details
• Soil boring logs
5.3.3 Additional Supporting 2D Documentation
Below are examples of additional 2D documentation required for delivery to the contractor.
Documentation will vary depending on project requirements:
• Sign structure, wall structure, rehabilitation documentation, and other information not
modeled in 3D
o Documents are to be attached to text on the zero elevation of a 3D .dgn file
• Reports applicable to the structure
o Load rating, geotechnical summary, etc.
• Summary data – acceptable formats include DGN, i-model, XLS, XLXS, PDF
o Summary tables for all quantities
o Elevation tables for bearing seats and substructure
o Screed elevation and dead load deflection
5.3.4 Files Advertised as Legal Document
In addition to the deliverable files described in sections 5.1.9 and 5.1.10, structures MBDC
projects require additional files be provided as the legal document and for information only
documents.
As previously stated, the EOR may choose to deliver files in a variety of formats for the
convenience of the contractor. However, only the following files and specific formats listed will
be considered the legal document for MBDC projects.
The legal document files and required/acceptable formats:
• Model reinforcement summary reports – PDF, XLS, XLSX
• Deck elevation reports – PDF, XLS, XLSX
• Pier elevation reports – PDF, XLS, XLSX
• Beam seat elevation reports – PDF, XLS, XLSX
• Wall, sign, rehabilitation plans – PDF
• Additional information as needed for the project
If the EOR chooses to deliver the above items in additional formats, those files will be treated as
for information only and not the legal document.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-20 Design
5.3.5 Files Advertised as For Information Only
The EOR is encouraged to provide other project resources and files to the contractor. These
files can be very useful in expanding the understanding of the design intent. They can also
assist contractors who use a wide array of software. Some of these items are submitted to the
Department in a different manner but will be attached to the model so they must be marked as
“for information only.” A few examples and suggested formats of these files includes:
• Compiled detail sets – PDF
• Load rating reports – PDF
• Published models for other software use – .ifc, i.dgn
• Published read-only models for field use – i-model
• Additional information attached to model submitted to the Department in a different
manner
• Structural calculations for fabricator(s)
5.3.6 Model Relevant Information
The following information is an example of the information to include in some manner in the 3D
model or supplemental information documents. This list is not exhaustive and includes required
information for typical structures.
MODEL ELEMENT REQUIRED INFORMATION
Abutment cap Location, bottom elevation, bearing seat elevation, material
properties
Approach slab Location, thickness, material properties
Bearings Location, bearing seat elevation, type
Bent cap Location, top elevation, bottom elevation, length, width, depth,
material properties
Deck Location, thickness, material properties
Diaphragms/cross
frames
Location, material properties
girders Location, plate sizes/girder type, material properties
Granular backfill Location, top elevation, bottom elevation
Overlay Location, type, thickness
Parapets Location, type/shape, material properties
Piles Location, length, tip elevation, cut-off elevation, pile type, batter,
material properties, pile data table
Reinforcing steel Location, bar size, length, spacing, clear distance, bar mark, bar
type, orientation
Rigid plastic foam Location, material properties
Sleeper slab Location, material properties
Wingwall/finwall Location, material properties
Model Based Design and Construction (MBDC) Guidelines June 2019
5-21 Design
5.3.7 File Naming Convention
• PIN_Structure #_Design Program_Element (if needed).dgn
o Models
▪ Open Bridge Modeler (OBM)
▪ ProStructures – one model needed for each element (additional possible)
• PIN_Structure #_Detail or Report Name.dgn, .xlsx, .pdf
o Model attached documents
▪ Details created from .dgn sheet files
▪ Reports created from design software or external sources
5.3.8 OpenBridge Modeler
OpenBridge Modeler is a powerful software that gives bridge engineers the ability to convey
design intent through 3D models instead of 2D plan sets. For software tutorials, see the Bentley
OpenBridge YouTube page or videos and training available through the Bentley CONNECTION
Client, or CONNECT Advisor. 3D modeled bridges are built slightly different than other
discipline models. The geometry of the bridge is controlled completely by the roadway geometry
file (alignment file), which is referenced into the structures model. Bridge models are also
different in that there is only one 3D model space used within the file. It is imperative that
structure models are created from a 3D project seed file.
5.3.9 ProStructures
ProStructures is used to define and model all reinforcement within the concrete elements. It is
suggested that a separate file be created for each concrete element type in the structure model.
Additional files can also be created to allow for multiple modelers to work on different reinforcing
within the same element.
5.3.10 OBM Libraries
Libraries can be defined for almost all the different elements within OpenBridge. These libraries
are stored either on the local drive or within the project workspace on ProjectWise. Libraries do
not have to be updated due to the parametric functionality of OBM. However, the process can
run much quicker and easier going forward if templates are saved and reused. Templates are
used to define the base geometry of elements. Once a template is defined, the solid can be
manipulated by the parametric tools created for each template. Solid modeling tools may be
used to make any additional adjustments that are required to create accurate geometry. Care
must be taken to ensure the parametric capabilities of the element are not compromised due to
the solid modeling tools.
Variables for each template can be defined within the workspace. Each variable will either read
from a .xml or a cell library (.dgnlib). Examples of these files can be taken from the installed
templates on the local drive.
Workspace libraries can be adjusted and added dynamically through the project. Care must be
taken to ensure that changes do not adjust other models within the project. Any change to a
template will update any model that is using that element template. The process to change any
Model Based Design and Construction (MBDC) Guidelines June 2019
5-22 Design
Figure 5.5 – OBM Template Management Tab
template is to check out the template file first and then check out any model. Go to the Template
Management tab, shown in Figure 5.5 below, and open the desired template. Changes or
additions can be added and then saved within the model. Finally, check the model into the
workspace and then check the template file back in.
Currently, ProStructures does not contain any libraries that can be used directly through the
workspace. However, there are multiple local documents that will determine the layout of
reports, such as bar bending schedules. These can always be saved and sent to other
colleagues to use on other models.
5.3.11 Special Considerations
Modeling Limitations
Currently the Bentley OpenBridge Designer does not have the capability to model elements
such as intermediate bracing on prestressed girders. It has also been confirmed that the
software has known issues with certain processes such as rebar modeling, inability to model
integral abutments or drop-down pier caps. In these cases, an alternate route must be chosen
to ensure all information needed is conveyed to reviewers and advertisement. Creating
additional detail sheets is an easy way to convey this information, knowing that end users are
already comfortable with this type of data delivery. However, the intent of the MBDC process is
to continue increasing the effectiveness of delivered information and use the tools that are
provided to us. It might be more difficult and time consuming to put information in a 3D form
compared to creating a 2D plan sheet, but this is expected early in the learning process. The
more the Department and users become familiar with the Digital Delivery process, the more
streamlined it will become.
Union Pacific Railroad (UPRR)/BNSF Railway Submittals
Railroad submittals are required to have more information than what is typically provided to the
Department for an MBDC project. The detail sheets for general notes, location plan, plan,
elevation, and typical section will have additional information required by the “Guidelines for
Railroad Grade Separation Projects” manual. A “Railroad Notes and Clearance” detail sheet is
also required. For submittals after S&L, additional details are required to provide the complete
design intent and detailing. These additional details are not necessarily required by the railroad
but should still be included in all railroad submittal packages.
Interaction of Structure Solids
OpenBridge takes a top down modeling approach. By doing this, most solids elevations are
controlled by the deck. Care must be taken when modeling all solids to ensure input values are
correctly modeled. It is the responsibility of the modeler to check all elevations of each solid and
make corrections as needed to have a geometrically-correct model.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-23 Design
A few known issues are:
• Haunch input for steel girders will include the top flange of the girder.
• Quantities for steel haunches will also include the top flange area for the amount of
haunch concrete.
• Concrete girders will model as chorded elements from bearing line to bearing line.
• Haunches for concrete and steel girders will not model thickness correctly and must be
adjusted.
• Superstructure concrete diaphragm elements can match top of deck but will not model
correctly. A simpler approach is to set the bottom of substructure and then use solids
modeling to adjust the top of concrete diaphragms.
• Substructure elements have the option to match the deck edge, however a more stable
approach is to set the actual length of solid with a horizontal offset from PGL line. The
ends can then be adjusted by solids modeling tools.
Pierlines/Control Lines
Pierlines is a term used within OBM to control the geometry of substructures as well as the
beginning and end points of the superstructures. When pierlines are created within the model
they are placed at the zero elevation, along with a few other elements used to set bridge solids.
These elements must be labeled for end users to easily understand their use. It is suggested to
create pierlines for the centerlines of every support and for every centerline of bearing for the
superstructure. Pierlines will also be used to control the extents of deck elements, precast
panels, approach slabs, parapets/curbs, and even sleeper slabs. It is imperative for the modeler
to have a great understanding of how pierlines can manipulate solid elements and the issues
that might arise from having pierlines in certain positions.
A few known issues are:
• The inability to manipulate girder lines when pierlines intersect the girder layout.
• The maximum distance between sections in the deck options must be changed to one
foot when pierlines intersect the deck elements. If not, girder elements might model
incorrectly.
• Small deck elements constrained by pierlines might need to be manipulated by solid
modeling tools to ensure extents are correct.
Miscellaneous Elements
A few miscellaneous issues are:
• Intermediate cross frames cannot be modeled for concrete girder structures and must be
detailed in additional detail sheets.
• The use of solid modeling tools might strip the parametric intelligence from the solids.
This can be due to the way the solids are being manipulated. Different manipulation
tools might fix this.
• Quantity reports can be created from the native software, but these reports must be
checked to ensure accuracy.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-24 Design
• Additional modeling issues will be encountered and should be communicated to the
software manufacturer and the Department when available.
5.3.12 Structures Model Design QA/QC Procedures
Structures models are to be reviewed differently than other discipline files due to the way
models are created and the amount of embedded information in each structure element. The
roles and responsibilities of individuals involved are like that of a traditional project.
Roles and Responsibilities for Model QC
Originator: The individual who develops the model and/or templates geometry. The originator
can also be the individual who attributes the model with data or links to additional project
documents.
Checker: The individual who verifies the accuracy and completeness of the model, model
attributes, attachments, and any model output or items used to create the model.
Backchecker: The individual who responds to the checker’s comments. This person generally is
the originator but can also be someone else. The backchecker cannot be the checker.
Updater: The individual who updates the model per comments. Typically this person will be the
originator of the model. This individual can also be the updater.
Verifier: The individual responsible for verifying the checker’s comments have been properly
addressed. This person is generally the checker but can also be someone else. The verifier
cannot be the updater.
Procedure and Approach for Internal Design Check
Upon completion of model authoring, the model originator will provide the checker with .dgn files
and calculations for the corresponding model elements. The checker will then check the model
against the calculations. A checklist is used to guide and document the check of the model
geometry and attributes for each element. Checklists have been provided in the Appendix,
Section 7.6.6. The checklist includes sections for each element and associated attributes,
including identification of the design data relevant for the specific element. The checklist is
developed by the originator to aid in model development and QC. The checker will verify each
element in the model is geometrically correct with the appropriate design data associated to
each element; will use the completed calculations for each element to verify compatibility; and
will review the model for overall completeness and constructability. Notes and comments can be
added to each element in the checklist. The checker will provide positive verification of
completing the check by either initialing each element in the checklist or similar. The checked
model files will be returned to the originator to address any comments and/or corrections. Once
the originator has addressed the comments, the originator/updater will update the model as
necessary and initial the checklist to indicate the revisions have been made and/or comments
have been addressed. The model and checklist are then returned to the verifier to verify all
comments have been addressed and can be closed.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-25 Design
Procedures and Approach
Checklists must be developed to document the checking process. The checklist includes
sections for each element and associated attributes, including identification of the design data
relevant for the specific element. The checklist can be developed by the originator to aid in the
model development. The checker will verify each element in the model is geometrically correct
with the appropriate design data associated to each element; will use the completed
calculations for each element to verify compatibility; and will review the model for overall
completeness and constructability.
Review Meetings
Previous MBDC structures projects have used the same method to perform UDOT reviews. The
following approach is provided not to specify it is the only method to perform these reviews, but
rather to show how the method has been used to date.
Perform review meetings by reviewing the 3D model using Bentley OpenRoads Navigator
(ORN) and the model attachments using Bluebeam review sessions. Comments in the
Bluebeam review sessions can then be exported out in the tabular format for documentation.
Review comments are created in ORN by generating an issue. Issues are stored in the Bentley
CONNECT project cloud and exported into a report. As each comment is generated and a
response is provided, team members can assign the issue to the next individual responsible for
closing out the comment. For more information on performing reviews within Bentley and
Bluebeam, see Model Review Training Documentation in Appendix Section 7.5.
5.4 SUBSURFACE UTILITY MODELING CONSIDERATIONS
ORD has the capability to dynamically model subsurface utility networks and perform hydrologic
and hydraulic calculations for drainage analysis and design. This section introduces subsurface
utility modeling and tips for producing subsurface MBDC deliverables in ORD. It also documents
current difficulties in attempts to model subsurface utilities in ORD and provides a list of
advantages and disadvantages of using ORD versus InRoads Storm and Sanitary to design and
deliver a MBDC project.
5.4.1 Subsurface Utility Modeling
Getting Started
Always start a DGN for a utility model from the 2D project seed file. Rename the default model
space prior to placing any utility features, as renaming the model space will cause file
synchronization problems. See Appendix Section 7.1 for file and model naming convention.
ORD includes subsurface utility modeling tools that are accessed by selecting the “Subsurface
Utilities” in the workflow dropdown box, as shown in Figure 5.6.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-26 Design
Figure 5.6 – ORD Subsurface Utilities Workflow
OpenRoads Designer licensing allows for the creation and attribution of storm and sewer
networks of up to 100 nodes using the StormCAD hydraulics engine. The StormCAD routine
only supports the rational method peak flow hydrology analysis. If the model requires more than
100 nodes or dynamic flow routing of hydrographs it will be necessary to activate the
appropriate hydraulic software. License activation can be found in the “Tools” menu ribbon of
the “Subsurface Utilities” Workflow, as shown in Figure 5.7.
Figure 5.7 – Activate Hydraulic Software in ORD
To create subsurface utilities, use the layout menu within the layout tab, as shown below in
Figure 5.8.
Figure 5.8 – Layout Subsurface Utility Features
The first time a layout tool is activated a window will pop up asking to proceed with creating a
utility model, as shown in Figure 5.9.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-27 Design
Figure 5.9 – Create Utility Model
When you click “Yes” a 3D model will be created where the 3D utility graphics will be displayed
and updated as new features are created and deleted or edited in the utility database.
Workspace
The workspace is required to include the variable SUDA_SEED_FILE or
SUDA_SEED_MODEL, otherwise a utility model cannot be created, and the error shown in
Figure 5.10 will appear.
Figure 5.10 – Workspace Error
Model Based Design and Construction (MBDC) Guidelines June 2019
5-28 Design
The UDOT standard workspace includes many existing and proposed utility feature definitions.
Created feature definitions can be browsed using the “Explorer” window under the OpenRoads
Standards tab shown in Figure 5.11. Any features not included will need to be set up in a project
.dgnlib file.
Figure 5.11 – OpenRoads Standards Tab
The current UDOT workspace does not include hydraulic prototypes associated with feature
definitions. Hydraulic prototypes consist of the hydraulic properties needed for hydraulic
analysis (i.e., grate type, pipe roughness coefficient). However, the hydraulic properties can be
set individually in the hydraulic properties dialog or in a batch using flex tables.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-29 Design
Database Management Features
ORD includes features and tools that are helpful in reviewing and managing the utility model
data. The “Subsurface Utilities Model” tab in the “Explorer” window, as shown in Figure 5.12,
allows for selection, deletion, zoom to, and other commands. Utility profile runs are also created
and managed in this tab.
Figure 5.12 – Subsurface Utilities Model Tab in Explorer
ORD also has the ability to view, batch edit, and customize the utility database in a table format
using flex tables. User defined attributes can be added to the database. Utility attributes such as
pay item information can be used instead of using Item Types. The utility properties that are
published to i-models can be specified using the i-model configuration command in ORD.
Model Based Design and Construction (MBDC) Guidelines June 2019
5-30 Design
5.4.2 ORD Issues
Current attempts to model and design subsurface utilities and hydraulics in ORD have proven
the software tools are not as developed or stable as roadway modeling tools in ORD. Modeling
of non-hydraulic subsurface utilities has been more successful than storm drain sewers that
require hydraulic or hydraulic analysis. It is recommended that files containing SUDA hydraulic
data are backed up often. It is also recommended to “Synchronize Drawing” frequently to
prevent the .dgn drawing to stay synchronized with the database, which has been identified as
one cause of difficulties.
Figure 5.13 – Synchronize Drawing to Subsurface Utilities Database in ORD
If SUDA is chosen, make sure the schedule and budget include time for file troubleshooting,
backup recovery, and support coordination with Bentley. Alternatively, a MBDC project can be
delivered using Legacy InRoads SS2 Storm and Sanitary if the budget and schedule do not
allow for use and testing of ORD. Figure 5.14 outlines the current advantages and
disadvantages to a SUDA vs. Storm and Sanitary workflow in the context of MBDC projects. If
Storm and Sanitary is chosen then the storm drain modeling files are to be delivered including
database (.sdb), drainage structure (.dat), and preference files (.xin).
Model Based Design and Construction (MBDC) Guidelines June 2019
5-31 Design
ORD SUBSURFACE UTILITIES (SUDA)
Advantages Disadvantages
3D model updates automatically Software is unstable, leading to file corruption
Better interface with roadway ORD
models
Lost work time redoing modeling or working from
backups
UDOT ORD workspace includes feature
definitions and 3D cells for most
drainage structures
Automatic updating can make initial layout slower
STORM AND SANITARY INROADS SS2
Advantages Disadvantages
Software stability and performance 3D model is not automatically updated
Familiar workflow Need to redisplay 3D elements after a change is
made to the storm drain database (.sdb) file
Requires converting proposed roadway terrain
models to .dtm file for design and profile production
Does not have a UDOT standard preference file
(.xin) and drainage structure file (.dat) to
automatically display pipes with correct symbology
3D cells are not as detailed as UDOT cells created
Figure 5.14 – ORD Subsurface Utilities vs. Storm and Sanitary Advantages and
Disadvantages
Model Based Design and Construction (MBDC) Guidelines June 2019
6-1 QC/QA
CHAPTER 6
Quality Control (QC) / Quality Assurance (QA) and Milestone Design Reviews
6.1 MBDC QC/QA INTRODUCTION
A commonly asked question during MBDC discussion is, “How do you check the models?”
Historically models have not been checked directly as a primary QC effort, but rather the design
is verified as it is represented in the 2D plans, profiles, and cross sections. Digital Delivery
requires a fundamental shift in thinking about the QC process. The ultimate goal of an MBDC
project is to provide detailed and complete models so that all reports, i-models, and other
published formats that are generated from the original design models are correct and accurately
communicate the designer’s intent.
Fundamentally, the reviewer’s effort must address these two questions:
• Does the proposed design intent meet the agency’s design standards?
• Do the delivered models accurately and completely reflect the designer’s intent?
6.2 PURPOSE
The purpose of UDOT QC/QA Procedures is not different for an MBDC project. The goal of the
UDOT QC/QA Procedures is to assist the project team to create and deliver safe, economic,
quality, and constructible designs. However, digital delivery projects require significant
modifications to the existing procedures.
6.2.1 Alternative QC/QA Procedure Form
The alternative QC/QA Procedure Approval Form will be required for all MBDC projects and can
be found here: https://www.udot.utah.gov/main/uconowner.gf?n=20526518777114403. The
intent of this form is to describe the QC/QA procedure and show that it is equal to or better than
the standard UDOT QC/QA procedure.
6.3 QC DOCUMENTATION
6.3.1 QC/QA Checklists
QC/QA checklists are required and important tools for an MBDC project. Appendix 7.6 includes
MBDC checklists for design activities that are different for an MBDC project and are required in
place of the standard design activity checklists.
6.3.2 Model QC Expectations
Models submitted as deliverables must be checked and accompanied by all support
documentation (i.e. horizontal and vertical geometry, quantity reports, spreadsheets, hand
Model Based Design and Construction (MBDC) Guidelines June 2019
6-2 QC/QA
calculations, software input/output reports, etc.) in accordance to UDOT and Project
Procedures.
6.3.3 DGN Model QC
The QC of a DGN model can be accomplished in a similar procedure to a sheet check using
colors and QC levels, as shown in Figure 6.1. The check print stamp and notes are drawn in a
copy of the QC-ready design model. Additionally, a version of the corrected model design files
will need to be saved for documentation and auditing. Drafting and storing documentation in a
DGN file requires that QC personnel have access to design and modeling software
(MicroStation, ORD) and sufficient skills to operate.
Figure 6.1 – Check Print and QC Legend in DGN
Figure 6.2 and Figure 6.3 show an example of a DGN QC procedure used.
Figure 6.2 – Drainage QC DGN, Geometry Review
Model Based Design and Construction (MBDC) Guidelines June 2019
6-3 QC/QA
Figure 6.3 – Drainage Corrected DGN, Geometry Review
6.4 ROADWAY MODEL QC NOTES
Modeling Components Meshes – Modeling components meshes must be checked for
completeness and accuracy. As the project nears the final design condition, additional focus
and review of the detail modeling areas will be necessary. Ultimately, if every component mesh
has not been reviewed independently from top, bottom, and sides for accuracy and fidelity to the
design intent, then the models cannot be considered checked.
3D Breakline File(s) – Regardless of how well the MBDC project is modeled it will still be
necessary to create, clean up, and curate a set of 3D breaklines that the contractor can use to
generate/import design surfaces into their construction and surveying applications. Once a
surface is saved or exported from the native design application, the original triangulation is
compromised. The surface will likely not present or triangulate the same way in applications
used by contractors and surveyors. To deliver a proper set of 3D breaklines, the modeler must
thoroughly review, trim, and prepare these files to account for Delaunay’s and other
triangulation issues. These files are the most critical for the contractor to leverage AMG and
estimate and stage the earthwork needs. Thus, particular focus on the quality and accuracy of
these lines is paramount.
Section 5.2, Roadway Modeling Considerations, offers tips and suggestions related to the
modeling approach and checking. The EOR is responsible to ensure completeness of the QC.
Model Based Design and Construction (MBDC) Guidelines June 2019
6-4 QC/QA
6.5 MILESTONE REVIEWS
Prepare a plan for how submittals will be reviewed. The plan needs to accommodate time for
testing and possible implementation of new or improved software. The design team will
schedule with each discipline reviewer a time at the beginning of the review phase to discuss
the following:
• How the design model is being displayed
• What models and levels organization are expected
• Design assumptions and intent
• Attributes, details, attachments, and design notes
• What information is 3D and what is 2D
Figure 6.4 on the following page and the video found here show an example of the milestone
review process. The design team will provide all documentation needed to the review team in
the form of a federated design review model and any additional information per the Project
Delivery Network (PDN). Review comments will then be provided to the design team and a
review meeting will be held. See Appendix Section 7.5 for a detailed guide on providing
comments within Bluebeam and Bentley Navigator.
Model Based Design and Construction (MBDC) Guidelines June 2019
6-5 QC/QA
Figure 6.4 – Milestone Review Process Diagram
Model Based Design and Construction (MBDC) Guidelines June 2019
7-1 Appendix
CHAPTER 7
APPENDIX
7.1 DGN FILE AND MODELS NAMING CONVENTION
FILE NAME MODEL SPACES AND NAMES
[PIN]_Alignment.dgn Alignment
Alignment-3D
[PIN]_ATMS.dgn ATMS
ATMS-3D
[PIN]_Communications.dgn Communications
Communications-3D
[PIN]_Details.dgn Details
[PIN]_Electrical Electrical
Electrical-3D
[PIN]_Erosion_Control.dgn Erosion Control
Erosion Control-3D
[PIN]_Exrow.dgn Preconstruction Right of Way
[PIN]_ExSignals Existing Signals
Existing Signals-3D
[PIN]_Extopo.dgn Preconstruction Survey
Preconstruction survey data
Existing Terrain Model(s)
[PIN]_Exutil.dgn Existing Utility Locating Data and
Survey
[PIN]_Exutil_Communications.dgn Existing Communications
Existing Communications-3D
[PIN]_Exutil_Electric Existing Electric
Existing Electric-3D
[PIN]_Exutil_Gas.dgn Existing Gas
Existing Gas-3D
[PIN]_Exutil_Sewer.dgn Existing Sewer
Existing Sewer-3D
[PIN]_Exutil_Water.dgn Existing Water
Existing Water-3D
[PIN]_Gas.dgn Gas
Gas-3D
[PIN]_Hydro.dgn Drainage
Drainage-3D
Drainage Profiles
Drainage Details
Model Based Design and Construction (MBDC) Guidelines June 2019
7-2 Appendix
FILE NAME MODEL SPACES AND NAMES
Drainage Removals
[PIN]_Landscaping.dgn Landscaping
[PIN]_Lighting.dgn Lighting
Lighting-3D
[PIN]_MOT.dgn Maintenance of Traffic
[PIN]_Removals.dgn Removals
[PIN]_Roadway_Design.dgn 2D Roadway Design
2D Roadway Design-3D
[PIN]_Roadway_Model_[Segment].dgn Model[Segment]
Model[Segment]-3D
Template_Switches
[PIN]_ROW.dgn Design Right of Way
[PIN]_Sewer.dgn Sewer
Sewer-3D
Sewer Profiles
[PIN]_Signals.dgn Signals
Signals-3D
[PIN]_Signing.dgn Signing
Signing-3D
[PIN]_Striping.dgn Striping
[PIN]_[Structure No]_[OBM/PS_element].dgn Structures
Structures-3D
[PIN]_Typical_Sections.dgn Typical Sections
[PIN]_Water.dgn Water
Water-3D
Water Profiles
7.2 PUBLISHING I-MODELS RESOURCES
The publishing of i-model content is one of the required file(s) to deliver as part of any MBDC
project. Creation of these files allows checkers, reviewers, contractors, and others to open and
access the data rich, 3D geometry in a read-only format on both mobile and web applications.
Creating these files may be unfamiliar to staff who are new to the MBDC process.
Publishing for i-models is found by clicking on the file menu to access the backstage in
OpenRoads Designer, as shown in Figure 7.1.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-3 Appendix
Figure 7.1 – Publishing for i-models Location
Model Based Design and Construction (MBDC) Guidelines June 2019
7-4 Appendix
Once the backstage is open you can select the Publish i-model option to access the publishing
dialog as shown in Figure 7.2 and Figure 7.3.
There are also great resources on YouTube for generating i-models, including this Bentley
video: Bentley's Publishing i-model Series.
Figure 7.2 – Access the
Publishing Dialog
Figure 7.3 – Publishing i-models Dialog
Model Based Design and Construction (MBDC) Guidelines June 2019
7-5 Appendix
7.3 PUBLISHING GIS COLLECTOR FILES
UDOT is developing a workflow and configuration to allow for the use of Feature Manipulation
Engine (FME) to automate the creation of GIS assets from the project CAD data. Below are the
basic steps for preparing CAD files required for GIS conversion on all MBDC projects:
1. QC all base files to ensure the correct working units, global origin, and geographic projection
information are correct
2. Open a blank 2D seed file
3. Reference the specific design file to translate
4. Copy linework in 2D
a. Metadata can be attached or attach metadata after copied in b. Delete any hatching c. Break line strings into complex lines
5. Drop line styles (minus striping and barrier)
6. Drop leader lines and text (if text does not translate to GIS, use metadata)
7. Simplify geometry to lines as much as possible; if the intent is to be represent CAD data as
shapes or polygons in GIS, make sure that each individual geometry in CAD is an enclosed
shape. Further, do not hatch or pattern any of these shapes. Improperly closed geometry
and hatch and pattern definitions lead to significant challenges during translations to GIS.
8. Copy in the 2D representation of 3D cells
9. Eliminate reference files/saved views/levels turned off (all data comes through)
7.4 PUBLISHING MODEL BASED DESIGN FILES TO PROJECT EXPLORER
There are a number of important steps to be followed as part of the attribution (in ProjectWise)
and delivery of MBDC project files. This section provides guidance notes for project teams.
7.4.1 Steps to be Completed by the Designer
Step One – Attribute Original files (Designer)
1. Select file and press the space bar to open the document properties window
2. Select Attributes tab (1)
3. Set Submit to Electronic Plan Room attribute to either:
a. MBDC FIO – For files to be used for information only (i.e .imodel, .xml, .dtm, .alg, etc. on MBDC projects or any file provided to contractors on a non-MBDC project)
Model Based Design and Construction (MBDC) Guidelines June 2019
7-6 Appendix
b. MBDC Legal – For files that are legal documents (i.e. .dgn file containing 2D and/or 3D models)(2)
4. Click Save (3)
NOTE: The interface shown is for Roadway. Although the interface will vary for each discipline,
the attributes for the advertising process are the same and are available in the respective
interfaces.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-7 Appendix
Tips and Tricks: Verify if files are attributed correctly by entering a file extension in the Quick
Search field and setting the View to Advertisement. This view will list the Submit to Electronic
Plan Room for all files that meet your search criteria, as shown in the following example.
Step Two – Copy files for MBDC Publishing (Designer)
IMPORTANT: This step involves using a Saved Search to find and create a list of the all MBDC
FIO and MBDC Legal files in the project folder. If the Submit to Electronic Plan Room attribute
was not applied to the original document(s), the saved search will not accurately find and report
a list of the document(s) to be published because the search is dependent on those attributes.
In preparation to copy files, expand the \Construction\Advertising folder. In the next steps you
will copy files to the MBDC for Publishing folder.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-8 Appendix
1. From the Saved Searches folder in the project, click on the Global>Advertisement>MBDC
Files saved search (1).
2. Select all the documents from the document list view
3. Drag the files to the \Construction\Advertising\MBDC for Publishing folder and release
the left mouse button. This should copy the files from their original location.
4. If the Select a Wizard dialog appears, select No Wizard and OK
Model Based Design and Construction (MBDC) Guidelines June 2019
7-9 Appendix
5. If any of the selected documents have versions, select No when prompted to copy the
versions
6. Click on the MBDC for Publishing folder and verify the files were copied and the files have
the correct attributes. This folder defaults to the Advertisement view so the attributes
should be listed as columns for easy review.
NOTE: The MBDC for Publishing folder is a holding place for advertising files until they can be
posted at the correct time by Construction Advertising.
Step Three – Run Scan References and Link Sets…on MBDC for Publishing folder (Designer)
IMPORTANT: The next two steps (Steps Three and Four) are performed to restore the
referencing of MicroStation files when the file names are changed. It is mandatory that these
steps be done in the proper order so ProjectWise can establish the referencing before the name
is changed.
1. Right-click on the MBDC for Publishing folder and select Scan References and Link
Sets… (1)
Model Based Design and Construction (MBDC) Guidelines June 2019
7-10 Appendix
2. The Scan Reference Files and Link Sets Wizard opens. Click Next>.
3. In the Specify Scan Options dialog, toggle on the Scan for master and referenced
documents (1) and Scan for DGN Link Sets (2) options. Click Next>.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-11 Appendix
4. In the Select Master Files and Folders dialog, place a check in the box next to the folder you
want scanned (1). Click Next>.
5. In the Master Folder Settings dialog, scroll down and select MicroStation (1) as the desired
Application Type for filtering the master files. Click Next>.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-12 Appendix
6. In the Reference File Priority Search Options dialog, leave the Enable Priority Search
option toggled off and click Next>.
7. In the Reference File Proximity Search Options dialog, ensure that the Master File’s Folder
option is selected as the Start Location (1). Click Next>.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-13 Appendix
8. In the Reference File Search Options dialog, choose a location and file name for the log file
by choosing the Browse… button. Click Next>.
9. In the Scan References and Link Sets Wizard configuration is complete dialog, click Scan to
start the scanning process.
10. In the Scanning for References and Link Sets…Done dialog box, click on the View Log box
to open the log file for evaluation of the scanning results. Search for errors to see what
reference files were missing in the search. Attribute and copy (Step One and Two) into the
MBDC for Publishing folder any reference files that are missing and needed. Re-run this
step to get all files corrected. Click Close when done.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-14 Appendix
Step Four – Rename documents in the MBDC for Publishing folder (Designer)
IMPORTANT: This step is only to be done when all MicroStation files have been scanned for
referenced files in the MBDC for Publishing folder (all other file types can be renamed at any
time).
1. Select the \Construction\Advertising\MBDC for Publishing folder
2. Select all the documents from the document list view that need to be renamed, excluding
documents that have multiple file extensions (ie. document.icm.dgn, document.i.dgn,
file.tar.gz). Documents that have multiple file extensions will need to be renamed individually
using the Rename… option.
3. Right-click on the selection and choose Modify… (1)
Model Based Design and Construction (MBDC) Guidelines June 2019
7-15 Appendix
4. In the Modify documents dialog, ensure the Document Name: lock is toggled on and select
the expansion arrow next to the lock (1). Choose the Document File Name option from the
expanded list (2).
Note: “Document Name” is not the same as “Document File Name” and will give different
results.
5. Continuing in the Modify documents dialog, add the _ADV (1) text to the Name: field after
the variable text that was added by the Document File Name selection. Click OK (2) when
done.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-16 Appendix
6. Verify the names have been changed correctly with the _ADV added to the name (this
process removes the extension from the document name but it should be correct for the
document file name)
7. Right-click on a MicroStation file that has references attached and select Set>Show
References (1). Make sure all attached reference files have the new _ADV document
names.
8. A saved search was created for comparing published and original files. From the Saved
Searches folder in the project, click on the Global>Advertisement>MBDC Files for
Publishing Comparison saved search (1). The results of the saved search will show all
documents in the project that have the MBDC FIO and MBDC Legal attributes. With the
project ready for advertisement, you should see pairs of documents (original name and
name with _ADV).
Model Based Design and Construction (MBDC) Guidelines June 2019
7-17 Appendix
NOTE: If a MicroStation file is added after this step has been completed, the reference files for
that MicroStation file need to be manually modified in the file to map to the _ADV files in the
MBDC for Publishing folder.
Step Five – Modifying Files for an Addenda (Designer)
For all files except MicroStation Files
1. Follow Steps One and Two for attributing and moving the documents to the MBDC for
Publishing folder. Follow Step Four for renaming the documents with an _AD## where ## is
a two-digit addendum number (i.e. AD01 for the first addendum).
For MicroStation Files
1. Copy the document(s) that need to be modified from the
\Construction\Advertising\CAD_FIO or the \Construction\Advertising\CAD_Legal
folders. These files have the correct _ADV reference files attached.
2. Once the file modifications are complete, copy the document(s) to the
\Construction\Advertising\MBDC for Publishing folder.
3. Run the Scan References and Link Sets… wizard as described in Step Three but with the
following changes:
a. In the Reference File Priority Search Options dialog, toggle on the Enable Priority
Search option (1), select the \Construction\Advertising\CAD_FIO and
\Construction\Advertising\CAD_Legal folders (2) for the search. Click Next>.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-18 Appendix
b. In the Reference File Proximity Search Options dialog, make sure the Enable
Proximity Search toggle is on and ensure that the Master File’s Folder option is
selected as the Start Location
c. In the Reference File Search Options dialog, set the Search Order to Proximity then
Priority (1).
NOTE: It is important to use this search order since the CAD_FIO or CAD_Legal folder will
contain a document of the same name as the ones being modified for the addendum. With this
search order, the MBDC for Publishing folder will be searched first for the reference
attachment assignment, thus assigning the modified file(s).
4. Rename the files as described in Step Four but using the _AD## format.
5. The Construction Advertising group will move the files when the addendum is ready to be
released.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-19 Appendix
7.4.2 Steps to be Completed by Construction Advertising
Step One – Post Files for Publishing (Construction Advertising)
1. In preparation to copy files, expand the \Construction\Advertising folder. In the next steps
you will move files to the CAD_FIO and CAD_Legal folders.
2. From the Saved Searches folder in the project, select Global>Advertisement>MBDC FIO
Files to Contractor
3. Select all documents in the Document List Window
4. While holding down the left mouse button, press the Shift key. Drag the files to the
\Construction\Advertising\CAD_FIO folder and release the left mouse button. This should
move the files from their original location.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-20 Appendix
5. From the Saved Searches folder in the project select Global>Advertisement>MBDC Legal
Files to Contractor
6. Select all documents in the Document List Window
7. While holding down the left mouse button press the Shift key. Drag the files to the
\Construction\Advertising\CAD_Legal folder and release the left mouse button. This
should move the files from their original location.
8. At this point, the files in the CAD_FIO and CAD_Legal folder will automatically be published
to Project Explorer and be accessible to the Contractor(s).
9. There should not be any documents remaining in the MBDC for Publishing folder at this
point. As addendum files are added, this step would need to be repeated for each
addendum.
7.4.3 Saved Searches Definitions
MBDC Files
• Description: Used by designers to locate documents attributed with the MBDC FIO and
MBDC Legal attributes
• Attributes Searched:
o Submit to Electronic Plan Room-MBDC FIO
o Submit to Electronic Plan Room-MBDC Legal
• Document Restrictions: Only current version
Model Based Design and Construction (MBDC) Guidelines June 2019
7-21 Appendix
MBDC Files for Publishing Comparison
• Description: Used by designers to verify documents attributed with the MBDC FIO and
MBDC Legal attributes have a companion document in the MBDC for Publishing folder
with the _ADV name
• Folders Searched: All project folders except CAD_FIO and CAD_Legal
• Attributes Searched:
o Submit to Electronic Plan Room-MBDC FIO
o Submit to Electronic Plan Room-MBDC Legal
• Document Restrictions: Only current version
MBDC FIO Files to Contractor
• Description: Used by Construction Advertising to move documents attributed with the
MBDC FIO from the MBDC for Publishing folder to the CAD_FIO folder
• Folders Searched: MBDC for Publishing
• Attributes Searched: Submit to Electronic Plan Room-MBDC FIO
• Document Restrictions: None
MBDC Legal Files to Contractor
• Description: Used by Construction Advertising to move documents attributed with the
MBDC Legal from the MBDC for Publishing folder to the CAD_Legal folder
• Folders Searched: MBDC for Publishing
• Attributes Searched: Submit to Electronic Plan Room-MBDC Legal
• Document Restrictions: None
7.4.4 ProjectWise Advertising Naming Convention Resources
To access the ProjectWise Advertising Naming Convention that includes MBDC ProjectWise
attributes for advertising, click the following link: ProjectWise Advertising Naming Conventions
7.5 MODEL REVIEW TRAINING DOCUMENTATION
The tools and methods mentioned in this section are meant to be an example of possible
solutions for Milestone reviews. These methods and programs have been proven to provide the
detail needed for reviews. This section covers 3D project model review and is intended for those
who are responsible for providing comments on project deliverables at interim and final
submittal. This section will provide instruction to the reviewer in the following areas:
• Review process
• Review tools and their basic application
This guide only covers the basic tools necessary for navigation and comment and should not be
used as a comprehensive training manual for the review applications.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-22 Appendix
7.5.1 ProjectWise
All deliverables will be posted to UDOT’s ProjectWise server as directed by the project
manager. Models and documents will be processed and transferred to their respective review
platforms by an individual assigned by the project manager. Comments are not to be posted to
the documents and models in ProjectWise.
7.5.2 Bentley CONNECTED Project
3D models for review and comment will be hosted on the Bentley CONNECTED project site.
Invitations to join the CONNECTED Project will be issued by an individual assigned by the
project manager. Models will be available to all review team members for a set amount of time,
as determined by the project manager. Markups and comments will be collected, sorted, and
cataloged. The results will be made available to the review team, in the standard UDOT
comment resolution form, during the Comment Resolution Meeting.
7.5.3 Bluebeam Studio
All linked documents will be reviewed within a Bluebeam Studio Session. The Bluebeam Studio
Session will be initiated and invitations will be sent to the review team by an individual assigned
by the project manager. Documents will be available to all review team members for a set
amount of time, as determined by the project manager. Markups and comments will be
collected, sorted, and cataloged. The results will be made available, in standard UDOT
comment resolution form, to the review team during the Comment Resolution Meeting.
3D Model Review Links
Bentley Systems
OpenRoads Navigator
• Accessing Models: Bentley CONNECT Portal
• Model Navigation: OpenRoads Navigator
• Review Tools: UDOT Structures Tool chest
Design Document Review
Bluebeam
• Studio Session: Bluebeam Review Session
• Bluebeam Tools: Bluebeam Revu/VU
Process Overview
The following Figure 7.4 flowchart and the video found here outline the process to complete a
design review. Once the 3D model has been completed, documents are broken into two
categories:
• Federated models published to the i-model and attachments
• Reports that can be reviewed in Bluebeam
Model Based Design and Construction (MBDC) Guidelines June 2019
7-23 Appendix
The design files are then published and placed into the appropriate review platform. Once
comments have been provided within the Bluebeam Revu session and Navigator CONNECT, a
comment resolution meeting is held to address all comments. The design team will then
address all comments and organize the model and documents into a report format. If the
structural models and documentation do not need additional revisions and are ready for
advertising, the design review is complete. It is suggested that a digital review training session
with the reviewers be held prior to sending out any documents for review.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-24 Appendix
Figure 7.4 – 3D Model Based Design Review
Model Based Design and Construction (MBDC) Guidelines June 2019
7-25 Appendix
7.6 EXAMPLES OF REVIEW ITEMS AND CHECKLIST
7.6.1 Roadway
• Horizontal Alignment (annotated in the DGN and the i-model)
o Horizontal curves – verify horizontal curve radii meet the design criteria
o Tangents and curves – verify these meet the following:
▪ Horizontal alignment bearings are tied to the existing ROW or the designer
has attributed why the alignment does not tie into the existing ROW
▪ Horizontal alignment location considers where the roadway crown
placement is and avoids placing the crown in the wheel path of a traffic
lane
▪ Alignment has been placed to minimize ROW impacts
o Review the horizontal geometry report from OpenRoads
▪ Geometry report will be attached to the alignment itself or provided as an
attached link in the i-model
• Vertical Alignment (i-model or DGN profile view)
o Minimum/maximum grades – verify grades meet the Project Design Criteria (PDC)
o Vertical curves
▪ K values meet the PDC requirements
▪ Grade breaks to standard or more are connected with a vertical curve
• Typical Sections and/or Cross Sections (typical section PDFs linked in the i-model)
o Components are shown, with the correct widths; verify stations listed on sections
match the design
o Side slopes meet UDOT standards
o Pavement section matches the pavement design report
• Roadway Items (i-model)
o The design meets the project intent
o Roadway pay items are attributed with pay item name, number, and element
information by selecting each individual element
• Grading – Currently the i-model lacks the functionality to sufficiently check the grading
design. It may be necessary to review the contours in the roadway model .dgn files until
Bentley adds additional functionality to the i-model. The following i-model upgrades have
been requested:
o Grading heat map to better show elevation changes
o The ability to turn contours on and off
o A measuring tool to measure slopes from point to point
o The ability to turn on the profile for any 3D line in the i-model
Some designers have used virtual reality (VR) by publishing to Bentley LumenRT to verify the
grading is smooth, particularly on widening projects or for intersection grading, due to the lack of
functionality. By importing the design into LumenRT, the grading can be viewed from different
scales, enabling any dips or anomalies at corners of intersections to be seen more clearly at this
personal scale.
Model Based Design and Construction (MBDC) Guidelines June 2019
7-26 Appendix
7.6.2 Roadway Removals
• Removals (i-model)
o Removal extents are accounted for based on the design
o Removal pay items are attributed with pay item name, number, and element
information by selecting each individual element
7.6.3 Signing and Striping
• Striping (i-model)
o Lane widths – use the measure distance tool to ensure the lane widths and
markings match the design intent
o Tapers – correctly labeled or attributed by the designer
o Striping type (paint, tape, pavement grinding) – correctly labeled or attributed by
the designer
• Signing (i-model)
o New signs
▪ Verify attributes by selecting each sign and check to make sure sign size,
MUTCD code, post type, and foundation type are attributed correctly
▪ Verify the correct 3D sign post/foundation cell has been attached to the
correct surface. Verify from the utility conflict analysis report that the sign
foundations are placed in locations not in conflict with utilities.
o Relocate signs
▪ Existing and proposed locations are attributed on the sign by clicking on
the sign
▪ Each sign is attributed with the MUTCD code, post type, and foundation
type
o Remove signs
▪ Verify signs to be removed are marked visually with a hatching over them
to make them easy to identify in the i-model
▪ Each sign is attributed with the pay item name and number
7.6.4 Drainage
• Drainage (i-model)
o Storm drain pipes meet the drainage design criteria
▪ Capacity, minimum slope, cover, etc.
o Conflicts with existing utilities and other design features are identified
o Pay items are attributed with pay item name, number, and element information
by selecting each individual element
• Erosion Control (i-model)
o Erosion control design is complete
o Erosion control pay items are attributed with pay item name, number, and
element information
Model Based Design and Construction (MBDC) Guidelines June 2019
7-27 Appendix
7.6.5 Utilities
• Existing Utilities (i-model)
o Existing utilities are shown in 3D and attributed
o Utility pay items are attributed with pay item name, number, and element
information by selecting each individual element
o Third party utility design work is shown and not in conflict
7.6.6 Structures
3D Model QC Checklist
This checklist has been used to record the QC process for items within OpenBridge Modeler
and any supporting documents used in the creation of the model or produced from the model.
These checklists are not meant as a template and will not be provided by the Department. They
are only an example of the type of checklist that can be created for internal checking of the
model documents.
• Bridge feature definitions
o Each element in “bridge standards”
o Element templates, levels
• Horizontal and vertical alignment
• Pierline
o Stationing, skew
• Deck placement
o Variable constraint, point control, offsets, feature definition
• Approach slab placement
o Variable constraint, point control, offsets, feature definition
• Beam layout and offsets
• Beam type
o Feature definition, plate or beam sizes
• Cross frames
o Feature definition, locations, basic shape
Model Based Design and Construction (MBDC) Guidelines June 2019
7-28 Appendix
• Stiffeners
o Feature definition, location, basic shape
• Abutments
o Feature definition, elevation constraints, substructure template, location
• Columns
o Feature definition, elevation constraints, substructure template, location
• Sleeper slab
o Feature definition, elevation constraints, substructure template, location
• Piers
o Feature definition, elevation constraints, substructure template, location
• Footings
o Feature definition, template, location
• Wingwalls
o Feature definition, wingwall template, location
• Bearings
o Feature definition, location, type
o Cap and girder bearings
• Barrier
o Feature definition, template, location, variable constraint, point control
• Granular backfill borrow
o Feature definition, location
• Curb
o Feature definition, template, location, variable constraint, point control
• Drainage
o Feature definition, location
• Auxiliary
o Feature definition, cell, location
Model Based Design and Construction (MBDC) Guidelines June 2019
7-29 Appendix
• Reports (insert all reports applicable to model)
o Input report (fully checked)
o Quantities
o Elevations from:
▪ Deck
▪ Beam
▪ Bearing seat
▪ Pier/column
• Special considerations for detailing (use this section for items not defined previously
or additional modeling that might be easily missed)
o Look at deck elements, main deck spans, as well as precast panel layouts
o Sleeper slab cutbacks
o Adjustment of caps and sleeper slabs for top elevation
Insert Project explorer tree from OpenBridge Modeler. Every item in the tree must be
checked.
3D BIM Rebar Detailing QC Checklist
As stated for the OBM checklists these tables are meant as an example of the items that should
be checked within the reinforcement models and are not an exhaustive list. It is the
responsibility of the consultant to ensure a completely checked submittal package. It is
suggested to create something similar for internal checking, but different processes can be
used.
MAIN REINFORCEMENT COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material; use E
class steel for all epoxy coatings
Verify spacing used is within limits or
design
Verify correct number of bars have been
modeled
Verify all end conditions, including
standard bend diameters
Check for any clash locations, small
adjustments in field may be more
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule
Model Based Design and Construction (MBDC) Guidelines June 2019
7-30 Appendix
SECONDARY MAIN REINFORCEMENT COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material;use E
class steel for all epoxy coatings
Verify spacing used is within limits or design
Verify correct number of bars have been
modeled
Verify all end conditions including standard
bend diameters
Check for any clash locations, small
adjustments in field may be more
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule
MAIN STIRRUPS COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material; use E
class steel for all epoxy coatings
Verify spacing used is within limits or design
Verify correct number of bars have been
modeled
Verify all end conditions including standard
bend diameters
Check for any clash locations, small
adjustments in field may be more
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule
SECONDARY STIRRUPS COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material; use E
class steel for all epoxy coatings
Model Based Design and Construction (MBDC) Guidelines June 2019
7-31 Appendix
Verify spacing used is within limits or
design
Verify correct number of bars have been
modeled
Verify all end conditions including standard
bend diameters
Check for any clash locations, small
adjustments in field may be more
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule
SEISMIC STIRRUPS COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material; use E
class steel for all epoxy coatings
Verify spacing used is within limits or design
Verify correct number of bars have been
modeled
Verify all end conditions including standard
bend diameters
Check for any clash locations, small
adjustments in field may be more
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule
TEMPERATURE AND SHRINKAGE REINFORCEMENT
COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material; use E
class steel for all epoxy coatings
Verify spacing used is within limits or design
Verify correct number of bars have been
modeled
Verify all end conditions including standard
bend diameters
Check for any clash locations, small
adjustments in field may be more
Model Based Design and Construction (MBDC) Guidelines June 2019
7-32 Appendix
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule
AUXILIARY REINFORCEMENT COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material; use E
class steel for all epoxy coatings
Verify spacing used is within limits or design
Verify correct number of bars have been
modeled
Verify all end conditions including standard
bend diameters
Check for any clash locations, small
adjustments in field may be more
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule
AUXILIARY 2 REINFORCEMENT COMMENTS INITIAL
Description:
Verify reinforcement clearances to all faces
Verify bar size and grade of material; use E
class steel for all epoxy coatings
Verify spacing used is within limits or
design
Verify correct number of bars have been
modeled
Verify all end conditions including standard
bend diameters
Check for any clash locations, small
adjustments in field may be more
appropriate. Verify placement of rebar
around concrete blockouts.
Compare reinforcement bar marks to rebar
schedule