<?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>topic Re: Best workflow for multiple wall finish combinations without Composite Bloat in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/706036#M70211</link>
    <description>&lt;P&gt;In our professional workflows, we follow what&amp;nbsp;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/12391"&gt;@O_De Costa&lt;/a&gt;&amp;nbsp;is describing, which generally is to separate wall/partition types and finish types in our drafting standards. But back to how to model/organize this system: I find that a large number of composites is unavoidable, and the less error-prone option (you also note the limitations of other options).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend to our users they take it one step further, even, and create separate composites for different conditions. For example, this allows identical wall types (architecturally) to be used in a parapet condition vs. a soffit condition. The only difference in the composites (BIM-wise) is the intersection priority of the materials, which allows the model to do most of the heavy lifting for us when it comes to assembly intersections. It takes really good naming conventions, but other than that, it's manageable.&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jun 2026 19:04:24 GMT</pubDate>
    <dc:creator>Brandon-W_DWa</dc:creator>
    <dc:date>2026-06-22T19:04:24Z</dc:date>
    <item>
      <title>Best workflow for multiple wall finish combinations without Composite Bloat</title>
      <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/703043#M70087</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;I am looking for the best professional workflow to manage various interior and exterior wall finishes in Archicad without ending up with an uncontrollable number of Composite Structures (Composite Bloat).&lt;/P&gt;
