There are many benefits to using Revit, including the ability for all trades to work and collaborate on a central model. The engineers and architects can work on separate models then sync their work to the central model for the rest of the team to see. Although this is a useful feature, it comes with many problems.
One problem with Revit is that if the central model is created in one version of the software, the rest of the team is advised to open the project and only work in that version. Neglecting to work in the same Revit version can affect the central model when syncing. Furthermore, companies would have to regularly update their machines, which can be a tedious process. Another current problem with Revit is that some engineers and architects are still in the process of learning and mastering the software. Not everyone on the team may have the same level of experience using Revit, so a more inexperienced user may slow down the design process. However, this should not be seen as an issue since we all had to take some time to learn it, and we should be helping each other become more adept at it. An issue I encountered at engineering firms I have worked at was figuring out a syncing schedule. One firm was still relatively new to Revit so everyone synced their work whenever they felt the need to. The downside to this process was that it often slowed down the model to the point where no one was able to work on it. A different firm I worked for had a more organized way of syncing their work. An added feature on Revit allowed each member of the project team to see if anyone was currently syncing. This prevented multiple people from simultaneously syncing and slowing down the model. They recommended that each trade synced every thirty minutes in an alternating pattern, and this process proved to work well for the team.
Many people are aware of these current problems, so I am sure that software engineers for Revit are working hard to solve these issues. For now, using Revit just takes patience, practice and good communication skills.
Comments:
(Link)
Jake,
An important advantage that you mentioned was the fact that information can easily be shared between Autodesk applications. For example, you can build a model in Revit then use another Autodesk application called FormIt to analyze how heat from the Sun is absorbed by the building. This allows engineers to perform many different analyses without having to manually transfer information from one application to another. Like you said, these analyses help the engineers prove to the owner that they are choosing the best options for the building.
(Link)
(Link)
Spencer,
Data waste is a term I was not fully aware of, so I am glad you discussed this point in your post. BIM software, just like our brains, can be very powerful when used at its full potential, but this is a rare case. This may be because new features are regularly being added and engineers do not always have the time to learn them. The firms I worked for regularly had BIM experts come in to give us lessons on new features that could make our jobs easier, and I believe this is something that all firms should do.
(Link)
Data waste is a term I was not fully aware of, so I am glad you discussed this point in your post. BIM software, just like our brains, can be very powerful when used at its full potential, but this is a rare case. This may be because new features are regularly being added and engineers do not always have the time to learn them. The firms I worked for regularly had BIM experts come in to give us lessons on new features that could make our jobs easier, and I believe this is something that all firms should do.
(Link)
Abdul,
The ability of BIM to basically centralize collaboration speeds up the design process and produces higher quality results, as you mentioned in you post. Instead of having regular in person team meetings to present work from different trades, BIM software can easily compile the work from every member of the project team for everyone to see. This keeps everyone on the same page during every step of the design process. As collaboration through BIM improves, the faster projects will reach completion.
4 comments:
I appreciate that you shared your own issues with us and your own experiences. I also find that syncing schedules are hard adversity to overcome, especially in the ever-changing and chaotic field we find ourselves in. As leaders in this field, we must try to overcome these kinds of issues to create better efficiency.
Ina,
I like how you talked about the learning curve and process of mastering any sort of BIM program. It’s so important for people to work together within the firm, and sharing knowledge about a BIM interface like Revit is something that requires communication and a flow of teaching and learning. Effectively utilizing time is such an important part of our industry, but there are certain instances like with the learning of a program where investing some time now will prove to be beneficial for the firm later.
Ina,
With this post you brought attention to one of the biggest problems encountered with Revit in a collaborative setting. Syncing work can be a confusing and tedious task at times. I remember in the last firm I worked with, an engineer who was still learning how to use Revit accidentally deleted a few electrical panels along with their schedules and synced their work right before a set submittal, causing everyone to panic. We ended up losing all the information for good because there had been no backup for the central model. Although that was stressful, we managed to fix it and laugh about it afterward. Having a route to restore previous versions of the model might be helpful for Revit to prevent situations like that.
Ina,
I agree with you in that Revit requires a lot of patience and good communication skills when working in a team. I think you brought up one of the biggest issues that we students face when using Revit as we have to sync our projects and constantly be changing in between software versions.
Post a Comment