Chapter 3 - Standard Naming Conventions - Revision history

BergK1 at 16:01, 24 January 2025

2025-01-24T16:01:01Z

BergK1 at 17:03, 24 April 2024

2024-04-24T17:03:06Z

BergK1: Replaced content with "{{Navbox DSR|Chapter 2 - Data Requirements|Chapter 4 - Developing Electronic Data}} The Development Guide has moved to a Sharepoint site. [https://stateofmichigan.sharepoi..."

2024-04-24T17:01:42Z

Replaced content with "{{Navbox DSR|Chapter 2 - Data Requirements|Chapter 4 - Developing Electronic Data}} The Development Guide has moved to a Sharepoint site. [https://stateofmichigan.sharepoi..."

Show changes

BergK1: /* Alignment Files: */

2024-03-08T13:12:03Z

Alignment Files:

BergK1: /* Bridge Files: */

2024-03-08T13:08:09Z

Bridge Files:

BergK1: /* Design Files: */

2024-03-08T13:06:52Z

Design Files:

BergK1: /* Survey: */

2024-03-08T13:01:31Z

Survey:

BergK1: /* Utilities: */

2024-03-08T12:59:48Z

Utilities:

BergK1: /* Cross-Sections: */

2024-03-08T12:58:47Z

Cross-Sections:

BergK1: /* Notes: */

2024-03-08T12:56:48Z

Notes:

@@ Line 1: / Line 1: @@
 {{Navbox DSR|Chapter 2 - Data Requirements|Chapter 4 - Developing Electronic Data}}
-The Development Guide has moved to a Sharepoint site. [https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide New Development Guide]
+The Development Guide has moved to a Sharepoint site.
-If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov
+If you haven't visited the new site yet contact MDOT-EngineeringSupportTraining@michigan.gov to request access to the Development Guide.

← Older revision		Revision as of 17:03, 24 April 2024
Line 3:		Line 3:

	If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov		If you haven't visited the new site yet, click the link, then click Request Access. You will be added to the Sharepoint Visitors group, and will receive an email with a link to the Development Guide. If you still have access issues, contact MDOT-EngineeringSupportTraining@michigan.gov
−
−
−	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.

@@ Line 65: / Line 65: @@
 ** This file can also include proposed ROW information as warranted by the project.  When ROW is included in this file add '_ROW' after Align in the file name.
 ** The proposed project horizontal roadway alignments may be created as a forward copy from the survey data.
-**Please refer to alignment levels within the Alignments Level Library ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
-**Please refer to horizontal geometry levels within the Level Library ([https://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=e443f12a-8475-438a-904a-7c9f1d9faafd&fileName=MDOT_02_Workspace_2017-07-12.zip MDOT_02 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_02]] workspace.
+**Please refer to horizontal geometry levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.
 *A-XXXXXX_Align_''Roadway''_20YY-MM-DD.dgn
 **These files are only required when all alignments are not stored in the A-XXXXXX_Align_20YY-MM-DD.dgn.
-**DGN file from design that contains horizontal roadway alignments that make up the A-XXXXXX_Align_20YY-MM-DD.dgn.  If using the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_02]] workspace 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_''Roadway''1_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.)
+**DGN file from design that contains horizontal roadway alignments that make up the A-XXXXXX_Align_20YY-MM-DD.dgn.  If 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_''Roadway''1_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 ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
+**Please refer to alignment levels within the Alignments Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file.
-**Please refer to horizontal geometry levels within the Level Library ([https://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=e443f12a-8475-438a-904a-7c9f1d9faafd&fileName=MDOT_02_Workspace_2017-07-12.zip MDOT_02 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_02]] workspace.
+**Please refer to horizontal geometry levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file.
 *A-XXXXXX_Prof_20YY-MM-DD.dgn
 **DGN file(s) from design that contains all profile information.
-**Please refer to profile levels within the Level Library ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
+**Please refer to vertical geometry levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file.

@@ Line 107: / Line 107: @@
 ** A 2D DGN file from design that contains a plan view of the proposed bridge elements (i.e. substructure, foundations, temporary shoring, beams, deck, railing, approaches)
 ** Merge all proposed base files into one DGN file.
-** Please refer to the structure levels within the Level Library ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=cda9e808-0879-4e58-a878-449eaea8d33b&fileName=%22MDOT_02_Workspace_2016-08-26.zip%22 MDOT_02 Workspace])  for standard levels that should be used within this reference file in the MDOT_02 workspace.
+** Please refer to the structure levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups])  for standard levels that should be used within this reference file in the  workspace.
@@ Line 114: / Line 114: @@
 ** A 2D DGN file from design based upon a possible combination of survey, existing plans and engineering judgment that contains a plan view of the existing bridge elements. Provide this file as required based upon the type of work.
 ** Merge all existing base files into one DGN file.
-** Please refer to the structure levels within the Level Library ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=cda9e808-0879-4e58-a878-449eaea8d33b&fileName=%22MDOT_02_Workspace_2016-08-26.zip%22 MDOT_02 Workspace])  for standard levels that should be used within this reference file in the MDOT_02 workspace.
+** Please refer to the structure levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups])  for standard levels that should be used within this reference file in the workspace.

@@ Line 137: / Line 137: @@
 *D-XXXXXX_Const_20YY-MM-DD.dgn
