How to manage multiple scope sets in one Revit model?

[micah]

Hello,

I have a hotel renovation with multiple scope sets, each with its own submittal. How do we manage the drawing boarder so that sheet numbering can repeat once for each scope set? Our Title Sheet T1.0 would apply to Scope 1 and again to Scope 2, with different data on each T1.0. This is an example, but there are other instances where we would repeat sheet numbers and view names.

[syman2000]

Is there a reason you cannot place one scope as its own independent Revit model? Afterward you link the existing model into that particular scope. That way you wouldn't have to figure out how to make multiple scope having the same T1.0 sheet. If that is not possible, then I would set the sheet with 1-T1.0 for scope 1 and 2-T1.0 for scope 2.

[micah]

Hello,

I was trying to keep it simple, I suppose, but will implement a prefix or
suffix to the numbering and get creative with sheet names. Thank you!

[ToanDN]

Create different files for different scopes and keep sheets unique to each scope in their own file.  Your main file is for sheets that can be shared among multiple scopes.

[micah]

Thanks @ToanDN . For clarification, does your technique require the modeling to be completed in separate files, or just the sheets? I hesitate to break up the modeling into different files. Maybe this is due to my background working mostly on smaller projects like SFRs. For instance, for this hotel renovation, if I model scope A on one file, and scope B on another, how do do put it all together for a rendering or for coordination? Or, again, are you saying to break up the files only for purposes of setting up sheets?

[syman2000]

What I find is if you break up the file into separate files,  you are able to have multiple users working on separate scope files without slowing down the model. Recently I have a project where the team decided to work in one Revit file. The team consists of 10 people working in one Revit file. It takes an extremely long time to sync since everyone is syncing one after the other. Breaking them up does have its advantages and you can have multiple users working on the file in their own separate model. As for rendering, you can link them together and Twinmotion, Lumion and Enscape will be able to render the scene seamlessly.

[micah]

Thank you. Some day, when I have more than one FTE, this will be more
handy. Good to know this is the way to go on big projects.

[ToanDN]

---

@micah wrote:

Thanks @ToanDN . For clarification, does your technique require the modeling to be completed in separate files, or just the sheets? I hesitate to break up the modeling into different files. Maybe this is due to my background working mostly on smaller projects like SFRs. For instance, for this hotel renovation, if I model scope A on one file, and scope B on another, how do do put it all together for a rendering or for coordination? Or, again, are you saying to break up the files only for purposes of setting up sheets?

---

No.  The model and all model views + shared drafting views/legends/schedules are in the main file.  The unique files are for things such as coversheets.