9.1 control - oregonplan - “.pl_” note - “.nt_” plan-profile - “.pp_” full profile -...

54
9.0 Construction Plan & Profile and Construction Notes 9-1 Volume 1 Contract Plans Development Guide September 1, 2005 9.1 Control The purpose of the roadway construction plans portion of the contract plans is to exhibit the necessary horizontal and vertical information to locate and build the new roadway and related design. The roadway construction plans typically include the construction alignment, right-of-way, existing topography, new road- way construction including drainage and utilities, and sometimes, removal plans. Depending on how detailed and complex the design information is, everything may be included on “combined” construction plans, or divided onto “separated” plans, to maintain clarity. See Table 9-1 for the division of information onto the “separated” types of construction plans. Although the construction plans are developed by the Roadway Designers and Drafters, two types of reference file basemaps needed for the construction plans are usually developed by other units at ODOT. The survey unit develops the existing topographic basemap and the Right-of-Way Engineering Unit produces the right-of-way basemaps. Coordination efforts should occur in the preliminary phases of the project be- tween the Roadway Designer and the Survey Unit to develop the existing topo- graphic basemap CAD file to a level of detail that will meet the project needs through the final submittal. The Roadway Designer should also coordinate with the Right-of-Way Engineer- ing Unit as the right-of-way basemap is developed. The existing right-of way information is generated by the Right-of-Way Engineering Unit from the surveyed field data, recovery survey of found monuments, existing right-of-way record drawings and descriptions and the topographic basemap. The Right-of-Way Engi- neering Unit is responsible to provide this information to the Roadway Designer or Drafter in a CAD file containing the existing right-of-way basemap. After the roadway design has been well established, the Roadway Designer is responsible to make the design basemap CAD file available to the Right-of-Way Designer or Drafter, for right-of-way acquisition to be determined. This file should contain the proposed centerline alignment and proposed cut and fill limits of construction. At this time, the Right-of-Way Engineering Unit begins acquisition procedures and delineation of a final right-of-way line, which should be provided in an updated CAD file to the Roadway Designer. Note: For information on developing basemaps, see Section 2.6, Volume 1. Note: For information on seed files, see Section 2.5, Volume 1.

Upload: others

Post on 25-Jul-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-1Volume 1

Contract Plans Development Guide September 1, 2005

9.1 Control

The purpose of the roadway construction plans portion of the contract plans isto exhibit the necessary horizontal and vertical information to locate and buildthe new roadway and related design. The roadway construction plans typicallyinclude the construction alignment, right-of-way, existing topography, new road-way construction including drainage and utilities, and sometimes, removal plans.Depending on how detailed and complex the design information is, everythingmay be included on “combined” construction plans, or divided onto “separated”plans, to maintain clarity. See Table 9-1 for the division of information onto the“separated” types of construction plans.

Although the construction plans are developed by the Roadway Designers andDrafters, two types of reference file basemaps needed for the construction plansare usually developed by other units at ODOT. The survey unit develops theexisting topographic basemap and the Right-of-Way Engineering Unit producesthe right-of-way basemaps.

Coordination efforts should occur in the preliminary phases of the project be-tween the Roadway Designer and the Survey Unit to develop the existing topo-graphic basemap CAD file to a level of detail that will meet the project needsthrough the final submittal.

The Roadway Designer should also coordinate with the Right-of-Way Engineer-ing Unit as the right-of-way basemap is developed. The existing right-of wayinformation is generated by the Right-of-Way Engineering Unit from the surveyedfield data, recovery survey of found monuments, existing right-of-way recorddrawings and descriptions and the topographic basemap. The Right-of-Way Engi-neering Unit is responsible to provide this information to the Roadway Designeror Drafter in a CAD file containing the existing right-of-way basemap.

After the roadway design has been well established, the Roadway Designer isresponsible to make the design basemap CAD file available to the Right-of-WayDesigner or Drafter, for right-of-way acquisition to be determined. This file shouldcontain the proposed centerline alignment and proposed cut and fill limits ofconstruction. At this time, the Right-of-Way Engineering Unit begins acquisitionprocedures and delineation of a final right-of-way line, which should be providedin an updated CAD file to the Roadway Designer.

Note: For information ondeveloping basemaps, seeSection 2.6, Volume 1.

Note: For information onseed files, see Section 2.5,Volume 1.

Page 2: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-2Volume 1

Contract Plans Development Guide September 1, 2005

9.1 Control (Cont’d)The right-of-way file is developed by the Right-of-Way Engineering Unit to theirown standards that vary from the Roadway Design Unit standards. Right-of-WayEngineering uses their own cell library, RW.CEL, located in the ODOT workspace: Internal ODOT staff http:\\scdata3\odot_space\standards\cell External ftp://ftp.odot.state.or.us/isb/appeng/Microstation/Version8/

They also access the ODOT Menu, which contains a right-of-way menu devel-oped by the Right-of-Way Engineering Unit. The only manipulations to the right-of-way file, once it has been released by the Right-of-Way Engineering Unit, arethe moving of text to avoid conflicts with text or graphics in other reference filesor the working file, and moving an element to a different level for display pur-poses. The right of way centerline is shown on the roadway construction plans ifit is different from the construction centerline and new right-of-way is being pur-chased, based on the right-of-way centerline. If the right-of-way centerline is tobe shown, P.I. data should be removed, and the centerline and associated text arechanged to the appropriate weight, etc. It is very important to maintain theestablished right-of-way linework on its coordinate base because it is recorded aslegal documentation. It is the responsibility of the Road Engineer to verify thatthe latest version of the R/W file is being used, as revisions are made often duringthe plans process.

The construction plans, including plan sheets, profiles and construction notes areproduced by the Roadway Designers and Drafters. The Roadway Designer is re-sponsible for developing the design in the proposed design basemap CAD file.The designer is also responsible for providing sketches or redlines of any designrevisions and additions to the drafter as the project progresses.

Throughout the development of the project, it is the responsibility of the drafterto maintain ODOT drafting standards as set forth here, in the Contract Plans Devel-opment Guide.

Review of the contract plans is accomplished at the preliminary, advance andfinal submittal stages by a designated Roadway Design Team leader. The Road-way Engineer’s registration seal and signature are placed on all sheets.

9.2 DevelopmentThe Project Designer and Drafter should begin development of the constructionplans using the following appropriate steps.

