Cost Estimation System Tool MPO Conference GDOT Office of Planning Dave Cox July 10, 2009.
-
Upload
abraham-claydon -
Category
Documents
-
view
213 -
download
0
Transcript of Cost Estimation System Tool MPO Conference GDOT Office of Planning Dave Cox July 10, 2009.
Planning Level Cost Estimates• Issues
– The current funding environment has created a critical need to ensure accurate and current planning level cost estimates
– Federal / State / Local funding requires accurate estimates to assist with spending prioritization and balancing
Planning Level Cost Estimates• Answers
– Develop Software to better standardize planning level cost estimation.– Cost Estimation System (CES)
– AASHTO software product– Estimates Construction & PE phases
– Right of Way and Utility Relocation Cost Estimate Tool (RUCEST)– Created by GDOT
- Items previously not included in planning level estimating
- Software cost groups calculate items (asphalt, concrete, earthwork, etc.) known to be in the majority of projects constructed by GDOT.
- Software calculates item cost based project location (geographic region of State).
- Added contingency captures unknown variables (i.e. concrete walls, culverts, landscaping, lighting, etc.)
- User friendly interface allows user to add secondary project items (traffic signals, turn lanes, etc.)
Improving Planning level Estimates
What does CES do for you?• Generates planning level estimates for Construction costs
using pre-made project “templates” • Template uses predetermined Cost Groups info to
calculate planning level cost estimate based on the project length and the typical section– Uses GDOT historical data (3 year window) and
updated each quarter• Provides contingency percentages for unknowns• Documents all planning level assumptions in an attached
text file
The way CES works• Research project description (logical termini, typical
section needed)• Use aerial imagery (Google Maps) to confirm
– Project Length– Existing section– Urban/rural– Proposed improvements
• Primary work type (i.e. widening, new road)• Secondary work types (i.e. bridges, turn lanes,
signals, etc.)
The way CES works (cont.)• Select appropriate template in CES
– Primary Project template (required)– Secondary template (add as needed)
• Enter project length and width• Enter optional items as appropriate.
– Traffic Signals, Turn Lanes, Major Intersections.– Document all assumptions for planners and designers
to review your cost assumptions.
Project Type CES Templates•Auxiliary lanes•Bridges•Frontage roads•HOV lanes•Median work•Multi-use Trail•Park and Ride Lots
•Passing lanes•Ramps•Roadway (new alignment)•Roundabouts•Sidewalks•Turn lanes•Widening Projects
CES Main Estimating Screen
Location:• County• Urban/Rural• GDOT District
Length & Width
Enter Project Description
CES Optional ItemsEnter quantity # of various items along project corridor• Left Turn Lanes• Right Turn Lanes• Major Intersections• Traffic Signals
RUCEST- ROW & Utility Estimating Tool• AASHTO’s CES only calculates CST & PE via %• RUCEST created to generate and document planning
level cost estimate for Right of Way (ROW) and Utility Relocation– Uses database of cost items organized by counties (ROW)
and DOT District (Utility)
• Creates cost sheet that can be exported to PDF or print for archival purposes
• Catalogs different cost scenarios as snapshots
How RUCEST works• Use aerial imagery (GIS or Google Maps) to estimate
project length, ROW land type, takes, and utility • For smaller parcels (i.e. gas stations) found within the
corridor, estimate length and subtract from primary land use type.
• Fill in the worksheet to compile and document the information before adding a new Snapshot in RUCEST
• Add attachment files (PDF maps of corridor) as appropriate
• Finalize “snapshots” to save record in RUCEST• Revisit estimates on regular basis as appropriate
Items to enter into RUCEST• Terrain (flat, rolling, mountainous)• Typical Section (Urban or Rural)
• Tool provides default ROW width
• County & Land Type • Enter length of each land type• Tool provides default land value $ cost per acre
• Enter known displacements (takings)• Tool provides default land value $ cost per acre
• Add known and assumed Utilities• Add attachments (PDFs, Study, N&P, maps, etc.)
Cost Estimation resources: Google
Use Distance Measurement Tool to measure Length and Width
ChurchBridge
Utility Corridor
Potential items to look for
Power Poles
Traffic Signal
signage
Fire Hydrant (water line)
Storm Drain (sewer)
Sample Documentation
Input project name & description
Text File Attachment
Input: • Date /
Estimator• Project length• Project width • # of lanes
Text File AttachmentRoadway Project Width Assumptions:
48’ feet Travel Lanes (12’ ft per travel lane) 13’ feet for paved outside shoulders (13’ ft) 0’ feet for paved inside shoulders (4’ ft) 14’ feet for flush median (range 14’ ft) 0’ feet for bike lanes (8’ ft)
Total width of pavement (s): 75’ feet Other Roadway assumptions (not affecting width in CES):
Median Treatment: 14’ Flush (none, flush, raised, grass, depressed) Sidewalks: No (yes or no)
Based on typical section selected
Sample Documentation
Text File AttachmentCreate separate project for bridges using bridge widening templates (secondary project)
Cost from CES template based on length and total width of new bridge less existing width
Summary• Use these Planning level cost estimating tools to
develop initial project cost during LRTP development, for projects which have not had preliminary engineering (PE) initiated
• Save all documentation in software tools so estimates can be reviewed in the future
• Review the available training materials and documentation
• Provide future suggestions
Questions?
Contact info:
Dave CoxGDOT - Office of Planning