|
Forums >> Revit Building >> Tips & Tricks >> Standard Details
|
|
|
active
Joined: Sat, Oct 25, 2003
411 Posts
 |
How would one build a library of standard details from objects drawn in Revit
- detail lines alone
- detail objects + detail lines.
|
This user is offline |
View Website
|
 |
|
|
|
site moderator|||
Joined: Mon, Jan 12, 2004
2889 Posts
 |
We create our standard details as detail components, then simply load into the project you need them in.
|
This user is offline |
View Website
|
|
|
active
Joined: Sat, Aug 6, 2005
241 Posts
 |
Mr. Spot
I've been trying to create standard details as detail components but some of the tools (like insulation and leaders) are not available. How do you usually do these?
Post edited on 2005-10-31 19:43:35
|
This user is offline |
|
|
|
active
Joined: Sat, Oct 25, 2003
411 Posts
|
I think revit is not great at detailing. I haven't gotten to it yet, but seems Autodesk agrees and has some tech info or a white paper on the website about going back and forth with Autocad ADT. Otherwise, you can cut and paste details from one project to another. And also file->transfer project statndards for stuff like wall types.
|
This user is offline |
View Website
|
|
|
active
Joined: Sat, Aug 6, 2005
241 Posts
|
I'd like to be able to archive standard details so I've resorted to turning details into groups and exporting the groups for use in other projects. I haven't played with "transfer project standards" yet.
|
This user is offline |
|
|
|
active
Joined: Sun, Apr 25, 2004
1207 Posts
|
I find this discussion interesting. I have been using Revit for almost three years now on numerous projects and have yet to have an issue with detailing. If you model your building correctly in Revit there is very little to be added to a section or callout to make what you would call in traditional 2D drafting programs a "detail". The only reason that you have a detail library in the 2D drafting world is because you cannot derive the real construction condition from a virtual model of the building so you have to "simulate" the lack of a building model with stock details hoping to choose the correct ones and make notes of items that may differ from what you show on your standard details such as beam sizes, joist depths, mullion widths etc.
To me I'd rather model the building correctly and make use of the detail components Revit provides to add the finishing touches to a "detail" knowing that my "detail" is live to the building model and will react to changes I make to the model as I have made full use of the Revit mechanisms to align, lock, and constrain detail components to the model elements.
Tom
|
This user is offline |
View Website
|
|
|
active
Joined: Sat, Oct 25, 2003
411 Posts
|
If you are able to build without detailed construction sections and details, you have most prescient contractors.
|
This user is offline |
View Website
|
|
|
active
Joined: Sat, Aug 6, 2005
241 Posts
|
I guess I find using standard details faster. Aren't you kind of reinventing the wheel? I mean, for instance, we are using the same details for 8 cottages. I wouldn't want to have to tweek callouts for 8 different cottages to get the same detail.
Post edited on 2005-11-01 18:14:33
|
This user is offline |
|
|
|
site moderator|||
Joined: Mon, Jan 12, 2004
2889 Posts
|
Once we have a detail that we want, we group it and rename it appropriately.
Then load it into a special detail project where we can grab details from as required...
This way we can view the details, select the ones we want and copy and paste into the new project.
HTH.
|
This user is offline |
View Website
|
|
|
active
Joined: Sun, Apr 25, 2004
1207 Posts
|
I never said that we don't provide detailed views of the model to build from, just that these are not "stock" details added from some static library that has no real world relationship to the project being built. In Revit we provide more detailed documentation of the building than we were ever able to provide using AutoCAD. The contractors love our Revit documentation as it is as error free as they have ever seen and provides them with the clearest direction on how to construct the building they have ever seen. All of this is a result of proper modeling and using the features of Revit to enhance enlarged detail views yet have those views live linked to the model rather than to some static image from 15 years ago. As Mr. Spot suggests, there is the ability to group things and save them out which we do, but when these groups are placed into a new project we make sure the detail components get aligned and locked to the proper parts of the model.
Tom
|
This user is offline |
View Website
|
|
|
|
|
active
Joined: Wed, Mar 12, 2008
322 Posts
|
I have a question for those of you using Revit Structure (and I suppose Building as well): When you are creating your standard detail content, are you using detailing components or just linework and filled regions? For example; I want to create a standard detail which has a W-Beam in the detail. Are you using filled regions to accomplish this, or are you actually placing a component? It's been brough up at my firm and I am leaning more towards minimal use of actual shapes. What are you doing and why? Also, on another note, we've created seperate files which house our standard details based on their structural type. When we want to pull them in we simply insert views from file. This works REAL nice.
|
This user is offline |
|
|
|
active
Joined: Thu, Dec 6, 2007
4 Posts
No Rating |
We use Drafting Views to create standard details. all of the drafting tools are available, and drafting views do not need a model behind them for definition. they can exist in isolation. then we collect these drafting views into an .rvt file and place it in the library. then use the Insert From File command to load them into the current project. (this command can also be used to copy drafting views from other projects.) we currently have roofing details, millwork, and head/jamb/sill details done this way. the last job i was able to take care of all the roofing details in about 30 secs.
|
This user is offline |
|
|
|
active
Joined: Fri, May 13, 2005
61 Posts
|
gnomey, I think we using the same approach, perhaps, that is the only proper way to create "standard details".I know others might think can create each standard detail in a detail component family, but I find that will be to much constrain, and asking user to adjust the detail in a detail component is high risk. So down to the road, I think use insert from file will be more approperate. The key for the sucessful standard dtail rvt file is the index system and the view naming.
|
This user is offline |
View Website
|
|
|
active
Joined: Thu, Dec 6, 2007
4 Posts
No Rating |
drafting views really are the best option. they are faster. i can load in all my roof details, for example, in a few clicks. the insert from file command lets you preview each view to pick and choose which details you want. and because these are individual views, i can pre-set the view properties so that they load into the proper place in the browser in our company template. (we've added a parameter to our view properties that let's us define additional view groupings for organization of the browser, so now i can put the roof plan and roof details clustered togehter in the browser under "ROOF".) and of course, the drafting views are named in plain speak english so they're easy to identify without needing to know any codes or abbreviations.
|
This user is offline |
|
|
|
active
Joined: Fri, May 13, 2005
61 Posts
|
True, index system is an extra, I perhaps need to print them out as a referene book, so I need the index system work. If you no need to print those detail out, the index is certainly no need.
|
This user is offline |
View Website
|
|
|
Search