To make the (only manipu-lations as described, right)modifications to the right-of-way file for inclusion into theroadway contract plans, usethe Right-of-Way section ofthe ODOT Menu. See Appen-dix “C”.

Tip

Page 3: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-3Volume 1

Contract Plans Development Guide September 1, 2005

Use the following steps to begin development of the “combined” constructionplans or the “separated” alignment, general construction, drainage and utilities orremoval plans. Additional steps for each specific type of sheet can be found inSections 9.2.2 through 9.2.7.

Steps 1 - 8 All construction sheets including plans,construction notes, and profiles

Step 9 “Combined” construction plan sheets onlyStep 10 “Separated” construction plan sheetsSteps 11 - 13 All construction plan and plan-profile sheets

Step 1 — Create an “Active File”Create a new MicroStation™ file from the seed file named SEED2D.DGN orSEED3D.DGN found at: Internal ODOT staff http:\\scdata3\ODOT_space\standards\seed\ External ftp://ftp.odot.state.or.us/isb/appeng/Microstation/Version8/

and name it KEYNUF.PL1, where “KEYNU” represents your project key num-ber assigned by ODOT (to be filled in by you), “F” represents that this file is partof the final contract plans, and “.PL1” is the appropriate extension for the firstfile of Plan sheets. This is your active file. Subsequent plan sheets should benamed “.PL2”, “.PL3,” etc.

Step 2 — Add sheet bordersEnter ODOT’s proprietary software, “Plotypus,” to automatically place borders(File/Plotypus). “Plotypus” automatically creates the borders at a pre-designatedlocation in the design file. Choose the intended scale and sheet size, placing up toten borders per design file. See Appendix D, “A Quickguide To Plotypus,” formore information on placing borders.

Step 3 — Create the Project Title and “V” Number Reference FileCreate a new MicroStation™ file from the seed file named SEEDV8.NAM foundat: Internal ODOT staff http:\\scdata3\ODOT_space\standards\seed\ External ftp://ftp.odot.state.or.us/isb/appeng/Microstation/Version8/

and name it KEYNUF.NAM, where “KEYNU” represents your project key num-ber (to be filled in by you), “F” represents that this file is part of the final contractplans, and “NAM” represents that this generic file is for the project title informa-tion. For example, a new file name might be 01234F.NAM.Title block text is provided in two scales within SEEDV8.NAM for convenientediting.Edit the project title text in the appropriate place within the title block. When thecontract plans are complete and ready to be advertised for bid, the “V” number

Note: For information ontitle block text, see Section2.8, Volume 1.

Note: For information onreference files, see Section2.3, Volume 1.

9.2.1 Sheet Setup

Filename extensions for theroadway construction plansheet are:Plan - “.PL_”Note - “.NT_”Plan-profile - “.PP_”Full profile - “.PF_”

Filenames

Note: For file namingconventions, see Section2.4, Volume 1.

Step 3 may have beencompleted as part of an-other section of the con-tract plans. If it has, use ithere and go on to Step 4.

Tip

Page 4: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-4Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-1 Reference Files - Construction Plans

KEYNUF.NAM filecontaining the projecttitle and “V” number orreview block (referencefile)

“V” No. orreview block

ProjectTitle

The title block is acell. The sheetborder is a cellplaced by Plotypus.

The drafter may place1-10 borders per activefile. Attach referencefiles KEYNUF.NAM andPLANSV8.DGN.

PLANSV8.DGN(reference file)

Active fileKEYNUF.PL_,KEYNUF.NT_,KEYNUF.PP_orKEYNUF.PF_

Page 5: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-5Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-2 Sheet Titles - Combined Construction Plan Sheet

Step 5 — Add Sheet NumbersWhile in the active file, add the appropriate sheet numbers, snapping to the pointprovided in the space. The active file should now have blank pipe data sheetswith the title blocks filled.

will be added to this file in the upper right hand corner of each plan sheet. Forpreliminary, advance and final review submittals, the appropriate block shall beplaced here rather than the “V” number (from the cell library ODOT.cel).

Step 4 — Attach Reference FilesOpen the new active file created in Step 1. Attach KEYNUF.NAM as a refer-ence file and assign a logical name as appropriate for your plan sheet. AttachPLANSV8.DGN as a reference file. Its default location is below the borders asstacked by Plotypus.

Note: For standard font,size, level, and color, seeSection 9, Volume 2.

9.2.1 Sheet Setup (Cont’d)

Note: For examples ofsection text and boundarylines, see Section 9,Volume 2.

Note: For examples of titleson construction plan sheets,see Section 9, Volume 2.

Construction plan sheets thatare “combined” do not have atitle, but do include the section,township and range

Sheet titles are tobe placed in theactive file

Title Block(See section2.9, Volume 1)

Day, Month, Year, and Timeare to be filled in here (seeSection 2.9, Volume 1)

Locate the section textby top center justificationon the snap handlesprovided

Location and name ofworking CAD file are tobe filled in here. ForODOT users, this willupdate automatically.Users outside ODOTmay use a pen table

Page 6: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-6Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-3 Sheet Titles - Separated Alignment, General Construction, Drainage and Utilities andRemoval Plan Sheets

Note: For information oncreating clip boundaries,See Section 2.7, Volume 1.

Step 6 — Add Professional Engineer StampWhile in the active file, add the Professional Engineer’s Stamp cell for the appropri-ate person signing the plans, snapping the cell to the point provided.

Step 7 — Sheet InformationThe location, name and date of the active file are to appear in the lower left cornerof the sheet as shown in Figure 9-2. For ODOT users, this will update automati-cally. Users outside ODOT must use an appropriate pen table.

Step 8 — Turn Levels On or OffWhile in the active file, turn the appropriate levels on or off in the attachedreference files. See Tables 9-1 through 9-5.

Step 9 — Add Titles to “Combined” Construction Plan SheetsWhile in the active file, add the section, township and range at the top of the planor plan-profile sheet and the name of the city or interchange, which are appropri-ate for the project. If more than one section is represented on the plan sheet,

9.2.1 Sheet Setup (Cont’d)Note: For information onpreparing basemaps foruse as reference files onroadway plans, seeBasemaps, Section 2.6,Volume 1.

Construction plan sheets thatare “separated” include thesection, township and range

Locate the section textby top center justifica-tion on the snaphandles providedwithinROADWAYTBLK.CEL

Title Block(See section2.9, Volume 1)

SheetnumberConsultant

logo location.

Consultantlogo location.

Page 7: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-7Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-4 Attach and Modify Reference Files

