tag:blogger.com,1999:blog-9240097.post3984506827394632599..comments2024-03-28T14:45:49.929-07:00Comments on Revit OpEd: Local Files and other Workset ThoughtsStevehttp://www.blogger.com/profile/14230364057800484763noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-9240097.post-29468375630563822372008-06-25T09:51:00.000-07:002008-06-25T09:51:00.000-07:00I too am glad to see this being discussed. Teamwor...I too am glad to see this being discussed. Teamwork issues are critical to any shared database solution.<BR/><BR/>The inevitable improvements to Worksets should be made through the lens of collaboration across the internet via typical broadband connections. Clearly lots of optimizing will be required to reduce the volume of redundant data. But that's what Riverbed appliances do now and they are only working with the file data, not the source code. <BR/><BR/>As the internet continues it's spread toward ubiquity BIM can become a completely web based application. A service remotely hosted from a secure data center. Hey, we rent Revit as it is, right?<BR/><BR/>Ultimately this topic should be broadened to included the collaboration between disciplines. If the BIM is truly shared (both technically and legally) then doesn't it make sense for everyone (including builders and owners) to interoperate directly within a single model? The client-side tools might differ but the database is the same.<BR/><BR/>Such a vision is based on a completely different business model than the one under which Autodesk currently operates. But other companies are aggressively developing these types of capabilities. I suppose when demand for this is undeniable Autodesk will just buy the company with the most promising technology and bolt it onto Revit. Unless of course that company is Google.<BR/><BR/>Cheers,<BR/>Geoff Briggs,<BR/>SeattleGeoffBhttps://www.blogger.com/profile/01328569113469529633noreply@blogger.comtag:blogger.com,1999:blog-9240097.post-3788006168376144922008-06-24T10:45:00.000-07:002008-06-24T10:45:00.000-07:00You are right. Worksets are a pain to our users. T...You are right. Worksets are a pain to our users. They are kinda like Autocad layers! (you have to be in the correct layer to draw, etc.) Our users seem to be ok to wait for 5 more seconds than to be worrying about adding elements in the correct workset, etc.Nicholas Iyaduraihttps://www.blogger.com/profile/18007710409361967246noreply@blogger.comtag:blogger.com,1999:blog-9240097.post-88891860102309307762008-06-24T08:57:00.000-07:002008-06-24T08:57:00.000-07:00Hear, hear!!! I too have been using the world “fra...Hear, hear!!! I too have been using the world “fragile”, not that the whole concept sucks, far from it, it’s just awkward to set up. Once setup, it’s a fantastic way to work. However, as you have highlighted it should be transparent to the user and easy for the cad manager or bim manager to implement. In its present state it isn’t, which is a shame because in programming terms this shouldn’t be difficult to do. Having seen the work that Dave Baldacchino and others have shared, thank goodness for there ingenuity, Autodesk should take note. It’s funny really, because when I demonstrate and train Revit, new users just love the power of the application and without doubt the project collaboration question will always come up. When you demonstrate what you actually have to do to set this up, you can see their faces drop! For the hardcore Revit user who has gone through the pain of implementing the process it becomes second nature, but in reality it shouldn’t be as hard as that. Also, “permissions” are essential! I have seen large scale government projects that have not gone the Revit route because Revit lacked permissions and security. This is must as the product moves forward. Let’s hope Autodesk are listening!!! ;-)Anonymoushttps://www.blogger.com/profile/05609028351574557112noreply@blogger.com