<?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 Ci Tools Keynotes | Archicad Keynotes | Properties | Attributes in General discussions</title>
    <link>https://community.graphisoft.com/t5/General-discussions/Ci-Tools-Keynotes-Archicad-Keynotes-Properties-Attributes/m-p/714805#M8776</link>
    <description>&lt;DIV&gt;I’d like to paint a picture of these individually valuable improvements, which now seem to require a little refinement to bring them together into a cohesive whole.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;One of the key advantages of CI Tools Keynotes is that they can be linked to an external database, such as an Excel spreadsheet or a MasterSpec/SmartSpec specification.&lt;/STRONG&gt; However, this workflow breaks down when using PMK detail drawings between files.&lt;/P&gt;&lt;P&gt;Our typical workflow involves maintaining a central Project Detail Library that supports 8 to 10 housing projects. Each house is a separate Teamwork file, resulting in 8 to 10 project files plus the shared detail library. Details are exported from the library as PMK drawings and then placed into the individual house files. The MasterSpec keynotes are linked in every file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;The limitation is that CI Keynotes do not pass through PMK drawings, which means we are unable to use the scheduling functionality across the project. As a result, one of the most valuable features of the keynote system is lost within this workflow.&lt;/U&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;I appreciate Archicad Keynotes because they work seamlessly with the PMK-based workflow described above.&lt;/STRONG&gt; Since keynote information is retained in the PMK detail drawings, we can place those details into the individual house files and successfully generate keynote schedules at the project level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;However, Archicad Keynotes have the opposite limitation of CI Tools Keynotes. While they support scheduling through PMK drawings, there is currently no option to link them to an external database such as Excel, MasterSpec, or SmartSpec.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;As a result, we gain the flexibility of scheduling across projects, but lose the benefits of a centralised, database-driven specification system. Maintaining and coordinating keynote data therefore becomes a more manual process, increasing the risk of inconsistencies across projects.&lt;/U&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;I see value in using Archicad Properties.&lt;/STRONG&gt; Properties can be displayed directly in Archicad's native Door and Window Interactive Schedules, which is a significant advantage. We generally avoid the CI Tools Door and Window Schedule because it can noticeably increase file size and impact performance.&lt;/P&gt;&lt;P&gt;&lt;U&gt;However, when keynote systems (either CI Tools Keynotes or Archicad Keynotes) are used to define glazing types in joinery details, an additional coordination step is required. The glazing information contained within the keynote must also be replicated in the element properties to ensure consistency.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;This means maintaining the same information in two places: the detail-level keynote and the model element properties. As a result, extra checking is needed to verify that both sources remain aligned and that there is no ambiguity about the glazing specification required for the project.&lt;/U&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;I like using Building Materials and Surfaces because they allow us to embed specification codes directly into their names and then reference those codes using AutoText labels and Expression-based Properties.&lt;/STRONG&gt; This provides a straightforward and efficient way to communicate material and finish information throughout the documentation from the 3D model.&lt;/P&gt;&lt;P&gt;&lt;U&gt;However, when Keynotes (either CI Tools Keynotes or Archicad Keynotes) are also used, we introduce a second source of specification data that must be maintained. The codes and descriptions defined within the Building Materials and Surfaces need to remain consistent with those contained in the Keynotes.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;As a result, additional coordination and checking are required to ensure both systems remain aligned. Without this, discrepancies can arise between the model data, labels, schedules, and keynote information, potentially leading to confusion during documentation and construction.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Similar to the Properties workflow, we end up maintaining related specification information in multiple locations. While each system offers valuable benefits, they rely on ongoing coordination to ensure a single source of truth is maintained throughout the project.&lt;/U&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 11&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 16 Sep 2026 22:39:06 GMT</pubDate>
    <dc:creator>Andras Bognar</dc:creator>
    <dc:date>2026-09-16T22:39:06Z</dc:date>
    <item>
      <title>Ci Tools Keynotes | Archicad Keynotes | Properties | Attributes</title>
      <link>https://community.graphisoft.com/t5/General-discussions/Ci-Tools-Keynotes-Archicad-Keynotes-Properties-Attributes/m-p/714805#M8776</link>
      <description>&lt;DIV&gt;I’d like to paint a picture of these individually valuable improvements, which now seem to require a little refinement to bring them together into a cohesive whole.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;One of the key advantages of CI Tools Keynotes is that they can be linked to an external database, such as an Excel spreadsheet or a MasterSpec/SmartSpec specification.&lt;/STRONG&gt; However, this workflow breaks down when using PMK detail drawings between files.&lt;/P&gt;&lt;P&gt;Our typical workflow involves maintaining a central Project Detail Library that supports 8 to 10 housing projects. Each house is a separate Teamwork file, resulting in 8 to 10 project files plus the shared detail library. Details are exported from the library as PMK drawings and then placed into the individual house files. The MasterSpec keynotes are linked in every file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;The limitation is that CI Keynotes do not pass through PMK drawings, which means we are unable to use the scheduling functionality across the project. As a result, one of the most valuable features of the keynote system is lost within this workflow.&lt;/U&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;I appreciate Archicad Keynotes because they work seamlessly with the PMK-based workflow described above.&lt;/STRONG&gt; Since keynote information is retained in the PMK detail drawings, we can place those details into the individual house files and successfully generate keynote schedules at the project level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;However, Archicad Keynotes have the opposite limitation of CI Tools Keynotes. While they support scheduling through PMK drawings, there is currently no option to link them to an external database such as Excel, MasterSpec, or SmartSpec.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;As a result, we gain the flexibility of scheduling across projects, but lose the benefits of a centralised, database-driven specification system. Maintaining and coordinating keynote data therefore becomes a more manual process, increasing the risk of inconsistencies across projects.&lt;/U&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;I see value in using Archicad Properties.&lt;/STRONG&gt; Properties can be displayed directly in Archicad's native Door and Window Interactive Schedules, which is a significant advantage. We generally avoid the CI Tools Door and Window Schedule because it can noticeably increase file size and impact performance.&lt;/P&gt;&lt;P&gt;&lt;U&gt;However, when keynote systems (either CI Tools Keynotes or Archicad Keynotes) are used to define glazing types in joinery details, an additional coordination step is required. The glazing information contained within the keynote must also be replicated in the element properties to ensure consistency.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;This means maintaining the same information in two places: the detail-level keynote and the model element properties. As a result, extra checking is needed to verify that both sources remain aligned and that there is no ambiguity about the glazing specification required for the project.&lt;/U&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;I like using Building Materials and Surfaces because they allow us to embed specification codes directly into their names and then reference those codes using AutoText labels and Expression-based Properties.&lt;/STRONG&gt; This provides a straightforward and efficient way to communicate material and finish information throughout the documentation from the 3D model.&lt;/P&gt;&lt;P&gt;&lt;U&gt;However, when Keynotes (either CI Tools Keynotes or Archicad Keynotes) are also used, we introduce a second source of specification data that must be maintained. The codes and descriptions defined within the Building Materials and Surfaces need to remain consistent with those contained in the Keynotes.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;As a result, additional coordination and checking are required to ensure both systems remain aligned. Without this, discrepancies can arise between the model data, labels, schedules, and keynote information, potentially leading to confusion during documentation and construction.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Similar to the Properties workflow, we end up maintaining related specification information in multiple locations. While each system offers valuable benefits, they rely on ongoing coordination to ensure a single source of truth is maintained throughout the project.&lt;/U&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 11&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 16 Sep 2026 22:39:06 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/General-discussions/Ci-Tools-Keynotes-Archicad-Keynotes-Properties-Attributes/m-p/714805#M8776</guid>
      <dc:creator>Andras Bognar</dc:creator>
      <dc:date>2026-09-16T22:39:06Z</dc:date>
    </item>
  </channel>
</rss>

