Mine are all built in to my Revit Template. About 20 of them, and some of them are even pre built to take advantage of consultants linked files.

I dont use as many Smart Filters and smart selections in the navis exports, since they are built to accommodate the least common denominator (other peoples revit files). SO its largely separations by Categories. I dont break mine up level by level. I used to, because *i assumed* that was how folks would want them. But after talking to some folks that actually DO the Coordination, i was convinced to not break them up that way anymore.

Sure, they do the coordination level by level. But having the files broken up level by level doesnt necessarily help, in that regard. Its a buttload more files, and more pieces, and not necessarily helping. Plus, moving a riser on one level affects other levels. If they are different exports and different files, previous clashes that were resolved but now arent, might reoccur and not be noticed, if you dont rerun those smaller segmented exports.

Id grab you a screenie of mine, but Revit is locked up doing weekly exports right now.

If you care to post a screenshot sometime, that'd be great and appreciated.

So I'm actually on the side that does the coordination. It seems to me that, just like getting a Revit project started when on the design side, setting up a project that's used for spitting out NWCs can be a numbing process. Unfortunately for me, I haven't started one from scratch, yet; project gets setup and then handed down for maintaining during the coordination and construction process.

It is typical, in my case, to split level by level for future clashing of the Subs models against each other (it would be fun to talk to others and see what approach they prefer). But, just to clarify, I'm not taking in Sub's Revit models and exporting for coordination use in Navis. Instead, the model would typically contain Design Model content, some Construction Model content, along with the possible self-performed work content.

Yes, I've accommodated all of our common down-the-line workflows (.nw*, .dwg, .fbx, .gbXML & .ifc) into our standard office .rte.

No, we have one 3D view with one view template all to follow one process in which we manually export .nwc following pre & post-model-issue checks. We pretty much send out everything (of our model elements) - except entourage.

Personally, I've never done the "by-system", "by-level" or any other type of (.nwc) file-division - as our (Revit) model divisions remove much of the need (Exterior, Interior, Landscape, etc) and we have a fairly robust collection of Search Sets predefined in Navisworks where we can sub-select (to isolate) pretty much all of those things right of the bat.

We have all of our items broken in to search sets as well. But re exporting the entire file Every time you need to update one part of the model is goddamn annoying.

Plus, you don't always want everything to be in play when you're running all of your clash tests. So having some general things that can just be removed from the compact list is a bit faster.

And constantly clicking on search sets that have to go through the entire model every single time? Freakishly slow.

I'll post mine up when I get back to the office.

Sent from my Phablet. Please excuse typos... and bad ideas.

Aaron Maller
Director
Parallax Team, Inc.

We "only" export to .nwc with each .rvt issue, which is mostly a fortnightly affair, and yes, whilst it would be nice to have the export (time) reduced to "only" changed elements, since Revit doesn't record such, that's a non-starter. All said, we're almost always making universal changes between issues anyway, so are obliged to send it all "again".


We've clash test specific search sets defined - and when running isolated tests will use them to reduce what's displayed - but it's certainly a major bummer that Clash Detective effectively demands everything remain in play when batch updating all tests, resulting in desperately-busy, often useless, clash thumbnails.

There are many features/functions I'd love Navis poach from Revit (and vice versa) - but I'd happily start with having a VG/VT like function for views to support the retention of search-set-based filter/override settings.

My point was, i dont have to reexport the entire model, if i know that "what changed" was something minor in the Structural Concrete. Hell, even if i need to export my rather large "Core Shell" group, it still comes out to less than half of the total items in the model. Thats particularly handy because- when its a construction project- i have the 3D Room Tags in there, which are HELLA heavy. They take longer to export than everything else in the model.

More, though, its that the file is much more convenient in Navisworks. Sure, ive got Search Sets that find all my Millwork too. But it still takes longer to click it and wait for the progress bar. Particularly when there are 30 subcontractors model in there, that takes a minute or two (literally a minute or two). When i can just select my Millwork Export in the selection tree, and kill its visibility. I use my Search sets for my Fire Ratings, Materiality selections, Clearances, Construction Information (Pour Sectors, Schedule dates), and so on.

These are all of the Views and View Templates that are in my Template. Stairs/Railings is no longer named correctly, as it now contains all of Vert Circ, including Elevs and Escalators. A few of them also get tweaked project by project, of course. The one thats missing from my template is the new 3D Room Tag View, which is just the generic models made by the Rhythm Node i use for tagging rooms.

Then i use CTC's Batch Exporter to kick them all out. Every few days. Along with hunnnnnnndreds of CAD exports and PDF's.

Speaking strictly from a design side perspective (architecture):

No template. 1 3D view per revit file with everything on except model lines (people get creative those and I don't think it creates any value in Navis). Only export the geometry of that file (no links).

I let Navis do all the heavy lifting in terms of search sets.

These look familiar haha - there's also the added benefit of being able to remove specific NWCs (Save-As NWF - remove NWCs) that are not needed for Subcontractor MEP installation to improve the model performance on the iPad when pushing to BIM360 Glue Mobile.

Along with being able to Clash Arch Lighting, MEP Overlap, and Plumbing against the all of Subcontractor models to quickly see RCP alignment issues.

I also run a Clearance Clash with Arch Specialty Equipment & Generic Models vs all Subcontractor MEP models to find Clashes with in-wall/recessed Arch items like Paper Towel/Trash Receptacles, Fire Cabinets, and Medicine Cabinets vs Plumbing Risers.

This approach works very well especially when dealing with Third Party Architecture models that tend to break any/all Search Sets due to different standards from firm to firm.

I wish we did it more often, but when we do export, we've got Views set up for each Level.
From just above the Floor to just above the next Floor up.
We've found it's way too overwhelming to clash everything against everything, so if we split it up before exporting, we can examine just one Level at a time.
Most of the issues are in the interstitial space above the Ceiling, so we look from the bottom up.
We simply clash the "3rd Floor Architecture" against "3rd Floor HVAC". No Search Sets.

Would be even better if Navis would limit the clashes to what shows in the section box.
Then we wouldn't need to do anything fancy in Revit