Uses
of databases in design offices
Databases are useful tools
to any company or organization who deals with data. But that is not exclusive
to tech companies. Almost all companies have customers and the more data that
can be collected about them the better. Knowing your customers allows companies
to understand how to better serve them, increasing customer satisfaction and
company profits. Design offices in particular work with a large amount of data
about buildings and their users. As with any company it it useful to have the most efficient work flow possible. Databases can also be incredibly useful in keeping track of employee information by the human resources department. Databases can be useful for sharing large amounts of data between multiple users, but now there are so many different database options to choose from.
Databases make it easier to manipulate data
but in turn make it more complex overall. This puts significantly more amounts
of strain on a company's IT department. A company must decide if the pros outweigh the
cons in this situation.
An Evernote article
profiles an online database startup and explains where the future of the database
is headed. Orchestrate.io has pieced together the most useful components from
other large database stores to create the foundation for their own super
program. Overall, they have
sacrificed customization for use-friendly simplicity. And the company is
realistic about their industry. Technology must become more compatible and able
to interface with other, similar programs. Orchestrate.io automatically backs
up the data to Amazon S3 in case a user wants to later change database
providers. To me this seems like a good business practice. It is important to
be realistic, and your customers will recognize and appreciate that.
Resources:
https://www.evernote.com/pub/view/aengineer/ae-510/93e26d2a-0a80-455d-844f-601ee408c083?locale=en#st=p&n=93e26d2a-0a80-455d-844f-601ee408c083
Bridget,
We both wrote about databases in design offices and I really like how you started your post with a simple definition of what a database is. I also like how you connected it specifically to BIM and the Revit project from class. Something that can be especially useful that I has not considered is a physical database, such as the one created by Material ConneXion. Architects obviously have a specific appearance in mind when designing a building and it would be incredibly useful to be able to compare different materials in person. As I also stated above, one of the main purposes of a database is to streamline building practices so designer's and builder's time can be better spent elsewhere.
Gary,
You did a great job at explaining the technical definitions involved with creating databases. This knowledge will be especially helpful for our future assignment of building our own databases. I think it is especially important for new database user to understand that there is a logic model behind the physical data they are using or manipulating.
Overall you gave a lot of great detail and information. On a way to improve, it would be helpful to the reader to add in specific examples of these topics that they may encounter in their everyday lives.
Bridget,
We both wrote about databases in design offices and I really like how you started your post with a simple definition of what a database is. I also like how you connected it specifically to BIM and the Revit project from class. Something that can be especially useful that I has not considered is a physical database, such as the one created by Material ConneXion. Architects obviously have a specific appearance in mind when designing a building and it would be incredibly useful to be able to compare different materials in person. As I also stated above, one of the main purposes of a database is to streamline building practices so designer's and builder's time can be better spent elsewhere.
Gary,
You did a great job at explaining the technical definitions involved with creating databases. This knowledge will be especially helpful for our future assignment of building our own databases. I think it is especially important for new database user to understand that there is a logic model behind the physical data they are using or manipulating.
Overall you gave a lot of great detail and information. On a way to improve, it would be helpful to the reader to add in specific examples of these topics that they may encounter in their everyday lives.
No comments:
Post a Comment