Graphics Programs Reference
In-Depth Information
Figure 10.24 Granted
confirmation
Worksharing Best practices
Now that you have a general understanding of how worksharing and worksets
operate, take a moment to consider a few best practices.
think of worksets as containers. Worksets aren't layers as in CAD. Think of
them as containers for major systems in your building (interior, exterior, roof,
core, and so on). You need to manage or be mindful only of objects that belong
to user-created worksets, such as the following:
Datum (levels and grids)
Geometry (building elements that show up in multiple views)
Rooms (the spaces that can be tagged)
Be mindful of the active workset. As you're creating datums, geometry,
or rooms, be mindful of the active workset. And keep in mind that Revit
Architecture automatically manages the worksets for everything else (views,
families, and project standards), and these cannot be changed by the user.
Borrow elements on the fly. Don't check out worksets by making the entire
workset editable. Instead, just borrow elements on the fly. This approach lets
you avoid many conflicts that occur when one person needs to modify some-
thing you own (but don't really need) in the model. With the interconnected
nature of buildings, you don't even need to deliberately make an element edit-
able. All you have to do is modify an existing element, and Revit Architecture
will transparently borrow it for you. This works the same when adding new ele-
ments as well.
associate linked files to their own workset. Associate any linked files to their
own workset. Then you can open and close the worksets associated to those
links. This strategy is much more predictable than loading and unloading links
 
Search WWH ::




Custom Search