Production evidence
What should a capping production run log record?
A useful capping production run log records the bottle and cap format, component batches, machine and feeder recipe, guide and belt settings, spindle or chuck setup, start and stop times, accepted output, reject reasons, faults, quality sample results, changeovers, maintenance and operator interventions. The purpose is to connect a finished-pack result with the exact process condition that produced it.
Record design starting point
Capture enough detail to reconstruct the pack and line state
Use the sequence below to capture enough evidence to reconstruct the pack, setup and line state without making the log impractical for operators. Cause-coded records are most useful when they identify the first known event and affected samples.
A production log should support a later comparison, not become a second operating manual. Use controlled format identifiers and short, consistent fault categories, while retaining photographs or samples separately when the event cannot be described reliably in one line.
Record the minimum evidence needed to reconstruct the run
| Record area | Examples to capture | Why it matters |
|---|---|---|
| Pack identity | SKU, bottle batch, cap batch, liner or closure variant and fill condition | Separates packaging variation from machine variation |
| Format setup | Machine height, guides, belt gap and height, spindle positions, conveyor and feeder settings | Supports repeatable changeover and setup comparison |
| Production result | Start/stop time, accepted output, planned stops and cause-coded downtime | Shows usable output rather than theoretical cycle rate |
| Quality evidence | Cap presence, height, visual result, torque/integrity samples and reject reason | Connects settings with accepted finished packs |
| Intervention | Jam clearance, adjustment, part change, cleaning, alarm and first-off approval | Identifies what changed before a fault improved or returned |
| People and handover | Operator, changeover confirmation, supervisor release and open action | Makes follow-up clear across shifts |
Use cause codes that help improvement
A single “machine stopped” code gives little information. Separate cap shortage, feeder jam, missing cap, bottle backup, bottle instability, torque failure, visual reject, cleaning, planned changeover and downstream blockage where those events are relevant. The code should reflect the first known cause, not only the final alarm.
Keep the list practical enough for operators to use consistently. Detailed photographs or notes can be attached for unusual events without turning every normal run into an engineering report.
Use the log to compare patterns, not to assign blame
Repeated faults by cap batch may indicate component variation. Drift after a known number of production hours may point towards wear or cleaning. A fault that appears after every changeover can indicate an incomplete format record. Comparing the evidence helps the production and maintenance teams test one hypothesis at a time.
Prepare a useful remote-support pack
- Relevant run-log extract and exact fault time.
- Photographs or video showing bottle and cap movement where safe.
- Good and faulty finished packs retained from the same run.
- Cap and bottle batch details.
- Current format settings and the last successful reference.
- Alarm text, sensor state and action already taken.
Related guidance
Continue the investigation or specification
Spindle capper maintenance schedule
Connect production symptoms with planned inspection and wear checks.
Troubleshooting guide
Use run evidence to isolate cap, bottle, feeder and machine causes.
Spindle capper setup checklist
Record a repeatable format before production begins.
Service and technical support
Prepare the evidence needed for remote or on-site review.