Explain what someone could learn from the records
A single part model and a connected project history offer different kinds of information. Drawings, assemblies, revisions and inspection results can add technical context where they genuinely belong to the same design.
A large collection of unrelated exports may leave important relationships unresolved. A smaller, coherent group might support a different research task. That is not a universal ranking of archive types: the intended use also matters. An archive is not accepted simply because it contains one preferred format or a long history.
| Characteristic | What you can describe for the discussion |
|---|---|
Engineering content |
Parts, assemblies, drawings or connected project sets |
Source material |
Authoring systems, known versions and exchange formats |
Development history |
Traceable changes, release states or design decisions |
Supporting records |
Related BOMs, manufacturing records or inspection reports |
Readability |
Known access, missing references and system dependencies |
Permission to license |
Original work, third-party material and existing restrictions |
The aim is to make these features understandable. You do not need to prove that every project is complete before describing the archive.
Treat quantity, age and quality as different factors
Files, independent designs, revisions and duplicate copies are not interchangeable quantities. State what has been counted or estimated. Unknown volume is a valid starting point; the archive counting guide provides a practical way to keep the categories apart.
Age alone is not evidence of suitability. Older records still need to be readable, intelligible and usable for the proposed purpose. They may also disclose know-how used in current products or remain subject to customer obligations. A date on a folder cannot settle those questions.
Rights and licensing scope affect the available opportunity
Technically interesting content must also be available for the intended use. Customer drawings, supplier models and library components can carry separate conditions. The provenance guide helps identify where those conditions may need review.
Purpose, recipients, duration and any exclusivity are further matters for negotiation. Existing licences can constrain what remains available to offer. An exclusive licence does not automatically produce a particular or higher payment. Its meaning depends on the exact scope agreed.
A description that gives the conversation a useful starting point
Consider this fictional business archive: it covers several product generations, includes native assemblies and drawings, and has revisions that can partly be matched. File volume is estimated. Supplier components and current product ranges still need to be separated.
That description identifies something concrete to discuss. It also shows what the first conversation can achieve: outline a sensible subset, identify technical questions and establish who needs to clarify permissions. It is not a valuation or evidence that an offer will follow.
Move from an overview to a possible offer
Bring the information you already have. BRIDGERS can discuss an appropriate next step with you. If a representative sample becomes useful, its content, recipients and protection arrangements are agreed before transfer.
The licensing process explains how that separate review may lead to a commercial discussion. Actual demand and further assessment are needed before there can be a concrete offer.