My workflow is to create a reference file to hold the Revit import and then reference that into my site model. Subsequent updates to the architectural model is then easy to update. My work heading to architects for collab generally stay within the dwg and pdf realm instead of IFC, etc workflows.
A lot of line work often goes into making the drawing legible and complete in Revit (and Vectorworks) - Grids etc - and therefore you need to also request to the DWG data from model space to be able to use this for coordination in addition to IFC.
I should add here that in the context of this thread, model = 3D file. In the context of CAD generally, of which BIM is a subset, Model = 2D or 3D, i.e. modelspace and the location of the origin is equally critical in a 2D workflow as it is a 3D workflow since the two are intrinsically linked.
Bit of a bump here but do you know which of Revit's origins is the one that needs to align? As far as I know there is a project base point, a survey point and an internal origin and they may not be aligned with each other.
I suggest your aim should be to agree the basic elements of 'transfer/process' before you even start the project. Don't make any assumptions that you will match expectations back/forth - have it in writing (BIM Manual or similar to outline application) if a contract depends on it. You'll then iron-out the pitfalls.
It is good practice to align all three at the start of the project. The critical point is the internal origin. Ideally this would be aligned to the PBP and Survey Point. If the Revit users want to change the location of the PBP after, it will have no impact on coordination as the PBP is peculiar to revit.
Models must be built at the same level relative to the internal origin and a level should not be applied to the PBP in Revit unless agreed (e.g. when the buulding is up a mountain, you establish a common datum and agree that ground floor FFL = 0m in the model = 1000m AOD.
Thanks for all this, a new one for me I've been given a survey in Revit and everyone else is working Revit so I have to tie in with them rather than vice versa (Revit-centric BEP was already written). So I got the Architect to move the project base point to the internal origin/survey point because previously I only had co-ords for the PBP and no way of knowing where it was! So now I have the georeferencing and co-ords set up, but when I tried with the angle to true north shown in georeferencing it went very wrong. What I ended up doing was rotating the drawing north with the same internal origin and am hoping that will make my exports match up. Still a bit of work to do before i get to that point.
When all team members are connected to a Local Area Network (LAN), and there is a file server connected (for example: Z://FileShare) to this LAN, then the team can use this file server as the place to store the Central Model File. The picture below explains this.
To set this up (for example, at home or in a small office), you connect your computer and a NAS device or file server to your internet router. With some minimal configuration for this device (there are consumer models available, starting below $1000 for 24 TB), you will be up and running in no time. With a VPN solution, you can extend access to this LAN to users who are not residing where the LAN is located.
The schematics of working on a shared Central Model file on a WAN are shown in the next picture. Office 1 can be in Texas, whilst Office 2 can be in Timbuktu: all four computers in the schematic are connected to the Z://FileShare in Office 1.
The cost drivers for file-sharing on the WAN are a charge for network bandwidth and for the use of the storage. A rough estimate (please check with your IT department) would be $5 per Mbit of bandwidth and $0,10 per GB of storage.
You might be wondering why you need the help of servers to share the Revit Central Model file on your WAN. The reality of doing work-sharing over a WAN is that you will be sending a lot of data back and forth between the local files on the LAN to the Central Model file over the WAN. This will eventually bog down your WAN and therefore your users. The solution that Autodesk has developed is called Revit Server. The software that is required to set this up is entirely free of charge.
The cost of this setup is a set of additional servers for each LAN. Although Autodesk provides this software for no additional cost, this solution will have some additional costs over file-based WAN. An internal IT department will typically charge more than $1000 per server per month to keep this machine up and running. Assuming 20 users per accelerate server, this adds an additional $50 per user, per month.
Designair provides high-end virtual desktops for architects, engineers and designers, and we recently added a FileShare service to our portfolio. This service is a shared drive that lives in the cloud, and is connected to Designair's virtual desktops.
This functionality of the FileShare service is comparable with the internal File Server (options 1, 2 and 3). The major different is that it is available in the cloud. It does not have the bells and whistles of BIM Collaborate (such as chat options), and it is only available with a Designair virtual desktop.
The second scenario is the support of flexible work policies, and environment where users can work from the office as well as work from home (WFH). Depending on several factors, either an on-premise or a cloud-based scenario have their merits.
The simplest, most affordable option to work with the Revit Central Model File is clearly on the LAN. In combination with a VPN solution it is still viable for WFH, but VPN does add costs (about $20/month per user) and at some point you will run into performance issues, especially at peak hours.
If you already have a WAN in place, and your organization can not or will not move Revit files outside its own premises, then this is your best option. If you run into any performance bottlenecks, you can extend the usefulness of your WAN setup with Revit Server. With a VPN, you can extend the WAN to WFH users, with the same caveats as for the LAN.
In comparison with WAN-based collaboration, BIM Collaborate is definitely more affordable, and offers more capabilities beyond file-sharing. But it is out of bounds if your company can not or does not want to have its Revit files in the cloud.
I recently started at a new company, who has always managed their Revit projects with a by-the-seat-of-our-pants workflow. As far as I can tell, they've always just downloaded other trades' models, linked them in locally (or used Vault, which I didn't really even realize was possible), and never really done a TRULY collaborative project. Until I came along and started working on projects in the cloud, with desktop connector, linking in the live models, etc. And we're getting into REALLY large projects, where this workflow is mandatory per contract.
Well, they asked me to start working on a model for a project they've had for a couple of years now. Not a problem until I realized that the entire project is being done in Revit 2018 (my subscription doesn't go back that far), is using BIM 360 TEAMS (which is SERIOUSLY no longer supported), and requires the C4R plugin (which is no longer available). Yes, I've asked if they were going to upgrade to a newer version and collaboration platform, but they seem to be in no hurry as Autodesk is literally suspending sunsetting 360 TEAMS for this client so they can continue working like this. If I told you what the project was, you'd understand why.
Now... my question is... how the **** do I do this? We have ONE person that still has access to 2018 with the collaboration plugin, but she doesn't know how to model. Literally the only thing I could think of would be to create a virtual machine on her CAD computer that I could come into and use her setup. But that seems RIPE for issues.
Collaboration for Revit (C4R) is Autodesk's answer to cloud-hosting of a Revit workshared model. Utilizing cloud storage and your Autodesk ID, Revit files are stored and shared through the cloud with users both within your own network and outside with other organizations, stakeholders, and other users. Integrated with AutodeskBIM 360Team, Collaboration Revit enables entire project teams to access shared building information models. A subscription to Collaboration for Revit includesBIM 360Team. Here are a list of the top things you need to know when creating, accessing, sharing, and utilizing a cloud-workshared mode in C4R.
You should note that 1) Is the newBIM 360Team logo that takes you to the cloud where you can find your Team Hubs and 2) is a listing of your Team Hubs. Once you select the appropriate Team Hub, double+click the appropriate Revit Model and click 'Open'.
Collaboration for Revit is a wonderful feature for project teams looking to expand their worksharing capability to the cloud. If you're looking for a replacement for Revit Server, Collaboration for Revit is it. If weekly file updates are holding the project back and your project teams from making timely updates and design changes, Collaboration for Revit will certainly help. By centralizing the Revit Model, Model updates, Design teams, and providing a Hub for all design team members to work in, C4R pushes cloud-based collaboration and communication for design teams to further heights.
Autodesk Revit Collaboration Suite made its debut today at the American Institute of Architects [AIA] Convention in Atlanta, Georgia. Revit Collaboration Suite is a new pay-as-you-go offering that provides architects, engineers, and contractors with a more flexible, lower cost entry point to BIM workflows. With the latest releases of Autodesk AutoCAD and Autodesk Revit software, plus Autodesk A360 Team cloud collaboration software, the suite provides the essential tools for collaborative model-based building design.
92d504bec8