Difference between revisions of "Chapter 3 - Standard Naming Conventions"

From MediaWiki
Jump to navigation Jump to search
Line 158: Line 158:
  
 
* M-XXXXXX_PrCorridor_20YY-MM-DD.dgn (MDOT_02 and SS3 Only)
 
* M-XXXXXX_PrCorridor_20YY-MM-DD.dgn (MDOT_02 and SS3 Only)
−
** A 2D DGN file from design which shall contain all the proposed 2D corridor files of the entire proposed project or in logical portions clearly defined in the [//{{SERVERNAME}}/images_design/1/1f/RID_Index.xlsx RID_Index.xlsx] as warranted by the size or complexity of the project. Proposed corridor models created in separate DGN files shall be referenced into one overall file for submittals.
+
** A 2D DGN file from design which shall contain all the proposed 2D corridor and modeling files which represent the entire proposed project or in logical portions clearly defined in the [//{{SERVERNAME}}/images_design/1/1f/RID_Index.xlsx RID_Index.xlsx] as warranted by the size or complexity of the project. Proposed corridor and other design models created in separate DGN files shall be referenced into one overall file for submittals.
−
** 2D corridor files shall contain 3D DGN Models of the roadways and should be free of unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.  
+
** 2D corridor files shall contain 3D DGN Models of proposed project and should be free of unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.  
 
** Corridor  levels shall be consistent with the required level naming convention as shown in the [//{{SERVERNAME}}/images_design/d/df/3D_Model_Surface_Feature_List_SS3.pdf 3D Model Surface Feature List SS3.pdf].
 
** Corridor  levels shall be consistent with the required level naming convention as shown in the [//{{SERVERNAME}}/images_design/d/df/3D_Model_Surface_Feature_List_SS3.pdf 3D Model Surface Feature List SS3.pdf].
  
  
 
* M-XXXXXX_PrLineString_Surf_''Roadway''_20YY-MM-DD.dgn
 
* M-XXXXXX_PrLineString_Surf_''Roadway''_20YY-MM-DD.dgn
−
** A 3D DGN file from design which shall contain the proposed 3D line strings (features) from the top surface of the entire roadway or in logical portions clearly defined in the [//{{SERVERNAME}}/images_design/1/1f/RID_Index.xlsx RID_Index.xlsx] as warranted by the size or complexity of the project.
+
** A 3D DGN file from design which shall contain the proposed 3D line strings (features) from the top surface of the entire project or in logical portions clearly defined in the [//{{SERVERNAME}}/images_design/1/1f/RID_Index.xlsx RID_Index.xlsx] as warranted by the size or complexity of the project.
 
** Each individual side road (greater than 200’ in length) and mainline roadway shall be in separate files.
 
** Each individual side road (greater than 200’ in length) and mainline roadway shall be in separate files.
−
** 3D Line strings should be free from unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations) or anomalies in the side slopes around transitions and radii are acceptable.
+
** 3D Line strings should be free from unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
 
** Line string levels shall be consistent with the required level naming convention as shown in the [//{{SERVERNAME}}/images_design/c/cc/3D_Model_Surface_Feature_List_SS2.pdf 3D Model Surface Feature List SS2.pdf] or [//{{SERVERNAME}}/images_design/d/df/3D_Model_Surface_Feature_List_SS3.pdf 3D Model Surface Feature List SS3.pdf].
 
** Line string levels shall be consistent with the required level naming convention as shown in the [//{{SERVERNAME}}/images_design/c/cc/3D_Model_Surface_Feature_List_SS2.pdf 3D Model Surface Feature List SS2.pdf] or [//{{SERVERNAME}}/images_design/d/df/3D_Model_Surface_Feature_List_SS3.pdf 3D Model Surface Feature List SS3.pdf].
  
  
 
* M-XXXXXX_PrLineString_SubSurf_''Roadway''_20YY-MM-DD.dgn**
 
* M-XXXXXX_PrLineString_SubSurf_''Roadway''_20YY-MM-DD.dgn**
−
** A 3D DGN file from design which shall contain the 3D line strings (features) from the subbase, clay grade or bottom most surface features of the entire roadway or in logical portions clearly defined in the [//{{SERVERNAME}}/images_design/1/1f/RID_Index.xlsx RID_Index.xlsx] as warranted by the size or complexity of the project.
+
** A 3D DGN file from design which shall contain the 3D line strings (features) from the subbase, clay grade or bottom most surface features of the entire project or in logical portions clearly defined in the [//{{SERVERNAME}}/images_design/1/1f/RID_Index.xlsx RID_Index.xlsx] as warranted by the size or complexity of the project.
 
** Each individual side road (greater than 200’ in length) and mainline roadway shall be in separate files.
 
** Each individual side road (greater than 200’ in length) and mainline roadway shall be in separate files.
 
** 3D line strings should be free from unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
 
** 3D line strings should be free from unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
Line 178: Line 178:
  
 
* M-XXXXXX_PrTriangle_20YY-MM-DD.dgn  
 
* M-XXXXXX_PrTriangle_20YY-MM-DD.dgn  
−
** File from design that contains the proposed surface triangle file for the project.
+
** A 3D DGN file from design that contains the proposed surface triangle file for the project.
  
  

Revision as of 07:34, 29 September 2014

This Chapter is a guide as to the format and file naming convention that shall apply to each document that is placed into the RID folder. Clarification for milestone and Computer-Aided Design and Drafting (CADD) naming conventions are also included in this section.

3.1 Prefixes:

A- Alignment
B- Base\Master (overall project files referenced to the sheets)
C- Changes to Letting Files (Addendums, Plan Revisions, etc.)
D- Design (Design based files typically not referenced to the sheets)
E- Environmental
G- Geotechnical
I- Images (Aerial, photos, etc.)
M- Models (3D component, or line string)
R- Reports
S- Survey
U- Utilities (Any utility information not included in the design files)
X- Cross Sections
Z- Miscellaneous (Anything we might have missed or should be included)

3.2 RID

This Section is a guide as to which project documents shall be released as reference information documents (RID) for bidding purposes, and what format and file naming convention shall apply. To apply to projects for any given job number (XXXXXX):

[top of page]

Alignment Files:

  • A-XXXXXX_Align_Roadway_20YY-MM-DD.dgn
    • DGN file from design that contains all project horizontal roadway alignments for mainline and side street alignments. If using POWER GEOPAK SS3 and you have multiple alignment drawings the file names shall be named as stated above. If there are multiple alignments for the same roadway then a number should be added after the word Roadway to differentiate the alignments for example (A-XXXXXX_Align_Roadway1_20YY-MM-DD.dgn). (If using models or multiple alignment scales, include only one set of the project alignments, preferably the alignments at the scale used for the Alignment/ROW Sheets.)
    • Please refer to alignment levels within the Alignments Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to horizontal geometry levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • A-XXXXXX_Align_Supp_Roadway_20YY-MM-DD.dgn
    • DGN file from design that contains all project horizontal roadway alignments for all supplemental design alignments. (If using models or multiple alignment scales, include only one set of the project alignments, preferably the alignments at the scale used for the Alignment/ROW Sheets.)
    • Please refer to alignment levels within the Alignments Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to horizontal geometry levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • A-XXXXXX_Prof_Roadway_20YY-MM-DD.dgn
    • DGN file(s) from design that contains profile information.
    • Please refer to vertical geometry levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to vertical geometry levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • A-XXXXXX_Prof_Supp_Roadway_20YY-MM-DD.dgn
    • DGN file(s) from design that contains supplemental profile information.
    • Please refer to vertical geometry levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to vertical geometry levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • A-XXXXXX_LandXML_Geometry_Roadway_20YY-MM-DD.xml
    • File from design that shall include the alignments (horizontal and vertical) for each roadway (over 200’ in length) in separate files. Side roads under 200’ in length should be included with the mainline roadway.
    • Alignments for other roadway features such as independent ditches, retaining walls, etc. should also be provided if necessary for construction.
    • See the Power GEOPAK Training Videos for more information on creating LandXML Files.

[top of page]

Base/Master Files:

  • B-XXXXXX_Const_20YY-MM-DD.dgn
    • A 2D DGN file from design that contains proposed construction elements. For Projects in SS3 proposed roadwork elements can be referenced from Corridor files for milestone submittals.
    • It is not necessary to merge all proposed design disciplines (i.e. utilities, structures, signals, signing, etc) elements into one DGN. The data can be presented in separate DGN files by disciplines as warranted by the project; however each file must be listed and clearly described in the RID_Index.xlsx.


  • B-XXXXXX_Light_20YY-MM-DD.dgn
    • DGN file from design that contains proposed lighting elements.
    • Primarily used for lighting projects but can be used for projects requiring multiple disciplines.
    • Please refer to the lighting levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to the lighting levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • B-XXXXXX_Sign_20YY-MM-DD.dgn
    • DGN file from design that contains proposed Sign elements.
    • Primarily used for signing projects but can be used for projects requiring multiple disciplines.
    • Please refer to the Signing levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to the Signing levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • B-XXXXXX_Signal_20YY-MM-DD.dgn
    • DGN file from design that contains proposed Signal elements.
    • Primarily used for signal projects but can be used for projects requiring multiple disciplines.
    • This file is intended to be a compilation of all signals for a given project.
    • Please refer to the Signal levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to the Signal levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • B-XXXXXX_ITS_20YY-MM-DD.dgn
    • DGN file from design that contains proposed ITS elements.
    • Primarily used for ITS projects but can be used for projects requiring multiple disciplines.
    • Please refer to the ITS levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to the ITS levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • B-XXXXXX_Drain_20YY-MM-DD.dgn
    • DGN file from design that contains proposed project drainage. Depending on the size of the project, and the design preferences of the project team, the information in this file may be included in the B-XXXXXX_Const_20YY-MM-DD.dgn.
    • Please refer to the drainage levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to the drainage levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • B-XXXXXX_Topo_20YY-MM-DD.dgn
    • DGN file from design that contains existing topographic project data.
    • This file includes topographic project data from surveys, and any existing items moved to a removal, adjust, or relocate level.

[top of page]

Changes Made After Advertisement:

  • C(X-XXXXXX_Original_File_Name)_20YY-MM-DD.dgn
    • Add the Prefix "C-" at the beginning of the original file name to denote a change has been made to the file. Keep the same file name but change the date to reflect the date the change was made only after advertisement. For example CB-XXXXXX_Topo_20YY-MM-DD.dgn.

[top of page]

Design Files:

  • jobXXX.gpk
    • Design (.gpk) file from GEOPAK

[top of page]

Environmental Files:

  • E-XXXXXX_Envir_20YY-MM-DD.dgn
    • DGN file from design that contains existing or proposed environmental drawings.
    • Wetland mitigation drawing
    • Permit information other than that already provided in the project proposal

[top of page]

Geotechnical Files:

  • G-XXXXXX_Geotech_20YY-MM-DD.docx or .dgn format
    • Geotechnical information not provided in plans or proposal.

[top of page]

Images:

  • I-XXXXXX_Bridge
    • Folder containing pictures of bridge elements


  • I-XXXXXX_Drainage
    • Folder containing pictures of drainage elements


  • I-XXXXXX_Roadway
    • Folder containing pictures of roadway elements

[top of page]

Models:

If using GEOPAK SS2 please refer to the 3D Model Submittal Preparation SS2.pdf document for detailed instructions on how to create the following files.

If using GEOPAK SS3 please refer to the 3D Model Submittal Preparation SS3.pdf document for detailed instructions on how to create the following files.

  • M-XXXXXX_PrLineString_Surf_20YY-MM-DD.dgn
    • A 3D DGN file from design which shall contain all the proposed 3D line strings (top surface features) from the entire proposed project or in logical portions clearly defined in the RID_Index.xlsx as warranted by the size or complexity of the project. For Projects in SS3 proposed line string data can be referenced from Corridor files for milestone submittals.
    • 3D line strings should be free of unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
    • Line string levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS2.pdf or 3D Model Surface Feature List SS3.pdf.


  • M-XXXXXX_PrLineString_SubSurf_20YY-MM-DD.dgn
    •  A 3D DGN file from design which shall contain all the proposed 3D line strings (bottom surface features) from the entire proposed project or in logical portions clearly defined in the RID_Index.xlsx as warranted by the size or complexity of the project. For Projects in SS3 proposed line string data can be referenced from Corridor files for milestone submittals.
    •  3D line strings should be free of unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
    •  Line string levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS2.pdf or 3D Model Surface Feature List SS3.pdf.


  • M-XXXXXX_PrCompnt_20YY-MM-DD.dgn (MDOT_01 and SS2 Only)
    • A 3D DGN file from design which shall contain the proposed 3D components of the entire proposed project or in logical portions clearly defined in the RID_Index.xlsx as warranted by the size or complexity of the project
    • 3D components should be free of unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations) or anomalies in the side slopes around transitions and radii are acceptable.
    • Component levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS2.pdf


  • M-XXXXXX_PrCorridor_20YY-MM-DD.dgn (MDOT_02 and SS3 Only)
    • A 2D DGN file from design which shall contain all the proposed 2D corridor and modeling files which represent the entire proposed project or in logical portions clearly defined in the RID_Index.xlsx as warranted by the size or complexity of the project. Proposed corridor and other design models created in separate DGN files shall be referenced into one overall file for submittals.
    • 2D corridor files shall contain 3D DGN Models of proposed project and should be free of unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
    • Corridor levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS3.pdf.


  • M-XXXXXX_PrLineString_Surf_Roadway_20YY-MM-DD.dgn
    • A 3D DGN file from design which shall contain the proposed 3D line strings (features) from the top surface of the entire project or in logical portions clearly defined in the RID_Index.xlsx as warranted by the size or complexity of the project.
    • Each individual side road (greater than 200’ in length) and mainline roadway shall be in separate files.
    • 3D Line strings should be free from unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
    • Line string levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS2.pdf or 3D Model Surface Feature List SS3.pdf.


  • M-XXXXXX_PrLineString_SubSurf_Roadway_20YY-MM-DD.dgn**
    • A 3D DGN file from design which shall contain the 3D line strings (features) from the subbase, clay grade or bottom most surface features of the entire project or in logical portions clearly defined in the RID_Index.xlsx as warranted by the size or complexity of the project.
    • Each individual side road (greater than 200’ in length) and mainline roadway shall be in separate files.
    • 3D line strings should be free from unnecessary gaps in the hard surfaces of the roadway, small gaps (less than 0.2 stations or where civil cells are in use) or anomalies in the side slopes around transitions and radii are acceptable.
    • Line string levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS2.pdf or 3D Model Surface Feature List SS3.pdf.


  • M-XXXXXX_PrTriangle_20YY-MM-DD.dgn
    • A 3D DGN file from design that contains the proposed surface triangle file for the project.


  • M-XXXXXX_LandXML_PrSurf_Roadway_20YY-MM-DD.xml
    • File(s) from design that shall include the proposed surface (for each roadway over 200’ in length) in separate XML files. Side roads under 200’ in length should be included with the mainline roadway.


  • M-XXXXXX_LandXML_PrSubSurf_Roadway_20YY-MM-DD.xml**
    • File(s) from design that shall include the proposed subbase or clay grade surface (for each roadway over 200’ in length) in separate XML files. Side roads under 200’ in length should be included with the mainline roadway.


  • M-XXXXXX_LandXML_PrTriangle_20YY-MM-DD.xml
    • File from design that contains the proposed surface triangle for the project in one XML file.

[top of page]

Reports:

  • R-XXXXXX_Alignment Name_Report_20YY-MM-DD.pdf
    • Alignment Reports containing the alignment report generated from GEOPAK for each alignment within the project.


  • R-XXXXXX_Drain_Report_20YY-MM-DD.pdf
    • Drainage Reports generated containing all drainage calculations.


  • R-XXXXXX_Earth_Report_20YY-MM-DD.pdf
    • Earthwork Reports generated containing all earthwork calculations.


  • R-XXXXXX_Other_Report_20YY-MM-DD.pdf
    • Other Reports as needed for each roadway.

[top of page]

Survey:

  • S-XXXXXX_ControlPts_20YY-MM-DD.txt
    • Copy of the original survey control points and benchmarks delivered for the project in a comma delimited file (ASCII text) of the points included in the Survey Info Sheet shall include the following format (Point Name / Number, Northing, Easting, Elevation, Description). This file should be in its original state and should not contain any changes from design.
    • This file should be placed in the RID folder by the Survey PM at the time the design survey is delivered to the Engineer.


  • S-XXXXXX_Survey_Info_Sheet_20YY-MM-DD.doc
    • Copy of the original Survey Info Sheet in word format. This file should be in its original state and should not contain any changes from design.
    • This file should be placed in the RID folder by the Survey PM at the time the design survey is delivered to the Engineer.


  • S-XXXXXX_ROW_20YY-MM-DD.dgn
    • DGN file from design that contains existing and proposed ROW information.
    • Please refer to boundary levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to boundary levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3


  • S-XXXXXX_ROW_20YY-MM-DD.xml
    • LandXML file from Survey that contains existing Legal or Non-Legal Alignments


  • S-XXXXXX_ExDTM_20YY-MM-DD.tin or S-XXXXXX_ExDTM_20YY-MM-DD.dat
    • Copy of the original survey existing tin file (current standard survey deliverable) or .dat file (previous standard survey deliverable) GEOPAK file delivered for the project design.
    • This file should be in its original state and should not contain any changes from design.


  • S-XXXXXX_ExTriangle_20MM-YY-DD.dgn
    • Copy of the original survey existing surface triangle file delivered for the project design.
    • This file should be in its original state and should not contain any changes from design.


  • S-XXXXXX_Survey_2D_20YY-MM-DD.dgn and S-XXXXXX_Survey_3D_20YY-MM-DD.dgn
    • Copies of the original survey topo files delivered for the project design.
    • These files should be in their original state and should not contain any changes from design.


  • S-XXXXXX_Parcel_20YY-MM-DD.dgn*
    • DGN file from real estate/design that contains project parcel information. This file should be provided by Real Estate or the Real Estate consultant.
    • Please refer to boundary levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to boundary levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.

[top of page]

Utilities:

  • U-XXXXXX_Utility_20YY-MM-DD.dgn
    • DGN file from design that contains underground and overhead utility lines. Typically this information is provided by the utility companies during the life of the project and may be in approximate locations.
    • Please refer to utility line levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to utility line levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.


  • U-XXXXXX_ExUtility_20YY-MM-DD.dgn
    • DGN file from design that contains the existing underground and overhead utility lines (SUE).


  • U-XXXXXX_Sanitary_20YY-MM-DD.dgn
    • DGN file from design that contains the proposed sanitary sewer system.


  • U-XXXXXX_Water_20YY-MM-DD.dgn
    • DGN file from design that contains the proposed water system.

[top of page]

Cross-Sections:

  • X-XXXXXX_XS_Roadway_20YY-MM-DD.dgn
    • Cross-section files from design placed on cross-section sheets.
    • Add station range to the file name if necessary.


  • (X-XXXXXX_XS_Roadway_20YY-MM-DD_310-320.pdf)
    • Please refer to XS levels within the Level Library (mdot_01 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS2.
    • Please refer to XS levels within the Level Library (mdot_02 workspace) for standard levels that would be used within this reference file in Power GEOPAK SS3.

[top of page]

Miscellaneous:

  • Z-XXXXXX_RID_Index_20YY-MM-DD.pdf
    • Index of all items submitted in the RID Folder

[top of page]

Notes:

  • **Not required on overlay projects without wedging or on reconstruction projects without superelevation when all of the strata are a direct offset from the finished surface.

Please Note:

  1. For date, label with the date of original project turn in to the Specifications & Estimates Unit in the format (20YY-MM-DD). Or, in the case of file updates, please use the date of the addendum. The date can be added to the files using Mass Rename. The date will be important for tracking changes that have been made during advertisement. The process for adding updated files to e-Proposal after advertisement will be the same process as the MDOT Notice to Bidder Inquiry process. Add updated files with the appropriate date to the RID area in ProjectWise, include an updated RID_Index.xlsx, and change the state on the additional files. (MDOT Project Managers - See Section 5.2 for directions or contact MDOT RID Support for more information.)
  2. If design files were created with an older MDOT workspace than MDOT’s current workspace, please provide the design files with the appropriate levels from the workspace used to design the project.
  3. If multiple existing topo and TIN files were used on the project they should be merged together or submitted as separate files, clearly defined in the RID_Index.xlsx, clipped (cleaned) such that there is no conflicting data submitted for any project area. Additionally, existing surface anomalies which do not impact the design or construction of roadway do not need to be corrected prior to submittal.
  4. Proposed 3D models of retaining walls and other significant roadway features not directly in the influence of a roadway such as independent ditches can be supplied in separate DGN and LandXML files per the specified file naming convention and clearly defined in the Project Data Summary if warranted.
  5. RID files should be standalone DGN files free of any reference files.
  6. RID Files should be submitted in a compressed (ZIP file named XXXXXX_RID_File_20XX-MM-DD.zip).
  7. Any files generated in design not specifically listed in this document but considered useful for construction, maintenance, or future design should be included in the RID submittal, clearly defined in the RID_Index.xlsx and placed in the Misc Section.

For any questions and clarification please contact MDOT RID Support.

[top of page]

3.3 CADD File Naming Standards

See the MDOT V8i CADD file Naming Standards for the appropriate file names at milestone turn in Cadd_Filenames.pdf.

3.4 Level Library

See the Level Library for a list of levels to be used.

3.5 Supporting Documents

See the Supporting Documents Naming Conventions file for the appropriate file names. This file will be created as part of a future process improvement.


3.6 Milestone Submittals

For the given job number XXXXXX:

Base Plans:

XXXXXX _Road_Base.pdf
XXXXXX _Bridge_Base.pdf
XXXXXX _Proposal_Base.pdf (if applicable)

Preliminary Plans:

XXXXXX _Road_Prelim.pdf
XXXXXX _Bridge_Prelim.pdf
XXXXXX _Proposal_Prelim.pdf (if applicable)
Marked Final ROW
XXXXXX _Road_MFROW.pdf

OEC Plans:

XXXXXX _Road_OEC.pdf
XXXXXX _Bridge_OEC.pdf
XXXXXX _Proposal_OEC.pdf

Final Plan Turn In:

XXXXXX _Road.pdf
XXXXXX _Bridge.pdf
XXXXXX _Proposal.pdf


The maximum pdf file size for any given plan set submittal is 30 MB. If more than one set is needed per package due to size, number sets sequentially. For example:

XXXXXX _Road_OEC1.pdf
XXXXXX _Road_OEC2.pdf


[top of page]

Retrieved from "https://mdotwiki.state.mi.us/design/index.php?title=Chapter_3_-_Standard_Naming_Conventions&oldid=398"