A milling shop's real archive is not the drawing cabinet. It is a folder on one PC, named in a way only its owner understands, holding CAM files, tool libraries and a post-processor he has adjusted over years. Beside it sits his memory. He knows which casting rocks in the vice unless the left jaw gets a shim. He knows which bracket needs a lighter step-over on its thin wall, and which customer's revision C moved a dowel hole.
When that programmer goes on leave, repeat orders slow down. When he resigns, they can stop for weeks.
Signs on the floor
- A repeat order lands and the setter cannot tell which of three similarly named files is current, so he waits or phones the programmer at home.
- New parts queue behind one CAM seat while machines run old work and enquiries go unanswered.
- Setters relearn how to hold a gearbox cover that was solved last year, and scrap the first one again.
- The programmer edits feeds at the control to cure chatter, and the change never reaches the master file.
- Nobody else can open or post the toolpaths, so a dead laptop becomes a production stoppage.
What the shop pays for it
The direct cost is time. A repeat housing that should run on Monday waits until the toolpath is rebuilt. First-offs on old jobs fail more often because the clamping note was never written. Delivery promises turn into guesses. The hidden cost is bargaining power. A programmer who knows he is irreplaceable can name his price, and a competitor who senses it can make him an offer. Either way the shop's future rests on one man's decision.
How the memory ends up in one head
Small lots leave no slack. There is a new part to program every day, so recording an old one never feels urgent. The programmer is praised for turning round new work, not for making his knowledge usable by anyone else. The person who could learn from him usually has a full machining centre to run. Without a name, a schedule and a reason, the second programmer never appears.
Spreading the memory in five moves
- 1
Count the jobs only one person can run
Ask the programmer to list each repeat part that he alone could program or prove. Sort the list by how often each is ordered. The top ten become your first job packs.
- 2
Build a job pack for each repeat part
File name and version, post used, tool list with holder and stick-out, and a fixture or vice sketch with clamp points. Add the work zero and probing routine, first-off notes and the drawing revision. Keep the folder on a shared drive and a printed page at the machine.
- 3
Move master files off one PC
Store programs on a shared drive with a fixed naming rule and a weekly backup. Any edit made at the control is written on the job pack and copied back to the master that same day.
- 4
Name an understudy and give them live work
Choose a setter who already reads G-code and understands workholding. Give them one repeat job a month to program from scratch under the senior's review, then one new job each quarter.
- 5
Reward the handover
Make job packs and the understudy's progress part of the senior's review and pay. Say plainly that his role grows, perhaps toward process lead or fixture design, as others take on routine programming.
One quick test shows where you stand. Pick three repeat parts at random. Can someone other than the programmer find the right file, the right revision and the clamping note within ten minutes? If not, start there.
Keeping the senior programmer on side
Programmers resist documentation when it looks like the first step toward being replaced. Say the opposite and mean it. A programmer whose routine work is shared can take on harder parts, five-sided fixtures or customer discussions about manufacturability. Check his salary against nearby shops before someone else tells him what he is worth. If the gap is real, close it as part of the same conversation about job packs.
More for milling shops
Our CNC milling shops page sets out the other strains in this business, from setups all day to late drawing revisions. Job packs are a records problem first, covered under keeping job packs and role notes current. The understudy idea is developed in naming a second programmer before you need one.
Pay is the subject of programmer and setter salaries against nearby mills. The route from operator into setting in teaching offsets and probing in stages. Our precision machining people hub maps the whole trade.
