237.13 Contract Plan File Name Convention: Difference between revisions

From Engineering_Policy_Guide
Jump to navigation Jump to search
← Older edit
Smithk (talk | contribs)
Modot, modot
20,986 edits
m Per Design, updated example set of plans
m →‎237.13.2 Electronic Design Data: changed GeoPak to OpenRoads Designer
 
(15 intermediate revisions by 2 users not shown)
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==
The file naming convention for all eProject documents shall begin with:
:'''[job#]_[general identification]_'''
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:


'''[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''


:'''[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.
: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.
[[image:237.13.1.jpg|right|150px]]
:'''[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.4 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 (i.e., EC_01, EC_02 would be the 1st and 2nd Erosion Control Sheets).
:'''[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).
 
:'''[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


----
----
Line 47: 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"
|+
|+
|Content's File Report:|| [job#]_contents_file.pdf
|align="center"| '''Contents File Report'''||width="350"| project_data_Summary_report_[job#].XLSX
|-
|rowspan="3"|Geometry File(s):|| [job#]_geometry.gpk
|-
|-
|[job#]_geometry.alg
|align="center" rowspan="3"|'''Geometry Files'''|| civil_geometry_[job#].DGN
|-
|-
|[job#]_geometry.xml
|civil_geometry_[job#].XML
|-
|-
|rowspan="6"|Microstation Files:||[job#]_plan_[optional description].dgn
|civil_geometry_report_[job#].XLSX
|-
|-
|[job#]_profile_[optional description].dgn
|align="center" rowspan="8"|'''MicroStation Files'''|| corridors_[job#].DGN
|-
|-
|[job#]_xs_[optional description].dgn
|graphical_filters_[job#].DGN
|-
|-
|[job#]_drainage_[optional description].dgn
|superelevation_[job#].DGN
|-
|-
|[job#]_shapes_[optional description].dgn
|drainage_[job#].DGN
|-
|-
|[job#]_3D_[optional description].dgn
|xs_[job#].DGN
|-
|-
|rowspan="3"|3D Existing Terrain Models:||[job#]_Existing_[optional description].tin
|plan_[job#].DGN
|-
|-
|[job#]_Existing_[optional description].dtm
|profile_[job#].DGN
|-
|-
|[job#]_Existing_[optional description].xml
|plan_profile_[job#].DGN
|-
|-
|rowspan="6"|3D Digital Design Models:|| [job#]_PFG_surface_[optional description].tin
|width="260" align="center" rowspan="5"|'''3D Existing Terrain Models'''|| terrain_existing_[job#].DGN
|-
|-
|[job#]_PFG_surface_[optional description].dtm
|terrain_existing_[job#].XML
|-
|-
|[job#]_PFG_surface_[optional description].xml
|survey_[job#].DGN
|-
|-
|[job#]_subgrade_surface_[optional description].tin
|survey_report_[job#].PDF
|-
|-
|[job#]_subgrade_surface_[optional description].dtm
|survey_coordinate_[job#].CSV
|-
|-
|[job#]_subgrade_surface_[optional description].xml
|align="center"|'''3D Digital Design Models'''|| proposed_surface_[job#].XML
|-
|rowspan="3"|Final Engineering Design Data:||[job#]_[optional description].rdp
|-
|[job#]_[optional description].ird
|-
|[job#]_[optional description].itl
|}
|}


==237.13.3 Bridge Contract Plans==
==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]].
 
 
 
The file naming convention for all Bridge Contract Plans shall be as follows:
 
:'''[B]_[bridge number]_[sheet#]_[job#].dgn'''
 
:'''[B]''' is the letter “B” for Bridge.
 
:'''[bridge number]''' is the bridge number (i.e., A7005).
 
:'''[sheet#]''' is the number of a particular sheet unique to a bridge number.
 
:'''[job#]''' is the job number as assigned to the project (i.e., J0P0928).
 
:'''[''optional'' description]''' is a description of the sheet information (i.e., BARBILL, FRONTSHEET).
 
----
'''Example Single Bridge Sheet'''
 
[[Image:237.13 Single Bridge Sheet.gif]]
 
----
'''Example Multiple Bridge Sheets'''
 
[[Image:237.13 Multiple Bridge Sheets.gif]]


==237.13.4 Example Set of Plans==
==237.13.4 Example Set of Plans==
Line 175: Line 167:
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"
{| border="1" class="wikitable" style="margin: 1em auto 1em auto"
|+
|+
|Content's File Report:|| J0P0928_contents_file.pdf
|rowspan="2" width="210"|Content's File Report|| Project_Data_Summary_Sheet_J2P0928.pdf
|-
|rowspan="3"| Geometry File(s):||J0P0928_geometry.gpk
|-
|J0P0928_geometry.alg
|-
|-
|J0P0928]_geometry.xml
| Civil_Geometry_Report.xlsx or pdf
|-
|-
|rowspan="6"|Microstation Files:||J0P0928_plan_rte65.dgn
|Horizontal & Vertical Civil<br/>Features File ||Civil_Geometry_J0P0928.xml
|-
|-
|J0P0928_profile_ rte65.dgn
|rowspan="13"|Power GeoPak SS4 Files|| Civil_Geometry_J0P0928.dgn
|-
|-
|J0P0928_xs_ rte65.dgn
| Corridors_J0P0928.dgn
|-
|-
|J0P0928_drainage_ rte65.dgn
| Drainage_J0P0928.dgn
|-
|-
|J0P0928_shapes_ rte65.dgn
| Graphical_Filters_J0P0928.dgn
|-
|-
|J0P0928_3D_ rte65.dgn
| Plan_J0P0928.dgn
|-
|-
|rowspan="3"|3D Existing Terrain Models:||J0P0928_Existing_ rte65.tin
| Profile_J0P0928.dgn
|-
|-
|J0P0928_Existing_ rte65.dtm
| Striping_J2P0928.dgn
|-
|-
|J0P0928_Existing_ rte65.xml
| Superelevation_J0P0928.dgn
|-
|-
|rowspan="6"|3D Digital Design Models:|| J0P0928_PFG_surface_ rte65.tin
| Survey_Exported_Graphics_J0P0928.dgn
|-
|-
|J0P0928_PFG_surface_ rte65.dtm
| Survey_Terrain_J0P0928.dgn
|-
|-
|J0P0928_PFG_surface_ rte65.xml
| Survey_J0P0928.dgn
|-
|-
|J0P0928_subgrade_surface_ rte65.tin
| Coordinate_Points_Sheet_J0P0928.dgn
|-
|-
|J0P0928_subgrade_surface_ rte65.dtm
| XS_J0P0928.dgn
|-
|-
|J0P0928_subgrade_surface_ rte65.xml
|rowspan="2"|Terrain Files|| Terrain_Existing_J0P0928.xml
|-
|-
|rowspan="3"|Final Engineering Design Data:|| J0P0928_rte65.rdp
| Terrain_Proposed_J0P0928.xml
|-
|-
|J0P0928_ rte65.ird
|rowspan="2"|Survey Files|| Survey_Coordinate_File_J0P0928.csv
|-
|-
|J0P0928_ rte65.itl
| Survey_Report_J0P0928.pdf
|}
|}


