Trial Batch Scheduling: Capacity and Production Handback

Schedule an engineering trial with a defined question, reserved resources, stop conditions and a production handback plan. Approve the time it takes away from committed orders before releasing the trial to the floor.

This guide is for a production planner and development engineer sharing machines with customer work. Use it when a new material, tool, program or process trial needs time on a production resource. The trial owner prepares the request; planning approves the capacity trade-off; quality defines the evidence and sample disposition.

Write the trial question before reserving the machine

A useful question identifies what will change and what will be measured. For example: can the proposed fixture hold the specified feature through the agreed trial sequence under the stated conditions? “Try the new fixture” leaves the operator to guess the intended evidence.

The NIST experimental-design guidance starts with objectives and calls for ownership of the experimental plan. Use a suitable statistical design when the question requires one. The scheduling sheet below organises the resources and boundaries of the trial; it does not establish statistical validity.

Reserve the whole interruption

Illustrative scenario: the trial needs 35 minutes for setup, 40 minutes to run, 20 minutes for measurement while the machine remains reserved, and 25 minutes to restore the production setup. The total reservation is 120 minutes.

A 150-minute gap leaves 30 minutes unallocated. If the measurement step grows to 65 minutes, the reservation becomes 165 minutes and exceeds the gap by 15 minutes. The trial owner must stop at the agreed boundary or obtain a revised plan from the authorised planner. Starting the next customer job late is a capacity decision, even when the trial looks promising.

List any tasks that can run in parallel and justify that assumption. Inspection performed elsewhere may free the machine earlier, but only if the next setup does not destroy evidence or create an unsafe handback. Record the actual release time rather than assuming all measurement is off-machine work.

Keep trial output separate from saleable stock

Give trial samples a clear identity and disposition. Count material issued, samples retained, scrap, unused returns and any unresolved balance. Do not receive experimental pieces as accepted finished goods unless the required technical and quality approval explicitly permits it.

If the trial changes a setting or program, keep the prior approved configuration and record what was restored. Handback needs the site's required setup and first-piece checks. For the release record, use the drawing revision checklist alongside the relevant job instructions.

A failed trial still produces useful evidence when the question, conditions and observations are preserved. Keep the conclusion distinct from an instruction to change normal production. The technical owner reviews that change through the approved process.

Connect the reservation and evidence in Optiwise

Our machine calendars and production entries support the resource reservation and actual time record. With our no-code forms and linked records, you can configure a trial request containing the question, sample register, approval and handback evidence.

Review completed trials for reservation overruns, missing sample dispositions and delayed production handbacks. A trial is administratively closed when every sample has a recorded destination, the normal configuration has its required release, and displaced commitments have been reconciled. The engineering conclusion may remain open for further analysis.

Trial batch questions

Should the trial fit into leftover machine time?

Only when all required people, tools, inspection and restoration work also fit. A free machine alone is insufficient.

Does a successful trial approve normal production?

No. The technical owner must decide whether the evidence supports the intended change and complete the applicable release process.

Bring a recent trial request and its affected production plan to an Optiwise workflow demo.