Difference between revisions of "237.14 Electronic Design Data Delivery (BIM Deliverables)"

From Engineering_Policy_Guide
Jump to navigation Jump to search
(→‎237.14.4 Delivery of Electronic Design Data from Consultants: New details to help consultants deliver plans in an electronic format)
m (→‎237.14.1 Delivery of Electronic Design Data for GPS Grading: Per CADD, file size limitations specified in E 237.14.1.9 and additional file formats provided in E 237.14.1.2)
Line 32: Line 32:
  
 
===237.14.1.2 [http://caddnet/index.php?title=Category:GEOPAK_Road Geopak] Coordinate Database (a.k.a. GPK File)===
 
===237.14.1.2 [http://caddnet/index.php?title=Category:GEOPAK_Road 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.
+
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 two formats: (1) the native Geopak (*.gpk) format and (2) the LandXML version.
  
 
===237.14.1.3 MicroStation Design Files (a.k.a. DGN files)===
 
===237.14.1.3 MicroStation Design Files (a.k.a. DGN files)===
Line 65: Line 65:
  
 
===237.14.1.9 Method of Delivery===
 
===237.14.1.9 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#]_Earthwork_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.
+
The district must submit all electronic design data compressed into one single or multiple files (if file size exceeds 250MB) using WinZip (or other compression software package) via ProjectWise at the time contract plans and other PS&E documents are submitted. No zip file shall exceed 250MB. The file shall be placed in the “Contract Plans” folder within ProjectWise.  The naming convention for this file shall be [job#]_Earthwork_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.2 Delivery of Electronic Design Data for Pavement==
 
==237.14.2 Delivery of Electronic Design Data for Pavement==

Revision as of 07:17, 5 August 2009

Operator using GPS grading

MoDOT uses MicroStation 2004 (v.8.5) for highway and bridge design and drafting. Highway design surveys and road design computation shall be achieved by using the GEOPAK software.

237.14.1 Delivery of Electronic Design Data for GPS Grading

Delivery of electronic design data 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 gemeotry database (a.k.a. GPK file), Microstation design plans and cross-sections, existing ground model, superelevation transitions, cross-section reports, and soil report.

237.14.1.1 Contents File

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 may be submitted in the following formats: ASCII Text, Microsoft Word or Microsoft Excel. The file naming convention for this file shall be as follows:

Additional Information
125 CADD Services
Multi-Line Report
XS-List Report
JSP-05-05 “Electronic Information for Bidder’s Automation”
How to Export a Job Folder for Construction from ProjectWise
Computer Deliverable Contract Plans
[job#]_contents_file.[extension for chosen format]

Examples are:

J0P0928_contents_file.txt
J0P0928_contents_file.doc
J0P0928_contents_file.xls

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 two formats: (1) the native Geopak (*.gpk) format and (2) the LandXML version.

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 Photogrammetry, district survey party or a combination of both. The file is submitted both in the native Geopak TIN format as well as in XML format. Because control survey is required for GPS grading, 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 Photogrammetry or the district survey party chief and shall be documented in the contents file.

237.14.1.5 Superelevation Transitions

File 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 Cross-Section Reports

How to create cross-section reports
Multi-Line Report
XS-List Report

Two Geopak cross-section list reports per master cross-section file must be submitted; one for the existing ground and one for the proposed template. In some instances, a cross-section list report for complex proposed templates is not practical, in which case, the district must submit a Geopak cross-section multi-line report. For help creating these reports contact the CADD Support staff.

For simple cross-sections, create a XS-List Report. For complex cross-sections where you must differentiate between primary and secondary surfaces, create a Multi-Line Report.

237.14.1.7 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.8 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.9 Method of Delivery

The district must submit all electronic design data compressed into one single or multiple files (if file size exceeds 250MB) using WinZip (or other compression software package) via ProjectWise at the time contract plans and other PS&E documents are submitted. No zip file shall exceed 250MB. The file shall be placed in the “Contract Plans” folder within ProjectWise. The naming convention for this file shall be [job#]_Earthwork_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.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 data for GPS grading as discussed in 237.14.1.9 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:

  • MicroStation design files including cross-sections sheets
  • and the existing ground model.

237.14.3.1 MicroStation Design Files (a.k.a. DGN)

The MicroStation design files refer to all project plan sheets and all reference files associated with them as well as all cross-section sheets along with the Geopak cross-section master file. Proposed cross-section master 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. Only final plans as submitted for the letting shall be included.

237.14.3.2 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 for a District Computer Specialist to transfer to the appropriate project office. 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 Delivery of Electronic Design Data from Consultants

Consultant contracts shall continue to be in compliance with the specifications for Computer Deliverable Contract Plans and 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 GPS Grading as described in 237.14.1 Delivery of Electronic Design Data for GPS Grading. The CD-ROM shall be labeled “Electronic Deliverables for GPS Grading”. The second CD-ROM shall contain all the files required for the MoDOT Project Office as described in 237.14.2 Delivery of Electronic Design Data for Project Offices. This CD-ROM shall be labeled “Electronic Deliverables for Project Office”.