Autodesk Construction Cloud is a cloud platform for managing a construction project’s documents, models and approval processes in one place. It serves as the Common Data Environment: a single space where every party works from the current version of information, with a status that is clear and traceable.
How does Autodesk Construction Cloud relate to BIM 360?
Many teams still call the platform BIM 360, and reasonably so. Autodesk Construction Cloud is the continuation of that product line, with scope widened from model coordination to the full project cycle including site work and reporting.
What keeps the confusion alive is documentation. Internal training material, company quality procedures and even tender documents still carry the old name. Teams reading a tender requirement that says "BIM 360" often hesitate over whether the platform they run satisfies it.
For practical purposes the answer is simple: where project documents cite BIM 360, the requirement is almost always met by Autodesk Construction Cloud. What needs confirming is not the platform name but whether the required status and approval flow genuinely runs inside it.
What are the components of Autodesk Construction Cloud?
The platform comprises several components that can be enabled separately. Knowing which are genuinely needed avoids paying for capacity nobody uses.
| Component | Function | Who uses it most |
| Docs | Document storage with versioning, status and approval flow | Every discipline |
| Model Coordination | Federating models and running automated clash checks | BIM coordinator |
| Build | Site work management, checklists and quality issues | Project teams on site |
| Insight | Project status summaries drawn from the collected data | Project management |
Not every project needs every component from the start. Most begin with Docs alone, because the largest early benefit is stopping files circulating by email. Model Coordination gets added once discipline count grows and manual clash checking starts consuming too much time.
How do you structure a CDE that lasts?
The most expensive mistake is not the choice of platform but a folder structure and naming convention assembled hurriedly in week one and then used for two years. A poor structure does not stop work — it merely makes every file search take three times as long, every day, until the project ends.
- Set the folder structure around information stages, not around the names of the companies involved. Companies can change mid-project; stages do not.
- Agree file naming rules before the first file is uploaded. Standardising naming after thousands of files exist practically never finishes.
- Decide who has authority to move information from one status to the next, and name them.
- Record those decisions in the BIM Execution Plan so others can inspect them, rather than keeping them as a verbal understanding.
The status structure normally follows the ISO 19650 division: work in progress, shared, published, archive. Autodesk Construction Cloud provides status and approval mechanisms that map directly onto all four, so meeting the standard does not require an extra process outside the platform.
What changes in day-to-day work?
The biggest change is not the tool but the habit. Four things are felt most directly in the first weeks.
- Models are no longer emailed; every discipline uploads to the same location and everyone else takes from there.
- The current version is always identifiable without asking anyone, because file status is recorded in the system.
- Coordination issues are logged in the same place as the models, not in a separate spreadsheet circulating in several versions.
- Change history is available when a disagreement arises later, including who changed what and when.
The last item proves its value during a dispute. The question "which version governed when that decision was made" usually has no answer on a project run by email, and that ambiguity always costs whoever did not keep a copy.
What should you prepare before migrating?
Moving a live project into a new data environment always causes disruption. It cannot be eliminated, but it can be shortened. Four preparations matter most.
- Make file naming consistent before uploading, not after. Uploading disorder into a new platform simply relocates the disorder.
- Set the date the old location stops being used, and enforce it. Two locations running in parallel is the worst of both.
- Train one reference person per discipline, so questions do not queue behind a single individual and stall the whole team.
- Set up the access permission structure before external parties are invited in, particularly the distinction between who may view and who may approve.
The second is the one most often left unenforced. While the old location remains reachable, part of the team keeps using it because it is familiar, and the project runs on two competing sources of truth. Closing access on the announced date works far better than repeated reminders.
Frequently Asked Questions
Is ACC the same as BIM 360?
Autodesk Construction Cloud is the continuation of the BIM 360 line with wider scope, covering site work and project reporting. Where your tender documents or internal procedures cite BIM 360, the requirement is generally met by this platform.
What is a Common Data Environment?
The shared environment where all project information is managed with a defined status. What distinguishes it from a shared folder is that status: every file sits at a stage — work in progress, shared, published or archive — and moving between stages requires a check.
Does everyone need Revit?
No. Documents and models from various sources can be stored and reviewed, including through open exchange formats such as IFC. What needs agreeing is the format version and naming rules, not uniformity of tooling across every party.
Must a CDE be cloud-based?
Not in principle. What the standard requires is a shared data environment with clear, inspectable status and approval. A cloud platform makes that easier to satisfy, particularly where the parties involved are spread across several offices or companies.
Sources
- ISO — Building information modelling (BIM), seri ISO 19650 — https://www.iso.org/sectors/building-construction/building-information-modelling
- ISO 19650-2:2018 — Delivery phase of the assets — https://www.iso.org/standard/68080.html
- ISO 19650-4:2022 — Information exchange — https://www.iso.org/standard/78246.html
Get an Initial Consultation with BIMAGE Indonesia
BIMAGE Indonesia sets up and runs Common Data Environments on Autodesk Construction Cloud, including folder structure, naming conventions and approval flows aligned to ISO 19650. As an Autodesk Gold Partner + ACC Elite, we also provide training and implementation mentoring. If you are weighing a migration mid-project, bring your current folder structure to an initial consultation.