There seems to be a lot of questions and excitement about the new Revit Server extension out there. Today, I'd like to talk about some of the differences between using Revit Server and using the typical file based worksharing method.
Here are 10 things that are different about Revit Server. I'd love to hear what you think of these.
- Creating Local files - The only way to create a local file from a Central model on Revit Server, is through the Revit open dialog. You cannot create a local file using Windows Explorer or any other way other than the check box to create new local. This means that any scripts you have for copying a central file to create a local file will not work with Revit Server.
- Editing Request - With a project using Revit Server, the Editing Request button is grayed out and not available.
- Worksharing Monitor - With Revit Server, in part because editing requests are not available, the worksharing monitor will not function to give you notications about the model. To handle times when you would normally place a editing request, you can use a Instant Messaging Application to communicate with others on the project.
- Working at Risk - Otherwise known as taking a local file home and working on it and being able to bring in back and syncing with center, is not fesible with a Revit Server project.
- Thumbnails of the Central Model - When you are creating a local model or opening the central model from Revit Server, thumbnail previews are not available for the file.
- No right click in the open dialog for the Revit Server - Unlike the normal open dialog in Revit, you will not be able to right click within the Revit Server window. Also, the meta data available on a central model in Revit Server is limited to only the Name, Type, and Date of the file.
- Folder Management must be done with the Revit Server Adminstrator - You must use the adminstrator to create new folders, move or copy/cut/paste projects for Revit Server. These options are not available via the open dialog in Revit.
- Overwriting the Central model - Perviously it was possible to save over a central file using the same name, with Revit Server, this is not possible. You must save the central model with a new name or delete or rename the orignal central model.
- Recent Files List - Only Local files will appear on the Recently used files list for Revit. Central models will not appear.
- Restore Backups of Central - You cannot roll back to a backup of the Central file using the Restore backups tool within Revit. Local files can be rolled back to a previously saved version, but Central Models cannot.
Revit Server worksharing is about sharing models across a WAN with mutliple offices. Typical file based worksharing is still available for use if you feel it is the right option for you.
To get a better idea about Revit Server, check out this video:
Harlan,
I know this is the first release for this, but many of these seem like steps backward. Notification is one that we see as critical especially when over a WAN. Many companies block IM so that may not be a solution.
Since many people use the borrow function, how do users edit elements that are in other users worksets? Has borrowing been disabled in the server?
Posted by: Chris Hubbard | October 01, 2010 at 12:16 PM
@Chris,
I'm surprised that your own company does not have internal IM. On top of that I would highly recommend for anyone attempting a collaborative project between multiple offices that the team needs IM. Our teams regularly rely on IM to facilitate communication about the Model and Project, particularly when working across offices. Phone is not good enough because it can be disruptive and is "synchronous", e-mail is too "asynchronous", therefore the sweet spot is some type of IM client, particularly one with chat rooms and group history (like Skype). Something like Skype is even more critical if you are collaborating live with other firms on the same project.
Regarding borrowing, yes you can still borrow elements, but if you run into overlap the other person will need to SWC and you will need to reload.
You'll also note that in the blog-o-sphere the word "Bluestreak" has come up in relation to Rvt Server. Hopefully your company does not block that site too.
Posted by: Robert Manna | October 01, 2010 at 12:41 PM
I applaud the first step taken, but it leaves me waiting for what the next step will be.
For us, the use case that desperately needs solving is that of staff working from home (or other location). In this case, working on a Revit model via a vpn, is simply too slow. A server managing permissions could potentially reduce the network usage to make this viable, and would be a big deal for us. But needing a server at both ends is not tenable for out-of-office users.
I know this is an issue for other firms as well as ours, so I hope that it is on Autodesk's to-do list. Rdp sessions to computers within the office are a poor substitute for working on your local machine, especially when your local model has all the information needed.
Posted by: Joel Osburn | October 01, 2010 at 04:54 PM
I'm very interested to know how the system deals with linked rvt files and linked non-revit native files, i.e. dwg, skp and sat files.
Also, does the drive mapping in each local office need to be the same?
Posted by: Brian Renehan | October 02, 2010 at 09:33 PM
My above questions have been answered by Robert here:
http://forums.augi.com/showthread.php?t=124364&page=2
Posted by: Brian Renehan | October 02, 2010 at 09:59 PM
Would Revit Server work with consultant models? I can imagine instant messaging a consultant to move a light fixture, mechanical duct, etc. Coordination issues could be fixed on the spot and we could see changes instantly.
Posted by: Brian | October 04, 2010 at 09:54 AM
Hi Everyone,
Thanks for the great feedback and comments.
Robert, we really appericate the comments about using IM tools on a large project. Its great to hear about using the tools in the world. I am sure our reader apperciate the insight.
As for Revit Server with consultants, I would think the trick would be getting them setup a local server on your domain so that they can access your central server. I am not sure how the permissions would work, but I am not sure if you would want to be able to give your consultants access to your network and server. If you could though, I don't see why they couldn't act as just another office working on the model.
Curious to see what anyone else thinks.
Thanks again for all the comments :)
Posted by: Harlan Brumm | October 04, 2010 at 10:03 AM
Re: working with consultants, attend (or watch at a later date) my AUv course this year.
I can't give away all my secrets on blogs and fourms, right! :-)
Posted by: Robert Manna | October 04, 2010 at 01:14 PM
/*
Editors note: This comment has been removed as solicitation.
*/
Posted by: Laszlo | October 07, 2010 at 03:52 PM
Security, How's secure of the connection between Local server and Central Server? I.e. Virus, Malware infection, etc.
Required Windows Sever 2008 only? How's bout other Windows product like Windows 7 or XP? Most of the contractors don't have or can afford Windows server 2008.
Posted by: Tim | October 07, 2010 at 07:29 PM
We've done some testing @ABT in the Netherlands. Our company exists of multiple offices, each ofcourse with their own IP-subdomain. Master en local servers works great within/between our offices.
However, we've been trying to connect another local server to a master server located at an architects office over internet. It's impossible to connect from Revit to this second local server that resides on the same subdomain as where our own master server is located...
Can anyone tell if there is a solution for this situation?
Thanks in Advance,
Richard Fielt,
ABT, The Netherlands.
Posted by: Richard Fielt | October 29, 2010 at 09:59 AM
In relation to the post above, some additional info about the used IP domains. I really hope that some-one could tell me if it's possible or absolutely not (yet?)
For 'internal use' we installed a CS in IP-subnet (172.19.0.0/16) and a LS in IP-subnet (172.16.0.0/16) for two of our three offices. That works just fine (ofcourse).
But.. we also installed an LS on IP-subnet (172.19.0.0/16, same as our internal MS) which connects to a CS over internet (collaboration with external architect). This LS can't find the external MS..
Maybe you've got a hint with which we can make this work? Thanks in advance for your reply!
Posted by: Richard Fielt | November 03, 2010 at 05:09 AM