Case study: From a month on the shop floor to 14,420 programs delivered

When CNC Programming Becomes a Long-Term Engineering Function

CNC programming is often treated as a task with a clear beginning and end: a program is written, validated, and handed over. In most production environments, however, the reality is more continuous. Machines are updated, components are revised, tolerances are reviewed, and programs need to be rewritten or refined to reflect those changes. For manufacturers operating at high volume with tight quality requirements, programming is not a one-time deliverable — it is an ongoing engineering responsibility.

This case began with that understanding on both sides.

The Context: High Precision, No Margin for Error

Our client is a manufacturer of pharmaceutical packaging machines — equipment used in the production and handling of medications in blister packs, sachets, and vials. The machined components inside these machines operate within tight dimensional tolerances. Any deviation in the machining program translates directly into a part that does not perform as specified, which in a validated pharmaceutical production environment carries significant consequences.

The client needed a CNC programming partner that could work inside their production system — not alongside it. That meant using their software, following their documentation standards, and maintaining the same level of quality consistency that their internal engineers applied. The technical requirements were well defined. The harder requirement was organisational: finding a team that would genuinely integrate rather than operate as a separate external supplier.

Starting with the Production Floor, Not the Software

Before a single program was written, our team lead spent over a month at the client’s manufacturing facility. The purpose was not administrative onboarding — it was direct exposure to the production environment. During that period, it was possible to observe the full production cycle first-hand: from planning and blank material ordering, through tool preparation, to machining and final quality control.

That level of visibility changes the way programs are written. Understanding how a tolerance that looks acceptable on paper behaves differently on the actual machine — in the specific cutting conditions, with the specific tooling, on the specific equipment — is knowledge that cannot be transferred through documentation alone. It requires time on the floor.

This immersion phase was the foundation on which the rest of the cooperation was built.

Integration into the Client’s Production System

Following the immersion phase, the team was integrated into the client’s software environment. Programs are written in SolidCAM and validated in Vericut before they are passed to production. All work goes through the client’s own file structure, naming conventions, and revision control process. There is no separate GFE system running in parallel — the team operates as a direct extension of the client’s programming department.

This approach required an adjustment period on our side, not on the client’s. The client’s internal workflows did not change. The GFE team learned and matched them. That distinction matters in practice: when an external team requires the client to adapt their processes, it creates friction and additional management overhead. When the external team adapts instead, the cooperation becomes transparent.

Results: Six Years, 14,420 Tasks

The cooperation that began in January 2019 is still active. Over six years, the team has completed 14,420 programming tasks and made seven visits to the client’s facility. The scope has remained consistent: NC programs for the machined components of pharmaceutical packaging machines, written and validated to the client’s standards, delivered through the client’s system.

The duration of this engagement is itself a result. Long-term technical cooperation of this kind only functions when the output is consistently reliable and when the working relationship between teams is well established. Both conditions have been maintained throughout.

What This Model Requires

This case is not typical of a short-term programming subcontract. It required a willingness on both sides to invest in a proper integration phase before expecting results. For the client, that meant allowing our team lead access to their production environment for an extended period. For our side, it meant treating that time as a prerequisite — not a cost to be minimised.

The engineering output that followed was a direct consequence of that investment. When programming decisions are informed by direct knowledge of how the machines behave, how the tooling is managed, and how quality is verified, the programs produced are more accurate and require fewer iterations. Over six years and more than fourteen thousand tasks, that difference accumulates significantly.

For manufacturers considering external CNC programming support, the question worth asking is not only whether the technical capability exists, but whether the proposed working model will allow that capability to be applied consistently over time.