Split large project into 2 models

[Anonymous]

I have a large residential project. I split it into 2 models. 1 is on one side of the street and the other is on the other side of the street. A number of the wall sections and details are identical, but they are 2 separate drawing sets so details cannot be referenced between them.

How can I use the wall sections from one set for the other set? Obviously if I were in Auto cad I could easily use multiple details in different projects.

I am looking for a way to avoid doing the same work twice and cannot think of a way?

Thank you for your input!!

[Sahay_R]

Drafting views would be one way out - they can be inserted from one file to the other. Or create detail families.

[Anonymous]

I don't really like that solution because when I do wall sections I key them into the model and when the elevation changes the building section changes then the wall sections change then the details. If you use drafting views everything is 2d nothing is linked at that point it is not much different than auto cad.

[Sahay_R]

Can both models be linked into one single file for detailing purposes? Just a thought.....

[ToanDN]

- Link one model to the other
- Cut a section (A) where they located in the original link
- Open (A), edit the Revit Link display settings and to By linked view or Custom, and select the appropriate section view from the list (see screenshot)

- Put (A) on a Sheet.

- Cut another section (B) in the actual model but instead of create a new view, choose reference other view, and select (A)

- Rinse and repeat

[Anonymous]

It started out as a single model but was split into 2 to speed it up and make it easier for 2 groups of people to work on it from 2 different branch offices

[Alfredo_Medina]

I would not try to merge the two buildings into one if they are not supposed to be the same project. Referencing from one project to another might lead to errors with section lines, drawing numbers, sheet numbers, etc...

[FGPerraudin]

Hi Thomas,

There is no easy solution to that problem.

Ideally, both offices are connected with optic fiber and you can sync everything out... Maybe in a few tens of years?

Well, we need solutions while we wait.

The first thing you could do is take a note of families that evolve, save them in a specific folder, share them and regularly reload them in the other project.

That is the easy part.

The second issue is more difficult to deal with as it is about embeded properties and system families.

The only way to share and sync them is to use the Manage > transfer project standards in order to sync them.

It works very well except that it will replace the whole bunch of wall styles without letting you pick wich ones... Hard times!

What we have done at the practice when the problem happened is that we regularly created a new project that included all the modified elements (modified families, walls, etc) - then send it to the other team that linked and then binded the link. then we chose to replace the elements.

It requires to be very careful and strict with what you share that way, consequences can be terrible, but kinda works...

Sorry I do not know of more effective methods,

François

[Anonymous]

I think that could work, but defeats the purpose of creating 2 models. How is this better than just making the entire project in 1 model, which would be a huge slow file but if you are linking 1/2 into the other 1/2 would it be just as large and slow?

[ToanDN]

There is no easy answer to why one method is better or worse than another. It all depends on preferences and circumstances. You mentioned two teams at different offices working so you needed to split the file. I myself had some projects where I have all buildings in one file and they turned out fine contrary to the majority of opinions that they should be separate files.

[FGPerraudin]

Sorry I assumed that it was about developing two different parts of the same project from two different offices locations - thus the synchronyzing issue.. that would work but obvs take ages!

François

[Anonymous]

I see that if I link another model in and cut a section at the same location in the link all the annotation and detail items appear, would this also work for the callouts within the wall sections?

Thank you.

[Yien_Chao]

split the model and use a 3rd model to linked both of them.

this model should only be use for documentation.

It is not perfect, but at least you have two files only for modeling, which could be fast. And a 3rd one for annotations, details and documentation, which is good if you have SAME details on both project. Plus, you have to manage only at one place the graphic output, schedules, Revisions and references.