Quantities Manager and the Interface to Estimating Full Implementation

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

description

Quantities Manager and the Interface to Estimating Full Implementation. Todd R.Bergland Trns • port Systems Manager Minnesota DOT. - PowerPoint PPT Presentation

Transcript of Quantities Manager and the Interface to Estimating Full Implementation

Todd R.Bergland Trns•port Systems Manager

Minnesota DOT

Quantities Manager and the Interface to Estimating

Full Implementation

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!

Quantities Manager and the Interface to Estimating

Full Implementation Quantities Manager Overview Implementation Overview Implementation Steps 1-9 Reporting General Considerations/Findings

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

Quantities Manager Overview

Quantity Manager

Design and Computation Manager

Quantity Database

Trns*port Database

Quantities Manager Overview

Microsoft Access SQL Server Oracle Others

Quantity Manager

Quantity Database

JDBC

ADO

DBMS Option

Quantities Manager Overview

Quantity Manager

Payitem/Funding Master

List

Payitem Quantities

Estimator

Trns*port PES

Trns*port PES/CES

GEOPAK

InRoadsJune 2004

Design XML Interface

Estimation

Trns*portCES

Quantities Manager Overview

COPY SEEDDATABASE

COMPUTEGRAPHIC

QUANTITIESVIA GEOPAK

(OPT.)

MANUALLYADD ITEMSFROM PICK

LIST AND ADDQUANTITIES

CREATE TABULATIONS

DESIGN ENGINEER'SESTIMATE

STATEMENT OFESTIMATEDQUANTITIES

SEND DATABASE TOESTIMATING

Bridging The Gap

Design

aecXML

Method

Quantities Manager Overview Promotes Standardization. XML is the future Promotes Collaboration. Connections between disparate

applications. Allows for sorting, searching,

reporting,importing,exporting and updating. Example ( Engineers Estimates)

AecXML Benefits

Implementation Overview Trained all nine districts Implemented Standards for

exchange Processed 30 projects Require all projects be processed

using Quantities Manager Two Phase Implementation

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

Implementation - Step 1

Payitem List - AECITEM00.XML Pay item numbers Descriptions Units of Measure (including lump sum)

Funding List - AECFUND.XML Pay item numbers DescriptionsCost Estimate (Excel) -

Average_engineers_estimate_english01.csv Pay Item Several cost estimates

Trnsport Exports

Implementation - Step 1

Export BySpec Yr. 00 01

Export Items

Implementation - Step 1Export Funds

Implementation – Step 1 Export Sample

Add xml piece

Implementation QM Step 2

Sets up

pointers to

Trns•port files

Sets up Spec

Year (English /

Metric)

Seed Database

Implementation - Step 2Seed Database

Implementation – Step 3

Filter by unit system, spec

year and payitem name

Define Items

Implementation - Step 3Multiple Pay Items

Implementation - Step 3Individual Pay Items

Implementation - Step 4

Pay items from Trns•port MUST match DDB Item!Graphic Items

Implementation - Step 5

1 Phase for each State Project

1 Phase for every funding splits

Funding

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

Implementation - Step 5

SP #1 SP #250% City50% State

DesignEstimate

DesignEstimateA

DesignEstimateB

Implementation - Step 6

Export

XML File to

Trnsport

Implementation - Step 7

Import

XML File to

Trnsport PES/CES

Implementation Step - 8

Review

Quantities

Implementation - Step 9

Rename

Project

Reporting

Create Custom Reports using Style Sheets

Reporting

Select a category

Select individual or groups

of quantities

Reporting

Export costs from

Trns*port

Import costs into QM

Adjust as needed

Create report

Can be done throughout

project life cycle

Final Design Estimate

Traffic Signal Estimate

ReportingStatement of Estimated Quantities

General Considerations

Data Restrictions

Project Names <= 13 characters

Funding Rules > 1 and < 9999

Phases DesignEstimate

Quantity Value Maximum of 999,999,999.999

Pay Items Must Exist in Trns•port

Payers Must Exist in Trns•port

Rules for Transfer

General Considerations Mn/Dot does not utilize the Payers option

in the Quantities Manager as this will be determined by the PES Manager.

Examples: Utilities Inplace Drainage

Must match DDB Feature in terms of symbology

Store in its own QM database

General Considerations

Non-Pay Item Graphics

General Findings

Small .5 - .75 hrs.

Medium1-1.5 hrs.

Large2 days

Time Savings

General Findings

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

Design Benefits of QM/Trnsport Sharing

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

Long Term Goals – “ Big Picture”

General Findings

References

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

ANY QUESTIONS