AI-Powered CAD File Management Beyond PDM
Engineering teams create an enormous amount of knowledge in the course of building a product. They make decisions, explore alternatives, resolve conflicts, coordinate across disciplines, and iterate through dozens of revisions before anything reaches production. Most of that knowledge is real, hard-won, and genuinely valuable.
Most of it is also lost.
Not immediately, and not all at once. It disappears gradually, stored in files that aren’t connected to each other, in email threads that nobody can find six months later, in the memories of engineers who have moved on to other projects or other companies. The systems that were supposed to capture this knowledge — PDM, PLM, ERP — were designed primarily to store approved records, not to preserve the living context of how products are actually developed.
That gap is what OpenBOM is building toward closing. We call the destination Product Memory: a connected, evolving foundation that preserves not just the files and records of engineering work, but the relationships, history, decisions, and context that give those records meaning.
OpenBOM CAD File Agent for SOLIDWORKS is the first step in that direction.
It starts with files because files are still where most engineering work begins. For thousands of engineering teams working in SOLIDWORKS and similar desktop CAD environments, the file is still the fundamental unit of design work. Getting that layer organized — capturing files with their full context, managing revisions systematically, preserving history in a way that is actually navigable — is the foundation everything else depends on. You cannot build Product Memory on top of scattered folders and disconnected local drives.
That is what CAD File Agent is designed to do. And it is designed to do it without asking engineering teams to abandon the tools and workflows they already depend on.
Why Traditional PDM Falls Short for Modern Engineering Teams
The traditional PDM function was built around control. Put the files in a vault, prevent conflicts, track versions and control who can make changes. For a long time, that was a meaningful step forward from unmanaged folders and shared drives. Each desktop CAD has its own favorite PDM owned by the same vendor.
But that model was built for a world where the CAD file itself was treated as the center of engineering work. That assumption now feels too narrow.
Engineering teams today need to do more than store files and lock them. They need to understand what those files represent, how they connect to the wide scope of other informational assets, engineering and product structures, what changed between revisions, who was working on what, how engineering decisions evolved, and how that information flows into manufacturing, procurement, service, and support.
This is where traditional PDM falls short. Most existing systems were designed around the idea of a file vault. Their architecture and workflows focus on controlling files, locking them, checking them in and out, and managing a rigid administrative process around them. That approach can protect files, but it often stops there. It does not capture the broader context of engineering work, and it struggles to support the flexibility, collaboration, and connected data models that modern engineering teams need. For products that span mechanical, electronic, and software systems, those limitations become especially difficult to work around.
Traditional PDM is focused on file control rather than broader knowledge capture. Most systems are difficult to deploy, require complex server or hosted cloud environments, and are difficult to connect across teams and organizations. Most importantly, they do not preserve enough of the product knowledge created around them. A vault is useful, but a vault is not enough.
Why AI in Engineering Starts with a Strong Data Foundation
There is a lot of conversation today about AI in engineering and manufacturing. But too often the conversation jumps too quickly to the assistant or the model. The more important question is what does the AI actually know about engineering data and historical context, communications, and other pieces of connected information?
If engineering knowledge is fragmented across files, folders, emails, spreadsheets, and disconnected systems, then AI has very little reliable context to work with – it cannot truly understand the product, its history, its relationships, or its lifecycle.
That is why our first AI application is focused on capturing and organizing design data at the source. Before AI can become genuinely useful in engineering workflows, the data foundation must improve. Files must be connected to context. History must become captured and visible. Relationships must be preserved. Product information must become part of a structured memory, not just a collection of isolated file records.
OpenBOM CAD File Agent: Key Features and Capabilities
CAD File Agent is designed around a simple but important idea: CAD files must be captured, the rich change history must be controlled and design data must be connected to other pieces of information – that organizing files is only the beginning. The real value comes from the connection of those files to other elements of product activity – communication threads, rich history references to other design disciplines and other activity such as supply chain, procurement and production.

