B5: Use of Databases in Design Offices

    In simplest terms “a database is a collection of information... organized in a way to be easily accessed, managed, and updated.” [1] This “information” can refer to anything from the names, positions, and other data populating a given company’s operational-level employee database all the way down to the content of a single excel sheet on a company’s intranet. Due to the flexibility and ubiquity of the term itself, databases are essential to most modern companies, and design firms are no exception to this. 
    Databases allow for massive quality of life improvements in the day-to-day operations of a design firm. The databases built into applications like Revit allow designers to apply and reference data such as material dimensions, weight, and other engineering considerations to their BIM designs. These modeled objects and their various associated properties (Tuples and Attributes, in terms of Relational Database Theory) are observed throughout a suite of software for easy cross-referencing between different engineers and designers. This creates a quantified, object-oriented approach to BIM engineering through documenting physical properties of known materials in a digital format before a structure is even designed. [2]

    The existence of a centralized cross-reference database is perhaps more important than the existence of a database for any one given application- A database is only as useful to a firm as it is accessible and legible to all relevant employees. Also integral to the usability and benefit of a database is the depth to which it is detailed; The more a tuple is described with ample, descriptive, and most of all relevant attribute data, the easier it is to find and assess for use in multiple future design scenarios. 
    I would go further to posit that a solid understanding of Relational Database Theory is useful to all professionals, engineers and otherwise. The logical reasoning and mathematical syntax behind selection of tuples and attributes in a system such as SQL is in itself an engineering challenge- one that must be explored in order to full understand the ways in which databases can be used to their maximum potential within our industry.

Sources:
https://searchsqlserver.techtarget.com/definition/database

https://www.cmu.edu/cee/projects/PMbook/14_Organization_and_Use_of_Project_Information.html#14.4%20Organizing%20Information%20in%20Databases

Comments on others:
Hanyan Chen: You wrote a very well-detailed explanation of OODB systems. I understand some rudimentary RDBT concepts from a class I previously took on SQL, but this post helped me understand a little more of the core tenants behind how RDBT is implemented.


Calvin Tang:
I agree that knowledge of SQL code fundamentals and syntax may not be necessary to all, a decent grasp on the theory behind the syntax is absolutely a great asset for any engineer or other STEM professional to have. SQL syntax is derived from discrete mathematics, after all. 

Laney Fries:
You did a good job of explaining the multiple ways that CAD can interface with CAM over a centralized database. The implication for different phases of a construction project all being able to interface so seamlessly is really exciting.