Worksets and Multiple Buildings

[nsinha73]

We have a Site that has Multiple buildings...Right now we have just one workset....I want to Separate each building into its own Workset....eg. Wing 1, Wing 2 and so on.
By Doing this, would we be able to improve performance as well work flow?
We have been using Revit for couple years but this is the first time I am trying to implement Worksets
Your response and Solution is highly appreciated, thanks guys

[Andre Carvalho]

You mentioned about multiple buildings on a site file. Usually I would have one file as the site, then each building as a separated file and each file with their worksets. Then I would link and position all buildings into the site file and publish the coordinates from the site file to all linked files. This will definitely improve performance.

Andre Carvalho

[bbeck]

I live and die by worksets. Large projects need it. If you're worrking with other members of the design team using Revit they can link or not link individual worksets. This lightens up their model also. Opening a project with selected worksets improves performance.

[twiceroadsfool]

Worksets are great, and i use them religiously on just about every project. Yes, if used in a good fashion then will improve performance and workflow. If used poorly, they will be a hinderance, a headache, and will cause problems.

That said, for multiple buildings i use File Links AND Worksets. Then i pick one building to have the "Drawing Set" in it. (Assuming its all one set of documentation). If its multiple sets, then i would DEFINETELY use File Links, without question.

[nsinha73]

I am not a fan of Linking....but I believe that if done properly, it is definately a benefit. But for now I will go with Worksets....4 Buildings, each building in its own workset.

[twiceroadsfool]

I went that route on a large project once. Once it got large enough, it really stunk, even with the worksets...

1. Is it all one set of drawings? Or multiple sets of drawings?

2. The actual worksets: Consider how you might break up the work. Having worksets to delineate buildings is fine, but you may want to segregate it more than that too, depending on the complexity of the programs, etc. Or are they just empty shells? You may want:

Bldg1-ext
Bldg1-int
Bldg1-struct
Bldg2-ext
Bldg2-int
Bldg2-struct

[nsinha73]

Hi twiceroadsfool,
Right now I have set it up as Each Building in its own workset....The guys (Architects) in my Office wants to work in Each Building at a time.....I simply don't want to create more learning curve for them....I have pulled enough of my hair listening to their complains :-D

Where can I find detailed Tutorial on Linking? I can give a try.....

Thanks!!

[twiceroadsfool]

The best information on it is available here, in my opinion. Search for it, weve had TONS of threads on the benefits and caveats of File Linking.

FWIW, the learning curve wouldnt be all that different. If it were me, id put them in Links. But, thats my piece. :)

[ajayholland]

Unless these are very simple buildings, each one should be a separate file, and coordinated through a separate site file. Worksets in each building file will provide the opportunity for improved performance.

Don’t worry about the learning curve. Assure your users that these techniques are simple, logical, and aligned with the ‘best practice’ of seasoned users.

Where in California?

~AJH