View Map Organization?

[Brandon-W_DWa]

I'm curious how others organize their View Map? Primarily, whether you use Clone Folders or not.

For years, our company template has had clone folders for every type of view. This was useful in that staff didn't have to remember to apply the correct settings for each view, but the downside is that we have dozens of clone folders for sections (for example), to account for changes in scale, layer combination, renovation status, etc. Keeping with the section example, a 'Sections' clone folder specifically setup for 3/4" Wall Sections contains not only the appropriate views, but also millwork sections, building sections, section details, etc.

Creating a new company template from scratch is allowing us to rethink how we work, in an effort to support consistency and efficiency, and this is probably at the top of my list.

[Nathan Hildebrandt]

I personally don't use clone folders as there are several items that I don't want automatically pushed into saved views. So that users don't struggle too much with knowing what to do when saving views, I have all of my view settings named to align with the view type that they are saving. For example for a Slab Setout drawing I have a Layer Combination, Model View Option and Graphic Override named "SlabSetout" so that the view will be saved by a user to produce the graphical output that is expected to be achieved for each view type.

Yes it results in a lot more MVO's and GO's that are really needed but it means that all of the views can also be QA checked in a project schedule to make sure that they have been saved correctly.

Regards Nathan

[jl_lt]

We do what Nathan suggests but embedded in the cloned folders, as each plan type has its own layer combo and whatnot. Since we are very few people there is not much trouble.  Wish we could hide unused views though

[JeffH]

I have ours setup with Layer Combinations, MVO's and GO's as well for each drawing type/Division that we have.

We don't use any cloned folders within our template.