Architecture Collaboration

[kmarquis]

I am starting work on a team where another architecture firm is responsible for the entire core/shell as well as the interior fitout. Our firm is soley resonsible for the Lab Casework and equipement. I'm thinking this is as simple as linking the architects model into our file and adding in the equipement. How should we approach wall/ceiling hosted families? Do we need to create generic families that are not hosted? Should we copy/monitor walls into our file so we can host equipment to walls? How well does Copy/Monitor work being inexperienced with this tool? If the architecture firm moves a wall how will we know to shift our casework to the new wall location? Thanks in advance.

[sbrown]

I would recreate all content as NON hosted.

[Scott Womack]

I am starting work on a team where another architecture firm is responsible for the entire core/shell as well as the interior fitout. Our firm is soley resonsible for the Lab Casework and equipement. I'm thinking this is as simple as linking the architects model into our file and adding in the equipement. How should we approach wall/ceiling hosted families? Do we need to create generic families that are not hosted? Should we copy/monitor walls into our file so we can host equipment to walls? How well does Copy/Monitor work being inexperienced with this tool? If the architecture firm moves a wall how will we know to shift our casework to the new wall location? Thanks in advance.

As Scott said, safest is non-hosted, next safest is face hosted.

If you chose to copy monitor the walls, when you get an updated model, and reload youtr project, you'd get a coordination alert. This would tell you to bring that report up, and you'd have to step through every wall, and accept, reject, or postpone it. Accepting it, causes your wall to move/chnge to the new location, along with any hosted items.

The issue would come in if the other architect deleted walls and redrew them, without warning you. This would actually cause that wall, if accepted in the coordination report, to disappear, along with any wall hosted items as well. (Not Good) Face based objects as would non-hosted items remain behind. (Much better).

[kmarquis]

Thanks...This is very useful information. So if I have a wall hosted family I'm thinking I could just load it into a generic family template and create some shared parameters for scheduling instead of completely re-creating the family from scratch?

[Scott Womack]

Thanks...This is very useful information. So if I have a wall hosted family I'm thinking I could just load it into a generic family template and create some shared parameters for scheduling instead of completely re-creating the family from scratch?

Sorry to disappoint you. You cannot take a hosted family, and nest it into a non-hosted family, nor into a different type of hosted family. To convert a wall hosted family into either a face-based, or non-hosted family, you have to copy clip the geometry from one type of family, into a blank family of the other type, recreate reference plans, and parameters, reconnect them to the geometry, and ensure they work.

The reason that virtually none of the Architectural content has face-hosted elements, is that the content was originally created before face-hosted types of families existed.