Wednesday, August 10, 2011

Projects with Shared Details

These projects typically have "standard/common/shared" details AND "specific/custom" details. It's a pretty common question, "How do I manage the shared details?". In an earlier post I wrote about the Insert Views from File tool that Revit added several years ago. The overall strategy I like boils down to this list:

  • Do all the detailing that they share in "one" project
  • Do all the detailing that is shared in Drafting Views, not model "live" views
  • Use Insert Views from File to pass them to the other projects.
    • This allows for local view referencing of callouts/sections etc
  • Do all shared detailing in the "master" project
  • Only worry about keeping the sheet and detail numbering updated between all sheets
  • Don't bother to update the details in each other project, the views could be blank for that matter (except for a piece of text, has to be something in the view)
  • Print all shared details from the master
    • Strategically use a separate sheet numbering scheme for shared details so they don't compete with project specific details.
    • Only necessary to manage sheet reference and detail numbers during the course of the project and add new shared details if they arise.
    • Easiest when detailing is done in later stages of documentation naturally

I think that it's easy to miss that it isn't really necessary to put "finished" details in all the other project files to keep them "up-to-date". The only thing we need to keep "up-to-date" is the sheet number and detail numbers, assuming that detail sheets are printed from the master project instead of from each individual project. That's why I suggest a separate sheet numbering scheme for these shared details, so they don't compete with the rest of the set.

3 comments:

Duncan Lithgow said...

I've described my proposed solution here at AUGI: http://forums.augi.com/showthread.php?139087-Detailing-a-multi-building-%28campus%29-project&p=1170962#post1170962

Steve said...

My post describes a workflow that lives within the confines of Revit processes, intentional process. Revit was never meant to do documentation in a separate project from the geometry.

Over time it has expanded on what is possible through links but it is never as integrated as a single model. Fundamentally Revit is meant to do one building in one file (per discipline).

The effort required to pull off what is described in the AUGI post will be much more tedious and finicky than the process I describe.

Duncan Lithgow said...

I appreciate that what I've described is more complex to set up. But once it is set up (by one or two people) - then Callouts to details in each building are placed via the linked view without having to open each project. I don't have to make a placeholder view to refer to, and I don't have to check & recheck that where I have placed it in my model is the same as where it was placed where it's been drawn. References just appear in the right place as long as RVT link to 'Details_project' on Level x is shown by linked view to Level x.