Chapter 3 - Standard Naming Conventions

From MediaWiki
Jump to navigation Jump to search

The Development Guide has moved to a Sharepoint site. New Development Guide

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.

3.1 Prefixes:

A- Alignment
B- Bridge
C- Changes to Letting Files (Addendums, Plan Revisions, etc.)
D- Design (All design based files including all project files referenced to the sheets)
E- Environmental
G- Geotechnical
I- Images (Aerial, photos, etc.)
M- Models (3D component, or line string)
R- Reports
RE- Real Estate
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):


  • XXXXXX_RID_Review.dgn
    • DGN file created by design in the -Supporting Documents > RID Preparation folder by the Plan Review Submittal. This file is intended to reference the working RID files to allow for communication between the design team, MDOT RID Support, and other reviewers.
    • Requires that the working design files are updated in the respective Plan Set folder per the Milestone_RID process.


  • XXXXXX_RID_Survey_20YY-MM-DD.zip
    • The zip files created from survey files in the Pre-Construction folder.
    • If there needs to be more than one .zip file they will be named consecutively as follows: XXXXXX_RID_Survey1_20YY-MM-DD.zip, XXXXXX_RID_Survey2_20YY-MM-DD.zip or in a similar logical format.


  • XXXXXX_RID_Design_20YY-MM-DD.zip
    • The zip files created from design files in the Plan Set folder.
    • If there needs to be more than one .zip file they will be named consecutively as follows: XXXXXX_RID_Design1_20YY-MM-DD.zip, XXXXXX_RID_Design2_20YY-MM-DD.zip or in a similar logical format.


  • XXXXXX_RID_Index.pdf
    • A pdf copy of the Project Summary tab in the RID_Index.xlsm placed separately in the 'RID Documents' folder.
    • If there are multiple .zip files the RID_Index.xlsm will identify which .zip file contains each category on the row for the category name.


  • XXXXXX_RID_Changes_Index.pdf
    • A pdf copy of the Project Changes tab in the RID_Index.xlsm placed separately in the 'RID Documents' folder.
    • This file is only needed for updates/changes after initial publication of RID files related to an Addendum or Plan Revision.


  • XXXXXX_RID_Post_Award_Index.pdf
    • A pdf copy of the Post Award tab in the RID_Index.xlsm placed separately in the 'RID Documents' folder.
    • This file is only needed for files added after Letting as requested by the contractor.

[top of page]

