CADD Engineering Standards - Ohio Department of Transportation

CADD Engineering Standards - Ohio Department of Transportation CADD Engineering Standards - Ohio Department of Transportation

dot.state.oh.us
from dot.state.oh.us More from this publisher
09.04.2013 Views

January 18, 2013 Select the Apply button to generate the report. An example of the output for one cross section station is shown below. Station X Y Z Offset 1360970.473 720238.200 970.520 -75.863 70+00.000 R 1 1360964.235 720230.561 967.232 -66.000 1360963.602 720229.786 967.232 -65.000 1360962.970 720229.012 967.232 -64.000 1360959.175 720224.364 968.732 -58.000 1360953.483 720217.393 969.452 -49.000 1360952.850 720216.618 969.532 -48.000 1360950.320 720213.520 969.864 -44.000 1360942.731 720204.225 970.860 -32.000 1360935.141 720194.930 971.856 -20.000 1360933.560 720192.993 972.064 -17.500 1360928.816 720187.184 971.986 -10.000 1360928.184 720186.410 971.906 -9.000 1360922.543 720179.501 969.676 -0.081 1360920.013 720176.403 969.676 3.919 1360916.799 720172.467 970.946 9.000 1360916.167 720171.692 971.026 10.000 1360909.842 720163.947 971.856 20.000 1360902.253 720154.651 972.852 32.000 1360894.663 720145.356 973.848 44.000 1360893.398 720143.807 974.014 46.000 1360892.133 720142.258 973.994 48.000 1360891.501 720141.484 973.914 49.000 1360885.808 720134.512 973.194 58.000 1360862.284 720105.702 960.795 95.194 1360860.387 720103.378 959.795 98.194 1360859.754 720102.604 959.795 99.194 1360859.122 720101.829 959.795 100.194 1360857.906 720100.340 960.757 102.117 504.8 Submission of Electronic Files to Central Office Section 1503 of The Location and Design Manual, Volume Three – Highway Plans details the plan documents required for electronic submission, which will be made available to contractors during ODOT’s construction contract bidding process. The District shall review the electronic documents submitted to the Department to ensure the required CADD and ASCII files are provided. It is the District’s responsibility to submit these files to Central Office as per Section 1503.4 of The Location and Design Manual, Volume Three – Highway Plans, and as detailed below. The District shall consolidate the electronic files to be provided to bidders into a .zip file to be submitted to the Office of Contracts. The .zip file shall conform to the following file naming convention: nnnnn.zip nnnnn = Five digit PID Number Example: 12345.zip 110 ODOT CADD Engineering Standards

January 18, 2013 The Office of Contracts will post the electronic files on the ODOT website for contractor access during the bidding process. The District is responsible for uploading the .zip file to the “Reference Only” folder on the following Central Office server: \\CTRFS100\D##$ The District can map a network drive to the Central Office Server using the following codes: D1 = \\CTRFS100\D01$ D7 = \\CTRFS100\D07$ CO = \\CTRFS100\CEN$ D2 = \\CTRFS100\D02$ D8 = \\CTRFS100\D08$ D3 = \\CTRFS100\D03$ D9 = \\CTRFS100\D09$ D4 = \\CTRFS100\D04$ D10 = \\CTRFS100\D10$ D5 = \\CTRFS100\D05$ D11 = \\CTRFS100\D11$ D6 = \\CTRFS100\D06$ D12 = \\CTRFS100\D12$ A separate folder is set up for each District and Central Office. Each folder is set up with write permissions for the corresponding District or Central Office with the exception of the TEMP folder, which has been set up with write access for everyone. Note: The electronic files submitted to the District from an external consultant may include additional files that should not be provided to bidders via the Office of Contracts. The District shall ensure that the .zip file provided to the Office of Contracts contains only the required documents as specified in section 1503 of The Location and Design Manual, Volume Three – Highway Plans. A checklist of required files is provided in Appendix E. Care must be taken to ensure that the Save full path info option is toggled on when adding files to the .zip file as shown in the example below. This will ensure that all design file reference attachments are maintained when the files are unzipped by the recipients. ODOT CADD Engineering Standards 111

January 18, 2013<br />

The Office <strong>of</strong> Contracts will post the electronic files on the ODOT website for contractor access during the<br />

bidding process. The District is responsible for uploading the .zip file to the “Reference Only” folder on<br />

the following Central Office server:<br />

\\CTRFS100\D##$<br />

The District can map a network drive to the Central Office Server using the following codes:<br />

D1 = \\CTRFS100\D01$ D7 = \\CTRFS100\D07$ CO = \\CTRFS100\CEN$<br />

D2 = \\CTRFS100\D02$ D8 = \\CTRFS100\D08$<br />

D3 = \\CTRFS100\D03$ D9 = \\CTRFS100\D09$<br />

D4 = \\CTRFS100\D04$ D10 = \\CTRFS100\D10$<br />

D5 = \\CTRFS100\D05$ D11 = \\CTRFS100\D11$<br />

D6 = \\CTRFS100\D06$ D12 = \\CTRFS100\D12$<br />

A separate folder is set up for each District and Central Office. Each folder is set up with write<br />

permissions for the corresponding District or Central Office with the exception <strong>of</strong> the TEMP folder, which<br />

has been set up with write access for everyone.<br />

Note: The electronic files submitted to the District from an external consultant may include additional files<br />

that should not be provided to bidders via the Office <strong>of</strong> Contracts. The District shall ensure that the .zip<br />

file provided to the Office <strong>of</strong> Contracts contains only the required documents as specified in section 1503<br />

<strong>of</strong> The Location and Design Manual, Volume Three – Highway Plans. A checklist <strong>of</strong> required files is<br />

provided in Appendix E.<br />

Care must be taken to ensure that the Save full path info option is toggled on when adding files to the<br />

.zip file as shown in the example below. This will ensure that all design file reference attachments are<br />

maintained when the files are unzipped by the recipients.<br />

ODOT <strong>CADD</strong> <strong>Engineering</strong> <strong>Standards</strong> 111

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!