- Ownership comes first: published supplier terms make customer-paid tool models and prints, and work created under the contract, the customer's property.
- Designs you engineered on your own account, with their full feature tree, are the part of an automotive archive a supplier can usually license.
- In our reading, most commercial automotive technology is EAR99, but releasing it to a foreign person in the US is still an export under 15 CFR 734.13; defense work falls under the ITAR.
- Buyers want native SolidWorks, CATIA, NX or Creo files with history plus STEP, because STEP keeps the shape and drops the construction history.
Can an auto parts supplier license its CAD files to AI companies?
Yes, for designs the supplier owns, once three sets of rules allow it. They apply in this order: your customers' purchase and tooling terms, US export control, and your own confidentiality promises. The table quotes each one from its source. This page is general information, not legal advice.
| Rule or source | What it says | What it means for you | Date checked |
|---|---|---|---|
| A Tier 1 supplier's published purchase terms (Inteva, February 2025) | Works "created in the course of performing the Contract" are "works made for hire" and "the sole property of Purchaser" | Design work you did under a customer's purchase order may belong to that customer, not to you | 20 Nov 2026 |
| The same terms, on the customer's information | The supplier must "use the Purchaser's Information solely for the purpose of supplying Products and Services to Purchaser" | Drawings, specifications and data a customer gave you cannot go into a license | 20 Nov 2026 |
| A Tier 1 supplier's published tooling terms (Nexteer, 2019) | "Tool models and tool prints are considered part of the Tooling and are also the property of the Buyer" | Tool models the customer paid for are out, unless the design was your own proprietary tooling | 20 Nov 2026 |
| EAR, 15 CFR 772.1 | "Technology" can take the form of "computer-aided design files" | A CAD archive is technology under US export rules, whatever its classification | 20 Nov 2026 |
| EAR, 15 CFR 734.13(b) | A release of technology "to a foreign person is a deemed export" | Sharing files with a buyer's foreign staff in the US can be an export | 20 Nov 2026 |
| ITAR, 22 CFR 120.33 | Technical data includes drawings "required for the design, development, production" of defense articles | Military vehicle and defense programs need their own review and usually stay out | 20 Nov 2026 |
Sources: Inteva terms, Nexteer tooling terms, 15 CFR 772.1, 15 CFR 734.13 and 22 CFR 120.33, read on 20 November 2026. The two supplier documents are what a Tier 1 company asks of its own suppliers; your OEM contracts may say more or less, so read your own.
Who owns the CAD: the OEM, or the Tier 1 and Tier 2 supplier?
It depends on who was responsible for the design, and the purchase order usually says. Automotive suppliers work in two modes. In build-to-print work, the OEM or the Tier 1 sends the drawing and you make the part. The model you rebuilt from their print, and any changes you made at their request, follow their information. Under terms like the ones quoted above, that material is theirs to control.
In design-responsible work, you engineer the part to a performance specification. The geometry, the feature tree, the design calculations and the test history are your engineering. Even then, read the contract: some customers write a works-made-for-hire clause or an assignment into every purchase order, which can move ownership of the design work to them. Others leave the design with you and take only a license to use it for their vehicles.
Aftermarket makers are often in the clearest position. A company that reverse engineered nothing, designed replacement or performance parts in house and sold them under its own brand usually owns the whole archive. Supplier-proprietary tooling is the other clear case: the Nexteer terms say "any Seller claims of proprietary tooling, or tooling design, shall be deemed intellectual and physical property of the Seller".
Production part approval packages tell you a lot. A PPAP file for each part number shows whose drawing was approved, which design record applies and every engineering change after launch. Pull it before you sort the archive. Origin's guide to PPAP in manufacturing explains what each element holds.
Is automotive CAD export controlled under the EAR or ITAR?
Yes, it is subject to the rules, even when no license is needed. The Export Administration Regulations define "technology" as information necessary for the "development," "production," "use," and later service of an item, and a note to that definition lists "computer-aided design files". In our reading, most commercial passenger car and truck parts are not on the Commerce Control List, and the rule says items subject to the EAR but not on that list "are designated as" EAR99. EAR99 technology still cannot go to an embargoed country or a restricted party without a license.
The point suppliers miss is the deemed export. Under 15 CFR 734.13, a release of technology to a foreign person inside the United States counts as an export to that person's home country. An AI company with engineers from many countries is a release point. Ask the buyer where the files will be stored and who can open them, and write that into the license.
Defense work is different. 22 CFR 120.33 covers technical data "required for the design, development, production, manufacture, assembly" and repair of defense articles, including blueprints and drawings. A supplier with a military vehicle program or a defense subcontract should treat those part numbers as out of scope and keep them in a separate folder from the start. Origin's CAD licensing guide has a full export-control checklist; this page does not repeat it.
Why do AI companies want native SolidWorks, CATIA, NX and Creo files?
Because the native file holds how the part was built, not only what it looks like. A SolidWorks part, a CATIA CATPart, an NX part or a Creo part stores the sketch, each feature, the parameters, the constraints and the order they were applied. Engineers call that the feature tree or the feature history. It is the closest thing to a written record of design intent that a CAD archive holds.
Research shows why that record matters for machine learning. The DeepCAD paper notes that "CAD models encode the user creation process of 3D shapes", and its authors trained their model on "178,238 models and their CAD construction sequences". The Fusion 360 Gallery paper said in 2021 that "currently there does not exist a dataset of realistic CAD models in a concise programmatic form". The public ABC dataset gathered a million CAD models, mostly hobby and open designs. What none of them has is decades of production parts from a regulated industry, with every engineering change attached.
That is what an automotive supplier holds. Brackets, housings, castings, stampings and injection molded parts, each with revisions driven by tooling trials, warranty returns and cost-downs. For format detail, see Origin's pages on the CATPart file and on NX and Teamcenter data.
Is STEP enough, or do buyers want native files plus STEP?
Buyers want both, and STEP alone is weaker. STEP is the international standard for exchanging product data; its automotive and aerospace application protocol is ISO 10303-242, "Managed model-based 3D engineering", and ISO now lists a 2025 edition. A STEP file opens in almost any CAD system, which makes it the common reference copy in a dataset.
What STEP usually loses is the history. A NIST report put it plainly: "Most STEP translators can currently only transfer 'dumb' shape models encapsulating the final result of some constructional process, all information about that process being lost in the exchange." The lost items it lists are the construction history, the parameters and the constraints. So a buyer pairs the two: the native file for the history, the STEP file as a neutral copy any tool can read.
If part of your archive survives only as STEP or IGES, because an old CAD system was retired or a customer sent neutral files, it still counts. List it separately and say so. A buyer prices a history-rich native set very differently from imported dumb solids.
What do buyers want and reject in an auto parts CAD archive?
What raises interest: native files that open with their full tree, assemblies whose references resolve, a bill of materials, drawings with tolerances, revision history linked to change orders, and a clear owner for each part number. Material callouts, simulation results and test reports linked to the same part make the set richer.
What gets a set rejected or discounted: customer-owned parts mixed in with your own, files with broken external references, exports that flattened the history, duplicates of the same part saved under many names, and anything a buyer cannot clear for export. Files with OEM logos, title blocks or part numbers from a customer's system are a warning sign even when the geometry is yours, because they suggest the design record sits with the customer.
- Volume: count parts, assemblies and drawings separately, and how many have more than one revision.
- Systems: which CAD versions, and whether a PDM or PLM vault holds the history or it sits in folders.
- Ownership tag: own design, customer print, joint, or unknown, per part number.
- Export tag: EAR99, controlled, ITAR, or not yet classified.
How do you export a PDM vault or Teamcenter archive with its history?
Export from the vault, not from engineers' desktops, so references and revisions come out intact. In Autodesk Vault, for example, the help pages say Pack and Go "collects a file and all of its referenced files into a single package" outside the vault, and that "Selecting a file from the History tab allows you to package historical versions". The package can "retain the folder structure from the vault", and you can append a transmittal report "of all of the files in the package". Vault also lists using it to "extract a data set that makes up a specific revision of an item and its bill of materials".
SolidWorks PDM, Teamcenter and Windchill have their own tools for the same job; Origin's guides to the SolidWorks PDM vault and to NX and Teamcenter data walk through them. Whatever the system, the order of work is the same.
- Remove customer-owned and build-to-print part numbers first, using the ownership tags.
- Remove ITAR and controlled part numbers and anything under a customer NDA.
- Strip title blocks, customer logos and supplier codes that identify another company.
- Export a small sample with history and references, and check that it opens on a clean machine.
- Keep the full export inside your company until the license is signed.
What should auto parts suppliers do next?
We help you license your data. Origin Data Partners is an independent data partner that helps business owners value and license their company records: the company pays Origin nothing, and a buyer may pay Origin when a deal completes. Start with a description, not files: your CAD systems, roughly how many parts and assemblies, how many years of revisions, and how much of it is your own design.
We work only with data you created in running your business, or hold under a written licence that lets you license it for AI training. We do not take scraped web data, purchased contact or consumer lists, people-search or location data, or personal data collected without a notice that covers this use. When you can describe the archive, check what your CAD records may be worth. Not the owner? Advisers can introduce the company.
How we checked this
We read every source on this page on 20 November 2026. The export rules come from the official regulation text on eCFR (15 CFR 772.1, 734.3 and 734.13, and 22 CFR 120.33). The ownership examples come from two Tier 1 suppliers' own published terms. The format facts come from ISO's page for ISO 10303-242, a NIST report and Autodesk's own Vault help. The research on CAD history comes from three papers on arXiv.
What we could not verify: the terms in any OEM's current supplier contract, which most OEMs do not publish; the export classification of any particular part; and any price for an automotive CAD archive, because no buyer has published one. The approved range above covers company records in general.
Common questions
Can an automotive parts supplier sell or license its engineering CAD files to AI companies? Who buys them and what do they pay?
Yes, for designs it owns. AI companies that train design and engineering models license CAD archives, and AI companies pay $20K to $5M for company records in general. No buyer has published a price for automotive CAD specifically. A supplier usually licenses rather than sells, so it keeps the files. Customer-owned parts, tooling prints a customer paid for and defense work usually stay out of the license.
Our auto parts engineering team has decades of old CAD models on a server. Is there any way to make money from them?
Possibly, if the models are your own designs and still open in their native CAD system. Old revisions are not dead weight: the sequence of changes on a part is what makes an archive useful for training. Sort the server by owner first, then by export status, then count parts and revisions. A description of that count is enough to learn whether the archive is worth a conversation.
Do we own our native CAD files with feature history, or do customers or our software vendor have rights to them?
Your CAD software vendor does not own your models; its license covers the software. Customers are the real question. If you modeled a part from a customer's drawing, or your purchase order makes design work a work made for hire, the customer controls it. Parts you designed on your own account are usually yours. Check purchase order terms part number by part number.
Are there export control issues with licensing our CAD and engineering drawings to an AI company?
Yes, they need checking. Under the EAR, CAD files are a form of "technology", and in our reading most commercial auto parts technology is EAR99. That still bars shipments to embargoed countries and restricted parties, and a release to a foreign person in the US is a deemed export. Drawings for defense articles fall under the ITAR and usually stay out. This is general information, not legal advice.
What is a native CAD file?
A native CAD file is the file in the format of the program that created it: SLDPRT and SLDASM for SolidWorks, CATPart and CATProduct for CATIA, PRT for NX and Creo. It keeps everything that program knows about the part, including sketches, features, dimensions, constraints and their order. Opening it in the same program lets you edit the design as it was built.
Can you see history in SOLIDWORKS?
Yes. A SolidWorks part shows its history in the FeatureManager design tree, which lists every sketch and feature in the order it was created. Dragging the rollback bar steps back through that sequence. The tree survives in native SLDPRT files. Exporting to STEP or another neutral format usually flattens it into a single body with no tree.
Are .stp and .STEP files the same?
Yes. Both extensions name the same kind of file: product data written in the STEP exchange format of ISO 10303. Some systems save .stp, others .step, and either opens in the same tools. What can differ is the application protocol the file follows, such as AP203, AP214 or AP242, and how much product information beyond geometry it carries.
Who helps an automotive supplier license its CAD archive to AI companies?
Origin Data Partners helps companies license records they own, including CAD archives. The supplier describes the archive first, without sending files: CAD systems, part counts, years of revisions and how much is its own design. The supplier keeps the decision and signs any license itself. An export-control adviser and the supplier's own counsel review the controlled and customer-owned parts.
Sources and further reading
- Inteva Products: General Terms and Conditions (12 February 2025)
- Nexteer Automotive: Tooling Terms and Conditions (effective 15 September 2019)
- 15 CFR 772.1: Definitions of terms used in the EAR (eCFR)
- 15 CFR 734.13: Export, including deemed exports (eCFR)
- 15 CFR 734.3: Items subject to the EAR, including EAR99 (eCFR)
- 22 CFR 120.33: Technical data under the ITAR (eCFR)
- NIST: NISTIR 7433, exchange of parametric and feature-based CAD models with STEP (2007)
- ISO 10303-242: STEP application protocol for managed model-based 3D engineering
- Autodesk Vault Help: Pack and Go for Files
- Autodesk Vault Help: Package Files
- arXiv: DeepCAD, a deep generative network for computer-aided design models (2021)
- arXiv: Fusion 360 Gallery, programmatic CAD construction from human design sequences (2021)
- arXiv: ABC, a big CAD model dataset for geometric deep learning (2019)
