Naming Conventions

I originally posted this on linkedin, but thought it would be a good add for the Blog Site as well.

Good morning everyone. I wanted to touch base on Naming conventions. We use Names in everything we do to uniquely identify or categorize the things we work with. In CAD We have a number of areas that we can do better in our naming efforts. This is not a rule or standard, but more of a practice that I suggest you adopt when naming things.
What kind of things?
Layers Blocks Folders Filenames (Drawings, Models, Excel Files, Word Documents…) Tabs (Inside Excel and other documents like Layouts in AutoCAD)
And just about anything else.
Back in the days of DOS (Disk Operating System) we were restricted to filenames of 8 characters and a 3 character extension separated by a period. Something like thisfile.ext. Now imagine today’s content being limited to that structure.

Todays operating systems (discussing Windows Systems) allows us to use a large number of characters (255 of them) for our filenames. This does not include the folder structure path, but it can impact limits in other ways for the folder and begin to limit the actual filename length below 255 chars. Add in sharing files across the cloud or on different Operating systems, and it can become a challenge. This gives us an array of options when naming our files. Often times we just throw something out and hope it is unique enough and easy enough to relate to the subject matter. Problem is haphazard naming will often lead to issues later in some form or fashion. You might not see them, you might not know they are causing problems for you or someone else, but they eventually do.

Have you ever tried copying a bunch of files to another location and had the computer prompt you with a message filename invalid or truncated? Something like this..
No alt text provided for this image
Imagine if you will, that you are archiving a project and this pops up. How many files are in that project that this affects. How about if the project has 12000+ files. Imagine if it was just 5% (That is over 600+) of the files that you had to go back and “shorten” the file names before you could archive the project? How would you make the decision to rename files or even folders. What files have data links, or dependencies on those filenames and locations. In other words, what is going to break when you rename files or folders? What good is the archive at that point?

Hopefully that at least presented one good reason to develop some habits in your naming conventions.

Some other things to consider
a. Programming and automations systems – Often times special chars or naming limits become an issue
b. Databases – Special Chars and char lengths are important for these systems
c. Wild Card characters – Databases, search engines, operating systems use special chars as wild cards for searches
d. Search abilities – You want to be able to find things, not just you, but other people as well.
e. Memory limits for applications – Long Layer names and an abundance of them can cause AutoCAD to slow down, especially if you leave the layer Dialog box up.
Use names that make sense and work for the content
The following applies to more than just filenames.
Now for the part on suggestions for you to consider.
1. No special characters. Do not use things like a comma or period in the name unless it is for a good purpose
  a. Chars to avoid
    i. Parenthesis ()
 ii. Commas, single or double quotes and apostrophes ‘ , `“
  iii.Chars above numbers !@#$%^&*
  iv. Tilde and accents ~ `
  v. Greater than or Less Than < >
  vi. Question Mark ?
  vii. Vertical bar and Forward or Back Slash | / \
  viii. Curly or square brackets {} []
2. Avoid Spaces (Try using something like or similar to Camel Case, Capitalize first letter of each word and use no spaces)
  a. Samples of Camel Case (not getting into all the specifics)
   i. ThisIsCamelCase
  ii. DrawingForPiping
  iii.MyFile
  iv. MySpecialTab
3. Dashes and Underscores are ok, but can be distracting if over used.
4. Avoid adding redundant data if the file is a dwg file and you add Drawing to the file name it is redundant and not needed.
5. Consider Sorting
  a. If you want to sort by year for data put the year first 20190220(This sorts by Year Month day) instead of 02202019 (This sorts by Month day year)
 b. Sequential numbering. If you have 9 files 1 – 9 they will sort clean but as soon as you add 10 to the files it will sort with 1 then 10. Prefixing the sequence with 0’s will help the sorting process. If you know your max files will be less than 1000 then make sure you prefix with 0’s as needed to have a total of 3 chars in the sequence.
6. Avoid getting too long with your names.

Something else to consider is being consistent in your naming systems. It will help you find, sort and share your files much more efficiently

Quality and Loyalty go hand in hand.

DILBERT © 2008 Scott Adams. Used By permission of ANDREWS MCMEEL
SYNDICATION. All rights reserved.

I’m sure many of you have felt it. I’m sure most of you have seen it. I’m sure a lot of you have experienced it. What you ask? The decline in loyalty, to and from an employer, and the quality of deliverables from employees and employers. Unless you are a one man shop, you are part of a team. A good team is made up of dedicated, loyal, quality driven people focused on the same goal. Great things can be accomplished with a good team. Companies use to promote the development of such teams.

