Overview of FDOT’s Long Range Estimating System 2005 TEA Conference November 4, 2005 Daytona Beach, Florida

Presentation Outline History / Background LRE Basic Concepts –Project Levels –Typical Sections Demo

Pre-1986, we used cost-per-mile method. In 1986 we developed our first LRE program, which used typical section characteristics, applied to a length of roadway, to generate: –Pay Items –Quantities –Unit Prices Original LRE didn’t facilitate accurate estimating of non-roadway features. History / Background

In 2000 we identified a need for a new and improved LRE: –User friendly and intuitive –Minimal input required –Improved accuracy and reporting Planning team formed in October 2000 to lay the groundwork: –Statewide representation of key estimators –Bi-monthly workshops, Oct 2000 – June 2001 –Established preliminary requirements, developed input screens, formulas, etc., while funding for LRE was pending. History / Background

Programming team formed in July 2001 –Project Manager –2 Systems Program Analysts –4 Programmers / Web Developer –2 Database Administrators Programming team and Planning team combined, to form the Functional Steering Committee –Users involved in all phases of the project Implemented new system in July 2003  History / Background

LRE Quantities Formula-Driven or Calculated Quantities: –Earthwork, Roadway, Median and Shoulder quantities can be generated by a formula –System uses pavement, median and shoulder widths, pavement design information and section length to generate roadway quantities (stabilization, base, asphalt, FC, etc.) –System uses fill height, slope data, and characteristics from other components (roadway, median, shoulder) to generate the appropriate earthwork quantities.

Sample Input Screen

LRE Quantities, continued… “Component Detail” Default Quantities: –Available on several components –Spreadsheet of assumed pay items, quantities and unit prices – Quantities are based on model selected and length specified (Drainage, Signing, Conventional Lighting, Erosion Control), or a selected type/size (Signalization, Retention Basins, Intersections) –Default data can be adjusted, as necessary.

Sample Component Detail

Administrative Features User Maintenance / Role Assignment –*C.O. Administrator (can assign any role) –*District Coordinator (can assign Estimator, Coder and Reviewer roles within their District) –Estimator –Coder –Reviewer (District and State) Maintenance of Pay Items and Prices Maintenance of System Defaults (C.O. only) –Typical section default characteristics –Component detail default values Maintenance of User Help (C.O. only) No Administrative functions

LRE Demonstration

Price Files and Updates Recently changed the update process and schedule. Default prices will now be updated each month, using 1 year of bid history, and all bidders. Pricing is entirely customizable.

Technical Information Web-based (Intranet application) Oracle database interfaces with: –DSS –FDOT’s Financial Management System / Work Program Administration –Estimates Report Tracking System (ERTS) No hardware or software requirements, other than standard desktop and access to the FDOT intranet

Overall Success Management Support Dedicated resources / personnel User involvement at ALL phases: –Planning –Requirements –System Design –Construction –Testing –Implementation User Feedback feature

Post-Implementation During the first year, 2 major Maintenance Releases addressed over 40 enhancements to the initial implementation. Now in the system maintenance phase –43 enhancements completed to date –25 enhancements pending Expected to meet the Department’s needs for at least the next 7-10 years

Contact Information Dale Stanley, LRE Administrator; User Support and Training David Davis, Technical Questions Greg Davis, Management Issues

Questions ???