Topographic datashown here is forinformation only,and is not a part ofthe clip boundaryreference file

Clip boundary(Multisidedconstruction lineshape)

Sheetboundaries

Show angle ofrotation and sheetnumber

Moved clipboundary

Borders

Page 8: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-8Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-5 Completed Attached Reference Files

9.2.1 Sheet Setup (Cont’d)

Topographic base, right-of-way, and design base mapsattached as reference files

Note: For a detailed listof element attributes andlevels, see the LevelStandards, Table 2-3 and2-4, Volume 1.

Step 10 — Add ItemsAdd text and other project specific items as necessary. See the check list at theend of this section for a list of typically required items.

There are some general items that are found on every type of construction plansheet, combined, alignment, general construction, drainage and utilities, and re-moval. Figures 9-6 and 9-7 give some guidelines for these items.

See sections 9.2.3 through 9.2.8, for each specific type of construction plan thatmay be included in the development of the “combined” construction plans:

Note: For standard font,size, level, and color, seeSection 9, Volume 2.

Clip boundary

The area tothe right ofthe dashedline isreserved forconstructionnotes

Alignment.....................................................9.2.3General Construction...................................9.2.4Drainage and Utilities...................................9.2.5Removal.......................................................9.2.6Construction Notes......................................9.2.7Profiles.........................................................9.2.8

Page 9: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-9Volume 1

Contract Plans Development Guide September 1, 2005

the section data is labeled in the plan portion of the sheet instead of at the top ofthe sheet. The section text is oriented with its associated boundary line on theplan view. Add the sheet number in the title block. See Figure 9-2.

Step 11 — Add Titles to “Separated” Construction Plan SheetsWhile in the active file, add titles at the top of the plan or plan-profile sheet, and asheet number in the title block, as illustrated in Figure 9-3, which are appropriatefor the project and for the type of plan sheet you are creating. Most titles can befound in the “Cache” (PLANSV8.DGN) and copied and edited.

Step 12 — Attach Base MapsAttach the appropriate existing topographic base map, right-of-way file and de-sign base as reference files. Manipulate these files to the same parameters (move,rotate, scale, and clip boundary) that you used for the clip boundary file for thesame plan sheet.

9.2.2 “Combined” Construction PlansTo continue to develop construction plans with “combined” information, use thefollowing steps.

Step 13 -- Turn Levels On or OffWhile in the active file, turn the appropriate levels on or off in the attached basemapreference files. Table 9-1 lists the items for “combined” plans that include all ofthe alignment, construction, drainage and utility, and removal information. Usethe MicroStation™ command “save settings” to maintain the levels turned onand off.

9.2.1 Sheet Setup (Cont’d)

Page 10: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-10Volume 1

Contract Plans Development Guide September 1, 2005

Table 9-1 “Combined” Construction Plan Levels

The alignment plans display the construction centerline and data, right-of-waylines and data, and existing topography. Drainage and utilities are not shown onthe alignment plans. Also, generally not shown are new construction items suchas approaches. To continue to develop construction plans with alignment infor-mation, use the following steps.

Step 8 — Turn Levels On or OffWhile in the active file, turn the appropriate levels on or off in the attached basemapreference files. For a guideline of levels to turn off for alignment plans, see Table9-2.

Step 9 — Add ItemsAdd text and other project specific items as necessary, as shown in Figures 9-8through 9-15. See the check list at the end of this section for a list of typicallyrequired items.

9.2.3 Alignment Plans

Table 9-2 Alignment Plan Levels

Note: For alignment planexamples, see Section 9,Volume 2.

SNALPNOITCURTSNOC"DENIBMOC"

ELIFECNEREFERPAMESAB WOHS WOHSTONOD

yhpargopoTgnitsixE,yhpargopotgnitsixE

gnitsixe,eganiardgnitsixeseitilitu

tniop,txetevitpircseDsrebmun

esaBngiseD

,enilretnecnoitcurtsnoCwen,atadevruc

,senallevart,noitcurtsnocseitilituwen,eganiardwen

tniop,txetevitpircseDsrebmun

W/R senildnasnoisnemidW/R tniop,txetsuoenallecsiMsrebmun

SNALPTNEMNGILA

ELIFECNEREFERPAMESAB WOHS WOHSTONOD

yhpargopoTgnitsixE yhpargopotgnitsixEgnitsixe,eganiardgnitsixE

,txetevitpircsed,seitilitusrebmuntniop

esaBngiseD,enilretnecnoitcurtsnoCfoegdewen,atadevruc

tnemevap

levart,eganiardweNtsom,seitilituwen,senal

,noitcurtsnocwentniop,txetevitpircsed

srebmun

W/R txetdnasnoisnemidW/R tniop,txetsuoenallecsiMsrebmun

Page 11: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-11Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-6 Basic Horizontal Alignment Items

Station tic and label intervals on plans with scalesother than the default of 1”=100’ may vary asappropriate for the scale and plan sheet

Small tics areplaced every 100’on all of thecenterlines on aproject

Large tics are placedevery 500 feet on thecenterline of construc-tion, left side only

For curve data, flaggedcontrol points, andstation equations seeAlignment Plans,Section 9.2.3

Develop plan sheets with stationing increasingfrom left to right. Stationing is read ahead on line.Alignment stationing increases from north to southand from west to east on N-S and W-E Routes. Forexamples, see Section 9, Volume 2.

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Label stations oncenterline(s) ofconstruction every500 feet When more than one

centerline is shown, labelall existing centerlinesand centerlines ofconstruction

Page 12: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-12Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-7 Match Lines

Do not use match lineson the primary construc-tion centerline run ofplan sheets, left to right

Use match lines on non-mainline constructioncenterlines, when the plansheet boundary is exceeded

Do not locate a matchline or sheet break atthe same location as acontrol point. Controlpoint and flag should beclearly visible on oneside of match line.

Avoid locating match lines or sheet breaks, ifpossible:1) Within the curb return area at intersections2) At an approach or road/street connection3) On a structure

For standard level, font,size, color, weight, andline code, see Section 9,Volume 2

Include an overlapof about 25’ oneach side of thesheet

Page 13: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-13Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-8 Curve Data and Flagged Control Points

Simple Curve and Equal Spirals

Simple Curve and Unequal Spirals

Simple Curve

See Standard Abbrevia-tions, Appendix “A”,Volume 1

The standard maximumnumber of decimalplaces for curve data is 2decimal places

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Page 14: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-14Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-9 Bearings

