On Land

Environment Information
At Rill Architects we run ArchiCAD on Mac OS X. If you work at Rill, this is your stuff. If you don't, but you work in ArchiCAD, you may find something interesting. Anybody else, I don't know.
RSS

It would nice to have standard details in one place, where any project could use them with no need to redraw anything. These would be standard assembly types, foundations, flashing, etc.

You can place views from any number of external project in a layout book in 9 or 10. The trouble comes in when you want to refer to the external drawing with a detail marker. Even in 10, this is still not possible.

So we have to consider a couple imperfect alternatives.

• Maintain modules, one for each detail. Merge or hotlink the modules into detail windows within the project. Refer to the internal detail drawings normally.

If you hotlink the modules, they can be truly standardized, with any changes distributed to all projects by updating hotlinks. The drawback is the module reference warning if you take the project off network. No harm, just hassle. (You could choose to break the hotlink, which would leave the detail intact, but it wouldn't be connected to the original.)

As an alternate to separate modules, you could place all the details in one project file, with one detail on each story. In this case, merging is not an option. You would hotlink the stories and optionally break the hotlinks.

Then you could use Publisher to create modules if you wanted them.

The one-project method also makes attribute management easier. It's important to rigorously control attributes so you don't 'contaminate' the current project.

Using hotlinks to the detail project stories presents a problem: You can't insert a story without breaking the links in projects. Ouch.

• Use external views directly, even though the referencing doesn't work. You would need a fixed ID, specific to the detail, which would appear in a drawing title object in the detail, and in the detail ID in the project. These IDs would bear no relationship to the sheet. Weird.

Conclusion:

• Create the details in a project file, one on each story. This is simpler generally and helps with the attributes.

• From this project, publish modules of the details. Then the modules themselves are hotlinked or merged. The detail project becomes an administrative resource; users don't interact with it directly. The stories can be managed for the convenience of the 'detail administrator'. Whenever a detail is added or changed, republish the modules.

• Hotlink or merge the modules into project detail windows and reference them normally.