AC-Teamwork, Hotlinked, Xref

[Anonymous]

We are working in a project using Hotlinked, Teamwork and Xref. This is a Condominium divided in 3 connected buildings. I create 1 plp for every building and hotlinked all of them to a master plp. Buildings A, B and C are just for design it doesn't contains any text, dimension, zones or detail.
557,000 sq. ft is our construction area and here is the problem.
We used to attach as xref our electrical/mechanical consultants design which came in Autocad to make our coordination plans which is reflected at Reflected ceiling plans, and roof plans mostly. The case now is that one of our new employees draw a lot of elevations in Autocad and merge them into our master .plp. That makes our file very slow and one of the options that we have to keep work faster is take out all the details from our master .plp and create a new .plp just for details and blow-ups. I know this sound like a mess because that forced us to import and coordinate every detail and blow up from another plp. does anyone have a suggestion to keep this project on track without loosing very good features of AC, PM?

Regards

[TomWaltz]

How do you handle the annotation from the original floor? Aren't there room names and labels that say "Third Floor" or something that would need to change from floor to floor?

[Anonymous]

ANDY,

I think tom has a good question below, but can be handled.

Assuming you are not using teamwork anymore, how many team members work on one of your projects?

Jim

[Ignacio Azpiazu]

TomWaltz wrote:
How do you handle the annotation from the original floor? Aren't there room names and labels that say "Third Floor" or something that would need to change from floor to floor?

Initially, everything that is repetitive goes to the module, everything that is story-specific goes to the PLN story. [Generally text in modules leads to headaches when the modules start rotating, which doesn't apply to Andy's single multistory building, but must be just about every other case.]

But you can have objects in the modules reading the zones in the pln stories and showing that information, so that can save some work.

[Anonymous]

I have a related question now after setting up a large project using strictly hotlinks and avoiding teamwork. An important issue is to skip when necessary to avoid circuliar references and doubles of nested modules.

I knew at some point I was going to have a problem with the nested hotlink files when a point along the tree of references, a host file (a composite master file in my case) will not want to skip particuliar modules, but skip other nested files. As you know, when you select skip nested files in a host file near the top of the tree structure, it's all or nothing.

I like the way xrefs work for this reason, so you can overlay at the frontend of the linking procedure.

See my schematic if you will. It might help explain my quandry. Let me know if any of you worked this out before or had to go another route.

[TomWaltz]

Teamwork's not that bad. You're going to waste more time trying to work around it like this than you ever would just learning it and doing it.

[Ignacio Azpiazu]

jim wrote:
An important issue is to skip when necessary to avoid circuliar references and doubles of nested modules.

TomWaltz wrote:
Teamwork's not that bad.

I agree. Teamwork gooood.

Still: publishing to modules would allow you to hide the control layer for the modules, or the layers for the structural elements in the modules, so that you are not sending that stuff into the master file.

Check out
http://www.graphisoft.com/support/archicad/archiguide/TipOnPublishingToModuleFiles.html