Sign in or 
Share this
Naming Conventions
Wall Naming
Methods used for wall naming are:
Field Guide
Made By-This field houses the initials of the person that created the wall. The idea is that you know who the point person is for information on reasons of methods for the walls creation.
Use-The Use field gives a general description of what the wall is used for. For example you might put in this field Interior, Exterior or Retaining. A 3 letter abbreviation is recommended:
Thickness-A simple number value for the thickness of the wall.
Finish-This field is for the primary aesthetic finish being used. For Example, Brick, Sheet Metal, Stucco.
Fire Rating-The rating of the wall when exposed to flames.
Example:
An exterior brick wall has been made. With all the layers in it, the thickness of the wall comes out to 11.75 inches thick. The wall was also made by Laura K Lawless. The wall is scheduled as type F4 in the wall schedule. In this case the following name is applied to the wall:
Model Based Family Naming
Methods used for family naming are:
Field Guide
Made By-This field houses the initials of the person that created the wall. The idea is that you know who the point person is for information on reasons of methods for the walls creation.
Category-This is a 4 letter code the relates to the items family category.
Use-Specify how a person would interact with this object.
For example:
Brief Description-Whether it’s a model number, manufacturer, or thought; this field is meant to be filled in at the discretion of the creator.
Example:
A cupboard is created for use in a kitchen by Kirsten P Fossli. The cupboard is to be made of hickory and sizeable. The result is:
View Naming
In the Browser Organization properties, Views should be organized by:
Methods used for view naming are:
Level-List the level in L, B or R form. Example:
View Type-This designates what the views intended use is.
Standard Types:
Methods used for wall naming are:
- Made By-Use-Type-Thickness-Finish-Fire Rating
Field Guide
Made By-This field houses the initials of the person that created the wall. The idea is that you know who the point person is for information on reasons of methods for the walls creation.
Use-The Use field gives a general description of what the wall is used for. For example you might put in this field Interior, Exterior or Retaining. A 3 letter abbreviation is recommended:
- Interior – INT
- Exterior – EXT
- Retaining – RTN
Thickness-A simple number value for the thickness of the wall.
Finish-This field is for the primary aesthetic finish being used. For Example, Brick, Sheet Metal, Stucco.
Fire Rating-The rating of the wall when exposed to flames.
Example:
An exterior brick wall has been made. With all the layers in it, the thickness of the wall comes out to 11.75 inches thick. The wall was also made by Laura K Lawless. The wall is scheduled as type F4 in the wall schedule. In this case the following name is applied to the wall:
- LKL-EXT-F4-11 3/4”-Brick
Model Based Family Naming
Methods used for family naming are:
- Made By-Category-Use-Brief Description
Field Guide
Made By-This field houses the initials of the person that created the wall. The idea is that you know who the point person is for information on reasons of methods for the walls creation.
Category-This is a 4 letter code the relates to the items family category.
| REVIT VISIBILITY (VV) | ABREVIATION |
| Casework | CSWK |
| Columns | COLM |
| Curtain Panels | CWPL |
| Curtain Wall mullions | CNWM |
| Doors | DOOR |
| Detail Items | - |
| Electrical Equipment | ELEC |
| Electrical Fixtures | ELFX |
| Entourage | ETRG |
| Furniture | FURN |
| Furniture Systems | FSYS |
| Generic Models | GMOD |
| Lighting Fixtures | LITE |
| Lines | - |
| Mass | MASS |
| Mechanical Equipment | MECH |
| Parking | PARK |
| Planting | PLNT |
| Plumbing Fixtures | PLBG |
| Railings | RAIL |
| Raster Images | - |
| Roads | ROAD |
| Windows | WIND |
| Site | SITE |
| Specialty Equipment | SEQP |
| Stairs | STR |
| Structural Beam System | SBM |
| Structural Columns | SCOL |
| Structural Foundations | SFDN |
| Structural Framing | SFRM |
Use-Specify how a person would interact with this object.
For example:
- A chair or bench would be for Seating.
- A table or countertop would be Surfaces.
- Beds and exam tables would be Laying.
Brief Description-Whether it’s a model number, manufacturer, or thought; this field is meant to be filled in at the discretion of the creator.
Example:
A cupboard is created for use in a kitchen by Kirsten P Fossli. The cupboard is to be made of hickory and sizeable. The result is:
- KPF-CSWK-Storage-Hickory Cupboard 61cm x 183cm
View Naming
In the Browser Organization properties, Views should be organized by:
- Discipline
- Family and Type
- View Group-a property that needs to be created
Methods used for view naming are:
- Level-View Type-Description
- The views should have a parameter called View Group.
Level-List the level in L, B or R form. Example:
- B01-first grade below ground
- L00-for ground floor
- R01-Roofs
View Type-This designates what the views intended use is.
Standard Types:
- WRK -Working
- This view is used for editing elements in the model. The intent is to be a view where the designer and architect can change the view settings to show whatever their design concentration is on without worry of changing a document that will be printed for construction.
- PLT -Plot
- These views are being used for documents that will be printed for construction. Their settings are set up for specific instructions and PLT tells everyone that the views properties should not be changed.
- PRE -Presentation
- This view is used for design reviews or presentations to clients. Again, this lets other team members know not to change properties. Description This is typically the view title or a description of intended use.
|
SRobbins1977 |
Latest page update: made by SRobbins1977
, May 5 2008, 6:06 PM EDT
(about this update
About This Update
Edited by SRobbins1977
3 words deleted view changes - complete history) |
|
Keyword tags:
None
More Info: links to this page
|
| Started By | Thread Subject | Replies | Last Post | ||
|---|---|---|---|---|---|
| travistlo | View Naming | 5 | Jun 24 2009, 12:20 PM EDT by MikeDaniell | ||
|
Thread started: May 14 2008, 5:10 PM EDT
Watch
I dont completely agree that your View naming convention is the most appropriate for Revit. My reasons are as followed.
1. You can orginize your project browser by Level already. Revit knows what Levels things are based on the dimesions set. So labeling per level for orginization isnt very effective. 2. If you label your level with these abreviations, You now have to override your titlemark for the sheet? I know this is possible, but isnt it easier to have your view labeled the same as the titlemark on the sheet? This way you can keep things corresponding correctly, and it wont be so confusing to someone new jumping in on a project? Personally and around our office, we orginize our browser: Associated Level Family And Type View Group Family Just a comment for dicussion, to see how other people view it. -travis
1
out of
1 found this valuable.
Do you?
Keyword tags:
View Naming Conventions
|
|||||
Showing 1 of 1 threads for this page
