Autodesk Construction Cloud (ACC): A VDC Team's Practical Guide

Autodesk Construction Cloud (ACC) is the unified platform Autodesk introduced to consolidate BIM 360 and several other project management tools. If you are still running BIM 360 on active projects or configuring a new project for the first time understanding what ACC is, how it differs from BIM 360, and how to configure it effectively saves significant setup time and prevents collaboration failures.

What Is Autodesk Construction Cloud?

ACC is Autodesk's common data environment (CDE) for the construction industry. For VDC teams, the most relevant modules are:

• Docs Document management, RFIs, submittals, and model storage (BIM 360 Docs successor)
• Model Coordination Cloud-based clash detection without local Navisworks (BIM 360 Model Coordination successor)
• Design Collaboration Shared model views and version comparison (new in ACC)
• Build Field management, quality and safety (BIM 360 Field successor)

ACC vs. BIM 360: What Actually Changed

Unified login and project structure. BIM 360 had separate modules with inconsistent permissions. ACC has a unified admin interface and consistent role-based permissions across all modules a real improvement for multi-module projects.

Model Coordination improvements. ACC supports cloud-based clash detection you do not need Navisworks locally for basic clash tests. However, it is not a replacement for Navisworks for high-volume triage. Think of it as a stakeholder-facing overview tool.

Design Collaboration. New in ACC allows design teams to publish models on schedules and compare versions. Useful for tracking model progress across design milestones.

How to Configure ACC for Effective BIM Coordination

1. Set up your folder structure before anyone starts uploading. ACC's folder structure cannot easily be reorganized after files are in it. Define your folder hierarchy in the BEP: typically by discipline (Architectural / Structural / Mechanical / Electrical / Plumbing / FP / Civil) with subfolders for current models, archive, and reference.

2. Define permission levels explicitly. ACC has five permission levels: View, Download, Upload, Edit, Manage. Most subcontractors should have Upload to their own folder and View/Download to others. The GC VDC coordinator should have Manage across all project folders.

3. Configure Model Coordination with the right model set. A model set in ACC Model Coordination defines which models are included in clash detection. Create separate model sets for different coordination zones (e.g., podium, tower, mechanical penthouse) rather than one enormous model set it keeps clash counts manageable.

4. Publish on a schedule, not ad-hoc. The value of ACC as a CDE is that everyone works from the same current models. Establish a publishing schedule in the BEP (e.g., subcontractors update by Monday noon), and enforce it. Models that are weeks out of date make coordination meaningless.

5. Connect ACC to your issue management workflow. ACC's RFI and issue tools can be connected to Revizto or directly managed within the platform. Decide before the project starts running two parallel issue tracking systems is worse than one imperfect system used consistently.

ACC Model Coordination vs. Navisworks: When to Use Each

Use ACC Model Coordination for:

• Real-time model viewing by non-technical stakeholders (owners, field staff)
• Basic clash overview without requiring local software installation
• Design review and model version comparison

Use Navisworks for:

• High-volume clash triage (1,000+ clashes requires Navisworks-level filtering and grouping)
• Complex clash test configuration (tolerance settings, discipline pairing, search sets)
• VDC coordinator-level analysis work