workset/work sharing

[mj_lampad@yahoo.com]

Does Anyone could share me the essence of using workset/worksharing and the proper method of executing it. because until now I couldnt understand how to use workset eventhough I read some material regards on it.

Does workset/worksharing can be done in one unit or must be in network or different computer?

thanks

[benmay]

Technically you don't need a network to use worksets/worksharing.

As a quick summary, enabling worksharing is done when you activate worksets

As a default Revit will place all grids and levels onto one workset and all other elements onto a default workset called "workset1"

From here when you next save, a message will note that your file is now a central file

This is now a sort of master file

You could continue to work in this file, and when saving you will only be able to select the syncronize to central button instead of the save button

So now that you have saved the file again, and you have a central file. The central file takes note of its location. If you were to move the file, it would then become a local file, you would be noted this in a message when opening the moved file. It would note something along the lines of "you have moved this file, it will now be a local user file..."

You would then have two save options, save (save local) and sync central, so a user can work away saving local at regular intervals to backup their work, then they can Sync Central at other intervals updating the "Master File"

By opening this local file, you can then allow other users to open their own local file which is how worksharing operates. But this is were you would need to Central file to be saved on a server or a shared computer at a minimum so that each user can access and sync to the central file

I wont go into worksets in great detail, as the help file does cover worksets reasonably well, but so long as the local file is only opened without the entire worksets checked out as editable, you dont need many worksets for each set of elements, as users can check out elements "on the fly" by borrowing elements as required

Where breaking your project into worksets is useful is when you would like to have additional control over groups of elements. This can be useful for groups of elements like site works, which you would set to a workset, which will allow you to turn them off in particular views, or even open your project without that workset loaded, which should improve model performance as well


Hope that clears things up a little, its pretty simple once you get into it.

Cheers