detailing moves?

[doe]

i'm curious how detailing is done for others. We have a callout of a column, we then did all t he detailing in that callout, the element then moved in the model (meaning the callout moved too) when we go back to the callout alot of the detailing elements like detail lines and components were left behind. how do we make sure that all the elements move with it? is there something we're missing?

[brede.207016]

We too have had that problem... After talking with our local Revit technical guys, we settled on doing most of our detailing in Autocad and linking the drawings in. This has worked really well for us since we already have a detail library built in cad. We import the details onto individual drafting views and then you can still use callouts, just select the "reference other view" check box.

This method is probably considered a "work around" but the revit tech help we consult with explained that cad and revit will always go hand-in-hand and that there is no sense in re-doing all our details.

If this doesn't appeal to you, you might try locking the detail lines to actual parts of the model.

[cganiere]

I have worked in this method:
Start in a detail view
Create all the detailing components
Create a new drafting view
Cut/Paste all the 2D stuff to the new view
Use Callout/Section Reference Other View

[doe]

brede - that works idealy if it's standard details, which even those we are converting to Revit details. no point in having archaic DWGs if we can avoid it. Yes, they go hand in hand, but might as well have it converted to try and be 100% revit.

the problem with using drafting views is you don't have the ability to use elevation tags and proper section tags in it. so if you have an architectural column and you want to show sections and elevations of it, then you can't use the symbols in a drafting view.

the idea of having to lock all the detail lines seems overly cumbersome. i don't understand why detail lines and components don't move if the callout to that detail does. seems counter-intuitive that they aren't associated.

[twiceroadsfool]

I certainly wouldnt defeat the model by using drafting views or importing autocad details in to it... You can do one of a few things:

1. Constrain the objects to the modeled element

2. Model group the elements, and embed the detail items to the model group. Then move it as a group, and the details go with it. You can save that group out to a new file as well, so it starts off detailed in the next project. Yeah, you still need to place all the drafted stuff in a detail group, but you can do it while youre detailing it.

3. Move the column, then go grab the details and move them the same dimension.

4. Depending on the column (is it one family, or a series of walls, etc) you can embed some of the detailing in to the family itself. Detail components, etc.

[Scott Womack]

I agree with Aaron's ideas as a definate basis.

I am a little more unique, in that I am an experienced project manager with 25 years architectural experience, who is also an experienced Revit User. Personnally, eventhough we are usually monitoring the Structural model, as a project manager, I want to KNOW visually when something in the model has moved to cause this "detailing shift". Too many times the assumption is that we just move the components back over the model. There are a meriad of other things to be looked at, and that must be explored IMMEDIDATELY when this occurs. Anyone working on my projects had better not be moving a section, detail, or callout without my authorization or they are in deep trouble, period.

Don't look at this as a huge problem. It can also be used as another form of checking the project/project documents for consistancy, quality, and design integrety. Personnally, I don't want many of my detailcomponents locked to the model elements (repeating brick to the face brick being an exception) so that I can see these shifts. It helps me coordinate the design, as well as keep tabs on the personnel assigned to my projects.

[twiceroadsfool]

100% agree with what you said, Scott.

Revit is great for automating some of the monotony of architecture, but it cant automate the PROJECT, and the ARCHITECTURE itself. Discussions and communications are still a must.