<?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: Controlling details in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56172#M2564</link>
    <description>Here's an &lt;A href="http://www.aecbytes.com/tipsandtricks/2007/issue18-archicad.html" target="_blank"&gt;excellent article.&lt;/A&gt;</description>
    <pubDate>Tue, 09 Oct 2007 03:25:36 GMT</pubDate>
    <dc:creator>Richard Morrison</dc:creator>
    <dc:date>2007-10-09T03:25:36Z</dc:date>
    <item>
      <title>Controlling details</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56169#M2561</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;When 2D details are created to develop our office detail library, we are considering having a template file specifically for detailing so that all details live in the same place and are created with the same attributes. (Details are going to be created on an as needed basis from project to project so that it is all created under a billable project). Is this a sound practice or is there a better way? I fell as though this limits flexibility, ie we can't hotlink the details as modules. Maybe we don't want this flexibility?? Any feedback would be great!&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 08 Oct 2007 19:09:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56169#M2561</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-10-08T19:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling details</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56170#M2562</link>
      <description>Having one file for developing your standard details is a reasonable approach. You can publish these as modules to easily insert them into the project file (or copy/paste if you have both files open - multiple users can open the standard detail file as Read Only).&lt;BR /&gt;
&lt;BR /&gt;
I don't recommend keeping all your developed project details in this one single file. While there are ways to make this work (Teamwork for multiple access, ID codes by project, etc.) but it is asking for trouble. There are so many possible problems with this that I can't go into it right now.&lt;BR /&gt;
&lt;BR /&gt;
You should have your attributes sufficiently standardized that details can be imported to project files without problems. Pens, fills and linetypes are all that really matter. Details can generally exist on a single layer and variant pens can be handled with pen sets if necessary. So if you are standardized on your line and fill types you will be fine.</description>
      <pubDate>Mon, 08 Oct 2007 19:29:24 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56170#M2562</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-10-08T19:29:24Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling details</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56171#M2563</link>
      <description>Thank you Matthew! Do you have a suggestion for a solid way to organize and manage details?</description>
      <pubDate>Mon, 08 Oct 2007 22:34:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56171#M2563</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-10-08T22:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling details</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56172#M2564</link>
      <description>Here's an &lt;A href="http://www.aecbytes.com/tipsandtricks/2007/issue18-archicad.html" target="_blank"&gt;excellent article.&lt;/A&gt;</description>
      <pubDate>Tue, 09 Oct 2007 03:25:36 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56172#M2564</guid>
      <dc:creator>Richard Morrison</dc:creator>
      <dc:date>2007-10-09T03:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling details</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56173#M2565</link>
      <description>Nice article !!!&lt;BR /&gt;
&lt;BR /&gt;
Compiling a detail catalog will be very useful !&lt;BR /&gt;
&lt;BR /&gt;
Thanks</description>
      <pubDate>Fri, 26 Oct 2007 12:36:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Controlling-details/m-p/56173#M2565</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-10-26T12:36:29Z</dc:date>
    </item>
  </channel>
</rss>

