BRIDGERSDiscuss your archive Direct contact
Menu

CAD guides

Keep models, revisions and BOMs in their engineering context

An archive description should explain more than which files exist. Which drawing belongs to which model? What parts make up an assembly? Which state was changed later? Those connections can help someone follow an engineering decision and understand the documented result.

You do not need to rebuild missing relationships before contacting BRIDGERS. Start with what is known and identify the uncertain links. We can discuss which part of the archive provides a sensible starting point for a possible next step.

Discuss your CAD archive No files needed for your first enquiry.
Traceable design revisions with their associated bill of materials REV. AREV. BREV. C DESIGNREVISIONAPPROVAL
Connected design, revision and approval. Schematic illustration.

Different relationships answer different questions

A model-to-drawing relationship connects a design with its technical representation. An assembly-to-BOM relationship identifies the components in a defined configuration. A revision sequence shows changes between states. Links to manufacturing or inspection records may indicate what was made or checked.

These relationships may be visible in a CAD or PDM system, folder structure, file properties or internal register. Similar filenames alone do not prove a reliable match. Nor does a modification timestamp necessarily establish which version was technically released.

A fictional assembly example

This example contains no real company or partner data.

Record Known relationship What can be said about it
Mounting-bracket assembly, state B
References its base plate and fasteners
The component arrangement is identifiable.
Base-plate drawing, state B
Matches the part model within that assembly
Model and manufacturing representation refer to the described state.
Bracket BOM, state B
Lists the assembly's components
Quantities and component references exist as a separate record.
Change note from B to C
Describes a revised hole
One development step is documented.
Inspection report
Its relationship to the part is not yet clear
It should not be attributed to that revision without checking.

The unresolved final row is as important as the clear matches. It prevents an available report from being presented as evidence for a design state that it may not concern.

Make gaps visible rather than filling them with assumptions

Some archives contain only final released designs. Others contain many intermediate versions but little explanation of the changes. Both can be described accurately. A series of similarly named files is not automatically a complete development history.

Use distinctions such as clearly matched, partly matched or currently unknown. Missing drawings, orphaned references and unavailable libraries can be identified separately. You do not need to restore an incomplete assembly merely to make the initial enquiry.

More context does not mean more independent designs

A part, its drawing and several exports may be separate files representing the same design. Counting every record as a separate engineering design would misstate the scale. The archive counting guide separates files, design states and independent constructions.

Technical relationships and licensing authority also remain different questions. A supplied component cannot be cleared for additional uses simply because it fits an assembly. The provenance guide helps keep original work and received material distinguishable.

Preserve the context in a later sample

If a sample is agreed after the conversation, a few complete, representative native projects may explain more than disconnected printouts. The permitted assemblies, references, drawings and supporting records are defined beforehand. Existing project and folder relationships should remain understandable within that approved scope.

The native CAD files guide explains the difference between source material and exports. The licensing process shows where a separately authorised sample fits into the discussion.

Discuss the context in your CAD archive

Start with what you know.

A description of your CAD archive is enough to begin. Your first enquiry and conversation are non-binding. Please do not send files or confidential project examples.

Discuss my archive