237.14 Electronic Design Data Delivery (BIM Deliverables)

File:237.14.jpg

Operator using GPS grading

MoDOT uses MicroStation for highway and bridge design and drafting. Highway design surveys and road design computations are achieved by using Bentley GEOPAK software. All department drawings are available to the consultant in a Microstation DGN format only. GEOPAK deliverable requirements pertain to road design, preliminary design, and survey projects only. Bridge design projects do not require GEOPAK deliverables.

237.14.1 Specifications of Electronic Design of Contract Plans for Automated Machine Guidance (AMG)

Delivery of electronic design data for the purpose of AMG is required for all MoDOT projects containing cross-sections regardless of size of project or amount of earthwork. The design electronic data used in the development of the contract plans must be submitted along with all other project documents to Design via the ProjectWise document management system.

The following data must be submitted: Contents file, Geopak coordinate geometry database (a.k.a. GPK file), Microstation design master plan drawing, master profile drawing and cross-sectionssurvey control file, 3-D existing ground model, superelevation transitions, 3-D digital design models for proposed finished grade and any alternate models such as the subgrade depicted in the cross-sections, soil report and contents file report.

237.14.1.1 Contents File Report

This document describes all electronic information provided including, but not limited to, coordinate systems and datums used for control survey and design, names and description of coordinate geometry, MicroStation design files, cross-section reports and superelevation transitions. The contents file report may be submitted in pdf format. The file naming convention for this file shall follow guidance in EPG 237.13 File Naming Convention.

Additional Information

125 CADD Services

JSP-05-05 “Electronic Information for Bidder’s Automation”

How to Export a Job Folder for Construction from ProjectWise

Creating Subgrade Tie-in Components

237.14.1.2 Geopak Coordinate Database (a.k.a. GPK File)

This file contains all final alignments used in the development of the contract plans. Alignments include all chains, existing and proposed profiles, control points and any special profiles used for drainage purposes or other design features such as sidewalks, retaining walls, etc. The coordinate geometry file should not contain any preliminary alignments. All geometry contained in the GPK file shall have names representative of the designed alignments and features found in the plans. The coordinate geometry information must be provided in both formats: (1) the native Geopak (*.gpk) format and (2) the LandXML version and (3) InRoads (*alg) format if available.

237.14.1.3 MicroStation Design Files (a.k.a. DGN files)

These MicroStation files contain 2D proposed plan view or cross-section geometry. Plan view geometry includes items such as edges of pavement, shoulders, curbs, gutters, sidewalks, retaining walls or any other feature used in the generation of a 3-dimensional model. Cross-section geometry refers to the master proposed cross-section files (not the cross-section sheets) for all alignments found in the GPK file if applicable. Proposed cross-section files shall include the Geopak cross-section cells, all existing ground lines including subsoil conditions, proposed templates including all pavement, shoulders, curbs, gutters, sidewalks and all other side slope conditions.

237.14.1.4 Existing Ground Model

This 3-dimensional model represents the existing ground conditions as provided by Central Office surveys staff, district survey party or a combination of both. The file is submitted both in the native Geopak TIN and LandXML format. Because control survey is required for any AMG construction method, the district must specify the coordinate system, datum and any project projection factors used to acquire the existing conditions. Coordinate systems, datums and projection factors can be obtained from the originator of the data and shall be documented in the contents file report.

237.14.1.5 Superelevation Transitions

Files containing all transition points showing stationing, cross-slopes, superelevation rates, runoff lengths and runout tangent lengths must be submitted. The superelevation transitions are submitted in ASCII text format as generated using the Geopak superelevation tools. In addition, the district may include the MicroStation pattern-shape file generated using the Geopak superelevation tools.

237.14.1.6 3-D Digital Design Models

Video by Bentley: How to Create Alternate Surfaces for Machine Control (41:45)

One all-inclusive Roadway Designer 3-D design model of the project corridor(s) must be submitted as part of the design data deliverables. At a minimum, these two surfaces should be created: (1) surface representing the proposed finished grade (PFG), (2) surface representing the top of dirt, or top of aggregate (both should daylight to the side slopes).The 3-D Digital Design Models should be submitted in the following formats: Geopak TIN and LandXML and InRoads DTM when available.

237.14.1.7 Final Engineering Design Files