Figure 9-10 Alignment Horizontal Offset

For standard font, size,level, color, and weight,see Section 9, Volume 2

For standard font, size,level, color, and weight,see Section 9, Volume 2

Label all tangentbearings ofconstructionalignments

Page 15: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-15Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-11 Station Equations

A station equation indicates a gap, realignment, or intersection of the horizontalcenterline stationing. The equation states the mathematical relationship of thecenterline stationing back “Bk.” or before the point of equation and the stationingahead “Ah.” or after the point of equation.

Plan View

Profile

Station ahead

Station back

The station equation isshown in both the planand profile views

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Station back

Station ahead

Page 16: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-16Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-12 Government Boundaries

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

For examples, seeSection 9, Volume 2

Use the ODOT Menu toaccess the correct textand symbology

Page 17: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-17Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-13 Existing Right-of-Way, Construct Right-of-Way, and Access Control

For examples, seeSection 9, Volume 2

The type of right-of-wayshould be labeled on allof the construction plansheets

Do not show existingfence inside right-of-wayunless requested by thedesigner

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Use the ODOT Menu toaccess the correct textand symbology

Page 18: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-18Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-14 Access Control

Figure 9-15 Temporary Easement

Label TemporaryEasement line

Label TemporaryEasement width

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Label TemporaryEasement beginningand end stations

Access Control is the condition where the right of owners, or occupants ofabutting land, or other persons, to access in connection with a highway isfully or partially controlled by public authority

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Page 19: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-19Volume 1

Contract Plans Development Guide September 1, 2005

The general construction plans display all of the new construction and travellanes, but do not display the new drainage and utilities. The construction center-line is shown, but not the curve data. Also shown are the right-of-way lines andexisting topography. To continue to develop the general construction plans, usethe following steps.

Step 8 — Turn Levels On or OffWhile in the active file, turn the appropriate levels on or off in the attached basemapreference files. For a guideline of items to turn off for general construction plans,see Table 9-3. Use the MicroStation™ command “save settings” to maintain thelevels on and off.

Step 9 — Add ItemsAdd text and other project specific items as necessary, as shown in Figures 9-16through 9-22. See the check list at the end of this section for a list of typicallyrequired items.

Table 9-3 General Construction Plan Levels

Note: For generalconstruction planexamples, see Section 9,Volume 2.

9.2.4 General Construction Plans

SNALPNOITCURTSNOCLARENEG

ELIFECNEREFERPAMESAB WOHS WOHSTONOD

yhpargopoTgnitsixE yhpargopotgnitsixEgnitsixe,eganiardgnitsixE

,txetevitpircsed,seitilitusrebmuntniop

esaBngiseD,enilretnecnoitcurtsnoC,noitcurtsnocwentsom

senallevart

wen,eganiardweN,atadevruc,seitilitu

tniop,txetevitpircsedsrebmun

W/R senilW/R,snoisnemidW/R

tniop,txetsuoenallecsimsrebmun

Page 20: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-20Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-16 Edge of Pavement and Curbs

Dimension shoulderwidth where both acurb and a shoulderoccur

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

In this case, thecurb line, edge ofpavement and edgeof sidewalk are thesame line

In this case, the edgeof pavement coincideswith the shoulder line

Page 21: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-21Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-17 Travel Lanes and Tapers

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Label the rate of taper asthe change in width to thechange in length. Forexample, a taper of 1:100equals a change in widthof 1 foot for every 100 feetof length.

Provide travel lanewidth dimensions atboth ends of each plansheet and at locationswhere the roadwaytypical changes

Page 22: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-22Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-18 Approaches and Road/Street Connections

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

For road/street connec-tions, include the streetname and radii

Show radial returnsfor road and streetconnections

Pavinglimit

Show radialreturns forapproaches

For approaches, includethe width, station, andtype of surfacing

Show limits of paving which may vary.See English Standard Drawings fornormal paving limits. Non-standardpaving limits should be addressed inthe detail portion of the contract plans.

Page 23: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-23Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-19 Guardrail

Construction Note ExamplePlan View ExampleGuardrail Construct

Opposite End of Guardrail with End Piece Extending onto Another Plan Sheet

Opposite End of Guardrail with End Piece on the Same Plan Sheet

Guardrail Extends onto Another Plan Sheet

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Page 24: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-24Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-20 Guardrail (Cont’d)

Guardrail Removal and Construct at the Same Location

Construction Note ExamplePlan View Example

Guardrail Connection

Guardrail Flare

Some guidelines for guardrail construction notes are:

1. Guardrail notes are usually found on the first plan or construction note sheet that the guardrail appears.2. List guardrail types in consecutive numerical order, i.e. 2A, 3, transition.3. Treat median and shoulder barrier notes the same as guardrail notes.

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Page 25: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-25Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-21 Mailbox Installation

Plan View Example

Construction Note Examples

Follow the example formailbox construction noteswhen locations are notknown. This note should beplaced on the first construc-tion plan sheet.

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

These notes may becombined if all informationis the same

Follow the examples formailbox construction noteswhen locations are known

Page 26: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-26Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-22 Structures (Bridges, Box Culverts and Walls)

The structure informationon the plan and profilemust match the structureinformation in the bridgedrawings

Note: For standard level,font, size, color, weight,and line code, seeSection 9, Volume 2

Label thebeginning andending stationsof the newstructure.

Page 27: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-27Volume 1

Contract Plans Development Guide September 1, 2005

The drainage and utilities plans display all of the new and existing drainage andutilities features, and applicable new construction, but do not display the travellanes and curve data. Also shown are the right-of-way lines and existing topog-raphy. To continue to develop the drainage and utilities plans, use the followingsteps.

Step 10 — Turn Levels On or OffWhile in the active file, turn the appropriate levels on or off in the attached basemapreference files. For a guideline of intems to turn off for the drainage and utilitiesplans, see Table 9-4. Use the MicroStation™ command “save settings” to main-tain the levels on and off.

Step 11 — Add ItemsAdd text and other project specific items as necessary, as shown in Figures 9-23through 9-25. See the check list at the end of this section for a list of typicallyrequired items.

Table 9-4 Drainage and Utilities Plan Levels

Note: For drainage andutilities plan examples, seeSection 9, Volume 2.

9.2.5 Drainage and Utilities Plans

SNALPSEITILITUDNAEGANIARD

ELIFECNEREFERPAMESAB WOHS WOHSTONOD

