2009

Table Of Contents

2.4TYPENAMINGCONVENTIONS

Allfamiliesmustincludeonepredefinedtype.Forfamiliesthatcreatereal‐worldobjectsthatareavailablein

standardsizes,predefinedtypesshouldbegenerated.Unlesstheyrepresentnominalsizes,typenamesshould

includeunitsorcapacity,andincludeaunitindicator.

Whennamingafamilytype,usetheformatandrulesbelow:

GUIDELINES

• Donotincludethefamilynameorcategoryinthetypename.

• Typenamesshouldmirroractualusage.

• Typenamesshouldindicatethekeydifferencesbetweentypes(size,count,material)and,when

applicable,reflectstandardsizes.

Insomecases,youmaybasenamesonsizedifference,butusecommontermsratherthannumbers.

• Whentypesarenamedbysize,usedimensionsonly.

Avoidtheuseofcharactersorwords.(h,w,d,orheight,width,depth).

• Typenamesshouldincludeunitsorcapacityandaunitindicator,unlesstheyrepresentnominalsizes.

• Metrictypesshouldreflectthelocalunitstandard,unlessthetypesareintendedtobegeneric.

• Keeptypenamesasshortaspossible.

TypenamesmustdisplayindialogsandintheTypeSelector.

FORMAT

Unlessthereisamarket‐specificreasontodootherwise,usethefollowinggeneralorderintypenames:

Fordoorsandwindows:   <width>x<height>

Forcaseworkandfurniture:   <width>x<depth>x<height>

Forotherelementtypes: <width>x<depth>



Version2.1RMCSG—33

