CAD Standards – Your Layer List

Standard Layers are a big deal. Getting them right is very important and getting them wrong is very easy.

I have seen so many vague lists that I have been frustrated trying to follow them. They do not give the right amount of information that is needed. They leave gaps.

Here is what I think needs to be documented in your layer list.
Make sure it includes:

• Layer Names for All Disciplines
• Default ON or Freeze
• Default Lock Status
• Default Color
• Line Type
• Line weight
• Plot Style
• Plot/No Plot
• New VP Freeze
• Layer Description

If you have not covered all of these areas,then your users will get creative with the ones you have left out.

Basically – define everything that is in the Layer List Dialog box.

Layer names are the first step in a CAD Standard. Most firms start here and move forward with other areas. I have seen some CAD Standards that are just a layer list and they stop there. Following the AIA and the NCS will put you in line with most firms.

Here is some wording that starts to address layer standards:

The National CAD Standard & AIA CAD Layer Guidelines are to be used on all projects as they apply.

The base nine colors (i.e. 1-9) should be used for each discipline’s base layer names. These colors have names as well as color numbers.  Other colors can be used as the disciplines define their layers.

The format of layer names must follow the two-four-four-four-one standard, No layer name can exceed this convention. The preferred method is to use just one character for the discipline designator.

The last character in the layer name, called the status field, will be modified to allow for scale factor designations in the layer name (i.e. ¼” will be 0048, ½” will be 0024; ex. A-anno-text-0048 is a ¼” text layer) This field code will be used for all scale-specific layer names.

Specific layer names will define settings for linetype, color & line type. These will be broken out to allow for specific use.

All graphics will be created “ByLayer”. No assignment of Linewieght (LWT) to Layers will be used. Everything is drawn using default Line wieghts and plots bylayer.

Keep layer names as short and simple as possible. To do this use the base layer name for all objects that pertain to the entity you are creating. Break out layers only as needed.

An Appendix can be added that has layer names defined more specifically to each discipline.

From the Autodesk MS Ride team site…

Team Autodesk

Autodesk believes in being a responsive community partner. Through our products, values and actions we strive to build and foster healthy, sustainable communities. Our mission is to improve and enrich the lives of those in need by supporting vital community programs. We care. It’s what we do.

The number of people living with multiple sclerosis increases every hour of every day. This astonishing rate is not going to diminish, nor will it stop, until we’ve found a cure. Research has made some incredible advances recently, but the world can still only offer disease management drugs and therapies to the 400,000 people living with MS in America.

Help Team Autodesk in the Fight Against MS!

This is the third consecutive year we’ve formed a team for the MS Bike Tour. Join our team as a cyclist or a volunteer! Make a donation online! Send in a check! Talk to your employer about becoming a sponsor of the MS Bike Tour! There are so many ways to make a difference in the fight against MS, and it all begins right here.

This is especially close to my heart.  My sister-in-law suffers from MS.  If you are financial able – please consider sponsoring this team in their efforts to raise money to find a cure.

Buried in the User Docs for the 2010 version of AutoCAD Architecture is a cool little cheat sheet for the new User Interface. The Ribbon is here to stay and you need to get familiar with what it does. This PDF shows what is what and where it is located.

Give a quick look…

ACA 2010 User Interface Cheat Sheet

Thanks Autodesk…

CAD Standards need to address all the info that might be in the template files or that need to be set by the users. The Standard Settings and Styles are defined and documented well enough to let people know what they should be using. By defining these in your standard you assist them to verify what is being used.

Why list these or show them in the standard if they are in the template? If they are already set, then there is no need to show them – right?

I think not. By showing the users what the standard settings, styles and more are defined they can verify that they are using the right ones. There are many times when the file they are using may get changed up. When copying from old files or importing info. So I think that the best way to make sure that everything is set correctly is to show everyone what the setting actually are.

Even the most basic things like Document Settings need to be documented. Do you use Decimal or Architectural Units? Do you set the Unit round-off?

Do you use Metric files? Are you using true metric? Real metric? Not the fake US translated from Imperial metric? Do you define the linestyle library to use? What about blocks and cel libraries?

There are so many that need to be documented. This will keep everyone on the same page and outline the exact target to be hit with the critical settings inside CAD.

I have used a method of management in many areas of my career that defines not the target, but the boundary limits of a successful task or function.  When I started looking on the internet for supporting documents to what I thought was fairly commonly used, I found very little.  What I did find was spot on, but not very extant.

I have not fully defined when to use what I call Boundary Management, but I can give you a few examples.  I think it is a change in perspective that makes a few things easier and works well in some cases, but not all.

• It can make delegations easier
• It can make defining CAD Guidelines easier
• It can allow flexibility while still following the rules

First here is my definition:

Boundary Management consists of defining the general target and the limits of constraint.  It may consist of setting a small well defined target and allowable area of deviation.  It can also define a task that does not even have a hard target at all.  It may just be defining the target by stating what it “is not” rather than what the target “is”.

