Insights · Industrial data

A new purpose for your CAD archives

Older designs may still contain useful engineering knowledge. They can document technical solutions, variations and design decisions relevant to particular research and AI applications. Whether an archive can support a licensing opportunity depends on much more than the number of files it contains.

1. Describe the archive before preparing files

Start with a simple inventory. When were the files created? Do they represent individual parts, assemblies, tooling or complete machines? Which CAD systems and file formats were used? An approximate indication of scale is enough initially. There is no need to convert or clean the entire archive before its basic suitability has been assessed.

Separate in-house designs from customer drawings and purchased components. This distinction supports both technical selection and the later review of licensing rights. Identify someone in your organisation who understands how the archive was created.

2. Preserve the engineering context

A model becomes easier to interpret when its drawings, bills of materials and version information can be located. A potential user may need to understand which files belong together and whether units, materials or manufacturing steps are documented. Record missing relationships instead of filling the gaps with assumptions.

Native CAD files and exchange formats serve different purposes. A STEP model can provide geometry, while a native file may contain additional design information. The format required should follow the intended application, rather than a blanket conversion exercise.

3. Separate research relevance from buyer demand

Autodesk's Fusion 360 Gallery research demonstrates the use of human CAD construction sequences in machine-learning research. This provides evidence of a technical application. It does not establish that any company archive will attract a buyer, or that a particular licensing price is available.

The practical question is how your archive relates to a specific requirement. What task should a model learn, or what capability should be evaluated? Once that is understood, the relevant part of the archive can be selected more precisely.

4. Review rights and confidentiality early

Having a file on your server does not automatically mean that you can license it to another party. Review customer contracts, confidentiality agreements, external designers' rights and restrictions relating to supplied components. Older or completed projects can still be subject to limitations.

Removing customer names does not resolve every issue. Geometry, drawing headers and engineering context may still disclose confidential information. Identify areas that must remain excluded and the documents that could support an eventual decision to release other material.

5. Keep any later sample controlled

A sample may become useful after the requirement, recipient and evaluation purpose have been clarified. Choose a small, representative subset that has been explicitly approved for disclosure. Agree who may access it, how it may be used and what should happen to it after evaluation.

The sample should support a reliable assessment of structure and quality. It should neither reveal unnecessarily sensitive projects nor create a misleading picture of the archive by including only exceptional examples.

Use an internal inventory as a working document

A simple inventory can record the product area, period, approximate number of files, formats, related documents and known restrictions for each archive group. Distinguish estimates from verified information. Add a responsible contact and known technical issues, such as missing reference files. This working document does not need confidential project names. Once a specific requirement emerges, it can help identify which parts of the archive deserve closer review without requiring a full file transfer.

The next step: a short archive description

For an initial enquiry to BRIDGERS, describe your industry, data types, approximate age, formats and scale. Indicate whether the archive mainly contains your own designs. Sensitive files and access credentials are not needed at this stage.

This provides a basis for discussing whether a more detailed assessment is worthwhile and which information is still missing. A licensing opportunity depends on a suitable requirement, adequate rights and terms that the parties accept.

Sources & further reading

What’s in your data archives?

A short description is all you need to start. No raw data required.

Assess your data