<?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: Is there a better way to do apartments? in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140760#M75546</link>
    <description>I sometimes keep all the apartments in one pln and use "save selected to module" this helps in consolidating some of the pln.</description>
    <pubDate>Fri, 03 Dec 2010 16:37:32 GMT</pubDate>
    <dc:creator>Eduardo Rolon</dc:creator>
    <dc:date>2010-12-03T16:37:32Z</dc:date>
    <item>
      <title>Is there a better way to do apartments?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140759#M75545</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;It seems to be working fine, but slow, we are doing individual units in their own pln, then buildings in their own pln, hotlinking the units to the building plans, then using a site plan pln to "put a bow on it."  We are using the site plan file as for all the layouts and external sourcing for the views.  Is this the best way?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 03 Dec 2010 16:27:01 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140759#M75545</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-12-03T16:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a better way to do apartments?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140760#M75546</link>
      <description>I sometimes keep all the apartments in one pln and use "save selected to module" this helps in consolidating some of the pln.</description>
      <pubDate>Fri, 03 Dec 2010 16:37:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140760#M75546</guid>
      <dc:creator>Eduardo Rolon</dc:creator>
      <dc:date>2010-12-03T16:37:32Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a better way to do apartments?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140761#M75547</link>
      <description>A few years back I set up the apartments in a single PLN with a separate story (or stories for duplexes) for each unit type. I then created views of each and published them as modules. The units were all lined up from floor to floor at project zero to keep a common insertion point (lower left interior as I recall).&lt;BR /&gt;
&lt;BR /&gt;
In most cases the common and exterior walls were modeled in the main building with partial ones added to the unit plans to publish the drawings. One advantage of publishing modules was that we could turn off the layers we did not want to convey from the unit plan models to the main buildings.&lt;BR /&gt;
&lt;BR /&gt;
This was in AC9-10. Not sure if I would do it any differently now.</description>
      <pubDate>Sat, 04 Dec 2010 03:37:37 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140761#M75547</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-12-04T03:37:37Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a better way to do apartments?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140762#M75548</link>
      <description>In nearly all our projects (especially multi-res and high rise) we have a master file and a module file. The module file has a story structure set up whereby unit types, floor plates, cores, site info, grids, etc can be created in their respective groups. &lt;BR /&gt;
&lt;BR /&gt;
A pre-made publisher set exists that saves each story out as a module file. Both the Master and Module files are shared on the BIM Server and our mod files are published to another server. &lt;BR /&gt;
&lt;BR /&gt;
It all works together very well and is easy to manage and use. Much better than hotlinking project stories together and creating a web of links. &lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Link.</description>
      <pubDate>Sat, 04 Dec 2010 04:56:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140762#M75548</guid>
      <dc:creator>Link</dc:creator>
      <dc:date>2010-12-04T04:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a better way to do apartments?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140763#M75549</link>
      <description>&lt;BLOCKQUOTE&gt;Link wrote:&lt;BR /&gt;Much better than hotlinking project stories together and creating a web of links.&lt;/BLOCKQUOTE&gt;

Hotlinking to PLNs for this is definitely a mess to be avoided. Publishing the modules gives fine tuned control. The extra step of having to publish does have its advantages as well. Performance is generally better and you have total control of the update process. Kind of like the difference between manual and automatic gearboxes.</description>
      <pubDate>Sat, 04 Dec 2010 15:04:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Is-there-a-better-way-to-do-apartments/m-p/140763#M75549</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-12-04T15:04:32Z</dc:date>
    </item>
  </channel>
</rss>

