10xAnd
Scoping review

CADBridge

CAD migration without the re-drawing tax.

Change platforms without paying an engineering team to re-model geometry by hand and chase broken drawing references for a quarter.

Send me the one-pager Request a scoping review
10X-SVC-CADBRIDGE REV B
What
Migration pilot
Price
Fixed by model count
When
2–3 weeks

AI-drafted · evidence-cited · human-reviewed

Why this holds up

01

A method proven on device assemblies

The migration methodology was developed and refined on real medical device assemblies — parts with tight tolerances, controlled drawings, and document-control obligations, not demo geometry.

02

Automated checks, human sign-off per model

Every migrated model is checked automatically for geometric deviation, mass properties, feature integrity, and metadata carry-over. A named engineer signs off on each model’s check result before it is delivered.

03

A verification report you can file

The pilot ends with a migration verification report structured for document control: what was migrated, what was checked, what the tolerances were, and who signed.

How it works

  1. CAD-01

    Pick the pilot set

    A representative assembly — ideally your ugliest one. Complex features, imported bodies, and legacy history are what stress the method, and that is what a pilot is for.

  2. CAD-02

    Migrate

    Geometry and metadata are converted to the target platform with the assembly structure and configuration intent preserved where the target supports it.

  3. CAD-03

    Check and sign

    Automated comparison against the source: geometric deviation, mass properties, feature and constraint integrity, drawing references, PDM metadata. Deviations are listed, not smoothed over. A named engineer signs each model.

  4. CAD-04

    Report and decide

    You get the migrated set, the verification report, and a per-model estimate for the full library — enough to decide whether to run the whole migration at all.

What the work looks like

Source CAD tree through the conversion and check pipeline A source assembly tree of five items enters a pipeline with three stages: convert geometry, carry metadata, then run automated checks for deviation, mass properties, feature integrity, and references. The target tree comes out with a per-item badge: four pass, one is flagged for manual engineer review rather than being marked passed. SOURCE TREE PIPELINE TARGET TREE ASM-100 Top PRT-101 Body PRT-102 Cap PRT-103 Seal DRW-101 Sheet convert geometry carry metadata automated checks deviation · mass features · references ASM-100 Top PRT-101 Body PRT-102 Cap PRT-103 Seal DRW-101 Sheet ✓ checked and signed ! manual review — never auto-passed
FIG. 1 Source CAD tree through the conversion and check pipeline to the target tree, with per-model pass/fail badges. Every badge traces to a check in the verification report.

The offer

The pilot engagement

This is a new service line and we are pricing it to learn: price is fixed by model count in the pilot set, quoted at the scoping review once we have seen the tree.

Intake is limited, because every model in the set gets a named engineer’s sign-off and that does not parallelise. If your pairing is one we cannot migrate well, the review is where you find that out.

Two to three weeks. The pilot deliberately precedes any full-library commitment: if the method does not hold on your geometry, you want to have found that out for a fixed fee on twenty models rather than a project fee on two thousand.

What you receive

  • The migrated assembly set on the target platform, with structure and metadata carried across.
  • A migration verification report: per-model check results, tolerances applied, deviations found, and the engineer who signed.
  • A deviation list naming every model that needs manual attention and why.
  • A per-model cost and schedule estimate for migrating the full library.

What the verification report contains

  • The named engineer and date for every model signed off.
  • The check suite run against each model, and the tolerance applied to each check.
  • Every deviation found, with its magnitude and the disposition decided.
  • Models the automated checks could not fully verify, called out as manual-review items rather than passed.
Get the one-pager Request a scoping review
10X-SVC-CADBRIDGE REV B
What
Migration pilot
Price
Fixed by model count
When
2–3 weeks

AI-drafted · evidence-cited · human-reviewed

Limited intake

Get the CADBridge pilot one-pager

What the pilot covers, how fidelity is verified, and what we need to quote it.

This reaches us as an email and we reply to it — we are not adding you to a mailing list, because we do not run one yet. See the privacy policy.

Questions we get

Which platforms do you support?

Supported source and target platforms are listed in the pilot one-pager. If your pairing is not on it, tell us — the honest answer is sometimes that the pairing needs a feasibility check before we would quote a pilot at all.

How is fidelity actually verified?

By comparison against the source model, not by eyeballing the result: geometric deviation against a stated tolerance, mass and volume properties, feature and constraint integrity, and metadata carry-over. Each check has a pass criterion written down before the migration runs, and each result is signed by a named engineer.

What happens to drawings?

Models and drawings are treated as separate problems, because they are. Model migration is the primary deliverable; drawing handling — regeneration, reference repair, or deliberate re-creation — is scoped explicitly in the pilot so nobody discovers at the end that the views detached. The pilot report states exactly what happened to every drawing in the set.

Does PDM or PLM metadata come across?

Metadata carry-over is part of the check suite: part numbers, revisions, descriptions, custom properties, and configuration data are mapped to the target’s schema and verified per model. Where the target has no equivalent field, that is reported as a mapping gap rather than silently dropped.

Why start with a pilot set instead of the whole library?

Because migration quality is a property of your specific geometry and modelling history, and no vendor can honestly promise a number before seeing it. A pilot converts an unbounded project into a fixed-price test with a report at the end, and gives both sides a per-model estimate grounded in your actual models.

Is the migrated data usable in a regulated file?

That is your quality system’s call, which is why the pilot produces a verification report rather than just files. The report is built to be filed as objective evidence that the migration was checked, against stated criteria, by a named reviewer.

Other ways we 10x device programs