Onshape production files
Generate STEP packages from supported named-version Onshape parts and assemblies using the local bridge. Publish root or individual child files into existing working copies, then review each native change request. Vendor-account acceptance remains pending.
Read the workflow docs →Onshape part-number writeback
Review number allocation for supported local workspace parts, bind each native record to its exact CAD identity, and explicitly write the issued reference back to Onshape. This separate local workflow requires vendor-account acceptance.
Read the workflow docs →Siemens NX counted assemblies
Export supported saved NX assemblies with the local Windows adapter, then review counted parts and quantities before importing. The adapter has a defined assembly scope and awaits actual NX-runtime acceptance.
Read the workflow docs →Altium and KiCad electrical packages
Review supported Altium electrical reports or KiCad board packages, including BOM and manufacturing evidence. A counted Altium CSV bridge supports manual BOM imports; the component-library connector has separate setup and licensed-runtime requirements.
Read the workflow docs →Spreadsheet baseline comparison
Map a local CSV baseline and compare exact internal part numbers, quantities and optional component details with a saved electrical package. Review differences before preparing a board change; source files are not monitored in the background.
Read the workflow docs →Altium component-library connector
Run the operator-hosted Generic Connector to expose supported ManyRows component parameters to Altium. Altium owns full and incremental sync scheduling and library commits; retained source exports do not prove target application. Licensed-runtime acceptance remains pending.
Read the workflow docs →CAD assembly import
Use local exporters for FreeCAD, Onshape, Inventor, Fusion, SOLIDWORKS and NX to prepare a snapshot, then review it in the assembly’s CAD tab. Each exporter includes setup instructions and defines its supported assemblies.
Read the workflow docs →FreeCAD runtime validation
Saved Part/Link assemblies were exercised in FreeCAD 1.1.4 on macOS arm64, including shared parts, quantity changes and native import replay. Onshape, Inventor, Fusion and SOLIDWORKS still need acceptance in their actual vendor runtimes.
Read the workflow docs →Review before applying
Inspect matched and new parts, exact quantities and proposed BOM changes before importing. Imports opened from a record are restricted to that assembly, and omitted BOM lines are retained.
Read the workflow docs →Send exports directly for review
Send locally exported snapshots into the assembly’s CAD review queue. Check destination access before exporting, recover interrupted sends without duplicates, and review a fresh preview before changing the BOM.
Read the workflow docs →CAD changes through approval
For approval-required records, prepare a draft change request from the snapshot. Review and submit it through the usual workflow; the live BOM changes only after approval.
Read the workflow docs →Source mappings and import receipts
Keep source component identities and accepted import receipts alongside each record. Re-importing an identical accepted version is a no-op. Source history records what was imported; it is not a live connection to your CAD application.
Read the workflow docs →Initialize CAD properties
Map supported properties into new parts with the FreeCAD, Onshape and Fusion exporters. Review incoming values before applying; existing records keep their attributes. Destination field types and units must match.
Read the workflow docs →Native files and 3D review derivatives
Keep original CAD files in Documents and inspect self-contained GLB derivatives with cross-sections and approximate mesh-distance measurements. Connect geometry to product and direct BOM records while preserving the exact model behind a revision. Assembly imports use reviewed snapshots.
Read the workflow docs →