Container supply
Record empty-container shortages, unstable packs, guide adjustments and accumulation at the filler entry.
Line-performance evidence
How should OEE and good output be specified for a chemical filling line?
Measure accepted finished packs over a defined operating period and retain the loss-state evidence needed to explain availability, rate and quality.
- Written for chemical filling projects
- Uses verified first-party or authoritative information
- Final suitability depends on the actual product, pack and site
Direct answer
Specify accepted good packs over a defined operating period, then use OEE-style loss categories to explain why output was gained or lost.
A chemical filling line should not be accepted from the filler’s isolated cycle rate alone. Define the line start and finish points, planned production time, product and pack, reference rate, acceptable finished pack, reject rules and normal operating interruptions. Count saleable packs at the agreed discharge after filling, closure, label, code and inspection.
Overall equipment effectiveness (OEE) can organise availability, performance and quality losses, but the calculation is only useful when every party uses the same time base, rate and quality definition. The machine specification should state the raw events needed to reproduce the result rather than relying on one unexplained percentage.
Measure at the finished-pack boundary
Include fill quantity, closure, leak, label, code, inspection and reject confirmation so rework and failed packs are not counted as useful output.
Common definitions
Fix the measurement rules before comparing results.
| Term | Definition to agree | Typical evidence |
|---|---|---|
| Planned production time | The period in which the line is expected to make the specified product and pack, with planned exclusions stated | Shift or test start/finish, planned breaks, cleaning and changeover treatment |
| Availability | Time the line was capable of running compared with the agreed planned time | Stop start/end, fault code, cause, responsible station and recovery confirmation |
| Performance | Actual production rate compared with the agreed demonstrated reference rate for that SKU | Pack counts, run time, starved/blocked state, reduced-speed mode and station rates |
| Quality | Accepted packs compared with total packs processed under the agreed inspection rules | Fill, cap, leak, label, code and reject results; rework treatment |
| Good output | Accepted finished packs produced at the specified line boundary during the observation period | Counter reconciliation, reject confirmation and retained acceptance record |
Line balance
Record starved, blocked and fault states at the station that creates them.
Product and dosing
Separate low product, lost prime, quantity correction, nozzle cleaning and product-condition reductions.
Cap presentation and torque
Record cap replenishment, misfeeds, no-cap states, torque faults and filled-but-uncapped recovery.
Label and code
Identify web or ribbon changes, label absence, code verification and product-specific setup loss.
Reject and confirmation
Reconcile the detected fault, reject action, reject confirmation and final accepted count.
Accumulation and removal
Record blocked time caused by downstream packing, pallet movement or operator collection.
FAT and SAT
Use a repeatable test sequence that includes normal disturbances.
- Run the agreed product or justified test medium and representative pack at the specified rate.
- Reconcile infeed, processed, rejected, reworked and accepted-pack counts.
- Introduce agreed short starved and blocked conditions.
- Test cap, label, code and reject faults without creating unsafe product release.
- Stop and restart with containers remaining in the line.
- Record the event times, causes, states and recovery sequence.
- Repeat the site-critical changeover or replenishment task where included.
Do not hide these losses
- Waiting for product, containers or closures
- Minor repeated stops below the fault-report threshold
- Reduced speed caused by foam, splash or pack instability
- Unconfirmed rejects or manual rework
- First packs after start or changeover
- Cleaning, priming and product recovery
- Operator response and safe access time
Data and ownership
Retain the raw event trail needed to explain the headline result.
Agree counter sources, timestamps, fault codes, operator reasons and the treatment of planned stops before the test. Where the HMI stores recipes or event history, define what is supplied, retained and backed up. The site should be able to reconcile a reported efficiency figure with packs and events rather than accepting a dashboard value that cannot be reproduced.
Buyer questions
Questions about OEE, line balance and accepted output.
Is OEE the same as bottles per minute?
No. Bottles per minute is a rate under defined conditions. OEE separates availability, performance and quality over an agreed production period. A purchase specification should also state accepted good packs at the line discharge and the loss categories included.
Which speed should be used as the reference rate?
Use an agreed, demonstrated rate for the specific product and pack combination, not an unrelated catalogue maximum. Record nozzle count, dose, product condition, container, closure, label and all line stations included.
Should cleaning and changeover be included in OEE?
The site must define planned production time and loss categories consistently. Cleaning and changeover may be reported separately or included in a wider utilisation measure, but the rule must be fixed before comparing shifts, machines or suppliers.
Why can a fast filler produce a slow line?
The capper, labeler, coder, inspection, reject system, container supply, replenishment or operator response can repeatedly starve or block the filler. Insufficient accumulation and poor recovery logic amplify short downstream stops.
Can a short FAT prove production OEE?
A short FAT can prove defined functions, rates and recovery states under factory conditions, but it cannot by itself prove long-term site OEE. Use FAT to establish repeatable evidence and SAT/routine production to confirm installed performance.
Speak to Lancing
Define the accepted pack, test period and loss states before comparing line output.
Send the product and pack mix, required good output, shift pattern, changeover duty, downstream scope and quality checks.