Friday, August 3, 2012

Building Code plans

When developing building code plans in Revit I've come up with a few rules I currently like to use:
  1. Code plans should be made from an Area plan
    • When calculating code required areas you have much more control of Areas then Rooms.
    • Room sf don't go to the center of wall for some rooms and to the face of walls in others 
    • Occupancy types go beyond the walls
  2. Code plans should be created in the Complete phase
    • There are diagram objects that you could be putting into the code plans that could show up in other views.
    • When doing a multi-phase project, the code officials want to understand the final out come of the project.
    • In the default Architectural Revit template there are 3 typical phases Existing, New Construction and Compete. Most of the new work you do is usually done on the New Construction phase, and the complete phase is considered a future phase of the project.
  3. Code plans should be at least half (if not smaller) the scale of the original views.
    • The code plan is a diagram about code information not building information. 
  4. Use view filters to show different fire ratings. (ignore NCS here)
    • The diamonds that the NCS suggest using for depicting fire ratings suck.(though I do think the US Army Corps of engineers has put together a good symbol for this in there Revit template)
    • Using a dash dot pattern in the walls is much cleaner then the diamonds.
  5. When calculating egress length use a custom railing family
    • Railings can be built as one object, rather then inserting multiple families
    • Bollards can be built to look like direction arrows, that can be placed at a specific interval 
    • Generic families need to added up, while a railing tag can give total length at one time
    • Railing will give the length along the slope of a stair or ramp

No comments: