A Reddit thread in r/manufacturing asked how small shops bridge the gap between CAD and production. Twenty-three comments came in — ranging from printed travelers to shared Dropbox folders to custom Fusion 360 dashboards. No two shops described the same system. The only consensus: whatever they’re doing, it’s held together with naming conventions and institutional memory.

The CAD-to-production gap is not one problem. It’s four overlapping failures that compound each other, and small fabrication shops feel every one of them because they can’t throw PDM licenses and MES platforms at the problem.

The Four Failures

1. Format Translation Loss

A SolidWorks sheet metal part carries rich parametric data: material, thickness, bend allowance, K-factor, grain direction, part number. When exported as DXF, nearly all of that disappears. What reaches the laser cutter operator is a flat 2D outline — no thickness, no material callout, no bend sequence, no revision number.

Most engineers don’t manually type metadata into the filename or embed it as DXF text entities. The press brake operator opening the DXF in their nesting software sees a flat outline with no label. Material thickness gets communicated separately — usually by the naming convention or an accompanying PDF. When the filename says bracket.DXF and the accompanying PDF is from a different revision, the operator has no way to reconcile them.

2. Version Control Without a System

SolidWorks PDM costs thousands per seat and requires a server. Small shops fall back on shared network folders, Dropbox, or email. These have no file-locking, no check-in/check-out, and no assembly-reference tracking.

The specific failure mode with Dropbox: it syncs on every Ctrl+S. A half-finished revision propagates to the shop floor the moment an engineer saves. Moving a subfolder breaks all external references in assemblies. There’s no equivalent of “this is the released revision” — just a folder of files with incrementing names like bracket_v3_FINAL_new.DXF.

The standard folder structure used by shops without PDM:

Jobs/
  [Customer Name]/
    [Part Number]/
      CAD/      ← SolidWorks files (.SLDPRT, .SLDASM)
      DXF/      ← Exported flat patterns
      Drawing/  ← PDFs of engineering drawings
      CAM/      ← NC programs

There’s no enforceable link between a CAD file and its exported DXF. An engineer updates the SolidWorks part, but the old DXF in the shared folder stays until someone manually re-exports — if they remember.

3. BOM Data Re-Entry

When an engineer finishes a design and a job is opened in the ERP (or more commonly, in a spreadsheet), someone manually reads the drawing and types part numbers, quantities, and materials into a work order. The industry data on this is sobering: engineers report spending roughly a fifth of their working time correcting BOM errors rather than designing. A single decimal-point error in a BOM has been documented to cost $45,000 in scrapped material.

This is the same problem described in detail in our post on why PDM doesn’t solve the downstream BOM problem. The data doesn’t break in the CAD system — it breaks at handoffs.

4. The K-Factor Mismatch

CAD software uses a default K-factor (typically 0.44) representing a theoretical average for A36 mild steel on a standard V-die. It doesn’t represent aluminum 5052-H32, doesn’t match 6061-T6, and doesn’t account for the specific V-die width the shop’s press brake operator uses.

Two shops using the same DXF file and the same material can produce flat patterns that differ in length because their V-die widths differ. The result: laser-cut blanks that fold to the wrong dimensions, misaligned assembly holes, and scrapped material.

The single most important question engineers almost never ask their supplier: “For this material and thickness, what V-die width do you use, and what K-factor should I input in my CAD?”

How Small Shops Actually Bridge the Gap

The Paper Traveler

The job traveler — also called a router card — remains the backbone of production in thousands of small fabrication shops. It’s a paper packet (sometimes in a plastic sleeve) that physically follows the part through the shop:

  • The printed 2D drawing or DXF print
  • A routing sheet listing every operation: laser cut → deburr → bend → weld → paint → inspect
  • Material callouts, quantities, due dates
  • Spaces for operators to sign off each step

This paper packet is the only mechanism carrying design intent from the CAD file to the press brake operator. When the customer changes a quantity, the traveler gets reprinted. When it gets lost in the shop, it’s reprinted from scratch — and any handwritten notes about setup variations or tooling substitutions are gone.

ProShop ERP documented the specific failure modes: “Enormous costs are incurred every day because of paper travelers. These costs are not obvious and aren’t on top of people’s minds.” Workers can’t start their operation because the physical packet hasn’t reached their station. Job-splitting means photocopying the packet — messy and error-prone.

The Whiteboard

