We're setting up a project with a large team on a massive multi-use project. The project is a single building which will be divided up into three zones based on use. I've told my boss that there are two ways this could be approached, since we're working as a combined team in a single space we could work in a single architectural model and divide the zones based on worksets.
Alternately, we could set up a single core and shell model and then give each zone its own linked model, which I believe would allow the machines we're working on to run better. My boss asked what the disadvantages of the latter option are and I haven't really been able to think of any significant ones. It does mean you have three models to check and clean up as a BIM manager, but that's balanced out by having much more manageable file sizes to work with IMO.
Having never worked with multiple architectural models within a single building, I'm curious to ehar outside opinions on the workflow methods I mentioned and on other possible methods.
One additional question that has come up is the method of defininf these zones. For simple rectilinear zones we could use scope boxes to define them, but for something less simple I was thinking of suggesting something using Masses in the Core and Shell model. What the bosses want is something that will give soem sort of notification, warning or at least visual cue when someone working in one zone puts elements in another zone. Any thoughts on this would be doubly appreciated.