yhpargopoTgnitsixEdnaeganiardgnitsixE

tsom,sbruc,seitilituyhpargopotgnitsixe

tniop,txetevitpircseDsrebmun

esaBngiseD

,enilretnecnoitcurtsnoC,seitilitudnaeganiardwen

,sreirrabdnasbrucwenlavomereganiard

srebmuntniop,atadevruC

W/R ylnosenilW/R,snoisnemidW/R

tniop,txetsuoenallecsimsrebmun

Page 28: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-28Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-23 Culverts

The length of the culvert inthe plan should match thelength in the constructionnote, and as shown in thepipe data sheet

Use DITCH CONST_V8line code to show theditch at its approximatelocation

Use the cell PEslopeCfrom ROAD.CEL to showpaved end slopes. Thereal size of the paved endslope does not need tobe represented.

For standard font, size,level, weight and color,see Section 9, Volume 2

The station callout inthe construction noteis determined at thepoint where theculvert crosses thecenterline

Page 29: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-29Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-24 Manholes, Inlets and Drainage Sewer Pipe

Example 2

Example 1

The manhole is locatedby the constructioncenterline station andthe offset distance fromthat centerline

The mainline sewer pipe isincluded in the constructionnote with the manhole intowhich the stormwater flows

Existing inlet

The new inlets, in this example, flow tothe extg. inlet, not a manhole. Theinlets are located by constructioncenterline station and the offsetdistance from that centerline.

Pipe lengths are mea-sured from the center tocenter of structure orsymbol.

Label pipesize andlength

The inlets, in thisexample, are included inthe same constructionnote as the manholethey are associated withor flow into

For standard font, size,level, weight, and color,see Section 9, Volume 2

Page 30: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-30Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-25 Drainage and Utility Removal

Plug orabandon pipe

Manholeremoval

Inletremoval

For standard font, size,level, weight, and color,see Section 9, Volume 2

Add the applicable legend items tothe drainage and utilities plans

Page 31: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-31Volume 1

Contract Plans Development Guide September 1, 2005

The removal plans display all of the removal items except for drainage andutilities removal, which is shown on the drainage and utilities plans. To con-tinue to develop the removal plans use the following steps.

Step 10 — Turn Levels On or OffWhile in the active file, turn the appropriate levels on or off in the attachedbasemap reference files. For a guideline of items to turn off for the removalplans, see Table 9-5. Use the MicroStation™ command “save settings” tomaintain the levels on and off.

Step 11 — Add ItemsAdd text and other project specific items as necessary. See the check list at theend of this section for a list of typically required items.

Table 9-5 Removal Plan Levels

Note: For removal planexamples, see Section 9,Volume 2.

9.2.6 Removal Plans

SNALPLAVOMER

ELIFECNEREFERPAMESAB WOHS WOHSTONOD

yhpargopoTgnitsixE tsom,sbrucgnitsixEyhpargopotgnitsixe

tniop,txetevitpircseDsrebmun

esaBngiseD

,enilretnecnoitcurtsnoCtnemevap,lavomerbruc

klawedis,lavomerlavomergnidliub,lavomer

wen,noitcurtsnocweN,seitilituwen,eganiard

,atadevruc,sednallevartsrebmuntniop

W/R ylnosenilW/R,snoisnemidW/R

tniop,txetsuoenallecsimsrebmun

Page 32: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-32Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-26 Pavement, Sidewalk and Building Removal

Existing curb isshown as asolid line onremoval plans

Sidewalk removalis shown cross-hatched

Pavementremoval isshown hatched

Provide constructionnote bubbles andnumbers for removalitems

Building to beremoved

For standard font, size,level, weight and color,see Section 9, Volume 2

Page 33: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-33Volume 1

Contract Plans Development Guide September 1, 2005

The purpose of the construction notes is to describe the general information andlocation to build the new design. They can be located either on a plan sheet, plan-profile sheet or a separate construction note sheet. To begin development of thenotes, Steps 1 - 4 in Section 9.2.1, Sheet Setup, should be followed before con-tinuing on to the next steps, shown here.

If the construction notes are being added to a plan or plan-profile sheet, you willneed to continue developing the plan portion of the sheets with Steps 5-10 inSection 9.2.1, Sheet Setup, before continuing with this section. If you are devel-oping a construction note sheet, continue with the following steps. The note mar-gin bar is a cell, located in ROAD.CEL.

Step 6 — Add a Sheet NumberAdd the sheet number within the title block. See Figure 9-3. This text can befound in the “Cache” (PLANSV8.DGN) and copied and edited. A constructionnote sheet is generally numbered to correspond with the plan sheet with which itis associated. For example, a plan sheet numbered “6” would have a note sheetnumbered “6A”.

Step 7 — Add Construction NotesAdd the construction notes to the active file at the margins and tic locations asshown in Figures 9-27 and 9-28.

General InformationConstruction notes should be listed in the same order that the items occur in theStandard Specifications. Notes added later can be placed at the end of the sequence.Within individual notes, a standard must be followed for order of constructionnote composition. General guidelines for construction note composition are:

1. All notes are to be written for single application.2. Give removal item first, then construction item, except in the case of tempo-

rary installation, i.e. detours.3. Place one space between words, after comma and period, and on either side

of a hyphen. No space is required on either side of the equal sign.

See Standard Order of Construction Note Composition, later in this section.

Note: For constructionnote examples, seeSection 9, Volume 2.

Note: For note marginlevels in PLANSV8.DGN,see Section 2.9, Volume 1.

9.2.7 Construction Notes

Page 34: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-34Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-27 Construction Note Placement and Information

For standard font, size,level, weight and color,see Section 9, Volume 2

AC=NoteMargin(ROAD.CEL)

Place note number text,with top right justificationat the left end of tic mark,with a circle AC=BUBBLEE1(ODOT.CEL)

Place text node, with topleft justification, at theright end of the tic mark

If construction note items are based ondrawings from the EnglishStandardDrawings, include the reference number onthe first construction note it applies, only

References to project detailsshould be made in every construc-tion note to which they apply

The use of Standard Drawingsis highly recommended

The spacesbetween notes mayrange from 2 to 4

Page 35: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-35Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-28 Construction Note Placement and Information

Center the constructionnotes within the sheet

Do not add note linesbelow the last tic

The construction notes should be listed inthe same order that the items occur in theStandard Specifications. Notes added latecan be placed at the end to save time andeffort.

For guardrail and mailbox installation construc-tion note examples, see Figures 9-19 through9-21

