Model Coordination process questions

[chubbard]

We got our first look at BIM 360 last week, watched the tutorials and have started playing around with it. WE have a couple questions about how the coordination works.

1. Tutorial clashed entire models against entire models and used all Revit. How does it work with DWG and IFC models? We get a number of both of those.
2. Can we connect Local Navisworks to Bim360 models, like we do with glue, and use it to clash?
3. Can we pare down the clashes in BIM360 using searches or filters? Seems like we get lots of false clashes just clashing entire models
4. What do we do when the origins do not align? Revit is pretty easy. But moving entire DWG files can have issues, and IFC files really cannot be relocated.
5. How do we ensure that all the models are properly aligned? Large misalignments are easy, but what about small issues that are hard to see? 

[richardparker]

Hi Christopher, a few notes in-line...

1. Tutorial clashed entire models against entire models and used all Revit. How does it work with DWG and IFC models? We get a number of both of those. Currently Model Coordination works with both Revit and DWG. IFC is next up. 
2. Can we connect Local Navisworks to Bim360 models, like we do with glue, and use it to clash? Not currently. Connecting desktop products to 'next-gen' BIM 360 is a priority, so stay tuned. 
3. Can we pare down the clashes in BIM360 using searches or filters? Seems like we get lots of false clashes just clashing entire models. We are working on tools that will allow you to be more precise in selecting the subset of the project that you want to coordinate. Currently you are restricted to models, we will move beyond that (e.g. systems, locations, levels etc.).
4. What do we do when the origins do not align? Revit is pretty easy. But moving entire DWG files can have issues, and IFC files really cannot be relocated. Currently you are required to align models in the design product, it is not yet possible in Model Coordination. 
5. How do we ensure that all the models are properly aligned? Large misalignments are easy, but what about small issues that are hard to see?  The viewer does have tools that will let you zoom / measure model aggregates, so although it is not automated you should be able to identify misaligned models with the available tools. Let us know if not, or how you would like to see things improved. 

[chubbard]

So do we have a time frame on these items?

We really cannot use it in the current form. Every project we do has an IFC file from Tekla and all of them are misaligned. Tekla users claim there is no good way to align in Tekla. Wrong but that's what we get all the time. 

So i see we can measure, but cannot adjust unless connected to Revit, and then only Revit files. 

So really till we get some ability to move or align and read more file formats its kind of too soon to really use.

[richardparker]

Thanks for the feedback Johann. We don't have specific dates for resolving these issues but recognize their priority and are working hard to address them. You can find a high-level overview of the BIM 360 roadamp including Model Coordination here - http://blogs.autodesk.com/bim360-roadmap/find-out-what-the-bim-360-team-is-working-on/ 

Cheers

Richard 

[Anonymous]

Hello,

In testing the module for a recent presentation demo, I toyed around with single Revit models that represented the three primary disciplines. However, I couldn't get the depth I was accustomed to.

I used my classic BIM 360 Glue trick. First, I'd create 3D views oriented to floor plans in each discipline's model in Revit (the old RMB/View Cube>Orient to View>Floor Plans.) For the single MEP Revit project file, I'd make multiple 3D views oriented to each floor per trade (using view filter or worksets for visibility.) Finally, I'd go to Publish Settings on the Collaborate tab and make a Set called "Model Coordination" to only include those 3D views of each floor.

After uploading and publishing finished processing in Docs, I could go to the Model Coordination module, select clashes, and filter the clashes per each 3D view.

The images in the AKN suggest separate RVT files but, that's not exactly necessary.

[Anonymous]

More Screencaptures of the clashes per my previous reply.

[richardparker]

Hi Bill, many thanks for your feedback and pleased to hear that you are having success with the process you describe. Certainly using Revit views to break the model down into manageable subsets is a recommended workflow. We will work with our content team to update AKN. Your feedback is appreciated! 

[Anonymous]

Richard,

I had time to also test the Design Collaboration Module recently and that feature automated the creation of folders for each Team collaborating. One of these folders is called the “Shared” folder. At a glance, it appears we’re back to creating data silos in the same project by publishing files to separate areas in Docs. M.C. uses a share folder in Plans while D.C. uses a share in Project Files. Could you elaborate on why the M.C. and D.C. modules wouldn’t use the same setup process and share the same resource files being published and packaged by model authors?

[richardparker]

Full agree with you here Bill and we are working with the Design Collaboration team to ensure the two modules can work on a shared data source. 

Thanks,

Richard