Are Bad CAD Standards Worth Having?

Many of us have very good standards in place and we go to great lengths to enforce them. We review them on a regular basis and update them as needed. Others have acceptable standards that help to get people on the same page but leave a few thing to the imagination (and CAD users can be very imaginative).

I want to speak to those of us that have a very weak standard. One that has many holes in it. One that fails to define the needed items that everyone uses every day. If you fall into this category – listen up. If you have to use a standard provided by others that falls into this category – listen up.

We have all seen bad standards. Here are a few things that I have seen that I think make for a Bad Standard.

1. The Simple Things

Bad Layer List – Basic items that are not even covered. This might include a layer list that does not tell you color or line weight or they may have left off linetypes.

Outdated guidelines – stated needs for delivering in AutoCAD 14 format. If I see this in a standard, I start questioning when the last time it was updated.

2. The Hidden Things

Defining your terms – often they have left out the definitions for the terms they are using throughout the standard.

3. The Major Misses

Project Folder Structure – many times this is left out. Define what goes where and how the folders interrelate.

MS and PS – what goes where. Tell me where you want me to draw things. Don’t leave it up to me to think it through.

4. The Little things

LTSCALE – uses and abuses of this setting have plagued users for many years. Tell me exactly what you want done.

Saved View Names – do you want them used? – tell me how to name them.

5. The Critical Things

Title Block Data – if you are really serious about getting the title blocks to look the same. Define this completely.

I say that Bad Standards are not worth having. I would rather be given the right to use my own standard than to be handcuffed into using a Bad One.

Now – what are the problems that may arise from using a Bad Standard? Let’s take a look…

1. A Bad Standard creates a false sense of security. Project Managers, Upper Management, Job Leads, all expect that the standard is being followed and that it is sufficient to make their CAD files usable and efficient. If your standard does not do this, you will be falling short.

2. A Bad Standard makes you hard to work with. Others are trying to comply with your standard. Your subs are straining to provide you with compliant files. If your standard does not define what they must do, then they will be frustrated and take more time (equals – more dollars)

3. A Bad Standard give you junk files. Take a look at your internal problems with CAD. Are they there because your folks are not able to understand your standard? Does it fail to define some needed areas? Are those areas open for interpretation by the users so that you end up with scattered layer names, or block names, or design methods?

4. A Bad Standard costs you money and time. It slows people down. If it is too complex, people won’t understand it. If it is too simple, it won’t cover enough to keep things humming.

Having a Good Standard is critical. It is not easy to do. It takes time and thought, but it is achievable.

What would a CAD production environment look like if it did not have a CAD Standard?

Every User for Themselves – Every person will tend to focus on what works for them. They each tend to do what is best for them to get their job out the door without worrying about the needs of others or the impact of their choices on other users.

No communication – sending files to others will be more difficult since the recipient will not know what they are receiving, nor will each file be similar to another.

Every Project is different – not only will files differ, projects will also. They will be differences that impact plotting and output and even opening files.

Every User is unique – This is not bad in and of itself, but when a user needs assistance or needs to have others work on their files, there is a difficulty in not understanding what has been done with a file. How was it put together? What support files are needed? What layer is correct?

No automation – You will be unable to automate much since data may be scattered and disjointed on every file. One file may have a block named one way and another file may use a different name. Or maybe it is a layer name? Whatever it is, automation can only come from unified standards and procedures.

No ease of use – Getting into another person’s file means that you will have to figure out how it was created, where things go and what is needed to get the job done.

Clients not satisfied – when they get chaotic files, they start getting concerned about chaotic designs. If they find problems in the CAD product, they start wondering what other items may be overlooked in the design process.

Consultants confused – They receive files that have data in differing locations from one file to another or from one version of a file to the next.

Users frustrated – Trying to figure out what the last person has done starts to grind on a users ability to even want to find out. They tend to give up and just match what was there before, thereby continuing the disconnected data and graphics.

No way to know if something is wrong – without a standard, who’s to say who is right and who is wrong.  If you have not defined what “right” is, then nothing is “wrong”.  Anything that gets the file plotted correctly will be allowed.

