Revit Collaborate Tab

[Cassaundra Marley]

Forstarters, I am the account administrator, the project administrator, and I have all the access permissions. I have set up two projects, and can see/upload/edit all this in the Desktop Connector app as well as seeing these uploads going into the BIM360 Docs folder structure.

The problem is, when I select 'Collaborate in Cloud', the only place that comes up is the top level folder of BIM360 and nothing else. There's none of the folder structure I was expecting to see, and thus I can't collaborate on the cloud.

I also have no idea how to associate a BIM 360 project with any variation of Revit (18, 19, 20, 21...). How could I check that this is not the case?

I have set all these files up today, with no other versions of Revit installed on this pc.

When setting up the projects, it's possible they may have not been set up for Revit2020 i.e. if it was setup for 2021 it won't appear in any version other than Revit 2021. Somewhere you can specify the Revit version you need when setting up the project (I don't know where, as I'm not a system admin on my end, but I do know it can be done). I don't think you can roll a project back on BIM360, but you can roll it forward if it was inadvertently set up for 2019, should be the same process as was described in the previous link (maybe this is a good way to check which version you're on, too).

I have created a new project in BIM 360 Docs, applied all the permissions, teams, companies, everywhere that I can tick a box or fill in a form I have completed. However, In Revit 2020 I can only see the BIM360 top folder and no projects in there.

You'll have to get a copy of Revit 2021 I believe, since you are on an EU server. From what I've seen online, the EU server only supports R2021. -products/troubleshooting/caas/sfdcarticles/sfdcarticles...

We were somehow signed up to the EU data centre which only supports Revit 2021. The technicans at Autodesk either moved us from the EU data centre to the US one, or refunded our licenses and moved us over.

I am able to collaborate in the cloud in Revit 2019, not in 2020. My co-worker can use the collaborate function successfully in 2020 using the same file I am working on. I have tried different models, I have tried making a brand spanking new fresh model. I have uninstalled revit 2020 and reinstalled. I have checked and double checked and triple checked my access and permissions, and I have them all. I have logged out of Autodesk, rebooted and logged back in. I can open revit 2020 projects that are workshared on BIM360. I can see and access all projects hosted on BIM 360. To make matters more frustrating and confusing I used to be able to do this function. I've done it many times. I tried running the collaborate function with revit 2020.2 and then upgraded to 2020.2.9. Desktop connector is up to date (15.8.0.1827).

Thank you Lance.Coffey! I don't know how you found that info, but thank you! That was the culprit. I somehow installed that Publish NWC addon when I was installing a bunch of autodesk updates. It's removed and things are back to normal. Wish I had found you yesterday.

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.

I want to reinforce, for example, the level 1, that I'm the owner of the work set. When I put the reinforcement in a column I must ask for permission from the owner of the above level (level 2) in order the rebars to pass through the slab (level 2).

When you don't own worksets but only elements, you will encounter a lot less requests. You automatically become owner of an object if you edit it. Just synchronize regularly, it will be much easier to collaborate.

Taking ownership of worksets is a way to prevent people from making changes to the elements on that workset. It is not usually a part of a daily workflow. Worksets were not really meant to be used for visibility. While it is a convenient way to handle visibility, it is not recommended. It's my understanding that they were designed as a way to "check out" parts of a model, so that someone can work on them while not connected to the central model and block others from making any changes to them so that there are no conflicts when those objects are synced back to the central mjodel.

It's my understanding that they were designed as a way to "check out" parts of a model, so that someone can work on them while not connected to the central model and block others from making any changes to them so that there are no conflicts when those objects are synced back to the central mjodel.

This is "kind of" true. When worksets were first introduced you did have to check out an entire workset and other users were able to request permission to edit one element at a time like now. The real difference was sometime after worksets were first introduced, "active borrowing" was added. This is what allows you to check out/borrow something that is not "owned" by someone else automatically, on the fly as you work. Prior to "active borrowing" you had to more explicitly "check out" what you were going to work on ahead of time.

So worksets were not designed for working on the model in a non connected state, they were created so more than one person could work on the model period. You don't even want to know the system for multiple users prior to worksets. Worksets were also NOT intended for visibility control. They can be used this way, but I would not recommend it. Not loading a workset is more about memory load and model performance rather than controlling what you see and don't see.

To collaborate on Revit models in the cloud using Revit Cloud Worksharing, each user must be given access to Revit Cloud Worksharing. While this topic speaks specifically to Revit Cloud Worksharing, the same procedure applies for the Collaboration for Civil 3D and Collaboration for Plant 3D entitlements.

There are two ways to provide individual users access to products. If you are providing access for an individual user, it is easiest to add By User. If you are providing access for mulitple users, it is easiest to add By Product.

Attention should be paid to adopting existing or developing new BIM standards. If standards have been used loosely or there were very little common practice rules, the company should hire or consult with BIM professionals and implement things like project folder structure, modelling methodology, etc. (See Tables 1 & 2). It is also important to comply with existing BIM mandates relevant to your country. The guidelines in AEC (UK) BIM Protocol, for example, are laid out clearly and are quite useful when it comes to organizing your work effectively.

Use the default or define custom Project Templates to enforce office standards, so that every time you begin a new project from the template, you will already have some key information consistently in place.

All this can also take place on a local access network (LAN) and work exactly the same way, just that it would be local to where the server is, typically somewhere in the office. The content of files and folders stored on the server might resemble the folder structure as seen below.

Working with Revit links is a great way to separate AEC disciplines and perform interdisciplinary coordination between design teams. It does, however, require exchanging BIM models regularly. Once the links are loaded and graphics/visibility options are set, it is convenient to explore how different systems would work together and foresee potential issues or clashes between elements.

3a8082e126