The St. Louis Arch brought two towering structures of a calculus derived shape together within 1/64th of an inch accuracy at the top. Think about that for a moment. 1/64th of an inch margin of error for two massive structures to meet in the middle 600’+ in the air and almost the same distance apart at the ground. Today, though, we seem to have trouble getting a piece of pipe to set on top of a piece of steel in a computer CAD model. Why is that? Yes we can go round and round about “Whose fault it is” but why is it only ONE at fault? It truthfully is a team’s failure to come together, communicate, and resolve the issue, or better yet work pro-actively to make sure it is NOT an issue. As a company we are part of a team, we strive from good leadership. Good leadership promotes dedication and inspires greatness, from that greatness comes great things. That’s pretty close to the SpiderMan quote of “With Great Power, comes Great Responsibility” – Ben Parker (Peter Parker’s Uncle.) We seemed to have cast aside both power and responsibility. I believe that by accepting responsibility you gain power of self-control aka Internal Locus of Control.

Corporate Leadership has become divided into a non-balanced effort to promote better profits, efficiency and return. The corporate goal is, or should be, a well-oiled machine that churns out profits, produces results and builds on the company name and image (in a positive way that is.) Now, imagine the quality of the components of the machine and how well those components are loyally lubricated with the oil. The Machine will run great, right? Stephen Covey talked about the P/PC (Production and Production Capability) in his 7 habits of Highly Effective people. Paraphrasing here, about the “new manager that strolled in and took productivity through the roof, by running the machine at peak capacity, ignoring maintenance and care. Profits were through the roof, they promoted him, the next guy came in to take over and guess what? The machine was at the verge of break down and needed to be shut down for maintenance and repairs, guess what profits went down, and costs skyrocketed. The other guy still looked great and the new guy, not looking good at all.” This has happened to us in our industry.  Loyalty has not been maintained as a result quality is down and cost is up. Our industry has been consistently chipping away loyalty and degrading the quality of the people for years now. Quality, as a result, is all but gone; replaced by quantification of bulk efforts of cheap labor in other countries. Costs of Engineering, Construction and Procurement have sky-rocketed as a result. Are we really getting more for less? No we are not. We are getting far less for far more.

We can improve our situation through never ending dedication to improvement of our selves, pride in our work and commitment to our industries excellence. Yes, it would appear, I’m saying that we make the first move to take back our industry from those that cheapen it with minimal effort, inefficient design, principles that cost construction costs to sky rocket, poor quality drafting, lackluster software systems that promise the world and fail to deliver. I’m sure some of you can identify a software system in particular. I’m not going to rant on that as many of you know I could, grin.

Moving on… In the days of past you could distinguish a company employee from a contractor. The understanding was that a company employee was part of the company, and proud to be part of it. A Contractor was someone that would come in under ramped up project demands. They were typically paid more money, but lacked the benefits of job security, and actual employer provided benefits. There used to be a real difference. The Employee was dedicated to the company and the face of that company, the contractor was dedicated to the paycheck and most of the time the project at hand. There isn’t really much of a distinction any more, with the exception that most don’t seem to care about the company or the project. Projects have gotten so screwed up, people just hope they aren’t the primary scape goat. Corporations will quickly discard you once the project is up. Your contributions good or bad are irrelevant as the cold sled comes to your cubicle as you are called into HR. Lucky for you HR will escort you out of the building after providing you with a few minutes to gather your things. Not much loyalty in that picture is there? Hurry up finish this project so we can get you off the books. That’s not said, but it is the point. I’ve heard so many company campaigns or slogans that do their best to convince you otherwise, but in the end, it is the same result.

Cutting costs is what promotes this short sighted thought process, especially since we get our stock stats right on our phones in an instant. We want instant results, we expect them. Who drives that? We do. You want instant results, so do corporations. If they cut 10 professionals from the payroll, that’s pretty much a million dollars a year savings. Tell me that doesn’t look good on the books. It looks great on the books. Never mind the reality of the people you laid off were valued team members, and replacing them is not just as easy as hiring someone with similar qualifications. How much does it cost to hire a new employee? How long does it take to get them up to speed on your systems? How much time is vested in that new employee to discover they don’t have the abilities you hired them for, and you are forced to go back to the pool of candidates. How much does that cost on the front end of the project. How much time is vested getting a new project team to come together? Wouldn’t it be great to have a team already in place? Of course it would, perhaps we should consider that when building our teams, and maintaining them. A team works together well when they are loyal to the team and the goal of the team. Take the team out of it and just utilize a pool of “assets” and you have done nothing more than throw your toolbox full of tools at the task you hope to work on.

