Difference between revisions of "Chapter 2 - Data Requirements"
Wilkersonj1 (talk | contribs) |
Wilkersonj1 (talk | contribs) |
||
| Line 1: | Line 1: | ||
==[[#2.1 Level of Detail Requirements|2.1 Level of Detail Requirements]]== | ==[[#2.1 Level of Detail Requirements|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 [//{{SERVERNAME}}/images_design/a/a5/Project_Data_Requirements_Table.xlsx Project Data Requirements Table.xlsx] 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 RID Review | + | 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 [//{{SERVERNAME}}/images_design/a/a5/Project_Data_Requirements_Table.xlsx Project Data Requirements Table.xlsx] 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 [//{{SERVERNAME}}/images_design/8/8c/RID_Review_Checklist.xlsm RID Review Checklist.xlsm] with justification provided in the Preliminary Comments column. [mailto:MDOT-RIDSupport@michigan.gov MDOT RID Support] will then review the exceptions with the Preliminary Submittal. |
[[File:Project Data Requirements Table.png|700px|thumb|center|Figure 2.1.1: Project Data Requirements Table]] | [[File:Project Data Requirements Table.png|700px|thumb|center|Figure 2.1.1: Project Data Requirements Table]] | ||
Revision as of 09:31, 26 September 2014
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.xlsx 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 RID Review Checklist.xlsm with justification provided in the Preliminary Comments column. MDOT RID Support will then review the exceptions with the Preliminary Submittal.
2.2 Software Requirements
2.2.1 MDOT Workspace
For consistency and uniformity MDOT provides a CAD workspace for free download at the following location:
http://www.michigan.gov/mdot/0,4616,7-151-9625_21540_36037-259870--,00.html
The current workspace is required to be utilized for all MDOT design work.
2.2.2 MDOT Road Design Software Requirements
In order to provide consistent, uniform deliverables MDOT designers must utilize the current MDOT accepted version of Bentley Power GEOPAK (or MicroStation plus GEOPAK equivalent package). This software must be used in conjunction with MDOT’s current Workspace. Refer to Section 2.2.1 MDOT Workspace.
2.2.3 MDOT Bridge Design Software Requirements
-Reserved-
2.2.4 MDOT Drainage and Utility Design Software Requirements
-Reserved-
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 | |
| Photographs | .jpeg |
Table 2.3.1