VitruAI + BIM 360 / ACC
The VitruAI + BIM 360 / ACC integration authenticates against Autodesk Construction Cloud and reads/writes cloud-hosted Revit central files, ACC Docs, and ACC Issues through Autodesk’s Forge/APS APIs and the Revit cloud worksharing API. It supports BIM 360 Docs, Design Collaboration, Model Coordination, and ACC Build hubs, and is currently shipping with 1–3 design partners on ACC-led projects using the same agents as local Revit workflows.
- Cloud Revit access — central files in ACC read and written through the same Revit add-in path; agents see the same workshared model and worksets the team sees in Revit.
- ACC Docs + Issues integration — agent findings written back as ACC Issues with attached viewpoints and element references; comment thread continuity and audit history preserved across design iterations.
- Federation-aware — Model Coordination clash test results read and used by the Clash Review Agent, so prioritisation respects the same federated sets used in coordination meetings.
Install, authentication, and what runs through the integration.
-
APS-authenticated workspace
A BIM 360 or ACC admin grants the VitruAI workspace per-hub authentication via Autodesk APS, using a standard OAuth app key and project-scoped permissions. The integration acts as a project member, not a tenant admin, so it only sees the hubs and projects you explicitly authorise. Token refresh and APS app maintenance are handled by VitruAI, with audit logs available per workspace.
-
All cloud-hosted Revit central files supported
VitruAI connects to cloud-hosted Revit central files in BIM 360 Docs, Design Collaboration, ACC Docs, and ACC Build using the official Revit cloud worksharing API. Any VitruAI agent that works with local RVT files through VitruAI + Revit runs against these cloud centrals with the same add-in ribbon, view filters, and workset handling. Worksharing status, element ownership, and pinning are respected so agents do not override active user sessions.
-
ACC Issues round-trip
When the Code Compliance Agent or the Clash Review Agent finds a problem in a cloud-hosted model, the integration posts an ACC Issue with the correct type, location, and viewpoint. Issue titles include rule IDs or clash IDs, and descriptions include element IDs for direct selection in Revit. Designers respond in ACC; VitruAI reads the same thread on the next run and updates status instead of spamming duplicates.
-
Model Coordination integration
Existing Model Coordination clash tests remain the source of truth; VitruAI reads the clash results instead of creating its own tests. The Clash Review Agent pulls clash groups, involved models, and status from Model Coordination, then triages them alongside Navisworks integration outputs where firms still run desktop coordination. This keeps ACC-led coordination aligned with MEP clash review workflows already in place.
-
EU and ME tenant regions
VitruAI workspaces can be pinned to eu-central or me-central regions so workspace-side data residency matches firm requirements, while ACC hub data remains in Autodesk’s chosen region. Only the minimum metadata needed for agents to run leaves ACC; RVT geometry is streamed through the Revit API rather than bulk-exported. Region choice is set during onboarding and can be split by workspace if you run both EU and ME practices.
-
Same agents, cloud location
All live VitruAI agents that work with local Revit files — from the Code Compliance Agent to the Clash Review Agent — run unchanged when the central file lives in BIM 360 or ACC. The integration treats ACC as another file location, so rule libraries, clash templates, and QA/QC checks behave identically. This lets firms move from desktop to cloud Revit without rebuilding their automation stack.
BIM 360 / ACC integration FAQ
-
Does this require an APS app key from Autodesk?
Yes, the VitruAI workspace uses an Autodesk APS app key so it can authenticate to BIM 360 and ACC hubs as an application. An ACC or BIM 360 admin completes a one-time consent flow per hub, which typically takes ~15 minutes including internal approvals. After that, new VitruAI agents and workflows connect to the same hubs without additional setup per project.
-
Does it work with the older BIM 360 hubs?
Yes, VitruAI supports BIM 360 Docs, Design Collaboration, and Model Coordination hubs as well as ACC Docs and ACC Build on the same code path. Mixed estates where some projects live in BIM 360 and others in ACC run through a single VitruAI workspace. This lets firms standardise on one automation layer while they gradually migrate from BIM 360 to ACC.
-
Can VitruAI write Issues without admin permissions?
Yes, VitruAI posts ACC Issues as a project member, so it only writes to projects and folders where it has explicit access. Permissions follow the same team member model your coordinators and discipline leads use, and no tenant-wide admin role is required. This keeps [vitruai for bim 360 acc] aligned with your existing governance while still allowing agents to create and update Issues as part of QA/QC runs.
-
How is this different from the local Revit integration?
Functionally, it is the same agents and checks; the difference is that the RVT lives in BIM 360 or ACC instead of a file server. VitruAI + Revit covers local and network-hosted central files, while this integration targets cloud-hosted centrals in Autodesk Construction Cloud. Firms with hybrid setups often point the same agents at both local projects and ACC projects during a transition period.
-
What does the Beta cohort look like?
The Beta cohort consists of 1–3 design partners running ACC-led practices where most active Revit centrals live in BIM 360 or ACC hubs. Typical candidates already use Model Coordination or have a regulated-compliance workflow, such as repeated code checks by the Code Compliance Agent on cloud-hosted centrals. Each Beta deployment ships a per-project accuracy and run-time report calibrated to the customer’s pipeline so teams can see the impact on clash review and compliance cycles.