It seems like just yesterday we had taken a few trips back in time - well, to us time travelers it was yesterday! In real life though it’s been a little over a year. You see, the good Doctor was a bit miffed about the Cheetos dust that I had carelessly left on the controls of the TARDIS. It’s taken me this long to convince him I’ll take better care this time around. So let’s hop aboard and take a little jaunt back to the early days of CAD, say about the early-to-mid 80’s.
Keep in mind that I don’t have first-hand knowledge of CAD systems of that time period, but I do know how the available technology helped formulate how many work with CAD still today. It was a simpler time then... Computers were of limited processing power, graphics capabilities were short on color options and memory was expensive. To utilize those machines it was very common to have simplified standards as well. A typical CAD drawing was made up of layer names that went like this: OBJ which would of course contain the line work of the parts being designed or detailed. Since you need to show features that are not visible there was a layer called HID or in some cases perhaps HID2 or some other designation to indicate a scale with a different linetype. Centerlines would be placed on yet another layer called CEN and again this would be of another color and linetype. DIM layers, while not so bright, held your dimensions and perhaps your notes. Last, and for the most part least, you might find a layer called PHAN containing phantom objects used for objects that were there, but weren’t.
All of the above seems rather reasonable - for 25 or 30 years ago. I often see this type of layering standard being promoted today, but I think there is a better way. One of the things I faced when I began doing contract design and drafting in 1991 was establishing a standard to work by. It was important to comply with the standards of my customers and I was happy to do so if it meant getting work. But there was a dilemma in that each of my customers had their own standards and seldom did one customer’s standards match another’s. Ultimately I decided it was more time efficient to not comply with any of my customer’s standards. Instead of switching from one standard to the next between jobs my efforts needed to be focused on creating my own standards, then employ the power of AutoCAD’s customization to convert my drawings to the individual customer standard.
You may not have a need to supply drawings of varying standards but my hope is you will find value in how I ended up organizing my layering conventions and what it meant to my work flow. Over the years I have evolved some of the details but since it is patterned in a way allowing for modification to various standards there was no reason I couldn’t adjust my standard as I go. So without further ado, let’s get to it.
My work consists of machine design and when you get right down to it machines are simply a compilation of many individual parts. The overarching concept that I started with was one of association. To put it simply, any line work associated with a part would exist on that part’s layer and each entity would have a color and linetype to indicate its feature (centerlines, hidden lines, etc.) The first order of layer management was to arrive at a naming convention. I Came up with the idea of using just three or four patterns and each pattern would be appended with a sequential numeric value. So for manufactured parts I started with DET0000 and the basic line work would be continuous, color black. Next, there are typically many purchased items involved and I wanted to segregate these items since they would not require detailing so, PUR0000 it was with line work of continuous, and by a stroke of genius the color was red. In cases where I needed a reference detail or assembly I used a REF0000 layer and in this case the layer linetype was set to phantom and the color was gray. Finally I needed a layer that would hold the contents of the part(s) that a machine was designed to work on, that would be PRT0000 layer, the linework would be phantom and the color would vary.
Creation of each layer is performed automatically with a combination of a custom toolbar and an AutoLISP program that looked up the next sequential number in a text file then incremented it. I created other programs that would allow me to isolate one or more layers and turn on or off layers by the pattern or by picking. Having linework associated with the layer meant that I would still see all centerlines or hidden lines with the particular layers when isolated. You can see what that means in these images.
Isolating layer DET1316, DET1317, and REF0165 gives you everything you need to work on those details.
Isolating layer CEN doesn’t really offer you much value.
Another important aspect of how I’ve set up my layers is in the construction of the block libraries that I use. When a common part is needed whether it is a fastener or a commercial item my geometry is always placed on layer 0 and if centerlines or hidden lines are needed I will keep those entity types on layer 0 but created with the corresponding color and other properties. When inserted into the machine assembly or part detail they will be placed on the associated part layer and the line properties remain intact. The trick is if the item needs to be exploded I use an AutoLISP program that gathers the exploded entities and automatically changes the layer to that which the block was inserted into. Some of the more recent AutoCAD versions may have that capability out of the box.
The fly in the ointment are those files that you use from a third party source. Many vendors offer a vast array of product drawings at no cost and many items are available from the internet free for the taking. What a huge bonus in time savings. While these can save you lots of time in design you might consider an intermediate step before using them - spend a little time changing them over to your standard. That can save you some headaches down the road. And don’t forget to check dimensional accuracy.
Finally, I created much of my standards with automation in mind. When I began, long file names didn’t exist - we were limited to the old DOS 8 characters with an extension. The use of shortened layer names allowed me to create macros and AutoLISP programs that once a layout was completed each detail part file was created with very little manual effort. For now I’m sticking with the short file names because I find typinginreallylongfilenames.dwg names somewhat cumbersome, but I can see where a well laid out convention could work.
Well even though the use of the TARDIS means we can arrive back at any time we desire (so we’re not going to be late) it may be prudent for us to take our leave now. I don’t want to run the risk of a sudden Dalek appearance potentially causing damage to the TARDIS.