Having no standards only causes the process and production side of things to slow down.

What should a CAD Standard cover?

Here is a brief list of the major topics that should be covered by every CAD Standard.

10 Essentials

The list below is what I consider the bottom line. These issues need to be fully defined and articulated. Go to whatever lengths to get these outlined completely to provide efficiency for your firm.

1. Standard Folders – names, locations, relationships, contents
2. Project Names – numbering, names
3. File Names – complete definition, how they are created, what folder they go in
4. Layer Names, Line styles, Pen Weights
5. Pen Tables – CTB, STB
6. Lettering Fonts and Sizes – when used, fonts, style names
7. Dimension Styles – exact names, all terms defined
8. Drafting Symbols – your basic symbology
9. Xref Usage – naming, content, attachment method
10. Layout tabs – names, format, page setup

A Fuller List

This list is a fuller definition of what may be included in your Standard. This reflects what may be found in a Standard for plain AutoCAD. If you have LDT, Civil 3D or Revit then a even larger list may be needed.

1. Standard Folders
2. Project Names
3. File Names
4. Standard Units
5. LTSCALE
6. Paper Space and Model Space
7. Viewports
8. Date stamping of plots
9. Revision tracking of files
10. Layer Names, Linestyles, Pen Weights
11. Pen Tables
12. Lettering Fonts and Sizes
13. Annotative Text guidelines
14. Dynamic Blocks
15. Dimension Styles
16. Drafting Symbols
17. Graphic Symbols
18. Xref Usage
19. PDF Underlay Use
20. Saved Views
21. Title Blocks
22. Layout tabs
23. Detail Creation and use
24. Menus
25. Support Files
26. Plotting
27. Hardware Requirements
28. Software Requirements
29. Deliverables

For ADT/ACA

1. Standard Directory Structure (for Project Navigator)
2. Project Names
3. File Names
4. Project Setup
5. Standard Units
6. LTSCALE
7. Paper Space and Model Space Use
8. Datestamp Drawing files
9. Revision tracking of files
10. Layer Names
11. Pen Tables, Pen Weights (CTB, STB)
12. Lettering, Fonts and Sizes
13. Dimensioning
14. Drafting Symbols – defined as common symbols used by all disciplines
15. Graphic Symbols – defined as discipline specific symbols
16. AEC Content
17. Xref Usage
18. Viewports
19. Saved Views
20. Spaces
21. Tags and Schedules
22. Sections
23. Elevations
24. Keynoting
25. Title Blocks
26. Layout tabs
27. Detail Creation and use
28. Custom Menus
29. Support Files
30. Plotting
31. Hardware Requirements
32. Software Requirements
33. File Exchange
34. Deliverables
35. Project Closeout
36. Archiving

I have written quite a bit on developing CAD Standards over the years, but I want to revisit the entire process.  As I get ready to do this you may want to review what I have already written.

Here are some of the things I have written in the past.

Who Needs CAD Standards?

CAD Standards – Not Set in Stone
CAD Standards – An Ideal

CAD Standards – A Target to Hit
CAD Standards – Silence equals permission

Written CAD Standards – making progress
Written CAD Standards – Keeping Them Up to Date
Written CAD Standards – Print It

CAD Standards based on Principles

Developing Standards – From Principle to Action
Chaotic CAD – No Principles and no Standards
Ethereal CAD – All Principle and no practical
Despot CAD – Oppresive Standards
Ethereal CAD vs Chaotic CAD vs Despot CAD

CAD Standards and CAD Users – a partnership
CAD Standards – Almost Perfect

Which Autodesk products do you have?

I am re-running a poll from this time last year so that we can compare the results.  Have things changed in a year?  Are you using different software now than at this time last year?  Have you moved from one software title to another one.

This poll just focuses on Autodesk products, but you may use others.  Please jsut let us know what Autodesk tools you are using.

Take the poll on the main page of the blog site.

No – I am not calling you a dummy, but sometimes even the best need some help. I have bought and read some of the “Dummies” books over the years and they are quite good.

