1 / 59

State Aid Project Plan Preparation

State Aid Project Plan Preparation. Topics. State Aid reference materials State Aid Project Number Request Submittal items Plan preparation State Aid checklist Engineer’s Estimate Review timeframe/approvals. State Aid reference materials. State Aid reference materials.

lilika
Download Presentation

State Aid Project Plan Preparation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. State Aid Project Plan Preparation

  2. Topics State Aid reference materials State Aid Project Number Request Submittal items Plan preparation State Aid checklist Engineer’s Estimate Review timeframe/approvals

  3. State Aid reference materials

  4. State Aid reference materials • Road Design Manual • Standard Plans • Standard Plates • State Aid Rule Book (PDF) State Aid Manual (Chapter 5.4) Metro Design Guide (PDF) State Aid Training PowerPoints State Aid Tech Memos MnDOT Tech Memos

  5. SAP AAA-BBB-CCC State Aid Project Number Request

  6. Obtain a project number • You may have multiple project numbers for one plan with multiple partners and/or multiple state aid routes. • Does your project have multiple partners? • Will you or your partners be using state aid, federal aid or state funds? • Is your project on more than one state aid route?

  7. Obtain a project number (continued) • Here is the “secret number code.” • SAP AAA-BBB-CCC numbers are for municipal and county state aid construction funds. • SP AAA-BBB-CCC number are for federal aid funds. • SP DDDD-CCC numbers are for state funds and to identify projects with work on the Trunk Highway. • AAA signifies the state aid city or county number. • BBB signifies the state aid route number or a special state aid program fund number. • CCC signifies the consecutive project number on a route. • DDDD signifies a state highway control section location.

  8. Obtain a project number (continued) • State aid project numbers can be requested through an online form or a fill-in PDF form that is e-mailed to the District State Aid Engineer or other assigned district staff. • Both forms can be found on the SALT Project Delivery webpage under “Requests” • For Metro Projects send in PDF directly to margaret.hylton@state.mn.us.

  9. Submittal items

  10. Submittal items Plan State Aid checklist – bridge or no bridge Pre Engineer’s Estimate Final Engineer’s Estimate Excel version (with final plan submission)

  11. Submittal items (continued) Lab Request Pavement Design Information/Geotechnical Report Signal Justification Letter/Report or ICE Roundabout Justification Report or ICE

  12. Submittal items (continued) Special provisions No parking resolutions (for urban roads only) Drainage information LRIP application (submitted at different time and by local agency) Bridge bond application (submitted at different time and by local agency) After bid opening send the Bid Tabulation with all bidders prices in Excel to Sharon LeMay.

  13. Lab request • Ask the local agency for their TA98 numbers; if they don’t know it please contact Sharon LeMay or Rob Wielinski for this number (metro agencies only). • If using MnDOT services, please submit a copy of the Special Provisions for our Materials Office to reference. Make sure to fill in the TA98 number on the Lab Service Request if using MnDOT services

  14. Pavement Design Report/Geotechnical Report MnPAVE Geotechnical Report Pavement Design Report

  15. Signal justification • Letter • Needed if revising a signal • For pedestrian crossing signals • Flashing yellow arrow addition • Report • Needed for new signal or leg of signal • ICE • Name required if a leg is Trunk Highway

  16. Roundabout justification Include the reason for choosing roundabout over signal with warrants. Make sure to include turning movements of trucks through proposed roundabout. Report images should match what is in the plan. Fast pass speed Sight lines

  17. Justification signatures Prepared By Approved: City (if applicable) Approved: County (if applicable) Approved: Metro District – State Aid Engineer Approved: Metro District – Traffic Engineer (ICE only)

  18. Local Road Improvement Program/Bridge bonds If selected for this type of funds you need to provide an Excel version of the Engineer’s Estimate. Plan will be signed when the funding letter is written for the project by Patti Loken. This can take a few days to obtain so plan accordingly.

  19. Plan preparation

  20. Plan preparation • MnDOT Standard Plans • Typicals • Plan Sheets • Cross Sections Title Sheet SEQ Sheet Tabulations MnDOT Standard Plates

  21. Title Sheet • Each SAP requires a location of project description. • SAP AAA-BBB-CCC located on route from road A to road B. • SAP AAA-BBB-CCC located on route from X’ direction of road A to X’ direction of road A. • Do not use stationing as your limits (unable to use to determine location from). • Location map index. • Begin SAP AAA-BBB-CCC with stationing. • End SAP AAA-BBB-CCC with stationing. • Show any exception areas (see plan sheet section). • Label old/new bridge (if part of project). • If a signal project then just show a leader to the intersection.

  22. Title Sheet (continued) • Label spec year note: • THE 2018 EDITION OF THE MINNESOTA DEPARTMENT OF TRANSPORTATION “STANDARD SPECIFICATION FOR CONSTRUCTION” SHALL GOVERN. • Traffic control note: • ALL TRAFFIC CONTROL DEVICES AND SIGNING SHALL CONFORM AND BE INSTALLED IN ACCORDANCE WITH THE CURRENT “MINNESOTA MANUAL ON UNIFORM TRAFFIC CONTROL DEVICES” (MnMUTCD), INCLUDING THE LATEST FIELD MANUAL FOR TEMPORARY TRAFFIC CONTROL ZONE LAYOUTS.

  23. Title Sheet (continued) • Required Plan Signatures • Prepared By: • Approved: City Engineer (If with in City R/W) • Approved: County Engineer (If within County R/W) • District State Aid Engineer: Reviewed for Compliance with State Aid Rules/Policy • Approved for State Aid Funding: State Aid Engineer • MnDOT Signatures if a LPP Plan

  24. Title Sheet (continued) • Ton design • ESAL’s • R value • Design speed not met at ___. • Height of eye: 3.5’ • Height of object: 2.0’ • ADT (20XX) (year of construction) • Future ADT (20XX) (20 years later) • # of traffic lanes • Shoulder information • Parking lanes • Design speed Design designation block (For each SAP project)

  25. Title Sheet (continued) • Trail design designation block • Based on: stopping sight distance • Height of Eye: 4.5’ • Height of Object: 0’ • Length block (For each SAP project) • Gross length X Ft X Miles • Bridge length X Ft X Miles • Exception length X Ft X Miles • Net length X Ft X Miles

  26. Title Sheet (continued) • Variance note language: • VARIANCE NOTE, if one has been approved for the project, in the following format; • * THIS PROJECT HAS BEEN GRANTED A VARIANCE FROM MINNESOTA RULE 8820.__(a)__, DATED FEBRUARY 2013, SO AS TO PERMIT ___(b)___ IN LIEU OF THE REQUIRED ___(c)___. THE VARIANCE WAS SIGNED BY ___(d)___ ON ___(e)___. • Complete the blanks in the variance note with; • (a) The rule number the variance was granted from, followed by the date of the current rules book. • (b) The project roadway width, design speed, R/W width, or condition allowed by the variance. • (c) The condition that would have been required by the rules had the variance not been granted. • (d) The name and position of the person who signed the variance. • (e) The date the signature was affected.

  27. SEQ Sheet • Separate quantity column for each SAP. • Separate storm quantity column for each SAP (urban roads only). • For storm sewer eligible items. • Storm removals and culverts are not storm eligible but roadway items. • Separate column for local items. • Total quantity column if more than one payee column. • Spec year must match spec year transport list used. • Item numbers have changed from 2016 to 2018 transport lists.

  28. SEQ Sheet (continued) If an item has been salvaged on the project it must be reinstalled on the project to be state aid eligible; otherwise a local cost. Striping no longer calls out color in SEQ item description (only in tabs). Make sure you have a pay item for everything being called our in the plan otherwise make note that they are “incidental.”

  29. SEQ Sheet (continued) • No decimals on quantities unless under one, or it is warranted. • Item numbers should be in numerical order. • Not by scattered item numbers. • By work types (not the preferred method but allowed if client asks for it). • All Items must have a item # from the transport list. • Do not show “zero” quantities. • Use correct unit that corresponds to item number extension.

  30. SEQ Sheet (continued) If combining items into one pay item use .6XX extension. If calling out install it means an item is being furnished by owner to be put in or was salvaged for install; note that it needs to be furnished and installed. Some items include furnish and install and don’t need extra install pay items or to say F&I.

  31. SEQ Sheet (continued) Street signs on corner/above a stop sign are “sign type special” and are not state aid eligible; local cost (see eligibility chart in eSAM).

  32. SEQ Sheet (continued) • Salvage and install are separate pay items: • Wrong way • 2104.502 SALVAGE & INSTALL SIGN TYPE C EACH • Proper way • 2104.502 SALVAGE SIGN TYPE C EACH • 2564.502 INSTALL SIGN TYPE C EACH

  33. Tabulations Tabs are not required but quantities must be verifiable in the plan in some way. Tabs are helpful. Make sure to break out quantities for each payee group.

  34. MnDOT Standard Plates Use the most current version of plate. If multiple sheets of plate then use (X SHEETS) after description. Plates must be in list format; plates do not get shown in the plan. Include FHWA note with plate list. If you call out a plate make sure there is a pay item included in the SEQ. Don’t call out plate letter in notes. If traffic control pay item included in plan use 8000. If ADA in the plan include plate 7038.

  35. MnDOT Standard Plans Use the most current version of plan sheet. If using ADA (.250 (6 sheets)) or driveway (.254 (4 sheets)) plan sheets; must include all sheets in that set. If you modify a standard plan sheet then you must sign it. Standard plans do not require additional signatures if unmodified. Only include plan sheets that have items in the plan.

  36. Typicals Trail must have 2’ clear zone on both sides. Show pavement inserts no matter the type of work. Show right of way (R/W).

  37. Typicals (continued) Wrong way Correct way 10.66’ 2’ Clear Zone Trail dimensions are measured from back of curb, not front of curb.

  38. Typicals (continued) Missing description and dimensions With description and dimensions Label all lanes, shoulders, parking, and show dimensions.

  39. Typicals (continued) Varies dimensions (24’-25’) don’t equate to Lane dimensions (2 11’) Make sure all dimensions add up correctly with what’s shown.

  40. Typicals (continued) Do not use VAR/VARIES. Show actual dimension range for verification.

  41. Typicals (continued) Rural sections show clear zone.

  42. Plan Sheets • Label begin and end of state aid project limits. • Make sure the profiles show grades and vertical curve information. • If work is within MnDOT R/W then show and label on plan sheets. • Permit will be required from MnDOT for work within MnDOT R/W. • This will trigger a Trunk Highway review from the functional groups.

  43. Plan Sheets (continued) Make sure all work is within the R/W, easements, on local agency property, or you have right of entry permission and label the plan sheets.

  44. Plan Sheets (continued) Make sure to label exception area with begin and end area with stationing.

  45. Plan Sheets (continued) Correct end point for project Don’t overlap project limits with adjoining roads or intersection road center line.

  46. Plan Sheets (continued) Make sure all work is within project limits including additional striping (traffic control is not a factor with project limits).

  47. Cross Sections Show R/W and any easements. If work is beyond R/W and on city/county property label as that. If work is beyond R/W and you have right of entry permission label as that.

  48. Cross Sections (continued) Make sure all work is within easement or labeled properly.

  49. Cross Sections (continued) Make sure proposed lines connect to existing ground lines.

  50. State Aid checklist

More Related