[cad-linux] Re: Database Use Cases

> The following was supposedly scribed by
> Thomas Schmidt
> on Friday 16 May 2003 03:17 pm:

>So I am looking forward to hear from you what
>you would tell your boss to convince him/her that a database is a must-ha=
>ve?

Here's what I've come up with so far:

- Use multiple programs without need for export, import, updating, etc.
- Reuse information between modeling and analysis software.
- Modeling and sharing of details allows for more comprehensive analysis        
        
        (structural, HVAC, lighting).
- Update model based on results of analysis.
- Quantity take-offs for estimation and ordering directly from model.
- Load-take-offs updated as changes are made.
- Sharing of data in standard format by manufacturers saves entering catalog 
        data, ensures up-to-date data.
- Interference check for ductwork, piping, elevator, etc between multiple 
        disciplines and multiple offices.
- Access control 
        (read-only, read-write, partial read, partial write, write-only).
- Revision and correspondence tracking 
        (who changed what, when, legal record, change orders, rfi)
- Link for in-house custom programming 
        (standard, easily accessible data       format)
- Easy to find software solutions 
        (when the apps are there, they will all be compatible without worries)

Most of this assumes that the system is already available and every developer 
has started releasing apps to work with it.  This is really the only 
perspective that the end-user can have with the system.

A lot of the technical details to be worked-out at the beginning have to do 
with making these things possible and seamless to the user, but I think that 
the technical merit of the system has to be attractive to developers before 
it can be attractive to users.

--Eric

Other related posts: