In This Guide
- Define the Output You Actually Need
- Record Sustainable Rates on the Same Format
- Distinguish Starvation from Blockage
- Include Material Supply and Routine Replenishment
- Use Buffers to Manage Interruptions
- Turn the observation record into a targeted action
- Worked example: running rate and accepted output answer different questions
- Record one stop event and its effects on other stations
- Buyer Questions
- Related practical guides
- Equipment scope for the line review
- Review the output of your connected line

Selecting each machine from its headline output does not establish the output of the connected line. A washer, filler, capper or labeler can wait for incoming containers, pause behind accumulated packs or produce rejects that reduce useful delivery. This guide focuses on measuring those losses and locating the constraint. It complements equipment selection by turning a proposed bottle line into a format-specific output test.
Compare sustainable rates on the same production format, then measure acceptable finished packs over a defined elapsed period. Record starvation, blockage, faults, setup and rejects separately. Under steady running, the slowest sustainable stage constrains the line; short buffers can absorb interruptions but cannot remove a persistent capacity mismatch.
Define the Output You Actually Need
Specify the finished-pack condition at the measuring point: washed, filled, closed and labeled as applicable, with the required checks completed. Use consistent units across stages and identify the particular bottle, product, closure and label. A bottle count before capping is not automatically the count of acceptable finished packs.
Separate instantaneous running rate from output over the agreed production period. A practical elapsed-period measure is acceptable finished packs divided by elapsed time. State whether that period includes startup, planned replenishment or changeover so that competing results are comparable.
Record Sustainable Rates on the Same Format
Published references may use different samples and conditions. Compare bottle washing machines, filling machines and labeling machines only after their suitability for the required format is established. Include the selected multi head screw capping machine's bottle and closure combination rather than assuming head count alone determines the rate.
| Stage | Conditions to record |
|---|---|
| Washer | Container handling, wash sequence and transfer |
| Filler | Product, dose, fill result and refill conditions |
| Capper | Cap supply, engagement and closure acceptance |
| Labeler | Label roll, container presentation and application result |
| Packing | Workstation demand and finished-pack discharge |
Distinguish Starvation from Blockage
A starved machine lacks ready incoming containers or required materials. A blocked machine cannot discharge because the next stage or buffer is full. A faulted or stopped machine has its own interruption. Recording only a total downtime figure hides these different causes.
Observe several stations at the same time where possible. If the filler waits while the capper has no room to discharge, investigate downstream flow before concluding the filler is slow. Keep the stop cause, start time and recovery action so repeated interruptions can be traced to an interface or supply condition.
Include Material Supply and Routine Replenishment
Check how containers, product, closures and labels are supplied during the run. Record waiting for cap replenishment, roll replacement, product receiving or removal of completed packs. A short demonstration with every material prepared can conceal these operating demands.
Review the packing conveyor and manual workstations as part of the line. If finished packs cannot be removed or inspected at the incoming rate, upstream accumulation will eventually stop production. Define the staffing and material-handling conditions used in the trial instead of attributing every interruption to machine capacity.
Use Buffers to Manage Interruptions
Record the usable accumulation before and after the suspected constraint. A buffer can bridge a short pause when containers remain stable and controlled, but a continuously slower downstream machine will still fill it. Increasing conveyor length is therefore not always a capacity solution.
Test coordinated responses to full and empty conditions. Identify which upstream machine stops first and how the line restarts without a surge of containers. Confirm sensors and inter-machine signals in the supply scope; adjacent conveyors do not by themselves establish an integrated stop sequence.
Turn the observation record into a targeted action
Before observing the line, agree the product/format, period, staffing, quality checks and final counting point. Identify startup, replenishment, changeover and planned checks included in that period. State any excluded period separately; do not quietly remove a loss after reviewing the result.
- Record the boundary: note the start/end counters and times, accepted and rejected totals, and any work already between stations. Compare counters at the same point; a filler counter and a final pack counter can differ because of rejects and work in progress.
- Locate the originating event: distinguish the station with its own stop from stations waiting for material or downstream space. Record “cause unconfirmed” when the sequence does not establish an origin.
- Assign one practical action: a replenishment delay needs a supply and staffing review; a recurring transfer fault needs an equipment/format review; a sustained capacity mismatch needs a comparison of demonstrated stage rates on the same format.
- Name the owner and evidence: specify the change to assess, the person responsible, the repeat-trial condition and the result needed to close the issue. Do not replace the original record with the improved run.
- Compare like periods: record changed staffing, product, settings, buffer state or quality rules. An output increase obtained by excluding checks or counting rejected packs has not demonstrated the original requirement.
Worked example: running rate and accepted output answer different questions
Invented training data only. This example describes no actual H M Pharma Machines installation, speed guarantee or recommended trial duration. It uses one unchanged format and one final counting point. All packs counted during the two running periods have been classified at that point; no pack is counted twice.
| Elapsed interval | Recorded condition | Checked / rejected / accepted packs |
|---|---|---|
| 0–10 minutes | Startup and setup checks; no packs reach the counting point | 0 / 0 / 0 |
| 10–30 minutes | Running; 800 packs reach the counting point | 800 / 20 / 780 |
| 30–35 minutes | Label-roll replenishment; no finished output | 0 / 0 / 0 |
| 35–55 minutes | Running; 800 packs reach the counting point | 800 / 10 / 790 |
| 55–60 minutes | Planned check; no finished output | 0 / 0 / 0 |
| Total: 60 minutes | 40 running minutes and 20 minutes without output | 1,600 / 30 / 1,570 |
The gross running rate is 1,600 ÷ 40 = 40 packs/minute. Accepted output over the stated observation period is 1,570 ÷ 60 = 26.17 accepted packs/minute, rounded to two decimal places. Accepted output during running alone is 1,570 ÷ 40 = 39.25 packs/minute. These are different measures; label each with its count and time basis. The example includes startup and planned checks because its 60-minute boundary explicitly includes them.
This record shows the size of the observed losses, but it does not by itself prove which machine limits the running rate. Establish that from comparable stage observations and the sequence of starving, blocking and local stops. In a real trial, record work in progress at the start and end when comparing counts from different stations.
Record one stop event and its effects on other stations
Give an interruption one event ID and timestamp its beginning and recovery. Add the originating station and reason, then the affected stations and their states. Useful reason codes include material replenishment, handling fault, downstream blockage, upstream starvation and a planned check. Keep the observed state separate from a cause that still needs investigation.
| Field | What to enter | Use in the review |
|---|---|---|
| Event and time | Event ID, start, finish and elapsed duration | Build the line timeline without counting the same interval repeatedly. |
| Origin and evidence | First observed local stop, alarm or material event; evidence reference; confirmed or unconfirmed cause | Direct the investigation to the origin rather than the last machine seen stopped. |
| Affected stations | Station, observed state and interval; note when buffers fill or empty | Show how the original interruption propagates through the line. |
| Recovery and output | Action, restart time, accepted output after recovery and any rejected/held packs | Check both resumed flow and the required finished-pack condition. |
| Follow-up | Owner, change to test, comparable observation window and closure evidence | Turn the event into a measurable next action. |
In the invented example above, suppose the labeler is stopped for five minutes for a roll refill and the upstream capper, filler and washer are blocked during parts of that same interval as their buffers fill. That remains one five-minute line interval. Adding the overlapping station intervals would count some of the same time more than once. Station-level lost minutes may be useful as a separate measure; record their actual start/end times and keep that measure separate from total elapsed line time.
Buyer Questions
Will machines with the same published rate form a balanced line?
Not necessarily. Their references may use different formats and conditions. Compare sustainable operation and accepted output on the same pack, including transfers and routine interruptions.
Can a longer conveyor solve a bottleneck?
It may absorb a limited pause, but it cannot indefinitely balance a stage that consistently runs slower than incoming production. Determine whether the problem is interruption or sustained capacity.
Which count should be used for line acceptance?
Define the agreed measuring point and count acceptable packs meeting the required finished condition. Report rejects and the observation period separately.
Related practical guides
- Plan turntables, conveyors and buffers — review available accumulation and the response when it is full or empty.
- Review cap presentation and replenishment — identify feed interruptions before changing the capper speed.
- Define accepted and rejected output — agree the quality checks and final counting point for the trial.
Equipment scope for the line review
Review the selected washer, filler, multi-head screw capper, labeler and packing conveyor as connected stages. Their product pages describe equipment scope; the approved layout, interface schedule and a trial on the intended format establish the line conditions. The arithmetic example in this guide is self-authored training material, not a published capacity for those machines.
Review the output of your connected line
Share the required accepted output, product and format, station list, layout, observation period and a short stop record with the originating station identified. H M Pharma Machines can review the equipment and interfaces relevant to the observed constraint.
Request a line output review