How do we get the corporations to be more loyal to the employees? Step one, make sure you are not only valuable, but extremely valuable. Step up your game, not only do you do good work, you help others strive for the same. Spread the knowledge, skills, tips, and tricks you have learned, pass on that knowledge through mentoring new recruits in the industry. Hold them accountable as well. There are a large number of “senior” designers out there in their 20’s that, are not Senior designers. They may have scored a position, during a high demand time, as a senior designer, but that only caused them a disservice. We need to fix that, help them learn. Those of you that find yourself offended to that, need to open your mind and learn from actual senior level designers. Your lack of knowledge and experience in proper design for your discipline impacts the quality we as a whole provide. We as a group need to become cohesive. Don’t be afraid to ask for education, and don’t get offended when someone offers you an education. Don’t get your feelings hurt when someone points out something you screwed up. Learn from it. It’s called an opportunity to improve. The more you learn the better you are, the better our industry gets. The better our effort becomes, the faster we can execute projects and the cheaper it costs to do work properly. Back to one of my favorites “Do it Right the First Time!” The more money left in our pockets, the more security we have. Companies typically want to repeat what makes money for them. If a company operates smoothly and actively gains market share through real results, executives will tend to stay at that company, rather than jumping ship. At that point hiring 10 people means making over a million dollars more in returns. That’s loyalty on both sides. That’s Quality at its best.

If you are a corporate executive, a project manager, a designer, a drafter, an admin, a student, or … reading this, ask yourself; “What can I do better to improve the quality in myself and those around me?” Raise the bar, raise your expectations.

 

Hello Everyone!

Welcome to SeeMSixty7, a place to discuss AutoCAD, Databases, Development and More. We don’t have to limit ourselves to just AutoCAD, though CAD in General.

Where to Start…. Why Start this Blog? Well I’m frustrated and disappointed in the direction of Drafting/Design. Over the years it seems quality has gone down, in my opinion. So let’s open that up for discussion. Keep in mind this is not a debate, just a place to talk about how to improve our industry.

AutoCAD has grown into a powerful CAD system that offers tons of features and abilities. Drafting in the last 10 years though has not improved as a result, from what I have seen. I believe there are a number of factors that are influencing this trend; younger drafters that have not been properly mentored or trained; offshoring to places like India; data driven systems that produce drawings; older designers that never really learned CAD efficiently. There are more, but I think those are the big ones.

Younger Drafters typically learn AutoCAD and have the belief this now makes them a drafter. Not quite. Drafting has evolved over the years in so many ways and has so many guidelines and semi-standards that should be followed. Keep in mind drafting in one industry compared to another may in fact contradict each other’s standards. The problem is made worse when a young drafter holds a position as a drafter for a year, and suddenly believes they are now a designer or worse senior designer. Reality is you are setting yourself up to fail if that is the case. Do your time and become a good drafter, before taking on being a designer. Your time drafting and better understanding of what you are presenting will help you be better at both. Learn from the older guys. they might not be the best at CAD, but they should be better at the design and the drafting. Something else to keep in mind, Engineers are not drafters, and unless they started as a drafter, they probably are not the best at instructing you on how you should draft or present your content on the drawing. That is not a knock against Engineers, but they are typically engineers because they are good at engineering, not drafting!

Offshoring to India is  sore subject when we see jobs leaving our cities to go to another country. Typically the people that trained many of those in India were designers/drafters who were reluctant to teach them how to draft, and frankly probably wanted them to fail. This is not a knock against the drafters in India or the people of India in any way. It is just a fact that people don’t like to train their replacement and then get laid off. I’m going to avoid the political points on all of this, but from what I have seen, the results coming out of India are the same as the previous paragraph, lack of experience in drafting and design. Quality is still not where it needs to be.

Data Driven systems that produce ISO’s, Loops, P&ID’s, One-Lines, Wiring Diagrams… I have been automating drawing processes for nearly 30 years. I created Loop generators from lotus 123/excel data back in 89. I Managed to generate over a thousand loops in a few hours. Keep in mind 286 processor with 2 MB of RAM back then. It wasn’t exactly fast. They were good looking Loops too, because I worked the templates to be clean, I knew the format of the data, I knew all the nuisances that would come up and wrote my code to compensate. Data Systems are typically taken out of the box, and data thrown into them and drawings start spitting out. These systems are written to fit a generic template or layout with a particular data format that works with the generic. When you tweak the data formats, the data model input into the system you tend to blow that consistency up, resulting in poor quality drawings. Automated systems are great. I love them, but they need so be flexible enough and the time needs to be taken to properly implement them.

Old Guys, of which now I’m either in that group or pretty close to it. LOL. I’m still in denial on that. Some of the “more experienced” designers started on the board, and begrudgingly moved into CAD in the late 80’s and early 90’s. I personally started on CAD and did some board drafting. I have a lot of respect for the board drafters, some serious skill and tedious efforts in that. Some took to CAD like a fish to water, others adapted as best they could. Keep in mind they didn’t grow up with  computer in the house. Technology was added much later in their years. Some it is natural, and some it isn’t. These are the people you can learn from. Appreciate their opinions, just because you know more about CAD than they do, does not mean you know more about drafting/design than they do. My father once told me. “You can always learn something from someone, and there is always someone that knows more than you do.” The “more experienced” can also learn some CAD from the “less experienced.”

This has been a lengthy intro, but hopefully we can start some good dialog and start sharing knowledge to make us all better. Thank you for participating. Create a login and start contributing. I will be sharing a wealth of information, tools and best practices with blog members.