Forty-six lines on the cutting list for a new machine frame: profile, length, miter, quantity. The cut-off saw has a control that can import such a list without any trouble. Yet a work planner spends an hour keying those lines in, because the list leaves the CAD environment as a printout and the saw expects a file. The model already knew everything; somewhere on the way to the machine it turned into paper.
That intermediate step is no exception, and it is not limited to the saw. Between CAD and the shop floor run more data streams than the familiar DXF for the sheet cutter: cutting lists, drilling files, bending programs, machining data. Wherever such a stream is interrupted by retyping, you pay twice: in hours and in typos that only surface during assembly. This article maps out how to get CAD data to production machines directly, which format each workstation needs and where a toolbox like Thundercad takes over the manual work.
One boundary up front: the stream from flat pattern to cutting machine, with layers, engravings and delivery conventions, was covered in detail in Sheet metal: from flat pattern to a DXF your laser cutter loves. Here we look at the complete picture, from saw to press brake.
Map the streams first
Walk through an order in your mind and note, per workstation, what information it needs and how it gets there today. At most machine builders and sheet metal shops it looks roughly like this:
| Workstation | What the machine needs | Where it already lives in CAD |
|---|---|---|
| Cutting machine (laser, plasma, waterjet) | Contours and engravings as DXF | The flat pattern of every sheet part |
| Cut-off saw | Cutting list: profile, length, miter, quantity | Model and BOM |
| Drill or saw line | NC file per profile | The 3D model of every profile |
| Press brake | Bending program or flat pattern with bend lines | Flat pattern and 3D model |
| Machining center | STEP for the CAM package | The 3D model of the part |
The right-hand column is the point: almost everything the machines ask for already exists in the model. So the question is never whether the data is there, but in what form it makes the crossing: as a file the control imports, or as paper somebody retypes.
The cutting machine: the stream that usually runs already
It is no coincidence that the DXF stream to the sheet cutter is the first one sorted out almost everywhere. The volume is high, the format is a widely accepted standard and the nesting software on the other side handles it natively. If you still write those files away one by one, you can at least speed that up: with Export DXF you convert a drawing in a single action, without clicking through the same export dialogs every time.
More interesting is what this stream teaches you for the rest. It runs because three things are fixed: the file format, the agreements about content (layers, engravings, bend lines) and the delivery moment. You need exactly those three ingredients at every other workstation too. A format without agreements produces files the operator still has to correct; agreements without a fixed delivery moment produce outdated files.
Cutting lists and drilling files: retyping in miniature
The saw is the neglected child. While the cutting machine receives files, many saws have a clipboard hanging next to them with a printed list, and the operator keys the dimensions into the control. That easily costs half an hour per frame, and every line is a chance of a swapped length or a forgotten miter. Modern saw controls import a simple list, often as CSV or a vendor-specific list format. Such a list is essentially nothing more than a BOM export with the right columns in the right order: with Export BOM you push the bill of materials into a fixed Excel template that delivers exactly those columns.
The same story applies to drill and saw lines, one size up: those controls expect an NC file per profile, generated from the 3D model. If that stream does not exist, somebody at the machine programs every hole again from the drawing. On a platform staircase with dozens of identical hole patterns you feel immediately where that chafes: double work, and a second moment of interpreting the same geometry.
How many lines does your work preparation retype every week? Thundercad exports your drawing set, DXF files and BOMs straight from the current state of your model, so the shop floor receives files instead of paper.
Try 30 days freeThe press brake: 3D or flat pattern, no interpretation
Bending is the stream where the most gets lost without anyone calling it waste. Without supplied data, the press brake operator builds the program himself: reading views, working out a bend sequence, choosing tooling, making a test bend. With a flat pattern including bend lines, or a 3D model as STEP for the offline bending software, most of that puzzling disappears and interpreting is reduced to a final check.
You see the same pattern at the machining center: the CAM package wants the 3D model, not a drawing to copy dimensions from. The drawing remains important as a document for inspection and acceptance, but geometry should be entered exactly once, and that is in CAD.
One release moment instead of loose files
As soon as several streams run, a new problem appears: fragmentation. The DXF files go to the cutter on Monday, the cutting list follows on Tuesday, and on Wednesday the model changes. Which files are still current? That is why data streams need a fixed release moment: after release you generate the complete package in one run. With Batch Publish you export all drawings of an assembly in bulk to PDF, DWG, DXF and STEP, also in combination with Vault, so everything comes from the same state.
What belongs in that package per recipient and how to keep the overview is covered in The complete production package: what do you deliver, and to whom?. For the machines, add one agreement on top: every workstation has a fixed folder or delivery point, so the operator never has to search or guess which version applies.
Where people stay in the stream
Data streams replace the retyping, not the craftsmanship. Nesting remains the cutter's trade-off, rush jobs remain human work and an operator who spots an odd dimension should absolutely keep picking up the phone. The difference is that those people decide and check instead of keying data in. Three questions to start with this week:
- Which workstation gets its information via paper or retyping today, and how many lines per week is that?
- Which file format can that station's control import? Ask the operator or the supplier.
- Where does that information come from right now: straight from the model, or from a copy somebody maintains?
Start with the stream that has the most lines per week; that is where the gain shows fastest and where support grows quickest.
Frequently asked questions
Our saw cannot import files at all. Is this still worth it?
Yes. Even a printed list that comes straight from the model beats a retyped one: the retyping is the error source, not the paper itself. And when a replacement investment ever comes up, put the control's import options on the list of requirements.
Should such a stream run through the ERP system, or may a file go straight to the machine?
Both happen and both work, as long as there is one source and one release moment. ERP is strong at quantities, orders and planning; geometry and programs travel as files. Above all, agree who releases and where the files live per workstation, otherwise shadow copies appear anyway.
Where do I start without a big automation project?
Pick one stream and one machine, and give yourself a few weeks. Measure beforehand how many lines are retyped per week and how much time that takes, then compare. If you want to speed up the export side right away, you can try Thundercad free for 30 days.