Think of it as a fence around an area of freedom.  As long as you are inside the fence, you are free to do what you think is most effective.  If there are any limits to the freedom, they are stated.

Sometimes it is easier to define what something is not, rather than what it is.  At times like these, the fence is defined by your “NO” rather than your “YES”.  Even when you end up defining what the target may be, you may get started by defining what it is not.

Let’s apply this to a CAD issue. CAD Standards are a good place to start because I know that I apply this method to my CAD Standard.

When I define what is in the CAD Standard, I include exact targets to hit.  Like Text sizes, Fonts, and such.  I specifically say that ROMANS will be used.  That is a hard target.

But there are also areas that I do not define, like creating Building Elevations.  I define the file name, the layers to use, but I do not define how they actually create the file.  Some may generate it from plans, or draw it from scratch.  There may be other ways like attching xrefs and drawing lines out from the plan drawing (like hand drafted methods).  They may rotate the plan or pull the elevations out like an unfolding box (I call this the Happy Meal method). They can choose to create the elements any way they choose as long as they meet the hard targets for layers, text, line weights, etc.

There are two parts to the above discussion.  First, some hard targets and second, some boundaries.  The hard targets are defined and the fences extend to whatever we tell  them that they cannot do.  If I do not want them attaching XREF’s, I will put that in the standard.  If I do not want them to create Happy Meals, I will put that in the standard.

Hopefully you get the idea…

Another area may be assigning tasks to a group of CAD users.  You may ask them to brainstorm on a better way to get plotting done.  You will paint the target by telling them that it needs to be easy to use and the solution has to answer the open issues of plots not being consistent.  You also include the boundaries, if any.  Boundaries may include not buying new plotters, not buying software, not editing the pen table, etc.  These are the limits and the boundaries.  Anything that hits the target and does not violate the boundaries will be considered.  It provides a large area of options, allows the team to be creative and sets a target.

This is what I call Boundary Management.  It can be used effectively in many areas but not all.

Boundary Management is a vital tool for any manager as long as it is applied correctly.  It must be used at the right time, in the right way and in the right situation.

Boundary Management as previously defined is loosely defining the target and setting up limits. It is not creating a bull’s eye, but rather a ballpark.

So when do you use this method of management?

Here are a few areas:

When defining your CAD Standard – this may include quite a few exact targets, but some areas may allow a little wiggle room.

When you are seeking creative answers to problems – this allows people to think outside the box (as long as they are still in the ballpark)

When you are researching new tools – finding new software tools is not an exact science. IF you restrict the search you may overlook some valuable options.

When coaching an employee – let them define a few things. If you have established every last nuance of a process, then they are little more than slave labor.

When delegating a task – paint the target well, but in broad terms and define what is not allowed. By giving someone some leeway in the method they use to get the job done they can bring value to the process that you never thought of.

Boundary Management can and should be part of your varied management skills.  It may be already, but if it is not, think about giving it a try.

When should you not use Boundary Management?

There are several areas that come to mind where this kind of management style may not work well.  If is is used in the wrong way or for the wrong issue, it may actually cause more problems.

When the issue really only has one answer: Some issues may only have one solution and the restrictions are too great to allow much flexibility.  This may include issues like work hours or job duties.  I would not suggest that you allow too much flexibility in junior staff related to work hours.  For support personnel, they need to be on-site when the workforce is there.  Adjusting work hours may not be an option.

When the staff does not have enough knowledge to be creative: Sometimes the staff you are working with just do not have enough experience to work under a boundary system.  they need to be told exactly what to do and exactly how to do it.  Until they gain some wisdom and perspective, allowing them to bounce around within the boundaries can be unproductive.

When everyone is watching: This method may not be good for mission critical and time sensitive issues.  Getting the job done quick and right may apply to just about everything, but some items are critical and must be perfect.  Restricting the target to something exact is called for.

When the people are too creative: You may need to revisit the boundaries when working with very creative teams.  They could think of things that don’t violate the boundaries, but do not achieve the result within “unspoken” guidelines.

Making Sheet files – the files you plot from – is the core output process for the projects you create. Getting them right will increase your consistent output and processing of Construction or Manufacturing Documents.

Here are some thoughts on getting them right.

Sheet File Creation

Sheet files are located in the Sheet folders under the Discipline folder.

Sheet files are created to display the plotting information and construction annotations needed to produce an output file for plotting.

To create the Sheet file you may overlay (or attach – for nesting) multiple Model files into Model Space and the border into Paper Space.

One Sheet file represents one Plot file. I am convinced that while using multiple tabs in paperspace is allowed that in a multi-user environment, it may cause confusion. So stick to one tab for all output files.

The first Layout Tab shall be used for full size plotting. It will use the default name “LAYOUT1”.

Attach Nested XREF’s to sheet files. This means that you may attach a Model file to a Sheet file that has nested files attached to it.

XCLIP may be used on Sheet files for irregular shaped displays of Model file data.

Image files are placed into the Sheet folder and referenced only to Sheet files.