What ACC Automation Actually Means
When people refer to "automating ACC," they typically mean one of two things: using the ACC platform APIs to move data between systems without manual intervention, or using Autodesk's Design Automation API to run CAD and BIM applications server-side without a human operating them.
The first category — data integration via REST APIs — covers tasks like synchronising project data between ACC and an ERP system, automatically routing submittals to the correct reviewers based on discipline and specification section, or pushing field observation data from ACC Build into a project management dashboard. These integrations eliminate the manual data re-entry that persists in most AEC workflows even when teams are using ACC comprehensively.
The second category — server-side CAD/BIM processing via Design Automation — is more technically sophisticated and more transformative. It enables tasks like generating drawing sheets from a Revit model, extracting quantities from an updated model version, or running a coordination clash check to run automatically on a schedule or as a trigger-based workflow — without an engineer opening Revit and manually initiating the process.
Win 1: Automated Coordination & Clash Triage
Clash detection has been part of BIM workflows for over a decade. But in most AEC teams, the coordination process still requires significant manual effort: a coordinator downloads updated models from ACC, runs the clash test in Navisworks, exports a report, reviews hundreds of clashes to determine which are real issues vs. tolerance artefacts, assigns clashes to responsible disciplines, and distributes the coordination report — a process that typically takes half a day per coordination cycle.
Automated coordination workflows change this substantially. Using ACC's Model Coordination API and Design Automation, the clash detection can run automatically whenever a model is updated — no human needs to initiate it. The results flow into a structured database rather than a PDF report. Automated triage logic filters out known false positives (soft clashes below a configurable clearance threshold, clashes between non-interfering element types) and categorises remaining clashes by discipline pair, severity, and location.
What previously required a half-day of coordinator time is compressed into an automated process that runs overnight and delivers a pre-triaged, pre-categorised issue list to the coordination meeting. The meeting focuses on resolution rather than triage.
Reduction in coordination meeting preparation time reported by AEC teams implementing automated clash triage workflows — shifting from manual report assembly to reviewing pre-processed, categorised output.
The additional value is consistency. Manual triage is inconsistent — different coordinators make different judgments about what's a real issue vs. an artefact. Automated triage applies the same rules every time, producing coordination reports that are comparable across cycles and trackable over the project timeline.
Win 2: Automated Drawing Sheet Production
Drawing sheet production from BIM models remains one of the most labour-intensive tasks in AEC documentation. Even in mature Revit workflows, generating a full drawing package from an updated model involves: setting up sheet templates, placing views, adjusting view extents, managing annotation visibility, updating title block information, and coordinating sheet numbering and revision history. For a large project, a single documentation milestone can require days of drafting work.
Using the Design Automation API for Revit with custom Revit add-ins deployed as Design Automation appbundles, this process can be automated end-to-end for standardised building types or product families.
The automation works by:
- Triggering from a model version update or a scheduled release milestone
- Running the Revit automation on Autodesk's servers, executing the appbundle that contains the sheet generation logic
- Placing views on sheets according to a template-driven layout, setting view extents, configuring visibility and graphic overrides
- Updating title block parameters from project metadata stored in ACC
- Exporting PDFs and DWFs to ACC Docs, automatically versioned and linked to the correct project document register
For firms producing highly repetitive building types — multifamily residential, industrial facilities, standardised commercial fit-outs — this automation can eliminate 70-80% of the manual drawing production effort on each project phase.
Win 3: Automated Project Reporting
Project reporting in construction — progress reports, submittal status, RFI logs, cost reports — consumes disproportionate project management time. In a typical mid-size project, a project manager spends 4-6 hours per week assembling reports from data that already exists in ACC, just in different places and different formats.
ACC's REST APIs provide programmatic access to all of this data: submittal logs, RFI status, issue logs, model version history, document approval status, and cost item tracking. Custom reporting automation aggregates this data, formats it according to the project's reporting templates, and delivers completed reports automatically to stakeholders on a defined schedule.
Beyond scheduled reporting, trigger-based alerts can replace manual status monitoring: automated notifications when an overdue submittal crosses a threshold, when a critical path RFI has been open for longer than the defined response window, or when a model version is uploaded without the required BIM validation checks passing.
The time saving is real — but the more significant benefit is reliability. Manually assembled reports are occasionally late, occasionally incomplete, and occasionally inconsistent with the previous week's numbers due to human error. Automated reports are always on time, always comprehensive, and always consistent because they draw from the same data source.
The Design Automation API: Technical Foundation
For teams evaluating the technical investment required, the Design Automation API (DA4R for Revit, DA4ACAD for AutoCAD) is a cloud-based workitem execution system. The workflow is:
- Appbundle: A Revit or AutoCAD add-in packaged specifically for Design Automation. This contains the logic that runs against the model — generating sheets, extracting data, or performing modifications.
- Activity: A definition of what the automation does — which appbundle to run, what inputs it needs, what outputs it produces.
- Workitem: A specific execution instance — here's the model, here are the parameters, run the activity and return the output.
The add-in code is standard Revit API or AutoCAD API development (C#), with some modifications for the headless execution context. Engineers who have developed Revit add-ins for desktop deployment can adapt existing code for Design Automation with moderate effort. Greenfield development typically takes 4-12 weeks depending on complexity.
Getting Started with ACC Automation
The highest-value starting point for most AEC teams is identifying the manual, repetitive task that consumes the most time per project cycle. In most cases, this is either coordination reporting or drawing sheet production — both are strong candidates for the automation approaches described above.
A proof-of-concept for ACC automation can typically be built in 3-6 weeks: one specific workflow, automated end-to-end, demonstrating the value before committing to broader development. The technical barrier is lower than teams typically expect — and the ROI on the right target workflow is immediate and measurable. Our Autodesk Platform Services practice covers ACC Design Automation API, Forge/APS integration, and custom Revit and AutoCAD appbundle development for AEC teams.