Why attend AS1411: The Stack Inversion is Real: How AI Is Changing What CAD Managers Actually Do
I have been doing CAD management in one way or another for a long time, and the workflows and challenges today don’t look like those from just five years ago. The tools moved. The work moved with them.
Here is the shift. Some of the tasks that used to require deep CAD knowledge can now be researched and diagnosed fast. Meanwhile the decisions that actually matter, standards, compliance, support, who owns which workflow, keep landing on the CAD manager’s and Design Technology Lead’s desk. The value is moving up the stack. That is the inversion, and it is already happening whether your team planned for it or not.
This is not a slide deck of AI buzzwords. I am going to show you the actual work. How you can run advanced support research now. How I diagnose a messy Civil 3D issue that used to eat a full afternoon. How I read CER crash data across a fleet instead of guessing. How I use real project and support data to build standards, workflows, and best practices.
One number I keep coming back to. In my experience roughly ~50-70 percent of Autodesk product crashes are environment problems, not direct Autodesk bugs. Bad graphics drivers, stale third party plugins, workflows, corrupt data, an OS in a weird state. If you know how to read what the crash reporter is telling you, most of those stop being mysteries. That skill is worth more now than it was a year ago, and it is the kind of thing we will get into.
If you manage CAD for a team and you are trying to figure out where your time should go next, this session is for you. Come with your own problems. The parts that land hardest are usually the ones that map to something you are dealing with on the following Monday when you return from AU to your office.
Why the Braindates
The regular AU session is me talking. The Braindates are us talking, and honestly those conversations are where I learn the most.
I have two topics up. CERs and crashes, because everyone has crash pain and almost nobody is looking at the data behind it. And Civil 3D reference loops, because circular and deeply recursive data shortcut chains are a real problem and I want to compare notes with people who are living in the same situation on note strategies on dealing with them until Autodesk puts in some workflow guardrails like they did in Xref.
The reference loop one matters to me right now. I have been building custom tooling to map these graphs, and I want to know how other teams are handling it. If you have a project that turned into a hairball of references, bring it. That is exactly the conversation I want.
If crashes are your headache instead, come to that one. I will share what I have seen reading CER data across our fleet and you can tell me what you are seeing across yours. Small group, focused, 45 minutes. No slides.
Come to the session, grab a Braindate, or find me in the hallway. I am there to talk nerdy CAD shop talk, network, and meet people. That is the whole reason I go to AU to exchange knowledge and meet with new and old friends.
Cheers,
Shaan