ConstructionEstimatingDatabase

[Campbellbrian]

Thanks advance for any clues,
I have a customer needing a database for a home construction
business. The customer needs 2 basic components:
1) Estimating module for predicting costs
2) Order module for entering contracts for housing bids they receive

My first thought was to have a typical Northwind model where a subform
accumulates entries that are stored in a table called "Order Details
Extended".
All estimates would be treated as orders. The individual lumber,
roofing, and labor entries would correspond to the "food" entries in
Northwind.

Does anyone have any better thoughts on any projects involving
estimating for construction businesses, metal fabricators, etc.?

Thanks! Brian

[Jayjay]

Re: ConstructionEst imatingDatabase

On 17 Sep 2003 11:56:05 -0700, campbellbrian20 01@yahoo.com
(Campbellbrian) wrote:
[color=blue]
>Thanks advance for any clues,
> I have a customer needing a database for a home construction
>business. The customer needs 2 basic components:
>1) Estimating module for predicting costs
>2) Order module for entering contracts for housing bids they receive
>
>My first thought was to have a typical Northwind model where a subform
>accumulates entries that are stored in a table called "Order Details
>Extended".
>All estimates would be treated as orders. The individual lumber,
>roofing, and labor entries would correspond to the "food" entries in
>Northwind.
>
>Does anyone have any better thoughts on any projects involving
>estimating for construction businesses, metal fabricators, etc.?
>
>Thanks! Brian[/color]


I have been working on this very database for about 4 yrs now. And
let me tell you - the one I've got is a beast!

There is one database for the "items" which are all the items
(different size/length pipes, lumber, materials, etc). THis database
can track cost history etc.

There is a second database that houses the "data" files. Project
information, bids, item costs per project. Etc. These tables are
appended to whenever a new bid or a revision to a bid hapens. ANd we
have a history, as in can look up a bid, or copy a bid from one
project to another, (same house, different lot)... etc.

Then there is the 3rd database that houses all the screens and
reports. (the front end). This ofcourse ties the 2 other databases
together.

Users can create a new bid from scratch by selecting items, or they
can copy an existing bid from another project into a new project, or
they can make revisions to existing bids and save as a new revision.
(example, the client asks to add an extra room onto the house, but
wants the option to go back to the original house if the cost to add
the room is too much).

And finally, we have the option to have multiple construction
companies bid on 1 job so the client can have a report that shows the
side by side comparison of all the bids from the different
construction companies.