Page 36: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-36Volume 1

Contract Plans Development Guide September 1, 2005

The standard order of construction note composition is:Sta. 00+00, Lt. or Rt.Sta. 00+00 To Sta. 00+00, Lt. or Rt.Const. Appr.Const. Street (Road) Conn.Remove (Abandon) ManholeConst. (Reconst., Adjust) ManholeRemove (Abandon) InletAdjust (Cap) InletConst. Type “G-2” Mod. InletConst. Precast Sump 10’ DeepRemove Pipe30” Culv. Pipe - 38’ (In Pl.)Remove End Sec. Lt. or Rt.Remove - 15’ Lt. or Rt.Extend - 10’ Lt. or Rt., 5’ DepthInst. 12” Sew. Pipe - 146’ 5’ DepthInst. 12” Sew. Pipe - 146’Inst. 5’ Depth Lateral Sec. With Cleanout GateInst. 3 Piece 20° Elbow - 2Inst. Slip JointInst. Slope AnchorConst. Subgrade Cutoff DrainConst. Drainage CurbConst. Paved End Slope Lt. or Rt.Const. Loose Riprap (Class 50) - 90 Cu. Yd.Class 3300 -1.5 Conc. - 2.5 Cu.Yd.Reinf. - 350 KDrainage Geotextile, Type “?” - 65 Sq. Yd.Filter Blanket - 25 Cu.Yd.Gravel Drain Matl. - 16 Cu. Yd. Resurf.Tr. Resurf. - 35 S.Y.

orTrench Resurf. - 35 S.Y.Trench - 75 Sq. Yd.Granular Backfill or Bedding Matl. - 30 Cu. Yd.Gen. Exc. - 30 Cu.Yd.Tr. Exc. - 50 Cu.Yd.Dt. Exc. - 24 Cu.Yd.Toe Tr. Exc. - 18 Cu.Yd.Const. Type CL-6 Fence(For Details, See Sht. xx)(For Drg. Nos., See Sht. 1)(Earthwork Incl. in Main Rdwy. Distr.)

9.2.7 Construction Notes (Cont’d)

Note: For guardrail andmailbox installationconstruction noteexamples, see Figures 9-19through 9-21.

TipAs the line items shownhere are only a partial listof those possible, the de-signer is allowed to decideproper order of note com-position using this list asa guide. It is also sug-gested that the examplesin Volume 2 be used indeciding note composi-tion, in order to maintainsome consistency onODOT projects.

Page 37: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-37Volume 1

Contract Plans Development Guide September 1, 2005

The vertical alignment of a roadway is the progression of elevations, typicallyalong the construction centerline. The existing ground profile line (ground line) isshown as well as the profile of the proposed vertical construction centerline align-ment on a profile grid. Also shown, within the profile grid, is the depth of thenew construction, the location of existing subsurface features, and any new pro-posed subsurface features such as sewer pipes, drain pipes, manholes and inlets.The profile grid is either just below the plan on the same sheet or displayed sepa-rately on a full profile sheet. See Figure 9-31.

To begin development of the profiles, Steps 1 - 4 in Section 9.2.1, Sheet Setup,should be followed before continuing on to the next steps, shown here. If theprofile is being added to a plan-profile sheet, you will need to continue develop-ing the plan portion of the sheets with Steps 5-10 in Section 9.2.1, Sheet Setup,before continuing with this section. If you are developing a full profile sheet,continue with the following steps.

Step 5 — Add Sheet NumberWithin your active file, add the sheet number in the title block. See Figure 9-3. Thistext can be found in the “Cache” (PLANSV8.DGN) and copied and edited. Turnthe correct levels on or off to display the required profile grid.

Step 6 — Create Clip BoundariesCopy the seed file, SEED2D.DGN, to a new file using the appropriate file namingconvention. This file will be your clip boundaries reference file to be used in thecreation of the profiles. Open the new clip boundaries file and create sheet bound-aries using multisided shapes that fit your sheet breakout and scale. Normally, at1”=50’ scale, this would be 1200 feet per single plan sheet. The station limitsneed to match the related plan station limits. On a plan-profile sheet, the profileshould be aligned directly under the plan, by station.

Step 7 — Attach Clip BoundariesOpen the active file and attach the clip boundaries file you created in the previousstep. Scale and move the clip boundaries reference file so it fits properly withinthe borders of the first open plan-profile or profile sheet. Place a fence on the clipboundary shape you wish to show and clip the reference file objects. See Figure9-29. Keep a record of the “move from” and “move to” points and the scale asyou will need this information for the profile base reference file.

The horizontal scale of profile sheets is set by Plotypus. The vertical scale is aratio of 10 to 1 with the horizontal scale. For every 10 feet measured horizontally,the vertical distance is 1 foot.

Note: For profile examples,see Section 9, Volume 2.

Note: For file namingconventions, see Section2.5, Volume 1.

Note: For information oncreating clip boundaries,See Section 2.8, Volume 1.

9.2.8 Profiles

Page 38: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-38Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-29 Attach and Modify Reference Files

Profile information shownhere is for information only,and is not a part of the clipboundary reference file

Moved andscaled clipboundary

Using Plotypus, the numberand placement of views inthe active file can bedetermined by the user andis no longer limited to onedek of six views.

SheetboundariesClip boundary

construction

Page 39: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-39Volume 1

Contract Plans Development Guide September 1, 2005

Clipboundary

Vertical profile base attachedas a reference file, twice onthe same sheet at adjacentstation locations

Clipboundary

Step 8 — Attach Profile BaseAttach the appropriate vertical profile base, “KEYNUF.PRO”, as a referencefile. Figure 9-30 represents a profile sheet with the vertical profile reference fileattached correctly. Manipulate this file to the same parameters (move, scale, andclip boundary) that you used for the clip boundary file. Two profile “runs” aretypical on full profile sheets, which requires an additional attachment of the pro-file base.

Step 9 — Add ItemsAdd text and other project specific items as necessary to the active file or the pro-file base file. Generally, the items in Figures 9-31 and 9-38 are the only onesadded to the active file. See the following Figures 9- 38 for information regardingspecific items shown on the profiles. See the check list at the end of this sectionfor a list of typically required items.

Figure 9-30 Completed Attached Reference Files

9.2.8 Profiles (Cont’d)

Page 40: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-40Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-31 Basic Profile Sheet Item Placement

