Accepted Output & Operator Workload Test for Fillers

A catalogue cycle rate is not the same as accepted production output, and neither figure defines how much work an operator can support. A filling test should count accepted packages while recording rejects, replenishment, adjustments, stops and manual tasks under named conditions. This method helps buyers compare equipment and staffing requirements without converting a short demonstration into an unsupported shift, labor-saving or return-on-investment promise.

1. Define the decision and test boundary

State whether the test is for early configuration screening, quotation comparison, factory acceptance or site acceptance. Identify the exact machine, filler or connected line included in the boundary. List the product, container, closure, label, target fill and quality criteria. If downstream operations are excluded, make that visible in the result.

Separate nominal equipment speed from accepted output. The first can describe a controlled cycle or setting; the second requires a package to pass the agreed checks. Neither should be projected to a production day without recording planned and unplanned losses.

2. Freeze the start, finish and observation windows

Define when setup ends and measured production begins. Use an agreed stable-running condition rather than selecting the fastest short interval after the test. Record the measured duration, sample count and any excluded time with a reason. If the test includes more than one window, report each separately.

Define when an output is counted: at filler discharge, after closure, after label inspection or at the final line exit. A pack should not be counted as accepted before the required operations and checks are complete.

3. Write the accepted-package criteria before running

List the relevant checks for dose or net weight, fill height, container cleanliness, closure, leak, seal, label, code, appearance and reject handling. State the measuring instrument, resolution, sample frequency and calculation method. The buyer should provide destination or internal release criteria through a qualified reviewer.

Count rejects by reason. Do not remove setup waste or failed packs from the record without classification. If the sample is too small to support a stability conclusion, label the result as an observed trial rather than a guaranteed capability.

4. Record every production interruption

Use a simple event log with start time, end time, duration, cause, responsible station and recovery action. Separate planned replenishment, container or closure shortages, product refill, cleaning, quality checks, adjustment, jam, fault and downstream block. Where the cause is unknown, keep it open for review.

Short stops can consume significant operator attention even when total stopped time appears small. Record the number of interventions as well as their duration. Avoid assigning every interruption to the machine when material variation, site utilities or test setup may be involved.

5. Observe operator work without hiding assistance

Name the number of operators, their roles, training level and whether supplier technicians assisted. List recurring tasks such as loading containers, adding product, replenishing caps or labels, removing rejects, sampling quality, cleaning drips and responding to alarms. Record walking, lifting and reach conditions that affect whether the observed method is sustainable.

Separate machine-attending time from direct manual processing. An operator who can leave the machine briefly is not automatically available for another full task. If one person tends multiple stations, include simultaneous events and the recovery priority.

6. Include replenishment and normal disturbances

A steady run with full hoppers and preloaded packages does not measure routine operation. Include named refill or replenishment events when they are part of the intended production cycle. If product temperature, settling, foam or container variation changes during a run, record the condition.

For connected equipment, test a defined upstream or downstream interruption and observe stop logic, accumulation and restart. The line interface checklist can help define these handoffs.

7. Calculate only transparent test metrics

Report total produced, accepted, rejected and unclassified packages; measured time; stopped time; and the number of interventions. Accepted output for the window is accepted packages divided by the named observation time. If run time excludes stops, label it clearly and also show elapsed-window output.

Operator-capacity findings should remain descriptive unless the test design supports a numerical workload measure. State which tasks were observed, how often they occurred and what assistance was provided. Do not publish labor savings, annual output or ROI without site-specific, reviewed inputs.

8. Repeat the conditions that matter

Where the decision depends on repeatability, run more than one observation and include a restart, refill or other agreed disturbance. Test the relevant launch formats rather than assuming one package represents all change parts and products. Retain raw measurements, event logs, rejected samples or images as agreed.

Use the sample test protocol to control inputs, the FAT checklist for acceptance evidence and the semi-automatic versus automatic guide to frame staffing questions.

Information to define before the test

• Decision stage, equipment boundary and exact configuration.
• Representative product, package and launch format.
• Accepted-package checks and measurement methods.
• Observation duration, count point and treatment of setup.
• Planned replenishment, disturbance and restart events.
• Operator roles, permitted assistance and required records.

Send the proposed test conditions to MUJIU so the observation method can be agreed before the equipment trial.