Difference between revisions of "Chapter 2 - Data Requirements"

From MediaWiki
Jump to navigation Jump to search
(Consolidated software requirements into section 2.2.2)
Line 67: Line 67:
 
To further clarify the information provided under the use columns, please see the definitions below.<br>
 
To further clarify the information provided under the use columns, please see the definitions below.<br>
 
Testing = We have started to test the software version.<br>
 
Testing = We have started to test the software version.<br>
Available = We have tested the software for bug fixes and compliance with the MDOT CONNECT Configuration.<br>
+
Available = We have tested the software for bug fixes and compliance with the MDOT CONNECT Configuration. The software can be used in production if tools available in other required software packages are not needed.<br>
 
Piloting = We have developed a working version of the software that is in compliance with the MDOT CONNECT Configuration. Design teams can pilot use of the software and are encouraged to provide feedback.<br>
 
Piloting = We have developed a working version of the software that is in compliance with the MDOT CONNECT Configuration. Design teams can pilot use of the software and are encouraged to provide feedback.<br>
 
Date = The software version is required for use on or after the date specified.<br>
 
Date = The software version is required for use on or after the date specified.<br>

Revision as of 11:26, 25 April 2022

2.1 Level of Detail Requirements

The Reference Information Documents (RID) process will require the inclusion of proposed 3D models for all projects as a general rule. Please refer to the Project Data Requirements Table.pdf document to determine the categories that are required for each project type (Project Description). The table is intended to capture the majority of the projects listed under each project description. At the discretion of the MDOT Project Manager some of the categories or RID files may be excluded based on the project parameters. For exceptions to all RID categories MDOT Project Managers can designated the RID category or File as 'N/A' on the Joint RID Review Checklist and Index.xlsm with justification provided in the Preliminary Comments column. MDOT RID Support will then review the exceptions with the Preliminary Submittal.

To help clarify the intent of when a 3D Model is required the following project types are generally excluded from this requirement:

  • Log projects
  • Standalone bridge projects
  • Mill and fill projects
  • Pavement patching and repair projects
  • Crush and shape projects
  • Projects without survey

Unless:

  • There is wedging, widening, or earthwork for more than 1,000 feet
  • The road elevation changes more than 3 feet
  • The cross slope changes for more than 1,000 feet
  • The superelevation or transition changes
  • The improvements re-grade more than a total of 1,000 feet of ditch
  • The improvements impact ROW
  • The horizontal or vertical alignments change

The above lists are intended to be a starting point to help clarify the 3D Model requirements, and to convey the thought processes used to determine 3D Model requirements. We encourage design teams to provide input as they work through unique and challenging situations.

Figure 2.1.1: Project Data Requirements Table

[top of page]


2.2 Software Requirements

2.2.1 MDOT Workspace

For consistency and uniformity MDOT provides the following two CADD workspaces for free download.

MDOT_02 Workspace

  • This workspace requires Power GEOPAK SS10 or MicroStation SS10 + GEOPAK Civil Engineering Suite SS10.
  • The workspace no longer supports SS3 or SS4.
  • The MDOT_02 Workspace is available for download by consultants at the following link:
MDOT SS10 Workspace Install 2021-01-03
  • The MDOT_02 Workspace install procedure supports the following applications:
a) Power GEOPAK SS10
b) MicroStation SS10 + GEOPAK Civil Engineering Suite SS10
c) Stand-alone MicroStation SS10


MDOT CONNECT Configuration

  • This configuration is required for all new projects started after October 1, 2020.
  • The MDOT CONNECT configuration is available for download by consultants at the following links:
MDOT Connect Configuration - Install Procedure
MDOT Connect Configuration Install 10.09 2021-03-18
  • The MDOT CONNECT Configuration install procedure supports the following applications:
a) OpenRoads Designer CONNECT Edition
b) OpenBridge Modeler CONNECT Edition
c) Microstation CONNECT Edition
  • If you are in the early stages of a project started using the MDOT_02 Workspace and need assistance with upgrading of survey & design data for use with the MDOT CONNECT Configuration, please contact MDOT-CADSupport.

[top of page]


2.2.2 MDOT Design Software Requirements

In order to provide consistent, uniform deliverables MDOT designers must utilize the current MDOT accepted version of Bentley products. Please note that any of the software applications below are compatible with the applicable workspace:

To further clarify the information provided under the use columns, please see the definitions below.
Testing = We have started to test the software version.
Available = We have tested the software for bug fixes and compliance with the MDOT CONNECT Configuration. The software can be used in production if tools available in other required software packages are not needed.
Piloting = We have developed a working version of the software that is in compliance with the MDOT CONNECT Configuration. Design teams can pilot use of the software and are encouraged to provide feedback.
Date = The software version is required for use on or after the date specified.

MDOT CONNECT Configuration General Survey Roadway Drainage Bridge Utilities
MicroStation CONNECT Update 16 (10.16.01.056.exe) Available Available Available Available Available Available
OpenRoads Designer CONNECT 2021 Release 1 (ord10100103en.exe) November 2021 November 2021 November 2021 Piloting November 2021 Piloting
OpenBridge Modeler CONNECT 2021 Release 1 (obm10100085en.exe) November 2021
OpenBridge Designer CONNECT 2021 Release 1 (brges10100026en.exe) Piloting
ProStructures CONNECT Update 5 (ppst10050054en_updt5.exe) Piloting
MDOT_02 Workspace (Legacy)
Civil Suite SS10 (gkste081109918en.exe)
MicroStation SS10 (ms081109912en.exe)
Power GEOPAK SS10 (pgk081109918en.exe)

This software must be used in conjunction with MDOT's current Workspace or Configuration. Refer to Section 2.2.1 MDOT Workspace.

[top of page]


2.3 Digital File Formats

Electronic Data is to be delivered in the following digital file formats:

File Type MDOT Delivered Format
CAD Graphics (2D & 3D) .dgn (MicroStation / Power GEOPAK design file)
Survey Control Coordinate Files ASCII .txt
Alignments (Horizontal and Vertical) .xml
Existing & Proposed Surface Data .xml
Cross Section Data .dgn and .pdf
Reports .pdf
Project PDF submittals (Only for designated Project PDF jobs) .pdf
Removal and Construction Quantity files (Only for designated Project PDF jobs) .kmz
Photographs .jpeg

Table 2.3.1

[top of page]



2.4 Guidelines for Plan Preparation

Ambox move.png
Move proposal : This Section has been moved to Chapter 7 - Plan and Proposal Preparation.


[top of page]