<?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: How can I combine model data and schedule totals into one building data summary table? in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/How-can-I-combine-model-data-and-schedule-totals-into-one/m-p/717313#M15918</link>
    <description>&lt;P&gt;Hi Siluett,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good news: this can be done with native Archicad tools. The key thing to know up front is that one schedule cannot reference another schedule's totals — there are no cross-schedule references in Archicad. So instead of merging your existing schedules, build one master summary schedule fed directly by the source elements (zones, fills, objects). Each indicator becomes a row in that schedule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Direct answers to your three questions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Reference values or totals from other schedules? Not directly — a schedule can't read another schedule's grand total. Property expressions can only reference the element's own parameters. So point your summary schedule at the source elements instead (your fills, your zones, one small "data" object — see below).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Fill area? Yes. Fills are schedulable: add the "Measured Net Area" / "Measured Gross Area" field and your footprint fill feeds the table automatically. Values from associative dimensions? No — dimensions are annotation and can't appear in schedules. Read the height/length/width off your dimensions once (or use the Measure tool) and enter them as manual values (see below).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Combine linked values with manual entries? Yes. Custom properties are editable directly in schedule cells, so automatic and manual values can live side by side in the same table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A reusable recipe (all native):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 1 — Create custom properties. Options &amp;gt; Property Manager &amp;gt; new group, e.g. "Building Summary". Add:&lt;/P&gt;&lt;P&gt;- "Indicator" (Text) — the row label, e.g. "Building footprint"&lt;/P&gt;&lt;P&gt;- "Manual value" (Number, or Length / Area / Volume as needed) — for hand-entered data&lt;/P&gt;&lt;P&gt;- "Show in summary" (Option Set: Yes / No, default No) — the switch that decides which elements appear in the table&lt;/P&gt;&lt;P&gt;Apply this group to Fills, Zones and Objects.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 2 — Tag your source elements. Set "Show in summary" = Yes on:&lt;/P&gt;&lt;P&gt;- your footprint fill ("Indicator" = Building footprint)&lt;/P&gt;&lt;P&gt;- the above-ground footprint fill&lt;/P&gt;&lt;P&gt;- your heated-area zones (their category names can become the Indicator text, or keep your existing grouped zone schedule and let the summary show the totals you care about)&lt;/P&gt;&lt;P&gt;- one small library Object placed out of the way on its own layer, named e.g. "BUILDING DATA" — give it Indicator rows for the manual values: "Building height", "Absolute elevation of highest point", "Building length", "Building width", "Depth below ground", "Storeys above ground", "Storeys below ground".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 3 — Expressions for the semi-automatic rows. Expressions only see the element's own properties, but combined with one or two manual inputs they automate the arithmetic. For example, on the footprint fill:&lt;/P&gt;&lt;P&gt;- "Building volume" = Measured Gross Area x "Average height" (a manual Number property you type in)&lt;/P&gt;&lt;P&gt;- "Absolute elevation of highest point" = "Project altitude" (manual) + "Building height" (manual)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 4 — Build the schedule. Document &amp;gt; Schedules &amp;gt; Scheme Settings &amp;gt; New:&lt;/P&gt;&lt;P&gt;- Element types: Fill, Zone, Object (multiple types are allowed in one schedule)&lt;/P&gt;&lt;P&gt;- Criteria: "Show in summary" = Yes&lt;/P&gt;&lt;P&gt;- Fields: "Indicator" | "Measured Net Area" | "Measured Gross Area" | "Manual value" | your expression properties&lt;/P&gt;&lt;P&gt;- Sort by "Indicator", or add a "Sort order" number property if you want a custom row order.&lt;/P&gt;&lt;P&gt;Save the scheme in your office template and the whole setup travels with every new project — next time you just tag the elements.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Two honest limitations to plan around: zones don't expose volume natively in schedules (use the Area x Height expression trick above, or schedule a Morph mass — morphs have a schedulable Volume parameter), and storey counts plus the absolute elevation will always be manual entries. Typing those few numbers once into custom properties inside the schedule is still far better than retyping a whole table or stitching screenshots.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that gets you a proper one-table workflow.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S. When you cross-check a hand-measured area against a printed or PDF drawing at a stated scale, this free scale converter saves a lot of calculator work: &lt;A href="https://gad.design/scale-converter" target="_blank"&gt;https://gad.design/scale-converter&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 12 Oct 2026 01:58:36 GMT</pubDate>
    <dc:creator>gaddesign</dc:creator>
    <dc:date>2026-10-12T01:58:36Z</dc:date>
    <item>
      <title>How can I combine model data and schedule totals into one building data summary table?</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/How-can-I-combine-model-data-and-schedule-totals-into-one/m-p/717090#M15917</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;How can I combine model data and schedule totals into one building data summary table?&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I’m using Archicad 29 and would like to create one building data summary table, with the indicator name in the first column and its value in the second.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The table needs to include:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Building footprint (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Above-ground building footprint (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Heated floor area (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Floor area heated to room temperature (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Enclosed net floor area (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Residential floor area, including associated ancillary rooms (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Non-residential floor area (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Common-use area (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Technical/service room area (m²)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Building height (m)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Absolute elevation of the building’s highest point (m above sea level)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Building length (m)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Building width (m)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Building depth below ground (m)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Number of above-ground storeys&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Number of underground storeys&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Building volume (m³)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Above-ground building volume (m³)&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;I already have:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;A Zone Schedule with area totals grouped by category.&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;A separate schedule containing the building volume and above-ground building volume.&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;A Fill measuring the building footprint.&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Associative dimensions showing the building’s height, length and width.&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;My goal is to bring this information together into &lt;/SPAN&gt;one table, with most values automatically populated from the model or existing schedules and kept linked for updates.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Not every value needs to be automatic. If an indicator cannot easily be retrieved from the model—for example, the number of storeys—I would be happy to enter it manually as text in the same table.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a way to:&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Reference values or totals from different schedules in one summary table?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Include the Fill area and values from associative dimensions, or equivalent measurements from the model?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Combine these linked values with manually entered information in the same table?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;I’m looking for a reusable solution rather than manually retyping all the values or assembling cropped pieces of different schedules on a Layout.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can this be done with native Archicad tools, or would it require an add-on or script? A sample file, workflow or tutorial would be very helpful.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you!&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>Fri, 09 Oct 2026 07:47:51 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/How-can-I-combine-model-data-and-schedule-totals-into-one/m-p/717090#M15917</guid>
      <dc:creator>Siluett</dc:creator>
      <dc:date>2026-10-09T07:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: How can I combine model data and schedule totals into one building data summary table?</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/How-can-I-combine-model-data-and-schedule-totals-into-one/m-p/717313#M15918</link>
      <description>&lt;P&gt;Hi Siluett,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good news: this can be done with native Archicad tools. The key thing to know up front is that one schedule cannot reference another schedule's totals — there are no cross-schedule references in Archicad. So instead of merging your existing schedules, build one master summary schedule fed directly by the source elements (zones, fills, objects). Each indicator becomes a row in that schedule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Direct answers to your three questions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Reference values or totals from other schedules? Not directly — a schedule can't read another schedule's grand total. Property expressions can only reference the element's own parameters. So point your summary schedule at the source elements instead (your fills, your zones, one small "data" object — see below).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Fill area? Yes. Fills are schedulable: add the "Measured Net Area" / "Measured Gross Area" field and your footprint fill feeds the table automatically. Values from associative dimensions? No — dimensions are annotation and can't appear in schedules. Read the height/length/width off your dimensions once (or use the Measure tool) and enter them as manual values (see below).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Combine linked values with manual entries? Yes. Custom properties are editable directly in schedule cells, so automatic and manual values can live side by side in the same table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A reusable recipe (all native):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 1 — Create custom properties. Options &amp;gt; Property Manager &amp;gt; new group, e.g. "Building Summary". Add:&lt;/P&gt;&lt;P&gt;- "Indicator" (Text) — the row label, e.g. "Building footprint"&lt;/P&gt;&lt;P&gt;- "Manual value" (Number, or Length / Area / Volume as needed) — for hand-entered data&lt;/P&gt;&lt;P&gt;- "Show in summary" (Option Set: Yes / No, default No) — the switch that decides which elements appear in the table&lt;/P&gt;&lt;P&gt;Apply this group to Fills, Zones and Objects.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 2 — Tag your source elements. Set "Show in summary" = Yes on:&lt;/P&gt;&lt;P&gt;- your footprint fill ("Indicator" = Building footprint)&lt;/P&gt;&lt;P&gt;- the above-ground footprint fill&lt;/P&gt;&lt;P&gt;- your heated-area zones (their category names can become the Indicator text, or keep your existing grouped zone schedule and let the summary show the totals you care about)&lt;/P&gt;&lt;P&gt;- one small library Object placed out of the way on its own layer, named e.g. "BUILDING DATA" — give it Indicator rows for the manual values: "Building height", "Absolute elevation of highest point", "Building length", "Building width", "Depth below ground", "Storeys above ground", "Storeys below ground".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 3 — Expressions for the semi-automatic rows. Expressions only see the element's own properties, but combined with one or two manual inputs they automate the arithmetic. For example, on the footprint fill:&lt;/P&gt;&lt;P&gt;- "Building volume" = Measured Gross Area x "Average height" (a manual Number property you type in)&lt;/P&gt;&lt;P&gt;- "Absolute elevation of highest point" = "Project altitude" (manual) + "Building height" (manual)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 4 — Build the schedule. Document &amp;gt; Schedules &amp;gt; Scheme Settings &amp;gt; New:&lt;/P&gt;&lt;P&gt;- Element types: Fill, Zone, Object (multiple types are allowed in one schedule)&lt;/P&gt;&lt;P&gt;- Criteria: "Show in summary" = Yes&lt;/P&gt;&lt;P&gt;- Fields: "Indicator" | "Measured Net Area" | "Measured Gross Area" | "Manual value" | your expression properties&lt;/P&gt;&lt;P&gt;- Sort by "Indicator", or add a "Sort order" number property if you want a custom row order.&lt;/P&gt;&lt;P&gt;Save the scheme in your office template and the whole setup travels with every new project — next time you just tag the elements.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Two honest limitations to plan around: zones don't expose volume natively in schedules (use the Area x Height expression trick above, or schedule a Morph mass — morphs have a schedulable Volume parameter), and storey counts plus the absolute elevation will always be manual entries. Typing those few numbers once into custom properties inside the schedule is still far better than retyping a whole table or stitching screenshots.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that gets you a proper one-table workflow.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S. When you cross-check a hand-measured area against a printed or PDF drawing at a stated scale, this free scale converter saves a lot of calculator work: &lt;A href="https://gad.design/scale-converter" target="_blank"&gt;https://gad.design/scale-converter&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2026 01:58:36 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/How-can-I-combine-model-data-and-schedule-totals-into-one/m-p/717313#M15918</guid>
      <dc:creator>gaddesign</dc:creator>
      <dc:date>2026-10-12T01:58:36Z</dc:date>
    </item>
  </channel>
</rss>

