From CNC Program Handoff to First Good Part

A practical process for receiving, reviewing, setting up, and proving out a new CNC program.

A new CNC program is not ready for production just because it posts without an error. The program, setup, tooling, workholding, offsets, stock, machine, and inspection plan all have to describe the same job. Prove-out is the controlled process that confirms they do.

SAFETY COMES BEFORE PROVE-OUT

Follow the machine builder's instructions, your employer's procedures, and all applicable guarding and lockout requirements. Never bypass an interlock or reach into the work envelope while hazardous motion is possible. Control names and behavior vary by machine.

A COMPLETE HANDOFF

The programmer should release a complete job package, not just an NC file. Every file should identify the part number and revision so the machinist can tell whether the drawing, model, setup sheet, and program belong together.

A useful handoff includes:

• Released drawing and model revision
• Posted NC program and controlled CAM source
• Machine, control, post processor, and post revision
• Setup sheet with stock orientation, workholding, and work-coordinate location
• Tool list with holders, offsets, and stick-out requirements
• Material, stock size, quantity, and inspection requirements
• Notes covering unusual moves, optional stops, or known risks

Stop the handoff when information conflicts. If the setup sheet calls for G54 at the top of the stock but the programmer describes the origin at the finished surface, resolve that difference before entering an offset.

REVIEW THE PROGRAM

Read the setup sheet, drawing, tool list, and program together before machine motion. Confirm the program number, units, active plane, work coordinate, compensation states, canned-cycle state, feed mode, spindle mode, and other modal conditions.

Review every tool call, spindle direction and speed, feed value and mode, work offset, tool-change approach, clearance plane, retract, compensation move, canned cycle, subprogram, macro, coolant command, and program end.

Graphics or CAM simulation is useful, but it does not replace this review. A simulation may not include the exact machine configuration, holder geometry, control settings, fixture details, or posted output that will exist at the machine.

MATCH THE MACHINE TO THE PROGRAM

Verify that the selected machine is the machine named in the handoff. Machines with similar travels can still differ in tool-change position, available M codes, rotary direction, probing routines, and control options.

Load the released program using the shop's approved transfer method and confirm that the file at the control matches the released revision.

Do not quietly repair a questionable program at the control and continue. Record the change, communicate it, update the controlled source, repost when appropriate, and preserve the accepted revision.

BUILD THE PHYSICAL SETUP

Confirm the fixture, jaws, chuck, collet, stops, parallels, clamps, fasteners, stock size, material, and orientation. Locating surfaces must be clean, the work must be adequately supported, and every clamp, jaw, probe, tool setter, tailstock, pallet, and rotary component must have clearance.

Install each tool to match the released tool list. Verify the holder and insert as well as the cutting tool. Confirm length, diameter, radius, orientation, and stick-out using the shop's normal process.

Set the work coordinate from the documented datum. Independently confirm the sign, axis, and reference surface of every entered value. On a multi-operation job, make sure the active work offset belongs to the current operation.

VERIFY BEFORE CUTTING STOCK

Use the verification tools provided by the machine and control. Review the toolpath and program extents in graphics mode when available.

Look for motion on the wrong side of the part, travel beyond machine limits, rapids crossing the fixture, unexpected depth or diameter, missing or repeated operations, an incorrect work offset, or a toolpath starting from an implausible position.

Graphics can reveal gross errors, but a clean display does not prove the setup is safe. The control may not know the shape of every holder, clamp, jaw, or accessory.

RUN THE FIRST CYCLE UNDER CONTROL

Before cycle start, close the enclosure, confirm guarding and interlocks are functioning, clear unnecessary people from the machine area, and identify feed hold, cycle stop, reset, and emergency stop.

Use the control features appropriate to the machine and process. Common prove-out practices include single block, reduced rapid override, conservative feed override, optional stops, and close monitoring of distance-to-go and machine position. These features reduce the amount of motion between decisions; they do not make an unsafe setup safe.

Give extra attention to the first motion after cycle start, a tool change, work-offset change, coordinate shift, spindle-orientation command, subprogram call, or mid-program restart.

Before allowing the next block, confirm:

1. The correct tool, station, and offset are active.
2. The machine is moving in the expected direction.
3. The complete tool assembly has clearance for the entire move.

As the tool approaches the stock, reduce unattended motion. Watch the position display and the physical machine. Once cutting begins, verify spindle load, chip formation, coolant delivery, sound, vibration, and chip evacuation.

INSPECT THE FIRST PART

The first cycle produces evidence, not automatic approval. Clean and identify the part, then inspect it using the drawing and inspection plan. Check the correct revision, datums and relationships, critical dimensions, threads, bores, grooves, chamfers, radii, surface finish, and any witness marks or clamp damage.

Make offset corrections using the shop's documented method. Know whether an entry is absolute or incremental and whether it affects geometry, wear, radius, or length.

If the correction requires a program change, update the master source, identify the new revision, review the affected motion, and repeat the relevant prove-out steps.

RELEASE TO PRODUCTION

A job is ready for production when the program revision, setup, offsets, tooling, and inspection result agree and the responsible person approves the first part.

Capture the accepted program revision, machine, setup corrections, fixture information, tool assemblies, work-offset method, wear strategy, first-off inspection result, in-process inspection frequency, tool-life limits, and operator notes.

Remove temporary prove-out changes. Confirm overrides, optional stops, block-delete state, dry-run modes, and modified offsets are in the intended production condition. Watch the next part closely enough to confirm that the process repeats.

PROVE-OUT CHECKLIST

BEFORE SETUP
□ Drawing, model, program, and setup sheet show the same revision
□ Correct machine, control, and post processor are identified
□ Tools, offsets, feeds, speeds, and clearances are reviewed

AT THE MACHINE
□ Program at the control matches the released file
□ Workholding and stock match the setup sheet
□ Tools, holders, offsets, and stick-outs are verified
□ Work coordinate is set from the documented datum
□ Guards and interlocks are in normal working condition

DURING THE FIRST RUN
□ Single-block and override controls are set appropriately
□ First motion after each major state change is verified
□ Distance-to-go and physical clearance agree
□ Load, chips, coolant, sound, and vibration are acceptable

BEFORE PRODUCTION RELEASE
□ First part passes inspection
□ Corrections are recorded and master files are updated
□ Temporary modes and offsets are restored
□ Accepted revision and setup notes are saved

THE GOAL IS A REPEATABLE PROCESS

Good prove-out is disciplined risk reduction. The programmer makes the intended process clear, the machinist verifies that the physical setup matches it, and first-off inspection confirms that the result meets the drawing.

Need help reviewing a CNC program, correcting a Fusion 360 post processor, or preparing a reliable machining process? Contact Adamantium Machine with your machine, control, program, setup information, and project requirements.