Separated Sheet file

[Anonymous]

Hi all, 

I work for an architectural practice in Spain and I'm struggling with their way of managing Model and Sheet file. They basically split every project (not only really big scale ones) into a model file (or more) and a sheet file where all the views and annotation are created. I find this way of working quite frustrating cause annotating direclty on sheets files generate orphan and tag loss, not mentioning the fact that the sheet file is a very heavy file difficult to manage.

On the top of that they want to duplicate all the structure information in the actual architecture file, which I again find really unuseful given that we've got an exterior structure consultant that works with his proper file (linked in our). 

I'd like to understand if this way of working is any good and if there is a common good practice to managing big and medium scale project avoiding to split the project into model and sheet file, and if so, wouldnt be better to maintain views and annotations in the actual architecture file and then link the views in the sheets file?

Thanks a lot, I appreciate any help.

[SteveKStafford · Accepted solution]

Working that way is completely and utterly un-Revit. That is not how it was ever intended to be used. If it is being done because "File Size" then they've been led astray.

Separate models is a reality when the party responsible for the model(s) are separated by physical distance or company boundaries. It is as a last resort that we ever separate the model and the annotation.

Revit was conceived to make it easier to create better coordinated documentation. Separating it's built in integration is like buying a car but insisting we can only push it everywhere ... to save fuel.

[Anonymous]

Hi Steve, 

thanks a lot for your answer, I totally agree with you. I'll try to talk to them to find some sort of compromise and avoid this method.

Kind regards,

Bianca