The Current Workflow:
When I first started doing BIM Coordination 4 years ago, the typical workflow went like this:
- The subcontractors created a 3D model using design or fabrication software
- The subcontractors uploaded their model to an FTP site at a designated time
- The BIM coordinator downloaded the design / fab models & created a federated Navisworks model
- The BIM coordinator ran clash tests using Navisworks & generated clash reports
- The Coordination Team met & discussed the Clashes
- The process repeats.
When I ran coordination meetings, this process was pretty successful, but it was slower than it should be. For the most part, coordination moved along, but there were often times where clashes would go untouched for weeks at a time - multiple weeks. The most common answer I recieved about why the clashes weren't promptly fixed, "I didn't know what the <other coordination team member> was going to do with this clash. I was waiting on him."
BIM 360 Glue helps solve these problems. It gives your team the conficence that the model they're viewing isn't obsolete - it's as up-to-date as possible. It frees your team up to solve the minor clashes on their own time, and allows the Coordination Team as a whole to maximize meeting time to discuss major design issues & possible RFIs during the weekly Coordination Meetings.
In the above demo, I saved my model, uploaded it to BIM 360 Glue, ran a clash test on my model, notified myself of my responsible clashes via email, and used the Clash Pinpoint tool to locate each clash for revision. Finally, I re-uploaded my revised model to BIM 360 Glue. The video shows this taking place over 10 minutes (I edited out the loading & waiting so that you wouldn't get bored watching it).
So let's compare this to the old workflow. With the typical Navisworks / GC0-controlled workflow, it would take about a week between revisions for the entire team to be able to view even one revised clash.
BIM 360 Glue gives the entire Coordination Team 24-hour access to data that previously only the GC/BIM Coordinator had access to.
The New Workflow:
So let's go over the new workflow with BIM 360 Glue.
Model & Fabricate:
Just as before, the subcontractor / modeler would create their 3D model & then upload the model. However, with Glue, it's one touch of a button in Revit or Fab CAD MEP instead of uploading the model manually to a folder on a server.
Once the model / models are uploaded, the BIM Coordinator / GC creates a federated model just as before. However, instead of creating the Federated Model in Navisworks, he creates a Merged Model in Glue.
This is beneficial in two ways. Once the BIM Coordinator creates the Merged model in Glue, lines up the models, and creates his clash tests, the model is ready for the team to view at anytime via the cloud.
Furthermore, the model is opened up to the entire Coordination team to clash test, create viewpoints & markups, and assign responsibility to issues.
Pinpoint & Revise:
Here is where the enhanced BIM 360 Glue workflow really comes in. One of the best attributes to BIM 360 Glue is the Notify button in the Clash Test module. Notify allows you to email a clash or clashes to a specific, responsible team member. The email is sent to the responsible party within a minute (which is pretty cool).
But what's really cool is that BIM 360 Glue takes this information one step further. Open your model in Revit, AutoCAD or FAB CAD MEP, and utilize the Clash Pinpoint tool to locate each clash in your model.
This greatly improves the revision process because it opens the power of coordination to everyone on the team and locates each clash inside of the design or fabrication model.
Here are some quick takeaways from this discussion. With BIM 360 Glue, you can:
- Confidence that the model being viewed is the Single Source of Truth
- Greatly improve the speed of BIM Coordination process
- Improve transparency & accessibility to the Federated model