tag:blogger.com,1999:blog-25558076.post114852369486062343..comments2023-09-20T09:52:20.755-04:00Comments on don't think: Do Revit: Revit Standardization: Family SpecsRoberthttp://www.blogger.com/profile/10689574748658789222noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-25558076.post-5680111993196020072008-08-22T11:01:00.000-04:002008-08-22T11:01:00.000-04:00This is a fantastic idea! I was probably a few ar...This is a fantastic idea! I was probably a few arguments away from coming up with something similar. Teams are always asking for "insert generic family" but cannot define what they actually want. So far, my strategy has been to require drawings with dimensions at the very least and cut sheets if available. The additional issue this solves is that the scope or specifics of the original request change between the time they ask for it and the time you deliver it. Having a document explicitly detailing what is expected helps keep the family maker out of the dog-house. It also forces the person making the request to put some thought into what they really want.<BR/><BR/>On a larger scale, our firm goes through a similar process for projects when we deal with consultants. The document we're using details what is expected from consultants models and determines who is responsible for what information. The intent is the same but on a larger level!<BR/><BR/>Starting my family-request spec right away...Kellhttps://www.blogger.com/profile/04463427749684093048noreply@blogger.comtag:blogger.com,1999:blog-25558076.post-1148667770435231542006-05-26T14:22:00.000-04:002006-05-26T14:22:00.000-04:00DMW,I'm afraid to say that I care not to share the...DMW,<BR/><BR/>I'm afraid to say that I care not to share the actual spec document at this time. Though I will talk it over with the team. The best thoughts I can give is that once you have at least one or two people who are very comfortable with regards to family creation, that it is merely a matter of breaking down what you expect in a well crafted family. For instance, making sure that reference planes are named, that their "is a reference" setting is changed from the default. There are any number of details related to having a good family; symbolic geometry, sub categories, visibility and level of detail settings, etc... Our outline spec merely provides a vehicle for detailing exactly what we want, so that all of our families meet certain expectations.<BR/><BR/>With regards to text, our 2D CAD standard is Aerial Narrow. So, we've set-up our defualt project template to use Aerial narrow, it actually matches pretty darn well, even when we link CAD details/drawings into a Revit project for placement on sheets.Roberthttps://www.blogger.com/profile/10689574748658789222noreply@blogger.com