In class, during Huw Roberts’ lecture, Revit/BIM’s current problems were
discussed. Roberts made the point that Revit plans are static, and not dynamic.
This is useful to see different versions of the same building, but it means
that these plans are not easily changed on the fly. In a constantly changing
project where new information is coming in everyday about a construction
project, changing the designs in Revit is a necessity. It would be easier to do
if these plans were not static as they are now and were dynamic. This feature
contributes to the problem of Revit being a platform that is slow to change
easily.
Another point that was brought up during Roberts’ presentation was that
Revit and most other BIM programs can only show one specific thing at a time.
Revit, in particular, can only show the physical design model of the project
being built. Revit cannot show things such as a temperature reading overlay of
any rooms or the building as a whole, shadow casting of the building, cost of
the building or individual sections of the building, etc. It would be very
useful if these models could display this information along with the physical
model that is already being displayed. There is more to the design of a
building than just the physical model and the fact that Revit can only display
the physical model is a significant problem with Revit.
Another problem with Revit that was discussed during Professor Mitchell’s
lecture arises when someone needs to make multiple models of the same
construction project. If someone wants to make an MEP model or an architectural
model or any other type of model, that person must make entirely different sets
of models for each application. This creates a problem because models are not
linked together within one file for ease of access. There are no things such as
layers to differentiate between different applications of models. It also
creates a time constraint problem as it takes time to create all of these
different models. For projects that are in a time constraint, it would be much
easier to edit an existing model with a different layer and overlay that layer
over the main model instead of creating an entirely new model from scratch. The
counter-argument to this problem is that the people who create and look at architectural
models do not necessarily care about objects or details present in an MEP or
any other type of model.
**Edit**
Comment 1: http://ae-510-ay15-16.blogspot.com/2016/01/b3-group-b-farnelli.html?showComment=1453818470654#c6563366622835996056
Comment 2: http://ae-510-ay15-16.blogspot.com/2016/01/b3-group-b-kai-waechter.html
Comment 1: http://ae-510-ay15-16.blogspot.com/2016/01/b3-group-b-farnelli.html?showComment=1453818470654#c6563366622835996056
Comment 2: http://ae-510-ay15-16.blogspot.com/2016/01/b3-group-b-kai-waechter.html
Hello Mark,
ReplyDeleteI really like your integration of last classes lecture into this weeks blog as it fits perfectly with our topic. I also like how you focused on technical issues with Revit which is on the opposite spectrum of how I looked at this weeks topic. I focused more on problems associated with incorporating BIM into a business and how it fails to meet certain expectations.
Mark,
ReplyDeleteI found your discussion of the Revit disadvantages interesting. It would be very useful if Revit would allow systems to be put on different layers which could be turned on and off similar to layers in AutoCAD. Revit offers some development of non-architectural systems including fire systems and HVAC yet this aspect of the program could definitely be expanded upon. It would be interesting to see how they complete this as the architectural and structural systems often overlap. I think that Revit, if properly developed, may become the next big thing in streamlining design and production processes. Additionally the development of dynamic functionality and the addition of temperature, light, and other analysis features would further increase the capabilities of such a program. The better Revit becomes at performing these functions the more likely it is that the program will be integrated into common practice.
This comment has been removed by the author.
ReplyDeleteMark,
ReplyDeleteI really enjoy that you used Huw's lecture as an example. As he explained, it is extremely hard to modify a static model in Revit once it has been initially designed. Another huge problem is a editing a linked model to make multiple models as links are a huge disadvantage in Revit. As this is extremely easy to complete in other design programs, I do agree that Revit falls short in this case.
~Danielle