-**A 2D DGN file from design that contains proposed construction elements. For Projects in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_02]] workspace proposed roadwork elements can be referenced from Corridor files for milestone submittals.
+**A 2D DGN file from design that contains proposed construction elements. For Projects in the [https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Software-Requirements.aspx#mdot-connect-configuration MDOT Connect Configuration] workspace 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 [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=44417294-c470-4e39-9da7-0721b0cfc619&fileName=%22RID_Index.xlsm%22 RID_Index.xlsm].
@@ Line 143: / Line 143: @@
 *D-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 D-XXXXXX_Const_20YY-MM-DD.dgn.
-**Please refer to the drainage levels within the Level Library ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
+**Please refer to the drainage levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.
@@ Line 150: / Line 149: @@
 **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 ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
+**Please refer to the ITS levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.
@@ Line 157: / Line 155: @@
 **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 ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
+**Please refer to the lighting levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.
@@ Line 164: / Line 161: @@
 ** DGN file from design that contains proposed ROW information.
 ** This file is only required when the proposed ROW is not included in the A-XXXXXX_Align_20YY-MM-DD.dgn as warranted by the project.
-** Please refer to boundary levels within the Level Library ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
+** Please refer to boundary levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.
@@ Line 184: / Line 180: @@
 **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 ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
+**Please refer to the Signal levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.
@@ Line 191: / Line 186: @@
 **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}}

@@ Line 343: / Line 343: @@
 **The map must show the bearing and distance in the units defined above between adjacent PLSS corners and the distance along the section or quarter section line from the corners to the alignment.
 **A section corner monument and monument box must be observed and noted independently to account for MDOT's Pay Item structure.
-**Please refer to boundary levels within the Level Library ([http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=f95eba59-65d3-436b-aef7-fb04032c573e&fileName=%22MDOT_01_Workspace_2016-08-18.zip%22 MDOT_01 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_01]] workspace.
-**Please refer to boundary levels within the Level Library ([https://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=e443f12a-8475-438a-904a-7c9f1d9faafd&fileName=MDOT_02_Workspace_2017-07-12.zip MDOT_02 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_02]] workspace.
+**Please refer to boundary levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.

← Older revision		Revision as of 12:59, 8 March 2024
Line 377:		Line 377:
	**DGN file from design that contains existing utility information as provided by the utility agencies during the life of the project and may be in approximate locations. Proposed underground and overhead utility lines shall be provided in this file if applicable.		**DGN file from design that contains existing utility information as provided by the utility agencies during the life of the project and may be in approximate locations. Proposed underground and overhead utility lines shall be provided in this file if applicable.

−	**Please refer to utility line levels within the Level Library ([https://~~mdotjboss~~.~~state~~.~~mi.us~~/~~SpecProv~~/~~getDocumentById.htm?docGuid=e443f12a~~-~~8475~~-~~438a-904a-7c9f1d9faafd&fileName=MDOT_02_Workspace_2017~~-07-~~12.zip MDOT_02 Workspace~~]) for standard levels that would be used within this reference file in the ~~[[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements\|MDOT_02]]~~ workspace.	+	**Please refer to utility line levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-groups Cad Standards - Level Groups]) for standard levels that would be used within this reference file in the workspace.

@@ Line 392: / Line 392: @@
 *X-XXXXXX_XS_''Roadway''_20YY-MM-DD.dgn
-**Please refer to XS levels within the Level Library ([https://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=e443f12a-8475-438a-904a-7c9f1d9faafd&fileName=MDOT_02_Workspace_2017-07-12.zip MDOT_02 Workspace]) for standard levels that would be used within this reference file in the [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|MDOT_02]] workspace.
+**Please refer to XS levels within the Level Library ([https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/CAD/SitePages/Levels.aspx#level-usage Cad Standards - Level Usage]) for standard levels that would be used within this reference file in the workspace.
 **Cross-Sections should be provided at all critical stations as noted in [[Chapter_4_-_Developing_Electronic_Data#4.1.2_Preliminary_Plan_Proposed_3D_Model_Requirements|Section 4.1.2]] and [[Chapter_4_-_Developing_Electronic_Data#4.1.3_OEC_and_Final_Plan_Proposed_3D_Model_Requirements|Section 4.1.3]].
 **The cross-section interval shall be determined by the scope of the project.  Generally the maximum interval should be 50 feet.

@@ Line 412: / Line 412: @@
 #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 File Rename''' which can be found in the workspace under MDOT Tools > File Tools > Mass File 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 [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=44417294-c470-4e39-9da7-0721b0cfc619&fileName=%22RID_Index.xlsm%22 RID_Index.xlsm], and change the state on the additional files.  (MDOT Project Managers - See [[Chapter_5_-_RID_Process#5.2_Reference_Information_Documents_.28RID.29_Process|Section 5.2]] for directions or contact [mailto:MDOT-RIDSupport@michigan.gov MDOT RID Support] for more information.)
 #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.
-#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 [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=44417294-c470-4e39-9da7-0721b0cfc619&fileName=%22RID_Index.xlsm%22 RID_Index.xlsm], 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.
+#If multiple existing topo and Terrain files were used on the project they should be merged together or submitted as separate files, clearly defined in the [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=44417294-c470-4e39-9da7-0721b0cfc619&fileName=%22RID_Index.xlsm%22 RID_Index.xlsm], 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.
 #Proposed 3D models of retaining walls and other significant roadway features not directly in the influence of a roadway can be supplied in separate DGN and LandXML files per the specified file naming convention and clearly defined in the [http://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=44417294-c470-4e39-9da7-0721b0cfc619&fileName=%22RID_Index.xlsm%22 RID_Index.xlsm] if warranted.
 #RID files should be standalone DGN files free of any reference files except as called for in the file names above.