Is there any reason to separate structure in different linked file for a small project?

[svalente9GJKH]

Much of what I do is residential homes with wood framing, usually just model wood faming into my model.

Just wondering if there would be any benefit having  a different model for framing because I plan to generate production/wood framing drawings (using Strucsoft plugin)

Also, if I plan to add in hvac ducts, plumbing etc,   but doing it all on my end,    is there any reason to have different linked models?

Thanks

[jvpantin2 · Accepted solution]

Hi, @svalente9GJKH it all depends on your workflow, think there is not only one way to do such things: models can be organized by discipline (or worksets, if other criteria applies), and some categories like analytical models can be exported separately. If you ask me, the only two main reasons to have linked models are: 1, if there are different disciplines teams managing its own data and models*, e.g. by specific BEP requirements or responsibilities; and 2, if models are too heavy and there is some risk of computer overload*. If you are working alone, I may think there is no reason to separate in linked files, you'll be condemned to jump from one model to another and be realoading on every change you made in both and loose the whole picture. I'll put my bet on separate by discipline, nothing more is needed to create separated drawing sets or export data.

*BTW, all of these can be done with worksets, but there are some reasons to use links instead.

[RDAOU · Accepted solution]

@svalente9GJKH 

Having separate models for each trade/discipline is one approach you use when working/collaborating with multi-discipline 3rd parties.  However, if you are modeling everything (in-house) then splitting into several models will not give you that much of an advantage .

You can model all in one.