location menu los angeles location costa mesa location san diego location
tabbed nav training page software page events page services page support resources page
content cap
left_col_top_cap

About the Author

blogger photo

DannyCounts
I was recently certified by Autodesk as a Civil 3D Implementation Certified Expert or ICE. I have worked in the Civil Engineering industry since 1987. In 1994 I started my consulting business doing training and consulting for Civil Engineering customers utilizing Autodesk civil engineering technology. I started L.A. CAD in 1999 and we are currently the 3rd largest Autodesk partner in the U.S. Studied Civil Engineering at Long Beach State, graduated in 1996.

left_col_top_cap
Civil 3D 2007 Implementation Certified Expert Logo
K-Tek, Where knowledge meets technology

Digging In...

Thursday, May 18, 2006

 

Vault Workflow in Civil 3D 2007 (Part 2)

PART 2
(see May 16th Part 1 post)

We are positioning this post and the previous one as a "proposed" method or one possible method of workflow within Vault. Also understand, this is for a "typical" project and we understand it is not for all projects.

This portion was not included in the original post (Part 1) on a "proposed" Vault workflow, but certainly IS a part of the workflow.

Worth mentioning up front… Although this proposed workflow uses the principle of “One Object per drawing” (except with an alignment and its profile) we believe this workflow could represent the most efficient way to work because the drawing sizes would be much smaller. And as we suggested in Part 1, the fact that the objects exist in different drawings can really be transparent to the user.

Linework File
There would be a need for a "linework" file. The way this file would be setup is by creating references to all of your alignment drawings in the Linework.dwg file. Once the alignment references exist, we can use these to create offsets for other road features, and establishing curb return areas, etc. Essentially, we might include in this file everything that is not represented by a Civil 3D object. Once we have all of these primitive 2D graphics, we would recommend removing the alignment references. The reason to remove the alignment references is so we can create the references directly into the sheet files mentioned below.

Steps...
1. Start a new linework drawing, save it to a logical name and add it to the appropriate project in Vault.
2. Create references to all alignments in the project by going to the Projects area in your toolspace and creating the references in the linework file
3. Use these alignments to create offsets for roadway features, curb return and intersection areas, etc. (Again, anything that will not be represented by a Civil 3D object).
4. Remove the alignment references from the linework file.

Sheet Files
In your sheet files, you would XREF in the linework drawing that contains all of the primitive graphics not represented by Civil 3D Objects. In your Sheet Files, you would create data references to your alignments, surfaces and profiles. The advantage of these alignments and profiles not residing in an XREF is that you can stylize them in the sheet files. If you setup your default styles correctly in Civil 3D, the alignments and profiles will always come in looking the same and being labeled the same. The disadvantage to this method is if you wanted to change the style for the alignments in 100 drawings, this could be time consuming. For this purpose we mention a few alternatives... if it is that important to use this workflow described here, develop a routine that will automate the task of changing the style in 100 drawings. Alternatively, keep the alignments in the Linework file mentioned above and then XREF the linework file in containing the alignments. This way the alignments reside in a more centralized location.

Steps...
1. Start a new sheet file, save it to a logical name, and then attach to your project.
2. XREF your linework file(s) in
3. Create references from the Projects area of the toolspace to your alignments, surfaces and profiles.
4. You will need to provide some detailing on the alignments and profiles. Some sheets will need to pull in multiple alignments and in all sheets you will need to construct match lines on plan and profile. You should be able to accomplish this easy enough with a dynamic label. This is the part of Civil 3D I would insure our less experienced CAD Technicians learn so we can improve their skills.

I will say it again in conclusion… Although this proposed workflow uses the principle of “One Object per drawing” (except with an alignment and its profile) we believe this workflow could represent the most efficient way to work because the drawing sizes would be much smaller. And as we suggested in Part 1, the fact that the objects exist in different drawings can really be transparent to the user.

Posted by DannyCounts @ 9:12 PM
Permalink


Comments:

Posted by Anonymous Anonymous : 7:54 AM
Thanks very much Danny for taking the time to publish a workflow option. This is one of the things we are working on.

John Postlewait
IS Department
George Butler Associates, Inc.
 

Posted by Blogger DannyCounts : 7:58 AM
John,

I am also interested in what you have come up with. I believe there will be a few different workflow methods.

Danny
 

Posted by Blogger Jon Rizzo : 5:46 AM
Great article, Danny. We have been debating this internally as well. I personally favor the workflow you have detailed here, but the jury is definitely still out. Who knows, we may end up implementing different workflows for different types & sizes of projects, since each method seems to offer different advantages and disadvantages.

Jon
 

Posted by Blogger DannyCounts : 7:50 AM
Thanks Jon. I agree there may be a few to several different workflow possibilities.
 

Posted by Blogger Rebecca Ferguson : 7:04 PM
Thanks so much for the great info. We, like the previous posters, have been brainstorming on what our SOP will be for dwg setup. We had hoped to have the profiles seperate from alignments (wanted to have pipes together w/ alignments instead). I did not realize this could pose a problem until reading you posts. We are trying to determine our SOP before we switch over from 06 to 07. I would also be interested to hear what everyone else is implementing. Likewise, I will share ours (as soon as we figure out what that will be!). Thanks!
 

Posted by Blogger DannyCounts : 7:16 PM
Rebecca,

thanks for the note. I am still planning on posting something related to Vault and Sheet Set Manager too.

Most that we talk with will be implementing 2007 version, not 06. The new capabilities with piping and grading plus several other smaller items have our customers leaning this direction
 

Post a Comment



<< Home

This page is powered by Blogger. Isn't yours?



content cap