<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Organizational Groups / Open Pseudo-Families en Revit Ideas</title>
    <link>https://forums.autodesk.com/t5/revit-ideas/organizational-groups-open-pseudo-families/idi-p/7094290</link>
    <description>&lt;P&gt;The introduction of global parameters to Revit 2017 was an interesting&amp;nbsp;solution to consistency problems regarding project-wide specifications&amp;nbsp;like, the facade materials of a building, minimum window heights and many others.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This was a well received addition in my office, all&amp;nbsp;my coworkers were quite happy about it. We started using it a lot and then realized that we were kinda turning our&amp;nbsp;projects into massive families, for example: using named parameters for the material of the walls on every room&amp;nbsp;("Room1.Walls.Interior_Material"), or for positioning different things into a kitchen&amp;nbsp;("Kitchen.Cabinets.Mounting_&lt;SPAN&gt;Height&lt;/SPAN&gt;"), thankfully we had luck we defined a consistent naming scheme for them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I came up with an idea that could&amp;nbsp;solve these problems and I think that's something that Revit desperately needs, Open Pseudo-Families.&lt;/P&gt;&lt;P&gt;These "families" or "advanced groups" would&amp;nbsp;serve exclusively as a dedicated structure and namespace&amp;nbsp;for a group of revit objects, that orchestrates the placement and holds parameters specific to that group of objects without adding any primitive geometry.&lt;/P&gt;&lt;P&gt;You can think of it&amp;nbsp;like the existing groups or matices of objects, but with a dedicated namespace specific to that group, where you can hold&amp;nbsp;different parameters, in addition to that, they would need to be transparent,&amp;nbsp;all inner objects should be reachable and usable as much as its constraints allow, and nestable. A basic example would be a set of chairs and a table as one open family that gets nested into a the "kitchen" open-family.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These are some basic specifications as the main idea is quite simple, implementing a tree-like structure of relationships to Revit, because we design buildings that way, there's no stove without a kitchen and there's no bed without a bedroom. I hope you found this idea interesting, have a nice day.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 18 May 2017 23:20:48 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-05-18T23:20:48Z</dc:date>
    <item>
      <title>Organizational Groups / Open Pseudo-Families</title>
      <link>https://forums.autodesk.com/t5/revit-ideas/organizational-groups-open-pseudo-families/idi-p/7094290</link>
      <description>&lt;P&gt;The introduction of global parameters to Revit 2017 was an interesting&amp;nbsp;solution to consistency problems regarding project-wide specifications&amp;nbsp;like, the facade materials of a building, minimum window heights and many others.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This was a well received addition in my office, all&amp;nbsp;my coworkers were quite happy about it. We started using it a lot and then realized that we were kinda turning our&amp;nbsp;projects into massive families, for example: using named parameters for the material of the walls on every room&amp;nbsp;("Room1.Walls.Interior_Material"), or for positioning different things into a kitchen&amp;nbsp;("Kitchen.Cabinets.Mounting_&lt;SPAN&gt;Height&lt;/SPAN&gt;"), thankfully we had luck we defined a consistent naming scheme for them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I came up with an idea that could&amp;nbsp;solve these problems and I think that's something that Revit desperately needs, Open Pseudo-Families.&lt;/P&gt;&lt;P&gt;These "families" or "advanced groups" would&amp;nbsp;serve exclusively as a dedicated structure and namespace&amp;nbsp;for a group of revit objects, that orchestrates the placement and holds parameters specific to that group of objects without adding any primitive geometry.&lt;/P&gt;&lt;P&gt;You can think of it&amp;nbsp;like the existing groups or matices of objects, but with a dedicated namespace specific to that group, where you can hold&amp;nbsp;different parameters, in addition to that, they would need to be transparent,&amp;nbsp;all inner objects should be reachable and usable as much as its constraints allow, and nestable. A basic example would be a set of chairs and a table as one open family that gets nested into a the "kitchen" open-family.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These are some basic specifications as the main idea is quite simple, implementing a tree-like structure of relationships to Revit, because we design buildings that way, there's no stove without a kitchen and there's no bed without a bedroom. I hope you found this idea interesting, have a nice day.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2017 23:20:48 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-ideas/organizational-groups-open-pseudo-families/idi-p/7094290</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-05-18T23:20:48Z</dc:date>
    </item>
  </channel>
</rss>

