Quantities Manager and the Interface to Estimating Full Implementation

1. Quantities Manager and the Interface to Estimating Full Implementation Todd R.Bergland Trns•port Systems Manager Minnesota DOT

2. Ben & Jerry’s offers a progressive benefits package that includes the usual stuff plus paid family leave, health club memberships and three free pints of Vermont’s Finest super premium ice cream, frozen yogurt and sorbets every day!

3. Quantities Manager and the Interface to Estimating Full Implementation • Quantities Manager Overview • Implementation Overview • Implementation Steps 1-9 • Reporting • General Considerations/Findings

4. Quantities Manager Overview • Java based stand-alone application • MicroStation or GEOPAK use not required (Non-Graphic portion) • MicroStation and GEOPAK license required • Access database format

5. Quantities Manager Overview Design and Computation Manager Quantity Manager Quantity Database Trns*port Database

6. Quantities Manager Overview • Microsoft Access • SQL Server • Oracle • Others DBMS Option Quantity Manager JDBC ADO Quantity Database

7. Quantities Manager Overview Design XML Interface Estimation Trns*port PES/CES Payitem/Funding Master List Estimator GEOPAK Quantity Manager Payitem Quantities Trns*port CES InRoadsJune 2004 Trns*port PES

8. Quantities Manager Overview

9. aecXML Method Bridging The Gap Design

10. Quantities Manager Overview AecXML Benefits • Promotes Standardization. • XML is the future • Promotes Collaboration. • Connections between disparate applications. • Allows for sorting, searching, reporting,importing,exporting and updating. • Example ( Engineers Estimates)

11. Implementation Overview • Trained all nine districts • Implemented Standards for exchange • Processed 30 projects • Require all projects be processed using Quantities Manager • Two Phase Implementation

12. Implementation Overview • Phase I – Fully implemented • Non-graphic pay items • Database delivery to Estimating Unit • Utilities tabulations • Engineers Estimate • Introduce new DDB for beginning new projects • Phase II – Tentatively set to coincide with V8 • More templates for tabulations • Graphics pay items • Estimated quantities for multiple S.P.s

14. Implementation - Step 1 Trnsport Exports • Payitem List - AECITEM00.XML • Pay item numbers • Descriptions • Units of Measure (including lump sum) • Funding List - AECFUND.XML • Pay item numbers • Descriptions Cost Estimate (Excel) - Average_engineers_estimate_english01.csv • Pay Item • Several cost estimates

15. Implementation - Step 1 Export Items Export By Spec Yr. 00 01

16. Implementation - Step 1 Export Funds

17. Implementation – Step 1 Export Sample • Add xml piece

18. Sets up pointers to Trns•port files Sets up Spec Year (English / Metric) Seed Database Implementation QM Step 2

19. Implementation - Step 2 Seed Database

20. Filter by unit system, spec year and payitem name Implementation – Step 3 Define Items

21. Implementation - Step 3 Multiple Pay Items

22. Implementation - Step 3 Individual Pay Items

23. Implementation - Step 4 Graphic Items Pay items from Trns•port MUST match DDB Item!

24. Implementation - Step 5 Funding • 1 Phase for each State Project • 1 Phase for every funding splits

25. Implementation - Step 5  100% State Funding  90% Federal Funding 10% State Funding  80% Federal Funding 20% State Funding  Mixture of State, Federal and City Funds Four Common Funding Splits

26. Implementation - Step 5 50% City 50% State SP #1 SP #2 DesignEstimateA DesignEstimate DesignEstimateB

27. Implementation - Step 6 Export XML File to Trnsport

28. Implementation - Step 7 Import XML File to Trnsport PES/CES

29. Implementation Step - 8 Review Quantities WOW !

30. Implementation - Step 9 Rename Project

31. Reporting Create Custom Reports using Style Sheets

32. Select a category Select individual or groups of quantities Reporting

33. Reporting Final Design Estimate Traffic Signal Estimate • Export costs from Trns*port • Import costs into QM • Adjust as needed • Create report • Can be done throughout project life cycle

34. Reporting Statement of Estimated Quantities

35. General Considerations Rules for Transfer

36. General Considerations • Mn/Dot does not utilize the Payers option in the Quantities Manager as this will be determined by the PES Manager.

37. General Considerations Non-Pay Item Graphics • Examples: • Utilities • Inplace Drainage • Must match DDB Feature in terms of symbology • Store in its own QM database

38. General Findings Time Savings Large 2 days Medium 1-1.5 hrs. Small .5 - .75 hrs.

39. General Findings Design Benefits of QM/Trnsport Sharing • Streamlining Improvements • Major time savings • One database used for multiple purposes • Decrease in time (after learning curve) • Improved Quality • Correct (up to date) pay item numbers • Eliminate human error • Promotes standardization

40. General Findings Long Term Goals – “ Big Picture” • Sharability of data • Estimating, Finance, Construction,Traffic • Further XML Enhancements • Lat/Long Transfer • Begin Station – End Station • Begin Termini – End Termini • Export Facility from PES/CES • Electronic bidding life cycle • QM database is one part of the 100% electronic plan

41. References • www.w3c.com • www.bentley.com • www3.dot.state.mn.us/qm/qm.html

42. ANY QUESTIONS