In addition to the 3-D design models, the following final engineering files must be submitted: Bentley’s Corridor Modeler Preference (*.rdp), Bentley’s Roadway Designer Design File (*.ird), and any Bentley’s Roadway Designer Template Library files developed to complete the project (*.itl).

237.14.1.8 Preliminary Geotechnical Report

This is the report provided by the district geologist and it is used for creating the subsurface 3-dimensional model. This file should be in a .pdf format. Subsurface information is included in all contracts with cross-sections (see Sec 102.5.1). For additional information see Release of Subsurface Information.

237.14.1.9 Job Special Provisions

The Job Special Provisions are revisions to the standard specifications and general provisions for an individual project. Like the standard specifications, the JSPs contain information covering work methods, materials, measurements or basis of payment. The JSPs take precedence over all material contained in the bidding documents. JSP 05-05 “Electronic Information for Bidder’s Automation” must be included on every project containing cross-sections.

237.14.1.10 Method of Delivery

The district must submit all electronic design data compressed into one single file using WinZip (or other compression software package) via ProjectWise at the time contract plans and other PS&E documents are submitted. The file shall be placed in the “Contract Plans” folder within ProjectWise. The naming convention for this file shall be [job#]_Electronic_Deliverables.zip. The district is responsible for all QA/QC of the files. Project Manager has the responsibility to ensure all data is accurate and represents the contract plans as signed and sealed.

237.14.1.11 File Naming Convention

All naming convention shall be in accordance to MoDOT’s file naming convention as stated in EPG 237.13 File Naming Convention.

237.14.2 Delivery of Electronic Design Data for Pavement

When available, pavement data shall be considered part of the Electronic Deliverables. The pavement data may include, but is not limited to, the pavement history, coring data and testing data of the existing pavement and subgrade. On a project containing cross-sections, the electronic pavement data shall be included in the same file with the electronic design data for AMG as discussed in EPG 237.14.1.10 Method of Delivery.

237.14.3 Delivery of Electronic Design Data for Project Offices

All electronic highway plan design data for the letting shall be submitted to the appropriate district project office to provide the construction inspectors the necessary data for constructing the project.

This portion of the article details the type of files and the method of delivery to be submitted. The following data must be submitted: contents file report, GEOPAK Coordinate Database (a.k.a. GPK file), existing digital terrain model, 3-D digital design model, Microstation Design files as stated in EPG 237.14.1. In addition, all plan sheets and cross-section sheets in Microstation (DGN) format should be submitted to the project office for preparation of final plans.

Method of Delivery

How to Export a Job Folder for Construction from ProjectWise

Roadway Plans. The project folder shall be exported out of ProjectWise into a district network folder to be transfered to the appropriate project office by district information systems staff. It is advisable to export the entire job folder to ensure that ProjectWise reattaches all reference files. Once the job has been exported, the designer shall remove any files not needed for construction.

Bridge or Structure Plans. Electronic bridge plans will be made available upon request from the project office.

237.14.4 Specifications of CADD Deliverable Contract Plans for Consultants

237.14.4.1 General CADD Requirements

1. The consultant shall furnish to MoDOT all of the contract plan drawings, for an entire project as Microstation drawings (DGN). The consultant is responsible for verifying with MoDOT Design CADD Services for the current software version. All files shall be compatible with MoDOT’s current CADD software version. All associated files that are attached to the drawing such as cell libraries, line definitions, and reference files must be included. The use of Microsoft Excel spreadsheet program can be used to create summary sheets, however, any type of linking between the files to the contract plans is not permitted.

2. All design elements of the project shall be provided to the department in GEOPAK files completed with the MoDOT current version of the software.

3. Each drawing file that is part of the final contract set shall be a full size plan sheet of 22 in. x 34 in. (560 mm x 865 mm) nominal size. All images shall be within a border of 20.375 in. x 31.25 in. (520 mm x 800 mm). The border shall be centered on the plotted page to ensure no part of the drawing is cut off during reproduction. Other than cross-section sheets, there shall be one MicroStation drawing file that corresponds to each sheet of the plan set as submitted. The consultant may provide all cross-section sheets in a single MicroStation file but must reference MoDOT’s border to each individual sheet.

4. The plan drawings shall be to a represented scale. The geometry shall be within a 2D file and consist of vector lines, which can be selected and manipulated. Drawings shall be created in real world modified state plane coordinates at a 1 to 1 scale where applicable and plotted to the represented scale.

5. All drawings shall be self contained or furnished with the supporting library of symbols and details to make the drawings complete in the format provided. MoDOT plots all drawings in a WYSIWYG (What You See Is What You Get) format based upon a MoDOT specific border file attached as a reference file. The department will furnish the appropriate color table through its GEOPAK and MicroStation Drawing Standards internet site. All line style, cells and symbology are applied to the MicroStation drawing and not modified at plot time. Drawings that require specific commercial plotting software to create plots that match delivered contract documents will not be accepted. All drawings must be fully reproducible in black and white. Screening, shading and use of grayscale on plans will not be accepted for final plans delivery.

6. MoDOT will verify the computer drawings using the department’s current version MicroStation and GEOPAK The computer graphic image will be checked against a plotted copy of the drawing furnished by the consultant. All information relating to plotting parameters shall be included in the drawing file. (i.e. weights placed on lines, symbols shown as they should plot.)

7. Drawings shall have a color table meeting department’s standards to simplify the transfer process. MoDOT will furnish the appropriate color table through its GEOPAK and MicroStation Drawing Standards internet site.

8. All drawings shall conform to department drawing standards as shown in this article and the referenced MicroStation CADD Standards manual. The MicroStation CADD Standards Manual is available from the department’s internet site at GEOPAK and MicroStation Drawing Standards. All drawings shall follow the department’s standards for names, numbers of levels, colors and line weights as defined in the appropriate manual. For ease in implementation of these standards, all standard items shown in the above document are selectable from department created MicroStation Settings managers and/or GEOPAK Design and Computation Manager database file (.ddb) that are also available on the department's internet site.

9. Drawings shall be filed in drawing groups or directories with the project number as the name of the parent folder and with file names describing the types of sheet they contain. The MoDOT file naming convention is detailed in EPG 237.13 File Naming Convention.

10. The consultant shall furnish the computer drawings on CD ROM format. All submittals shall consist of two CD ROMs, one shall be labeled "working set" and one set labeled "archive set". In addition the CD ROMs shall contain a contents file report including project name, drawing names, consultant's name and the date of submittal in addition to all the requirements specified in item #1. This file shall be located in the root directory of the disk.

11. Drawing files shall be submitted at the point in which all work covered by the contract is complete. Road project files shall be delivered to the project manager in the district or the project manager's assigned, responsible person in the district where the project is located. Bridge project files shall be delivered to the Structural Liaison Engineer responsible for the project.

12. Copies of MoDOT's format drawings, a copy of the department's standard library of details and the Missouri Standard Plans for Highway Construction are available on the department's internet site. Copies of these files will be supplied in MicroStation DGN format.

13. Payment to the consultant for the computer deliverable will not be made until all of the drawings for the project have met the satisfaction of the department.

237.14.4.2 Specific GEOPAK Requirements

1. All elements representing existing topography features shall be plotted according to the current MoDOT Survey Manager Database (.smd). MoDOT will furnish the appropriate Survey Manager Database through it's GEOPAK and MicroStation Drawing Standards internet website.

2. All survey or photogrammetry information supplied by the consultant and included in the project’s development shall be plotted in a MicroStation drawing file (.dgn). The consultant shall also supply the GEOPAK coordinate geometry database file (.gpk) containing the survey and photogrammetry information. A text file index listing the import data set names, their associated point ranges, and description of the data shall also be supplied for each gpk file. The feature codes used in the survey and photogrammetry information shall conform to the MoDOT standard feature codes as specified in the current MoDOT Survey Manager Database (.smd) file.

3. The consultant shall provide a GEOPAK digital terrain model (.tin) representing the existing ground, and any surface from which original ground sections are derived. A text file index describing the tin model, the name of the file, and the derivation shall be included in the final submittal. (For example, but not limited to staged construction surfaces, existing subsurface material)

4. The consultant shall provide the GEOPAK Design and Computation Manager attributes from the standard MoDOT Design and Computation Manager database (.ddb) at the time of letting.

5. The consultant shall provide a GEOPAK coordinate geometry database file (.gpk) containing all chains, profile, and other elements needed to construct the final plans including but not limited to special ditch profiles, sidewalk profiles, wall profiles, etc. The chains and profiles shall have names pertaining to the items they represent. Documentation of all chains and profiles are to be supplied in the contents report file.

6. When using Geopak shapes to determine superelevation, the consultant shall provide MicroStation drawing file(s) (.dgn) containing such shapes used in deriving the proposed cross-sections. Shapes shall be constructed for driving lanes only. The shoulders are not to be shaped. Dependent and independent shapes shall be plotted in different colors. Superelevation shapes used for the construction of each cross-section file with a different cross-section alignment shall be distinguished either by the shape colors, or by being drawn in a separate MicroStation drawing file.

7. The consultant shall provide all input files used to construct the automated superelevation shapes.

8. If shapes are not the method for determining superelevation, the consultant shall specify the method used for calculating superelevation (e.g. AASHTO Methods, tables or Roadway Designer wizard).

9. Proposed cross-sections for roadway projects shall be designed using Bentley’s Roadway Designer.

10. MoDOT will provide a standard template library and styles file to use with Geopak version of Roadway Designer through the GEOPAK and MicroStation Drawing Standards website.

11. Consultant is not required to use the MoDOT standard template library. However, the consultant shall provide any custom template libraries used as part of the project design. All custom libraries shall conform to the MoDOT standard roadway designer’s styles.

12. The consultant shall submit ALL roadway design files for any project partially or completely designed with roadway designer. Files to be submitted include but are not limited to: the roadway designer preference file (*.rdp), roadway designer project (*.ird), any custom template library (*.itl), triangulated irregular networks (*.tin), digital terrain models (*dtm), roadway designer geometry (*.alg) as well as a Geopak coordinate geometry file (*.gpk).

13. The consultant shall provide MicroStation drawing file(s) with all cross-sections for the project. There shall be a separate cross-section file for each cross-section baseline along which earthwork is computed. The cross-sections in the cross-section file shall exactly match the cross-sections shown in the submitted cross-section sheets file(s), and the cross-sections shown on the submitted contract plans. A GEOPAK cross-section cell shall be present at the proper location for each cross-section in the cross-section file.

14. Cross-sections shall be submitted for but not limited to earthwork sections, entrance sections and superelevation transition sections. Cross-sections used to compute earthwork shall be shown in a separate file or distinguished by a separate pattern line color from all sections not used for earthwork. The superelevation transition sections included shall be at the following locations as described in Standard Plan 203.20 and Standard Plan 203.21: Section A-A (normal crown), Section B-B (0% superelevation), Section C-C (reverse crown) and Section D-D (full superelevation).

15. Earthwork sections and superelevation transition sections shall be perpendicular to the alignment they represent. In areas where alignments meet, and a cross-section crosses more than one alignment, the station value shall be plotted at the location the pattern line intersects the secondary alignment(s).

16. The consultant shall provide cross-section sheets file(s) containing the cross-section information. The cross-sections represented in the cross-sections sheets files shall exactly match the cross-sections drawn in the submitted cross-section file(s), and the cross-sections shown on the submitted section sheets of the contract plans. A maximum of 255 sheets shall be included in the cross-section sheets file. Each sheet shall be within a MoDOT standard border.

17. All GEOPAK Project Manager files and input files used in the development of the plans shall be submitted. The Project Manager files shall be located in the \projdbs directory within the project directory.

237.14.4.3 Specific Requirements for Submittal of Electronic Plans and Design Data

Consultant contracts shall comply with the specifications described in EPG 237.14 Electronic Design Data Delivery and EPG 237.9.6.8 Consultant Designed Projects. In addition to those requirements, the consultant shall provide two additional CD-ROMs. The first CD-ROM shall contain all the files required for Automated Machine Guidance (AMG) construction methods as described in EPG 237.14.1 Specifications of Contract Plans Electronic Design Data for Automated Machine Guidance (AMG). The CD-ROM shall be labeled “Electronic Deliverables for AMG Construction Methods”. The second CD-ROM shall contain all the files required for the MoDOT Project Office as described in EPG 237.14.3 Delivery of Electronic Design Data for Project Offices. This CD-ROM shall be labeled “Electronic Deliverables for Project Office”.