Revit should allow you to create worksets even when a file is not collaborative or workshared. They essentially break down the project into layers and this function shouldn't be tied to just workshared files.
Not to be a semantics nazi but I think we should refrain from liking worksets to layers because layers have a lot of mental luggage attached to them from 2D CAD days. It's hard enough to get some of the older, err, I mean more experienced folk, to come to grips with BIM. Making them think that Revit is like a fancy 3D version of Autocad just leads to continuous misunderstandings and under-appreciation of the tool.
Having said that, I wholeheartedly agree that worksets should be available all the time. They are a great way to partition a project into, how should I say it, "sets of work"
I find the colour representation of worksets particularly useful on large projects. I use this all the time when I'm moving elements between worksets. For example, moving all bits of furniture to their own set or joinery items, etc. It's really useful
I agree with tomek. If you're using Worksets for Visibility control, you're using them wrong.
That said, why not just enable Worksets if that's what you want?
Where's the upside of having Worksets, but not Workshared?
What's the downside of just making it Workshared?
Anonymous
01-23-201807:24 AM
01-23-201807:24 AM
As a student I am using worksets for file management primarily. The ability to only load and work on parts of the model is extremely beneficial and should be available regardless of whether you are workshared or not. As someone without a server, the need to create a central model is extra time and space is just unnecessary.