Using the BIM 360 integration you can import Revit models directly into Arkio without having to open Revit on a PC. This way you can always access your team's latest Revit models from any device such as the Oculus Quest, tablet, or phone to plan a quick virtual meeting and to explore new ideas that can be exported back to Revit.
Linking BIM 360 to Arkio
After downloading Arkio on your devices and adding our BIM 360 integration to your portal (see bottom of this page for detailed installation instructions) you can use our BIM 360 portal to log in to Autodesk and give Arkio permission to read and save new files on BIM 360 on your behalf.
To limit our access to your files on BIM 360, Arkio opens Revit files in read-only mode when receiving an export request and only saves a new Revit project in the user-defined path if a model is exported from Arkio back to BIM 360. Existing files on BIM 360 are not replaced or overwritten in any way.
Once logged in you can link your BIM 360 to Arkio using the top right "Link to Arkio" button. This will open a dialog with a 6 digit authorization code that can be used to connect the apps. This code can be filled on any of the devices with Arkio running by going to the Create/Import/BIM 360 tab on the expanded create drawer or from imports on the model's viewer.
When Arkio and BIM 360 are linked you can see and download the models that have been exported and place them in the scene for everyone in the meeting to see.
You can also view all active jobs exported that day using the "Export Status" button on the BIM 360 portal. This will show the export jobs you have activated in the last 24 hours and some statistics for the status and time the jobs took to complete. Please note that exported files will only remain available for 24 hours, after that they will need to be exported again.
Exporting from BIM 360 to Arkio
Once Arkio has been linked to BIM 360 you can export models from the BIM 360 portal by selecting a Revit project from the project browser and clicking on the green Arkio icon (2) in the bottom right corner of your viewer.
When you make an export from BIM 360 the model we will look for a 3D view called "Arkio" (with or without capitals) if this view is found in the project that views visibility settings, and section box will be used to make the export to Arkio. If no view with the name Arkio is found a default 3D view of the project will be used instead with all Revit categories and objects visible.
If you are working on large Revit BIM 360 projects we recommend preparing an "Arkio" 3D view in your model with appropriate view settings, furniture, entourage, and railing categories hidden, and a section box around the part of the building you like to export so your models will be able to load on mobile devices and VR.
Once in Arkio, you can see what jobs are being processed (this could take a while for large models) and what models are ready to be downloaded to your device. When you click on the "GET" icon that model will be downloaded from the server.
Once this model is downloaded the "GET" Icon will change to "RVT" And that model will be prepared for Arkio after which it can be placed and updated like a regular Revit model on your table. You can go back to the local tab (PC icon) to open this file and place or update the model on the table.
Exporting from Arkio to BIM 360
You can also export your Arkio models back to BIM 360 once Arkio is linked to your BIM 360 account. This is useful when you don't have access to Revit but still like to provide the team with a Revit file with all the geometry you created in Arkio, or if you would like to export several design options to link and compare into your Revit worksharing project.
To set up the default folder for your Arkio export you can log in to the Arkio BIM 360 portal and select the desired project folder on the left side of the page. With the preferred folder selected you can click on the top "Set to currently selected" button.
When you export a model from Arkio to BIM 360 it will appear with the name "Arkio_(timestamp)..." placed in the selected export folder on BIM 360. It's currently only possible to convert Arkio creations to generic models in Revit files using this approach and we plan to add other export settings later.
The resulting files can be downloaded as an RVT file to be linked or bound to the main Revit worksharing file.
If you're unsure if you have admin rights you can check if you have an Account Admin button under your BIM 360 Docs portal. If you don't have this button you likely don’t have these rights for your organization and you need to send the above instructions to your account admin.
Once on the Account admin page, you can add apps and choose Arkio. We will ask for your permission to read and add user-requested Revit files.
Our integration only reads BIM 360 files for viewing models in our portal and opens Revit files as read-only when the user makes exports of the latest Revit central model to Arkio. We don't make any changes to your original files and only add new RVT models in the user's BIM 360 docs when they make an export from Arkio to BIM 360.
Once you have the integration installed all users of your organization can log in to their Autodesk account on the Arkio BIM 360 portal and link Arkio to their BIM 360 projects using a personal code (see the top of this page for more instructions)
Known issues for our BIM 360 workflow:
- Models exported from BIM 360 will be cleared from our server after 24 hours (local imports will remain in Arkio)
- All categories, Worksets, and visible 3D elements will be exported unless you save and publish a 3D view in Revit named "Arkio" with the required visibility settings
- Large and complex models will take a longer time to export and could fail, we advise starting with smaller projects first
- If a model is saved in Revit 2018 or earlier it needs to be updated first, this will result in long export times
- Custom (Non-Autodesk) textures will not be included in the export
- Export back to BIM 360 is missing some features supported in the latest Arkio Revit plugin (masses, loading of custom families, parameters, and materials)