Thought of one other wish item which builds upon the last suggestion/post.
If a company could store all their standard layers and their settings in the Layer Key database which is outside the drawing, Autodesk could add a feature to the Layer Manager allowing the user to use a "add layer" selection menu based on the external layer key database. I'm thinking a good example for the use of this feature would be when we create details, we don't necessarily add "objects" but often draw with lines & circles. The user could easily add a company standard layer and start drawing on it. I'm sure there would be other uses, but it still adds flexibility to the ABS software.
Thanks.
Joshua
"Joshua P. Benoist" wrote in message news:4006f75e_2@statler...
Hi,
Please allow me to describe our situation, our goals, our problem and then propose a "wishlist" for the future.
I am part of a core team assigned to create a single company template that, as best as possible, conforms to our layer standards. Our firm has a large number of engineers across many diciplines. This template is for M,E,P,FP only. Our goal for this template is to make it as user friendly as possible so engineers do not have to set up systems or configure layer settings with every project, every drawing. We have identified the most commonly used systems or put another way, ones we do not wish to do without. We would like standard systems readily available in the drop down for engineers to select from and what they draw go to a standard layer with color and linetype preset. We want to do this with one template which we would roll-out to the users, versus having to roll out more than one template and add complexity.
Our understanding of the way Autocad intended ABS to be used, we would setup all the systems and layer overrides at the system level. The layer key would contain the base layers (ie. M-Duct, P-Pipe, E-Cndt, M-Eqpm etc) and those layer settings. The System would override or add to the Layer Keys (ie. M-SYS-Duct or some variation). However, Autocad allows us to link the system to a layer key and preset colors/linetypes, etc. But this is not the original intent, not for EVERY system. The drawing itself does not contain every layer, but creates the layer from the key and system overrides when the system is used in the drawing. Absolutely love it Autocad, you are on the right track!
The problem is, we cannot afford for every engineer, across every dicipline, to waste time with layer or key settings or adding systems, every time they create a new drawing. We have decided to create layer KEYS with layer settings preset for all of our systems, and to do this in one template. Sounds great and the work is 90% complete, however Autocad did not intend for the layer key to grow soo large. We currently have over 1200 keys and need to add roughly 450 more. With all the layer keys, it now takes 4-1/2 minutes to add a single key. There is no option to copy and paste or import. It has to be one at a time. With an 8-hour day it will take approximately 5 days non-stop or a month if we are to get any other work done. We have come to the realization that these additional keys slow down the duct add/pipe add/wire or conduit add dialog boxes. We feel this slowing is a far cry better than allowing users to set their own standards or configure systems every time. We will live with it for now till a better/acceptible solution presents itself.
We want this post to address the layer key limitations, what are our options to add the remaining 450 keys?
Is there a quicker way to add these keys? Can we use Visual Basic or a database editor/text editor? Should we continue to plug away?
Finally, we want to propose a "Wish/suggestion." Please increase the layer key capabilities to handle more keys efficiently. Two, please make a layer key database outside the template, possibly in a subfolder with the MvParts catalog and other content. it would be in a location the drawing/template references to add layers as needed, but seperate from the drawing. Another suggestion would be to build in copy/paste and import/export functions to the layer key database. One suggestion would be to allow the system itself to define the layer settings (but this would still reside within the drawing), a good option nonetheless. Our last suggestion would be to add an off-drawing/template database for the systems and their settings. This could go in the same file as the layer key database or share database editors/functionality.
Hope this helps. Please RSVP, we are going to grow old adding keys...LOL.
Thank you in advance.
Joshua