Line 229: Line 217:
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 247: Line 235:
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)   

Latest revision as of 11:13, 16 January 2024

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

The file naming convention for all eProject documents shall begin with:

[job#]_[general identification]_

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 EPG 237.14.3.2 Submittal of MoDOT Designed Projects.

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

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 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. 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.
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 shall be unique and also used in the 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).
[job#] is the job number as assigned by the district (e.g., J0P0928).
[scale] is the scale the MicroStation border was created in for a particular drawing (e.g., 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.).

Example of No Typical Sections

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

Example Single Quantity Sheet

Example Multiple Quantity Sheet

Example with Optional Description

Example Single Cross-Section Sheet

Example Multiple Cross-Section Sheets

237.13.2 Electronic Design Data

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

Contents File Report project_data_Summary_report_[job#].XLSX
Geometry Files civil_geometry_[job#].DGN
civil_geometry_[job#].XML
civil_geometry_report_[job#].XLSX
MicroStation Files corridors_[job#].DGN
graphical_filters_[job#].DGN
superelevation_[job#].DGN
drainage_[job#].DGN
xs_[job#].DGN
plan_[job#].DGN
profile_[job#].DGN
plan_profile_[job#].DGN
3D Existing Terrain Models terrain_existing_[job#].DGN
terrain_existing_[job#].XML
survey_[job#].DGN
survey_report_[job#].PDF
survey_coordinate_[job#].CSV
3D Digital Design Models proposed_surface_[job#].XML

237.13.3 Bridge Contract Plans

The file naming convention for all bridge contract plans shall be in accordance with EPG 751.5.1.4 Contract Plan File Name Convention.

237.13.4 Example Set of Plans

001_TITLE_J0P0928_ITITLESHEET.dgn 009_SS_02_J0P0928_I20.dgn
002_TS_01_J0P0928_I5_001.dgn 010_EC_01_J0P0928_I50.dgn
002_TS_02_J0P0928_I5_002.dgn 011_EC_02_J0P0928_I50.dgn
002_TS_03_J0P0928_I5_003.dgn 012_EC_03_J0P0928_I50.dgn
002_TS_04-06_J0P0928_I5_004.dgn 013_CS_01_J0P0928_I10.dgn
002_TS_04-06_J0P0928_I5_005.dgn 014_CS_02_J0P0928_I10.dgn
002_TS_04-06_J0P0928_I5_006.dgn B_A6885_001_J0P0928_FrontSheet.dgn
003_QU_01-05_J0P0928_I1_001.dgn B_A6885_002_J0P0928_CulvertDetails.dgn
003_QU_01-05_J0P0928_I1_002.dgn B_B7008_003_J0P0928_BarBill.dgn
003_QU_01-05_J0P0928_I1_003.dgn B_B7008_004_J0P0928_InfoSheets.dgn
003_QU_01-05_J0P0928_I1_004.dgn XS_001-005_J0P0928_I5_Stage1_001.dgn
003_QU_01-05_J0P0928_I1_005.dgn XS_001-005_J0P0928_I5_Stage1_002.dgn
003_QU_06_J0P0928_I1.dgn XS_001-005_J0P0928_I5_Stage1_003.dgn
004_PP_J0P0928_I50_Rte65.dgn XS_001-005_J0P0928_I5_Stage1_004.dgn
005_PP_J0P0928_I50_Rte65.dgn XS_001-005_J0P0928_I5_Stage1_005.dgn
006_PP_J0P0928_I50_Rte65.dgn XS_006-010_J0P0928_I5_Stage1_006.dgn
007_PP_J0P0928_I50_Rte65.dgn XS_006-010_J0P0928_I5_Stage1_007.dgn
007A_PP_J0P0928_I50_Rte65.dgn XS_006-010_J0P0928_I5_Stage1_008.dgn
008_SS_01_J0P0928_I20.dgn XS_006-010_J0P0928_I5_Stage1_009.dgn

237.13.5 Example Set of Electronic Design Data

Content's File Report Project_Data_Summary_Sheet_J2P0928.pdf
Civil_Geometry_Report.xlsx or pdf
Horizontal & Vertical Civil
Features File		 Civil_Geometry_J0P0928.xml
Power GeoPak SS4 Files Civil_Geometry_J0P0928.dgn
Corridors_J0P0928.dgn
Drainage_J0P0928.dgn
Graphical_Filters_J0P0928.dgn
Plan_J0P0928.dgn
Profile_J0P0928.dgn
Striping_J2P0928.dgn
Superelevation_J0P0928.dgn
Survey_Exported_Graphics_J0P0928.dgn
Survey_Terrain_J0P0928.dgn
Survey_J0P0928.dgn
Coordinate_Points_Sheet_J0P0928.dgn
XS_J0P0928.dgn
Terrain Files Terrain_Existing_J0P0928.xml
Terrain_Proposed_J0P0928.xml
Survey Files Survey_Coordinate_File_J0P0928.csv
Survey_Report_J0P0928.pdf

237.13.6 Index of Sheets

Following is an example of the Index of Sheets on the title sheet:

DESCRIPTION SHEET NUMBER

TITLE SHEET---------------------------------------------------------------------1

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

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

PLAN-PROFILE (PP)-------------------------------------------------------XX-XX

RIGHT OF WAY (RW)------------------------------------------------------XX-XX

REFERENCE POINTS (RP)----------------------------------------------XX-XX

COORDINATE POINTS (CP)---------------------------------------------XX-XX

SPECIAL SHEETS (SS)---------------------------------------------------XX-XX

TRAFFIC CONTROL SHEETS (TC)------------------------------------XX-XX

EROSION CONTROL SHEETS (EC)----------------------------------XX-XX

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

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

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

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

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

BRIDGE DRAWINGS (B)

A####------------------------------------------------------------------------XX-XX
A####------------------------------------------------------------------------XX-XX
A####------------------------------------------------------------------------XX-XX
A####------------------------------------------------------------------------XX-XX

CROSS-SECTIONS (XS)----------------------------------------------------XX-XX

Retrieved from "https://epgtest3.modot.org/index.php?title=237.13_Contract_Plan_File_Name_Convention&oldid=53329"