- DATA INTERPRETATION Ideally the architect should only be sending relevant data to the engineer. This being the case the engineer will be able to start on the structural analysis of the building and produce a logical solution for the building structure, columns, floors etc at an early stage that may well, for example, facilitate the designer as there will be less ‘head scratching’ when deciding on spans etc.
- MANAGING CHANGE Once a proper BIM workflow is established and exercised both the architect and engineer can work better within their own areas of expertise and at the same time feel confident that what they are doing is known to the other party via an accurate, up to date, BIM model.
Ideally, as they progress in the design and eventual construction phase, which will involve constructors, all will be in sync with the use of the BIM model if this workflow compatibility is maintained and communication is multi-directional, between all design professionals, allowing any design changes to be handled in an intelligent way and recorded in the BIM model.
Once the constructor comes into the picture and the construction starts, it becomes more obvious that the architect and engineer have been working on their own particular models and only
used the other party’s model as a reference but all the data is combined in the BIM model for all involved, particularly the constructor.
- OWNERSHIP OF DATA Both the architect and structural engineer manage and maintain their own models. The reason is that workflow compatibility requires that the real-world setup be mirrored so parties carry full responsibility for their part of the project, they may well also require mutual ownership of all BIM data. It’s not file compatibility but rather workflow compatibility that can make or break open collaboration between the various stakeholders of the AEC industry. With open collaboration all participants of the AEC workflow enjoy unique benefits.
- UNIQUE BENEFITS Project members can choose to work with the best of breed solutions in their respective fields and locations.
Project members can decide about their software upgrades independently from their peers in different projects.
Project coordination errors are greatly reduced due to workflow level compatibility in contrast to just file compatibility alone, the old system!
www.sketchUcation.com
52