Moving Beyond Legacy Model Transfers: The Case for ACC Bridging
- Feb 18
- 2 min read
A Letter from AI-MEP’s Vice President of Technology & Growth, Daniel Villeneuve
Hello AEC Community,
I grew up around blueprints in a contractor’s environment, and I learned early that the greatest risk on a project is rarely the drawing itself. The real risk is whether everyone is working from the right information, at the right time, with clear accountability. That understanding shaped my path from computer science and CAD into architectural engineering, and ultimately into helping AEC organizations modernize how they deliver work. Again and again, I’ve seen our industry struggle not because the tools are insufficient, but because our processes have not kept pace with what those tools make possible.
That is the lens I bring to Autodesk Construction Cloud (ACC) bridging. Bridging is not simply a more efficient way to share models. It is a fundamentally better way to collaborate across firms while preserving data ownership, governance, and responsibility. It enables cloud-based coordination without turning project delivery into a free-for-all where authority blurs and accountability erodes.
The concerns people raise are legitimate, and they should not be brushed aside. If updates fly too frequently, teams can lose confidence in what they are coordinating against. If there is not a disciplined way to track what changed from one submission to the next, transparency drops. And if critical project information lives primarily inside another organization’s environment, you can weaken your ability to manage security, administration, and long term retention.
That matters because our work carries professional liability. Architectural and engineering requirements for signing, sealing, and record retention cannot be put at risk, or made harder to comply with. This can occur when unclear governance and ownership force IT and security teams into convoluted workarounds. State specific rules around responsible control, signing and sealing, and record retention vary, but the consistent theme is accountability. In practice, each firm should ensure it maintains custody and governance over the authoritative project record throughout the design process and afterwards, while still enabling the right level of coordination with partners.
This is why I continue to advocate for bridging as a practical step forward. It allows teams to move beyond legacy exchange habits that were designed for yesterday’s constraints, without compromising the professional responsibilities that define our work. When used intentionally—through predictable sharing, clear version comparison, and firm-controlled records - bridging delivers faster coordination and cleaner handoffs while reinforcing governance, not weakening it.
Our industry is full of talented professionals operating under increasing complexity, risk, and speed. Bridging respects that reality. It modernizes collaboration in a way that aligns with how serious our obligations are, while finally allowing our delivery methods to match the demands of today’s projects.
