Announcement

Collapse
No announcement yet.

Plan - Tagging Detail Components

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Plan - Tagging Detail Components

    We have a specific type of "Infection Control" Plan we create for our healthcare projects. In the past, we have created the graphics shown in the attached jpg with detail components and detail component tags. The dark dashed lines that are tagged are not actual walls, which is why we've done them as a line-based detail component family. The hatched areas are filled regions.

    The issue I've run into is that the tag has to read an instance parameter because a filled region can't have a type parameter added. Any ideas on how to do this better? I was thinking maybe an area plan? But then we'd have to have 2 types of tags - one for areas and one for detail components. Or would keynotes be the way to go here?

    I'm typically a little leery of keynotes, because often the order of the notes changes over the course of the project, and then those changes have to be made in the model.

    #2
    Image attached: IC.JPG

    Comment


      #3
      You can use type parameters on Filled Regions. Make them shared parameters, this will work.
      There is a thread here somewhere on tagging stuff in Revit. I posted my Generic Tag there (all text parameters, shared, type). Change the Category in the family and save as, also export the shared parameters and import in your project. Or just recreate it...
      Martijn de Riet
      Professional Revit Consultant | Revit API Developer
      MdR Advies
      Planta1 Revit Online Consulting

      Comment


        #4
        Originally posted by mdradvies View Post
        You can use type parameters on Filled Regions.
        I had already tested that out before I posted, and was unable to add any type parameters to filled regions.

        Comment


          #5
          Originally posted by LKeyser View Post
          I had already tested that out before I posted, and was unable to add any type parameters to filled regions.
          I will post an working example tomorrow... I don't have Revit on me just now to check.
          Martijn de Riet
          Professional Revit Consultant | Revit API Developer
          MdR Advies
          Planta1 Revit Online Consulting

          Comment


            #6
            Originally posted by LKeyser View Post
            I had already tested that out before I posted, and was unable to add any type parameters to filled regions.
            Yes it is possible, but as filled regions are system families which are categorised as detail items, you cannot cannot add the parameter to only filled regions, you will need to add the shared parameter to all detail items as a project parameter

            To do this you need to follow the steps below
            1. Create the shared parameter
            2. Add the shared paramter to your project through the manage panel, project parameters, you should assign this parameter to the detail items category
            3. Create your detail item tag, and label the tag with the shared parameter


            The problem with this workflow is that all detail items in your project will now have this parameter

            Also Detail items cannot be scheduled, which limits your options for actually managing and using this information in your project
            Revit BLOGGAGE

            http://www.revic.org.au

            Comment


              #7
              Line Based Generic Models, with nested details or annotations. Then you have to OPTION to keep it coordinated on all of the plans, even if you never show it on any of the plans. Works great.
              Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
              @Web | @Twitter | @LinkedIn | @Email

              Comment


                #8
                Originally posted by Ben-May View Post
                Yes it is possible, but as filled regions are system families which are categorised as detail items, you cannot cannot add the parameter to only filled regions, you will need to add the shared parameter to all detail items as a project parameter

                To do this you need to follow the steps below
                1. Create the shared parameter
                2. Add the shared paramter to your project through the manage panel, project parameters, you should assign this parameter to the detail items category
                3. Create your detail item tag, and label the tag with the shared parameter


                The problem with this workflow is that all detail items in your project will now have this parameter

                Also Detail items cannot be scheduled, which limits your options for actually managing and using this information in your project
                Thanks for sorting that out, knew it was possible. Few notes on the side:

                - I create my filled regions by type. So, when in need of a certain filled region (for instance to represent a kind of wall), the naming will be similar to the naming of said wall. This clears out the problem of having the SP applied to all filled regions.
                - The SP will indeed be applied to all detail items, NOT the value though. In that way they work the same as tags for other categories.

                Aaron: never thought about this (mainly because I use DC's for 95% of the time). How does this affect visibility? Do you need to apply filters for the views you don't want them in (since it's a GM) or does it only show in the view that it's placed in (since it's a nested DC)? And if it only shows in the view you placed it in, does the "grip" show as an empty line in other views? Just asking, cause this would mean a setback: you then would be able to select and delete it without knowing...
                Martijn de Riet
                Professional Revit Consultant | Revit API Developer
                MdR Advies
                Planta1 Revit Online Consulting

                Comment


                  #9
                  Originally posted by Twiceroadsfool View Post
                  Line Based Generic Models, with nested details or annotations. Then you have to OPTION to keep it coordinated on all of the plans, even if you never show it on any of the plans. Works great.
                  I'm with you on the Line Based Generic Models, but how would you do the hatched areas in this situation? Ideally the users would be using the same tag (or keynote tag, if applicable) for all of the elements.

                  And for those of you who have suggested that you can add a type parameter to a filled region, could you post a working example? I understand that you assign it to the detail items category, but as I posted earlier, the parameter does not show up in the filled region's type properties.

                  Filled Region Type Parameter.png

                  Comment


                    #10
                    Originally posted by LKeyser View Post
                    I'm with you on the Line Based Generic Models, but how would you do the hatched areas in this situation? Ideally the users would be using the same tag (or keynote tag, if applicable) for all of the elements.

                    And for those of you who have suggested that you can add a type parameter to a filled region, could you post a working example? I understand that you assign it to the detail items category, but as I posted earlier, the parameter does not show up in the filled region's type properties.

                    [ATTACH=CONFIG]1264[/ATTACH]
                    You can create the same type of tag, using the same SP's. BUT they won't be linked. So you need to manually coordinate between the different types (Filled Region vs GM). Attached a working DC Tag. Open the tag in the family editor, replace the labels with your own and you're off... Top one is also loaded in the project, the second one isn't and therefor can't be filled out.
                    Are the Parameter Types set correctly (to text, and not something else like Area)
                    Attached Files
                    Martijn de Riet
                    Professional Revit Consultant | Revit API Developer
                    MdR Advies
                    Planta1 Revit Online Consulting

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X