Alignment Files:

  • A-XXXXXX_Align_20YY-MM-DD.dgn
    • DGN file from design that contains all proposed project horizontal roadway alignments for mainline and side street alignments. At the Preliminary Plan milestone the A-XXXXXX_Align_Roadway_20YY-MM-DD.dgn files can be referenced into one file. (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.)
    • This file is not required if the alignments are provided in separate A-XXXXXX_Align_Roadway_20YY-MM-DD.dgn files.
    • 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 horizontal geometry levels within the Level Library (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 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 (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 (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 vertical geometry levels within the Level Library (Cad Standards - Level Groups) for standard levels that would be used within this reference file.


  • A-XXXXXX_Prof_Roadway_20YY-MM-DD.dgn
    • These files are only required when all alignments are not stored in the A-XXXXXX_Prof_20YY-MM-DD.dgn.
    • DGN file(s) from design that contains profile information that makes up the A-XXXXXX_Prof_20YY-MM-DD.dgn.
    • 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 the MDOT_01 workspace.
    • 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 the MDOT_02 workspace.


  • A-XXXXXX_LandXML_Geometry_20YY-MM-DD.xml

[top of page]

Bridge Files:

Bridge files are not currently required as part of the Reference Information Documents (RID) submittal process, When submitted, these files will be provided at Final Turn-In Submittal only.


For Bridge, the bridge type and bridge ID (X) and control section (CS) are used to identify the files.

  • B-XXX_CS_Pr_20YY-MM-DD.dgn
    • 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 (Cad Standards - Level Groups) for standard levels that should be used within this reference file in the workspace.


  • B-XXX_CS_Ex_20YY-MM-DD.dgn
    • 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 (Cad Standards - Level Groups) for standard levels that should be used within this reference file in the workspace.


  • B-XXX_CS_XXXXX_Asbestos Survey Report.pdf
    • A PDF copy of the asbestos survey report for a structure.


  • B-XXXXXX_Existing Bridge Plans.zip
    • A folder containing existing bridge plans that are submitted as PDF files.


[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 C-B-XXXXXX_Topo_20YY-MM-DD.dgn.

[top of page]

Design Files:

  • D-XXXXXX_Const_20YY-MM-DD.dgn
    • A 2D DGN file from design that contains proposed construction elements. For Projects in the 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 RID_Index.xlsm.


  • 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 (Cad Standards - Level Groups) for standard levels that would be used within this reference file in the workspace.


  • D-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 (Cad Standards - Level Groups) for standard levels that would be used within this reference file in the workspace.


  • D-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 (Cad Standards - Level Groups) for standard levels that would be used within this reference file in the workspace.


  • D-XXXXXX_ROW_20YY-MM-DD.dgn
    • 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 (Cad Standards - Level Groups) for standard levels that would be used within this reference file in the workspace.


  • D-XXXXXX_Sign_20YY-MM-DD.dgn
    • DGN file from design that contains proposed Sign elements.
    • Applies to permanent and temporary signage.
    • Primarily used for signing projects but can be used for projects requiring multiple disciplines.


  • D-XXXXXX_SignCAD.zip
    • Zip file from Traffic and Safety/Signage that contains SignCAD files.
    • Applies to permanent and temporary signage.
    • Primarily used for signing projects but can be used for projects requiring multiple disciplines.


  • D-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 (Cad Standards - Level Groups) for standard levels that would be used within this reference file in the workspace.


  • D-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]

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_Images_Structure_Designation
    • Compress to a ZIP file containing pictures of bridge or structure elements


  • I-XXXXXX_Drainage
    • Compress to a ZIP file containing pictures of drainage elements


  • I-XXXXXX_Roadway
    • Compress to a ZIP file containing pictures of roadway elements

[top of page]

Models:

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


[top of page]

MDOT_02 and MDOT_CONNECT Model Files:

  • M-XXXXXX_PrCorridor_20YY-MM-DD.dgn [[Chapter_2_-_Data_Requirements#2.2.2_MDOT_Road_Design_Software_Requirements|]
    • A 3D DGN file from design which shall reference all the proposed corridor and modeling (civil cells, independent ditches, etc) files which represent the entire proposed project or in logical portions clearly defined in the RID_Index.xlsm 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.
    • Corridor files shall reference 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_PrCorridor_Roadway_20YY-MM-DD.dgn
    • The 2D DGN files from design that contain the corridors that make up the M-XXXXXX_PrCorridor_20YY-MM-DD.dgn. If there are multiple corridors for the same roadway then a number, station range, or bound should be added after the word Roadway to differentiate the corridors for example (M-XXXXXX_PrCorridor_Roadway1_20YY-MM-DD.dgn).
    • Corridor levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS3.pdf.


  • M-XXXXXX_PrCorridor_CivilCells_20YY-MM-DD.dgn
    • DGN files from design that contain the civil cells that are included in the M-XXXXXX_PrCorridor_20YY-MM-DD.dgn. If there are multiple civil cell files then a number, roadway, station range, or bound should be added after the word PrCivilCells_ to differentiate the civil cells for example (M-XXXXXX_PrCorridor_CivilCells_I94WB_20YY-MM-DD.dgn).
    • Corridor levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS3.pdf.


  • M-XXXXXX_PrCorridor_Roadway_Super_20YY-MM-DD.dgn
    • 2D DGN files from design that contain the superelevation shapes that are included in the M-XXXXXX_PrCorridor_20YY-MM-DD.dgn. If there are multiple superelevation shape files for the same roadway then a number, station range, or bound should be added after the word Roadway to differentiate the superelevation shape files for example (M-XXXXXX_PrCorridor_RoadwayWB_Super_20YY-MM-DD.dgn).
    • Corridor levels shall be consistent with the required level naming convention as shown in the 3D Model Surface Feature List SS3.pdf.

[top of page]

MDOT_02 and MDOT_CONNECT Model Output Files:

  • M-XXXXXX_PrLineString_Surf_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.xlsm. Linestrings should generally be submitted in a single file. Multiple files may be submitted at the designer's discretion. For Projects in the MDOT_02 workspace, proposed line string data can be referenced from Corridor files for milestone submittals.
    • 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
    • See the Workflow-Creating Model Line Strings and Land XML RID files for additional information on creating this file.


  • M-XXXXXX_PrLineString_SubSurf_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.xlsm. Linestrings should generally be submitted in a single file. Multiple files may be submitted at the designer's discretion.
    • 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
    • See the Workflow-Creating Model Line Strings and Land XML RID files for additional information on creating this file.


  • M-XXXXXX_LandXML_PrSurf_20YY-MM-DD.xml
    • File(s) from design that shall include the proposed top surface from the 3D line strings (export the terrain model to LandXML with features only) in one file.
    • If the project is broken due to gaps in the model data (e.g., a bridge), then separate XML files shall be created for each project area.
    • See the Workflow-Creating Model Line Strings and LandXML RID files for additional information on creating this file.


  • M-XXXXXX_LandXML_PrSubSurf_20YY-MM-DD.xml
    • File(s) from design that shall include the proposed subbase or clay grade surface from the 3D line strings (export the terrain model to LandXML with features only) in one file.
    • If the project is broken due to gaps in the model data (e.g., a bridge), then separate XML files shall be created for each project area.
    • See the Workflow-Creating Model Line Strings and LandXML RID files for additional information on creating this file.


  • M-XXXXXX_LandXML_PrTriangle_20YY-MM-DD.xml
    • File from design that contains the proposed surface triangle for the project in one XML file (Export the terrain model(s) to LandXML with triangles only).
    • If the project is broken due to gaps in the model data (e.g., a bridge), then separate XML files shall be created for each project area.
    • See the Workflow-Creating Model Line Strings and LandXML RID files for additional information on creating this file.

[top of page]

KMZ Quantity Files:

  • Q-XXXXXX_Quantities_Removal_20YY_MM_DD.KMZ - A KMZ file with the layers that represent removal quantities exported to a KMZ file. These are only submitted on jobs that use a Project PDF.


  • Q-XXXXXX_Quantities_Construction_20YY_MM_DD.KMZ - A KMZ file with the layers that represent construction quantities exported to a KMZ file. These are only submitted on jobs that use a Project PDF.


See the Workflow Creating Quantities KMZ Files for RID for additional information on creating this 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:

See Chapter 10 - Deliverables of the Survey Standards of Practice for more information about the Survey RID Files and Standard Naming Convention.


  • S-XXXXXX_ControlPts_20YY-MM-DD.txt
    • Copy of all points listed on the survey info sheet, which includes but is not limited to the original survey control points and benchmarks delivered for the project in a comma delimited file (ASCII text).
    • The information must be provided in 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
    • This document will list all Primary Control, Intermediate Control, and Photogrammetry Target points, Bench Marks, PLSS Corners, and Alignment Points.
    • Each point shall include a Northing, Easting, Elevation, standard deviation (2 sigma) in each coordinate, point scale factor out to 12 significant figures, description of the monument, station and offset and witnesses.
    • The header should outline the company name, month and year of point establishment, datum, geoid used, SPC zone, the formula to convert from grid to ground distances, average combined scale factor, and the horizontal and vertical control points held fixed in the adjustments.
    • Include a list of all the points that may be in danger of being disturbed during construction in a table at the end.
    • This file will be placed in the RID folder by the Survey PM at the time the design survey is delivered to the Engineer.
    • Example Survey Info Sheet


  • S-XXXXXX_Align_ROW_20YY-MM-DD.dgn
    • DGN file from survey that contains existing Legal or Non-Legal alignments, ROW, and parcel information if applicable to the project.
    • The PLSS corners should be connected by lines.
    • 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 (Cad Standards - Level Groups) for standard levels that would be used within this reference file in the workspace.


  • S-XXXXXX_Align_LandXML_20YY-MM-DD.xml
    • LandXML file from survey that contains existing Legal or Non-Legal alignments for the project.


  • S-XXXXXX_ExTerrain_20YY-MM-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.
    • Additional survey should be merged into one existing surface triangle file to provide consistency between design and construction.


  • S-XXXXXX_ExTerrain_LandXML_20YY-MM-DD.xml
    • LandXML file from survey of the original existing surface delivered for the project design.


  • S-XXXXXX_Survey_2D_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.
    • Additional survey should be added into one survey topo file to provide consistency between design and construction.


  • 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.
    • Additional survey should be added into one survey topo file to provide consistency between design and construction.

[top of page]

Utilities:

  • U-XXXXXX_Utility_20YY-MM-DD.dgn
    • 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 (Cad Standards - Level Groups) for standard levels that would be used within this reference file in the workspace.


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


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

[top of page]

Cross-Sections:

  • X-XXXXXX_XS_Roadway_20YY-MM-DD.dgn
    • Please refer to XS levels within the Level Library (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 Section 4.1.2 and 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.
    • At minimum the cross-sections should show grade and slope changes as noted in RDM Section 1.03.04.

[top of page]

Miscellaneous:

  • Z-XXXXXX_File Name_20YY-MM-DD.pdf
    • Any files generated in design not specifically listed above but considered useful for construction, should be included in this category.

[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 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 RID_Index.xlsm, 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 Terrain files were used on the project they should be merged together or submitted as separate files, clearly defined in the 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.
  4. 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 RID_Index.xlsm if warranted.
  5. RID files should be standalone DGN files free of any reference files except as called for in the file names above.
  6. RID Files should be submitted in a compressed (ZIP file named per Section 5.2).
  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.xlsm and placed in the Miscellaneous Section.
  8. The RID_Index.xlsm must be posted as a separate pdf file that is not included in the RID zip files.

For any questions and clarification please contact MDOT RID Support.

[top of page]

3.3 Sheet File and Non-RID File Naming Standards

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

Generally design files that are created and not turned in as part of the RID should not include a letter prefix. They should start with the job number and follow a similar naming convention to the RID or other CADD files. Examples of such files are included below:

  • 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.
    • This file is only used when the parcel information is not included in the A-XXXXXX_Align_20YY-MM-DD.dgn as warranted by the project.
    • This file should not be submitted as part of the RID.
    • Please refer to boundary levels within the Level Library (Cad Standards - Level Groups) for standard levels that would be used within this reference file.

[top of page]

3.4 Level Library

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

The following table includes some of the common Level Terminology used. We have received more inquiries regarding the items in red.

Level Terminology
Abbreviation Description
$ Pay Item
$Cyd Pay item represented by closed shape element with units of Cubic Yards. Uniform depth attached to element using adhoc attribute.
$Ft Pay item represented by linear element with units of Feet.
$IIOCI Pay item that is "Included In Other Contract Items" and formerly referred to as "Incidental" in spec book.
$Sft Closed shape to be used for pay item calculations. Typically created by flooding "Edge" elements.
$SP Pay item requiring Special Provision.
$Sta Station
$Syd Pay item represented by closed shape element with units of Square Yards.
~ Non-plotting level, to be turned off during sheet setup using automated "Sheet View" level filters.
Adhoc Feature to which Geopak Adhoc Attributes are attached, in order to represent multiple vertically stacked pay items (e.g. pavement section, manhole, turf, etc.).
Agg Aggregate
Ali Alignment - Alignment Sheets and non-geometric alignments (Noise Barriers, Culverts, Storm Sewers, Driveways, Paths, Sidewalks, Sanitary Sewer, & Watermain).
All Applies to All features within level group.
Appr Approach paving (turning areas, low volume).
Barr Barrier
CB Catch Basin
ChanDev Channelizing Device
CL Centerline
Conc Concrete
Ct Center
Culv Culvert
Ex Existing
Exc Excavation
Furn Furnish
Geom Geometry - Horizontal geometry (alignments) and vertical geometry (profiles) involving geometric curves for roadway design.
GS Geodetic Survey - Existing survey features collected as part of a ground, photogrammetry, or mobile lidar survey.
HighInt High Intensity
HMA Hot Mix Asphalt
Label Level for placement of sheet labeling information, including Text, Survey Description, Survey Elevation, Cell, Typeline
Label:Cell Cell based label.
Label:Cell-A Abandon cell.
Label:Cell-Adj Adjust cell.
Label:Cell-R Remove cell.
Label:Cell-Rec Reconstruct cell.
Label:Cell-Rel Relocate cell.
Label:Cell-S Save cell.
Label:Desc Description label for surveyed feature.
Label:EL Elevation label for surveyed feature.
Label:Text Text based label.
LM Loose Measure
Lt Left
LU Land Use
MH Manhole
Mod Existing feature to be modified. Appears on both a removal and construction sheet.
Mon Monument
MT Maintaining Traffic / Maintenance of Traffic
NoID Featre collected by surveyors that lacks adequate detail to be placed on a specific level.
NoPlot Non-plotting level.
Oper Operate
Pavt Generic reference to any hard paved surface (HMA or concrete), including travelway, shoulders, sidewalk, etc.
Pr Proposed
Prdctn Production paving (mainline, high volume).
Prof Profile
PvMk Pavement Marking
Rem Existing feature to be removed. Appears only on removal sheet.
Resurf Resurfacing using surface treatments, not rehab.
RPM Raised Pavement Marker
Rt Right
SCS Soil Conservation Service
Struc Structure
Temp Temporary
Terrain Digital "Terrain" Model (DTM)
TravelWay Roadway vehicle lanes. Edge of Pavement is now Edge of Travelway. See "Pavt" for further clarification.
XS Cross Section

[top of page]

3.5 Supporting Documents

See the Supporting_Document_Naming_Convention.pdf for the appropriate file names.

XXXXXX _SupportingDocuments_Milestone.pdf
  • For each milestone submittal include a single pdf of the supporting documents from the -Supporting Documents folder in the respective Milestone folder for review and comment.
  • A pdf of the Supporting Documents is not required at the Final Plan Turn In.

3.6 Milestone Plan and Proposal PDF 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)

FPC Plans:

XXXXXX _Road_FPC.pdf
XXXXXX _Bridge_FPC.pdf
XXXXXX _Proposal_FPC.pdf

Final Plan Turn In:

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

Notes:

  • The PDF plan set page size shall be 11"x17". The PDF proposal page size shall be 8.5" x 11".
  • Please note that the Preliminary ROW submittal is part of the Base Plans, and the Final ROW submittal is part of the Preliminary Plans. See the respective PPMS Task for more information.
  • The maximum pdf file size for any given plan or proposal set submittal is 30 MB. If more than one file is needed per package due to size, number sets sequentially. For example:
    XXXXXX _Road_FPC1.pdf
    XXXXXX _Road_FPC2.pdf


[top of page]

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