Announcement

Collapse
No announcement yet.

Code Information Sheets

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Code Information Sheets

    We are reworking our Code Information Sheet(s) and I'm not sure what the best approach to it is, and more precisely some of the pros & cons of different approaches. I've seen these sheets done as all text on a page, text in drafting views, generic annotations with some fill-in the blanks, fake schedules (key schedules / Ideate Sticky, etc), and a hodgepodge of all of the above.
    • I don't like the text on page as it leaves way too much room for user error, both in formatting and deleting things that should exist. Yes, I shouldn't have to worry about it but I'm a curmudgeon.
    • Text in drafting views has the same issues, although somewhat reduced since the individual segments would be separate views.

    Frequently these have a lot of copy/paste from the code, which I am especially against since there is far too much probability of someone not updating the text to reflect a state or local variation, even if the actual review was done correctly.
    • In theory generic annotations would be a good option; it would be easy to create objects based the various code sections, but there is some layout flexibility that is lost because they are a defined size that is difficult to change, although that isn't much different than the drafting view approach. This could result in dozens of families though...
    • Fake schedules are OK for some pieces, not really opposed as long as the traps mentioned above are avoided.

    Anyhow - I'm curious what others are doing and if there are any caveats or major issues encounted with any of these methods, or if I am just overlooking something altogether. :beer::beer:
    Revit for newbies - A starting point for RFO

    chad
    BEER: Better, Efficient, Elegant, Repeatable.
    Tags: None
    #2
    Legends, with mainly text. No text on the actual sheet.
    I'm just in the process of creating a more or less comprehensive rvt file just to hold all the legends, as these are used on all the sheets to hold general/typical notes. I'm removing these legends from the template file, and use JOTools to "import" in the legend as needed. Like you said, it's getting terribly difficult to monitor what needs to be specific for a jurisdiction or updated properly for the what seems to be constant code changes (California here...)
    Fred Blome
    Residential Architect

    Comment

      #3
      Something else to consider: Excel-Dynamo-Note Block method.

      Create a GA with shared params; you probably want 3 - the item title (in the left column), item data (in the right column), and a sorting order. Once these are placed into a view, you can create a note block schedule of them, and use the standard schedule formatting tools to adjust the size and arrangement of the schedule.

      If you combine this with Dynamo and Excel, it starts to get powerful. You can read the notes from Excel, find a drafting view where the notes should live, get the existing notes (if any), modify or delete them, place any new notes required, etc. This drafting view never needs to be on a sheet - you're just using it to generate the schedule. All your text can be edited (and verified) in Excel.
      Attached Files
      Chris Ellersick

      Comment

        #4
        Interesting. I've created Key Schedules from Excel with Dynamo, but never Note Blocks. I don't think I've even used a note block in the last 5 years :crazy:
        Revit for newbies - A starting point for RFO

        chad
        BEER: Better, Efficient, Elegant, Repeatable.

        Comment

          #5
          Originally posted by FBlome View Post
          Legends, with mainly text. No text on the actual sheet.
          I'm just in the process of creating a more or less comprehensive rvt file just to hold all the legends, as these are used on all the sheets to hold general/typical notes. I'm removing these legends from the template file, and use JOTools to "import" in the legend as needed. Like you said, it's getting terribly difficult to monitor what needs to be specific for a jurisdiction or updated properly for the what seems to be constant code changes (California here...)
          I use legends extensively. I have a large library of them by topic and just drop them in as needed. And they can be re-used on the multiple sheets when it's useful. Like putting the "Egress Lighting Notes" on the ceiling plans as wells as the code plan.

          Legends also allow for detail references to be placed onto them, so you can refer to typ details etc. You can't drop those onto a sheet, has to be in a view. You can use legend components (such as the are), draft to scales, etc. I find them pretty useful, I keep a ton of the key ones in my template. When some code or standard changes, i just update the template.

          Comment

          Previous template Next

          Related Topics

          Collapse
          Working...
          X