Project Setup Tips? Shell / Tenant Plan coordination

[MMontgomery]

I have a shopping center project.

What is the slickest way to coordinate the shell plan with the tenant plans, while giving me the flexibility to submit the shell plans seperately from the tenants and the tenants seperate from each other?

Should I be thinking hotlinked modules?

-or-

Should I be thinking Layer, Layer Combination and View Set manipulation and Attribute Manager?

-or-

???

________________

I'd prefer to keep everything in a single .PLN and break out different sets of plans from the one .PLN file. It seems that this would be the simplest way to keep changes between the shell and tenants coordinated. I'll admit, I don't use hotlinked modules very often and don't know whether they might be a better way to go. A single PLN would require a large amount of time for setup for layering, layer combinations, view sets, etc..., but seems to be a nice, clean way of going about it.

I'm curious how others have setup a project like this.

[Aaron Bourgoin]

Think strategically about the project and the work to be done after the base building is under way. Seems to me you could save a whole lot of time with TI work, leasing certificates, etc. by treating each CRU as a separate file and hotlinking the tenant spaces into it, you could be saving a lot of time down the road, and demonstrating the advantage of this flexibility as a service to the client.

Give some thought to the facility management tie-in and you should have a client for life.