We are really hurting in our office with a "protection" issue. Not sure how else to describe it. Here's the deal...
We are, (for now), a team of 3. Our company builds modular buildings. We have decided that the best way to build our Revit models is to construct them the way that our plants/ factories would build them, or as closely as possible. Therefore, we have framing, walls, MEP, etc., essentially everything, all in one model. ** The problem ** As we progress deeper and deeper into the Revit models, we are running into an issue where one of our users is not paying attention as closely as they should. For example, let's say this person is working on MEP ONLY, somehow they are moving the walls and framing around when they should not be doing so. Is there a way to protect each entity or items on certain worksets so that they cannot accidentally be tampered with? If you know of any posts or blogs that are out there that could address this issue, please send me the link. I appreciate the help!
Your best bet is to have each user check out his/her Workset(s) at the beginning of the day. That way, each user immediately claims ownership of the respective elements. One could even go so far as to check out specific Views as well. Now, if you want to take it a step further, your users can opt to even keep ownership of their Workset(s) after syncing and closing the Project. Use that method with caution, though.
The downside to this is that each user must remember to work on the appropriate Workset! When a new local file is created, The current Workset is retrieved from the Central file, being the last active Workset of the last user than synced. This is the motivation for this post of mine in MEP Wishes: Default Worksets
one simple way is to simply check out the worksets you don't want changed. some customers will change their user name to "admin" or "locked" (or something else creative) and check out some worksets they want to "lock". Then save and don't relinquish those worksets, chage the user name back to your normal user name, and go back to work. Any item you don't want changed will be checked out and unable to be modified.
I figured this was the best way to do it, but you are correct, the downside is that you have to rely on that user to remember to check out only their workset and since we can't seem to get this user to do anything the same way twice (disorganized and chaotic!!) then I don't have confidence that our problem will be solved. It may be the temporary fix, however, until the situation can be resolved.
You're probably going to disagree with me on this ... split your files based on disciplines or even sub-disciplines. Your file size might be small (like if you have a 10'x10'x10' shack) but you're guaranteed that your stuff is safe and the only way for someone to sabotage your stuff is for them to go to your files and change stuff in them. There are other great benefits for splitting up files other than sabotage (accidental or deliberate).
In response to worksets: as long as you rename the default "Workset1" to something like "Mechanical Piping" or "Fire Protection" in your split up files, you're good. No need to create and keep track of a bunch of worksets when you got what you need in that file as default and most likely your only workset. Worksets are too clunky and require additional monitoring.
General rule of thumb is not to rename Workset1 as there are many system elements assigned to this when activating worksharing. Also, there is strong suspicion in industry that by renaming this workset and modelling elements within it, you run the risk of elements "moving" to non-editable worksets (such as Project Information, etc.) and partially corrupting your model.
Perhaps you should use one model for two users and then keeping the other user's file linked in. You may wish to bind the linked file at the last minute but that may not happen without some issues. Alternatively punish the other user until they work in a co-operative manner???
Start with some of our most frequented solutions to get help installing your software.