Elevations (1”=50’ scale) areplaced on each line of the verticalprofile grid at 5’ intervals. Eleva-tions (1”=100’ scale) are placed oneach line of the vertical profile gridat 10’ intervals.

Generally, elevation labels begin at twoelevation numbers below the lowest gradepoint and ends at two elevation numbersabove the highest grade point of the profileshown.

Station references (1”=100’) areplaced at 500’ spacings withstation tics at 100’ intervals. Notic is placed with the stationnumber at even 500’ distances.Stations (1”=200’) are placed at500’ spacings with no tics.

All items shown here areplaced in the active file

Page 41: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-41Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-32 Vertical Alignment Item Placement

The profile grade begins (generally)at the line which designates thebeginning of the construction projectand runs continuously from profilesheet to profile sheet throughout theproject and terminates with the linewhich designates the end of theconstruction project. Place the label“Profile Grade @ L” once per profilesheet.

CThe grade notes indicatethe slope of the gradeexpressed as a percentof rise divided by thedistance (run), shown totwo decimal places

The ground line runs continu-ously from profile sheet to profilesheet throughout the project, andis representative of existingground at the same horizontallocation as the profile grade andconstruction centerline

Note: For standard font, size,level, weight and color, seeSection 9, Volume 2

Page 42: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-42Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-33 Vertical Curves and Data Item Placement

Length of VerticalCurve, expressed infeet and labeled V.C.,is placed at thecenter and on theinside of the curve

A Tic is a shortvertical line usedas a visualreference for thebeginning and endof a vertical curveAC=VCendE

V.P.I. is thevertical pointof intersec-tion. Thesymbol is acircleAC=VCcircle

Station and Elevation labels thelocation of the V.P.I. The stationnotation is placed below theprofile grade and elevation isplaced above the profile grade

A vertical curve is used to connect two grade lines. The intersectionpoint between the grade line and the vertical curve is called the B.V.C.(begin vertical curve) and the E.V.C. (end vertical curve). The intersectionof the two grade lines is called the V.P.I. (vertical point of intersection)

Note: For standard font,size, level, weight andcolor, see Section 9,Volume 2

Page 43: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-43Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9- 34 Structures Item Placement

Bridge information, including the depth and length ofthe structure, can be found on the bridge drawings.The stations should be shown at the ends of thebridge or structure.

The bridge number anddesign high waterelevation are placedhorizontally on the sheet.The same information isshown in the plan viewand must match.

Additional features to thebridge such as riprapare shown in the profile

Feature Notes areplaced horizontally onthe sheet. The noteincludes the type of itemand class, if applicable.

A bridge may be shown withsupport columns and orembankment slopes

Page 44: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-44Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-35 Box Culverts and Drainage Facilities

Note: For standard font,size, level, weight andcolor, see Section 9,Volume 2

The drainage feature orstructure note is placedhorizontally on the sheet.The note includes thestructure type and size

Reinforced Concrete Box Culvert,Drainage Facilities, etc.: As thesefeatures are generally at an angle,usually perpendicular to the roadwayprofile grade, a cross section of thebox culvert or drainage facility isshown, at an exaggerated verticalscale

Page 45: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-45Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-36 Sub-Surface Features

Other common sub-surface features not shown hereare: Existing sewer and drain pipes, construct drainpipe and existing and construct ditch lines. All ofthese items can be accessed through the ODOTMenu - FD Plans - Profiles.

Construct sewer pipe dataincludes the percentageslope, size and length

Constructsewer pipe

The subgrade is measured from the profile grade line to thebottom of the subgrade. The dimension and label are placedtwice on each profile sheet, once at the beginning of theprofile run and again at the end of the profile run. The depthshould be shown in inches read ahead on line. If the area isshort in total length only one label on one profile sheet isrequired.

Note: For standard font,size, level, weight andcolor, see Section 9,Volume 2

Page 46: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-46Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-37 Manholes and Inlets Item Placement

The drainage structure andpipe information in the profileshould match the constructionnotes on the plan or construc-tion note sheets

Note: For standard font,size, level, weight andcolor, see Section 9,Volume 2

Additional inlet and manholeinformation such as grate orrim elevation and distance leftor right is recommendedwhere additional clarity iswanted

Inlet Note and Text: The note isplaced horizontally on the sheet.The inlet note includes the stationand the inlet identification labeland the flow line elevation. An inletnot labeled with the word “Extg.” isconsidered new construction.

Manhole Note & Text: The note isplaced horizontally on the sheet. Themanhole note includes the station andthe manhole identification label andthe flow line elevation. A manhole notlabeled with the word “Extg.” isconsidered new or to be constructed.

ConstructManholeExisting

ManholeConstructInlet

ExistingInlet

Page 47: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-47Volume 1

Contract Plans Development Guide September 1, 2005

Figure 9-38 Earthwork Brackets

9.2.9 Superelevation Runoff Charts

The purpose of the superelevation runoff chart is to show the superelevationgrade relationship between the roadway construction centerline and the left andright edge of traveled way. A superelevation runoff chart displays multiple lineprofiles of these lines and should be used to check for any problems such as gradecontrols at road approaches, building elevations or interchange designs. For moreinformation on superelevation, see the ODOT English Highway Design Manual.Superelevation runoff charts can be developed with design software such asInRoads and added to the profile sheets within the contract plans.

Arrows at the end of the brackets indicatethe quantities and brackets extend ontoanother profile sheet or profile run on thesame sheet.Cell name: AC=Sectionarrow (ODOT.CEL)

Place embankment and/or excava-tion brackets. Earthwork Bracketsare in fixed positions horizontally bystationing, but may be placed in anyconvenient location vertically. Themost common placement is at thebottom of the profile sheet, justabove the station numbers.

The earthwork brackets for stageconstruction in the profiles relate tothe staging as shown in the trafficcontrol portion of the contract plans

Note: For standard font,size, level, weight andcolor, see Section 9,Volume 2

Page 48: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-48Volume 1

Contract Plans Development Guide September 1, 2005

The section numbers that correspond with the Construction plans, located in theStandard Specifications for Highway Construction, ODOT, can be located in variousparts and may include the following sections:

9.3.1 AlignmentSection 00170 -- Legal Relations and Responsibilities

9.3.2 General ConstructionSection 01030 - SeedingSection 01050 - FencesSection 01070 - Mailbox SupportsSection 02820 - Metal GuardrailSection 03010 - Fencing Materials

