2009
Table Of Contents
- FEEDBACK ON THE GUIDE
- AUDIENCE
- DEFINITION: QUALITY REVIT CONTENT
- CONTENTS
- SUPPLEMENTARY FILES
- ADDITIONAL FILES
- RECOMMENDED REVIT RELEASE AND DISCIPLINE FOR CONTENT CREATION
- 1.1 DETERMINING DESIGN INTENT
- 1.2 BALANCING PERFORMANCE AND DESIGN COMPLEXITY
- 1.3 AUTODESK EXCHANGE FORMAT (.ADSK)
- 1.4 USING IMPORTED CONTENT
- 1.5 PLANNING A REVIT MODEL FAMILY
- 2.1 WORKFLOW FOR MODEL CONTENT CREATION
- 2.2 FAMILY UNITS
- 2.3 FAMILY NAMING CONVENTIONS
- 2.4 TYPE NAMING CONVENTIONS
- 2.5 CATEGORY AND SUBCATEGORY STANDARDS AND USAGE
- 2.6 AUTODESK APPROVED PARAMETER USAGE
- 2.7 PARAMETER NAMING CONVENTIONS
- 2.8 MATERIAL NAMING CONVENTIONS
- 2.9 PREVIEW IMAGE STANDARDS
- 2.10 TYPE CATALOG STANDARDS AND USAGE
- 2.11 MATERIAL APPLICATION IN MODEL FAMILIES
- 3.1 GENERAL FAMILY TESTING GUIDELINES
- 3.2 FAMILY-SPECIFIC TESTING GUIDELINES
1.1DETERMININGDESIGNINTENT
WhencreatingaRevitfamily,theintendeduseofthefamilyinaprojectenvironmentdeterminestheextentto
whichitisdesigned.Youcandesignallfamiliestoincludeanumberofrepresentationsforuseindifferentproject
viewsandprojectphases.
Thetypeandsizeoftheprojectthatafamilyisintendedforuseinisacriticalpointtoconsiderwhendeciding
whatrepresentationsshouldbeincludedinthefamilyandwhatlevelofdetaileachrepresentationshouldhave.
Themoredetailedafamilyis,thelargeritsfilesizewillbe.Thelargerthefilesize,theslowertheperformance,
loading,andregenerationtimeofthefamilywillbe.Whenconsideringthedesignintentofafamily,usethe
followingguidelines:
• Forlargercommercialorinstitutionalprojects,inwhichhundredsofelementsmaybecreatedwitha
singlefamily,designthefamilytobeassmallaspossibletominimizeprojectsizeandperformance
impact.
• Forsmallerresidentialprojects,whereelementscreatedwithasinglefamilyarenotusedubiquitously
andwheretheoverallprojectsizeissmaller,designthefamilytoincludemoredetail.
Thenexttopic,BalancingPerformanceandComplexity,addressestheissueoffamilysizeandcomplexityinmore
detail.
DETERMININGTHETEMPLATETOUSE
Forobjectstypicallyhostedbyothercomponents,suchasawindoworlightfixture,startwithahost‐based
template.Forexample,forawindowordoor,useawall‐basedtemplate,suchasWindow.rftorDoor.rft.Howthe
familyishosted(orwhatitdoesordoesnotattachto)determineswhichtemplateshouldbeusedtocreatethe
family.Ingeneral,thechoiceofatemplateisdrivenbythehostoftheobject,withthefollowingexceptions:
• Floor‐basedobjectstypicallyusealevel‐basedtemplateunlesstheyarerequiredtocutthefloor.For
example,Furnitureobjectsarecreatedwithalevel‐basedtemplate.
• Forobjectsthataredesignedtobeusedinmorethanonediscipline,suchasplumbingorlightingfixtures,
useahost‐basedtemplatethatallowsthegreatestflexibilityforalldisciplines.Forexample,alighting
fixtureusedexclusivelyinanarchitecturaldisciplinecouldbecreatedwithaceilingorwall‐based
template,butforanengineeringenvironment,aface‐basedtemplateisrequiredforthemodellinking
workflow.Therefore,foralightingfixturethatwillbeusedinbothdisciplines,useaface‐basedtemplate.
Version2.1RMCSG—11