&lt;P&gt;I have prepared a small demo plan to illustrate the issue. As you can see in the attached image, even in a very small layout, I am forced to create 5 different wall combinations (&lt;STRONG&gt;TYPE-1&lt;/STRONG&gt; to &lt;STRONG&gt;TYPE-5&lt;/STRONG&gt;) because the finish layers (&lt;STRONG&gt;C-1&lt;/STRONG&gt; to &lt;STRONG&gt;C-4&lt;/STRONG&gt;) change depending on the room types on either side of the core wall.&lt;/P&gt;
&lt;P&gt;I have already tried two common workarounds:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Using Wall Accessories.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Modeling finishes as separate, thin composite/basic walls (furring walls).&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;However, both methods create serious headaches when it comes to doors and windows. The openings do not automatically coordinate seamlessly across multiple walls, and whenever a door/window position or size changes during revisions, it becomes a manual tracking nightmare.&lt;/P&gt;
&lt;P&gt;How do you handle this complexity in large-scale professional projects? Is there a native feature, a specific Wall Closure/Opening Tool workflow, or an industry-standard method that makes managing separate finish layers seamless when dealing with doors and windows?&lt;/P&gt;
&lt;P&gt;I would highly appreciate your insights and workflows. Thank you!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="003.jpg" style="width: 799px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/101263iC49B2E644D608C4E/image-dimensions/799x629?v=v2" width="799" height="629" role="button" title="003.jpg" alt="003.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Windows &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 20 May 2026 10:39:44 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/703043#M70087</guid>
      <dc:creator>Cazer_36</dc:creator>
      <dc:date>2026-05-20T10:39:44Z</dc:date>
    </item>
    <item>
      <title>Re: Best workflow for multiple wall finish combinations without Composite Bloat</title>
      <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/703640#M70100</link>
      <description>&lt;P&gt;There is a related wish that would resolve issues with your second stated workaround. Currently, the wish is listed as &lt;EM&gt;"On Roadmap"&lt;/EM&gt;, though it never was. The &lt;EM&gt;"Opening Input in Section/Elevation"&lt;/EM&gt;&amp;nbsp;that came out with AC29 was stated as being related though it is a bit of a tangent, and quite a leap in it's current form from the wish...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.graphisoft.com/t5/Wishlist/Opening-Tool-as-Standard-Wall-Penetration-Tool/idc-p/703639#M4214" target="_blank"&gt;https://community.graphisoft.com/t5/Wishlist/Opening-Tool-as-Standard-Wall-Penetration-Tool/idc-p/703639#M4214&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ling.&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2026 08:48:25 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/703640#M70100</guid>
      <dc:creator>Lingwisyer</dc:creator>
      <dc:date>2026-05-26T08:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: Best workflow for multiple wall finish combinations without Composite Bloat</title>
      <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/704559#M70162</link>
      <description>&lt;P&gt;Thank you, Lingwisyer,&amp;nbsp;&lt;/P&gt;&lt;P&gt;The main problem I am facing is that the same structural wall core often requires different finish build-ups on each side depending on the functions of the adjacent rooms, which eventually leads to an excessive number of Composite Structures.&lt;/P&gt;&lt;P&gt;What I am really curious about is how offices handle this situation in large-scale projects. Are most users modeling finishes as separate walls or accessories and manually managing opening coordination, or is there a more robust Archicad workflow that I may be overlooking?&lt;/P&gt;&lt;P&gt;I would be very interested to hear how this is handled in projects.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jun 2026 19:37:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/704559#M70162</guid>
      <dc:creator>Cazer_36</dc:creator>
      <dc:date>2026-06-07T19:37:46Z</dc:date>
    </item>
    <item>
      <title>Re: Best workflow for multiple wall finish combinations without Composite Bloat</title>
      <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/704565#M70163</link>
      <description>&lt;P&gt;Drafting wise, are you modelling the finish build-ups as generic thickness, or as composite layers to be listed? I assume you are labelling the walls based on the inside / outside&amp;nbsp;&lt;EM&gt;Building Material ID&lt;/EM&gt;?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2026 01:46:37 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/704565#M70163</guid>
      <dc:creator>Lingwisyer</dc:creator>
      <dc:date>2026-06-08T01:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Best workflow for multiple wall finish combinations without Composite Bloat</title>
      <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/704746#M70177</link>
      <description>&lt;P&gt;Yes, I am modeling the finish build-ups as composite layers so they can be properly listed in the schedules. And yes, you are correct, I am labeling the walls based on the Building Material ID.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jun 2026 11:31:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/704746#M70177</guid>
      <dc:creator>Cazer_36</dc:creator>
      <dc:date>2026-06-09T11:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: Best workflow for multiple wall finish combinations without Composite Bloat</title>
      <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/706006#M70208</link>
      <description>&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/134417"&gt;@Cazer_36&lt;/a&gt;&lt;BR /&gt;Since Archicad doesn't offer a native solution for this, workarounds are unavoidable. Your Option 2 (thin finish walls) is workable and has been used effectively in professional practice, typically in combination with fully built-out composite structures. The opening coordination issue you mentioned, can be managed using empty openings, which can then be filtered out of schedules to keep documentation clean and having the advantage of indexing/tracking openings after/for revisions.&lt;/P&gt;&lt;P&gt;That said, the more fundamental shift worth considering is in how Wall Types and Wall Finishes are classified. Trying to encode finish information directly into wall type identifiers leads to exactly the composite bloat you're describing. I would suggest that a cleaner approach is to treat them separately:&lt;/P&gt;&lt;P&gt;Wall Types defined by their structural or functional core (not their finishes)&lt;BR /&gt;Wall Finishes captured on a Room Finish Schedule, with surface information called out via classification and properties labels&lt;BR /&gt;This keeps the wall type library manageable and puts finish data where it's most useful --- in the schedules.&lt;/P&gt;&lt;P&gt;While a native modeling solution for this would be a genuine improvement to Archicad, revisiting the classification logic is the most scalable path within the current toolset&lt;/P&gt;&lt;P class=""&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 14:15:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/706006#M70208</guid>
      <dc:creator>O_De Costa</dc:creator>
      <dc:date>2026-06-22T14:15:29Z</dc:date>
    </item>
    <item>
      <title>Re: Best workflow for multiple wall finish combinations without Composite Bloat</title>
      <link>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/706036#M70211</link>
      <description>&lt;P&gt;In our professional workflows, we follow what&amp;nbsp;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/12391"&gt;@O_De Costa&lt;/a&gt;&amp;nbsp;is describing, which generally is to separate wall/partition types and finish types in our drafting standards. But back to how to model/organize this system: I find that a large number of composites is unavoidable, and the less error-prone option (you also note the limitations of other options).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend to our users they take it one step further, even, and create separate composites for different conditions. For example, this allows identical wall types (architecturally) to be used in a parapet condition vs. a soffit condition. The only difference in the composites (BIM-wise) is the intersection priority of the materials, which allows the model to do most of the heavy lifting for us when it comes to assembly intersections. It takes really good naming conventions, but other than that, it's manageable.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 19:04:24 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Best-workflow-for-multiple-wall-finish-combinations-without/m-p/706036#M70211</guid>
      <dc:creator>Brandon-W_DWa</dc:creator>
      <dc:date>2026-06-22T19:04:24Z</dc:date>
    </item>
  </channel>
</rss>

