Reflecting on an oft debated subject, I point to a well argued blog post:
(bim)x: Should This Project Be a "BIM Project"?. The list presented weighs out costs and benefits, but two keys may be missing: flexibility and motivation. A typical architectural firm, uninitiated in Building Information software (BIM), may well tick down the list to a resounding "no," When working in Connecticut, I was often reminded of an unofficial motto: "the State of Steady Habits". We are effective with old habits, and so it is hard to evolve to new tools. In terms of leveraging new technology, how did it come about that the time honored use of the hand ledger was finally overtaken with automated spreadsheet? In Architecture, what is the tipping point of moving from careful use of smaller amounts of personally thought out information to mapping out large quantities of interconnected data, both visual and quantitative?
No comments:
Post a Comment