Using Project Navigator vs Not Using Project Navigator

[DrakeCanyonArchitecture]

The biggest hurdle that I have faced so far using AutoCAD has been workflow. I have been stuck for an embarrassingly long time on this subject. The biggest problem is that the tutorials that I have watched on the subject don't even touch on how we would use AutoCAD in the real world. Meaning that the guys creating these tutorials are creating just 3d models and not really explaining how you would draw an actual set of working drawings complete with truss layouts, footings, electrical plans, plumbing plans, etc. 

That moves me to the subject of Project Navigator. I thought I was getting things set up properly by getting my sheet sets and layers set up. Then I hear about PN and it totally threw me a curve ball. In the software that I was using, the entire drawing was in one file with several layout tabs. As far as I can tell, you guys are using (correct me if I'm wrong) a floor plan as an xref then creating several other drawings. So the roof plan would be it's own drawing, foundation, etc. One of the things that just makes my head hurt is how would you see where your loads are coming from and going to with everything being separate drawings? In the other software that I use, I toggle my layers so that I can place an expanded footer under a girder truss. That footer then automatically shows up in the viewport. 

So my big question is, what is the best and most logical way to deal with these issues? I know there has to be a simple answer. AutoCAD is pretty much the king in the CAD world, so how do you guys who are using the software for creating actual working drawings deal with this? This is the only thing keeping me from moving forward in learning the software at this point. I made this switch in an effort to make myself a more valuable draftsman since this is the program that most Architects and Engineers use.

One last note. The other thing that confuses me is that the way I would develop my own template is to draw an entire set of house plans. I would set up all the settings, styles, symbols, blocks, etc then save that template and all of those things would then be available from that point forward. How do you handle something like this if you have multiple drawings for each project? I appreciate any help. If I can just get over this hump, I think I can move forward pretty well. 

[Richard.Vivanco]

Hi... about your last comment, you could configure your project to use your own dwt when create new construct, levels, models or sections.  See the attach

PN is useful specially for big projects or when you work in team.  You can divide the task in specialties ( architects, engineers) or you can divide it by zones or levels.    In my case for a small project that im working, i separete it by levels, its more easy to control or see the differentes elements (walls, windows, furniture etc) level  by level.

Then in a 3D view you can attach all the levels and assemble the entire project, the same for create sections or elevations.

I hope I have helped a little 

[dbroad]

The project navigator only works in AutoCAD Architecture so, while the workflow is flexible in AutoCAD, all coordination must be done by the user.  The PN in ACA sets up a paradigm for working with AEC objects. Modeling is done in constructs. Views are created produce 2d documents and to annotate and dimension. The PN sheet set manager facilitates placing views on sheets, titling, and cross-referencing.  When using ACA, I always use PN.  Others prefer using ACA as if they were using AutoCAD, forgoing the PN.

You should use the sample project to learn about PN features.  Once you complete a project once using PN, you could either create a copy of that project, deleting all the geometry, dimensions, and annotation to use on similar future projects or use the copy project structure option in the project browser.

[DrakeCanyonArchitecture]

---

@Richard.Vivanco wrote:

Hi... about your last comment, you could configure your project to use your own dwt when create new construct, levels, models or sections. 

I have actually set up a template, or have started to I should say. And I have set it to be the template for new projects. The thing that confuses me is that, say I start a new drawing for the roof plan and my template is the basis for that. I go through the process of creating layers, beam schedule styles, tag tools, etc. (as I just did with the help of David Koch). I then do the same for the foundation plan, creating layers, schedule styles, etc. Now I have two additional drawings with all this information in them that I want in my template so that it is available for the next project that I draw. What is the most logical way to consolidate all this information? Do you copy all the styles and paste them in the drawing template file via the style manager? And then what about the newly created layers? This is where the idea of multiple drawings kinda tweaks my brain a bit. It seems like a lot of work to get the base template set up. I'm sure there is a logical way to handle all of this and I'm just not getting it yet. This is all assuming that there are individual drawings for each view, from what I gather that's how most of you guys work. Is that correct?

[DrakeCanyonArchitecture]

---

@dbroad wrote:

The project navigator only works in AutoCAD Architecture so, while the workflow is flexible in AutoCAD, all coordination must be done by the user.  The PN in ACA sets up a paradigm for working with AEC objects. Modeling is done in constructs.

Are you drawing your model and then disassembling it into the various constructs? Or are you creating the constructs then creating the drawing/model within it? Also, what is the most logical way to break down a plan?

For my first attempt, I had created my model, then my levels in PN, then split the model between those levels/constructs. Each construct that I created was the entire floor plan, roof plan, foundation plan. So walls, windows, doors, appliances, etc were all one construct. Then the roof plan construct included the floor plan construct and the roof slabs. But this has to be terribly wrong, lol. It just doesn't feel like this is how things are supposed to work. The other thing about this is, in order for me to tag the beams and headers that reside in my floor plan, I have to do that on the actual floor plan itself rather than the roof plan. This is going to reveal why I'm pulling my hair out. Lol. I have the utmost confidence that everything makes complete sense. I just haven't found the right answers yet. I do appreciate the time you guys have taken out of your day to help me out.

[Richard.Vivanco · Accepted solution]

What i do is open the base files that appears in C:\ProgramData\Autodesk\ACA 2020\enu\Styles\Metric and copy the walls, windows and doors that i want to be include in my template.  You can do this with the style manager too.

To complement, i create one or two wall styles, my own tags for windows, doors, my own shedules with the information that i need, my layouts, configuration of layers etc..

Template creation takes a lot of time, the same is in revit or autocad.  

You need to configure or customize all,  taking in count your workflow or standards.

[DrakeCanyonArchitecture]

That is a GREAT bit of information about copying the styles from the syles file and pasting into the template! As far as the rest of the template, as you said, I guess it will just take a bit of time. I guess what I could do is once I have an entire set of plans done, copy everything from the individual drawings into the template to bring all the layers in.

[dbroad · Accepted solution]

Are you drawing your model and then disassembling it into the various constructs? Or are you creating the constructs then creating the drawing/model within it? Also, what is the most logical way to break down a plan?

You create at least one construct for each level. You use the views to assemble the overall model. If you need to break down the plan by discipline or function you create a construct for each discipline and drag-n-drop the other constructs into the active construct as backgrounds. PN automatically knows where to place each construct and whether it should be attached as an overlay or attach.

Elevation, section, and detail views can be generated either in the same file or in another file. These views should always be generated from a view type file rather than a construct type file. A floor plan, for example, is a view file that references one or more constructs. Interior elevations should be done in the floor plan view files. The elevation results could be in the same floor plan file but probably should be in elevation view files.

[DrakeCanyonArchitecture]

I think I finally got it. My biggest issue (and dumb mistake) was selecting more than one level when creating constructs. A misunderstanding of how they, and views work. It makes absolute sense now. I was getting multiple instances of the constructs. The other thing that helped me to understand was that I read a few times that if it is an actual object that you would be able to touch when the building is constructed, it will be included in a construct. Notes schedules, annotation, etc in views. I appreciate your guys' help. You both helped a ton, thank you!

[dbroad]

It's not necessarily a mistake to select more than one level for a construct.  It will, however, be inserted at the lowest level though when combined with others.  Applications for a multi-level construct include grids, multi-story curtainwalls, stair towers, and exteriors that span multiple stories.

[DrakeCanyonArchitecture]

I see what your saying. I guess what my issue was that I had several instances of the floor plan overlapping. The other day I did something (I can't remember what exactly) but there were suddenly tons of yellow triangles everywhere. Some how I had two instances of the floor plan together in the same drawing. At any rate, I'm feeling much more comfortable with the way PN works now. Not to mention, and I think this was my biggest problem... When I created my constructs, even though some of the layers were turned off, each construct had all the layers. So each drawing was essentially the same, with different layers on/off. A bit of a mess, but once I discovered that and cleaned it up, things started to make more sense.

[dbroad]

Warnings generally occur if you try to override the insertion Z-coordinate to make it 0,0 for non-first-level contstructs. When walls physically overlap in view drawings or constructs, that causes issues.  Sheet files for plan views should always only have a single layout and generally should only have a single level.

Layers are fine to be duplicated as each construct should have virtually the same layer names.  Always edit the model in constructs.  Add annotation and dimensions in view files.

Dragging a PN model space view to a sheet will preset the scale, and layer overrides for the viewport to match the view file. Since each xref's layers are unique, other than defpoints and layer 0, there shouldn't be any layer conflicts.