9.3.3 Drainage and UtilitiesSection 00240 - Temporary Drainage FacilitiesSection 00405 - Trench Excavation, Bedding and

BackfillSection 00420 - Salvaging PipeSection 00430 - Subsurface DrainsSection 00435 - Wick DrainsSection 00440 - Minor Structure ConcreteSection 00445 - Culvert, Siphon, Sewer and Irrigation PipeSection 00450 - Structural Plate Pipe, Pipe Arch and ArchSection 00460 - Paved Culvert End SlopesSection 00470 - Manholes and InletsSection 00475 - Drain WellsSection 00480 - Drainage CurbsSection 00490 - Adjustment of Manholes, Inlets, and BoxesSection 02410 - Concrete and Plastic PipeSection 02420 - Metal PipeSection 02430 - Structural Plate PipeSection 02440 - Joint MaterialsSection 02450 - Manholes and Inlets

9.3.4 RemovalSection 00310 -- Removal of Structures and Obstructions

9.3.5 ProfilesSection 00330 - Earthwork

Note: For additionalinformation on specialprovisions, see Section 16,Volume 1.

9.3 Coordination With Specifications & Special Provisions

Page 49: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-49Volume 1

Contract Plans Development Guide September 1, 2005

9.4 ChecklistThe roadway construction plan, profile and construction note sheets that areincluded in the contract plan documents should show any or all of the following:

“Combined” Construction Plan Sheet

Sheet number and “V” numberNorth arrowStandard ODOT English borders and title blockProject titleCAD file name and pathSection, township, and range location and city or interchange (ifapplicable)Roadway construction centerlines with centerline namesCenterline stationsCenterline curve data and tangent bearingsFlagged control pointsStation equationsCenterline match lines when necessaryConstruction notes and note bubblesRight-of-way, access control, and easement linesExisting topography, drainage, and utilitiesBegin project and end of project notationsNew edge of pavement, curbs, medians, and sidewalkOffset dimensions at right-of-way line angle pointsNew travel lanes, dimensions and tapersNew approaches and street/road connections and informationNew guardrail and flaresNew mailboxesNew structures (bridges, box culverts, and walls)New fencesNew culverts and pipesNew manholes and inletsNew utilitiesRemoval symbology and legendText read from bottom left (readable as traveling upstation along thecenterline stationing)

Page 50: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-50Volume 1

Contract Plans Development Guide September 1, 2005

9.4 Checklist (Cont’d)

Alignment Plan Sheet

Sheet title, sheet number and “V” numberNorth arrowStandard ODOT English borders and title blockProject titleCAD file name and pathSection, township, and range location and city or interchange (ifapplicable)Roadway construction centerlines with centerline namesCenterline stationsCenterline curve data and tangent bearingsFlagged control pointsStation equationsCenterline match lines when necessaryRight-of-way, access control, and easement linesExisting topographyBegin and end of project notationNew edge of pavement, curbs, medians, and sidewalkOffset dimensions at right-of-way line angle pointsNew approaches and street/road connectionsNew structures (bridges, box culverts, and walls)New fencesText read from bottom left (readable as traveling upstation along thecenterline stationing)

Page 51: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-51Volume 1

Contract Plans Development Guide September 1, 2005

9.4 Checklist (Cont’d)

General Construction Plan Sheet

Sheet title, sheet number and “V” numberNorth arrowStandard ODOT English borders and title blockProject titleCAD file name and pathSection, township, and range location and city or interchange (ifapplicable)Roadway construction centerlines with centerline namesCenterline stationsStation equationsCenterline match lines when necessaryConstruction notes and note bubblesRight-of-way, access control, and easement linesExisting TopographyBegin and end of project notationNew edge of pavement, curbs, medians, and sidewalkNew travel lanes, dimensions and tapersNew approaches and street/road connections and informationNew guardrail and flaresNew mailboxesNew structures (bridges, box culverts, and walls)New fencesText read from bottom left (readable as traveling upstation along thecenterline stationing)

Page 52: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-52Volume 1

Contract Plans Development Guide September 1, 2005

9.4 Checklist (Cont’d)

Drainage and Utilities Plan Sheet

Sheet title, sheet number and “V” numberNorth arrowStandard ODOT English borders and title blockProject titleCAD file name and pathSection, township, and range location and city or interchange (ifapplicable)Roadway construction centerlines with centerline namesCenterline stationsStation equationsCenterline match lines when necessaryConstruction notes and note bubblesRight-of-way, access control, and easement linesExisting Topography, drainage, and utilitiesBegin and end of project notationNew edge of pavement, curbs, medians, and sidewalkNew Approaches and Street/Road ConnectionsNew structures (bridges, box culverts, and walls)New culverts and pipesNew manholes and inletsNew utilitiesDrainage removal symbology and legendText read from bottom left (readable as traveling upstation along thecenterline stationing)

Page 53: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-53Volume 1

Contract Plans Development Guide September 1, 2005

Removal Plan Sheet

Sheet title, sheet number and “V” numberNorth arrowStandard ODOT English borders and title blockProject titleCAD file name and pathSection, township, and range location and city or interchange (ifapplicable)Roadway construction centerlines with centerline namesCenterline stationsStation equationsCenterline match lines when necessaryConstruction notes and note bubblesRight-of-way, access control, and easement linesExisting topographyBegin and end of project notationRemoval symbology and legendText read from bottom left (readable as traveling upstation along thecenterline stationing)

9.4 Checklist (Cont’d)

Page 54: 9.1 Control - OregonPlan - “.PL_” Note - “.NT_” Plan-profile - “.PP_” Full profile - “.PF_” Filenames Note: For file naming conventions, see Section 2.4, Volume 1

9.0 Construction Plan & Profile and Construction Notes

9-54Volume 1

Contract Plans Development Guide September 1, 2005

9.4 Checklist (Cont’d)

Construction Note Sheet

Sheet number and “V” numberStandard ODOT Englsih borders and title blockProject titleCAD file name and pathConstruction notes and note bubbles

Profiles

Sheet number and “V” numberStandard ODOT English borders and title blockProject titleCAD file name and pathSheet titles (alignment name)Stations and elevationsExisting ground lineProfile grade and vertical alignment dataStation equationsSubgrade and dimensionsExisting drainage pipesNew drainage pipesExisting manholes and inletsBegin and end of project notationNew manholes and inletsDesign High Water ElevationNew structures (bridges, box culverts)Earthwork BracketsText read from bottom left (readable as traveling upstation along thecenterline stationing)