In practical terms, CAD File Agent captures CAD files together with all their references and dependencies, so nothing gets lost in translation between local folders and a shared workspace. It then analyzes and organizes that design information into structured context, giving teams a clearer picture of what they have and how it fits together.
From there, teams can coordinate work across multiple contributors with appropriate access controls, keeping parallel work from creating conflicts without imposing the kind of rigid administrative overhead that makes traditional PDM feel like a burden rather than a tool.
Where CAD File Agent goes further is in its treatment of history. Every operation, change, and revision is captured as it happens, creating a detailed and navigable record of how the product evolved. Change history and revisions are managed systematically and any prior version of a project can be restored with all its references intact. That last capability matters more than it might sound. The ability to go back to exactly where you were at any point in development, with the full assembly structure preserved, is something many engineering teams discover they need only after they have lost it.
CAD File Agent supports agentic workflows and provides a conversational interface for navigating your product context. Because files, revisions, and history are structured and connected, teams can query design information, trace relationships, and surface relevant context without digging through folders or reconstructing history manually.
From CAD File Control to Connected Product Context
We believe the next step is not simply a better cloud vault. The next step is turning CAD files into connected product context.
That means organizing not just the CAD documents themselves, but the entire history of work, references, revisions, and activity around them. It means giving teams a way to work in a more connected environment without forcing them to abandon the tools and habits that are already part of their day-to-day engineering process.
OpenBOM CAD File Agent transforms scattered CAD files into an organized, collaborative, revision-controlled engineering workspace. It understands CAD files and associated design data and helps teams manage their work without forcing them to change how they use CAD. Instead of thinking only in terms of storing files, CAD File Agent helps teams think in terms of structured engineering work.
Why OpenBOM CAD File Agent Starts with SOLIDWORKS
SOLIDWORKS remains one of the most significant engineering environments in discrete manufacturing. A large number of engineers and companies using SOLIDWORKS still operate entirely within a Windows and file-based environment. It also represents a reality many companies face every day: highly valuable engineering knowledge stored in files, assemblies, drawings, local folders, network drives, and disconnected spreadsheet and email-based workflows. This is the daily operating environment for thousands of engineering teams.
Many of these teams do not need a large enterprise system imposing more administrative weight on their process. They need a practical way to organize the design data they already have, coordinate work across people, and preserve the history of product development in a way that is accessible and useful. CAD File Agent is built for that reality.
CAD File Management as the Foundation of Product Memory
This launch matters not only because it introduces a new product, but because it marks a new architectural direction for OpenBOM. We call that direction Product Memory.
Product Memory is our vision for a modern engineering and manufacturing data foundation that does more than store files or records. It preserves the evolving memory of a product over time. It connects files, BOMs, revisions, relationships, decisions, discussions, and lifecycle activity into a living context that people and intelligent agents can use.
That distinction matters. Traditional systems of record are good at storing approved information. But they often lose the context of how the work happened, why changes were made, what alternatives were considered, and how knowledge moved across people and teams. Product Memory is about preserving that context, not just the final record.

CAD File Agent is the first practical step in this direction. It starts by organizing the file layer, because for many companies that is where product knowledge begins. The long-term goal is broader: a connected memory of product development that supports engineering, manufacturing, procurement, service, and AI-driven workflows across the full product lifecycle.
Learn More
OpenBOM CAD File Agent for SOLIDWORKS is the first AI-powered application in the OpenBOM Product Memory Platform vision.
To learn more about OpenBOM CAD File Agent for SOLIDWORKS, visit: openbom.com/cad-file-agent
To learn more about the OpenBOM Product Memory Platform vision, visit: openbom.com/openbom-product-memory-platform-vision OpenBOM CAD File Agent for SOLIDWORKS
Join our newsletter to receive a weekly portion of news, articles, and tips about OpenBOM and our community.