Generic production tools don’t know what an assembly is. OpifexHQ starts where your work starts — the model in SolidWorks.
The difference in one move
You import an assembly and the BOM — parts, materials, quantities, configurations — comes in automatically and the flow sets itself up. No generic MES or ERP does that; there you type it in or upload a CSV by hand.
| What matters on the floor | OpifexHQSolidWorks-native | Generic MESshop-floor suite | ERP / Excelaccounting + sheets |
|---|---|---|---|
| Source of production data | ✓Import from SolidWorksBOM, parts, materials, configs — automatic | ~Manual / CSV | ✗Typed in |
| Per-part flow setup | ✓Automatic + memoryfrom the tree; remembers routes | ~Manual routing | ✗None |
| Live shop-floor tracking | ✓Tablet · QR · batchper-piece, map, delays | ✓Yes | ✗No |
| Revisions & re-import (ECO) | ✓Keeps flow + partsdetects what changed | ~Rarely CAD-aware | ✗No |
| CAD exports (DXF/PDF/STEP, satin, nesting) | ✓Built in | ✗Separate tools | ✗Manual |
| Materials · stock · cost | ✓From the BOM, unified | ~Partial | ~Excel |
| Time to first value | ✓Minutesone import + we set you up | ~Weeks of setup | ✗— |
| Speaks the user’s language | ✓The designer’sassembly, part, config, DXF | ~Generic MES terms | ✗Accounting terms |
We’re not an ERP: we don’t do deep accounting or invoicing. We’re exactly the SolidWorks → production piece that no generic tool covers — and we sit happily alongside whatever you already use for the books.
Request a demo and we do the first import together — we set you up with 30 days free.
Request demo