Announcement

Collapse
No announcement yet.

Casework

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

    Casework

    The purpose of this thread, is to create a template for all categories, so let´s start with this, and then go on with the other categories once we have a layout with all the needed information.

    In the below, I´ve added most of the hardcoded system information, along with the info suggested by Seek... Do we base this on Seek, or do we start from scratch ?

    Category used for:
    Base Cabinets, Tall Cabinets, Wall Cabinets, Counter Tops

    OOTB Templates:
    Casework.rft
    Casework wall based.rft (for all wall based families)

    RFO Templates:
    RFO_Casework.rft
    RFO_Casework face based.rft (for all face based families)

    Graphics:
    Cutable = Yes
    Depth Clip = No
    Join Geometry (in Project) = No

    Known Category Restrictions:
    None.

    Parameters (System / Seek / RFO)

    Construction
    Construction Type

    Material and Finishes
    Finish
    Cabinet Material (Shared, Instance, Material)
    Door Material (Shared, Instance, Material)
    Drawer Material (Shared, Instance, Material)
    Hardware Material (Shared, Instance, Material)
    Shelves Material (Shared, Instance, Material)
    Toe Kick Material (Shared, Instance, Material)

    Dimensions
    Depth
    Height
    Width
    Toe Kick Height (Shared, Type, Length)
    Toe Kick Depth (Shared, Type, Length)
    Cabinet Height (Shared, Type, Length)
    Door Width (Shared, Type, Length) Formula = Width/2
    Countertop Thickness (Shared, Type, Length)
    Height A (Shared, Type, Length)
    Height B (Shared, Type, Length)
    Height C (Shared, Type, Length)
    Height D (Shared, Type, Length)


    Identity Data
    Keynote
    Model
    Manufacturer
    Type Comments
    URL
    Description
    Assembly Code
    Cost
    OmniClass Number
    Style (Shared, Type, Text, Sample: Mission, Modern, Cottage, etc.)

    Green Building Properties
    Percentage of Recycled Content (Shared, Type, Number, Sample: Value representing a percentage )
    Salvage or Reuse (Shared, Instance, Yes/No)
    Low Emitting Material (Shared, Type, Yes/No)
    Low Emitting Finish (Shared, Instance, Yes/No)

    Construction
    Door Type (Shared, Type, Family Type)
    Drawer Type (Shared, Type, Family Type)
    Hardware Type (Shared, Instance, Family Type)
    Lock Doors (Shared, Instance, Yes/No)
    Lock Drawers (Shared, Instance, Yes/No)

    Graphics:
    Show Door (Shared, Type, Yes/No)
    Show Drawer (Shared, Type, Yes/No)
    Show Toe Kick (Shared, Instance, Yes/No)
    Show Hardware (Shared, Instance, Yes/No)
    Cut Sink Hole (Shared, Instance, Yes/No)

    Subcategories (System / Seek / RFO)
    Elevation Swing
    Hidden Lines
    Cabinet
    Counter Top
    Glass
    Hardware
    Plan Swing
    Plan Rep Above
    Toe Kick

    Category Specific "Best Practices"
    Doors, Drawers and Hardware should always be nested and shared.

    Casework families should never be wall based - use face based instead.

    Plan representation:
    • Base Cabinet: Masking region with subcategory set to “Hidden Lines [Projection]” and “Draw in Foreground” selected.
    • Wall Cabinet: Symbolic lines on subcategory “Plan Rep Above [Projection].”
    • Tall Cabinet: Masking region with subcategory set to “Casework [Projection]” and “Draw in Foreground” selected.
    • Counter Top: Masking Region with subcategory set to “Counter Top [Projection],” with the “Draw in Foreground” option cleared, and the work plane specified at the top of the cabinets.
    Level of Detail (LOD)
    Coarse = Working view, optimized for performance (Box only)
    Medium = Documentation View (Shows what´s needed for documentation only)
    Fine = Presentation and Rendering (Shows all details)


    Document History:
    • Changed wall based to facebased
    • LOD section added
    • Added suggestions from Post #3-#17
    • Toe Kick dimensions changed to Type
    Last edited by Munkholm; March 1, 2011, 06:15 PM. Reason: Toe Kick dimensions changed to Type
    Klaus Munkholm
    "Do. Or do not. There is no try."

    #2
    First off, I would like to scratch the wall-based and make this face based. For example for ceiling or column hosted cabinets.
    Martijn de Riet
    Professional Revit Consultant | Revit API Developer
    MdR Advies
    Planta1 Revit Online Consulting

    Comment


      #3
      Originally posted by mdradvies View Post
      First off, I would like to scratch the wall-based and make this face based. For example for ceiling or column hosted cabinets.
      Agreed!

      Here´s some suggestions for additional parameters:

      Material and Finishes
      Cabinet (Shared, Instance, Material)
      Door (Shared, Instance, Material)
      Drawer (Shared, Instance, Material)
      Hardware (Shared, Instance, Material)

      Dimensions
      Plinth Height (Shared, Instance, Length)
      Cabinet Height (Shared, Type, Length)

      Construction
      Door Type (Shared, Type, Family Type)
      Drawer Type (Shared, Type, Family Type)

      Graphics:
      Show Door (Shared, Type, Yes/No)
      Show Drawer (Shared, Type, Yes/No)
      Show Plinth (Shared, Type, Yes/No)

      Best Practices
      I´d suggest that doors and drawers should be nested families, unshared, casework category.
      Klaus Munkholm
      "Do. Or do not. There is no try."

      Comment


        #4
        Totally off topic, but why the hell a latin text???

        Back on topic:
        Like the extra parameters.
        How do you handle sinks and built in kitchen appliences like dishwasher and stuff? I model these in a different category and just keep openings in the cabinets. Do you link these in?
        Martijn de Riet
        Professional Revit Consultant | Revit API Developer
        MdR Advies
        Planta1 Revit Online Consulting

        Comment


          #5
          Construction
          Hardware Type (Shared, Instance, Family Type)

          Graphics:
          Show Hardware (Shared, Instance, Yes/No)

          Best Practices
          Hardware (handles) should be nested into the door/drawer families, unshared, casework category.
          Klaus Munkholm
          "Do. Or do not. There is no try."

          Comment


            #6
            Originally posted by mdradvies View Post
            Totally off topic, but why the hell a latin text???

            Back on topic:
            Like the extra parameters.
            How do you handle sinks and built in kitchen appliences like dishwasher and stuff? I model these in a different category and just keep openings in the cabinets. Do you link these in?
            The latin text is commonly used on the internet as "dummy" text, but goes back to the 1500s....

            Sinks I build as facebased plumbing (with a void) and nest into the counter top with a <Family Type> parameter (shared), so that it can be swapped.
            Kitchen appliances i build as Electrical Equipment and nest into my (typical) tall units... (currently as separate families, non swappable... but maybe that should be improved)
            Klaus Munkholm
            "Do. Or do not. There is no try."

            Comment


              #7
              Just going thru my current and older libraries, and would add these parameters:

              Other
              Door Width (Shared, Type, Length) For double doors = Width / 2 (anyone need uneven doors ?)

              Graphics
              Cut Sink Hole (Shared, Instance, Yes/No)

              Dimensions
              Plinth Depth (Shared, Instance, Length)
              Klaus Munkholm
              "Do. Or do not. There is no try."

              Comment


                #8
                Ohh... and something that should be covered in all categories: Level of Detail (LOD)
                Klaus Munkholm
                "Do. Or do not. There is no try."

                Comment


                  #9
                  Originally posted by Munkholm View Post
                  The latin text is commonly used on the internet as "dummy" text, but goes back to the 1500s....
                  To expand on this just a bit, This text is used but its typical use is not really as a place holder for text in any situation
                  It is meant to be used in bodies of text where the visual composition of a body of text is important. The reason it is used, is that it "looks" similar to our language when written without it actually being legible, hence publishers, for example, can use it to compose the layout of a body of text without the need to actually have the article written.

                  Back on topic

                  How about adding a parameter for

                  Materials and Finishes

                  Shelves (shared, instance, materials)??
                  I have a couple of cabinet families with shelves and even wine racks
                  Juan Carlos Moreno
                  Store Designer & Merchandising Manager
                  Sisley Cosmetics

                  Comment


                    #10
                    Thanks for the clarification on "Lorem Ipsum"

                    I could easily imagine having the need for a separate material for Shelves Any other parameters needed for shelves ? Like "Number of Shelves", etc.
                    Klaus Munkholm
                    "Do. Or do not. There is no try."

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X