Revit Structure Detail Library

[Anonymous]

Our office is attempting to develop some Revit detail libraries. We intend on filling them with typical / commonly-used details that we plan on inserting into projects. Does anyone have any recommendations on what View Name to use for the details? We are looking for something that is a good combination of functional (solid description of the detail itself considering the different types of materials involved: wood, steel, etc.) and organized (we anticipate a large number of details to be utilized, so the naming convention needs to be able to accommodate the sheer volume of details). Any suggestions or descriptions of real-world use is greatly appreciated. Thanks.

[Alaaeldin_Alsahli]

If you using Metric Values as family type name

Then you could start with M_ for metric

You should mention the company name. to be able to find your families in a collaboration project

M_Company_

Then The discipline ELE, MEC, STR, ARCH,

M_Company_Str_

Then the Material + element name

M_COMPANY_STR_Steel_Beam_

OminClass number could be useful for different project

M_COMPANY_STR_Steel_Beam_23.25.30.11.14.14

And after finishing each project you could export all the famillies used under a new Project family Folder. Sometimes it is easier to remember used famillies under specific project folder.

[Alaaeldin_Alsahli]

You Could Use D for detail in the beginning of the family D_M_....

If ever you want to export all families you could differentiate between model and detail family

[Anonymous]

Thanks for the reply. After working ours out, we ended up with a much simpler coding system. It's intended for internal use, not as a shared thing, so we don't need the company specific stuff. It boiled down to using the coding to define material, material type, and what level it occurs on. We are using a start-up view that has an index of this for easy reference.

[Alaaeldin_Alsahli]

The problem is when comes to big project. BIM managers from different companies get together and decide some standards to simplify the search inside the project. Some project in Canada for example, Like in Ottawa or in the French Provence Require Bilingual Naming. Other project Require Omni Class Number so sometimes it gets trickier for some specific project. 

[Anonymous]

But that's what I meant in saying that this coding system was for internal use only. Outside companies or entities have no real need to know what our coding convention is because it's simply a way for our engineers and Reviteers to communicate with what typical details are needed and where they need to go. The coding system is all numerical also, no acronyms or words or phrases.

[Anonymous]

We use something failry simple, a short description of what type of detail is (Conc, steel etc) and the number on the typical detail sheet. So we will have say 5 concrete sheets named Conc 1, Conc 2, etc. so the detail would be 1-Conc 1, 1-Conc 2 and so on. Simple, and for internal use only.