Looking for your opinion

[Anonymous]

Looking for your opinion

Hello everyone.
I am doing a project that is largest so far for me. It is 6 storey, 91 unit apartment building.

I did this project using “Hotlink Manager” for the actual unit walls bathrooms kitchens. And exterior walls and walls between units are placed on drawing using wall tool.

So my question is: What is the easiest way to detail these (17 different) units so even if something changes in the unit (i.e.: wall moves or bathroom changes) It will update automatically.

I tried using Detail marker but updating does not work the best plus everything is in 2D.
Also I tried using white Fill and filling everything around the unit so I can see only the unit working, but problem with that is that there is way too many layers (17 units and 17 different fills and its layers).

Does anyone have any other solutions?


Thank you
Dragan

[Anonymous]

The file size of the modules seems to be in line at 22.5MB for about 35 different versions of units from flats to thownhouses. The ability to publish a set version of the units for each function, i.e. modules to assemble the building, mods for export to dwg for consultants and other versions for presentation etc. is the key to the productivity of the system. The project in question is a midrise steel framed building of about 70 0r so units..(No comment about the individuality of the unit plans) we just like variety. Updates are fairly quick even when accessed across our MAC network. Schedules have been extracted from the units alone and the public areas of the building generate the general stuff. Haven't gotten to the finishes and equipment lists yet but expect the system to do it fairly easy.

Lew Bishop
Jon Worden Architects
G5 Dual 2.0 4GB nVidia 6800
OS X 10.4.7 AC 10 966

[Anonymous]

I'm in the midst of a nasty mess right now.

Working on a our story townhouse, that I wanted to share with people in my office.

It's carried over from AC 9, so it has old Lib parts, which I'm sure complicates things.

I started trying to use Teamwork, but the file slowed way down.

Then figured, change each floor to a mod, and hotlink back to host. Then I noticed all int. elevation work is lost in the mod. Better to hotlink a pln, and keep each floor int. elev in the individual floor pln. The each workerbee can do their layouts regarding that floor, and they can be imported to the host for publication (all to get a list of drawings.)

However, saving each floor as a pln, they generate errors, and all my walls have vanished.

What have I done wrong? Why do the AC gods frown so?

Hey, here's a suggestion: Post a table of what info gets held in Mod files, and where it is appropriate to hotlink them vs. plns. And what operations work in each. (SEOs work between wall of one mod and roof of another. Acutally, you can SEOs within a mod that is already in a host. Mods don't save views.)

[Anonymous]

Nathan wrote:
However, saving each floor as a pln, they generate errors, and all my walls have vanished.

What have I done wrong? Why do the AC gods frown so?

There are basically two methods which differ only in the details:

1: Link the PLNs directly. They link floor by floor so there is no need to save the stories as separate files. This has the advantage of being easy to set up and very automatic. It has the disadvantage of denying any control over what is included in the linked files.

2: Publish the stories as modules. This allows detailed control of which layers are included in the linked files.

In either case the interior elevations are best developed in the source files and linked as drawings to the layout set. The only way to share 2D data between sections is to publish those separately as modules. This is a situation where fully developing the model will really pay off so that building elements don't have to be drawn in 2D.

[Laura Yanoviak]

Nathan wrote:
...change each floor to a mod, and hotlink back to host. Then I noticed all int. elevation work is lost in the mod. Better to hotlink a pln, and keep each floor int. elev in the individual floor pln. The each workerbee can do their layouts regarding that floor, and they can be imported to the host for publication (all to get a list of drawings.)

However, saving each floor as a pln, they generate errors, and all my walls have vanished...

Publish to MOD to hotlink into master model; keep the PLN as a working file for editing and to generate interior elevations, etc. Just remember to publish to MOD again after making changes to keep MOD file current.

[Anonymous]

This is all to avoid/ work around teamwork, right? Or do people use published mods in conjunction with TW?

What elevation marker do you use now?
How do you key elevations if they aren't in the host? (Sorry LY, but keeping the markers in the host means only the host worker gets to work on them.) The Hotlinked plans need to be referenced in the hosts' layout or they don't show their elevation markers, but then they only know what they are referencing if its in the host file.(or is it time to retire the Multi Elevation Marker? )

And is it true that hotlinked data doesn't show up in schedules? I've set most everything to schedule in this job, and don't want to risk loosing that. I realize that the schedule is no longer 2-way: Doors in the Linked plan can't be modified from the host's schedule, only the hotlinked PLN.

[Laura Yanoviak]

Publishing to MOD helps keep the master model file size manageable -- it doesn't have anything to do with working with TW.

We don't use the Interior Elevation Tool, in that it's impractical (at best) and was downright unpredictable in AC9. We use individual SE Markers. I don't know why these couldn't be placed in the host...