Separate the original files from their outputs
| File group | What it tells you | What still needs checking |
|---|---|---|
Files from the original CAD system |
The design was created and saved in its authoring environment |
Which modelling information, references and earlier states remain available |
Exchange formats, such as STEP |
Files were produced to move information between systems or workflows |
The source system, export settings and structure retained in the output |
Drawings and document outputs |
Issued design information exists, for example as PDFs |
Whether editable models, linked files or additional content such as 3D views also exist |
A STEP file does not become an original authoring file simply because a CAD application can open it. It may still carry geometry and, depending on the export, other information or assembly structure. Equally, a native extension does not demonstrate that all dependencies or earlier project states have been retained.
PDF is not a complete description of a document's contents either. A drawing output and a 3D PDF can contain different information. For the initial archive description, state what is known and label assumptions clearly.
One assembly file is not necessarily one complete project
A model may rely on component files, subassemblies and derived drawings. References can point to other folders, libraries or a managed data environment. Counting an assembly file therefore does not establish that the whole project can still be opened or understood.
Record whether those relationships can be traced. Does the technical contact know the source system? Are the associated folders available? Are components stored locally or managed elsewhere? A description such as “assemblies with associated parts present; completeness not yet checked” is more useful than an unsupported claim that every project is complete.
Keep the existing filing structure intact for this first enquiry. Do not reorganise the archive or build a transfer package for BRIDGERS. The first conversation needs an overview, not copies of company files.
Distinguish modelling history, file versions and revisions
The modelling sequence inside a file is different from earlier saved versions of that file. A released revision may be recorded in a PDM or PLM system rather than in the current file alone. What remains available depends on the system and how it was used.
Describe these levels separately where possible. “Earlier versions may be held in the management system” is more accurate than assuming that each file contains the entire development history. If access is uncertain, keep it as an open question. Do not include credentials in an enquiry.
An example of a useful first description
The following is fictional and contains general metadata only. It is not a client case or an offered dataset.
| Attribute | Illustrative archive description |
|---|---|
Engineering work |
Completed mechanical design projects |
Storage |
Original CAD files in project folders, with additional STEP and PDF outputs |
Relationships |
Assemblies and drawings partly connected; library references not yet checked |
Period |
Several project years, with the exact boundary still to be defined |
Quantity |
Unknown; the technical contact can explain the filing system |
Provenance |
In-house and supplied material require separate consideration |
That description is enough to begin a conversation. It does not prove completeness, licensing authority or market value.
Questions you can answer without new exports
- Which CAD systems and versions were used, where known?
- Which of the three file groups are present?
- Can parts, assemblies, drawings and revisions be connected? Are related manufacturing or inspection records identifiable?
- Are earlier states held in files, folders or a management system?
- Who can explain the technical filing structure?
- Which answers are estimates, and which remain unknown? If designs and files have been counted separately, preserve both figures as separate measures.
Technical availability is one part of the picture. The provenance guide separates your own engineering work from customer material, supplier content and libraries. The archive counting guide helps avoid adding unlike quantities, while revisions and bills of materials examines project relationships in more detail.
Enquire with the knowledge you already have
Open questions do not all need solving before you contact us. State the types of records, approximate period and your role. Unknown quantities can remain unknown. This route concerns company engineering archives; an individual model for download is a different use case.
Do not send files, screenshots, project contents or access details. The process overview explains how a description can lead to a separately agreed next step.
Technical references
Autodesk's Inventor Pack and Go documentation explains referenced files. Its Vault documentation addresses versions and revisions, and the saving and exporting guide distinguishes authoring and output formats. These product examples explain the questions; they are not a universal compatibility or partner acceptance list. This guide is not the result of testing your archive.