Databases are now being used for
design work in all aspects of architectural design. This integration is making designers’ work
easier by saving and classifying different tools and built objects in BIM. Using relational databases can help create
new tools that help change minor details in the project. They can be attached to different properties
of building elements to quickly edit heights, sizes, or other properties with a
click of a button or moving a slide bar.
Dynamo, a program that links with Revit, allows for this. There are several editing tools that relate
to another piece of the project. The
video of the Dynamo example shows how they can create a structure completely in
Dynamo by creating a repeated design and then defining the space that it will
cover. They can even change the
materials and how the roof curves throughout the structure.
The Dynamo program is driven by
SQL. This is a database program that
allows Dynamo to feed the tables in Revit.
SQL can be coded to set objects into categories such as furniture and
can be pulled from Revit into an easy to understand table. This will allow you to pull all the information
for a particular type of object. As the
SQL code expands, you can get more specific in what you would like to look
at. If a client would like to see all
the types of chairs he or she was getting in a design, the designer could
easily go into SQL and pull that data for an easy to understand chart for the
client. This is much easier than setting
up a furniture schedule and then having to just highlight all the chairs in the
project.
The same procedure can be done with
the rooms of a project. Once all the
data is collected, then they can be sorted using SQL to show what furniture is
in which room. This is just one example
of the power of relational databases in design.
This can be done for any part of piece of a design project. This will ultimately make communication
between the owner and the designer easier.
They can create quick lists during the design process to give updates
and keep records of the design at certain times.
Resources:
https://revitbeyondbim.wordpress.com/2015/09/09/driving-a-sql-database-with-dynamo/
Responses:
1) DiGiovanni:
Brad,
It sounds like you found a great article that you could combine with your personal knowledge of the industry. I agree that it would be incredibly beneficial for design firms to have databases filled with information from sensors on previous projects. Since design firms typically specialize in a certain type of building or facility, most of their jobs tend to be very similar. They also probably work for some of the same owners repeatedly. They could know what the design did for those previous projects and make small changes to reach the goals that the owner sets out for them in contract. Although the contracts you mention are very harsh to the designers, it would still be incredibly useful for them to understand exactly how their design actually runs. One of the big issues of this type of contract is how the contractor builds the facility. If the design is not built properly, this may have an impact on the expectations of the design. This alter the actual data collected and may leave the design firm misinformed.
2) Wahbeh:
Jacob,
I think you found several benefits to database technology for the construction industry. Being able to access the drawings virtually from site is a major bonus for contractors. Although this does not replace the typical paper drawings, contractors can receive updates faster and keep the project on schedule. Also, one of the most important aspects of being a constructor is keeping records. With all revisions, change orders, and RFIs kept in database collection, they will not be lost in translation. These are crucial for finding when and where these parts were sent. This allows a better defense for contractors or designers when trying to find faults on the project.
3) Zhang:
Shuyuan,
You made a very good point about the subcontractors only getting the information they need for the project. With all of the design typically coming in one package, it can be difficult to sort through all the disciplines to find what specific contractors may need. With databases, it is easy to sort the data out into different categories. This allows all plumbing aspects to go to the plumber, all electrical aspects to the electrician, etc. This saves time and effort typically for the contractor. The general contractor still needs to make sure everything is coordinated correctly, this may not be as necessary for the subs. If the information can move more easily, the project typically moves smoother and faster.
Responses:
1) DiGiovanni:
Brad,
It sounds like you found a great article that you could combine with your personal knowledge of the industry. I agree that it would be incredibly beneficial for design firms to have databases filled with information from sensors on previous projects. Since design firms typically specialize in a certain type of building or facility, most of their jobs tend to be very similar. They also probably work for some of the same owners repeatedly. They could know what the design did for those previous projects and make small changes to reach the goals that the owner sets out for them in contract. Although the contracts you mention are very harsh to the designers, it would still be incredibly useful for them to understand exactly how their design actually runs. One of the big issues of this type of contract is how the contractor builds the facility. If the design is not built properly, this may have an impact on the expectations of the design. This alter the actual data collected and may leave the design firm misinformed.
2) Wahbeh:
Jacob,
I think you found several benefits to database technology for the construction industry. Being able to access the drawings virtually from site is a major bonus for contractors. Although this does not replace the typical paper drawings, contractors can receive updates faster and keep the project on schedule. Also, one of the most important aspects of being a constructor is keeping records. With all revisions, change orders, and RFIs kept in database collection, they will not be lost in translation. These are crucial for finding when and where these parts were sent. This allows a better defense for contractors or designers when trying to find faults on the project.
3) Zhang:
Shuyuan,
You made a very good point about the subcontractors only getting the information they need for the project. With all of the design typically coming in one package, it can be difficult to sort through all the disciplines to find what specific contractors may need. With databases, it is easy to sort the data out into different categories. This allows all plumbing aspects to go to the plumber, all electrical aspects to the electrician, etc. This saves time and effort typically for the contractor. The general contractor still needs to make sure everything is coordinated correctly, this may not be as necessary for the subs. If the information can move more easily, the project typically moves smoother and faster.
Cody,
ReplyDeleteI really liked how you introduced Dynamo as many students don't what it is and many if not all of us know the workings behind it. I personally believe that Dynamo can make the entire design process more efficient. Also after reading your post, I did not know how many programs rely on SQL, a language that most AEs-DB know.