method of working on a large project

[Anonymous]

what I'm doing in a file I have the model in another file I have the document and another file I have plans, but what I want is to avoid having a long list of layers and elevations, where loss of control of the project, as it should be the best method?
each discipline working in a different file?

[dhaval7shah]

you can organize all the things; Model, Drawings and detail documentations - all in a single file.
Make use of Hotlinks to make the file lighter and smart linked.
Link the libraries instead of embedding objects.

If your files take much time in layout regeneration, then...
-> you make a separate file to gather the documentations (viewmap drawings) from different files.
I this file you should compose your layouts (having the external viewmaps) only.
(however this is a quick tip, but still there are many things me and other users can write here, i will right more on this sooner)

[Anonymous]

Hello,

dhaval7shah wrote:
Make use of Hotlinks to make the file lighter

Just a side note - hotlinking might be useful, but it does not reduce the file size.

Thanks dhaval7shah anyway for your comments.

[Link]

dhaval7shah wrote:
Link the libraries instead of embedding objects.

And please, what benefits have you discovered to this method?

Cheers,
Link.

[dhaval7shah]

Juha wrote:
Hello,

dhaval7shah wrote:
Make use of Hotlinks to make the file lighter

Just a side note - hotlinking might be useful, but it does not reduce the file size.

Thanks dhaval7shah anyway for your comments.

Hello Juha,
Let me correct you. Hotlinking saves file size, when you place more than one same hotlinks in a file.
e.g.
-> case 1: If without hotlinking, you copy the same 'Bungalow model' 100 times, the file size becomes approx. 100 times the single model file.
-> case 2: If you place a module of a 'Typical Twin Bungalow model' and repeat (copy) it 100 times in the same file. Then the file size will be approximately same as the module's file size.
Because here, the mother file remembers the module's model elements' info only ones. And then for every copy it has to remember the location, elevation, orientation and layer info only (not the whole model info again and again, bcz it is linked).
This way it saves file size.

Please let me know your comments on this.

[dhaval7shah]

Link wrote:

dhaval7shah wrote:
Link the libraries instead of embedding objects.

And please, what benefits have you discovered to this method?

Cheers,
Link.

Hi Link, keeping Embedded objects occupies memory for all saved objects in the file, and linking will save your file size and complexity.

Also while working in TW13 or 14, every member can link libraries normally or from the BIM server, this saves the huge amount of local memory.
And it eliminates the updation issues of objects (after sending and receiving operation) for every member.

I experienced it highly beneficial for the TeamWork in reducing size and thus saving time.

The Other benefit is in a very large company, Group members can link the libraries from a single location, which might be updated every few weeks.

Thanks for you question.
Cheers.