237.13 Contract Plan File Name Convention - Revision history

Hoskir: /* 237.13.2 Electronic Design Data */ changed GeoPak to OpenRoads Designer

2024-01-16T17:13:45Z

237.13.2 Electronic Design Data: changed GeoPak to OpenRoads Designer

← Older revision		Revision as of 12:13, 16 January 2024
Line 74:		Line 74:
	==237.13.2 Electronic Design Data==		==237.13.2 Electronic Design Data==

	File naming convention for electronic design data files generated from ~~GEOPAK~~ for Roadway Contract Plans shall be as follows:		File naming convention for electronic design data files generated from MicroStation and/or OpenRoads Designer for Roadway Contract Plans shall be as follows:

	{\| border="1" class="wikitable" style="margin: 1em auto 1em auto"		{\| border="1" class="wikitable" style="margin: 1em auto 1em auto"

Smithk: /* 237.13.1 Design Contract Plans */

2022-06-27T17:29:49Z

237.13.1 Design Contract Plans

← Older revision		Revision as of 12:29, 27 June 2022
Line 2:		Line 2:

	==237.13.1 Design Contract Plans==		==237.13.1 Design Contract Plans==
	The file naming convention for all eProject documents shall begin:		The file naming convention for all eProject documents shall begin with:
	:'''[job#]_[general identification]_'''		:'''[job#]_[general identification]_'''

	The general identification is a description such as “SIMS_FORM”, “WORK_DAY_STUDY”, etc. The only CADD file that is ~~place~~ in eProjects is a zipped Electronic Design Data (EDD) file called Job#_EDD_info.zip. See [[237.14 Electronic Design Data Delivery (BIM Deliverables)#237.14.3.2 Submittal of MoDOT Designed Projects\|EPG 237.14.3.2 Submittal of MoDOT Designed Projects]].		The general identification is a description such as “SIMS_FORM”, “WORK_DAY_STUDY”, etc. The only CADD file that is placed in eProjects is a zipped Electronic Design Data (EDD) file called Job#_EDD_info.zip. See [[237.14 Electronic Design Data Delivery (BIM Deliverables)#237.14.3.2 Submittal of MoDOT Designed Projects\|EPG 237.14.3.2 Submittal of MoDOT Designed Projects]].

	The file naming convention for all Design Contract Plans shall be as follows:		The file naming convention for all Design Contract Plans shall be as follows:

Smithk: /* 237.13.1 Design Contract Plans */

2022-06-27T17:29:06Z

237.13.1 Design Contract Plans

← Older revision		Revision as of 12:29, 27 June 2022
Line 2:		Line 2:

	==237.13.1 Design Contract Plans==		==237.13.1 Design Contract Plans==
	The file naming convention for all eProject documents shall be:		The file naming convention for all eProject documents shall begin:
	:'''[job#]_[general identification]_'''		:'''[job#]_[general identification]_'''

Smithk: /* 237.13.1 Design Contract Plans */ Per EPS, new guidelines to produce a filing convention that is acceptably searchable without bringing undue pressure or constraint upon the districts

2022-06-27T16:27:47Z

237.13.1 Design Contract Plans: Per EPS, new guidelines to produce a filing convention that is acceptably searchable without bringing undue pressure or constraint upon the districts

← Older revision		Revision as of 11:27, 27 June 2022
Line 2:		Line 2:

	==237.13.1 Design Contract Plans==		==237.13.1 Design Contract Plans==
			The file naming convention for all eProject documents shall be:
			:'''[job#]_[general identification]_'''

			The general identification is a description such as “SIMS_FORM”, “WORK_DAY_STUDY”, etc. The only CADD file that is place in eProjects is a zipped Electronic Design Data (EDD) file called Job#_EDD_info.zip. See [[237.14 Electronic Design Data Delivery (BIM Deliverables)#237.14.3.2 Submittal of MoDOT Designed Projects\|EPG 237.14.3.2 Submittal of MoDOT Designed Projects]].

	The file naming convention for all Design Contract Plans shall be as follows:		The file naming convention for all Design Contract Plans shall be as follows:

	'''[sheet#]_[abbreviated sheet type]_[''optional'' sheet# by sheet type]_[job#]_[scale]_[optional description].dgn'''		:'''[sheet#]_[abbreviated sheet type]_[''optional'' sheet# by sheet type]_[job#]_[scale]_[optional description].dgn'''

	''The only acceptable characters will be capital letters, numbers, or an underscore "_". An underscore "_" will be used as a separation between items''		''The only acceptable characters will be capital letters, numbers, or an underscore "_". An underscore "_" will be used as a separation between items''

Smithk: /* 237.13.1 Design Contract Plans */ Per Bid & Contracts, clarified how to name contract plan files when typical sections are not included in the plans

2021-02-17T14:38:04Z

237.13.1 Design Contract Plans: Per Bid & Contracts, clarified how to name contract plan files when typical sections are not included in the plans

← Older revision		Revision as of 09:38, 17 February 2021
Line 8:		Line 8:
	''The only acceptable characters will be capital letters, numbers, or an underscore "_". An underscore "_" will be used as a separation between items''		''The only acceptable characters will be capital letters, numbers, or an underscore "_". An underscore "_" will be used as a separation between items''

	:'''[sheet#]''' is a sequential 3 digit number assigned to each sheet. There are two exceptions to the 3 digit convention:		:'''[sheet#]''' is a sequential 3 digit number assigned to each sheet and should match that of the Index of Sheets of the Title Sheet. There are two exceptions to the 3 digit convention:
	::*First, for sheets #001 through #003, all Title Sheets will begin with the number #001, Typical Section Sheets will begin with #002 and Quantity Sheets will begin with number #003.		::*First, for sheets #001 through #003, all Title Sheets will begin with the number #001, Typical Section Sheets will begin with #002 and Quantity Sheets will begin with number #003. For projects that do not have Typical Sections, the Quantity Sheets will begin with number #002.
	::*Second, for sheets with multiple borders (such as in cross-section (XS) sheets), the naming convention will differ as follows: The type of sheet will be followed by the sheet numbers. The following example shows cross-section sheets 011-015 followed by job #, scale, and optional description: XS_011-015_J0P0928_I5_RP1.dgn. There will be no leading numbers on these file names.		::*Second, for sheets with multiple borders (such as in cross-section (XS) sheets), the naming convention will differ as follows: The type of sheet will be followed by the sheet numbers. The following example shows cross-section sheets 011-015 followed by job #, scale, and optional description: XS_011-015_J0P0928_I5_RP1.dgn. There will be no leading numbers on these file names.
	~~[[image:237.13.1.jpg\|right\|270px]]~~
	:After sheet(s) #003, sequential numbering shall continue with no duplicate numbers. If a sheet (or sheets) need(s) to be inserted, a sequential letter will follow the number (004, 005, 006, 006A, 006B, 006C, 007, etc.). If more than 26 sheets are required to be inserted, the designer should consider renumbering all contract plans from the insertion point forward.		:After sheet(s) #003, sequential numbering shall continue with no duplicate numbers. If a sheet (or sheets) need(s) to be inserted, a sequential letter will follow the number (004, 005, 006, 006A, 006B, 006C, 007, etc.). If more than 26 sheets are required to be inserted, the designer should consider renumbering all contract plans from the insertion point forward.

	:'''[abbreviated sheet type]''' is the 2 lettered abbreviation, identifying a particular kind of sheet (i.e., QU=Quantity Sheet, PP=Plan-Profile Sheet, etc.). These abbreviations ~~are~~ also used in the [[#237.13.6 Index of Sheets\|Index of Sheets]] on the title sheet and must match.		:'''[abbreviated sheet type]''' is the 2 lettered abbreviation, identifying a particular kind of sheet (i.e., QU=Quantity Sheet, PP=Plan-Profile Sheet, etc.). These abbreviations shall be unique and also used in the [[#237.13.6 Index of Sheets\|Index of Sheets]] on the title sheet and must match.

			:'''[''optional'' sheet# by sheet type]''' is an optional 2 or 3 digit number, assigned by a designer, within a particular sheet type (e.g., EC_01, EC_02 would be the 1st and 2nd Erosion Control Sheets).

	:'''[~~''optional'' sheet~~# ~~by sheet type~~]''' is ~~an optional 2 or 3 digit~~ number, assigned by ~~a designer, within a particular sheet type~~ (i.e., ~~EC_01, EC_02 would be the 1st and 2nd Erosion Control Sheets~~).		:'''[job#]''' is the job number as assigned by the district (e.g., J0P0928).

	:'''[~~job#~~]''' is the ~~job number as assigned by~~ the ~~district~~ (i.e., ~~J0P0928~~).		:'''[scale]''' is the scale the MicroStation border was created in for a particular drawing (e.g., I1, I100).

	:'''[~~scale~~]''' is the ~~scale the MicroStation border was created in for~~ a ~~particular drawing~~ (i.e., I1, ~~I100~~).		:'''[optional description]''' is a description added by the designer to quickly identify components of a project that need to be identified (e.g., STAGE1, 54THSTREET, etc.).

	:'''~~[optional description]~~''' ~~is a description added by the designer to quickly identify components of a project that need to be identified (i~~.e.~~, STAGE1, 54THSTREET, etc~~.).		----
			'''Example of No Typical Sections'''
			[[image:237.13.1 no typical.jpg\|right\|270px]]
			:::001_TL_JXSXXXX.pdf
			:::002_QU_01_JXSXXXX.pdf
			:::002_QU_02_JXSXXXX.pdf
			:::002_QU_03_JXSXXXX.pdf
			:::002_QU_04_JXSXXXX.pdf
			:::003_CL_01_JXSXXXX.pdf
			:::004_CL_02_JXSXXXX.pdf
			:::005_CL_03_JXSXXXX.pdf
			:::006_CP_01_JXSXXXX.pdf
			:::007_TC_01_JXSXXXX.pdf
			:::008_TC_02_JXSXXXX.pdf
			:::009_TC_03_JXSXXXX.pdf
			:::010_TC_04_JXSXXXX.pdf
			:::011_TC_05_JXSXXXX.pdf
			:::012_TC_06_JXSXXXX.pdf
			:::013_TC_07_JXSXXXX.pdf
			:::014_TC_08_JXSXXXX.pdf

	----		----

Smithk: /* 237.13.3 Bridge Contract Plans */

2019-09-04T19:28:21Z

237.13.3 Bridge Contract Plans

← Older revision		Revision as of 14:28, 4 September 2019
Line 92:		Line 92:
	[[image:237.13.2 bridge contract plans.jpg\|right\|180px]]		[[image:237.13.2 bridge contract plans.jpg\|right\|180px]]

	The file naming convention for all ~~Bridge Contract Plans~~ shall be in accordance with [[751.5 Structural Detailing Guidelines#751.5.1.4 Contract Plan File Name Convention\|EPG 751.5.1.4 Contract Plan File Name Convention]].		The file naming convention for all bridge contract plans shall be in accordance with [[751.5 Structural Detailing Guidelines#751.5.1.4 Contract Plan File Name Convention\|EPG 751.5.1.4 Contract Plan File Name Convention]].

	==237.13.4 Example Set of Plans==		==237.13.4 Example Set of Plans==

Smithk: /* 237.13.3 Bridge Contract Plans */ Per BR, moved EPG 237.13.3 to 751.5.1.4 Contract Plan File Name Convention and referenced EPG 751.5.1.4 from 237.13.3. The existing EPG 751.1.4 became new EPG 751.1.7.

2019-09-04T18:39:38Z

237.13.3 Bridge Contract Plans: Per BR, moved EPG 237.13.3 to 751.5.1.4 Contract Plan File Name Convention and referenced EPG 751.5.1.4 from 237.13.3. The existing EPG 751.1.4 became new EPG 751.1.7.

@@ Line 90: / Line 90: @@
 ==237.13.3 Bridge Contract Plans==
-[[image:237.13.2 bridge contract plans.jpg|left|250px]]
+[[image:237.13.2 bridge contract plans.jpg|right|180px]]
+The file naming convention for all Bridge Contract Plans shall be in accordance with [[751.5 Structural Detailing Guidelines#751.5.1.4 Contract Plan File Name Convention|EPG 751.5.1.4 Contract Plan File Name Convention]].
 ==237.13.4 Example Set of Plans==

Smithk: /* 237.13.6 Index of Sheets */

2019-06-26T12:39:58Z

237.13.6 Index of Sheets

← Older revision		Revision as of 07:39, 26 June 2019
Line 236:		Line 236:
	EROSION CONTROL SHEETS (EC)----------------------------------XX-XX		EROSION CONTROL SHEETS (EC)----------------------------------XX-XX

	LIGHTING (LT)----------------------------------------------------------------XX-XX		LIGHTING (LT)---------------------------------------------------------------XX-XX

	SIGNALS (SG)-----------------------------------------------------------------XX-XX		SIGNALS (SG)----------------------------------------------------------------XX-XX

	SIGNING (SN)-----------------------------------------------------------------XX-XX		SIGNING (SN)----------------------------------------------------------------XX-XX

	PAVEMENT MARKING (PM)---------------------------------------------XX-XX		PAVEMENT MARKING (PM)---------------------------------------------XX-XX

	CULVERT SECTIONS (CS)------------------------------------------------XX-XX		CULVERT SECTIONS (CS)-----------------------------------------------XX-XX

	BRIDGE DRAWINGS (B)		BRIDGE DRAWINGS (B)

Smithk: /* 237.13.6 Index of Sheets */

2019-06-26T12:32:47Z

237.13.6 Index of Sheets

← Older revision		Revision as of 07:32, 26 June 2019
Line 218:		Line 218:
	TITLE SHEET---------------------------------------------------------------------1		TITLE SHEET---------------------------------------------------------------------1

	TYPICAL SECTIONS (TS) (XX SHEETS)-------------------------------2		TYPICAL SECTIONS (TS) (XX SHEETS)---------------------------------2

	QUANTITIES (QU) (XX SHEETS)------------------------------------------3		QUANTITIES (QU) (XX SHEETS)-------------------------------------------3

	PLAN-PROFILE (PP)-------------------------------------------------------XX-XX		PLAN-PROFILE (PP)-------------------------------------------------------XX-XX
Line 236:		Line 236:
	EROSION CONTROL SHEETS (EC)----------------------------------XX-XX		EROSION CONTROL SHEETS (EC)----------------------------------XX-XX

	LIGHTING (LT)-----------------------------------------------------------------XX-XX		LIGHTING (LT)----------------------------------------------------------------XX-XX

	SIGNALS (SG)-----------------------------------------------------------------XX-XX		SIGNALS (SG)-----------------------------------------------------------------XX-XX

	SIGNING (SN)------------------------------------------------------------------XX-XX		SIGNING (SN)-----------------------------------------------------------------XX-XX

	PAVEMENT MARKING (PM)---------------------------------------------XX-XX		PAVEMENT MARKING (PM)---------------------------------------------XX-XX

Smithk: Per CADD, removed CADD link

2019-06-24T15:18:02Z

Per CADD, removed CADD link

← Older revision		Revision as of 10:18, 24 June 2019
Line 1:		Line 1:
	A conventional method of naming contract plan files is a necessary part of the implementation of electronic plans for MoDOT. This file naming convention is a vital part of the ~~[http://caddnet/index.php?title=Category:~~ProjectWise ~~ProjectWise]~~ document management system.		A conventional method of naming contract plan files is a necessary part of the implementation of electronic plans for MoDOT. This file naming convention is a vital part of the ProjectWise document management system.

	==237.13.1 Design Contract Plans==		==237.13.1 Design Contract Plans==