Dee Dee Strohl - Blog 5

Uses of databases in design offices

What is a database?

A database is a computerized system that stores information that can be easily searched and selected. It is a collection of records that contain one or more fields (pieces of data) about some entity (object). This can be used in many applications; like libraries keeping track of available and checked out books, or a company who’s stored all employee information. There are a few types of databases that can be used: flat, hierarchical, network, and relational. Though Excel can and is used for a plenty of projects in design offices (and beyond), using a database is more capable with respect to large, complex projects that contain a lot of data or pieces. Databases are also attractive because several people can access and edit information at the same time.

From a design office perspective:

From an architectural or engineering firm perspective, using a database could be helpful in several applications. A database could be created to keep all client information and the projects associated with them. From working in an engineering firm, I’ve seen that different clients have specific requirements for building design and construction. Having a database to contain all the client information and specifications would be helpful. Especially because you can search for distinct words/requirements in the database easily. The database, and thus the information, can be accessed remotely and files are easily backed up to prevent losing work and edits.

From an owner perspective:

With databases, it’s easier for owners to share information with design firms and track progress. It makes finding documentation on both ends easier. Besides having access to a database for the design process, owners could create a database to use once the building is construction and in use. Information about the performance of the building systems, building automation, or life cycle could be track by looking at past and present data.

From a general perspective:

Because databases are becoming more and more used, the sharing of information has gotten easier. Different firms and people can share their projects or technologies with the world through them, making processes easier and more efficient. Even throughout college, databases have made it easier to research for classes and papers. This is particularly seen from the Drexel Libraries system, which allows you to search thousands of articles and journals with just a few keywords. It can also be helpful from a marketing perspective because everything is easily accessible.

Sources:

 “Architectural File Management Systems and Database,” Human Service Solutions. Accessed 2/11/18. https://www.hswsolutions.com/work/case-studies/architecture-file-management-database/

“Database Definition,” The Linux Information Project. Accessed 2/11/18. http://www.linfo.org/database.html

“How to Better Manage Your Project Data,” Archsmarter. Accessed 2/11/18. http://archsmarter.com/manage-project-data/

COMMENTS:

Isaac Quelly:

It’s awesome that you got to look at the GSI project and database in its early stages. I see why it’s important for every step of the design and build process to be tracked and added to the database and how it could be troublesome if changes are made without the correct procedure. Do you think the PWD has done anything to keep this issue from occurring in projects? Do you think the implementation of this technology will continue? I know when I worked at the city people were hesitant to take on new procedures.

Luciana Tangari:

Like you, I know nothing about object oriented databases (I honestly barely understand the types of databases as a whole). The analogy you added to your post was very helpful in gaining a better understanding of OODMS and relational databases. It’s interesting that OODMS can handle such complex data but makes it easier to access. I’m still not completely sure I understand OODMS, but your post helped me at least gain a bit of knowledge on the topic.

Dung Tran:

Thanks for giving me an understanding of what a relational database is. I ready in Luciana’s post about OODMS so it was nice to read about the other side of the coin. It’s interesting that in this type of database tables can be defined with constraints or algorithms but also don’t have to be. The images you included also made your (and Darwen’s) explanation easier to understand.