MFG3731 Vault on Autopilot: my session at Autodesk University 2026

I am going to be a speaker at Autodesk University 2026. The session is called Vault on Autopilot, its code is MFG3731, and it runs on Thursday September 17 at 4:30 PM in Las Vegas: a 60 minute Technical Deep Dive on the Design and Manufacturing track.

I write it and it still sounds strange. So let me tell you what AU is, what I am presenting and why I think it is worth an hour of anyone's conference.

What Autodesk University is

AU is Autodesk's global conference: the annual meeting point for engineers, architects, developers and partners from all over the world who work with Inventor, Vault, Revit, Fusion, Forma and the rest of the portfolio. It is not a marketing event: it is where the technical community compares notes on what actually works in production.

A Technical Deep Dive is the most technical format in the program. Sixty minutes to open a solution from the inside, with architecture, decisions and demonstrations. It is not a vision talk. It is a how talk.

The road here

I started as an Applications Engineer at an Autodesk reseller in Colombia. My job was teaching people how to use the products: implementation, support, training. Over the years I moved through presales, commercial management and innovation management.

At some point the role changed: I stopped only teaching products and started building inside them. I founded asistIA to develop AI agents. Today I work as a senior AI solutions consultant at Avant Leap, where together we develop VaultPilot, a native AI agent for Autodesk Vault Professional 2026. And I built a design assistant that generates parametric parts and assemblies from natural language inside Inventor.

That is the work taking me to Las Vegas.

What the session is about

About putting an AI agent inside a product data management system without it wiping your project one day.

It is a more interesting problem than it sounds, because Vault is the most explicitly rule-governed system in the whole engineering stack: lifecycle definitions name every state and every legal transition, revision schemes say which sequence applies to which category, categories carry their property mappings, permissions say who may do what. All of it is written down. And still, the one executing those rules click by click is a person.

The session runs through five blocks: where the bottleneck is, how the agent loop is built, what it takes to trust it, what evidence it left behind, and how you pick the first workflow worth automating. The second half is not about what I built: it is about how to decide in your own operation.

What there will not be

There will be no lab promises and no numbers rounded up. I am going with a development log, with its date and its sample size, and with a line on the same slide saying what those numbers do not prove.

The technical community can smell hype from miles away. The only way to stand on that stage is with real work, uncomfortable parts included.

See you there

Over the coming weeks I will publish the four pillars of the session here, one per article. If you are going to be at AU 2026, write to me and let's plan a coffee in Las Vegas. And if you are not travelling but you work with Vault or Inventor, a good part of what I will present applies directly to your operation.

MFG3731 · Vault on Autopilot. Thursday September 17, 2026, 4:30 PM, Autodesk University, Las Vegas. A 60 minute Technical Deep Dive on the Design and Manufacturing track.