Originally Posted by
cadtag
Before you get too far down this road, take a step back and really understand the"Why" of your standardization effort. Way too many company and people treat CAD Standards as a check list item, and assemble bits and pieces and decide "this is how we want to do it", then bull ahead.
That's not necessarily a bad thing, but it's still not a good thing. There are many approaches to standardizing CAD, many things that can or should be standardized, but the how and the what in your organization really ought to be driven by what end result you're after. The basic reason for that is that many of the wonderful goals companies think they'll find in CAD Standards nirvana are mutually exclusive.
One quick example -- standardization intended to expedite production of highly repetitive work that's all done in-house by a cohesive team calls for a simplicity in the standards -- e.g. make it only as complex as necessary, and no more. So short cryptic layer names can work.
Standardization that's intended to facilitate multi-discipline projects across multiple organizations running multiple CAD packages on the other hand, would mean that those same short names are a failure. UOE may mean Utility Overhead Electric Line to you, but it's unlikely to be easily understood by an interior decorator on the project team. For that environment, a full blown NCS naming practice is vital.
In a nutshell, define the goals you want to accomplish, rank them in terms of importance to your group, and only after laying that out and getting buy-in, start doing any standardization.