family creation request form

[dschwers]

I am new to revit management, and I am looking for a family creation request form.
Can any of you expert assist me in creating one, or if you already have one may I barrow it for reference.

Thanks

[richard.binning]

interesting... I'd like to see this too.

[Dave Jones]

I am new to revit management, and I am looking for a family creation request form.
Can any of you expert assist me in creating one, or if you already have one may I barrow it for reference.

Thanks

would this be an in house document for an Architectural firm?

[richard.binning]

I'd think that it could be used by MEP or Structure as well.

[Dave Jones]

I'd think that it could be used by MEP or Structure as well.

makes sense. What I was asking though is if this would be a form that would come internally from an Architectural firm, hence making 1000's of types of them "available" or is it like an AIA doc that is a standard for all Architecture firms?

[j_starko]

there was talk of something like this being structured at my firm. one or a small group of people responsible for revit maintenance and making familes. It makes sense. but doesn't always seem practical..

for me personally, I find it quite easy to find a family online that I can use or modify. then opening it.. putting it on a diet for things and options not needed and then presto .. into the project.
the proposed method would be me showing via website or pdf what I'd like.. then having to wait for someone possibly in another city ( but same firm) creating said componenet some time down the road.

[richard.binning]

Yes, I'd wager that most handle it that way. I remember Paul Aubin had something similar for ADT content in his ADT Implementation Guide. It would be nice to formalize it.

[Dimitri Harvalias]

Spec'ing out a family makes a great deal of sense. It allows a firm to maintain some degree of control over how families are developed, what they contain, graphic conventions etc.
The biggest issue with downloaded content is that it can contain too much detail, parameters/materials/sub-categories that don't adhere to company conventions. You'd be surprised how quickly a project fills up with useless junk when you grab something as 'innocent' as a curtain wall mullion profile off the web or manufacturer's site. (anybody want 45 colors or full spec sections in the comments field just to get a profile that takes 10 minutes to create :shock:)

I'd suggest that you train everyone at the office to create a basic placeholder family (with emphasis on the importance of origin point) and then develop the form you are talking about.

The form should, as a starting point, ask for a description of how the family would be used, whether it needs to be 2D, 2.5D or 3D, what the graphic representation is in plan, elevation, section, what parameters are required (for schedules and tagging) etc.

The main thing is to get people thinking beyond 'what does it look like' and get them into the mindset of
-what information does it need to convey
-who is going to need this information
-what is the best way to convey that information (graphics, data)
-what downstream uses/requirements could be served at the same time

[dschwers]

would this be an in house document for an Architectural firm?

yes we are a firm of 50+ and located in two cities