Autodesk Revit Content 2009 Style Guide EN
User Manual: autodesk Revit Content - 2009 - Style Guide Free User Guide for Autodesk Revit Software, Manual
Open the PDF directly: View PDF .
Page Count: 67
- 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
REVITMODELCONTENTSTYLEGUIDE
December2009
Version2.1
Copyright© 2009 Autodesk, Inc.
All Rights Reserved
This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose.
AUTODESK, INC., MAKES NO WARRANTY, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE REGARDING THESE
MATERIALS, AND MAKES SUCH MATERIALS AVAILABLE SOLELY ON AN "AS-IS" BASIS.
IN NO EVENT SHALL AUTODESK, INC., BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING OUT OF PURCHASE OR USE OF THESE MATERIALS.
THE SOLE AND EXCLUSIVE LIABILITY TO AUTODESK, INC., REGARDLESS OF THE FORM OF ACTION, SHALL NOT
EXCEED THE PURCHASE PRICE OF THE MATERIALS DESCRIBED HEREIN.
Autodesk, Inc., reserves the right to revise and improve its products as it sees fit. This publication describes the state of the
product at the time of publication, and may not reflect the product at all times in the future.
Autodesk Trademarks
The following are registered trademarks of Autodesk, Inc., in the USA and/or other countries: 3D Props, 3D Studio, 3D
Studio MAX, 3D Studio VIZ, 3DSurfer, 3ds max, ActiveShapes, ActiveShapes (logo), Actrix, ADI, AEC Authority (logo), AEC-
X, Animator Pro, Animator Studio, ATC, AUGI, AutoCAD, AutoCAD LT, AutoCAD Map, Autodesk, Autodesk Envision,
Autodesk Inventor, Autodesk (logo), Autodesk Map, Autodesk MapGuide, Autodesk Streamline, Autodesk University
(logo), Autodesk View, Autodesk WalkThrough, Autodesk World, AutoLISP, AutoSketch, backdraft, Biped, bringing
information down to earth, Buzzsaw, CAD Overlay, Character Studio, Cinepak, Cinepak (logo), cleaner, Codec Central,
combustion, Design Your World, Design Your World (logo), EditDV, Education by Design, gmax, Heidi, HOOPS, Hyperwire,
i-drop, Inside Track, IntroDV, Kinetix, lustre, MaterialSpec, Mechanical Desktop, NAAUG, ObjectARX, Physique, Planix,
Powered with Autodesk Technology (logo), ProjectPoint, RadioRay, Reactor, Revit, Softdesk, Texture Universe, The AEC
Authority, The Auto Architect, VISION*, Visual, Visual Construction, Visual Drainage, Visual Hydro, Visual Landscape, Visual
Roads, Visual Survey, Visual Toolbox, Visual Tugboat, Visual LISP, Volo, WHIP!, and WHIP! (logo).
The following are trademarks of Autodesk, Inc., in the USA and/or other countries: AutoCAD Learning Assistance,
AutoCAD LT Learning Assistance, AutoCAD Simulator, AutoCAD SQL Extension, AutoCAD SQL Interface, AutoSnap,
AutoTrack, Built with ObjectARX (logo), burn, Buzzsaw.com, CAiCE, Cinestream, Civil 3D, cleaner central, ClearScale,
Colour Warper, Content Explorer, Dancing Baby (image), DesignCenter, Design Doctor, Designer's Toolkit, DesignKids,
DesignProf, DesignServer, Design Web Format, DWF, DWFit, DWG Linking, DXF, Extending the Design Team, GDX Driver,
gmax (logo), gmax ready (logo),Heads-up Design, jobnet, ObjectDBX, onscreen onair online, Plans & Specs, Plasma,
PolarSnap, Productstream, Real-time Roto, Render Queue, Visual Bridge, Visual Syllabus, and Where Design Connects.
Autodesk Canada Co. Trademarks
The following are registered trademarks of Autodesk Canada Inc. in the USA and/or Canada, and/or other countries:
discreet, fire, flame, flint, flint RT, frost, glass, inferno, MountStone, riot, river, smoke, sparks, stone, stream, vapour, wire.
The following are trademarks of Autodesk Canada Inc., in the USA, Canada, and/or other countries: backburner, Multi-
Master Editing.
Third Party Trademarks
All other brand names, product names or trademarks belong to their respective holders.
Third Party Software Program Credits
ACIS Copyright© 1989-2001 Spatial Corp. Portions Copyright© 2002 Autodesk, Inc.
Copyright© 1997 Microsoft Corporation. All rights reserved.
Flash ® is a registered trademark of Macromedia, Inc. in the United States and/or other countries.
International CorrectSpell™ Spelling Correction System© 1995 by Lernout & Hauspie Speech Products, N.V. All rights
reserved.
InstallShield™ 3.0. Copyright© 1997 InstallShield Software Corporation. All rights reserved.
PANTONE® Colors displayed in the software application or in the user documentation may not match PANTONE-
identified standards. Consult current PANTONE Color Publications for accurate color.
PANTONE® and other Pantone, Inc. trademarks are the property of Pantone, Inc.© Pantone, Inc., 2002
Pantone, Inc. is the copyright owner of color data and/or software which are licensed to Autodesk, Inc., to distribute for
use only in combination with certain Autodesk software products. PANTONE Color Data and/ or Software shall not be
copied onto another disk or into memory unless as part of the execution of this Autodesk software product.
Portions Copyright© 1991-1996 Arthur D. Applegate. All rights reserved.
Portions of this software are based on the work of the Independent JPEG Group.
RAL DESIGN© RAL, Sankt Augustin, 2002
RAL CLASSIC© RAL, Sankt Augustin, 2002
RMCSG—2 Version2.1
Representation of the RAL Colors is done with the approval of RAL Deutsches Institut für Gütesicherung und
Kennzeichnung e.V. (RAL German Institute for Quality Assurance and Certification, re. Assoc.), D-53757 Sankt Augustin.
Typefaces from the Bitstream® typeface library copyright 1992.
Typefaces from Payne Loving Trust© 1996. All rights reserved.
AutoCAD 2006 is produced under a license of data derived from DIC Color Guide® from Dainippon Ink and Chemicals,
Inc. Copyright © Dainippon Ink and Chemicals, Inc. All rights reserved. DIC Color Guide computer color simulations used
in this product may not exactly match DIC Color Guide, DIC color Guide Part 2 identified solid color standards. Use
current DIC Color Guide Manuals for exact color reference. DIC and DIC Color Guide are registered trademarks of
Dainippon Ink and Chemicals, Inc.
Printed manual and help produced with Idiom WorldServer™ .
WindowBlinds: DirectSkin™ OCX © Stardock®
AnswerWorks 4.0 © ; 1997-2003 WexTech Systems, Inc. Portions of this software © Vantage-Knexys. All rights reserved.
The Director General of the Geographic Survey Institute has issued the approval for the coordinates exchange
numbered TKY2JGD for Japan Geodetic Datum 2000, also known as technical information No H1-N0.2 of the
Geographic Survey Institute, to be installed and used within this software product (Approval No.: 646 issued by GSI, April
8, 2002).
Portions of this computer program are copyright © 1995-1999 LizardTech, Inc. All rights reserved. MrSID is protected by
U.S. Patent No. 5,710,835. Foreign Patents Pending.
Portions of this computer program are Copyright © ; 2000 Earth Resource Mapping, Inc.
OSTN97 © Crown Copyright 1997. All rights reserved.
OSTN02 © Crown copyright 2002. All rights reserved.
OSGM02 © Crown copyright 2002, © Ordnance Survey Ireland, 2002.
FME Objects Engine © 2005 SAFE Software. All rights reserved.
GOVERNMENT USE
Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212 (Commercial
Computer Software-Restricted Rights) and DFAR 227.7202 (Rights in Technical Data and Computer Software), as
applicable.
Version2.1RMCSG—3
CONTENTS
FeedbackontheGuide7
Audience7
Definition:QualityRevitContent7
Contents8
SupplementaryFiles8
AdditionalFiles9
Section1:PlanningRevitModelContent10
RecommendedRevitReleaseandDisciplineforContentCreation10
1.1DeterminingDesignIntent11
DeterminingtheTemplatetoUse11
FamilyRepresentations12
1.2BalancingPerformanceandDesignComplexity16
DesignIntentvs.Performance16
RecommendedFamilyFileSizes18
LevelofDetail19
ElementVisibility20
AreastoAvoidforOptimumPerformance20
ExamplesofFamilieswithAppropriateandcomplexLevelsofDetail21
ConsiderationsforNestingFamilyContent22
NestingRecommendations:22
1.3AutodeskExchangeFormat(.ADSK)23
AECExchangeEnvironment23
CreatingIntelligentConnectors23
SimplifyingtheGeometricRepresentation24
Publishingtothe.ADSKformat24
reading.ADSKfiles25
ImportingintoRevitFamilies25
Limitations25
1.4UsingImportedContent26
RMCSG—4 Version2.1
SupportedContent26
Limitations26
1.5PlanningaRevitModelFamily27
Section2:ModelContentCreationStandards28
2.1WorkflowforModelContentCreation29
Prototyping30
2.2FamilyUnits30
2.3FamilyNamingConventions31
2.4TypeNamingConventions33
2.5CategoryandSubcategoryStandardsandUsage35
AddingSubcategoriesToModelFamilies35
SubcategoryNamingConventions36
2.6AutodeskApprovedParameterUsage37
AddingManufacturerDatatoFamilies38
CSIOmniClassTable4938
CSIClassificationCodes39
AssigningtheMasterFormatandUniFormatClassificationinRevit39
AssigningtheOmniClassclassificationinRevit(Revit2010andlater)40
2.7ParameterNamingConventions41
2.8MaterialNamingConventions44
Guidelines44
FormatForIndividualFinishMaterials(StoredInsideProjects)44
FormatForIndividualFinishMaterialsUsinganExternalImageFile45
FormatForIndividualMaterialsImages(StoredOutSideofRevit)45
2.9PreviewImageStandards46
CreatingAutodeskStandardFamilyPreviewImages47
2.10TypeCatalogStandardsandUsage52
TypeCatalogStandards52
2.11MaterialApplicationinModelFamilies54
Option1–ApplyMaterialswiththeMaterialParameter54
Version2.1RMCSG—5
Option2–ApplyMaterialstoFamilyGeometrybyCategoryandSubcategory55
Option3–ApplyMaterialswithCustomInstanceorTypeMaterialParameters55
Example:AssigningMaterialstoaTableFamily56
2.12BestPracticesforAddingConnectorsinRevitMEPFamilies58
AddingaConnector58
SystemTypes59
ConnectorDirection60
PrimaryConnector60
LinkingConnector61
ConnectorMapping62
ConnectorDescriptions63
Section3:TestingGuidelines64
3.1GeneralFamilyTestingGuidelines65
FamilyEditorTestingCriteria65
ProjectTestingCriteriaforRevitArchitecture66
3.2Family‐SpecificTestingGuidelines67
RMCSG—6 Version2.1
INTRODUCTION
ThepurposeofthisguideistodefineAutodeskguidelinesandstandardsformodelcontentcreationinRevit®
Architecture,Revit®MEP,andRevit®Structure.Modelcontentreferstothetwo‐dimensionalandthree‐
dimensionalstandardcomponentfamiliesthatareusedtocreateelementsthatrepresentmanufacturedcontent
(forexample,windows,furnaces,heatpumps,andstructuralsteelmembers).
Byfollowingtheguidelinesandstandardsinthisguide,contentcreatorswillensuretheportabilityand
performanceoftheircontent,andfulfillthenecessarydistributionrequirementsfortheAutodesk®Seekweb
service.TheAutodeskSeekwebservicerequires:
• theuniformdisplayofproductsofferedbyasinglemanufacturer
• complete,consistent,andaccuratepresentationofproductdataacrossmanufacturers
• thefulluseofAutodeskSeeksearchcapabilities
FEEDBACKONTHEGUIDE
PleasesendyourcommentsontheRevitModelStyleGuideandsupportingdocumentationto:
rmsg.feedback@autodesk.com
Wecan’trespondtocommentsindividually,butfeedbackwillbeconsideredinfutureversionsoftheRevitModel
ContentStyleGuide.
AUDIENCE
Thisguideisintendedformanufacturers,contentserviceorganizations,andothercontentcreatorswhohave
advancedknowledgeofbothRevitsoftwareandRevitmodelcontentcreation.
DEFINITION:QUALITYREVITCONTENT
QualityRevitcontentbalancesperformancewithdesignaccuracyandrequiredlevelsofdetail.Qualitycontentis
easytousebecauseitfunctionsreliablyinarangeofprojectsandprojectphases,whiledeliveringmanufactured
contentinaformatappropriateforarchitectureandengineeringdocumentationdeliverables.
QualityRevitcontentiscreatedwiththefollowingconsiderations:
• Designintent–theauthorhasconsideredhowthefamilywillbeusedinaproject.
• Appropriatelevelofdetaildesigned
• Adequatenumberoftypescreated
• Flexibleuseofparameters
• Accuracy–complete,consistentpresentationofproductdata.
• Standards–adherestoindustryandAutodeskstandards.
• Namingconventions
• Graphicguidelines
Version2.1RMCSG—7
• Parameterusage
• Performance–contentdesignedtoreducetheperformanceimpactofthefamilyonaproject.
• Testing–thoroughtestingofthefamilyparametersandtypesindependentlyandinaproject
environment.
CONTENTS
Section1:PlanningRevitModelContent
• Explainshowdesigncomplexityinfamiliescanaffectprojectperformanceandoffersguidelinesfor
reducingperformanceimpact
• DetailstherecommendeduseandlimitationsofcontentcreatedwithotherCADsoftware
• Providesbestpracticesforplanningmodelcontent
Section2:ModelContentCreationStandards
• Describesbestpracticesformodelcontentcreation
• ContainsAutodeskstandardsforunits,namingconventions,subcategories,parameters,previewimages,
andtypecatalogs
Section3:TestingGuidelines
• Containsgeneralandfamily‐specifictestingguidelinesformodelcontentfamilies.
Notincludedinthisguide:
• Detailedfamilycreationinstructions
• Standardsforannotationorsystemfamilycreation
• Category‐specificguidelinesforfamilycreation
• In‐depthbestpracticesforfamilycreation
SUPPLEMENTARYFILES
Thefollowingdocumentsandfilesarereferencedforusewiththisguideandareincludedinthedownload
package.
• RevitMasterParameterList.xls‐includesAutodesk‐approvedRevitmastersharedparameters
• RevitMasterSharedParameterFile.txt‐includesAutodesk‐approvedsharedparameterstouseinyour
projects
• RevitMasterSubcategoryList.xls–includesAutodesk‐approvedRevitsubcategories
• RevitMasterPartTypeList.xls–includesAutodesk‐approvedRevitparttypes
• RevitModelContentSampleFiles–includessampleRevitmodelcontentandimages
• Category‐specificModelContentGuides–includescreationguidelinesforspecificcontent
• SharingRevitContentonAutodeskSeek–includesdistributionrequirementsfortheAutodeskSeekweb
service.
RMCSG—8 Version2.1
ADDITIONALFILES
ThefollowingresourcesareavailableforworkingwithbothRevitmodelcontentandAutodeskSeek.
AUTODESKMETADATASTYLEGUIDEANDPRODUCTWORKBOOK
TheAutodeskMetadataStyleGuidedefinesstylesandformattingrulesthatmanufacturers,contentservice
organizations,andcontentspecialistsmustabidebysothatthecontentthattheyproducecanbeloadedintothe
AutodeskSeekstagingenvironment.
Downloadat:http://seek.autodesk.com/participate.htm.
DOCUMENTATION
FormoreinformationonRevitfamilycontentcreation,seethefollowingreferencemanualsandtutorials:
• Revit®ArchitectureFamiliesGuide
Downloadatwww.autodesk.com/revitarchitecture‐documentation.
• RevitArchitecture,Revit®MEP,andRevit®StructureTutorials
Downloadat:
www.autodesk.com/revitarchitecture‐documentation
www.autodesk.com/revitmep‐documentation
www.autodesk.com/revitstructure‐documentation
DISCUSSIONGROUPS
• AUGI(AutodeskUserGroupInternational)
Accessatwww.augi.com.
• AutodeskSeekDiscussionGroup
Accessatwww.autodesk.com/contentsearch‐discussion.
Version2.1RMCSG—9
SECTION1:
PLANNINGREVITMODELCONTENT
InordertoensureRevitmodelcontentisdevelopedefficientlyandtoAutodeskstandards,contentcreatorsshould
followAutodesk‐approvedbestpracticeswhencreatingRevitfamilies.
Byfollowingtheguidelinesinthissection,youcan:
• createRevitfamilycontenteasilyandwithfewererrors
• ensureconsistencyandstabilityofRevitfamilycontent
• createcontentsuitablefordeliveryonAutodeskSeek
RECOMMENDEDREVITRELEASEANDDISCIPLINEFORCONTENTCREATION
Note:AllsamplefamilyandprojectfileswerecreatedbasedontheRevitPlatform2009release;therefore,they
can’tbeopenedinearlierversionsofRevit.
RECOMMENDATION:Toensurethatcontentisavailabletothelargestnumberofendusers,createthecontent
usingAutodeskRevit2009.Contentcreatedinrelease2009canalsobeusedinlaterversionsofRevit.Ifthe
contentrequiresfunctionalityavailableinalaterrelease,thencreatethecontentinthatreleaseofRevit.
UsetheRevitproduct(RevitArchitecture,RevitMEP,orRevitStructure)thatisappropriateforthecontentyouare
creating,forexample,foraDoorfamily,useRevitArchitecture,foranAirHandlingUnit,useRevitMEP.Ifthe
contentcrossesdisciplines,forexample,alightingfixtureorplumbingfixture,usetheproductthathasthemost
requirements,inthiscaseRevitMEP.
RMCSG—10 Version2.1
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
FAMILYREPRESENTATIONS
Dependingontheintendeduseofafamily,itmaycontainthefollowingrepresentations:
• Schematic(genericcontent;typicallynotmanufacturerspecific;mayincludemultiplelevelsofdetail)
• Designdevelopment(manufacturer‐specificcontent;typicallyCoarselevelofdetail)
• Constructiondocument(manufacturer‐specificcontent;typicallyMediumlevelofdetail)
• Highqualityrendering(manufacturer‐specificcontent;typicallyFinelevelofdetail)
Dependingontheusecaseforthecontent,the3manufacturer‐specificrepresentations(Designdevelopment,
Constructiondocument,andHighqualityrendering)maybedevelopedin1or2familyfiles.Forexample,one
familyfilemaycontaintheDesigndevelopmentandConstructiondocumentationrepresentationsofthecontent
andasecondfilemaycontainthehighqualityrenderingrepresentation.TypicallyMEPcontentdoesnotincludea
highqualityrendering,soforthistypeofcontentonefamilyfilemaybecreatedcontainingtheDesign
developmentandConstructiondocumentationrepresentations.
SCHEMATIC
Schematicrepresentationsarecreatedfromtwo‐dimensionallineworkandrepresentthefamilyobjectinitsmost
basicappearance.Theycanbeconsidered“placeholders”forelementsthatwillbeincludedinmoredetailed
designdrawings.Schematicrepresentationsdonotusuallydisplaymaterials.
RMCSG—12 Version2.1
Schematicrepresentationsofatoiletfamilyandofatablefamily
DESIGNDEVELOPMENT
Designdevelopmentrepresentationsincludemoredesigndetailthanschematicrepresentations,aswellas3D
forms.Theymayalsoincludebasicmaterials.Dependingontheelementthatwillbecreatedfromthefamily,the
designdevelopmentrepresentationmayincludethefollowingviews,aswellasappropriatelevelsofdetail:
• Model
• Plan/ReflectCeilingPlan(RCP)
• Section/Elevation
• TypicallyCoarselevelofdetail
Designdevelopmentrepresentationofawindow:displaysminimaldetail,mullionsarerepresentedbymodellines
Version2.1RMCSG—13
Designdevelopmentrepresentationofawatersoftener:displaysbasicshapesofthesoftenerandshows
connectors
CONSTRUCTIONDRAWING
Constructiondrawingrepresentationsareusuallysymbolictwo‐dimensionalrepresentations.Dependingonthe
elementthatwillbecreatedfromthefamily,theconstructiondrawingrepresentationmayincludethefollowing
viewsaswellasappropriatelevelsofdetail:
• Plan/ReflectedCeilingPlan(RCP)
• Section/Elevation
• TypicallyMediumlevelofdetail
Constructiondocumentationrepresentationofawindow:includesmullionsandswing
RMCSG—14 Version2.1
Constructiondocumentationrepresentationofawatersoftener:displaysamorerealisticrepresentationofthe
softeneranditsconnections
HIGHQUALITYRENDERING
Todefinetheappearanceoffamilyelementsinhighqualityrenderings,materialsmustbeassignedtofamily
geometry.Materialpropertiesandlightingmustbedefined.Therenderingistypicallycreatedfroma
representationwithFinelevelofdetailthatincludesobjectsnotusuallyshowninconstructiondrawings,suchas
thehardwareorinlayinthetablebelow.
Highqualityrepresentationofatableinashadedviewandinarenderedimage
Version2.1RMCSG—15
1.2BALANCINGPERFORMANCEANDDESIGNCOMPLEXITY
ThedesigncomplexityofafamilycanaffectitsperformancewhenitisusedtocreateelementsinRevitprojects.
Thisisanimportantconsiderationwhencreatingfamiliesthatincludealotofgeometry,multipleparametric
relationships,and/oralargenumberoffamilytypes(sizes).Efficientgeometrycreation,judicioususeof
parametricconstraints,andcarefullyplanneddetailandvisibilitysettingscanreducetheperformanceimpacta
familywillhaveontheprojectsinwhichitisused.
Inthissection,youlearnto:
• Identifypossibleperformancegainsandimpedimentspriortofamilycreation
• Managedifferentperformancefactors,includingparametricrelationships,detaillevel,andvisibility
settings
• Createefficientfamilies
DESIGNINTENTVS.PERFORMANCE
Themorecomplexanddetailedafamilyis,thelargeritsfilesizeandimpactonperformancewillbe.Before
creatingafamily,determinethefollowing:
• Thedesignintentofthefamily:Whataretherepresentationsthatthefamilymustcontain(schematic,
designdevelopment,constructiondocumentation,highqualityrendering),andhowdetailedmusteach
representationbe?
• Thetypeofprojectinwhichthefamilywillbeusedandhowfrequentlyitwillbeused:Willthefamily
createonly10elementsinasmallresidentialproject,orwillitbeusedtocreatehundredsofelementson
manyfloorsofalargecommercialbuildingmodel?
RMCSG—16 Version2.1
Thefollowinggraphdisplaysthegeneraltrendfortheimpactofdesigncomplexityonfilesize.Generallythemore
representationsafamilyhasandthemoredetailedtheyare,thelargerthefamilyfilesize.Thelargerthefamilyfile
sizeis,themoreofanimpactitwillhaveonperformance(longerloadingandregenerationtimesandgreater
increaseinprojectfilesize).
ImpactofDesignComplexityandProjectSizeonFamilyFileSize
Forexample,awindowfamilythatisintendedtobeusedhundredsoftimesinalargecommercialprojectwillhave
asmallerfilesizeifitcontainsonlybasicschematicanddesigndevelopmentrepresentations.Impactonthe
projectsizewillbeasminimalaspossible.
Conversely,adifferentwindowfamilyintendedforuseinasmallresidentialprojectmaycontainahighquality
renderingrepresentationthatwillincreaseprojectfilesizewhenthefamilyisadded,butbecausethewindowsit
createsareaddedtotheprojectonlyafewtimes,theincreaseinfilesizeismanageable.
Version2.1RMCSG—17
RECOMMENDEDFAMILYFILESIZES
Toprovidecontentcreatorswithatangibleguidelineforfamilyfilesize,somecommonfamilytypesandtheir
recommendedfilesizesarelistedbelow.Usethefilesizesbelowasarecommendation,asactualsizemayvary.
Large,complex,and/orunusualfamiliesmayexceedtheserecommendations.
ApplicationElementComplexityLevelFileSize
RevitArchitectureCaseworkSimple 200
–
300K
Complex 500K
Door(single‐panel) Simple 300
–
400K
Complex 600K
FurnitureSystem Simple 200
–
300K
Complex 500K
Window(single‐unit) Simple 300
–
400K
Complex 600K
RevitMEPAirHandlerUnitSimple 300
–
400K
Complex 800K
–
1000K
ChillerSimple 300
–
400K
Complex 800K
FanSimple 200
–
300K
Complex 400K
PlumbingFixture Simple 300
–
400K
Complex 600K
RevitStructureW‐ShapeSimple 180
–
200K
Complex 300K
IMPORTANT:Tohelpreducethefilesize,inRevit,clickFile→PurgeUnusedtodeleteitemsthatarenotinuse,
clickFilemenu→SaveAs,andverifythattheCompactFileoptionisselectedwhensavingthefile.
RMCSG—18 Version2.1
LEVELOFDETAIL
Detaillevelsdeterminewhichpiecesoffamilygeometrydisplayindifferenttypesofprojectviews.WhenaRevit
elementiscreatedwithafamilyandaddedtoaprojectview,thecurrentdetailleveloftheview(coarse,medium,
orfine)displaystheappropriatefamilygeometry.
INTENT:Theintentistobuildthefamilybasedontheexpectedfinerepresentation,thenremovedetailtocreate
thelowerlevelsofdetail.Thisapproachimprovestheperformanceofthefamilyinlowerlevelsofdetailviewsin
theproject,butstillprovidestherequiredgraphicsforproperdocumentationofaproject.Theintentisnotto
buildeachlevelofdetailincrementallyoradditionally.
AwindowdisplayedinbothCoarseandFinedetail
Familiesthatincludeintricatelevelsofdetailcanimpedeperformancewhenusedinprojects.Foroptimalfamily
performance,onlythenecessaryfamilygeometryshouldbemodeledandtheuseofhighlydetailed
representationslimited.
Whendecidingwhatlevelofdetailshouldbeshown,usethefollowingrecommendations:
• Don’tmodelgeometrythatwillnotbevisiblewhenthefamilyisaddedtoabuildingmodel.
Forexample,foratablefamilythatincludesadrawer,modelthefaceonly,nottheentiredrawer.
• Dependingonthetypeoffamily,usethefollowingguidelinewhenmodelinggeometry:
Ifthegeometryis…Setthedetaillevelto…
Smallerthan1’Fine
1’
–
3’Medium
Largerthan3’Coarse
• Donotduplicategeometrythatcanbeusedfordifferentlevelsofdetail.
Version2.1RMCSG—19
ELEMENTVISIBILITY
Typically,thegeometryofanelementcreatedbyafamilywillchangedependingonthecurrentprojectview.The
visibilitysettingsofthefamilydetermineinwhichprojectviewselementscreatedwiththefamilywilldisplay.
Inaplanview,youmaywanttoseea2Drepresentationoftheelement.Ina3Dorelevationview,youmaywant
todisplayafullydetailed3Drepresentationoftheelement.Inotherviews,youmaywanttohidetheelement.
Limitingthevisibilityofhighlydetailedfamilygeometrytoonlycertainviewscanimproveprojectperformance.
AREASTOAVOIDFOROPTIMUMPERFORMANCE
Usethistableasaguidetoimprovetheperformanceofyourfamilies.
CommonMistakeWhenCreatingFamilies RecommendedApproach
LackofplanningpriortofamilycreationBeforecreatingafamily,usetheguidelinesoutlinedin
1.4PlanningaRevitModelFamily.
UnnecessaryparametricrelationshipsBeforeaddinggeometrytoafamily:
• Plantheparametricrelationshipsandcreatea
familyskeletonthatfeaturesthemain
parametricrelationships.
• Buildonlytheparametricfamilybehaviorthat
youneedtoavoidover‐constrainingthe
model.
• Flextheskeletontotesttherelationships
beforeyouaddgeometry.
Useofgeometryinsteadofsymboliclinesinplanviews Inplanviewrepresentations,geometryusuallycanbe
representedwithsymboliclines,ratherthan(solid)
geometry.Usinggeometryinsteadofsymboliclineswill
createanunnecessarilylargerfamily.
Highlevelsofgeometricdetailandunderuseofvisibility
settings
UsetheguidelinesintheLevelofDetailandElement
Visibilitysectionsofthisguidetoavoidunnecessarily
largefamilyfiles.
Overuseofvoids,formulas,andarraysExtensiveuseofvoids,formulas,andarrayswilladdto
theoverallfamilysizeandaffectitsperformancein
projects.
Useoftoomanynestedfamilies(familiesimportedinto
otherfamilies)
Nestfamiliestocreategeometryinotherfamilies only
whennecessary.Onlyusenestedcontenttoshare
objectsamongmultiplefamilies,forexample,door
hardware,muntinpatterns,andsoon.
Largefamilieswithmanytypesthatdonotincludetype
catalogs
Themoretypes(particularlyunused)theheavierthe
family.Createtypecatalogsforfamiliesthatcontain6
ormoretypes.See2.10TypeCatalogStandardsand
Usage.
InadequatefamilytestingSee 3.1 GeneralFamilyTestingGuidelines.
RMCSG—20 Version2.1
EXAMPLESOFFAMILIESWITHAPPROPRIATEANDCOMPLEXLEVELSOFDETAIL
ThepurposeofcreatingRevitfamiliesformanufacturedcontentisnotforthemanufacturingprocess,butfor
architectureandengineeringdocumentationdeliverables.Itisimportanttocreatethefamilycontentatan
appropriatelevelofdetailfortheintendeduse.Thefollowingexamplesofawindowfamilyillustratethisguideline.
Ineachofthefollowingimages,thewindowontheleftincludesanappropriatelevelofdetailandthewindowon
therightincludesmoredetailthanisrequiredorusefulfortheproject.
PLANVIEW
NOTE:Theaboveimageshowstypicalgraphicqualityforaplanviewscale.Noticethe“muddy”qualitytothe
windowontheright.
PLANVIEWENLARGED
SECTIONVIEW
Version2.1RMCSG—21
CONSIDERATIONSFORNESTINGFAMILYCONTENT
Anestedfamilyisonethathasbeenloadedintoanotherfamily.Insomecases,itcanbeconvenienttorepresent
partsofthenestedfamilyseparatelyfromthemainfamilymodel.Forexample,youcouldcreateawindowsill
familyandnestitinawindowfamily.Thisallowsyoutobuilduponpreviousworkwhilecreatingfamiliessuitedto
yourneeds.
IMPORTANT:Itisimportanttounderstandthatnestingfamiliesincreasesthefilesizeandaffectsperformance,
specificallytheregenerationprocessofthefamilyviews.
NESTINGRECOMMENDATIONS:
• Insteadofnesting,considercreatingallofthenecessarygeometryinthefamily.Usereferencelinesand
labelstolockgeometryinplace.
• Limitnestingto2levels‐Thedeeperthatfamiliesarenested,thelongertheytaketoupdateinthe
projectfile.
• Onlynesthigh‐valuecontentthatmaybeusedinseveraldifferentfamilies,suchasadoorhandle.
Becarefulwhenchanginganestedcomponentthatissharedbymorethanonefamily.Whenyoureload
thecomponentintotheprojectfileitwillupdateallofthefamiliesinthefilesharingthesamenested
family.
RMCSG—22 Version2.1
1.3AUTODESKEXCHANGEFORMAT(.ADSK)
Startinginthe2010releaseofAutodeskproducts,theAutodeskExchangeformat(.ADSK)providesanimproved
methodformanufacturerstoleverageDigitalPrototypestoproduceRevitFamilies.TheInventor2010AEC
ExchangeenvironmentprovidesmanufacturerswiththeabilitytoprovidetheirexistingDigitalPrototypesas.ADSK
files,whichcancontainasimplified3Dgeometricrepresentation,intelligentconnectors,andotherproduct
metadatathatcanbereadbyRevitArchitecture2010,RevitMEP2010,AutoCADArchitecture2010,andAutoCAD
MEP2010software.ByreusingtheinformationfromexistingCADdesigns,manufacturersandtheircustomerscan
avoidthetimeandexpenserequiredtoremodelthisdata.
AECEXCHANGEENVIRONMENT
TheAECExchangeenvironmentisavailableinInventor2010andlaterversions,andthecommandsforpreparing
andpublishingcontentareavailabledirectlywithintheInventoruserinterface.Thecontentpreparationand
publishingprocessinvolves:
• Creatingintelligentconnectors
• Simplifyingthegeometricrepresentationoftheproductdesign
• Addingproductmetadatainformation
• Publishingthedesigntothe.ADSKformat
CREATINGINTELLIGENTCONNECTORS
TheAECExchangeenvironmentsupportsthedefinition
ofpiping,ducts,andelectricalconnectors,whichallow
theAECApplicationUsertoconnecttheADSK‐sourced
contenttoBuildingServicesintheirdesigns.
Theseconnectorsareassignedpropertiesthatare
relevanttotheirusage(e.g.,flowdirectionand
quantityofairflowforaduct),whicharerequiredfor
connectiontotheirrespectiveBuildingServices.
Version2.1RMCSG—23
Figure1‐ElectricalConnectorsonanHVACUnit
SIMPLIFYINGTHEGEOMETRICREPRESENTATION
AsthetypicalDigitalPrototypeismodeledaround
manufacturinglevelofdetail,itissuggestedthata
modelsimplificationworkflowbeusedtodramatically
simplifyandreducethelevelofdetailthatisprovided
toAECCustomers.
Withoutmodelsimplification,thehighlevelofdetail
thatcanbepresentinaDigitalPrototypewillhavean
adverseimpactonmodelperformanceintheAEC
application.Userscancontrolthelevelof
simplification,rangingfromremovalofkeyinternal
detailstoacomplete“shrinkwrap”thatrepresents
onlytheouterenvelopeoftheproductdesign.The
“shrinkwrap”processenablesthecreationofa
simplifiedgeometricrepresentationofthebuilding
productwhileretainingtheinformationthatisdesiredbyarchitectsandengineers.Theprocesscanalsohelp
protecttheIntellectualpropertythatmanufacturersdonotwishtodisclosetodownstreamcustomers,byallowing
forselectivedeterminationoffeaturesandgeometrytobeincludedorexcludedduringtheprocess.
Figure2‐DetailedGeometryofanHVACUnit
Figure3–Simplifiedrepresentation
PUBLISHINGTOTHE.ADSKFORMAT
Thepublishingprocessinvolvesexportingtherelevantgeometry,connectors,andproductinformationtothe
.ADSKfile.Usershavetheoptiontoexportrelevantproductmetadata(e.g.,producttype,model,manufacturer,
cost,andcustom).TheproducttypeclassisbasedontheOmniClassTable23AECIndustryTaxonomy.Direct2D
viewrepresentationsofthe3Dgeometrycanalsobeincluded.
RMCSG—24 Version2.1
READING.ADSKFILES
The.ADSKformatcanbereadbyRevitArchitecture2010,RevitMEP2010,AutoCADArchitecture2010,and
AutoCADMEP2010softwareversionsorlater.Informationfromthe.ADSKfilecanbeincorporatedintothe
receivingapplicationandsavedoutintheapplication’snativeformat.
IMPORTINGINTOREVITFAMILIES
ADSKfilesthencanbeimportedintoRevitFamiliesforsomepostprocessingtohelpmeettherequirementsofthe
RevitModelContentStyleGuide.Thisprocesswillbediscussedinmoredetailinafutureappendix.
LIMITATIONS
TherearelimitationstoADSK‐sourcedcontentwhichshouldbeunderstoodinordertomaximizethevaluefor
manufacturersandtheirspecifyingAECcustomers.Notethatsomeoftheselimitationscanbemitigatedwithpost‐
processingoftheADSKfilesafterithasbeenconsumedbyRevit.
• AsaresultofthemodelsimplificationprocessinInventoranddifferencesbetweentheInventorandAEC
product’sParametricgeometryhandling,thegeometrythatiscurrentlyproducedforAECapplications
throughtheAECExchangeEnvironment,isstatic,andcannotbeediteddirectlybytheAECuser.Itwill
appearasimportedgeometry.
• ADSKfilesdonotcurrentlycontainvisualappearanceinformation,andthereisnowaywithinRevit
productstomanuallymodifytheirappearance.
• ADSKfilesdonotcurrentlysupportRevitHostingbehavior,andthereforethecontentcannotbeplaced
onFacesofBuildingElements,orhaveholescutinthem.IntegratingthecontentintoaRevitfamily(.rfa)
filecanhelpremovethislimitation.
• LightSourceDefinitionscannotcurrentlybedefinedinADSKfiles,andthusmustbemanuallyaddedin
theRevitenvironmentifneeded.IntegratingthemintoaRevitfamily(.rfa)filecanhelpremovethis
limitation.
Asaresultofcurrentlimitations,ADSKfilesaremosteffectivefordeliveringconfiguredengineeringproductsthat
donotrequireahighlevelofvariabilityforusebytheenduser.
Version2.1RMCSG—25
1.4USINGIMPORTEDCONTENT
ContentcreatedinotherCADformatsmaybeimportedandusedtocreateRevitfamilycontent.Importedcontent
mayincludegeometry,metadatasuchasproductperformanceinformation,connectors,andviews.Theuseof
suchimportedgeometrydoesnotofferallofthecapabilitiesavailablewiththe.ADSKformat(seeSection1.3)but
isanoptionif.ADSKdataisnotavailable.
WhenimportinggeometryfromotherCADformats,foroptimalresultsandintegralfamilyfunctionality,itis
recommendedthattheimportedgeometryisusedasaguideforfamilycreation,notasthefamilygeometryitself.
NOTE:ItisacceptabletouseimportedgeometryforcontentthatisdifficulttocreategeometricallyinRevit,such
aspeople,trees,cars,etc.
SUPPORTEDCONTENT
RevitfamiliessupporttheimportofcontentcreatedinthefollowingCADfileformats:
• .DWG(AutodeskAutoCADformat)
• .DXF(AutoCADDrawingInterchangeFormat)
• .SAT(SpatialCorporationStandardACISformat)
• .SKP(GoogleSketchUpModelformat)
LIMITATIONS
Ifyouimportcontentintoafamilyanduseittocreatethefamilywithoutmodification,theresultingfamilytypes
willbeaddedtobuildingmodelsasstaticelementsthatdonotsupportthedynamicparametricrelationships
inherentinRevitbuildingmodels.Familiescreateddirectlyfromimportedcontentdonotsupportdirect
assignmentofmaterialsandotherparameters,limitingtheiroveralluseintheprojectenvironment.Imported
contentmayalsohaveadverseeffectsonprojectperformance.Insomecases,theselimitationsmaybe
acceptable,buttoconformtostandardbuildinginformationmodelingpractice,itisrecommendedthatmost
importedcontentshouldberecreatedasafullyfunctionalRevitfamily.
RMCSG—26 Version2.1
1.5PLANNINGAREVITMODELFAMILY
Beforefamilycreationbegins,carefulupfrontplanningofthefamilyshouldbeperformed,evenforthesimplestof
families.Planningfamiliespriortocreationcansavetimeandpreventerrors.
• Willthefamilyneedtoaccommodatemultiplesizes?
Forawindowthatisavailableinseveralpresetsizes,orabookshelfthatcanbebuiltinanylength,create
astandardcomponentfamily.
• Howshouldthefamilydisplayindifferentviews?
Thewaytheobjectshoulddisplayinviewsdeterminesthe3Dand2Dgeometrythatyouneedtocreate,
aswellashowtodefinethevisibilitysettings.Determinewhethertheobjectshoulddisplayinaplanview,
elevationview,and/orsectionalviews.
• Doesthisfamilyrequireahost?
Forobjectstypicallyhostedbyothercomponents,suchasawindoworlightfixture,startwithahost‐
basedtemplate.Howthefamilyishosted(orwhatitdoesordoesnotattachto)determineswhich
templatefileshouldbeusedtocreatethefamily.
• Howmuchdetailshouldbemodeled?
Insomecases,youmaynotneed3Dgeometry.Youmayonlyneedtosketcha2Dshapetorepresentyour
family.Also,youmaysimplifythe3Dgeometryofyourmodeltosavetimeincreatingthefamily.For
example,lessdetailisrequiredforawalloutletthatwillonlybeseenininteriorelevationsfroma
distance,thanforadoorwithraisedpanelsandasidelightthatwillbeseeninaninteriorrendering.
• Whatistheinsertion/originpointofthisfamily?
Theinsertion/originpointisthepointatwhichyouwanttoplacethefamilyinaproject(indicatedbythe
cursorposition).Theinsertionpointmaychangebasedonusecase.Forexample,theinsertionpointfor
windowsanddoorsisthecenterofthegeometry,sothatthecontentparametricallyexpandsfromthe
centerout.Foracountertop,theinsertionpointisatacornerandthecontentexpandswiththeinstance
lengthinonedirection.Determiningtheappropriateinsertionpointwillhelpusersplacethefamilyina
project.
Version2.1RMCSG—27
SECTION2:
MODELCONTENTCREATIONSTANDARDS
InordertoensureRevitmodelcontentisdevelopedefficiently,consistently,andtoAutodeskstandards,content
creatorsshouldfollowtheAutodesk‐approvedstandardsinthissectionwhencreatingRevitfamilies.
Usethetopicsinthissectionto:
• ensureconsistencyandstabilityofyourRevitfamilycontent
• ensureaconsistentuserexperience
• createcontentsuitabletoshareonAutodeskSeek
RMCSG—28 Version2.1
2.1WORKFLOWFORMODELCONTENTCREATION
Beforeyoucreateamodelfamily,reviewthestandardsinthissection,andthenusethebestpracticeworkflow
belowtocreateyourcontent.Thisworkflowhelpstoensurethatyourcontentiscreatedinthemostefficientand
leasterror‐pronemanner.
1. Createanewfamilyfile(.rfa)withtheappropriatefamilytemplate.
2. Definesubcategoriesforthefamilytohelpcontrolthevisibilityofthefamilygeometry.
3. Createthefamilyskeleton,orframework:
• Definetheorigin(theinsertionpoint)ofthefamily.
• Layoutreferenceplanestosnaptowhenyousketchcomponentgeometry.
• Adddimensionstospecifyparametricrelationships.
• Labeldimensionstocreatetypeorinstanceparametersor2Drepresentation.
• Test,orflex,theskeleton.
4. Definefamilytypevariationsbyspecifyingdifferentparameters.
5. Addasinglelevelofgeometryinsolidsandvoids,andconstrainthegeometrytoreferenceplanes.
6. Flexthenewmodel(typesandhosts)toverifycorrectcomponentbehavior.
7. Repeatpreviousstepsuntilthefamilygeometryiscomplete.
8. Specify2Dand3Dgeometrydisplaycharacteristicswithsubcategoryandentityvisibilitysettings.
9. Savethefamily,andthentestit.
10. Forlargefamiliesthatincludemanytypes,createatypecatalog.
TIP:Formoreinformationonthestepsinthisworkflow,downloadtheRevit®Architecture2009FamiliesGuide
(www.autodesk.com/revitarchitecture‐documentation),andseetheCreatingStandardComponentFamiliestopic.
Version2.1RMCSG—29
PROTOTYPING
Ifyouneedtocreateanumberofsimilarfamilies:
1. Planandcreateasingle“prototype”family.
2. TesttheprototypefamilyintheFamilyEditorandinaprojectenvironmenttoidentifyanyerrorsor
inconsistencies.
SeeSection3:TestingGuidelinesfortestingcriteria.
3. Correctanyerrorsandinconsistenciesandretestthefamilytoensureitisworksproperlybeforecreating
theadditionalfamilies.
2.2FAMILYUNITS
Althoughfamiliescanbecreatedasunit‐specific(imperialormetric),Revitsoftwarestoresallcoordinatesin
universalunitsanddisplaysspecificunitsaccordingtouserpreference.Thismeansthat:
• Unitscanbesettodisplayasnecessaryforatargetaudience(i.e.,displayasdecimalunitsforacivil
engineeringdrawingorfractionalunitsforanarchitecturaldrawing).
• Familiescreatedinimperialunitsmaybeloadedintoandusedinmetricprojectsandviceversa.
Forinformationonchangingthedisplayofunits,see“ProjectUnits”intheRevitHelp.
Touseanimperialormetricfamilyinaprojectwithdifferentbaseunits,useoneofthefollowingoptions:
• Loadthefamilyintheprojectwhereitwillusethecurrentprojectunits.
However,anyimperial‐ormetric‐specifictextinthefamilyname,typenames,andparameternameswill
stilldisplayasmetricunlessexplicitlychanged.Standardssizesmayalsoneedtobeadjusted.
• Duplicatethetypeswithinametricorimperialfamilytocreatebothimperialandmetrictypeswithinthe
family.
• Openthefamily,saveitasanewfamily,andchangetheunits.
RMCSG—30 Version2.1
2.3FAMILYNAMINGCONVENTIONS
FamilynamesaretheprimarymeansofidentifyingfamiliesinAutodeskSeekandintheRevitsoftware.Autodesk
familynamingconventionsensurethatfamiliescanbeidentifiedinAutodeskSeekandtheRevitsoftwarebythe
real‐worlditemsthattheycreate.Thenamingconventionsincludedescriptorsthatallowtheusertosearchfor
familiesbyelement,bymanufacturer,and/orbaseunits.
GUIDELINES:
• Createuniquenamesforeachfamily.
Forexample,afixedwindowfamilyandafixeddoorfamilycannotsharethesamename.
• Usenaturallanguagetonamethefamily.
Thefamilynameshoulddescribehowthefamilyisidentifiedintherealworld(i.e.,incatalogs,by
manufacturer,etc.).
• Ifpossible,donotincludethefamilycategoryinthefamilyname,unlessthefunctionaltypeisthesame
asthecategory(e.g.,window).
• Use‘titlecasing’(aswiththetitleofabook)forfamilynames,astheyarecasesensitive.
• Keepfilenamesasshortaspossible.
FamilynamesmustdisplayindialogsandintheTypeSelector.
• Whenaddingoptionaldescriptorstofamilyfilenames,considertheorderinwhichthedescriptorsare
listedtoensurethatthefamilyfilesdisplayintheProjectBrowserinthemostlogicalandintuitiveorder.
• Donotusespacesbetweenwordsinfilenames.Toseparatewordswithinasyntaxelement(e.g.,
ManufacturerorDescriptor),usetheunderscorecharacter(_).
• Ifahyphen(‐)isusedtoincludeaperformancerange,enclosetherangeinparentheses,forexample,
(230‐250_Ton).
• Ifatypecatalogistobeusedwithafamily,namethetypecatalog(.txtfile)withthesamenameasthe
family.Seesection2.10foradditionalinformation.
FORMAT
<FunctionalType>‐<Subtype>‐<Manufacturer>‐<Descriptor1>‐<Descriptor2>‐<2Difnecessary>
Note:RefertotheRevitMasterPartTypeList(includedinthedownloadpackage)forinformationonapproved
FunctionTypesandSubtypes.
Descriptionoffields:
Field/ComponentRequiredorOptional Description
FunctionalTypeRequiredNamestheelementthatthefamilycreates(forexample,
DoororWindow)
SubtypeAsneededNamestheparttype,forexample,foraWindow the
subtypecouldbeCasement.
Manufacturer/GenericOptionalManufacturername,genericfamiliesmaysubstitute the
Manufacturernamewith“Generic.”
DescriptorAsneeded
2DRequiredUseonlyfor2Dfamilies
Version2.1RMCSG—31
Examples
Window–Double_Hung–Acme–Tilting_Sash–Clad.rfa
Chiller–Air_Cooled–Acme–Low_Profile.rfa
Fountain–Drinking–Acme–Polished_Chrome.rfa
Window–Double_Hung–Generic–Wood.rfa
Chiller‐Air_Cooled‐Acme‐Scroll‐(75‐100_Ton)‐Pkgd.rfa
RMCSG—32 Version2.1
2.4TYPENAMINGCONVENTIONS
Allfamiliesmustincludeonepredefinedtype.Forfamiliesthatcreatereal‐worldobjectsthatareavailablein
standardsizes,predefinedtypesshouldbegenerated.Unlesstheyrepresentnominalsizes,typenamesshould
includeunitsorcapacity,andincludeaunitindicator.
Whennamingafamilytype,usetheformatandrulesbelow:
GUIDELINES
• Donotincludethefamilynameorcategoryinthetypename.
• Typenamesshouldmirroractualusage.
• Typenamesshouldindicatethekeydifferencesbetweentypes(size,count,material)and,when
applicable,reflectstandardsizes.
Insomecases,youmaybasenamesonsizedifference,butusecommontermsratherthannumbers.
• Whentypesarenamedbysize,usedimensionsonly.
Avoidtheuseofcharactersorwords.(h,w,d,orheight,width,depth).
• Typenamesshouldincludeunitsorcapacityandaunitindicator,unlesstheyrepresentnominalsizes.
• Metrictypesshouldreflectthelocalunitstandard,unlessthetypesareintendedtobegeneric.
• Keeptypenamesasshortaspossible.
TypenamesmustdisplayindialogsandintheTypeSelector.
FORMAT
Unlessthereisamarket‐specificreasontodootherwise,usethefollowinggeneralorderintypenames:
Fordoorsandwindows: <width>x<height>
Forcaseworkandfurniture: <width>x<depth>x<height>
Forotherelementtypes:<width>x<depth>
Version2.1RMCSG—33
Forunit‐specificfamilies:
Forimperialfamilytypes:
Inmostcases,sizeshouldbeexpressedininches.Useonlyoneoftheconventionsbelowwithinafamilyand
forrelatedfamilies.
Forfamilieswithmostsizesunder10’: XX”xYY”
Forfamilieswithmostsizesover10’: XX’–YY”xAA’–BB”
Formetricfamilytypes:
Foralltypesinmetricfamilies: XXXXxYYYYmm(orlocalmetricunitindicator)
Forfamiliesthatfeaturenominalsizesorindustry‐standardterms:
Intypenames,dropthedimensionindicators(“,’,ormm)and/oruseindustry‐standardnamingconventions.
Brick(industry‐standardnaming): Common,Norman,CSR,MetricModular
Lumber(nominalsizes): 2x4
Structure(industry‐standardnaming): W12x204
EXAMPLES
TYPESFORANIMPERIALWINDOW:
16”x24”
16”x48”
24”x24”
24”x48”
24”x72”
36”x24”
36”x48”
36”x72”
RMCSG—34 Version2.1
2.5CATEGORYANDSUBCATEGORYSTANDARDSANDUSAGE
Allfamilies,includinggenericfamilies,mustbeassignedtoappropriatecategoriesandsubcategories.Whena
familyiscreated,itisassignedacategory.Thecategorydefinesitstoplevelofidentification(forexample,Door,
Window,orCasework)withintheprojectenvironment.Whenthefamilyisusedinaproject,thefamilycanbe
locatedintheProjectBrowserunderitscategory,andelementscreatedbythefamilytypeswillschedulebyits
category.Thelineweight,linecolor,linepattern,andmaterialassignmentofthefamilygeometrycanalsobe
assignedtobycategory.
Todisplaydifferentlineweights,linecolors,linepatterns,andmaterialassignmentsfordifferentgeometric
componentsofthefamily(forexample,theframe,sash,mullions,andglassthatcompriseawindow),the
componentscanbeassignedtosubcategorieswithinthefamilycategory.
CategoriesarepredefinedinRevitsoftwareandcannotbecreatedorchangedbytheuser.Subcategoriesare
predefinedinsomefamilies,butothersubcategoriescanbecreatedinfamiliesasneeded.
ADDINGSUBCATEGORIESTOMODELFAMILIES
Ifyouneedtoaddsubcategoriesinyourfamilies,usethestepsbelowtoensurethatyoursubcategoriesadhereto
Autodeskstandards:
1. OpenthelistofAutodesk‐approvedsubcategories,RevitMasterSubcategoryList.xls(includedinthe
downloadpackage).
2. Selecttheworkbookthatcorrespondstothecategoryofthefamilythatyouarecreating.
Thefirsttablecontainsanypredefinedsubcategoriesthatareestablishedbythefamilytemplate.The
secondtablelistsadditionalsubcategoriesthatyoucanuse.
Version2.1RMCSG—35
3. Determineifanyoftheadditionalsubcategoriesfityourneeds.
4. Ifthelistdoesnotcontainthesubcategoriesthatyouneed,createnewsubcategoriesusingthenaming
conventionsinthenextsection.
5. SubmityoursubcategoriestotheAutodeskSeekteamforapproval.Aftertheyareapproved,the
subcategorieswillbeaddedtothemasterlist.
SUBCATEGORYNAMINGCONVENTIONS
• Createuniquenamesforeachsubcategory.
• Usenaturallanguagetonamethesubcategory.
Thesubcategorynameshoulddescribehowthesubcategoryisidentifiedintherealworld(i.e.,in
catalogs,bymanufacturer,etc.)
• Donotincludethefamilycategoryinthesubcategory.
• Keepsubcategorynamesasshortaspossible.
• Capitalizetheleadinglettersofthewordsthatformthesubcategoryname.
RMCSG—36 Version2.1
2.6AUTODESKAPPROVEDPARAMETERUSAGE
Familiescontainparametersthatnotonlycreatethefamilygeometry,butidentifyorclassifytheelementsthatare
createdbythefamily.Allfamilieshavepredefinedparametersthatyouassignvaluesordatato,butyoucanadd
parametersthatarenotpredefinedinRevitsoftware(thatarenotsystemparameters).
IMPORTANT:Ifyouwanttodisplaythenamesandvaluesofcustomparametersinaschedule,theymustbe
definedassharedparametersinatextfilethatisindependentoffamilyandprojectfiles.
REQUIREMENT:Topromoteconsistencyinmodelcontent(particularlyformanufacturercontentthatissharedon
AutodeskSeek),useparametersastheyareexplicitlydefined(includingtheGUID)intheapprovedshared
parametersfile.Ifarequiredparameterisnotinthefile,addittoyourcontentasnecessary.Itisalso
recommendedtoincludethesharedparameterfilecontainingtheadditionalparameterswithyourcontent
package.Whencreatingcustomparameters,referto2.7ParameterNamingConventions.
Refertothemastersharedparametersfile(RevitMasterSharedParameters.txt)forthelistofAutodesk‐approved
sharedparameters.Thisfilecontainsmostofthesharedparametersthatyouwillneedtoaddtoyourfamilies.A
spreadsheet(RevitMasterParameterList.xls)thatliststheseparametersbyfamilycategory,alongwithapplicable
predefinedsystemparametersisalsoavailableforyourreference.
WindowscategoryintheRevitMasterParameterList
Version2.1RMCSG—37
ADDINGMANUFACTURERDATATOFAMILIES
IdentityDataparametersinfamiliescanincludemanufacturerdata,includinginformationsuchasthemodel,
description,assemblycode,cost,andmanufacturerURL.Whenelementsarecreatedwiththefamilyinaproject,
theparametersandassociatedvaluescanbeincludedinschedules.
Identitydataparametersforawindowthatincludevaluesformanufacturerdata
ParameterNameDescription TypeofParameter
ManufacturerManufacturername System
ModelModelnameornumber System
ProductPageURLURLtoproductpage Shared(seesharedparameterlist)
ProductDocumentationLinkURLtoproductdocumentation Shared(seesharedparameterlist)
URLURLtomanufactureswebsite System
CSIOMNICLASSTABLE49
FamilyparameterscanreferenceOmniClassTable49properties,althoughRevitparametersandOmniClass
propertiesmaynotmatchperfectly.SeeRevitMasterParameterList.xlstoviewthemappings.
RMCSG—38 Version2.1
CSICLASSIFICATIONCODES
OnAutodeskSeek,contentfamiliescanbelocatedbytheappropriateCSI(ConstructionSpecificationsInstitute)
code.Forbestresults,includeinformationin3formatstandards:
• MasterFormat2004–50divisionsthatstandardizeinformationinconstructionprojectmanuals.
• UniFormatII(AssemblyCode)–Organizingpreliminaryconstructioninformationbasedonitssystemsand
assemblies.Usedforpreliminaryprojectdescriptions,performancespecifyingandcostestimation.
• OmniClass1.0–Consistsof15tables,eachrepresentingadifferentfacetofconstructioninformation.
Formoreinformationonthestandards,refertotheCSIWebsite,http://www.csinet.org/s_csi/index.asp.
ASSIGNINGTHEMASTERFORMATANDUNIFORMATCLASSIFICATIONINREVIT
TheMasterFormat2004andUniFormat(AssemblyCode)shouldbeassignedtoeachfamilytype.
1. OpentheFamilyTypesdialogforthefamily.
2. UnderIdentityData,forKeynote,entertheMasterFormatcodeappropriateforthefamilycontent.Refer
totheCSIWebSiteforalistofclassificationcodes.
3. UnderIdentityData,forAssemblyCode,clickintheValuefield,andclickthebrowsebuttontoselectthe
appropriateAssemblyCodefromthedialog.
4. Repeattheprocedureforeachtypeinthefamily.
Version2.1RMCSG—39
ASSIGNINGTHEOMNICLASSCLASSIFICATIONINREVIT(REVIT2010ANDLATER)
TheOmniClass1.0codeisassignedtothefamily.Youdonotneedtoassignittoeachfamilytype.
5. InRevit,OpentheFamilyCategoryandParametersdialog.
6. UnderFamilyParameters,forOmniClassNumber,clickinthefield,andclickthebrowsebuttontoselect
theappropriateOmniClasscodefromthedialog.
NoticethattheOmniClassTitlevalueisaddedautomatically.
RMCSG—40 Version2.1
2.7PARAMETERNAMINGCONVENTIONS
ConsistentparameternamingenableseasierandmorecomprehensiveparametricsearchinginAutodeskSeek.
Createparametersonlywhenvariationcreatesmeaningfullydifferentiatedtypesthatrepresentreal‐world
possibilities.
GUIDELINES
• Usestandardapprovedparameternameswhenavailable.
• Keepparameternamesasshortaspossible.
• Avoidabbreviationandtruncation,whenpossible.
• Use‘titlecasing’(aswiththetitleofabook)forparameternames,astheyarecasesensitive(e.g.,
CoefficientofPerformance;PointofShipment;HighandLowPressureGasConnectionDiameter).
• Parametersmustdisplayindialogs.
• DonotchangelabelnamesprovidedbytheRevitfamilytemplates.
• Parameternamesthatyoureusetocreateequalitiesshouldbecarefullycheckedfornamecoherence.
• Usethemostcommondescriptorforagroupofparametersasthefirstpartofthenamesothatthe
parameterssortlogically(e.g.,FilterFaceArea;FilterEfficiency).
• Parametersforsubsequentitemsshouldincludeanumberinthenamebeforethefinalpartofthe
description,butdonotincludeanumberinthenameforthefirstitem(e.g.,ActualHotGasFlow;Actual
HotGas2Flow).
• Avoidusingsymbolsinparameternames,including:+‐/\*()“‘<>|^${}[].
• Donotincludeunitsinthenameofaparameter(e.g.,SupplyAirFlowCFM).
• UsingthetermsActualorDesign:
o Actual–describestheactualvaluethesystemdefinitionrequires.“Actual”parametersarelinked
toconnectorsandareoftenusedforparametersthatdefineflowrates,forexample,Actual
SupplyAirFlow;ActualChilledWaterFlow.
o Design–describeswhattheproductisdesignedtodo,forexample,DesignVentilationAirFlow;
DesignReturnAirFlow.
• NameYes/NoparameterssotheyimplythattheyreturnaYes/Novalue,forexample:
o HasHandle
o IsEnergyEfficient
o ShowHoods
Version2.1RMCSG—41
FORMAT
<Function/Object><Typeofmeasurement/Descriptor>
<Function/Object>requirediftheparameterappliestoasub‐componentratherthan
theentirefamily.
<Typeofmeasurement/Descriptor>requiredforallparameterstodescribethevaluebeingpassed.
EXAMPLES
PARAMETERSTHATAPPLYTOTHEENTIREFAMILY
Format:<Typeofmeasurement/Descriptor>
Casementwindow:
• Height
• DefaultSillHeight
• Width
• WindowInset
• RoughWidth
• RoughHeight
Engineeringequipment:
• ActualHeaterGasFlow
• TotalHeatingCapacity
• FullLoadCurrent
• CompressorType
PARAMETERSTHATDESCRIBEAMEASUREMENTVALUEOFASUB‐COMPONENT:
Format:<Function/Object><TypeofMeasurement/Descriptor>
• HeatPumpCoilFaceArea
• HeatPumpCoilFaceVelocity
• ExhaustFanBladeSpeed
• ExhaustFanDrive
• ExhaustFanMotorSpeed
RMCSG—42 Version2.1
PARAMETERSTHATDESCRIBETHELINEARDIMENSIONOFASUB‐COMPONENT(CONNECTOR)
Format:<Function/Object>Connection<TypeofMeasurement/Descriptor>
• HotGasBypass2ConnectionDiameter
• CondenserWaterConnectionDiameter
• SupplyAirConnectionWidth
• SupplyAirConnectionHeight
Version2.1RMCSG—43
2.8MATERIALNAMINGCONVENTIONS
Finishmaterialnamingconventionsorganizethematerialbymanufacturer,andgeneraldescriptiontomore
specificdescription.Dependingonthetypeofmaterial,afinishmaterialnamemayincludeacolor,code,finish
type,oridentificationnumber.
GUIDELINES
• Finishnamesshouldindicatethekeydifferencesbetweenmaterials(manufacturer,type,color,
finish)and,whenapplicable,reflectstandardsizes.
Insomecases,youmaybasenamesonsizedifference,butusecommontermsratherthannumbers.
• Metricfinishnamesshouldreflectthelocalunitstandard,unlessthematerialsareintendedtobe
generic.
• Keepfinishnamesasshortaspossible.
RECOMMENDATION:Tooptimizethefilesizeforfamilieswithalargenumberofavailablematerials,provideonly
themostcommonmaterialsinthefamily,andprovidetheremainingmaterialsinaseparatefinishlibrary.Seethe
Finishesparttypeguideformoreinformation.
FORMATFORINDIVIDUALFINISHMATERIALS(STOREDINSIDEPROJECTS)
<FinishType>‐<Manufacturer>‐<Code>‐<Descriptor>
EXAMPLES
Paint‐AcmePaint‐AC440‐VintageBrownMatte
Glass‐AcmeGlazing‐Series1205–Clear
Aluminum‐AcmeMetal‐AC120‐Anodized(Clear)
Fabric‐AcmeFabrics‐ACF820‐Houndstooth‐Black/White
Stain‐AcmeWindows‐NaturalWoodFinish
RMCSG—44 Version2.1
FORMATFORINDIVIDUALFINISHMATERIALSUSINGANEXTERNALIMAGEFILE
Materialsrequiringexternalimages,bumpmapsandcutoutshouldbestoredinalocationthatcanbesharedby
multipleRevitProductinstalls.
ForWindowsXP:
C:\DocumentsandSettings\AllUsers\ApplicationData\RevitManufacturerLibrary\Materials\<MFG>
ForWindowsVistaandWindows7:
C:\ProgramData\AllUsers\ApplicationData\RevitManufacturerLibrary\Materials\<MFG>
GUIDELINES:
• Createuniquenamesforeachuniquematerialimage.
• Capitalizetheleadinglettersineachportionofthefamilyname.
• Donotusespacesbetweenwordsinfilenames.Toseparatewordswithinasyntaxelement(e.g.,
ManufacturerorDescriptor),usetheunderscorecharacter(_).
• Acceptablefileformatsformaterialimagesinclude:bmp,jpg,jpegandpng.
• ProvideareadmetodescribewheretheimagefilesmustbelocatedandhowtomapRevittothe“Revit
ManufacturerLibrary“folderintheRenderingOptionsdialog.
FORMATFORINDIVIDUALMATERIALSIMAGES(STOREDOUTSIDEOFREVIT)
MaterialImage:
<FinishType>‐<Manufacturer>‐<Code>‐<Descriptor>+fileextension
Bumpmaps:
<FinishType>‐<Manufacturer>‐<Code>‐<Descriptor>‐bump+fileextension
Cutouts:
<FinishType>‐<Manufacturer>‐<Code>‐<Descriptor>‐cutout+fileextension
EXAMPLES
ImageFile:
Paint‐Acme_Paint‐AC_440‐Vintage_Brown_Matte.jpg
Stain‐Acme_Windows‐Natural_Wood_Finish.jpg
BumpImageFile:
‐bump.jpg
Stain‐Acme_Windows‐Natural_Wood_Finish‐bump.jpg
Cut‐outs/Perforations:
‐cutout.jpg
Aluminum‐Acme_Fencing‐AC120‐Anodized‐cutout.jpg
Version2.1RMCSG—45
2.9PREVIEWIMAGESTANDARDS
Afamilypreviewimageisareducedthumbnailimageofa2Dor3Dfamilyviewthatgraphicallyidentifiesafamily
beforeitisdownloadedoropened.Previewimagesdisplayin:
• ThumbnailsviewinMicrosoft®WindowsExplorer
• AutodeskSeeksearchresults
• thePreviewwindowinRevitOpenandLoadFamilydialogswhenafamilyisselected
BycreatingpreviewimagesthatadheretoAutodeskstandards,userscanviewconsistentpreviewsacrossfamilies,
ensuringaconsistentuserexperiencebothinAutodeskSeekandinRevitsoftware.
FamilypreviewimagesinAutodeskSeek,WindowsExplorer,andRevitOpenFamilydialogs
RMCSG—46 Version2.1
CREATINGAUTODESKSTANDARDFAMILYPREVIEWIMAGES
Tocreateapreviewimage,beginbycreatingafamilyviewtouseexclusivelyforthepreviewimage.Althoughyou
cansaveanyfamilyviewasthepreviewimageview,thebestpracticeistocreateaviewthatcanbesetto
consistentlydisplayasisrequiredforthepreviewimage.
Afteryoucreatetheview,setAutodeskstandardgraphiccontrolsinthepreviewimageviewtoensurevisual
consistencywiththepreviewimagesofotherRevitfamilies.Differentgraphicstandardsexistforthefollowing
typesoffamilypreviewimages:
• Detailcomponentandannotationfamilies
• Hostedmodelcomponentfamilies
• Non‐hostedmodelcomponentfamilies
NOTE:Althoughannotationfamiliesarenotcoveredinthisguide,similarstandardsforannotationpreview
imagesexist.
IMPORTANT:Whenmodificationstothepreviewimageviewarecomplete,savetheviewandsetthefamilytouse
thecurrentviewasthepreviewimage.Eachtimeyousaveandclosethefamily,youmustensurethatthepreview
imageviewistheactive(open)viewsoitwilldisplayasthepreviewimage.
CREATINGADETAILCOMPONENTPREVIEWIMAGE
Foraneasilyidentifiabledetailcomponentpreview,setthepreviewimagetodisplaythe2Dviewthatfeatures
onlythecomponentlineworkandfilledregions.
Turnoffvisibilityofdimensionsandreferenceplanes/linesintheview,astheseelementsmayobscurecomponent
geometryiftheydisplay.
Version2.1RMCSG—47
TOCREATEADETAILCOMPONENTPREVIEWIMAGE:
Createaviewtouseasthefamilypreviewimage
1. Ifnecessary,openthedetailcomponentfamilyforwhichyouwanttocreateapreviewimage.
Turnoffvisibilityofdimensionsandreferenceplanes/lines
2. ClickViewmenu→Visibility/Graphics.
3. IntheVisibility/GraphicOverridesdialog,clicktheAnnotationCategoriestab.
4. UnderVisibility,clearDimensions,Levels,ReferenceLines,andReferencePlanes.
5. ClickOK.
SetstandardviewcontrolsinthePreviewview
6. OntheViewControlBar:
• Clickthecurrentviewscale,anddependingonthefamilyunits,click11/2”=1’‐0”or1:5.
• ClickDetailLevel,andclickFine.
• ClickModelGraphicsStyle,andclickWireframe.
7. ClickSave.
RMCSG—48 Version2.1
CREATINGAHOSTEDORNON‐HOSTEDMODELCOMPONENTPREVIEWIMAGE
Dependingonthetypeofmodelcomponentthatapreviewimagedepicts,itmaydisplaya2Dorisometricview.If
thepreviewimageiscreatedforahostedfamily,hostelementsmayormaynotdisplayinthepreview.
Thistopicpresentsgeneralguidelinesforcreatingpreviewimages.Foradditionalguidelines,refertothecategory‐
specificdocumentationformodelcomponentpreviewimages.
Createpreviewimageviewsaccordingtothefollowinggeneralguidelines:
• Doorandwindowpreviewimagesshoulddisplaya2Dfrontexteriorelevationviewofthefeatured
component.Visibilityofthehostelement(usuallyawall)shouldbeturnedofftobetterdisplaythe
windowordoor.
Thispreviewimageofawindowfamilyisagoodexamplebecauseithasanappropriatelevelofdetail,isa2D
frontview,andisrepresentativeofthecontent:
Thispreviewimageofawindowfamilyisapoorexamplebecauseitisa3Dviewthatincludesthehostobject
(wall)whichmakesthewindowdifficulttosee:
• Othermodelcomponentpreviews,suchasfurnitureorcasework,shoulddisplayinasoutheastisometric
view.
Version2.1RMCSG—49
• Host‐basedfamiliesotherthandoorsandwindows,suchaslightfixtures,mayincludehostelements
(wallsorceilings)inthepreviewimage.
Turnoffvisibilityofdimensionsandreferenceplanes/linesintheview,astheseelementsmayobscure
componentgeometryiftheydisplay.
TOCREATEAMODELCOMPONENTPREVIEWIMAGE:
Createaviewtouseasthepreviewimage
1. Ifnecessary,openthefamilyforwhichyouwanttocreateapreviewimage.
2. IntheProjectBrowser,selectaviewofthefamilythatyouwanttouse:
• Foradoororwindowfamily,selectanelevationview(preferablyfront).
• Forothermodelcomponentfamilies,selecta3Dview.
3. Right‐clicktheviewname,andclickDuplicateView→Duplicate.
4. Renametheduplicateview:
• IntheProjectBrowser,right‐clicktheviewname,andclickRename.
• TypePreviewandclickOK.
• ClickNotoretainthenamesofcorrespondingviewsandlevels.
5. Ifnecessary,opentheview.
Setastandardpreviewimagevieworientation
6. Dependingonthetypeofcomponentthatyouarecreating,setthevieworientation:
• Foradoororwindowfamilyinanelevationview,ontheViewCube,click .
• Forotherfamiliesthatdisplayina3Dview,ontheViewCube,click tosetasoutheast
orientation,right‐click,andclickSetCurrentViewasHome.
Turnoffvisibilityofdimensionsandreferenceplanes/linesandifnecessary,setthehostvisibility
7. ClickViewmenu→Visibility/Graphics.
8. IntheVisibility/GraphicOverridesdialog,clicktheAnnotationCategoriestab.
9. UnderVisibility,clearDimensions,Levels,ReferenceLines,andReferencePlanes.
10. Ifyouarecreatingapreviewforahost‐basedfamily,setthehostvisibility:
• Forfamilypreviewsinwhichthehostshouldnotdisplay,suchasdoorsandwindows,clearall
hostcategories.
RMCSG—50 Version2.1
• Forfamilypreviewsinwhichthehostshoulddisplay,selectallhostcategories.
11. ClickOK.
SetstandardviewcontrolsinthePreviewview
12. OntheViewControlBar:
• Clickthecurrentviewscale,anddependingonthefamilyunits,click11/2”=1’‐0”or1:5.
• ClickDetailLevel,andclickFine.
• ClickModelGraphicsStyle,andclickShadingwithEdges.
Setthepreviewimagetodisplaythecurrentview
13. ClickFilemenu→SaveAs.
14. IntheSaveAsdialog,inthelower‐rightcorner,clickOptions.
15. IntheFileSaveOptionsdialog,underPreview,forSource,select“3DView:Preview”,thenselect
“Regenerateifview/sheetisnotup‐to‐date”.
IMPORTANT:Thissettingdisplaystheselectedviewasthepreviewimage.Itisalsorecommendedthatthe
activeviewwhenyousavethefileisthesameastheselectedpreviewview.
TIP:SelecttheCompactFileoptiontohelpreducethefilesize.
16. ClickOK.
17. ClickSave.
Version2.1RMCSG—51
2.10TYPECATALOGSTANDARDSANDUSAGE
Atypecatalogiscomma‐delimitedTXTfilethat,whenplacedinthesamedirectoryasafamily,displaysalistof
familytypesbeforethefamilyisloadedintoaproject.Youcanselectandloadonlythefamilytypesthatthe
currentprojectrequires,avoidinganunnecessaryincreaseinprojectsizefromunusedtypesandalonglistoftypes
intheTypeSelector.Thetypecatalogalsoprovidesanexternalmeansofeditingthefamily,asyoucanremoveand
addparametersandtypesinthecatalogfile(TXT).
TYPECATALOGSTANDARDS
Usethefollowingstandardswhencreatingtypecatalogs:
• Useanytexteditortocreatetypecatalogs.
• Createtypecatalogsforfamiliesthatcontainsixormoretypes.
• Nameatypecatalogfile(.txt)withthesamenameasthefamilyfile(.rfa)thatitsupports.
• Ensurethatparametersintypecatalogsaretestloadedbythefamilyforwhichyoucreatethetype
catalog.Iftheparametersarenotused,thefamilywillnotload.
IMPORTANT:InTypeCatalogs,inordertoincludefeetandinchmarksinthetypename,youmustincludea“mark
afterthefootorinchsymbol.
Todisplaythetypename…Inthetypecatalog,enter…
48”x60”48””x60””
3’
–
6”3’”
–
6””
Forinformationoncreatingatypecatalog,see“CreatingTypeCatalogs”intheRevitHelpandFamiliesGuide.
UNIT‐SPECIFICFAMILY
Atypecatalog(TXTfile)foradoorfamily
RMCSG—52 Version2.1
Dialogdisplayedbythetypecatalogwhenthedoorfamilyisloaded
STRUCTURALCONTENT–INDUSTRY‐STANDARDNAMING
Atypecatalog(TXTfile)forasteeljoistfamily
Dialogdisplayedbythetypecatalogwhenthesteeljoistfamilyisloaded
Version2.1RMCSG—53
2.11MATERIALAPPLICATIONINMODELFAMILIES
Materialscanbeappliedtofamiliestodepictthereal‐worlddisplayofelementscreatedwiththefamilyinshaded
andrenderedviews.
IMPORTANT:Whenapplyingmaterialstoafamily,rememberthatmaterialsincreasethefamilysize,whichin
turndecreasesitsperformancewhenitisloadedandusedinprojects.
Dependingonhowyouapplymaterialstoafamily’sgeometry,youcancontroltheuser’sabilitytomodifythe
materialsofelementsthattheycreatewiththefamily.Usetheseguidelinestoapplymaterialstofamilygeometry:
Ifyouwantto…Then…
usematerialsthatwillnotneedtobechangedApplythematerialdirectlytothefamilygeometryby
assigningittotheMaterialparameter(Option1).
changethematerialforthefamilycategory
and/orforsubsetsofgeometriccomponentsin
thefamily
Applyamaterialtothefamilycategory.
Createsubcategories,assignmaterialstoeach
subcategory,andassignsubcategoriestogeometry
(Option2).
changethematerialforageometriccomponentin
afamilybyinstanceortype
Createaninstanceortypematerialparameterand
assignittotheappropriatefamilygeometry(Option3).
NOTE:Thisisthemostflexibleandpreferredmethodof
materialassignment.
Ifpossible,usethematerialsthatareavailableintheRevitsoftwarewhenassigningmaterialstofamilygeometry.
Ifyouneedtocreateamaterial,makesurethatthematerialnameconformstothenamingconventionsdescribed
intheMaterialNamingConventionstopic.
OPTION1–APPLYMATERIALSWITHTHEMATERIALPARAMETER
YoucanapplymaterialsdirectlytosomeorallofthefamilygeometryintheFamilyEditor.Eachpieceoffamily
geometryhasadefaultMaterialparametertowhichyoucanassignmaterials.
USETHISMETHODWHEN:
Thematerialofthefamilygeometryisunlikelytochange,suchasforamanufacturedcomponentthatissupplied
withasinglestandardmaterial.
RMCSG—54 Version2.1
RESULT:
Whenyoucreateelementsinaprojectwiththefamily,youcannot:
• changetheelementmaterialswithouteditingthefamily
• changethematerialforinstancesortypesofthefamily
• changethematerialsbyassigningamaterialtotheelementcategory
OPTION2–APPLYMATERIALSTOFAMILYGEOMETRYBYCATEGORYANDSUBCATEGORY
Youcanapplymaterialstoallorselectpiecesoffamilygeometrybysubcategory.Subcategoriesarecategoriesthat
existwithinthefamilycategory.Youcanassigndifferentpiecesoffamilygeometrytoeachsubcategory,andthen
applyadifferentmaterialtoeachsubcategory.Toapplymaterialtogeometrythatisnotassignedtoa
subcategory,youcanapplymaterialsbythefamilycategory.
USETHISMETHODWHEN:
Youwanttobeabletoapplydifferentmaterialstodifferentfamilycomponentsbycategoryorsubcategory.
RESULT:
Whenyoucreateanelementinaprojectwiththefamily,
• youcanchangethematerialsassignedtoeachsubcategoryorcategory.
OPTION3–APPLYMATERIALSWITHCUSTOMINSTANCEORTYPEMATERIALPARAMETERS
Youcancreateandassignacustominstanceortypematerialparametertofamilygeometry.
BESTPRACTICE:Thisisthemostflexiblemethodofmaterialassignmentthatyoucanprovidetheuser.
USETHISMETHODWHENYOUWANT:
• toallowtheusertochangefamilymaterialsbyinstanceorbytype.
• bysettingthematerialparameterto<bycategory>thisoptioncanalsoallowtheelementstobeupdated
bysubcategoryorcategory.
RESULT:
Whenyoucreateanelementwiththefamilyinaproject,theparametergivesyoutheoptiontochangeamaterial
foraninstanceoftheelementorforeachtypeofelementthatyoucreate.
Version2.1RMCSG—55
EXAMPLE:ASSIGNINGMATERIALSTOATABLEFAMILY
Inthisexample,acombinationofmaterialoptionsisusedtoapplymaterialsinasimpletablefamily.
Materialassigneddirectlytogeometry(Option1):Thehardwarewillnotneedtochangewhenthisfamilyisused
inaproject,soamaterialisapplieddirectlytotheknobforthetabledrawer.IntheElementPropertiesdialogfor
theknobgeometry,underMaterialsandFinishes,theMaterialparametervalueissettoMetal–Chrome.
Materialsassignedwithtypematerialparameters(Option3):Twotypematerialparametersarecreatedinthe
tablefamily:
• LegMaterial–assignedtoablackpaintfinish
• TopMaterial–assignedto<ByCategory>
RMCSG—56 Version2.1
Thematerialforthetablelegscanbechangedasrequiredbytheuserintheproject.InElementProperties,the
MaterialpropertyforthetablelegsgeometryisassociatedwiththeLegMaterialfamilyparameter.Thematerial
forthelegsthereforeisdeterminedbythematerialassignedtotheLegMaterialparameterintheFamilyTypes
dialog.
Thematerialforthetabletopcanbechangedbytheuserasrequiredtomatchotherfurniturecomponentsinthe
project.TheMaterialpropertyforthetabletopgeometryisassociatedwiththeTopMaterialfamilyparameter.
ThematerialforthetabletopisthereforedeterminedbythematerialassignedtotheFurniturecategoryinthe
ObjectStylesdialog(inthisexample,Walnut).
Byusingamaterialfamilyparameterandassigningthevalueof<ByCategory>toit,yougivetheusertheflexibility
ofusingthedefaultmaterialappliedtothefamilycategoryorchangingtheparametervaluetoamaterialoftheir
choice.
Version2.1RMCSG—57
2.12BESTPRACTICESFORADDINGCONNECTORSINREVITMEPFAMILIES
InRevitMEP,theconnectorconnectsthesinglefamilycomponentwithothercomponentstocreateMEP
systems.Withoutaconnector,anRMEfamilywouldjustbeastaticplaceholder.
InRevitMEP,thereare3kindsofconnectors:
• ElectricalConnector
• DuctConnector
• PipeConnector
ADDINGACONNECTOR
1. Clickthetoolfortheconnectoryouwishtoadd(ElectricalConnector,DuctConnector,orPipe
Connector).
2. Clicktoplacetheconnectorinthedrawingarea.
RMEprovidestwowaystoplacetheconnector,placingitonafaceoronaworkplane.Ifyouselectthe
PlaceonFaceoption,theconnectorisautomaticallyaddedtothecenterofthefaceofthegeometryand
moveswiththeface.Ifthegeometryisdeleted,theconnectorisalsodeleted.
BESTPRACTICE:Placeconnectorsonafaceratherthanonaworkplane.
RMCSG—58 Version2.1
SYSTEMTYPES
Thefollowingtableprovidesanoverviewoftheapplicationscenarioforeachsystemtype.
SystemTypeApplicationScenario Example
PipeConnector
HydronicSupplyFamiliesinclosedwatercirculationsystems Boiler,Chiller,
CoolingTower
HydronicReturn
SanitaryPlumbingfixtures
Lavatories,
WaterClosets.
DomesticHotWater
DomesticColdWater
FireProtectionWetThethreesystemsarematchingthethree
sprinklersystems,sprinkler‐wet,sprinkler‐dry,
sprinkler‐pre‐action.
Sprinkler,
DryValve
FireProtectionDry
FireProtectionPre‐Action
FireProtectionOtherOtherfireprotectionsystemsexceptthethree
above,suchasstandpipe
Cabinet,Hose
Connection
FittingPipeFittingsElbow,Tee
Globa
l
Familiesthatwillbeinmultiplesystems Pump,Valve
OtherFamiliesingas,refrigerant systems,
Placeholderforpipesystemsnotincluded
Gasconnectorof
Waterheater
Unsupported StromDrainage ,SanitaryVentilation
DuctConnector
SupplyAirHVACAirdeliverysystems AirConditioner,
DustCollector
ReturnAir
ExhaustAir
OtherAirPlaceholderforairsystemsnotincluded
FittingDuctFittings Elbow,Tee
Global Familiesthatwillbeinmultiplesystems Fan
Unsupported FreshAir
ElectricalConnector
DataAutomaticallyormanuallycontrolthe
transmitting,receiveorsendingofdata/voice
signals.
DataOutlet
Power
–
Balance
d
Equipment,deviceorfixtureoperatesin
powersupply/distributionsystems.
Generator
Power
–
Unbalance
d
PanelBoard
TelephoneTelecommunicationdevicesusedtotransmit
andreceivesound.
Telephoneoutlet
SecurityBearmedanddetectsecurity/accessproblem SmokeDetector
FireAlarmAlarm‐initiatingdevicesoperatetocontrol
alarmsignals
WaterFlow
Indicator
NurseCal
l
Keycomponentinaddressingpatientcare
needs.
CallPoint
ControlsNormallyusedforremotecontrolinsome
specialcircumstances
ControlValve
CommunicationDevicesincommunicationsysteminbuilding,
usedtotransmitting,receiveorsend
communicationsignals
Speaker
Version2.1RMCSG—59
CONNECTORDIRECTION
Forduct/pipeconnectors,anarrow,perpendiculartothesurface,displays.Thedirectionthatthearrowispointing
isalsothedirectioninwhichtheconnectingduct/pipewillbedrawn.Asthepictureshows,verticalductcanbe
drawnfromanupconnectorinanairterminal.
NOTE:Thearrowdoesnotrepresenttheflowdirection.
PRIMARYCONNECTOR
Bydefault,thefirstconnectorineachdomainisassignedastheprimaryconnector.Inthefollowingimage,youcan
easilyidentifytheprimaryconnector(connector1)bythecrosssymbol.TheRe‐assignPrimarytoolallowsyouto
reassigntheprimaryconnector,asrequired.
Theprimaryconnectorofpipeandductfittingsshouldbelocatedatcoordinates(‐1,0,0).Inthefollowingimage
oftheplanviewofaP‐Trap,connector1istheprimaryconnector.
RMCSG—60 Version2.1
Forotherfamilies,thelocationoftheprimaryconnectorisnotimportant.
LINKINGCONNECTOR
Whentherearemorethanonepipe/ductconnectors,thereisachoiceforlinkingconnectors.
• Linkedconnectorsonlyhaveaneffectwhenthesystemtypeissettoglobalforequipmentorfitting.
• Linkingconnectorsonequipmentmakesitpossibletopropagateengineeringdata,allowingyoutouse
equipmentasaninlinecomponentinasystem.
• Linkingconnectorsonfittingsshouldincludetheprimaryconnector.
Version2.1RMCSG—61
CONNECTORMAPPING
EditElementPropertiesfortheconnectortodefineparametersfortheconnector.
Forpartparameters,clickingabrowsebuttondisplaysadialogthatmakesiteasytomapconnectorparametersto
familyparameterswiththesameunits.Connectormappingmakestheconnectorparametricwiththefamily.
RMCSG—62 Version2.1
CONNECTORDESCRIPTIONS
Inthefollowingexampleofcomplexequipment,itwouldbedifficulttodeterminethefunctionofeachconnector.
Tomakeiteasiertoidentifythefunctionofconnectorsinthefamily,addconnectordescriptions.These
descriptionsdisplayintheSelectConnectordialog.Inthefollowingimage,descriptionsareunderlinedinredfor
illustrationpurposes.
Version2.1RMCSG—63
SECTION3:
TESTINGGUIDELINES
ToensurethequalityofRevitfamilycontent,thoroughlytestfamiliesbeforeusingtheminproductionorsharing
themonAutodeskSeek.Testfamilieswiththeguidelinesinthissectionto:
• verifythatnewfamilycontentmeetsAutodeskstandards
• ensurefamilyparametricrelationships
• ensureaconsistentuserexperience
Twosetsoftestingguidelinesareincluded:generalguidelinesandfamily‐specificguidelines:
• Usethegeneralfamilytestingguidelinestotestallfamilies.
• Usethefamily‐specifictestingguidelinestotestspecificcriteriaperfamilytype.
Inaddition,category‐specifictestingguidelinesareavailableforsomefamilycategories.Thesedocumentscontain
specifictestingguidelinesthatyoushouldusewhenavailable.Beforetestingafamily,determinewhethera
category‐specificdocumenthasbeenpublishedforthecategoryofthefamilythatyouaretesting.
RMCSG—64 Version2.1
3.1GENERALFAMILYTESTINGGUIDELINES
Performgeneraltestingonafamilywhenitis:
• openintheFamilyEditor
• loadedintoaproject
Usethecriteriainthechecklistsbelowtotestfamiliesineachoftheaboveenvironments.
Whentestingfamiliesinprojects,itisstronglyrecommendedthatyou:
• Testfamiliesinprojectscreatedwiththegenericmetricandimperialtestingtemplateprojectsthatwere
includedinthedownloadpackage.
• Testfamiliesinprojectsthatmatchthedesignintentofthefamily.
Forexample,testawindowfamilythatisdesignedtobeplacedinalargecommercialbuildinginalarge
commercialproject.
• ContentthatisdesignedtoworkinmorethanoneRevitdisciplinemustbetestedinallapplicable
disciplines.Forexample,foralightingfixture,testtheconnectorsinRevitMEP,andverifythatthefixture
castslightasexpectedwhenrenderinginRevitArchitecture.
TIP:Forlargecontentcreationprojects,itisrecommendedthat“spotchecking”orrandomtestingof10%ofthe
contentbeperformedbyatesterwhoisnotthecontentcreator.
FAMILYEDITORTESTINGCRITERIA
R Testallfamilyparameterstoensurethatthegeometryflexes/adjustscorrectlywhenthefamily
parametersaremodified.
R Testallfamilytypes–changethetype,applyit,andinspectthegeometrytoverifythatthedimensions
andrelationshipsaremaintained.
R Inahost‐basedfamily,verifythatthehostflexesasexpected.Changethehostthicknessandensurethat
thefamilygeometryadjustsappropriately.
R VerifythatthefamilypreviewimageisusingthePreviewview.
R Checkallviewstoensurethatthefamilydisplaysappropriatelyindifferentdetaillevelsandwhen
differentModelGraphicsstylesareapplied.
R Testconstraints:
o Testthehandlesontheedgeofthegeometryandmakesurethatallgeometryisconstrainedto
eitherareferenceplaneorareferenceline.
o Testthedimensionparametertomakesurethatthereferenceplaneorlineisbeingadjustedby
theparameterandnottheactualgeometry.
Version2.1RMCSG—65
PROJECTTESTINGCRITERIAFORREVITARCHITECTURE
R Usingatestprojectoroneofthetestingtemplateprojectsavailablefordownload,loadthefamilyina
projectenvironment,andcheckallviewsforanomalies.Ifthefamilyincludesatypecatalog,useittoload
thefamily.
R Inspectthefamilyappearanceinallviews(plan,reflectedceilingplan,elevation,Section,3D)at
alldetaillevels(Coarse,Medium,Fine).
R InspectthefamilyappearanceindifferentModelGraphicsStyles:Wireframe,HiddenLine,
Shading,andShadingwithEdges.
R Testallfamilytypes–changethetype,applyit,andinspectthegeometrytoverifythatthedimensions
andrelationshipsaremaintained.
R Createnewtypesandmodifyallparameters,checkingallviewsforanomalies.
R Modifyallmaterialassignmentstoverifythatmaterialsareassociatedtothegeometrycorrectly.
TIP:Tobetterinspectfamilygeometry,modifyallmaterialtypeparameterstoglass.Also,ifanyofthe
familygeometrydoesnotdisplayasglass,thenamaterialparameterisassignedincorrectly.
R Modifycategoryandsubcategorymaterialstoverifythefamilyisnotusingmaterialtypeparameters.
R Forhostedfamilies:
R Placehostedfamiliesintotheprovidedhostthicknessesandconfirmfamiliesworkinallhosts
appropriatetothefamiliesuse,includingin‐placewallsandmasselements.
R Modifythehostthicknessby25%‐400%,andcheckforunconnectedgeometryand/orplan
representationsthatmaybedisconnectedfromthegeometry.
R Re‐inspectthefamilyappearanceinallviewstoensurethatthegeometrydisplaysasexpected.
R Dimensiontoallreferencesandsnapallreferencestowalls.
R Createatestrendering.
R Testthefollowingcommandsongeometrycreatedinthefamily:
R Copy/Paste
R Rotate
R Mirror
R VerifythatthefamilypreviewimageisusingthePreviewview.
R Testthefamilyinanactualproject,verifyitsperformance,andensurethattheprojectmatchesthe
designintentofthefamily.
RMCSG—66 Version2.1
Version2.1RMCSG—67
3.2FAMILY‐SPECIFICTESTINGGUIDELINES
Dependingonthetypeoffamilybeingtested,theremaybespecificcriteriatotestinadditiontothegeneral
testingthatshouldbeperformedonallfamilies.
Usethistabletodetermineifafamilyrequiresanyspecifictesting:
REVITFAMILY‐SPECIFICTESTING
FamilyTypeExampleTest
Freely‐PlacedFurniture,entourage Testinarelevantprojectcontext.
Forexample,placefurnitureorcaseworkelements
onafloorwithatexturetoensurethatthe
elementsmaskthefloor.
HostedWindow,door Ensurethatthefamilyinteractsproperlywitha
hostandadjuststodifferenthostthicknesses.
Face‐BasedLightfixture Ensurethatthefamilyattachesproperlytofaces
anddoesn’timproperlyembedin,orprojectaway
from,thefaceoftheobjecttowhichitisattached.
DetailComponentDetailcomponent Ensurethatthefamilysnapstoothergeometry
correctlyandthatitmasksanygeometryonwhich
itisplaced.