Here are a few that are CAD related…

Google SketchUp For Dummies – By Aidan Chopra

AutoCAD 2009 For Dummies – By David Byrnes

SolidWorks For Dummies, 2nd Edition – by Greg Jankowski, Richard Doyle

AutoCAD 2008 3D Modeling Workbook For Dummies – by Lee Ambrosius

AutoCAD 2009 & AutoCAD LT 2009 All-in-One Desk Reference For Dummies – by Lee Ambrosius

You can buy them or just browse them on page 2 of my bookstore.

I sent out the February CADD Manager Journal… Here are the topics discussed

Top  Ten CAD Manager Failures – the Second Five

AutoCAD 2010 – Sneak Peek

AutoCAD 2010 – Bloggers Speak Out

A Tour of the Autodesk Gallery

January Survey results

Are you a subscriber?     Subscribe here

Here is a quick outline of what I think my be significant items that will be part of AutoCAD 2010 for the CAD Manager to consider.

Online License Transfer: This replaces the portable license utility.  You can export a license or import one from a standalone copy of AutoCAD.  You have two choices: Public and Private.  Private can be used only by the person who exported it.  The Public license can shared between users as long as they have the same version installed and the smae serial number.  It appears that this is a mechanism for moving standalone install licenses around without having to uninstall and reinstall.

Action Macro Manager: A new Action Macro Manager allows you to copy, rename, modify, and delete action macro files from a centralized location. You can get to it from the Options dialog box.

CUI Changes: In AutoCAD 2010, the CUI file is replaced with the new CUIx format. A CUIx file is a package file format that helps to improve performance when working with the CUI Editor. The CUIx can contain images used in commands.  It is an expanded format.

Drawing File Format: AutoCAD 2010 introduces a new file format that offers improved save times, especially when saving files with lots of annotative objects, along with several new features.

The Ribbon: The ribbon has been updated to provide greater flexibility, easier access to tools, and consistency across Autodesk applications. You can drag a ribbon panel off the ribbon to display it as a sticky panel. Sticky panels remain displayed, even when selecting a different tab, until you select the option to Return Panels to Ribbon. If you are new to the ribbon, this may be a major change for your users.

Here are some recent links to blogs that have posted on AutoCAD 2010. There was an unveiling event held in San Francisco, but I was unable to attend. So I figured I would provide you with a brief list from some that did attend and some who did not and from Autodeskers.

Let the AutoCAD 2010 Blogging Begin!
Lynn Allen starts it off…

Heidi Hewett’s Blog: AutoCAD 2010… a closer look at the
AutoCAD 2010 includes a new Application Menu, which is accessible from the big “A” in the upper left corner of the AutoCAD display. At first glance, you might think the Application Menu is just a minor variation of the Menu Browser

Between the Lines: AutoCAD 2010 – 2D Geometric Contraints and …
I posted a short video on YouTube showing some of the experimentation with the new AutoCAD 2010 feature 2D geometric constraints and parametrics.

Through the Interface: The new APIs in AutoCAD 2010 – Part 1
This is the second post in the series looking at the new APIs in AutoCAD 2010, and following on from this post. I’ve copied the information in this post from the recently-published Platform Technologies Customization Newsletter

Lynn Allen’s Blog: My First AutoCAD 2010 Presentation!
This week I had the opportunity to do my first AutoCAD 2010 demo while in Miami for Digital Drafting Systems. Woo-Hoo! I’ll be the first to admit I wasn’t quite polished yet in my performance

JTB World Blog: AutoCAD 2010 for Revit users
This is a great example on how AutoCAD 2010 can be useful as a 3D application even for Revit users. Normally AutoCAD is used by Revit users for plain 2D work like details. Read about it on David Light’s Revit blog.

CAD-a-Blog: AutoCAD 2010 Revealed
I went to the Autodesk office in San Francisco on February 5th to take part in an even that revolved around the live web cast of Autodesk’s announcement of the release of the latest version of AutoCAD, AutoCAD 2010