Worksharing Monitor was created as a separate application and originally made available at the Autodesk Subscription site back in January 2008. I mentioned it in THIS POST and also mentioned that David Light had put together a nice summary of its features on his blog.
What is it intended to do? Provide more information to a team using worksets, such as when files are out of date or when an editing request is generated.
Flash forward to the present and I still find that few firms are aware of it, or if they are, actually using it routinely. This makes me wonder about how effective the delivery of the tool is. Users might be aware of subscription and that there is a site at Autodesk for it. Fewer users actually have access to it or are able to download from it. Since we are talking about a separate software installation that means we are asking an IT department, for any firm large enough to warrant having one, to get it installed. It might be more effective to have it installed as part of the Revit deployment itself.
When I first saw the tool I imagined it was a perfect example of Autodesk using its own Revit API (Application Programming Interface) to deliver features apart from the primary code for Revit. A faster way to deliver features because it didn't rely on a formal release cycle or planned development to get it done. Said another way, a rogue solution that could ultimately be incorporated into Revit itself. That bit hasn't happened so far and I suppose that having it separate give us the choice to use it or not.
If you use worksets for your projects and would like to improve how you interact with Revit as a team then you and your team should be using Worksharing Monitor. If you aren't using it I encourage you to look into it and see what is preventing it from showing up on your desktop.
It isn't perfect however, for example, if you are using Remote Desktop Server it doesn't support that kind of connection at this time. I have also heard about some issues with latency, where it doesn't update as quickly as it should. Overall however it has been a benefit to most everyone I've met that IS using it. I personally prefer to be able to use it when I'm working with a group.