A full sheet of panels with the holes in the old place
The customer moved two holes on a panel and sent a new drawing. The drafter updated the flat pattern and saved it in the job folder. The nesting library still had the previous DXF, imported the last time the panel was made. The programmer searched the library by part number, found it, and nested twelve panels.
They were cut, bent and powder coated before anyone noticed the holes did not line up.
Why the wrong file gets nested
Sheet metal parts pass through several pieces of software: the customer's CAD, your CAD for unfolding, the nesting software and sometimes the brake's offline program. Each keeps its own copy. When a revision changes, one copy is updated and the others stay as they were.
- The nesting library holds old imports that are never cleaned out.
- DXF file names do not include the revision.
- Customer DXFs are nested directly without checking against the drawing.
- Repeat orders pull whatever file was used last time.
- Nobody checks queued nests when a revision arrives.
What a wrong file costs
Scrapped sheets and parts, often after bending and finishing have been added. Remakes that push the delivery late. A customer who wonders what else you might have got wrong. And the risk of it happening again, because the old file is still sitting in the library.
The DXF control we build
- Each part revision has one approved flat pattern, checked by the drafter against the drawing, held in a single store with the drawing it came from.
- The nesting software's library is fed from that store. Old revisions are marked superseded or removed from the library, depending on what your software allows.
- File names and metadata carry the part number and revision, so a nest report shows exactly which revision was cut.
- When a new revision is approved, the tool checks queued and planned nests for the old revision and warns the programmer to re-nest.
- Customer supplied DXFs are compared with the drawing's key dimensions and hole counts before approval, and differences are flagged.
- Repeat orders always pull the current approved revision, never the file from the last job folder.
| Point of risk | Check in place |
|---|---|
| New revision received | Old flat pattern superseded in the store and library |
| Nesting | Only approved revisions available |
| Queued nests | Warned if a part's revision has changed |
| Customer DXF | Compared with the drawing before approval |
| Repeat order | Current revision pulled automatically |
What changes for the programmer
The programmer picks parts from a library that only offers current, approved flat patterns. A new revision arriving mid week flags any nest that is affected, before it is cut. Nest reports show the revision, so traceability to the drawing is clear. The drafter's check at approval becomes the one point where a flat pattern is trusted, rather than every copy being trusted a little.
It also makes the nesting library smaller and easier to search, because it stops collecting every file ever imported.
Customer changes are handled more calmly too. When a revision lands the day before a big nest is due to run, the programmer is told which nests contain the part and which sheets they were planned on, so only those nests are rebuilt. Without that, the choice is between re-checking everything by hand or trusting luck.
Is the wrong file a risk in your shop?
- Parts have been cut from an old DXF.
- The nesting library is full of old imports.
- DXF names do not carry the revision.
- Customer DXFs are nested without checking.
- Queued nests are not checked when revisions change.