Detailing a family for Construction Doc's.

[patricks]

I have a family for a decorative wall/roof bracket, which I need to create several detail views to show its dimensions and how it is constructed. I'm curious as to how others do this?

On a project from a couple of years ago, I had a steel bracket that needed several detail views. For that I actually placed a bracket instance by itself way out in space in my project file, and created several views from that, including a 3D Axon view for clarity.

Is that the best method (or only method) for doing this or do others prefer doing it differently?

[sbrown]

I put it in place, then create a 3d view, turn on scope boxes and crop down around the bracket, then turn off everything but the bracket.

[patricks]

So you actually create a scope box for the bracket itself? And this is using one that's actually on the building and not out in space somewhere?

[greg.mcdowell]

I don't think I'd create a Scope Box so much as a Section Box for this... I think that's what he was referring to.

[sbrown]

I'm sorry, section box and yes it is on the building not off in space.

[archjake]

Yes, use the one in the model. If you started placing items in space you're using BIM incorrectly. What if this were to show up on a schedule. It may drive a contractor crazy trying to find the one that doesn't show up anywhere in the plans.




So you actually create a scope box for the bracket itself? And this is using one that's actually on the building and not out in space somewhere?

[Justin Marchiel]

i read a thread where someone created a managment phase that occured before anythings else, and put typical itmes like groups, etc.

This would avoid it being counted on a schedule, and only show up when you set the phase.

Justin

[patricks]

Okay now for a more difficult scenario.... On this decorative bracket I have in my project, I need to show the bracket in an exploded view to make it clear how several different pieces go together. What will be the best way to accomplish this? I could create the separate pieces in a family and have a 3D view of that, but there's really no way to get that view into my project. I think it would have to be in the project but off in space somewhere. Thoughts?

[noah]

We've had a lot of luck recently with using drafted views for ALL details.

What happens when you switch the bracket detail to something else? or it moves just a 1/4" in your model? Your detail gets all messed up.

I would suggest drafting anything at scales greater than 1/2"=1'-0" and just model your components so they look good at a 1/4" - it will save you a huge amount of stress worrying about things moving or changing. And most importantly it allows you to begin to develop a library of details that can be swapped in and out (and you can finally save details now in 9.0). Drawing the detail conventionally gives you much more control over how you want it (e.g. exploded as you suggest).

And as far as I'm concerned it's still consistent with the concept of BIM because you've modeled the item and it can therefore be tracked through schedules.

[dbaldacchino]

I tend to agree....it sounds like you'd be running the risk to overmodel if you get down to the "nuts and bolts".

Another way of isolating objects that I'm currently using is worksets. I put a window type or a door frame type on a workset bearing a descriptive name such as Window Type A, etc. (I make it visible in all views by default) and then I create a view and set only that workset to be visible. Obviously, nothing else shows up except what's on that workset. Since we have pretty much placed everything on a "Modelling Elements" workset (and "Shared levels and grids") in the project, the number of worksets are still reasonable. I tried using filters but they didn't work as nicely as worksets. You might just follow along this method and place your bracket to be detailed on a unique workset. Then you can create any number of elevations/sections/3D views without worrying about seeing other objects.

In our case, we're using the modeled elements form the modeled project itself for documentation, so any last minute changes by the designer will be reflected in the final document set. I don't like the idea of putting a duplicate somewhere out in space or in a different phase, although it could work. It's prone to mis-coordination and the issue is exacerbated in large projects or complex/highly detailed small projects.

[patricks]

well I am needing a 3D axonometric exploded view, and I was hoping to not have to draft that, but I may have to anyway. :(

[Elmo]

Patrick it sounds like the best way is to model it then make a legend of the family. You could create all the seperate components as families and then make 2 quick families one with the components exploded and the other where it is correctly put together.

[twiceroadsfool]

well I am needing a 3D axonometric exploded view, and I was hoping to not have to draft that, but I may have to anyway. :(

It sounds like a hassle, but why not load the fam. in to a blank project, hook up your 3d exploded axon, put the 3d view on a sheet, and export to DWG? Then you can put it back in your project as a Drafting View (linked, if you prefer?), so that if the detail changes, you just change the family, load it in again, and update link?

I would hate having to have a separate *blank* project file just to create a Drafting View in 3D, but it would still be faster than drafting an axon, imho...