I’ll be honest — working across multiple projects over the past few years, I kept running into the same frustrating moment: a beautifully coordinated model in Revit, decisions locked inside Forma’s site studies, and then somewhere between design sign-off and breaking ground, critical context just… evaporated. Data got re-entered, assumptions got lost, and field teams were working from information that was already stale. So when the news broke about ACC integrating into Autodesk Forma on March 24, 2026, my first reaction wasn’t just “interesting” — it was “finally.”
The industry has long buzzed about the “Industry Cloud” concept, and we are about to see its most significant evolution yet. On March 24, 2026, Autodesk will officially bring Autodesk Construction Cloud (ACC) into the Autodesk Forma ecosystem.
This isn’t just a rebranding exercise — it is a strategic consolidation designed to bridge the gap between design intent and field execution.
What Kind of Projects Stand to Gain the Most?
Think large-scale mixed-use developments, hospital campuses, infrastructure corridors, or any project where multiple firms, trades, and owners share data across a multi-year lifecycle. A 500-unit residential tower, for instance, might involve an architect using Forma for massing and environmental analysis, a structural engineer coordinating in BIM Collaborate, a GC managing RFIs in Build, and an owner tracking assets for long-term facility management — all operating in loosely connected silos today.
But the project type that arguably has the most to gain right now? AI data centers.
If you haven’t been watching this space, the numbers are staggering. The global data center construction market, valued at approximately $241 billion in 2024, is on a trajectory to exceed $456 billion by 2030. These aren’t your typical commercial buildings. Design loads above 100–200 kW per rack are becoming increasingly common, forcing a rethink of the mechanical and electrical architecture of entire sites — cooling systems, power distribution, and structural layouts are all being adapted to cope with added weight, heat, and cabling complexity.
Today’s AI data centers are orders of magnitude larger and more complex than those built just a decade ago, and they’re being compressed into 18–24 month delivery cycles. Single campuses now require 4,000 workers instead of 750, and customer specifications shift mid-deployment as technology evolves faster than buildings can rise.
This is precisely where a consolidated platform like Forma could make a measurable difference. When cooling system engineers, structural coordinators, MEP specialists, and facility operators all work from the same connected data environment — from initial site feasibility through to handover and long-term asset management — the risk of costly misalignments decreases significantly. Projects slip not because people are incompetent, but because the system is incapable of detecting slippage early enough to act. A unified, AI-powered platform with real-time data visibility directly addresses that structural failure.
Asset management also becomes dramatically more effective for owners and operators of these facilities. When the as-built model, the commissioning records, and the equipment data all live in the same ecosystem that was used during construction, facility managers can respond to issues faster and plan maintenance proactively — critical in environments where downtime has enormous financial and operational consequences.
The Evolution of the Platform
By integrating ACC into Forma, Autodesk is creating a single, AI-powered thread that runs from the first conceptual site study through to the final handover.
That AI layer is worth unpacking. Autodesk AI — built into Forma’s core — already supports capabilities like automated clash detection, generative design exploration, energy and carbon analysis at early design stages, and predictive scheduling insights. Autodesk has been developing a neural CAD model trained to understand shapes, forms, and CAD geometry — one that can reason in 3D and in the physical world, not just process text against a CAD API. With the merger, those capabilities extend into the construction phase: AI-assisted quantity takeoffs in Forma Takeoff, intelligent document comparison flagging spec deviations in Forma Data Management, anomaly detection in daily logs within Forma Build.
How it used to work — and why it was painful
Before this consolidation, a project team might go through something like this: an architect completes a site feasibility study in Forma (the conceptual tool), exports geometry into Revit, coordinates with consultants in BIM Collaborate Pro, and then — at construction handover — the GC receives a static PDF package and a model dump. The GC re-imports, re-structures, and manually recreates submittal logs in ACC’s Build module, largely disconnected from the design decisions upstream.
I’ve seen teams spend 3–4 weeks on a major project just reconciling model data between design and construction platforms at handover. That’s time and budget that simply shouldn’t be lost.
Important context gets lost along the way. Decisions made early are hard to trace later. For AECO professionals, this new integration means a more cohesive data environment where information doesn’t “die” when it moves between project phases.
New Names, Same Familiar Tools
As of March 24, several core products will adopt new identities within the Forma portfolio:
| Current Name | New Name (within Forma) |
| Autodesk Docs | Forma Data Management |
| Autodesk Build | Forma Build |
| Autodesk Takeoff | Forma Takeoff |
| Autodesk BIM Collaborate Pro | Forma Design Collaboration |
| Autodesk Forma (Conceptual tool) | Forma Site Design |
What This Means for the Industry
For firms currently utilizing ACC, the transition is designed to be seamless. Autodesk has confirmed that there will be no immediate change to data storage, APIs, or existing project workflows. Your environment is simply gaining a more powerful context.
On the practical side, the consolidation has real productivity implications. Industry estimates suggest that data fragmentation and manual re-entry account for roughly 30% of rework costs on large construction projects. Teams currently copying information between Docs, Build, and external systems could realistically recover 5–10 hours per week per project manager. For a firm running 20 concurrent projects, that compounds quickly.
The move signals four major shifts for the AECO industry:
1. Reduced Fragmentation — Moving away from software silos and toward a unified platform means fewer handoff failures and less duplicated effort across project phases.
2. AI-Native Workflows — Forma’s underlying architecture is built for rapid analysis and automation, which will now permeate the construction phase.
3. Connected Data & Digital Twin Lifecycle — By using a shared data foundation, the industry moves closer to a true Digital Twin lifecycle — where the model used for design informs construction, and ultimately drives facility operations for decades.
4. Improved Cross-Platform Data Exchange — Forma’s open API architecture means data will flow more cleanly to and from third-party platforms: ERP systems, FM software, GIS tools, and specialty trade applications. Instead of one-way exports that go stale the moment they leave the platform, connected integrations can maintain live data relationships.
But Let’s Be Honest — This Isn’t Without Risks
I think it’s important to balance the excitement here with a clear-eyed look at what could go wrong. Because there are legitimate concerns that the industry shouldn’t brush aside just because the announcement sounds impressive.
The rebranding fatigue is real. As one ACC admin put it on the Autodesk community forums, “this constant rebranding is becoming tedious and making training difficult.” This isn’t the first time we’ve been through this — BIM 360 became ACC, and now ACC is becoming Forma. Every time the names change, someone has to update the BEP templates, the training materials, the contract language, and the onboarding decks. For smaller firms without dedicated BIM managers, that overhead is a real cost.
The naming confusion is genuinely problematic. For years, “Autodesk Forma” meant the conceptual site design tool. Now, the entire Autodesk Construction Cloud is Autodesk Forma. Explaining to a client or contractor what “Forma Build” is when they remember “Build” being a standalone product — that’s a communication challenge we’ll be dealing with for the next year at least.
Not everyone lives in a pure cloud world. The platform needs to remain accessible to those who aren’t living in a 100% “connected” environment yet. Many firms — particularly mid-size contractors and subcontractors in certain markets — still rely heavily on file-based workflows, local servers, and offline access in remote site conditions. The pressure toward a cloud-native, always-connected model could inadvertently leave those users behind or force costly infrastructure upgrades they aren’t ready for.
Vendor lock-in becomes a bigger conversation. The more deeply your project data lives inside a single, consolidated Autodesk ecosystem, the harder it becomes to switch tools, negotiate pricing, or adopt best-of-breed alternatives for specific workflows. The industry’s move toward openness and interoperability (IFC, open BIM, etc.) arguably runs counter to the direction a tightly integrated proprietary platform pushes you.
Today it’s a rebranding — tomorrow it’s a feature roadmap question. Autodesk has been careful to say APIs and workflows won’t change immediately. But “immediately” does a lot of work in that sentence. The real test isn’t what happens on March 24, it’s what the product roadmap looks like in 18 months — which features get investment, which legacy ACC tools get deprioritized, and whether the promised integration depth actually materializes.
Preparing for the Shift
While the technical side remains stable for now, this is the time for digital leads and BIM/VDC managers to update internal documentation, workflows, and training materials — and to have honest internal conversations about platform dependency. The goal is clear: a future where “design” and “build” are no longer separate chapters, but a continuous, data-driven narrative. Whether Autodesk fully delivers on that promise is something we’ll be watching closely after March 24.
“By bringing these capabilities together under Forma, we are removing the friction that has historically slowed down the AECO industry.” — Autodesk, on the March 24 integration. The ambition is right. The execution is what matters now.
