<?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 Archicad Doors and Windows with IfcOpeningElement in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Archicad-Doors-and-Windows-with-IfcOpeningElement/m-p/716486#M15911</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am experiencing an issue during IFC export regarding the automatically generated 'IfcOpeningElement' entities created by doors and windows.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When validating our IFC models against strict IDS (Information Delivery Specification) requirements, these automatically generated opening elements fail the checks. The IDS requires a value for both the 'PredefinedType' and 'Name' attributes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even though I have set up explicit Data Mapping rules in the IFC Translator to assign a fallback 'Name' and specific parameters to 'IfcOpeningElement' (or IfcFeatureElementSubtraction), Archicad ignores these rules for the sub-elements generated by door/window wall cutouts. They are exported with PredefinedType as 'None' (or empty) and their 'Name' attributes are either left empty or cannot be overridden properly, resulting in validation failures in Solibri / BIMcollab.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I use the Model Filter to exclude 'IfcOpeningElement', Archicad completely closes the wall voids, which ruins the geometry.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a hidden way, a workaround, or a planned hotfix to allow users to force Data Mapping rules onto these automatically generated opening sub-elements without breaking the host wall geometry?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SefaYakut_0-1791204695329.png" style="width: 999px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/106568iE2521EF9BBCF7ECC/image-size/large?v=v2&amp;amp;px=999" role="button" title="SefaYakut_0-1791204695329.png" alt="SefaYakut_0-1791204695329.png" /&gt;&lt;/span&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>Mon, 05 Oct 2026 12:52:30 GMT</pubDate>
    <dc:creator>Sefa Yakut</dc:creator>
    <dc:date>2026-10-05T12:52:30Z</dc:date>
    <item>
      <title>Archicad Doors and Windows with IfcOpeningElement</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Archicad-Doors-and-Windows-with-IfcOpeningElement/m-p/716486#M15911</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am experiencing an issue during IFC export regarding the automatically generated 'IfcOpeningElement' entities created by doors and windows.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When validating our IFC models against strict IDS (Information Delivery Specification) requirements, these automatically generated opening elements fail the checks. The IDS requires a value for both the 'PredefinedType' and 'Name' attributes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even though I have set up explicit Data Mapping rules in the IFC Translator to assign a fallback 'Name' and specific parameters to 'IfcOpeningElement' (or IfcFeatureElementSubtraction), Archicad ignores these rules for the sub-elements generated by door/window wall cutouts. They are exported with PredefinedType as 'None' (or empty) and their 'Name' attributes are either left empty or cannot be overridden properly, resulting in validation failures in Solibri / BIMcollab.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I use the Model Filter to exclude 'IfcOpeningElement', Archicad completely closes the wall voids, which ruins the geometry.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a hidden way, a workaround, or a planned hotfix to allow users to force Data Mapping rules onto these automatically generated opening sub-elements without breaking the host wall geometry?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SefaYakut_0-1791204695329.png" style="width: 999px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/106568iE2521EF9BBCF7ECC/image-size/large?v=v2&amp;amp;px=999" role="button" title="SefaYakut_0-1791204695329.png" alt="SefaYakut_0-1791204695329.png" /&gt;&lt;/span&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>Mon, 05 Oct 2026 12:52:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Archicad-Doors-and-Windows-with-IfcOpeningElement/m-p/716486#M15911</guid>
      <dc:creator>Sefa Yakut</dc:creator>
      <dc:date>2026-10-05T12:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Archicad Doors and Windows with IfcOpeningElement</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Archicad-Doors-and-Windows-with-IfcOpeningElement/m-p/716492#M15912</link>
      <description>&lt;P&gt;I don't know a workaround or fix in Archicad, but you can take the exported IFC file, and potentially fix these missing values there.&lt;/P&gt;
&lt;P&gt;There are solutions that let you read, modify, and save IFC files.&lt;/P&gt;
&lt;P&gt;One such solution is IfcOpenShell, which is a Python library.&lt;/P&gt;
&lt;P&gt;Another is Bonsai, the BIM Add-On developed on top of Blender, which is also based on IfcOpenShell.&lt;/P&gt;
&lt;P&gt;IfcOpenShell just runs from your command prompt, while Bonsai will be able to load and display your full IFC file, so visually that is easier.&lt;/P&gt;
&lt;P&gt;In either of these, you can modify the IFC Properties of IFC elements in the IFC file.&lt;/P&gt;
&lt;P&gt;So, I think you should be able to fill out those missing IFC Property values of the IfcOpeningElement entities and save the result. Then you can run the IDS check on them to make sure they pass.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I had a recent test where I was saving the individual skins of Composite Walls in the IFC, and as it turns out the exact sizes (Length, Height) of the skins were not calculated correctly in Archicad, so when I mapped their values to IFC Properties, they did not contain the accurate values. So, I used IfcOpenShell to check the actual length, width, and height values of the individual skins as stored in the IFC file (they were saved as BREPs so I knew the geometries were correct), and based on those results, I modified the corresponding IFC Properties within the file. Then, the IFC Properties did contain the accurate dimensions of each individual composite skin. Actually, Claude Desktop guided me through the whole process and I achieved the desired result perfectly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This can be turned into a workflow. Obviously, it is an extra step after the IFCs are exported from Archicad, but the result is a correct IFC file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2026 13:27:16 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Archicad-Doors-and-Windows-with-IfcOpeningElement/m-p/716492#M15912</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2026-10-05T13:27:16Z</dc:date>
    </item>
  </channel>
</rss>