For very small shops (3–5 machines), a magnetic whiteboard with columns per machine and rows per day is the dominant scheduling system. A software developer surveying small shops on Practical Machinist found this was the most common approach — with one consistent complaint: “a huge pain to rewrite every day.”

The whiteboard has one advantage no software matches: anyone in the shop sees full production status in 10 seconds.

The Shared Folder + Naming Convention

Without PDM, the naming convention is the version control. Some shops enforce patterns like {PartNumber}_{Rev}_{Material}_{Thickness}.DXF. Others use {JobNumber}_{SequenceNumber}.DXF. Most use whatever the last engineer decided felt right.

What breaks: the naming convention is informal and inconsistent across engineers and jobs. When a new hire joins, they learn the system by asking a coworker. When that coworker leaves, the institutional knowledge goes with them.

The Outsourcing Escape Valve

A growing number of small shops — product development shops, one-person operations, hardware startups — outsource sheet metal cutting to services like SendCutSend or OSH Cut. This sidesteps the shop floor file management problem entirely.

SendCutSend runs 100–200 automated DFM checks on upload, catching open contours, duplicate lines, holes below minimum size, and short flanges. Engineers describe this as the first time they get real manufacturing feedback on a design — before any material is cut.

The tradeoff: no institutional knowledge accumulates, finishes require separate suppliers, and iteration turnaround is 2–4 days rather than same-day. And bend data is still the engineer’s responsibility — if your K-factor assumption doesn’t match the service’s V-die tooling, the folded part will be wrong.

The DXF Export Problem Specifically

The SolidWorks-to-laser-cutter workflow has several documented failure points that small shops hit repeatedly:

Bend lines disappeared in SolidWorks 2022. Prior to 2022, bend lines were automatically placed in a DXF layer called BEND. SolidWorks 2022 removed this default. Shops that upgraded without noticing began sending flat-pattern DXFs to press brake operators with no bend lines — operators received a cut blank with no guidance on where to bend.

Splines become hundreds of short line segments. Curved cutouts get tessellated during DXF export into many short linear segments. CNC laser controllers interpret each segment as a discrete move, slowing the cut and sometimes rejecting the file. Exporting splines as polylines requires a manual option toggle.

Metadata is absent. Standard SolidWorks DXF export contains only geometry. Material type, thickness, part number, revision, and quantity live in SolidWorks custom properties but don’t transfer to the DXF. Everything fabricators actually need from a DXF file beyond raw geometry requires separate communication — typically through the naming convention or an accompanying PDF.

Scale errors from drawing sheets. When exporting DXF from a SolidWorks drawing (not from the part directly), if the sheet has a scale factor (e.g., 1:10), the exported DXF can inherit that scale. A 500mm part exports at 50mm. This failure has been reported by users who submitted files to laser cutting shops and received parts an order of magnitude smaller than designed.

What Engineers Build to Fix This

Community evidence shows a class of technically sophisticated shop owners building their own bridges:

  • VBA macros that batch-export all flat patterns from an assembly, apply consistent file naming, and dump DXFs into a network folder organized by job number. Reported time savings: from 5–7 minutes per assembly to under 2 minutes.
  • QR codes on travelers that link back to the source CAD file, reducing “wrong revision” problems because the operator can scan and verify the file date.
  • Custom dashboards — the Reddit thread that prompted this post described a Fusion 360-based shop floor system built from scratch. Multiple commenters described similar custom builds, each solving the same problem slightly differently.

Open-source projects like Assem2DXF on GitHub tackle the batch export problem specifically. They all converge on the same workflow: traverse assembly → find sheet metal parts → flatten → export DXF with naming convention → organize into folders.

Where CadShift Fits

CadShift addresses the DXF export step: batch export from assemblies with material, thickness, part number, and quantity embedded as DXF text entities. Bend lines are auto-trimmed to correct length for laser etching. PDFs get QR codes linking to documentation.

It doesn’t replace PDM, ERP, or the conversation between engineer and fabricator about V-die widths. But it automates the most time-consuming manual handoff in the chain — getting correct, labeled, revision-matched DXFs from an assembly to the shop floor without re-exporting one part at a time.

The honest framing: CadShift solves one painful step in a longer chain of manual handoffs. The paper traveler, the naming convention, the K-factor conversation — those remain the shop’s responsibility. But eliminating the hour spent manually exporting, renaming, and organizing DXF files from a 50-part assembly means that hour goes to the work that actually requires human judgment.