Reuse of any or all material contained within this document for commercial purposes,without the express written consent of AUGI, Inc. or its authorized agents is expresslyprohibited.
© Copyright 2004 Autodesk User Group International, Inc. All rights reserved.
. This is the topic I choose to tackle. Just when I found my little niche in the world withAutoCAD, along comes a new love. Ahhh! The fond memories of spending days on end…which turn into weekson end just figuring out how to program my favorite drafting program to do what I needed it to. And it was likeChristmas every year when Autodesk invented a new way to insert a block!Blocks. They were so cute and simple. It was so fun when they were hiding! All those convoluted file structuresthat nobody in the office followed. HA! Dragging in all of the old layers you don’t use anymore.Layers! I remember those. Do you use a CTB or an STB? Is Cyan used for text or thick lines? Thick lines? Howthick, and specifically which lines are you using it for?Raise your hand if you are scared to death of messing up the CUI!Ok, I could go on all day. The point here is this: Bosses, senior architects and senior engineers are finally startingto notice something. It’s the incredible waste of time and money it takes to have an architect or an engineeractually mark up a sketch and hand it to a production drafter using…a production drafting program. They are alsonoticing the errors and misinterpretations inherited by this antiquated method. Now, don’t show up in my frontyard with pitchforks and torches just yet, or burn me at the stake as a heretic. I have been on both sides of thedesign / drafting fence. Mistakes come from both angles. It’s not the fault of either party. It’s the void createdwhen your design physically leaps out of the software, onto a piece of paper, into the brain of a drafter, and backinto the computer.Let’s summarize the things that can go wrong with this “application to finger to brain to application” method. Acondition commonly known as
.So the designer sketches a crude (or sometimes quite painstakingly meticulous) design on a piece of paper. Shehands it to the drafter. The drafter interprets it with his best ability, and a project is born. He prints it. She marks itup and sends it back. All the while another designer in another firm is changing it. He finishes the mark up, andshe shows up with a new background that needs to be cleaned up and referenced into the CAD drawing.This happens 45 times in the life of a project.PLUS! CAD standards need to be maintained. File structures need to be maintained. Schedules need to beproduced, estimates need to be…estimated. The project manager is going back and forth between this and that.The phone is ringing AHHHHHH!!If you are thinking Architectural desktop, you are getting close. Unfortunately, Arch. Desktop produces about onein every one hundred true, 3D drawings capable of rendering, scheduling and efficiently maintaining.Think again. Think about placing a wall instead of drawing a meaningless line. Think about placing an actual floorinstead of a note that just says…Floor.In Revit, this is what you do. And you pretty much do it in 2D plan. But, once the plan is done so are theelevations and sections. Schedules and estimates are just a few clicks away as well.Let’s see how this all works shall we?