One geometry.
One identity.
Gauge.ID computes a deterministic, replayable identity for CAD parts — certified under declared policy.
- ▸Same file, same policy, same Gauge.ID — run it twice, on any two machines, and the bytes match.
- ▸Every verdict is issued under the tolerance and equivalence rules you approve, with a signed, replayable record.
- ▸No silent guesses — anything that cannot be certified is flagged for engineering review.
Aerospace & Defense · Medical Device · Automotive · Industrial Robotics
Certified under the declared policy · replayable. Digest shown is from a real engine determinism run — same input, byte-identical on replay.
A pilot audit takes a sample of your library, runs it under a policy you approve, and returns three things.
A Gauge.ID for every part — stable across pose, format, and export path. The same geometry gets the same identity, every run, on any machine.
Duplicate and near-duplicate findings with consolidation candidates — each one recorded together with the policy it was judged under, ready for your PLM workflow.
A signed report you can re-run: same inputs, same policy, byte-identical results — on your hardware or ours. Anything that could not be certified is flagged for engineering review, never silently guessed.
- A Evaluated on a 49,994-part public engineering corpus (ABC dataset); results deterministically replayable. Run reports available during a pilot.
- B Cost figures are industry planning estimates, not Gauge.ID measurements; the cost model exposes every assumption as an editable input.
of part numbers duplicated or obsolete Industry studiesB
of engineering time lost to redundant work Industry estimatesB
lifecycle cost per unnecessary part Industry estimatesB
capture rate assumed in our cost model Modeled
§01What is geometric canonicalization?
Geometric canonicalization transforms CAD geometry into a normalized representation that is invariant to translation, rotation, and reflection. Gauge.ID produces a deterministic, replayable identity for a 3D geometry under a declared policy — the tolerance and equivalence rules you approve — so parts match consistently regardless of pose, file naming, or export path. We do not claim absolute uniqueness: identity is certified up to the declared policy, and the certificate says so.
§02How does Gauge.ID identify duplicate CAD parts?
Gauge.ID computes a canonical identity for each part and compares identities under your declared policy. Exact duplicates and near-duplicates surface even when parts differ in name, file format, or orientation. Every comparison is recorded and replayable, and anything that cannot be certified with confidence is flagged for engineering review rather than guessed.
§03What CAD file formats are supported?
The engine operates on mesh (STL, OBJ) and B-rep (STEP) geometry today; any CAD system that exports these neutral formats is supported — including CATIA, NX, Creo, SolidWorks, Inventor, and Solid Edge via their standard export paths. Native-format readers and PLM connectors (Teamcenter, Windchill) are roadmap items.
§04How does an evaluation start?
With a pilot audit: we run a sample of your library under a declared policy and return a signed, replayable report. Pilots typically start within days because the engine runs on your exported geometry as-is. Production integration timelines depend on your PLM/ERP landscape and are scoped during the pilot.
§05Which compliance standards does this support?
Gauge.ID is designed to support workflows governed by AS9100, ISO 13485, IATF 16949, FDA 21 CFR Part 820, and ISO 9001: replayable audit trails, versioned policies, and traceable comparison records help you demonstrate due diligence during audits. Compliance obligations remain the customer's; we provide the evidence trail.
§06Can we cite Gauge.IDs in DOORS, ECOs, or a DHF?
Yes. A Gauge.ID with its policy reference is plain text, so it pastes into a DOORS or Jama requirement attribute, an ECO/ECN package, a DHF entry, or an FAI record today — with the signed replayable report attached as evidence. Anyone holding the record can re-verify the citation later: re-run it, and the bytes match. Native requirements and PLM connectors are roadmap items.
§07Is my CAD data secure?
Data is encrypted in transit (TLS 1.3) and at rest (AES-256). Hosted evaluations run on cloud providers holding SOC 2 Type II attestations; GaugeID LLC has not yet completed its own SOC 2 audit, and our controls and roadmap are available under NDA. For strict residency or export-control requirements, on-premise and air-gapped deployment keep geometry inside your network. The browser demo parses files locally and uploads nothing.
Run a pilot on your own library.
A sample of your parts, a declared policy, a signed replayable report. Verify the determinism claim yourself: run it twice — the bytes match.